Search Results instruction_created

Overview

IBY_FD_POST_PICP_PROGS_PVT is a private PL/SQL package body within the Oracle Payments (IBY) module of Oracle E-Business Suite, versioned for release 12.1.1 and 12.2.2. Its responsibility is to drive the posting and formatting of payment instructions, payment processing results, and associated regulatory or remittance outputs once a Payment Instruction has been built and confirmed by the preceding build and format stages of the payments lifecycle. The package sits behind the public IBY_FD_POST_PICP_PROGS API surface and is classified as PVT, meaning it is intended for internal consumption by the Oracle Payments engine and its dependent programs rather than direct customer invocation.

The package header reveals the core architectural concerns: security initialization, accessibility checks against payment process request organizations, formatted-value and turnaround-summary report submission, straight-through-processing (STP) status control, and the Federal summary format API. The private nature of the package reflects that its entry points are orchestrated by the payments concurrent programs and by sibling packages in the IBY schema.

Key Procedures and Functions

• PROCESS_FEDERAL_SUMMARY_FORMAT — the sole fully documented API entry point, following the standard FND_API calling convention with version compatibility checking, savepoint-based rollback, and message-list initialization. It processes payment instructions flagged for federal summary formatting.
• RUN_POST_PI_PROGRAMS — invokes the downstream concurrent programs required after a payment instruction is finalized.
• POST_RESULTS — persists the outcome of payment processing, propagating status and identifiers back to the payment instruction and transaction records.
• INSERT_TRANSMISSION_ERROR — records transmission-level failures for audit and retry.
• SAVE_LAST_PERIODIC_SEQ_NUMS — preserves the last used periodic sequence numbers so that subsequent runs continue numbering correctly.
• SET_SRA_CREATED, SET_POS_PAY_CREATED, SET_REG_RPT_CREATED — flip creation indicators on the payment instruction for supplemental remittance advice, positive pay files, and regulatory reports respectively.
• POST_FV_SUMMARY_FORMAT_STATUS — writes the status of the formatted-value summary generation.
• GET_INSTRUCTION_FORMAT — resolves the format associated with a payment instruction.
• GET_ALLOW_MULTIPLE_SRA_FLAG — retrieves the profile setting governing multiple supplemental remittance advices.
• VAL_INSTRUCTION_ACCESSIBLE, VAL_PMT_REG_INSTR_ACCESSIBLE, VAL_PPR_ST_RPT_ACCESSIBLE — security validation routines checking user access to instructions and PPR-related statements.
• CHECK_PPR_MOAC_BLOCKING — evaluates blocking conditions on multi-organization access control for the payment process request.
• RESET_PERIODIC_SEQUENCE_VALUE — clears a periodic sequence value when renumbering is required.
• SUBMIT_SCHEDULE, SUBMIT_ACP_LTR, TEST_CP — submission helpers for scheduling and the ACP letter, alongside a concurrent program test utility.
• RUN_ECE_FORMATTING — invokes ECE (Electronic Commerce Engine) formatting for outputs.
• Init_Security and get_accessible_ppr_org_count — establish security context and count accessible organizations.
• Submit_FV_TS_Report and Turn_off_STP_Flag — submit the formatted-value turnaround summary report and disable the STP indicator when conditions require manual intervention.

Tables Accessed

The package reads and writes across the core Oracle Payments data model. IBY_PAY_INSTRUCTIONS_ALL and IBY_PAYMENTS_ALL hold the instruction and payment records being posted. IBY_DOCS_PAYABLE_ALL links payments to their Payables documents. IBY_FORMATS_B and XDO_TEMPLATES_B supply format definitions and the XML Publisher templates used for output generation. IBY_TRANSACTION_ERRORS and IBY_TRANSACTION_ERRORS_S capture and sequence error conditions. IBY_PAY_SERVICE_REQUESTS and IBY_PROCESS_ORGS support processing-organization and request-scoped security checks. IBY_ACCT_PMT_PROFILES_B and IBY_REMIT_ADVICE_SETUP provide account payment profiles and remittance advice configuration. FND_APPLICATION resolves application context, and DUAL is used for single-row queries.

Usage Notes

Because IBY_FD_POST_PICP_PROGS_PVT is marked PVT, it is invoked indirectly. The standard entry points are the Oracle Payments concurrent programs that post payment instruction results, format federal summary output, and generate regulatory and supplemental remittance outputs. Forms within the Payments workbench trigger these programs, which in turn call the private package. The documented dependency graph shows ten other packages referencing this body, confirming its role as a shared posting and formatting engine. Customizations should avoid calling the private package directly and instead use the public IBY_FD_POST_PICP_PROGS API; direct calls bypass supported entry points and may not observe savepoint, security initialization, or message-list conventions.