Results for “config_error”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PACKAGE APPS.IBY_FNDCPT_COMMON_PUB is a public (PUB-classified) PL/SQL package belonging to the Oracle Payments (IBY) module of Oracle E-Business Suite. It provides the shared payer-context utility layer used throughout the Funds Capture and payment instrument infrastructure. Its principal business purpose is to resolve, validate, and compare payer context — the combination of a party, customer account, and customer site that determines which payment instruments and external payer records apply to a transaction.

The package defines the canonical constants that govern payer equivalency (IMMEDIATE, UPWARD, DOWNWARD, FULL) and the three payer context levels (PARTY_LEVEL, CUSTOMER_ACCT_LEVEL, CUSTOMER_SITE_LEVEL). It also standardizes result handling through constants for result categories such as SUCCESS, SUCCESS_WITH_RISK, PENDING, SYSTEM_ERROR, INVALID_PARAM, INCORRECT_FLOW, FINANCIAL_ERROR, and CONFIG_ERROR, and through result codes including INVALID_PARTY_CONTEXT. In ETRM this result code is the origin of the invalid_party_context condition encountered by users and integrators: it is raised when the supplied payer context cannot be resolved to a valid party, customer account, or site combination.

Key Procedures and Functions

• VALIDATE_PAYER — Confirms that a supplied payer context is valid across the relevant hierarchy level. This is the routine most directly associated with the INVALID_PARTY_CONTEXT result code.
• COMPARE_PAYER — Compares two payer contexts using the equivalency modes defined by the package constants (IMMEDIATE, UPWARD, DOWNWARD, FULL), determining whether one payer satisfies or subsumes another.
• PREPARE_RESULT — Constructs and populates the standardized result structure returned to callers, applying the result category and result code constants.
• GET_RESULT_CATEGORY — Returns the category classification for a given result code, allowing callers to branch on success, pending, parameter, or system-level outcomes.
• CLEAR_MSG_STACK — Resets the package message stack, clearing accumulated messages before or after a processing cycle.

Tables Accessed

The package reads the Oracle Trading Community Architecture (TCA) and Payments payer tables through APPS synonyms:

• IBY_EXTERNAL_PAYERS_ALL — External payer definitions used to match a payer context to a configured payment source.
• IBY_RESULT_CODES — Maps result codes to their categories and messages.
• HZ_PARTIES, HZ_PARTY_PREFERENCES — Party identity and preference data used during validation.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES — Customer account and role relationships that establish account-level context.
• HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL — Account site and site-use records that establish site-level context and determine whether a site is usable for the payment purpose.

Usage Notes

IBY_FNDCPT_COMMON_PUB is an infrastructure package rather than an end-user API. It is referenced by 65 other packages, indicating that it is invoked internally by Funds Capture, payment instrument, and payer authorization flows. Custom code that must reconcile or validate a payer before creating a payment instrument should call VALIDATE_PAYER and inspect GET_RESULT_CATEGORY, treating the INVALID_PARTY_CONTEXT result code as an indication that the TCA party, account, or site hierarchy does not resolve correctly. Because the package version header references 120.10 and the 12.1.1 / 12.2.2 documentation sets are substantially aligned for this object, behavior is consistent across both releases.