User/Contact Batch Upload Template Formats

You can create a batch upload definition to upload the details of users and contacts. While creating a batch upload definition template for users or contacts, see the following tables:

Table 1. User/Contact Batch upload definition template - Column Descriptions
Field	Value	Description
User Name	Users: Mandatory to enter the user name	Must enter the user name. This field is used as a lookup field. The bulk uploader attempts to locate the user by the user name to update the identified user. If no matching user is found, then a new user is created. Note: If the user name edit feature is turned on in the application, you must specify a different lookup field for user upload.
User Name	Contacts: Must be blank	Not required. For updating a contact that has no user name, the UUID can be used.
Activate/Unsuspend	Y or N	Can be used for users and contacts.
Type	Internal_User Internal_Contact External_User External_Contact Contact	User type cannot be modified. Entity of type Contact is specific to Emptoris® Contract Management. Organization and Supplier is not specified for this type. Contact can be modified to become Internal Contact or External Contact. To convert a contact to internal or external contact, update the type and specify the organization or supplier. Internal or External contact cannot be converted to user through bulk upload. They can be converted only through the user interface.
Display Name	Name to be displayed in the application.	This field is required.
Organization	Organization code	Optional for internal users and internal contacts. By default, the organization code is used to locate the organization. You can also select a different organization attribute for the lookup. If you do not enter any value in this field, the value is set to None. For more details about the organization code, see the Notes mentioned at the end of the topic.
Supplier/external party	Supplier or external party ID Master record name Un-mastered source record (data source name and the source record name separated with '\|')	Mandatory only for external users and external contacts. Examples of unmastered records: If IBM® is a data source record for Emptoris Supplier Lifecycle Management and I.B.M is the master then you need to enter I.B.M. If IBM is a data source record for Emptoris Supplier Lifecycle Management and there is no master, you need to enter SLM\|IBM. By default, the supplier company name is used to locate the supplier. You can select a different supplier attribute for the lookup.
Manager	Users: User name of the manager. Contacts: User name of the manager.	If you do not enter any value in this field, the value is set to None. Manager data must exist in the system or displayed before the user information in the template. If you cannot upload the manager data, the user field is also not uploaded.
Child Organization	Business Units	Child organizations in Emptoris Strategic Supply Management Platform, are referred to as business units in Emptoris Sourcing. Multiple business units should be entered as a comma separated list. The top-level public and Emptoris Sourcing restricted organizations are considered by Emptoris Sourcing. All descendent organizations of top-level Emptoris Sourcing organizations are recognized as business-units. Note: Application.ESP.Organization is by default associated with the Suite Applications.Organization.Code attribute. If this setting is changed to search on a different attribute, for example, Suite Applications.Organization.Organization Detail.Additional.Code, the Child Organizations are searched using the same Organization attribute.
State	Two character state code Complete state name or abbreviation	If the country field is blank, the state field must also be blank. Value must match to only one existing state record. Values are not case sensitive.
Country	Two character country code Three character ISO3 code Country name or part of the country name	Value must match to only one existing country record. Values are not case sensitive.
Roles	Role names
Groups	Group names

Table 2. Batch upload definition template - Preference Fields
Field	Value	Description
Date	D/MM/YYYY MM-DD-YYYY DD.MM.YYY YYYY/MM/DD YYYY-MM-DD	If this field is left blank, the default date format of MM/DD/YYYY is considered.
Number Format	#.###,## # ###,## # ###.##	If this field is left blank, the default number format of #,###.## is considered.
Language	Two character language code (for example, en) Two character language code and the 2 character country code separated with '_' (for example, en_US) Language name, or part of the language name	Values are not case sensitive. If this field is left blank, the default language 'English' is considered.
Time Zone	Region name and time zone name separated with '/' (Example: Europe/Minsk)	Do not include any UTC information.

Note: Mandatory fields in the template are indicated with an asterisk (*).

Application-specific fields

Table 3. Emptoris Supplier Lifecycle Management fields and attributes
Field	Value	Description
Application.SLM.Enabled	Y or N	Used for enabling or disabling Emptoris Supplier Lifecycle Management for a user. Application can be enabled for Internal User, External User, Internal Contact, and External Contact.
Application.SLM.Organization		Adds top-level organization with public scope or Restricted scope to Emptoris Supplier Lifecycle Management.
Application.SLM.Supplier	Blank for internal users/contacts.	This field is supported for External Users or Contacts only. Valid value is the Name of Supplier that belongs to the Data Source for that application. For example, IBM is a Data Source record for Emptoris Supplier Lifecycle Management and I.B.M is the Master then enter IBM. In the following cases you may leave this field blank and the value is automatically calculated: The supplier of the user is a master record which has only one Data Source record for this application. In this case the Application Supplier field, if left blank, it gets automatically set to the Data Source record. The supplier of the user is a Data Source record for this application. In this case the Application Supplier field, if left blank, is automatically set to the same source record.
Application.SLM.First Day of the Week	Name of the day of the week (Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday). Number representing the day of the week. For example, 1 for Sunday, 2 for Monday, and 3 for Tuesday.
Application.SLM.Assigned Groups		Bulk Loader links users to application specific groups. Bulk Loader validates that the group specified for the user in application specific group column is indeed linked to that application in the system. Internal application specific groups can only be assigned to internal users while external application specific groups can only be assigned to external users. If data is provided in application specific group column for a contact, then it is ignored. Group names is a comma separated list. Groups must be associated with Emptoris Supplier Lifecycle Management.

Table 4. Emptoris Sourcing fields and attributes
Field	Value	Description
Application. ESP.Enabled	Y or N	Enables or disables Emptoris Sourcing for a user. Application can be enabled for Internal User and External User.
Add Application. ESP.Organization		Adds top-level organization with public scope or restricted scope to Emptoris Sourcing. This is not applicable when Application.ESP.Assigned Role corresponds to a "System" level Sourcing Role.
Application.ESP.Supplier		Rules are the same as for Application.SLM.Supplier field.
Application.ESP.Language	Language can be specified in the following ways: The two character Language Code and the two character Country Code separated by "_" (e.g. nl_NL) The Language Name	Bulk Import supports the additional languages for Emptoris Sourcing. The support is available for users only. Emptoris Sourcing supports the following additional languages: nl_NL - Dutch pl_PL - Polish ru_RU - Russian tr_TR - Turkish sl_SI - Slovenian sv_SE - Swedish
Application.ESP.Homepage	User can enter either the Code or the Name of the Home page and comparison is not case sensitive. The various options are: Portal - Portal Page RfxList - View and Manage RFx(s) RfxCalendar - View RFx Calendar SimpleHomePage - Simple RFX Homepage Binders - View and Manage Binders SupplierProfileList - View and Manage Suppliers	User Bulk Upload includes Home page field for the Sourcing application and is supported for Internal User only, and ignored otherwise. If the field is not specified during User creation, it defaults to RfxList. If the data specified by the User does not match the above list, then import fails for that record. During an update, if no value is specified, then no update on this field is done. The field cannot be null. If {null} is entered during update, it is ignored.
Application.ESP.Default Wizard Mode	User can enter either the code or the name of the wizard mode and comparison is not case sensitive. The various options are: BASIC - Display Basic Steps ADVANCED - Display All Steps	Default wizard mode is available for Emptoris Sourcing and is supported for internal user only; otherwise it is ignored. If the field is not specified during user creation, it defaults to BASIC. If the data specified by the user does not match the above list, then import fails for that record. During an update, if no value is specified, then no update on this field is done. The field cannot be null. If {null} is entered during update it is ignored.
Application.ESP.Date Format	MM/DD/YYYY, DD/MM/YYYY, YYYY/MM/DD	To accommodate the smaller list for Emptoris Sourcing, an alternate date format in Emptoris Sourcing application section can be specified. Bulk Loader ensures that only the list available for Emptoris Sourcing is allowed as the valid content for this field. This property can only be specified for a user during bulk upload, not a contact; if specified for contact, it is ignored. If this data is not provided during bulk import, and if primary date format specified for the user is available in Emptoris Sourcing, then the Emptoris Sourcing date format contains that value. If not, then the default value of the date format for Emptoris Sourcing is set as MM/DD/YYYY.
Application.ESP.Number Format	Number formats supported in Emptoris Sourcing: #,###.## #.###,## # ###,##	To accommodate the smaller list for Emptoris Sourcing, an alternate number format in Emptoris Sourcing application section can be specified. Bulk Loader ensures that only the list available for Emptoris Sourcing is allowed as the valid content for this field. This property can only be specified for a user during bulk upload, not a contact; if specified for contact, it is ignored. If this data is not provided during bulk import, and if the primary number format specified for the user is available in Emptoris Sourcing, then Emptoris Sourcing number format contains that value. If not, then the default value of the number format is set as #,###.##.
Application.ESP.Assigned Role		This field is a special case. In Emptoris Strategic Supply Management Platform, it is treated as a group while in Emptoris Sourcing it is treated as a role. Only one role can be specified in this field and the role cannot be modified from the system to organization group type and vice versa; otherwise upload fails with an "Group for Sourcing application cannot be updated" error message.
Application.ESP.Module Visibility	Buyer Survey Creative negotiation Decision Support Demand Aggregation Executive Dashboard Forward Auctions Notices Forward Auction Dutch Reverse Auction Dutch Reverse Auction English Forward Auction Japanese Reverse Auction Japanese RFI RFP RFQ	This setting enables administrative users to control the Emptoris Sourcing functions available to users. The list of modules a user can be associated with is limited to the organization a user is associated with. The input is comma separated list of values. List supplied during user update is considered to be a replacement. Available only for internal users. If it is supplied for external users or internal/external contact, it is ignored. The list is validated against the user's top level organization's list of modules that are enabled in the organization.

Table 5. Emptoris Contract Management fields and attributes
Field	Value	Description
Application.ECM.Enabled	Y or N	Enables or disables a user for Emptoris Contract Management. Application can be enabled for Internal User, External User, Internal Contact, External Contact, and Contact (unaffiliated).
Application.ECM. Organization	Blank indicates root level organization.	Adds organization with public scope or Restricted scope to Emptoris Contract Management.
Application.ECM.Supplier		Rules are the same as for Application.SLM.Supplier field.
Application.ECM.Landing Page	0 - My Tasks 1 - My Contracts 2 - Search - Homepage tab 3 - Search - Repository screen	Supported only for an internal user. It is ignored for external user and internal/external contact, even if the data is provided. User can enter either the code or the name of the landing page. If the field is not specified during user creation, it defaults to My Tasks. During an update, if no value is specified, then no update on this field is done. The field cannot be null. If {null} is entered during update it is ignored. If the data specified by the user does not match the above list, then import fails for that record.
Application.ECM.Assigned Groups		Comma separated list of Group Names. Only Groups associated with Emptoris Contract Management are allowed.

Table 6. Emptoris Spend Analysis fields and attributes
Field	Value	Description
Application.Spend.Enabled	Y or N	Enables or disables a user to access Emptoris Spend Analysis. Application can be enabled for Internal User.
Application.Spend.Assigned Groups		Comma separated list of group names. Only groups associated with Emptoris Spend Analysis are allowed.
Application.Spend. Organization		Adds organization with public scope or Restricted scope to Emptoris Spend Analysis.

Table 7. Emptoris Program Management fields and attributes
Field	Value	Description
Application.PGM.Enabled	Y or N	Enables or disables a user to access Emptoris Program Management. Application can be enabled for Internal User.
Application.PGM. Assigned Groups		Comma separated list of group names. Only groups associated with Emptoris Program Management are allowed.
Application.PGM. Assigned Roles		Comma separated role names. Only roles associated with Emptoris Program Management are allowed.

Maximum permitted character sizes for fields

The maximum permitted characters in the fields in the user/contact batch upload template are listed in the following table. The maximum permitted size also includes the multi-byte characters for fields that support multi-byte characters. These character sizes are also applicable for the fields in the user interface and the web services.

Table 8. Maximum character size in fields
Field	Maximum Character Size	Multi-byte Support
User Name	256 characters This is a mandatory field.	Yes
First Name	100 characters This is a mandatory field.	Yes
Last Name	100 characters This is a mandatory field.	Yes
Middle Name	32 characters	Yes
Display Name	201 characters This is a mandatory field.	Yes
Title	200 characters	Yes
Phone	30 characters	Yes
Phone Ext	5 characters	Yes
Alternate Phone	30 characters	Yes
Alternate Phone Ext	5 characters	Yes
Pager	40 characters	Yes
Fax	30 characters	Yes
Email Address	256 characters This is a mandatory field.	Yes
Alternate Email	256 characters	Yes
Address Line1	255 characters	Yes
Address Line2	255 characters	Yes
City	50 characters	Yes
Postal Code	15 characters	No
P.O. Box Number	25 characters	No
P.O. City	50 characters	Yes
P.O. Zip	15 characters	No

Notes:

When creating a new user or a new contact, any value you enter in a column is used. If you do not enter any value in an optional field, the fields are left as blank. However, this rule is not applicable to certain fields.
The user preferences columns are an exception – if they are left blank, the default value is used.
When updating an existing user or an existing contact a blank value in the template preserves the old value.
If you want to keep the existing value, you are not required to enter values in any column. You can either populate all the columns, or only the columns that you want to update.
The lookup columns must always be populated. For example, if you want to update user, and modify only the phone number, and your lookup field is email, you may only include these columns; Email Address: user@email.com, Phone: 978-111-2222. The phone number is updated, while the rest of the fields is left untouched.
By default, the Suite Applications.Supplier.Company Name is used to locate the supplier. You can select a different supplier attribute to locate the supplier. The supplier attribute must be selected from the Suite Applications.Supplier attribute hierarchy, and not merely the [Application User.]Supplier sub-tree.
By default, the Suite Applications.Organization.Code is used to locate the desired organization. You can edit the user template and select a different organization attribute. It is imperative that the organization attribute be selected from the Suite Applications.Organization attribute hierarchy, and not merely the [Application User.] Organization sub-tree. Otherwise, the HrBatchProcessor cannot understand the user’s choice and revert to Suite Applications.Organization.Code.
If the Primary Supplier of the user is a mastered supplier, then the user can be enabled for any application. Identifying supplier for each application is not needed, unless there are multiple suppliers within an application linked to that Master. In such case, a specific supplier must be specified for that application.
If the Primary Supplier of the user is an unmastered supplier, then the user can only be enabled for the application that the unmastered supplier is created.