Search Results log_list_status_iec_error
Overview
IEC_OCS_LOG_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle E-Commerce/TeleSales (IEC) product family. The suffix _PVT designates it as a private package: it is not exposed as a public API for customer extension and is intended for internal consumption by other packages within the IEC application layer. Its principal business function is centralized message and error logging for the IEC On-Line Catalog Store (OCS) subsystems — subset generation, territory validation, source-type resolution, status processing, and record filtering.
The package encapsulates a library of message-formatting routines that produce consistent, user-facing and diagnostically useful text for conditions encountered during processing. Rather than each IEC package embedding its own literal error strings, callers invoke IEC_OCS_LOG_PVT to obtain standardized messages and to write them to the logging destination. The ETRM metadata records the object as VALID in both 12.1.1 and 12.2.2, confirming that it is a supported, compiled component of the runtime codebase.
Key Procedures and Functions
ETRM documents 35 program units within the package. The documented routines fall into several related groups.
- Logging and message output: LOG_MESSAGE, LOG_INTERNAL_PLSQL_ERROR, LOG_LOCATE_LIST_DATA_ERROR, LOG_LIST_STATUS_IEC_ERROR, LOG_LIST_STATUS_AMS_ERROR, and LOG_RECYCLE_MV_DUP_REC_STMT. These emit messages to the package's logging target, specialise in surfacing Oracle internal PL/SQL exceptions, and record conditions arising from list and territory status processing, Oracle Marketing (AMS) status errors, and duplicate records detected during materialized view recycling.
- Encoded message access: GET_ENCODEDMESSAGE returns a pre-encoded message string keyed by an internal message identifier, allowing callers to avoid hard-coding text.
- Module identification: GET_MODULE returns the current module name for inclusion in log output, supporting traceability of which IEC component raised a message.
- Initialisation of standard messages: A family of INIT_* routines builds or caches canned error text, including INIT_GETSUBSETVIEWERRORMSG, INIT_NOENTRIESFOUNDMSG, INIT_SOURCETYPEDOESNOTEXISTMSG, INIT_SOURCETYPEMISMATCHALLMSG, INIT_SOURCETYPEMISMATCHSOMEMSG, INIT_SOURCETYPEMISSINGCOLSMSG, INIT_SOURCETYPENOTSUPPORTEDMSG, INIT_SQLERRMMSG, INIT_STATUSUPDATEERRORMSG, INIT_SUBSETVIEWDOESNOTEXISTMSG, INIT_TERRITORYNOTFOUNDMSG, and INIT_TERRITORYNOTUNIQUEMSG. Collectively these cover missing or mismatched source types, absent or invalid subset views, empty result sets, SQL error text, status-update failures, and territory lookup problems.
No parameter lists are reproduced here, as they are not part of the documented metadata.
Tables Accessed
The ETRM excerpt lists no directly referenced tables; the package's dependency section shows references only to SYS.STANDARD and the PL/SQL STANDARD package. This is consistent with a logging utility whose persistence is delegated to invoking packages, or which writes exclusively to file, log tables owned elsewhere, or the database alert/debug output. Any table access occurs through APPS synonyms in the caller rather than directly within IEC_OCS_LOG_PVT.
Usage Notes
IEC_OCS_LOG_PVT is referenced by nine other packages: IEC_COMMON_UTIL_PVT, IEC_CPN_RLSE_STTGY_PVT, IEC_IH_HLPR_PVT, IEC_OCS_LOG_PVT itself, IEC_RECORD_FILTER_PVT, IEC_RECOVER_PVT, IEC_REPORTS_PVT, IEC_STATUS_PVT, IEC_SUBSET_PVT, and IEC_VALIDATE_PVT. It is therefore invoked indirectly whenever those packages run — typically during concurrent program execution for subset generation and validation, territory and source-type setup forms, campaign release strategy processing, and report generation. Custom code should not call this private package directly; the supported integration surface lies in the public IEC APIs. Because the package is private and its signatures are undocumented externally, any direct dependency risks breakage during patching or upgrade between 12.1.1 and 12.2.2.