The unique identifier for the requisition header associated with this requisition line. This field links the line to the overall requisition. Example: 1001 for requisition ID 1001.

A unique identifier for the requisition. It is used for insert, update, and delete operations in place of the RequisitionHeaderId. Example: 'REQ1001' could be a unique ID.

The identifier for the requisition header associated with this requisition line. This value connects the requisition line to the requisition it belongs to. Example: 12345.

A unique identifier for the individual requisition line. This is used to track a specific item or service requested in the requisition. Example: 001 for line 1 in the requisition.

A unique identifier for the requisition line. Used instead of RequisitionLineId for insert, update, and delete operations. Example: 'LINE1001'.

The sequential number assigned to the requisition line. It helps in ordering and referencing the requisition lines. Example: 1 for the first line, 2 for the second.

The identifier for the SmartForm associated with the requisition line. A SmartForm can help streamline data entry or automate processes. Example: 456 for a custom SmartForm.

The name of the SmartForm associated with this requisition line, used for identifying and organizing forms. Example: 'Basic Requisition Form'.

The identifier for the parent requisition line, used when there are dependent or related lines within the same requisition. Example: 1001 for the main item in the requisition.

The identifier for the line type of the requisition. This could categorize the line as a product, service, or another category. Example: 2 for a service line.

The code representing the requisition line type, helping to classify the line (for example, 'PROD' for products or 'SRVC' for services). Example: 'SRVC'.

A human-readable description of the requisition line type. This helps distinguish between different types of requisition lines. Example: 'Service' or 'Product'.

The source from which the requisition line originated. It could be manually created or sourced from an agreement or catalog. Example: 'Manual' or 'Catalog'.

The unique identifier for the category to which the requisition line belongs. Categories help in grouping items or services in the requisition. Example: 1001 for 'Office Supplies'.

The name of the category for the requisition line. This is used for easier classification and reporting. Example: 'Electronics'.

A description of the item or service being requested. This provides more details on what is being requisitioned. Example: 'Laptop computer with 15-inch screen'.

The unique identifier for the item in the item catalog. This links the requisition line to the item being requested. Example: 1234 for a specific product in the catalog.

The name or code of the item requested. This can be a short, recognizable description. Example: 'Laptop' or 'Office Chair'.

The revision number for the item, indicating if it has been updated or changed. Example: 'Rev A' or 'Rev B'.

The quantity of the item or service requested. This determines how many units are needed. Example: 10 for ten laptops.

An optional field to capture a secondary quantity in a different unit of measure. For example, if you order 10 boxes, this field could capture the quantity in individual items (for example, 100 items per box). Example: 100 for 10 boxes containing 100 units each.

The price per unit of the item or service being requested. This field reflects the negotiated or catalog price per unit. Example: 500 for $500 per laptop.

The currency code used for pricing in this requisition line, such as USD for US Dollars or EUR for Euros. Example: 'USD'.

The full name of the currency used in the requisition line. Example: 'US Dollar' or 'Euro'.

The unit of measure code that represents how the quantity is measured (for example, 'EA' for each, 'BOX' for box). Example: 'EA' for each.

The unit of measure that describes the quantity measurement. It could be 'Each', 'Box', or other units depending on the item. Example: 'Each'.

The unit of measure code for the secondary quantity if applicable. This might be used for alternate units like weight or volume. Example: 'KG' for kilograms.

The unit of measure for the secondary quantity. For example, you could specify weight in kilograms for an item that is ordered by each. Example: 'KG' for kilograms.

The type of conversion rate applied to convert between different currencies or units of measure. Example: 'Spot Rate' for current exchange rates.

The conversion rate type manually selected by the user, allowing for overrides. Example: 'User-Defined'.

The date the conversion rate is based on. This ensures the rate applies to the correct time period. Example: '2023-12-01'.

The rate at which quantities or currencies are converted. Example: 1.25 for converting USD to EUR.

The price at which the item is being requisitioned. This could reflect the standard price or a negotiated price. Example: 200 for $200 per item.

The current status of the requisition line, such as 'Open', 'Approved', or 'Closed'. Example: 'Open'.

A user-friendly value for displaying the line status in the system. This may provide more readable options than the status code. Example: 'Pending Approval'.

The total amount for the requisition line, calculated as Quantity x UnitPrice. Example: 5000 for 10 units at $500 each.

The amount for the requisition line expressed in the specified currency. Example: 5000 for 10 units at $500 each in USD.

Indicates whether the requisition line is marked as urgent, requiring expedited processing. Example: True for urgent items, False for regular items.

Indicates whether the requisition line price has been negotiated by the preparer. Example: True for negotiated prices.

Indicates whether the requisition line requires negotiation before approval. Example: True for items requiring special pricing or terms.

Indicates whether the requisition line will be paid using a procurement card. Example: True if using a corporate procurement card.

The code representing the type of source agreement for the requisition line. This helps identify whether the line is sourced from a blanket agreement, contract, or other sources. Example: 'BPA' for Blanket Purchase Agreement.

A human-readable description of the source agreement type for the requisition line. Example: 'Contract' or 'Blanket Purchase Agreement'.

The unique identifier for the source agreement header related to the requisition line. This links the requisition line to the original source agreement. Example: 1234 for the blanket agreement.

The name or description of the source agreement, which is the origin of the requisition line. Example: 'Office Supplies Contract'.

The unique identifier for the line within the source agreement associated with the requisition line. Example: 001 for the first line item in the source agreement.

The line number within the source agreement related to the requisition line. This helps track which specific line of the source agreement is being referenced. Example: 1 for the first line.

The unique identifier for the UN number associated with the requisition line. This is used for hazardous materials and safety classification. Example: 789 for a specific hazardous material.

The UN number associated with the requisition line, identifying dangerous goods for compliance purposes. Example: 'UN1234' for a specific hazardous material.

The identifier for the hazard class of the requisition line item, used for safety and regulatory purposes. Example: 10 for flammable liquids.

The name or classification of the hazard associated with the requisition line, for example, 'Flammable' or 'Corrosive'.

The code representing the hazard class of the requisition line. This is used in regulatory reporting and classification. Example: 'FL' for flammable materials.

The UNSPSC (United Nations Standard Products and Services Code) for the requisition line, used for categorizing goods and services. Example: '43211504' for computers.

The name of the manufacturer of the item in the requisition line. This helps identify the supplier of the item. Example: 'HP' for Hewlett Packard.

The manufacturer's part number for the item, used for tracking specific products. Example: 'HP1234' for a laptop part number.

Indicates whether the user has overridden the price from the Blanket Purchase Agreement (BPA) for the requisition line. Example: True if the price was adjusted.

Indicates whether the supplier for this requisition line is new. This can help track new supplier relationships. Example: True if the supplier is newly onboarded.

The unique identifier for the supplier associated with the requisition line. This links the requisition to the supplier’s details. Example: 1001 for 'ABC Supplies'.

The name of the supplier for the requisition line. Example: 'XYZ Electronics' or 'Global Supplies'.

The unique identifier for the supplier site associated with the requisition line, used to track where goods or services are provided. Example: 001 for 'XYZ Electronics - NY'.

The name or code of the supplier site, which refers to the specific location of the supplier. Example: 'XYZ Electronics - LA'.

The unique identifier for the supplier contact associated with the requisition line, used for communication. Example: 5678 for the main contact person.

The name of the supplier contact for the requisition line, used to communicate about the order. Example: 'John Doe' or 'Sarah Smith'.

The email address of the supplier contact for the requisition line, used for official correspondence. Example: '[email protected]'.

The phone number of the supplier contact for the requisition line, used for communication. Example: '(555) 123-4567'.

The fax number of the supplier contact for the requisition line, if applicable. Example: '(555) 987-6543'.

An additional email address for contacting the supplier, used for backups or secondary communication. Example: '[email protected]'.

The name of the suggested supplier for the requisition line, often used when the original supplier is unavailable. Example: 'ABC Corp' as an alternative to 'XYZ Electronics'.

The name of the suggested supplier site for the requisition line, used when recommending a different location for fulfillment. Example: 'ABC Corp - NY'.

The name of the suggested supplier contact for the requisition line, used for managing supplier relationships. Example: 'Jane Doe' for an alternative supplier contact.

The phone number of the suggested supplier contact, used to manage communication. Example: '(555) 444-5678'.

The fax number of the suggested supplier contact, if applicable. Example: '(555) 444-5679'.

The email address of the suggested supplier contact, used for backup communication. Example: '[email protected]'.

The item number assigned by the supplier for the requisition line, used for item identification. Example: 'ABC123' for a specific part number.

The unique identifier for the requester who initiated the requisition line. This links the requisition line to the individual who made the request. Example: 2345 for 'John Doe'.

The name of the requester who created the requisition line. Example: 'Jane Smith'.

The display name of the requester, which may be formatted differently for easier display. Example: 'Jane S.'

The email address of the requester, used for notifications and correspondence. Example: '[email protected]'.

The unique identifier for the suggested buyer for the requisition line. Example: 3456 for 'Mike Johnson'.

The name of the suggested buyer for the requisition line, often used when a buyer needs to be assigned. Example: 'Mike Johnson'.

The email address of the suggested buyer for the requisition line. Example: '[email protected]'.

The unique identifier for the buyer who modified the requisition line. Example: 4567 for 'Sarah Lee'.

The name of the buyer who last modified the requisition line. Example: 'Sarah Lee'.

The unique identifier for the buyer assigned to the requisition line for further action. Example: 5678 for 'Alex Patel'.

The name of the buyer assigned to manage the requisition line. Example: 'Alex Patel'.

The display name of the buyer assigned to the requisition line. Example: 'Alex P.'

The email address of the assigned buyer for the requisition line. Example: '[email protected]'.

The requested date for delivering the item or service in the requisition line. Example: '2023-06-15'.

The code representing the destination type for the requisition line (for example, 'WARE' for warehouse, 'STOR' for store). Example: 'WARE'.

A description of the destination type for the requisition line. Example: 'Warehouse' or 'Store'.

The unique identifier for the organization where the requisition line’s items are to be delivered. Example: 123 for 'XYZ Corp'.

The code representing the destination organization. Example: 'XYZ'.

The name or description of the destination organization for the requisition line. Example: 'XYZ Corp'.

The subinventory location within the destination organization where the requisition line’s items will be delivered. Example: 'Main Warehouse'.

Indicates whether the requisition line uses a one-time delivery location, typically for special or temporary addresses. Example: True if the delivery address is a one-time use address.

The unique identifier for the location to which the requisition line’s items are to be delivered. Example: 789 for 'Main Office'.

The code used to reference the specific delivery location for the requisition line. Example: 'NYC' for the New York office.

The full address where the requisition line’s items will be delivered. Example: '123 Main St, New York, NY 10001'.

A version of the delivery address formatted for display or printing. This is typically used for shipping or logistics. Example: '123 Main St, Suite 200, New York, NY 10001'.

A note for the buyer associated with the requisition line, often containing special instructions or clarifications about the purchase. Example: 'Please prioritize this order for immediate shipment.'

A note for the receiver of the requisition line’s items, typically containing handling or inspection instructions. Example: 'Inspect for damage before signing for receipt.'

A note for the supplier providing the requisition line’s items, often containing additional order specifications. Example: 'Please ensure packaging is eco-friendly.'

Indicates whether the requisition line is in a pool, awaiting further processing or approval. Example: 'Yes' if the line is in the approval pool.

The code representing the reason for failure in the purchase order automation process. This helps in troubleshooting automation issues. Example: 'PRICE_ERR' for pricing errors.

A detailed description of why the purchase order automation failed for the requisition line. Example: 'Price mismatch with the supplier catalog'.

The unique identifier for the purchase order header created from the requisition line, used to track the PO associated with the requisition. Example: 10234 for 'PO10234'.

The unique identifier for the purchase order line associated with the requisition line, helping to link the requisition to the created purchase order. Example: 1 for the first line in the PO.

The purchase order number generated for the requisition line. This number is used for tracking the order. Example: 'PO12345'.

The unique identifier for the buyer assigned to the purchase order for the requisition line. Example: 4001 for 'Alice Green'.

The name of the buyer responsible for the purchase order generated from the requisition line. Example: 'Alice Green'.

The name of the supplier listed on the purchase order associated with the requisition line. Example: 'ABC Electronics'.

The unique identifier for the procurement business unit handling the requisition line. Example: 5001 for 'Procurement Department'.

The name of the procurement business unit managing the requisition line. Example: 'Global Procurement'.

The code representing the source type for the requisition line, such as 'Manual' for manually created requisitions or 'Catalog' for items selected from a catalog. Example: 'Manual'.

The description of the source type for the requisition line, such as 'Manual' or 'Catalog'. Example: 'Catalog' for sourced items.

The unique identifier for the source organization where the requisition line originated. Example: 2001 for 'North America Sales'.

The code representing the source organization where the requisition line originated. Example: 'NAM' for North America.

The name or description of the organization from which the requisition line originated. Example: 'North America Sales'.

The subinventory where the requisition line originates, used for inventory tracking. Example: 'Main Warehouse'.

The unique identifier for the transfer order header associated with the requisition line, typically used for internal transfers. Example: 301 for 'Transfer Order 301'.

The transfer order number associated with the requisition line, used to track internal inventory transfers. Example: 'TO123'.

The unique identifier for the transfer order line related to the requisition line. Example: 1 for the first line in the transfer order.

The unique identifier for the negotiation header associated with the requisition line, indicating that the line was part of a negotiation process. Example: 400 for 'Neg-400'.

The description or name of the negotiation associated with the requisition line. Example: 'Supplier Negotiation for 2023 Electronics'.

The line number in the negotiation related to the requisition line. Example: 1 for the first line in the negotiation.

The response number associated with the requisition line in a negotiation process, helping track different offers. Example: 1 for the first response.

The line number of the response in the negotiation process. Example: 1 for the first line in the response.

Indicates whether the requisition line is currently under negotiation. Example: True if the item is under negotiation for better terms.

The unique identifier for the work order associated with the requisition line, used to track internal production or service orders. Example: 6001 for 'WO6001'.

The work order number associated with the requisition line. Example: 'WO12345'.

The unique identifier for the operation in the work order associated with the requisition line. Example: 101 for 'Operation 1'.

The sequence number for the operation in the work order, used for tracking work order progress. Example: 1 for the first operation.

The product or service associated with the work order operation for the requisition line. Example: 'Custom Widget'.

The subtype of the work order related to the requisition line, used for additional classification of work order types. Example: 'Assembly'.

Indicates whether the requisition line is linked to a back-to-back process, often used in supply chain to automatically create purchase orders from requisitions. Example: True if the line is back-to-back.

Indicates whether the requisition line is for a configured item that requires customization. Example: True for customized laptop configurations.

The unique identifier for the customer receiving the requisition line’s goods. Example: 7890 for 'Acme Corp'.

The name of the customer receiving the requisition line’s goods. Example: 'Acme Corp'.

The location ID where the requisition line’s items are to be delivered, typically used for multiple customer locations. Example: 101 for 'Main Office'.

The requested date for shipping the requisition line’s items. Example: '2023-05-15'.

The sales order line number associated with the requisition line, helping to track sales orders and their requisitions. Example: 'SO1234-1'.

The sales order number associated with the requisition line, linking the requisition to a customer order. Example: 'SO1234'.

The schedule number for the sales order associated with the requisition line. Example: 'SO1234-S1'.

The unique identifier for the customer to whom the goods in the requisition line are shipped. Example: 12345 for 'XYZ Corp'.

The name of the customer receiving the goods in the requisition line. Example: 'XYZ Corp'.

The code representing the service level agreement for the requisition line, indicating the level of service expected. Example: 'EXP' for expedited shipping.

The description of the service level associated with the requisition line. This could indicate the urgency or type of service provided. Example: 'Expedited' or 'Standard'.

The code representing the mode of transport for the requisition line, used to track how the goods are delivered. Example: 'AIR' for air transport.

The description of the transport mode for the requisition line. This provides details about how the goods are being delivered. Example: 'Air Freight' or 'Ground Shipping'.

The unique identifier for the carrier responsible for transporting the requisition line’s goods. Example: 2001 for 'FedEx'.

The name of the carrier responsible for shipping the requisition line’s goods. Example: 'FedEx' or 'UPS'.

The username or identifier of the user who created the requisition line. Example: 'JohnDoe' or 'JaneSmith'.

The date and time when the requisition line was created. This timestamp is important for tracking the requisition’s creation. Example: '2023-01-15 09:00:00'.

The username or identifier of the user who last updated the requisition line. Example: 'MikeBrown'.

The date and time when the requisition line was last modified. This helps track changes over time. Example: '2023-01-20 12:30:00'.

The date and time when the requisition line was last submitted for approval. Example: '2023-01-18 10:00:00'.

The date and time when the requisition line was last approved. Example: '2023-01-19 14:30:00'.

The original date and time when the requisition line was first submitted for approval. Example: '2023-01-15 09:00:00'.

The original date and time when the requisition line was first approved. Example: '2023-01-16 11:00:00'.

The date when the requisition line was canceled, indicating the end of its process. Example: '2023-01-20'.

The reason for canceling the requisition line, providing context for the cancellation. Example: 'Budget Constraints'.

The unique identifier for the purchase order instance created from the requisition line. This helps link requisition lines to generated POs. Example: 12345.

Indicates whether the requisition line is being actively processed by the buyer. Example: True if the buyer is handling the line.

A grouping identifier for requisition lines, often used to categorize lines with similar characteristics or processes. Example: 'Tech Equipment'.

The type of product requested in the requisition line, helping to classify the type of goods or services. Example: 'Hardware' or 'Software'.

The code used to represent the product type in the requisition line. Example: 'HW' for hardware or 'SW' for software.

The URL linking to an image of the product associated with the requisition line. Example: 'http://example.com/product123.jpg'.

An auxiliary identifier for the item assigned by the supplier, used for tracking products that may have additional identifiers. Example: 'AUX12345'.

Indicates whether autosourcing is disabled for the requisition line, preventing the system from automatically sourcing items. Example: True if autosourcing is turned off.

The address used for one-time deliveries. This is often used for special or temporary addresses. Example: '456 Temporary St, New York, NY'.

The lookup code representing the order type for the requisition line, indicating the type of purchase or service. Example: 'PURCHASE' for a standard purchase order.

The unique identifier for the buyer who returned the requisition line, usually due to issues with the order. Example: 7890 for 'Alice Green'.

The display name of the buyer who returned the requisition line. Example: 'Alice Green'.

The reason provided for returning the requisition line, indicating why it was rejected or returned. Example: 'Incorrect Product'.

The code representing the lifecycle status of the requisition line, which shows the current stage of processing. Example: 'OPEN', 'APPROVED'.

The display name of the requisition line’s lifecycle status, giving more context to the processing stage. Example: 'Approved' or 'In Review'.

The code representing the action required for the requisition line, such as 'Approve' or 'Review'. Example: 'APPROVE'.

The description of the action required for the requisition line, helping users understand what is needed. Example: 'Approval Needed' or 'Price Review'.

The reason for canceling the associated purchase order, if applicable. Example: 'Vendor Delayed Shipment'.

The reason the purchase order for the requisition line is placed on hold. Example: 'Payment Issue'.

The unique identifier for the public shopping list header associated with the requisition line, used for shared requisition lists. Example: 3210 for 'Public Shopping List'.

Indicates whether the information template has been modified for the requisition line. Example: True if the template was edited.

The code representing the funds status for the requisition line, indicating whether funds are available. Example: 'AVAILABLE' or 'INSUFFICIENT'.

The description of the funds status, helping to understand the availability of funds. Example: 'Available' or 'Not Approved'.

An additional status indicating the secondary stage of the requisition line’s lifecycle. Example: 'Under Review' or 'Awaiting Approval'.

Indicates whether the item was manually overridden by the user. Example: True if the user changed the item details.

Indicates whether the description for the BPA (Blanket Purchase Agreement) was overridden by the user. Example: True if the description was customized.

The unique identifier for the EPP (Enhanced Purchase Process) line associated with the requisition. Example: 45678 for the specific EPP line.

The unique identifier for the item in an external marketplace associated with the requisition line. Example: 'MARKET1234' for an item listed on a marketplace.

The concatenated code representing the transaction business category for the requisition line, used for classification and grouping purposes. Example: 'OFFICE-TECH' for office technology items.

The business category associated with the requisition line, providing an easy classification of the item or service being requisitioned. Example: 'Office Equipment' or 'Software'.

The code representing the business category of the requisition line for internal classification. Example: 'TECH' for technology items.

The code representing the taxation country for the requisition line, helping to determine tax rates and rules. Example: 'US' for the United States.

The concatenated code combining the document’s fiscal classification with the requisition line’s data, used for tax reporting. Example: 'TAX-USA' for items taxed in the U.S.

The code representing the fiscal classification of the product in the requisition line, used for tax reporting and compliance. Example: 'EXEMPT' for tax-exempt products.

The unique identifier for the fiscal classification of the product in the requisition line, helping with tax reporting and categorization. Example: 101 for 'Exempt Product'.

The concatenated code representing the product category associated with the requisition line, used for classification. Example: 'COMPUTER-HARDWARE'.

The code that defines the intended use for the requisitioned item, helping to categorize it for specific purposes. Example: 'OFFICE' for office use.

The unique identifier for the intended use of the requisition line’s item, linking the item to its specific use. Example: 5001 for 'Office Equipment'.

The user-defined fiscal classification code for the requisition line, allowing for customization in tax or accounting processes. Example: 'REGULAR' for standard tax rate items.

The tax classification code associated with the requisition line, used to apply the appropriate tax rules. Example: 'TAXABLE' for taxable goods.

The assessable value for tax purposes, used to calculate the amount that will be taxed. Example: 200 for an item with a taxable value of $200.

The tax registration ID for the first party involved in the transaction, used for tax reporting. Example: 12345 for 'ABC Corp'.

The tax registration ID for the third party involved in the transaction, if applicable. Example: 67890 for a third-party supplier.

The identifier for the location where the goods will be finally discharged or delivered, relevant for customs or taxation. Example: 1001 for 'Port of Los Angeles'.

The code representing the location of final discharge for the requisition line, typically used in shipping and logistics. Example: 'LA' for the 'Port of Los Angeles'.

The tax registration number for the first party involved in the transaction, typically used for tax compliance. Example: '123-456-7890'.

The cost center associated with the requisition line, used for budgeting and accounting purposes. Example: 'Sales Office'.

The intended use of the item requested in the requisition line, often used to justify the purchase. Example: 'Office Supplies' or 'Manufacturing Equipment'.

The fiscal classification of the product in the requisition line, which helps determine tax rates and rules. Example: 'Taxable' or 'Exempt'.

The tax registration number for a third party involved in the requisition line, used for compliance and tax reporting. Example: '987-654-3210'.

The user-defined classification for the requisition line, allowing for customized tax reporting or accounting. Example: 'Import Tax' or 'Local Tax'.

The fiscal classification code for the document associated with the requisition line, affecting tax treatment. Example: 'VAT'.

The description of the document’s fiscal classification, indicating how it should be treated for tax purposes. Example: 'Exempt' or 'Standard Rate'.

The country associated with the taxation of the requisition line, used to determine tax rates and apply country-specific rules. Example: 'USA' or 'Germany'.

The category to which the product belongs, used for classification and reporting purposes. Example: 'Electronics' or 'Furniture'.

The code representing the category of the product in the requisition line, helping to classify it for accounting and procurement purposes. Example: 'EL' for Electronics.

The classification that determines how the requisition line is taxed, used to ensure compliance with tax laws. Example: 'Sales Tax' or 'Exempt'.

Indicates whether the user has overridden the tax attributes for the requisition line. Example: True if the user modified the tax classification.

The unique identifier for the suggested procurement business unit for the requisition line, guiding where the procurement will occur. Example: 4001 for 'Central Procurement'.

This field is for insert operations only. For updates or deletions, use operations on the child table. This field is typically used to reference a template for item or requisition details.

This field is for insert operations only. For updates or deletions, use operations on the child table. This is a reference to a descriptive flexfield for capturing custom data.

This field is for insert operations only. For updates or deletions, use operations on the child table. This field tracks special handling requirements for the requisition line.

This field is for insert operations only. For updates or deletions, use operations on the child table. It links the requisition line to any distribution-related data or financial postings.

The unique identifier for the preparer, used to link the requisition line to the user who created it. Example: 5001 for 'John Doe'.

The unique identifier for the requisition header, helping to link the requisition line to its parent header record. Example: 2001 for 'Requisition 2001'.

A reference field used for searching requisition lines within the system, allowing users to filter and locate specific requisitions. Example: 'Search by Item'.

The reference number linking child aggregates with their parent tables, ensuring data integrity between the requisition lines and parent records. Example: 1001 for 'Requisition Line 1'.

The date from which the requisition line is considered effective. This is typically used to filter records by date range or to apply business logic. Example: '2023-01-01'.