Search Results batch




The GML.GML_BATCH_TMP table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 serves as a temporary storage structure within the Global Manufacturing and Logistics (GML) module. This table is primarily utilized during batch processing operations to temporarily hold data before it is validated, processed, or transferred to permanent tables. The design aligns with Oracle EBS's architecture, where temporary tables optimize performance by reducing contention on transactional tables during high-volume data operations.

Purpose and Functionality

The GML.GML_BATCH_TMP table acts as an intermediary in batch-oriented processes, such as inventory transactions, material movements, or production reconciliations. It enables the system to stage data before applying business rules, validations, or posting to permanent tables like GML_BATCH_HEADER or GML_BATCH_DETAILS. This approach minimizes locking issues and improves throughput in high-transaction environments.

Key Attributes

While the exact schema may vary based on customizations, the table typically includes the following columns:
  • BATCH_ID: A unique identifier for the batch process.
  • TRANSACTION_TYPE: Specifies the operation (e.g., "ISSUE," "RECEIPT").
  • ITEM_CODE: References the item involved in the transaction.
  • QUANTITY: Stores provisional quantities before validation.
  • STATUS_FLAG: Indicates processing state (e.g., "PENDING," "PROCESSED").
  • CREATION_DATE: Timestamp for audit purposes.
  • ERROR_MESSAGE: Captures validation failures during processing.

Integration with Oracle EBS Modules

The table interacts with core EBS functionalities:
  1. Inventory Management (INV): Temporarily holds unposted material transactions.
  2. Cost Management (CST): Stages cost adjustments before final accounting entries.
  3. Work in Process (WIP): Buffers production batch data before updating shop floor records.

Technical Considerations

  • Performance: Indexes on BATCH_ID and STATUS_FLAG optimize batch job performance.
  • Purging Mechanism: Scheduled concurrent programs typically truncate processed records to maintain efficiency.
  • Partitioning: In high-volume implementations, partitioning by CREATION_DATE may be implemented.

Customization Scenarios

Implementations often extend the table with client-specific columns like CUSTOMER_REFERENCE or PROJECT_CODE to support specialized workflows. Such modifications require careful impact analysis to avoid conflicts with standard batch processing programs.

Security Model

Access is typically restricted to:
  • GML module responsibilities
  • Batch processing concurrent programs
  • Database triggers enforcing data integrity

Migration Implications

Between EBS 12.1.1 and 12.2.2, the table structure generally remains consistent, but 12.2.2 may introduce:
  • Enhanced auditing columns for GDPR compliance
  • JSON-type columns for flexible attribute storage
  • Integration with Oracle Fusion Middleware for web service-based batch processing
The GML.GML_BATCH_TMP table exemplifies Oracle EBS's approach to handling batch data with efficiency and reliability, serving as a critical component in manufacturing and logistics operations.