This chapter provides an overview of messaging and discusses how to:
Set up messages.
Publish outbound messages.
Process inbound messages.
Messaging is an architecture that uses a publish and subscribe model to integrate PeopleSoft applications with each other and with third-party applications. Messaging enables applications to publish data that can be subscribed to by multiple processes. These processes are located on the same database and server, or located on another database and server. This functionality works in an asynchronous environment, which means that the publisher doesn't need to be connected to the subscriber when publishing the data. This is comparable to the way in which email uses queues to guarantee the delivery of a message to its subscribers.
Messaging offers a more automated, timely, and efficient way to send data across systems than was previously available. Messaging helps synchronize data stored in different systems, enables system-to-system workflow, and supports business-to-business integration through the internet using XML and HTTP.
See Also
Enterprise PeopleTools 8.46 PeopleBook: Integration Broker
To set up an existing enterprise integration point (EIP) for publication or subscription:
Activate the message.
Messages are delivered as inactive, so you need to activate each message prior to publication or subscription.
Define a message node.
Configure the message channel associated with the message.
Set up chunking rules for outbound publication messages.
Define business unit and setID chunking rules that are standard on any PeopleSoft database and create user-defined chunking rules. Also, establish the chunking field for subscribing node mapping relationships and on Route Publication PeopleCode used to route the message chunking to the correct subscribing node.
Activate a publish rule for outbound publication messages.
Address any special setup steps defined for a particular EIP.
To access these special considerations, access the documentation on the selected EIP in the EIP Catalog. Access the format information for the EIP.
For example, click the PO_EXPECTED_RECEIPT_SHIPTO Format link to access information for the PO_EXPECTED_RECEIPT_SHIPTO message. In the section, scroll down to the data rules and review the information in the Special Setup Considerations subtopic section.
See Also
To publish an outbound message:
Run the appropriate process to publish the message data to the outbound staging tables.
For information about the processes used to stage message data for each PeopleSoft Purchasing outbound message, see the usage details for the message in the following table.
Use the common Publish Outbound Message page to publish the staged message data:
Select the check box to activate the link associated with your message.
Click the link to access the Selection Criteria page, where you can define the run control parameters for the process that will publish your message.
Click OK to return to the Publish Outbound Message page.
Click the RUN button to access the Process Scheduler Request page, from which you can publish your message.
Take note of the process instance number.
Click the Process Monitor link to access the Process Requests - Process List page, where you can confirm that your process instance ran successfully.
Access the Integration Broker Monitor to confirm that your message was published successfully.
In the Channel Name column, look for an instance of the appropriate message channel. Your published message should have incremented the number in the Done column.
Click the Done number link to access the Integration Broker Monitor - Message Instances page, where you can view details about the message that you published.
If more than one instance of a message appears, the most recently published message instance appears last in the list.
Click the Details link to access the Message Details page, where you can view the contents of your published message in the XML Message Viewer or the Structured Message Viewer.
The following table lists PeopleSoft Purchasing outbound messages and usage information.
Note. For the message to work as designed, you must have already activated the message, activated the appropriate batch publish rules, and defined chunking.
PeopleSoft Purchasing supports these EDI outbound transactions:
Request For Quote (RFQ).
Return To Vendor (RTV).
Purchase Order (PO) Dispatch/ PO Change Request.
Purchase Order Expected Receipts.
See Setting Up and Publishing the Purchase Order Expected Receipts EIP.
Purchase Order Receipt Notification.
See Setting Up and Publishing the Purchase Order Receipt Notification EIP.
Credit Card Data.
See Also
Enterprise PeopleTools 8.46 PeopleBook: Integration Broker
Enterprise PeopleTools 8.46 PeopleBook: PeopleSoft Process Scheduler
Processing Outbound EDI Transactions
This section discusses how to:
Subscribe to the Item Price List EIP.
Subscribe to the GPO Load Manufacturer Price EIP.
Subscribe to the GPO Load Distributor Price EIP.
Third-party systems can send information to PeopleSoft applications using a number of integration points established throughout the system. Depending on the application, various technologies provide multiple options for interacting with PeopleSoft. Each option provides audit trails, validations, and error handling to insure that data integrity is maintained within the PeopleSoft database.
Subscribing to inbound messages involves using the Transaction Maintenance page and Data Definition Maintenance page to view all transaction- and data definition-based information in the transaction log. Detail pages for each transaction type, accessible from the Transaction Maintenance page, provide error messages and transaction details and enable you to revise fields containing errors.
To subscribe to a message:
Use the common Transaction Maintenance or Data Definition Maintenance pages to view message data picked up in the subscription process.
For information about the appropriate page to use for a particular message, see the usage details for the message in the following table.
Run the appropriate process to move message data from the staging tables to the application tables.
For information about the processes used to move staged message data to the application tables, see the usage details for the message in the following table.
PeopleSoft Purchasing supports these EDI inbound transactions:
RFQ Response.
Purchase Order Receipt.
Advance Shipment Receipt (ASR).
Purchase Order/ Purchase Order Change Acknowledgement.
See Subscribing to the Purchase Order and Purchase Order Change Order Acknowledgement EIP.
Item Price List.
Purchase Order Requisition.
Procurement Card.
GPO Load Manufacturer Price.
GPO Load Distributor Price.
See Also
Processing Inbound EDI Transactions
Enterprise PeopleTools 8.46 PeopleBook: Integration Broker
Enterprise PeopleTools 8.46 PeopleBook: PeopleSoft Process Scheduler
The Item Price List EIP loads item price list data from a third-party application to the PO Item staging tables.
This asynchronous batch subscribe message also supports flat-file processing for EDI transaction X.12 832.
Run the PO Item Price List Load process (PO_ITMLOAD) and Item Loader process (IN_ITMLOAD) to move the data from the staging tables to application tables.
This section discusses how to subscribe to the Item Price List EIP.
Page Name |
Object Name |
Navigation |
Usage |
RUN_PO_ITMLOAD |
SCM Integrations, Process Transactions, Items, Item Price List Batch Load, Item Price List |
Specify the parameters for the PO Item Price List Load process. |
|
RUN_IN_ITMLOAD |
SCM Integrations, Process Transactions, Items, Item Loader |
Flag items for standard price updating and business unit standard price updating when Item/Vendor UOM price records are entered in batch. The Item Loader process (IN_ITMLOAD) is run to update your PeopleSoft application tables with the item data in the Item Loader staging tables. |
|
BCT_SETUP_FS |
SCM Integrations, Setup, Data Collection, Data Collection Setup |
Set the option to keep transaction log history for electronic data collection transactions and to set the default file suffix. |
|
EO_EIP_CTL_MAINT |
SCM Integrations, Transaction Error Handling, Maintain Data Definitions, Data Def Maint (data definition maintenance) |
View data detail or correct errors for subscribe messages that contain data rather than transactions. |
Before you can subscribe to the Item Price List EIP, you must:
Activate the ITEM_PRICELIST_LOAD message.
Run the PO Item Price List Load process (PO_ITMLOAD) and Item Loader process (IN_ITMLOAD) to move the data from the staging tables to application tables.
Use the Data Definition Maintenance pages to view message data and correct error messages that are picked up in the subscription process.
The GPO Load Manufacturer Price EIP subscribes to a message that enables you to load GPO inbound item price list data from a third-party application to the PO Item staging tables.
This asynchronous batch subscribe message also supports flat-file processing for EDI transactions.
This section discusses how to subscribe to the GPO Load Manufacturer Price EIP.
Page Name |
Object Name |
Navigation |
Usage |
GPO Load Manufacturer Price |
RUN_GPO_MFG_PRICE |
SCM Integrations, Process Transactions, Items, GPO Load Manufacturer Price |
Specify the parameters for the GPO Load Manufacturer Price process. |
RUN_IN_ITMLOAD |
SCM Integrations, Process Transactions, Items, Item Loader |
Flag items for standard price updating and business unit standard price updating when Item/Vendor UOM price records are entered in batch. The Item Loader process (IN_ITMLOAD) is run to update your PeopleSoft application tables with the item data in the Item Loader staging tables. |
|
BCT_SETUP_FS |
SCM Integrations, Setup, Data Collections, Data Collection Setup |
Set the option to keep transaction log history for electronic data collection transactions and to set the default file suffix. |
|
EO_EIP_CTL_MAINT |
SCM Integrations, Transaction Error Handling, Maintain Data Definitions, Data Def Maint (data definition maintenance) |
View data detail or correct errors for subscribe messages that contain data rather than transactions. |
Before you can subscribe to the GPO Load Manufacturer Price EIP, you must:
Activate the ITEM_MFG_GPO_LOAD message.
Run the GPO Load Manufacturer Price process (GPO_MFG_PRICE) and Item Loader process (IN_ITMLOAD) to move the data from the staging tables to application tables.
Use the Data Definition Maintenance pages to view message data and correct error messages that are picked up in the subscription process.
The GPO Load Distributor Price EIP subscribes to a message that enables you to load GPO inbound item price list data from a third-party application to the PO Item staging tables.
This asynchronous batch subscribe message also supports flat-file processing for EDI transactions.
This section discusses how to subscribe to the GPO Load Distributor Price EIP.
Page Name |
Object Name |
Navigation |
Usage |
GPO Load Distributor Price |
RUN_GPO_VNDR_PRICE |
SCM Integrations, Process Transactions, Items, GPO Load Distributor Price |
Subscribe to the GPO Load Distributor Price EIP. |
RUN_IN_ITMLOAD |
SCM Integrations, Process Transactions, Items, Item Loader |
Flag items for standard price updating and business unit standard price updating when Item/Vendor UOM price records are entered in batch. The Item Loader process (IN_ITMLOAD) is run to update your PeopleSoft application tables with the item data in the Item Loader staging tables. |
|
BCT_SETUP_FS |
SCM Integrations, Setup, Data Collections, Data Collection Setup |
Set the option to keep transaction log history for electronic data collection transactions and to set the default file suffix. |
|
EO_EIP_CTL_MAINT |
SCM Integrations, Transaction Error Handling, Maintain Data Definitions, Data Def Maint (data definition maintenance) |
View data detail or correct errors for subscribe messages that contain data rather than transactions. |
Before you can subscribe to the GPO Load Distributor Price EIP, you must:
Activate the ITEM_VNDR_GPO_LOAD message.
Run the GPO Load Distributor Price process (GPO_VNDR_PRICE) and Item Loader process (IN_ITMLOAD) to move the data from the staging tables to application tables.
Use the Data Definition Maintenance pages to view message data and correct error messages that are picked up in the subscription process.