| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Order Management Guide > Preparing for Integration > About Using Third-Party Product Availability Applications >
Optional Setup Procedures for Checking Availability
When setting up the use of third-party product availability-to-promise systems, you may want to perform the following tasks:
Preventing Rollup of Availability Information
Product availability information is displayed for:
- The entire quote or order
- The quote or order line items
- The scheduled line items
The following information is preconfigured to roll up:
- Available status, date, and quantity are rolled up from the promised lines to the quote or order lines.
- Available status and date are rolled up from the quote or order lines to the quote or order header.
If your availability fulfillment engine only returns promised schedule lines and does not roll up this data to the line or the header, the out-of-the-box behavior will provide you with a rollup of the data.
If, however, your fulfillment engine already calculates this rollup, or if you do not want to roll up these fields, you may want to turn off this behavior.
Following are some examples of the preconfigured rollup of availability information:
- Dates: The latest date is rolled up at the parent level. For example, if line 1 has an available date of 7/15/02 and line 2 has an available date of 7/23/02, the available date for the order is set to 7/23/02.
- Status: If all lines have an ATP status of Available, the order also has a status of Available. However, if one of the lines has a different status, the order status is kept blank.
- Quantity: If Schedule line 1 has an availability quantity of 10, Schedule line 2 has an available quantity of 20, and both lines have the same ATP status of Available, then the quantity rolled up is the sum of both quantities (30).
NOTE: Rollup only occurs on quantity and date when the status of the promised line or the status of the line item is Available or Reserved.
To turn off computation of the availability summary date
- In Siebel Tools, select the ATP business service.
- Select Business Service User Prop.
- Select the Rollup Availability user property, and change the value from Y to N.
Extending the ASI
If you want to extend the ASI, you must add fields to:
- The External Integration object called ATP Check Interface
- These Internal Integration objects:
- ATP Check Interface Request - Quotes
- ATP Check Interface Request - Orders
- ATP Check Interface Response - Quotes
- ATP Check Interface Response - Orders
This will create the necessary mapping between the ATP interface structure and the Siebel Quote and Order business components.
NOTE: If you make changes to these objects, the names of the fields in the Internal and External integration objects must match.
If you add a field, make sure that the names of the fields in the Internal and External integration objects match. For example, if you want to add the field Account DUNS# that maps on quote to Account DUNS#-quote and on order to Account DUNS#-order, you would do so as follows:
- ATP Check Interface
Integration Component Field:
Name: Account DUNS#
External Name: <BLANK>
- ATP Check Interface Request - Quotes
Integration Component Field:
Name: Account DUNS#
External Name: <your mapping of Account DUNS # to the Quotes Buscomp>
- ATP Check Interface Request - Orders
Integration Component Field:
Name: Account DUNS#
External Name: <your mapping of Account DUNS # to the Orders Buscomp>
If this is a field that you do not want the fulfillment engine to be able to modify, such as Ship To Address Id, add the NoUpdate Field user property to the internal response integration objects, as follows:
- ATP Check Interface Response - Quotes
Integration Component Field:
Name: Ship To Address Id
External Name: <your mapping of Ship To Address Id to the Quotes Buscomp>
Integration Component Field User Property:
Name: NoUpdate
Value: Y
- ATP Check Interface Response - Orders
Integration Component Field:
Name: Ship To Address Id
External Name: <your mapping of Ship To Address Id to the Orders Buscomp>
Integration Component Field User Property:
Name: NoUpdate
Value: Y
For information about how to extend the integration object, see Integration Platform Technologies: Siebel eBusiness Application Integration Volume II.
Extension of Returned Data
For information about how to extend the data that is received from the third-party inventory management system, including data about products that are expected to be manufactured, see Application Services Interface Reference: Siebel eBusiness Application Integration Volume VI.
Customization of UI Terms
You may want to change the following terms in the user interface to more precisely reflect the type of data expected by, and returned by, your particular product availability fulfillment engine.
Requested Date. This could be either the date on which the customer wants to receive the product or the date on which the customer wants the seller to ship the product
Available Date. This could be either the date that the customer will receive the product or the date that the product will be shipped.
These two fields are designed to work together, reflecting parallel information.
| Bookshelf Home | Contents | Index | Search | PDF | |
Siebel Order Management Guide Published: 18 April 2003 |