Scribd
Upload
23 views1 page

Legacy Payments - Possible Approach

The document outlines a systematic approach for processing legacy payment feed data into Oracle E-Business Suite (EBS), including the transfer of invoice information and the development of a custom process for updating payment schedules. This process will handle complex scenarios such as partial payments and multiple invoices, while leveraging Oracle's standard payment functionality for automation and accuracy. Additionally, a scheduled custom process will reconcile data and update payment statuses to ensure traceability and alignment with historical records.

Uploaded by

sreekanthg.235
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
23 views1 page

Legacy Payments - Possible Approach

The document outlines a systematic approach for processing legacy payment feed data into Oracle E-Business Suite (EBS), including the transfer of invoice information and the development of a custom process for updating payment schedules. This process will handle complex scenarios such as partial payments and multiple invoices, while leveraging Oracle's standard payment functionality for automation and accuracy. Additionally, a scheduled custom process will reconcile data and update payment statuses to ensure traceability and alignment with historical records.

Uploaded by

sreekanthg.235
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Possible Approach:

1. Upon successful processing, all legacy payment feed data including invoice information against which
the payment is made, will be systematically transferred to the designated Oracle E-Business Suite
(EBS) custom staging tables. This step ensures that the data is accurately captured and made available
for subsequent validation, transformation, or integration activities within the EBS environment.
2. A new custom process will be developed to update payment schedules on Accounts Payable (AP)
invoices and assign the appropriate legacy payment method (e.g., Legacy-Wire). This process ensures
that the payment schedules are accurately aligned with the data received from the legacy system
including amount paid, supplier, invoice number etc.,

This custom process will be designed with the necessary intelligence to handle complex scenarios.
These include:

a. Managing multiple payment schedules in cases of partial payments,


b. Aligning payment schedules with corresponding prepayment applications against invoices,
c. Facilitating a single payment transaction across multiple invoices, and
d. Identifying and notifying relevant stakeholders of potential exceptions, enabling timely
intervention and corrective action.

3. Leveraging Oracle’s standard payment functionality, a Payment Process Request (PPR) will be
scheduled using predefined selection criteria based on the legacy payment method. This process will
initiate the generation of payments, which should ideally align with the original custom payment feed
received from the legacy system.

By leveraging Oracle’s standard payment functionality, the business benefits


a. From accurate and automated accounting processes, including the offsetting of liabilities on
invoices.
b. Seamless cash management reconciliation
c. Automatic updating of invoice payment statuses.
d. Reducing custom process involvement in critical architecture thereby enhancing efficiency,
reliability, and maintainability.

4. A scheduled custom process will perform the following functions,


a. Reconcile the data from the custom staging tables with the payments created in the previous
step, and accordingly update the status of the records in the staging table to reflect
successful processing.
b. Populate the designated Descriptive Flex fields (DFFs) on the payments created in Oracle E-
Business Suite (EBS) with the legacy payment number and payment date retrieved from the
staging data, ensuring traceability and alignment with historical records.

Assumptions:

Open Invoices are available in EBS to apply against those payments will be created based on the legacy
payment feed.

You might also like