Search Results ego_custom_security_pub

Overview

The APPS.EGO_CUSTOM_SECURITY_PUB package is a public PL/SQL API within the Oracle E-Business Suite product family known as EGO, which governs the Oracle Product Information Management and Item Master data model. Its primary business function is to provide a controlled extension point through which customers can implement custom data security rules that supplement or override the seeded attribute-based security behavior of the Oracle Product Information Management application. In EBS 12.1.1 and 12.2.2, data security for items, item attributes, and related product entities is enforced by the EGO_DATA_SECURITY package hierarchy. The EGO_CUSTOM_SECURITY_PUB package is the documented, supported hook by which site-specific logic can participate in that security decision process without modifying Oracle-owned code.

The package is classified as a PUB (public) API, meaning its interface is published for customer invocation and is therefore subject to Oracle's compatibility guarantees. It is owned by the APPS schema and is validated in the ETRM metadata, confirming that the package specification and body compile cleanly against the referenced dependencies in a supported EBS release.

Key Procedures and Functions

ETRM documentation exposes a single documented entry point on this package:

• CHECK_CUSTOM_SECURITY — The sole documented procedure/function of the package. Its purpose is to evaluate a caller-supplied security context against customer-defined rules and return the result of that evaluation to the calling application. It is the mechanism by which custom security logic is registered with the Oracle data security framework so that the framework can consult site-specific rules when determining whether a given user may access a given product-data record. Because the package is a PUB API, this routine is intended to be implemented or replaced in a customer extension schema while preserving the published signature.

No additional procedures or functions are documented in the ETRM metadata for this object. The parameter list is intentionally not reproduced here; the published specification should be consulted for the exact signature at implementation time.

Tables Accessed

The ETRM metadata for APPS.EGO_CUSTOM_SECURITY_PUB does not list any base tables or APPS synonyms directly referenced by the package. This is consistent with the design intent of a hook-style API: the package itself performs no direct DML against EGO or FND tables. Instead, it depends on the Oracle Application Object Library API package APPS.FND_API, which supplies the standard API return-status conventions (success, expected error, and unexpected error handling) used throughout EBS PL/SQL APIs. It also references SYS.STANDARD, the built-in PL/SQL package providing base language types and operators.

Any table access performed in support of custom security evaluation occurs within the customer's implementation of the procedure, or within the calling framework package EGO_DATA_SECURITY, which invokes this API during the standard security evaluation cycle.

Usage Notes

This package is not invoked directly by end users or by Oracle standard concurrent programs. It is called by EGO_DATA_SECURITY, the framework package responsible for evaluating product data security, as reflected in the dependency metadata where EGO_DATA_SECURITY references EGO_CUSTOM_SECURITY_PUB. The dependency listing also shows the package referencing itself, which typically indicates the package body invoking the specification's routines internally or recursion within the custom logic.

Typical usage scenarios include:

• Implementing site-specific security rules that must be layered on top of seeded EGO attribute-based security, such as restricting item visibility by organization, category, or external system of record.
• Extending the security check to consult customer-maintained tables or external systems before returning an access decision.
• Supporting form-based item and product-data queries where EGO_DATA_SECURITY is engaged, including Oracle Product Workbench and related PIM user interfaces.

Because the object is published with PUB classification, customers should preserve the documented interface and avoid altering Oracle-owned code. All custom logic belongs in the customer's extension of the documented entry point, ensuring the customization remains upgrade-safe through EBS 12.1.1 and 12.2.2 maintenance and release transitions.