This chapter provides an overview of PeopleSoft Customer Relationship Management (PeopleSoft CRM) integration points and discusses how to:
Process PeopleSoft Business Interlinks transactions.
Process inbound application message transactions.
Process inbound transactions.
Process outbound application message transactions.
Set up chunking.
Publish outbound messages.
PeopleSoft CRM integration points enable you to:
Send or publish a message to a third-party system.
Accept or subscribe to messages from third-party systems.
Send a synchronous request and reply transaction to a third-party system for processing.
Sometimes PeopleSoft CRM needs to call an external system vendor's application to request information. This information must be provided in a real-time, synchronous mode. The PeopleSoft application waits for the answer from the other application in real time, before the PeopleSoft application can continue processing.
These transactions use PeopleSoft Business Interlinks definitions to specify the data passed to this external system as well as to define the output to be received from the external system. The data that is passed from the interlink object is interpreted by an interlink plug-in, which then contacts the external system, passes the data in the correct form, retrieves the data, and then passes it, in the correct form, back to the interlink object:
EIP |
Object Name |
PeopleSoft CRM Product |
Reference |
Import Data |
CR_IMPORT_DATA |
General Options/Common |
|
Open Model Template |
CR_OPEN_MODEL_TEMPLATE |
General Options/Common |
|
Recalculate |
CR_RECALCULATE |
General Options/Common |
|
Sales Order |
PSGETID |
General Options/Common |
|
Freight Calculations CRM |
RATE_REQUEST |
PeopleSoft Enterprise Order Capture |
|
Freight Calculations CRM |
RATE_REQUEST_XFRM |
PeopleSoft Enterprise Order Capture |
|
Freight Calculations CRM |
RATE_RESPONSE |
PeopleSoft Enterprise Order Capture |
|
Purchase Order & InterUnit Transfer Information |
RF_GETPOIUT |
PeopleSoft Enterprise Integrated Field Service |
|
Item Balance |
RF_IN_ITEM_BALANCES |
PeopleSoft Enterprise Integrated Field Service |
|
Tax Calculations |
TAXWARE_CALCTAX |
Enterprise Strategy Group |
|
Tax Calculations |
VERTEX_CALCTAX |
Enterprise Strategy Group |
|
VAT Calculations CRM |
VAT_CALC |
PeopleSoft Enterprise Order Capture |
See Also
Enterprise PeopleTools 8.45 PeopleBook: PeopleSoft Business Interlinks
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:
Inbound transaction flow
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 using subscription processes that are unique to 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 load message information into staging tables where background programs validate and process individual transactions within the message.
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. Examples are provided showing how to use this utility, as PeopleSoft CRM electronic data interchange (EDI) transactions have been set up to take advantage of this feature.
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. 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.
See Also
Enterprise PeopleTools 8.45 PeopleBook: PeopleSoft Integration Broker
PeopleSoft CRM provides these inbound transactions:
EIP |
Object Name |
PeopleSoft CRM Product |
Reference |
Basic Data Insert/Update |
BO_BAS_RES |
General Options/Common |
|
Basic Data Insert/Update |
BO_BASIC_DBO |
Online Marketing |
|
Basic Data Insert/Update |
BO_BASIC_IND |
Online Marketing |
|
Basic Data Insert/Update |
BO_BASIC_ORG |
Online Marketing |
|
Contact |
CONTACT_FULLSYNC |
Customer Data Model |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Contact |
CONTACT_FULLSYNC |
Customer Data Model |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Contact |
CONTACT_FULLSYNC_EFF |
Customer Data Model |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Contact |
CONTACT_FULLSYNC_EFF |
Customer Data Model |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Contact |
CONTACT_SYNC |
Customer Data Model |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Contact |
CONTACT_SYNC_EFF |
Customer Data Model |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Alternate_Capacity |
CUST_ALT_CAPACITY_FULLSYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Alternate_Capacity |
CUST_ALT_CAPACITY_FULLSYNC_EFF |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Alternate_Capacity |
CUST_ALT_CAPACITY_SYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Alternate_Capacity |
CUST_ALT_CAPACITY_SYNC_EFF |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Company |
CUST_COMPANY_FULLSYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Company |
CUST_COMPANY_FULLSYNC_EFF |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Company |
CUST_COMPANY_SYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Company |
CUST_COMPANY_SYNC_EFF |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Consumer |
CUST_CONSUMER_FULLSYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Consumer |
CUST_CONSUMER_FULLSYNC_EFF |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Consumer |
CUST_CONSUMER_SYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Consumer |
CUST_CONSUMER_SYNC_EFF |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Partnership |
CUST_PARTNERSHIP_FULLSYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Partnership |
CUST_PARTNERSHIP_FULLSYNC_EFF |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Partnership |
CUST_PARTNERSHIP_SYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Partnership |
CUST_PARTNERSHIP_SYNC_EFF |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Site |
CUST_SITE_FULLSYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Site |
CUST_SITE_FULLSYNC_EFF |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Customer_Site |
CUST_SITE_SYNC |
General Options/Common |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
Expense |
EXPENSE_SYNC |
PeopleSoft Enterprise Integrated Field Service |
See Managing Enterprise Integration for PeopleSoft Enterprise CRM. |
ATM Card Transaction-In |
RBF_ATM_CARD_TRAN_IN |
EXTERNAL |
|
Financial Account Creation |
RBF_FIN_ACCT_FULL_SYNC |
EXTERNAL |
|
Insurance Change Policy Status |
RBI_CHANGE_POLICY_STATUS |
EXTERNAL |
|
Get Bill Summary |
RBT_GETBILL_REQ_MSG |
Energy Industry |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Summary |
RBT_GETBILL_REQ_MSG |
Communications Industry |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Events |
RBT_GETBILLEVENTS_REQ_MSG |
Energy Industry |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Events |
RBT_GETBILLEVENTS_REQ_MSG |
Communications Industry |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Events |
RBT_GETBILLEVENTS_RPY_MSG |
EXTERNAL |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Events |
RBT_GETBILLEVENTS_RPY_MSG |
EXTERNAL |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Items |
RBT_GETBILLITEMS_REQ_MSG |
Energy Industry |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Items |
RBT_GETBILLITEMS_REQ_MSG |
Energy Industry |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Items |
RBT_GETBILLITEMS_REQ_MSG |
Communications Industry |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Items |
RBT_GETBILLITEMS_REQ_MSG |
Communications Industry |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Items |
RBT_GETBILLITEMS_RPLY_MSG |
EXTERNAL |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Items |
RBT_GETBILLITEMS_RPLY_MSG |
EXTERNAL |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Summary |
RBT_GETBILLS_RPLY_MSG |
EXTERNAL |
See Integrating Billing with Communication and Energy Industries. |
Get Bill Summary |
RBT_GETBILLS_RPLY_MSG |
EXTERNAL |
See Integrating Billing with Communication and Energy Industries. |
Case Inquiry Request Message |
RC_CASE_INQUIRY_REQ_SYNC |
EXTERNAL |
|
Case Creation or Updation Message |
RC_CASE_REQUEST_ASYNC |
EXTERNAL |
|
Case Creation or Update Request Message |
RC_CASE_REQUEST_SYNC |
General Options/Common |
|
Representative |
REP_SYNC |
General Options/Common |
|
Representative Full Sync |
REP_SYNC_FULLSYNC |
General Options/Common |
|
Service_Location |
SERVICE_LOCATION_FULLSYNC |
General Options/Common |
|
Service_Location |
SERVICE_LOCATION_FULLSYNC_EFF |
General Options/Common |
|
Service_Location |
SERVICE_LOCATION_SYNC |
General Options/Common |
|
Service_Location |
SERVICE_LOCATION_SYNC_EFF |
General Options/Common |
|
Worker |
WORKER_FULLSYNC |
General Options/Common |
|
Worker |
WORKER_FULLSYNC_EFF |
General Options/Common |
|
Worker |
WORKER_SYNC |
General Options/Common |
|
Worker |
WORKER_SYNC_EFF |
General Options/Common |
Outbound EIPs exist throughout the PeopleSoft system, providing interface points for third-party applications requiring information as activity occurs within the PeopleSoft system. The PeopleSoft Application Messaging technology is utilized to format and publish industry standard XML messages. For example, as item master information is entered into PeopleSoft applications, the system generates XML-based messages and delivers them to third-party systems requiring this information to set up their own item master tables.
PeopleSoft CRM applications as well as interacting third-party systems have various processing and timing requirements that dictate when information can be generated or received. For this reason, the integration points provided by PeopleSoft utilize a number of different approaches when generating outbound application messages.
For example, a third-party system requiring item master information from the PeopleSoft Inventory application may want immediate incremental updates as information is changed online or may want periodic updates on a nightly or weekly basis. The Item Master EIP provides both options, giving the third-party system the choice as to how it wants to receive this information.
Component or Incremental Publish
The system generates Component Published messages immediately upon saving a component in various PeopleSoft applications. Components used to maintain setup type information such as items or customers utilize the Component Publish approach.
Batch Publish
Batch Publish messages provide the functionality to group many like transactions into a single message.
Background processes that work on batches of transactions at one time utilize this approach.
In addition, other processes use this approach where interface requirements demand various groupings of like transactions based on common information within each transaction. For example, an Advanced Shipping Notice message can be published to a customer when the customer's order is shipped within the PeopleSoft Inventory system. This message may go directly to the customer or it may go through third-party software that converts the XML message to one of the industry standard EDI formats, such as X.12, before passing it on to the customer. Using the options available with the Batch Publish approach, users can dictate whether to create a single message for all customers to send to the third-party software or create individual messages to send directly to each customer.
PeopleSoft CRM applications all use the Publish Outbound Message process to initiate the Batch Publish messages. Built into this routine is the Batch Publish utility, a common PeopleSoft tool that provides the functionality to group and filter or “chunk” messages as noted in the previous example.
The Batch Publish utility also provides the option to create flat files instead of XML messages, when file layout objects exist for transactions being generated. File layout objects are easy to modify, and PeopleSoft provides examples for all transactions included in the EDI feature.
Full Data Replication
Full data replication is the process used to seed, or initially populate or repopulate, a copy of an entire table onto a remote database or legacy system. The entire contents of the table are published to all systems that require a copy of the table. Generally, full data replication occurs with setup tables—that is, relatively static, low volume tables keyed by setID.
Once a copy of the table exists, incremental updates provide a mechanism or process to keep the copy up-to-date with changes made on the master. Incremental updates occur most often with transaction tables—that is, frequently updated tables keyed by business unit.
Most full data replication message names end in _FULLSYNC.
PeopleSoft CRM provides these outbound transactions:
EIP |
Object Name |
PeopleSoft CRM Product |
Reference |
Basic Data Insert/Update |
BO_BAS_RES |
General Options/Common |
|
Basic Data Insert/Update |
BO_BASIC_DBO |
Online Marketing |
|
Basic Data Insert/Update |
BO_BASIC_IND |
Online Marketing |
|
Basic Data Insert/Update |
BO_BASIC_ORG |
Online Marketing |
|
Contact |
CONTACT_FULLSYNC |
Customer Data Model |
|
Contact |
CONTACT_FULLSYNC |
Customer Data Model |
|
Contact |
CONTACT_FULLSYNC_EFF |
Customer Data Model |
|
Contact |
CONTACT_FULLSYNC_EFF |
Customer Data Model |
|
Contact |
CONTACT_SYNC |
Customer Data Model |
|
Contact |
CONTACT_SYNC |
Customer Data Model |
|
Contact |
CONTACT_SYNC_EFF |
Customer Data Model |
|
Publish Quote |
CRM_QUOTE |
PeopleSoft Enterprise Order Capture |
|
Publish Order |
CRM_SALES_ORDER |
PeopleSoft Enterprise Order Capture |
|
Publish Order Change |
CRM_SALES_ORDER_CHANGE |
PeopleSoft Enterprise Order Capture |
|
Customer_Alternate_Capacity |
CUST_ALT_CAPACITY_FULLSYNC |
General Options/Common |
|
Customer_Alternate_Capacity |
CUST_ALT_CAPACITY_FULLSYNC_EFF |
General Options/Common |
|
Customer_Alternate_Capacity |
CUST_ALT_CAPACITY_SYNC |
General Options/Common |
|
Customer_Alternate_Capacity |
CUST_ALT_CAPACITY_SYNC_EFF |
General Options/Common |
|
Customer_Company |
CUST_COMPANY_FULLSYNC |
General Options/Common |
|
Customer_Company |
CUST_COMPANY_FULLSYNC_EFF |
General Options/Common |
|
Customer_Company |
CUST_COMPANY_SYNC |
General Options/Common |
|
Customer_Company |
CUST_COMPANY_SYNC_EFF |
General Options/Common |
|
Customer_Consumer |
CUST_CONSUMER_FULLSYNC |
General Options/Common |
|
Customer_Consumer |
CUST_CONSUMER_FULLSYNC_EFF |
General Options/Common |
|
Customer_Consumer |
CUST_CONSUMER_SYNC |
General Options/Common |
|
Customer_Consumer |
CUST_CONSUMER_SYNC_EFF |
General Options/Common |
|
Customer_Partnership |
CUST_PARTNERSHIP_FULLSYNC |
General Options/Common |
|
Customer_Partnership |
CUST_PARTNERSHIP_FULLSYNC_EFF |
General Options/Common |
|
Customer_Partnership |
CUST_PARTNERSHIP_SYNC |
General Options/Common |
|
Customer_Partnership |
CUST_PARTNERSHIP_SYNC_EFF |
General Options/Common |
|
Customer_Site |
CUST_SITE_FULLSYNC |
General Options/Common |
|
Customer_Site |
CUST_SITE_FULLSYNC_EFF |
General Options/Common |
|
Customer_Site |
CUST_SITE_SYNC |
General Options/Common |
|
Customer_Site |
CUST_SITE_SYNC_EFF |
General Options/Common |
|
Get Geo Code |
ESRI_ADDRESS_US_MSG |
Government Industry |
See ESRI Integration. |
Get Geo Code |
ESRI_GEO_CODE_US_MSG |
ESRI |
See ESRI Integration. |
Get Map Extents |
ESRI_MAP_EXT_REPLY_MSG |
ESRI |
See ESRI Integration. |
Get Map Extents |
ESRI_MAP_EXT_REQ_MSG |
Government Industry |
See ESRI Integration. |
Get Map |
ESRI_MAP_REPLY_MSG |
ESRI |
See ESRI Integration. |
Get Map |
ESRI_MAP_REQ_MSG |
Government Industry |
See ESRI Integration. |
Expense |
EXPENSE_SYNC |
PeopleSoft Enterprise Integrated Field Service |
|
Hr_Helpdesk_360 |
HD_360_REQUEST_SYNC |
PeopleSoft Enterprise Support |
See Defining EIP Options for Integration to PeopleSoft HRMS. |
Order Capture ESA Proposal |
OC_ESA_PROPOSAL |
General Options/Common |
See Activating EIPs. |
Order Capture ESA Proposal Status |
OC_ESA_PROPOSAL_STATUS |
General Options/Common |
See Activating EIPs. |
Marketing Audience |
RA_OM_AUDIENCE_MSG |
PeopleSoft Enterprise Marketing |
See Using Audiences. |
Customer Profile |
RA_PROFILE_MSG |
PeopleSoft Enterprise Marketing |
|
OLM Response |
RA_RESPONSE |
Online Marketing |
|
Financial Account Nickname |
RBF_ACCT_NN_MSG |
Financial Services Industry |
|
Automatic Funds Transfer |
RBF_AFND_TR_MSG |
Financial Services Industry |
|
ATM Card Transaction - Out |
RBF_ATM_CARD_TRAN_OUT |
Financial Services Industry |
|
Bill Payment History |
RBF_BILL_PAY_HISTORY |
External |
|
Bill Payment History |
RBF_BILL_PAY_HISTORY_REQ |
Financial Services Industry |
|
Bill Payment History |
RBF_BILL_PAY_HISTORY_RES |
External |
|
Change Financial Account Address |
RBF_CHG_ACTADR_MSG |
Financial Services Industry |
|
Close Financial Account |
RBF_CLOSE_ISSUE_MSG |
External |
|
Fee Reversal |
RBF_FEE_REVERSAL |
Financial Services Industry |
|
Financial Account Address |
RBF_FINACCT_ADDRESS |
External |
|
Financial Account Fees |
RBF_FINACCT_FEES |
External |
|
Financial Account Relationships |
RBF_FINACCT_RELATIONSHIPS |
External |
|
Financial Account Security |
RBF_FINACCT_SECURITY |
External |
|
Financial Account Security By Role |
RBF_FINACCT_SECURITY_BYROLE |
External |
|
Transfer Funds |
RBF_FUNDS_TRANSFER_REQ |
Financial Services Industry |
|
Transfer Funds |
RBF_FUNDS_TRANSFER_RES |
External |
|
Close Financial Account |
RBF_ISSUE_CLOSE_ACCT |
Financial Services Industry |
|
Close Financial Account - From Legacy |
RBF_ISSUE_CLOSE_ACCT_RESPONSE |
External |
|
Modify Account |
RBF_MODACCT_MSG |
Financial Services Industry |
|
Order Cashiers Check |
RBF_ORD_CCHK_MSG |
Financial Services Industry |
|
Order Checks |
RBF_ORD_CHK_MSG |
Financial Services Industry |
|
Order Documents |
RBF_ORD_DOC_MSG |
Financial Services Industry |
|
Order Foreign Currency |
RBF_ORD_FCUR_MSG |
Financial Services Industry |
|
Order Travelers Checks |
RBF_ORD_TCHK_MSG |
Financial Services Industry |
|
Incoming Quote |
RBF_QUOTE |
External |
|
Reorder Checks |
RBF_REO_CHK_MSG |
Financial Services Industry |
|
Sales Entry For Financial Account |
RBF_SALES_ENTRY |
Financial Services Industry |
|
Stop Check Payment |
RBF_STP_PAY_MSG |
Financial Services Industry |
|
Transaction History For Financial Account |
RBF_VIEW_TRANS_REQ |
Financial Services Industry |
|
Transaction History For Financial Account |
RBF_VIEW_TRANS_RES |
External |
|
Get Map Extents |
RBG_MAP_EXT_REPLY_MSG |
External |
See ESRI Integration. |
Get Map Extents |
RBG_MAP_EXT_REQ_MSG |
Government Industry |
See ESRI Integration. |
Get Map |
RBG_MAP_REPLY_MSG |
External |
See ESRI Integration. |
Get Map |
RBG_MAP_REQ_MSG |
Government Industry |
See ESRI Integration. |
Get Geo Code |
RBG_SYNC_ADDRESS_US_MSG |
Government Industry |
See ESRI Integration. |
Get Geo Code |
RBG_SYNC_GEO_CODE_US_MSG |
External |
See ESRI Integration. |
Insurance Billing History |
RBI_BILLING_HISTORY |
External |
|
Insurance Billing History - Sync Message |
RBI_BILLING_HISTORY_REQ |
Insurance Industry |
|
Insurance Billing History - Sync Message |
RBI_BILLING_HISTORY_RES |
External |
|
Insurance Change Policy - Sync Message |
RBI_CHANGE_POLICY_REQ |
Insurance Industry |
|
Insurance Claim Details |
RBI_CLAIM_DETAILS |
External |
|
Insurance Claim Header Creation |
RBI_CLAIM_HDR |
External |
|
Insurance Claim Details - Sync Message |
RBI_CLAIMNO_RES |
External |
|
Insurance Claim Details - Sync Message |
RBI_CLAIMNO_SYNC |
Insurance Industry |
|
Insurance Publish Issue |
RBI_ISSUE_PUBLISH |
Insurance Industry |
|
Insurance Payment History |
RBI_PAYMENT_HISTORY |
External |
|
Insurance Payment History - Sync Message |
RBI_PAYMENT_HISTORY_REQ |
Insurance Industry |
|
Insurance Payment History - Sync Message |
RBI_PAYMENT_HISTORY_RES |
External |
|
Insurance Policy Creation |
RBI_POLICY |
External |
|
Insurance Change Policy - Sync Message |
RBI_QUOTE |
Insurance Industry |
|
Insurance Change Policy - Sync Message |
RBI_QUOTE |
Insurance Industry |
|
Insurance Sales |
RBI_SALES |
Insurance Industry |
|
View Account Balance |
RBT_ACTBAL_REQ_MSG |
Energy Industry |
|
View Account Balance |
RBT_ACTBAL_REQ_MSG |
Communications Industry |
|
View Account Balance |
RBT_ACTBAL_RPLY_MSG |
External |
|
View Account Balance |
RBT_ACTBAL_RPLY_MSG |
External |
|
Change Service |
RBT_ACTSRVC_MSG |
Energy Industry |
See Activating EIPs. |
Change Service |
RBT_ACTSRVC_MSG |
Communications Industry |
See Activating EIPs. |
Account Status |
RBT_ACTSTATUS_MSG |
Energy Industry |
|
Account Status |
RBT_ACTSTATUS_MSG |
Communications Industry |
|
View Account Usage |
RBT_ACTUSG_REQ_MSG |
Energy Industry |
|
View Account Usage |
RBT_ACTUSG_REQ_MSG |
Communications Industry |
|
View Account Usage |
RBT_ACTUSG_RPLY_MSG |
External |
|
View Account Usage |
RBT_ACTUSG_RPLY_MSG |
External |
|
Change Service |
RBT_ADDSRVCFT_MSG |
Energy Industry |
See Activating EIPs. |
Change Service |
RBT_ADDSRVCFT_MSG |
Communications Industry |
See Activating EIPs. |
Create Dispute |
RBT_BILL_DISP_MSG |
Energy Industry |
See Understanding EIPs. |
Create Dispute |
RBT_BILL_DISP_MSG |
Communications Industry |
See Understanding EIPs. |
Change Billing Address |
RBT_CHANGADDR_MSG |
Energy Industry |
See Understanding EIPs. |
Change Billing Address |
RBT_CHANGADDR_MSG |
Communications Industry |
See Understanding EIPs. |
Churn Message |
RBT_CHURN_MSG |
External |
|
Churn Message |
RBT_CHURN_MSG |
External |
|
Get Bill Summary |
RBT_GETBILL_REQ_MSG |
Energy Industry |
See Understanding EIPs. |
Get Bill Summary |
RBT_GETBILL_REQ_MSG |
Communications Industry |
See Understanding EIPs. |
Get Bill Events |
RBT_GETBILLEVENTS_REQ_MSG |
Energy Industry |
See Understanding EIPs. |
Get Bill Events |
RBT_GETBILLEVENTS_REQ_MSG |
Communications Industry |
See Understanding EIPs. |
Get Bill Events |
RBT_GETBILLEVENTS_RPY_MSG |
External |
See Understanding EIPs. |
Get Bill Events |
RBT_GETBILLEVENTS_RPY_MSG |
External |
See Understanding EIPs. |
Get Bill Items |
RBT_GETBILLITEMS_REQ_MSG |
Energy Industry |
See Understanding EIPs. |
Get Bill Items |
RBT_GETBILLITEMS_REQ_MSG |
Energy Industry |
See Understanding EIPs. |
Get Bill Items |
RBT_GETBILLITEMS_REQ_MSG |
Communications Industry |
See Understanding EIPs. |
Get Bill Items |
RBT_GETBILLITEMS_REQ_MSG |
Communications Industry |
See Understanding EIPs. |
Get Bill Items |
RBT_GETBILLITEMS_RPLY_MSG |
External |
See Understanding EIPs. |
Get Bill Items |
RBT_GETBILLITEMS_RPLY_MSG |
External |
See Understanding EIPs. |
Get Bill Summary |
RBT_GETBILLS_RPLY_MSG |
External |
See Understanding EIPs. |
Get Bill Summary |
RBT_GETBILLS_RPLY_MSG |
External |
See Understanding EIPs. |
Add Service |
RBT_IPSTATUS_MSG |
External |
See Understanding EIPs. |
Add Service |
RBT_IPSTATUS_MSG |
External |
See Understanding EIPs. |
Create Account |
RBT_NEWACR_RPLY_MSG |
External |
|
Create Account |
RBT_NEWACR_RPLY_MSG |
External |
|
Create Account |
RBT_NEWACT_REQ_MSG |
Energy Industry |
See Understanding EIPs. |
Create Account |
RBT_NEWACT_REQ_MSG |
Communications Industry |
See Understanding EIPs. |
Add Service |
RBT_NEWSRVC_MSG |
Energy Industry |
See Understanding EIPs. |
Add Service |
RBT_NEWSRVC_MSG |
Communications Industry |
See Understanding EIPs. |
Change Payment Details |
RBT_PAYINFO_MSG |
Energy Industry |
See Understanding EIPs. |
Change Payment Details |
RBT_PAYINFO_MSG |
Communications Industry |
See Understanding EIPs. |
Add Service Feature |
RBT_PROSRVC_MSG |
Energy Industry |
See Understanding EIPs. |
Add Service Feature |
RBT_PROSRVC_MSG |
Communications Industry |
See Understanding EIPs. |
Disconnect Service |
RBT_REMOVESRVC_MSG |
Energy Industry |
See Understanding EIPs. |
Disconnect Service |
RBT_REMOVESRVC_MSG |
Communications Industry |
See Understanding EIPs. |
Change Service |
RBT_REMOVESRVCFT_MSG |
Energy Industry |
See Understanding EIPs. |
Change Service |
RBT_REMOVESRVCFT_MSG |
Communications Industry |
See Understanding EIPs. |
Installed Product Message |
RBT_SERVICEMGMT_MSG |
Energy Industry |
See Understanding EIPs. |
Installed Product Message |
RBT_SERVICEMGMT_MSG |
Communications Industry |
See Understanding EIPs. |
Suspend Service |
RBT_SUSPENDSRVC_MSG |
Energy Industry |
See Understanding EIPs. |
Suspend Service |
RBT_SUSPENDSRVC_MSG |
Communications Industry |
See Understanding EIPs. |
Case Inquiry Response Message |
RC_CASE_INQUIRY_RESP_SYNC |
PeopleSoft Enterprise Support |
|
Case Inquiry Response Message |
RC_CASE_INQUIRY_RESP_SYNC |
PeopleSoft Enterprise HelpDesk |
|
Case Inquiry Response Message |
RC_CASE_INQUIRY_RESP_SYNC |
PeopleSoft Enterprise HelpDesk for Human Resources |
|
Case Confirmation Message |
RC_CASE_RESPONSE_ASYNC |
PeopleSoft Enterprise Support |
|
Case Confirmation Message |
RC_CASE_RESPONSE_ASYNC |
PeopleSoft Enterprise Support |
|
Case Confirmation Response Message |
RC_CASE_RESPONSE_SYNC |
PeopleSoft Enterprise HelpDesk |
|
Case Confirmation Response Message |
RC_CASE_RESPONSE_SYNC |
PeopleSoft Enterprise HelpDesk for Human Resources |
|
Case Confirmation Response Message |
RC_CASE_RESPONSE_SYNC |
PeopleSoft Enterprise HelpDesk |
|
Case Confirmation Response Message |
RC_CASE_RESPONSE_SYNC |
PeopleSoft Enterprise HelpDesk for Human Resources |
|
Case Confirmation Response Message |
RC_CASE_RESPONSE_SYNC |
General Options/Common |
|
Representative |
REP_FULLSYNC_EFF |
General Options/Common |
|
Representative |
REP_SYNC |
General Options/Common |
|
Representative |
REP_SYNC_EFF |
General Options/Common |
|
Representative Full Sync |
REP_SYNC_FULLSYNC |
General Options/Common |
|
Service_Location |
SERVICE_LOCATION_FULLSYNC |
General Options/Common |
|
Service_Location |
SERVICE_LOCATION_FULLSYNC_EFF |
General Options/Common |
|
Service_Location |
SERVICE_LOCATION_SYNC |
General Options/Common |
|
Service_Location |
SERVICE_LOCATION_SYNC_EFF |
General Options/Common |
|
Service Order |
SERVICE_ORDER_SYNC |
PeopleSoft Enterprise Integrated Field Service |
|
Table Set Control |
SETID_INITIALIZE |
General Options/Common |
|
Time |
TIME_SYNC |
PeopleSoft Enterprise Integrated Field Service |
|
Worker |
WORKER_FULLSYNC |
General Options/Common |
|
Worker |
WORKER_FULLSYNC_EFF |
General Options/Common |
|
Worker |
WORKER_SYNC |
General Options/Common |
|
Worker |
WORKER_SYNC_EFF |
General Options/Common |
This section provides an overview of chunking and discusses how to set up chunking.
If you are publishing application messages, you may want to set up chunking. 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. For example, if you want to chunk by business unit, messages would be broken up by business unit sending each business unit’s transactions to a node that you have defined. Another example would be for sites sending EDI messages directly to trading partners. If you are sending purchase orders directly to a vendor then you want to make sure that that vendor gets only their transactions. Chunking provides the ability to split a batch of purchase orders into separate messages based on the trading partner. The Integration Broker then provides tools to route the message to specific nodes based on that trading partner identification, in this case the vendor ID.
Note. If you are using a middleware product to transform and route transactions to trading partners then you most likely will not need to use message chunking. All messages would go to the node defined for the middleware product.
Chunking is implemented using the Batch Publish Utility or the Full Data Publish Utility. In either case a batch publish rule is created and a chunking rule can be attached. The chunking rule defines a table containing a set of values that map to specific nodes. For example, in the example above where you are chunking by vendor ID, the chunking rule table would contain a set of vendor IDs that map to individual nodes for trading partners receiving the purchase order message.
The following is an step by step explanation of the process flow of a transaction using message chunking:
Chunking Selection
Run process that generated message. This may be the Full Data Publish Utility or one of the batch based messages that use the Batch Publish Utility.
Note. All messages generated from the Publish Outbound Messages use the Batch Publish Utility.
When the batch publish utility or full data publish utilities run they recognize the chunking rule assigned to the batch publish rule and split the different transactions into separate messages for each chunking rule value. They then publish the message handing it over to the Integration Broker.
Chunking Node Routing
The Integration Broker makes the decision of which node will receive the Message. Standard processing for the Integration Broker is to send the message to any node that has a transaction setup for that message. When chunking, you want to override the standard method of processing and force the Integration Broker to send the message only to the node for which the message was intended. This is done by assigning OnRouteSend PeopleCode to the message in the Application Designer. When OnRouteSend PeopleCode exists on a message the Integration Broker will only send the message to the nodes that it is told to by this routine. PeopleSoft provides some common functions that can be used for this purpose. The setup instructions for different messages explain exactly how to setup the OnRouteSend PeopleCode for messages where in most cases when using a chunking rule with the batch publish utility or the full data publish utility all you need to do to override the Integration Brokers standard processing is to add the following PeopleCode to the OnRouteSend PeopleCode for the message being sent.
Note. Incremental Publish messages do not use message chunking as defined above. By definition, incremental published messages do not need the Chunking Selection step because they only contain a single transaction. But, if incremental publish messages need to be sent to specific nodes based on values in the message then the Chunking Node Routing step defined above would still be required.
PeopleSoft provides a number of chunking rules, chunking rule tables, data entry pages and OnRouteSend functions that can be used to maintain node mappings and routing rules for some of the more commonly used field values. The data entry pages are noted in the Pages Used to Set up Chunking table below. Information about setup for specific messages is provided in the PeopleBook for the actual application publishing the message. Additional information is provided in the PeopleSoft Enterprise Components PeopleBook explaining how to create your own customized chunking rule, chunking rule table and data entry pages.
For an example of how multiple chunking rules can be setup on a single message 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. In this example, the ADVANCED_SHIPPING_NOTICE 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. In this case, to setup the routing rule you would add the following to the OnRouteSend people code on the ADVANCED_SHIPPING_NOTICE message:
Declare Function GetNodes PeopleCode FUNCLIB_INEIP.PUBLISH_ROUTE_PC FieldForumula; GetNodes (" ");
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 setup the ASN_SETID_SOLDTO chunk rule, populate the customer chunk rule table and setup the OnRouteSend Routing Rule.
See Also
PeopleSoft Enterprise Components for CRM 8.9 PeopleBook
Page Name |
Object Name |
Navigation |
Usage |
EO_ADNODECHUNK_PNL |
Enterprise Components, Integration Definition, Map Chunking Rules, Node to ChunkRule, Add Nodes to Chunk Rule |
Map nodes by Chunk Rules. |
|
EO_CHUNKBU |
Enterprise Components, Integration Definition, Map Chunking Rules, Business Units, BusUnit Mapping |
Maintain ChunkRule business unit mapping. |
|
EO_ADDBUNODE_PNL |
Enterprise Components, Integration Definition, Map Chunking Rules, BU to ChunkRule/Node, Quick Map |
Map business units by ChunkRules or nodes. |
|
EO_ADDNODEBU_PNL |
Enterprise Components, Integration Definition, Map Chunking Rules, ChunkRule/Node to BU, Map Business Unit |
Map ChunkRules or nodes by business unit. |
|
EO_CHUNKSETID |
Enterprise Components, Integration Definition, Map Chunking Rules, Setids, Setid Mapping |
Maintain ChunkRule setID mapping. |
|
EO_ADDSIDNODE_PNL |
Enterprise Components, Integration Definition, Map Chunking Rules, Setid to ChunkRule/Node, Quick Map |
Map setIDs by ChunkRules or nodes. |
|
EO_ADDNODESID_PNL |
Enterprise Components, Integration Definition, Map Chunking Rules, ChunkRule/Node to Setid, Map Set IDs |
Map ChunkRules by setID. |
|
OM_CHUNKCUSTID |
Data Exchanges, Chunking Rule, CustID to Node Mapping, Customer ID Chunk |
Map publish application messages by customer. |
|
IN_CHUNKBULOCATION |
Data Exchanges, Chunking Rule, BU/Loc to Node Mapping, BU/Location Node Mapping |
Map business units and locations. |
|
IN_CHUNKBUPARLOC |
Data Exchanges, Chunking Rule, BU/Par to Node Mapping, BU/Par Location Node Mapping |
Set up chunking by business unit and par location for publish application messages. |
|
PO_CHUNK_VENDOR |
Data Exchanges, Chunking Rule, Manage ChunkRule VendorID Map, Setup Vendor to Node |
Set up chunking by vendor ID for publish application messages. |
|
PO_CHUNK_SHIPTO |
Data Exchanges, Chunking Rule, Ship to Loc to Node Mapping, PO Chunk Shipto |
Set up chunking by ship to location for publish application messages. |
|
OM_CHUNK_SRC_CD |
Data Exchanges, Chunking Rule, Source Code to Node Mapping, Source Code Chunk |
Set up chunking by source code for publish application messages. |
See Also
PeopleSoft Enterprise Components for CRM 8.9 PeopleBook
This section discusses how to publish outbound messages.
Page Name |
Object Name |
Navigation |
Usage |
IN_RUN_PUB_MSG |
Data Exchanges, Publish Outbound Message |
Initiate the outbound message publish process for outbound PeopleSoft CRM messages that use the batch publish design pattern. |
Access the Publish Outbound Message page.
Note. This page is used only to publish messages that use the batch publish design pattern.
Select the check box by the name of the message that you want to publish. The system then makes the message name a link to a transaction-specific page for that message. You can publish messages one at a time or in multiples.