Search Results batch




The IGI_STP_CONTROL table is a critical component within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2, specifically designed to support the "Stop Payment" functionality in the Payables module. This table serves as a control mechanism for managing payment stoppages, ensuring compliance with financial controls, and maintaining audit trails. Below is a detailed analysis of its structure, purpose, and integration within Oracle EBS.

Purpose and Functional Overview

The IGI_STP_CONTROL table is primarily utilized to track and manage stop payment requests for issued checks or electronic payments. It acts as a repository for key metadata related to payment stoppages, including authorization details, status, and audit information. This functionality is essential for organizations to prevent fraudulent or erroneous payments, enforce internal controls, and comply with regulatory requirements.

Key Columns and Data Structure

The table typically contains the following critical columns:
  • STP_ID: A unique identifier for each stop payment request.
  • CHECK_ID: References the payment record in AP_CHECKS_ALL or similar tables.
  • STATUS: Indicates the current state (e.g., "Pending," "Approved," "Rejected").
  • REQUESTOR_ID: Links to the user who initiated the stop payment.
  • APPROVER_ID: Identifies the authorized approver.
  • CREATION_DATE and LAST_UPDATE_DATE: Timestamps for audit purposes.
  • REASON_CODE: Categorizes the reason for the stoppage (e.g., "Lost Check," "Vendor Dispute").

Integration with Oracle EBS Modules

The IGI_STP_CONTROL table interacts with multiple EBS modules:
  1. Accounts Payable (AP): Directly interfaces with payment tables (AP_CHECKS_ALL, AP_INVOICES_ALL) to flag stopped payments.
  2. General Ledger (GL): Ensures financial postings reflect payment reversals or adjustments.
  3. System Administration: Leverages user tables (FND_USER) for requestor/approver validation.

Workflow and Business Process

The stop payment process typically follows this sequence:
  1. A user submits a stop payment request via an EBS interface, creating a record in IGI_STP_CONTROL.
  2. The system validates the payment's eligibility for stoppage (e.g., not yet cleared).
  3. Approvers review the request and update the STATUS column upon decision.
  4. Approved requests trigger updates to payment tables and GL entries.

Technical Considerations

  • Indexing: The table should be indexed on CHECK_ID and STATUS for performance.
  • Concurrency: Oracle's locking mechanisms prevent conflicting updates during approval workflows.
  • Custom Extensions: Organizations often extend the table with additional columns for compliance reporting.

Audit and Compliance

The IGI_STP_CONTROL table supports SOX and other compliance frameworks by:
  • Maintaining immutable timestamps for all changes.
  • Providing traceability via user IDs and status transitions.
  • Integrating with Oracle Audit Vault for centralized monitoring.

Conclusion

In Oracle EBS 12.1.1 and 12.2.2, the IGI_STP_CONTROL table is a foundational element for payment risk management. Its design ensures secure, auditable, and efficient handling of stop payments while integrating seamlessly with core financial modules. Proper configuration and maintenance of this table are essential for organizations relying on Oracle EBS for accounts payable operations.