Contract Syndication Steps

This topic provides high-level steps that you use with the Syndication feature to manage contracts between the PeopleSoft parent system and third-party remote systems. To syndicate the current version of a contract:

1. Use the parent system to set up the syndication system.

   This includes defining installation options, nodes, and remote locations.

   See Setting Up Contract Syndication.

2. Create a contract in the PeopleSoft parent system.

   Use the Purchase Order process option when adding a contract for syndication so that the PeopleSoft system can syndicate it to multiple remote systems. This process option supports sharing contract pricing information with multiple remote systems. You can only syndicate contracts that use other process options to a single remote system.

   See Defining Contracts for Syndication.

3. Syndicate the contract from the PeopleSoft parent system.

   You define the remote systems that can use the contract and reference which remote systems are to receive the contract definition. When the processing option is Purchase Order, you can specify multiple remote systems.

   When you syndicate a contract the first time, the system publishes the entire contract. The parent system tracks contract changes after the syndicated date and time so that with subsequent syndication of the contract, the system sends only the contract header, lines, and categories that have been modified.

   Note:

   The child system's inbound contract processing must be capable of supporting net changes to contracts and correctly interpreting any new lines versus changed lines as a part of the inbound processing.

   See Syndicating Supplier Contracts.

4. Remote systems receive contract information into their own processing framework.

   This depends on the remote system. Using remote systems, you map the contract to a contract import definition that PeopleSoft publishes.

5. Remote systems execute contract lines and summarized and publish summary information back to the PeopleSoft parent system.

   This information might include, for example, purchase orders, receipts, and voucher amounts. The remote system must include the capability to publish the contract activity back to the PeopleSoft parent system.

6. After receiving contract activities from the remote system, capture the parent activities.

   You perform this process in the parent system to capture any additional parent activity information for contracts that use the Purchase Order process option. This is how the system creates a consolidated view of information for viewing in the Review Contract Activity component.

   See Capturing Parent Activities.

7. Review contract activity for both the parent and remote nodes.

   Use this feature to review transactions against the parent contract. You can view both local (parent) and syndicated (remote) activity and navigate to view activities for specific remote systems.

   See Reviewing Contract Activities.

8. Publish the updated contract back to the remote systems using outbound messages.

   You can publish the entire contract again or only the updates made to the parent contract definition.

   See Publishing Outbound Messages.