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.

Connector Overview

Component

Detail

Company Type

Buyer

Version Type

1.0

Format

CSV

Prerequisites

Company Details Setting must be turned on for Integration – Requisition Line Item Detail Download.

User role permission must be turned on for Upload Data and Download Data.

Predecessors

Work Orders

Statement Of Works

Related Connectors

Requisition Response Upload

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:

  1. Batch Approval Request – SAP Fieldglass sends the WO/SOW (Work Order/Statement of Work) record and locks the object to prevent approvals.

  2. 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

Detail

Column Header Name

Data Type

Length

Enabled by Default?

Value(s)/Format

Description/Use/Field Rules

Object ID Text 16 Yes

Examples:

XXXXWO00000001

XXXXTQ00000007

SAP Fieldglass Work Order or SOW object reference.
Revision Number Yes

Example:

0

Revision number corresponding to the object reference.

Description

Text

200

Yes

Examples:

Tester Level 1

Q3 Infrastructure Refresh

Job Posting Title or SOW Name

Status

Text

100

No

SAP Fieldglass SOW/Work Order Status

External ID

Text

100

No

Example:

Client123

An external identifier used by the client for tracking purposes.

Buyer Ref

Text

100

No

Buyer reference

Master SOW Ref

Text

16

No

Example:

XXXXTQ00000007

SAP Fieldglass Master SOW ID.

Master SOW External Ref

Text

100

No

An external identifier for Master SOW used by the client for tracking purposes.

Master SOW

Text

3

No

Valid values are:

Yes

No

Indicates if Object Id refers to a Master SOW.

Master SOW PO Number

Text

100

No

Optional purchase order number from the Master SOW.

Object Owner Username

Text

100

No

Valid SAP Fieldglass username

Username of object owner, latest revision.

Object Owner Employee ID

Text

100

No

Employee ID of Work Order/SOW owner, latest revision.

Object Creator Username

Text

100

No

Valid SAP Fieldglass username

Username of object creator, latest revision

Object Creator Employee ID

Text

100

No

Employee ID of Work Order/SOW creator, latest revision.

Object Create Date

Date

Yes

Example:

12/04/2016

The date the SOW/Work Order was created.

Object Start Date

Date

Yes

Example:

12/05/2016

Start date of the Work Order/SOW.

Indicates the latest revision start date.

Object End Date

Date

Yes

Example:

12/06/2016

End date of the Work Order/SOW.

Indicates the latest revision end date.

Actual End Date

Date

No

Example:

12/07/2016

When the SOW is closed, this field indicates when the SOW needs to be closed

Closed Reason

Text

100

No

Closed reason for SOW/Work Order

Supplier Code

Text

6

Yes

Valid SAP Fieldglass supplier code for the buyer.

Example:

SUP1

Supplier Code for the SOW/Work Order

Vendor ID

Text

100

No

Example:

92200593

The Vendor ID value associated to the Supplier

Remit to Address Code

Text

100

No

Valid SAP Fieldglass Remit To Address Code

Remit to address (if any) specified by the Supplier on the Work Order/SOW.

Site Code

Text

100

Yes

Valid SAP Fieldglass Site Code

SAP Fieldglass Site object for SOW/Work Order, latest revision.

Location Code

Text

100

No

Valid SAP Fieldglass Location Code

SAP Fieldglass Location object for SOW/Work Order, latest revision.

Business Unit Code

Text

100

Yes

Valid SAP Fieldglass Business Unit Code

SAP Fieldglass Business Unit Code.

Primary Cost Center Code

Text

200

Yes

Valid SAP Fieldglass Cost Center Code

Primary Cost Center Code identified on the SOW.

Primary Cost Center Name

Text

200

No

Valid SAP Fieldglass Cost Center Name Primary Cost Center Name identified on the SOW.

Account Category

Text

100

No

Identifies the type of Cost Center: Internal Order, Cost Center, WBS Element.

Cost Center Allocation Amount

Decimal

No

Example:

1234567.89

Indicates amount to be allocated to cost center if not using allocation percentages.

Applicable for SOW Work Orders only.

Allocation %

Decimal

Yes

Example:

50.000

Allocation % is the percent value for whichever object (Cost Center % or GLA % or SOD %) is driving the cost allocation.

If company configuration 'Cost Allocation Percentage decimal precision' is enabled, this field shows zeros beyond the precision value set digit.

Applicable for SOW Work Orders only.

Primary Cost Center Owner Employee ID

Text

100

No

Employee ID of the primary cost center owner.

General Ledger Account

Text

100

No

Valid SAP Fieldglass GL Account

Example:

ABCDE

Pass the GL Account for Cost Center associated.

This field only appears if company configuration ‘GLA allocation on job postings and statements of work is required’ is enabled.

Segment Object Detail

Text

2000

No

Examples:

IS|Admin|12001

IS-Admin-12001

IS;Admin;12001

IS:Admin:12001

Segmented Object Detail string.

Segments will be separated by delimiter on the Segmented Object.

Valid delimiters are colon (:), semi-colon (;), pipe (|), and dash (-).

Required if ‘Segmented object detail’ configuration set.

More than one string can appear for a cost center.

Legal Entity Code

Text

100

No

Valid SAP Fieldglass Legal Entity Code

Legal Entity Code related to the SOW or the Work Order, latest revision.

Required if 'Use legal entity' configuration set.

Legal Entity Name

Text

100

No

Valid SAP Fieldglass Legal Entity Name

Legal Entity Name related to the SOW or the Work Order, latest revision

PO Number

Text

100

No

Populated with the value of the SAP Fieldglass PO Number field where populated.

Committed Spend

Decimal

Yes

Example:

1234567.89

Amount of committed spend/revised committed spend excluding tax or adjustment for Work Order

or

the Maximum Budget Amount (without Site Tax or any Adjustments) from the SOW.

Cumulative Committed Spend

Decimal

Yes

Example:

1234567.89

Value of Cumulative Committed Spend from the Work Order / Work Order Revision

or

the Presented Budget Amount (without Site Tax or any Adjustments) from the SOW.

Spend to Date

Decimal

Yes

Example:

1234567.89

Cumulative spend across all revisions for Work Order

or

Spend to Date from the SOW.

Currency

Text

100

Yes

Examples:

USD

CAN

EUR

ISO Currency code from SOW/Work Order.

Job Seeker/Worker Name

Text

100

No

SAP Fieldglass Job Seeker Name object for the Work

Order latest revision and Worker Name object for SOW with SOW workers on latest SOW revision.

Job Seeker ID

Text

16

No

Line Item ID

Text

16

Yes

Examples:

XXXXPS00000002

XXXXTU00000003

SAP Fieldglass SOW Line item ID.

External Line Item ID

Text

100

No

Example:

Client123

An external identifier used by the client for tracking purposes.

Line Item Description

Text

200

Yes

Description of SOW line item

Line Item Name

Text

100

Yes

Name of the SOW Line Item.

Line Item Type

Text

2

Yes

Valid values are:

Fee Definition

Schedule

Management Event

Valid SOW Line Item Type.

All Fee Definitions, Schedules in Created status and Management Events in Pending status.

Sequence Number

Number

10

Yes

The sequence number assigned automatically by the Fieldglass application.

Buyer Defined Sequence Number

Number

10

No

Example:

1234

The sequence number assigned manually by the buyer.

Units

Decimal

Yes

The number of units being billed for schedules or fees.

Maximum Units

Number

No

Maximum units allowed for schedules or fee characteristics.

Unit of Measure

Text

100

No

The unit of measure code for the Units listed.

Unit of Measure Name

Text

100

No

The unit of measure name for the Units listed

Line Item Rate

Decimal

Yes

Example:

22.58

Line Item Rate

Requested Amount

Decimal

Yes

Example:

910.24

Requested Amount for work order/SOW

Charged Amount

Decimal

Yes

Example:

110.24

Amount for the individual charge detail of the SOW Line Item.

Total Line Item Amount

Decimal

Yes

Example:

2100.92

Total Line Item Amount.

Due Date

Date

No

The due date noted for the SOW Line Item.

This field is only applicable for Schedules.

Library Definition Code

Text

100

No

The Code of the library definition used to create the Line Item.

Only applicable to SOW Characteristics.

For Fee Responses, the library is pulled from the Fee Definition.

Library Definition Name

Text

100

No

The Name of the library definition used to create the Line Item

Only applicable to SOW Characteristics.

For Fee Responses, the library is pulled from the Fee Definition.

Line Item Cost Center Code

Text

200

Yes

Valid SAP Fieldglass Cost Center Code

Cost center code for line item

Line Item Cost Center Name

Text

200

No

Cost center name for line item

Line Item Cost Center Allocation Amount

Decimal

Yes

Example:

1234567.89

Amount allocated to line item cost center

Line Item General Ledger Account

Text

100

No

Valid SAP Fieldglass GL Account

Example:

ABCDE

The GL Account for associated Cost Center.

This field only appears if company configuration ‘GLA allocation on job postings and statements of work is required’ is enabled.

Line Item Segment Object Detail

Text

2000

No

Examples:

IS|Admin|12001

IS-Admin-12001

IS;Admin;12001

IS:Admin:12001

Segmented Object Detail string.

Segments will be separated by delimiter on the Segmented Object.

Valid delimiters are colon (:), semi-colon (;), pipe (|), and dash (-).

Required if ‘Segmented object detail’ configuration set.

Note – more than one string can appear for a cost center.

Line Item Allocation %

Decimal

Yes

Example:

50.0

Allocation % is the percent value for whichever object (Cost Center % or GLA % or SOD %) is driving the cost allocation for the SOW Line Item.

Line Item Product Group Code

Text

100

No

A valid Product Group Code configured in the Product Group admin object.

The product group code for the event line item.

Line Items Product Group Name

Text

100

No

A valid Product Group Name configured in the Product Group admin object.

The product group name for the event line item.

[s] Event Hierarchy Contract Segment Name

Depends on the custom lookup segment configuration.

Depends on the custom lookup segment configuration.

Conditional

Example:

If the user-selected segment name on the event hierarchy is ‘Contract Line’ and the value selected is '14909823', the header of this column should be:

[s] Contract Line

The value in this column would be:

14909823

The 'Data Set' company configuration must be enabled to view this field.

The Segment Name should contain an [s] before the name.

Valid values of the user selectable segments are picked up from the Event Hierarchy

Commodity Code

Text

100

No

Example:

432231

Description of the commodity code from the Contingent Work Order, Statement of Work, Event, Fee, or Schedule.

This field must be manually configured to be in the download file template.

Commodity Description

Text

100

No

Example:

Digital Mobile

Network

Infrastructure Equipment

Components

Description of the commodity code from the Contingent Work Order, Statement of Work, Event, Fee, or Schedule.

This field must be manually configured to be in the download file template.

[c] custom field1

Dependent on Custom Field

Dependent on custom field

Dependent on Custom Field

Any custom fields from available modules which were requested to be added to the download.

Contact your SAP Fieldglass Representative to determine which custom fields may be included.

Event Owner

Text

100

No

A valid SAP Fieldglass username.

The SAP Fieldglass username of the user who is the event owner.

Event Account Category

Text

500

No

A valid SAP Fieldglass account category.

The SAP Fieldglass account category.

Unique Identifier

  • Object ID field

  • Revision (sequence #) field

  • Line Item ID (if applicable)

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.