Search Results po_requisition_lines_all

The PO_REQUISITION_LINES_ALL table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical entity within the Purchasing module, serving as the foundation for requisition line-level data. This table stores detailed information about individual requisition lines, which are components of purchase requisitions. A purchase requisition is a formal request for goods or services, and each requisition can contain multiple lines, each representing a distinct item or service being requested. The PO_REQUISITION_LINES_ALL table is designed to support multi-organization structures, as indicated by the "_ALL" suffix, which means it contains data across all operating units when Multi-Org is enabled. ### Key Columns and Their Significance 1. **REQUISITION_LINE_ID**: The primary key, uniquely identifying each requisition line. 2. **REQUISITION_HEADER_ID**: Foreign key linking to PO_REQUISITION_HEADERS_ALL, associating the line with its parent requisition. 3. **LINE_NUM**: The sequence number of the line within the requisition. 4. **ITEM_ID**: References MTL_SYSTEM_ITEMS_B for catalog items; null for non-catalog requests. 5. **ITEM_DESCRIPTION**: Free-text description of the requested item or service. 6. **CATEGORY_ID**: Links to MTL_CATEGORIES_B, categorizing the item for reporting and approval routing. 7. **UNIT_MEAS_LOOKUP_CODE**: The unit of measure (e.g., EA, KG) from FND_LOOKUP_VALUES. 8. **UNIT_PRICE**: The expected price per unit, used for budgeting and approval checks. 9. **QUANTITY**: The requested quantity of the item or service. 10. **NEED_BY_DATE**: The date by which the item is required. 11. **DESTINATION_TYPE_CODE**: Determines whether the item is for inventory ("INVENTORY"), expense ("EXPENSE"), or other destinations. 12. **DESTINATION_ORGANIZATION_ID**: For inventory items, specifies the target inventory organization. 13. **SOURCE_TYPE_CODE**: Indicates if the item is sourced from a supplier ("VENDOR"), inventory ("INVENTORY"), or other sources. 14. **SOURCE_ORGANIZATION_ID**: For inventory transfers, specifies the source inventory organization. 15. **VENDOR_ID**: References PO_VENDORS if a specific supplier is preferred. 16. **VENDOR_SITE_ID**: Specifies the supplier site from PO_VENDOR_SITES_ALL. 17. **CHARGE_ACCOUNT_ID**: Links to GL_CODE_COMBINATIONS for accounting purposes. ### Functional Workflow Integration The PO_REQUISITION_LINES_ALL table integrates with Oracle EBS workflows for approvals, sourcing, and procurement. Requisition lines are subject to approval hierarchies based on amount, category, or other rules. Once approved, they may be converted into purchase orders (POs) or aggregated into blanket agreements. The table also interfaces with Oracle Inventory, General Ledger, and Supplier modules, ensuring data consistency across procurement-to-pay processes. ### Customizations and Extensions Customizations often extend this table via descriptive flexfields (DFFs) or by adding columns to support unique business requirements, such as project-specific attributes or regulatory compliance fields. Performance tuning (e.g., indexing on REQUISITION_HEADER_ID or ITEM_ID) is common in high-volume environments. ### Data Security and Access Access to PO_REQUISITION_LINES_ALL is controlled via Oracle's Multi-Org and data security policies. Views like PO_REQUISITION_LINES_V provide filtered access based on user responsibilities. In summary, PO_REQUISITION_LINES_ALL is a cornerstone of Oracle Purchasing, enabling granular control over requisitioning processes while maintaining integration with financial, inventory, and supplier systems.