Workbook fields and formats

Start from the example workbook saved through Mass User Create → Help → Save Example Mass User Create Spreadsheet. Preserve its headings and underscores. Use the exact spelling shown below even where a check accepts other letter casing.

Layout and required fields

Set cell A1 to Vertical or Horizontal. A Vertical batch shares role and parameter lists among its users. A Horizontal batch places those assignments along each user’s row. Keep parameter IDs paired with their values.

Separate batches with two blank rows, following the example workbook. Do not insert blank columns between populated columns: a blank header can be interpreted as the end of the field list.

Field	Purpose	Example
Comment	Identifies the batch in the worksheet	Demo team
System	Connection entry used for the target system	Example SAP system
SID	Target system identifier	ABC
Client	Target client within that system	100
User_ID	Account to create	DEMO_J

Include these fields for each batch/user as shown in the chosen template. The same user can be created in multiple target clients; check every target before starting.

The template includes Comment to identify batches. The current format checker reports its absence as a warning; it should still be included to keep batches understandable.

Use a three-character alphanumeric SID and a three-digit Client such as 010. Preserve leading zeroes. The System entry must match a configured connection, and each SID entry needs its corresponding client value. Keep the supplied field order unless you have checked the relationships between repeated columns.

Repeatable assignments

In a Vertical batch, put the shared roles, profiles and parameter pairs down their respective columns. Every user in that batch receives the shared assignments in each listed target client. Keep user-specific contact/default values on the user’s row.

In a Horizontal batch, put assignments across each user’s row. The columns Roles, Role_Valid_From, Role_Valid_To, Profiles, Parameter_ID and Parameter_Value can repeat; other duplicate headings are rejected. Use Profiles (plural).

Keep each parameter’s Parameter_Value immediately after its Parameter_ID. Repeat the pair to provide another parameter. A missing value is a blank value, not an instruction to skip the parameter. Preserve significant spaces when a SAP parameter requires them.

Place a role’s validity columns immediately after that Roles column, before the next role. Review every repeated group. If role validity is not supplied, the reader defaults the start to the current date and the end to 31 December 9999; supply explicit dates when that is not appropriate.

For example, a Vertical batch containing two users and two demo role rows gives both roles to both users. In a Horizontal batch, fill a role cell only on the row of the user who should receive it. These are layout examples, not authorization recommendations.

Horizontal profile limitation: a Horizontal sheet containing Profiles but no Parameter_ID heading can leave out the requested profiles. Use the Vertical layout for that case and verify the resulting profiles before notifying users. A successful create result is not proof that all requested authorizations were applied.

Dates

Use actual spreadsheet date cells with a simple explicit format, such as dd/mm/yyyy, and check the displayed values before running validation. In that format, 23/09/2026 means 23 September 2026.

The reader converts the displayed date using the cell’s number format. Text pasted into a differently formatted cell, complex regional formats or ambiguous values can fail or be interpreted differently from what you intended. Keep the template’s simple date formatting and verify with a date whose day is greater than 12.

This applies to Valid_From, Valid_To, Role_Valid_From and Role_Valid_To. The Date_Format field below controls the SAP user’s display preference; it is not the workbook cell format.

Identity and contact fields

Field	Purpose
Account_ID	Account number
Alias	Alternative account identifier
Birth_Name	Birth name
First_Name	First name
Last_Name	Last name; the user ID is used when no last name is supplied
Middle_Name	Middle name
Title	Form of address
Email	Email address, for example jane.demo@example.com
Telephone_Cell	Mobile telephone number
Telephone_Land	Landline telephone number
Building	Building identifier
Department	Department
Floor	Floor
Function	Job function
Room	Room
Cost_Center	Cost center

Access and security fields

Field	Purpose
Password	Initial password; if omitted or blank, the workflow requests a generated password from SAP
User_Type	SAP user-type code accepted by this workflow: A, B, C, L or S
User_Group	Authorization-check user group
Reference_User	Reference user for additional authorization
Roles	Roles to assign, following the selected layout
Role_Valid_From	Role-assignment start date
Role_Valid_To	Role-assignment end date
Profiles	Profiles to assign; use only approved profiles
Security_Policy	Security policy configured in the target client
Valid_From	Account validity start date
Valid_To	Account validity end date
SNC_Name	Full SNC identity name
SNC_Gui_Flag	Whether password logon is allowed with SNC; follow the template’s yes/no values

Supplying a password does not guarantee that it meets every target system’s password policy. Check the returned messages. Do not populate broad administrative profiles as example data in a real workbook.

Defaults and parameters

Field	Purpose
Date_Format	SAP date-display preference code; the checker accepts 1–6
Decimal_Format	Blank for 1.234.567,89, X for 1,234,567.89, or Y for 1 234 567,89
Time_Format	0 for 24-hour time; 1/2 for 12-hour time with AM/PM or am/pm; 3/4 for 0–11 hours with AM/PM or am/pm
Logon_Lang	Default logon language
Output_Device	Default output device
Start_Menu	Initial area menu
Timezone	SAP time-zone key valid in the target system
Parameter_ID	Parameter identifier
Parameter_Value	Value for its paired parameter identifier

Use the example workbook and the in-application column guidance for coded preferences. Confirm that system-specific keys exist in the target client. Do not substitute operating-system locale names for SAP preference codes.

When using Decimal_Format in a Vertical sheet, include and populate Date_Format as well, then inspect the created account’s defaults. Without both fields, the decimal preference may not be applied correctly.

Reserved fields

Add_Remove, Profile_Valid_From and Profile_Valid_To are not supported by this creation workflow. Leave them out of new workbooks.

Validate before creating

Run Check → Format & Systems, inspect Messages and the highlighted cells, correct errors, then check again. Save the workbook before creation and save the resulting account/password worksheet afterward. Continue with Mass User Create.