Search Results populate_plsql_tbl_with_extval
Overview
ECX_CODE_CONVERSION_PVT is a private PL/SQL package in the APPS schema that underpins Oracle E-Business Suite's XML Gateway code-conversion infrastructure. Its principal business function is to translate values between an external trading-partner representation and the internal Oracle EBS representation, using the cross-reference definitions held in the ECX (e-Commerce XML) reference tables. External partners transmit or expect codes such as unit-of-measure codes, currency codes, and other semantics that differ from internal EBS codes; this package resolves those differences during inbound and outbound XML message processing.
The package is declared with AUTHID CURRENT_USER and carries a set of global constants that reveal its design lineage and validation contract. Error and status constants (G_NO_ERRORS, G_INVALID_PARAMETER, G_UNEXP_ERROR, G_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXP_ERROR) follow the standard EBS API return-status convention. Missing-value sentinels (G_MISS_NUM, G_MISS_CHAR, G_MISS_DATE) are explicitly noted as "taken from the FND_API for the Standalone Version," indicating the package was originally written to run outside a full EBS schema context. The validation-level constants G_VALID_LEVEL_NONE (0) and G_VALID_LEVEL_FULL (100) define the granularity of validation applied during conversion.
Key Procedures and Functions
The ETRM metadata documents four entry points:
- POPULATE_PLSQL_TBL_WITH_EXTVAL — Populates an in-memory PL/SQL table with external values, accepting parameters that include an API version number, initialization and simulation flags, a commit flag, a validation level defaulting to
G_VALID_LEVEL_FULL, a standard identifier, standard API OUT parameters (p_return_status,p_msg_count,p_msg_data), a level indicator, a DTD node table (ecx_utils.dtd_node_tbl), and a trading-partner identifier. It is used to stage external-representation values for subsequent conversion. - POPULATE_PLSQL_TBL_WITH_INTVAL — The internal-representation counterpart, following the same parameter conventions and also defaulting
p_validation_leveltoG_VALID_LEVEL_FULL. It stages internal values for outbound translation. - CONVERT_EXTERNAL_VALUE — Performs the actual conversion of an incoming external value to its internal equivalent, resolving the cross-reference and returning the mapped value.
- CONVERT_EXTERNAL_VALUE_JAVA — A Java-callable variant of the conversion routine, exposed for invocation from Java-based XML Gateway processing agents.
The G_VALID_LEVEL_FULL constant (value 100) is the default validation level for both populate procedures, meaning callers receive full validation unless they explicitly lower it.
Tables Accessed
- ECX_STANDARDS — Defines the XML standards (for example, the transaction standard and version) against which cross-references are scoped.
- ECX_XREF_STANDARDS — Links cross-reference definitions to specific standards.
- ECX_XREF_DTL — Holds the detail rows that map external code values to internal code values; this is the primary source read during conversion.
- PLITBLM — The index-by table of VARCHAR2, used as a temporary staging structure for value lists.
These accesses are performed through APPS synonyms, consistent with the package's deployment in the APPS schema.
Usage Notes
Because this is a PVT (private) package, it is not part of the public EBS API surface. It is referenced by three other packages and is invoked indirectly by the XML Gateway runtime when transforming inbound and outbound messages. The default p_validation_level of G_VALID_LEVEL_FULL reflects the intended high-integrity path for standard processing, while G_VALID_LEVEL_NONE supports performance-oriented or pre-validated bulk scenarios. Custom integrators should not call this package directly; instead, they should configure cross-references through the standard XML Gateway setup and rely on the supported conversion path. Direct invocation is appropriate only for diagnostic or advanced extension work where the caller fully understands the staging tables and return-status contract.
-
PACKAGE: APPS.ECX_CODE_CONVERSION_PVT
12.1.1
-
PACKAGE: APPS.ECX_CODE_CONVERSION_PVT
12.2.2
-
PACKAGE: APPS.EC_CODE_CONVERSION_PVT
12.1.1
-
PACKAGE: APPS.EC_CODE_CONVERSION_PVT
12.2.2
-
PACKAGE BODY: APPS.ECX_CODE_CONVERSION_PVT
12.1.1
-
PACKAGE BODY: APPS.ECX_CODE_CONVERSION_PVT
12.2.2
-
PACKAGE BODY: APPS.EC_CODE_CONVERSION_PVT
12.2.2
-
PACKAGE BODY: APPS.EC_CODE_CONVERSION_PVT
12.1.1
-
APPS.EC_CODE_CONVERSION_PVT dependencies on ECE_FLATFILE_PVT
12.1.1
-
APPS.EC_CODE_CONVERSION_PVT dependencies on ECE_FLATFILE_PVT
12.2.2
-
APPS.EC_CODE_CONVERSION_PVT dependencies on FND_API
12.2.2
-
APPS.EC_CODE_CONVERSION_PVT dependencies on FND_API
12.1.1
-
APPS.EC_CODE_CONVERSION_PVT dependencies on FND_API
12.1.1
-
APPS.EC_CODE_CONVERSION_PVT dependencies on ECE_FLATFILE_PVT
12.2.2
-
APPS.EC_CODE_CONVERSION_PVT dependencies on FND_API
12.2.2
-
APPS.EC_CODE_CONVERSION_PVT dependencies on ECE_FLATFILE_PVT
12.1.1
-
APPS.ECX_CODE_CONVERSION_PVT dependencies on ECX_CODE_CONVERSION_PVT
12.1.1
-
APPS.ECX_CODE_CONVERSION_PVT dependencies on ECX_DEBUG
12.2.2
-
APPS.ECX_CODE_CONVERSION_PVT dependencies on ECX_DEBUG
12.1.1
-
APPS.ECX_CODE_CONVERSION_PVT dependencies on ECX_CODE_CONVERSION_PVT
12.2.2
-
APPS.EC_CODE_CONVERSION_PVT dependencies on FND_MSG_PUB
12.1.1
-
APPS.EC_CODE_CONVERSION_PVT dependencies on EC_UTILS
12.2.2
-
APPS.EC_CODE_CONVERSION_PVT dependencies on FND_MSG_PUB
12.2.2
-
APPS.EC_CODE_CONVERSION_PVT dependencies on EC_UTILS
12.1.1