Results for “igw_prop”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGW_PROP is the core PL/SQL package within the Oracle E-Business Suite Grants/Proposal (IGW) module, responsible for retrieving, validating, and maintaining proposal-related data. It is declared with AUTHID CURRENT_USER, meaning that execution privileges are evaluated against the invoking schema rather than the package owner (APPS), which is significant for customizations and for callers that need to respect the calling user's security context. The package is classified as OTHER in the ETRM documentation for 12.1.1.

Functionally, IGW_PROP acts as a centralized access layer over the IGW proposal tables. It resolves personnel names and identifiers, determines business group and organizational context, evaluates signatory and role attributes, and orchestrates copy operations across the various proposal component tables. It is referenced by three other packages, indicating that it serves as a shared utility for higher-level proposal processing logic.

Key Procedures and Functions

The package exposes fifteen documented procedures and functions. The following describes their purpose based on the ETRM metadata:

• GET_BUSINESS_GROUP — Returns the business group identifier and name, providing the organizational context for governance and security.
• GET_SIGNING_OFFICIAL — Retrieves the signing official's identifier and name for a given organization.
• GET_ADMIN_OFFICIAL_ID — Returns the administrative official identifier for an organization.
• GET_USER_NAME — Resolves a person identifier to a displayable user name.
• GET_PI_FULL_NAME — Returns the full name of the principal investigator associated with a proposal. This is the object the user searched for.
• GET_PI_FORMATTED_NAME — Returns the principal investigator's name in a formatted presentation, typically for display in forms or reports.
• GET_LOOKUP_MEANING — Resolves a lookup code to its meaning using the supplied lookup type and code.
• GET_NARRATIVE_STATUS — Returns the narrative status for a proposal.
• GET_MAJOR_SUBDIVISION — Returns the major subdivision description for an organization.
• IS_PROPOSAL_SIGNING_OFFICIAL — Determines whether a given user is the signing official for a proposal.
• GET_TOP_PARENT_ORG_NAME — Returns the name of the top parent organization for a given organization.
• INS_PROP_USER_ROLE — Inserts a user-to-role association for a proposal.
• DEL_PROP_USER_ROLE — Removes a user-to-role association for a proposal.
• COPY_PROPOSAL_ALL — Copies all components of a proposal.
• SET_COMPONENT_STATUS — Updates the status of a proposal component.

Several functions carry PRAGMA RESTRICT_REFERENCES declarations (WNDS and/or WNPS), confirming that they perform no database writes or package state changes, which makes them safe for use inside SQL statements.

Tables Accessed

IGW_PROP reads and writes through APPS synonyms. The primary proposal tables include IGW_PROPOSALS_ALL, IGW_PROP_ABSTRACTS, IGW_PROP_CHECKLIST, IGW_PROP_LOCATIONS and IGW_PROP_LOCATIONS_S, IGW_PROP_NARRATIVES, IGW_PROP_PERSONS, IGW_PROP_PROGRAM_ADDRESSES, IGW_PROP_SCIENCE_CODES, IGW_PROP_SPECIAL_REVIEWS, and IGW_PROP_USERS. Personnel and organizational resolution uses FND_USER, HR_ALL_ORGANIZATION_UNITS, and IGW_ORG_DETAILS. Attachment handling references FND_ATTACHED_DOCUMENTS. These tables support the name resolution, status, role, and copy operations described above.

Usage Notes

IGW_PROP is typically invoked from Oracle Forms within the Grants/Proposal module, from concurrent programs that process or copy proposals, and from other PL/SQL packages that depend on its utility functions. Because it uses AUTHID CURRENT_USER, custom code invoking GET_PI_FULL_NAME or related functions must ensure the executing schema has appropriate execute privileges and access to the underlying tables. The RESTRICT_REFERENCES declarations mean the read-only functions are safe to call within SQL, while procedures such as INS_PROP_USER_ROLE and COPY_PROPOSAL_ALL perform DML and should be invoked transactionally.