An overview of Oracle Streams by Lewis CunninghamFull description
oracle
Description complète
ORACLE
Descripción: Oracle Forms By Oracle
Engine Info
Engine InfoFull description
Information om Sverige på lätt svenska
Descripción completa
Full description
problems tohelp in operations mgmt
Koné manual instruction
E-OmFull description
Koné manual instructionDescripción completa
tumorDeskripsi lengkap
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 Order ARPREMAT - Prepayments Matching Program ARXRWMAI - Receipts RAXTRX - Autoinvoice Import Program AR_PREPAYMENTS_PUB.Create_prepayment
PURPOSE
Starting from Financials Family Pack E Patch 2842697, 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. DETAILS
Process: The process for multiple prepayments is as follows: 1. Enter a new sales order from Order Management Responsibility: Responsibility: Order Management Super User Navigation: Navigation: Orders & Returns > Sales Orders (Form Name: OEXOEORD) 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 order 3. Navigation: Actions-button > Payments 4. Enter payment information Enable flag: prepay Note: You can enter multiple prepayments of different types at once as long as the following is set: Responsibility: Responsibility: Order Management Super User Navigation: Navigation: Setup > System Parameters Values > Payments Parameters
Set Allow multiple payments: YES
Also 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 Process Process deferred: Yes Process timeout: Yes 7. 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_number 2. 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 place APPLICATION_REF_TYPE: Identifies the application reference type and determines the context for the APPLICATION_REF_ID and APPLICATION_REF_NUM columns For example: OM (for Order Management) APPLICATION_REF_ID: Application reference identifier whose context is determined by the APPLICATION_REF_TYPE column's value For example: contains the order's SO_HEADER_ID APPLICATION_REF_NUM: User-visible application reference number whose context is determined by the APPLICATION_REF_TYPE column's value For example: contains the Order Number Additional Information: In AR, under Navigation: Control > Requests, the Prepayments Matching Program can be run separately if needed: There are two parameters: 1. Matching Source 2. AutoInvoice Request id
