Results for “increment_revision”

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

Overview

BOMPINRV is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides revision management utilities for Oracle Bills of Material. Its single documented procedure, increment_revision, computes the next logical revision identifier for an inventory item within a specific organization, without persisting or implementing that revision in the database. The package therefore serves as a decision and formatting layer rather than a data-maintenance API: calling programs retain responsibility for actually creating or activating the revision row.

The package is classified as OTHER in the ETRM metadata, indicating it is not a standard public-interface API such as those in the BOMP family. Its encapsulated design deliberately allows customers to substitute their own revision-numbering algorithm. Because the procedure signature is exposed, Oracle documents increment_revision as customer-modifiable, while warning that any change to its parameters requires review of dependent calling code — specifically programs such as BOMPKMUD.

Key Procedures and Functions

• increment_revision — Determines the next revision for a given item and organization as of a supplied effective date, returning the resulting revision string through an OUT parameter and reporting failures through a PL/SQL error message. The procedure receives the inventory item identifier, the organization identifier, the effective date of the prospective new revision, and a program information structure carrying session context (user id, concurrent request id, application id, program id, and login id). It does not implement the revision; it only calculates and returns the incremented value. Internal logic reads the current revision from the item revision tables to derive the successor value.

The package also declares the ProgramInfoStruct record type, a standard EBS context structure used to pass runtime identity and request information into the procedure for auditing and concurrent processing purposes.

Tables Accessed

• MTL_ITEM_REVISIONS — The primary revision entity and the source of the current revision value and effectivity date used to compute the next revision.
• MTL_ITEM_REVISIONS_B and MTL_ITEM_REVISIONS_B_S — Base tables holding revision definitions and their sequence or key structure; _B_S is the corresponding sequence surrogate used by the revision entity.
• MTL_ITEM_REVISIONS_TL — The translation table supplying language-specific revision descriptions and text.
• FND_LANGUAGES — Used to resolve the current session language when reading translated revision data.
• DUAL — Used for single-row evaluation and PL/SQL expression evaluation.

All references are made through APPS synonyms, consistent with the package executing under the APPS schema.

Usage Notes

BOMPINRV is typically invoked indirectly. Oracle documents one dependent package, and the header comment cites BOMPKMUD as a calling program that must be inspected if the procedure signature is altered. This pattern indicates the package is called from higher-level revision-maintenance logic, including concurrent programs and form-driven processes that create new item revisions.

Because the procedure does not implement the revision, callers must supply their own insert or update against MTL_ITEM_REVISIONS after receiving the OUT revision value. Customers implementing organization-specific revision schemes may modify the procedure body, relying on the package encapsulation to prevent side effects in callers. Any such modification should be re-applied after patching or upgrading to 12.1.1 or 12.2.2, since the package is not a protected public API.