Search Results cadastro de produtos no sistema




The PO_ATT_TMP_RECORDS table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a temporary storage table used within the Purchasing (PO) module to manage attachment-related data during transaction processing. This table plays a critical role in handling document attachments associated with purchase orders, requisitions, and other procurement documents before they are permanently stored in the primary attachment repository (FND_ATTACHED_DOCUMENTS and related tables). Below is a detailed analysis of its purpose, structure, and functional significance.

Purpose and Functional Context

The PO_ATT_TMP_RECORDS table acts as an intermediary staging area for attachment metadata during the creation or modification of procurement documents. When users attach files (e.g., PDFs, images, or spreadsheets) to purchase orders or requisitions, the system temporarily stores transactional data in this table before final validation and persistence. This design ensures data integrity by segregating in-progress attachments from committed records, reducing the risk of orphaned or partially processed attachments.

Key Columns and Structure

While the exact schema may vary slightly between EBS 12.1.1 and 12.2.2, the table typically includes the following columns:
  • RECORD_ID: Primary key, often a sequence-generated unique identifier.
  • DOCUMENT_ID: References the attached file's metadata in FND_DOCUMNS.
  • ENTITY_NAME: Specifies the entity type (e.g., PO_HEADERS, REQUISITION_HEADERS).
  • PK1_VALUE: Foreign key value linking to the parent record (e.g., PO_HEADER_ID).
  • CREATION_DATE, CREATED_BY: Audit columns tracking record origination.
  • STATUS_FLAG: Indicates processing state (e.g., 'PENDING', 'PROCESSED', 'ERROR').

Integration with Attachment Framework

Oracle EBS leverages the FND_ATTACHED_DOCUMENTS framework for document management. The PO_ATT_TMP_RECORDS table interfaces with this framework as follows:
  1. Staging: During document upload, metadata populates PO_ATT_TMP_RECORDS while the physical file is stored in a designated directory or database blob (FND_LOBS).
  2. Validation: The system validates entity relationships and user permissions before committing.
  3. Commit: Upon successful validation, records migrate to FND_ATTACHED_DOCUMENTS, and temporary entries are purged.

Performance and Maintenance Considerations

Administrators should monitor this table for:
  • Orphaned Records: Entries with STATUS_FLAG='ERROR' may require manual cleanup.
  • Indexing: Ensure indexes exist on RECORD_ID, PK1_VALUE, and STATUS_FLAG for efficient queries.
  • Purge Jobs: Implement scheduled jobs to delete processed records (>30 days old) to prevent table bloating.

Customization and Extensions

In custom implementations, this table may be extended to:
  • Add columns for custom entity types or additional metadata.
  • Integrate with third-party document management systems via APIs.
  • Support multi-language attachment descriptions through FND_DOCUMNS_TL.

Conclusion

The PO_ATT_TMP_RECORDS table is a pivotal component in Oracle EBS's procurement attachment workflow, ensuring transactional consistency and data integrity. Its temporary nature optimizes performance while maintaining referential accuracy. Proper understanding of this table aids in troubleshooting attachment issues, optimizing purge strategies, and extending functionality for business-specific requirements.