ChartField Combination Editing in Batch or Background Processing

To make combination editing background processing generic to all PeopleSoft applications, combination editing uses a ChartField Combination Editing template, which is discussed in a separate topic in this topic. The template defines the table structure of the various application transaction records. The combination editing process uses this structural information to perform its edit.

Record templates have a unique name that is applicable to a particular PeopleSoft application. You supply that name for your application to enable background combination editing.

Select the name of the combination edit template on the ChartField Combination Template page, in the Template field. The template is used only for background, or batch, editing.

Various underlying tables are available to combination editing that support batch editing. These underlying table options are also described in a separate topic in this topic.

The system performs batch, or background, combination editing at the time of journal editing or during accounting line and voucher line edits in the various PeopleSoft General Ledger feeder systems. In any case, editing occurs before posting journals to the general ledger.

Note:

During journal editing , the Transaction Set Editor (TSE) determines whether a journal line is valid by finding a ChartField on a line, and then checking the ChartField against its ChartField table to make sure that the ChartField itself is valid. If the ChartField is invalid, the TSE marks it invalid and immediately excludes the journal line from the combination editing process.

Combination editing also validates whether a combination group is associated with a business unit and ledger group during a batch combination edit process.

Batch Validation of Project Costing ChartFields

The following PeopleSoft applications have the ability to perform Project Costing ChartField validation through the batch Combination Edit process:

  • Asset Management

  • General Ledger

  • Grants

  • Payables

  • Receivables

  • Purchasing

  • Project Costing

Similar to the online validation of detail Project ChartFields, PeopleSoft enables validation of Project ChartFields through batch combination edit by calling PC_EDIT. The online Combination Edit does not call project validation; however, the existing online project edits handle the validation.

The following Project Costing edits are included in the batch combination edit:

  • Validation of the Project Costing Business Unit, Project ID, and Activity ID combination

  • Enforcement of Project and Activity Status Control check (Set Up Financials/Supply Chain, Install, Installation Options, Project Costing Integration)

  • Enforcement of the Input Control option (Set Up Financials/Supply Chain, Business Unit Related, Project Costing, Project Costing Options)

  • Enforcement of the Dynamic Edit Tables option (Set Up Financials/Supply Chain, Business Unit Related, Project Costing, Project Costing Definition)

  • Validation of Project Costing and General Ledger Business Unit mapping via the Project Costing Integration Template (Set Up Financials/Supply Chain, Product Related, Project Costing, Project Options, Integration Templates, General Ledger Integration)

  • Enforcement of the Analysis Type is required (for General Ledger journals only)

To implement the validation of Project Costing ChartFields through batch combination edit,

  • Project Costing must be an installed product.

  • Use the Project Costing Options page to Establish project-related transaction fields that are required for importing transactions from other PeopleSoft applications (Set Up Financials/Supply Chain, Business Unit Related, Project Costing, Project Costing Options).

In General Ledger, you can perform validation of Project Costing ChartFields of Spreadsheet journals or from Flat File Journal Import using batch edit, for example. In Payables, the batch edit occurs during the Voucher Build process, for example.

See PeopleSoft General Ledger Documentation Update: Project Costing Edit, Note number 1063525.1, on My Oracle Support, at: https://support.oracle.com/CSP/ui/flash.html.

Batch Combination Editing Using the Combo Data Table or a User-Defined Data Table

The combination editing process repeats the following steps for each combination group that you associate with a business unit and ledger group for which you select either the Combo Data table or a user-defined combination data table:

  • Combination editing compares all transaction lines against the table.

    If the combination exists in the data table, it marks the line as valid or invalid depending on the Combination Group Defines option that you select.

    If the anchor ChartField value has a combination rule defined for it and if the entire combination is not found, the combination fails the edit.

    If the anchor ChartField value does not have a combination rule defined for it, then the line is marked with the state that you select—either Mark Invalid or Mark Valid on the ChartField Combination Editing Group page for the Anchor Values Not in Rules field.

  • When the program encounters an invalid combination, it logs the invalid transaction with an error status message in the error log records that are defined in the Combination template.

Batch Combination Editing Using the Master Selector Tables Option

If you select the master selector tables option for the combination group, the batch combination editing process does the following:

  • It retrieves the combination groups that are attached to the business unit and ledger group that you specify.

  • It loops through the combination groups and determines if the master selector tables are built for a group. If you have not built them, it builds them dynamically according to the rules, using Application Engine temporary tables.

  • It expands the master selector tables to create an Application Engine temporary COMB_EXP_TAO table that contains the permutations of values for the combinations.

  • It compares each journal line against the COMB_EXP_TAO table and if the combination exists in the table, it marks the line as valid or invalid depending on the option that you select in the Combination Group Defines field.

  • It analyzes transaction lines that are not found on the table to determine if an anchor ChartField has a value for which you have defined a combination rule.

    • If the anchor ChartField value has a combination rule defined for it and if the entire combination is not found, the combination fails.

    • If the anchor ChartField value does not have a combination rule defined for it, then the line is marked with the state you select, - either Mark Invalid or Mark Valid on the ChartField Combination Editing Group page in the Anchor Values Not in Rules field.

      Note:

      In other words, if the combination fails, it is marked valid or invalid depending on the attribute that is selected for this field.

  • If the process encounters an invalid combination, it logs the invalid transaction with an error status message in the error log records defined in the ChartField Combination Editing Template.

  • When the edits are complete, the process deletes the COMB_EXP_TAO tables.