1. SUNDAY

Indicate the number of lag days that should be allowed for posting the transactions which were entered on Sunday. For example, entering 1 day means that Sunday's work will post Monday. Entering 2 days means that Sunday's work will post Tuesday.

EXAMPLE: Type 2 (RET)

FIELDS 2 - 7 MONDAY - SATURDAY

For the remaining days of the week, indicate how many lag days should be allowed for posting the transactions entered on those days.

EXAMPLE: (See illustration and comments below.)

8. SWEEP PERIOD

Entering a number of days in this field affects the start date on the Accounting DBR. For example, entering "29" causes the report to be run for a period of 30 days: the business day of the DBR plus the 29 previous days. Leaving this field blank means that the DBR will be run for only the business day itself without going back to pick up any previous days.

The purpose of the 'sweep' is to pick up transactions that might have been missed.

EXAMPLE: Type 30 (RET)

NOTE: Many operations choose to have automatic posting run daily. However, Thermeon's Customer Support Dept. can set it up to run on other schedules such as weekly, twice a month, or monthly. When automatic posting is run for multiple days, each day posts separately. That is, a separate Accounting DBR is produced for each day. When a number is present in this field (Sweep period), only the first DBR will include the sweep days.

WARNING: Operations that use the Oracle Financials Accounting Data Export logic, PSTRA7, MUST SET THIS VALUE TO ZERO. Setting this to any other value will cause edited RAs to be exported more than once to Oracle.