Use Async Start Date for Billing Transactions (E95)

Purpose: Use this screen to define whether to use the Async start date as the billing date for billing transactions.

Using the Async start date may be useful if, for example, you want to change the cutoff for a group of shipments.

Yes/no field: Select this field if you want the option to use the Async start date as the billing date for billing transactions.

To start the asyncs:

• select Start for the CNTL_ASYNC; see Working with the CNTL_ASYNC Job.

• create a schedule for a periodic process that contains the STRASYN periodic function to start asyncs.

Function	Description	Program	Summary
STRASYN	Start asyncs	MSSTRASYNC	Calls the Controlling Data Queue (CNTL_ASYNC) in Background Job Control (MBJC) and starts the background jobs. This periodic function performs the same updates as selecting Start for the CNTL_ASYNC to start the background jobs. See Starting the Background ASYNC Jobs.
For more information: • See Working with Periodic Processes (WPPR) for information on how to assign each function to a periodic process. • See Executing Periodic Processes (EPRO) for more information on scheduling a periodic process to run at a specified time.

The fields updated with the date you started asyncs are:

• invoice date (all related tables except the Invoice Header table)

• inventory transaction date

Sales Audit integration: It is recommended to have this field unselected if you use the Oracle Retail Sales Audit Integration.

Leave this field unselected if you want the system to use the system date as the billing date.