Processing Inbound Service Operations
Third-party systems can send PeopleSoft applications information using a number of integration points established throughout the system. Depending on the application, various technologies provide multiple options for interacting with the PeopleSoft system. Each option provides audit trails, validations, and error handling to insure that data integrity is maintained within the PeopleSoft database.
Depending on the requirements of the interacting system and the integration point within the PeopleSoft system, various technologies are used to receive transactions into the PeopleSoft system:
Application Message Based Transaction
The PeopleSoft Application Messaging functionality provides a method for asynchronous communications between external systems and PeopleSoft applications using industry standard XML-formatted messages. XML messages are automatically loaded into the PeopleSoft system by setting the queue status to run for each message type. You can view all transactions in the transaction log and access the detail pages that enable you to correct transaction errors. Most subscription processes get associated to handlers. Handlers are then defined on a service operation.
The Inbound File Publish utility, which utilizes the File Layout Object tool, may also be used to automatically convert flat file input to XML-based application messages.
Electronic Data Collection Transaction Pages
PeopleSoft CRM includes transaction pages for many of the inbound transactions. The transaction pages are designed for quick data entry. There are minimal edits, and no application database updates are performed in these pages as the background programs scanning the transaction logs handle detail processing. The transaction pages provide a method of quick data entry for much of the transaction-based information processed by the system. You can enter the transactions directly onto the page, or attach a wedge and bar code reader to take advantage of bar code scanning benefits.
System-Generated Transactions
Several transactions that are fed in the transaction log are generated from internal application programs. By generating these transactions, applications push heavy processing functions to a background mode.
Validations, Error Handling, and Database Updates
Most inbound transactions, no matter which technology delivers them to the PeopleSoft system, are loaded into staging tables, where they are validated by background routines scanning these transaction logs awaiting incoming work. If errors are found, the transaction status in the transaction log is changed to Error, and rows are inserted into error tables for each error message.
Error messages appear on the Transaction Maintenance page for transactional type data such as, inventory adjustments and purchase order receipts (select ).
For definitional type data such as item master and bills of material, the Data Definition page is used to review and correct the erroneous information.
Once you have corrected the information and saved the page, the transaction is ready to be reprocessed.
Some transactions provide functionality to immediately validate and update application tables from subscription processes. For example, the Consumer and Par Location Count transactions both attempt to update the application tables, but if errors are found, the transactions write the data to the error tables so that corrections can be made.
SeePeopleTools: Integration Broker and PeopleTools: Integration Broker Service Operations Monitorproduct documentation.