Search Results submit_lockbox_via_srs




Overview
Explore in AI Chat

Overview

AR_SUBMIT_LOCKBOX is an Oracle E-Business Suite Accounts Receivable package body classified as an OTHER API in the ETRM repository. Its principal purpose is to programmatically submit a Lockbox transmission so that the concurrent process responsible for importing bank lockbox files is launched with the correct transmission context. The package encapsulates the logic needed to validate a transmission, resolve its associated lockbox number, transmission format, and original request identifier, and then hand the request over to the concurrent manager through the standard concurrent request submission interface.

The package is particularly relevant to implementations that need to trigger lockbox processing automatically rather than requiring a user to navigate the Submit Lockbox Processing form. Typical scenarios include external scheduling tools, custom PL/SQL wrappers, and integrations that receive notification of a newly available bank file and must immediately initiate its transmission into Receivables. The package body also contains internal helper logic, most notably a validation routine for transmission information, that ensures the target transmission exists and is in an appropriate state before submission proceeds.

Key Procedures and Functions

  • SUBMIT_LOCKBOX_VIA_SRS — The single documented procedure in this package and the object most commonly associated with the search term "submit_lockbox_via_srs." It submits the lockbox transmission through the Standard Request Submission (SRS) framework, causing the appropriate concurrent program to be scheduled and executed. It serves as the supported entry point for programmatic lockbox submission and is the procedure custom code should call when an automated trigger is required.
  • validate_transmission — An internal function (not part of the documented public API) that validates transmission information before submission. It verifies that the specified transmission exists, that a new transmission name does not collide with an existing one, and that an existing transmission is not closed. It also retains the lockbox number, transmission format, and original request ID for reuse during the submission.

Tables Accessed

  • AR_LOCKBOXES — Identifies the lockbox definition associated with the transmission, supplying the lockbox number used to drive the import.
  • AR_TRANSMISSIONS — The central table for transmission records; stores the transmission name, status, requested lockbox, requested format, and original request ID validated and updated during submission.
  • AR_TRANSMISSION_FORMATS — Provides the transmission format definition that governs how the inbound file is parsed.
  • AR_TRANS_FIELD_FORMATS and AR_TRANS_RECORD_FORMATS — Supply the field-level and record-level format mappings required by the transmission format in use.
  • AR_SYSTEM_PARAMETERS — Supplies Receivables system-level settings that influence lockbox processing behavior.
  • FND_NEW_MESSAGES — Used to retrieve and log Oracle Application message text, including validation error messages surfaced during transmission checks.

Usage Notes

AR_SUBMIT_LOCKBOX is invoked programmatically, most commonly through SUBMIT_LOCKBOX_VIA_SRS. It is not a form-level API and is not referenced by any other documented package in the ETRM repository, which indicates that it is intended as a top-level entry point for custom or external callers rather than as a shared utility within the application codebase. Typical callers include custom concurrent programs, database triggers or schedulers that respond to the arrival of a bank file, and workflow or integration layers that need to launch lockbox import without user intervention.

Because submission relies on the Standard Request Submission framework, the caller must ensure that the requested lockbox and transmission format are correctly configured and that the target transmission is not already closed. Validation failures are returned via FND_MESSAGE and logged through FND_FILE when the AFLOG_ENABLED profile option is set, which is useful when diagnosing failed submissions in a concurrent request log. Debug output is controlled by the PG_DEBUG flag derived from FND_PROFILE.value('AFLOG_ENABLED'). Implementations upgrading between 12.1.1 and 12.2.2 should confirm that the concurrent program and transmission configuration remain valid after upgrade, since the package depends on both the AR transmission setup tables and the concurrent manager being available at invocation time.