Search Results what is mt-access in rrc setup request




The FND_CONC_REQ_OUTPUTS table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical repository for managing concurrent request output files generated by the Concurrent Processing framework. This table stores metadata about output files, including their locations, formats, and associations with specific concurrent requests. Below is a detailed analysis of its structure, functionality, and significance in Oracle EBS.

1. Purpose and Role

The FND_CONC_REQ_OUTPUTS table serves as a central repository for tracking output files generated by concurrent programs. Each time a concurrent request executes, it may produce one or more output files (e.g., reports, logs, or data extracts). This table maintains references to these files, enabling users and applications to retrieve them efficiently. It acts as a bridge between the concurrent manager and the file system or database where outputs are stored.

2. Key Columns and Structure

The table includes several important columns:
  • REQUEST_ID: Foreign key linking to FND_CONCURRENT_REQUESTS, identifying the parent concurrent request.
  • OUTPUT_FILE_ID: Primary key uniquely identifying each output file.
  • FILE_NAME: The name of the output file (e.g., report.txt or output.pdf).
  • FILE_DATA: In some configurations, this BLOB column stores the actual file content (if stored in the database).
  • FILE_FORMAT: Indicates the file format (e.g., TEXT, PDF, HTML).
  • CREATION_DATE: Timestamp of file generation.
  • NODE_NAME: Identifies the server node where the file was created.
  • TRANSFER_STATUS: Tracks whether the file was successfully transferred to a designated location (e.g., PENDING, COMPLETED).

3. Integration with Concurrent Processing

When a concurrent request completes, the Concurrent Manager updates FND_CONC_REQ_OUTPUTS with details of the generated outputs. The table interacts with other key EBS components:
  • FND_CONCURRENT_REQUESTS: Provides request details (e.g., phase, status).
  • FND_CONCURRENT_PROGRAMS: Defines the program associated with the output.
  • FND_FILE: Oracle's utility package for file I/O operations, often used to read/write outputs referenced in this table.

4. Output Storage Mechanisms

Outputs can be stored in two ways:
  1. File System: Files are written to directories specified by the APPLCSF (Application Top Concurrent Processing Log/Temp Directory) or custom paths. The table stores file paths for retrieval.
  2. Database (BLOB): For smaller files or specific configurations, outputs may be stored directly in the FILE_DATA column.

5. Common Use Cases

  • Report Generation: PDF or text reports from concurrent programs are logged here.
  • Log Files: Debug or execution logs for troubleshooting.
  • Data Exports: Outputs from data extraction programs (e.g., CSV files).
  • Integration: External systems query this table to fetch outputs via APIs or direct SQL.

6. Administration and Maintenance

Administrators should:
  • Monitor table growth, as BLOB storage can consume significant space.
  • Purge obsolete entries using FND_CONCURRENT_REQUESTS cleanup utilities.
  • Ensure proper filesystem permissions for output directories.

7. Performance Considerations

Indexes on REQUEST_ID and OUTPUT_FILE_ID optimize query performance. For high-volume environments, consider partitioning or archiving historical data.

8. Differences in EBS 12.1.1 vs. 12.2.2

While the core structure remains consistent, EBS 12.2.2 may include enhancements:
  • Improved BLOB handling for larger files.
  • Additional columns for cloud or multi-node environments.
  • Tighter integration with Oracle WebLogic in 12.2.2.

Conclusion

The FND_CONC_REQ_OUTPUTS table is indispensable for managing concurrent request outputs in Oracle EBS. Its design ensures traceability, accessibility, and scalability, supporting critical reporting and data processing workflows. Proper understanding of this table aids in troubleshooting, auditing, and optimizing concurrent processing operations.