Search Results payables




The IGI_STP_CANDIDATES_ALL table is a critical component within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2, specifically designed to support the Subledger Transfer Program (STP) functionality. This table serves as a staging area for identifying and managing accounting entries that are candidates for transfer from subledgers to the General Ledger (GL). Below is a detailed analysis of its structure, purpose, and integration within Oracle EBS.

Purpose and Functional Context

The IGI_STP_CANDIDATES_ALL table is part of Oracle's Internet Global Intercompany (IGI) module, which facilitates intercompany accounting and reconciliation. Its primary role is to store transactional data that qualifies for subledger-to-GL transfer during the STP process. The STP ensures that accounting entries from subsidiary systems (e.g., Payables, Receivables, Assets) are accurately consolidated into the central GL while maintaining audit trails and compliance.

Key Columns and Data Structure

The table typically includes the following columns:
  • CANDIDATE_ID: A unique identifier for each candidate record.
  • SOURCE_ID: References the originating subledger transaction (e.g., invoice ID in AP).
  • SOURCE_TYPE: Indicates the subledger module (e.g., 'AP' for Payables).
  • LEDGER_ID: Links to the target GL ledger.
  • TRANSFER_STATUS: Tracks the STP workflow (e.g., 'PENDING', 'PROCESSED', 'ERROR').
  • CREATION_DATE and LAST_UPDATE_DATE: Audit timestamps.
  • BATCH_ID: Groups related candidates for batch processing.

Integration with Oracle EBS Modules

The table interacts with multiple EBS components:
  1. Subledger Accounting (SLA): SLA rules populate this table with eligible entries based on accounting events.
  2. General Ledger (GL): During STP execution, records are transferred to GL_INTERFACE or GL_JE_BATCHES.
  3. Concurrent Programs: STP-specific programs (e.g., "Transfer Journal Entries to GL") process records from this table.

Technical Considerations

  • Multi-Org Support: The '_ALL' suffix indicates the table stores data across operating units, filtered by MOAC (Multi-Org Access Control).
  • Indexing: Typically indexed on SOURCE_ID, BATCH_ID, and TRANSFER_STATUS for performance.
  • Purge Mechanisms:
    • Processed records may be archived via Oracle's Purge utilities.
    • Custom scripts often supplement standard cleanup.

Customization and Extensions

Organizations may extend this table for:
  • Additional Attributes: Custom columns for project tracking or regulatory requirements.
  • Validation Rules: PL/SQL triggers to enforce business logic before GL transfer.

Common Issues and Resolutions

  1. STP Failures: Investigate TRANSFER_STATUS='ERROR' records using associated error logs.
  2. Performance Bottlenecks: Optimize by partitioning large datasets or tuning SLA rules.

Conclusion

The IGI_STP_CANDIDATES_ALL table is a pivotal element in Oracle EBS's financial architecture, ensuring seamless subledger-to-GL integration. Its design supports scalability, auditability, and compliance, making it indispensable for organizations leveraging STP functionality. Proper configuration and monitoring of this table are essential for maintaining accurate financial reporting and operational efficiency.