This chapter provides an overview of PeopleSoft CRM 360-Degree View functionality and discusses how to set up the PeopleSoft Billing and PeopleSoft CRM integration.
The PeopleSoft CRM 360-Degree View is a tool to manage customer interactions. You can use this feature as an entry point for all customer interactions, and as the central point to launch all customer transactions, such as quote and order creation, case creation, and opportunity creation.
The 360-Degree View enables the customer service representative to do the following:
Access customer profile information.
Manage transactions.
Record interactions.
View all customer interactions using the 360-Degree View tree.
Integration Between PeopleSoft CRM and Supply Chain Management
When defining the nodes for the 360-Degree View tree, you can define a node that represents invoices for the customer. This node on the 360-Degree View tree is populated by information that resides in PeopleSoft Billing.
Using a defined EIP, the customer service representative can request information from PeopleSoft Billing for invoice information associated with a customer using a request message. PeopleSoft Billing sends the requested information back to PeopleSoft CRM using a response message to display under a node on the 360-Degree View tree.
PeopleSoft CRM sends a request application message (BI_EIP360_REQ) to PeopleSoft Billing for invoices; PeopleSoft Billing sends a response application message (BI_EIP360_RSP) back to PeopleSoft CRM for the information to display under the 360-Degree View tree.
Agents can click invoice links that appear on the 360-Degree View tree to access additional invoice detail in PeopleSoft Billing.
Note. Enable single signon to access PeopleSoft Billing inquiry components from PeopleSoft CRM.
See Also
Integrating PeopleSoft CRM with Billing Through the Transaction Billing Processor
To integrate the PeopleSoft Billing and PeopleSoft CRM, perform the following steps:
Enable the message channel status.
Activate the message.
Verify default local nodes setup.
Grant security permissions to the message channel.
Verify remote node setup.
Update the integrationGateway.properties file.
Verify node access in the PeopleSoft CRM and FSCM databases.
Verify message setup on the Node Definitions - Transactions page in the PeopleSoft CRM and FSCM databases.
Enable single sign-on.
Note. The node names PSFT_EP and PSFT_CR are used in the following sections as examples only. You might have different default local nodes, for example, the default PeopleSoft CRM local node might be CR880. Use the correct default local node name in each of the following setup steps.
The message channel is initially defined with a default status of pause. To enable the message channel, change the message channel status to run.
To change the message channel status to run:
Access the PeopleSoft CRM database using PeopleSoft Application Designer.
Open message channel BI_EIP360.
Click the Properties button, and select Use tab.
In the Message Channel Status group box, select Run.
Click OK to save the message channel.
Repeat steps 1 through 5 in the PeopleSoft FSCM database.
You must activate the message in PeopleSoft Application Designer.
To activate the message:
Access the PeopleSoft CRM database using PeopleSoft Application Designer.
Open message BI_EIP360_REQ.
Click Message Properties, and select the Use tab.
In the Status group box, select Active.
Click OK to save.
Open message BI_EIP360_RSP.
Click Message Properties, and select the Use tab.
In the Status group box, select Active.
Click OK to save.
Repeat steps 2 through 9 in the PeopleSoft FSCM database.
In the PeopleSoft CRM and FSCM databases, grant permissions to the message channel.
To grant security permission to the message channel:
Access the PeopleSoft CRM database.
Select PeopleTools, Security, Permissions & Roles, Permission Lists.
Select Permission List in the Search By field, and enter ALLPAGES in the adjacent Begins With field.
Select the Message Monitor tab.
Ensure that channel BI_EIP360 appears in the Channels grid area. If channel BI_EIP360 does not appear, add it. In the Access field, select Full.
Repeat steps 2 through 4 in the PeopleSoft FSCM database.
In the PeopleSoft CRM and FSCM databases, verify that you have set up the correct default local nodes.
To verify default local node setup:
Access the PeopleSoft CRM database with the User ID PS and Password PS.
Alternately, enter User ID VP1 and Password VP1.
Select PeopleTools, Integration Broker, Node Definitions.
In the Search By field, select Node Name, and click Search.
A grid appears at the bottom of the search page with all node names that meet the search criteria.
For node name PSFT_CR, verify that the Local Node column is Yes.
This value appears for a node if you selected the Local Node option for this node on the Node Info page.
For node name PSFT_CR, verify that the value that appears in Default Local Node is Yes
This value appears if you selected the Default Local Node option for this node on the Node Info page.
Ensure that the node is active.
The node is active if you selected Active Node for the node on the Node Info page. See the following section for activating the remote node.
Repeat steps 1 through 6 in the PeopleSoft FSCM database.
In the PeopleSoft FSCM database, verify default settings for the PSFT_EP node name.
Verify that each remote node is set up in the PeopleSoft CRM and FSCM databases.
To verity that the correct remote node is set up:
Access the PeopleSoft CRM database.
Select PeopleTools, Integration Broker, Node Definitions.
In the Search By field, select Node Name.
In the adjacent Begins With field, enter PSFT_EP.
On the Node Info tab, select the Active Node option, and click Save.
Repeat steps 2 through 4 in the PeopleSoft FSCM database.
In step 3, enter PSFT_CR in the Begins With field.
Update the integrationGateway.properties file on the PeopleSoft CRM and PeopleSoft FSCM web servers.
To update the integrationGateway.properties file on the PeopleSoft CRM web server:
Locate the file in the tools directory: For example:
c:\pt84602b\webserv\peoplesoft\applications\peoplesoft\PSIGW\WEB-INF
Replace all instances of $NODENAME with PSFT_EP (or with the exact name that you use for the FSCM node).
Replace the information that appears within the < > arrows with the correct machine information for the node (remove the arrows as well).
If you use a node other than the default, uncomment the following code lines and enter the appropriate serveURL, userid, password, and toolsRel:
#CR890FDM ig.isc.PSFT_EP.serverURL=//adntas07:9330 ig.isc.PSFT_EP.userid=VP1 ig.isc.PSFT_EP.password=JekncVtPdNg= ig.isc.PSFT_EP.toolsRel=8.43-H2
To update the integrationGateway.properties file on the PeopleSoft FSCM web server:
Locate the file in the following directory:
C:\bea\wlserver6.1\config\peoplesoft\applications\PSIGW\WEB-INF
Replace all instances of $NODENAME with PSFT_CR (or with the exact name that you use for the CRM node).
Replace the information that appears within the < > arrows with the correct machine information for the node (remove the arrows as well).
If you use a node other than the default, uncomment the following code lines and enter the appropriate serveURL, userid, password, and toolsRel:
#CR890CRM ig.isc.PSFT_CR.serverURL=//adntas08:9330 ig.isc.PSFT_CR.userid=VP1 ig.isc.PSFT_CR.password=JekncVtPdNg= ig.isc.PSFT_CR.toolsRel=8.43-H2
Ensure that you can access the PSFT_EP node from PeopleSoft CRM and the PSFT_CR node from PeopleSoft FSCM.
To ensure access to PeopleSoft CRM and FSCM nodes:
Access the PeopleSoft CRM database.
Select PeopleTools, Integration Broker, Monitor, Monitor Message.
Select the Node Status tab.
In the Message Node Name field, enter PSFT_EP, then click the Ping Node button.
If you set up the nodes correctly, the system displays a success message in the Node Information grid area.
Repeat steps 2 through 4 in the PeopleSoft FSCM database.
In step 4, enter PSFT_CR in the Message Node Name field.
Ensure that the BI_EIP360_REQ message is set up correctly, and appears on the Node Definitions - Transactions tab.
To ensure that the BI_EIP360_REQ message is set up correctly:
Access the PeopleSoft CRM database.
Select PeopleTools, Integration Broker, Node Definitions.
Select Node Name in the Search By field, and enter PSFT_EP in the adjacent Begins With field.
Click Search to access the Node Definitions - Node Info page.
Select the Transactions tab.
Locate the value BI_EIP360_REQ in the Request Message column. If the BI_EIP360_REQ transaction does not appear, skip ahead to step 10.
Click Edit to access the Transaction Detail page for BI_EIP360_REQ.
In the Status field, select Active.
Click Return to Transaction List to return to the Node Definitions - Transactions page.
If, in step 6, the BI_EIP360_REQ transaction does not appear, click the Add Transaction button to access the Node Transactions page.
Select Outbound Synchronous in the Transaction Type field.
Select BI_EIP360_REQ in the Request Message field.
Enter the appropriate version in the Request Message Version field.
Click Add to access the Transaction Detail page.
Select Active in the Status field.
Select the Messages tab.
Select BI_EIP360_RSP in the Name field in the Response Message group box.
Click Save.
Repeat steps 2 through 10 to verify the message setup on the PeopleSoft FSCM database.
In step 3, select Node Name in the Search By field, and enter PSFT_CR in the adjacent Begins With field. In step 10, select Inbound Synchronous in the Transaction Type field.
To transfer EIPs from PeopleSoft CRM to PeopleSoft Billing, you must enable single sign-on, and add the PeopleSoft CRM PSFT_CR node information into PeopleSoft FSCM.
To enable single sign-on:
Access the PeopleSoft CRM database.
Select PeopleTools, Security, Security Objects, Single Signon to access the Single Sign-On page.
Click the Add New Row button, and select the PSFT_EP node from the available options in the Message Node Name column.
Click Save.
Select PeopleTools, Portal, Node Definitions.
Select Node Name in the Search By field, and enter PSFT_EP in the adjacent Begins With field to access the Node Definitions - Node Info page.
Select the Portal Content tab.
8. Enter the correct urls in the Content URI Text and Portal URI Text fields.
For example, enter a URL that contains the following information: http://someserver/psc//pshome/
Click Save.
Access the PeopleSoft FSCM database.
Select PeopleTools, Security, Security Objects, Single Signon to access the Single Sign-On page.
Click the Add New Row button, and select the PSFT_CR node from the available options in the Message Node Name column.
Click Save.