Oracle R12 Upload External Payments in Payables

11/21

4 Process Integration for Payable Invoices

This chapter provides an overview of the procedure integration for payable invoices and discusses concern process flows, assumptions and constraints, Oracle East-Business organisation Suite (Oracle EBS) and Oracle Transportation Management (OTM) interfaces, cadre Oracle Application Integration Compages (Oracle AIA) components, and integration services.

This chapter includes the following sections:

• Department four.1, "Overview"

• Section four.ii, "Business Process Flows"

• Department 4.three, "Assumptions and Constraints"

• Section 4.4, "Oracle EBS Interfaces"

• Section 4.five, "OTM Interfaces"

• Department iv.half dozen, "Core Application Integration Architecture Components"

• Section four.7, "Integration Services"

4.one Overview

The payables invoice integration flow allows OTM to pay its service providers, carriers, and other parties by sending its invoice (vouchers) transactions to the Oracle EBS Payables application. Oracle EBS Payables generates the payment and create the proper bookkeeping for the payment transactions.

iv.2 Business organisation Process Flows

The procedure integration for payable invoices supports these integration flows:

• Voucher match and pay (no car pay).

  OTM receives the invoice from the service provider:

  1. Matches information technology to the shipments based on the lucifer rules and approves the invoice.

  2. Creates the voucher.

  3. Changes the voucher condition to issued and sends the transaction using the VoucherXML to Oracle EBS Account Payables (AP).

• Voucher auto pay.

  OTM calculates the freight charges for the shipments:

  1. Approves the invoice.

  2. Creates the voucher.

  3. Changes the voucher status to issued and sends the transaction using the VoucherXML to Oracle EBS Business relationship Payables (AP).

• Consolidated invoice batches.

  OTM receives a consolidated invoice from a service provider for multiple shipments:

  1. Matches the consolidated invoice with the shipments.

  2. Approves the invoice for payment.

  3. Creates a voucher.

  4. Changes the voucher status to issued and sends the transaction using the VoucherXML to Oracle EBS AP.

• One invoice with multiple vouchers.

OTM receives an invoice for multiple payments from a service provider:

• 1. Matches it with the shipments.

  2. Manually approves invoice for fractional payment.

  3. Creates the voucher.

  4. Changes the voucher status to issued and sends the transaction using the VoucherXML to Oracle EBS AP.

• Prepaid invoice (comcheck).

  The user manually creates a prepayment invoice both in OTM and Oracle Due east-business suite. When the service provider invoice arrives:

  1. OTM creates a voucher containing the total invoice amount, prepayment amount, advance fee, and outstanding approved voucher amount.

  2. OTM changes the voucher status to issued and sends the transaction using the VoucherXML to Oracle EBS AP.

  3. The prepayment application is washed automatically based on the reference fields entered in the voucher.

• Credit memo.

  OTM receives an invoice from the service provider:

• 1. Matches the invoice to the shipments.

  2. Creates a credit memo for over payment, matches information technology with the original shipment, and creates the invoice with the status of procedure hold. The user approves the invoice and creates the approved voucher.

  3. Changes the approved voucher condition to issued, and sends the transaction using the VoucherXML to Oracle EBS AP.

• Voucher with third-party payment

  OTM receives a supplier invoice, which specifies that a third-party supplier should exist paid for the service. For case, OTM plans the shipment and sends a tender to supplier A. Supplier A wants supplier B to be paid for the service:

• 1. Approves the invoice.

  2. Creates the voucher, changes the voucher status to issued, and sends the transaction using the VoucherXML to Oracle EBS AP to pay supplier B.

• Foreign currency voucher.

  OTM receives an invoice in a foreign currency:

• 1. Matches information technology to the shipments based on the lucifer rules.

  2. Approves the invoice.

  3. Creates the voucher with the strange currency.

  4. Changes the voucher status to issued, and sends the transaction using the VoucherXML to Oracle EBS AP.

• Voucher with Disputed Amount and Reason.

  If the shipment is partially paid, OTM approves the invoice:

  1. Creates the voucher with the original invoice amount, approved payment corporeality, and dispute reason.

  2. Changes the voucher status to issued, and sends the transaction using the VoucherXML to Oracle EBS AP.

Figure 4-1 shows the process integration for payable invoices:

Figure 4-1 OTM (Logistics) to Oracle E-business Suite Payable Invoice Menstruum

4.2.1 Sending Payable Invoices to Oracle EBS Business relationship Payables

The payable invoices integration flow creates the invoice in Oracle EBS AP based on the voucher sent from OTM.

Figure 4-2 shows the payable invoice menstruation from OTM to Oracle E-Business concern Suite:

Figure 4-two OTM (Logistics) to Oracle E-business Suite Payable Invoice Flow

When you lot initiate the process, these events occur:

1. OTM enqueues the messages into the AIA_PAYABLEINVOICE_AQ queue. The CreatePayableInvoiceListLogisticsAQConsumer service dequeues the messages and invokes the CreatePayableInvoiceListLogisticsReqABCSImpl service.

2. The CreatePayableInvoiceListLogisticsReqABCSImpl service transforms the OTM PayableInvoiceListLogisticsABM into the CreatePayableInvoiceListEBM, populates the enterprise business concern message (EBM) Header, updates the cross-reference data, and invokes the PayableInvoiceEBS with the CreatePayableInvoiceList operation in fire and forget mode.

3. The PayableInvoiceEBS service with the CreatePayableInvoiceList functioning routes the letters based on the Blended Application Validation Service (CAVS) flag to either the CreatePayableInvoiceListEbizProvABCSImpl service or the CAVS simulator in an synchronized burn down and forget mode.

4. The CreatePayableInvoiceListEbizProvABCSImpl transforms the CreatePayableInvoiceListEBM into the Oracle E-Business Suite PayableInvoiceListEbizABM, and invokes the CreatePayableInvoiceListEbizDBAdapter.

5. The CreatePayableInvoiceListEbizDBAdapter service receives the PayableInvoiceListEbizABM and makes insert calls to the Oracle E-Business organization Suite accounts payable interface table.

4.three Assumptions and Constraints

These are the solution assumptions and constraints:

• OTM sends only approved vouchers for payment.

• OTM creates the vouchers and enqueues them in the AIA_PAYABLEINVOICE_AQ queue based on user defined agents.

• If any errors occur and the voucher does not reach Oracle EBS interface tables, the AIA error handling framework notifies you.

  You lot must manually re-submit the transactions that failed. In instance a batch of vouchers is sent in a unmarried transmission, if a single voucher fails, the whole batch fails and should be sent once more.

• This integration does non perform any validations and raise errors due to any business validation failure in OTM or in Oracle EBS.

  For example, if the Oracle EBS invoice import process rejects the invoice due to a validation mistake, you should manually correct the data in the Oracle EBS interface tables and re-run the import process.

• This integration supports only the cosmos of a listing of payable invoices. Update and query of payable invoices is non supported in this integration.

• OTM matches the invoices against shipments and sends the approved vouchers to Oracle EBS AP based on a user-defined agent. Duplicate payment checking is done in OTM.

• OTM only sends single currency invoices for payment. As the OTM requester ABCS does non validate if the currency is different at the line level and at the header level, OTM must reject the invoices that have different currency at the header and the line level.

• An invoice tin can just belong to one operating unit. Therefore, if there are consolidated invoices with multiple operating units, the payments are made from only one operating unit of measurement.

• Payment terms are fix and maintained in Oracle EBS AP. OTM does not ship the payment terms with an invoice; therefore, the payment terms is defaulted by Oracle EBS AP organisation.

• OTM does non send the invoice due engagement information to Oracle E-Business concern AP. Oracle EBS AP derives the due date of an invoice using a setup of the default terms and date at the supplier site level.

  For automobile pay, the invoice received appointment in OTM is blank; therefore, y'all must set up up the suppliers site payment terms based on the system appointment.

• Payment method is maintained in Oracle EBS AP and tin can be overridden at the transaction level.

• Supplier pay site is derived by Oracle EBS AP based on the supplier number and the operating unit included in the invoice sent by OTM.

• If an invoice comes into Oracle E-Business AP for an inactive supplier or supplier site, Oracle EBS AP rejects the invoice.

• OTM populates the reference number to point the operating unit with a reference qualifier type as OP_UNIT based on the agents divers to copy this value from society release to shipment and invoice.

• All invoices are assigned the default invoice type of standard, unless there is a negative corporeality at the voucher level and so the invoice blazon is a credit memo.

• For consolidated invoices, the parent invoice in OTM is the invoice header in Oracle EBS AP and the child invoice lines in OTM are the invoice lines in Oracle EBS AP.

• For a prepayment application, OTM should send a negative line corporeality and the Oracle AP prepayment invoice number as a reference number in the reference qualifier name PREPAY_INV_NUMBER.

  This is considered a prepay line blazon and Oracle EBS AP applies the prepayment and reduce the total corporeality. If you practise not put a reference number value in the invoice, the invoice is treated equally a negative invoice and a prepayment is not applied.

• Merely one prepayment awarding invoice line is immune for each invoice. If in that location are multiple prepayment invoice lines in an invoice, it fails within the Oracle E-Business concern AP application.

• Users should use OTM for cancellations (either contrary, or issuing a credit note) instead of using standard Oracle E-Business Invoice counterfoil functionality.

• For consolidated invoices, if a parent invoice has ii or more than invoices and each invoice has 2 or more lines, then there are four or more lines and 1 header in Oracle E-Business AP.

  For instance, if an OTM consolidated invoice has two invoices and each invoice has two lines of $25 each, then in that location is an invoice of $100 in Oracle E-Business AP with four lines of $25 each.

• The OTM invoice number and the voucher XID should not be more fifty characters. Oracle EBS invoice number should be unique and should non exist more than fifty characters.

4.5 OTM Interfaces

OTM uses PayableInvoiceListOTMABM to send approved vouchers for payment to accounts payable financials system. GLogXML.xsd, element - Manual, subelement - Voucher

For more data about the logistics service, come across Oracle Transportation Management Integration Guide.

four.6 Cadre Application Integration Architecture Components

The integration catamenia uses these components:

• PayableInvoiceEBO

• CreatePayableInvoiceListEBM

• PayableInvoiceEBS

The core enterprise business object (EBO) and enterprise business message (EBM) XSD files can be located by EBO within the $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/ parent folder.

The core enterprise business services (EBS) web services definition linguistic communication (WSDL) files tin can be located by EBO within the $AIA_HOME/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Cadre/EBO/ parent folder.

For detailed documentation of individual EBOs and EBMs, click AIA Reference Doc link on EBO and EBM detail pages in the Oracle Enterprise Repository.

For more than data about using the Oracle Enterprise Repository and configuring it to provide the AIA Reference Medico link, come across Oracle Fusion Middleware Developer's Guide for Oracle Awarding Integration Architecture Foundation Pack, "Configuring and Using Oracle Enterprise Repository equally the Oracle AIA SOA Repository."

EBOs can be extended, for instance, to add new data elements. These extensions are protected, and remain intact after a patch or an upgrade.

For more information, come across Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Compages Foundation Pack, "Extensibility for AIA Artifacts".

4.7 Integration Services

These are the services delivered with this integration:

• CreatePayableInvoiceListLogisticsAQConsumer

• CreatePayableInvoiceListLogisticsReqABCSImpl

• PayableInvoiceEBS

• CreatePayableInvoiceListEbizProvABCSImpl

• CreatePayableInvoiceListEbizDBAdapter

• UpdatePayableInvoiceListEbizXref

• PayableInvoiceResponseEBS

iv.7.1 CreatePayableInvoiceListLogisticsAQConsumer

This mediator service dequeues the InvoiceListLogisticsABM message whenever OTM enqueues a message into AIA_INVOICE_AQ queue. This service takes the PayableInvoiceListLogisticsABM from the wrapper AQ xsd, which contains the entire transmission chemical element as CLOB. This service invokes the CreateInvoiceListLogisticsReqABCSImpl service.

4.7.2 CreatePayableInvoiceListLogisticsReqABCSImpl

The CreatePayableInvoiceListLogisticsReqABCSImpl is a Business Process Execution Language (BPEL) process and a unmarried operations service that has the PayableInvoiceEBS as a partner service. This service receives the PayableInvoiceListLogisticsABM message every bit a request and does not render a response to the calling service.

This service performs these actions:

• Accepts the PayableInvoiceListLogisticsABM message from OTM.

• Transforms the PayableInvoiceListLogisticsABM into the CreatePayableInvoiceListEBM. While it is transforming from the awarding business message (ABM) to the enterprise business bulletin (EBM), cantankerous-references are populated for the: PAYABLEINVOICE_PAYABLEINVOICEID.

• Sends the CreatePayableInvoiceListEBM message as an input to the CreatePayableInvoiceList operation in the PayableInvoiceEBS service.

These DVM lookups are used by this service:

• PAYMENTMETHOD_CODE: domain value mapping for the payment method codes.

• PAYABLEINVOICE_PAYABLEINVOICELINETYPE: domain value mapping for the payable invoice line types.

4.seven.iii PayableInvoiceEBS

The PayableInvoiceEBS is an enterprise business service that exposes all the enterprise operations related to the payable invoice like create payable-invoice, update payable-invoice, and so on. This integration uses only the CreatePayableInvoiceList performance. This service routes the request to the appropriate provider similar the CreatePayableInvoiceListEbizProvABCSImpl or the Composite Application Validation System (CAVS) based on the filter condition and operations. No transformations are done in this service.

For more data about this enterprise concern service (EBS), see Oracle Fusion Middleware Developer'southward Guide for Oracle Application Integration Architecture Foundation Pack, "Designing and Developing Enterprise Business Services" and Oracle Fusion Middleware Concepts and Technologies Guide for Oracle Awarding Integration Compages Foundation Pack, "Agreement Enterprise Concern Services".

4.7.4 CreatePayableInvoiceListEbizProvABCSImpl

The CreatePayableInvoiceListEbizProvABCSImpl is a BPEL process, which receives the CreatePayableInvoiceListEBM, transforms the message into the PayableInvoiceEbizABM, and invokes the CreatePayableInvoiceListEbizDBAdapter service.

These DVM lookups are used by this service:

• PAYABLEINVOICE_PAYABLEINVOICETYPE: domain value mapping for the invoice type (that is standard, credit memo).

• PAYMENTMETHOD_CODE: domain value mapping for the payment method codes.

• PAYABLEINVOICE_PAYABLEINVOICELINETYPE: domain value mapping for the payable invoice line types.

iv.7.5 CreatePayableInvoiceListEbizDBAdapter

This service accepts the PayableInvoiceListEbizABM message from the CreatePaybleInvoiceListEbizProvABCSImpl and inserts the data into the Oracle EBS AP interface tables.

iv.vii.6 UpdatePayableInvoiceListEbizXref

The UpdatePayableInvoiceListEbizXref service is a Business concern Process Execution Language (BPEL) procedure. When the payables open interface program successfully imports an invoice, it raises the business organization event oracle.apps.ap.invoice.import. The subscription to this event calls the UpdatePayableInvoiceListEbizXref service. This service using the UpdatePayableInvoiceListEbizXrefAdapter, fetches the invoice IDs and corresponding AIA global unique identifier (GUID), and updates to the PAYABLEINVOICE_PAYABLEINVOICEID cross-reference tabular array.

If you choose not to utilize this service, y'all tin disable the event subscription in the Oracle EBS awarding.

4.vii.7 PayableInvoiceResponseEBS

The PayableInvoiceResponseEBS is the enterprise concern service (EBS) used to route all payable invoice response related actions to the requesting awarding similar create payable-invoice response, update payable-invoice response, delete payable-invoice response, and synchronize payable-invoice response. CreatePayableInvoiceListResponse is implemented as a function of this integration.

langstoninforent.blogspot.com

Source: https://docs.oracle.com/cd/E58077_01/doc.116/e50313/processintepayinvo.htm

Share this post