1) Name two ways to start a transaction?
Answer: 1) Dynamic Menu
2) Command Field
2) What is a data dictionary or repository?
Answer: Central catalog that contains the descriptions of an organization's data and provides information about the relationships between the data and its use in programs and screens. The data description in a Data Dictionary is also called metadata, i.e., data that describes other data.
The ABAP/4 Dictionary stores system-wide data definitions. When you create a new data definition, the Dictionary tool does all the processing necessary to create the definition. You can use the Dictionary tool to look up the "definition" of objects in your R/3 System.
3) Name the three different kinds of messages in the R/3 system. What is the difference between them?
Answer: A message can have five different types. These message types have the following effects during list processing:
A (=Abend):
The system displays a message of this message type in a dialog window. After the user confirms the message using ENTER, the system terminates the entire transaction (for example SE38).
E (=Error) or W (=Warning):
The system displays a message of this message type in the status line. After the user chooses ENTER, the system acts as follows:
While creating the basic list, the system terminates the report.
While creating a secondary list, the system terminates the corresponding processing block and keeps displaying the previous list level.
I (=Information):
The system displays a message of this message type in a dialog window. After the user chooses ENTER , the system resumes processing at the current program position.
S (=Success):
The system displays a message of this message type on the output screen in the status line of the currently created list.
Answer: A message can have five different types. These message types have the following effects during list processing:
A (=Abend):
The system displays a message of this message type in a dialog window. After the user confirms the message using ENTER, the system terminates the entire transaction (for example SE38).
E (=Error) or W (=Warning):
The system displays a message of this message type in the status line. After the user chooses ENTER, the system acts as follows:
While creating the basic list, the system terminates the report.
While creating a secondary list, the system terminates the corresponding processing block and keeps displaying the previous list level.
I (=Information):
The system displays a message of this message type in a dialog window. After the user chooses ENTER , the system resumes processing at the current program position.
S (=Success):
The system displays a message of this message type on the output screen in the status line of the currently created list.
4) Why do you create user-specific parameters?
They supply defaults to R/3 fields. If a field is indicated, the system automatically fills in default value. Depending on the field definition, the entry can also be replaced with a value entered by the user. (Concept of PARAMETER ID)
5) What is a match code?
Answer: Comparison key. A match code allows you to locate the key of a particular database record (e.g. account number) by entering any field value contained in the record. The system then displays a list of records matching the specifications.
6) If you want an end user to see a specific menu after logging on the R/3 system, how could you do that?They supply defaults to R/3 fields. If a field is indicated, the system automatically fills in default value. Depending on the field definition, the entry can also be replaced with a value entered by the user. (Concept of PARAMETER ID)
5) What is a match code?
Answer: Comparison key. A match code allows you to locate the key of a particular database record (e.g. account number) by entering any field value contained in the record. The system then displays a list of records matching the specifications.
Answer: User maintenance transactions allow the system administrator to create and maintain user master records. This includes the generation and assignment of authorizations and authorization profiles.
