Search Results encryption_enabled




Overview
Explore in AI Chat

Overview

IBY_CC_SECURITY_PUB is a public PL/SQL package in the APPS schema within Oracle E-Business Suite, positioned within the Payments (IBY) product family and specifically within the credit card security subsystem. Its stated purpose is to expose security-related configuration and lookup services that other Payments components require when processing credit card and other payment instrument data. In both 12.1.1 and 12.2.2, EBS stores payment security configuration at multiple levels — system-wide options, key assignment and security segments — and this package provides a clean public interface into that configuration so that callers do not need direct knowledge of the underlying storage tables. The package body is documented as VALID in ETRM, indicating it is a supported, compiled component of the standard application codebase rather than a customization artifact.

Key Procedures and Functions

Two documented program units make up the public interface:

  • ENCRYPTION_ENABLED — a function that reports whether encryption is currently enabled for the relevant payment security context. Callers use this to decide whether sensitive instrument data will be encrypted before storage and to branch their processing logic accordingly. It allows dependent code to remain agnostic to whether a particular environment has encryption turned on.
  • GET_SEGMENT_ID — a function that returns the identifier of a security segment. Security segments are the discrete units into which protected payment data is divided for encryption, key management, and access control purposes. This routine supplies callers with the correct segment identifier, which is then used when reading or writing encrypted values and when applying security rules.

The signature and parameter details of both routines are not enumerated in the available ETRM metadata, so callers should verify the exact specification against the deployed package in their environment.

Tables Accessed

The package body references two application tables, both resolved through APPS synonyms:

  • IBY_SECURITY_SEGMENTS — the definition table for payment security segments. GET_SEGMENT_ID derives its return value from data held here, making this the authoritative source for segment identifiers.
  • IBY_SYS_SECURITY_OPTIONS — the system-level security options table, which stores settings such as whether encryption is active. This table underpins the ENCRYPTION_ENABLED function.

Because the documented dependency list names only these tables, the package appears to be read-only with respect to the schema; it functions as a query facade over configuration rather than a maintenance API.

Usage Notes

ETRM records that IBY_CC_SECURITY_PUB references the package specification of the same name and the SYS.STANDARD package, and that it is referenced by three other packages. It is therefore an internal building block invoked from within the Payments stack — most likely from credit card validation, encryption, and instrument processing packages — rather than an end-user facing API. Typical invocation points include Oracle Forms-based payments setup screens (system security options, security segment maintenance) and any custom code that must determine encryption state or resolve a segment identifier before handling protected payment data. Because the routines are classified PUB, they are safe to call from custom extensions, but developers should note that the package exposes configuration lookups only; it neither encrypts data nor enforces access, and it should be treated as a read-only query interface whose results reflect current setup in IBY_SECURITY_SEGMENTS and IBY_SYS_SECURITY_OPTIONS.