Search Results refund_activity_on_emd_receipt

Overview

PON_EMD_AR_INTEGRATION_GRP is an Oracle EBS PL/SQL package that resides in the APPS schema and is classified as an API group (GRP). Its business purpose is to integrate the Earnest Money Deposit (EMD) functionality of Oracle Sourcing and Procurement with the Oracle Receivables (AR) and Oracle Payables (AP) sub-ledgers. In public-sector and regulated procurement environments, buyers collect EMDs from bidding parties as a good-faith guarantee against auction participation. The package automates the financial lifecycle of those deposits — receipt creation, application against receivables transactions, refunds, credit memo generation, and forfeiture posting — without requiring manual data entry in the Receivables or Payables forms.

The package also manages the customer and supplier master data needed to transact these deposits. Because bidding parties may exist only as trading partners (HZ_PARTIES) rather than as fully defined AR customers, PON_EMD_AR_INTEGRATION_GRP can create customer accounts, sites, and site uses on demand so that deposits and refunds can be processed through standard Receivables flows.

Key Procedures and Functions

The documented API surface includes 26 procedures and functions. The principal routines are grouped below.

• CREATE_EMD_DEPOSIT — Creates the EMD deposit transaction, establishing the receivable against the bidding party.
• CREATE_EMD_RECEIPT_AND_APPLY — Creates an AR cash receipt and applies it to the EMD-related transaction.
• UNAPPLY_EMD_RECEIPT — Reverses an existing receipt application, typically before refund or forfeiture.
• REFUND_ACTIVITY_ON_EMD_RECEIPT — Processes refund activity against a previously recorded EMD receipt.
• CREATE_CM_ON_EMD_DEPOSIT — Generates a credit memo associated with an EMD deposit.
• CREATE_CUST_ACCOUNT, CREATE_CUST_ACC_SITE_AND_USAGE — Create the Receivables customer account, site, and site usage records required for deposit transactions.
• GET_CUSTOMER_INFO, GET_BANK_INFO, GET_CREDIT_CARD_INFO — Retrieval functions returning party, bank, and credit card attributes used to build receipts.
• GETTRXINFOFROMPARENTTRX, GETRECEIPTINFOOFPARENTTRX — Retrieve transaction and receipt detail from a parent (source) transaction for downstream processing.
• VALIDATE_TRX_INFO, VALIDATE_PON_EMD_FIN, VALIDATE_TRX_PAYMENT_TYPE_INFO, VERIFY_FINANCE_INSTALLATION — Validation routines that confirm setup completeness, payment type consistency, and Oracle Financials installation status before transactions post.
• POST_EMD_DEPOSIT_TRANSACTIONS, POST_EMD_REFUND_TRANSACTIONS, POST_EMD_FORFEIT_TRANSACTIONS, PROCESS_EMD_FORFEIT_TRANS — Posting routines that push deposit, refund, and forfeiture activity into the AR and AP sub-ledgers.

Tables Accessed

The package reads and writes Oracle Sourcing tables including PON_AUCTION_HEADERS_ALL, PON_BIDDING_PARTIES, PON_EMD_TRANSACTIONS, PON_EMD_FIN_PARAMETERS_ALL, and PON_EMD_PAYMENT_TYPES_ALL, which hold auction, bidder, deposit, parameter, and payment-type data. It interacts with Receivables objects such as AR_CASH_RECEIPTS, AR_PAYMENT_SCHEDULES, AR_RECEIPT_METHODS, AR_RECEIVABLE_APPLICATIONS, RA_BATCH_SOURCES, RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, and RA_CUST_TRX_TYPES. Supplier data is drawn from AP_INVOICES, AP_SUPPLIERS, AP_SUPPLIER_CONTACTS, and AP_SUPPLIER_SITES. TCA/party master data is accessed through HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. Profile values are retrieved via FND_PROFILE.

Usage Notes

PON_EMD_AR_INTEGRATION_GRP is invoked internally by Oracle Sourcing EMD processes, typically triggered from the Sourcing auction and EMD setup pages or from concurrent programs that post deposit, refund, and forfeiture activity. It is not intended for direct end-user execution. Customizations should call the documented procedures rather than insert into the underlying PON_EMD and AR tables, since the package enforces validation, profile checks, and sub-ledger posting logic. The package is referenced by no other database packages and is self-referenced, indicating it operates as a top-level integration API group rather than a library consumed by other PL/SQL units.