Integrating with Fulfillment and Billing Systems

This chapter provides an overview of fulfillment integration and discusses how to:

Click to jump to parent topicUnderstanding Fulfillment Integration

This section discusses:

See Also

Defining Integrations and Mappings

Defining Order Capture Business Units

Click to jump to top of pageClick to jump to parent topicIntegration Setup

The primary setup of Order Capture integration occurs in the Order Capture Integration Workbench. The Integration Workbench is designed so that all of your fulfillment and maintenance activity can be configured there. There are also a few fields that must be populated on the Business Unit Definition page.

Click to jump to top of pageClick to jump to parent topicIntegration Points

Order Capture uses integration points to transfer information between itself and an order fulfillment system, such as PeopleSoft Order Management or PeopleSoft Inventory. These integration points enable you to configure your collaborative selling solution to work with any third-party fulfillment system or enterprise application integration (EAI) system.

Note. Delivered integration points are configured for integration with PeopleSoft Supply Chain Management (SCM), which provides corresponding integration points for example, integration points that publish the information for which PeopleSoft CRM listens. Integration with other fulfillment or EAI systems might require the use of the PeopleTools Integration Broker to build the necessary transformation layer on top of the existing integration points that PeopleSoft delivers.

PeopleSoft provides the following integration points to support the order fulfillment process:

Integration Point


Message / Transaction Name



Get Autonumber

Requests an ID number (to be used for a new order or quote) from your fulfillment system. This integration point is used only when autonumbering is used for order ID assignment.


Outbound / Synchronous

Get Order Status

Requests current order and order line status from your fulfillment system.



Outbound / Synchronous

Get Product Availability

Requests product availability information from your fulfillment system.

Note. The Get Product Availability integration point gives PeopleSoft CRM users on-demand access to product availability information. Users click the Check Availability button on the order or quote Entry Form page to initiate the transaction.



Outbound / Synchronous

Publish Order

Sends new orders to your fulfillment system.



Outbound / Asynchronous

Publish Order Change

Sends changed orders to your fulfillment system.



Outbound / Synchronous

Publish Quote

Sends new quotes to your fulfillment system.



Outbound / Asynchronous

Receive ASN

Listens for ASNs published by your fulfillment system.



Inbound / Asynchronous

Receive Order Acknowledgement

Listens for order acknowledgements published by your fulfillment system.



Inbound / Asynchronous

Receive Quote Acknowledgement

Listens for quote acknowledgements published by your fulfillment system.



Inbound / Asynchronous

Receive Order Change Acknowledgement

Listens for order change acknowledgements published by your fulfillment system.



Inbound / Asynchronous

Sales Order Status

Listens for order updates published by your fulfillment system.



Inbound / Asynchronous

Note. The integration points listed in the preceding table use PeopleTools Integration Broker messages. Application Message Monitor and Send Master (a PeopleTools testing utility) help you track and test the messages and transformations that make up these integration points. The Get Autonumber integration point is an exception in that it uses PeopleTools Business Interlink technology.

Click to jump to top of pageClick to jump to parent topicActivation of Integration Points for Use with PeopleSoft SCM

If you are using PeopleSoft SCM, you need to:

Note. If a product uses an inventory item, that item must also be in the CRM (Item Master Table), otherwise the CRM CI Process will fail. Make sure that you sync the item master first before ProductFullSync or ProductSync.

Click to jump to top of pageClick to jump to parent topicOrder Maintenance Integration Points

When an order is captured in PeopleSoft CRM, it is passed to the fulfillment system for processing. Subsequent changes to the order are sent from and received by the fulfillment system by means of appropriate integration points. The integration points support integrations with PeopleSoft SCM and other third-party fulfillment systems. The Get Order Status integration point is used as part of the Order Maintenance process when an order is retrieved for maintenance. This ensures that PeopleSoft only allows edits on orders and order lines that are not yet fulfilled.

Note. Order maintenance messages, such as CRM_SALES_ORDER_CHANGE, always contain RO_HEADER information, and always publish the RO_INTEGRATION, RO_HISTORY, and RO_CHARGE data for the order. The remainder of the CRM_SALES_ORDER_CHANGE data only contains order information that has been added or changed.

Order maintenance activities require customer service representatives (CSRs) to have accurate information about changed orders. The following table explains the four integration points that form the backbone of Order Capture's order maintenance activities:

Integration Point Name

Object Name





Notifies PeopleSoft SCM of an order maintenance request. It is a transformation of the CRM_SALES_ORDER_CHANGE message.




Notifies non PeopleSoft fulfillment systems of the order maintenance request.




Notifies Order Capture when changes are processed in SCM.




Notifies Order Capture of the current state of the order in SCM.


Here is a complete list of the SCM integration points to activate for complete fulfillment functionality:

Click to jump to top of pageClick to jump to parent topicCustomer Data Hub (CDH) Impact on Integrations with PeopleSoft Financials and Supply Chain Management (FSCM)

Customer merges can happen in the CRM system at any time. This raises the possibility that customer information on a transaction that was originally sent by Order Capture to FSCM via an EIP message is replaced on the CRM transaction due to a merge. This would cause the customer on the original transaction to be lost, because FSCM does not update customers information due to PeopleSoft merges. To ensure that it is always possible to map from the current customer BO_ID in CRM to the original customer BO_ID is SCM, a field that stores the original customer information has been added to the following EIPs:

The existing mapping tables between CRM and SCM are not changed as part of this feature.

If CDH is installed, this mapping of CRM customers to SCM customers is maintained by the CDH data synchronization process, otherwise the mapping is maintained by the Customer Sync EIP.

Note. If PeopleSoft SCM is your fulfillment system, you must keep customer and product data synchronized in the two systems. The Product Sync EIP manages product data synchronization. If you have CDH installed, the CDH data synchronization process manages customer data synchronization; otherwise the Customer Sync EIP manages customer data synchronization.

See Also

Understanding Customer Data Hub Integration

Click to jump to parent topicActivating Integration Points

This section discusses how to activate Integration Broker integration points.

Click to jump to top of pageClick to jump to parent topicActivating Integration Broker Integration Points

Integration Broker integration points are inactive when delivered. You must activate fulfillment integration points. If you are integrating with PeopleSoft SCM, you must activate the Order Management and Inventory integration points listed in the previous section as well. To activate integration points, activate each of the following elements:

You need to set the necessary Queues (called Channel in previous releases) to a Run status in order to process integration broker messages. This is accessed through PeopleTools, Integration Broker, Integration Setup, Queues. Fulfillment uses queues CRM_ORDER_STATUS, SALES_ORDER_LOAD, SALES_ORDER_ACKNOWLEDGEMENT and SALES_ORDER_STATUS.

Click to jump to parent topicCreating Autonumbering for Orders and Quotes

You can choose either the autonumbering or grid option for your orders and quotes. Autonumbers are controlled by business unit. When you set up autonumbering, you choose the business unit that controls autonumber generation and specify whether autonumbers are generated in the PeopleSoft CRM system or in an external fulfillment system.

Choosing a Business Unit to Control Autonumber Generation

When you define an Order Capture business unit, you map it to an Order Management business unit. You can map multiple Order Capture business units to a single order management business unit. Therefore, to ensure a single source for all numbers that are sent to the order management system, CRM uses the order management business unit to drive autonumbering. For example, if order capture business unit A is mapped to order management business unit B, then when you create an order in business unit A, its number is generated based on the rules for business unit B.

Note. By design, PeopleSoft SCM cannot use CRM as its autonumbering master for orders and quotes, only for customers, contacts, and products.

Establishing an External ID Source for Orders and Quotes

You can generate order and quote numbers in the CRM system or in your order fulfillment system. If the CRM system does not have an external autonumbering master for orders and quotes, then order numbers are created locally. In this case, be sure that your autonumbering rules include a CRM-specific prefix so that numbers are unique across both your CRM and order fulfillment system. If your fulfillment system is the autonumbering master, the Get Autonumber integration point fetches order numbers from the external system as orders are created. Because order numbers in both systems come from a common autonumbering definition, this configuration ensures that order numbers are unique across both systems.

Note. The external ID for an order or a quote in Order Capture is used to identify the order or quote in your fulfillment system. The RO_INTEGRATION table stores the external ID data. This table stores the external ID by source code (for example, SCM), thus allowing for multiple external IDs per CRM order. In addition to storing the external order number, we use this table to store a mapping of sequence numbers on header and line notes.

Notes no longer have sequence numbers in CRM, but SCM requires a sequence number to identify a note, which is why we map the information in RO_INTEGRATION. In our previous release, EXTERNAL_ID was simply a field on the RO_HEADER table.

Click to jump to parent topicMapping Line Statuses

When you send an order to your fulfillment system, that system is responsible for tracking status of the order; CRM integration points bring status information into CRM to display the status of an order.

Understanding Line Status Mappings

Because different systems can use different order statuses, you must map your fulfillment system's statuses to Order Capture statuses. The Get Order Status integration point reads the map and converts your fulfillment system's statuses into Order Capture statuses. For line statuses, Partial means that if a part of one line is backordered and part is shipped, it is in fact, partially shipped.

Header status mappings may differ slightly. PeopleSoft delivers a map for all the Order Management statuses. If you integrate with a different fulfillment system, modify the map accordingly.

Note. Order Capture maps the status values to node, PSFT_EP, and if you are using a different node name for your Order Management system, you need to enter status mappings against your node name. The node name is read-only once the data is saved.

The following table shows the delivered line status mappings for SCM statuses:

SCM Status

CRM Status

CRM Partial Status

X (Canceled)

1 (Canceled)

1 (Canceled)

Q (Requisitioned)

1000 (Open)

1100 (Partially Open)

U (Purchased)

1000 (Open)

1100 (Partially Open)

B (Backordered)

2000 (Backordered)

2100 (Partially Backordered)

P (Pending)

3000 (Pending)

3100 (Partially Pending)

H (On Hold)

3500 (Fulfillment Hold)

Note. Holds that originate in PeopleSoft CRM have the status, 9000. This is to differentiate a hold that originated in PeopleSoft CRM (status 9000), from a hold that originated in SCM.

3500 (Fulfillment Hold)

O (In Fulfillment)

4000 (In Fulfillment)

4100 (Partially In Fulfillment)

K (Picked)

5000 (Picked)

5100 (Partially Picked)

C (Closed)

6000 (Shipped)

6100 (Partially Shipped)

S (Shipped)

6000 (Shipped)

6100 (Partially Shipped)

Click to jump to parent topicPublishing Order and Quote Messages

When you capture an order or quote in Order Capture, the system instantiates the CORE_ORDER_BP or CORE_QUOTE_BP business project. Both of these business projects include a task that runs the RO_EIP_PUB Application Engine process, which triggers the Publish Order and Publish Quote integration points. These integration points, which consist of the CRM_SALES_ORDER and CRM_SALES_QUOTE messages, make order and quote information available to your fulfillment system. PeopleSoft delivers the Integration Broker transformation rules required to integrate with SCM; integration with other systems requires additional transformation rules.

If you use Order Management, integration points receive the transformed messages and enter order data into Order Management staging tables. The orders have a source code of CRM and start with a status of Open.

Note. The instantiation of these business projects is determined by the setID. Some setIDs may run business processes.

Running Batch Jobs in Order Management (PeopleSoft SCM customers only)

Subsequent to order submission, the Order Management fulfillment process starts with the OMEC process followed by the OM_BACKGRND process; OM_EC - OM Electronic Commerce is the process that moves data from the staging tables to the order production tables. OM_BACKGRND - Order Completion process completes the defaulting of values onto the order. .In Order Management, you can set up exclusions to choose which subprocesses within OMBACK to run or skip based on the order source code. Because orders that originate in CRM already have tax, freight, and pricing information, you should configure OMBACK to skip tax, freight, and pricing calculations for orders with the PeopleSoft CRM source code.

There are fours specific SCM processes you need to run to complete the pre-fulfillment tasks. These consist of:

  1. Order Validation Process (OM_EC)

  2. Order Completion Process (OMBACK)

  3. Outbound Acknowledgement (OMEC Outbound)

  4. Data Exchange (Data Publish)

Batch Job



1: Order Validation (OMEC)

When you submit an order, the transaction is loaded into order staging tables. We first need to run the Electronic Commerce SQR process (OMEC), which:

  • Parses data such as customer information and product information to ensure that it is valid.

  • Sets system defaults and status flags for subsequent processes.

  • Loads data into the production order tables (order staging data found to have errors is not loaded into the production tables until the errors have been resolved).

To run the OMEC batch job:

  1. In the FDM menu, navigate to Order Management, Electronic Commerce, Validate Staged Orders/RFQs.

  2. Add a new Run Control ID.

  3. In the Processing Options group box, select the Inbound Order/RFQ Activity check box.

    Note. This will make 2 extra fields (Transaction Type and Integration Point Control ID) available in the Processing Parameters group box.

  4. Leave the remaining 3 “queue” check boxes in Processing Options unchecked.

  5. In the Processing Parameters group box, choose the specific (Order Management) Business Unit you specified on the Order Capture Definition.

  6. Choose the Transaction Type of PO (Inbound Sales Order).

  7. Leave the Integration Point Control ID field blank.

  8. Click the RUN button. This tells the system to process our orders that are sitting in the staging tables. You will automatically be taken to the Process Scheduler Request.

  9. Choose the Server Name, PSNT, and then click OK. You will return to the Electronic Commerce page.

  10. Click the Process Monitor link and examine the Run Status of your job. You are looking to see the status change from Posting to Success. Click Refresh repeatedly to see if the status has changed.

2. Order Completion (OMBACK)

The Order Completion process (OMBACK):

  • Applies the agreement, sold to customer, ship to customer, bill to customer, and order group defaults to the order header and order lines.

  • Performs order pricing, and does tax defaulting and tax calculations.

  • Processes estimated shipments and external freight calculations.

To run the OMBACK batch job:

  1. Navigate to Order Management, Quotes and Orders, Process Orders, Order Completion

  2. Add a new Run Control ID.

  3. Select the same Business Unit you chose previously in the From Business Unit field.

    Note. The To Business Unit field automatically populates with the same Business Unit.

  4. In the From Order Number and To Order Number fields, select the entire range of your pending orders, and then click Run.

    Note. You will automatically be taken to the Process Scheduler Request.

  5. As with the previous job, choose the Server Name, PSNT, then click OK..

  6. Click the Process Monitor link, and examine the Run Status of your job. You are looking to see the status change from Posting to Success. Click Refresh repeatedly to see if the status has changed.

    Note. You can now view orders in the PeopleSoft SCM system.

3. Outbound Acknowledgement (OMEC Outbound)

The Outbound Publish process (OMEC Outbound) puts entries in the order acknowledgement queue, which are subsequently used to publish order acknowledgements to PeopleSoft CRM.

To run the OMEC batch job:

  1. In the FDM menu, navigate to Order Management, Electronic Commerce, Validate Staged Orders/RFQs.

  2. Select the Run Control ID you created when you ran OMEC.

  3. 3. Uncheck the Inbound Order/RFQ Activity check box, and check the Acknowledgement Queue.

  4. Click Run, and you will go to the Process Scheduler Request.

  5. Select the PSNT Server Name, and click OK.

  6. Click the Process Monitor link on the Electronic Commerce page.

  7. Examine the Run Status of your job. You are looking to see the status change from Posting to Success. Click Refresh repeatedly to see if the status has changed.


Batch Job



4. Data Exchange (Data Publish)

The Data Exchange job is used to publish the Sales Order Acknowledgement message to PeopleSoft CRM, using the information from the order acknowledgement queue.

To run the Data Publish job:

  1. In the FDM menu, navigate to Data Exchanges, Publish Outbound Message.

  2. Select your existing Run Control ID.

  3. On the Publish Outbound Message screen, there are a variety of check boxes. Select the Sales Order Acknowledgement check box. The Sales Order Acknowledgement will change to a link. Click on this link.

  4. On the Order Acknowledgement Message Selection Criteria page, first choose your Business Unit and then select CRM as the Source Code. Leave everything else blank.

    Note. In the Outbound Messages Selected group box, Order Acknowledgement Queue is pre-selected.

  5. Click OK. This takes you back to the Publish Outbound Message page. Click Run.

  6. Enter PSNT as the Server Name, and click OK. Then click on the Process Monitor link.

If the orders are In Process, this means that you have run the entire cycle of SCM batch jobs successfully.

Note. If you navigate to Order Management, Quotes and Orders, Create/Update Order, and choose your business unit, you can search for any order and see that a specific order is In Process.

Understanding the Transformation Process

PeopleSoft delivers transformation rules that you can use when sending information to Order Management. The Application Engine program that performs the transformation has three stages:

  1. It evaluates products and packages that were ordered and transforms order lines as follows:

    1. Service products are not sent at all, but other products are sent exactly as defined in the order line.

    2. Product packages are sent as packages, as there is a 1 to 1 mapping of information with Order Management here. However, lightly configured packages are broken into multiple order lines and packages contained in other packages are broken into multiple order lines. Each product included in the package within a package is given its own order line. For example, if Package 1 consists of product A and Package 2, while Package 2 consists of products B and C, then an order line for Package 1 is broken into three order lines: one each for products A, B, and C.

      Note. If you use PeopleSoft SCM and you set pricing at the package level (rather than the component level), no pricing details are sent; each component is sent with a price of zero. Therefore, if you are a SCM customer, pricing for dynamic packages needs to be at the component level.

  2. It performs an XSL transformation to structure the integration point data for Order Management.

  3. It adds SCM customer information (for example, bill to and ship to addresses) to the order data by looking at the tables (RB_INT_CUSTOMER and RB_INT_CUST_ADS) that map PeopleSoft CRM customer data to SCM customer data. This mapping is maintained by the Customer Sync integration point.

Note. If you use PeopleSoft SCM as your fulfillment system, you must keep customer and product data synchronized in the two systems. The Customer Sync and Product Sync integration points manage this synchronization.

Understanding the Message Content

This section describes certain parts of the order and quote messages published by CRM. For more details about the messages, refer to the integration point catalog and the message definitions. Order and quote messages published by PeopleSoft CRM include:

Click to jump to parent topicSubscribing to Order Status Messages

In PeopleSoft SCM, the Data Exchanges > Publish Outbound Message utility enables you to publish a snapshot of the order as it exists in the SCM system. The Sales Order/Quote Status option enables you to publish orders by business unit, source code (for example, CRM), customer, order type, order number range, order date range, and order change date range. Also, you can choose to publish orders for specific order status values.

Order Capture subscribes to these SALES_ORDER_STATUS messages to provide a method for synchronizing changes made to the order in SCM, so that the order reflects the same information. For example, if an order is maintained in SCM, and a new order line is added, the SALES_ORDER_STATUS message delivers that order and its new line to Order Capture.

Also, as part of the SALES_ORDER_STATUS processing, the current order status is updated, just as the Get Order Status integration point provides.

If the SALES_ORDER_STATUS message contains orders that did not originate in Order Capture (for example, EDI orders), then order header information is created so that these orders are viewable through the Order Search screen. When users drill down for further details, they are transferred to the uniform resource locator (URL) specified in the Source Code definition for that order. If no URL is specified, then the user is only able to view the header information for that order.

Getting On-Demand Status Updates

The Get Order Status integration point provides on-demand status updates. Users invoke the update by clicking the Refresh button on the Order Tracking page.

The Get Order Status integration point updates:

The integration point also updates the RO_LINE_HIST table, which stores a history of line statuses. You can query this history, but it does not appear on any Order Capture pages.

Click to jump to parent topicSubscribing to Order and Quote Acknowledgements

In PeopleSoft SCM, the Batch Publish job publishes regular acknowledgments (the SALES_ORDER_ACKNOWLEDGEMENT and SALES_QUOTE_NOTICE messages) and change acknowledgements (the SALES_ORDER_CHANGE_NOTICE message) for orders that come from electronic commerce channels—that is, for orders that are entered into the SCM staging tables.

Note. Change acknowledgements are not published for orders that originate within PeopleSoft Order Management.

In CRM, the Receive Order Acknowledgement and Receive Quote Acknowledgement integration points subscribe to SCM messages, while the Receive Order Change Acknowledgement integration point subscribes to the change acknowledgement message. When PeopleSoft CRM receives a change acknowledgement, the order status and change history are updated, while rejected order changes are rolled back. When Order Capture receives a simple order acknowledgement, it updates the order header status to In Process, and it sets the order line statuses to the line status map that you established in the Integration Workbench. When an SCM order line status is set to Open, and this is the status that the acknowledgement message sends, Order Capture maps this to a status of In Fulfillment.

Change History was created with a status of Open when order changes were initially submitted. When the change acknowledgement is processed, changes that were accepted by the Fulfillment system are marked Confirmed, and changes that are not accepted are marked Rejected. When a requested change is rejected, the original values on the order are restored back to their values prior to the change. For example, if a quantity on an order line was increased from 1 to 2, and that change is rejected because the order line had shipped, the quantity is restored to 1 following the processing of the change acknowledgement.

Change Acknowledgement updates order statuses just as the Get Order Status integration point does, providing a current snapshot of the order status at the time the Change Acknowledgement was published. Order statuses are set based on the status mapping that you establish. The Change Acknowledgement also creates order notifications based upon the setup for the Order Capture business unit.

Notifications may be specified to go to the customer, the CSR, both, or none, based on the acceptance of the changes that were requested. In addition, when notifications are specified for the CSR, the notification is sent based on the CSR's preferred notification setting as found in the Worker component, which can be email, worklist, or both. Notifications to the customer are sent to the email address of the contact listed on the order, or for a consumer order, the consumer's email address. If there is no email specified for the contact or consumer, notifications cannot be sent to the customer. Email notifications show the changes requested, along with the acceptance status of Confirmed or Rejected, and display the order following the Change Acknowledgement processing. A CSR's Worklist notification is a link to the order in the Order Capture Worklist.

Click to jump to parent topicSubscribing to ASNs

PeopleSoft Inventory publishes ASNs that provide the number of items that have shipped for a specific order line. These messages do not contain status information about items that have not shipped.

The Receive ASN integration point subscribes to the ASN message.

When PeopleSoft CRM receives an ASN, it updates statuses using the following logic:

  1. The shipped quantity from the ASN is added to any previously recorded quantity shipped.

  2. If the total shipped quantity is greater than or equal to the quantity ordered, the line and all items in the line have a status of Shipped.

  3. If the total shipped quantity is less than the quantity ordered, the system assumes that the items with the highest status were shipped and adjusts statuses accordingly.

Since status numbers increase as an item moves through the fulfillment process, the unshipped item with the highest status is considered the most likely item to have been shipped.

For example, consider the following status update history for an order line consisting of ten items:



Status From Message

Status Displayed in the Status By Quantity Section of the Order

10:00 am


10 In Fulfillment

10 In Fulfillment

1:00 pm


5 Shipped

5 Shipped

5 In Fulfillment

2:00 pm

Order status

10 Partially Shipped

10 Partially Shipped

5:00 pm


3 Shipped

3 Shipped

7 Partially Shipped

8:00 pm


2 Shipped

5 Shipped

5 Partially Shipped

10:00 pm


10 Shipped

10 Shipped

At 10:00 am, the order was submitted. An order acknowledgment message caused the system to set the status of all ten items to In Fulfillment.

At 1:00 pm, an ASN message indicated that five items had been shipped. Status changes for these five items and the remaining five items keep the status In Fulfillment.

At 2:00 pm, the order status message provided one status for all ten items of that order line, which will be displayed in the Line Details section and the Status By Quantity section of the order in the CRM system.

At 5:00 pm, an ASN message indicated that three more items were shipped. The system updates the Status By Quantity section after the receipt of this ASN message: three items with the status of Shipped and seven items with the status of Partially Shipped. Note that the update only reflects the change in item shipment gathered in this particular ASN message. Access the Package Tracking section of the order to view the total number of items that have been shipped successfully.

At 8:00 pm, an ASN message indicated that two items have shipped. The order will now show us that five have shipped and five are Partially Shipped (even though its true that all have shipped, we don't know that unless we look at the package tracking section).

At 10:00 pm, we receive an Order Status message, and it tells us that ten items have shipped, and now the CRM system shows ten Shipped.

Note. If an ASN is received for any component of a static package, the entire package is considered to have been shipped. When all products on the order have been marked either Shipped, Complete, or Cancelled, the order header status is set to Complete.

Click to jump to parent topicManaging Externally Originating Orders

This section explains how Order Capture handles externally originating orders, and explains how to specify URLs for tracking purposes.

Handling External Orders

Order Capture uses the Receive Orders integration point to create PeopleSoft CRM records for orders that originate in your fulfillment system (or any other external system). Unlike the Get Order Status integration point, the Receive Orders integration point does not attempt to match the external system's order numbers with Order Capture order numbers. Each Order Capture business unit definition specifies the source code that is used for orders created in the PeopleSoft CRM system. Orders that are entered by the Receive Orders integration point have a source code provided by the external system. Make sure that the source codes are different for orders that originate internally and externally.

Note. If a user attempts to view an order with a source code other than the one specified in the business unit definition, the system reroutes the user to a page that you specify. If you haven't specified a URL, then you see the header information in order tracking but you can't click on the order for details.

You can specify different target pages to be used when accessing orders in the internal Order Tracking page and the external (self-service) Order Tracking page. The system marks orders that originate outside of CRM, and if you provide the system with the URL for the external system, then a user who attempts to view such an order in the CRM order tracking pages is automatically redirected to the system where the order originated.

Click to jump to parent topicIntegrating with Billing Systems

Order Capture integrates with PeopleSoft Transaction Billing Processor to allow access to standard billing functionality such as revenue recognition structure, billing cycle details, and account rules for applying revenue to the General Ledger. It also allows the enterprise to apply surcharges and taxation to billable amounts and process them through user-defined invoice formats.

Click to jump to top of pageClick to jump to parent topicSetting Up an Integration to PeopleSoft Transaction Billing Processor

This integration is detailed in a chapter in the PeopleSoft Enterprise CRM 9.1 Services Foundation PeopleBook.

See Also

Transaction Billing Processor Integration

Click to jump to top of pageClick to jump to parent topicUsing the Transaction Billing Processor Integration from Order Capture

If a contract doesn’t exist, the Order Capture transaction triggers a new contract to be created in the Billing system. Pricing is done by the Enterprise Pricer through Order Capture. For agreement products, pricing is also done by the Service Pricing routines. Order Capture sends the total for each order line containing a service or agreement product to the Transaction Billing Processor.

Note. Transaction Billing Processor integrates with Order Capture and enables you to create invoices and recognize revenue for service products. However, Order Capture sends standard products through the integration to Order Management. Order Capture uses Proposal Management to send engagement-type services.

Order Capture only sends transactions that are ready to be billed to the Transaction Billing Processor. Order Capture also sends tax parameters, which are used to retrieve the sales and use tax or VAT rate.

See Also

PeopleSoft Enterprise Contracts 9.1 PeopleBook