Search Results ece_tp_details

Overview

The ECE_TP_DETAILS table is a core data object within the Oracle E-Business Suite e-Commerce Gateway (EC) module. It functions as the central repository for defining and storing the detailed processing rules associated with specific trading partners. In the context of B2B electronic data interchange (EDI), these rules govern how inbound and outbound transaction documents, such as purchase orders or invoices, are parsed, validated, transformed, and routed. The table works in conjunction with the ECE_TP_HEADERS table, forming a parent-child relationship where the header defines the general trading partner setup and the details define the specific, actionable instructions for each transaction type or document standard.

Key Information Stored

The table's primary purpose is to map trading partner transactions to specific E-Commerce Gateway processing components. Its key columns include the surrogate primary key TP_DETAIL_ID and the foreign key TP_HEADER_ID, which links each rule to a parent record in ECE_TP_HEADERS. Other critical columns define the processing workflow: TRANSACTION_TYPE typically identifies the business document (e.g., 850 for a PO), STANDARD_CODE specifies the EDI standard (e.g., X12 or EDIFACT), and VERSION_CODE indicates the standard's version. The table stores references to the application engine programs, maps, and functions responsible for translation, validation, and extraction (columns like EXTRACT_PROGRAM, VALIDATE_PROGRAM, TRANSLATE_PROGRAM). Direction flags indicate whether the rule applies to inbound or outbound processing, enabling the system to apply the correct logic based on document flow.

Common Use Cases and Queries

This table is primarily accessed for configuration, troubleshooting, and auditing trading partner setups. A common operational query involves listing all processing rules for a specific trading partner to verify setup completeness.

• Sample Query: Rules for a Trading Partner
  SELECT etd.transaction_type, etd.standard_code, etd.direction
FROM ece_tp_details etd, ece_tp_headers eth
WHERE eth.tp_header_id = etd.tp_header_id
AND eth.tp_code = 'TRADING_PARTNER_ABC';
• Use Case: Integration Debugging: When an inbound EDI document fails, support personnel query this table using the transaction type and standard to identify the assigned validation or translation program for debugging.
• Use Case: Implementation Reporting: Implementation teams run summary reports to document all configured EDI transactions across partners, often joining with ECE_TP_HEADERS to include the partner name.

Related Objects

The ECE_TP_DETAILS table has a direct, integral relationship with several other e-Commerce Gateway objects. Its primary foreign key constraint links it to ECE_TP_HEADERS (TP_HEADER_ID), establishing the core header-detail model. The processing programs (e.g., EXTRACT_PROGRAM) referenced in its columns are typically Application Engine programs or custom functions defined within the EC module. The table is also fundamentally related to the transaction maps and translation engines that execute the rules it defines. While not a direct foreign key, the data in ECE_TP_DETAILS drives the runtime behavior of the E-Commerce Gateway's inbound and outbound processing engines, which populate interface tables like ECE_PROCESSED_MSGS for logging.