Search Results destination_organization_id




The PO.PO_DISTRIBUTIONS_DRAFT_ALL table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 serves as a critical intermediary storage for purchase order (PO) distribution line data during the requisition-to-PO conversion process or when modifying existing POs in draft mode. This table temporarily holds distribution-level information before final submission, ensuring data integrity and auditability during PO lifecycle management. ### **Table Purpose and Functional Context** In Oracle Procurement, the PO_DISTRIBUTIONS_DRAFT_ALL table acts as a staging area for distribution lines when users create or modify POs in "draft" status. Unlike the permanent PO_DISTRIBUTIONS_ALL table, this draft table stores uncommitted changes, allowing users to save incomplete work without affecting live procurement data. Key scenarios include: - **Requisition Conversion**: Distribution lines from requisitions are staged here before PO creation. - **PO Modifications**: Edits to existing POs (e.g., quantity, account coding) are held in draft until approved. - **Multi-Org Support**: The _ALL suffix indicates it stores data across operating units, filtered by ORG_ID. ### **Key Columns and Relationships** The table’s structure aligns with PO_DISTRIBUTIONS_ALL, with additional draft-specific columns: 1. **Primary Keys and References**: - DISTRIBUTION_ID: Unique identifier for the draft distribution line. - PO_DISTRIBUTION_ID: Links to the corresponding distribution in PO_DISTRIBUTIONS_ALL (for edits). - PO_HEADER_ID/PO_LINE_ID: References the draft PO header/line in PO_HEADERS_DRAFT_ALL and PO_LINES_DRAFT_ALL. 2. **Financial and Quantity Attributes**: - QUANTITY, AMOUNT: Temporary values for uncommitted changes. - CHARGE_ACCOUNT_ID: Draft accounting flexfield data (e.g., GL code combination). - DESTINATION_TYPE_CODE: Defines inventory/expense destinations (e.g., "INVENTORY", "EXPENSE"). 3. **Draft-Specific Metadata**: - DRAFT_ID: Ties the distribution to a specific draft session (from PO_DRAFTS). - ACTION: Indicates if the record is for creation (INSERT), update (UPDATE), or deletion (DELETE). - CHANGE_FLAG: Tracks modifications (e.g., "U" for updated). ### **Integration with Oracle Modules** - **General Ledger (GL)**: Validates draft accounting segments before submission. - **Inventory (INV)**: Validates item-related distributions (e.g., subinventory, locator). - **Projects (PA)**: Supports project-funded distributions via PROJECT_ID/TASK_ID. ### **Data Flow and Lifecycle** 1. **Draft Creation**: Data populates during PO entry or requisition import. 2. **Validation**: Checks against Oracle’s approval workflows and accounting rules. 3. **Submission**: On approval, data migrates to PO_DISTRIBUTIONS_ALL; draft records are purged. ### **Customization Considerations** - **APIs**: Use PO_DRAFT_API_PVT for programmatic draft management. - **Audit Trails**: Draft tables log changes via LAST_UPDATE_DATE/LAST_UPDATED_BY. - **Performance**: Indexes on DRAFT_ID and PO_DISTRIBUTION_ID optimize large-scale drafts. ### **Conclusion** The PO_DISTRIBUTIONS_DRAFT_ALL table is pivotal in Oracle EBS Procurement, enabling flexible, auditable PO workflows. Its transient nature ensures data consistency while supporting multi-org and multi-module integrations. Understanding its schema and lifecycle is essential for customization, reporting, and troubleshooting in EBS 12.1.1/12.2.2 environments.