Results for “commit_cm”

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

Overview

SYS.DBMS_STANDARD is the built-in PL/SQL package that defines the language primitives available to every stored program unit in the Oracle database. It is not an Oracle E-Business Suite product component, but it is the foundation on which all EBS PL/SQL — including the 3,721 packages that reference it in ETRM 12.2.2 — implicitly depends. Every trigger that calls RAISE_APPLICATION_ERROR, every program that tests INSERTING, UPDATING, or DELETING, and every unit that issues COMMIT, ROLLBACK, or SAVEPOINT is invoking routines declared in DBMS_STANDARD.

In the ETRM classification, the package carries the API classification OTHER and is owned by SYS. Because it is compiled into the database kernel and instantiated automatically at session start, it cannot be modified, dropped, or recompiled by an EBS application schema. Its definitions are referenced by identity, not by an APPS synonym.

Key Procedures and Functions

ETRM documents 40 procedures and functions. The principal groups are:

• Error handling: RAISE_APPLICATION_ERROR raises a user-defined exception with a numbered error and message, propagating it to the calling form, concurrent program, or client. IS_SERVERERROR and SERVER_ERROR support inspection of server-side error conditions.
• Trigger predicates: INSERTING, DELETING, and UPDATING (the last overloaded for a named column) return BOOLEAN and allow row-level trigger logic in EBS audit and validation triggers to branch on the DML that fired the trigger.
• Transaction control: COMMIT, COMMIT_CM, ROLLBACK_NR, ROLLBACK_SV, SAVEPOINT, and SET_TRANSACTION_USE provide the commit, rollback, and savepoint semantics that EBS concurrent managers and forms rely on for transactional integrity.
• Session and event information: SYSEVENT, DICTIONARY_OBJ_TYPE, DICTIONARY_OBJ_OWNER, DICTIONARY_OBJ_NAME, DATABASE_NAME, INSTANCE_NUM, LOGIN_USER, and DES_ENCRYPTED_PASSWORD expose database event context used in DDL triggers, auditing, and environment resolution.
• Type definitions: ORA_NAME_LIST_T and the DBMS_ID/DBMS_QUOTED_ID subtypes standardize identifier handling across the data dictionary APIs.

Several routines carry the PRAGMA RESTRICT_REFERENCES directive with the WNPS, RNPS, WNDS, and RNDS constraints, guaranteeing that they perform no package state writes, no reads, no database writes, and no database reads. This is the origin of the "restrict_references" search term: the pragma assures the PL/SQL compiler that these primitives are side-effect free, so they remain callable from within SQL statements and purity-constrained contexts.

Tables Accessed

ETRM records no tables referenced through APPS synonyms. This is consistent with the package's definitional role: it operates on session and kernel state rather than application data. Any persistence associated with routines such as COMMIT_CM is handled inside the database server, not through EBS application tables.

Usage Notes

DBMS_STANDARD is invoked implicitly. Forms-based transactions, concurrent programs, and custom PL/SQL never call it by qualified name — the routines are resolved as language keywords. EBS developers should be aware of the following practical points:

• Because the package is a SYS built-in, custom code should not attempt to create a schema-level package with the same name; object resolution would be ambiguous or shadowed.
• RAISE_APPLICATION_ERROR is the standard mechanism by which EBS APIs signal business-rule failures; the error range between -20000 and -20999 is reserved for application-defined messages.
• The trigger predicates are essential in EBS audit triggers and in the seeded trigger templates that populate WHO columns and audit tables.
• COMMIT and rollback routines must be used with care inside EBS workflows, since the concurrent manager and the Forms runtime manage transaction boundaries deliberately; explicit commits can break restartability or leave partial data.
• Any future EBS upgrade retains this package unchanged, making it one of the most stable dependencies in the 12.1.1 and 12.2.2 codebase.