Explore topic-wise InterviewSolutions in .

Leave to List-PROCESSING statement is used to produce a list from a MODULE POOL. Leave to list processing statement ALLOWS to switch from dialog-mode to list-mode within a dialog program.

Leave to List-processing statement is used to produce a list from a module pool. Leave to list processing statement allows to switch from dialog-mode to list-mode within a dialog program.

A current screen PROCESSING terminates when CONTROL reaches either a Leave-screen or the END of PAI.

A current screen processing terminates when control reaches either a Leave-screen or the end of PAI.

Suppressing entire screens is POSSIBLE USING this command. This command allows us to PERFORM screen processing "in the background". The system carries out all PBO and PAI logic, but does not display the screen to the user. Suppressing screens is USEFUL when we are branching to list-mode from a transaction dialog step.

Suppressing entire screens is possible using this command. This command allows us to perform screen processing "in the background". The system carries out all PBO and PAI logic, but does not display the screen to the user. Suppressing screens is useful when we are branching to list-mode from a transaction dialog step.

If we don't use Suppress-Dialog to NEXT screen will be displayed but as empty, when the user PRESSES ENTER, the STANDARD LIST output is displayed.

If we don't use Suppress-Dialog to next screen will be displayed but as empty, when the user presses ENTER, the standard list output is displayed.

By IMPLEMENTING an AUTHORITY CHECK.

By implementing an authority check.

SYNCHRONOUS and ASYNCHRONOUS.

Synchronous and Asynchronous.

A program ASKS the SYSTEM to perform a certain TASK, and then either WAITS or doesn’t WAIT for the task to finish. In synchronous processing, the program waits: control returns to the program only when the task has been completed. In asynchronous processing, the program does not wait: the system returns control after merely logging the request for execution.

A program asks the system to perform a certain task, and then either waits or doesn’t wait for the task to finish. In synchronous processing, the program waits: control returns to the program only when the task has been completed. In asynchronous processing, the program does not wait: the system returns control after merely logging the request for execution.

Commit-Work STATEMENT "performs" many functions relevant to SYNCHRONIZED EXECUTION of tasks. Rollback-work statement cancels: all reuests relevant to synchronized execution of tasks.

Commit-Work statement "performs" many functions relevant to synchronized execution of tasks. Rollback-work statement cancels: all reuests relevant to synchronized execution of tasks.

• SEMANTIC INTEGRITY.
• Relational Integrity.
• PRIMARY KEY Integrity.
• Value Set Integrity.
• Foreign Key integrity.
• Operational integrity.

• Semantic Integrity.
• Relational Integrity.
• Primary Key Integrity.
• Value Set Integrity.
• Foreign Key integrity.
• Operational integrity.

It is a MECHANISM for defining and APPLYING logical LOCKS to DATABASE objects.

It is a mechanism for defining and applying logical locks to database objects.

The TABLES.
The LOCK ARGUMENT.

The tables.
The lock argument.

SHARED LOCK.
EXCLUSIVE lock.
EXTENDED exclusive LIST.

Shared lock.
Exclusive lock.
Extended exclusive list.

By calling ENQUEUE&LT;LOCK OBJECT> and Dequeue<lock object> in the transaction.

By calling Enqueue<lock object> and Dequeue<lock object> in the transaction.

-PROCESS ON HELP-REQUEST (POH).
-PROCESS ON VALUE-REQUEST (POV).

-PROCESS ON HELP-REQUEST (POH).
-PROCESS ON VALUE-REQUEST (POV).

A matchcode is an AID to FINDING records stored in the system whenever an object KEY is REQUIRED in an input field but the user only KNOWS other (non-key) information about the object.

A matchcode is an aid to finding records stored in the system whenever an object key is required in an input field but the user only knows other (non-key) information about the object.

- Data element documentation.
- Data element additional TEXT in screen PAINTER.
- Using the process on HELP REQUEST event.

- Data element documentation.
- Data element additional text in screen painter.
- Using the process on help request event.

A roll area CONTAINS the PROGRAM’s runtime context. In addition to the runtime STACK and other structures, all local VARIABLES and any data known to the program are STORED here.

A roll area contains the program’s runtime context. In addition to the runtime stack and other structures, all local variables and any data known to the program are stored here.

- Transactions run in their own roll areas.
- Reports run in their own roll areas.
- DIALOG MODULES run in their own roll areas.
- Function modules run in the roll AREA of their callers.

- Transactions run in their own roll areas.
- Reports run in their own roll areas.
- Dialog modules run in their own roll areas.
- Function modules run in the roll area of their callers.

- Transactions run with a separate SAP LUW.
- Reports run with a separate SAP LUW.
- DIALOG MODULES run in the same SAP LUW as the caller.
- Function modules run in the same SAP LUW as the caller.
The only exceptions to the above RULES are function modules called with IN UPDATE TASK (V2 function only) or IN BACKGROUND TASK (ALE applications). These ALWAYS run in their own (separate) update transactions.

- Transactions run with a separate SAP LUW.
- Reports run with a separate SAP LUW.
- Dialog modules run in the same SAP LUW as the caller.
- Function modules run in the same SAP LUW as the caller.
The only exceptions to the above rules are function modules called with IN UPDATE TASK (V2 function only) or IN BACKGROUND TASK (ALE applications). These always run in their own (separate) update transactions.

FUNCTION MODULES are general-purpose LIBRARY ROUTINES that are AVAILABLE system-wide.

Function modules are general-purpose library routines that are available system-wide.

In general, FUNCTION module can have four types of parameters:
- EXPORTING: for PASSING data to the called function.
- IMPORTING: for receiving data RETURNED from the function module.
- TABLES: for passing internal tables only, by reference (that is, by address).
- CHANGING: for passing parameters to and from the function.

In general, function module can have four types of parameters:
- EXPORTING: for passing data to the called function.
- IMPORTING: for receiving data returned from the function module.
- TABLES: for passing internal tables only, by reference (that is, by address).
- CHANGING: for passing parameters to and from the function.

In CONTRAST to LEAVE TO TRANSACTION, the CALL TRANSACTION STATEMENT causes the system to start a new SAP LUW. This SECOND SAP LUW runs parallel to the SAP LUW for the CALLING transaction.

In contrast to LEAVE TO TRANSACTION, the CALL TRANSACTION statement causes the system to start a new SAP LUW. This second SAP LUW runs parallel to the SAP LUW for the calling transaction.

There are THREE options for passing SELECTION and parameter data to the report.
- Using SUBMIT…WITH.
- Using a report VARIANT.
- Using a RANGE table.

There are three options for passing selection and parameter data to the report.
- Using SUBMIT…WITH.
- Using a report variant.
- Using a range table.

We can send a REPORT to the printer INSTEAD of diplaying it on the screen. To do this, use the KEYWORDS TO SAP-SPOOL: SUBMIT RSFLFIND…TO SAP-SPOOL DESTINATION 'LT50'.

We can send a report to the printer instead of diplaying it on the screen. To do this, use the keywords TO SAP-SPOOL: SUBMIT RSFLFIND…TO SAP-SPOOL DESTINATION 'LT50'.

USING SPA/GPA PARAMETERS(SAP MEMORY).
Using EXPORT/IMPORT DATA (ABAP/4 memory).

Using SPA/GPA parameters(SAP memory).
Using EXPORT/IMPORT data (ABAP/4 memory).

SPA/GPA parameters are field values saved globally in MEMORY. There are two WAYS to USE SPA/GPA PARMETERS:

• By setting field attributes in the SCREEN Painter.
• By using the SET PARAMETER or GET PARAMETER statements.

SPA/GPA parameters are field values saved globally in memory. There are two ways to use SPA/GPA parmeters:

BATCH DATA COMMUNICATION SESSION.

Batch Data Communication Session.

The first step in a BDC session is to identify the screens of the TRANSACTION that the PROGRAM will process. Next step is to WRITE a program to build the BDC table that will be used to submit the DATA to SAP. The final step is to submit the BDC table to the system in the BATCH mode or as a single transaction by the CALL TRANSACTION command.

The first step in a BDC session is to identify the screens of the transaction that the program will process. Next step is to write a program to build the BDC table that will be used to submit the data to SAP. The final step is to submit the BDC table to the system in the batch mode or as a single transaction by the CALL TRANSACTION command.

The information on the current SCREEN can be FOUND by SYSTEM 􀃆 STATUS COMMAND from any MENU.

The information on the current screen can be found by SYSTEM 􀃆 STATUS command from any menu.

The DATA in BDC tables is SAVED by USING the field NAME 'BDC_OKCODE' and field value of '/11'.

The data in BDC tables is saved by using the field name 'BDC_OKCODE' and field value of '/11'.

In all BDC tables the last ENTRY is to save the data by using the field NAME BDC_OKCODE and a field value of '/11'.

In all BDC tables the last entry is to save the data by using the field name BDC_OKCODE and a field value of '/11'.

A multiple line field is a special KIND of field which allows the user to ENTER multiple LINES of DATA into it.

A multiple line field is a special kind of field which allows the user to enter multiple lines of data into it.

To populate data into a multiple line field, an INDEX is ADDED to the field name to indicate which line is to be POPULATED by the BDC SESSION (Line index).

To populate data into a multiple line field, an index is added to the field name to indicate which line is to be populated by the BDC session (Line index).

No. The CALL TRANSACTION METHOD ALLOWS only a single transaction to be processed by SAP.

No. The CALL TRANSACTION method allows only a single transaction to be processed by SAP.

Yes.

Yes.

CALL TRANSACTION TRANS [ using bdctab MODE mode ].
Three POSSIBLE entries are there for MODE.

• A - Show all screens.
• E - Show only screens with errors.
• N - Show no screens.

CALL TRANSACTION trans [ using bdctab MODE mode ].
Three possible entries are there for MODE.

The database LAYER describes the DATA FORMATS used in the database.

The database layer describes the data formats used in the database.

The ABAP/4 LAYER DESCRIBES the DATA formats used by the ABAP/4 PROCESSOR.

The ABAP/4 layer describes the data formats used by the ABAP/4 processor.

The external LAYER is the plane at which the user sees and interacts with the data, that is, the data FORMAT in the user INTERFACE. This data format is INDEPENDENT of the database SYSTEM used.

The external layer is the plane at which the user sees and interacts with the data, that is, the data format in the user interface. This data format is independent of the database system used.

• The EXTERNAL LAYER.
• The ABAP/4 layer.
• The DATABASE layer.

• The external layer.
• The ABAP/4 layer.
• The database layer.

The SAP front-end s/w can either run on the same computer or on different computers provided for that purpose. User terminal input is accepted by the SAP terminal PROGRAM SAP GUI, converted to SAP proprietary format and sent to the SAP dispatcher. The dispatcher coordinates the information exchange between the SAP GUIs and the work processes. The dispatcher first places the processing request in request QUEUES, which it then processes. The dispatcher dispatches the requests ONE after another, to the available work process. The actual processing takes PLACE in the work process. When processing is COMPLETE, the result of a work process is returned via the dispatcher to the SAP GUI. The SAP GUI interprets the received data and generates the output screen for the user.

The SAP front-end s/w can either run on the same computer or on different computers provided for that purpose. User terminal input is accepted by the SAP terminal program SAP GUI, converted to SAP proprietary format and sent to the SAP dispatcher. The dispatcher coordinates the information exchange between the SAP GUIs and the work processes. The dispatcher first places the processing request in request queues, which it then processes. The dispatcher dispatches the requests one after another, to the available work process. The actual processing takes place in the work process. When processing is complete, the result of a work process is returned via the dispatcher to the SAP GUI. The SAP GUI interprets the received data and generates the output screen for the user.

In SAP TERMINOLOGY, a TRANSACTION is series of LOGICALLY connected DIALOG steps.

In SAP terminology, a transaction is series of logically connected dialog steps.

V1 and V2. V1 must be processed before V2. But, we can have more than one V2 LOGS.

V1 and V2. V1 must be processed before V2. But, we can have more than one V2 logs.

SPOOL requests are generated during DIALOG or background processing and placed in the spool database with information about the printer and print format. The actual DATA is places in the Tem Se (Temporary SEQUENTIAL OBJECTS).

Spool requests are generated during dialog or background processing and placed in the spool database with information about the printer and print format. The actual data is places in the Tem Se (Temporary Sequential objects).

COMMON PROGRAM INTERFACE COMMUNICATION.

Common Program Interface Communication.

The SAP GATEWAY PROCESS communicates with the clients based on the TCP/IP PROTOCOL.

The SAP Gateway process communicates with the clients based on the TCP/IP Protocol.

The MEANS of COMMUNICATION between R/2,R/3 and external applications is via the CPI-C HANDLER or SAP Gateway, USING the CPI-C PROTOCOL.

The means of communication between R/2,R/3 and external applications is via the CPI-C handler or SAP Gateway, using the CPI-C Protocol.

The UNION of all s/w COMPONENTS that are assigned to the same databases is CALLED as a SAP SYSTEM.

The union of all s/w components that are assigned to the same databases is called as a SAP system.

A S/W COMPONENT that uses the service (OFFERED by a s/w component) is CALLED a Client. At the same time these clients may ALSO be servers for other services.

A S/W component that uses the service (offered by a s/w component) is called a Client. At the same time these clients may also be servers for other services.

A component can consist of one PROCESS or a group and is then CALLED the server for the RESPECTIVE SERVICE.

A component can consist of one process or a group and is then called the server for the respective service.