Business Unit Download

Connector Overview

Component	Detail
Company Type	Buyer MSP Partner Supplier
Version Type	1.0 2.0 - Includes AP Code field.
Format	CSV
Prerequisites	Company plug-ins must be turned on for Integration – Business Unit Download. User role permission must be turned on for Download Data and Download Data.
Predecessors	Business Units
Related Connectors	Business Unit Upload

Triggering Events

Business units will appear in the download if their status is 'Open' at run time.

File Formatting

Header

Component	Enabled by Default?	Definition/Use	Notes	Value
Type	Yes	Download File Type	If you have a custom connector name for a standard connector, you may use the exact same custom name for the Type header; otherwise, you must use the standard name shown in the Value field.	Business Unit Upload
Transaction	No	Transaction Type	Transaction Type. The valid type names are: True: if any record errors, entire Download fails. False: only records that are in error fail, remaining records are committed successfully. If this field is not included in the header, the default value will be True.
Number Format	No	Determines the number format to be used in the file.	This is an optional header value. Determines the Number Format used in the company. The valid number format values are: “#,##9.99" (Example: "1,234,567.99”) “#.##9,99" (Example: "1.234.567,99”) “#'##9.99" (Example: "1'234'567.99”) “# ##9,99" (Example: "1 234 567,99”) The quotes are required even if the value does not have a comma in it. If this field is not included in the header, the default value will be #,##9.99.
Date Format	No	Determines the date format to be used in the file.	The valid date format values are: MM/DD/YYYY DD/MM/YYYY YYYY-MM-DD If this field is not included in the header, the default value will be MM/DD/YYYY.
Language	No	Determines the language to be used for values in the file, such as drop-down lists and radio buttons. Column headers will always default to the upload user's preferred language.	The valid language values are: Arabic (Standard Arabic) Chinese (Simplified) Chinese (Traditional) Dutch (Netherlands) English (United Kingdom) English (United States) French (Canada) French (France) German (Germany) Hebrew (Israel) Hungarian (Hungary) Italian (Italy) Japanese (Japan) Korean (Korea) Mongolian (Mongolia) Polish (Poland) Portuguese (Brazil) Portuguese (European) Russian (Russia) Spanish (Mexico) Swedish (Sweden)
Comments	No	Download Comments		This is a comment field containing notes about the download file.

Immediately following the Header section of the Download is one blank line.

Detail

Field Header Name	Data Type	Field Length	Enabled by Default?	Value(s)/Format	Description/Use/Field Rules
Modification Type	Char	1	Yes, for Deletes only.	Valid values are: A	A – Add
Code	Text	200	Yes	Valid Business Unit Code	Code describing the Business Unit. Value must be unique.
Name	Text	200	Yes		Name of the Business Unit.
Parent Business Unit	Text	200	Yes	Valid Business Unit Code	Code of the Business Unit directly above this Business Unit in the company Hierarchy.
General Ledger	Text	100	No	Valid SAP Fieldglass General Ledger Codes	General Ledger Code associated to the Business Unit.
Escalation Preference	Text	100	Yes	Valid SAP Fieldglass Escalation Thresholds	Escalation Preference Name related to transactions that will be created for this Business Unit.
Resource Coordinator Required Flag	Text	3	No	Valid values are: Yes No	Determines whether a Resource Coordinator will be required for this Business Unit. If left blank, defaults to No.
Resource Coordinator Username	Text	100	No	SAP Fieldglass Username for intended Resource Coordinator.	Required if theResource Coordinator Required Flag = Yes. SAP Fieldglass Username of the Resource Coordinator to be assigned to this Business Unit. User will need the “This User can act as Resource Coordinator/Distributor” flag set to Yes on his or her User Profile.
Distributor Required Flag	Text	3	No	Valid values are: Yes No	Determines whether a Distributor will be required for this Business Unit. If left blank, defaults to No.
Distributor Username	Text	100	No	SAP Fieldglass Username of intended Distributor.	Required if the Distributor Required Flag = Yes. SAP Fieldglass Username of the Distributor to be assigned to this Business Unit. User will need the “This User can act as Coordinator/Distributor” flag set to Yes on their User Profile.
Remit-To Address Required	Text	3	No	Valid values are: Yes No	If left blank, defaults to No.
Buyer Selects AP Code	Text	3	No	Valid values are: Yes No	Company configuration ‘AP Code Required’ must be enabled. The ‘Remit-To-Address Required’ field must be set to Yes in order to have this field’s value be Yes. If left blank, this field defaults to No.
Legal Entity	Text	100	No	Valid SAP Fieldglass Legal Entity or blank	Legal Entity Code for the site. Only applicable if company configuration is enabled for Legal Entity. If the Legal Entity Association is set to All, then in the download, this field will show ALL instead of actual Legal Entities.
[c] BU Custom Field[x]	Text	100	No	Dependent upon Custom Field Type	Any custom field associated with the Business Unit module. The custom field name should be prefixed with ‘[c]’. For example, custom field name: ‘BU Custom Field 1’ should be ‘[c] BU Custom Field 1’. Valid values of the custom field are configured during the setup of the SAP Fieldglass system. Do not include this field if it is not being used.

Unique Identifier

Code field

Assumptions/Tips

If the buyer company has multiple MSPs, when the MSP supplier user downloads records, they will see only records for their MSP.

Custom Fields

The download file will include custom fields from various modules in SAP Fieldglass. The specific modules are explained in the file format above.
The client can specify the custom fields they wish to include in the file and the order that they wish to see in the file.
At the time the connector is activated for the client, the client will be required to supply a list of the custom fields and their order. This list will be stored in SAP Fieldglass against the setup of the connector. If no custom fields are supplied, the download will not include any custom field values.
Custom fields included will always appear at the end of the column layout after all of the native, either default, or optional SAP Fieldglass fields have been output.
Custom field headers will be displayed in the format “[c] modulename_Field Name”.

Configuration Considerations

#	Item	Notes
1	Invoicing Considerations	The Business Unit field in SAP Fieldglass is often tied to some portion of the invoicing process. Whatever its connection may be, it is important to consider the back end invoicing implications of grouping the organization into separate Business Units. Organizations often find that what they originally believe to be their organization’s Business Units may not be the appropriate choice in all instances.
2	Visibility Impacts of Business Unit Configuration	SAP Fieldglass user’s visibility in the application will be partially governed by the Business Units to which they are associated. While configuring SAP Fieldglass, it is important to consider visibility when determining which of the numerous options for Business Unit association will be chosen.

#

Item

Notes

1

Invoicing Considerations

The Business Unit field in SAP Fieldglass is often tied to some portion of the invoicing process. Whatever its connection may be, it is important to consider the back end invoicing implications of grouping the organization into separate Business Units. Organizations often find that what they originally believe to be their organization’s Business Units may not be the appropriate choice in all instances.

2

Visibility Impacts of Business Unit Configuration

SAP Fieldglass user’s visibility in the application will be partially governed by the Business Units to which they are associated.

While configuring SAP Fieldglass, it is important to consider visibility when determining which of the numerous options for Business Unit association will be chosen.