Problems in processing batch input sessions

What are the problems in processing batch input sessions How is batch input process different from processing online

i) 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.

ii)if session processing fails data will not be transferred to SAP database table.

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

Creation of a batch input session

 An ABAP program creates a batch input session. We need to submit the program and the batch session in back ground. How to do it?

Please go to SM36 and create background job by giving job name,job class and job steps (JOB SCHEDULING)

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

Call transaction ABAP

What is the alternative to batch input session

Call transaction.

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

Alternative to batch input session ABAP

What is the alternative to batch input session


Call transaction.

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

BATCH INPUT SESSION ABAP

What is a batch input session


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.

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

Approach for writing a BDC program ABAP

What should be the approach for writing a BDC program


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

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

STEP 3:
DEPENDING UPON THE BDC TYPE i)call transaction(Write the program explicity)

ii) create sessions (sessions are created and processed.if success data will transfer).

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

What are field symbols and field groups. ABAP

What are field symbols and field groups  Have you used "component idx of structure" clause with field groups

• Field symbols
• Field groups 

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

ABAP Typical Structure

What is the typical structure of an ABAP/4 program

• HEADER 
• BODY
• FOOTER

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

DIFFERENCE BETWEEN SAP MEMORY AND ABAP MEMORY

What are the differences between SAP memory and ABAP memory

ABAP Memory is a memory area in the internal session (roll area) of an ABAP program. Data within this area is retained within a sequence of program calls, allowing you to pass data between programs that call one another. It is also possible to pass data between sessions using SAP Memory.

SAP Memory is a memory area to which all sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session (as with ABAP memory) or to pass data from one session to another

SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). 

These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens ABAP/4 Memory ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. 

Data within this area remains intact during a whole sequence of program calls. To pass data to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse. 

The SAP memory, otherwise known as the global memory, is available to a user during the entire duration of a terminal session. Its contents are retained across transaction boundaries as well as external and internal sessions. The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory. ABAP/4 memory The contents of the ABAP/4 memory are retained only during the lifetime of an external session (see also Organization of Modularization Units). 

You can retain or pass data across internal sessions. The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory. This code is from which program you want to export to the ABAP memory: export ist_resb to memory id 'ZPPC0122_FD'. where ist_resb is the internal table name & ZPPC0122_FD is the include name of my program ZPPC0122. 

This code is from which program you want to import from the ABAP memory import *ist_resb *= ist_resb from memory id 'ZPPC0122_FD'. where ist_resb This internal table is the importing program internal table. ist_resb This internal table is the exporting program internal table. But remember in both the program you have defined the same internal table with same structure Nowadays Export & Import statement is OBSOLETE it gives SLIN CHECK ERROR in SAP 6.0 Version

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

TYPES OF LUW's IN ABAP

Different types of LUWs. What r they?

Two types of LUW are:

DB LUW 


A database LUW is the mechanism used by the database to ensure that its data is always

consistent. A database LUW is an inseparable sequence of database operations that ends with a database

commit. The database LUW is either fully executed by the database system or not at all. Once a database

LUW has been successfully executed, the database will be in a consistent state. If an error occurs within a

database LUW, all of the database changes since the beginning of the database LUW are reversed. This

leaves the database in the state it had before the transaction started.

SAP LUW  


A logical unit consisting of dialog steps, whose changes are written to the database in a single

database LUW is called an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and

be executed using a series of different work processes.

Database Logical Unit of Work (LUW) 

From the point of view of database programming, a database LUW is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been successfully executed, the database will be in a consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are reversed. This leaves the database in the state it was in before the transaction started.

The database changes that occur within a database LUW are not actually written to the database until after the database commit. Until this happens, you can use a database rollback to reverse the changes. In the R/3 System, database commits and rollbacks can be triggered either implicitly or using explicit commands.

Implicit Database Commits in the R/3 System

A work process can only execute a single database LUW. The consequence of this is that a work process must always end a database LUW when it finishes its work for a user or an external call. Work processes trigger an implicit database commit in the following situations:

· When a dialog step is completed    Control changes from the work process back to the SAP GUI.

· When a function module is called in another work process (RFC).  Control passes to the other work process.

· When the called function module (RFC) in the other work process ends. Control returns to the calling work process.

· When a WAIT statement interrupts the work process.

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

SYSTEM FIELDS IN ABAP

What are the system fields u have worked with? Explain? 

I had worked with the following (30) system fields:

1) SY-DBSYS - Central Database

2) SY-HOST - Server

3) SY-OPSYS - Operating System

4) SY-SAPRL - SAP Release

5) SY-SYSID - System Name

6) SY-LANGU - User Logon Language

7) SY-MANDT - Client

8) SY-UNAME - Logon User Name

9) SY-DATLO - Local Date

10) SY-DATUM - Server Date

11) SY-TIMLO - Local Time

12) SY-UZEIT - Server Time

13) SY-DYNNR - Screen Number

14) SY-REPID - Current ABAP program

15) SY-TCODE - Transaction Code

16) SY-ULINE - Horizontal Line

17) SY-VLINE - Vertical Line

18) SY-INDEX - Number of current loop Pass

19) SY-TABIX - Current line of internal table

20) SY-DBCNT - Number of table entries processed

21) SY-SUBRC - Return Code

22) SY-UCOMM - Function Code

23) SY-LINCT - Page Length of list

24) SY-LINNO - Current Line

25) SY-PAGNO - Current Page Number

26) SY-LSIND - Index of List

27) SY-MSGID - Message Class

28) SY-MSGNO - Message Number

29) SY-MSGTY - Message Type

30) SY-SPONO - Spool number during printing

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

DIFFERENCE BETWEEN SY-TABIX and SY-INDEX

Difference between SY-TABIX and SY-INDEX? Where it is used?

Can u check SY-SUBRC after perform?

SY-TABIX 

• - Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.
•  APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.
• COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE,SY-TABIX is set to 0.
• LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SYTABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.
•  READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.
•  SEARCH FOR sets SY-TABIX to the index of the table line in which the search string is found.

SY_INDEX - In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.

SY-TABIX - Current line of an internal table. SY-TABIX is set by the statements below, but only for index tables. The field is either not set or is set to 0 for hashed tables.

* APPEND sets SY-TABIX to the index of the last line of the table, that is, it contains the overall number of entries in the table.

* COLLECT sets SY-TABIX to the index of the existing or inserted line in the table. If the table has the type HASHED TABLE, SY-TABIX is set to 0.

* LOOP AT sets SY-TABIX to the index of the current line at the beginning of each loop lass. At the end of the loop, SY-TABIX is reset to the value that it had before entering the loop. It is set to 0 if the table has the type HASHED TABLE.

* READ TABLE sets SY-TABIX to the index of the table line read. If you use a binary search, and the system does not find a line, SY-TABIX contains the total number of lines, or one more than the total number of lines. SY-INDEX is undefined if a linear search fails to return an entry.

* SEARCH FOR sets SY-TABIX to the index of the table line in which the search string is found.

SY_INDEX - In a DO or WHILE loop, SY-INDEX contains the number of loop passes including the current pass.

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk

SYSTEM FIELDS IN ABAP

What are the system fields? Explain?

The ABAP system fields are active in all ABAP programs. They are filled by the runtime environment, and you can query their values in a program to find out particular states of the system. Although they are variables, you should not assign your own values to them, since this may overwrite information that is important for the normal running of the program.

However, there are some isolated cases in which you may need to overwrite a system variable. For example, by

assigning a new value to the field SY-LSIND, you can control navigation within details lists.

ABAP system fields are always available in ABAP programs. The runtime system fills them according to context. They can then be used in programs to query the system status. System fields are variables but you should always treat them as though they were constants, and only read them. If you change their values, important information for the flow of the program may be lost. In exceptional circumstances, system fields may be overwritten in an ABAP program to control the system – for example, SY-LSIND (for navigating to a detail list).

With one exception the names and data types of the system fields are stored in the ABAP Dictionary in the SYST structure and realized as components of the predefined structure SY in ABAP programs.

The system field SY-REPID is not part of SYST or SY. Instead, every program contains the predefined constants SY-REPID and SYST-REPID, which both contain the name of the corresponding program. Furthermore, there are two predefined types of the same name, SY-REPID and SYST-REPID.

All system fields are addressed using SY field name and their types using SYST field name.

Alphabetical Overview

The following table lists the definitions of the structure SYST in the ABAP Dictionary alphabetically. The character in the first column indicates how you can use the corresponding system field in ABAP programs. Name is the name of the component, Type is the Dictionary data type, and Length is the field length defined in the Dictionary. The Use column shows in which environment the system fields are set. The Description indicates the content.

	Name	Type	Length	Use	Description
	ABCDE	CHAR	26	Constants	Alphabet (A,B,C,...)
	APPLI	RAW	2	Obsolete
	BATCH	CHAR	1	Background processing	Program runs in the background
	BATZD	CHAR	1	Obsolete
	BATZM	CHAR	1	Obsolete
	BATZO	CHAR	1	Obsolete
	BATZS	CHAR	1	Obsolete
	BATZW	CHAR	1	Obsolete
	BINPT	CHAR	1	Batch input	Program runs under batch input
	BREP4	CHAR	4	Obsolete
	BSPLD	CHAR	1	Obsolete
	CALLD	CHAR	1	ABAP Program	Call mode of ABAP program
	CALLR	CHAR	8	Printing Lists	ID for print dialog function
	CCURS	DEC	9	Obsolete
	CCURT	DEC	9	Obsolete
	CDATE	DATS	8	Obsolete
	CFWAE	CUKY	5	Internal
	CHWAE	CUKY	5	Internal
	COLNO	INT4	10	Creating Lists	Current column in the list
	CPAGE	INT4	10	List processing	Current page number
	CPROG	CHAR	40	ABAP Program	External procedure call

Confused? Feel free to ask

Your feedback is always appreciated.I will try to reply Ur queries as soon as time allows.
Regards,
SAPhelpdesk