| Oracle® Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cash Implementation Guide Release 3.1.1 Part Number E20515-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Application Integration Architecture Siebel CRM Integration Pack for Oracle Order Management: Order to Cash Implementation Guide Release 3.1.1 Part Number E20515-04 |
|
|
PDF · Mobi · ePub |
This chapter provides an overview and discusses the process integration for Credit Check.
This chapter includes the following sections:
Section 9.2, "Siebel Customer Relationship Management (Siebel CRM) Interfaces"
Section 9.3, "Oracle E-Business Suite (Oracle EBS) Interfaces"
Section 9.4, "Core Oracle Application Integration Architecture (Oracle AIA) Components"
If the order payment method is Purchase Order, then the Credit Check integration flow can be called on request before submitting the order. The Credit Check integration flow is a synchronous call, initiated in Siebel Customer Relationship Management (Siebel CRM) that obtains the credit check status from Oracle EBS. The account ID and order amount are passed to Oracle E-Business Suite (Oracle EBS) to check whether the order must be on credit hold. Oracle EBS responds with a message indicating whether to put the order on hold. This data is returned to Siebel CRM so that a Customer Service Representative (CSR) can inform the customer. The order is not sent to the back office until the hold is removed in Siebel CRM and the order is resubmitted.
If the credit check fails, then the Hold flag is set to True and the purchase order payment status is set to Rejected. When an order is submitted to Oracle EBS, if the Hold flag is enabled or if the purchase order status is not set to Approved, then the order is not submitted to the back office system for fulfillment.
This integration flow works with Siebel sales orders only, not quotes.
Figure 9-1 and Figure 9-2 illustrate where the Credit Check integration flow fits in the Order to Cash integration flow.
Find prerequisites in Chapter 13, "Reviewing Prerequisites and Data Requirements."
These are the assumptions for the Credit Check integration flow:
The credit profile is maintained in Oracle EBS before credit check being invoked.
The order payment method is Purchase Order.
Credit check is not supported for Siebel quotes.
This integration flow uses the following interfaces:
CustomerPartyEBS
CreditCheckSalesOrderSiebelReqABCSImpl
ProcessCreditEligibilityEbizProvABCSImpl
Figure 9-3 illustrates the Credit Check integration flow:
From the Siebel Order window, search for and select your order.
Order line items appear in the line item applet. Navigate to the Payments applet and select Payment Lines. Click the New button on the Payment Lines tab. Enable the Payment Method option and select Purchase Order. Click outside the applet to save information.
Navigate to the Payment Detail - Purchase Order applet. The Transaction Amount field equals the Transaction Amount field from the Payment Lines applet. The Credit Status, Credit Status As Of, and Credit Check Message fields are gray and set to null. Click Credit Check at the top of the applet. Customer credit information is returned to Siebel CRM from Oracle EBS.
The Siebel web service calls the CreditCheckSalesOrderSiebelReqABCSImpl with the operation CreditCheck.
The CreditCheckSalesOrderSiebelReqABCSImpl transforms the CreditCheckSiebleReqMsg into ProcessCreditEligibilityVerificationEBM and invokes the CustomerPartyEBS with the operation ProcessCreditEligibilityVerification.
Invoking the CustomerPartyEBS with the message ProcessCreditEligibilityVerificationEBM and the operation ProcessCreditEligibilityVerification routes the message to the ProcessCreditEligibilityEbizProvABCSImpl.
The ProcessCreditEligibilityEbizProvABCSImpl with the input message ProcessCreditEligibilityVerificationEBM does a transformation from ProcessCreditEligibilityVerificationEBM to the input of Oracle EBS OE CREDIT_CHECK_PUB API.
The response of the CREDIT_CHECK_PUB API is transformed back to the ProcessCreditEligibilityVerificationResponseEBM, and the response is sent back to the CustomerPartyEBS.
The CustomerPartyEBS with the message ProcessCreditEligibilityVerificationResponseEBM and operation ProcessCreditEligibilityVerification routes the message to the invoking CreditCheckSalesOrderSiebelReqABCSImpl.
The CreditCheckSalesOrderSiebelReqABCSImpl transforms the ProcessCreditEligibilityVerificationResponseEBM to the ProcessCreditEligibilityVerificationRespMsg, and the response is sent back to the invoking sync web service.
The result of the Credit Check appears in Siebel CRM. If the Credit Check is successful, the payment status field indicates Approved status.
For the Credit Check integration flow, these are the Siebel CRM artifacts:
SWIOrderIO.xsd
Siebel calls the CreditCheckSalesOrderSiebelReqABCSImpl with a CreditCheckSalesOrderReqMsg application business message (ABM).
SWIOrderIO.xsd
Siebel expects the CreditCheckSalesOrderRespMsg ABM from CreditCheckSalesOrderSiebelReqABCSImpl.
For more information about Siebel web services, see CRM Web Services Reference.
The Oracle EBS web services for the Credit Check integration flow are:
APPS_OE_EXTERNAL_CREDIT_PUB_CHECK_EXTERNAL_CREDIT.xsd
Service Name: OE_EXTERNAL_CREDIT_PUB. CHECK_EXTERNAL_CREDIT
APPS_OE_EXTERNAL_CREDIT_PUB_CHECK_EXTERNAL_CREDIT.xsd
Service Name: OE_EXTERNAL_CREDIT_PUB. CHECK_EXTERNAL_CREDIT
For more information about Oracle E-Business Suite web services and documentation prior to Release 12.1.3, see the library on Oracle Technology Network: http://www.oracle.com/technetwork/documentation/applications-167706.html?. For Oracle E-Business Suite documentation for R12.1.3 and beyond, see this library: http://download.oracle.com/docs/cd/E18727_01/index.htm?
The Credit Check integration flow uses the following delivered horizontal components:
CreditEligibility EBO
ProcessCreditEligibilityVerificationEBM
ProcessCreditEligibilityVerificationResponseEBM
For detailed documentation of individual EBOs and EBMs, click the AIA Reference Doc link on EBO and EBM detail pages in Oracle Enterprise Repository.
For more information about using the Oracle Enterprise Repository and configuring it to provide the AIA Reference Doc link, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository."
EBOs can be extended, for instance, to add new data elements. These extensions are protected, and they remain intact after a patch or an upgrade.
For more information, see Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack, "Understanding Extensibility."
The following services are delivered with the Credit Check integration flow:
CustomerPartyEBS
CreditCheckSalesOrderSiebelReqABCSImpl
ProcessCreditEligibilityEbizProvABCSImpl
For more information, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Configuring and Using Oracle Enterprise Repository as the Oracle AIA SOA Repository."
For the Credit Check integration flow, the CustomerPartyEBS exposes the ProcessCreditEligibilityVerification operation related to the CustomerParty EBO and:
Routes ProcessCreditEligibilityVerificationEBM to the Oracle EBS provider service
Routes ProcessCreditEligibilityVerificationResponseEBM to the Siebel requester service
For more information about this EBS, see Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack, "Designing and Developing Enterprise Business Services" and Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Application Integration Architecture Foundation Pack, "Understanding Enterprise Business Services."
The CreditCheckSalesOrderSiebelReqABCSImpl is the application business connector service (ABCS) that exposes the Credit Check operation related to the Credit Check integration on the Siebel ABM.
This Business process Execution Language (BPEL) process is used by the ProcessCreditEligibilityVerification integration flow. The CreditCheckSalesOrderSiebelReqABCSImpl transforms the Siebel Request message into the ProcessCreditEligibilityVerificationEBM and calls the CustomerPartyEBS. The CustomerPartyEBS routes it to the provider service ProcessCreditEligibilityEbizProvABCSImpl.
The provider service gets the CreditCheck details from Oracle EBS and sends back the ProcessCreditEligibilityVerificationResponseEBM to the routed EBS. The routing EBS then routes the message to the CreditCheckSalesOrderSiebelReqABCSImpl.
The CreditCheckSalesOrderSiebelReqABCSImpl then transforms the ProcessCreditEligibilityVerificationResponseEBM to the Siebel response message and returns it to the calling Siebel web service.
The CreditCheckSalesOrderSiebelReqABCSImpl has the following transformations:
XformRequestCreditEligibilitySiebelReqMsg_to_ProcessCreditEligibilityVerificationEBM
XformProcessCreditEligibilityVerificationEBM_to_CreditCheckSalesOrderRespMsg
The ProcessCreditEligibilityEbizProvABCSImpl BPEL process is used by the ProcessCreditEligibilityVerification integration flow. The CustomerPartyEBS routes the ProcessCreditEligibilityVerificationEBM message to the provider ABC ProcessCreditEligibilityEbizProvABCSImpl. This process is the provider implementation for credit eligibility verification when the application is Oracle EBS.
The ProcessCreditEligibilityEbizProvABCSImpl transforms the ProcessCreditEligibilityVerificationEBM message into an Oracle EBS application programming interface (API)-specific message (ABM message). The provider ABCS calls the Oracle EBS adapter with the ABM message and gets the ABM response message from Oracle EBS. The ProcessCreditEligibilityEbizProvABCSImpl transforms this response ABM message into the ProcessCreditEligibilityVerification ResponseEBM and sends it back to the CustomerPartyEBS.
|
 Copyright © 2001, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
