SAP R3 Interview Questions and Answers
Question - 41 : - What Are R/3 Basis Configurations?
Answer - 41 : -
- A central system with centrally installed presentation software.
- Two-level client/server system with rolled out presentation software.
- Two-level client/server system. Presentation and Application run on the same computer.
- Three-level client/server system. Presentation, Application and database each run on separate computers.
Question - 42 : - From Hardware Perspective, Every Information System Can Be Divided Into Three Task Areas Presentation?
Answer - 42 : -
- Application Logic and Data Storage.
- The R/3 Basis software is highly suitable for use in multi-level client/server architectures.
Question - 43 : - Define Instance?
Answer - 43 : -
An instance is an administrative unit in which components of an R/3 systems providing one or more services are grouped together. The services offered by an instance are started and stopped at random. All components are parameterized using a joint instance profile. A central R/3 system consists of a single instance in which all-necessary SAP services are offered. Each instance uses separate buffer areas.
Question - 44 : - Can You Create A Table With Fields Not Referring To Data Elements ?
Answer - 44 : -
YES. eg:- ITAB LIKE SPFLI.here we are referening to a data object(SPFLI) not data element.
Question - 45 : - What Should Be The Approach For Writing A Bdc Program ?
Answer - 45 : -
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).
Question - 46 : - What Are The Problems In Processing Batch Input Sessions And How Is Batch Input Process Different From Processing Online ?
Answer - 46 : -
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.
Question - 47 : - What Does An Extract Statement Do In The Abap Program ?
Answer - 47 : -
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.
Question - 48 : - What Is The Step By Step Process To Create A Table In Data Dictionary ?
Answer - 48 : -
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).
Question - 49 : - What Is The Typical Structure Of An Abap/4 Program?
Answer - 49 : -
HEADER ,BODY,FOOTER.
Question - 50 : - What Is A Batch Input Session?
Answer - 50 : -
BATCH INPUT SESSION is an intermediate step between internal table and database table. Data along with the action is stored in session ie data for screen fields, to which screen it is passed, program name behind it, and how next screen is processed.