List processing and PF status.

Hi Team ABAP,
i got a problem in List processing.
I´m in a dypro with a table control on it. Users can mark one or more ALV lines and then e.G. press "process".
Something gets done then (some forms get printed), and after that i want to display a protocol.
First i tried to process a simple write list by using WRITE statement.
Coding got processed, but it had no effect, no write list was generated, or at least not shown on my screen.
So i tried to code a "LEAVE TO LIST PROCESSING" right before my first WRITE statement.
Well, now it works my write list is on Screen. But here start the Problem. Like i got told in the ducomentation of the LEAVE TO LIST PROCESSING statement the WRITE list gets processed with the actual active PF status from the dynpro where i came from.
1. This is quite uncool, since i do not need those Buttons in my List.
2. Even if it was ok, those buttons are not working. Typing /h in OK_CODE field and pressing ENTER doesnt help it. When after that i click a button, nothing happens, such as if i didnt click them.
I searched the forum, but i got drowned in thousands of "interactive list" threads and wasnt able to find my required info in an acceptable time of 30 minutes.
Did i do a essential error? Someone got an Idea where i´m stuck or a proposal on how to improve?
Any Help or tip will be welcome and rewared accordingly.
regards

Hi Florian,
Try if you can display the list in ALV where you can maintain the pf-status.
You can check the demo program DEMO_LEAVE_TO_LIST_PROCESSING. In this, it is setting set pf-status to space.
Hope it helps.
Sujay

Similar Messages

ALV grid to list processing and GUI status

Hi,
In a customized program the report output is in ALV grid which is interactive. On selecting a record and pressing SAVE button a BAPI runs in background. In order to display BAPI error message the leave to list-processing has been used. But GUI status is not working in list display and can not exit or go back from here to main selection screen.
when try to see program name & screen no it displays
Program - SAPLKKBL
Menu - STANDARD_FULLSCREEN
pls advise how to go back from list to main screen or ALV output.
thanks
anya

Hi Anya,
As per my understanding, this is your prog flow:
*Main ALV Display.
*Select record.
*Click on Button SAVE.
*Handle Event.
*Call BAPI for processing based on selection.
Now at this point why dont you colect the error messages from the BAPI, and display it in a POP-UP ALV display?
You need not e very much worried about the PF status and all. Also this POP-UP will be placed on the MAIN ALV. So when you close the POP-UP it will come back to the main ALV.
By this when you press the BACK button of the main ALV, it will take you back to the selection scree.
Please let me know if i am missing something.
ags

Problem facing in ALV to List processing and back to ALV

HI all,
In ALV USER_COMMAND i have inserted statement 'LEAVE TO LIST-PROCESSING'. I want to display records on List processor (Classical report) which are selected from ALV.
Due to LEAVE TO LIST-PROCESSING i can see Classical report but from here i am not able to come back on ALV screen...even not on any screen because BACK button on GUI-Status is not working.
From List Status i can see same GUI status which i gave to ALV.
also i have tried giving LEAVE LIST PROCESSING but due to this though i get ALV back but i cant get List display.
Please direct how to move.
thanks,

hello~ try this
FORM alv_user_command USING r_ucomm LIKE sy-ucomm
                             rs_selfield TYPE slis_selfield.
CASE r_ucomm.
    WHEN 'ELOG'.
      call screen 100.
ENDCASE.
rs_selfield-refresh = 'X'.
ENDFORM.
screen 100 just need PBO Module
module LOG_DISPLAY output.
SET PF-STATUS space.
WRITE: / 'HELLO'.
LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
LEAVE SCREEN.
endmodule.

Problem with leave to list-processing and return to screen

Hi all,
I am designing a screen in which I have provided a pushbutton which will allow the user to upload (via BDC) the price list to VK11 transaction. And consequently, after upload the BDC message will be captured and displayed as an ALV list. for this, I am using leave to list-processing and return to screen 100 statement.
My problem is, when I return from the alv list screen by pressing back/any button the called screen 100 is displayed as a dialog window. but actually the screen 100 is a normal screen.
How can I rectify this problem?
Thanks,
Rajan

rajan,
i think the below link will clear your problem.
[http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9d2f35c111d1829f0000e829fbfe/frameset.htm]
Regards,
Venkat

Leave to list processing and retun to scren 100

Once output is generated in the list i want back to main screen .
How i will prceed
regards
jithen

This will end up current calling sequence (will proceed after CALL SCREEN XXX statement). So if no other CALLs were found the program will be finished, or will go back in selection screen.
LEAVE to LIST-PROCESSING and RETURN TO SCREEN 0.
This will go back to screen XXX, if main screen is 200.
LEAVE to LIST-PROCESSING and RETURN TO SCREEN 200. "when you choose BACK, screen 200 will be called (main screen)
Regards
Marcin

Processing and Released Status when we create a new Condition table

Hi all
I created a new condition table in M/03, and assigned one field to it, Generated and saved. Then added the condition table in the access sequence. There appeared two more lines below the field that i have assigned. One is Processing status and the other is released status, both are having green lights. what are these and what is its impact.
inputs will be highly appreciated
thanks

I myself could find the answer

Dialog Module and List Processing.

Hi All,
I am having a program in which after processing I get a basic list. Using PF-STATUS of the basic list a dialog module is called using 'CALL SCREEN' which accepts date and has exectue and cancel buttons on it.
What do I do to so that user when clicks on cancel button the dialog module disapperas and the original list processing is still seen.
Thanks,
DJ

Hi,
To pass control from the dialog processor to the list processor, you must include the following statement in one of the dialog modules:
LEAVE TO LIST-PROCESSING [AND RETURN TO SCREEN <nnnn>].
You can include this statement in either the PBO or the PAI event. Its effect is to start the list processor and display the basic list after the PAI processing of the current screen. The basic list contains any list output from all PBO and PAI modules that have been executed up to that point.
regads,
keerthi

Leave to List processing is not working

Hi all,
I am displaying data in separate window using Window stratin at '' ''
ending at '' ''.
in screen PBO.
SUPPRESS DIALOG.
LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
PERFORM output.
everything is working fine.but its not showing the whole output .
even if i scroll .
what am i did wrong...?

Hi,
Its my bad, i am using
CALL SCREEN 1000 STARTING AT 01 01
                   ENDING   AT 150 50.
MODULE status_1000 OUTPUT.
PERFORM include_exclude_function USING sy-dynnr.
SET PF-STATUS 'AAA' EXCLUDING fcodes.
SET TITLEBAR '1000'.
SUPPRESS DIALOG.
LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
PERFORM output.
ENDMODULE.                 " STATUS_8000 OUTPUT

Leave to list-processing doesn't work

Hi 2 all!
I have a problem with LEAVE TO LIST-PROCESSING. I have developed a module pool (type M) and screen with the screen painter of type Normal. Now I want to go to the report from my screen with LEAVE TO LIST-PROCESSING, but it doesn't work. I am trying to do this when the button is pressed ( at my application status). The operation is performed but then the Init_screen_xxxx module is called again. Highly appreciate your help.

Hi Nata
Yes U can do it.
We go from module pool program to report program and vice-versa.
1. From report to screen (transaction)
       Call transaction
      Leave to list-processing and return to screen
2. From screen to list (report)
         we can write a report program for fuction key available in the screen.
          for example.
    case sy-ucomm.
      when 'fctcode'.
       select .......... from tabl   into ..
    write:/.........,
endcase.
reward if useful.

Command leave to list processing

Dear All,
I have an executable program (execute via SE38) that need to call an additional screen for input before the actual output on sapscript.
It is like this, user key in the input into selection screen, then program will extract data and display them into a pop up window. User will further select data from the pop up, and then sapcript will be printed out eventually.
I'm now stuck at the pop up window. I created a new screen 9000 with screen type "Modal dialog box" and coding as follow:
Executable program:
CALL SCREEN 9000 STARTING AT 40 20
                   ENDING   AT 150 50.
Flow Logic:
PROCESS BEFORE OUTPUT.
MODULE STATUS_9000.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_9000.
Coding:
MODULE STATUS_9000 OUTPUT.
SUPPRESS DIALOG.
LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 9000.
SET PF-STATUS 'STATUS_9000'.
LOOP AT TAB INTO WA_TAB.
    WRITE:/1 WA_TAB-TYPE.
ENDLOOP.
ENDMODULE.                 " STATUS_9000 OUTPUT
MODULE USER_COMMAND_9000 INPUT.
OK_CODE = SY-UCOMM.
CASE OK_CODE.
    WHEN 'OK'.
******** trigger output to sapscript
    WHEN 'CANCEL'.
      SET SCREEN 0.
      LEAVE SCREEN.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_9000 INPUT
With the above code, output is successfully displayed on screen 9000 with command "Leave to list-processing". But after the list displayed, those buttons that defined in Status_9000 are not working at all in screen 9000. There is no response from any buttons i clicked, even i tried in debugging mode it didn't go in debugger as well.
Please comment which part i miss. Thanks.

Hi,
I think the problem is with your statement in the PBO module.
Why not try and delete this part 'AND RETURN TO SCREEN 9000'. Over here, if you want to use this addition RETURN TO SCREEN, then screen number should be other than your modal list screen. Currently you have changed the modal screen to behave as list, but at the same time, you want it to behave as the normal screen, after you come back from the list.
If you really need that, then please create another screen, say 9100, and change it to AND RETURN TO SCREEN 9100, instead of AND RETURN TO SCREEN 9000.
Regards,
Lim...

Call an other dynpro after list-process. with a button in the functionmenu

Hi expert-forum-members
in my report I start a DynPro after the starting-point "start-of-selection":
START-OF-SELECTION.
CALL SCREEN 100.
In the screen 100, I want to show a simple list like that:
module pbo_0100 output.
SET PF-STATUS 'SCREEN_100'.
LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
PERFORM lief_lfa1.
PERFORM kunden_kna1.
LEAVE SCREEN.
endmodule.
In the "PF-STATUS" I defined a button which should call another dynpro with a ALV-List. But when I am debugging the "list-processing" screen I could not catch any sy-ucomm event?!?
If I comment the two commands ("LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.","LEAVE SCREEN. LEAVE SCREEN.") out, then the buttonfunction is correct.
So how can I use a button by using the "LEAVE TO LIST-PROCESSING " command?
Regards,
Steffen

Hi Steffen,
The logic:
LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
PERFORM lief_lfa1.
PERFORM kunden_kna1.
LEAVE SCREEN.
shold be inside a PAI module an not PBO module.
pai.
module user_command_0100.
in program:
module user_comman_0100.
case sy-ucomm.
when '<Fcode for the button>'.
LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
PERFORM lief_lfa1.
PERFORM kunden_kna1.
LEAVE SCREEN.
endcase.
endmodule.
Regards,
Ravi

Leave list processing

hi to all sdn people
i know the functionality of the leave list processing
and leave to list processing . but tell how to use them in the screen programs ?pls give
one sample screen program .

LEAVE TO LIST-PROCESSING
Basic form 5
LEAVE TO LIST-PROCESSING.
Addition:
... AND RETURN TO SCREEN scr.
Effect
Switches from "dialog processing" (module pool, screens) of the current transaction to "list processing". You can then use all the usual list layout commands (WRITE, SKIP, ...).
After leaving the current screen, the list formatted in this way is displayed implicitly or explicitly by LEAVE SCREEN. Here, all list programming options are possible, e.g. line selection, F keys, windows.
LEAVE LIST-PROCESSING continues with "Processing Before Output" (PBO) of the screen which controls the list processing.
Note
After switching to list processing mode with SET PF-STATUS ..., you are recommended to define a GUI (Graphical User Interface) of type List or List in dialog box.
Please consult Data Area and Modularization Unit Organization documentation as well.
Addition
... AND RETURN TO SCREEN scr.
Effect
LEAVE LIST-PROCESSING continues with "Processing Before Output" (PBO) of the screen scr.
Note
Using LEAVE LIST-PROCESSING to leave list processing explicitly is only necessary in exceptional cases; normally, the standard F keys ( F3=Back and F15=Exit) are sufficient.
Refer the following code:
REPORT demo_leave_to_list_processing .
TABLES demo_conn.
DATA: wa_spfli TYPE spfli,
      flightdate TYPE sflight-fldate.
CALL SCREEN 100.
MODULE status_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE cancel INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE user_command_0100.
CALL SCREEN 500.
SET SCREEN 100.
ENDMODULE.
MODULE call_list_500 OUTPUT.
LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.
SET PF-STATUS space.
SUPPRESS DIALOG.
SELECT carrid connid cityfrom cityto
    FROM spfli
    INTO CORRESPONDING FIELDS OF wa_spfli
    WHERE carrid = demo_conn-carrid.
    WRITE: / wa_spfli-carrid, wa_spfli-connid,
             wa_spfli-cityfrom, wa_spfli-cityto.
    HIDE: wa_spfli-carrid, wa_spfli-connid.
ENDSELECT.
CLEAR: wa_spfli-carrid.
ENDMODULE.
TOP-OF-PAGE.
WRITE text-001 COLOR COL_HEADING.
ULINE.
TOP-OF-PAGE DURING LINE-SELECTION.
WRITE sy-lisel COLOR COL_HEADING.
ULINE.
AT LINE-SELECTION.
CHECK NOT wa_spfli-carrid IS INITIAL.
SELECT fldate
    FROM sflight
    INTO flightdate
    WHERE carrid = wa_spfli-carrid AND
          connid = wa_spfli-connid.
    WRITE / flightdate.
ENDSELECT.
CLEAR: wa_spfli-carrid.

Process and reprocess

Hi experts I have One doubt in ALEIdoc
If any One ask me in interview ,
How do u process Idoc in inbound side what I have to tell
and If they ask me how do u reprocess idoc at inbound side what I have to tell please guide me
Points will be rewarded
Thanks,
Durga .

Hi,
searchsap.techtarget.com/tip/0,289483,sid21_gci1268508,00.html - 68k - Cached - Similar pages
Sample Processing Routines
Last edited:
Creating and processing IDocs are a widely mechanical task, as it is true for all interface programming. We will show a short example that packs SAP R/3 SapScript standard text elements into IDocs and stores them back to texts in a second routine. The text elements can be edited with SO10.
Outbound function     IDoc outbound functions are function modules with a standard interface which will read data from an application database and convert the data into IDoc format.
     The interface parameters need to be compatible with a well defined standard, because the function module will be called from within another program.
Inbound function     IDoc inbound functions are function modules with a standard interface, which will interpret the received IDoc data and prepare for processing by an application.
     The received IDoc data is processed record by record and interpreted according the segment information provided with each record. The prepared data can then be processed by an application, a function module or a self-written program.
     The example programs in the following chapters will show you how texts from the text pool can be converted into an IDoc and processed by an inbound routine to be stored into another system. The following will give you the basics to understand the example.
Text from READ_TEXT     SAP R/3 allows the creation of text elements, e.g. with transaction SO10. Each standard text elements has a header record which is stored in table STXH. The text lines itself are stored in a special cluster table. To retrieve the text from the cluster, you will use the standard function module function READ_TEXT . We will read such a text and pack it into an IDoc. That is what the following simple function module does.
     If there is no convenient routine to process data, the easiest way to hand over the data to an apllication is to record a transaction with transaction SHDB and create a simple processing function module from that recording.
Sample Inbound Routines
Last edited:
Inbound processing is widely the reverse process of an outbound.. The received IDoc has to be unpacked, interpreted and transferred to an application for further processing.
Inbound processing function module     Below is the example of an inbound function module. This module expects an IDoc with rows of plain text and will save this text under a given name to SAP's text database. The procedure will extract the text name and the text line from the IDoc and hand over the text data to the function module READ_TEXT which will store the text in the text pool.
FUNCTION
""Lokale Schnittstelle:
*"       IMPORTING
*"             VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*"             VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*"       EXPORTING
*"             VALUE(WORKFLOW_RESULT) LIKE BDWFAP_PAR-RESULT
*"             VALUE(APPLICATION_VARIABLE) LIKE BDWFAP_PAR-APPL_VAR
*"             VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"             VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*"       TABLES
*"              IDOC_CONTRL STRUCTURE EDIDC
*"              IDOC_DATA STRUCTURE EDIDD
*"              IDOC_STATUS STRUCTURE BDIDOCSTAT
*"              RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"              SERIALIZATION_INFO STRUCTURE BDI_SER
DATA: XTHEAD   LIKE THEAD .
DATA: TLINES LIKE TLINE    OCCURS 0 WITH HEADER LINE.
CLEAR XTHEAD.
REFRESH TLINES.
*** --- Unpacking the IDoc --- ***
LOOP AT IDOC_DATA.
     CASE IDOC_DATA-SEGNAM.
       WHEN 'YAXX_THEAD'.
            MOVE IDOC_DATA-SDATA TO XTHEAD.
       WHEN 'YAXX_TLINE'.
            MOVE IDOC_DATA-SDATA TO TLINES.
     ENDCASE.
ENDLOOP.
*** --- Calling the application to process the received data --- ***
CALL FUNCTION 'SAVE_TEXT'
       EXPORTING
            HEADER          = XTHEAD
            SAVEMODE_DIRECT = 'X'
       TABLES
            LINES           = TLINES.
    ADD SY-SUBRC TO OK.
füllen IDOC_Status
fill IDOC_Status
    IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
    IDOC_STATUS-MSGV1 = IDOC_CONTRL-IDOCTP.
    IDOC_STATUS-MSGV2 = XTHEAD.
    IDOC_STATUS-MSGID = '38'.
    IDOC_STATUS-MSGNO = '000'.
    IF OK NE 0.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
    ELSE.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'S'.
      CALL_TRANSACTION_DONE = 'X'.
    ENDIF.
    APPEND IDOC_STATUS.
ENDFUNCTION.
Unpacking the IDoc data     The received IDoc data is processed record by record and unpacking is a simple discrimination by case according the segment name provided with each record..
*** --- Unpacking the IDoc --- ***
LOOP AT IDOC_DATA.bb
     CASE IDOC_DATA-SEGNAM.
      WHEN 'YAXX_THEAD'.
            PERFORM UNPACK_IDOC TABLES IDOC_DATA USING XTHEAD.
      WHEN 'YAXX_TLINE'.
            PERFORM UNPACK_TAB TABLES IDOC_DATA TLINES.
       ENDCASE.
ENDLOOP.
Application processing     When the IDoc is unpacked it needs to be passed to the application. In our case this will be a simple call to a standard function which is going to store the data to the text database.
*** --- Calling the application to process the received data --- ***
CALL FUNCTION 'SAVE_TEXT'
       EXPORTING
            HEADER          = XTHEAD
            SAVEMODE_DIRECT = 'X'
       TABLES
            LINES           = TLINES.
Writing a status log     Finally the processing routine needs to pass a status record to the IDoc processor. This status indicates successful or unsuccessful processing and will be added as a log entry to the table EDIDS.
fill IDOC_Status
    IF OK NE 0.
      IDOC_STATUS-STATUS = '51'.
    ELSE.
      IDOC_STATUS-STATUS = '53'.
    ENDIF.
    APPEND IDOC_STATUS.
     The status value '51' indicates a general error during application processing and the status '53' indicates everything is OK. There are numerous other status values, with distinct meanings, but '51' and '53' are the most common ones.
http://idocs.de/www3/cookbooks/id
verify if it helps
Thanks & regards,
sravani yendru

ALV grid refresh problem when I return from list-processing

hi,
I have made alv grid with f4 help features and i'm using row select feature.
When i click on a button in Application toolbar, the program leaves to list processing and then return to alv gridscreen.
Now the problem arises.
(1)Even if i select rows and press F8, the program does not identify the rows selected and does not give me desired output.
(2)Also, when i press F4, the selected value does not appear in the text field.
Both the cases are working fine, if i dont press button and go to list processing.
Please help!!

You can use the function module as stated below -
FORM user_command USING r_ucomm TYPE sy-ucomm
rs_selfield TYPE slis_selfield.
CALL FUNCTION 'GET_GLOBALS_FROM_SLVC_FULLSCR'
IMPORTING
ET_EXCLUDING =
E_FLG_NO_HTML =
E_CALLBACK_PROGRAM =
E_REPID =
e_grid = ref1
ES_LAYOUT_KKBLO =
ES_SEL_HIDE =
CALL METHOD ref1->check_changed_data.
This helps to get the data in the internal table refreshed as well as that on the screen so that both are in sync.
this is generally used on some event, you can also use it otherwise.
<b>
Reward if useful.</b>
Regards,
Pritha

PPPI Process messages and check status

Hello.
Does anyone know of any method from xMII to get and check status of process messages sent to PP-PI?
E.g. check for status (has it been sent) and for any errors?
BR
Poul.

Hi Poul,
I found a few RFCs which might do the job and will list them here so you can test them:
PROCESS_MESS_DOWNLOAD
PROCESS_MESS_EXCHANGE
PROCESS_MESS_GET_RETURN_CODE
PROCESS_MESS_UPLOAD
My search method is kind of funny. I put PROCMESS* into the search pattern of a SAP_JCo_Interface action block to return a list of related action blocks. But since I can't use BAPI in SAP and must rely on SE37, I can't readily see the documentation to determine relevance. But I suspect you can take if from here. I would be interested in knowing what you come up with for these.
I also tried PROCMSG* and get these:
BAPI_HU_PROCESS_MSG
BAPI_HU_PROCESS_MSG_DIRECT
BAPI_LIKP_PROCESS_MSG
BAPI_LIKP_PROCESS_MSG_DIRECT
Where HU stands for Handling Unit, but I can't seem to find out what LIKP refers to.
Hope this helps and maybe together we can get the information.
Thanks,
Mike
Found a couple more
RSAP_GET_MSG_TEXT
RSSM_GET_MSG_TEXT
You may also be able to use RFC_READ_TABLE, but I do not know the table structures which would be of interest.
Edited by: Michael Appleby on Jul 16, 2008 3:07 PM

List processing and PF status.

Similar Messages

Maybe you are looking for