Search Results supplier sites table in ebs




The WIP_BIS_PROD_DEPT_YIELD_TEMP table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a temporary staging table primarily used within the Work in Process (WIP) module to support Business Intelligence System (BIS) reporting for departmental yield analysis. This table plays a critical role in aggregating and processing transactional data before it is transformed into meaningful yield metrics for manufacturing departments. Below is a detailed technical and functional breakdown of its purpose, structure, and integration within Oracle EBS.

Functional Overview

The WIP_BIS_PROD_DEPT_YIELD_TEMP table acts as an intermediary data store for yield-related calculations at the departmental level. It captures key performance indicators (KPIs) such as:
  • Units started, completed, and scrapped
  • Yield percentages (good units vs. total units processed)
  • Department-specific efficiency metrics
This data is later consumed by Oracle BIS or custom analytics tools to generate yield trend reports, identify bottlenecks, and optimize production workflows.

Technical Structure

The table typically includes the following columns (exact schema may vary by EBS version):
  • ORGANIZATION_ID: Identifies the inventory organization.
  • DEPARTMENT_ID: Links to the WIP department (from WIP_DEPARTMENTS).
  • PRODUCTION_LINE_ID: Associates data with a manufacturing line.
  • ITEM_ID: References the manufactured item (from MTL_SYSTEM_ITEMS_B).
  • TRANSACTION_DATE: Timestamp for yield calculations.
  • START_QUANTITY, COMPLETED_QUANTITY, SCRAP_QUANTITY: Quantities used for yield computation.
  • YIELD_PERCENTAGE: Derived field calculated as (Completed Quantity / (Completed Quantity + Scrap Quantity)).
  • TEMP_FLAG: Indicates whether records are pending processing (often purged after BIS jobs run).

Integration with Oracle EBS Modules

  1. Work in Process (WIP): Receives transactional data from WIP move transactions, completions, and scrap entries via APIs or concurrent programs.
  2. Inventory (INV): Validates item and organization references.
  3. Cost Management (CST): May integrate with yield-based cost analysis.
  4. Oracle BIS: Serves as a data source for pre-configured yield dashboards and ad-hoc queries.

Data Flow

  1. Data is populated via EBS concurrent programs (e.g., "WIP Yield Analysis Collection").
  2. Intermediate processing may involve PL/SQL packages like WIP_BIS_YIELD_PKG.
  3. Processed records are either archived or purged to maintain performance.

Customization Considerations

  • Indexing: Additional indexes on ORGANIZATION_ID and TRANSACTION_DATE may improve query performance.
  • Partitioning: Recommended for high-volume manufacturing environments.
  • Extensions: Custom columns can be added for site-specific KPIs, but require modifications to feeder programs.

Performance Implications

  • Table growth should be monitored—automated purges are critical.
  • Concurrent program scheduling during off-peak hours is advised.

Conclusion

The WIP_BIS_PROD_DEPT_YIELD_TEMP table is a specialized component of Oracle EBS's manufacturing analytics framework. Its design supports real-time yield monitoring while maintaining separation from transactional systems. Proper configuration ensures accurate reporting without impacting production operations.