Search Results gen_xml_corpt_str_list

Overview

IEX_STRATEGY_DIAG_REPORT is an Oracle EBS Advanced Collections (IEX) diagnostic utility package owned by the APPS schema and classified under the "OTHER" API category. Its purpose is to generate an XML-formatted diagnostic report that describes the configuration and runtime state of a collections strategy, including its associated work items, delinquency context, and resource assignments. The header comment identifies the package as the "strategy diagnostic report" generator. The package is compiled with AUTHID CURRENT_USER, meaning its unqualified object references resolve against the privileges of the invoking user rather than the definer. The $Header line records version 120.2 dated 2010/10/04, consistent with EBS 12.1.1 and 12.2.2 code lines. The package is self-contained: it is referenced by zero other packages, so it is intended as an entry-point utility rather than a reusable library. It is not a business transaction API; it does not create, update, or delete collections strategy data. Its sole documented output path is the emission of XML fragments and the printing of CLOB content, making it a read-only reporting instrument used for troubleshooting strategy setup and work item generation.

Key Procedures and Functions

Eleven documented procedures and functions make up the public interface. GEN_XML_HEADER_DATA_STRATEGY emits the opening portion of the XML document describing a strategy. GEN_XML_BODY_STRATEGY produces the body of the report for a given strategy, optionally accepting a strategy record and a status value. GEN_XML_APPEND_CLOSETAG_STY writes the closing tags that terminate the strategy section of the XML — the identifier most commonly associated with this package in searches. GEN_XML_CORPT_STR_LIST generates the corporate strategy listing. GEN_XML_BODY_WI and GEN_XML_BODY_AUTO_WI render the body sections for work item templates and automatic work items respectively. MAIN is the driving entry point; it exposes the standard concurrent-program signature of error buffer and return code out parameters. Formatting and utility support is provided by FORMAT_STRING, which normalizes string values, PRINT_CLOB, which writes CLOB content to the output, and WRITELOG, which records a message in the log. GET_RESOURCE determines the resource identifier and name associated with a strategy record and work item template. Several package-level variables — l_StrategyLevelName, l_DefaultTempName, and l_SourceName — hold descriptive attributes used during report assembly. No parameter lists beyond those documented above should be assumed.

Tables Accessed

The package reads configuration and transactional data through APPS synonyms. Strategy definition data comes from IEX_STRATEGIES, IEX_STRATEGY_TEMPLATES_TL, IEX_STRY_TEMP_WORK_ITEMS_B, and IEX_STRATEGY_WORK_TEMP_XREF. Work item and skill assignments are drawn from IEX_STRATEGY_WORK_ITEMS and IEX_STRATEGY_WORK_SKILLS. Delinquency and dunning context is obtained from IEX_DELINQUENCIES_ALL and IEX_DUNNINGS, with receivables exposure from AR_PAYMENT_SCHEDULES_ALL. Customer information is sourced from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES. Resource assignments and agent details come from JTF_RS_RESOURCE_EXTNS, whose data GET_RESOURCE resolves. Application-level configuration is referenced through IEX_APP_PREFERENCES_B. All access is documented as read-only for reporting purposes.

Usage Notes

IEX_STRATEGY_DIAG_REPORT is invoked as a diagnostic concurrent program, typically from the Collections responsibility when strategy behavior or work item generation produces unexpected output. MAIN supplies the ERRBUF/RETCODE interface required by the concurrent manager. The XML fragments written by the gen_xml_* procedures, in combination with PRINT_CLOB, form the report output consumed by the user. Because the package is referenced by no other package and carries an OTHER classification, it should not be called from custom business logic as a stable API. Its interface may change between releases. The presence of the gen_xml_append_closetag_sty procedure in the specification explains why users searching for that name land on this package: it is a private report-assembly routine, not a callable business service.