Search Results update_contact_stecode

Overview

OKC_CTC_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module, declared with AUTHID CURRENT_USER and shipped under the APPS schema. Its header carries the revision marker OKCSCTCS.pls 120.1, dated 23-Nov-2010. The package encapsulates the low-level data-manipulation and versioning logic for contract contacts, the associations between a contract (or contract line) and the parties, resources, or external contacts linked to it. Contact rows are stored in OKC_CONTACTS and its audit/version table OKC_CONTACTS_H, and the package provides the programmatic plumbing that higher-level public APIs, forms, and concurrent processes use to insert, update, lock, delete, validate, and version those rows. Because the API is classified PVT, it is not part of the supported public interface and is intended for consumption by Oracle's own contact-handling code rather than by customer extensions.

Key Procedures and Functions

ETRM documents 17 procedures and functions; the following are named in the metadata.

• INSERT_ROW — Creates a new OKC_CONTACTS row from the package record type ctc_rec_type, applying the OKC_API.G_MISS_* sentinel defaults declared in the global record structure.
• UPDATE_ROW — Modifies an existing contact row, including Who columns and the OBJECT_VERSION_NUMBER used for optimistic locking.
• UPDATE_CONTACT_STECODE — The routine matching the search term "update_contact_stecode". It maintains the contact source/status code (STECODE) associated with a contact, that is, the OKC_CONTACT_SOURCES linkage that identifies how or from where a contact was derived.
• VALIDATE_ROW — Performs attribute and referential validation before a contact record is committed.
• LOCK_ROW — Obtains a row-level lock on a contact to serialize concurrent modification.
• DELETE_ROW — Removes a contact record.
• CHANGE_VERSION — Advances or reconciles the object version number of a contact during an update cycle.
• CREATE_VERSION, RESTORE_VERSION, API_COPY — Version-management routines: they snapshot a contact into OKC_CONTACTS_H, restore a prior version, and copy contact data respectively.
• INSERT_ROW_UPG — An upgrade-specific insert variant used when migrating or seeding contact data.
• QC — A quality/consistency check routine.

Exact parameter lists are deliberately omitted here; callers should obtain signatures from the deployed package specification.

Tables Accessed

• OKC_CONTACTS — Primary contact entity, the target of INSERT_ROW, UPDATE_ROW, UPDATE_CONTACT_STECODE, DELETE_ROW, and LOCK_ROW.
• OKC_CONTACTS_H — History/audit table used by CREATE_VERSION and RESTORE_VERSION.
• OKC_CONTACT_SOURCES — Source and status mapping for contacts, central to UPDATE_CONTACT_STECODE.
• OKC_K_HEADERS_ALL_B and OKC_K_PARTY_ROLES_B — Contract header and party-role base tables, referenced for validation and role resolution.
• OKC_STATUSES_B — Status-code lookup used in validation.
• DBMS_SQL, PLITBLM, USER_TAB_COLUMNS — Dynamic SQL and index-by-table utilities, plus data-dictionary access for generic column handling.

Usage Notes

OKC_CTC_PVT is invoked indirectly. It is referenced by 26 other packages, meaning the supported public contact APIs and the Contracts forms layer call into it rather than calling it directly. Typical triggers include saving a contact from the Contracts or Customers form, running contact-related concurrent programs, or executing versioning and upgrade scripts that move contact data between OKC_CONTACTS and OKC_CONTACTS_H. Custom code should avoid direct calls to this package: the PVT classification signals that signatures and behaviour may change across patch levels and between EBS 12.1.1 and 12.2.2. Where custom extensions must manipulate contact source codes, the supported route is to use the corresponding public OKC API; UPDATE_CONTACT_STECODE should be treated as an internal helper whose logic Oracle may revise without notice.