Explore topic-wise InterviewSolutions in .

Transaction CODE ST01 is used to trace the user authorizations. This can be useful if we NEED to check which all the authorizations have been checked in background when any t-code is being EXECUTED by the BUSINESS user.

Below are the return codes of ST01 :

• 0 – Authorization check passed
• 1 – No Authorization
• 2 – Too many parameters for authorization check
• 3 – OBJECT not contained in user buffer
• 4 – No profile contained in user buffer
• 6 – Authorization check incorrect
• 7,8,9 – Invalid user buffer.

Transaction code ST01 is used to trace the user authorizations. This can be useful if we need to check which all the authorizations have been checked in background when any t-code is being executed by the business user.

Below are the return codes of ST01 :

The query can be created and executed using the t-code SQVI:

• Execute the t-code SQVI.
• Enter the name of query to be created and click on create button.
• Enter the Title and comments for query and select the DATA SOURCE such as table or table join.
• Select the preferred view as Basis Mode or Layout Mode and click on continue button.
• Above step will take US to the NEW SCREEN, add the respective table on which we need to create a query.
• If Data source is selected as table join, select the respective tables as needed and joining fields.
• Save and come to main screen. Here, you need to select the fields to be displayed in output and their sequence.
• The query can be created and executed using the t-code SQVI.

The query can be created and executed using the t-code SQVI:

Sarbanes-Oxley is a US law passed in 2002 to strengthen corporate governance and restore INVESTOR confidence. Act was sponsored by US Senator Paul Sarbanes and US Representative Michael Oxley.

The Sarbanes-Oxley Act is legislation enacted in response to the high-profile Enron and WorldCom financial scandals to protect shareholders and the general public from accounting errors and fraudulent practices in the enterprise. Sarbanes-Oxley defines which records are to be stored and for how long. The legislation not only affects the financial side of corporations, but also affects the IT departments whose job it is to store a corporation’s electronic records. The Sarbanes-Oxley Act STATES that all BUSINESS records, including electronic records and electronic messages, must be saved for “not less than five years”. The consequences for non-compliance are fines, imprisonment, or both. IT departments are INCREASINGLY faced with the challenge of creating and maintaining a corporate records archive in a cost-effective fashion that satisfies the requirements put forth by the legislation.

Organizations should be able to guarantee the integrity of some of their operations like PTP or OTC which can have quiet a significant impact on the way the financial statements are projected if not controlled.

Organizations today are thereby moving in direction of automating their SOFTWARES for SOX compliance. A key factor towards achieving SOX compliance is to seperate the duties amongst individuals to such an extent that no one person has the authorization to fulfill a complete cycle say procurement or sales.

Sarbanes-Oxley is a US law passed in 2002 to strengthen corporate governance and restore investor confidence. Act was sponsored by US Senator Paul Sarbanes and US Representative Michael Oxley.

The Sarbanes-Oxley Act is legislation enacted in response to the high-profile Enron and WorldCom financial scandals to protect shareholders and the general public from accounting errors and fraudulent practices in the enterprise. Sarbanes-Oxley defines which records are to be stored and for how long. The legislation not only affects the financial side of corporations, but also affects the IT departments whose job it is to store a corporation’s electronic records. The Sarbanes-Oxley Act states that all business records, including electronic records and electronic messages, must be saved for “not less than five years”. The consequences for non-compliance are fines, imprisonment, or both. IT departments are increasingly faced with the challenge of creating and maintaining a corporate records archive in a cost-effective fashion that satisfies the requirements put forth by the legislation.

Organizations should be able to guarantee the integrity of some of their operations like PTP or OTC which can have quiet a significant impact on the way the financial statements are projected if not controlled.

Organizations today are thereby moving in direction of automating their softwares for SOX compliance. A key factor towards achieving SOX compliance is to seperate the duties amongst individuals to such an extent that no one person has the authorization to fulfill a complete cycle say procurement or sales.

Authorization groups are the units comprising of tables for COMMON functional area. GENERALLY, each table is assigned to a authorization group due to this reason we NEED to mention the value of authorization group while restricting the ACCESS to table in authorization object S_TABU_DIS.

The authorization group can be created by using the t-code SE54. The assignment of tables to authorization group can be CHECKED by using table TDDAT.

Authorization groups are the units comprising of tables for common functional area. Generally, each table is assigned to a authorization group due to this reason we need to mention the value of authorization group while restricting the access to table in authorization object S_TABU_DIS.

The authorization group can be created by using the t-code SE54. The assignment of tables to authorization group can be checked by using table TDDAT.

This AUTHORIZATION object is USED to provide the ACCESS to tables on row LEVEL.

This authorization object is used to provide the access to tables on row level.

The t-code SU25 is used to copy the data from tables USOBT and USOBX to tables USOBT_C and USOBX_C. Generally, this t-code NEEDS to be executed after the INSTALLATION of SYSTEM upgrade so that the values in customer tables are UPDATED ACCORDINGLY.

The t-code SU25 is used to copy the data from tables USOBT and USOBX to tables USOBT_C and USOBX_C. Generally, this t-code needs to be executed after the installation of system upgrade so that the values in customer tables are updated accordingly.

To perform this mass role ASSIGNMENT, we need to follow below steps in SU10:

• In SU10 home screen, click on the button “Authorization Data”
• This will take to the new screen similar to screen in t-code SUIM -> User by complex search criteria. Enter the search criteria for users needed to be CHANGED in SU10 and EXECUTE the same
• Once the list of users is reflected, click on “select all” button on left top corner of the list and click on “Transfer” button. This will take us back to SU10 screen with all the selected users in users
• Now, click on select all button in SU10 home screen and then click on change button.
• Above step will take us to the next screen where you can perform the role assignment as in normal CASE of SU10 t-code.

To perform this mass role assignment, we need to follow below steps in SU10:

During the DISTRIBUTION of authorization data from master ROLE to derived roles, Organizational values and user assignment are not distributed. The Org. values and user ASSIGNMENTS are specific to individual roles hence has no bearing on master-derived role RELATIONSHIP.

During the distribution of authorization data from master role to derived roles, Organizational values and user assignment are not distributed. The Org. values and user assignments are specific to individual roles hence has no bearing on master-derived role relationship.

Logical system can be ASSIGNED to client by USING the TC -code SCC4. We NEED to be very careful while doing this change as it can AFFECT the CIA (if configured).

Logical system can be assigned to client by using the tc -code SCC4. We need to be very careful while doing this change as it can affect the CIA (if configured).

The values for PARAMETERS can be checked by USING the t-code RSPFPAR. After executing the t-code, GIVEN the parameter name and click on execute.

The values for parameters can be checked by using the t-code RSPFPAR. After executing the t-code, given the parameter name and click on execute.

The list of email ids for given USERS can be GENERATED by performing the below steps:

1. Execute the t-code SE16
2. Enter the table name as USR21.
3. UPLOAD the list of users using multiple selection option and execute. This will give us the list of users and their respective person numbers
4. Extract this data to excel SHEET
5. Now, go back to SE16 and enter table name ADR6
6. Upload the list of person number extracted from table USR21 and execute
7. Now, table ADR6 will give us the list of person numbers and their email ids.
8. Download the list in excel and perform V-look up in excel to map the email ids of users with their SAP IDs

The list of email ids for given users can be generated by performing the below steps:

This list can be GENERATED by USING the table AGR_1251 as below:

• Execute the t-code SE16
• Enter the table name as AGR_1251 and hit enter button
• Enter the field value as “G” in field “Object Status” and click on execute
• The same table can be used to generate the list of ROLES with authorization objects having status MODIFIED and manual with field values M and U RESPECTIVELY.

This list can be generated by using the table AGR_1251 as below:

The t-code SE10 PROVIDE the option to enter the user NAME. By using this FACILITY, we can search the TRANSPORT requests created by other users.

The t-code SE10 provide the option to enter the user name. By using this facility, we can search the transport requests created by other users.

The list of Transport requests containing the specific role can be RETRIEVED by performing below steps:

• Execute the t-code SE03
• Double click on OPTION “Search for OBJECTS in requests/Tasks” under node “Objects in Requests” in left panel of screen. This will TAKE us to NEW screen.
• In object selection screen, enter the field value as ACGR and check the checkbox present at left side.
• Enter the role name for which we need the list of transport request.
• In screen “Request/Task Selection” screen (below section of the same screen), check the status of the requests which we need in the list
• Click on execute button

The list of Transport requests containing the specific role can be retrieved by performing below steps:

USER GROUP can be created by performing the below steps:

1. Execute the t-code SUGAR
2. Enter the NAME of user group to be created in the textbox
3. CLICK on the create the button
4. Enter the description and click on save button

User group can be created by performing the below steps:

4 types of tables

1. Transparent tables : Exists with the same structure both in dictionary as well as in database exactly with the same data and FIELDS. Both Open sql and Native sql can be USED.
2. Pool tables
3. Cluster tables : These are LOGICAL tables that are arranged as records of transparent tables. one cannot use native sql on these tables (only open sql).They are not manageable directly using database SYSTEM tools. 
4. Internal tables.

4 types of tables

GLOBAL EXISTANCE(these COULD be used by any other PROGRAM without creating it again).

GLOBAL EXISTANCE(these could be used by any other program without creating it again).

HEADER ,BODY,FOOTER.

HEADER ,BODY,FOOTER.

step 1: CREATING domains(data TYPE, field LENGTH, range). 

step 2: creating data elements(properties and type for a table field).

step 3: creating tables(SE11).

step 1: creating domains(data type, field length, range). 

step 2: creating data elements(properties and type for a table field).

step 3: creating tables(SE11).

Once you have declared the POSSIBLE RECORD types as field groups and defined their STRUCTURE, you can fill the extract dataset using the FOLLOWING statements: EXTRACT. When the first EXTRACT statement occurs in a program, the system creates the extract dataset and adds the first extract record to it. In each subsequent EXTRACT statement, the new extract record is added to the dataset EXTRACT HEADER. When you extract the data, the record is filled with the current VALUES of the corresponding fields. As soon as the system has processed the first EXTRACT statement for a field group , the structure of the corresponding extract record in the extract dataset is fixed. You can no longer insert new fields into the field groups and HEADER. If you try to modify one of the field groups afterwards and use it in another EXTRACT statement, a runtime error occurs. By processing EXTRACT statements several times using different field groups, you fill the extract dataset with records of different length and structure. Since you can modify field groups dynamically up to their first usage in an EXTRACT statement, extract datasets provide the advantage that you need not determine the structure at the beginning of the program.

Once you have declared the possible record types as field groups and defined their structure, you can fill the extract dataset using the following statements: EXTRACT. When the first EXTRACT statement occurs in a program, the system creates the extract dataset and adds the first extract record to it. In each subsequent EXTRACT statement, the new extract record is added to the dataset EXTRACT HEADER. When you extract the data, the record is filled with the current values of the corresponding fields. As soon as the system has processed the first EXTRACT statement for a field group , the structure of the corresponding extract record in the extract dataset is fixed. You can no longer insert new fields into the field groups and HEADER. If you try to modify one of the field groups afterwards and use it in another EXTRACT statement, a runtime error occurs. By processing EXTRACT statements several times using different field groups, you fill the extract dataset with records of different length and structure. Since you can modify field groups dynamically up to their first usage in an EXTRACT statement, extract datasets provide the advantage that you need not determine the structure at the beginning of the program.

PROBLEMS:

• If the USER forgets to OPT for keep session then the session will be automatically removed from the session queue(log remains). However if session is processed we may delete it MANUALLY.
• if session processing FAILS data will not be transferred to SAP database table.

PROBLEMS:

STEP 1: CONVERTING THE LEGACY SYSTEM DATA TO A FLAT FILE to internal table CALLED "CONVERSION".

STEP 2: TRANSFERRING THE FLAT FILE INTO SAP SYSTEM CALLED "SAP DATA TRANSFER".

STEP 3: DEPENDING UPON THE BDC TYPE 

• CALL transaction(Write the program explicitly)
• create sessions (sessions are created and processed. If success data will transfer).

STEP 1: CONVERTING THE LEGACY SYSTEM DATA TO A FLAT FILE to internal table CALLED "CONVERSION".

STEP 2: TRANSFERRING THE FLAT FILE INTO SAP SYSTEM CALLED "SAP DATA TRANSFER".

STEP 3: DEPENDING UPON THE BDC TYPE 

YES. eg:- ITAB LIKE SPFLI.here we are referening to a data OBJECT(SPFLI) not data ELEMENT. 

YES. eg:- ITAB LIKE SPFLI.here we are referening to a data object(SPFLI) not data element. 

The name SAP a German company is an acronym for "SYSTEME, Anwendungen, Produkte in der Datenverarbeitung." This is TRANSLATED in English as "Systems, Applications, and Products in DATA PROCESSING."

The name SAP a German company is an acronym for "Systeme, Anwendungen, Produkte in der Datenverarbeitung." This is translated in English as "Systems, Applications, and Products in Data Processing."

1. APPLICATION LOGIC and DATA Storage.
2. The R/3 Basis software is HIGHLY suitable for use in multi-level client/server architectures.