Return to Navigation

Creating 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.