Product Interface and System Transaction Categorization

PeopleSoft delivers one or more System Transactions for each product primarily to provide the following:

  • An interface to the Inter/IntraUnit Central Processor for each product or application and its transactions that might require system generated inter and intraunit balancing lines.

  • Segregation of inter and intraunit payables and receivables by type of System Transaction, such as accounts payable voucher or general ledger journal.

  • Definition of options that are appropriate only to a particular System Transaction, such as whether to create an AP (accounts payable) Voucher and an AR (accounts receivable) Item for an InterUnit Bill.

The System Transaction provides predefined information about the tables and fields involved in an application transaction and supplies run-time parameters to the Centralized Inter/IntraUnit Processor.

There are some cases where there are multiple System Transaction Codes for a product, even when all of the technical details for the interface to the central processor are the same, such as AP (accounts payable) Vouchers and AP (accounts payable) Payments. This allows you to associate each system transaction with a different user-defined Transaction Code, which is the key to how you set up ChartFields for InterUnit and IntraUnit payable and receivable entries.

Transaction Codes are defined on the Transaction Code page. Each Transaction Code that you define can be mapped to one or more of the System Transactions on the System Transaction Map page, but each System Transaction can have only one Transaction Code for all products with the exception of general ledger. Once mapped, System Transactions determine the Transaction Codes available to a product for further categorization. If your inter and intraunit accounting does not differ across products and transactions you can define a single Transaction Code and map it to all the System Transactions.

Only the General Ledger System Transaction GLJ (general ledger journal) allows the mapping of multiple Transaction Codes so you can create additional subset categorizations for an inter and intraunit transaction. For example, you could create the following Transaction Codes and map them both to the General Ledger System Transaction.

  • ADVANCES (Intercompany cash advances)

  • INTEREST (Interest on Intercompany advances)

This enables you to further segregate and categorize interunit transactions within General Ledger by maintaining all advances in a separate category of interunit activity and inter company interest on these advances in another category.

Note:

When setting up business units across products, you must include all business units in the same ledger group to use the interunit processor functionality.