Setting Up Contract Syndication

The PeopleSoft parent system is always the system of record for the contract. You create contracts on the parent system and syndicate them to the remote system. The remote system receives the contract and executes contract releases and summarizes the release activity and sends it back to the parent system.

Setting Up the Parent System

A service operation definition consists of general information about an operation, such as its name, and alias if one has been defined. It also specifies an operation type, which determines how the operation is to be processed, synchronously or asynchronously. The CS_PROCUREMENT_CNTRCT is a service operation that is processed asynchronously. This means that the system creates the message and sends it, but does not suspend activity waiting for a response to the message. In addition, the service operation definition contains routings, which determine the direction, inbound or outbound, of the service operation. A service operation has one or more handlers, which contain and run the programming logic for sending or receiving the message and manipulating message content.

See "Understanding PeopleSoft Integration Broker," Incoming and Outgoing Message Flows, PeopleTools: Integration Broker

Use these steps to set up the parent system:

  1. Activate the CS_PROCUREMENT_CNTRCT service operation.

    This enables publishing contracts from the parent system. PeopleSoft delivers service operations in PeopleSoft Integration Broker with a default status of Inactive. You must activate each service operation before attempting to send or receive data from a third-party source or another PeopleSoft system. To activate the service operation:

    1. Select PeopleTools > Integration Broker > Integration Setup > Service Operations.

    2. Select CS_PROCUREMENT_CNTRCT in the Service Operations field.

    3. Click Search.

      The service operation appears.

    4. Click the Service Operation link.

      You specify messages for service operations in the Message Information section of the Service Operations - General page. Because the CS_PROCUREMENT_CNTRCT service operation is already available, it appears in the section. The message defines the structure of the data that is contained in the service operation. The service operation type determines the number of messages and message types (request or response) that you specify.

    5. Set the CS_PROCUREMENT_CNTRCT service to Active using the Active check box in the Default Service Operation Version group box, and click the Save button.

      Note: In addition to outbound syndication, you can also use the CS_PROCUREMENT_CNTRCT service operation with inbound contract message processing to load contracts into the parent system. However, contract syndication in the parent PeopleSoft system uses the outbound service operation only. See Understanding How to Load Contracts into the Parent System

    6. Select the Handlers tab.

      The page provides summary information about handlers that have been added to an operation. Two individual server processes work together to handle incoming requests. One server process functions as a dispatcher, while the other functions as a handler. You can specify an application class as a handler for a service operation. The CS_PROCUREMENT_CNTRCT service operation uses the application class handler CS_STAGE.

      See "Sending and Receiving Messages,"PeopleTools: Integration Broker

    7. Ensure that Active is selected in the Status field on the Handlers tab, and click the Save button.

    8. Select the Routings tab.

      This page provides access to routing information that have been added to an operation. Routings determine the direction, outbound for syndication, of the service operation. The routing page is where you specify the sending and receiving node information. The Sender Node field value should be the default local node for the CS_PROCUREMENT_CNTRCT_OUT routing. This value appears on the Nodes page and contains Y in the Local Node Name column for the node.

      The receiver node for the CS_PROCUREMENT_CNTRCT_OUT routing should be PSFT_XOUTBND .

      If you have defined a different external node for use with a particular remote system, you can create a new routing and enter that node in the Receiver Node field. There must be a routing created for each remote system where the sender node is the default local node, and the receiver node is the remote node.

    9. Select the routings you are going to use, and click the Activate Selected Routings button.

    10. Click the Save button.

      See Understanding Integration Setup, PeopleTools: Integration Broker

  2. Activate the CS_ACTIVITY_CNTRCT service operation to enable receiving activity summaries into the parent system.

    This step is the same as step 1 except for the Routings tab. You only need to activate the inbound routing where the Sender Node is ANY and the Receiver Node is the default local node.

  3. Use the Gateways page to define gateways for parent and remote systems.

    The PARENT gateway, points to the application server/web server used to access the local/parent database. The REMOTE gateway points to the application server/web server used to access the remote database. To access the page, select PeopleTools > Integration Broker > Configuration > Gateways.

    See "Managing Integration Gateways," PeopleTools: Integration Broker

  4. Set the Queue Status for the CS_CONTRACT_SYNDICATION queue to Run.

    To set the status:

    1. Select: PeopleTools > Monitor Service Operations > Administration > Queue Status.

    2. Scroll to the CS_CONTRACT_SYNDICATION queue.

    3. Click the Run button if the Queue Status is Paused.

      The status should be Running.

  5. Define the parent and remote system nodes and the transactions used for syndication.

    To access the page, select: PeopleTools > Integration Broker > Integration Setup > Node. To define settings for the parent system:

    1. Use the Nodes search page to open the node that has the Default Local Node = Y.

      This defines the application server/web server that connects to the parent system.

    2. Click the Connectors tab.

    3. Enter the gateway and connector ID for the parent system.

      Normally, the gateway ID is LOCAL and the connector ID is PSFTTARGET. You must define the remote node on the parent system, and add a routing for the CS_PROCUREMENT_CNTRCT service operation as described in Step H1.

      Note: If a connector does not have properties, you can use the Gateways page to setup gateway and connector IDs. Step 3 provides the purpose and a link for more information about defining the properties.

      Note: If you are loading contracts into the parent system (this is not a syndication feature), you must activate the inbound routing for the CS_PROCUREMENT_CNTRCT service operation.

  6. Use the Installation Options - Supplier Contract Management Page to set up the application for syndication use.

Summary Information for Remote Systems

This section provides considerations for setting up remote systems. Remote systems require the capability to subscribe to contract messages defined with the structure contained in the PeopleSoft parent system CS_PROCUREMENT_CNTRCT service operation.

Note: It's assumed that the remote system contains a contract structure that can have related purchase order and voucher-related activity placed against it similar to that of the PeopleSoft parent system. The mappings and implementation required for the structure depend on the remote system capability.

You should also consider these capabilities for remote systems:

  • Process mappings of contract messages to remote systems contract structure.

  • Process the addition of new contracts and changes to existing contracts based on information sent in the CS_PROCUREMENT_CNTRCT service operation structure.

  • Create and publish summary activity information for related purchase orders, receipts, and vouchers in the format required for the CS_ACTIVITY_CNTRCT service operation.