Search Results validate_pon_emd_fin

Overview

APPS.PON_EMD_AR_INTEGRATION_GRP is a PL/SQL group (GRP) package body in Oracle EBS Release 12.1.1 and 12.2.2 that encapsulates the integration between Oracle Purchasing sourcing/negotiation (PON) and Oracle Receivables (AR). Its central business purpose is to manage Earnest Money Deposit (EMD) processing for auctions and sourcing events. EMD represents a bidder's good-faith deposit, and the package provides the API layer that converts EMD entries held on the purchasing side into financial instruments on the receivables side. It creates deposits, receipts, credit memos, customer accounts, and applies or unapplies receipts against deposit transactions, and supports refund and forfeiture accounting. The package is identified in the ETRM metadata as an "API classification: GRP" object, with twenty-six documented procedures/functions. It is a wrapper over standard AR APIs, so callers interact with AR via this single, controlled entry point rather than directly. The header comment attributes revision control to PONGARIB.pls with a ship filename and version timestamp of 2013/02/09, confirming its role as a long-lived integration artifact in the EBS code line.

Key Procedures and Functions

• CREATE_EMD_DEPOSIT — Wrapper over AR APIs to create an EMD deposit; accepts deposit input and returns deposit output with a return status.
• CREATE_EMD_RECEIPT_AND_APPLY — Creates an EMD receipt and applies it to the appropriate transaction.
• UNAPPLY_EMD_RECEIPT — Reverses an existing receipt application when an EMD must be released.
• REFUND_ACTIVITY_ON_EMD_RECEIPT — Handles refund activity associated with an EMD receipt.
• CREATE_CM_ON_EMD_DEPOSIT — Creates a credit memo against an EMD deposit.
• CREATE_CUST_ACCOUNT — Creates a customer account for the bidder/supplier when none exists.
• CREATE_CUST_ACC_SITE_AND_USAGE — Creates the customer account site and site use required for AR processing.
• GET_CUSTOMER_INFO — Retrieves customer information for EMD processing.
• GET_BANK_INFO — Retrieves bank information used for receipt/deposit creation.
• GET_CREDIT_CARD_INFO — Retrieves credit card information for card-based EMD transactions.
• GETTRXINFOFROMPARENTTRX — Derives transaction information from a parent transaction.
• GETRECEIPTINFOOFPARENTTRX — Derives receipt information from a parent transaction.
• VALIDATE_TRX_INFO — Validates transaction details before processing.
• VALIDATE_PON_EMD_FIN — The validation routine matching the user's search term; validates PON EMD financial data prior to AR integration.
• VALIDATE_TRX_PAYMENT_TYPE_INFO — Validates transaction payment type information.
• VERIFY_FINANCE_INSTALLATION — Confirms that required financial modules are installed and available.
• POST_EMD_DEPOSIT_TRANSACTIONS / POST_EMD_REFUND_TRANSACTIONS / POST_EMD_FORFEIT_TRANSACTIONS — Post deposit, refund, and forfeiture accounting transactions respectively.
• PROCESS_EMD_FORFEIT_TRANS… — Processes forfeiture of an EMD when a bidder defaults.

Tables Accessed

The package reads and writes through APPS synonyms. AR tables — AR_CASH_RECEIPTS, AR_PAYMENT_SCHEDULES, AR_RECEIPT_METHODS, and AR_RECEIVABLE_APPLICATIONS — support receipt creation, application, and unapplication. Customer data comes from the TCA model: HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES, which are required when a bidder has no existing customer record. AP tables AP_INVOICES, AP_SUPPLIERS, AP_SUPPLIER_CONTACTS, and AP_SUPPLIER_SITES supply supplier and payee information. PON_AUCTION_HEADERS_ALL ties the financial processing back to the originating auction/sourcing event.

Usage Notes

PON_EMD_AR_INTEGRATION_GRP is invoked from the Oracle Purchasing/ Sourcing EMD flow — typically through concurrent programs or fulfillment logic that must post EMD financials into AR — and may be called from custom PL/SQL, forms, or OAF pages. Callers should supply the API version, initialization message list, and commit flags, and must inspect the returned status (SUCCESS/ERROR) before proceeding. Because it wraps AR APIs, all validations (including VALIDATE_PON_EMD_FIN) should be executed before financial calls. The metadata records no other packages referencing it, so it functions as a top-level integration entry point.