Search Results create_organization_unit




Overview
Explore in AI Chat

Overview

CS

The APPS.CSI_ORGANIZATION_UNIT_PUB package is a public PL/SQL API within the Oracle E-Business Suite Install Base (CSI) module. It manages the association between item instances and organization units. In EBS, an item instance represents a tracked entity such as an asset, serialized item, or equipment record, and an organization unit represents a logical grouping or ownership structure to which that instance may be linked. This package provides the programmatic interface through which applications create, retrieve, update, and expire those instance-to-organization-unit associations.

The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the calling user rather than the definer. The header comment dates to csipous.pls 115.21 and the code has remained stable across the 12.1.1 and 12.2.2 releases. Its procedures follow the standard Oracle EBS API conventions: an p_api_version parameter, commit and message-list control flags, a validation level, strongly typed record or table parameters based on the csi_datastructures_pub structures, and standard x_return_status, x_msg_count, and x_msg_data output parameters.

Key Procedures and Functions

  • GET_ORGANIZATION_UNIT — Retrieves information about the organization unit or units associated with an item instance. It accepts a query record built from csi_datastructures_pub.organization_unit_query_rec, a resolve-ID-columns flag, and an optional time stamp, and returns a table of organization unit headers through the x_org_unit_tbl output parameter.
  • CREATE_ORGANIZATION_UNIT — Creates a new association between an organization unit and an item instance. It accepts a table of organization units and a transaction record, both defined in csi_datastructures_pub, and is used whenever a new instance-to-organization relationship must be established.
  • UPDATE_ORGANIZATION_UNIT — Updates an existing instance-to-organization association. This is the procedure most commonly targeted by callers searching for the update_organization_unit entry point, and it is used when the attributes of an existing association change.
  • EXPIRE_ORGANIZATION_UNIT — Expires an existing instance-to-organization association, effectively ending the relationship without physically deleting the underlying record and thereby preserving the historical audit trail.

Tables Accessed

The documented metadata records DBMS_SQL and PLITBLM as the objects referenced via APPS synonyms. DBMS_SQL is the Oracle-supplied dynamic SQL package, indicating that the API builds and executes SQL dynamically at runtime, which allows flexible query construction for the GET_ORGANIZATION_UNIT retrieval path. PLITBLM is an Oracle-supplied PL/SQL table-index management package used internally to manipulate index-by tables during bulk collection processing. Because the API operates through APPS synonyms and its structures are defined in csi_datastructures_pub, the underlying insert, update, and expire operations act on the Install Base instance and organization unit tables. Direct DML against those base tables should be avoided in favour of this API.

Usage Notes

This package is typically invoked from Install Base forms, from concurrent programs that maintain instance-to-organization relationships, and from custom PL/SQL code that must integrate with CSI data. Callers must:

  • Initialize the API with the correct p_api_version, and set p_init_msg_list to fnd_api.g_true when a clean message stack is required.
  • Control transaction scope explicitly: pass p_commit as fnd_api.g_true only when the caller does not manage its own commit.
  • Populate the csi_datastructures_pub record and table structures before the call and check x_return_status against fnd_api.g_ret_sts_success upon return.
  • Retrieve error details through x_msg_count and x_msg_data, or through the FND message stack, before deciding whether to commit or roll back.

Because the package is classified as a PUB API, Oracle supports its use as a documented integration point for custom development, subject to the standard EBS API usage guidelines.