Search Results get_token_display_field




Overview
Explore in AI Chat

Overview

APPS.AP_XML_INVOICE_INBOUND_PKG is a PL/SQL package body in the Oracle E-Business Suite Payables (AP) module that supports the inbound processing of supplier invoices delivered as XML or electronic business messages. Within the Oracle EBS 12.1.1 and 12.2.2 releases, this package operates as part of the Payables open interface and the P2P (Procure-to-Pay) supplier collaboration infrastructure, orchestrating error handling, supplier notification, and validation logic that surrounds the loading of invoices into the AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables.

Its primary business function is to manage the lifecycle of inbound invoice messages after they have been transformed but before they are finally imported into the base Payables tables. The package coordinates rejection tracking, tax determination, charge type correction, and outbound notification to suppliers and internal recipients when an inbound document succeeds or fails. The presence of AP_P2P_INBOUND_NOTIFICATION_S as a referenced table confirms that the package is tightly integrated with the Oracle P2P inbound notification framework used for supplier-facing communications.

Key Procedures and Functions

The documented package exposes twelve procedures and functions, classified as OTHER. Their purposes are summarized below based on ETRM metadata.

  • GET_TOKEN_DISPLAY_FIELD — retrieves a display field value derived from a token, typically used to build user-facing messages or template content for notifications.
  • START_OPEN_INTERFACE — initiates the open interface processing step for the inbound invoice record.
  • SEND_EMAIL — dispatches an email message as part of the notification workflow.
  • NOTIFY_SUPPLIER — sends a notification to the supplier regarding the inbound invoice result or rejection.
  • NOTIFY_RECIPIENT — sends a notification to an internal recipient (such as a buyer or Payables user) regarding the inbound document.
  • CHANGE_CASE — performs case (upper/lower) conversion on string data during inbound processing.
  • DERIVE_ORG_ID — derives the operating unit/organization identifier for the inbound invoice.
  • DERIVE_VENDOR_ID — derives the supplier identifier associated with the inbound invoice.
  • DERIVE_EMAIL_ADDRESS — resolves the email address to be used for supplier or recipient notification.
  • AFTER_MAP — executes post-mapping logic after the inbound payload has been transformed into interface columns.
  • SET_TAXABLE_FLAG2 — sets the taxable flag on invoice lines, working in conjunction with tax utility routines.
  • CORRECT_CHARGE_TYPE — validates and corrects the charge type assigned to invoice distributions.

Tables Accessed

The package reads and writes a defined set of interface and configuration tables via APPS synonyms.

  • AP_INTERFACE_REJECTIONS — records rejection reasons when an inbound invoice or line fails validation.
  • AP_INVOICES_INTERFACE — stores the header-level inbound invoice data being processed.
  • AP_INVOICE_LINES_INTERFACE — stores line-level inbound invoice data.
  • AP_P2P_INBOUND_NOTIFICATION_S — supports the P2P inbound notification framework invoked by the user's search.
  • AP_SYSTEM_PARAMETERS_ALL and FINANCIALS_SYSTEM_PARAMS_ALL — supply Payables and Financials setup options used during derivation and validation.
  • FND_CONCURRENT_REQUESTS / FND_CONC_REQ_SUMMARY_V — checked for concurrent request status and submission context.
  • PO_HEADERS_ALL and PO_VENDOR_SITES_ALL — used to resolve purchase order and supplier site information.
  • DUAL and PLITBLM — utility tables used for standard PL/SQL constructs and bulk processing.

Usage Notes

AP_XML_INVOICE_INBOUND_PKG is typically invoked indirectly rather than directly by end users. It is called from Payables XML inbound processing flows, the Payables Open Interface concurrent program family, and the P2P supplier collaboration notification processes. Because it references WF_ENGINE and WF_DIRECTORY, some notification paths may also be triggered through Oracle Workflow. The package is not referenced by any other database object per the ETRM dependency metadata, indicating it acts as a top-level orchestrator. Custom code should not modify this package; extensions should be implemented through supported interfaces such as the Payables open interface tables, Workflow business events, or the P2P notification APIs. Debugging output is written through AP_DEBUG_PKG and FND_LOG, so DBMS_OUTPUT or FND log review is required when troubleshooting.