Reviewing EIP Examples

In this chapter, we provide an overview discussion of EIP examples, and discuss how to:

Set up the Sales Order Inbound EIP.
Process the Sales Order Inbound EIP.
Set up the Sales Orders Acknowledgement EIP.
Process the Sales Orders Acknowledgement EIP.
Set up the Purchase Order Dispatch EIP.
Process the Purchase Order Dispatch EIP.
Set up the Advanced Shipping Notice EIP.
Process the Advanced Shipping Notice EIP.
Set up the Billing Invoice EIP.
Process the Billing Invoice EIP.
Set up chunking.

Understanding EIP Examples

We are providing examples of the most commonly used SCM EIPs. EIP setup and processing is similar for EIPs of the same design pattern, so you can use this information and apply it to other EIPs.

See Understanding Inbound Application Message Transactions.

See Processing Outbound Application Message Transactions.

EIP	Description
Sales Order	Loads sales orders.
Sales Order Acknowledgement	Sends message acknowledging receipt of sales order.
Purchase Order Dispatch	Purchase order dispatched to a vendor using the Publish Outbound Message process
Advanced Shipping Notice	Notifies customers that their sales orders have been shipped using the Publish Outbound Message process.
Billing Invoice	Invoice sent out to a customer using the Publish Outbound Message process.

Common Elements in this Chapter

Asynchronous	Messages that do not require a response. These messages are sent to the destination system as one-way messages, and are used for publish and subscribe messages where there may be a lapse in time between the message being sent and received.
Batch Publish	Use this design pattern to publish messages from a batch application. The batch application can be a COBOL or Structured Query Report program that takes either a procedural or set-based approach, or it can be an Application Engine set-based program.
Batch Subscribe	This design pattern enables you to perform edits against messages in sets. This can be a useful technique for high volume data, including millions of inbound rows. This design pattern is useful when you know that a single message definition may contain multiple instances of a transaction, or when you must reuse an existing batch program.
Component Publish	In this design pattern, the transaction or setup data that you want to send out of PeopleSoft is being updated by using a PeopleSoft component. In this case, the data is already in the component buffer, and the Publish PeopleCode function is used to publish a message.
Full Table Publish	Use this design pattern to populate an entire copy of a table onto a remote database or legacy system. Generally, full data replication occurs with setup tables, or relatively static, low-volume tables that are keyed by setID. When a copy of a table exists on the remote system, incremental updates can be used.
Full Table Subscribe	Use this design pattern to subscribe to messages that contain an entire copy of a table that is published from a remote database or legacy system. Generally, full data replication occurs with setup tables, or relatively static, low-volume tables that are keyed by setID. When a copy of a table exists on the remote system, incremental updates can be used.
Synchronous	Occurring or existing at the same time. Used for messages that are sent out and receive an immediate response.

Setting Up the Sales Order Inbound EIP

This section discusses the Sales Order EIP.

Understanding the Sales Order Inbound EIP

The Sales Order EIP subscribes to a message that contains sales orders.

This asynchronous batch subscribe message also supports flat-file processing for EDI transaction X.12 850.

Before you can subscribe to messages with the Sales Order EIP, you must:

Type of Setup	Steps
Complete PeopleTools setup	Activate the message (SALES_ORDER). Define Nodes
Complete application setup	None for this message.
Enterprise Utility setup	For EDI/XML messages, confirm that the status is set to Active on the Inbound File page in the Inbound File Rule component.

Page Used to Set Up the Sales Order EIP

Page Name	Object Name	Navigation	Usage
File Inbound	EO_FILE_INBOUND	Enterprise Components, Integration Definitions, Inbound File Rule	Establish inbound file rules for inbound EIPs.

Activating Messages

To activate a message for publication:

Open an instance of PeopleSoft Application Designer.
Select File, Open. The Open Object dialog box appears.
In the Definition drop-down menu, select Message, enter the message name in the Name field, and click Open. The message you specified opens.
Select File, Definition Properties. The Message Properties dialog box appears.
On the Message Properties dialog box, select the Use tab.
Select the Active check box to activate the message.
Click OK, then select File, Save to save the message.
Right click on the Message Subscription PeopleCode, and select Message Subscription Properties.
Select the Use tab.
Select the Active check box to activate the message subscription.
Click the OK button, then select File, Save to save the message.

See Also

Enterprise PeopleTools 8.46 PeopleBook: Integration Broker

Defining Nodes

To define nodes:

Navigate to PeopleTools, Integration Broker, Select Node Definition.
Add the new node definition.
Select the Node info tab, and click the Active Node check box.
Select the connectors tab, and enter the gateway ID and connector ID.
Select Save and exit.
Navigate to PeopleTools, Integration Broker and select Gateways.
Enter the Gateway URL and load the correct connector.
Save and exit.

Setting the Inbound File Rule

Access the File Inbound page.

Change the Status to Active. Add the Definition Name of SALES_ORDER, and Message Name of SALES_ORDER_LOAD.

Processing the Sales Order Inbound EIP

This section discusses how you process inbound sales orders.

Pages Used to Process Inbound Sales Orders

Page Name	Object Name	Navigation	Usage
Electronic Commerce	RUN_OM_EC	Order Management, Electronic Commerce, Process Staged Orders/RFQs	Establish process parameters for inbound Sales Order EIPs.
Data Def Maint (Data Definition Maintenance)	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
Error Summary	OM_EIP_ORDERS	Click the Detail button on the Data Definition Maintenance page.	View the error queue.
Order Completion	RUN_OM_BACKGRND	Order Management, Quotes and Orders, Process Orders, Order Completion	Run the Order Completion process to complete processing for the request for all inbound messages.

Running Electronic Commerce

Access the Run Electronic Commerce page.

You can select a business unit, specify a transaction type and EIP control ID, and source code to limit the data to process.

Correcting Errors

Access the Data Definition Maintenance page.

Select a Transaction Type of PO. Enter a business Unit. Select Grid Select of Staged, and optionally enter a Status. Click the Search button.

Completing the Orders

Access the Order Completion page.

Setting Up the Sales Order Acknowledgement EIP

This section discusses the Sales Order Acknowledgement EIP.

Understanding the Sales Order Acknowledgment EIP

This message publishes an acknowledgement indicating that an order has been received. The Sales Order Acknowledgement EIP meets X.12 EDI requirements of the 855 transaction set. Sales Order Acknowledgement is an outbound asynchronous batch publish EIP.

Before you can publish messages with the Sales Order Acknowledgement EIP, you must:

Type of Setup	Steps
Complete PeopleTools setup	Activate the message (SALES_ORDER_ACKNOWLEDGEMENT).
Complete application setup	Associate customers receiving sales order acknowledgements with an ACKN document code and a preferred communication value of XML Only or XML and Print. If PeopleSoft Order Management is installed, you set up these values on the Contact Additional Info page in the Maintain Contact component.
Enterprise Utility setup	Activate the associated batch publish rule and specify the appropriate output for the message (an XML-based message or a flat file).

Integrating With a Third-Party Surgical Resource Software Application

Pages Used to Set Up the Sales Order Acknowledgement EIP

Page Name	Object Name	Navigation	Usage
Batch Publish Rules	EO_MSGPUBATCH	Enterprise Components, Integration Definitions, Batch Publish Rules	Set up publication rules. You must activate a publish rule for the publication messages you create to follow. This rule includes instructions on message chunking, if necessary.
Contact	CONTACT	Customers, Contact Information	Maintain information about each contact.
Contact Customer	CONTACT_CUST_PAGE	Click the Contact Customer Information link on the Contact page.	Indicate the primary ship to contact.
Contact Additional Info	CONTACT_ADDTL_INFO	Click the Additional Info link for a contact on the Contact Customer page.	Enter the preferred communication method for the selected document.

Activating Messages

To activate a message for publication:

Open an instance of PeopleSoft Application Designer.
Select File, Open. The Open Object dialog box appears.
In the Definition drop-down menu, select Message, enter the message name in the Name field, and click Open. The message you specified opens.
Select File, Definition Properties. The Message Properties dialog box appears.
On the Message Properties dialog box, select the Use tab.
Select the Active check box to activate the message.
Click OK, then select File, Save to save the message.

See Also

Enterprise PeopleTools 8.46 PeopleBook: Integration Broker

Verifying Contacts

You must ensure that the customer you are interacting with has a contact set up to accept EDI transmissions, and that the contact is a ship to contact.

Access the Contact page using the Customer ID in correction mode.

Access the Contact Customer page using the Contact Customer Information link.

Click the Primary Ship To check box to receive the proper shipping notifications.

Click the Additional Info link corresponding to the appropriate customer.

Under the Documentation group box, make sure the Document Code is ACKN (order acknowledgement), and Preferred Communication is R (XML and Print) or I (XML only).

Activate the Batch Publish Rule

Access the Batch Publish Rules page.

Select Active Status to activate this publish rule definition for this message to prevent this rule from applying to this message.
Select the appropriate Output Format. The PeopleSoft Application Engine program can create either an Extensible Markup Language (XML) message that flows through application messaging architecture or a flat file generated on the PeopleSoft Process Scheduler machine and not published elsewhere. Always select Message as your format when you send data to PeopleSoft systems, and Flat File if you are using EDI.
If you want to use message chunking, select a Chunking Rule ID.

See Setting Up Chunking, later in this document.

See Also

Assigning Publishing Rules

Processing the Sales Order Acknowledgement EIP

This section discusses processing the Sales Order Acknowledgement EIP.

Pages Used to Process the Sales Order Acknowledgement EIPs

Page Name	Object Name	Navigation	Usage
Publish Outbound Message	IN_RUN_PUB_MSG	SCM Integrations, Publish Outbound Message	Initiate the outbound message publish process for outbound SCM messages that use the batch publish design pattern.
Order Acknowledgement Message Selection Criteria	OM_RUN_OUTBOUND_EC	Select the Sales Order Acknowledgement check box on the page to enable its link. Click the link to launch the PO Sales Order Acknowledgement page. Select the Sales Order Change Notice check box on the page to enable its link. Click the link to launch the Sales Order Change Notice page. Select the Sales Quote Notice check box on the page to enable its link. Click the link to launch the Sales Quote Notice page.	Enter processing options for the Sales Order Acknowledgement, Sales Order Change Notice, and Sales Quote Notice outbound messages. You can select processing options for only one message at a time.

Publishing Outbound Sales Order Acknowledgement Messages

Access the Publish Outbound Message page.

Click the Sales Order Acknowledgement check box, and click the Sales Order Acknowledgement link to access the Sales Order Acknowledgement page.

Setting Up the Purchase Order Dispatch EIP

This section discusses setting up the Purchase Order Dispatch EIP.

Understanding the Purchase Order Dispatch EIP

This EIP publishes purchase orders and purchase order change requests (change orders) to vendors. This message also supports flat-file processing. The Purchase Order Dispatch EIP meets X.12 EDI requirements of the 850 transaction set. Purchase Order Dispatch is an outbound asynchronous batch publish EIP. If enabled, the system generates a Purchase Order Dispatch EIP transaction message when you run the Publish Outbound Message process. You can specify whether to generate the billing invoice for all sales order shipments in the business unit, sales orders belonging to a specific shipping ID, sales orders for a specific sold to customer, or sales orders for a specific ship to customer.

Before you can publish messages with the Purchase Order Dispatch EIP, you must:

Types of Setup	Steps
Complete PeopleTools setup	Activate the message (PURCHASE_ORDER_DISPATCH).
Complete application setup	On the purchase order, specify EDX as the PO dispatch method.
Complete Enterprise Utility setup	Activate the associated batch publish rule and specify the appropriate output for the message (an XML-based message or a flat file).

Pages Used to Set Up the Purchase Order Dispatch EIP

Page Name	Object Name	Navigation	Usage
PO Header Details	PO_HDR_DTL	Purchasing, Purchase Orders, Add/Update POs. Click the Header Details link on the Purchase Order page.	Enter or change PO header information online.
Batch Publish Rules	EO_MSGPUBATCH	Enterprise Components, Integration Definitions, Batch Publish Rules	Set up publication rules. You must activate a publish rule for the publication messages you create to follow. This rule includes instructions on message chunking, if necessary.

Page Name

Object Name

Navigation

Usage

PO Header Details

PO_HDR_DTL

Purchasing, Purchase Orders, Add/Update POs.

Click the Header Details link on the Purchase Order page.

Enter or change PO header information online.

Batch Publish Rules

EO_MSGPUBATCH

Enterprise Components, Integration Definitions, Batch Publish Rules

Set up publication rules. You must activate a publish rule for the publication messages you create to follow. This rule includes instructions on message chunking, if necessary.

Activating Messages

To activate a message for publication:

Open an instance of PeopleSoft Application Designer.
Select File, Open. The Open Object dialog box appears.
In the Definition drop-down menu, select Message, enter the message name in the Name field, and click Open. The message you specified opens.
Select File, Definition Properties. The Message Properties dialog box appears.
On the Message Properties dialog box, select the Use tab.
Select the Active check box to activate the message.
Click OK, then select File, Save to save the message.

See Also

Enterprise PeopleTools 8.46 PeopleBook: Integration Broker

Setting the Purchase Order Dispatch Method

Access the PO Header Details page.

Select the Dispatchcheck box to ensure that the system dispatches the PO. Also, select a dispatch Method of EDX.

See Also

Creating Purchase Orders Online

Activate the Batch Publish Rule

Access the Batch Publish Rules page.

Select Active Status to activate this publish rule definition for this message to prevent this rule from applying to this message.
Select the appropriate Output Format. The PeopleSoft Application Engine program can create either an Extensible Markup Language (XML) message that flows through application messaging architecture or a flat file generated on the PeopleSoft Process Scheduler machine and not published elsewhere. Always select Message as your format when you send data to PeopleSoft systems, and Flat File if you are using EDI.
If you want to use message chunking, select a Chunking Rule ID.

See Setting Up Chunking, which appears later in this document.

See Also

Assigning Publishing Rules

Processing the Purchase Order Dispatch EIP

This section discusses processing the purchase order dispatch EIP.

See Also

Creating Purchase Orders Online

Dispatching and Printing Purchase Orders

Pages Used to Process the Purchase Order EIP

Page Name	Object Name	Navigation	Usage
Dispatch Purchase Orders	RUN_DISP_POPO005	Purchasing, Purchase Orders, Dispatch POs	Run the PO Dispatch/Print process and dispatch POs, run the Email process, or run the PO Dispatch & Email multiprocess job.
Publish Outbound Message	IN_RUN_PUB_MSG	SCM Integrations, Publish Outbound Message	Initiate the outbound message publish process for outbound SCM messages that use the batch publish design pattern.
PO Dispatch Message Selection Criteria	PO_RUN_POD	Select Purchase Order Dispatch on the Publish Outbound Message page to enable the Purchase Order Dispatch link. Click the Purchase Order Dispatch link to launch the PO Dispatch Message Selection Criteria page.	Launch the Purchase Order Dispatch outbound transaction.

Dispatching Purchase Orders

Access the Dispatch PO page.

Ensure that the PO to be dispatched is included in your selection criteria. Click Run to stage POs for dispatch.

Publishing Outbound Purchase Order Messages

Access the Publish Outbound Message page.

Click the Purchase Order Dispatch check box, and click the Purchase Order Dispatch link to access the Purchase Order Dispatch page.

Select BU or Vendor as a Selection Type.
If you select BU, the BU Sel Type fields are enabled, and you can select All BUs or a 1 Bus Unit. If you select Vendor, the Vendor Selection Type fields are enabled, and you can select 1 Vendor or All Vendor.

Setting Up the Advanced Shipping Notice EIP

This section discusses the Advanced Shipping Notice EIP.

Understanding the Advanced Shipping Notice EIP

The Advanced Shipment Notice (ASN) EIP meets X.12 EDI requirements of the 856 - Ship Notice/Manifest transactions set. ASN is an outbound asynchronous batch publish EIP.

If enabled, the system generates an Advanced Shipping Notice EIP transaction message when a sales order entered from PeopleSoft Order Management has been depleted in PeopleSoft Inventory. You can specify whether to generate the ASN for all sales order shipments in the business unit, sales orders belonging to a specific shipping ID, sales orders for a specific sold to customer, or sales orders for a specific ship to customer.

Before you can publish messages with the Advanced Shipment Notice EIP, you must:

Type of Setup	Steps
Complete PeopleTools setup	Activate the message (ADVANCED_SHIPPING_NOTICE). If using message chunking, setup the OnRoute Send PeopleCode event on the message. Set up an outbound synchronous transaction defining the ADVANCED_SHIPPING_NOTICE message on each node that will receive the transaction. Verify the ADVANCED_SHIPPING_NOTICE message channel is in a run mode.
Complete application setup	Select the Use Advanced Shipment Notice option for the business unit on the Inventory Definition - Business Unit Options page. Associate customers receiving Advanced Shipment Notice EIP messages with an ASN document code and a preferred communication value of XML Only or XML and Print. If PeopleSoft Order Management is installed, you set up these values on the Contact Additional Info page in the Maintain Contact component.
Enterprise Utility setup	Activate the associated batch publish rule and specify the appropriate output for the message (an XML-based message or a flat file). If you are using message chunking, select a chunking rule ID. If you are using message chunking, set up the chunking rule mapping definitions.

Integrating With a Third-Party Surgical Resource Software Application

Pages Used to Set Up the Advanced Shipping Notice EIP

Page Name	Object Name	Navigation	Usage
Batch Publish Rules	EO_MSGPUBATCH	Enterprise Components, Integration Definitions, Batch Publish Rules	Set up publication rules. You must activate a publish rule for the publication messages you create to follow. This rule includes instructions on message chunking, if necessary.
Contact	CONTACT	Customers, Contact Information	Maintain information about each contact.
Contact Customer	CONTACT_CUST_PAGE	Click the Contact Customer Information link on the Contact page.	Indicate the primary ship to contact.
Contact Additional Info	CONTACT_ADDTL_INFO	Click the Additional Info link for a contact on the Contact Customer page.	Enter the preferred communication method for the selected document.
Business Unit Definition — Inventory Options	BUS_UNIT_INV5	Set Up Financials/Supply Chain, Business Unit Related, Inventory, Inventory Definition, Business Unit Options	Define external interfaces.

Activating Messages

To activate a message for publication:

Open an instance of PeopleSoft Application Designer.
Select File, Open. The Open Object dialog box appears.
In the Definition drop-down menu, select Message, enter the message name in the Name field, and click Open. The message you specified opens.
Select File, Definition Properties. The Message Properties dialog box appears.
On the Message Properties dialog box, select the Use tab.
Select the Active check box to activate the message.
Click OK, then select File, Save to save the message.

See Also

Enterprise PeopleTools 8.46 PeopleBook: Integration Broker

Verifying Contacts

You must ensure that the customer you are interacting with has a contact set up to accept EDI transmissions, and that the contact is a ship to contact.

Access the Contact page using the Customer ID in correction mode.

Access the Contact Customer page using the Contact Customer Information link.

Click the Primary Ship To check box to receive the proper shipping notifications.

Click the Additional Info link corresponding to the appropriate customer.

Under the Documentation group box, make sure the Document Code is ASN (advanced shipping notification), and Preferred Communication is R (XML and Print) or I (XML only).

Enabling the Inventory Business Unit

You must enable ASN generation in the business unit shipping the items.

Access the Inventory Definition - Business Unit Options page.

Click the Use Advanced Shipment Notice check box in the External Interfaces group box.

Activate the Batch Publish Rule

Access the Batch Publish Rules page.

Select Active Status to activate this publish rule definition for this message to prevent this rule from applying to this message.
Select the appropriate Output Format. The PeopleSoft Application Engine program can create either an Extensible Markup Language (XML) message that flows through application messaging architecture or a flat file generated on the PeopleSoft Process Scheduler machine and not published elsewhere. Always select Message as your format when you send data to PeopleSoft systems, and Flat File if you are using EDI.
If you want to use message chunking, select a Chunking Rule ID.

See Setting Up Chunking.

Chunking the Advanced Shipping Notice EIP

Chunking is only needed if you have requirements to break up the messages and send them to different destinations based on attributes in the message such as business unit or customer ID. The most common use of chunking with the ASN message is to send a single customer’s messages to a specific node setup for that trading partner. If you are using a middleware product to actually determine trading partner destinations then a single message with all trading partner transactions can usually be sent directly to the middleware product. You would not need to activate message chunking in this situation.

For an example of how to use chunking, look at the batch publish rules for the ADVANCED_SHIPPING_NOTICE Message. These batch publish rules were provided as examples to show the power of message chunking.

The ADVANCED_SHIPPING_NOTICE batch publish rule is the standard rule used without chunking. If you want to chunk by Business Unit just attach the BUSINESS_UNIT chunk rule to the batch publish rule. You would also have to populate the Business Unit to node values in the chunk table and set up the OnRouteSend Routing Rule on the Message when you activate it in the Application Designer.

If you want to chunk by Ship To Customer then activate the ASN_SETID_SHIPTO batch publish rule. In this case you also need to populate the customer chunk rule table and setup the OnRouteSend Routing Rule.

If you want to chunk by Sold To Customer then activate the ASN_SETID_SOLDTO chunk rule, populate the customer chunk rule table and setup the OnRouteSend Routing Rule.

See Also

Assigning Batch Publishing Rules

Setting Up Message Chunking

Processing the Advanced Shipping Notice EIP

This sections discusses processing the Advanced Shipping Notice EIP.

Pages Used to Process the Advanced Shipping Notice EIP

Page Name	Object Name	Navigation	Usage
Publish Outbound Message	IN_RUN_PUB_MSG	SCM Integrations, Publish Outbound Message	Initiate the outbound message publish process for outbound SCM messages that use the batch publish design pattern.
Advanced Shipping Notices Selection Criteria	IN_RUN_SHPNTC_ASN	Select Advanced Shipping Notices on the Publish Outbound Message page to enable the Advanced Shipping Notices link. Click the Advanced Shipping Notices link to access the Advanced Shipping Notices Selection Criteria page.	Launch the Advanced Shipping Notices outbound transaction for sales orders that have been depleted.

Publishing Advanced Shipping Notices

Access the Publish Outbound Message page.

Click the Advanced Shipping Notices check box, and click the Advanced Shipping Notices link to access the Advanced Shipping Notices Selection Criteria page.

All Shipments

Select to generate this transaction for all sales order shipments that have been through the Depletion process (INPDDEPL), but have not previously generated an ASN.

Sold To Customer

Select to generate this transaction for a sales order with a specific sold to customer.

Ship To Customer

Select to generate this transaction for a sales order with a specific ship to customer.

Specific Shipping ID

Select to generate this transaction for sales orders with a specific shipping ID.

Source Bus Unit

Select a valid source business unit. A source business unit is the PeopleSoft Order Management business unit that created the sales order. This field is required if you elect in the Selection Options group box to generate this transaction for a specific sold to or ship to customer. This field is not available for entry if you elect in the Selection Options group box to generate this transaction for all shipments, or for a specific shipping ID.

Sold To Customer

Select a valid sold to customer. This field is only available for entry and is required if you elect in the Selection Options group box to generate this transaction for a specific sold to customer.

Ship To Customer

Select a valid ship to customer. This field is only available for entry and is required if you elect in the Selection Options group box to generate this transaction for a specific ship to customer.

Shipping ID

Select a valid shipping ID. This field is only available for entry and is required if you elect in the Selection Options group box to generate this transaction for a specific shipping ID.

Re-Generate Message

Select this option to regenerate a message for sales orders that have already been sent out.

Note. When you navigate to the process monitor and wait till the process completes successfully, you can click the Details link and then the View Log/Trace link. This shows the output file as a link. The system generates the flat file to reflect the ASN information for the corresponding shipping ID.

Message Separation

PeopleSoft Inventory creates a single occurrence of an ASN transaction for each combination of business unit, source business unit, sold to customer, ship to customer, shipping ID, carrier ID, and ship via. The transaction message also lists the ASN creation date and time, the source business unit's address, the vehicle ID, the quantity ordered, the shipping weight, and, if defined, the shipping container ID and container type.

PeopleSoft sends the generated transaction to the ship to customer, the sold to customer, or both.

Troubleshooting Information

The system does not create an ASN under the following circumstances:

The shipment has not been through the Depletion process (INPDDEPL).
The order is a drop ship or is for non-inventory items.
The transaction has a demand source other than PeopleSoft Order Management.
PeopleSoft Order Management is not installed.

Setting Up the Billing Invoice EIP

This section discusses setting up the Billing Invoice EIP.

Understanding the Billing Invoice EIP

This EIP sends invoices to customers. The Billing Invoice EIP meets X.12 EDI requirements of the 856 transaction set. Billing Invoice is an outbound asynchronous batch publish EIP. Enable the Billing Invoice EIP and run the Finalize Bills process (BIIVC000) to populate the BI_HDR_EC table. Once the data is in BI_HDR_EC, the outbound publish process can create the outbound message/flat file.

Before you can publish messages with the Billing Invoice EIP, you must:

Types of Setup	Steps
Complete PeopleTools setup	Activate the message (BILLING_INVOICE_NOTICE).
Complete application setup	Associate customers receiving Billing Invoice EIP messages with a preferred communication value of XML Only or XML and Print, and a document code of Invoice. The system provides these values as a default to the Standard Billing - Address Info page when you create a bill for this customer.
Complete Enterprise Utility setup	Activate the associated batch publish rule and specify the appropriate output for the message (an XML-based message or a flat file).

Assigning Publishing Rules

Pages Used to Process Billing Invoices

Page Name	Object Name	Navigation	Usage
Batch Publish Rules	EO_MSGPUBATCH	Enterprise Components, Integration Definitions, Batch Publish Rules	Set up publication rules. You must activate a publish rule for the publication messages you create to follow. This rule includes instructions on message chunking, if necessary.
Contact	CONTACT	Customers, Contact Information	Maintain information about each contact.
Contact Customer	CONTACT_CUST_PAGE	Click the Contact Customer Information link on the Contact page.	Build the relationship between the contact and the different customer IDs the contact serves or is associated with. If the contact is only associated with one customer, enter that customer on this page. If the contact is a broker, for example, use this page to establish the relationships with the multiple customers that the broker serves. Set up security options on the Self Service Security tab.
Contact Additional Info	CONTACT_ADDTL_INFO	Click the Additional Info link for a contact on the Contact Customer page.	Enter the preferred communication method for the selected document.

Activating Messages

To activate a message for publication:

Open an instance of PeopleSoft Application Designer.
Select File, Open. The Open Object dialog box appears.
In the Definition drop-down menu, select Message, enter the message name in the Name field, and click Open. The message you specified opens.
Select File, Definition Properties. The Message Properties dialog box appears.
On the Message Properties dialog box, select the Use tab.
Select the Active check box to activate the message.
Click OK, then select File, Save to save the message.

See Also

Enterprise PeopleTools 8.46 PeopleBook: Integration Broker

Activate the Batch Publish Rule

Access the Batch Publish Rules page.

Select Active Status to activate this publish rule definition for this message.
Select the appropriate Output Format. The PeopleSoft Application Engine program can create either an Extensible Markup Language (XML) message that flows through application messaging architecture or a flat file generated on the PeopleSoft Process Scheduler machine and not published elsewhere. Always select Message as your format when you send data to PeopleSoft systems, and Flat File if you are using EDI.
If you want to use message chunking, select a Chunking Rule ID.

See Also

Assigning Publishing Rules

Setting Up Chunking

Verifying Contacts

You must ensure that the customer you are interacting with has a contact set up to accept EDI transmissions, and that the contact is a Ship to Contact.

Access the Contact page using the Customer ID in correction mode.

Access the Contact Customer page using the Contact Customer Information link.

Click the Primary Bill To check box to receive the proper invoice notifications.

Click the Additional Info link corresponding to the appropriate customer.

Under the Documentation group box, make sure the Document Code is INVC (invoice), and Preferred Communication is R (XML and Print) or I (XML only).

Processing the Billing Invoice EIP

This section discusses processing Billing Invoice EIPs.

Pages Used to Process the Billing Invoice EIP

Page Name	Object Name	Navigation	Usage
Publish Outbound Message	IN_RUN_PUB_MSG	SCM Integrations, Publish Outbound Message	Initiate the outbound message publish process for outbound SCM messages that use the batch publish design pattern.
Billing Invoice Notice Message Selection Criteria	BI_INVMSG_SEL_PNL	Select Billing Invoice Notice on the Publish Outbound Message page to enable the Billing Invoice Notice link. Click the Billing Invoice Notice link to launch the Billing Invoice Notice Message Selection Criteria page.	Launch the Billing Invoice Notice outbound transaction.

Publishing Billing Invoices

Access the Publish Outbound Message page.

Click the Billing Invoice Notice check box, and click the Billing Invoice Notice link to access the Billing Invoice Notice Selection Criteria page.

Enter a Request ID, Description, and Business Unit.

Setting Up Chunking

When publishing application messages, you can elect to set up chunking. Chunking is an optional step with batch publish messages. When chunking, the system automatically breaks up messages into several smaller messages based on the values in one or more of the fields in the level zero record.

Consider, for example, that you want to send EDI messages directly to a trading partner. When sending purchase orders directly to a vendor, you want to ensure that the vendor receives only their own transactions. Chunking enables you to split a batch of purchase orders into separate messages, based on the trading partner. The Integration Broker provides tools to route the message to specific nodes, based on the trading partner identification (in this example, the vendor ID).

To set up chunking you:

Associate chunking rules to publication rules.
Map nodes to a chunk rule.
Assign the business units to a chunk rule.
Specify the OnRoute PeopleCode.

Pages Used to Set Up Chunking

Page Name	Object Name	Navigation	Usage
Add Nodes to Chunk Rule	EO_ADNODECHUNK_PNL	Enterprise Components, Integration Definitions, Map Chunking Rules, Node to Chunk Rule	Map PeopleSoft Application Messaging nodes to chunking rules. (A node is a PeopleTools object that represents a publishing or subscribing system on the message network. A message node often relates to an application server or database name.)

Associating Chunking Rules to Publication Rules

If the data you're transmitting won't fit in a single message, or if you want to send different parts of the message to different target systems, set up the rules to chunk the message and associate it with your publish rule. The business unit and setID chunking rules are standard in PeopleSoft applications, but you can customize your own chunking rules.

To associate a chunking rule to the publication rule:

Access the Batch Publish Rules page.
Use the Publish Rule ID field to select the name of the message for which you're setting up rules.
Select a status of Active.
In the Chunking Rule ID field, select the name of the field by which you want to chunk the message. The message you publish is routed based on this field.
In the Alternate Chunk Rule ID field, select an additional field by which to chunk the message, if required.
Save and repeat the process for each required message rule.

Note. Some SCM application use page specific chunking rules.

See Also

Setting Up Message Chunking

Mapping Nodes to Chunk Rules

A node is a PeopleTools object that represents a publishing or subscribing system on the message network. A message node often relates to an application server or database name.

To map nodes to a chunk rule:

Access the Add Nodes to Chunk Rule page.
In the Add column, select the check box next to the nodes that you defined earlier.
Click the Save button to call up the Add Chunk Values column

Add Chunk Values

In this column, click the Add button to open the Quick Map page for the message that you defined earlier.

See Also

Setting Up Message Chunking

Set Up the OnRoute PeopleCode

To set up the OnRoute PeopleCode:

Open up an instance of PeopleSoft Application Designer.
Select File, Open.
In the Definition drop-down menu, select Message and enter the message name in the Name field.
Click Open.

The system opens the Message Definition.
Select View, View PeopleCode.
From the PeopleCode Event drop-down menu, select OnRouteSend.

The system displays the PeopleCode editor.

The following is an example of OnRoute Send PeopleCode: Declare Function GetNodes PeopleCode FUNCLIB_INEIP_PUBLISH_ROUTE_PC FieldForumula;GetNodes (" ");;
Click Save to save the Message Definition.

All Shipments	Select to generate this transaction for all sales order shipments that have been through the Depletion process (INPDDEPL), but have not previously generated an ASN.
Sold To Customer	Select to generate this transaction for a sales order with a specific sold to customer.
Ship To Customer	Select to generate this transaction for a sales order with a specific ship to customer.
Specific Shipping ID	Select to generate this transaction for sales orders with a specific shipping ID.
Source Bus Unit	Select a valid source business unit. A source business unit is the PeopleSoft Order Management business unit that created the sales order. This field is required if you elect in the Selection Options group box to generate this transaction for a specific sold to or ship to customer. This field is not available for entry if you elect in the Selection Options group box to generate this transaction for all shipments, or for a specific shipping ID.
Sold To Customer	Select a valid sold to customer. This field is only available for entry and is required if you elect in the Selection Options group box to generate this transaction for a specific sold to customer.
Ship To Customer	Select a valid ship to customer. This field is only available for entry and is required if you elect in the Selection Options group box to generate this transaction for a specific ship to customer.
Shipping ID	Select a valid shipping ID. This field is only available for entry and is required if you elect in the Selection Options group box to generate this transaction for a specific shipping ID.
Re-Generate Message	Select this option to regenerate a message for sales orders that have already been sent out.