PurchaseRequisitionslinesDFF
Provides descriptive flexfields for requisition lines, capturing unique data like internal codes or cost justification details.
Columns
| Name | Type | Description |
| PurchaseRequisitionsRequisitionHeaderId [KEY] | Long | The unique identifier for the requisition header associated with the descriptive flexfield (DFF) data, linking the DFF data to a specific requisition. Example: 1001 for Requisition 1001. |
| LinesRequisitionLineId [KEY] | Long | The unique identifier for the requisition line within the requisition header, linking the DFF data to a specific requisition line. Example: 2001 for Line 1. |
| RequisitionLineId [KEY] | Long | A unique identifier for the requisition line, used to track a specific line item in the requisition. Example: 3001 for Line ID 3001. |
| _FLEX_Context | String | The DFF context name, which is used to categorize or provide additional details for the purchase requisition distributions. Example: 'PurchaseOrder' or 'MaterialRequest'. |
| _FLEX_Context_DisplayValue | String | The display value of the descriptive flexfield context, which provides a human-readable version of the context. Example: 'Purchase Order Distribution' or 'Material Request Distribution'. |
| BindPreparerId | Long | The unique identifier for the preparer who created the requisition line, helping to link the DFF data to the preparer's record. Example: 123 for 'John Doe'. |
| BindRequisitionHeaderId | Long | The unique identifier for the requisition header, linking the DFF data to the specific requisition it belongs to. Example: 2001 for 'Requisition Header 2001'. |
| Finder | String | A placeholder or reference used for searching and locating the DFF data associated with requisition lines. Example: 'Search by Line ID' or 'Search by Category'. |
| RequisitionHeaderId | Long | The identifier for the requisition header, used to link the DFF data to the parent requisition record. Example: 1001 for Requisition Header 1001. |
| CUReferenceNumber | Int | The reference number used to map the child aggregates (such as DFF data) to their parent requisition or requisition line, ensuring data integrity. Example: 2001 for 'Requisition Line 1'. |
| EffectiveDate | Date | The date from which the DFF data is considered effective. This is typically used to filter records based on the validity of the data. Example: '2023-01-01' for data valid from the beginning of the year. |