SAP Function BAPI_USER_CLONE - Create/Change Users (Only Usable by CUA Distribution)

Parameter Reference Type Length Default Optional Text
ADDRESS BAPIADDR3 u 2031 X Address Data
ADD_FIELDS BAPIADDFLD u 1 X Additional USERCLONE IDoc Fields
ADD_FIELDSX BAPIADDFLDX u 1 X Change Indicator for BAPIADDFLD (Various Additional Fields)
ALIAS BAPIALIAS u 40 X User Name Alias
COMPANY BAPIUSCOMP u 42 X Company for Company Address
DEFAULTS BAPIDEFAUL u 70 X Structure with User Defaults
EXTIDSX BAPIUSEXTIDX u 1 X Change Indicators for External IDs
LOGONDATA BAPILOGOND u 339 X Structure with Logon Data
METHOD BAPIMETHOD u 30 Method to be Called
PASSWORD BAPIPWD u 40 X Password
REF_USER BAPIREFUS u 12 X Reference user for rights (Internet)
SNC BAPISNCU u 256 X Secure Network Communication - Data
UCLASS BAPIUCLASS u 45 X User Classification (License-Related)
UCLASSX BAPIUCLASSX u 2 X Change Indicators for License-Related User Classification
USATTRX BAPIUSATTRX u 1 X Change Indicators for the Additional User Attributes
USERNAME BAPIBNAME u 12 User Name

Parameter Reference Length Optional Text
ACTIVITYGROUPS BAPIAGR 127 X Activity Groups
ADDCOMREM BAPICOMREM 60 X
ADDFAX BAPIADFAX 143 X
ADDPAG BAPIADPAG 136 X
ADDPRT BAPIADPRT 40 X
ADDRFC BAPIADRFC 69 X
ADDRML BAPIADRML 63 X
ADDSMTP BAPIADSMTP 300 X
ADDSSF BAPIADSSF 2391 X
ADDTEL BAPIADTEL 142 X
ADDTLX BAPIADTLX 72 X
ADDTTX BAPIADTTX 72 X
ADDURI BAPIADURI 2219 X
ADDX400 BAPIADX400 948 X
APPLREF BAPIAPREF 90 X References to application objects for user
EXTIDHEAD BAPIUSEXTIDHEAD 36 X Header Data for External ID of a User
EXTIDPART BAPIUSEXTIDPART 234 X Part of a Long Field for the External ID of a User
GROUPS BAPIGROUPS 12 X Transfer Structure for a List of User Groups
PARAMETER BAPIPARAM 98 X Table with User Parameters
PARAMETER1 BAPIPARAM1 120 X Replaces parameter (length 18 -> 40)
PERSDATA BAPIPERS 92 X Personalization distribution exchange format
PROFILES BAPIPROF 74 X Profiles
RETURN BAPIRET2 548 X Return Structure
USATTR BAPIUSATTRTAB 157 X Additional User Attributes

Functionality
This method is purely technical. You need it to distribute users viaALE.
Do not call this method directly.

Notes
Use the parameter METHOD to call one of the methods of object USER. Inany case you should call the methods directly.
INCLUDE ADDR_TABL_BAPIADDR3 OBJECT DOKU ID TX
INCLUDE SU_COMPANY OBJECT DOKU ID TX
INCLUDE SU_DEFAULTS OBJECT DOKU ID TX

Description
If EXTIDX-EXTID = 'X', the external user IDs are to be copied from thetable parameters EXTIDHEAD and EXTIDPART. If EXTIDX-EXTID = SPACE, theparameters EXTIDHEAD and EXTIDPART are to be ignored.
INCLUDE SU_LOGONDATA OBJECT DOKU ID TX

Description
Method that is called.
Is not used
INCLUDE SU_SNC OBJECT DOKU ID TX

Description
User classification in accordance with the license agreement betweenthe customer and SAP.
LIC_TYPE is the user type (values from table TUTYPA or TUTYP).
SPEC_VERS is a possible special version (values from table TUZUS).
COUNTRY_SURCHARGE is a possible country surcharge (value range between-100% and +999%).
You can only ever specify a special version or a country surcharge,never both. The following must therefore apply: SPEC_VERS = '00' orCOUNTRY_SURCHARGE = 0.
SUBSTITUTE_FROM and SUBSTITUTE_UNTIL specify the time period in whicha user is a substitute (user type '04').
SYSID, CLIENT, and BNAME_CHARGEABLE point to the chargeable users forthe user types Substitute ('04') or Multi-Client/Multi-System ('11').

Description
The method 'Change' only changes the transferred fields that areexplicitly identified as change-relevant. The structure UCLASSX existsfor the structure UCLASS and the table UCLASSSYS. Only if UCLASSX-UCLASSis set to 'X' are the user classifications used.
In addition, you must specify in the central CUA system for centraluser classification, how the table is to process the system-specificuser classifications. The following values are permitted for the fieldUCLASSX-UCLASSSYS:

  • 'R' The system-specific user classifications are deleted and
    • replaced by the current values of the table.
    • 'S' Only the user classifications for the listed systems are
      • replaced. If the user classifications for a system are to be deleted,the user type must be initial.
      • Space The table is not used.

        • Description
        The structure USATTRX exists for the table USATTR. Only ifUSATTRX-USATTR is set are the additional user attributes used.
        The following values are permitted:

        • 'R' All user attributes are deleted and replaced by the
          • current values from the table.
          • 'S' Only the specified user attributes are created, changed, or
            • deleted.
            • Space The table is not used.

              • INCLUDE SU_USERNAME OBJECT DOKU ID TX
              INCLUDE SU_ACTIVITYGROUPS OBJECT DOKU ID TX

              Description
              There can be any number of external IDs for one user, which are to beused for authentication.
              Each external ID consists of a series of fields. These include the threelong fields EXTID, ISSUER, and SERIAL with a length of 4096 characters.
              When sending users using central user administration (CUA), the externalIDs are also sent. The sending is performed using ALE and thereforeIDocs. A segment of an IDoc can only be a maximum of 1000 bytes. Thelong fields of the external IDs must therefore be divided into smallerparts.
              The data is always sent as character data. In case the long fieldcontains raw data in the future, you can also transfer this database64 encrypted. In this case, the field CODE_TYPE should contain thevalue 'B'.
              The internal table EXTIDHEAD contains the header information for anexternal ID. The parts of the three long fields are sent in the internaltable EXTIDPART. The connection between the two tables is created usingthe field SEQ_NO_ID: For a record in table EXTIDHEAD with a particularSEQ_NO_ID, there can be any number of records in table EXTIDPART withthe same SEQ_NO_ID.

              Description
              There can be any number of external IDs for one user, which are to beused for authentication.
              Every external ID consists of a series of fields. These include thethree long fields EXTID, ISSUER, and SERIAL with a length of 4096characters.
              When sending users using central user administration (CUA), the externalIDs are also sent. This sending is performed using ALE and thereforeIDocs. A segment of an IDoc can only be a maximum of 1000 Bytes long.The long fields of the external IDs must therefore be divided intosmaller parts.
              The data is always sent as character data. In case the long fields alsocontain raw data in the future, you can transfer this data base64encrypted. In this case, the CODE_TYPE field should contain the value'B'.
              The internal table EXTIDHEAD contains the header information for anexternal ID. The parts of the three long fields are sent in the internaltable EXTIDPART. The connection between the two tables is made usingthe field SEQ_NO_ID: For a record in the table EXTIDHEAD with a certainSEQ_NO_ID, there can be any number of records in the table EXTIDPARTwith the same SEQ_NO_ID.
              In table EXTIDPART, the field name of the long fields is itself a field(FIELDNAME with the possible values 'EXTID', 'ISSUER', and 'SERIAL').The individual parts of a long field are sequentially numbered. Thesequence number is stored in field SEQ_NO_PART. The actual data is inthe PART_DATA field.
              INCLUDE SU_PARAMETER OBJECT DOKU ID TX
              INCLUDE SU_PROFILES OBJECT DOKU ID TX
              INCLUDE SU_RETURN OBJECT DOKU ID TX

              Description
              Additional attributes can be stored for a user. When it is being sentin an IDoc, the user attribute (data type string) must be dividedinto multiple rows of type CHAR. The user attribute is converted backinto the data type string in the receiving system.

787292Password-related problems