Академический Документы
Профессиональный Документы
Культура Документы
Current schedule
Archived recordings
Doc ID 740966.1
Teleconference Access:
Password: Oracle OM
OM Webcast Calendar/Archive
Doc ID 1288737.1
Setups
Payment Processing
Types of Payments
Goods
Payments
Pre Payments
Why they are Used Auto invoice creation
and receipt matching
Invoice
Setups
Payment Processing
Setups
Payment Processing
Payment Type Level Cash Check Credit Card ACH Direct Debit Wire transfer Commitment
Header X X
Pre Payment
Line X X X X X X X
X
Header X
Payment
Line
Enter View/Print
Prepayments/ Process Receipts
Payment terms of Payments (Optional)
type prepayment
Auto
Fulfill Order
invoice/Automatic
Receipt Matching
Cancel Sales
order
Note: The Print Payment Receipt action is available only if the function Sales Orders: Print Payment
Receipt is attached to the OM Menu
Setups
Payment Processing
Enter a new sales order from Order Management and Book the Order
Actions Payments
View Receipt
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.
Actions payments
Setups
Payment Processing
This is a multi-org table for payment records open interface. This table
stores payment information that is imported from a feeder system into
Oracle Order Management using Order Import
Sample code
--Payment related changes START
l_Header_Payment_tbl(1) := OE_ORDER_PUB.G_MISS_HEADER_PAYMENT_REC;
l_Header_Payment_tbl(1).operation := OE_GLOBALS.G_OPR_CREATE;
l_Header_Payment_tbl(1).PAYMENT_TYPE_CODE :='CASH';
l_Header_Payment_tbl(1).RECEIPT_METHOD_ID := 1102;
--Payment related changes END
Similarly the Line payments table can be populated for Line Level payment
l_Header_Payment_tbl(1).PAYMENT_NUMBER :=1;
l_Header_Payment_tbl(1).PAYMENT_COLLECTION_EVENT := 'PREPAY';
l_Header_Payment_tbl(1).PAYMENT_TYPE_CODE := 'CREDIT_CARD';
l_Header_Payment_tbl(1).CREDIT_CARD_CODE :='VISA';
l_Header_Payment_tbl(1).CREDIT_CARD_EXPIRATION_DATE :='12-DEC-2015';
l_Header_Payment_tbl(1).CREDIT_CARD_HOLDER_NAME :='test';
l_Header_Payment_tbl(1).CREDIT_CARD_NUMBER :='111111111111';
l_Header_Payment_tbl(1).payment_amount :=100;
Setups
Payment Processing
Create Prepayment: The document sequence number was used to default the receipt number.
Payment processing for 1.08 failed.
A payment failure hold has been applied against this order.
Order has been booked.
Resolution
Receivables responsibility, Navigation path = Setup > Receipts > Receivables Activities
Resolution
Ans:
create Sales Order by entering payment details, so that the trxn_extension_id will be passed to
Receivables during invoicing.
Enhancement Request Bug 7334362 is logged to default the payment details when the customer
has payment method and primary bank account attached.
Ans:
This observation is standard functionality at this point.The Payments option is not available to be
selected from the "Actions" button LOV in the Order Organizer form.
Ans:
The Payment Type LOV at the Order level is there only for backward compatibility, and meant for customers who
have Multiple Payments disabled. The users will not be able to make use of the new Payment Types enabled in
11.5.10 for Multiple Payments using the Payment Type LOV at the Order Level.
The new Payment Types enabled for Multiple Payments require additional information to be captured. That is the
reason why we need users to use the Payment window to capture the relevant information
Doc Id 740966.1