Search Results pos_create_enterprise_user

Overview

APPS.POS_ENTERPRISE_UTIL_PKG is a server-side PL/SQL utility package used by Oracle E-Business Suite to manage the enterprise (internal) organization's representation within the Oracle Trading Community Architecture (TCA) and Oracle Applications user model. In EBS, the enterprise itself is treated as a party—typically the "internal" organization created and maintained by the Applications seed data. This package provides a small, focused API surface that allows forms, concurrent programs, and other PL/SQL units to retrieve information about the enterprise party, obtain the enterprise party identifier and name, create the enterprise party record when it does not yet exist, and create a user associated with the enterprise with an accompanying party relationship. The header revision ($Header: POSENTRS.pls 120.1, dated 2005/07/21) indicates the package belongs to the older "POS" (Oracle Advanced Planning / enterprise-oriented) code family and has been carried forward through the 12.1.1 and 12.2.2 releases as a stable utility. It is classified as a non-public API (API classification: OTHER) and is referenced by twelve other packages, making it an internal building block rather than an end-user-facing entry point.

Key Procedures and Functions

The package exposes five documented procedures. Each is built around the EBS convention of returning an x_status outcome plus an x_exception_msg for diagnostics, so callers can test success or failure without relying on exceptions.

• GET_ENTERPRISE_INFORMATION — Returns the enterprise party identifier and party name together, along with status and exception message outputs. This is the broadest retrieval routine, useful when a caller needs to resolve the enterprise party in a single call.
• GET_ENTERPRISE_PARTY_NAME — Returns only the enterprise party name, with status and exception message. Typically used for display purposes where the identifier is already known.
• GET_ENTERPRISE_PARTYID — Returns only the enterprise party identifier, with status and exception message. Used when downstream logic needs the numeric party key for lookups or foreign-key assignment.
• CREATE_ENTERPRISE_PARTY — Creates the enterprise party record, returning status and exception message. This is the procedure most commonly located when searching for "create_enterprise_party"; it is the creation counterpart to the getter routines above and is intended for initialization or repair scenarios where the enterprise party does not yet exist.
• POS_CREATE_ENTERPRISE_USER — Creates an application user associated with the enterprise, taking username, first name, last name, and an optional e-mail address as inputs, and returning the new party identifier, the relationship identifier linking that user to the enterprise company, plus status and exception message outputs.

Tables Accessed

The documented table references are resolved through APPS synonyms and reflect the package's dual TCA/user-model responsibilities:

• HZ_PARTIES — The TCA party registry. Read by the getter routines to resolve the enterprise party's name and identifier, and written by CREATE_ENTERPRISE_PARTY (and indirectly by POS_CREATE_ENTERPRISE_USER) when a new party record must be created.
• HZ_CODE_ASSIGNMENTS — TCA classification/code assignment table, used to maintain the party classifications or codes that identify the enterprise organization and newly created user parties.
• FND_USER — The Oracle Applications user table. Referenced by POS_CREATE_ENTERPRISE_USER to create the application user account that corresponds to the enterprise-associated person, and to link that user to the party and relationship returned as outputs.

Usage Notes

POS_ENTERPRISE_UTIL_PKG is not intended for direct ad hoc invocation by end users; it is an internal utility invoked by other packages (twelve documented dependents) and possibly by enterprise-related forms or setup routines. The getter procedures are safe for read-only use in custom code, concurrent programs, or form triggers where the enterprise party must be resolved. The creation procedures—CREATE_ENTERPRISE_PARTY and POS_CREATE_ENTERPRISE_USER—have side effects in HZ_PARTIES, HZ_CODE_ASSIGNMENTS, and FND_USER; they should be called with commit/rollback control managed by the caller and only when the caller has determined that the enterprise party or enterprise user does not already exist. Because the API classification is OTHER rather than PUBLIC, Oracle does not guarantee backward compatibility, and customizations that depend on these signatures should be reviewed during upgrades from 12.1.1 to 12.2.2. Callers should always inspect x_status and x_exception_msg before proceeding, since the package reports failures through output parameters rather than raising exceptions.