IDoc Transactions


Simply brilliant IDoc transactions:
WE09 / WE02 IDoc lists according to content.
WE05 View IDocs.
WE19 EDI test tool. Use to test inbound Function module changes.
WE20 Partner profile configuration.
WE30 Create/Display IDoc type and extension
WE31 Create Segments
WE57 Assign function module to logical message and IDoc type
WE60 IDoc type documentation tool
WE82 Link Release detail to Extension IDoc Type
BD55 Conversion rule user exit. Link conversion rule user exit to the different system partner combinations
BD87 Reprocess IDocs in error or waiting for action. (Use BD88 in release prior to 4.6)
BALA ALE Application Distribution
BALM ALE Master Data Distribution
Very few people know this next one and it is one of my favorites:
WEDI

what sequence are profile parameter read?

          R/3 processes read the appropriate parameters from a C source in the R/3   kernel
  • The default profile /usr/sap//SYS/profile/DEFAULT.PFL is read; profile values already defined in the C source are replaced with the values in the default profile
  • The instance profile /usr/sap//SYS/profile/__ is read; profile values already defined in the default profile or in the C source are replaced with the values defined in the instance profile
  • This procedure ensures that system parameter values reflect the instance profile and the values in the default profile and the C source.

What are the different type of work process in SAP ?

The following work process in SAP R/3
  • Dialog (D): each dispatcher needs at least 2 dialog work processes 
        (not shown above)
  • Spool (S): at least 1 per R/3 System (more than 1 per dispatcher allowed)

  • Update (V): at least 1 per R/3 System (more than 1 per dispatcher allowed)

  • Background (B): at least 2 per R/3 System (more than 1 per dispatcher allowed)

  • Enqueue (E): exactly 1 per R/3 System (only 1 E work process is required and
    allowed)

How to reset SAP* password from oracle database?

                             Logon to your database with orasid as user id and run this sqldelete from sapSID.usr02
where bname='SAP*' and mandt='XXX';commit;
Where mandt is the client.

Now you can login to the client using sap* and password pass

How to create users?

                  Execute transaction SU01 and fill in all the field. When creating a new user, you must enter an initial password for that user on the Logon data tab. All other data is optional.

How many profiles can be assigned to any user master record

                                               Maximum Profiles that can be assigned to any user is ~ 312. Table USR04 (Profile assignments for users). This table contains both information on the change status of a user and also the list of the profile names that were assigned to the user.

                    The field PROFS is used for saving the change flag (C = user was created, M = user was changed), and the name of the profiles assigned to the user. The field is defined with a length of 3750 characters. Since the first two characters are intended for the change flag, 3748 characters remain for the list of the profile names per user. Because of the maximum length of 12 characters per profile name, this results in a maximum number of 312 profiles per user.

What is a derived role?

                                            Derived roles refer to roles that already exist. The derived roles inherit the menu structure and the functions included (transactions, reports, Web links, and so on) from the role referenced. A role can only inherit menus and functions if no transaction codes have been assigned to it before.
The higher-level role passes on its authorizations to the derived role as default values which can be changed afterwards. Organizational level definitions are not passed on. They must be created anew in the inheriting role. User assignments are not passed on either.

Derived roles are an elegant way of maintaining roles that do not differ in their functionality (identical menus and identical transactions) but have different characteristics with regard to the organizational level.

Single Role Vs Composite Role in SAP

Single Role:
                       Single roles contain authorization data.Say if you have some single role to create a object, you can edit ,create or delete that object based on authorization data defined.


Composite Roles:

                           A composite role is a container which can collect several different roles. For reasons of clarity, it does not make sense and is therefore not allowed to add composite roles to composite roles. Composite roles are also called roles.

Composite roles do not contain authorization data. If you want to change the authorizations (that are represented by a composite role), you must maintain the data for each role of the composite role.

Creating composite roles makes sense if some of your employees need authorizations from several roles. Instead of adding each user separately to each role required, you can set up a composite role and assign the users to that group.

The users assigned to a composite role are automatically assigned to the corresponding (elementary) roles during comparison.