Understanding Processing Time

After you resolve conversion errors, you can use the suggestions in this table to improve processing time:

Suggestion

Description

Create larger batches.

Organize the data into larger batches. Processing time can be improved if the program is not required to open and close batches.

Note: Gains in performance as a result of creating larger batches might be offset by an increase in the amount of time that is required to post the batch.

Also, although an error on one record might not prevent the batch processor from successfully processing the rest of the batch, an error while posting the batch does prevent all records in the batch from posting.

Create multiple versions of the batch processor program.

Create multiple versions of the batch processor program (R03B11Z1A) and run them simultaneously.

To do this, modify the data in the batch transaction tables so that you have several large batches. Then create additional versions of the program and modify the processing options to process one batch. Finally, run all versions of the program simultaneously.

Note: Gains in performance that you achieve by creating multiple versions of the batch processor program are extremely dependent on the type of data that you process. In some instances, due to technical issues such as record locks, running multiple versions simultaneously could actually increase processing time. To definitively know which solution is best for the data, you should perform tests.

Enter as much information as available.

Reduce the amount of time that the system requires to retrieve default information by entering the information directly into the F03B11Z1 and F0911Z1 tables.

For example, enter the customer's alpha name into the Explanation field (VNEXA) in the F0911Z1 table. Examples of other information that the system retrieves for processing are payment terms, exchange rates, company numbers, and so on. Then, when the batch processor program runs, the system validates only the information that is provided, rather than having to retrieve and validate the information.

Deactivate the Cost Management Constants (System 16).

If you are not using the Advanced Cost Accounting System (system 16), verify that the Activate Cost Objects (CO01) and Activate Activity Based Costing (CO03) fields are not selected in the Cost Management Constants program (P1609). You access the Cost Management Constants program from menu G1641.

Run the batch program on the server where the data and related programs reside.

Run the batch processor program (R03B11Z1A) on the server where the batch tables (F03B11Z1 and F0911Z1) and other related tables, such as Customer Master by Line of Business (F03012), Currency Exchange Rates (F0015), Tax Areas (F4008), and so forth, reside.

Also, ensure that the applicable master business functions (P03B0011 and P0900049), as well as any other related programs, are located on the same server.