Search Results get_allow_multiple_sra_flag

Overview

IBY_FD_POST_PICP_PROGS_PVT is a private (PVT) PL/SQL package owned by the APPS schema in Oracle E-Business Suite, with header revision 120.24 dated September 2, 2010. It declares AUTHID CURRENT_USER and registers the debug module iby.plsql.IBY_FD_POST_PICP_PROGS_PVT with the application debugging framework, which allows its execution to be traced through the standard FND logging infrastructure.

The package supports the post-processing phase of the Oracle Payments (IBY) payment instruction lifecycle, with particular emphasis on Federal付款 summary formats and payment process request (PICP) programs. Its primary API, PROCESS_FEDERAL_SUMMARY_FORMAT, is invoked by Federal code to drive the extract, formatting, and delivery of Federal summary formats after the original bulk payment file has been produced. The package also manages the scheduling and execution of post-payment-instruction programs, tracks SRA (Supplemental Remittance Advice), positive pay, and regulatory report creation status, and records transmission errors.

Key Procedures and Functions

• PROCESS_FEDERAL_SUMMARY_FORMAT — Entry point that initiates extraction, formatting, and delivery of a Federal summary format for a given payment instruction.
• RUN_POST_PI_PROGRAMS — Drives the set of post-payment-instruction programs that must execute after the payment file is built.
• POST_RESULTS — Writes processing results and status back to the repository.
• INSERT_TRANSMISSION_ERROR — Records transmission failures in the transaction error tables.
• SAVE_LAST_PERIODIC_SEQ_NUMS — Persists periodic sequence numbers used in summary file naming.
• SET_SRA_CREATED / SET_POS_PAY_CREATED / SET_REG_RPT_CREATED — Flags indicating that Supplemental Remittance Advice, positive pay, and regulatory reports have been generated.
• POST_FV_SUMMARY_FORMAT_STATUS — Updates status for Federal (FV) summary format processing.
• GET_INSTRUCTION_FORMAT — Retrieves format information for a payment instruction.
• GET_ALLOW_MULTIPLE_SRA_FLAG — Returns the flag controlling whether multiple SRAs may be created; this is the object associated with the search term that surfaced this package.
• VAL_INSTRUCTION_ACCESSIBLE / VAL_PMT_REG_INSTR_ACCESSIBLE / VAL_PPR_ST_RPT_ACCESSIBLE — Validation routines confirming that instructions, payment/regulatory instructions, and payment process request status reports are accessible to the caller before processing.
• CHECK_PPR_MOAC_BLOCKING — Detects blocking MOAC (Multi-Org Access Control) conditions affecting the payment process request.
• RESET_PERIODIC_SEQUENCE_VALUE — Resets the periodic sequence used for ECS DOS file naming.
• SUBMIT_SCHEDULE — Submits the post-processing schedule of programs.
• TEST_CP / SUBMIT_ACP_LTR — Utility for testing the concurrent program and for submitting the ACP letter.
• RUN_ECE_FORMATTING — Triggers formatting through the ECE (Electronic Commerce Engine) facility.

Tables Accessed

Documented references include IBY_PAY_INSTRUCTIONS_ALL, IBY_PAYMENTS_ALL, IBY_DOCS_PAYABLE_ALL, IBY_FORMATS_B, IBY_PAY_SERVICE_REQUESTS, IBY_ACCT_PMT_PROFILES_B, IBY_REMIT_ADVICE_SETUP, IBY_PROCESS_ORGS, IBY_TRANSACTION_ERRORS and its _S sequence, XDO_TEMPLATES_B, FND_APPLICATION, and DUAL. The Federal prerequisite tables FV_SUMMARY_CONSOLIDATE and FV_TP_TS_AMT_DATA supply the summary control number and treasury symbol/amount data required by PROCESS_FEDERAL_SUMMARY_FORMAT.

Usage Notes

This package is private and should not be called directly by customer code; it is invoked by Oracle Payments internal processes, by concurrent programs such as the payment instruction formatting and post-processing programs, and by the Oracle Forms UI when users submit, format, or inspect payment instructions. The GET_ALLOW_MULTIPLE_SRA_FLAG function is used internally to decide whether an additional Supplemental Remittance Advice may be generated for an instruction. Ten other packages reference this package, confirming its role as an internal dependency during post-payment-instruction processing. Custom code requiring similar behavior should use the public IBY APIs rather than this private package, since its signatures may change between releases without notice.