Sorting before get logical database

Hi,
I would like to know any way to apply sorting before get logical database?
for e.g.
GET regup.
   PERFORM extract.
   IF reguh-zbukr NE regup-bukrs.
     tab_uebergreifend-zbukr = reguh-zbukr.
     tab_uebergreifend-vblnr = reguh-vblnr.
     COLLECT tab_uebergreifend.
   ENDIF.
END-OF-SELECTION.
I need to sort regup before GET regup which before it trigger for each line.
Thanks.

Hi,
Instead of going for a sort before GET statement, you can move the required fields into an internal table first and sort that table and use it for your processing.
A small eg:
GET bkpf.
MOVE:bkpf-bukrs TO tb_bkpf-bukrs,
             bkpf-budat TO tb_bkpf-budat,
             bkpf-belnr TO tb_bkpf-belnr.
      APPEND tb_bkpf.
      CLEAR tb_bkpf.
Please revert back for any further queries.
Regards,
Chandra.

Similar Messages

GET (logical database)

Hi experts,
I have a get statement with logical database,
when it is executed, it should go to END-OF-SELECTION. But it goes to GET statement again. Why is it happening? Do anybody have explanation about it?

hi,
Get statement functions as loop and endloop statement .... and comes out of it only when it sees any exit statement after executing that statement ....For more information check out
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/get_.htm
Regards,
Santosh

What are structures of logical database.

hi
what are structures of logical database.

Dear Chaitanya,
The structure of LDB can be divided into three sections:
>Structure
>Selection
>Database Program
STRUCTURE:
The structure defines the data view of the logical database. It adopts the hierarchy of the database tables defined by their foreign key relationships. This also controls the sequence in which the tables are accessed. It determines the structure of the other components and the behavior of the logical database at runtime.
The structure of a logical database is usually based on the foreign key relationships between hierarchical tables in the SAP System. Logical databases have a tree-like structure, which can be defined as follows:
· There is a single node at the highest level. This is known as the root node.
· Each node can have one or several branches.
· Each node is derived from one other node.
The nodes must be structures defined in the ABAP Dictionary or data types from a type group. Normally, these are the structures of database tables which the logical database reads and passes to the user for further evaluation. However, it is also possible, and sometimes useful, to use ABAP Dictionary structures without an underlying database. For technical reasons, the maximum number of nodes allowed in the structure of a logical database is 300.
Any executable ABAP program that has a logical database linked to it can contain a GET statement for each node of the structure. When you run the program, the corresponding event blocks are processed in the sequence prescribed by the hierarchical structure of the logical database. If a program does not contain a GET statement for every node of a logical database, the processing passes through all the nodes that lie in the path from the root to the nodes specified by GET statements.
If you call a logical database using the function module LDB_PROCESS, the depth to which the system reads is controlled by an interface parameter.
SELECTIONS:
The selections define a selection screen, which forms the user interface of the executable programs that use the logical database. Its layout is usually determined by the structure. You can adapt the selections to your own requirements and also add new ones. When you link a logical database to an executable program, the selections of the logical database become part of the standard selection screen of the program (screen number 1000). If you call a logical database using the function module LDB_PROCESS, the selections are filled using interface parameters.
The selections in a logical database are defined using the normal statements for defining selection screens, that is, PARAMETERS, SELECT-OPTIONS and SELECTION-SCREEN. In a logical database, you can also use the additions VALUE-REQUEST and HELP-REQUEST to define specific input and value help. You define the selection screen in a special include program known as the selection include.
When you write programs using a logical database, you can also add your own program specific selections. The standard selection screen then contains the database-specific selections, followed by the program-specific selections that you have defined.
When the system generates the selection screen for an executable program, database-specific selection criteria and parameters are only displayed if you have declared an interface work area for them in your program using the NODES or TABLES statement.
Suppose you have a selection include containing the following lines:
SELECT-OPTIONS slifnr FOR lfa1-lifnr.
PARAMETERS pbukrs LIKE lfb1-bukrs FOR TABLE lfb1.
The selection criterion SLIFNR is linked to table LFA1, the parameter PBUKRS to table LFB1. If the TABLES statement in an executable program (report) declares LFA1 but not LFB1, SLIFNR is displayed on the selection screen, but PBUKRS does not appear.
The selection screen of a logical database can contain dynamic selections as well as static ones. Dynamic selections are extra, user-defined selections that the user can make as well as using the static selections defined in the selection include. To improve performance, you should always use this option instead of reading more data than you need and then sorting it out in the application program.
To make dynamic selections available for the node nodeof a logical database, the selection include must contain the following statement:
SELECTION-SCREEN DYNAMIC SELECTIONS FOR NODE|TABLE node.
If the node node is requested by the user of the logical databases, the dynamic selections are included in the selection screen. A user can then choose Dynamic selections to enter extra selections for the corresponding fields. If you call the logical database using the function module LDB_PROCESS, you can pass a corresponding parameter. You can use these selections in dynamic statements in the logical database program to read data. The values of the program-specific selection criteria that you defined for a node for which dynamic selections were available are also passed to the logical database. The user can also define the fields for dynamic selections as a selection view for the logical database.
The selection screen of a logical database is part of the standard selection screen (number 1000) of the executable program to which the logical database is attached. It has a standardized layout - the selection criteria and parameters appear on separate lines in the order in which they were declared. You can change the layout using the SELECTION-SCREENstatement.
The runtime environment generates the selection screen with number 1000 for every program in which the attributes do not contain a different selection screen version. You can prevent certain input fields from the selection screen of a logical database from appearing on the selection screen by defining selection screen versions with a screen number lower than 1000 in the selection include, and entering this version number in the program attributes. By pressing F4 there, you can get an overview of the selection screen versions defined in the logical database concerned. To define a selection screen version, use the statements SELECTION-SCREEN BEGIN|END OF VERSION. Within these statements you can use SELECTION-SCREEN EXCLUDEto specify fields that you do not want to appear on the selection screen.
If the attributes of an executable program contain the number of a selection screen version, the version is used in the standard selection screen. Although the input fields that you excluded from the selection screen are not displayed, the corresponding selections still exist, and you can still edit them in the program or by calling the function module LDB_PROCESS.
DATABASE PROGRAM:
The database program contains the ABAP statements used to read the data and pass it to the user of the logical database. There is a container for special subroutines into which, amongst other things, the data from the database tables is read. These subroutines are called by the reporting processor in the runtime environment in a sequence that has been predefined by the structure. The database program is determined by the structure and selections and can be adapted or expanded to meet your requirements.
The name of the database program of a logical database ldbconforms to the naming convention SAPDBldb. It serves as a container for subroutines, which the ABAP runtime environment calls when a logical database is processed. The sequence of the calls and their interaction with the events in executable programs or the function module LDB_PROCESS depends on the structure of the logical database.
A logical database program usually contains the following subroutines:
· FORM LDB_PROCESS_INIT
Called once only before the logical database is processed. It prepares it to be called more than once by the function module LDB_PROCESS.
· FORM INIT
Called once only before the selection screen is processed.
· FORM PBO
Called before the selection screen is displayed, each time it is displayed. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS.
· FORM PAI
Called when the user interacts with the selection screen. Consequently, it is only called when you use the logical database with an executable program, not with the function module LDB_PROCESS. The interface parameters FNAME and MARK are passed to the subroutine.
FNAME contains the name of a selection criterion or parameter on the selection screen.
MARK describes the selection made by the user: MARK = space means that the user has entered a simple single value or range selection. MARK = '*' means that the user has also made entries on the Multiple Selection screen.
· FORM LDB_PROCESS_CHECK_SELECTIONS
Called instead of the subroutine PAI if the logical database is called using the function module LDB_PROCESS without a selection screen. This subroutine can check the selections passed in the function module interface.
· FORM PUT_node
Called in the sequence defined in the structure. Reads the data from the node nodeand uses the
PUT node.
statement to trigger a corresponding GETevent in the ABAP runtime environment. The PUT statement is the central statement in this subroutine: It can only be used within a subroutine of a logical database. The logical database must contain the node node, and the subroutine name must begin with PUT_node. The PUT statement directs the program flow according to the structure of the logical database. The depth to which the logical database is read is determined by the GET statements in the application program or the interface parameter CALLBACK of the function module LDB_PROCESS.
First, the subroutine PUT_root is executed for the root node. The PUT statement then directs the program flow as follows:
i. If the database program contains the subroutine AUTHORITY_CHECK_node, the first thing the PUT_node statement does is to call it.
ii. Next, the PUT statement triggers a GET event in the runtime environment. If there is a corresponding GET nodestatement in the executable program to which the logical database is linked, the associated event block is processed. If the CALLBACK parameter of the function module LDB_PROCESS is filled accordingly, the corresponding callback routine is called.
iii. The PUT statement directs the program flow
(a) To the next subroutine of a node that follows directly, if a lower-level node (not necessarily the very next) in the same subtree is requested by GET in the executable program or in the function module.
(b) To the subroutine of a node at the same level, if the preceding node branches to such a node and if a GET statement exists for such a node in the executable program or the function module.
The PUT statement in that subroutine starts again at step (i). In the subroutine of the lowest node in a subtree to be processed using GET, the program control does not branch further. Instead, the current subroutine is processed further. When a subroutine PUT_node has been executed in its entirety, the program flow returns to the PUTstatement from which it branched to the subroutine PUT_node.
iv. When control has returned from a lower-level subroutine PUT_node, the PUTstatement triggers the event GET node LATEin the runtime environment.
· FORM AUTHORITY_CHECK_node
Called automatically by the PUT node statement. In this subroutine, you can specify authorization checks for the appropriate node node from the structure of the logical database.
· FORM PUT_ldb_SP
Called when the user makes a selection using a search help to process the key chosen in the search help. ldb is the name of the logical database. From this subroutine, you can use the entries in the search help tables to read the relevant entries from the root node root. The processing in the program can then be triggered using PUT root. The subroutine PUT_root is then not called automatically.
· FORM BEFORE_EVENT
Called before an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value START-OF-SELECTION, to call a subroutine before this event.
· FORM AFTER_EVENT
Called after an event, the name of which is passed in the parameter EVENT. Currently, the EVENT field can only contain the value END-OF-SELECTION, to call a subroutine after this event.
· FORM par_VAL, selop_VAL, selop-LOW_VAL, selop-HIGH_VAL
Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
· FORM par_HLP, selop_HLP, selop-LOW_HLP, selop-HIGH_HLP
Called when the user calls possible values help for the parameter par or the selection criterion selop. These must belong to the selections in the logical database.
Example
Suppose that in the logical database structure, LFB1 is a branch of LFA1.
and that the following selection criteria are defined in the selection include:
SELECT-OPTIONS: slifnr FOR lfa1-lifnr,
sbukrs FOR lfb1-bukrs.
A section of the database program would then read:
FORM put_lfa1.
SELECT * FROM lfa1
WHERE lifnr IN slifnr.
PUT lfa1.
ENDSELECT.
ENDFORM.
FORM put_lfb1.
SELECT * FROM lfb1
WHERE lifnr = lfa1-lifnr.
AND bukrs IN sbukrs.
PUT lfb1.
ENDSELECT.
ENDFORM.
An executable program (report) linked to the logical database could contain the lines:
GET lfa1.
WRITE lfa1-lifnr.
GET lfb1.
WRITE lfb1-bukrs.
In this example, the runtime environment calls the routine put_lfa1 after the event START-OF-SELECTION. The event GET lfa1 is triggered by the statement PUT lfa1.
Once the corresponding event block in the program is complete, PUT lfa1 branches to the subroutine put_lfb1.
From this subroutine, the event GET lfb1 is triggered in the application program. If LFB1 is the last node to be read, processing resumes with the SELECTloop in put_lfb1. Otherwise, the program flow moves to the subroutine put_node of the next node. At the end of the SELECT loop of the last node, processing resumes in the SELECTloop of the node at the next level up. The example of programming using nested SELECT loops is only used to make the program flow clearer. In a real logical database, you would avoid doing this in order to minimize the number of database accesses.
Regards,
Rajesh K Soman
Please reward points if helpful.

Problem about logical database programming

Dear all,
I have a logical database PRPS_R which contail PRPS and some additional fields.
In my abap report, I call this logical database by "GET PRPS_R". Can I ask how to perform sorting to the logical database in ABAP report?
Thanks
Sunny

PRPS_R is a structure of logical database PSJ
there is a user-exit available EXIT_FDBPS000_001

Logical Database-GET-LOOP.

Hi,
I am debugging a standard code where PYF logical database is used.
START-OF-SELECTION.
GET REGUH.
CHECK SEL_ZAWE.
CHECK SEL_UZAW.
CHECK SEL_HBKI.
CHECK SEL_HKTI.
CHECK SEL_WAER.
CHECK SEL_VBLN.
PERFORM PRUEFUNG.
PERFORM EXTRACT_VORBEREITUNG.
PERFORM SORTBANK.
GET REGUP.
PERFORM SORTBOLETO.
PERFORM EXTRACT.
END-OF-SELECTION.
SORT BY
    REGUH-ZBUKR
    REGUH-UBNKS
    REGUH-UBNKY
    REGUH-UBNKL
    REGUH-UBKNT
    REGUD-XEINZ
    REGUH-ZBNKS
    REGUH-ZBNKY
    REGUH-ZBNKL
    REGUH-ZBNKN
    REGUH-LIFNR
    REGUH-KUNNR
    REGUH-EMPFG
    REGUH-VBLNR
    REGUP-BELNR.
LOOP.
AT END OF REGUH-VBLNR.
ENDAT.
ENDLOOP.
Can anyone here please let me know
1.whether it is looping on REGUH or REGUP.Is it on REGUH ?
2.How to see the records in debugging for this loop.
I mean as in internal table where we will get to see all the records that it is looping (loop at itab..endloop),how to see
all the records that are considered for this loop in debugging.
3.Does it loops both REGUH and REGUP ?
Thanks,
K.Kiran.

INSERT
reguh
regup
regud-gjahr
regud-xabwz
INTO daten.
this create a structure (field group) for DATEN with every fields of reguh and regup, and two fields of regud.
EXTRACT daten.
move current values of the above mentionned structures to the group field and append it into the extract.
LOOP.
ENDLOOP.
will read the extract, here DATEN, so in each loop the whole data of the above mentionned structures will be available.
There are also SORT and AT options similar to those of internal tables, and a AT field_group when multiple structures were defined by INSERT statements.
Read some documentation at [Extracts|http://help.sap.com/abapdocu_70/en/ABENABAP_EXTRACTS_EXTENDED.htm]
Regards,
Raymond

Sort+logical database using field group and extract

Hi Folks,
I have a program which is using Logical database concept and creating a file on application server as below.
SORT BY
    reguh-zbukr                        "Zahlender Buchungskreis
    reguh-rzawe                        "Payment method
    reguh-ubnks                        "Bankland unserer Bank
    reguh-ubnky                        "Bankkey zur Übersortierung
    reguh-ubnkl                        "Bankleitzahl unserer Bank
    reguh-ubknt                        "Kontonummer bei unserer Bank
    payment_form                       "Brazil: CC, DOC or OP
    regud-xeinz                        "X - Lastschrift
    reguh-zbnks                        "Bankland Zahlungsempfänger
    reguh-zbnky                        "Bankkey zur Übersortierung
    reguh-zbnkl                        "Bankleitzahl Zahlungsempfänger
    reguh-zbnkn                        "Bank-Ktonummer Zahlungsempfänger
    reguh-lifnr                        "Kreditorennummer
    reguh-kunnr                        "Debitorennummer
    reguh-empfg                        "Zahlungsempfänger CPD
    reguh-vblnr                        "Zahlungsbelegnummer
    regup-belnr.
LOOP.
AT NEW reguh-rzawe
PERFORM store_on_file USING j_1bh1.
ENDAT
AT NEW reguh-ubnkl
PERFORM store_on_file USING j_1bh2.
ENDAT
AT NEW reguh-ubnkt
PERFORM store_on_file USING j_1bh2.
ENDAT
AT NEW VBLNR
PERFORM store_on_file USING j_1bh3.
AT DATEN
PERFORM store_on_file USING j_1bh4.
ENDAT.
ENDLOOP.
FORM store_on_file USING daten.
IF hlp_temse CA par_dtyp.            "Temse
    PERFORM temse_schreiben USING daten.
ELSE.
    TRANSFER daten TO g_name.
ENDIF.
ENDFORM.
Is Sorting concept different when it comes to logical databases and field groups ?
I had added a new field in the sort reguh-rzawe.I think due to that it is getting into AT NEW UBNKL and AT NEW UBKNT even though those details are same for the payment methods in the payment run.Even though the house bank number and account number is same for all the payment methods it is getting into AT NEW UBNKL and AT NEW UBKNT for every new payment method in the iteration.
vblnr-1
rzawe- A
ubnkl-12345
ubnkt-45678
vblnr-2
rzawe- A
ubnkl-12345
ubnkt-45678
vblnr-3
rzawe- B
ubnkl-12345
ubnkt-45678
vblnr-4
rzawe- B
ubnkl-12345
ubnkt-45678
Can anyone here throw some light on this.
Thanks,
K.Kiran.

Read the documentation for the at-new process. As I recall the at-new considers the field named, and all the fields to the left of that in the table. With that in mind, look at how your logic will work. This could result in more, or fewer, breaks than intended(fewer if, for instance, a field to the left was deleted).

Logical Database DDF - GET KNA1 - change KUNNR to another customer....

Hi
Question 1a:
When using logical database DDF I perform a GET KNA1 a check is performed in order to see if customer should be within selection or not. In some cases this customer refers to another customer (fiscal address) that should be used instead.
So Customer KNA1-KUNNR: 123 should instead be Customer 456 which contains the relevant data for the next step in the selections from the logical database.
..GET KNB1
..GET BSID...
How is it possible to replace customer 123 with customer 456 so the continous processing of the logical database will use the new customer number instead.
Question 1b
And a follow up question - If there is a solution to question above....
How can I make sure that IF customer 456 pops up in the regular selection from the logical database - It is excluded since it was already used (when customer 123 was replaced with 456 above)...
Best regards
Henrik

Hi Ranganath!
Thankyou for looking into my problem.
Ranganath Ramesh wrote:
...If you want to do something like that then you need to manually populate the customer numbers which are related to the selection screen field....
Could you please clarify how I manually could add this new customer number to my selection screen field...whithout disturbing the origianal selection with GET KNA1 - at the same time as the CHECK-statement for my old customer number fails and is excluded from the selection.
BR
Henrik

How to get the selection parameters from logical database into one of the t

Hi Sap ABAP Champians,
How to get the selection parameters from logical database into one of the tab in the tabstrip selection-screen.
Please help me for this
Thanks
Basu

Hi
Thanks, that will work, but then I'll have to insert code into all my reports.
I can see that "Application Server Control Console" is able to rerun a report.
This must mean that the Report Server has access to the runtime parameters.
But how?
Cheers
Nils Peter

Not getting fields in logical database of infotypes

Hi All,
I have created Infotype(9xxx) through PM01, and also maintained the screen for this with 6 feilds..
BEGDA, ENDDA, SUBTY, OBJPS, Zxxx1, Zxxx2
every thing is going fine but when im creating logical database for that infotype,
im getting only 3 feilds there
PERNR
Zxxx1
Zxxx2
I need to take all the fields there.. please suggest how to do this?
Regards
Neha Gupta

Solved on own.

Get mapl gives ' mapl not defined in the current logical database'.

Hello,
i am going through the report RCPDRK00, i found a statement get plkod , get mapl .
When i try to run this statement in my test program it says ' not defined in the curent logical database' .
How to link with logical database.
regards,
kevin.

GET statements will provide your program with database records based on the code for the logical database. The program in this case is SAPDBPNM.
Each GET will be supplied with data by the corresponding PUT subroutine.
Read the help about the logical databases. This is considered obsolete technology, but still, they can be very useful.
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/9f/db9b5e35c111d1829f0000e829fbfe/frameset.htm

How to extract current record using get pernr (logical database)

Hi all,
I am using logical database in the program and using <b>get pernr</b> method. But there are multiple entries in the infotype for a perticular employee. i want to extract employees current record whose end date is greater than sy-datum.
how to do this using <b>get pernr</b>?
Thanks in advance.

Hi Priti,
Get Pernr statement will get all the records for each employee spcicified for the Begin and End dates on the selection screen and store in an internal table for the infotypes declared in the infotypes statement.
You need to read this table and copy only the records that meet the date criteria in an internal table for further use.
For Ex:
infotypes : 0001.
tables : pernr.
TYPES : BEGIN OF ty_kostl,
         pernr TYPE pernr-pernr,
         kostl TYPE p0001-kostl,
         ename TYPE p0001-ename,
        END   OF ty_kostl.
Work Areas
DATA : g_kostl_wa TYPE ty_kostl.
Internal Tables
DATA : i_kostl TYPE TABLE OF ty_kostl.
start-of-selection.
   get pernr.
   PROVIDE * FROM p0001 BETWEEN pn-begda AND pn-endda.
    if p0001-endda GT sy-datum.
       g_kostl_wa-pernr = p0001-pernr.
       g_kostl_wa-kostl = p0001-kostl.
       g_kostl_wa-ename = p0001-ename.
       APPEND g_kostl_wa TO i_kostl.
       CLEAR g_kostl_wa.
    endif.
ENDPROVIDE.

How do I get Logic Pro X to see my USB audio interface Steinberg UR22? It saw it once before but now it doesn't.

How do I get Logic Pro X to see my USB audio interface Steinberg UR22? It saw it once before but now it doesn't. In preferences it doesn't appear as an input device option. Help!

First, go to System Preferences for OS X and verify that the operating system can see it.

Getting results from LDB (Logical Database)

Hi All,
I have a requirement where i need to pass LDB results to external application. It can be any LDB. Like in SE36 we put the LDB name and execute and final results are shown in ALV. I dont need it to display in ALV but from my custom program, need that output table which stores these results.
I tried using LDB_PROCESS but that need custom subroutine names to pass in that, i tried passing the same and results also came but thing is every logical database will have different tables in that, it'll be impossible to create those many subroutine to handle each and every table. So i need a generalized solution like se36 processes the data for any LDB.
Is anyone knows how can i achieve this?
Regards
Munish Garg
9041793217

Hello
Generally any LDB will have a event which triggers the data to be populated in the tables/memory. Now these data retrieval is written in a sub-routine "Perform PUT_<eventnamt>". So any LDB will have the sub-routine named "PUT_<eventname>" in its main program. May be you can create the sub-routine name dynamically using this method.
Regards
Ranganath

Usage of GET - Basic LOGICAL database question

Hi,
I have a few doubts in Logical Databases.
1.) Why should i include a logical database in a abap program.
2.) Can i add more than 1 LDB to a abap program
3.) can Nodes statement used on all nodes on LDB
4.) Please provide a example program based on F1S LDB with small explanation.
Thanks in advance,
Bala.

>
Bala Shanmuga Priyan wrote:
> Thank you all.
>
> What is the difference between tables and nodes statement,
>
> Thanks in advance,
> Bala.
AFAIK, it is expected that we should we the TABLES statement if the node type is a TABLE and if the node type is DDIC type then it is expected that we should use NODES statement, however I found that they can be used interchangeably.
We can find the node type info in the structure defintion of the LDB(in SE36)
Also check this extract from the SAP help
The nodes of the structure are declared with the TABLES statement which generates
the appropriate table work areas. You can also use the NODES statement to define
database tables as nodes. If a node of a logical database is not a database table,
you must use the NODES statement.
[Example of a Logical Database |http://help.sap.com/saphelp_47x200/helpdata/en/9f/db9be035c111d1829f0000e829fbfe/content.htm]

Logical Database PNP couldn't work

Hi all, I have the following code but it didn't work.
TABLES: pernr.
INFOTYPES: 0002. "Personal Data
data i_personaldata like p0002 OCCURS 0 WITH HEADER LINE.
SELECT-OPTIONS: language FOR p0002-sprsl.
*-- Selection screen
*-- Processing
GET PERNR.
rp_provide_from_last p0002 space pn-begda pn-endda.
IF pnp-sw-found EQ 0.
    WRITE: 'no record found'.
ELSE.
    CHECK language.
    WRITE: / p0002-pernr,
    sy-vline,
    pernr-ename,
    sy-vline,
    p0002-sprsl,
    sy-vline,
    p0002-gbdat.
ENDIF.
When I try to compile the program, the program is syntatically correct and the selection screen of the logical database works. But when I press execute, the program won't generate any result and the screen won't change.
I tried to debug the program. But the program couldn't get into the Get PERNR event.
My friend tried to run this program in another system and it works.
Anybody knows what could be the problem?

The event sequence in your program is incorrect. The correct sequence is
INFOTYPES: ...
START-OF-SELECTION.
"processing before fetching data
GET PERNR.
"process fetched data
END-OF-SELECTION. " mandatory
"process all the fetched data and display

Sorting before get logical database

Similar Messages

Maybe you are looking for