Search Results convert_org_to_id

Overview

CS_CORE_UTIL is a shared utility package body owned by APPS within the Oracle E-Business Suite Customer Service (CS) module. It is classified as a UTIL API, meaning it does not represent a business entity in itself but instead supplies reusable helper logic consumed by the larger Customer Service API family. Its principal responsibility is to centralize the low-level operations that many CS APIs require: constructing standardized FND error messages, resolving descriptive identifiers into their numeric primary keys, and performing common validation of parties, contacts, and descriptive flexfields before an API commits data.

The package is version-tracked with a header comment dating to release 11i (header 120.4), and it remains present in EBS 12.1.1 and 12.2.2 with 37 documented procedures and functions. It is referenced by at least seven other packages, confirming its role as foundational infrastructure rather than an end-user entry point.

Key Procedures and Functions

The documented surface divides into three functional groups.

• Message construction: ADD_DUPLICATE_VALUE_MSG, ADD_INVALID_ARGUMENT_MSG, ADD_MISSING_PARAM_MSG, ADD_NULL_PARAMETER_MSG, ADD_PARAM_IGNORED_MSG, ADD_SAME_VAL_UPDATE_MSG, and ADD_DESC_FLEX_MSG push standardized messages onto the FND message stack. Each checks the current message level via FND_MSG_PUB before adding, so callers honor session error-reporting settings.
• Identifier resolution: CONVERT_CUSTOMER_TO_ID, CONVERT_CUSTOMER_TO_NAME, CONVERT_CONTACT_TO_ID, CONVERT_EMPLOYEE_TO_ID, CONVERT_ORG_TO_ID, and CONVERT_LOOKUP_TO_CODE translate human-readable names, numbers, or lookup meanings into the internal identifiers required by downstream APIs. CONVERT_CUSTOMER_TO_ID is the procedure users most commonly search for, since it maps a customer name or number to an HZ_PARTIES-derived identifier.
• Validation and defaults: VALIDATE_CUSTOMER, VALIDATE_CUSTOMER_CONTACT, VALIDATE_BILL_TO_SITE, VALIDATE_COMMENT, and VALIDATE_DESC_FLEX verify input before persistence. DEFAULT_COMMON_ATTRIBUTES, IS_MULTIORG_ENABLED, and TRUNC_STRING_LENGTH supply supporting behavior for common attribute columns, multi-org determination, and column-length safety.

Tables Accessed

The package reads and writes the following documented objects through APPS synonyms:

• HZ_PARTIES — the registry of customers, contacts, and organizations; the source for all CONVERT_*_TO_ID lookups and VALIDATE_CUSTOMER checks.
• FND_USER and FND_LOGINS — used to resolve the current or named application user and to support CONVERT_EMPLOYEE_TO_ID and auditing context.
• FND_PRODUCT_GROUPS — consulted by IS_MULTIORG_ENABLED to determine whether the installation is multi-organization enabled.
• CS_INCIDENTS_ALL and CS_INTERACTIONS — the Customer Service service-request and interaction tables; referenced when validating comments and related attributes.
• DUAL — used for scalar evaluations and utility arithmetic.

Usage Notes

CS_CORE_UTIL is not exposed through a dedicated form or concurrent program. It is invoked internally by the Customer Service public APIs and by custom extensions that follow the CS API conventions. Typical call patterns include calling CONVERT_CUSTOMER_TO_ID to obtain a party identifier from a name entered on a service-request form, then passing that identifier into an incident or interaction API; or calling the ADD_*_MSG procedures to surface a consistent error block when a validation routine returns failure.

Because message-adding routines are conditional on FND_MSG_PUB.check_msg_level, developers embedding these calls in concurrent programs should verify that the message level is set appropriately. In 12.2.2 the package remains unchanged in classification (UTIL) and continues to depend only on documented APPS synonyms, making it safe to reference in custom code provided the same release-compatible HZ and FND objects are present.