Search Results admp_ins_eap_eitpi

Overview

IGR_GEN_001 is a general-purpose PL/SQL package owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its classification in the ETRM repository is "OTHER," indicating that it is a supporting utility package rather than a public, fully versioned Open Interface or API. The package resides within the IGR (Oracle Grants/Sponsored Projects) product family and, more specifically, supports the E-Business Tax Partner (EAP) / party registration data flows associated with the IGR person-identifier structures.

The package exposes only three documented program units, all of which are administrative in nature: ADMP_UPD_EAP_AVAIL, ADMP_DEL_EAP_EITPI, and ADMP_INS_EAP_EITPI. Although titled a "GEN" (general) package, its actual footprint is narrow and is limited to maintaining mappings between EAP availability records and person-identifier party information. It references the IGR_I_INFO_TYPES_V view within the APPS schema and depends on standard SYS constructs. Within the dependency graph it is referenced by a single other object, IGR_GEN_001 itself (i.e., the body references the specification), and it is referenced by IGR_I_A_ITYPE_PKG, reinforcing its role as a helper layer beneath the applicant type/party infrastructure.

Key Procedures and Functions

The three documented program units serve distinct administrative operations against the EAP/EITPI mapping data:

• ADMP_UPD_EAP_AVAIL — Updates EAP availability information. It is the maintenance routine used to refresh or adjust the availability values associated with EAP records so that downstream eligibility and applicant-type processing reflect the current state.
• ADMP_DEL_EAP_EITPI — Deletes an EAP-to-EITPI association. EITPI denotes the party identifier/type-party-identifier relationship, and this routine removes the mapping when it is no longer valid.
• ADMP_INS_EAP_EITPI — Inserts a new EAP-to-EITPI association. It is the complement of the delete routine and is used to establish the linkage when a new relationship is created.

No parameter lists or signatures are documented in the ETRM metadata, and none are inferred here. The naming convention (ADMP_ prefix) is consistent with administrative maintenance procedures used internally by the IGR grants product.

Tables Accessed

The package accesses the following objects through APPS synonyms:

• AMS_DELIV_KIT_ITEMS — Marketing delivery kit item data, read in the context of EAP availability processing.
• IGR_I_APPL_ALL — The applicant (applicant type) base table, which holds the applicant records to which the EAP/EITPI mappings apply.
• IGR_I_A_ITYPE — Applicant type definition data, referenced to identify the type context of each applicant.
• IGR_I_A_PKGITM — Applicant package item data, consulted during availability updates.
• IGS_PE_PERSID_GROUP_ALL — Person identification group definitions, part of the party/identifier model.
• IGS_PE_PERSID_GROUP_GP_ID_S — The sequence used to generate group identifiers.
• IGS_PE_PRSID_GRP_SEC — Person identifier group security records, used to enforce identifier group security.
• DUAL — Used for singleton queries and PL/SQL control operations.

Additionally, IGR_I_INFO_TYPES_V is referenced as a view dependency. Collectively, these objects confirm that the package operates at the intersection of applicant types and person-identifier party groups, rather than performing broad general ledger or grant accounting work.

Usage Notes

Because IGR_GEN_001 is classified as OTHER and exposes only administrative procedures, it is not intended for direct invocation from a user-facing form or a public concurrent program. It is typically called from within the IGR applicant type processing layer — specifically IGR_I_A_ITYPE_PKG — when EAP availability or EITPI mappings must be synchronized. Extension developers should treat it as an internal implementation detail: callers should prefer the supported parent packages rather than invoking ADMP_* procedures directly. When troubleshooting data inconsistencies in EAP availability or EITPI associations, DBMS_OUTPUT tracing combined with the documented dependencies on IGS_PE_PERSID_GROUP_* tables is the most reliable diagnostic path.