Requisition Line Item Detail Download
This integration downloads detail-level requisition information for the purpose of Approvals and/or Update Purchase Order (PO) numbers. This information includes Work Orders (WO), Work Order Revisions (WOR), Statements of Work (SOW), and Statement of Work Revisions (SOWR). This connector differs from the Requisition Detail Download in that it adds SOW characteristic details.
Each payment characteristic is added as a separate line and its corresponding details is sourced from the SOW. There is the ability to add custom fields, leverage sequence/line numbers, accounting from the line objects, etc. This gives customers the flexibility to replicate the SOW detail and match to these lines during invoicing.
This is the first step in a two-step process. See the Work Flow section of this document for details.
Triggering Events
The Work Order/Work Order revision will be pulled in the download if it’s in Pending External Acceptance status. In the case of SOW/SOW the object would be pulled when the status is Pending Buyer Response and is on the same level of the Integration Approver User.
Parameters
SAP Fieldglass will require parameters to be passed in order to pull download details.
The following parameters will be passed to specify the details that should be downloaded.
|
Parameter 1 values: |
Action |
|---|---|
|
1 |
Only work order details will be downloaded |
|
2 |
Only SOW details will be downloaded |
|
3 |
Both Work Order and SOW details will be downloaded |
|
Parameter 2 values: |
Action |
|---|---|
|
All |
All SOW/work order details will be downloaded |
|
Object ID |
Only SOW/work order details for specified Object ID is downloaded. Example: xxxxWO00000012 |
Work Flow
There are two steps in the Approval/PO integration:
-
Batch Approval Request – SAP Fieldglass sends the WO/SOW (Work Order/Statement of Work) record and locks the object to prevent approvals.
-
Batch Status Update – The client sends the status back to SAP Fieldglass (either approval or rejection) and a PO Number (if required). The approval/rejection is completed and the object is unlocked.
A role associated with the last approval level should be created. A non-native role is required, due to the need for backend association. The role name should be meaningful and self-explanatory to the end-user community.
When the WO/WOR is accepted by the supplier and the status is set to Pending External Acceptance, the object will lock and it is at this time that the record should pull down in the download. When SOW/SOWR is accepted by supplier, the SOW status is set to Response Pending Approval, the SOW will lock, and it is at this time that the record will be pulled down in the download. A punch-out account will be created for SOW/SOWR modules to lock the object once its status is on the last level of Response Pending Approval.
For SAP Fieldglass objects that contains multiple cost centers, multiple records will be sent, one for each cost center.
SAP Fieldglass supports approval for each WO, WOR (Work Order Revision), SOW, and SOWR (Statement of Work Revision) transaction by including the object in the Requisition Line Item Detail Download.
When the final Status Update is returned, the status of the WO, WOR, SOW, or SOWR is updated to the next approval status and the history of the approval is updated in the SAP Fieldglass Integration Audit Trail. For the initial WO and SOW, the PO# is returned as well.
File Formatting
Custom Fields
The download may include custom fields from the various modules shown below.
-
Business Unit
-
Buyer
-
Cost Center
-
Event
-
Fee Definition
-
Management Event
-
Schedule
-
SOW
-
SOW Revision
-
Supplier
-
Work Order
-
Work Order Revision
General Conventions
Object information will appear in the download if a triggering event has occurred since the last time the download was run. The Last Run Date is stored in SAP Fieldglass each time the connector is successfully run. Therefore, the download will pull any records that have changed since Last Run Date. In the event that previous data is required again, you can contact your SAP Fieldglass representative and they can update this date to the date you request.
This is a multi-line download, if an object is associated with more than one cost center object, information is downloaded in more than one record.
Assumptions/Tips
-
If ‘Hours/Days for Estimated and Committed Spend’ Job Posting Template rule is set as ‘Creator Enters’ and Rate Unit of Job Posting is Hr or Day, ‘Hours for Committed Spend’ of Work Order should get downloaded as ‘Total Hours’. If ‘Hours/Days for Estimated and Committed Spend’ Job Posting Template rule is set as ‘System Calculates’, ‘Total Estimated Hours’ should get downloaded as ‘Total Hours’.
-
If the buyer company has multiple MSPs, when the MSP supplier user downloads records, they see only records for their MSP.
-
Fee Definitions appear in every download regardless of utilization.
-
An error occurs if the cost center defined at the header level is different from the one at the line item level, unless the rule 'Add and Remove Cost center while editing cost allocation' is enabled OR the SOW is in draft status.
-
The company configuration 'Data Set' must be enabled in order for the field '[s] Event Hierarchy Contract Segment Name' to work as intended.
-
The system includes any inactive cost centers associated with the document.