Requisition Header DFFs Not Exposed in Search Index for Redwood Process Requisitions Search Views
We are currently evaluating the new 26A feature: "Redwood: Configure Search Views for Purchase Orders, Purchase Agreements, and Process Requisitions" and are trying to understand the supported behavior for requisition header DFFs within the fa-prc-por search index.
Our current setup is as follows:
At the requisition level, we have a Requisition Header DFF configured under:
- POR_REQUISITION_HEADERS
- Table Column: ATTRIBUTE4
- Segment Name: Reference/PO
At the PO level, we have a corresponding PO Header DFF configured under:
- PO_HEADERS
- Table Column: ATTRIBUTE4
- Segment Name: Reference
Although the segment names differ, both DFFs use the same underlying table column (ATTRIBUTE4) and are intentionally mapped together. During requisition to PO creation, the value entered into the requisition header DFF propagates downstream into the PO header DFF successfully through the PO_COPY_REQ_HDR_DFF_TO_PO profile option.