Siebel Order Management Guide > Integrating Order Management with Back-Office Applications >

About ASIs for Order Management


Siebel's Application Services Interfaces (ASIs) are predefined interfaces that allow the exchange of information between Siebel Business Applications and external applications.

Several features of Siebel Order Management use ASIs. They include:

  • Availability to promise. Availability to promise (ATP) allows end users to inquire whether an item is available. End users can specify a requested date, a specific source such as an inventory location, and preferred shipment methods that could impact the delivery time. End users can also reserve available products for a customer to make sure they are available when the order is processed, and they can unreserve products if customers change their minds.

    When the user clicks the Inquire, Reserve, or Unreserve button in a quote or order, the business service sends a request to a back office fulfillment engine to determine whether the specified line items are available. For details about how to set up the Availability to Promise ASI, see Integrating Order Management with Third-Party Product Availability Applications. For details about the user's experience of using the ATP functionality, see Checking Availability to Promise (ATP).

  • Credit check. When a customer uses the purchase order payment option for a quote or an order, the end user can perform a credit check to make sure that the customer can make the purchase on credit. In a quote, the user can perform the credit check by clicking the Credit Check button, which available in the Payment Detail - Purchase Order view when the payment method is Purchase Order. This action sends a request to an external application to get the credit decision for that transaction. Typically, the external application that performs the credit check is the back-office order or credit management application. For details about how to set up the Credit Check ASI, see Integrating Order Management with Third-Party Credit-Check Applications. For details about the users' experience of using the credit check functionality, see Checking Credit for a Purchase Order.
  • Submit order. When users have finished defining an order for a customer and the customer has agreed to the price and provided payment information, the order is submitted to the back office. When the user clicks the Submit button, the Submit Order ASI workflow sends information about the order to the back office application. For details about setting up the ASIs used by this workflow, see Setting Up Quote and Order ASIs. For details about the user's experience of using the submit order functionality, see Submitting an Order.
  • Submit quote. After a quote has been verified, the user can submit the quote to the back-office or any external application. When the user chooses the Submit menu option for a quote record from the menu on the Quote list, the Submit Quote ASI workflow sends the quote information to the external application and updates Siebel with the response from the external application.

    The external application might use the quote information for converting a quote to an order or for production planning. Make any additional required configurations in the Siebel Business Application as required to meet your company's business needs. For details about setting up the ASIs used by this workflow, see Setting Up Quote and Order ASIs.

  • Query order status. Typically, a company will receive information about the status of orders at regular intervals from the fulfillment application. However, when salespeople talk with customers about the status of an order, they want to make sure that they present the most current information. In order to do so, they can click the Get Status button on an order. This button calls the Get Order Status ASI workflow, which retrieves information from the back-office application. For details about setting up the ASIs used by this workflow, see Setting Up Quote and Order ASIs. For details about the user's experience of using the submit order functionality, see Submitting an Order.
  • Updating order status. When the status of an order is updated in a back-office application, it can replicate that information in the Siebel Business Application to keep the two applications synchronized. This synchronization is done by using the Siebel Order ASI with a method of Update or Sync, and can be set up as a Web service. For details about using the Siebel Order ASI, see Setting Up Quote and Order ASIs.

Figure 1 shows the points in the order process where ASI integration occurs.

Figure 1. ASI Integration Points in the Ordering Process

You must set up the ASIs shipped with Siebel Order Management before they can be used. This chapter provides the procedures that you must perform to set up these ASIs. It also describes the ways that Siebel Order Management calls ASIs, and documents the workflows that you may want to modify to change the ways that ASIs are called.

For general information about ASIs, see Siebel Application Services Interface Reference.

Siebel Order Management Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.