Results for “create_proposal”
15 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGW_CREATE_PROPOSAL_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Grants/Proposal (IGW) application family. Its declared purpose, as reflected by its name and API classification (PUB), is to expose a supported programmatic interface for the creation of proposal records within the ETRM/IGW data model. In EBS 12.1.1 and 12.2.2 the package body is shipped with a single public entry point, CREATE_PROPOSAL, which external callers can invoke to initiate proposal creation without directly manipulating the underlying base tables. The package follows the standard Oracle Applications public API convention: an internal constant (G_PKG_NAME) identifies the package for logging and error handling, and the body is deliberately compact so that all business logic lives behind a stable, forward-compatible signature. The header comment identifies revision 120.1 dated 2005/09/12, indicating that the shipped implementation has remained stable across releases.
Key Procedures and Functions
- CREATE_PROPOSAL — the sole documented procedure in the package body. It is declared immediately after the G_PKG_NAME constant and represents the public contract exposed to calling code. Notably, the shipped body of this procedure contains only a
NULL;statement, i.e. the documented implementation is a stub. This means that in the delivered 12.1.1 / 12.2.2 code base the procedure performs no database work on its own; the published interface exists to reserve the API name and signature for the IGW proposal creation workflow, allowing Oracle and customers to rely on a stable call point while the functional logic is supplied elsewhere (for example by form-level or concurrent-processing logic, or by a later revision). No parameter list is documented in the supplied excerpt, so callers should verify the exact formal parameters against the actual package specification in their instance before invoking it.
Tables Accessed
According to the documented metadata, the package references no tables through APPS synonyms. This is consistent with the shipped stub implementation, which performs no DML or queries. Any table access implied by the concept of "proposal creation" — for example insert into the IGW proposal header and related detail tables — is not implemented in this body and therefore cannot be attributed to it from the available documentation. Integrators must not assume that calling CREATE_PROPOSAL will populate IGW proposal tables; in the delivered code it will not.
Usage Notes
- The package is classified as a public (PUB) API, so it is the intended, supported surface for external calls; customers and partners should prefer it over direct inserts into IGW base tables to preserve upgrade safety.
- Because the shipped procedure body is a no-op stub, invocation from forms, concurrent programs, or custom code will succeed but produce no data changes in the delivered release. Treat it as an interface placeholder.
- The metadata records zero dependent packages, indicating no other shipped PL/SQL unit calls IGW_CREATE_PROPOSAL_PUB within the documented scope.
- Before writing custom code against this API, confirm the current package specification in the target instance (12.1.1 or 12.2.2) and validate behavior in a non-production environment, since the documented body may differ from a patched or customized version.
-
This is the lookup for the customer actions like Create Lead, Create Opportunity in the Customer Detail Pages
-
This is the lookup for the customer actions like Create Lead, Create Opportunity in the Customer Detail Pages
-
This is the lookup for the contact actions like Create Lead, Create Opportunity, Create Proposal, Create Quote in the Contact Detail Pages.
-
This is the lookup for the contact actions like Create Lead, Create Opportunity, Create Proposal, Create Quote in the Contact Detail Pages.