Search Results igcpoyee_xml

Overview

The concurrent program identified by the short name IGCPOYEE_XML belongs to the Oracle E-Business Suite product family IGC – Contract Commitment, the module historically associated with the government contracting extension of Oracle Purchasing and the Contracts Core architecture. Its documented title is Purchasing Year End Exception Report (XML) – Not Supported: Reserved For Future Use, with the corresponding description Purchasing Year End Exception Report. The purpose implied by the name is the identification and reporting of purchasing transactions that fail year-end processing rules — that is, commitments, obligations, or encumbrances that cannot be carried forward or closed cleanly at fiscal period end and therefore require exception handling by the buying organization.

The critical documented fact is that this program is not enabled. The ETRM metadata explicitly records Enabled: No and appends the qualifier Not Supported: Reserved For Future Use to the user-facing name. It therefore cannot be submitted successfully in a supported EBS 12.1.1 or 12.2.2 environment, and any reference to it in a runnable-request context should be treated as an artifact of the underlying data model rather than an operational report.

Execution Details

The documented execution method is Java Concurrent Program, meaning the program is designed to be launched by the Oracle concurrent manager through the Java Concurrent Program (JCP) framework rather than the traditional Oracle Reports or PL/SQL stored procedure path. The argument method is documented as Standard, indicating that parameters, where defined, are passed using the conventional concurrent program argument convention rather than a token-substitution or multi-token scheme.

Neither the Executable nor the Execution File is populated in the ETRM 12.2.2 metadata. This absence is consistent with the disabled status: because the program is reserved for future use, no executable registration has been completed. In an actual 12.1.1 or 12.2.2 instance, the corresponding executable would typically reside under the application top associated with the IGC product and would be invoked through the JCP classpath, but no such registration is documented here.

How to Run

Under normal EBS operation, a concurrent program of this class would be submitted from the Submit Request (SRS) window, either directly by name or through a responsibility-specific request group. Because IGCPOYEE_XML is disabled, it will not appear in the list of values for standard submission, and any attempt to invoke it programmatically through FND_REQUEST.SUBMIT_REQUEST would return a failure or zero request identifier.

Where year-end purchasing exception reporting is required in a supported configuration, users should rely on the enabled successor programs delivered for the Procurement and Contract Commitment modules. Parameter guidance for those programs generally centers on the operating unit, the fiscal year or accounting period range, and the transaction or commitment type filter. No parameter list is documented for IGCPOYEE_XML itself.

Related Objects

The program is conceptually adjacent to the standard purchasing and commitment objects that support year-end processing. These include the purchasing interface and commitment interface tables used by Purchasing and Contract Commitment, the encumbrance and funds-check APIs, and the enabled Purchasing year-end and period-close exception reports delivered in the Procurement family. Because the object is reserved for future use, no interface table or API is documented as being bound to it, and it should not be referenced in custom concurrent request groups, request sets, or scheduling definitions.