SAP Expert - All About SAP ABAP

Events in Report

2008-05-05T20:21:00.002+05:30

An event is a tag that identifies a section of code. The section of code associated with an event name and ends when a next name is encountered.

Some of the events are:

1. Initialization.
2. At Selection-Screen.
3. Start-of-Selection.
4. Top-of-Page.
5. end-of-Page.
6. End-of-Selection.
7. At line Selection
8. At PFn.
9. At User-command.

SAP has a inbuilt program called Driver Program which controls another program in the R/3 System.

DRIVER EVENTS:

Initialization.
At Selection-Screen.
Start-of-selection.
End-of Selection.
USER EVENTS:
At line-Selection
At PFn.

At User-Command.

PROGRAM EVENTS:
Top-of-Page.
End-of-Page.

What is message type?

2008-04-21T21:54:00.001+05:30

The message type defines the semantic context of an IDoc. The message type tells
the processing routines, how the message has to be interpreted.
The same IDoc data can be sent with different message types. E.g. The same IDoc
structure which is used for a purchase order can also be used for transmitting a sales
order. Imagine the situation that you receive a sales order from your clients and in
addition you receive copies of sales orders sent by an subsidiary of your company.

Example: The IDoc Type ORDERS01

2008-04-21T21:48:00.001+05:30

To allow an interference, here is a sample of IDoc type ORDERS01 which is used for purchase
orders and sales orders.

Purchasing and sales orders naturally share the same IDoc type because what is a
purchase order on the sender side will become a sales order on the receiver side.
Other than MATMAS01, the IDoc type ORDERS01 does not reflect the structure of
the underlying RDB entity, neither the one of SD (VA01) nor the one of MM
(ME21). The structure is rather derived from the EDI standards used in the
automobile industry. Unfortunately, this does not make it easier to read.
Note: With transaction WE05 you can monitor, if there are already any IDocs in
your system.

You can call transaction WE30 to display the structure of the IDoc type of the found
IDoc
If this IDoc would have been written to a file, the file content would have looked
similar to this:

ORDERS01 DEVCLNT100 INTERNAL...
...E1EDKA1 ....and here the data
...E1EDKA2 ....and here the data
...E1EDP19 ....and here the data

Basic Configuration in IDOC

2008-04-21T21:00:00.001+05:30

Define a new internal RFC destination INTERNAL
Explore both the transactions WEDI and SALE and adjust the settings as necessary
Use transaction BALE to generate an arbitrary IDoc

You can access most of the transactions used in the example below in the menu
WEDI and SALE.

We will assume, that we want to send material master data from the current system
to a remote system. To simulate this scenario we do not need to have a second
system. With a little trick, we can set up the system to send an IDoc back to the
sending client.

We will set up the system to use an RFC call to itself. Therefore we need to define
an RFC remote destination, which points back to our own client. There is a virtual
RFC destination called NONE which always refers to the calling client.
RFC destinations are installed with the transaction SM59. Create a new R/3
destination of type "L" (Logical destination) with the name INTERNAL and the
destination NONE.

Note: Do not use RFC type internal. Although you could create them manually, they
are reserved for being automatically generated. However, there is the internal
connection "NONE" or "BACK" which would do the same job as the destination we
are creating now.

The next step is defining a data port, which is referenced by the IDoc sending
mechanism to send the IDoc through. Declaring the port is done by transaction
WE21.
We will now declare an ALE connection from our client to the partner INTERNAL.
ALE uses IDocs to send data to a remote system. There is a convenient transaction
to send material master data as IDocs via the ALE.

The set up is done in transaction SALE. You first create a new ALE model, to avoid
interfering with eventual existing definitions. Then you simply add the IDoc
message MATMAS as a valid path from your client to INTERNAL.
In order to send the IDoc, you call the transaction BALE and choose the distribution
of material master data (BD10). Choose a material, enter INTERNAL as receiver
and go.

To see, which IDocs have been sent, you can use the transaction WE05. If you did
everything as described above, you will find the IDocs with an error status of 29,
meaning that there is no valid partner profile. This is true, because we have not
defined one yet.

Program for Outbound IDOC

2008-04-21T20:49:00.001+05:30

All IDoc data records are exchanged in a fixed format, regardless of the segment type. The
segment’s true structure is stored in R/3’s repository as a DDic structure of the same name.
The segment info tells the IDoc processor how the current segment data is structured
and should be interpreted. The information, which is usually the only interest, is the
name of the segment EDID4-SEGNAM.

The segment name corresponds to a data dictionary structure with the same name,
which has been created automatically when defining the IDoc segment definition
with transaction WE31 .

For most applications, the remaining information in the segment info can be ignored
as being redundant. Some older, non-SAP-compliant partners may require it. E.g.
the IDoc segment info will also store the unique segment number for systems, which
require numeric segment identification.

To have the segment made up for processing in an ABAP, it is usually wise to move
the segment data into a structure, which matches the segment definition.
For a segment of type e1maram the following coding is commonly used:

TABLES: e1maram.
. . .
MOVE edidd-sdata TO e1maram.

Then you can access the fields of the IDoc segment EDIDD-SDATA as fields of the
structure e1maram .

WRITE: e1maram-matnr.

The following coding sample, shows how you may read a MATMAS IDoc and
extract the data for the MARA and MARC segments to some internal variables and
tables.

DATA: xmara LIKE e1maram.
DATA: tmarc AS STANDARD TABLE OF e1marcm
WITH HEADER LINE.
LOOP AT edidd.
CASE edidd-segnam.
WHEN 'E1MARAM'.
MOVE edidd-sdata TO xmara.
WHEN 'E1MARCM'.
MOVE edidd-sdata TO tmarc.
APPEND tmarc.
ENDCASE.
ENDLOOP.
now do something with xmara and tmarc.

The IDoc Control Record

2008-04-21T20:38:00.001+05:30

The very first record of an IDoc package is always a control record. The structure of this
control record is the DDic structure EDIDC and describes the contents of the data contained in
the package.

The control record carries all the administrative information of the IDoc, such as its
origin, its destination and a categorical description of the contents and context of
the attached IDoc data. This is very much like the envelope or cover sheet that
would accompany any paper document sent via postal mail.

For R/3 inbound processing, the control record is used by the standard IDoc
processing mechanism to determine the method for processing the IDoc. This
method is usually a function module but may be a business object as well. The
processing method can be fully customised.

Once the IDoc data is handed over to a processing function module, you will no
longer need the control record information. The function modules are aware of the
individual structure of the IDoc type and the meaning of the data. In other words: for
every context and syntax of an IDoc, you would write an individual function module
or business object (note: a business object is also a function module in R/3) to deal
with.

The control record has a fixed pre-defined structure, which is defined in the data
dictionary as EDIDC and can be viewed with SE11 in the R/3 data dictionary. The
header of our example will tell us, that the IDoc has been received from a sender
with the name PROCLNT100 and sent to the system with the name DEVCLNT100 .
It further tells us that the IDoc is to be interpreted according to the IDoc definition
called MATMAS01 .

Structure of IDOC

2008-04-21T20:32:00.000+05:30

IDocs are basically a small number of records in ASCII format, building a logical
entity. It makes sense to see an IDoc as a plain and simple ASCII text file, even if it
might be transported via other means.

Any IDoc consists of two sections:
the control record

which is always the first line of the file and provides the administrative information.
the data record

which contains the application dependent data, as in our example below the material
master data.

We will discuss the exchange of the material master IDoc MATMAS in the
paragraphs that follow..

The definition of the IDoc structure MATMAS01 is deposited in the data dictionary
and can be viewed with WE30 .

What are IDocs?

2008-04-21T20:24:00.001+05:30

IDocs are structured ASCII files (or a virtual equivalent). They are the file format used by SAP
R/3 to exchange data with foreign systems.

IDocs are simple ASCII data streams. When they are stored to a disk file, the IDocs
are simple flat files with lines of text, where the lines are structured into data fields.
The typical structured file has records, each record starting with a leading string that
identifies the record type. Their specification is stored in the data dictionary.
IDocs is the acronym for Interchange Document. This indicates a set of (electronic)
information which builds a logical entity. An IDoc is e.g. all the data of a single
customer in your customer master data file, or the IDoc is all the data of a single
invoice.

IDoc data is usually exchanged between systems and partners that are completely
independent. Therefore, the data should be transmitted in a format that can easily be
corrected by the computer operators. It is therefore mandatory to post the data in a
human readable form.

Nowadays, this means that data is coded in ASCII format, including numbers which
are sent as a string of figures 0 to 9. Such data can easily be read with any text editor
on any computer, be it a PC, Macintosh, UNIX System, S/390 or any internet
browser.

The information which is exchanged by IDocs is called a message and the IDoc is
the physical representation of such a message. The name “messages” for the
information sent via IDocs is used in the same ways as other EDI standards. .
Everybody who has ever dealt with interface programming, will find IDocs very
much like the hierarchical data files used in traditional data exchange.
International standards like the ODETTE or VDA formats are designed in the same
way as IDocs are.

Other EDI standards like XML, ANSI X.12 or EDIFACT/UN are based on a data
description language. They differ principally from the IDocs concept, because they
use a programming language syntax (e.g. like Postscript or HTML) to embed the
data.

Download IDOC,ALE, EDI Book

2008-04-20T17:12:00.002+05:30

Learn your self after downloading this book.Infact this book is very good for basic concept on IDOCs.

http://www.savefile.com/files/1512902

Presentation on IDOC , ALE , EDI

2008-04-20T16:31:00.002+05:30

Download a nice presentaion from this link given below.

http://www.slideshare.net/shesagiri/ale-idoc-edi/

This is a very nice presentation available on net.

Learn SAP Script Online

2008-04-19T14:25:00.002+05:30

Sample Sapscripts Label Printing Program

A Sample SAP Scripts Reports

FAQ for Sap Scripts

Questions on PO SapScripts MEDRUCK

SapScript Question

Details information about SAP Barcodes

Delete Load program for SAPScript

Picture doesn't show in Print Preview

Import/Export SapScript form from PC file How do you backup sapscript layout sets? Can you download and upload? How?

How to Upload graphics (IMAGE) to your Sapscript?

How to convert Sapscript spools request to PDF?

SAPScripts - Developing SAPScript in different languages

SAPscripts How to calculate Totals and Subtotals

Retrieving data without modifying the original called program

Protect...Endprotect

Orientations in SAPSCRIPT

Print Footer notes only on the last page

Different font on the same line

SAP Printer commands in SAPScripts

SAP Scripts Boxes/Lines/Shading

Reading Text in SAPScripts

SAPScript Important Programs

SAPScript Transaction codes

SAP ABAP Performance tools

2008-04-19T14:22:00.001+05:30

Performance Tools

(i)Runtime Analysis

(ii) SQL Trace

SAP ABAP Performance factor :

2008-04-19T11:46:00.001+05:30

(i ) Runtime Analysis

(ii) SQL Trace

(iii) Internal Table Performance Improvements

(iv) Performance Tuning using Parallel cursor

(v)Performance tuning using GROUPBY

Concepts of Infotypes- Structure and Processing

2007-10-20T14:20:00.001+05:30

Infotypes:
An infotype represents a group of related data fields, provides information structure, facilitates data entry, and allows time dependent storage.

In other words we can say infotypes are information units used to enter the time dependent data of the employee.

Master data in HR is stored in infotypes. Each infotype pertains to a specific type of data.Each infotype has a database table associated with it.

Time constraints: Enable you to determine how the validity periods of infotype data records interact

Time constraint 1: Exactly one valid data record of the infotype in question must exist for the entire time that the employee belongs to the enterprise.

Time constraint 2: No more than one valid data record of the infotype in question can exist at any one time.

Time constraint 3: Any number of valid data records of the infotype in question can exist at any one time.

The prerequisites for the existence of a personnel or applicant number are infotypes 0000 Actions, 0001 Organizational Assignment, 0002 Personal Data, and 0003 Payroll Status.

Transparent tables for infotype

Each infotype has a transparent table. Each logical field for an infotype has a corresponding physical field on the database.
One physical table is stored on the database for each transparent table. The names of the physical table and logical table definition in the Dictionary are compatible.

The following naming convention applies to infotype tables; nnnn stands for the infotype number:

PAnnnn for transparent tables in Personnel Administration

PBnnnn for transparent tables in Recruitment

HRPnnnn for transparent tables in Personnel Planning

Example: For Infotype 0000, the corresponding database table associated with it is PA0000

Check and Control Tables for HR Infotypes

Check and Control Tables for HR Infotypes

Table T777D Infotypes - Dialog/Database Assignment is the central check table (domain
INFOTYP) for all HR infotypes (Administration and planning infotypes). It is used to store the names of all infotype-dependent repository objects (tables, structures, programs, and so on).

Table T77ID Infotypes: Enhancements to T777D is simply an enhancement of table T777D that exists for reasons of memory space.

Table T582A Infotypes - Customer-Specific Settings is used for customer settings in
Administration infotypes.

Table T77CD Infotypes - Customer-Specific Settings is used for customer settings in planning
infotypes.

The primary key of transparent table PAnnnn consists of the following key fields:

PERNR: the personnel number is the only unique key within a client for identifying an
employee. It is used to access the display and maintenance screens for an employee’s
master data and working time data (infotypes).

SUBTY: subtypes are subdivisions of infotypes. An infotype’s subtypes can have different
time constraints and form their own histories.

OBJPS: the object identification is used to make a distinction between records with the
same infotype, subtype, lock indicator, start date, and end date. For example, the child
number in infotype 0021 Family/Related Person.

SPRPS: the lock indicator for HR master data is used to lock and unlock data records,
which enables the “double verification principle” to be put into practice. In accordance with
this principle, at least two users are involved in the process of writing an active data record
to the database. One of the users creates a locked infotype record, and the other user
unlocks - that is, activates - the data record.

ENDDA: end date.

BEGDA: start date.

SEQNR: The Sequential Number is used to make a distinction between infotype records
that have the same key and time constraint '3' (any number of valid infotype data records
at any one time). Unlike the object identification, it is assigned by the system automatically.

Structure:

The Data Dictionary contains a Pnnnn structure for each infotype nnnn. The infotype structure
Pnnnn corresponds to the table PAnnnn. The Pnnnn structure of the infotype is used as the field
structure for the infotype entry screen (Transaction code PA30).

Basic form of an infotype:

Infotypes nnnn [name c] [occurs m] [mode n] [valid from comp1 to comp2].
nnnn can be 0000 to 9999.

0000 – 0999 are HR Master Data infotypes.
1000 – 1999 are HR Planning data infotypes.
2000 – 2999 are HR time data infotypes.
3000 – 8999 are not used
9000 – 9999 are used for the custom infotypes

Effect of the above syntax is

It creates an internal table as below...

DATA BEGIN OF c OCCURS m.
INCLUDE STRUCTURE Pnnnn.
DATA END OF c VALID BETWEEN comp1 AND comp2

If name option is not given in the syntax then the internal table will be created with the name
p

If occurs clause in not given then the size of an internal table would be 10 * size of the
structure pnnnn. That is in the place of ‘m’ it would be 10.

If valid clause is not given then the comp1 and comp2 values will be 01/01/1800 and
31/12/9999 respectively.

Mode n this clause can only be used with the LDB’s PCH and PNP. This addition stops this
infotype being automatically filled at the GET PERNR command.

The infotype records can be processed using the infotype structure when the report is run.

Processing Infotypes

Processing Single Infotype Record

We can process the Single records of an infotype using the following macros.

1.RP_PROVIDE_FROM_LAST Pnnnn SPACE PN-BEGDA PN-ENDDA.
This macro is used to retrieve the most recent record in the PN-BEGDA and PN-ENDDA data
selection period available in the structure Pnnnn for infotype nnnn

2. RP_PROVIDE_FROM_FIRST Pnnnn SPACE PN-BEGDA PN-ENDDA
This macro retrieves the earliest record for the given selection period.
If the infotype has subtypes, then replace SPACE with the subtype so, the data is retrieved based on
that subtype. If the retrieval is successful then the return code PNP-SW-FOUND will be ‘1’.

Processing All Infotype Records

Syntax: PROVIDE * FROM Pnnnn BETWEEN PN-BEGDA AND PN-ENDDA.
ENDPROVIDE

nnnn stands for 4-digit infotype number. The relationship between the data and the selection period
is established using the PN-BEGDA and PN- ENDDA variables.

Infotype List

Overview of PA and PD and Integration between PA and PD

2007-10-20T14:02:00.001+05:30

This explains how to use the ABAP programs, which set integration between PA and PD/OM. They are mainly used after data conversion, bulk updates or to correct errors caused by other programs.

Each program is explained in detail so you can decide which ones you need to run. To set up/fix full integration between PA and PD, they should be run in this sequence:

1. RHINTE00 – Transfer PA records into PD positions –batch
2. RHINTE20 – Create OM objects in PA tables – Online
3. RHINTE30 – Bulk update of infotype 0001
4. RHINTECHECK – Program to check PA to PD
5. RHCHECKV - Checks all inverse relationships

Overview

It is important to realize that in PA, there are tables that contain objects from OM, i.e. for those items displayed on infotype 0001 Organizational Assignment. Sometimes the tables can get ‘out of step’ with those in PD – table HRP1000.

The tables are:

T513, T513S Object type C (Job)
T528B, T528T Object types S (Position) and A (Work center)
T527X Object type O (Organizational unit)

RHINTE00

This loops through all employees in PA by looking at positions on infotype 0001. It checks the
corresponding person to position relationship exists in PD (A008), if not it is created.

RHINTE10

Generally, the program RHINTE20 will be used instead of this one. This program loops through the PD table HRP1000. For each job, position, work centre and organization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update work centers also. The main difference with this program as opposed to RHINTE20 is that this one has the option to delete items from the PA tables, which no longer exist in PD.

RHINTE20

This program loops through the PD table HRP1000. For each job, position, work centre and
organization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update work centers also. An example output will show:

Overview of PA and PD and Integration between PA and PD

2007-10-20T14:02:00.000+05:30

Expand the tree items to display a list of objects that can be created:

RHINTECHECK

When the above programs have been run, use this check program, which looks through all employees and reports any inconsistencies found between PA and PD.

Tick each item that you wish to be created, or click on the text

and click ‘select subtree’ to select them all then click to perform multiple updates. This program can prove to be ‘problematic’. If difficulties arise with it, try using RHINTE10 instead.

RHINTE30

This will create an infotype 0001 record with correct entries for org unit, job, position and work centre by looking through the organization structure. It creates a batch job, which must be run via SM35.

More details to follow.

RHCHECKV
This will check inverse relationships and create missing ones.

Learn ABAP HR Online-Overview & Features in HR Programming

2007-10-20T14:00:00.000+05:30

Overview & Features in HR Programming

The aim in the Human Resources component is to be able to process employee related data according to business requirements in an effective structure.The Human Resources module uses a system of data grouped together called infotypes.Infotypes mirror a quantity of connected data records; infotypes are identifiable through a four character numerical string [e.g. infotype Addresses (0006)] and a complete listing is included.You can save the infotypes as time-dependent to enable a retroactive evaluation ofEmployee data.The infotypes appear as an entry screen for the user, through which you can maintain infotype records. Infotypes can be processed individually or in fast entry mode.

Difference from conventional ABAP

Advanced Business Application Programming ABAP is SAP's fourth generation language. All of R/3's applications and even parts of its basic system are developed in ABAP. ABAP is used for customization and modification of SAP applications.In HR ABAP use of select statements significantly less than in other areas of ABAP development, Logical databases have limited applications in other modules but are very useful in HR. Also, you really need to understand the infotype time constraint concept, When you cannot get the information that you need out of the logical DB look at the function modules starting with HR* and RH*. These function modules will provide you with multiple ways of accessing data to save time. Worst-case scenario, use a select statement.

Sample ABAP Program to Upload table using new function GUI_UPLOAD

2007-10-18T22:17:00.000+05:30

*& Report ZUPLOAD *
*& *
*&---------------------------------------------------------------------*
*& This program uses the new function GUI_UPLOAD *
*& Input must be TAB delimited with a blank column at the start *
*& to allow for MANDT. *
*& To use this program for any Database Table replace ZTEST with *
*& new table name. *
*&---------------------------------------------------------------------*
*& AUTHOR: Sheila Titchener - abap at iconet-ltd.co.uk *
*& Date: February 2004 *
*&---------------------------------------------------------------------*

REPORT zupload MESSAGE-ID bd.

DATA: w_tab TYPE ZTEST.
DATA: i_tab TYPE STANDARD TABLE OF ZTEST.

DATA: v_subrc(2),
v_recswritten(6).

PARAMETERS: p_file(80)
DEFAULT 'C:\Temp\ZTEST.TXT'.

DATA: filename TYPE string,
w_ans(1) TYPE c.

filename = p_file.

CALL FUNCTION 'POPUP_TO_CONFIRM'
EXPORTING
titlebar = 'Upload Confirmation'
* DIAGNOSE_OBJECT = ' '
text_question = p_file
text_button_1 = 'Yes'(001)
* ICON_BUTTON_1 = ' '
text_button_2 = 'No'(002)
* ICON_BUTTON_2 = ' '
default_button = '2'
* DISPLAY_CANCEL_BUTTON = 'X'
* USERDEFINED_F1_HELP = ' '
* START_COLUMN = 25
* START_ROW = 6
* POPUP_TYPE =
* IV_QUICKINFO_BUTTON_1 = ' '
* IV_QUICKINFO_BUTTON_2 = ' '
IMPORTING
answer = w_ans
* TABLES
* PARAMETER =
* EXCEPTIONS
* TEXT_NOT_FOUND = 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.

CHECK w_ans = 1.

CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = filename
* FILETYPE = 'ASC
has_field_separator = 'X'
* HEADER_LENGTH = 0
* READ_BY_LINE = 'X'
* IMPORTING
* FILELENGTH =
* HEADER =
TABLES
data_tab = i_tab
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17.

* SYST FIELDS ARE NOT SET BY THIS FUNCTION SO DISPLAY THE ERROR CODE *

IF sy-subrc <> 0.
v_subrc = sy-subrc.
MESSAGE e899 WITH 'File Open Error' v_subrc.
ENDIF.

INSERT ZTEST FROM TABLE i_tab.

COMMIT WORK AND WAIT.

MESSAGE i899 WITH sy-dbcnt 'Records Written to ZTEST'.

Sample ABAP Program for Submitting report with selection table

2007-10-18T22:16:00.002+05:30

REPORT submit_with_selection_table.
TABLES QMSM.
* Work area for internal table IQMSM
DATA: BEGIN OF WQMSM,
QMNUM LIKE QMSM-QMNUM,
MNGRP LIKE QMSM-MNGRP,
MNCOD LIKE QMSM-MNCOD,
ZZSTAT LIKE QMSM-ZZSTAT,
END OF WQMSM.

* WORK Area for internal table iseltab.
DATA: WSELTAB LIKE RSPARAMS.
*----------------------------------------------------------------------*
* Internal tables
*----------------------------------------------------------------------*
* selection table to pass to RIQMEL30
DATA: ISELTAB LIKE TABLE OF WSELTAB.
* Table of notification numbers selected - will be passed to riqmel30
DATA: IQMSM LIKE TABLE OF WQMSM.
*----------------------------------------------------------------------*
START-OF-SELECTION.
*----------------------------------------------------------------------*
REFRESH IQMSM.
SELECT QMNUM MNGRP MNCOD ZZSTAT
FROM QMSM INTO CORRESPONDING FIELDS OF TABLE IQMSM
WHERE MNGRP = 'ACTION'
AND MNCOD = 'CALL'
and ( zzqmart = 'ZE' or zzqmart = 'ZI' )
AND ZZSTAT = ' '.

* create selection table entries for field QMART

WSELTAB-SELNAME = 'QMART'.
WSELTAB-KIND = 'S'.
WSELTAB-SIGN = 'I'.
WSELTAB-OPTION = 'EQ'.
WSELTAB-LOW = 'ZE'.
APPEND WSELTAB TO ISELTAB.
WSELTAB-LOW = 'ZI'.
APPEND WSELTAB TO ISELTAB.

* Create selection table entries for QMNUM

CLEAR WSELTAB.
WSELTAB-SELNAME = 'QMNUM'.
WSELTAB-KIND = 'S'.
WSELTAB-SIGN = 'I'.
WSELTAB-OPTION = 'EQ'.
LOOP AT IQMSM INTO WQMSM.
WSELTAB-LOW = WQMSM-QMNUM.
APPEND WSELTAB TO ISELTAB.
ENDLOOP
*
* SUBMIT program with parameters passed in table ISELTAB
* Other parameters passed explicitly

SUBMIT RIQMEL30 WITH SELECTION-TABLE ISELTAB
WITH MNGRP = 'ACTION'
WITH MNCOD = 'CALL'
WITH DATUV = '00000000'
WITH DATUB = '99991231'
WITH STAI1 = 'TSRL'.

Sample ABAP Program for Sending SAP Mail

2007-10-18T22:16:00.001+05:30

*&---------------------------------------------------------------------*
*& Form SEND_MAIL
*&---------------------------------------------------------------------*
* send email to current user *
*----------------------------------------------------------------------*
FORM SEND_MAIL.

* PARAMETERS FOR SO_NEW_DOCUMENT_SEND_API1
DATA: W_OBJECT_ID LIKE SOODK,
W_SONV_FLAG LIKE SONV-FLAG.
DATA: T_RECEIVERS LIKE SOMLRECI1 OCCURS 1 WITH HEADER LINE,
W_OBJECT_CONTENT LIKE SOLISTI1 OCCURS 1 WITH HEADER LINE,
W_DOC_DATA LIKE SODOCCHGI1 OCCURS 0 WITH HEADER LINE.
*
DATA: W_DATE(10).
CLEAR T_RECEIVERS.
T_RECEIVERS-RECEIVER = SY-UNAME.
T_RECEIVERS-REC_TYPE = 'B'.
T_RECEIVERS-EXPRESS = ' '.
APPEND T_RECEIVERS.

W_DOC_DATA-OBJ_DESCR = 'Change Expiry date'.

* Delivery NO
CONCATENATE 'Delivery No' M_VMVMA-VBELN INTO W_OBJECT_CONTENT
SEPARATED BY ' '.
APPEND W_OBJECT_CONTENT.
* material Batch
CONCATENATE 'Material' ZGREC-MATNR 'Batch' ZGREC-CHARG
INTO W_OBJECT_CONTENT SEPARATED BY ' '.
APPEND W_OBJECT_CONTENT.
* Expiry date
WRITE B_VFDAT TO W_DATE DD/MM/YYYY.
CONCATENATE 'Change expiry date to' W_DATE
INTO W_OBJECT_CONTENT SEPARATED BY ' '.
APPEND W_OBJECT_CONTENT.
*
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
EXPORTING
DOCUMENT_DATA = W_DOC_DATA
PUT_IN_OUTBOX = ' '
TABLES
OBJECT_CONTENT = W_OBJECT_CONTENT
RECEIVERS = T_RECEIVERS
EXCEPTIONS
TOO_MANY_RECEIVERS = 1
DOCUMENT_NOT_SENT = 2
DOCUMENT_TYPE_NOT_EXIST = 3
OPERATION_NO_AUTHORIZATION = 4
PARAMETER_ERROR = 5
X_ERROR = 6
ENQUEUE_ERROR = 7
OTHERS = 8.
ENDFORM. " SEND_MAIL

Sample ABAP Program for Search Layout sets for given String

2007-10-18T22:14:00.000+05:30

REPORT Ysearchl LINE-SIZE 132.

************************************************************************
*
* Program : Ysearchl
* Authors : Chris Harrop (chris.harrop@bigfoot.com)
* Date : March 1999
* Purpose : Searches all Y and Z layout sets for a given string
*
************************************************************************
*
* maintenance history
*
* date author purpose
*
************************************************************************

TABLES: STXL.

PARAMETERS:
STRING(128).

DATA: BEGIN OF TLINETAB OCCURS 0.
INCLUDE STRUCTURE TLINE.
DATA: END OF TLINETAB,
SUBRC LIKE SY-SUBRC.

SELECT TDNAME FROM STXL INTO (STXL-TDNAME)
WHERE TDOBJECT = 'FORM' AND ( TDNAME LIKE 'Y%' OR TDNAME LIKE 'Z%' )
AND TDID = 'TXT'.

PERFORM DISPLAY_STATUS_TEXT USING STXL-TDNAME.

REFRESH TLINETAB.
PERFORM GET_TEXT_TABLE
TABLES TLINETAB
USING 'FORM' 'TXT' STXL-TDNAME
CHANGING SUBRC.
LOOP AT TLINETAB.
IF TLINETAB-TDLINE CS STRING.
WRITE : / STXL-TDNAME, TLINETAB-TDLINE.
ENDIF.
ENDLOOP.
ENDSELECT.

* Display a message on the status bar
FORM DISPLAY_STATUS_TEXT USING VALUE(TEXT) TYPE C.
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
TEXT = TEXT.
ENDFORM.
*
* Get the long texts for the object
*
FORM GET_TEXT_TABLE TABLES TLINETAB
USING VALUE(TDOBJECT) LIKE THEAD-TDOBJECT
VALUE(ID) LIKE THEAD-TDID
VALUE(TDNAME) LIKE THEAD-TDNAME
CHANGING SUBRC LIKE SY-SUBRC.

DATA: BEGIN OF XTHEAD OCCURS 0.
INCLUDE STRUCTURE THEAD.
DATA: END OF XTHEAD.

DATA: EINTRAEGE LIKE SY-TFILL.

DATA XTDNAME LIKE THEAD-TDNAME.
REFRESH XTHEAD.
CLEAR XTDNAME.
XTDNAME = TDNAME.

CALL FUNCTION 'SELECT_TEXT'
EXPORTING
ID = ID
LANGUAGE = SY-LANGU
NAME = TDNAME
OBJECT = TDOBJECT
IMPORTING
ENTRIES = EINTRAEGE
TABLES
SELECTIONS = XTHEAD.

REFRESH TLINETAB.

CALL FUNCTION 'READ_TEXT'
EXPORTING
ID = ID
LANGUAGE = SY-LANGU
NAME = TDNAME
OBJECT = TDOBJECT
IMPORTING
HEADER = XTHEAD
TABLES
LINES = TLINETAB
EXCEPTIONS
ID = 01
LANGUAGE = 02
NAME = 03
NOT_FOUND = 04
OBJECT = 05
REFERENCE_CHECK = 06.
SUBRC = SY-SUBRC.
ENDFORM. " FILL_ITEM_TEXT

Sample ABAP Program for Sapscript PerForm Module

2007-10-18T22:13:00.000+05:30

REPORT YLSD999A.
DATA W_LENGTH TYPE I.
* GENERAL PURPOSE SUBROUTINES FOR CALLING FROM SAPSCRIPTS
*-----------------------------------------------------------------------
*----------------------------------------------------------------------
FORM DISPLAY_POUND TABLES IN_TAB STRUCTURE ITCSY
OUT_TAB STRUCTURE ITCSY.
DATA: COUNT TYPE P VALUE 16.
DATA: W_VALUE(17) TYPE C. "defined as 7 chars to remove pence
DATA: W_CHAR TYPE C.
DATA: W_DUMMY TYPE C.
DATA: W_CURR(3) TYPE C.
* Get first parameter in input table.
READ TABLE IN_TAB INDEX 1.
WRITE IN_TAB-VALUE TO W_VALUE .
* get second parameter in input table
READ TABLE IN_TAB INDEX 2.
MOVE IN_TAB-VALUE TO W_CURR.
IF W_CURR = 'GBP'.
W_CURR = '£'.
ENDIF.
W_LENGTH = STRLEN( W_CURR ).
* look for first space starting at right.
WHILE COUNT > -1.
W_CHAR = W_VALUE+COUNT(1).
* W_CHAR = IN_TAB-VALUE+COUNT(1).
IF W_CHAR = ' '.
COUNT = COUNT - W_LENGTH + 1.
W_VALUE+COUNT(W_LENGTH) = W_CURR.
COUNT = -1.
ELSE.
* W_VALUE+COUNT(1) = W_CHAR.
COUNT = COUNT - 1.
ENDIF.
ENDWHILE.
* read only parameter in output table
READ TABLE OUT_TAB INDEX 1.
OUT_TAB-VALUE = W_VALUE.
MODIFY OUT_TAB INDEX SY-TABIX.
ENDFORM.

Sample ABAP Program for Create IDOC

2007-10-18T22:11:00.000+05:30

FUNCTION Y_ISSUE_ROCO_IDOC.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(I_MODE) LIKE Z1ROCO-ZMODE
*" VALUE(I_ROUTE) LIKE Z1ROCO-ROUTE
*" VALUE(I_CUT_OFF) LIKE Z1ROCO-CUT_OFF OPTIONAL
*" VALUE(I_BEZEI) LIKE Z1ROCO-BEZEI OPTIONAL
*" VALUE(I_TROUTE_MON) LIKE Z1ROCO-TROUTE_MON OPTIONAL
*" VALUE(I_TROUTE_TUE) LIKE Z1ROCO-TROUTE_TUE OPTIONAL
*" VALUE(I_TROUTE_WED) LIKE Z1ROCO-TROUTE_WED OPTIONAL
*" VALUE(I_TROUTE_THU) LIKE Z1ROCO-TROUTE_THU OPTIONAL
*" VALUE(I_TROUTE_FRI) LIKE Z1ROCO-TROUTE_FRI OPTIONAL
*" VALUE(I_TROUTE_SAT) LIKE Z1ROCO-TROUTE_SAT OPTIONAL
*" VALUE(I_TROUTE_SUN) LIKE Z1ROCO-TROUTE_SUN OPTIONAL
*" VALUE(I_PGI_IND) LIKE Z1ROCO-PGI_IND OPTIONAL
*"----------------------------------------------------------------------

DATA: W_EDIDC LIKE EDIDC OCCURS 5 WITH HEADER LINE,
W_Z1ROCO LIKE EDIDC,
L_EDIDC LIKE EDIDC,
L_SEND_FLAG,
W_SDATA LIKE EDIDD-SDATA.
DATA: T_BDI_MODEL LIKE BDI_MODEL OCCURS 0 WITH HEADER LINE.
DATA: T_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
DATA: T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.

*- Call function module to determine if message is to be distributed

CALL FUNCTION 'ALE_MODEL_DETERMINE_IF_TO_SEND'
EXPORTING
MESSAGE_TYPE = 'ZZROCO'
IMPORTING
IDOC_MUST_BE_SENT = L_SEND_FLAG
EXCEPTIONS
OWN_SYSTEM_NOT_DEFINED = 1
OTHERS = 2.

*- Determine recipient systems

CALL FUNCTION 'ALE_MODEL_INFO_GET'
EXPORTING
MESSAGE_TYPE = 'ZZROCO'
* RECEIVING_SYSTEM = ' '
* SENDING_SYSTEM = ' '
* VALIDDATE = SY-DATUM
TABLES
MODEL_DATA = T_BDI_MODEL
EXCEPTIONS
NO_MODEL_INFO_FOUND = 1
OWN_SYSTEM_NOT_DEFINED = 2
OTHERS = 3.

* 3.2
*Call function 'L_IDOC_HEADER_CREATE'
* exporting
* i_mestyp = 'ZZROCO'
* i_mescod = ' '
* i_idoctp = 'ZSDROCO'
* i_rcvprn = 'Z_WMS'
* exceptions
* others = 1.
* 3.3
MOVE I_MODE TO Z1ROCO-ZMODE.
MOVE I_ROUTE TO Z1ROCO-ROUTE.
MOVE I_CUT_OFF TO Z1ROCO-CUT_OFF.
MOVE I_BEZEI TO Z1ROCO-BEZEI.
MOVE I_TROUTE_MON TO Z1ROCO-TROUTE_MON.
MOVE I_TROUTE_TUE TO Z1ROCO-TROUTE_TUE.
MOVE I_TROUTE_WED TO Z1ROCO-TROUTE_WED.
MOVE I_TROUTE_THU TO Z1ROCO-TROUTE_THU.
MOVE I_TROUTE_FRI TO Z1ROCO-TROUTE_FRI.
MOVE I_TROUTE_SAT TO Z1ROCO-TROUTE_SAT.
MOVE I_TROUTE_SUN TO Z1ROCO-TROUTE_SUN.
MOVE I_PGI_IND TO Z1ROCO-PGI_IND.

MOVE Z1ROCO TO: W_SDATA, T_EDIDD-SDATA.
MOVE 'Z1ROCO' TO T_EDIDD-SEGNAM.
APPEND T_EDIDD.

*call function 'L_IDOC_SEGMENT_CREATE'
* exporting
* i_segnam = 'Z1ROCO'
* i_sdata = w_sdata
* exceptions
* others = 1.

*call function 'L_IDOC_SEND'
* tables
* t_comm_idoc = w_edidc
* exceptions
* error_distribute_idoc = 1
* others = 2.

READ TABLE T_BDI_MODEL INDEX 1. " maximum 1 recipient
MOVE 'ZZROCO' TO L_EDIDC-MESTYP.
MOVE 'ZSDROCO' TO L_EDIDC-IDOCTP.
MOVE 'LS' TO L_EDIDC-RCVPRT.
MOVE T_BDI_MODEL-RCVSYSTEM TO L_EDIDC-RCVPRN.

*- Distribute the iDoc

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK
EXPORTING
MASTER_IDOC_CONTROL = L_EDIDC
TABLES
COMMUNICATION_IDOC_CONTROL = W_EDIDC
MASTER_IDOC_DATA = T_EDIDD
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 01
ERROR_WRITING_IDOC_STATUS = 02
ERROR_IN_IDOC_DATA = 03
SENDING_LOGICAL_SYSTEM_UNKNOWN = 04.

COMMIT WORK.
*E_RESPONSE = SY-SUBRC.
ENDFUNCTION.

Sample ABAP Program for Output file to application server then send mail with Download details

2007-10-18T22:10:00.000+05:30

*&---------------------------------------------------------------------*
*& Form download_to_application
*& download to application server, attach to mail and send to user
*&---------------------------------------------------------------------*
FORM download_to_application.

data: l_title type SO_OBJ_DES.

l_title = sy-repid.

CALL FUNCTION 'ZSEND_REPORT_MAIL'
EXPORTING
i_title = l_title
tables
it_text_data = it_download
EXCEPTIONS
INVALID_USER = 1
MAIL_SEND_ERROR = 2
OPEN_FILE = 3
FILE_GET_NAME = 4
OTHERS = 5
.
IF sy-subrc <> 0.
MESSAGE e368(00) with 'ZSEND_REPORT_MAIL fail -'
sy-subrc.
ENDIF.

ENDFORM. " download_to_application
===============================================================================

FUNCTION Zsend_report_mail.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" REFERENCE(I_UNAME) TYPE SYUNAME DEFAULT SY-UNAME
*" REFERENCE(I_TITLE) TYPE SO_OBJ_DES
*" TABLES
*" IT_TEXT_DATA
*" EXCEPTIONS
*" INVALID_USER
*" MAIL_SEND_ERROR
*" OPEN_FILE
*" FILE_GET_NAME
*"----------------------------------------------------------------------

* This function is used to store a file (report result) on the file
* system of the application server and to send an "active" SAP mail
* to the user.
* The "active" SAP mail calls function ZMAIL_DOWNLOAD to
* download the file to the presentation server.

DATA: ls_document_data LIKE sodocchgi1.
DATA: lt_object_para LIKE soparai1 OCCURS 5 WITH HEADER LINE.
DATA: lt_object_parb LIKE soparbi1 OCCURS 0 WITH HEADER LINE.
DATA: lt_object_cont LIKE solisti1 OCCURS 0 WITH HEADER LINE.
DATA: lt_reclist LIKE somlreci1 OCCURS 5 WITH HEADER LINE.

DATA: l_filename(200) TYPE c.

CHECK NOT it_text_data[] IS INITIAL.

* terminate if name not suitable.
IF i_uname IS INITIAL OR
i_uname = 'WF-BATCH' OR
i_uname = 'DDIC' OR
i_uname = 'SAP*'.
RAISE invalid_user.
ENDIF.

* get physical file from logical filename( optional)

CALL FUNCTION 'FILE_GET_NAME'
EXPORTING
logical_filename = 'MAILFILE'
parameter_1 = sy-uname
parameter_2 = sy-datum
parameter_3 = sy-uzeit
* USE_PRESENTATION_SERVER = ' '
* WITH_FILE_EXTENSION = ' '
* USE_BUFFER = ' '
* ELEMINATE_BLANKS = 'X'
IMPORTING
* EMERGENCY_FLAG =
* FILE_FORMAT =
file_name = l_filename
EXCEPTIONS
file_not_found = 1
OTHERS = 2.
IF sy-subrc NE 0.
RAISE file_get_name.
ENDIF.

* save file
OPEN DATASET l_filename FOR OUTPUT IN TEXT MODE.
IF sy-subrc NE 0.
RAISE open_file.
ENDIF.
LOOP AT it_text_data. " into l_text_data.
TRANSFER it_text_data TO l_filename.
ENDLOOP.
CLOSE DATASET l_filename.

* SAP mail header (execute function)
CLEAR: ls_document_data.
ls_document_data-obj_descr = i_title.
ls_document_data-proc_type = 'F'. " function call
ls_document_data-proc_name = 'ZMAIL_DOWNLOAD'.
ls_document_data-no_change = 'X'.
* SAP mail receiver
REFRESH lt_reclist.
CLEAR lt_reclist.
lt_reclist-receiver = i_uname.
lt_reclist-rec_type = 'B'.
* gt_reclist-express = 'X'.
APPEND lt_reclist.
* message text
REFRESH lt_object_cont.
CLEAR lt_object_cont.
lt_object_cont-line =
'The result of the following report has been saved.'.
APPEND lt_object_cont.
* report name
lt_object_cont-line = 'Report:'.
lt_object_cont-line+15 = sy-cprog.
CONDENSE lt_object_cont-line.
APPEND lt_object_cont.
* date & time
lt_object_cont-line = 'Date/Time:'.
WRITE sy-datum TO lt_object_cont-line+15.
WRITE sy-uzeit TO lt_object_cont-line+27.
CONDENSE lt_object_cont-line.
APPEND lt_object_cont.
*
lt_object_cont-line =
'Please execute (Ctrl-F6) this mail to download the result.'.
APPEND lt_object_cont.

* mail parameters
REFRESH lt_object_parb.
CLEAR lt_object_parb.
lt_object_parb-name = 'FUNCTION'. " mail identifier
lt_object_parb-value = 'FILE_DOWNLOAD'. " mail identifier
APPEND lt_object_parb.
lt_object_parb-name = 'FILENAME'.
lt_object_parb-value = l_filename.
APPEND lt_object_parb.

*call SAPOffice API
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
EXPORTING
document_data = ls_document_data
TABLES
object_content = lt_object_cont
object_para = lt_object_para
object_parb = lt_object_parb
receivers = lt_reclist
EXCEPTIONS
too_many_receivers = 1
document_not_sent = 2
document_type_not_exist = 3
operation_no_authorization = 4
parameter_error = 5
x_error = 6
enqueue_error = 7
OTHERS = 8.
IF sy-subrc NE 0.
RAISE mail_send_error.
ENDIF.

ENDFUNCTION.
===========================================================================
FUNCTION zmail_download.
*"----------------------------------------------------------------------
*"*"Local interface:
*" TABLES
*" MSGDIAL STRUCTURE SOPARBI1
*"----------------------------------------------------------------------
* This function is called in a SAP mail to download a file from the
* application server file system.
* Function ZSEND_REPORT_MAIL is used to save report result
* on application server file system and to send SAP mail to user.
* Based on UK COM solution by Damian Norton.

DATA: ls_msgdial TYPE soparbi1.
DATA: l_filename TYPE filep.
* DATA: l_filename_local TYPE filep.
DATA: l_operation(30) TYPE c.
DATA: BEGIN OF lt_text_data OCCURS 10,
line(2000),
END OF lt_text_data.

* read parameters
LOOP AT msgdial INTO ls_msgdial.
CASE ls_msgdial-name.
WHEN 'FUNCTION'.
l_operation = ls_msgdial-value.
WHEN 'FILENAME'.
l_filename = ls_msgdial-value.
WHEN OTHERS.
MESSAGE e368(00) WITH 'Invalid parameter' ls_msgdial-name.
ENDCASE. " ls_msgdial-name
ENDLOOP. " msgdial

IF l_operation = 'FILE_DOWNLOAD'.
* check, whether file exists on presentation server
REFRESH lt_text_data.
OPEN DATASET l_filename FOR INPUT IN TEXT MODE.
IF sy-subrc = 0.
DO.
READ DATASET l_filename INTO lt_text_data-line.
IF sy-subrc = 0.
APPEND lt_text_data.
ELSE.
EXIT.
ENDIF.
ENDDO.
CLOSE DATASET l_filename.
* request filename on presentation server - or GUI_DOWNLOAD??
CALL FUNCTION 'DOWNLOAD'
TABLES
data_tab = lt_text_data
EXCEPTIONS
invalid_filesize = 1
invalid_table_width = 2
invalid_type = 3
no_batch = 4
unknown_error = 5
gui_refuse_filetransfer = 6
customer_error = 7
OTHERS = 8.
IF sy-subrc NE 0.
MESSAGE e688(00) WITH 'File download error' sy-subrc.
ENDIF.
ELSE.
MESSAGE e398(00) WITH 'File open error' l_filename.
ENDIF. " sy-subrc = 0 (OPEN DATASET)
ENDIF. " l_operation = 'FILE_DOWNLOAD'

ENDFUNCTION.

Sample ABAP Program for Module Pool Skeleton

2007-10-18T22:09:00.000+05:30

PROGRAM YMPSKEL MESSAGE-ID YL.
*-----------------------------------------------------------------------
* DESCRIPTION
* written by !
*-----------------------------------------------------------------------
* TABLES:

DATA: OK_CODE(4), " ok code - screen 1
OK_CODE2(4).
DATA C LIKE SY-INDEX. " Index for screen loop
*&---------------------------------------------------------------------*
*& Module USER_COMMAND_0100 INPUT
*&---------------------------------------------------------------------*
* process after input for screen 0100 *
*----------------------------------------------------------------------*
MODULE USER_COMMAND_0100 INPUT.

CASE OK_CODE.
WHEN 'SAVE'.
*
WHEN 'DISP'.
*
WHEN 'LIST'.
C = 0. "reset loop control
*
WHEN OTHERS.
*
ENDCASE.
CLEAR OK_CODE.
ENDMODULE. " USER_COMMAND_0100 INPUT
*&---------------------------------------------------------------------*
*& Module STATUS_0100 OUTPUT
*&---------------------------------------------------------------------*
* process before output for screen 0100 *
*----------------------------------------------------------------------*
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'AMEND'. " set gui status
SET TITLEBAR '100'. " set title
ENDMODULE. " STATUS_0100 OUTPUT
*&---------------------------------------------------------------------*
*& Form SAVE data
*&---------------------------------------------------------------------*
* Save screen details
*&---------------------------------------------------------------------*
FORM SAVE.
*
CLEAR OK_CODE.
ENDFORM.
*&---------------------------------------------------------------------*
*& Form DISPLAY
*&---------------------------------------------------------------------*
*----------------------------------------------------------------------*
FORM DISPLAY.
*
*

ENDFORM.
*&---------------------------------------------------------------------*
*& Module EXIT_COMMAND INPUT
*&---------------------------------------------------------------------*
* exit commands are processed before validation *
* defined by E against function in menu painter(function list)
*----------------------------------------------------------------------*
MODULE EXIT_COMMAND INPUT.

CASE OK_CODE.
WHEN 'EXIT'. CLEAR OK_CODE. SET SCREEN 0. LEAVE SCREEN.
WHEN 'CANC'. CLEAR OK_CODE. SET SCREEN 0. LEAVE SCREEN.
WHEN 'BACK'. CLEAR OK_CODE. SET SCREEN 0. LEAVE SCREEN.
ENDCASE.
ENDMODULE. " EXIT_COMMAND INPUT
*&---------------------------------------------------------------------*
*& Form list
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
FORM LIST.

CLEAR OK_CODE. SET SCREEN 200. LEAVE SCREEN.

ENDFORM. " LIST
*&---------------------------------------------------------------------*
*& Module EXIT_COMMAND_200 INPUT
*&---------------------------------------------------------------------*
* exit command processing for screen 200 *
* defined by E against function in menu painter(function list)
*----------------------------------------------------------------------*
MODULE EXIT_COMMAND_200 INPUT.

CASE OK_CODE2.
WHEN 'EXIT'. CLEAR OK_CODE2. SET SCREEN 0. LEAVE SCREEN.
WHEN 'CANC'. CLEAR OK_CODE2. SET SCREEN 0. LEAVE SCREEN.
WHEN 'BACK'. CLEAR OK_CODE2. SET SCREEN 100. LEAVE SCREEN.
ENDCASE.
ENDMODULE. " EXIT_COMMAND_200 INPUT
*&---------------------------------------------------------------------*
*& Module STATUS_0200 OUTPUT
*&---------------------------------------------------------------------*
* process before output for screen 200 *
*----------------------------------------------------------------------*
MODULE STATUS_0200 OUTPUT.
SET PF-STATUS 'POPUP'.
* SET TITLEBAR 'xxx'.

ENDMODULE. " STATUS_0200 OUTPUT

Sample ABAP Program for Module Pool containing screen loop processing

2007-10-18T22:08:00.000+05:30

PROGRAM YLSDM004.
TABLES: LTAP, "Transfer order item
LIPS, "SD doc delivery: item data
MAKT, "material description
VEPO, "SD Document: Shipping Unit Item
VEKP, "SD Document: Shipping Unit Header
USR01, "USER defaults
ZPACKMAT, "Packing material table
T646M, "hazard class descriptions
ZCASHAZLAB. "SCasehazardous label table
DATA: OK_CODE(4).

DATA: C LIKE SY-INDEX, " cursor for case labels
* C1 LIKE SY-INDEX, " cursor for storage class(haz)
C2 LIKE SY-INDEX. " cursor for text
* screen fields for selection screen 0100
DATA: S_ZZTRACKING LIKE LTAP-ZZTRACKING,
* S_VENUM LIKE VEKP-VENUM,
S_EXIDV LIKE VEKP-EXIDV.
*
DATA W_MAKTX LIKE MAKT-MAKTX.
* packaging materials
DATA: S_PACKMAT1 LIKE VEKP-ZZPACKMAT1,
S_BEZEI1 LIKE ZPACKMAT-BEZEI,
S_PACKMAT2 LIKE VEKP-ZZPACKMAT1,
S_BEZEI2 LIKE ZPACKMAT-BEZEI.
* Case label codes and descriptions
DATA: BEGIN OF LABELS OCCURS 5 ,
CODE LIKE VEKP-ZZCASELAB1,
TEXT LIKE ZCASHAZLAB-ZZCLB_TEXT,
END OF LABELS.
* hazard class and descriptions
DATA: BEGIN OF HAZ OCCURS 3,
CODE LIKE VEKP-ZZLAGKL,
TEXT LIKE T646M-LAGKT,
END OF HAZ.
DATA: W_HAZ_TEXT1 LIKE T646M-LAGKT,
W_HAZ_TEXT2 LIKE T646M-LAGKT,
W_HAZ_TEXT3 LIKE T646M-LAGKT.

DATA T_LINES LIKE TLINE OCCURS 1 WITH HEADER LINE.
DATA T_HEADER LIKE THEAD.
*DATA W_INDEX LIKE SY-INDEX.
* start line of the last screen of text lines
DATA W_MAX LIKE SY-INDEX.
DATA W_TIN_MAKTX LIKE MAKT-MAKTX.
*&---------------------------------------------------------------------*
*& Module STATUS_0100 OUTPUT
*&---------------------------------------------------------------------*
* selection screen *
*----------------------------------------------------------------------*
MODULE STATUS_0100 OUTPUT.
CASE OK_CODE.
WHEN 'EXIT'. LEAVE TO SCREEN 0.
WHEN 'CANC'.

SELECT SINGLE * FROM USR01
WHERE BNAME = SY-UNAME .

LEAVE TO TRANSACTION USR01-STCOD.
ENDCASE.
SET PF-STATUS 'SELECT'.
CLEAR: VEKP,
LTAP.
SET TITLEBAR 'SEL'.

ENDMODULE. " STATUS_0100 OUTPUT
*&---------------------------------------------------------------------*
*& Module USER_COMMAND_0100 INPUT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
MODULE USER_COMMAND_0100 INPUT.
C2 = 0.
* Mandatory Fields
CHECK OK_CODE = 'EXEC'.
*
CALL SCREEN '0110'.
ENDMODULE. " USER_COMMAND_0100 INPUT
*&---------------------------------------------------------------------*
*& Module VAL_ZZTRACKING INPUT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
MODULE VAL_ZZTRACKING INPUT.
* MUST enter at least one value
* IF S_ZZTRACKING = ' ' AND S_VENUM = ' ' AND S_EXIDV = ' '.
IF S_ZZTRACKING = ' ' AND S_EXIDV = ' '.
MESSAGE E001(YL).
ENDIF.

* if tracking label entered other fields must be initial
IF S_ZZTRACKING NE ' '
* AND ( S_VENUM NE ' ' OR S_EXIDV NE ' ' ).
AND S_EXIDV NE ' ' .
MESSAGE E083(YL).
ENDIF.
* if tracking label number entered get record from LTAP

IF S_ZZTRACKING NE ' '.

SELECT SINGLE * FROM LTAP
WHERE ZZTRACKING = S_ZZTRACKING.
IF SY-SUBRC NE 0.
MESSAGE E022(YL) WITH S_ZZTRACKING.
ELSE.
*--------------------------------------------------------------------
*
* IF LTAP-VENUM NE ' '.
*
* SELECT SINGLE * FROM VEKP
* WHERE VENUM = LTAP-VENUM .
*
IF LTAP-EXIDV NE ' '.

SELECT SINGLE * FROM VEKP
WHERE EXIDV = LTAP-EXIDV .
*---------------------------------------------------------------------
IF SY-SUBRC NE 0.
MESSAGE E022(YL) WITH LTAP-EXIDV.
ENDIF.
ENDIF.
ENDIF.
ENDIF.
ENDMODULE. " VAL_ZZTRACKING INPUT
*&---------------------------------------------------------------------*
*& Module VAL_VENUM INPUT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
*MODULE VAL_VENUM INPUT.
* SET CURSOR FIELD S_VENUM.
* IF S_VENUM NE ' '
* AND S_EXIDV NE ' '.
* MESSAGE E083(YL).
* ENDIF.
* IF S_VENUM NE ' '.
*
* SELECT SINGLE * FROM VEKP
* WHERE VENUM = S_VENUM.
* IF SY-SUBRC NE 0.
* MESSAGE E022(YL) WITH S_VENUM.
* ENDIF.
* ENDIF.
*ENDMODULE. " VAL_VENUM INPUT
*&---------------------------------------------------------------------*
*& Module EXIT_COMMAND INPUT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
MODULE EXIT_COMMAND INPUT.
CASE OK_CODE.
WHEN 'EXIT'. LEAVE TO SCREEN 0.
WHEN 'CANC'.
SELECT SINGLE * FROM USR01
WHERE BNAME = SY-UNAME .

LEAVE TO TRANSACTION USR01-STCOD.
WHEN 'BACK'. LEAVE TO SCREEN 0.
ENDCASE.

ENDMODULE. " EXIT_COMMAND INPUT
*&---------------------------------------------------------------------*
*& Module VAL_EXIDV INPUT
*&---------------------------------------------------------------------*
* validate external shipping unit number exits on VEKP *
*----------------------------------------------------------------------*
MODULE VAL_EXIDV INPUT.
IF S_EXIDV NE ' '.
CONCATENATE '00' S_EXIDV INTO VEKP-EXIDV.
SELECT SINGLE * FROM VEKP
WHERE EXIDV = VEKP-EXIDV.
IF SY-SUBRC NE 0.
MESSAGE E022(YL) WITH S_EXIDV.
ENDIF.
ENDIF.
ENDMODULE. " VAL_EXIDV INPUT
*&---------------------------------------------------------------------*
*& Module STATUS_0110 OUTPUT
*&---------------------------------------------------------------------*
* Display screen *
*----------------------------------------------------------------------*
MODULE STATUS_0110 OUTPUT.
IF OK_CODE = 'P+ ' OR OK_CODE = 'P- ' OR OK_CODE = 'P++ '
OR OK_CODE = 'P-- '.
EXIT.
ENDIF.
IF VEKP-VENUM = ' '.
* processing mode b
PERFORM DISP_DELIVERY.
ELSE.
* processing mode a
PERFORM DISP_SHIP_UNIT.
ENDIF.
* common processing
* get mara details
CLEAR MAKT.
*SELECT SINGLE * FROM MARA
* WHERE MATNR = LIPS-MATNR .
*IF SY-SUBRC = 0.
* material description
SELECT SINGLE * FROM MAKT
WHERE MATNR = LIPS-MATNR
AND SPRAS = SY-LANGU .
DATA W_TDNAME LIKE THEAD-TDNAME.
W_TDNAME = LIPS-VBELN.
W_TDNAME+10 = LIPS-POSNR.
CLEAR T_LINES.
REFRESH T_LINES.
CALL FUNCTION 'READ_TEXT'
EXPORTING
ID = 'Z034'
LANGUAGE = SY-LANGU
NAME = W_TDNAME
OBJECT = 'VBBP'
IMPORTING
HEADER = T_HEADER
TABLES
LINES = T_LINES
EXCEPTIONS
ID = 1
LANGUAGE = 2
NAME = 3
NOT_FOUND = 4
OBJECT = 5
REFERENCE_CHECK = 6
WRONG_ACCESS_TO_ARCHIVE = 7
OTHERS = 8.
LOOP AT T_LINES.
EXIT.
ENDLOOP.
IF SY-TFILL > 1.
* W_MAX = SY-TFILL - 5.
W_MAX = SY-TFILL - 1.
ELSE.
W_MAX = 1.
ENDIF.
*
IF W_MAX > 3 .
SET PF-STATUS 'DELIVERY'.
ELSE.
SET PF-STATUS 'ONE'.
ENDIF.
ENDMODULE. " STATUS_0110 OUTPUT

*&---------------------------------------------------------------------*
*& Form DISP_DELIVERY
*&---------------------------------------------------------------------*
* Diplay delivery title - Read delivery item from LIPS
* processing mode B
*----------------------------------------------------------------------*
FORM DISP_DELIVERY.
* SET PF-STATUS 'DELIVERY'.
SET TITLEBAR 'DEL'.
CLEAR LIPS.
SELECT SINGLE * FROM LIPS
WHERE VBELN = LTAP-VBELN_VL
AND POSNR = LTAP-POSNR_VL .

ENDFORM. " DISP_DELIVERY

*&---------------------------------------------------------------------*
*& Form DISP_SHIP_UNIT
*&---------------------------------------------------------------------*
* Display Shipping unit title and read shipping details
*----------------------------------------------------------------------*
* Processing MODE a
*----------------------------------------------------------------------*
FORM DISP_SHIP_UNIT.

* SET PF-STATUS 'DELIVERY'.
SET TITLEBAR 'SHP'.
* vekp already read
* read vepo
* only one line per case
CLEAR VEPO.
CLEAR LIPS.
CLEAR W_MAKTX.
CLEAR W_TIN_MAKTX.
CLEAR ZPACKMAT.
CLEAR S_PACKMAT1.
CLEAR S_PACKMAT2.
CLEAR S_BEZEI1.
CLEAR S_BEZEI2.
CLEAR LABELS.
REFRESH LABELS.
SELECT SINGLE * FROM VEPO
WHERE VENUM = VEKP-VENUM.
IF SY-SUBRC = 0.
SELECT SINGLE * FROM LIPS
WHERE VBELN = VEPO-VBELN
AND POSNR = VEPO-POSNR .
ENDIF.
* packaging material
IF VEKP-ZZPACKMAT1 NE ' '.
SELECT SINGLE * FROM ZPACKMAT
WHERE ZZPACKMAT = VEKP-ZZPACKMAT1.
IF SY-SUBRC = 0.
S_PACKMAT1 = VEKP-ZZPACKMAT1.
S_BEZEI1 = ZPACKMAT-BEZEI.
ENDIF.
ENDIF.

IF VEKP-ZZPACKMAT2 NE ' '.
SELECT SINGLE * FROM ZPACKMAT
WHERE ZZPACKMAT = VEKP-ZZPACKMAT2.
IF SY-SUBRC = 0.
S_PACKMAT2 = VEKP-ZZPACKMAT2.
S_BEZEI2 = ZPACKMAT-BEZEI.
ENDIF.
ENDIF.
* hazard class x 3
CLEAR: W_HAZ_TEXT1, W_HAZ_TEXT2, W_HAZ_TEXT3.
* REFRESH HAZ.
IF VEKP-ZZLAGKL NE ' '.
* HAZ-CODE = VEKP-ZZLAGKL.

SELECT SINGLE * FROM T646M
WHERE SPRAS = SY-LANGU
AND LAGKL = VEKP-ZZLAGKL .
IF SY-SUBRC = 0.
W_HAZ_TEXT1 = T646M-LAGKT.
ENDIF.
* APPEND HAZ.
ENDIF.
IF VEKP-ZZLAGKL2 NE ' '.
* HAZ-CODE = VEKP-ZZLAGKL2.

SELECT SINGLE * FROM T646M
WHERE SPRAS = SY-LANGU
AND LAGKL = VEKP-ZZLAGKL2 .
IF SY-SUBRC = 0.
W_HAZ_TEXT2 = T646M-LAGKT.
ENDIF.
* APPEND HAZ.
ENDIF.
IF VEKP-ZZLAGKL3 NE ' '.
* CLEAR HAZ.
* HAZ-CODE = VEKP-ZZLAGKL3.

SELECT SINGLE * FROM T646M
WHERE SPRAS = SY-LANGU
AND LAGKL = VEKP-ZZLAGKL3 .
IF SY-SUBRC = 0.
W_HAZ_TEXT3 = T646M-LAGKT.
ENDIF.
* APPEND HAZ.
ENDIF.
* LOOP AT HAZ.
* EXIT.
* ENDLOOP.

* case label details
IF VEKP-ZZCASELAB1 NE ' '.
LABELS-CODE = VEKP-ZZCASELAB1.
APPEND LABELS.
ENDIF.
IF VEKP-ZZCASELAB2 NE ' '.
LABELS-CODE = VEKP-ZZCASELAB2.
APPEND LABELS.
ENDIF.
IF VEKP-ZZCASELAB3 NE ' '.
LABELS-CODE = VEKP-ZZCASELAB3.
APPEND LABELS.
ENDIF.
IF VEKP-ZZCASELAB4 NE ' '.
LABELS-CODE = VEKP-ZZCASELAB4.
APPEND LABELS.
ENDIF.
IF VEKP-ZZCASELAB5 NE ' '.
LABELS-CODE = VEKP-ZZCASELAB5.
APPEND LABELS.
ENDIF.

LOOP AT LABELS.

SELECT SINGLE * FROM ZCASHAZLAB
WHERE ZZCASELAB = LABELS-CODE .
LABELS-TEXT = ZCASHAZLAB-ZZCLB_TEXT.
MODIFY LABELS.
ENDLOOP.
* tin material description
IF VEPO-ZZTINNR NE ' '.
SELECT SINGLE * FROM MAKT
WHERE MATNR = VEPO-ZZTINNR
AND SPRAS = SY-LANGU .

IF SY-SUBRC = 0.
W_TIN_MAKTX = MAKT-MAKTX.
ENDIF.
ENDIF.

* case material description
IF VEKP-VHILM NE ' '.
SELECT SINGLE * FROM MAKT
WHERE MATNR = VEKP-VHILM
AND SPRAS = SY-LANGU .

IF SY-SUBRC = 0.
W_MAKTX = MAKT-MAKTX.
ENDIF.
ENDIF.

ENDFORM. " DISP_SHIP_UNIT
*&---------------------------------------------------------------------*
*& Module USER_COMMAND_0110 INPUT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
MODULE USER_COMMAND_0110 INPUT.
* position text line cursor
CASE OK_CODE.
WHEN 'P+ '.
C2 = C2 + 3.
IF C2 > W_MAX.
C2 = W_MAX.
ENDIF.
WHEN 'P- '.
C2 = C2 - 3.
IF C2 < 1.
C2 = 1.
ENDIF.
WHEN 'P++ '.
C2 = W_MAX.
WHEN 'P-- '.
C2 = 1.
WHEN 'VL02'.
SET PARAMETER ID 'VL ' FIELD LIPS-VBELN.
CALL TRANSACTION 'VL02'.

ENDCASE.
ENDMODULE. " USER_COMMAND_0110 INPUT

Sample ABAP Program for MB1B Call Transaction

2007-10-18T22:06:00.000+05:30

REPORT YMBIE096 LINE-SIZE 80.

*----------------------------------------------------------------------*
* Program: YMBIE096
* Author: Sheila Titchener
* Date: Mar 1999
* Purpose: To move stock to new plant
*----------------------------------------------------------------------*
TABLES: MCHB.

* internal table
DATA: BEGIN OF I_MCHB OCCURS 0,
MATNR LIKE MCHB-MATNR,
LGORT LIKE MCHB-LGORT,
CHARG LIKE MCHB-CHARG,
J_2CTRNR LIKE MCHB-J_2CTRNR,
J_2CELNG LIKE MCHB-J_2CELNG,
CLABS LIKE MCHB-CLABS,
END OF I_MCHB.

*-----------------------new code smt nov 98-----------------------------
* batch input tables
DATA BEGIN OF BDCDATA OCCURS 100.
INCLUDE STRUCTURE BDCDATA.
DATA END OF BDCDATA.

DATA BEGIN OF MESSTAB OCCURS 10.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA END OF MESSTAB.
*

SELECT-OPTIONS S_MATNR FOR MCHB-MATNR.
PARAMETERS: P_DISP AS CHECKBOX.
DATA W_MODE.
DATA W_MESSAGE LIKE MESSAGE.
*----------------------------------------------------------------------*
START-OF-SELECTION.
*----------------------------------------------------------------------*

SELECT MATNR LGORT J_2CELNG CHARG CLABS J_2CTRNR FROM MCHB
INTO CORRESPONDING FIELDS OF TABLE I_MCHB
WHERE MATNR IN S_MATNR
AND WERKS = 'BT'.

*----------------------------------------------------------------------*
END-OF-SELECTION.
*----------------------------------------------------------------------*

LOOP AT I_MCHB.
CHECK I_MCHB-J_2CELNG NE 0.
CHECK I_MCHB-J_2CELNG = I_MCHB-CLABS.
PERFORM MOVE_STOCK.
ENDLOOP.

*&---------------------------------------------------------------------*
*& Form MOVE_STOCK
*&---------------------------------------------------------------------*
* Call transaction MB1B to transfer stock
*----------------------------------------------------------------------*
FORM MOVE_STOCK.
DATA: W_QTY(10).
WRITE I_MCHB-J_2CELNG TO W_QTY DECIMALS 0.

REFRESH: BDCDATA, MESSTAB.

PERFORM DYNPRO USING:
'X' 'SAPMM07M' '0400',
' ' 'RM07M-BWARTWA' '301',
' ' 'RM07M-WERKS' 'BT',
' ' 'RM07M-LGORT' I_MCHB-LGORT,
' ' 'BDC_OKCODE' '/0',

'X' 'SAPMM07M' '0421',
' ' 'MSEGK-UMWRK' '94',
' ' 'MSEGK-UMLGO' I_MCHB-LGORT,
' ' 'BDC_OKCODE' 'NLE',
*CODING BLOCK
'X' 'SAPLKACB' '0002',
' ' 'BDC_OKCODE' '/0',

'X' 'SAPMM07M' '0421',
' ' 'MSEG-MATNR(1)' I_MCHB-MATNR,
' ' 'MSEG-ERFMG(1)' W_QTY,
' ' 'MSEG-CHARG(1)' I_MCHB-CHARG,
' ' 'BDC_OKCODE' '/0',
*CODING BLOCK
'X' 'SAPLKACB' '0002',
' ' 'BDC_OKCODE' '/0',

*CODING BLOCK
'X' 'SAPLKACB' '0002',
' ' 'BDC_OKCODE' '/0',

* 'X' 'SAPMM07M' '0410',
* ' ' 'BDC_OKCODE' '/0',
*CODING BLOCK
* 'X' 'SAPLKACB' '0002',
* ' ' 'BDC_OKCODE' '/8',

*CODING BLOCK
* 'X' 'SAPLKACB' '0002',
* ' ' 'BDC_OKCODE' '/8',

'X' 'SAPLJ2CW' '0190',
' ' 'J_5C7-UMCHA' I_MCHB-CHARG,
' ' 'BDC_OKCODE' '/7',

'X' 'SAPMM07M' '0421',
' ' 'BDC_OKCODE' '/11',
*CODING BLOCK
'X' 'SAPLKACB' '0002',
' ' 'BDC_OKCODE' '/0'.
IF P_DISP = 'X'.
W_MODE = 'A'.
ELSE.
W_MODE = 'N'.
ENDIF.
CALL TRANSACTION 'MB1B' USING BDCDATA MODE W_MODE UPDATE 'S'
MESSAGES INTO MESSTAB.

WRITE: / I_MCHB-MATNR, I_MCHB-CHARG, I_MCHB-LGORT,
I_MCHB-J_2CTRNR, I_MCHB-J_2CELNG.

IF SY-SUBRC NE 0.
* what to do if there's an error????
LOOP AT MESSTAB.
SY-MSGNO = MESSTAB-MSGNR.
CALL FUNCTION 'WRITE_MESSAGE'
EXPORTING
MSGID = MESSTAB-MSGID
MSGNO = SY-MSGNO
MSGTY = MESSTAB-MSGTYP
MSGV1 = MESSTAB-MSGV1
MSGV2 = MESSTAB-MSGV2
MSGV3 = MESSTAB-MSGV3
MSGV4 = MESSTAB-MSGV4
MSGV5 = MESSTAB-MSGV4
IMPORTING
* error =
MESSG = W_MESSAGE
* msgln =
EXCEPTIONS
OTHERS = 1.
WRITE: / W_MESSAGE.
* message id messtab-msgid type 'I' number messtab-msgnr.
ENDLOOP.

ENDIF.

ENDFORM. " CHANGE_BILLING_TYPE

*-----------------------------------------------------------------------
* FORM DYNPRO - new form smt nov 1998
*-----------------------------------------------------------------------
* > DYNBEGIN
* > NAME
* > VALUE
*-----------------------------------------------------------------------
*
FORM DYNPRO USING DYNBEGIN NAME VALUE.

IF DYNBEGIN = 'X'.
CLEAR BDCDATA.
MOVE: NAME TO BDCDATA-PROGRAM,
VALUE TO BDCDATA-DYNPRO,
'X' TO BDCDATA-DYNBEGIN.
APPEND BDCDATA.
ELSE.
CLEAR BDCDATA.
MOVE: NAME TO BDCDATA-FNAM,
VALUE TO BDCDATA-FVAL.
APPEND BDCDATA.
ENDIF.

ENDFORM.
*

Sample ABAP Program of Function Module to Convert Work Center into Personnel Number

2007-10-18T22:03:00.000+05:30

FUNCTION z_get_pernr_from_wc.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(I_WORK_CENTRE) TYPE ARBPL
*" EXPORTING
*" VALUE(E_PERSONNEL_NO) TYPE PERNR
*"----------------------------------------------------------------------
* Author: Sheila Titchener - www.iconet-ltd.co.uk
* Date: July 2005
* Description: Convert Work Centre into Personnel Number
*"----------------------------------------------------------------------
DATA: l_hroid TYPE hrobjid,
l_sobid TYPE sobid.

SELECT SINGLE hroid FROM crhd
INTO l_hroid
WHERE objty = 'A'
AND arbpl = i_work_centre.

CHECK sy-subrc = 0.

SELECT SINGLE sobid FROM hrp1001
INTO l_sobid
WHERE objid = l_hroid
AND sclas = 'S'.

CHECK sy-subrc = 0.

SELECT SINGLE sobid FROM hrp1001
INTO l_sobid
WHERE otype = 'S'
AND objid = l_sobid
AND sclas = 'P'.

CHECK sy-subrc = 0.

e_personnel_no = l_sobid.

ENDFUNCTION.

Sample ABAP Program of FTP Function Module

2007-10-18T22:02:00.000+05:30

FUNCTION Y_FTP.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(USER)
*" VALUE(PWD)
*" VALUE(HOST)
*" TABLES
*" COMMANDS
*" EXCEPTIONS
*" NO_SUCH_FILE
*"----------------------------------------------------------------------

DATA: W_USER(12) TYPE C ,
W_PWD(20) TYPE C ,
W_HOST(64) TYPE C.

DATA: HDL TYPE I,
KEY TYPE I VALUE 26101957,
DSTLEN TYPE I.

DATA: BEGIN OF RESULT OCCURS 0,
LINE(100) TYPE C,
END OF RESULT.

DESCRIBE FIELD PWD LENGTH DSTLEN.

CALL 'AB_RFC_X_SCRAMBLE_STRING'
ID 'SOURCE' FIELD PWD ID 'KEY' FIELD KEY
ID 'SCR' FIELD 'X' ID 'DESTINATION' FIELD PWD
ID 'DSTLEN' FIELD DSTLEN.

CALL FUNCTION 'FTP_CONNECT'
EXPORTING
USER = USER
PASSWORD = PWD
HOST = HOST
RFC_DESTINATION = 'SAPFTP'
IMPORTING
HANDLE = HDL.

LOOP AT COMMANDS.
IF COMMANDS NE ' '.
CALL FUNCTION 'FTP_COMMAND'
EXPORTING
HANDLE = HDL
COMMAND = COMMANDS
TABLES
DATA = RESULT
EXCEPTIONS
COMMAND_ERROR = 1
TCPIP_ERROR = 2.
LOOP AT RESULT.
WRITE AT / RESULT-LINE.
IF RESULT CS 'error'.
RAISE NO_SUCH_FILE.
ENDIF.
ENDLOOP.
REFRESH RESULT.
ENDIF.
ENDLOOP.

CALL FUNCTION 'FTP_DISCONNECT'
EXPORTING
HANDLE = HDL.

ENDFUNCTION.

Sample ABAP Program to EXPORT LIST TO MEMORY

2007-10-18T22:00:00.001+05:30

************************************************************************
* Author - Sheila Titchener *
* Program - Report of orders with billing/delivery blocks
* Date - October 1998 *
* Company - IconeT Services *
************************************************************************
************************************************************************

REPORT YVREE024 LINE-SIZE 185 LINE-COUNT 63 NO STANDARD PAGE HEADING.

*---------------------------------------------------------------------*
* DATA DECLARATIONS *
*---------------------------------------------------------------------*

TABLES: VBAK, VBAP, VBEP, KNA1, TVFST, TVLST.

* Selection screens.
*-----------------------------------------------------------------------
* mandatory parameters
SELECTION-SCREEN BEGIN OF BLOCK PARAMETERS
WITH FRAME
TITLE TEXT-020 .
PARAMETERS: P_VKORG LIKE VBAK-VKORG OBLIGATORY ,
P_VTWEG LIKE VBAK-VTWEG OBLIGATORY ,
P_SPART LIKE VBAK-SPART OBLIGATORY .

SELECTION-SCREEN END OF BLOCK PARAMETERS.
*-----------------------------------------------------------------------
* optional selection ranges
SELECTION-SCREEN BEGIN OF BLOCK SELECT_CRITERIA
WITH FRAME
TITLE TEXT-010 .
SELECT-OPTIONS:
S_VKBUR FOR VBAK-VKBUR,
S_VKGRP FOR VBAK-VKGRP,
S_KUNNR FOR VBAK-KUNNR.

SELECTION-SCREEN END OF BLOCK SELECT_CRITERIA .

* Order header table.
DATA: BEGIN OF I_VBAK OCCURS 0,
VBELN LIKE VBAK-VBELN,
KUNNR LIKE VBAK-KUNNR,
FAKSK LIKE VBAK-FAKSK, "billing block
LIFSK LIKE VBAK-LIFSK, "delivery block
END OF I_VBAK.
* report table
DATA: BEGIN OF ITAB OCCURS 0,
VBELN LIKE VBAP-VBELN, " Order Number
KUNNR LIKE VBAK-KUNNR, " Customer Number
NAME1 LIKE KNA1-NAME1, " Customer Name
ERNAM LIKE VBAK-ERNAM, " User created
POSNR LIKE VBAP-POSNR, " Line Item
MATNR LIKE VBAP-MATNR, " Material Number
KWMENG LIKE VBAP-KWMENG, " Quantity
MEINS LIKE VBAP-MEINS, " Unit of measure
NETWR LIKE VBAP-NETWR, " value
FAKSP LIKE VBAP-FAKSP, " billing block
LIFSP LIKE VBEP-LIFSP, " delivery block
END OF ITAB.

*---------------------------------------------------------------------*
INITIALIZATION .
GET PARAMETER ID 'VKO' FIELD P_VKORG.
GET PARAMETER ID 'VTW' FIELD P_VTWEG.
GET PARAMETER ID 'SPA' FIELD P_SPART.

*---------------------------------------------------------------------*
START-OF-SELECTION .
*---------------------------------------------------------------------*
* populate vbak table from selection criteria with headers that have
* billing or delivery blocks
PERFORM SELECT_DOCUMENTS.
* select blocked items from documents selected from vbak
PERFORM SELECT_BLOCKED_ITEMS.
*---------------------------------------------------------------------*
END-OF-SELECTION.
*---------------------------------------------------------------------*

SORT ITAB BY VBELN POSNR.

* print report from internal table
PERFORM PRINT_REPORT.

* run report of orders with payment block on customer
SUBMIT YVREE025 EXPORTING LIST TO MEMORY
AND RETURN
WITH P_VKORG = P_VKORG
WITH P_VTWEG = P_VTWEG
WITH P_SPART = P_SPART
WITH S_VKBUR IN S_VKBUR
WITH S_VKGRP IN S_VKGRP
WITH S_KUNNR IN S_KUNNR.

DATA: ABAPLIST LIKE ABAPLIST OCCURS 0.
* recover YVREE025 report and display
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
LISTOBJECT = ABAPLIST
EXCEPTIONS
NOT_FOUND = 1
OTHERS = 2.

*if sy-batch = space.
CALL FUNCTION 'DISPLAY_LIST'
EXPORTING
FULLSCREEN = 'X'
* CALLER_HANDLES_EVENTS =
IMPORTING
USER_COMMAND = SY-UCOMM
TABLES
LISTOBJECT = ABAPLIST
EXCEPTIONS
EMPTY_LIST = 1
OTHERS = 2.
*else.
* using write_list duplicates yvree024 headings on yvree025 list
* display_list prints ok in background as long as print immediately is
* NOT switched off

*call function 'WRITE_LIST'
* tables
* listobject = abaplist
* exceptions
* empty_list = 1
* others = 2.
*endif.
*---------------------------------------------------------------------*
TOP-OF-PAGE.
*---------------------------------------------------------------------*
* write top of page title.
PERFORM WRITE_TITLE .
* write column headings.
PERFORM WRITE_HEADER.

*&---------------------------------------------------------------------*
*& Form SELECT_DOCUMENTS
*&---------------------------------------------------------------------*
* select order header details from vbak depending on selection
* criteria entered
*----------------------------------------------------------------------*
FORM SELECT_DOCUMENTS.

SELECT VBELN KUNNR LIFSK FAKSK
FROM VBAK INTO CORRESPONDING FIELDS OF TABLE I_VBAK
WHERE VKORG = P_VKORG
AND VTWEG = P_VTWEG
AND SPART = P_SPART
AND VKGRP IN S_VKGRP
AND VKBUR IN S_VKBUR
AND KUNNR IN S_KUNNR.
ENDFORM. " SELECT_DOCUMENTS

*&---------------------------------------------------------------------*
*& Form SELECT_BLOCKED_ITEMS
*&---------------------------------------------------------------------*
* check extracted documents for blocks *
*----------------------------------------------------------------------*
FORM SELECT_BLOCKED_ITEMS.
* process oders selected
LOOP AT I_VBAK.
* if order blocked at header level select all items
IF I_VBAK-FAKSK NE SPACE OR I_VBAK-LIFSK NE SPACE.
PERFORM SELECT_ALL_ITEMS.
ELSE.
* check for block at item level
SELECT VBELN POSNR MATNR KWMENG MEINS NETWR FAKSP ERNAM
FROM VBAP INTO
(VBAP-VBELN, VBAP-POSNR, VBAP-MATNR, VBAP-KWMENG, VBAP-MEINS,
VBAP-NETWR, VBAP-FAKSP, VBAP-ERNAM)
WHERE VBELN = I_VBAK-VBELN.
IF VBAP-FAKSP NE SPACE.
CLEAR ITAB.
MOVE-CORRESPONDING VBAP TO ITAB.
MOVE I_VBAK-KUNNR TO ITAB-KUNNR.
APPEND ITAB.
ELSE.
* check for block at delivery level
SELECT LIFSP WMENG FROM VBEP INTO
(VBEP-LIFSP, VBEP-WMENG)
WHERE VBELN = I_VBAK-VBELN
AND POSNR = VBAP-POSNR.
IF VBEP-LIFSP NE SPACE.
CLEAR ITAB.
MOVE-CORRESPONDING VBAP TO ITAB.
MOVE I_VBAK-KUNNR TO ITAB-KUNNR.
* use schedule qty
MOVE VBEP-WMENG TO ITAB-KWMENG.
* and reason
MOVE VBEP-LIFSP TO ITAB-LIFSP.
* recalculate value
ITAB-NETWR = ITAB-NETWR / VBAP-KWMENG * VBEP-WMENG.
APPEND ITAB.
ENDIF.
ENDSELECT.
ENDIF.
ENDSELECT.

ENDIF.
ENDLOOP.

ENDFORM. " SELECT_BLOCKED_ITEMS

*&---------------------------------------------------------------------*
*& Form PRINT_REPORT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
FORM PRINT_REPORT.

DATA: W_REASON_TEXT(25).

LOOP AT ITAB.
* get name
SELECT SINGLE NAME1 FROM KNA1 INTO KNA1-NAME1
WHERE KUNNR = ITAB-KUNNR .
* get reason text
IF ITAB-FAKSP NE SPACE.
SELECT SINGLE VTEXT FROM TVFST INTO W_REASON_TEXT
WHERE SPRAS = SY-LANGU
AND FAKSP = ITAB-FAKSP .
ELSE.

SELECT SINGLE VTEXT FROM TVLST INTO W_REASON_TEXT
WHERE SPRAS = SY-LANGU
AND LIFSP = ITAB-LIFSP.
ENDIF.
*
WRITE: / SY-VLINE , (10) ITAB-VBELN,
SY-VLINE , (10) ITAB-KUNNR,
SY-VLINE , (35) KNA1-NAME1,
SY-VLINE , (12) ITAB-ERNAM,
SY-VLINE , (6) ITAB-POSNR,
SY-VLINE , (18) ITAB-MATNR,
SY-VLINE , (10) ITAB-KWMENG DECIMALS 0,
SY-VLINE , (3) ITAB-MEINS,
SY-VLINE , (15) ITAB-NETWR,
SY-VLINE , (02) ITAB-LIFSP,
SY-VLINE , (02) ITAB-FAKSP,
SY-VLINE , (25) W_REASON_TEXT,
SY-VLINE .
ENDLOOP.

WRITE:/1(185) SY-ULINE.
ENDFORM. " PRINT_REPORT

*---------------------------------------------------------------------*
* FORM WRITE_TITLE *
*---------------------------------------------------------------------*
* Form to write top of page title. *
*---------------------------------------------------------------------*
FORM WRITE_TITLE.

WRITE:/1(185) SY-ULINE.
WRITE:/ 'Pirelli Cables Limited' ,
40 SY-TITLE , " Report title
120 'Date :' , 130 SY-DATUM .

WRITE:/120 'Page :' ,
130 SY-PAGNO , " Page number of the report
160 'YV24 / YVREE024 /', SY-MANDT.
WRITE:/160 'Report 2 of 2'.
WRITE:/1(185) SY-ULINE.

* format color col_heading intensified off.

WRITE:/(25) 'Report generated for; ',
'Sales Organisation:',
P_VKORG ,
' Distribution Channel:',
P_VTWEG,
' Division:',
P_SPART.
WRITE: /27
'Sales Office:',
S_VKBUR-LOW.
IF S_VKBUR-HIGH NE SPACE.
WRITE: ' - ', S_VKBUR-HIGH.
ENDIF.
WRITE: 59 ' Sales Group:',
S_VKGRP-LOW.
IF S_VKGRP-HIGH NE SPACE.
WRITE: ' - ', S_VKGRP-HIGH.
ENDIF.
WRITE: 92 ' Customer:',
S_KUNNR-LOW.
IF S_KUNNR-HIGH NE SPACE.
WRITE: ' - ', S_KUNNR-HIGH.
ENDIF.
WRITE:/1(185) SY-ULINE.

ENDFORM.

*---------------------------------------------------------------------*
* FORM WRITE-HEADER *
*---------------------------------------------------------------------*
* Form to write Column headings *
*---------------------------------------------------------------------*
FORM WRITE_HEADER.

SKIP.

FORMAT COLOR COL_HEADING INTENSIFIED.

WRITE:/1(185) SY-ULINE.
WRITE:/
SY-VLINE , (10) ' Order ' ,
SY-VLINE , (10) ' Customer ' ,
SY-VLINE , (35) ' Name ' ,
SY-VLINE , (12) ' User created',
SY-VLINE , (06) ' Item ' ,
SY-VLINE , (18) ' Material',
SY-VLINE , (10) 'Quantity' CENTERED DECIMALS 0,
SY-VLINE , (03) 'UOM' ,
SY-VLINE , (15) ' Value ',
SY-VLINE , (02) 'DB',
SY-VLINE , (02) 'BB',
SY-VLINE , (25) ' Reason',
SY-VLINE .

ENDFORM.

*&---------------------------------------------------------------------*
*& Form SELECT_ALL_ITEMS
*&---------------------------------------------------------------------*
* select all items for this header when blocked at header level *
*----------------------------------------------------------------------*
FORM SELECT_ALL_ITEMS.

SELECT VBELN POSNR MATNR KWMENG MEINS NETWR ERNAM
FROM VBAP INTO
(VBAP-VBELN, VBAP-POSNR, VBAP-MATNR, VBAP-KWMENG, VBAP-MEINS,
VBAP-NETWR, VBAP-ERNAM)
* REMOVED appending corresponding fields of table itab
WHERE VBELN = I_VBAK-VBELN.
MOVE-CORRESPONDING VBAP TO ITAB.
MOVE I_VBAK-FAKSK TO ITAB-FAKSP.
MOVE I_VBAK-LIFSK TO ITAB-LIFSP.
MOVE I_VBAK-KUNNR TO ITAB-KUNNR.
APPEND ITAB.
ENDSELECT.

ENDFORM. " SELECT_ALL_ITEMS

Sample ABAP Program to Execute Unix command from within SAP

2007-10-18T21:57:00.000+05:30

REPORT YSMT018A
MESSAGE-ID YL.
* ABAP to append ribesnsl to ribes
* and remove input file using sxpg_command_execute

DATA: FILE1(25) VALUE '/vmedata/???/file1nsl'.
DATA: FILE2(25) VALUE '/vmedata/???/file2'.
DATA: W_MESSAGE(50).
DATA: RLBES LIKE RLBES.
FILE1+9(3) = SY-SYSID.
FILE2+9(3) = SY-SYSID.
* sxpg_command_execute parameters
DATA: REMOVE_FILE LIKE SXPGCOLIST-PARAMETERS.
DATA: PROTOCOL LIKE BTCXPM OCCURS 0.
*
OPEN DATASET FILE2 FOR APPENDING IN TEXT MODE MESSAGE W_MESSAGE.
IF SY-SUBRC NE 0 .
MESSAGE E114 WITH FILE2 W_MESSAGE.
ENDIF.
OPEN DATASET FILE1 FOR INPUT IN TEXT MODE MESSAGE W_MESSAGE.
IF SY-SUBRC NE 0.
MESSAGE E114 WITH FILE1 W_MESSAGE.
ENDIF.

DO.
READ DATASET FILE1 INTO RLBES.
IF SY-SUBRC NE 0.
EXIT.
ENDIF.
TRANSFER RLBES TO FILE2.
IF SY-SUBRC NE 0.
MESSAGE E009 WITH FILE2 SY-SUBRC.
ENDIF.
ENDDO.

MESSAGE I114 WITH FILE1 'appended'.
***----------------------------------------------------------------****

DATA: COMMAND3(60)
* VALUE 'rm /vmedata/???/rlbesnsl' .
VALUE 'rm /vmedata/???/file1nsl' .

COMMAND3+12(3) = SY-SYSID.

*submit the unix command remove file1
REMOVE_FILE = COMMAND3+3.
* create y_remove command in sm69
CALL FUNCTION 'SXPG_COMMAND_EXECUTE'
EXPORTING
COMMANDNAME = 'Y_REMOVE'
* OPERATINGSYSTEM = SY-OPSYS
* TARGETSYSTEM = SY-HOST
* STDOUT = 'X'
* STDERR = 'X'
* TERMINATIONWAIT = 'X'
* TRACE = ' '
ADDITIONAL_PARAMETERS = REMOVE_FILE
* IMPORTING
* STATUS =
TABLES
EXEC_PROTOCOL = PROTOCOL
EXCEPTIONS
NO_PERMISSION = 1
COMMAND_NOT_FOUND = 2
PARAMETERS_TOO_LONG = 3
SECURITY_RISK = 4
WRONG_CHECK_CALL_INTERFACE = 5
PROGRAM_START_ERROR = 6
PROGRAM_TERMINATION_ERROR = 7
X_ERROR = 8
PARAMETER_EXPECTED = 9
TOO_MANY_PARAMETERS = 10
ILLEGAL_COMMAND = 11
WRONG_ASYNCHRONOUS_PARAMETERS = 12
CANT_ENQ_TBTCO_ENTRY = 13
JOBCOUNT_GENERATION_ERROR = 14
OTHERS = 15.

IF SY-SUBRC = 0.
MESSAGE I114 WITH FILE1 'deleted'.
ENDIF.

Sample ABAP Program to Get Output in EXCEL

2007-10-18T21:55:00.000+05:30

REPORT YLMM015A

MESSAGE-ID YL.

*-----------------------------------------------------------------------

*

* EDI FORECASTING INTERFACE - SHEILA TITCHENER JAN 1998

* L_IDOC_HEADER_CREATE, L_IDOC_SEGMENT_CREATE & L_IDOC_SEND

* left idoc ready to send but did not send automatically.

* these were replaced by ALE_MODEL_DETERMINE_IF_TO_SEND

* ALE_MODEL_INFO_GET & MASTER_IDOC_DISTRIBUTE

* 'in update task'. This solved the problem. Records are set up in table

* t_edidd.

*-----------------------------------------------------------------------

* TABLES - Database *

*-----------------------------------------------------------------------

TABLES: EORD,

MARC,

MARM,

EINA,

PLAF,

EBAN,

EDIDD.

*-----------------------------------------------------------------------

* DATA - Work Fields

*-----------------------------------------------------------------------

DATA: W_START_MONTH LIKE SY-DATUM.

DATA: W_NEXT_MONTH LIKE SY-DATUM.

DATA: W_THIRD_MONTH LIKE SY-DATUM.

DATA: W_END_DATE LIKE SY-DATUM.

DATA: W_COMP_DATE LIKE SY-DATUM.

DATA: W_BEG_DATE LIKE SY-DATUM.

DATA: W_DESP_DATE LIKE SY-DATUM.

DATA: W_DAY LIKE HRVSCHED-DAYNR.

DATA: W_DAY_TXT LIKE HRVSCHED-DAYTXT.

DATA: W_INDEX LIKE SY-TABIX.

DATA: W_TOTAL LIKE EBAN-MENGE.

DATA: W_ITEM_NUMBER TYPE I.

* IDOC DATA

DATA: W_E1EDK01_DATA LIKE E1EDK01.

DATA: W_E1EDK03_DATA LIKE E1EDK03.

DATA: W_E1EDKA1_DATA LIKE E1EDKA1.

DATA: W_E1EDP01_DATA LIKE E1EDP01.

DATA: W_E1EDP20_DATA LIKE E1EDP20.

DATA: W_E1EDP19_DATA LIKE E1EDP19.

* DATA - INTERNAL TABLES

*-----------------------------------------------------------------------

* forecast buckets - 8/9 weekly for first 2 months then 10 monthly

DATA: BEGIN OF FORECAST OCCURS 19,

DATE TYPE D, "start date of bucket

WEEK_MON, "weekly or monthly indicator

QTY LIKE EBAN-MENGE. "accumulated qty

DATA: END OF FORECAST.

*DATA: PRODUCTS LIKE EORD OCCURS 10 WITH HEADER LINE.

DATA: BEGIN OF PRODUCTS OCCURS 10,

MATNR LIKE EORD-MATNR,

WERKS LIKE EORD-WERKS,

LIFNR LIKE EORD-LIFNR.

DATA: END OF PRODUCTS.

* planned orders table PLAF

DATA: BEGIN OF T_PLAF OCCURS 10,

GSMNG LIKE PLAF-GSMNG,

PEDTR LIKE PLAF-PEDTR.

DATA: END OF T_PLAF.

* planned orders table EBAN

DATA: BEGIN OF T_EBAN OCCURS 10,

MENGE LIKE EBAN-MENGE,

LFDAT LIKE EBAN-LFDAT.

DATA: END OF T_EBAN.

* IDOC _SEND parameter

DATA: COMM_IDOC_CONTROL LIKE EDIDC OCCURS 1 WITH HEADER LINE.

*-----------------------------------------------------------------------

* new fields for new way of sending IDOC

DATA: W_EDIDC LIKE EDIDC OCCURS 5 WITH HEADER LINE,

L_EDIDC LIKE EDIDC,

L_SEND_FLAG,

W_SDATA LIKE EDIDD-SDATA.

DATA: T_BDI_MODEL LIKE BDI_MODEL OCCURS 0 WITH HEADER LINE.

DATA: T_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE.

DATA: T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.

*--------------------------------------------------------------------

* OUTPUT file layout

DATA: BEGIN OF OUTREC,

MATNR LIKE EBAN-MATNR,

D1 VALUE '$',

IDNLF LIKE EINA-IDNLF,

D2 VALUE '$',

WEEK_MON,

D3 VALUE '$',

PERIOD LIKE SY-DATUM,

D4 VALUE '$',

QTY(8),

ENDOFLINE TYPE X VALUE '0D',

END OF OUTREC.

*-----------------------------------------------------------------------

* SELECT-OPTIONS

*-----------------------------------------------------------------------

SELECT-OPTIONS P_LIFNR FOR EORD-LIFNR.

*-----------------------------------------------------------------------

* PARAMETERS *

*-----------------------------------------------------------------------

PARAMETERS: P_PART LIKE EDIDC-RCVPRN DEFAULT 'EDIFCAST',

P_FILE(30) DEFAULT '/vmedata/XXX/mdafcstddmmyy' LOWER CASE.

*-----------------------------------------------------------------------

* INITIALIZATION.

*-----------------------------------------------------------------------

INITIALIZATION.

* move hoot name to output file name

P_FILE+9(3) = SY-SYSID.

* move todays date to output file name

P_FILE+20(2) = SY-DATUM+6(2).

P_FILE+22(2) = SY-DATUM+4(2).

P_FILE+24(2) = SY-DATUM+2(2).

*-----------------------------------------------------------------------

START-OF-SELECTION.

*-----------------------------------------------------------------------

* OPEN $ delimited file

OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.

* 4.1 create header idoc

* REPLACE function with alternative

* CALL FUNCTION 'L_IDOC_HEADER_CREATE'

* EXPORTING

* I_MESTYP = 'ORDERS'

* I_MESCOD = ' '

* I_IDOCTP = 'ORDERS01'

* I_RCVPRN = P_PART

* EXCEPTIONS

* OTHERS = 1.

*- Call function module to determine if message is to be distributed

CALL FUNCTION 'ALE_MODEL_DETERMINE_IF_TO_SEND'

EXPORTING

MESSAGE_TYPE = 'ORDERS'

IMPORTING

IDOC_MUST_BE_SENT = L_SEND_FLAG

EXCEPTIONS

OWN_SYSTEM_NOT_DEFINED = 1

OTHERS = 2.

*- Determine recipient systems

CALL FUNCTION 'ALE_MODEL_INFO_GET'

EXPORTING

MESSAGE_TYPE = 'ORDERS'

* RECEIVING_SYSTEM = ' '

* SENDING_SYSTEM = ' '

* VALIDDATE = SY-DATUM

TABLES

MODEL_DATA = T_BDI_MODEL

EXCEPTIONS

NO_MODEL_INFO_FOUND = 1

OWN_SYSTEM_NOT_DEFINED = 2

OTHERS = 3.

* 4.2 - 4.5 create idoc segments

PERFORM IDOC_CREATE.

* 4.6 Set up forecast bucket dates

* determine start of the next forecast month

W_START_MONTH = SY-DATUM.

* 12 months ago

*_LAST_12_MTH = SY-DATUM - 365.

IF W_START_MONTH+4(2) = '12'.

W_START_MONTH+4(2) = '01'.

W_START_MONTH(4) = W_START_MONTH(4) + '0001'.

ELSE.

W_START_MONTH+4(2) = W_START_MONTH+4(2) + '01'.

ENDIF.

W_START_MONTH+6 = '01'.

CALL FUNCTION 'RH_GET_DATE_DAYNAME'

EXPORTING

LANGU = 'E'

DATE = W_START_MONTH

* CHECK =

IMPORTING

DAYNR = W_DAY

DAYTXT = W_DAY_TXT

EXCEPTIONS

NO_LANGU = 1

NO_DATE = 2

NO_DAYTXT_FOR_LANGU = 3

INVALID_DATE = 4

OTHERS = 5.

CASE W_DAY.

WHEN 1.

WHEN 2.

W_START_MONTH = W_START_MONTH - 1.

WHEN 3.

W_START_MONTH = W_START_MONTH - 2.

WHEN 4.

W_START_MONTH = W_START_MONTH + 4.

WHEN 5.

W_START_MONTH = W_START_MONTH + 3.

WHEN 6.

W_START_MONTH = W_START_MONTH + 2.

WHEN 7.

W_START_MONTH = W_START_MONTH + 1.

ENDCASE.

* date of start of monthly forecasting

W_THIRD_MONTH = W_START_MONTH.

IF W_START_MONTH+4(2) < '11'.

W_THIRD_MONTH+4(2) = W_THIRD_MONTH+4(2) + '02'.

ELSE.

W_THIRD_MONTH+4(2) = W_THIRD_MONTH+4(2) - '10'.

W_THIRD_MONTH(4) = W_THIRD_MONTH(4) + '0001'.

ENDIF.

* day will be the first

W_THIRD_MONTH+6 = '01'.

* find nearest monday - removed

*CALL FUNCTION 'RH_GET_DATE_DAYNAME'

* EXPORTING

* LANGU = 'E'

* DATE = W_THIRD_MONTH

** CHECK =

* IMPORTING

* DAYNR = W_DAY

* DAYTXT = W_DAY_TXT

* EXCEPTIONS

* NO_LANGU = 1

* NO_DATE = 2

* NO_DAYTXT_FOR_LANGU = 3

* INVALID_DATE = 4

* OTHERS = 5.

*CASE W_DAY.

* WHEN 1.

* WHEN 2.

* W_THIRD_MONTH = W_THIRD_MONTH - 1.

* WHEN 3.

* W_THIRD_MONTH = W_THIRD_MONTH - 2.

* WHEN 4.

* W_THIRD_MONTH = W_THIRD_MONTH + 4.

* WHEN 5.

* W_THIRD_MONTH = W_THIRD_MONTH + 3.

* WHEN 6.

* W_THIRD_MONTH = W_THIRD_MONTH + 2.

* WHEN 7.

* W_THIRD_MONTH = W_THIRD_MONTH + 1.

*ENDCASE.

* set up all dates in table

DO.

IF SY-INDEX = 1.

FORECAST-DATE = W_START_MONTH.

W_NEXT_MONTH = W_START_MONTH.

ELSE.

* if this takes us into the third month set to monthly

IF W_NEXT_MONTH GE W_THIRD_MONTH.

IF W_NEXT_MONTH+4(2) = '12'. " add 1 month

W_NEXT_MONTH+4(2) = '01'.

W_NEXT_MONTH(4) = W_NEXT_MONTH(4) + '0001'.

ELSE.

W_NEXT_MONTH+4(2) = W_NEXT_MONTH+4(2) + '01'.

ENDIF.

* W_NEXT_MONTH = W_NEXT_MONTH + 28.

* IF W_NEXT_MONTH+4(2) = FORECAST-DATE+4(2).

* W_NEXT_MONTH = W_NEXT_MONTH + 7.

* ENDIF.

ELSE.

* add 1 week

W_NEXT_MONTH = W_NEXT_MONTH + 7.

ENDIF.

FORECAST-DATE = W_NEXT_MONTH.

ENDIF.

IF FORECAST-DATE GE W_THIRD_MONTH.

FORECAST-DATE+6(2) = '01'. "set start day to 1

FORECAST-WEEK_MON = '2'.

ELSE.

FORECAST-WEEK_MON = '1'.

ENDIF.

* year complete?

IF FORECAST-DATE+4(2) = W_START_MONTH+4(2)

AND FORECAST-DATE(4) > W_START_MONTH(4).

W_END_DATE = FORECAST-DATE.

EXIT.

ENDIF.

APPEND FORECAST.

ENDDO.

*-----------------------------------------------------------------------

* Start of selection processing

*-----------------------------------------------------------------------

* 4.7 select records from Purchasing Source list

*-----------------------------------------------------------------------

SELECT MATNR WERKS LIFNR FROM EORD INTO TABLE PRODUCTS

WHERE LIFNR IN P_LIFNR

AND FLIFN = 'X'

AND VDATU LE SY-DATUM

AND BDATU GE SY-DATUM.

* check within selection range

* CHECK P_LIFNR.

* add to table

* APPEND PRODUCTS.

*ENDSELECT.

* delete duplicates products

* table already in product code sequence

DELETE ADJACENT DUPLICATES FROM PRODUCTS COMPARING MATNR.

*-----------------------------------------------------------------------

* process selected vendors materials

*-----------------------------------------------------------------------

LOOP AT PRODUCTS.

*--------------------------------------

* 4.7 access material master

*--------------------------------------

SELECT SINGLE * FROM MARC

WHERE MATNR = PRODUCTS-MATNR

AND WERKS = PRODUCTS-WERKS .

CHECK MARC-DISMM = 'PD' OR MARC-DISMM = 'P3'

OR MARC-DISMM = 'ZD' OR MARC-DISMM = 'Z3'.

*--------------------------------------

* 4.8 access purchasing info record

*--------------------------------------

SELECT SINGLE * FROM EINA

WHERE MATNR = PRODUCTS-MATNR

AND LIFNR = PRODUCTS-LIFNR.

* record found?

CHECK SY-SUBRC = 0.

* vendor's material number begins with 45?

CHECK EINA-IDNLF(2) = '45'.

*--------------------------------------

* 4.10 clear forecast quantities

*--------------------------------------

LOOP AT FORECAST.

FORECAST-QTY = 0.

MODIFY FORECAST TRANSPORTING QTY.

ENDLOOP.

*--------------------------------------

* 4.10

*--------------------------------------

* calculate start & end dates

W_COMP_DATE = W_END_DATE + 9.

* W_BEG_DATE = W_START_MONTH + MARC-WEBAZ + 9.

* read all matching material records from planned orders table PLAF

SELECT GSMNG PEDTR FROM PLAF INTO CORRESPONDING FIELDS OF TABLE T_PLAF

WHERE MATNR = PRODUCTS-MATNR

AND PEDTR < W_COMP_DATE.

* AND PEDTR > W_BEG_DATE.

*--------------------------------------

* 4.11 process any records found

*--------------------------------------

IF SY-SUBRC = 0.

LOOP AT T_PLAF.

W_DESP_DATE = T_PLAF-PEDTR - 9.

* IF date is < first date add to first date

READ TABLE FORECAST INDEX 1.

IF FORECAST-DATE GE W_DESP_DATE.

W_INDEX = 1.

ELSE.

* find first slot where date > despatch date.

LOOP AT FORECAST

WHERE DATE GE W_DESP_DATE.

W_INDEX = SY-TABIX.

EXIT.

ENDLOOP.

* read previous entry.

W_INDEX = W_INDEX - 1.

READ TABLE FORECAST INDEX W_INDEX.

ENDIF.

* convert to purchasing unit of measure

IF EINA-UMREZ NE 0.

T_PLAF-GSMNG = T_PLAF-GSMNG * EINA-UMREN / EINA-UMREZ.

ENDIF.

*

FORECAST-QTY = FORECAST-QTY + T_PLAF-GSMNG.

MODIFY FORECAST INDEX W_INDEX.

ENDLOOP.

ENDIF.

*--------------------------------------

* 4.12 read all matching material records from planned orders table EBAN

*--------------------------------------

SELECT MENGE LFDAT FROM EBAN INTO CORRESPONDING FIELDS OF TABLE T_EBAN

WHERE MATNR = PRODUCTS-MATNR

AND LFDAT < W_COMP_DATE.

* AND LFDAT > W_BEG_DATE.

*--------------------------------------

* 4.13 process any records found

*--------------------------------------

IF SY-SUBRC = 0.

LOOP AT T_EBAN.

W_DESP_DATE = T_EBAN-LFDAT - 9.

* IF date is < first date add to first date

READ TABLE FORECAST INDEX 1.

IF FORECAST-DATE GE W_DESP_DATE.

W_INDEX = 1.

ELSE.

* find first slot where date > despatch date.

LOOP AT FORECAST

WHERE DATE GE W_DESP_DATE.

W_INDEX = SY-TABIX.

EXIT.

ENDLOOP.

* read previous entry.

W_INDEX = W_INDEX - 1.

READ TABLE FORECAST INDEX W_INDEX.

ENDIF.

* convert to purchasing unit of measure

IF EINA-UMREZ NE 0.

T_EBAN-MENGE = T_EBAN-MENGE * EINA-UMREN / EINA-UMREZ.

ENDIF.

* add to table

FORECAST-QTY = FORECAST-QTY + T_EBAN-MENGE.

MODIFY FORECAST INDEX W_INDEX.

ENDLOOP.

ENDIF.

*-----------------------------------------------------------------------

* 4.14 total all forecast buckets

*--------------------------------------

W_TOTAL = 0.

LOOP AT FORECAST.

W_TOTAL = W_TOTAL + FORECAST-QTY.

ENDLOOP.

CHECK W_TOTAL NE 0.

*--------------------------------------

* create idocs for material forecast

*--------------------------------------

W_ITEM_NUMBER = W_ITEM_NUMBER + 1.

IF W_ITEM_NUMBER > 80.

W_ITEM_NUMBER = 1.

PERFORM IDOC_CREATE.

ENDIF.

*--------------------------------------

* 4.14.3 create idoc E1EDP01

*--------------------------------------

W_E1EDP01_DATA-POSEX = W_ITEM_NUMBER.

WRITE W_TOTAL TO W_E1EDP01_DATA-MENGE DECIMALS 0.

* EDIDD-SDATA = W_E1EDP01_DATA.

T_EDIDD-SDATA = W_E1EDP01_DATA.

W_SDATA = W_E1EDP01_DATA. "????

T_EDIDD-SEGNAM = 'E1EDP01'.

APPEND T_EDIDD.

* CALL FUNCTION 'L_IDOC_SEGMENT_CREATE'

* EXPORTING

* I_SEGNAM = 'E1EDP01'

* I_SDATA = EDIDD-SDATA

* EXCEPTIONS

* OTHERS = 1.

*--------------------------------------

* 4.14.4 create idoc E1EDP20

*--------------------------------------

LOOP AT FORECAST.

IF FORECAST-QTY NE 0.

WRITE FORECAST-QTY TO W_E1EDP20_DATA-WMENG DECIMALS 0.

W_E1EDP20_DATA-AMENG = FORECAST-WEEK_MON.

W_E1EDP20_DATA-EDATU = FORECAST-DATE.

* EDIDD-SDATA = W_E1EDP20_DATA.

T_EDIDD-SDATA = W_E1EDP20_DATA.

W_SDATA = W_E1EDP20_DATA. "????

T_EDIDD-SEGNAM = 'E1EDP20'.

APPEND T_EDIDD.

* CALL FUNCTION 'L_IDOC_SEGMENT_CREATE'

* EXPORTING

* I_SEGNAM = 'E1EDP20'

* I_SDATA = EDIDD-SDATA

* EXCEPTIONS

* OTHERS = 1.

*--------------------------------------

* write record to $ delimited file

*--------------------------------------

OUTREC-MATNR = PRODUCTS-MATNR.

OUTREC-IDNLF = EINA-IDNLF.

OUTREC-WEEK_MON = FORECAST-WEEK_MON.

OUTREC-PERIOD = FORECAST-DATE.

WRITE FORECAST-QTY TO OUTREC-QTY DECIMALS 0.

TRANSFER OUTREC TO P_FILE.

ENDIF.

ENDLOOP.

* 4.14.5 End of this product

*--------------------------------------

W_E1EDP19_DATA-IDTNR = EINA-IDNLF.

* EDIDD-SDATA = W_E1EDP19_DATA.

T_EDIDD-SDATA = W_E1EDP19_DATA.

W_SDATA = W_E1EDP19_DATA. "????

T_EDIDD-SEGNAM = 'E1EDP19'.

APPEND T_EDIDD.

* CALL FUNCTION 'L_IDOC_SEGMENT_CREATE'

* EXPORTING

* I_SEGNAM = 'E1EDP19'

* I_SDATA = EDIDD-SDATA

* EXCEPTIONS

* OTHERS = 1.

ENDLOOP.

*--------------------------------------

* end of all products

*-----------------------------------------------------------------------

* REPLACE WITH MASTER_IDOC_DISTRIBUTE

* CALL FUNCTION 'L_IDOC_SEND'

* TABLES

* T_COMM_IDOC = COMM_IDOC_CONTROL

* EXCEPTIONS

* ERROR_DISTRIBUTE_IDOC = 1

* OTHERS = 2.

READ TABLE T_BDI_MODEL INDEX 1. " maximum 1 recipient

MOVE 'ORDERS' TO L_EDIDC-MESTYP.

MOVE 'ORDERS01' TO L_EDIDC-IDOCTP.

MOVE 'LS' TO L_EDIDC-RCVPRT.

* MOVE T_BDI_MODEL-RCVSYSTEM TO L_EDIDC-RCVPRN.

* partner profile parameter

MOVE P_PART TO L_EDIDC-RCVPRN.

*- Distribute the iDoc

CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' IN UPDATE TASK

EXPORTING

MASTER_IDOC_CONTROL = L_EDIDC

TABLES

COMMUNICATION_IDOC_CONTROL = COMM_IDOC_CONTROL

MASTER_IDOC_DATA = T_EDIDD

EXCEPTIONS

ERROR_IN_IDOC_CONTROL = 01

ERROR_WRITING_IDOC_STATUS = 02

ERROR_IN_IDOC_DATA = 03

SENDING_LOGICAL_SYSTEM_UNKNOWN = 04.

COMMIT WORK.

*-----------------------------------------------------------------------

END-OF-SELECTION.

CLOSE DATASET P_FILE.

*-----------------------------------------------------------------------

FORM IDOC_CREATE.

*-----------------------------------------------------------------------

* 4.2 Create idoc segment E1EDK01

W_E1EDK01_DATA-BELNR = 'EDI FORECAST'.

* EDIDD-SDATA = W_E1EDK01_DATA.

T_EDIDD-SDATA = W_E1EDK01_DATA.

W_SDATA = W_E1EDK01_DATA. "????

T_EDIDD-SEGNAM = 'E1EDK01'.

APPEND T_EDIDD.

* CALL FUNCTION 'L_IDOC_SEGMENT_CREATE'

* EXPORTING

* I_SEGNAM = 'E1EDK01'

* I_SDATA = EDIDD-SDATA

* EXCEPTIONS

* OTHERS = 1.

*--------------------------------------

* 4.3 Create idoc segments E1EDK03

*--------------------------------------

W_E1EDK03_DATA-IDDAT = '002'.

W_E1EDK03_DATA-DATUM = SY-DATUM.

* EDIDD-SDATA = W_E1EDK03_DATA.

T_EDIDD-SDATA = W_E1EDK03_DATA.

W_SDATA = W_E1EDK03_DATA. "????

T_EDIDD-SEGNAM = 'E1EDK03'.

APPEND T_EDIDD.

* CALL FUNCTION 'L_IDOC_SEGMENT_CREATE'

* EXPORTING

* I_SEGNAM = 'E1EDK03'

* I_SDATA = EDIDD-SDATA

* EXCEPTIONS

* OTHERS = 1.

*--------------------------------------

* 4.4 Create idco E1EDKA1

*--------------------------------------

W_E1EDKA1_DATA-PARVW = 'LI'.

W_E1EDKA1_DATA-PARTN = P_PART.

* EDIDD-SDATA = W_E1EDKA1_DATA.

T_EDIDD-SDATA = W_E1EDKA1_DATA.

W_SDATA = W_E1EDKA1_DATA. "????

T_EDIDD-SEGNAM = 'E1EDKA1'.

APPEND T_EDIDD.

* CALL FUNCTION 'L_IDOC_SEGMENT_CREATE'

* EXPORTING

* I_SEGNAM = 'E1EDKA1'

* I_SDATA = EDIDD-SDATA

* EXCEPTIONS

* OTHERS = 1.

ENDFORM.

Sample ABAP Program to Implement EDI

2007-10-18T21:54:00.000+05:30

Sample Program to dynamically change upload/download program for any Table

2007-10-18T21:51:00.000+05:30

*&---------------------------------------------------------------------*
*& Report ZRUNUPLOAD *
*& *
*&---------------------------------------------------------------------*
*& Written by Sheila Titchener abap at iconet-ltd.co.uk *
*& *
*&---------------------------------------------------------------------*

REPORT ZRUNUPLOAD .

data: code like rssource-line occurs 1 with header line,
filename(50).

PARAMETERS: p_dir(80)
DEFAULT 'C:\Documents and Settings\My Documents',
p_file(20).

read report 'ZUPLOAD' into code.

LOOP AT code.
IF code CS 'ztest'.
REPLACE 'ztest' WITH p_file INTO code.
MODIFY code INDEX sy-tabix.
ENDIF.
ENDLOOP.

insert report 'ZUPLOAD1' from code.

commit work.

CONCATENATE p_dir p_file '.xls' INTO filename.

submit ZUPLOAD1 with p_file = p_file.

Sample ABAP Program to download table using new function GUI_DOWNLOAD

2007-10-18T21:49:00.000+05:30

*&---------------------------------------------------------------------*
*& Report ZDOWNLOAD *
*& *
*&---------------------------------------------------------------------*
*& This program uses the new function GUI_DOWNLOAD *
*& Output will be TAB delimited and include MANDT *
*& It can be opened directly by Microsoft Excel *
*& To use this program for any Database Table replace ZTEST with *
*& new table name. *
*&---------------------------------------------------------------------*
*& AUTHOR: Sheila Titchener - abap at iconet-ltd.co.uk *
*& Date: February 2004 *
*&---------------------------------------------------------------------*

REPORT zdownload MESSAGE-ID bd.

DATA: w_tab TYPE ztest.
DATA: i_tab TYPE STANDARD TABLE OF ztest.

DATA: v_subrc(2),
v_recswritten(6).

PARAMETERS: p_file(80)
DEFAULT 'D:\\ICONET\\SAP\\ZTEST.DAT'.

DATA: filename TYPE string.

filename = p_file.

SELECT * FROM ztest INTO TABLE I_TAB.

* If text fields appear right justified or columns not lined up in output set
* TRUNC_TRAILING_BLANKS to X

CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
* BIN_FILESIZE =
filename = filename
* FILETYPE = 'ASC'
* APPEND = ' '
WRITE_FIELD_SEPARATOR = 'X'
* HEADER = '00'
TRUNC_TRAILING_BLANKS = 'X '
* WRITE_LF = 'X'
* COL_SELECT = ' '
* COL_SELECT_MASK = ' '
* IMPORTING
* FILELENGTH =
tables
data_tab = I_TAB
EXCEPTIONS
FILE_WRITE_ERROR = 1
NO_BATCH = 2
GUI_REFUSE_FILETRANSFER = 3
INVALID_TYPE = 4
NO_AUTHORITY = 5
UNKNOWN_ERROR = 6
HEADER_NOT_ALLOWED = 7
SEPARATOR_NOT_ALLOWED = 8
FILESIZE_NOT_ALLOWED = 9
HEADER_TOO_LONG = 10
DP_ERROR_CREATE = 11
DP_ERROR_SEND = 12
DP_ERROR_WRITE = 13
UNKNOWN_DP_ERROR = 14
ACCESS_DENIED = 15
DP_OUT_OF_MEMORY = 16
DISK_FULL = 17
DP_TIMEOUT = 18
FILE_NOT_FOUND = 19
DATAPROVIDER_EXCEPTION = 20
CONTROL_FLUSH_ERROR = 21
OTHERS = 22
.

* SYST FIELDS ARE NOT SET BY THIS FUNCTION SO DISPLAY THE ERROR CODE *

IF sy-subrc <> 0.
v_subrc = sy-subrc.
MESSAGE e899 WITH 'File Open Error' v_subrc.
ENDIF.

DESCRIBE TABLE i_tab LINES v_recswritten.

MESSAGE i899 WITH v_recswritten 'Records Written from ZTEST'.

Sample ABAP Program to Download file to Presentation Server

2007-10-18T21:48:00.000+05:30

DATA: BEGIN OF I_VEND OCCURS 0,

NAME1 LIKE LFA1-NAME1,

LIFNR LIKE MSEG-LIFNR,

MATKL LIKE MARA-MATKL,

MATNR LIKE MSEG-MATNR,

MAKTX LIKE MAKT-MAKTX,

WERKS LIKE MSEG-WERKS,

SOBKZ LIKE MSEG-SOBKZ,

MENGE LIKE MSEG-MENGE,

MEINS LIKE MSEG-MEINS,

DMBTR LIKE MSEG-DMBTR,

COUNT TYPE I,

END OF I_VEND.

DATA: BEGIN OF FIELDNAMES OCCURS 1,

NAME(60),

END OF FIELDNAMES.

" CHECK_UNITS

*&---------------------------------------------------------------------*

*& Form DOWNLOAD_VENDOR

*&---------------------------------------------------------------------*

FORM DOWNLOAD_VENDOR.

PERFORM VEND_FIELDNAMES.

CALL FUNCTION 'WS_DOWNLOAD'

EXPORTING

* BIN_FILESIZE = ' '

* CODEPAGE = ' '

FILENAME = FILENAME

FILETYPE = 'DAT'

* MODE = ' '

* WK1_N_FORMAT = ' '

* WK1_N_SIZE = ' '

* WK1_T_FORMAT = ' '

* WK1_T_SIZE = ' '

* COL_SELECT = ' '

* COL_SELECTMASK = ' '

* importing

* filelength =

TABLES

DATA_TAB = I_VEND

FIELDNAMES = FIELDNAMES

EXCEPTIONS

FILE_OPEN_ERROR = 1

FILE_WRITE_ERROR = 2

INVALID_FILESIZE = 3

INVALID_TABLE_WIDTH = 4

INVALID_TYPE = 5

NO_BATCH = 6

UNKNOWN_ERROR = 7

OTHERS = 8.

IF SY-SUBRC NE 0.

MESSAGE I004(YM) WITH FILENAME SY-SUBRC.

ENDIF.

ENDFORM. " DOWNLOAD_VENDOR

*&---------------------------------------------------------------------*

*& Form FIELDNAMES

*&---------------------------------------------------------------------*

FORM VEND_FIELDNAMES.

FIELDNAMES-NAME = 'Vendor name'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'Vendor No'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'Mat. Group'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'Material No'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'Material Desc.'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'Plant'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'SSI'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'Total Qty'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'UOM'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'Total value received'.

APPEND FIELDNAMES.

FIELDNAMES-NAME = 'Number'.

APPEND FIELDNAMES.

ENDFORM.

*

Sample ABAP Program to display pop message to avoid abort

2007-10-18T21:05:00.000+05:30

form output_message using p_mess.

* use popup instead of message so selection screen
* is saved
if sy-batch = space.
CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
exporting
textline1 = p_mess.

else.
MESSAGE E899(bd) WITH p_mess.
endif.
endform. " output_message

Sample ABAP Program of Dialogue Module Pool

2007-10-18T21:04:00.000+05:30

PROGRAM YLWMM005 MESSAGE-ID YL.
*-----------------------------------------------------------------------
* maintain additional fields on table t336 - difference indicators
* written by sheila titchener
*-----------------------------------------------------------------------
TABLES: T336, " Difference indicators
T300T, " Warehouse description
T336T. " Difference indicator text

DATA: OK_CODE(4),
OK_CODE2(4),
W_ERR_FLAG.
DATA: BEGIN OF XT336 OCCURS 1,
X LIKE T336,
DTEXT LIKE T336T-DTEXT,
END OF XT336.
DATA C LIKE SY-INDEX.
*&---------------------------------------------------------------------*
*& Module USER_COMMAND_0100 INPUT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
MODULE USER_COMMAND_0100 INPUT.
* Warehouse must not be space.
CHECK T336-LGNUM NE ' '.

CASE OK_CODE.
WHEN 'SAVE'.
PERFORM SAVE_T336.
WHEN 'DISP'.
PERFORM DISPLAY_T336.
WHEN 'LIST'.
C = 0.
PERFORM LIST_T336.
WHEN OTHERS.
PERFORM DISPLAY_T336.
ENDCASE.
CLEAR OK_CODE.
ENDMODULE. " USER_COMMAND_0100 INPUT
*&---------------------------------------------------------------------*
*& Module STATUS_0100 OUTPUT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'AMEND'.
SET TITLEBAR '100'.
ENDMODULE. " STATUS_0100 OUTPUT
*&---------------------------------------------------------------------*
*& Form SAVE_T336
*&---------------------------------------------------------------------*
* Save screen details
*&---------------------------------------------------------------------*
FORM SAVE_T336.
* reread record to make sure key is for last record read
* but store new value of ZZNOTO first
DATA: W_ZZNOTO LIKE T336-ZZNOTO.
W_ZZNOTO = T336-ZZNOTO.
SELECT SINGLE * FROM T336
WHERE LGNUM = T336-LGNUM
AND KZDIF = T336-KZDIF .
IF SY-SUBRC = 0.
T336-ZZNOTO = W_ZZNOTO.
UPDATE T336.
MESSAGE I018 WITH 'T336'.
COMMIT WORK.
ELSE.
MESSAGE I029 WITH T336-LGNUM T336-KZDIF.
W_ERR_FLAG = 'Y'.
ENDIF.
*
CLEAR OK_CODE.
ENDFORM.
*&---------------------------------------------------------------------*
*& Form DISPLAY_LOC
*&---------------------------------------------------------------------*
*----------------------------------------------------------------------*
FORM DISPLAY_T336.
W_ERR_FLAG = 'N'.
*
SELECT SINGLE * FROM T336
WHERE LGNUM = T336-LGNUM
AND KZDIF = T336-KZDIF.
IF SY-SUBRC NE 0.
MESSAGE I065.
W_ERR_FLAG = 'Y'.
ENDIF.
CLEAR T300T-LNUMT.
SELECT SINGLE * FROM T300T
WHERE SPRAS = SY-LANGU
AND LGNUM = T336-LGNUM.

SELECT SINGLE * FROM T336T
WHERE SPRAS = SY-LANGU
AND LGNUM = T336-LGNUM
AND KZDIF = T336-KZDIF.

* Abort if no warehouse
CHECK W_ERR_FLAG = 'N'.
*

ENDFORM.
*&---------------------------------------------------------------------*
*& Module EXIT_COMMAND INPUT
*&---------------------------------------------------------------------*
* exit commands are processed before validation *
*----------------------------------------------------------------------*
MODULE EXIT_COMMAND INPUT.

CASE OK_CODE.
WHEN 'EXIT'. CLEAR OK_CODE. SET SCREEN 0. LEAVE SCREEN.
WHEN 'CANC'. CLEAR OK_CODE. SET SCREEN 0. LEAVE SCREEN.
WHEN 'BACK'. CLEAR OK_CODE. SET SCREEN 0. LEAVE SCREEN.
ENDCASE.
ENDMODULE. " EXIT_COMMAND INPUT
*&---------------------------------------------------------------------*
*& Form READ_T336
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM LIST_T336.
DATA: T336-DTEXT_ST LIKE T336T-DTEXT.

T336-DTEXT_ST = T336T-DTEXT.
SELECT * FROM T336 INTO TABLE XT336
WHERE LGNUM = T336-LGNUM.

LOOP AT XT336.

SELECT SINGLE * FROM T336T
WHERE SPRAS = 'E'
AND LGNUM = T336-LGNUM
AND KZDIF = XT336-X-KZDIF.
XT336-DTEXT = T336T-DTEXT.
MODIFY XT336.
ENDLOOP.
T336T-DTEXT = T336-DTEXT_ST.
CLEAR OK_CODE. SET SCREEN 200. LEAVE SCREEN.

ENDFORM. " LIST_T336
*&---------------------------------------------------------------------*
*& Module EXIT_COMMAND_200 INPUT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
MODULE EXIT_COMMAND_200 INPUT.

CASE OK_CODE2.
WHEN 'EXIT'. CLEAR OK_CODE2. SET SCREEN 0. LEAVE SCREEN.
WHEN 'CANC'. CLEAR OK_CODE2. SET SCREEN 0. LEAVE SCREEN.
WHEN 'BACK'. CLEAR OK_CODE2. SET SCREEN 100. LEAVE SCREEN.
ENDCASE.
ENDMODULE. " EXIT_COMMAND_200 INPUT
*&---------------------------------------------------------------------*
*& Module STATUS_0200 OUTPUT
*&---------------------------------------------------------------------*
* text *
*----------------------------------------------------------------------*
MODULE STATUS_0200 OUTPUT.
SET PF-STATUS 'POPUP'.
* SET TITLEBAR 'xxx'.
IF T300T-LGNUM NE T336-LGNUM.

SELECT SINGLE * FROM T300T
WHERE SPRAS = SY-LANGU
AND LGNUM = T336-LGNUM .
ENDIF.
ENDMODULE. " STATUS_0200 OUTPUT

Sample ABAP Program to DIALOGUE FLOW LOGIC

2007-10-18T21:02:00.000+05:30

PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
*
PROCESS AFTER INPUT.
MODULE EXIT_COMMAND AT EXIT-COMMAND.
* Data is not in the screen fields until after the field stateme
CHAIN.
FIELD:
S_TANUM,
S_TAPOS MODULE VAL_TANUM.
ENDCHAIN.
* chain ensures all fields are open after an error

CHAIN.
FIELD: S_ZZTRACKING,
S_EXIDV,
S_TANUM,
S_TAPOS MODULE VAL_ZZTRACKING.
ENDCHAIN.
* process data entered
MODULE USER_COMMAND_0100.

Sample ABAP Program to Delete a file from the application server

2007-10-18T21:00:00.000+05:30

REPORT ZDELETE.
*----------------------------------------------------------------------*
* Delete a file on the application server.
*----------------------------------------------------------------------*
PARAMETERS: P_DIR LIKE RLGRAP-FILENAME
DEFAULT '/usr/sap/trans/',
P_FILE1 LIKE RLGRAP-FILENAME.

DATA: P_FILE(128).
DATA: W_ANS.

START-OF-SELECTION.
CONCATENATE P_DIR P_FILE1 INTO P_FILE.
*----------------------------------------------------------------------*
* check file exists
*----------------------------------------------------------------------*
OPEN DATASET P_FILE FOR INPUT.
IF SY-SUBRC NE 0.
MESSAGE E899(BD) WITH P_FILE 'does not exist'.
EXIT.
ELSE.

CALL FUNCTION 'POPUP_CONTINUE_YES_NO'
EXPORTING
DEFAULTOPTION = 'N'
TEXTLINE1 = P_DIR
TEXTLINE2 = P_FILE1
TITEL = 'ARE YOU SURE YOU WANT TO DELETE'
* START_COLUMN = 25
* START_ROW = 6
IMPORTING
ANSWER = W_ANS
EXCEPTIONS
OTHERS = 1.

ENDIF.
CLOSE DATASET P_FILE.
CHECK W_ANS = 'J'.
*----------------------------------------------------------------------*
* delete
*----------------------------------------------------------------------*

DELETE DATASET P_FILE.

IF SY-SUBRC NE 0.
MESSAGE E899(BD) WITH 'Invalid file name' P_FILE.
ELSE.
CLOSE DATASET P_FILE.
MESSAGE I899(BD) WITH P_DIR P_FILE1 'DELETED'.
ENDIF.

Sample ABAP Program to Compare to Unix or PC files and print differences

2007-10-18T20:59:00.000+05:30

REPORT Ycompare MESSAGE-ID Z1
NO STANDARD PAGE HEADING
* LINE-COUNT 65
LINE-SIZE 255.

*---------------------------------------------------------------------*
* Topic: Compare 2 unix or pc files and print the differences*
* *
* Author: Sheila Titchener
* *
*---------------------------------------------------------------------*
DATA: BEGIN OF TAB1 OCCURS 0,
LINE(5000),
END OF TAB1.

DATA: BEGIN OF TAB2 OCCURS 0,
LINE(5000),
END OF TAB2.
DATA: PARCOM_LOC(100) TYPE C.
DATA: COLOR TYPE I.
DATA: COUNT(16) TYPE C.

*-------------------------------------------------------------------*
* Parameters. *
*-------------------------------------------------------------------*
SELECTION-SCREEN SKIP 2.
PARAMETERS: PARCOM1(45) TYPE C LOWER CASE,
PARCOM2(45) TYPE C LOWER CASE,
PARCOM3 LIKE RLGRAP-FILENAME,
PARCOM4 LIKE RLGRAP-FILENAME ,
P_PC RADIOBUTTON GROUP ONE,
P_UNIX RADIOBUTTON GROUP ONE.
*-------------------------------------------------------------------*
* Parameter validation *
*-------------------------------------------------------------------*

*-------------------------------------------------------------------*
* TOP-OF-PAGE. *
*-------------------------------------------------------------------*
TOP-OF-PAGE.
PERFORM WRITE_PAGE_HEADING.

*-------------------------------------------------------------------*
* INITIALIZATION. *
*-------------------------------------------------------------------*
INITIALIZATION.
PARCOM1 = '/usr/sap/trans/* '.
PARCOM2 = '/usr/sap/trans/* '.
PARCOM3 = 'C:\TEMP\'.
PARCOM4 = 'C:\TEMP\'.

*-------------------------------------------------------------------*
* START-OF-SELECTION. *
*-------------------------------------------------------------------*
START-OF-SELECTION.
IF P_UNIX = 'X'.
PERFORM COLLECT_DATA.
ELSE.
PERFORM COLLECT_PC_DATA.
ENDIF.
PERFORM WRITE_FILE_CONTENT.
* perform write_number_of_content.

*---------------------------------------------------------------------*
* FORM COLLECT_DATA. *
*---------------------------------------------------------------------*
FORM COLLECT_DATA.
OPEN DATASET PARCOM1 FOR INPUT IN TEXT MODE.
DO.
READ DATASET PARCOM1 INTO TAB1.
IF SY-SUBRC NE 0.
EXIT.
ENDIF.
APPEND TAB1.
ENDDO.
CLOSE DATASET PARCOM1.

OPEN DATASET PARCOM2 FOR INPUT IN TEXT MODE.
DO.
READ DATASET PARCOM2 INTO TAB2.
IF SY-SUBRC NE 0.
EXIT.
ENDIF.
APPEND TAB2.
ENDDO.
CLOSE DATASET PARCOM2.
ENDFORM.

*-------------------------------------------------------------------*
* FORM WRITE_FILE_CONTENT. *
*-------------------------------------------------------------------*
FORM WRITE_FILE_CONTENT.

LOOP AT TAB1.
READ TABLE TAB2 INDEX SY-TABIX.
IF TAB1(7) = 'Element'.
WRITE: / TAB1.
ENDIF.
IF TAB1 NE TAB2 .
WRITE: / SY-TABIX NO-GAP, TAB1.
WRITE: / TAB2.
WRITE:/1(80) SY-ULINE.

ENDIF.
ENDLOOP.
ENDFORM.

*-------------------------------------------------------------------*
* FORM WRITE_PAGE_HEADING. *
*-------------------------------------------------------------------*
FORM WRITE_PAGE_HEADING.

WRITE:/1(80) SY-ULINE.
PERFORM STREGER_2.
FORMAT INTENSIFIED.
WRITE: /2(79) SPACE COLOR 1.
WRITE: 2 SY-DATUM COLOR 1.
IF P_UNIX = 'x'.
WRITE: / PARCOM1 COLOR 1.
WRITE: 45 PARCOM2 COLOR 1.
ELSE.
WRITE: / PARCOM3 COLOR 1.
WRITE: 45 PARCOM4 COLOR 1.
ENDIF.
PERFORM STREGER_2.
WRITE:/1(80) SY-ULINE.
PERFORM STREGER_2.
FORMAT INTENSIFIED.
WRITE: /2(79) SPACE COLOR 3.
WRITE: 2 'Offset' COLOR 3,
10 '0....+....1....+....2....+....3....+....' COLOR 3,
50 '4....+....5....+....6....+....' COLOR 3.
PERFORM STREGER_3.
FORMAT RESET.
WRITE:/1(80) SY-ULINE.
ENDFORM.

*-------------------------------------------------------------------*
* FORM STREGER_2. *
*-------------------------------------------------------------------*
FORM STREGER_2.
PERFORM WRITE_VLINE USING ' ' 1.
PERFORM WRITE_VLINE USING ' ' 80.
ENDFORM.

*-------------------------------------------------------------------*
* FORM STREGER_3. *
*-------------------------------------------------------------------*
FORM STREGER_3.
PERFORM WRITE_VLINE USING ' ' 1.
PERFORM WRITE_VLINE USING ' ' 9.
PERFORM WRITE_VLINE USING ' ' 80.
ENDFORM.

*-------------------------------------------------------------------*
* WRITE_VLINE. *
*-------------------------------------------------------------------*
FORM WRITE_VLINE USING MODE POS.
IF MODE NE 'T'.
FORMAT INTENSIFIED.
ENDIF.
POSITION POS.
WRITE: SY-VLINE.
IF MODE NE 'T'.
FORMAT RESET.
ENDIF.
ENDFORM.

*-------------------------------------------------------------------*
* FORM COLORLINE. *
*-------------------------------------------------------------------*
FORM COLORLINE USING TEXT1 TEXT2.
ON CHANGE OF SY-TABIX.
COLOR = COLOR + 1.
COLOR = COLOR MOD 2.
ENDON.
FORMAT RESET.
IF COLOR = 1.
WRITE: /2(79) SPACE COLOR 2.
IF TEXT1 = ' 0'.
WRITE: 3 TEXT1 COLOR 2, 11 TEXT2 COLOR 2.
ELSE.
WRITE: 3 TEXT1 COLOR 2, 10 TEXT2 COLOR 2.
ENDIF.
ELSE.
WRITE: /2(79) SPACE COLOR 4.
IF TEXT1 = ' 0'.
WRITE: 3 TEXT1 COLOR 4, 11 TEXT2 COLOR 4.
ELSE.
WRITE: 3 TEXT1 COLOR 4, 10 TEXT2 COLOR 4.
ENDIF.
ENDIF.
ENDFORM.

*-------------------------------------------------------------------*
* FORM WRITE_NUMBER_OF_CONTENT. *
*-------------------------------------------------------------------*
FORM WRITE_NUMBER_OF_CONTENT.
DESCRIBE TABLE TAB1 LINES COUNT.

FORMAT RESET. CONDENSE COUNT.
RESERVE 3 LINES.
WRITE:/1(80) SY-ULINE.
WRITE: /2(79) SPACE COLOR 2.
WRITE: 2 'Number of records in file:' COLOR 2,
29 COUNT COLOR 2.
PERFORM STREGER_2.
WRITE:/1(80) SY-ULINE.
ENDFORM.
*&---------------------------------------------------------------------*
*& Form COLLECT_PC_DATA
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM COLLECT_PC_DATA.

CALL FUNCTION 'WS_UPLOAD'
EXPORTING
* CODEPAGE = ' '
FILENAME = PARCOM3
* FILETYPE = ' '
* HEADLEN = ' '
* LINE_EXIT = ' '
* TRUNCLEN = ' '
* USER_FORM = ' '
* USER_PROG = ' '
* IMPORTING
* FILELENGTH =
TABLES
DATA_TAB = TAB1
EXCEPTIONS
CONVERSION_ERROR = 1
FILE_OPEN_ERROR = 2
FILE_READ_ERROR = 3
INVALID_TABLE_WIDTH = 4
INVALID_TYPE = 5
NO_BATCH = 6
UNKNOWN_ERROR = 7
OTHERS = 8.

CALL FUNCTION 'WS_UPLOAD'
EXPORTING
* CODEPAGE = ' '
FILENAME = PARCOM4
* FILETYPE = ' '
* HEADLEN = ' '
* LINE_EXIT = ' '
* TRUNCLEN = ' '
* USER_FORM = ' '
* USER_PROG = ' '
* IMPORTING
* FILELENGTH =
TABLES
DATA_TAB = TAB2
EXCEPTIONS
CONVERSION_ERROR = 1
FILE_OPEN_ERROR = 2
FILE_READ_ERROR = 3
INVALID_TABLE_WIDTH = 4
INVALID_TYPE = 5
NO_BATCH = 6
UNKNOWN_ERROR = 7
OTHERS = 8.
ENDFORM. " COLLECT_PC_DATA

Sample ABAP Program to Colour cells in ALV

2007-10-18T20:58:00.000+05:30

DATA: g_color_green TYPE slis_t_specialcol_alv.

* create a table of fieldnames to be coloured intensified green -

PERFORM colour_cells TABLES g_color_green
USING 21 31 5.

|
|
* set cells of this line to intensified green
IF CONDITION.....
out-color[] = g_color_green[].
ENDIF.

*---------------------------------------------------------------------*
* FORM E05_LAYOUT_BUILD *
*---------------------------------------------------------------------*
* ALV Layout options *
*---------------------------------------------------------------------*
* <-> E05_LS_LAYOUT *
*---------------------------------------------------------------------*
FORM e05_layout_build USING e05_ls_layout TYPE slis_layout_alv.
* Setting this flag avoids having to define field sizes.
e05_ls_layout-colwidth_optimize = 'X'.

* FIELD COLOR contains table of FIELDNAME and COLOURS.
e05_ls_layout-coltab_fieldname = 'COLOR'.
ENDFORM.

*&---------------------------------------------------------------------*
*& Form colour_cells
*&---------------------------------------------------------------------*
* Set up table to color field groups different from default colour
*----------------------------------------------------------------------*
* <--> t_color table of fields and colours
* <-- p_index_from - first field of catalogue to be coloured
* <-- p_index_to - last field of catalogue to be coloured
* <-- p_color - color number
*----------------------------------------------------------------------*
FORM colour_cells TABLES t_color
USING p_index_from TYPE sy-index
p_index_to TYPE sy-index
p_color TYPE i.

DATA: ls_fieldcat TYPE slis_fieldcat_alv,
w_tab TYPE slis_specialcol_alv.

* use field catalogue to build new table for consecutive fields
LOOP AT gt_fieldcat INTO ls_fieldcat FROM p_index_from TO p_index_to.
w_tab-fieldname = ls_fieldcat-fieldname.
w_tab-color-col = p_color.
IF p_color = 5. "green
w_tab-color-int = 1. "intensified on
ELSE.
w_tab-color-int = 0. "intensified off
ENDIF.
APPEND w_tab TO t_color.

ENDLOOP.
ENDFORM. " colour_cells

Sample ABAP Program to Calculate difference between date/times in hours

2007-10-18T20:56:00.000+05:30

DATA: l_start TYPE t,
l_end TYPE t,
l_startdate TYPE d,
l_enddate TYPE d,
l_hours TYPE p DECIMALS 2.

l_start = p_starttime.
l_end = p_endtime.
l_startdate = p_startdate.
l_enddate = p_enddate.

l_hours = ( ( l_enddate - l_startdate ) * 24
+ ( l_end - l_start ) / 3600 ).

Sample ABAP Program of BW User Exit

2007-10-18T20:54:00.000+05:30

CMOD Enhancement - RSAP0001

Add new fields to Extract structure.

Run RSA6 to 'unhide' new fields.

FUNCTION EXIT_SAPLRSAP_001.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_DATASOURCE) TYPE RSAOT_OLTPSOURCE
*" VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE
*" VALUE(I_UPDMODE) TYPE SBIWA_S_INTERFACE-UPDMODE
*" TABLES
*" I_T_SELECT TYPE SBIWA_T_SELECT
*" I_T_FIELDS TYPE SBIWA_T_FIELDS
*" C_T_DATA
*" C_T_MESSAGES STRUCTURE BALMI OPTIONAL
*" EXCEPTIONS
*" RSAP_CUSTOMER_EXIT_ERROR
*"----------------------------------------------------------------------

INCLUDE ZXRSAU01.

ENDFUNCTION.
*&---------------------------------------------------------------------*
*& Include ZXRSAU01 *
*&---------------------------------------------------------------------*
* Written by Sheila Titchener - www.iconet-ltd.co.uk - Oct 2005
*&---------------------------------------------------------------------*

DATA: l_s_mc13vd0itm LIKE mc13vd0itm, " extract structure
l_tabix LIKE sy-tabix,
l_knumv TYPE knumv.

data: t_konv type table of konv.
data: w_konv type konv.

CASE i_datasource.
*/ in bw 1.2b case i_isource.

WHEN '2LIS_13_VDITM'.
LOOP AT c_t_data INTO l_s_mc13vd0itm.
l_tabix = sy-tabix.
SELECT SINGLE knumv FROM vbrk
INTO l_knumv
WHERE vbeln = l_s_mc13vd0itm-vbeln.
IF sy-subrc = 0.
SELECT * FROM konv INTO TABLE t_konv
WHERE knumv = L_knumv
AND kposn = l_s_mc13vd0itm-posnr.

LOOP AT t_konv INTO w_konv.

CASE w_konv-kschl.
WHEN 'PR00'.
l_s_mc13vd0itm-kschl1 = w_konv-kschl.
l_s_mc13vd0itm-kwert1 = w_konv-kwert.
WHEN 'ZELE'.
l_s_mc13vd0itm-kschl2 = w_konv-kschl.
l_s_mc13vd0itm-kwert2 = w_konv-kwert.
WHEN 'SKTV'.
l_s_mc13vd0itm-kschl3 = w_konv-kschl.
l_s_mc13vd0itm-kwert3 = w_konv-kwert.
WHEN 'VPRS'.
l_s_mc13vd0itm-kschl4 = w_konv-kschl.
l_s_mc13vd0itm-kwert4 = w_konv-kwert.
WHEN 'ZCST'.
l_s_mc13vd0itm-kschl5 = w_konv-kschl.
l_s_mc13vd0itm-kwert5 = w_konv-kwert.
WHEN 'ZSUR'.
l_s_mc13vd0itm-kschl6 = w_konv-kschl.
l_s_mc13vd0itm-kwert6 = w_konv-kwert.
WHEN 'ZSTD'.
l_s_mc13vd0itm-kschl7 = w_konv-kschl.
l_s_mc13vd0itm-kwert7 = w_konv-kwert.
ENDCASE.

ENDLOOP.
ENDIF.
Modify c_t_data from l_s_mc13vd0itm index l_tabix.
ENDLOOP.
WHEN OTHERS.
EXIT.

ENDCASE.

Sample ABAP Program of ALV Grid control using OO methods

2007-10-18T20:53:00.000+05:30

*&---------------------------------------------------------------------*
*& Report Z_ALV_SKELETON
*&
*& Author: Sheila Titchener
*& Date: December 2006
*&---------------------------------------------------------------------*
*& ALV Grid control skeleton using OO Methods
*&
*&---------------------------------------------------------------------*
REPORT Z_ALV_SKELETON .
*&---------------------------------------------------------------------*
*&---------------------------------------------------------------------*
* internal tables
DATA: i_tab TYPE TABLE OF zchangereq,
w_tab TYPE zchangereq.
* display field details
DATA: w_field_cat_wa TYPE lvc_s_fcat. " Field Catalog work area
*
*&---------------------------------------------------------------------*
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-020.
*&---------------------------------------------------------------------*
PARAMETERS: p_outs RADIOBUTTON GROUP g1,
p_comp RADIOBUTTON GROUP g1.
SELECTION-SCREEN END OF BLOCK b1.
*&---------------------------------------------------------------------*
*MACROS
*&---------------------------------------------------------------------*
DEFINE add_field.
* &1 = FIELDNAME &2 = HEADING &3 = Key field flag
clear w_field_cat_wa.
w_field_cat_wa-fieldname = &1.
* lw_field_cat_wa-ref_table = p_ref_table.
* lw_field_cat_wa-inttype = p_inttype.
* lw_field_cat_wa-decimals = p_decimals.
* lw_field_cat_wa-coltext = p_coltext.
* lw_field_cat_wa-seltext = p_seltext.
* lw_field_cat_wa-do_sum = p_do_sum.
* lw_field_cat_wa-no_out = p_no_out.
* lw_field_cat_wa-col_pos = p_col_pos.
* lw_field_cat_wa-reptext = p_coltext.
* lw_field_cat_wa-colddictxt = p_colddictxt.
w_field_cat_wa-scrtext_m = &2.
w_field_cat_wa-key = &3.
append w_field_cat_wa to i_field_cat.
END-OF-DEFINITION.
*-----------------------------------------------------------------------
* ALV specific Declarations...........................................
*-----------------------------------------------------------------------
* ALV specific Internal table declarations.............................
DATA: i_field_cat TYPE lvc_t_fcat, " Field catalogue
i_alv_sort TYPE lvc_t_sort. " Sort table

* ALV variables........................................................
DATA: w_alv_layout TYPE lvc_s_layo, " ALV Layout
w_alv_save TYPE c, " ALV save
w_alv_variant TYPE disvariant. " ALV Variant

* ALV Class definitions................................................
*-----------------------------------------------------------------------
CLASS lcl_event_handler DEFINITION.
*-----------------------------------------------------------------------

PUBLIC SECTION.
METHODS: handle_double_click
FOR EVENT double_click OF cl_gui_alv_grid
IMPORTING e_row e_column.
METHODS: handle_hotspot
FOR EVENT hotspot_click OF cl_gui_alv_grid
IMPORTING e_row_id e_column_id.
ENDCLASS. " CLASS LCL_EVENT_HANDLER DEF..

* ALV Class implementation............................................
* In the Event of a Double Click drill down to the corresponding CHANGE REQUEST
*-----------------------------------------------------------------------
CLASS lcl_event_handler IMPLEMENTATION.
*-----------------------------------------------------------------------

METHOD handle_double_click.
DATA: l_tab LIKE LINE OF i_tab.
CHECK e_row-rowtype(1) EQ space.
READ TABLE i_tab INDEX e_row-index INTO l_tab.
SET PARAMETER ID 'ZTY' FIELD l_tab-ztype.
SET PARAMETER ID 'ZCR' FIELD l_tab-zcref.
CALL TRANSACTION 'ZCRT' AND SKIP FIRST SCREEN.
ENDMETHOD. " HANDLE_DOUBLE_CLICK

* not working yet - hotspot seems to stay in the gui!!
METHOD handle_hotspot.
DATA: l_tab LIKE LINE OF i_tab.
CHECK e_row_id-rowtype(1) EQ space.
READ TABLE i_tab INDEX e_row_id-index INTO l_tab.
SET PARAMETER ID 'ZTY' FIELD l_tab-ztype.
SET PARAMETER ID 'ZCR' FIELD l_tab-zcref.
CALL TRANSACTION 'ZCRT' AND SKIP FIRST SCREEN.
ENDMETHOD. " HANDLE_DOUBLE_CLICK

ENDCLASS. " CLASS LCL_EVENT_HANDLER IMPL...

* ALV Grid Control definitions........................................
DATA:
* ALV Grid Control itself
o_grid TYPE REF TO cl_gui_alv_grid,

* Container to hold the ALV Grid Control
o_custom_container TYPE REF TO cl_gui_custom_container,

* Event handler (defined in the class above)
o_event_handler TYPE REF TO lcl_event_handler.

*&----------------------------------------------------------------------*
INITIALIZATION.
*&----------------------------------------------------------------------*
PERFORM create_field_catalogue. " Create ALV Field Catalog

*&---------------------------------------------------------------------*
START-OF-SELECTION.
*&---------------------------------------------------------------------*
* Outstanding requests
IF p_outs = 'X'.
SELECT * FROM zchangereq
INTO TABLE i_tab
WHERE zstatus < 99.
ELSE.
* completed requests
SELECT * FROM zchangereq
INTO TABLE i_tab
WHERE zstatus = 99.
ENDIF.
*&---------------------------------------------------------------------*
END-OF-SELECTION.
*&---------------------------------------------------------------------*
PERFORM list_output_to_alv. " Perform ALV Output operations
*----------------------------------------------------------------------*
* FORM LIST_OUTPUT_TO_ALV *
*----------------------------------------------------------------------*
* This subroutine is used to call the screen for ALV Output. *
*----------------------------------------------------------------------*
* There are no interface parameters to be passed to this subroutine. *
*----------------------------------------------------------------------*
FORM list_output_to_alv.

CALL SCREEN 100.

*
ENDFORM. " LIST_OUTPUT_TO_ALV
*----------------------------------------------------------------------*
* Module STATUS_0100 OUTPUT *
*----------------------------------------------------------------------*
* This is the PBO module which will be processed befor displaying the *
* ALV Output. *
*----------------------------------------------------------------------*
MODULE status_0100 OUTPUT.

SET PF-STATUS '0100'. " PF Status for ALV Output Screen
IF p_outs = 'X'.
SET TITLEBAR 'STD'.
ELSE.
* completed requests
SET TITLEBAR 'COMP'.
ENDIF.

CREATE OBJECT: o_custom_container
EXPORTING container_name = 'SC_GRID',
o_grid
EXPORTING i_parent = o_custom_container.

PERFORM define_alv_layout. " ALV Layout options definitions

PERFORM save_alv_layout_options. " save ALV layout options

PERFORM call_alv_grid. " Call ALV Grid Control

ENDMODULE. " STATUS_0100 OUTPUT

*----------------------------------------------------------------------*
* Module USER_COMMAND_0100 INPUT *
*----------------------------------------------------------------------*
* This is the PAI module which will be processed when the user performs*
* any operation from the ALV output. *
*----------------------------------------------------------------------*

MODULE user_command_0100 INPUT.

CASE sy-ucomm.
WHEN 'EXIT' OR 'BACK' OR 'CANC'.
* may need to do this so display is refreshed if other report selected
CALL METHOD o_custom_container->free.
SET SCREEN 0.
ENDCASE.

ENDMODULE. " USER_COMMAND_0100 INPUT

*----------------------------------------------------------------------*
* FORM DEFINE_ALV_LAYOUT *
*----------------------------------------------------------------------*
* This subroutine is used to Define the ALV layout. *
*----------------------------------------------------------------------*
FORM define_alv_layout .

w_alv_layout-numc_total = 'X'. " Numc total line
w_alv_layout-cwidth_opt = 'X'. " Optimal column width
w_alv_layout-detailinit = 'X'. " Show values that are initial in
" detail list.
w_alv_layout-sel_mode = 'A'. " Column selection mode
w_alv_layout-no_merging = 'X'. " No merging while sorting columns
w_alv_layout-keyhot = 'X'.
ENDFORM. " DEFINE_ALV_LAYOUT
*----------------------------------------------------------------------*
* FORM SAVE_ALV_LAYOUT_OPTIONS *
*----------------------------------------------------------------------*
* This subroutine is used to Save the ALV layout options. *
*----------------------------------------------------------------------*
FORM save_alv_layout_options.

* See the ALV grid control documentation for full list of options

w_alv_save = 'A'.
w_alv_variant-report = sy-repid.

ENDFORM. " SAVE_ALV_LAYOUT_OPTIONS
*----------------------------------------------------------------------*
* FORM CALL_ALV_GRID *
*----------------------------------------------------------------------*
* This subroutine is used to call ALV Grid control for processing. *
*----------------------------------------------------------------------*
FORM call_alv_grid.

CALL METHOD o_grid->set_table_for_first_display
EXPORTING
is_layout = w_alv_layout
i_save = w_alv_save
is_variant = w_alv_variant
CHANGING
it_outtab = i_tab[]
it_sort = i_alv_sort
it_fieldcatalog = i_field_cat.
* Link used Events and Event Handler Methods
CREATE OBJECT o_event_handler.

* Set handler o_event_handler->handle_top_of_page for o_grid.
SET HANDLER o_event_handler->handle_double_click FOR o_grid.

ENDFORM. " CALL_ALV_GRID
*&---------------------------------------------------------------------*
*& Form create_field_catalogue
*&---------------------------------------------------------------------*
* set up field catalogue
*&---------------------------------------------------------------------*
FORM create_field_catalogue .
* Fieldname Heading Key?
*eg add_field 'ZTYPE' 'Type' 'X'.

ENDFORM. " create_field_catalogue

Sample ABAP Program of ALV Grid

2007-10-18T20:48:00.000+05:30

REPORT zalvgrid NO STANDARD PAGE HEADING.
*&---------------------------------------------------------------------*
*& Written By : Sheila Titchener - www.iconet-ltd.co.uk
& Date : January 2006
*&
*&---------------------------------------------------------------------*
* Includes logo and white background - optimized field size
*&---------------------------------------------------------------------*
* ALV
TYPE-POOLS: slis.
*----------------
* extracted Notification date
TYPES: BEGIN OF ty_data,
qmnum TYPE qmnum,
qmdat TYPE qmdat,
mzeit TYPE mzeit,
erdat TYPE erdat,
erzeit TYPE erzeit,
ernam TYPE ernam,
END OF ty_data.

* ALV print table
TYPES: BEGIN OF ty_out,
qmnum TYPE qmnum,
qmdat TYPE qmdat,
mzeit TYPE mzeit,
erdat TYPE erdat,
erzeit TYPE erzeit,
ernam TYPE ernam,
END OF ty_out.
*----------------------------------------------------------------------*
DATA: viqmel TYPE viqmel.
*----------------------------------------------------------------------*
* Internal tables and their work areas
*----------------------------------------------------------------------*
DATA: w_data TYPE ty_data,
t_data TYPE TABLE OF ty_data.
DATA: w_out TYPE ty_out,
t_out TYPE TABLE OF ty_out.
*----------------------------------------------------------------------*
* Headings.
*----------------------------------------------------------------------*
DATA: BEGIN OF h1,
print_date(10),
sdate(10),
END OF h1.
*
*----------------------------------------------------------------------*
* Data for ALV
*----------------------------------------------------------------------*
INCLUDE .
INCLUDE .
*---------
CONSTANTS:
*---------
gc_formname_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE'.

DATA: gt_fieldcat TYPE slis_t_fieldcat_alv,
gs_layout TYPE slis_layout_alv,
gs_print TYPE slis_print_alv,
gt_sort TYPE slis_t_sortinfo_alv,
gt_sp_group TYPE slis_t_sp_group_alv,
gt_events TYPE slis_t_event.
*
DATA: g_repid LIKE sy-repid.
DATA: gt_list_top_of_page TYPE slis_t_listheader.

DATA: g_save(1) TYPE c.
*----------------------------------------------------------------------*
* Report Selections
*----------------------------------------------------------------------*
PARAMETERS: plant LIKE viqmel-iwerk VALUE CHECK OBLIGATORY
MEMORY ID wrk,
sorg LIKE vbak-vkorg OBLIGATORY MEMORY ID vko.

SELECTION-SCREEN SKIP 1.

SELECT-OPTIONS: wkcentre FOR viqmel-arbpl,
nottype FOR viqmel-qmart,
notnum FOR viqmel-qmnum,
crdate FOR viqmel-erdat NO-EXTENSION,
createby FOR viqmel-ernam.

*-------
* MACROS
*-------
* FIELD CATALOGUE ENTRY FOR Keyed FIELDS
DEFINE catfield.
*----------------
* 1= Fieldname, 2= Description, 3=Key
clear ls_fieldcat.
ls_fieldcat-fieldname = &1.
ls_fieldcat-key = &3.
ls_fieldcat-hotspot = &3.
* ls_fieldcat-key_sel = 'X'.
ls_fieldcat-tabname = 'T_OUT'.
* Output length will be optimised by ALV
* ls_fieldcat-outputlen = '6'.
ls_fieldcat-seltext_m = &2.
append ls_fieldcat to gt_fieldcat.
* color C or X 1-9 = color number 0/1 intensified 0/1 inverse
ls_fieldcat-emphasize = 'C100'.
END-OF-DEFINITION.
*----------------
* FIELD CATALOGUE ENTRY FOR SUMMED FIELDS
DEFINE catsum.
*----------------
* 1= Fieldname, 2= color, 3= Description,
clear ls_fieldcat.
ls_fieldcat-fieldname = &1.
ls_fieldcat-do_sum = 'X'.
ls_fieldcat-key_sel = 'X'.
ls_fieldcat-tabname = 'T_OUT'.
ls_fieldcat-emphasize = &2.
ls_fieldcat-seltext_m = &3.
append ls_fieldcat to gt_fieldcat.
END-OF-DEFINITION.
*---------------------------------------------------------------------*
INITIALIZATION.
*----------------------------------------------------------------------*
g_repid = sy-repid.
* set to-date as today
crdate-high = sy-datum.
crdate-option = 'EQ'.
crdate-sign = 'I'.
APPEND crdate TO crdate.

REFRESH gt_fieldcat.
PERFORM e01_fieldcat_init .
PERFORM e03_eventtab_build USING gt_events[].
PERFORM e06_t_sort_build USING gt_sort[].
*----------------------------------------------------------------------*
AT SELECTION-SCREEN ON plant.
*----------------------------------------------------------------------*

*----------------------------------------------------------------------*
START-OF-SELECTION.
*----------------------------------------------------------------------*
PERFORM e04_comment_build USING gt_list_top_of_page[].

PERFORM selection.

*----------------------------------------------------------------------*
END-OF-SELECTION.
*----------------------------------------------------------------------*
PERFORM e05_layout_build USING gs_layout. "wg. Parameters
* Call ABAP/4 List Viewer
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_background_id = 'WHITE'
i_callback_program = g_repid
i_callback_user_command = 'USER_COMMAND'
is_layout = gs_layout
it_fieldcat = gt_fieldcat[]
* i_save = 'A'
is_print = gs_print
it_events = gt_events[]
TABLES
t_outtab = t_out.
*---------------------------------------------------------------------*
* FORM E01_FIELDCAT_INIT *
*---------------------------------------------------------------------*
* ........ *
*---------------------------------------------------------------------*
* --> E01_LT_FIELDCAT *
*---------------------------------------------------------------------*
FORM e01_fieldcat_init.
DATA: ls_fieldcat TYPE slis_fieldcat_alv.
* BASIC FIELDS
catfield 'QMNUM' text-024 'X'.
catfield 'QMDAT' text-023 ' '.
catfield 'MZEIT' text-022 ' '.
catfield 'ERDAT' text-021 ' '.
catfield 'ERZEIT' text-020 ' '.
catfield 'ERNAM' text-019 ' '.

ENDFORM.
*---------------------------------------------------------------------*
* FORM E02_DATA_ADD *
*---------------------------------------------------------------------*
* ........ *
*---------------------------------------------------------------------*
* --> *
*---------------------------------------------------------------------*
FORM e02_data_add .

LOOP AT t_data INTO w_data.
MOVE-CORRESPONDING w_data TO w_out.
PERFORM get_disp_task.
PERFORM get_tsrl_status.
APPEND w_out TO t_out.
ENDLOOP.
ENDFORM.
*---------------------------------------------------------------------*
* FORM E03_EVENTTAB_BUILD *
*---------------------------------------------------------------------*
* Set up TOP-OF-PAGE event processing *
*---------------------------------------------------------------------*
* --> E03_LT_EVENTS *
*---------------------------------------------------------------------*
FORM e03_eventtab_build USING e03_lt_events TYPE slis_t_event.
DATA: ls_event TYPE slis_alv_event.
*
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
i_list_type = 0
IMPORTING
et_events = e03_lt_events.
READ TABLE e03_lt_events WITH KEY name = slis_ev_top_of_page
INTO ls_event.
IF sy-subrc = 0.
MOVE gc_formname_top_of_page TO ls_event-form.
APPEND ls_event TO e03_lt_events.
ENDIF.
ENDFORM.
*---------------------------------------------------------------------*
* FORM E04_COMMENT_BUILD *
*---------------------------------------------------------------------*
* Create Headings
*
*---------------------------------------------------------------------*
* --> E04_LT_TOP_OF_PAGE *
*---------------------------------------------------------------------*
FORM e04_comment_build USING e04_lt_top_of_page TYPE slis_t_listheader.
DATA: ls_line TYPE slis_listheader.
DATA: l_date(10).
*
* Title Typ H
CLEAR ls_line.
ls_line-typ = 'H'.
ls_line-info = sy-title.
APPEND ls_line TO e04_lt_top_of_page.

* head 1
CLEAR ls_line.
* Plant
ls_line-key = text-101.
ls_line-info = plant.
ls_line-typ = 'S'.
APPEND ls_line TO e04_lt_top_of_page.

* Sales Org
ls_line-key = text-102.
ls_line-info = sorg.
APPEND ls_line TO e04_lt_top_of_page.
* Maintenance Work Centre
IF NOT wkcentre[] IS INITIAL.
ls_line-key = text-105.
ls_line-info = wkcentre-low.
APPEND ls_line TO e04_lt_top_of_page.
ENDIF.
* Notification Type
IF NOT nottype[] IS INITIAL.
ls_line-key = text-106.
ls_line-info = nottype-low.
APPEND ls_line TO e04_lt_top_of_page.
ENDIF.
* Notification Number
IF NOT notnum[] IS INITIAL.
ls_line-key = text-107.
ls_line-info = notnum-low.
APPEND ls_line TO e04_lt_top_of_page.
ENDIF.
* Created From
ls_line-key = text-103.
WRITE crdate-low TO l_date DD/MM/YYYY.
ls_line-info = l_date.
APPEND ls_line TO e04_lt_top_of_page.
* Created to
ls_line-key = text-104.
WRITE crdate-high TO l_date DD/MM/YYYY.
ls_line-info = l_date.
APPEND ls_line TO e04_lt_top_of_page.

*

ENDFORM.
*---------------------------------------------------------------------*
* FORM E05_LAYOUT_BUILD *
*---------------------------------------------------------------------*
* ALV Layout options *
*---------------------------------------------------------------------*
* <-> E05_LS_LAYOUT *
*---------------------------------------------------------------------*
FORM e05_layout_build USING e05_ls_layout TYPE slis_layout_alv.
e05_ls_layout-zebra = 'X'.
e05_ls_layout-colwidth_optimize = 'X'.
* e05_ls_layout-lights_fieldname = 'LIGHTS'.
ENDFORM.
*---------------------------------------------------------------------*
* FORM E06_T_SORT_BUILD *
*---------------------------------------------------------------------*
* ........ *
*---------------------------------------------------------------------*
* --> E06_LT_SORT *
*---------------------------------------------------------------------*
FORM e06_t_sort_build USING e06_lt_sort TYPE slis_t_sortinfo_alv.
* DATA: ls_sort TYPE slis_sortinfo_alv.
ENDFORM.
*---------------------------------------------------------------------*
FORM user_command USING r_ucomm LIKE sy-ucomm
rs_selfield TYPE slis_selfield.
*---------------------------------------------------------------------*
* called by ALV list viewer
*-----------------------------------------------------------------------
CASE rs_selfield-sel_tab_field.
WHEN 'T_OUT-QMNUM'.
SET PARAMETER ID 'IQM' FIELD rs_selfield-value.
CALL TRANSACTION 'IW53' AND SKIP FIRST SCREEN.
ENDCASE.
ENDFORM.
*---------------------------------------------------------------------*
* FORM SELECTION *
*---------------------------------------------------------------------*
* Select data from CATSDB *
*---------------------------------------------------------------------*
FORM selection.

SELECT * FROM viqmel

INTO CORRESPONDING FIELDS OF TABLE t_data
WHERE iwerk = plant
AND vkorg = sorg
AND arbpl IN wkcentre
AND qmart IN nottype
AND qmnum IN notnum
AND erdat IN crdate
AND ernam IN createby.
*
PERFORM e02_data_add.
ENDFORM.
*---------------------------------------------------------------------*
* FORM TOP_OF_PAGE *
*---------------------------------------------------------------------*
* ........ *
*---------------------------------------------------------------------*
FORM top_of_page.
* create logo in transaction OAER - Business Documents
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
i_logo = 'LOGO'
it_list_commentary = gt_list_top_of_page.

ENDFORM.
*&---------------------------------------------------------------------*
*& Form get_disp_task
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM get_disp_task.

ENDFORM. " get_disp_task
*&---------------------------------------------------------------------*
*& Form get_tsrl_status
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM get_tsrl_status.

ENDFORM. " get_tsrl_status

Sample ABAP Program to Browse a file on the application server

2007-10-18T20:45:00.000+05:30

REPORT ZBROWSE MESSAGE-ID Z1
NO STANDARD PAGE HEADING
* LINE-COUNT 65
LINE-SIZE 255.

*---------------------------------------------------------------------*
* Topic: Browse a file on the appication server
* *
* Author: Sheila Titchener
* *
*---------------------------------------------------------------------*
DATA: BEGIN OF TAB1 OCCURS 0,
LINE(5000),
END OF TAB1.

DATA: BEGIN OF TAB2 OCCURS 0,
LINE(5000),
END OF TAB2.
DATA: PARCOM_LOC(100) TYPE C.
DATA: COLOR TYPE I.
DATA: COUNT(16) TYPE C.
DATA: MESS(50).
*-------------------------------------------------------------------*
* Parameters. *
*-------------------------------------------------------------------*
SELECTION-SCREEN SKIP 2.
PARAMETERS: PARCOM1(55) TYPE C LOWER CASE.
* parcom2(55) type c lower case,
* parcom3 like rlgrap-filename,
* parcom4 like rlgrap-filename ,
* p_pc radiobutton group one,
*8 p_unix radiobutton group one.
*-------------------------------------------------------------------*
* Parameter validation *
*-------------------------------------------------------------------*

*-------------------------------------------------------------------*
* TOP-OF-PAGE. *
*-------------------------------------------------------------------*
TOP-OF-PAGE.
PERFORM WRITE_PAGE_HEADING.

*-------------------------------------------------------------------*
* INITIALIZATION. *
*-------------------------------------------------------------------*
INITIALIZATION.
PARCOM1 = '\\sapdev1\export\'.

*-------------------------------------------------------------------*
* START-OF-SELECTION. *
*-------------------------------------------------------------------*
START-OF-SELECTION.
PERFORM COLLECT_DATA.
PERFORM WRITE_FILE_CONTENT.
*---------------------------------------------------------------------*
* FORM COLLECT_DATA. *
*---------------------------------------------------------------------*
FORM COLLECT_DATA.
OPEN DATASET PARCOM1 FOR INPUT IN TEXT MODE MESSAGE MESS.
IF SY-SUBRC NE 0.
WRITE: 'Unable to open', PARCOM1.
WRITE: / MESS.
ELSE.
DO.
READ DATASET PARCOM1 INTO TAB1.
IF SY-SUBRC NE 0.
EXIT.
ENDIF.
APPEND TAB1.
ENDDO.
CLOSE DATASET PARCOM1.
ENDIF.

ENDFORM.

*-------------------------------------------------------------------*
* FORM WRITE_FILE_CONTENT. *
*-------------------------------------------------------------------*
FORM WRITE_FILE_CONTENT.
DATA: E LIKE SY-FDPOS.
LOOP AT TAB1.
E = STRLEN( TAB1-LINE ).
IF E GE 0.
PERFORM COLORLINE USING ' 0' TAB1-LINE+0(99).
PERFORM STREGER_3.
ENDIF.

IF E GE 100.
PERFORM COLORLINE USING '100' TAB1-LINE+99(100).
PERFORM STREGER_3.
ENDIF.
* write: /10 tab1.
*
ENDLOOP.
ENDFORM.

*-------------------------------------------------------------------*
* FORM WRITE_PAGE_HEADING. *
*-------------------------------------------------------------------*
FORM WRITE_PAGE_HEADING.

WRITE:/1(110) SY-ULINE.
PERFORM STREGER_2.
FORMAT INTENSIFIED.
WRITE: / PARCOM1 COLOR 1.
PERFORM STREGER_2.
WRITE:/1(110) SY-ULINE.
PERFORM STREGER_2.
FORMAT INTENSIFIED.
WRITE: /2(109) SPACE COLOR 3.
WRITE: 2 'Offset' COLOR 3,
10 '0....+....1....+....2....+....3....+....' COLOR 3,
50 '4....+....5....+....6....+....7....+....' COLOR 3,
90 '8....+....9....+....' COLOR 3.
PERFORM STREGER_3.
FORMAT RESET.
WRITE:/1(110) SY-ULINE.
ENDFORM.

*-------------------------------------------------------------------*
* FORM STREGER_2. *
*-------------------------------------------------------------------*
FORM STREGER_2.
PERFORM WRITE_VLINE USING ' ' 1.
PERFORM WRITE_VLINE USING ' ' 80.
ENDFORM.

*-------------------------------------------------------------------*
* FORM STREGER_3. *
*-------------------------------------------------------------------*
FORM STREGER_3.
PERFORM WRITE_VLINE USING ' ' 1.
PERFORM WRITE_VLINE USING ' ' 9.
PERFORM WRITE_VLINE USING ' ' 110.
ENDFORM.

*-------------------------------------------------------------------*
* WRITE_VLINE. *
*-------------------------------------------------------------------*
FORM WRITE_VLINE USING MODE POS.
IF MODE NE 'T'.
FORMAT INTENSIFIED.
ENDIF.
POSITION POS.
WRITE: SY-VLINE.
IF MODE NE 'T'.
FORMAT RESET.
ENDIF.
ENDFORM.

*-------------------------------------------------------------------*
* FORM COLORLINE. *
*-------------------------------------------------------------------*
FORM COLORLINE USING TEXT1 TEXT2.
ON CHANGE OF SY-TABIX.
COLOR = COLOR + 1.
COLOR = COLOR MOD 2.
ENDON.
FORMAT RESET.
IF COLOR = 1.
WRITE: /2(79) SPACE COLOR 2.
IF TEXT1 = ' 0'.
WRITE: 3 TEXT1 COLOR 2, 11 TEXT2 COLOR 2.
ELSE.
WRITE: 3 TEXT1 COLOR 2, 10 TEXT2 COLOR 2.
ENDIF.
ELSE.
WRITE: /2(79) SPACE COLOR 4.
IF TEXT1 = ' 0'.
WRITE: 3 TEXT1 COLOR 4, 11 TEXT2 COLOR 4.
ELSE.
WRITE: 3 TEXT1 COLOR 4, 10 TEXT2 COLOR 4.
ENDIF.
ENDIF.
ENDFORM.

*-------------------------------------------------------------------*
* FORM WRITE_NUMBER_OF_CONTENT. *
*-------------------------------------------------------------------*
FORM WRITE_NUMBER_OF_CONTENT.
DESCRIBE TABLE TAB1 LINES COUNT.

FORMAT RESET. CONDENSE COUNT.
RESERVE 3 LINES.
WRITE:/1(80) SY-ULINE.
WRITE: /2(79) SPACE COLOR 2.
WRITE: 2 'Number of records in file:' COLOR 2,
29 COUNT COLOR 2.
PERFORM STREGER_2.
WRITE:/1(80) SY-ULINE.
ENDFORM.

Learn all Functions in ALV Grid or ALV report

2007-10-16T22:43:00.000+05:30

After a report has been generated, there are many options available for customizing the data within the ALV grid. The sections below give more information for using the available options.

Modifying Columns
There are many options for manually modifying columns, including resizing, moving, freezing, sorting, hiding, and calculating.

Resize Columns
To resize a column, place your cursor over the line between column headers. When it turns into a cross, click and drag the edge of the column.

Move Columns
To move a column, click the column header once to select it. Then click and drag the column header to a new location.

Freeze Columns
To freeze a column, right-click the column header and select Freeze to Column. The column will not move when you scroll. To unfreeze the column, right-click the column header and select Unfreeze Columns.

Sort Columns
To sort a column, select a column header then click the appropriate sort icon. The icon sorts a column in ascending order. The icon sorts a column in descending order.

Hide Columns
To hide a column, right-click the column header and select Hide.

Calculate Columns
If a column is totaled, the mean, minimum, or maximum value can be determined by following the menu path Edit > Calculate and then selecting the desired option. The calculated value replaces the total at the end of the report.

Navigating Subtotals
To expand or collapse the lines included in a single subtotal, click the expand or collapse icon next to the field being subtotaled. To expand or collapse all subtotals, click the expand/collapse icon in the lower lefthand corner of the total line. Expand or collapse individual subtotals Expand or collapse all subtotals

Change a Report Layout
While many individual modifications can be made to a report using icons and dragging columns, multiple modifications can be made at once using the change layout function. The Change Layout icon provides an interface for changing the column order and the sort order. It allows you to apply filters and display options to the report. Below are directions for each of these functions. After making changes, click (Transfer) to apply your changes.

Change Column Order
The Columns tab is used to select and order the columns you want to appear on your report. The names on the left indicate the columns included in the order they will appear. The names on the right are the available fields that can be added. Double-click on a column name to move it from one area to the other. To reorder the columns, select a column name and click the arrows at the top of the tab to move the column up or down a position.

Change Sort Order
The Sort Order tab is used to define the sort order and subtotaling by column. The names on the left indicate the columns to be sorted in the order they will be sorted. The names on the right are the available columns. Double-click on a column name to move it from one area to the other. To reorder the columns, select a column name and click the arrows at the top of the tab to move the column up or down a position. There are three fields to the left of each included column. The first radio button indicates ascending order. The second radio button indicates descending order. The check box determines if the column is subtotaled.

Apply Filter
The Filter tab is used to set criteria for including or excluding specific items in a report. The names on the left indicate the columns to be filtered in the order they will be filtered. The names on the right are the available columns. Double-click on a column name to move it from one area to the other. To reorder the columns, select a column name and click the arrows at the top of the tab to move the column up or down a position. You click another tab or close the dialog box, an additional dialog box displays for you to enter the filter criteria. You can use the multiple selection icon to enter multiple values or ranges. You can also use dynamic selections to apply operators to the criteria. When you are finished entering values, click (Copy) to apply the filter.

Change Display Options
The Display tab is used to change the way a report is displayed. The following table provides an
explanation of each option.
Display Option Description
Without horizontal gridlines Removes horizontal lines
Without vertical gridlines Removes vertical lines
Without column headings Removes column headers
Without cell merging during sorts Places a horizontal line between each entry. If
not checked, horizontal lines are removed
between identical values.
With optimum column width Set each column to the width of its largest value
With striped pattern Set every other row to a different color
Display totals lines above the entries Moves totals and subtotals above the lines they
summarize

Save a Report Layout
1. Click (Save Layout).
2. Enter a name in the Save Layout field. The name must begin with a letter.
3. Type in a description for the layout in the Name field.
4. Select the Default Setting check box if you want this layout to be the default layout every time you run
the report.
5. Click (Continue).
Note: A warning message will appear if you are trying to save over an existing layout. Close the box by
selecting the X in the upper right hand corner or choose Yes to overwrite the layout.

Select a Layout
1. Click (Select Layout).
2. Select a layout and click (Enter). Your report will display in the layout you have chosen.
Delete a Layout
If a layout you created is no longer useful, it can be deleted using the following process.
1. Follow the menu path Settings > Layout > Manage.
2. Select the layout(s) to be deleted by clicking on the gray box on the left side of the layout name.
3. Click (Delete layout). The layout is removed.
4. Click (Back). A pop-up box displays asking you to save your changes. Click Yes.

Report Integration with Microsoft Office
After generating a report, it is possible to export it into Microsoft Excel and/or Microsoft Word using three different options. Each of these options saves the file in a slightly different format. Before using any of these options, you have to set the macro security in your Office products to medium. Within your Office program, follow the menu path Tools > Macro > Security. Select the Medium security setting. Then click the Trusted Sources tab and ensure all the check boxes are selected. Click OK to save the changes. For the best results, ensure your Office program is closed before performing any of the following actions.

Save to Local File
Using this export option will retain all of the formatting that you may have done to the report in SAP, such as moving columns, setting filters and sorts, etc., but will not retain any of the color or font formatting in SAP, unless you choose the HTML option.

1. Click (Local file). The Save list in file... box will open.
2. Choose the desired file type in which to save the file.
• unconverted - tab-delimited file not associated with a program
• Spreadsheet - Microsoft Excel file
• Rich text format - Microsoft Word file
• HTML format - HTML file. This option adds some formatting, which will make it display
similiar to the report in SAP.
3. Click (Continue). The Transfer DAT to a Local File box will open.
4. The default location in which to save the file is your "SAPWorkDir" folder. Click (Search) to
choose another location.
5. Enter your file name at the end of the path and use the proper extension associated with the file
type you chose in step 2.
• unconverted - none
• Spreadsheet - .xls
• Rich text format - .rtf
• HTML format - .html
6. Click . The message "XXX Bytes transferred" will display, indicating that your file was
successful exported.

Exporting to Microsoft Excel

Using this export option will not retain any of the formatting that you applied in SAP, such as moving columns, setting filters and sorts, etc. However, it does add a colored background and heading and retains the proper column width.
1. Click (Spreadsheet...). An Information box will open advising you that any formatting you have
applied in SAP will not be exported with the data.
2. Click (Continue). The Export list object to XXL box will open.
3. Choose Table and click (Continue).
4. Click (Continue) again.
5. Excel will open with the report displayed. You can now format the report and save it as necessary.
6. In SAP, an Information box opens stating that you should save the data in the spreadsheet. As
soon as you click (Continue), the report in Excel closes, so be sure you have saved it if
necessary before doing so.

Opening Microsoft Excel within SAP

This export option will actually open Microsoft Excel within SAP, allowing you to use any of the formatting or calculation features available in Excel along with the SAP tools. However, modifying the data in the Excel spreadsheet within SAP will not change the actual data in SAP itself.

1. Click (Change layout...). The Change layout box will open.
2. Click the View tab.
3. Choose the Excel option.
4. Click on sap_om.xls in the Template list that displays on the right side of the box.
5. Click (Transfer).
6. Microsoft Excel will open in the window where the report data was displayed. You can now use all
of the options within Microsoft Excel and SAP to format and manipulate the data as necessary.
7. To save the file, follow the Excel menu path File > Save Copy As.
8. To close Excel, click (Change layout...), click the View tab, choose the Grid option, and click
(Transfer).

Exporting to Microsoft Word

Using this option will not retain any of the formatting that you applied in SAP, such as moving columns, setting filters and sorts, etc., and it will export the data in a table within Word.

1. Click (Word Processing...). The Word Processor Settings box will open.
2. Choose the Create Document option and select Include Colors and/or Start MS Word if desired.
3. Click (Continue). The Transfer RTF to a Local File box will open.
4. The default location in which to save the file is your "SAPWorkDir" folder. Click (Search) to
choose another location.
5. Enter the file name at the end of the path and add the extension .rtf.
6. Click .
7. If you chose the option to have Word open, it will now open with the data displayed.

Other Relative Topics :

Sample ALV Program

SAP Memory Vs ABAP/4 Memory

2007-10-16T22:40:00.000+05:30

SAP memory is the memory area where all main sessions with in the SAP GUI have the access. We can use SAP memory either to pass data from one program to other within the session, or to pass data from one session to other. 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 the 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 datato 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.

SAP Implementation Process

2007-10-11T22:34:00.000+05:30

SAP Implementation is the whole of processes that defines a complete method to implement SAP software in an organization. The SAP implementation method described in this entry is a generic method and not a specific implementation method as such. It is based on best practices and case studies from various literature sources and presents a collection of processes and products that make up a complete implementation method to allow any organization to plan and execute the implementation of SAP (ERP) software.
Contents

1 Introduction
2 Overview
3 Table of concepts
4 Activity table
5 Implementation processes
5.1 Project preparation
5.2 Sizing and blueprinting
5.3 Functional development
5.4 Final preparation
5.5 Go Live
6 Critical success factors
7 See also
8 References

Introduction

The implementation of SAP software, such as SAP R/3 is almost always a massive operation that brings a lot of changes in the organization. The whole process can take a few years. Most probably every person in the organization is involved, whether they are part of the SAP technical support organization (TSO) or the actual end-users of the SAP software. All the changes that the implementation of SAP generates are being made to reach high level goals, such as improved communication and increased return on information (because people will work with the same information). It is therefore very important that the implementation process is planned and executed with the usage of a solid method. There are various SAP implementation methods, such as IBM’s Ascendant. Unfortunately, no information on these methods is freely available and therefore this entry does not describe such a method but a generic implementation method.

Overview Figure 1:

SAP Implementation process-data diagramThe SAP implementation process is made up out of four main phases, i.e. the project preparation where a vision of the future-state of the SAP solution is being created, a sizing and blueprinting phase where the solution stack is created and training is being performed, a functional development phase and finally a final preparation phase, when the last tests are being performed before the actual go live. For each phase, the vital activities are addressed and the deliverables/products are explained.The process-data diagram that is depicted at the right, gives an overview of all of these activities/processes and deliverables. The four gray boxes depict the four main implementation phases, which each contain several processes that are in this case all sequential. The boxes at the right show all the deliverables/concepts that result from the processes. Boxes without a shadow have no further sub-concepts. Boxes with a black shadow depict complex closed concepts, so concepts that have sub-concepts, which however will not be described in any more detail. Boxes with a white shadow (a box behind it) depict open closed concepts, where the sub-concepts are expanded in greater detail. The lines with diamonds show a has-a relationship between concepts.

Table of concepts

The data table below provides a summary of all the concepts addressed in the process-data diagram.

Concept Definition

CHANGE MANAGEMENT Activities involved in

(1) defining and instilling new values, attitudes, norms, and behaviors within an organization that support new ways of doing work and overcome resistance to change;

(2) building consensus among customers and stakeholders on specific changes designed to better meet their needs; and

(3) planning, testing, and implementing all aspects of the transition from one organizational structure or business process to another. (http://www.gao.gov/)

CHANGE MANAGEMENT DOCUMENTATION All documentation that is required and being delivered whilst performing change management, e.g. the functional test cases and all the other documents a new end-user of SAP requires and the various tools and approaches used to manage change by the TSO. (Anderson, 2003)

COST OF OWNERSHIP ANALYSIS Determination of where and when the costs are inquired within the context of the SAP solution stack and ongoing operations. The analysis addresses all internal and external costs, both one-time as well as recurring (Anderson, 2003)
CUTOVER The process of transitioning from one system to a new one (Anderson, 2003) CUTOVER PLAN All documentation related to planning, preparing and executing cutover, describing how to lock down the system from a technical change management perspective, preparing the TSO for its new role and rolling out the SAP graphical user interface to all future end users. (Anderson, 2003) DATA CENTER A data center is a facility used for housing a large amount of electronic equipment, typically computers and communications equipment.
(http://www.wikipedia.org/)

DATA CENTER REQUIREMENT A requirement for the SAP data center, i.e. a physical requirement like power requirements, a rack requirement, a network infrastructure requirement or a requirement to the network server. (Anderson, 2003) .

DISASTER RECOVERY (DR) REQUIREMENT Requirement that focuses on downtime that lasts many hours to days or even weeks (Anderson, 2003) .

FUNCTIONAL TEST CASE A set of conditions or variables under which a tester will determine if a certain business process works (www.wikipedia.org) .

HIGH AVAILABILITY (HA) REQUIREMENT Requirements that describes the amount of time that the system needs to be available to satisfy the needs of the users. (Anderson, 2003)

INSTALLATION DOCUMENTATION All documentation related to the installation of an end-to-end SAP solution (Anderson, 2003) .

OPERATIONS MANUAL The collection of current state system documentation, day-to-day and other regularly scheduled operations tasks, various installation and operations checklists and how-to process documents. (Anderson, 2003) .

SAP SAP AG is the name of the biggest European software company. The head office is in Walldorf, Germany. SAP was founded in 1972 as Systemanalyse und Programmentwicklung ("Systems Analysis and Product") by five former IBM employees in Mannheim, Germany. (www.wikipedia.org) .

SAP IMPLEMENTATION PROJECT PLAN A comprehensive project plan that contains all products that are delivered whilst performing an SAP implementation project (Anderson, 2003)
SOLUTION STACK Set of software subsystems or components needed to deliver a fully functional solution, e.g. a product or service. (www.wikipedia.org) .

SOLUTION STACK PARTNERS LIST A list of all vendors that deliver the products that make up the SAP solution stack (Anderson, 2003) .

SOLUTION VISION A vision of the future-state of the SAP solution (Anderson, 2003) .

STRESS TEST PLAN A test plan that is focused at determining the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. (www.wikipedia.org) .

TEST PLAN A detail of how the test will proceed, who will do the testing, what will be tested, in how much time the test will take place, and to what quality level the test will be performed. (IEEE 829) TRAINING The acquisition of knowledge, skills, and attitudes as a result of the teaching of vocational or practical skills and knowledge that relates to specific useful skills (http://www.wikipedia.org/).

TRAINING PLAN Consisting of training units, a training plan is the result of hierarchical decompositions of a training goal, tailored according to the learning preferences and prior knowledge of the trainee. A plan is the means by which the trainee satisfies the goal. (www.ece.eps.hw.ac.uk/) TSO Technical Support Organization. The people that are committed to implementation and management of SAP. (Anderson, 2003) TSO CHART A chart that depicts the structure of the TSO. (Anderson, 2003)

Activity table

The following table provides a summary of all of the activities that form the SAP implementation process. These activities will be described with more detail and elaborated with examples in the rest of this entry.

Activity Sub-Activity Description

Project preparation Craft solution vision Refine and communicate a SOLUTION VISION of the future-state of the SAP solution, to sketch a design that meets both business and financial requirements. The focus should be on the company’s core business and how the SAP solution will better enable that core business to be successful.Design and initially staff the SAP TSO Design and staff the key positions of the SAP Technical Support Organization (TSO), the organization that is charged with addressing, designing, implementing and supporting the SAP solution.Sizing and blueprinting Perform cost of ownership analysis Perform a COST OF OWNERSHIP ANALYSIS to determine how to get the best business solution for the least money i.e. to determine where and when the costs are incurred within the context of the SAP solution stack.Identify high availability and disaster recovery requirements Determine all HIGH AVAILABILITY and DISASTER RECOVERY REQUIREMENTS, to plan what to do with later downtime of the SAP systemEngage SAP solution stack vendors Select the best SAP hardware and software technology partners for all layers and components of the SAP SOLUTION STACK, based on a side-by-side sizing comparisonStaff TSO Staff the bulk of the TSO, i.e. fill the positions that directly support the near-term objectives of the implementation, which are to develop and begin installation/implementation of the SAP data center.Execute training Train the various members of the SAP TSO, like data center specialists, high availability specialist and network specialists and train the end-users to give all the required SAP knowledge and skillsSetup SAP DATA CENTER Build a new SAP DATA CENTER facility or transform the current data center into a foundation capable of supporting the SAP SOLUTION STACK.Perform installations Install the (My)SAP components and technological foundations like a web application server or enterprise portal.Round out support for SAP Identify and staff the remaining TSO roles, e.g. roles that relate to help desk work and other such support providing work.SAP functional development Address Change Management Develop a planned approach to the changes in the organization. The objective is to maximize the collective efforts of all people involved in the change and minimize the risk of failure of implementing the changes related to the SAP implementation.Address SAP systems and operations management Create a foundation for the SAP systems management and SAP computer operations, by creating a SAP OPERATIONS MANUAL and by evaluating SAP management applications.Perform functional, integration and regression tests Test the SAP business processes, by executing functional tests to ensure that business processes work, integration tests to ensure that the organization’s business processes work together with other business processes and regression tests to prove that a specific set of data and processes yield consistent and repeatable results.Final Preparation Perform systems and stress tests Plan, script, execute and monitor SAP STRESS TESTS, to see if the expectations of the end users, defined in service level agreements, will be met.Prepare for cutover Plan, prepare and execute the CUTOVER, by creating a CUTOVER PLAN that describes all cutover tasks that have to be performed before the actual go-liveGo Live Turn on the SAP system for the end-users.

What is the history of SAP?

2007-10-11T22:17:00.000+05:30

Systems, Applications, Products in data processing or SAP was originally introduced in the 1980’s as SAP R/2 which was a mainframe system that provided users with a soft-real-time business application that could be used with multiple currencies and languages. Later when client servers were introduced SAP brought out a server based version of their software called SAP R/3, henceforth referred to as SAP, which was launched in 1992. They also developed a graphical user interface or GUI to make it more user friendly and to move away from the mainframe style user interface. For the next 10 years SAP dominated the large business applications market. It was successful primarily because it was extremely flexible. Because SAP was a modular system meaning that the various functions provided by it could be purchased piecemeal it was an extremely versatile system. All a company needed to do was purchase the modules they wanted and customize the processes to match the company’s business model. SAP’s flexibility, while one of its greatest strengths is also one of its greatest weaknesses. We will now turn to the audit issues surrounding SAP.

SAP AG
From Wikipedia, the free encyclopedia
Jump to: navigation, search
SAP AG
Type: Aktiengesellschaft (FWB:SAP, NYSE: SAP)
Founded: Weinheim (1972)
Headquarters: Walldorf, Germany
Key people: Henning Kagermann, CEO
Shai Agassi, Development
Industry: Computer software
Products: ERP
Revenue: 8.5billion EUR (2005)
Employees: 32,205
Website: www.sap.com
SAP AG (FWB:SAP, NYSE: SAP) is the largest European software enterprise, with headquarters in Walldorf, Germany. SAP was founded in 1972 as System analyse und Programment wicklung by five former IBM engineers in Mannheim, Germany. The acronym was later changed to stand for Systeme, Anwendungen und Produkte in der Datenverarbeitung ("Systems, Applications And Products in Data Processing") and since the 2005 annual general
meeting the company's official name is just SAP AG.

Reputation

SAP is the third-largest software company in the world. It ranks after Microsoft and Oracle in terms of market capitalization. SAP is the largest business application and Enterprise Resource Planning (ERP) solution software provider in terms of revenue.

Products

SAP's products focus on ERP, which it helped to pioneer. The company's main product is SAP R/3; the "R" stands for realtime data processing and the number 3 relates to a 3-tier architecture: database, application server and client (SAPgui). SAP R/3's predecessor was R/2 which ran on a Mainframe architecture.

Other major product offerings include

Advanced Planner and Optimizer (APO),

Business Information Warehouse (BW),

Customer Relationship Management (CRM),

Supply Chain Management (SCM),

Supplier Relationship Management (SRM),

Human Resource Management Systems (HRMS),

Product Lifecycle Management (PLM),

Exchange Infrastructure (XI),

Enterprise Portal (EP) and Knowledge Warehouse (KW).

The APO name has been retired and rolled into SCM. The BW name (Business Warehouse) has now been rolled into the SAP NetWeaver BI (Business Intelligence) suite and functions as the reporting module.

The company also offers a new technology platform, named SAP NetWeaver. While its original products are typically used by Fortune 500 companies, SAP is now also actively targeting small and medium sized enterprises (SME) with its SAP Business One and SAP All-in-One.

Reportedly, there are over 100,800 SAP installations at more than 28,000 companies. SAP products are used by over 12 million people in more than 120 countries.

Architecture of the Enhancement Technique

2007-10-07T23:46:00.000+05:30

In order to enhance a program, you must first define a Business Add-In. The application developer creates an interface for the add-in. From this, enhancement management creates an adapter class that implements the interface and thus provides the interface for implementation by the customer, partner, and so on. The developer then creates an instance of the adapter class in the application program and calls the corresponding method at the appropriate time.

For each Business Add-In you have one interface and an adapter class that implements this. The interface is implemented by the user.

The generated class (Add-In adapter) has the following tasks:
· Control

The adapter class calls the active implementations.
1. · Filtering
If a Business Add-In is to be executed only under certain conditions, the adapter class ensures that only certain implementations will be executed.

This concept ensures mutlple use. Any Business Add-In that has been implemented once already can be implemented again by those groups listed to the right of the software chain shown in the above graphic.

Customers can find the enhancements in their system in the Implementation Guide (IMG) and in the component hierarchy. If a customer wishes to use a Business Add-In, he or she first creates an implementation. The customer must implement the methods and the enhancements, and afterwards activate the implementation of the enhancement. The enhancement's active components are then called at runtime. Normally, a Business Add-In contains an interface and other additional components such as function codes for menu enhancements. In some cases, Business Add-Ins also include enhancements for screens. The enhancement, interface, and generated classes are all located in the appropriate application development namespace. Business Add-In implementations are created in the respective implementation namespace.

A Comparison of Different Enhancement Techniques

2007-10-07T23:43:00.000+05:30

Due to the necessity of adjusting R/3 to meet the specific needs of a variety of customers, several different enhancement techniques were developed in the past. A short description of each of the various enhancement techniques follows.

Business Transaction Events (Open FI)

The Open FI enhancement technique was developed in the Financial Accounting component. Open FI is based upon the following principles:

Application developers must define their interface in a function module, an assignment table is read in the accompanying (generated) code, and the customer modules assigned are called dynamically.
This technique differentiates between enhancements that are only allowed to have one implementation and enhancements that can call multiple implementations in any sequence desired. Both industry-specific and country-specific enhancements may be defined.
The concepts behind the Business Add-Ins enhancement technique and Open FI are basically the same. However, the two enhancement techniques do differ from each other in the following points:

1. · Open FI can only be used to make program enhancements, that is, you can only enhance source code using Open FI. You cannot enhance user interface elements with Open FI like you can with Business Add-Ins.
1. · Open FI assumes that enhancement will only take place on three levels (SAP - partners - customers), whereas with Business Add-Ins you can create and implement enhancements in as many software layers as you like.
2. · Open FI uses function modules for program enhancements. With Business Add-Ins, ABAP Objects is used to enhance programs.

Enhancements in Transactions SMOD/CMOD

Making enhancements using the transactions SMOD/CMOD has the following disadvantages:
1. · This enhancement technique assumes a two-tiered system infrastructure (SAP – customers).
2. · The naming conventions in effect do not tolerate name extension.

Conclusion:
None of the techniques mentioned above can easily be extended to fulfill the requirements of a system infrastructure containing country versions, industry solutions, partners, and customers.Business Add-Ins should be considered generalized Business Transaction Events that can be used to bundle program, menu and screen enhancements into a single add-in. Business Add-Ins can be created and employed in each of the various software levels.

Defining a Business Add-In

2007-10-07T23:30:00.000+05:30

Use
An application developer who wishes to have a Business Add-In in a particular program defines the interface for an enhancement in the Business Add-In Builder. In the following step, he or she programs the interface call in the application program at the appropriate place. Customers can then select the add-in and implement it according to their needs.

Procedure
1. ...
1. From the SAP menu, choose Tools ® ABAP Workbench ® Utilities ® Business Add-Ins (transaction SE18).

We would like to explain the procedures using an application program as an example. There is a string conversion in the program. You want the add-in users to determine themselves how their strings are to be converted. The application developer defines an enhancement. It consists of an interface with a method. A changing parameter is used to pass on the string.

Option: Within SAP

Meaning: If the customer selects this option for an Add-In, he or she has no option for creating his or her own implementations for this Business Add-In or for using them. In the input help, Business Add-Ins with this flag are not displayed. For more information on the checkbox Within SAP, refer to the section Definition of a Business Add-In in the Enterprise Core.

Option: Multiple Use

Meaning: The Business Add-In can be set for multiple use. For more information, refer to the section Multiple-Use Business Add-Ins.

Option: Filter-Dependent

Meaning : The implementation of a Business Add-In is dependent on a particular filter value.For more information, refer to the section Multiple-Use Business Add-Ins.
None of the above options is selected.

5. Choose the Interface tab. The interface name is generated automatically and can be changed here.

2. Enter a name with a maximum of 20 characters for the Business Add-In.

3. Choose Create.
4. On the following screen, enter a short text as the description for the Business Add-In.In this example, we are dealing with a simple enhancement.

Under the FCodes tab, you can create Menu Enhancements, and under the Subscreens tab you can create Screen Enhancements.
6. Double-click the interface name field. The system branches to the Class Builder.
7. Confirm that you want to save the entries you have made. Assign a package to the Business Add-In.

8. Use the Class Builder to assign a method to the interface.

9. Now define a parameter with the following attributes:

10. Save and activate your entries. Use the pushbutton Back to navigate back to the Business Add-In definition.

You can now continue with the definition of the Business Add-In by executing activation in the Class Builder.
A table control now appears on the definition screen for the Business Add-In. It displays the method you have created for the interface.
When you maintain the interface methods, the corresponding executing class is generated. The generated code cannot be altered in the initial expansion phase.
11. Save your entries and use the Documentation pushbutton to create a description for your new Business Add-In. Remember that this documentation is very important for users to be able to understand the purpose behind the Add-In. For more information, read the section Documentation of a Business Add-In.

Choose Goto ® Default Coding / Sample Coding if you wish to create default coding and/ or sample coding for the Business Add-In. The default implementation is executed only if no other active implementation is available. This applies also to filter-dependent Business Add-Ins.

When you create default or sample coding, do not forget to save your entries. In this way, the connection between the class and the implementation is set up.

Calling a Business Add-In in the Application Program

2007-10-07T23:28:00.000+05:30

When you define a Business Add-In, enhancement management generates a class that implements your interface. The application developer uses a factory method to create an instance of this adapter class in the application program and calls the corresponding method, if necessary.
The adapter class method generated by add-in management decides whether one or several active implementations should be called. If necessary, these implementations are subsequently executed. The application program ensures only that the adapter class method is called. The application program does not know which implementations are called.

Example:

Having created a string conversion Business Add-In, you would program the call of the Business Add-In into your ABAP source code as follows:

1 Report businessaddin.
2 class cl_exithandler definition load. "Declaration
3 data exit type ref to if_ex_businessaddin. "Interface reference
4 data word(15) type c value 'Business Add-in'. "String to change

5 start-of-selection.
6 call method cl_exithandler=>get_instance "Factory method call
7 exporting "Method
exit name =’BUSINESSADDIN’
8 null instance accepted =’X’
9 changing instance = exit.
10 write:/'Please click here'.

11 at line-selection.
12 write:/ 'Original word: ',word.

13 if not exit is initial.
14 call method exit->method "Add-In call
15 changing parameter = word.
16 endif.
17 write:/ 'Original word: ',word.

In order to be able to call static methods, you must declare the corresponding class in ABAP Objects. This is why the class … definition load statement is necessary for the factory class.
A variable for object reference is also necessary when calling the method. Use data to create it and type it to the interface.

During initialization (line 6), the application developer creates an adapter class instance using the factory method. The instance methods are then called at the time specified.

To improve performance during creation of the instances, you should specify additional parameters for the call in the method GET_INSTANCE of the class CL_EXITHANDLER.

EXIT_NAME: The name of the BAdI definition is assigned to this parameter.

NULL_INSTANCE_ACCEPTED: Whenever the value X is assigned to this parameter, no instance is created if there are no active implementations for this BAdI definition. In this case, the INSTANCE parameter has the value NULL. Using this parameter implies that the method calls of this BAdI may only be called under the condition that this instance is not NULL. The query if not is initial. is necessary in this case.

Notes on Usage
The instance generated through the factory method should be declared as globally as possible or generally be passed as a parameter to ensure that the initialization process must be run as rarely as possible – just once would be best. In no case should you discard the instance as soon as it is generated or repeatedly run the initialization process in a loop.

Within the adapter class interface, required database accesses are buffered locally, so that each access is executed once only. However, repeated initialization makes the buffer useless and dramatically reduces performance.

Due to the local buffering, you can call Business-Add-In methods without having to expect considerable performance restrictions, even if no active implementations exist.

Also, if the definition of the Business-Add-In is filter-dependent, a single instance is sufficient.
However, you should not do without initialization altogether. Even if you could call static methods of the implementing class of the Business-Add-In implementation without an instance, you would lose the benefit of performance improvement through the Business-Add-Ins and the possibility of multiple use. If you switch the method type in the interface from the static method to the instance method at any time in the future, many code adjustments are required. In addition, you can no longer use default code that is provided

Implementing a Business Add-In

2007-10-07T23:17:00.000+05:30

A list of the Business Add-Ins available in your system can be found either in the SAP Reference Implementation Guide (IMG) or in the component hierarchy. BAdI definitions are included in the IMG so that the customer/partner can create suitable, company-specific implementations

Note : In the SAP Reference IMG, BAdI implementations - in addition to BAdI definitions - can be provided. This would be suitable in cases where you can see in advance which functions are required by the customer. Using a BAdI implementation, the customer/partner can simply switch the delivered implementations on or off, as required. In the SAP Reference IMG, choose Execute in front of the name of the BAdI implementation. The icon serves as a switch for activating and deactivating the implementation.

Starting from the name and the documentation of the enhancement, you can create an implementation. During the implementation, the system creates a class that implements the enhancement’s interface. The implementation is a separate transport object and lies within the namespace of the person or organization implementing it.

For the example given here, you are to create an implementation for the string conversion. You need to program the interface method in such a way that, when the add-in is called from the application program, the string is actually converted in the way the add-in user wants it.

To create an implementation, proceed as follows:
1. ...
1. 1. In the SAP menu, choose ABAP Workbench ® Utilities ® Business Add-Ins (transaction SE19) or double-click the corresponding activity in the Implementation Guide (IMG).
2. 2. Enter a name for the implementation and then click the Create pushbutton.
3. 3. Enter the name of the add-in for which you want to create an implementation for in the dialog box that appears.

4. 4. Enter a short text describing your implementation on the following screen.
5. 5. Choose the Interface tab.
6. 6. Choose ABAP Code as the implementation type.
In addition to ABAP Code, there is also the Formula option. If you choose Formula, the content of a method is determined using the Formula Builder. For more information on this, refer to the section Implementing Methods Using the Formula Builder.
7. 7. Navigate to the Class Builder by double-clicking the method. You must first enter a package before the Class Builder is displayed.
8. 8. Insert the desired source code for the implementation between the method if_ex_businessaddin~method. and endmethod. statements that already exist.

In our particular example, you could enter the statement translate parameter to upper case.
9. 9. Save your entries and return to the Change Implementation screen.
10. 10. Choose Activate. You may now use this implementation when the application program is executed.

Note : Several implementations may exist for a Business Add-In that is not used on a multiple basis. However, only one implementation can be active at any one time.What is also important is that you must declare the instance generation of the implementing class (Attributes tab) as public and not as private, protected, or even abstract. If you do this, the system will return short dumps at runtime.

Implementing Methods Using the Formula Builder

2007-10-07T23:12:00.000+05:30

Use
You can use the Formula Builder to implement methods for Business Add-Ins without writing a single line of ABAP code. The methods are implemented by means of socalled formulas.

This type of implementation does not require you to have programming knowledge. However, the functions it offers are more restricted than if you implement a method by writing ABAP code. If the range of functions provided by the Formula Builder is not sufficient, you can change the implementation type of the method at any time.

Features
A formula can consist of the following steps:

· Condition
You define a Boolean formula expression whose result can be true or false. This formula expression is a logical condition based on the importing and changing parameters of the method. Depending on whether the condition is true or false, the system triggers different steps. If you do not specify a dependent step for one of these two possibilities, the system continues with the next superior step.

· Substitution
The system replaces the value of a specific parameter with another value which you define as a constant value or by means of a mathematic formula. Substitution is only possible if the method contains changing, exporting or returning parameters.

· Message
The system issues a message. All messages issued are collected in a log table. You define the message variables as constant values or by means of mathematic formulas. The system can only issue a message if you created a log table during method definition.

· Exception
The system exits the method. No further steps are executed, and the application program continues in accordance with the exception defined. You can additionally display a message whose variables you define as constant values or by means of mathematic formulas. An exception can only be triggered if the method contains exceptions.

A formula editor is available which you can use to enter formula expressions. After starting the formula editor, you can display information on how to use it by choosing the pushbutton next to the status display (traffic light).

Activities
You implement the method using the BAdI Builder. For information on this topic, see Implementing Business Add-Ins. To implement a method as a formula, choose the Formula implementation type on the Interface tab. Double-clicking the method name takes to to the Formula Builder: BadI Implementation screen.

You can change the implementation type of the method on the Interface tab. You can implement a method both using a formula and using ABAP code. At the runtime of the application program, the system executes the implementation type currently chosen.

You create the necessary steps in the left section of the screen. To do this, choose and then select the appropriate step type from the dropdown list. Using the other icons available or the context menu (which you can call by clicking the right mouse button), you then determine the arrangement and the descriptions of the steps. You can also copy steps to use them as templates for other steps, or you can delete individual steps.

To specify the parameters for the individual steps, double-click the corresponding entry in the left section of the screen. You then enter the data required in the right section of the screen.

Formulas are transported automatically.

Multiple-Use Business Add-Ins

2007-10-07T23:07:00.000+05:30

You can differentiate between single-use and multiple use Business Add-Ins. The distinction is based on the procedure or event character of an enhancement. In the first case, the program waits for the enhancement to return something, usually a return code. A typical example could be a benefit calculation in HR. Depending on the implementation, alternative calculations can be executed. With multiple use add-ins, an event that may be of interest to other components is processed in program flow. Any number of components could use this event as a “hook” to hang their own additional actions on to.

Note :

In addition to importing parameters, you can also use changing parameters for multiple-use Business Add-Ins. There is no sequence control for multiple-use implementations of BadIs. Therefore, using changing parameters can cause problems. There is no guarantee that implementations will not overwrite the results of previous implementations. Sequence control is technically impossible, since at the time of the definition the interface does not know which implementations there will be and which parameters will be changed by implementations. It is not possible to have a decision as to which implementation should be executed before which other (future) implementation.

Example:
In a particular application, you want to be able to continue processing indexes after another component has saved data (in other words, the system should allow you to use an add-in after saving). Since this point in time can be useful for different purposes, you can create an enhancement here that can be used by multiple subscribers.

To create a multiple-use Business Add-In, proceed as follows:

2. ...
11. 1. Define an add-in and select the Multiple Use checkbox from the Administration tab.
12. 2. Define an interface with the method OBJECT_SAVED'and the importing parameter OBJECTNAME.
Calling your enhancement in the application program:
program event.
…
data exit_obj type ref to if_ex_event.
…
call method cl_exithandler =>get_instance
changing instance = exit.

form save_object using obj_name type c.
…
update …
call method exit_obj->object_saved
exporting objectname = obj_name.
endform.
For the caller it is irrelevant whether (and how many) subscribers use the event as a starting point for further actions. The active implementations are called in the adapter method.

Menu Enhancements

2007-10-07T22:54:00.000+05:30

Menu enhancements with function codes are provided for in the user interfaces. These function codes must adhere to the form /namensraum/+<...>, just like in the enhancement technique SMOD/CMOD. These function codes are assigned to an enhancement. Only when there is an active implementation of the assignment do they appear in the menu.

The application developer reserves specific function codes for customers when defining a Business Add-In and assigns them in the Menu Painter in the appropriate menu lists. The application developer must also ensure that these menu options are queried in the application program and that the corresponding add-in method is also called. Customers can take advantage of menu enhancements by creating a new implementation, choosing a text for the menu option, and then programming the method used to determine what action is performed when the menu enhancement is called.

Menu enhancements can only be used for single-use add-ins (not multiple-use add-ins) that are not filter-dependent. Currently, menu enhancements can only be created in conjunction with program enhancements (interfaces).

To create a menu enhancement, proceed as follows:
3.
13. 1. Create the definition of an add-in and define its interface.
14. 2. Choose the FCodes tab.
15. 3. Enter the name of your program, the function code, and a description.

16 4. Call the Menu Painter or double-click on the program name or function code to navigate to user interface maintenance in the Menu Painter. Enter the function code in the appropriate menu list. If you have accessed the Menu Painter directly during add-in definition, you can call the menu lists by choosing Goto ® Object Lists ® Menu Lists.

Calling a Menu Enhancement from the Application Program

The application program should look like this:
(…)
case fcode.
when 'SAP'.
(…)
when '+CUS'
call method …

Implementing a Menu Enhancement

To create the implementation of a menu enhancement, proceed as follows:

4. eine Implementierung an und wählen Sie den Registerindex Fcodes

1. Create an implementation and choose the FCodes tab. All data adopted from your Business Add-In's definition is displayed here. You can make entries for the implementation on the right. You can also double-click the first input field. The following dialog box appears:

Here you may enter a text for your function code, the name of an icon, a text for the icon, and a short description.
The actions that you want the system to perform after the pushbutton is chosen must be programmed in the appropriate method, either manually or using a default source code that has been provided for this purpose. Menu enhancements only become visible after the implementation has been activated and the application program that calls the Business Add-In has been executed.

Business Add-Ins: Import Procedure

2007-10-07T11:35:00.000+05:30

Conflicts can occur at release upgrade or when transporting a Business Add-In within a system infrastructure containing multiple levels (country versions, industry solutions, partners, etc.). Possible collisions include:

Case 1 : Multiple active implementations exist for Business Add-Ins that have not been designed for multiple use (for the same filter value, if add-in is filter-dependent).

Case 2 : Identical interfaces were assigned during Business Add-In definition.
Case 3 : Identical function codes were assigned during Business Add-In definition.

Whenever such collisions occur, corresponding error messages and warnings are created in the transport log at import. Their long texts provide you with information on how to proceed.

If the collision described in case 1 occurs in your system, proceed as follows

1. 1.Choose Utilities ® Adjustment ® Multiple active implementations (in transaction SE18).
A list appears displaying your Business Add-Ins. A red traffic light indicates that multiple active implementations exist for that add-in.
2. 2. Deactivate these implementations using the appropriate pushbutton or double-click on the name of the implementation to branch to the corresponding transaction where you can then correct the problem

In cases 2 and 3, proceed as follows:

1. 1. Choose Utilities ® Adjustment ® Multiple assigned interfaces or Multiple function codes assigned.

Both of these menu options display an overview; the Add-Ins in question are marked with a red traffic light.

2. 2. The people responsible for those add-in definitions where identical interfaces and function codes occur must now decide how to proceed. To delete a function code or change an interface name, call the ABAP Workbench and use the appropriate pushbutton to call the tool you need. A new transport may be necessary.

Sorting BAdI Implementations

Use
The sequence for execution of BAdI implementations can be controlled for BAdIs used on a multiple basis by a sort mechanism.
Procedure
1. en ...
2. .
In the BAdI Builder (SE18), choose Utilities ® Sort.
Choose Standard Sort if sorting is to take place using numeric sort values. The numeric values are entered in the displayed field Layer Value when you create the implementations and stored in a table. The implementations are executed in accordance with the specified sequence.
Choose Special Sort if sorting is to take place using non-numeric sort values. In this case, you need to enter the name of the implementation that will be created in the following step.
Proceed as follows if you require special sorting:

18. 1. Create an implementation for the BAdI definition BADI_LAYER contained in the delivered product. Enter a BAdI definition as filter value in the Properties tab (the name will be used as a dummy value to begin with).

19. 2. Create a screen (in a function group or a module pool). The screen contains, for example, a text field with the name Sort Value and an input field.

20. 3. Choose the Subscreens tab of the BAdI implementation and enter the called program and the screen number.

21. 4. Choose the Interface tab. The IF_EX_BADI_LAYER interface contains the following methods:

In addition to methods for data transmission of the sort value and for changing the BAdI implementation, the interface also contains a sort method that sorts a table of values in any specified order.

A standard table is passed to this method as a changing parameter. The table contains values only; it does not contain any implementation names.
This table contains, for example, inputs for the Sort Value field when you create implementations. The user can maintain any fields as required and sort them according to any specified criteria at runtime.

22. 5. Program the method SORT_DATA. Here is an example of simple sorting of numeric values:

23 6. Program the methods for data transmission in the following form (see also Screen Enhancements).

24 7. Program the call for implementations from the application program. The IF_EX_BADI_LAYER interface contains a parameter-free method called TEST for test purpose.

The implementations are executed (for example, in numeric sequence).

Switching Off Sort Function

To switch off the sort for the execution of BAdI implementations, choose Utilities ® Sort and finally No Sort. The implementations will now run in an arbitrary sequence in this case. The edit field that was displayed using a subscreen during the execution of a BAdI implementation now disappears.
Sorting of BAdI implementations can be switched on again at any time. This does not count as a modification to the standard version. The BAdI definition is not changed. Switching off or making a change, on the other hand, counts as a modification.

Example of Sending XLS file as a mail via SAPCONNECT

2007-10-05T22:04:00.001+05:30

&---------------------------------------------------------------------*

*& Report ZEMAIL_ATTACH *

*& *

*&---------------------------------------------------------------------*

*& Example of sending external email via SAPCONNECT *

*& *

*&---------------------------------------------------------------------*

REPORT ZEMAIL_ATTACH .

TABLES: ekko.

PARAMETERS: p_email TYPE somlreci1-receiver

DEFAULT 'test@sapdev.co.uk'.

TYPES: BEGIN OF t_ekpo,

ebeln TYPE ekpo-ebeln,

ebelp TYPE ekpo-ebelp,

aedat TYPE ekpo-aedat,

matnr TYPE ekpo-matnr,

END OF t_ekpo.

DATA: it_ekpo TYPE STANDARD TABLE OF t_ekpo INITIAL SIZE 0,

wa_ekpo TYPE t_ekpo.

TYPES: BEGIN OF t_charekpo,

ebeln(10) TYPE c,

ebelp(5) TYPE c,

aedat(8) TYPE c,

matnr(18) TYPE c,

END OF t_charekpo.

DATA: wa_charekpo TYPE t_charekpo.

DATA: it_message TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0

WITH HEADER LINE.

DATA: it_attach TYPE STANDARD TABLE OF solisti1 INITIAL SIZE 0

WITH HEADER LINE.

DATA: t_packing_list LIKE sopcklsti1 OCCURS 0 WITH HEADER LINE,

t_contents LIKE solisti1 OCCURS 0 WITH HEADER LINE,

t_receivers LIKE somlreci1 OCCURS 0 WITH HEADER LINE,

t_attachment LIKE solisti1 OCCURS 0 WITH HEADER LINE,

t_object_header LIKE solisti1 OCCURS 0 WITH HEADER LINE,

w_cnt TYPE i,

w_sent_all(1) TYPE c,

w_doc_data LIKE sodocchgi1,

gd_error TYPE sy-subrc,

gd_reciever TYPE sy-subrc.

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

*START_OF_SELECTION

START-OF-SELECTION.

* Retrieve sample data from table ekpo

PERFORM data_retrieval.

* Populate table with detaisl to be entered into .xls file

PERFORM build_xls_data_table.

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

*END-OF-SELECTION

END-OF-SELECTION.

* Populate message body text

perform populate_email_message_body.

* Send file by email as .xls speadsheet

PERFORM send_file_as_email_attachment

tables it_message

it_attach

using p_email

'Example .xls documnet attachment'

'XLS'

'filename'

' '

' '

' '

changing gd_error

gd_reciever.

* Instructs mail send program for SAPCONNECT to send email(rsconn01)

PERFORM initiate_mail_execute_program.

*&---------------------------------------------------------------------*

*& Form DATA_RETRIEVAL

*&---------------------------------------------------------------------*

* Retrieve data form EKPO table and populate itab it_ekko

*----------------------------------------------------------------------*

FORM data_retrieval.

SELECT ebeln ebelp aedat matnr

UP TO 10 ROWS

FROM ekpo

INTO TABLE it_ekpo.

ENDFORM. " DATA_RETRIEVAL

*&---------------------------------------------------------------------*

*& Form BUILD_XLS_DATA_TABLE

*&---------------------------------------------------------------------*

* Build data table for .xls document

*----------------------------------------------------------------------*

FORM build_xls_data_table.

CONSTANTS: con_cret TYPE x VALUE '0D', "OK for non Unicode

con_tab TYPE x VALUE '09'. "OK for non Unicode

*If you have Unicode check active in program attributes thnen you will

*need to declare constants as follows

*class cl_abap_char_utilities definition load.

*constants:

* con_tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB,

* con_cret type c value cl_abap_char_utilities=>CR_LF.

CONCATENATE 'EBELN' 'EBELP' 'AEDAT' 'MATNR'

INTO it_attach SEPARATED BY con_tab.

CONCATENATE con_cret it_attach INTO it_attach.

APPEND it_attach.

LOOP AT it_ekpo INTO wa_charekpo.

CONCATENATE wa_charekpo-ebeln wa_charekpo-ebelp

wa_charekpo-aedat wa_charekpo-matnr

INTO it_attach SEPARATED BY con_tab.

CONCATENATE con_cret it_attach INTO it_attach.

APPEND it_attach.

ENDLOOP.

ENDFORM. " BUILD_XLS_DATA_TABLE

*&---------------------------------------------------------------------*

*& Form SEND_FILE_AS_EMAIL_ATTACHMENT

*&---------------------------------------------------------------------*

* Send email

*----------------------------------------------------------------------*

FORM send_file_as_email_attachment tables pit_message

pit_attach

using p_email

p_mtitle

p_format

p_filename

p_attdescription

p_sender_address

p_sender_addres_type

changing p_error

p_reciever.

DATA: ld_error TYPE sy-subrc,

ld_reciever TYPE sy-subrc,

ld_mtitle LIKE sodocchgi1-obj_descr,

ld_email LIKE somlreci1-receiver,

ld_format TYPE so_obj_tp ,

ld_attdescription TYPE so_obj_nam ,

ld_attfilename TYPE so_obj_des ,

ld_sender_address LIKE soextreci1-receiver,

ld_sender_address_type LIKE soextreci1-adr_typ,

ld_receiver LIKE sy-subrc.

ld_email = p_email.

ld_mtitle = p_mtitle.

ld_format = p_format.

ld_attdescription = p_attdescription.

ld_attfilename = p_filename.

ld_sender_address = p_sender_address.

ld_sender_address_type = p_sender_addres_type.

* Fill the document data.

w_doc_data-doc_size = 1.

* Populate the subject/generic message attributes

w_doc_data-obj_langu = sy-langu.

w_doc_data-obj_name = 'SAPRPT'.

w_doc_data-obj_descr = ld_mtitle .

w_doc_data-sensitivty = 'F'.

* Fill the document data and get size of attachment

CLEAR w_doc_data.

READ TABLE it_attach INDEX w_cnt.

w_doc_data-doc_size =

( w_cnt - 1 ) * 255 + STRLEN( it_attach ).

w_doc_data-obj_langu = sy-langu.

w_doc_data-obj_name = 'SAPRPT'.

w_doc_data-obj_descr = ld_mtitle.

w_doc_data-sensitivty = 'F'.

CLEAR t_attachment.

REFRESH t_attachment.

t_attachment[] = pit_attach[].

* Describe the body of the message

CLEAR t_packing_list.

REFRESH t_packing_list.

t_packing_list-transf_bin = space.

t_packing_list-head_start = 1.

t_packing_list-head_num = 0.

t_packing_list-body_start = 1.

DESCRIBE TABLE it_message LINES t_packing_list-body_num.

t_packing_list-doc_type = 'RAW'.

APPEND t_packing_list.

* Create attachment notification

t_packing_list-transf_bin = 'X'.

t_packing_list-head_start = 1.

t_packing_list-head_num = 1.

t_packing_list-body_start = 1.

DESCRIBE TABLE t_attachment LINES t_packing_list-body_num.

t_packing_list-doc_type = ld_format.

t_packing_list-obj_descr = ld_attdescription.

t_packing_list-obj_name = ld_attfilename.

t_packing_list-doc_size = t_packing_list-body_num * 255.

APPEND t_packing_list.

* Add the recipients email address

CLEAR t_receivers.

REFRESH t_receivers.

t_receivers-receiver = ld_email.

t_receivers-rec_type = 'U'.

t_receivers-com_type = 'INT'.

t_receivers-notif_del = 'X'.

t_receivers-notif_ndel = 'X'.

APPEND t_receivers.

CALL FUNCTION 'SO_DOCUMENT_SEND_API1'

EXPORTING

document_data = w_doc_data

put_in_outbox = 'X'

sender_address = ld_sender_address

sender_address_type = ld_sender_address_type

commit_work = 'X'

IMPORTING

sent_to_all = w_sent_all

TABLES

packing_list = t_packing_list

contents_bin = t_attachment

contents_txt = it_message

receivers = t_receivers

EXCEPTIONS

too_many_receivers = 1

document_not_sent = 2

document_type_not_exist = 3

operation_no_authorization = 4

parameter_error = 5

x_error = 6

enqueue_error = 7

OTHERS = 8.

* Populate zerror return code

ld_error = sy-subrc.

* Populate zreceiver return code

LOOP AT t_receivers.

ld_receiver = t_receivers-retrn_code.

ENDLOOP.

ENDFORM.

*&---------------------------------------------------------------------*

*& Form INITIATE_MAIL_EXECUTE_PROGRAM

*&---------------------------------------------------------------------*

* Instructs mail send program for SAPCONNECT to send email.

*----------------------------------------------------------------------*

FORM initiate_mail_execute_program.

WAIT UP TO 2 SECONDS.

SUBMIT rsconn01 WITH mode = 'INT'

WITH output = 'X'

AND RETURN.

ENDFORM. " INITIATE_MAIL_EXECUTE_PROGRAM

*&---------------------------------------------------------------------*

*& Form POPULATE_EMAIL_MESSAGE_BODY

*&---------------------------------------------------------------------*

* Populate message body text

*----------------------------------------------------------------------*

form populate_email_message_body.

REFRESH it_message.

it_message = 'Please find attached a list test ekpo records'.

APPEND it_message.

endform. " POPULATE_EMAIL_MESSAGE_BODY

Treasury and Cash(TR) Tutorials

2007-09-08T19:25:00.001+05:30

TR - Cash Budget Management
Treasury (TR)
Treasury (TR)
Treasury - Changeover to the Euro
Treasury Workstation
TR - Treasury: Workflow Scenarios

Financial(FI) Tutorials

2007-09-08T19:25:00.000+05:30

FI Accounts Receivable and Accounts Payable
Financial Accounting (FI)
Financial Accounting (FI)
Financial Accounting - General Topics
FI Financial Accounting: Data Transfer Workbench
Financial Information System (FI)
FI/SD - Credit Management/Risk Management
FI - Special Purpose Ledger
Flexible General Ledger (FI-GL)
Forecasting (LO-PR)
Foreign Exchange
Foreign Trade / Customs (SD-FT) Funds Management
Payments
Payments
Payments
Payment Card Processing
Payment Program for Payment Requests (FI-BL)
Payment Release Pension Fund CH: Reference Guide
Pension Fund CH: Technical User Handbook
Pension Fund CH: User Hand Book
Transfer of Legacy Assets to the R/3 System Consolidation (EC-CS)
Consolidation (FI-LC)
Preparations for Consolidation (FI)
HR Funds and Position Management (PA-PM)
Funds Management
Flexible General Ledger (FI-GL)
General Ledger Accounting (FI-GL)
Travel Management (FI-TV)
General Ledger Accounting (FI-GL)

Human Resources ( HR ) Tutorial

2007-09-08T19:21:00.000+05:30

Human Resources (HR)
Human Resources (HR)
HR Form Editor (PY-XX-TL)
HR Forms Workplace (PY-XX-FO)
HR Funds and Position Management (PA-PM)
HR - Human Resource Management
HR Infotypes
HR Tools (PY-XX-TL)
Master Data Distribution (Human Resources)
Wage and Salary Payments
Wage Type Distribution
Wage Type Reporter (H99CWTR0)
Wage Type Statement Wage Types
Reporting in Human Resource Management
Report Programming in HR
Training and Event Management Payroll Account (Report RPCKTOx0;HxxCKTO0)
Payroll Argentina (PY-AR)
Payroll Australia (PY-AU) Payroll Austria (PY-AT)
Payroll Basics (PY-XX-BS) Payroll Belgium (PY-BE)
Payroll Brazil (PY-BR)
Payroll Canada(PY-CA)
Payroll Denmark (PY-DK)
Payroll France (PY-FR)
Payroll Germany (PY-DE)
Payroll Great Britain (PY-GB)
Payroll Hong Kong (PY-HK)
Payroll in a Background Operation
Payroll Indonesia (PY-ID)
Payroll in the SAP System
Payroll Ireland (PY-IE)
Payroll Italy (PY-IT)
Payroll Japan (PY-JP)
Payroll Journal (Report RPCLJNx0;HxxCLJN0)
Payroll Malaysia (PY-MY)
Payroll Mexico (PY-MX)
Payroll New Zealand (PY-NZ)
Payroll Philippines (PY-PH)
Payroll Portugal (PY-PT)
Payroll Singapore (PY-SG)
Payroll Spain (PY-ES)
Payroll Sweden (PY-SE)
Payroll Taiwan (PY-TW)
Payroll Thailand (PY-TH)
Payroll United States (PY-US)
Payroll Venezuela (PY-VE)
Payroll South Africa (PY-ZA)
Payroll Switzerland (PY-CH)

Project Systems (PS) Tutorial

2007-09-08T19:19:00.000+05:30

Decentralized Warehouse Management (LE-IDW)
SAP Open Information Warehouse
Warehouse Management Guide

Plant Maintenace(PM) Tutorial

2007-09-08T19:17:00.000+05:30

Plant Maintenance
Plant Maintenance and Customer Service (PM/CS)
PM/CS - Data Transfer in Plant Maintenance and Customer Service
PM/CS - Plant Maintenance & Customer Service: Workflow Scenarios
QM/PM Partner Roles
Capacity Planning in Customer Service and Plant

Warehouse Management(WM) Tutorial

2007-09-08T19:16:00.000+05:30

Decentralized Warehouse Management (LE-IDW)
SAP Open Information Warehouse
Warehouse Management Guide

Quality Management(QM) Tutorial

2007-09-08T19:14:00.000+05:30

Quality Certificates
Quality Management
Quality Management (QM)
Quality Management (QM)
Quality Notifications
Quality-Related Costs (QM-IM-IC)
Question & Answer Database
QM in Procurement (QM-PT-RP-PR)
QM in Production
QM in Sales and Distribution (QM-PT-RP-SD)
QM/PM Partner Roles
QM - Quality Management: Data Transfer
QM - Quality Management: Workflow Scenarios

Production Planning ( PP ) Tutorial

2007-09-08T19:01:00.000+05:30

Sales Distribution (SD ) Module

2007-09-08T19:00:00.000+05:30

Sales (SD-SLS)
Sales and Distribution (SD)
Sales and Distribution (SD)
Sales and Distribution
Sales and Distribution (SD) Workflow Scenarios
Sales and Operations Planning (LO-LIS-PLN)
Sales Employee (PA-PA)
Sales Support: Computer-Aided Selling (CAS)
Reports and Analyses (SD)
Pricing and Conditions
Shipping

Material Management ( MM )Tutorial

2007-09-08T18:56:00.000+05:30

Material
Materials Management (MM)
Materials Management (MM)
Material Master
Material Requirements Planning
MM Component Short Description
MM Materials Management
MM - Materials Management: Workflow Scenarios
MM - Material Price Change (MM-IV-MP)
MM MM-MOB and WM-LSR Interfaces
MM Vendor Evaluation
Dangerous Goods Management (EHS-DGP)
Goods Receipt Process for Inbound Deliveries
Inventory Management and Physical Inventory
Inventory Sampling (MM-IM-PI) Order BOMs

Details information about SAP Barcodes

2007-09-03T22:38:00.001+05:30

A barcode solution consists of the following:
- a barcode printer
- a barcode reader
- a mobile data collection application/program

A barcode label is a special symbology to represent human readable information such as a material number or batch number
in machine readable format.

There are different symbologies for different applications and different industries. Luckily, you need not worry to much about that as the logistics supply chain has mostly standardized on 3 of 9 and 128 barcode symbologies - which all barcode readers support and which SAP support natively in it's printing protocols.

You can print barcodes from SAP by modifying an existing output form.

Behind every output form is a print program that collects all the data and then pass it to the form. The form contains the layout as well as the font, line and paragraph formats. These forms are designed using SAPScript (a very easy but frustratingly simplistic form format language) or SmartForms that is more of a graphical form design tool.

Barcodes are nothing more than a font definition and is part of the style sheet associated with a particular SAPScript form. The most important aspect is to place a parameter in the line of the form that points to the data element that you want to represent as barcode on the form, i.e. material number. Next you need to set the font for that parameter value to one of the supported barcode symbologies.

The next part of the equation can be a bit tricky as you will need to get a printer to print that barcode font. Regular laser printers does not normally print barcode fonts, only specialized industrial printers that is specifically designed to support that protocol and that uses specialized label media and heat transfer (resin) ribbon to create the sharp image required for barcodes.

Not to fear though, there are two ways to get around this:
- You can have your IT department do some research -
most laser printers can accept a font cartridge/dimm chip (similar to computer memory), called a BarDIMM that will allow a laser printer to support the printing of barcodes.
- Secondly, you can buy software that you can upload in your SAP print Server that will convert the barcode symbology as an image that will print on a regular laser printer. I found that this option results in less sharper barcodes. This option is really if you need to convert a large quantity of printers (>10) to support barcodes.

Now you have a barcode printed - what next?
Well there are two options, depending on your business requirements:
- You can use an existing SAP transaction on a regular workstation and get a barcode wedge reader to hook up between the keyboard and the PC. These wedge readers comes in a wand or scanner format. There are even wireless wedge scanners available that allows you to roam a few yards from the workstation to scan a label. This approach is mostly used where you want to prevent human errors in typing in long material, batch or serial numbers in receiving or issuing of material. The problem is that it's just replacing the keyboard input and you are basically locked down in one location and have to bring all the material to that location to process.
- Another solution is to use SAPConsole transactions
or write your own ABAP Dialog programs that will fit onto a barcode enabled wireless handheld terminal and that will follow the business logic as executed on the shop floor.

These programs are highly complex exercises in industrial engineering and ergonomics because of the limited screen sizes and limited ability to accept keyboard input. The user is instructed step-by-step and only scan and push F-keys to interact with the SAP system. Scan, scan, beep, beep, enter - highly automated.

What is SAP Smart Forms?
Advantages of SAP Smart Forms
A Simple Smartform Tutorial
Difference with SMARTFORMS vs. SapScript(SE71)
FAQ on Migrating SAPscript to SmartForms
Conversion of SAPSCRIPT to SMARTFORMS
SmartForms System Fields
Example Forms Available in Standard SAP R/3
Smart forms Frequently Asked Questions