Results for “match_record_num”

16 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.EC_INBOUND_STAGE is a PL/SQL package body in the Oracle E-Business Suite (EBS) that supports the E-Commerce Gateway (ECE) inbound processing architecture. Its role is to receive, parse, and stage inbound electronic data interchange (EDI) and flat file transactions into the ECE interface and staging tables before those records are validated and processed by the ECE inbound processing programs. The package provides the foundational load, mapping, and record-matching logic on which document-specific inbound programs depend, converting delimited or fixed-position inbound file content into structured rows suitable for trading partner and transaction processing.

The package is owned by the APPS schema and is reported with a VALID status. It is a dependent object rather than a standalone entry point: it is referenced by several other ECE packages but is not referenced by any database object, indicating that it functions as an internal utility library within the E-Commerce Gateway inbound flow.

Key Procedures and Functions

  • LOAD_DATA — Orchestrates the loading of inbound data into the staging structures, driving the read and stage cycle for a given inbound run.
  • LOAD_DATA_FROM_FILE — Reads inbound file content, typically via UTL_FILE, and initiates processing of the records contained in the source flat file.
  • POPULATE_FLATFILE_MAPPING — Builds the mapping between the columns of the inbound flat file and the corresponding columns of the ECE interface and staging tables, based on the interface table and column definitions.
  • INSERT_INTO_STAGE_TABLE — Performs the physical insert of parsed inbound records into the ECE staging table, using dynamically constructed SQL where column layouts vary by document type.
  • MATCH_RECORD_NUM — Derives or matches record numbers used to identify and order records within an inbound transmission.
  • FIND_POS — Locates the position of fields within a delimited or positional flat file line, returning the offsets used to extract field values.
  • GET_TP_CODE — Resolves the trading partner code associated with an inbound record or run, supporting trading partner identification during staging.

Tables Accessed

The package reads configuration and mapping metadata from ECE_INTERFACE_TABLES and ECE_INTERFACE_COLUMNS, which define the target interface structure, and from ECE_EXTERNAL_LEVELS and ECE_LEVEL_MATRICES, which describe document levels and their relationships. Trading partner information is resolved through ECE_TP_HEADERS and ECE_TP_DETAILS. Staged records reference ECE_DOCUMENT_ID_S and ECE_STAGE_ID_S, the sequence generators for document and stage identifiers, while ECE_OUTPUT_RUNS_S supports run numbering. Validation and reference lookups draw on AP_BANK_BRANCHES, HZ_CUST_ACCT_SITES_ALL, and PO_VENDOR_SITES for bank, customer, and supplier site data. Utility access is provided through DUAL, DBMS_SQL for dynamic SQL, UTL_FILE for file input, and PLITBLM for string manipulation.

Usage Notes

EC_INBOUND_STAGE is not intended for direct invocation by end users. It is invoked indirectly through the E-Commerce Gateway inbound concurrent programs and their transaction-specific drivers during EDI and flat file inbound processing. Customizations that extend inbound document support, alter flat file layouts, or add new interface columns must respect the mapping logic implemented in this package, because the staging behavior is driven by the configuration held in the ECE interface and trading partner tables. Because the body is marked VALID and is referenced by multiple ECE packages, modifications should be limited to supported extension points or handled as a carefully versioned custom copy, consistent with Oracle EBS 12.1.1 and 12.2.2 patching and support practices.