SAP ABAP: ABAP ALV REPORTS SAMPLE CODES ERP,My SAP,ABAP,FICO,CRM,BW

Showing posts with label ABAP ALV REPORTS SAMPLE CODES. Show all posts

SAP Programming Report Back Order Processing

SAP programming report for back order processing is related to the Missing Parts Info System,this report displays all requirements for a given material and allows you to change prior commitment quantities.A planner would use this report to quickly assess demands and reallocate materials among manufacturing orders based on changing priorities and inventory availability.

The data displayed in backorder processing is based on commitments which are generally done automatically during order creation or release. Additional demand information will be reflected based on SD order allocations and the last MRP/MPS run. Consequently, backorder processing needs to consider this to ensure visibility of all potential demands. Backorder processing relies on the availability checking rules maintained in configuration and referenced on the MRP and sales view of the material master.

You can run backorder processing from the Missing Parts Info System, or call it up directly from the menu.

You can change the commitment quantity from the first screen within backorder processing. The menu options let you:

Branch to the stock overview
Display the individual demand element from MRP
Peg to upper-level demand
Drill down to dependent requirements

The first screen prompts you for material, plant, and the availability checking rule to be used, typically PP in production planning. This screen provides a vertical listing of demands in date sequence, with columns displaying the required quantity, committed quantity, and the cumulative ATP balance.

From the first screen, you can change the commitment quantity for a given demand either by choosing Change confirmation, or by choosing Edit → Change confirmation.

Other actions which may be taken from the menus or icons are as follows:

1. Save all changed commitment quantities (reallocations) (Backorder processing →Save).
2 Display Scope of Check to verify sources of demand and supply being considered in the check (Goto → Display scope of check; icon also available).
3. Filter the demands to show only SD requirements, reservations for production orders, or both (Settings menu).
4. Switch to columns reflecting receipts, demands, etc. by period (Settings →Period totals; icon also available).
5. Branch to the Stock Overview screen for the material (Settings → Stock overview).
6. Display the individual demand element (MRP element) (Environment → Disp MRP element).
7. Display pegging to upper-level demand or lower-level dependent requirements (Environment → Pegging or Order report; icons available).

To access the first screen for this report, choose Logistics → Production → Production control → Control → Backorder processing → Material
1. Enter 100-100 in Material.
2. Enter 3000 in Plant.
3. Enter PP in Checking rule.Checking rule PP is typically used for manufacturing orders.
4. Choose Enter.

This screen shows a recap of the total receipts, issues, and confirmed issues:

A Demand by date and source
B Committed quantity
C Cumulative ATP quantity
5. Choose Period totals to reformat the screen.

The screen is reformatted to bucket demand and supply by time periods.Time buckets may be changed using the icons provided on the toolbar.

D The Scope of check may be displayed using the icon.

Parameters defined in configuration for the checking rule are displayed here. This report is different from the Backorders report in that it focuses on production planning instead of sales and delivery.

Programming report on multi level bill of meterial
abap programming report on missing information

SAP ABAP ALV Report with Double Click Event

sap abap programming report sample code is about using alv double click event and its execution in a alv report.The sample coding is as shown below.

type-pools:
slis.
tables:
mara.

types:
begin of x_mara,
matnr like mara-matnr,
box(1),
end of x_mara.

data:
t_mara type standard table of x_mara,
t_events type SLIS_T_EVENT,
t_fieldcat type SLIS_T_FIELDCAT_ALV with header line.

data:
wa_matnr type x_mara,
WA_FIELDCAT LIKE t_fieldcat.

selection-screen begin of block b1.
select-options:
s_matnr for mara-matnr.
selection-screen end of block b1.

start-of-selection.

select matnr from mara into table t_mara
where matnr in s_matnr.
if sy-subrc = 0.
sort t_mara by matnr.
endif.

t_fieldcat-fieldname = 'BOX'.
t_fieldcat-seltext_l = 'Selection'.
t_fieldcat-tabname = 'T_MARA'.
t_fieldcat-checkbox = 'X'.
t_fieldcat-col_pos = 1.
t_fieldcat-input = 'X'.
t_fieldcat-edit = 'X'.
*T_FIELDCAT-hotspot = 'X'.
append t_fieldcat.

clear t_fieldcat.

t_fieldcat-fieldname = 'MATNR'.
t_fieldcat-seltext_l = 'Material'.
t_fieldcat-tabname = 'T_MARA'.
t_fieldcat-col_pos = 2.
T_FIELDCAT-hotspot = 'X'.
append t_fieldcat.

perform f_get_events.
perform f_display_report.

FORM USER_COMMAND1 USING R_UCOMM LIKE SY-UCOMM
RS_SELFIELD TYPE SLIS_SELFIELD.
data:
l_matnr like mara-matnr.

CALL FUNCTION 'CONVERSION_EXIT_MATN2_INPUT'
EXPORTING
input = rs_selfield-value
IMPORTING
OUTPUT = l_matnr.
IF sy-subrc 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

delete t_mara where matnr = l_matnr.
perform f_display_report.

perform f_display_report.
CALL TRANSACTION 'KO03' AND SKIP FIRST SCREEN.

ENDFORM. " USER_COMMAND1

&---------------------------------------------------------------------
*& Form f_display_report
----------------------------------------------------------------------
form f_display_report.

data:
l_prog like sy-repid.

l_prog = sy-repid.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING

I_INTERFACE_CHECK = ' '
I_BYPASSING_BUFFER =
I_BUFFER_ACTIVE = ' '

I_CALLBACK_PROGRAM = l_prog

I_CALLBACK_PF_STATUS_SET = ' '

I_CALLBACK_USER_COMMAND = 'USER_COMMAND1'

I_CALLBACK_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_TOP_OF_PAGE = ' '
I_CALLBACK_HTML_END_OF_LIST = ' '
I_STRUCTURE_NAME =
I_BACKGROUND_ID = ' '
I_GRID_TITLE =
I_GRID_SETTINGS =
IS_LAYOUT =

IT_FIELDCAT = t_fieldcat[]

IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =

I_DEFAULT = 'X'

I_SAVE = ' '
IS_VARIANT =
IT_EVENTS =
IT_EVENT_EXIT =
IS_PRINT =
IS_REPREP_ID =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IT_ALV_GRAPHICS =
IT_ADD_FIELDCAT =
IT_HYPERLINK =
I_HTML_HEIGHT_TOP =
I_HTML_HEIGHT_END =
IT_EXCEPT_QINFO =
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =

TABLES
t_outtab = t_mara

EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2

.
IF sy-subrc 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

endform. " f_display_report

here all meterials are displayed, as N when i click on the material number it will delete the selected material from the list and it will display's the report, like wise your can check the interactive event how it will works.

sap sales order programming report

ABAP Report ALV Block List in SAP Programming

This sap programming report with sample code using abap programming language explains you how to use alv block list to append the report.

REPORT ZALVBLOCK .

TYPE-POOLS : SLIS.

TABLES : AFKO,AFPO.

TYPES : BEGIN OF SAFPO ,
AUFNR LIKE AFPO-AUFNR,
POSNR LIKE AFPO-POSNR,
PLNUM LIKE AFPO-PLNUM,
STRMP LIKE AFPO-STRMP,
MATNR LIKE AFPO-MATNR,
PSMNG LIKE AFPO-PSMNG,
MEINS LIKE AFPO-MEINS,
END OF SAFPO.
TYPES : BEGIN OF SAFKO,
AUFNR LIKE AFKO-AUFNR,
END OF SAFKO.
DATA : IAFKO TYPE TABLE OF SAFKO WITH HEADER LINE,
IAFPO TYPE TABLE OF SAFPO WITH HEADER LINE.

DATA : IFIELDCAT1 TYPE SLIS_T_FIELDCAT_ALV,
WFIELDCAT1 TYPE SLIS_FIELDCAT_ALV,
ILAYOUT1 TYPE SLIS_LAYOUT_ALV,
IEVENT1 TYPE SLIS_T_EVENT,
WEVENT1 TYPE SLIS_ALV_EVENT,
IKEYINFO1 TYPE SLIS_KEYINFO_ALV.

DATA : IFIELDCAT2 TYPE SLIS_T_FIELDCAT_ALV,
WFIELDCAT2 TYPE SLIS_FIELDCAT_ALV,
ILAYOUT2 TYPE SLIS_LAYOUT_ALV,
IEVENT2 TYPE SLIS_T_EVENT,
WEVENT2 TYPE SLIS_ALV_EVENT.

SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.

SELECT-OPTIONS : S_AUFNR FOR AFKO-AUFNR,
S_GLTRP FOR AFKO-GLTRP.

SELECTION-SCREEN END OF BLOCK B1.
START-OF-SELECTION.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_INIT'
EXPORTING
I_CALLBACK_PROGRAM = SY-REPID.

I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
IT_EXCLUDING =

.

PERFORM GET_DATA.
PERFORM BUILD_FIELDCAT.
PERFORM BUILD_LAYOUT.
PERFORM BUILD_EVENT.
PERFORM BUILD_KEYINFO.

PERFORM BUILD_FIELDCAT2.
PERFORM BUILD_LAYOUT2.
PERFORM BUILD_EVENT2.

PERFORM DISPLAY_BLOCK1.

PERFORM DISPLAY_BLOCK2.

CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_DISPLAY'

EXPORTING
I_INTERFACE_CHECK = ' '
IS_PRINT =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =

EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2
.
IF SY-SUBRC 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.
&---------------------------------------------------------------------
*& Form GET_DATA
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM GET_DATA .
SELECT AUFNR FROM AFKO INTO CORRESPONDING FIELDS OF TABLE IAFKO
WHERE AUFNR IN S_AUFNR AND GLTRP IN S_GLTRP.

SELECT AUFNR POSNR PLNUM STRMP MATNR PSMNG MEINS FROM AFPO INTO CORRESPONDING FIELDS OF TABLE
IAFPO WHERE AUFNR IN S_AUFNR.
ENDFORM. " GET_DATA
&---------------------------------------------------------------------
*& Form BUILD_FIELDCAT
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM BUILD_FIELDCAT .
REFRESH : IFIELDCAT1.

*WFIELDCAT1-FIELDNAME = 'AUFNR'.
*WFIELDCAT1-COL_POS = '1'.
*WFIELDCAT1-SELTEXT_L = 'Order No'.
*APPEND WFIELDCAT1 TO IFIELDCAT1.
*CLEAR WFIELDCAT1.
WFIELDCAT1-FIELDNAME = 'GLTRP'.
WFIELDCAT1-COL_POS = '1'.
WFIELDCAT1-SELTEXT_L = 'Basic Finish Time'.
APPEND WFIELDCAT1 TO IFIELDCAT1.
CLEAR WFIELDCAT1.

WFIELDCAT1-FIELDNAME = 'GSTRP'.
WFIELDCAT1-COL_POS = '2'.
WFIELDCAT1-SELTEXT_L = 'Basic Start Time'.
APPEND WFIELDCAT1 TO IFIELDCAT1.
CLEAR WFIELDCAT1.

WFIELDCAT1-FIELDNAME = 'GAMNG'.
WFIELDCAT1-COL_POS = '3'.
WFIELDCAT1-SELTEXT_L = 'Total Order Qty'.
APPEND WFIELDCAT1 TO IFIELDCAT1.
CLEAR WFIELDCAT1.

WFIELDCAT1-FIELDNAME = 'GMEIN'.
WFIELDCAT1-COL_POS = '4'.
WFIELDCAT1-SELTEXT_L = 'UOM'.
APPEND WFIELDCAT1 TO IFIELDCAT1.
CLEAR WFIELDCAT1.

ENDFORM. " BUILD_FIELDCAT
&---------------------------------------------------------------------
*& Form BUILD_LAYOUT
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM BUILD_LAYOUT .
ILAYOUT1-COLWIDTH_OPTIMIZE = 'X'.
ILAYOUT1-ZEBRA = 'X'.

ENDFORM. " BUILD_LAYOUT
&---------------------------------------------------------------------
*& Form BUILD_EVENT
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM BUILD_EVENT .

WEVENT1-FORM = 'TOPOFLIST1'.
WEVENT1-NAME = SLIS_EV_TOP_OF_LIST.
APPEND WEVENT1 TO IEVENT1.

ENDFORM. " BUILD_EVENT
&---------------------------------------------------------------------
*& Form DISPLAY_BLOCK1
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM DISPLAY_BLOCK1 .
*CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_HS_APPEND'

EXPORTING
IS_LAYOUT = ILAYOUT1
IT_FIELDCAT = IFIELDCAT2
IS_KEYINFO = IKEYINFO1
I_HEADER_TABNAME = 'IAFKO'
I_ITEM_TABNAME = 'IAFPO'
IT_EVENTS = IEVENT1
- IT_SORT =
- I_TEXT = ' '
TABLES
T_OUTTAB_HEADER = IAFKO
T_OUTTAB_ITEM = IAFPO
- EXCEPTIONS
- PROGRAM_ERROR = 1
- MAXIMUM_OF_APPENDS_REACHED = 2
- OTHERS = 3
.

*IF SY-SUBRC 0.

- MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
- WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

*ENDIF.
*
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
IS_LAYOUT = ILAYOUT1
IT_FIELDCAT = IFIELDCAT1
I_TABNAME = 'IAFKO'
IT_EVENTS = IEVENT1

IT_SORT =
I_TEXT = ' '

TABLES
T_OUTTAB = IAFKO
EXCEPTIONS
PROGRAM_ERROR = 1
MAXIMUM_OF_APPENDS_REACHED = 2
OTHERS = 3
.
IF SY-SUBRC 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.
ENDFORM. " DISPLAY_BLOCK1

FORM TOPOFLIST1.

WRITE :/10 'TABLE AFKO CONTENTS'.
WRITE :/(30) SY-ULINE.

ENDFORM.
&---------------------------------------------------------------------
*& Form BUILD_FIELDCAT2
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM BUILD_FIELDCAT2 .
REFRESH : IFIELDCAT2.
WFIELDCAT2-FIELDNAME = 'AUFNR'.
WFIELDCAT2-COL_POS = '1'.
WFIELDCAT2-SELTEXT_L = 'Order No'.
APPEND WFIELDCAT2 TO IFIELDCAT2.
CLEAR WFIELDCAT2.

WFIELDCAT2-FIELDNAME = 'POSNR'.
WFIELDCAT2-COL_POS = '2'.
WFIELDCAT2-SELTEXT_L = 'Order Item No'.
APPEND WFIELDCAT2 TO IFIELDCAT2.
CLEAR WFIELDCAT2.

WFIELDCAT2-FIELDNAME = 'PLNUM'.
WFIELDCAT2-COL_POS = '3'.
WFIELDCAT2-SELTEXT_L = 'Planned Order No'.
APPEND WFIELDCAT2 TO IFIELDCAT2.
CLEAR WFIELDCAT2.

WFIELDCAT2-FIELDNAME = 'STRMP'.
WFIELDCAT2-COL_POS = '4'.
WFIELDCAT2-SELTEXT_L = 'Strt Dt Plnd ordr No'.
APPEND WFIELDCAT2 TO IFIELDCAT2.
CLEAR WFIELDCAT2.

WFIELDCAT2-FIELDNAME = 'MATNR'.
WFIELDCAT2-COL_POS = '5'.
WFIELDCAT2-SELTEXT_L = 'Material No'.
APPEND WFIELDCAT2 TO IFIELDCAT2.
CLEAR WFIELDCAT2.

WFIELDCAT2-FIELDNAME = 'PSMNG'.
WFIELDCAT2-COL_POS = '6'.
WFIELDCAT2-SELTEXT_L = 'Pland Ordr Qty'.
APPEND WFIELDCAT2 TO IFIELDCAT2.
CLEAR WFIELDCAT2.

WFIELDCAT2-FIELDNAME = 'MEINS'.
WFIELDCAT2-COL_POS = '7'.
WFIELDCAT2-SELTEXT_L = 'UOM'.
APPEND WFIELDCAT2 TO IFIELDCAT2.
CLEAR WFIELDCAT2.
ENDFORM. " BUILD_FIELDCAT2
&---------------------------------------------------------------------
*& Form BUILD_LAYOUT2
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM BUILD_LAYOUT2 .
ILAYOUT2-COLWIDTH_OPTIMIZE = 'X'.
ILAYOUT2-ZEBRA = 'X'.
ENDFORM. " BUILD_LAYOUT2
&---------------------------------------------------------------------
*& Form BUILD_EVENT2
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM BUILD_EVENT2 .

WEVENT2-FORM = 'TOPOFLIST2'.
WEVENT2-NAME = SLIS_EV_TOP_OF_LIST.
APPEND WEVENT2 TO IEVENT2.
CLEAR WEVENT2.

ENDFORM. " BUILD_EVENT2
&---------------------------------------------------------------------
*& Form DISPLAY_BLOCK2
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM DISPLAY_BLOCK2 .
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
IS_LAYOUT = ILAYOUT2
IT_FIELDCAT = IFIELDCAT2
I_TABNAME = 'IAFPO'
IT_EVENTS = IEVENT2

IT_SORT =
I_TEXT = ' '

TABLES
T_OUTTAB = IAFPO

EXCEPTIONS
PROGRAM_ERROR = 1
MAXIMUM_OF_APPENDS_REACHED = 2
OTHERS = 3

.
IF SY-SUBRC <> 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

ENDFORM. " DISPLAY_BLOCK2

FORM TOPOFLIST2.
WRITE : /10 'TABLE AFPO CONTENTS'.
WRITE :/(35) SY-ULINE.
ENDFORM.
&---------------------------------------------------------------------
*& Form BUILD_KEYINFO
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="" p2="" text="">

----------------------------------------------------------------------
FORM BUILD_KEYINFO .
IKEYINFO1-HEADER01 = 'AUFNR'.
IKEYINFO1-ITEM01 = 'AUFNR'.
ENDFORM. " BUILD_KEYINFO

ABAP ALV Hirarchical Report Sample Code in sap programming

ABAP programming report for alv hierarchical report in sample code gives you a real time report that tells you in detail with example coding how to write the abap programming report.

&---------------------------------------------------------------------
*& Report Z_HIERARCHIAL_ALV *
*& *
&---------------------------------------------------------------------
*& *
*& *
&---------------------------------------------------------------------

REPORT ZGDEMO_HIERARCHIAL_ALV_9AM .
TYPE-POOLS SLIS.
DATA : IT_EKKO TYPE TABLE OF EKKO,
IT_EKPO TYPE TABLE OF EKPO.

DATA WA_KEYINFO TYPE SLIS_KEYINFO_ALV.

****************************************

START-OF-SELECTION. *

****************************************
START-OF-SELECTION.
PERFORM READ_DATA.

PERFORM FILL_KEYINFO.

PERFORM DISPLAY_DATA.

&---------------------------------------------------------------------
*& Form READ_DATA
&---------------------------------------------------------------------
form READ_DATA .

SELECT * INTO TABLE IT_EKKO FROM EKKO UP TO 20 ROWS.

IF NOT IT_EKKO IS INITIAL.
SELECT * INTO TABLE IT_EKPO FROM EKPO
FOR ALL ENTRIES
IN IT_EKKO
WHERE EBELN = IT_EKKO-EBELN.
ENDIF.

endform. " READ_DATA

&---------------------------------------------------------------------
*& Form FILL_KEYINFO
&---------------------------------------------------------------------

text

----------------------------------------------------------------------
form FILL_KEYINFO .
WA_KEYINFO-HEADER01 = 'EBELN'.
WA_KEYINFO-ITEM01 = 'EBELN'.
WA_KEYINFO-ITEM02 = 'EBELP'.

endform. " FILL_KEYINFO
&---------------------------------------------------------------------
*& Form DISPLAY_DATA
&---------------------------------------------------------------------

text

----------------------------------------------------------------------

--> p1 text
<-- li="li" p2="p2" text="text">

----------------------------------------------------------------------
form DISPLAY_DATA .
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
EXPORTING

I_INTERFACE_CHECK = ' '

I_CALLBACK_PROGRAM = SY-REPID

I_CALLBACK_PF_STATUS_SET = ' '
I_CALLBACK_USER_COMMAND = ' '
IS_LAYOUT =
IT_FIELDCAT =
IT_EXCLUDING =
IT_SPECIAL_GROUPS =
IT_SORT =
IT_FILTER =
IS_SEL_HIDE =
I_SCREEN_START_COLUMN = 0
I_SCREEN_START_LINE = 0
I_SCREEN_END_COLUMN = 0
I_SCREEN_END_LINE = 0
I_DEFAULT = 'X'
I_SAVE = ' '
IS_VARIANT =
IT_EVENTS =
IT_EVENT_EXIT =

i_tabname_header = 'IT_EKKO'
i_tabname_item = 'IT_EKPO'
I_STRUCTURE_NAME_HEADER = 'EKKO'
I_STRUCTURE_NAME_ITEM = 'EKPO'
is_keyinfo = WA_KEYINFO

IS_PRINT =
IS_REPREP_ID =
I_BYPASSING_BUFFER =
I_BUFFER_ACTIVE =
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =

tables
t_outtab_header = IT_EKKO
t_outtab_item = IT_EKPO

EXCEPTIONS
PROGRAM_ERROR = 1
OTHERS = 2

.
IF sy-subrc 0.

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

endform. " DISPLAY_DATA

sap sales order programming report

sap sales and distribution back orders report in abap
sap sales and distribution incoming order report
sales in erp programming invoice report
sap abap programming in mm module report about purchase order
abap programming sample report for materiel documents
sap programming report with oops concept

SAP ABAP HR programming report sample for EEOC

SAP ABAP HR programming report about EEO 1 report deals with compiling the EEO-1 data that US employers need to file every year with the Equal Employment Opportunity Commission (EEOC). The resulting statistic is formatted in accordance with the standards for computerized output prescribed by the EEOC. Section G (Certification) is omitted, since multi establishment employers are required to file the certified consolidated report on the original EEO-1 form.

This report only runs for employees who have a valid organizational assignment infotype 0001, including assignment to a personnel area/subarea and job. Employees must also have a valid additional personal data infotype 0077, including assignment of ethnic origin, and veteran status.
In addition, you must maintain the following system tables:

T5U0P: Every personnel area subarea has to be maintained. The following country-specific fields—with country modifier 10 (US)—must be completed:

REPUN: Reporting organizational unit
COIND: Company ID
EEOHQ: Headquarters indicator (checkbox). Must be checked ONLY for headquarters unit.
SICNO: Standard industry code (T5USC)
EINUM: INS employer ID
DANDB: Dun & Bradstreet ID

T5U13—Jobs: Country-specific field for country modifier 10 (US). For each job, the field EEOCT - EEO job category must be maintained. Standard EEO job categories are delivered.
All EEO categories must be entered into feature EEOCT, which converts job categories to the row numbers (01 to 09) in the EEO-1 report. Features may be accessed using transaction PE03.

T5UAD: For every reporting unit, an address should be created.
T5URU - EEO unit number for each reporting unit should be then created. For each EEO unit number, an address has to be assigned.

T5U0E - EEO Record: This report uses this table in several ways. The table provides:

Previously reported totals per reporting unit
Settings (that is, section C and E) for the current report
Totals for the current period (if needed)
T505R - Ethnic origin: If table T505R is modified or extended to allow additional ethnic categories, feature EEOCL (transaction PE03) must be modified to reflect those changes. Feature EEOCL yields the EEO employee category based on ethnic origin and gender.

Depending on when you run the report, you will need to consider special requirements concerning totals previously reported to the government.

. Running the report for the first time: For the period that provides the previous reported total, a record needs to be created for EACH reporting unit in T5U0E. This record should contain the totals per employee category and, preferably, the indicators for the questions in sections B and C reported for that period.

2. Running the report in subsequent periods: If the indicators for section B and C have not changed, it is not necessary to create the records for the current periods, since the report will read the indicators from the previous period. If the indicators have changed, a new record for the current period, containing the correct settings must be manually created. If desired, the report will update table T5U0E with the totals for the current period when the report is run.

Choose PA_UPDAT to create or modify the entry per reporting unit in table T5U0E .

EEOCT (Feature): Depending on the value used in table T5U13 (field EEOCT), this feature must be modified to yield the correct row number for each EEO category.

This report includes:

Variants
Execution (and print) in background
Standard selection fields available
Additional selection fields via the Further Selections or Matchcodes buttons
Data output formatted in accordance with the standards for computerized output prescribed by the EEOC.

To run this abap report

choose System → Services → Reporting and enter RPSEEOU1 in the Program field. Then,
choose Execute to run the report.

1. Under Period, enter 06/01/1998 to 06/30/1998 in Other period and Person selection period.
2. Under Selection, enter 300 in Personnel area and 0001 in personnel subarea to limit the selection of employees.
3. Enter +3+ in Status 1/status 2/status 3 (employment status) to include only active employees.
4. Under Additional data, enter 00 1996 in Previous period. This determines the period from which the previously reported totals are read.
5. Enter 06 1996 in Current period.

This determines the period from which the indicators for sections C and E are read.

6. Choose Execute.

SAP ABAP FI/CO Reconciliation in Company Code Currency Report

Reconciliation in Company Code Currency Report of SAP ABAP provides an overview of the reconciliation postings necessary to ensure that FI and CO postings made across company codes, business areas, and functional areas within the selected company code have been recorded to the

General Ledger (G/L), both on a period and a fiscal year-to-date basis. The company code currency is used for this reconciliation.

The accounting department uses this report to ensure that financial and controlling transactions reconcile for CO postings that occur across company codes, business areas, and functional areas. Since cross-company code postings affect financial statements, this report monitors the expected reconciliation postings based on CO data, and the reconciliation postings made to FI.

You must enter a value in the selection fields before running this report. You may leave the company code selection blank, and obtain a list that contains values for all company codes for which reconciliation postings have been made. If you choose to use a group of company codes, you must first create a set that contains them in order to access Report Painter/Report Writer reports.

You can run a context-sensitive actual line item report from this reconciliation ledger report. For example, when positioning the cursor on a cell, only the line items that make up the cell total will appear. The actual line items for a reconciliation ledger report can be executed for either one cell, or a range of cells.

By double-clicking on any subtotals in the report, the amount of detail that makes up the subtotal can either be hidden or displayed. For example, double-clicking on a cost element summary line will hide the debit/credit detail. To display this detail again, double-click on this line again.

This report contains data obtained from postings to the reconciliation ledger. This is a fixed special ledger to which postings are made when CO transactions span company codes, business areas, and functional areas. As such, the data cannot be changed or manipulated from the report.
The report contains two different blocks of data, as shown below. By navigating around these blocks, different types of reconciliation ledger data can be viewed.

To access the first screen for this sap abap report, choose Information systems → Accounting → Overhead costs and then, Cost elements → Report selection.

From the reporting tree, choose the following report: Reconciliation CO/FI → In company code currency → CO/FI Reconciliation in CCde Crcy.

1. Enter 1997 in Fiscal year. This report runs for only one fiscal year at a time.

2. Enter 1 in Period. This report shows the reconciliation postings for the company code in the selected period.
In addition, the report shows a cumulative value of the reconciliation postings from period 1 through the selected period.

3. Enter 3000 in Or value(s). You may also enter a range of company codes, or a company code group.

4. Choose Execute.
As the report begins to run, a threshold value determines how detailed the output will be.

5. Choose Enter.

This screen shows the reconciliation accounts to which postings will be made from the reconciliation ledger. For primary cost elements, the system uses the same account. For secondary cost elements, the system determines the reconciliation account based on its configuration.

A CO postings to the reconciliation ledger
B FI postings to expense accounts
C Variance between the CO and FI postings
D Entries to the reconciliation ledger that have been made to FI (no values because the period-end process has not been executed)

6. Double-click on the reconciliation account to reveal its field text.

This screen shows the original data that generated the variance between CO and FI, and which posts to the G/L from the reconciliation ledger.

7. Choose Next columns.

This screen shows a cumulative view of the same data. Since the selected period is also period 1, the values are the same.

8. Choose Previous columns to navigate to the first block of data displayed in the report.

SAP FICO Profitability Analysis Plan and Actual Comparion

SAP FICO and in particular controlling wing ABAP report provides a contribution margin for divisions and products. Both actual and planned data list for the contribution margin, and a variance calculates for each value in it. This report summarizes revenues and contributions, and can do an in depth analysis of the margin for specific divisions or products.

A product line manager would use this report to monitor the performance of specific divisions and products and to identify the “bottom-line” impact of revenues and costs. Two features of this report, exception reporting and ranking, help to quickly identify both exceptional and marginal performers so that a product line manager can take immediate action to improve product performance.

You must set the Operating concern (but only when you first login). Choose Accounting → Controlling → Profitability analysis → Environment → Set operating concern. For the examples in this section, the operating concern is set to IDEA using cost-based profitability analysis.

All reports in profitability analysis are user-defined. This means you must configure and generate the operating concern before creating any reports and determine the rows, columns, variables, and general format by using drill down reporting (forms and reports).

Due to the configuration of this report, you must enter all selection options (that is, period range and fiscal year).

The profitability analysis line items which list are context sensitive. For example, when you position the cursor on a cell for a line item, only the reports that contain that line item show data. This improves performance of the report as a whole.

Once the original profitability analysis document appears, the original documents related to the line item may be retrieved. For example, from a sales document, a material master, customer master, billing document, and accounting document is available. From a direct financial entry, however, only the cost element and accounting documents are available. From settlement documents, the controlling object from which the settlement took place is generally available.

Two different views are available in this report:

1. Selected columns run across the report, while the characteristics (products, for example) run down the side.
2.All columns f or a single selected product show as rows for a contribution analysis.

You can analyze data using ranking lists, exception reporting, and sorting; list line items in the profitability analysis database; and access additional SAP data from this report.

This report contains data obtained from postings to cost-based CO-PA. As such, the data cannot be changed or manipulated from the report. Since cost-based—not account-based—CO-PA is used, value fields are used in the analysis instead of account numbers or cost elemets.

To access the first screen for this sap baap fico report, choose Information systems → Accounting → Profitability analysis Profitability report → Report selection.

From the reporting tree, choose the following report:

Plan- → Plan/Actual Comparison.

The initial screen looks like this in sap systems.

The numbers marked in the screen represent the following.

1. Enter 1 in From period and 12 in To period. This report will not provide a periodic breakdown of the costs, only totals for the period range.
2. Enter 1998 in From Fiscal Year. This report runs for only one fiscal year at a time.
3. Choose Execute.

The initial output of the report is as shown and each number of the output is explained as below.

The default sales organization number (for example, 1000) cannot be changed. Divisions show in rows. In this example, all postings were assigned to a division. If postings were not assigned to a division, Not assigned would appear in the last row.

Gross revenue and contribution margin data show in columns. For each of these values, planned and actual data appear, along with the absolute and percentage variances.

4. Double-click on the first division, Pumps. This screen shows the products within the Pumps division. Notice the breakdown of the Product characteristic as compared to the previous screen.
5. Choose Display to navigate to Division characteristic. This screen shows all Divisions.
6. Select the High Tech line.
7. Choose Enter.

Related Posts:

My sapcrm customers and consumer segmentation
Organizational challenges in crm and mysap solutions
Business View and Mysap.com
What is SAP R/3 introduction to mysap.com

SAP Finance Cost Center Summery Programming Report

This sap programming report of cost center summer and finance provides a summarized view of the costs, activities, and statistical key figures that posted to cost centers. It includes both planned and actual postings, and calculates an absolute and a percentage variance. In addition to a selected period, the report lists cumulative data from the beginning of the fiscal year through the selected period.

A cost center manager would use this report to monitor actual cost center performance against planned cost center performance, both on a periodic and cumulative basis. This report allows for a consolidated view of multiple cost centers and includes the balance of all cost center postings.

You must set the Controlling area before running the programming report. Choose Accounting → Controlling → Cost centers → Environment → Set controlling area. For the examples in this section, the controlling area is set to 2000. You must enter a value in the selection fields before running the report.

You may leave the cost center and cost element selection blank, so that all cost elements are selected. If you enter cost center groups and cost element groups, they must have already been set up. If they contain subtotals, hierarchy nodes should be created within the groups. Each hierarchy node then subtotals in this report.

To run this ABAP report, use one of the following access options:

Information systems → Accounting → Overhead costs
Cost centers → Report selection

From the reporting tree, choose the following report:
Plan/Actual Comparison → CCtr: Ongoing Period/Cumulated → CCtr: Current Period/Cumulated.

OR

Choose System → Services → Reporting and enter J1SISTQX in the Program field.
Then, choose Execute to run the report.

The sap system displays four columns for all sections of the report, including actual postings, planned data, and a calculation of the variance between the two, both as an absolute value and as a percentage (calculated by dividing the actual data by the planned).

By double-clicking on any subtotals in the report, the detail that makes up each subtotal can either be hidden or displayed. For example, double-clicking on the Internal activities line will hide the cost element detail. To display this detail again, double-click on this line.

This SAP ABAP report contains data obtained from cost center postings. As such, the data cannot be changed or manipulated from the report.

Example with screen shots of cost center report summery :

A cost center manager wants to monitor the variances for the cost center for the current period, as well as for the year. This report shows detailed postings for a cost center, including all planned and actual costs, activities, and statistical key figures.

To access the first screen for this report, choose Information systems → Accounting → Overhead costs Cost centers → Report selection. or

From the reporting tree, select the following report:
Plan/Actual Comparison → CCtr: Ongoing Period/Cumulated → CCtr: Current Period/Cumulated.

The out put screen is shown below.

The numbers of screen shots explains the following.

1. Under Selection values, enter 2000 in Controlling area.
2. Enter the year in Fiscal year (for example, 1997). This report runs for only one fiscal year at a time.
3. Enter 9 in Period. This entry means that all values from period 1 through period 9 will be selected for analysis of cumulative planned versus actual postings.
4. Enter 0 in Plan version.
5. Enter 3200 in Or value(s). You can also enter a range of cost centers, or a cost center group.
6. Enter OAS-TOTAL in Cost element group. This contains all cost elements.
7. Choose Execute.

The first screen of the report shows the cost elements, for which actual and planned costs are posted in the cost center.

The columns to the left of the cost elements contain the data for the selected period.
The columns to the right of the cost elements contain the data for the cumulative fiscal year through the selected period. Cost elements that are included in the cost element group, but for which no postings were made.

8. Choose Page Down to navigate to the next block of data.

This section of the screen shows the remaining cost element data. In this example, all cost elements posted to the cost center did not fit on the previous screen.

9. Choose Page Down to navigate to the next block of data.

These columns contain statistical postings made to the cost center. These cost elements posted to a controlling object, such as an internal order, but with a statistical reference to this cost center. These statistical postings are not reflected in the “real” postings seen in the previous section .

10. Choose Page Down to navigate to the next block of data.

These columns contain the activity quantities and corresponding unit of measure used in the postings, along with the absolute and percentage variances.

11. Choose Page Down to navigate to the next block of data.

The columns list the postings to statistical key figures, with the corresponding unit of measure. Absolute and percentage variances are calculated.

SAP Finance General Ledger Account Balance Report

SAP ABAP programming code is used in extracting data from different modules of SAP using ABAP coding. Evern some custom reports are available who are all ready prepared by the giant ERP i.e SAP to make the job of large companies simple to extract data. Following is one of that kind of ABAP code and report.

General Ledger Account Balance in SAP Finance :

The purpous of the ABAP report is to lists the general ledger account balances.

Primary output includes:

Balance carried forward at the beginning of the fiscal year
Debit total of the reporting period
Credit total of the reporting period
Debit or credit balances at the close of the period

The output is normally shown for a given fiscal year, but you may use period selection fields to narrow the search to a particular period.

You must select Fiscal year, Reporting periods, and Summarization levels before running this report.

However, limiting the selection criteria will speed up searches and provide more focused results.
The output control section of the first selection screen allows for sorting based either on a standard or a corporate group version.

The sort sequence of the standard version is by:

1. Company code
2. Account number
3. Business area

To run this report, use one of the following access options:

1.Information systems → Accounting → Financial accounting General ledger → Account balances

2.Choose System → Services → Reporting and enter RFSSLD00 in the Program field.

Then, choose Execute to run the report.

3.In the Command field, enter transaction F.08 and choose Enter.

Data presented in this report is from Finance G/L account balances. This SAP ABAP report does not allow manipulation of data.

Example :

Generate a simple list of G/L account balances for fiscal year 1996, including all sixteen posting periods in that year for 2 asset accounts. Use CAUS for the chart of accounts and 3000 for the company code.

To access the first screen for this report, choose Information systems → Accounting → Financial accounting General ledger → Account balances.

Each part of the screen represents the following.

1. Enter CAUS in Chart of Accounts.

2. Enter 1000 in G/L account.

3. The Multiple Selection for G/L account appears. The desired G/L accounts can be entered individually or as a range. In this example, enter 1000 and 11000.

The green arrow to the right of G/L account field (circled on the facing graphic) is highlighted indicating that additional accounts have been selected.

4. Enter 3000 in Company code and 1996 in Fiscal year.

5. Leave the Output control settings at standard values. In this example, use 0 for the Summarization level.

6. Choose Execute.

The result screen of SAP ABAP report can be summerised as explained below.

A The report display shows the company codes, the reporting periods, the currency, and the order of the information.

B According to the standard version the balances are separated by business area. The carry-forward balance is listed for each business area.

C The reporting debit balance, reporting credit balance, and the total debit balance are listed.

Related post :

SAP ABAP Finance general ledger Line items

SAP Finance Reports General Ledger Line items

SAP provides good integration between different modules and Finance is a very vital module for any large scale company. ABAP Programming is used to extract data from finance department and some times even default reports are useful for data extraction from resource.

General Ledger Line item report for SAP Finance: lists open or cleared items. It is used for open-item managed accounts. You can use parked documents as selection criteria to capture both posted and preliminary posting documents in the same programming report.

Similar to many other standard ABAP Programming reports, you can specify the key date which separates items posted before the key date and a range of dates for clearing.

To run this report, use one of the following access options:

1.Information systems → Accounting → Financial accounting
General ledger → Select report
Information systems → Account information → Line items → G/L line items

2. Choose System → Services → Reporting and enter RFSOPO00 in the Program field.
Then, choose Execute to run the report.

you can research the line items of a particular G/L account for a specified time period, such as an accrual account and the subsequent reversals of those accruals. This report can also be used in an audit to review documents and line items posted to a company code for a specified period. This report is a good starting point before going to the Display G/L Line Items (FBL3) or Displaying Documents (FB03).

Example report of ABAP:

Using a U.S. chart of accounts and a company code, create a simple listing of G/L line items with a given Open item at key date (default is system date at time of entry) and restricted selection criteria.

To access the G/L Line Items screen, choose

Information systems → Accounting → Financial accounting

General ledger → Select report.

From the reporting tree, choose the following report:

Information systems → Account information → Line items → G/L line items.

Follow the screen as shown in the figure with following points.

1. Enter CAUS in Chart of accounts.

2. Enter 3000 in Company code.

3. Open items at key date defaults to the system date but you can change it to any desired date.
The system selects all items that posted before the specified key date and are open for this period.

The Clearing date is usually the date of the paying document or the posting date of the invoice, whichever is the most recent.

4. Choose Execute.

The output of the report is as shown.

The parts of A and B are described below.

A The screen header shows the order in which information appears in the report.

The report list is sorted by:

Company code
Account number
Business area
Posting date

B For G/L account 099000:

Accruals were setup for the interest due on notes payable.

Documents with type SA 100000299 and 100000300 cleared with documents type AB 100000625 and 100000626.

The clearing document is cross referenced on the original document.

Related post is SAP finance general ledger report .

You can find a good number ALV Reports of SAP ABAP with sample codes here.

ABAP Sample Report on Finance General Ledger Accounts list

ABAP reporting is a vital part of SAP which helps in extracting data from different modules of SAP using ABAP. Here we are going to discuss some sample and important reports of ABAP which helps us to understand SAP and ABAP in a better way.

Finance General Ledger Accounts list

This report provides a listing of the General Ledger (G/L) accounts. The content can range from a simple description to more detailed information consisting of a G/L master record, such as document entry control and account management.

Depending on your specific needs, you can list the G/L accounts either as a simple range of accounts or as a combination of charts of accounts. You can base your selection on company codes, text, etc.

You can use this ABAP report to obtain a wide range of information:

1. Within the same chart of accounts, you can locate which G/L account is assigned to what company code.

2. If the reference field (Alternate account number) has been entered in the G/L master, you can create a list that has both the current account number and the reference number for the legacy chart of accounts.

3.Search with the output criteria of document entry control to determine which accounts are configured for automatic postings.

The selection screen of this sap abap report includes:

Variants
Dynamic selection options
User variables
Execution (and print) in background
The report list includes a listing of G/L accounts, grouped by account group.

To run this ABAP report, use one of the following access options:

1.Information systems → Accounting → Financial accounting
General ledger → Periodic Processing → Info System → Report Selection
Lists → Account → Company code acct directory → G/L accounts list

or

2.Choose System → Services → Reporting and enter RFSKVZ00 in the Program field.
Then, choose Execute to run the report.

This report contains data obtained from G/L account of SAP master records. As such, this data cannot be manipulated.

To access the first screen for this ABAP programming report, choose

Information systems → Accounting → Financial accounting
General ledger → Select report.

From the reporting tree, choose the following report:

Lists → Account → Company code acct directory → G/L accounts list.

1. Under General selections, enter CAUS in Chart of accounts.
2. Enter 3000 in Company code.
3. Choose Execute.

A The report output shows that the G/L accounts are selected for the U.S. chart of accounts.
B The display is sorted first by the G/L account and then by the company code.
C The listing of each G/L account shows the name of the account and any specific information for
the account.

In this programming ABAP example:

Account 1000 is for Land
Company code is 3000
Account belongs to the account
group ANL and is maintained in U.S. dollars (USD)

Remaining part of ABAP PROGRAMMING sample reports will be discussed in the further posts.

SAP ABAP Example report on Finance General Ledger with out programming :

Create a report for a range of accounts and company codes to determine which accounts are assigned to a certain company code.

In the selection screen of ABAP Program

1.Enter a range (for example, 200000 to 299999) in G/L account.
2. Enter CAUS in Chart of accounts to limit your range of G/L accounts.
3. Enter a range of company codes (for example, 3000 to 4000) in Company code.
4. Under Output control, select Creation data for company code.
5. Choose Execute as shown below .

The output screen of SAP ABAP Is as shown with symbols.
A Company codes (listed for each G/L account)
B Creation date and name of person who created the account assignment

Example Three for SAP FINANCE in abap programming :

Create a report to determine which accounts belong to which account group within a chart of accounts.

1.Enter CAUS in Chart of accounts.

2. Enter 3000 in Company code.

3. Scroll down the screen to the Output control.

4. Enter 2 in Account sorting. This option sorts the accounts first by account group, then by G/L
account.

5. Choose Execute.

The previous post deals with EDI tools for sap abap.
SAP Controlling and daily processing
SAP Financial and Controlling Overview
SAP Controlling Information System
SAP Financial Company Organization Customizing
SAP Controlling Creating General ledger accounts in sap controlling

LSMW in SAP ABAP

LSMW means Legacy System Migration Work Bench .SAP offers the Legacy System Migration (LSM) Workbench. The LSM Workbench is a SAP tool that facilitates the process of data transfer from non-SAP system (also called Legacy system) without additional programming to do data conversion. Wecan define the rules for the conversion. The LSM Workbench then generates an ABAP program and thus supports an important step in the process of data transfer.

It is a cross-application component (CA) of the SAP R/3 System and, therefore, is independent from the platform. The tool has interfaces with the Data Transfer Center and with batch input and direct input processing in R/3. The tool can be used in each of the different R/3 releases.

By combining the Data Transfer (DX) Workbench and the Legacy System Migration (LSM) Workbench in SAP Basis component Release 4.6, SAP has made substantial progress towards tackling one of the most costly and time-consuming implementation activities - the migration of legacy systems and the data transfer from ERP systems that are being replaced.

Data migration with the DX Workbench and the LSM Workbench guarantees maximum quality and consistency of your data in the SAP business solution. When data is imported, the system performs the same checks as it does during online entry. The update in your database is performed through the Standard Batch Input Program, Standard Direct Input Program and BAPIs.

Features of LSMW:

Instead of individual tables or field contents, the tool transfers complete business data objects (also called object class) such as Material Master, Supplier Master data. A migration object class is a unit combined from the business point of view, which can be used to transfer the data of all the legacy systems defined in the LSMW to the R/3 System.

The migration object class comprises the R/3 structures as well as the program used for data import. The batch and direct input technique is used to ensure consistency of data. For each migration object, a batch or direct input program has to be available in the SAP R/3 System.

The LSMW main functions are :

Definition of the legacy system structures and fields
Definition of object dependencies and assignment of conversion rules
The structure and field relationships between the legacy system and the R/3 System are defined in data mapping. The way how data is being processed during migration is determined by the conversion rules.
Data conversion
From the object dependencies, the LSMW generates conversion programs that translate the legacy system data.
Data import
Batch or direct input is used to import the data to the SAP R/3 System.

The additional functions of LSMW are :

Spreadsheet interface
Legacy system data in spreadsheet format can be processed.
Host interface
Legacy system data in a structured data format (that is, with record identifiers and correct sequence) can be processed.
Batch input recorder
The LSMW allows you to use the batch input recorder (shipped with the SAP R/3 standard system) in order to create user-specific classes of migration objects.

Automatic check functions
This function generates and performs value checks against check tables and fixed values specified in the Data Dictionary.

Constraints

The LSMW supports a single and complete transfer of data (initial data load) and also offers a restricted support of permanent interfaces. Thus, a periodic transfer of data is possible. It, however, does not include any functions for monitoring of permanent interfaces. The tool does not support any data export interfaces (outbound interfaces).