Oracle Receivables - Version 11.5.9 to 11.5.10.3 [Release 11.5.9
to 11.5.10]Information in this document applies to any
platform.OEXOEORD - Sales OrderARPREMAT - Prepayments Matching
ProgramARXRWMAI - ReceiptsRAXTRX - Autoinvoice Import
ProgramAR_PREPAYMENTS_PUB.Create_prepayment
PURPOSEStarting from Financials Family Pack EPatch 2842697, the
feature for multiple prepayments was released. You can create
multiple prepayments from Order Management at the time of entering
a new order.
This document describes the process flow and tables impacted by
this feature.DETAILSProcess: The process for multiple prepayments
is as follows:1. Enter a new sales order from Order Management
Responsibility: Order Management Super UserNavigation: Orders
& Returns > Sales Orders (Form Name: OEXOEORD)Note: Check
the "Others" tab / Payment_Term field: the entered payment term of
the order must be prepayment specific. This has to be setup in
advance!2. Book the order3. Navigation: Actions-button >
Payments4. Enter payment informationEnable flag: prepayNote: You
can enter multiple prepayments of different types at once as long
as the following is set:Responsibility: Order Management Super
UserNavigation: Setup > System Parameters Values > Payments
Parameters
Set Allow multiple payments: YESAlso you can create partial
prepayments from here.5. Click "Process Payments" button.The
prepayment API gets kicked off
(AR_PREPAYMENTS_PUB.Create_prepayment) and a receipt gets created
in AR
When checking the receipt at this point, see that an application
of type "prepayment" exist. Review the following:- Field
"Application Reference Number" (Folder) shows the order number-
Field "Application Reference type" shows "Calling from Order
Management"6. Run the Workflow Background Process from OM to
populate data into the AutoInvoice Interface tables
(RA_INTERFACE_LINES_ALL, and others)
FNDWFBG module: Workflow Background ProcessProcess deferred:
YesProcess timeout: Yes7. Run the Autoinvoice import program
(RAXMTR / RAXTRX) for batch source ORDER ENTRY
Please note that the Prepayments Matching Program (ARPREMAT)
gets kicked off automatically through autoinvoice. This program
matches existing prepayments with corresponding and currently
imported Orders/Invoices.8. Check the previously created receipt
after the autoinvoice import of the Order/Invoice again.Note that
the application is not of type prepayment anymore, but the receipt
has been automatically applied to the invoice now.Tables: The
tables impacted by the Prepayment feature:1. RA_CUSTOMER_TRX_ALL
(contains details for the Invoice), the following fields are
impacted:
- PREPAYMENT_FLAG: Y- CT_REFERENCE: equals the
sales_order_number2. RA_CUSTOMER_TRX_LINES_ALL (contains details
for the Invoice), the following fields are impacted:
PAYMENT_SET_ID: contains a value for lines of LINE and
FREIGHT
The payment_set_id is the id to match prepaid invoices with
their prepayment receipts.Validation: Must exist in
AR_RECEIVABLE_APPLICATIONS_ALL.PAYMENT_SET_ID (ie. for the
receipt)3. AR_RECEIVABLE_APPLICATIONS_ALL (contains details for the
Receipt Application)
PAYMENT_SET_ID: Contains a value that must match the
payment_set_id of the invoice in ra_customer_trx_lines_all for an
automatic application to take placeAPPLICATION_REF_TYPE: Identifies
the application reference type and determines the context for the
APPLICATION_REF_ID and APPLICATION_REF_NUM columnsFor example: OM
(for Order Management)APPLICATION_REF_ID: Application reference
identifier whose context is determined by the APPLICATION_REF_TYPE
column's valueFor example: contains the order's
SO_HEADER_IDAPPLICATION_REF_NUM: User-visible application reference
number whose context is determined by the APPLICATION_REF_TYPE
column's valueFor example: contains the Order NumberAdditional
Information:In AR, underNavigation: Control > Requests, the
Prepayments Matching Program can be run separately if needed:There
are two parameters:1. Matching Source2. AutoInvoice Request id
