Search Results missing_profile

Overview

IBY_ASSIGN_PUB is a public PL/SQL package in the Oracle Payments (IBY) module of Oracle E-Business Suite, delivered in releases 12.1.1 and 12.2.2. It implements the payment document assignment flow: the mechanism by which the payment system discovers which payment documents (invoices, debit memos, credit memos, and other payables documents) are ready for the next stage of the payment lifecycle, groups them by payee, and determines the correct payment profile and internal bank account to apply against them. The package sits between the payables document tables and the payment instruction build process, ensuring that only documents with complete payee and account setup are progressed.

The package refers to the term "ready_for_validation" in a specific way. The module-level constant DOC_STATUS_FULL_ASSIGNED is declared with the literal value 'READY_FOR_VALIDATION'. This is the status assigned to a payment document once the assignment step has successfully matched it to both a payee payment profile and an internal bank account. Documents that fail assignment are instead flagged MISSING_ACCOUNT, MISSING_PROFILE, or MISSING_ACCOUNT_AND_PROFILE. Correspondingly, the owning payment service request is set to ASSIGNMENT_COMPLETE or INFORMATION_REQUIRED. A document reaching READY_FOR_VALIDATION is therefore the successful terminal state of this package's work.

Key Procedures and Functions

The package exposes thirteen documented procedures and functions. PERFORMASSIGNMENTS is the main entry point that drives document assignment across the processing set. GETREQUESTATTRIBUTES retrieves the attributes of a payment service request needed to govern the assignment run.

• SETDOCUMENTASSIGNMENTS and UPDATEDOCUMENTASSIGNMENTS apply and persist the assignment outcome on each payable document, including the status transitions that produce READY_FOR_VALIDATION.
• POPULATEDOCATTRIBUTES derives document-level attributes required for assignment.
• GETPROFILEFROMPROFILEDRIVERS and GETPROFILEFROMPAYEEFORMAT resolve the payment profile for a payee, using either profile driver rules or payee-level formatting configuration.
• FINALIZESTATUSES and UPDATEREQUESTSTATUS consolidate results and move the payment service request to its completion status.
• DUMMYCEAPI and DUMMYASGNHOOK are placeholder/extension hook routines, permitting customer overrides at defined points in the flow.
• RAISEBIZEVENTS publishes business events via IBY_EVENT_KEY_S when assignment milestones occur.
• GETXMLCLOB returns XML used in the request processing payload.

Tables Accessed

The package operates against the core Payments and Cash Management tables through APPS synonyms. IBY_DOCS_PAYABLE_ALL stores the payable documents and receives the assignment status updates, including the READY_FOR_VALIDATION outcome. IBY_PAY_SERVICE_REQUESTS holds the request header whose status is updated to ASSIGNMENT_COMPLETE or INFORMATION_REQUIRED. CE_BANK_ACCOUNTS is queried to obtain candidate internal bank accounts for the payee. IBY_EXTERNAL_PAYEES_ALL provides payee information used in profile determination, while IBY_EVENT_KEY_S supports business event publication. DBMS_XMLQUERY, DUAL, and PLITBLM are used for XML construction and utility operations.

Usage Notes

IBY_ASSIGN_PUB is normally invoked indirectly. It is called during payment processing when the assignment stage is executed for a payment service request, and it is referenced by three other packages in the Payments module. It is not intended for ad hoc execution by end users. Forms-based users typically trigger it through the payment process request submission path, while technical users interact with it via the payment process request concurrent programs or through custom extensions that call the public entry point and the documented hook routines. Because the assignment status values, including READY_FOR_VALIDATION, are defined as package constants and written directly to the document and request tables, customizations that change assignment behaviour should preserve the expected status vocabulary to avoid breaking downstream validation and payment build processing.