Reviewing Performance Options
The Billing Interface:
Takes advantage of concurrent parallel processing.
Uses minimum edits.
The Billing Interface process takes advantage of concurrent parallel processing by using temporary tables. The Billing Interface is delivered with 10 sets of Billing Interface temporary tables. For the DB2/OS390 platform, only five sets of Billing Interface temporary tables are delivered. You may want to reduce or increase this number depending on your needs. The Billing Interface is set up for concurrent parallel processing. Consult with your PeopleSoft database administrator to determine how many temporary table sets you need for optimal performance.
The Billing Interface process performs multiple edits to verify that data in the staging table is valid. The process also performs multiple levels of defaults so that the source systems need to pass only minimum information. Because of this functionality, however, running an interface batch can be time consuming.
PeopleSoft Billing is delivered with additional options that you can set on the interface run control page to get more control over the interface process. To use these options, you must modify the page to display the Run Option field.
You can select one of these values in the field:
Field or Control |
Description |
|---|---|
All |
Run with all edits. |
Edit |
Run edits only. |
Min (minimum) |
Run with minimum edits. |
Run Option 1: All (Run with All Edits)
All is the default value. If you select All, the Billing Interface runs normally, performs all possible editing, and then creates a bill structure. To run the Billing Interface with an option other than All, you must modify the interface run control page.
Run Option 2: Edit (Run Edits Only)
The Edit option performs edits only and marks lines that have an error with an ERR load status. Lines with no errors are marked with a load status of NEW. The Edit option does not create bills. When you select Edit, you can review transactions that received an error status and correct them. After you correct any errors, you must still select either Min or All to create bills.
Run Option 3: Min (Run with Minimum Edits)
Only customers who require manual control over editing data from source systems should select Min. These two scenarios describe when to use this option:
Field or Control |
Description |
|---|---|
Scenario A |
If your installation requires the flexibility to run the interface as a two-step process, you can run the Edit option first. After you correct any errors, you can run the Billing Interface again in Min to actually create bills. Note: The Billing Interface process does not verify that you ran the Edit option before you ran the Min option. If you do not run the Edit option first, you may create a bill with invalid billing information. |
Scenario B |
If execution speed is more important than comprehensive validation from the Billing Interface process, you can elect to run the Min option, which greatly reduces the time that it takes for the interface process to complete. Note: When you elect to run Min, the Billing Interface does not fully validate the data. Consequently, you may create bills with bad billing information (such as a bill with an invalid customer ID). To avoid this risk, the source system must validate billable activity before passing it to the Billing Interface. |
Other Performance Considerations
Consider these points when you create a new bill by IDs:
Use the fewest number of bill by fields that meet your requirements.
From external interfaces, you may want to prepopulate fields if you know their values.
This reduces the work that the Billing Interface must do and can significantly improve batch performance.
See the product documentation for PeopleTools: Application Engine