Search Results create_card_wrapper

Overview

CS_CREDIT_CARD_ASSIGNMENT is a credit card assignment utility in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment. The package handles the processing and assignment of credit card information within Oracle iPayment (IBY) and Order Capture. Its primary purpose is to facilitate the creation, validation, and assignment of credit card instruments to owners or external payers within the Oracle payments framework. The package is part of the Customer Care / Service (CS) module integration with Oracle Payments, providing a controlled interface between application forms or processes and the underlying IBY_CREDITCARD instrument repository.

Key Procedures and Functions

• CREATE_CARD_WRAPPER — The single documented procedure within this package. Its purpose is to wrap the creation of a credit card instrument, providing a structured entry point through which a caller supplies card data and associated metadata. The wrapper abstracts the underlying complexity of inserting or updating records in the IBY_CREDITCARD table. Based on the parameter list in the source header, the procedure accepts a broad set of values including owner identity, cardholder name, billing address details, card number, expiry date, instrument type, purchase card flags, issuer and financial institution information, single-use and information-only flags, card purpose, description, active/inactive status, a DES3 system security key, and numerous descriptive flexfield attributes (attribute_category through attribute13). The DES3 security key parameter (p_sys_sec_key) indicates that the procedure handles secure encryption of sensitive card data before persistence, consistent with Oracle Payments PCI-related controls. The transaction control (p_commit) allows the caller to decide whether the wrapper commits or defers within a larger transaction.

Tables Accessed

• IBY_CREDITCARD — This is the primary Oracle Payments table that stores credit card instrument records. The package writes to (and reads from) this table to persist the credit card information supplied through CREATE_CARD_WRAPPER, including the card number, expiry date, encrypted security data, owner reference, and associated descriptive attributes.
• IBY_EXTERNAL_PAYERS_ALL — This table holds external payer records used by Oracle Payments. The package references it to resolve or validate the owner/payer identity (p_owner_id) so that the newly created card instrument is correctly linked to a valid payer in the payments system.

Usage Notes

The package is typically invoked from Oracle EBS forms or custom PL/SQL callers that need to programmatically create a credit card instrument. In the standard application, credit card capture and assignment occurs through the Oracle iPayment / Order Capture user interface, which in turn calls internal APIs; CS_CREDIT_CARD_ASSIGNMENT serves as a service-layer wrapper that consolidates those operations. Customizations commonly call CREATE_CARD_WRAPPER from custom forms, concurrent programs, or integration scripts when bulk loading or synchronizing credit card data. Because the procedure manipulates sensitive financial data and security keys, callers must supply appropriate privileges on the IBY schema objects and use secure handling of the card number and DES3 key. The procedure is not referenced by other documented packages per the ETRM metadata, so any invocation is from forms, concurrent processes, or external custom code. Developers should verify that any caller respects the transaction and commit semantics of p_commit and that descriptive flexfield attributes align with the target IBY_CREDITCARD entity configuration. Appropriate testing in a controlled environment is recommended before deployment to production, given the payment-related nature of the data.