Tracing of message in Status Bar using Call Transaction for MRBR

Hi
As per the business requirement, I would like to automate the MRBR Transaction. I am achieving this by using Call Transaction. After aaplying certain company codes as an i/p; i receive the invoices as an o/p in a ALV Lay out. Say for example, 100 invoices are displayed in a AlV Lay-out after applying i/p. Now I select all these 100 invoices and release them.
All these steps are recorded and supplied to Call Transaction via BDC table.
Problem:
The number of invoices released, appear in the status bar of that ALV Lay-out screen. This message appears on the ALV screen after I have released the invoices and clicked on "SAVE" button.I would like to use this information and display this number (No. of Invoices released) in my Job Log. But I do not know how to do it. Could any one help me out for this?
Thanks in advance,
Jigar Shah.

Yes I have tried that option as well.
But the thing is, the recording gets over as soon as I click on "SAVE" button.And that message apperas in status bar only after I click on "SAVE" button.So this way the message in the status bar never gets recorded.
Thanks & Regards,
Jigar Shah.

Similar Messages

Error 00-341 RAISE_EXCEPTION when using Call Transaction for VA01 in backgr

Hi,
I am getting this message when I use call transaction to create a sales order using VA01. Following is the statement I have used. Note that when i execute the program online, I am not getting any errors. I could create sales order without any problem. I am getting this exception only when I run in background.
      CALL TRANSACTION 'VA01'
                 USING BDC_TAB
                  MODE 'N'
                UPDATE 'S'
         MESSAGES INTO W_MESS_TAB.
When I captured message tab, I got following messages.
DC006 - Control Framework: Fatal error - GUI cannot be reached
00341 Runtime error RAISE_EXCEPTION has occurred.
Please help me in this regard.
Regards
Kasi

Some times execution of BDC program in back ground is different from the foreground. Some screens may appear in background and raise error while same will not when executed in foreground.
Double click the message in Session log to know more details.
One way is to suppress the screen while executing BDC.
Alternatively I suggest to use BAPI instead.
- Sanjay

Messages on status bar

Hi friends,
Thanks in advance.
Can we hide or suppress the messages displayed on the status bar .

Hi,
For BDC
R u using call transaction for ur BDC? If u r then u can catch all your messages and put them into an internal table of type bdcmsgcoll. Use the addition ... MESSAGES INTO itab with your CALL TRANSACTION statement.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Display a message in status bar when error in a block based procedure

Hi
I have a block based on procedures.
If I have an exception when I try to insert a record for example, how can I display a user friendly message in the status bar ?
here is my insert procedure :
PROCEDURE emp_insert2(t IN emptab) IS
BEGIN
    FOR i IN t.first..t.last LOOP
    INSERT INTO emp (empno, ename, job, hiredate, sal)
    VALUES(t(i).empno, t(i).ename, t(i).job, t(i).hiredate, t(i).sal);
    END LOOP ;
EXCEPTION
    When DUP_VAL_ON_INDEX then
        Raise_Application_Error( -20002, '^This identifier already exists^' ) ;
END emp_insert2;When I use the ON-FORM trigger and ERROR_CODE and ERROR_TEXT variables, I get an FRM-XXXX message saying :
40735--INSERT-PROCEDURE trigger raised unhandled exception ORA-00001.
I want a message like :
ORA-20002 This identifier already exists

Hello,
ORA-20500: ^This identifier already exists^ ORA-06512: à "SCOTT2.EMP_PKG", ligne 48
I cannot figure out what is the problem described by the second part of the message.
why numeric or value error in this case ? ( ligne 48 corresponds to the raise_applicaion_error instruction )There is no problem with the second part it is just for showing the line number it not the numeric or value error the code for numeric or value error is ORA-06502. See the below link for more information
http://www.techonthenet.com/oracle/errors/ora06512.php
So, now you can display your customized message in status bar using the error code which you defined in RAISE_APPLICATION_ERROR like below...
DECLARE
     errcode VARCHAR2(50) := DBMS_ERROR_CODE;
     errtxt VARCHAR2(1000) := DBMS_ERROR_TEXT;
BEGIN
     IF vErrCode='-20500' THEN
        MESSAGE('Here display your customized message.');
     ELSE
        -- Handle the rest errors...
     END IF;
END; -Ammad

Call transaction for less than 10,000 records

Hi all
Is call transaction advisable for processing less than 10,000 records.
I want to use call transaction for each record and if it fails, pass it to an opened bdc session for manual processing by functional consultants. At the same time, I have to write a report with successful and errored records. Is my approach the only way? Any other ideas are welcome and appreciated
Thanks
ricky

Its completely safe.
Check the return table for all message type E and then recreate your Error table and pass it to BDC open session and can be executed from SM35 in foreground mode. But what happen if there are more say 100 or 200 error records are there.Its not feasible to go and run each record in Foreground mode.Instead Display the error records in an editable ALV with the error message trap from the CALL Transaction return table and let the consultant correct then on the screen and download it, modify it to suit the upload procedure of your report. Then reprocess the file.
Also, display the audit report based on that table.
Regards,
Amit

Supress message in status bar when using Call Transaction

Hi,
I have designed a RF program and I am using a BDC program to call LT11 transaction for confirming TO.
As this was a Flowrack storage type we will assign Source HU during TO confirmation. So I went for a BDC.
But after confirmation I am getting a Status message TO XXX confirmed in the status bar which is also displayed in the RF Screen for every line item confirmed. I want to supress this message.
I am getting this message in the messtab table as well by using Call Transaction. So how can I supress this message in Status bar.
Please let me know for more information.
Thanks,
Manoj.

>
kaka79 wrote:
> I have designed a RF program and I am using a BDC program to call LT11 transaction for confirming TO.
> But after confirmation I am getting a Status message TO XXX confirmed in the status bar which is also displayed in the RF Screen for every line item confirmed. I want to supress this message.
> I am getting this message in the messtab table as well by using Call Transaction. So how can I supress this message in Status bar.
The CTU (CALL TRANSACTION ... USING ...) captures and stores all the messages into the message internal table (... MESSAGES INTO itab ...), but they are not displayed. So, if one of them appears in the status bar, it's because there is an additional MESSAGE ... statement in the program using the CTU. So look at it and add a condition before the MESSAGE statement to not output this exact message (click the message on status bar to get the message number, or debug the program to get it from the message internal table).

How to pass message in Status Bar

How can I pass message in status bar.
I typed bellow line but get some error.
void itemFileOpen_actionPerformed (ActionEvent e) {
statusBar.setText(" need Help ");
Error: (456) method setText(java.lang.String) not found in class oracle.dacf.control.swing.StatusBarControl.
Warning: Deprecated APIs are used. Please recompile with the 'deprecation' option for details.
null

Sergio,
Even though your form is based on the Apps Template form, double-check to ensure it has all of the triggers it should have, like the Form level Key-Commit. The easiest way to make this comparison would be to open your custom form and then open one of the EBS forms like "ARXCUDCI". If your comparison shows no significant differences you might be dealing with a situation when the message is displaying in the Console (status bar) but something else is clearing the console. Check for any Clear_Message calls.
Hope this helps.
Craig...
If my response or the response of another was helpful, please mark it accordingly

ALV Report - Field Overflow message in status Bar

Hi
I am trying to display ALV report , ALV report is displaying fine but on execution of report , an message in status bar is coming as "Field copy Number can not be totalled because of field overflow."
Can anyone tell why such messgae is comming?
Thanks,
Debadatta

Just a wild guess, treat the below as an example.
Eg:
assuming one field in the output is of length 2 type i.
values: 20, 30, 60, 45.
Totalling the values result as 155. but due to the length of the field as 2. We can encounter the overflow message.
Considering the above example, manually total the values of your numerical columns and see if any of the column is execeeding the specified length.
Regards
Eswar
Note: Reward if you find the info useful.

FM to display warning message at status bar

Hi,
can any body give me the FM to display the warning message
at status bar.
Thanks in advance

Hi,
To give a warning message , you dont need any function module. You can use the keyword 'MESSAGE' and give the type as 'W'.
Do a F1 on the keyword MESSAGE for further details.
regards,
Advait

Error Message in Status bar

Hi ,
i am getting an error message in pop-up box ,can we show this same error message in status bar..?
Thanks.

Hi shiva ,
data : dtype type c value 'S'.
MESSAGE E053(z4) DISPLAY LIKE dtype.
my code is like that,but still it shows in popup window.
can you check it once...?
Thanks

SAP GUI 7.20 and Animated Messages in Status Bar

Hello Experts,
Is there a way to disable "animated" display of messages in status bar when Signature Design is active? Currently messages are scrolled from left to right and then fade in. (Please note that this is a different from "Animated Focus" or "Animation" feature and only unique to Signature Design Theme). It would be nice to disable the animation so messages are immediately displayed without disabling Signature Design. I have asked this question in the past and there was basically no way to accomplish this. Is there any hope that this would be included in future patches for SAP GUI 7.20?
Thank you!
Abdul

Daniel,
Have you had any luck with this issue? We recently installed SAP GUI 7.20 patch 2 and are having similar issues. While working in t-code SWDD, "Workflow Builder", I am automatically logged out of SAP and the LOGON pad also closes out and I forced to sign back in. This is happening when I drag and drop an event into a step and enter in information that should normally prompt a warning/error message after hitting the "Enter" key.
Thanks in advance.
Edited by: Michael Kostek on Oct 7, 2010 9:11 AM

Regarding message in status bar

Hai SDN members , i have to display message in status bar , my requirement is like this ,ihave three fields in gui screen 1 is shipment num ,2 is shipment type and 3 is packing ref . and if i give the input in this three fields ,then the shipment number should be displayed in status bar

hi,
u want message after pressing some button or enter?
u need to write this in USER_AOMMAND module of PAI, in when case..
like
when 'SAVE'.
MESSAGE s000(zmsg_fmtr) WITH srn.
here zmsg_fmtr is my message class
and this is my 000 message in that mssage class
Record Saved Successfully with Serial Number &
in place of & my passing parameter (srn) will come on status
reward if usefull...

BDC using call transaction

Hi ,
This is vijay...
can anyone help me plz
Hi,
Iam uploading data using call transaction.Tcode is ff67.In this TCode we have the begining balance(ssald) and ending balance(esald).The new record we are uploading will take the begining balance as the previous record ending balance, if we give the begining balance wrong then the record does not saved it will show error(the begining balance does not match with the prior ending balance).
while uploading the data using MODE A iam able to get the desired output but by using the MODE N iam not able to get the desired output i,e if there is any error in the begining balance also the record is being saved iam not getting the error message.
Iam attaching the code below..please help me
report Z_BRS_BDC no standard page heading line-size 255.
        INTERNAL TABLES DECLARATIONS
DATA : BEGIN OF bdcdata OCCURS 0.
        INCLUDE STRUCTURE bdcdata.
DATA : END OF bdcdata.
DATA: LV_OUT TYPE STRING.
DATA : iopt LIKE ctu_params.
DATA : wa_rec_err   TYPE i.
DATA : wa_rec_wri TYPE i.
DATA : wa_tot_rec TYPE i.
DATA : amt(16) type c.
DATA : BEGIN OF gu_upload OCCURS 0,
       hbkid LIKE febmka-hbkid,
       hktid LIKE febmka-hktid,
       aznum LIKE febmka-aznum,
       azdat LIKE febmka-azdat,
       ssald LIKE amt,
       esald LIKE amt,
       budtm LIKE febmka-budtm,
       mnam1 LIKE febmka-mnam1,
       jname LIKE febmka-jname,
       vgman LIKE febmka-vgman,
       valut LIKE febep-valut,
       kwbtr(13) TYPE c,
       chect_kf LIKE febmkk-chect_kf,
      END OF gu_upload.
DATA:GU_DOWNLOAD LIKE GU_UPLOAD OCCURS 0 WITH HEADER LINE.
kishi*********************************
DATA: BEGIN OF itab OCCURS 0,
     vgman LIKE febmka-vgman,
     valut LIKE febep-valut,
     kwbtr(13) TYPE c,
     chect_kf LIKE febmkk-chect_kf,
     END OF itab.
kishi)(_()00-8-09
DATA: BEGIN OF messtab OCCURS 0.
        INCLUDE STRUCTURE bdcmsgcoll.
DATA: END OF messtab.
DATA: BEGIN OF messtab1 OCCURS 0.
        INCLUDE STRUCTURE messtab.
DATA: END OF messtab1.
DATA : BEGIN OF int_count OCCURS 0.
        INCLUDE STRUCTURE alsmex_tabline.
DATA : END OF int_count.
DATA: c_tcode      LIKE sy-tcode              VALUE 'FF67',
      c_upd        LIKE ctu_params-updmode    VALUE 'S',
      c_def_size   LIKE ctu_params-defsize    VALUE 'X'.
*VALUES FOR STARTING COLUMNS AND ROWS IN THE EXCEL SHEET
DATA : c_begcol     TYPE i                     VALUE '1',
      c_begrow     TYPE i                     VALUE '1',
*DATA IS ENDED AT THE 13TH COLUMN IN THE EXCELSHEET
      c_endcol     TYPE i                     VALUE '13',
*LAST ROW IN THE EXCEL SHEET
      c_endrow     TYPE i                     VALUE '65536',
      c_path(3)    TYPE c                     VALUE 'C:\'.
*Field Symbols
FIELD-SYMBOLS: <fs>.
     SELECTION SCREEN PARAMETERS
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS : p_file LIKE rlgrap-filename DEFAULT
'C:\ ',
*This is the path for downloading file
P_FNAME2 LIKE RLGRAP-FILENAME ,
c_mode LIKE ctu_params-dismode DEFAULT 'N'.
SELECTION-SCREEN END OF BLOCK b1.
AT SELECTION-SCREEN.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
*F4 HELP FOR FILE SELECTION
PERFORM validate_input_file.
START-OF-SELECTION.
CLEAR gu_upload.
REFRESH gu_upload.
     UPLOAD THE DATA FROM FLAT FILE TO INTERNAL TABLE
PERFORM file_upload.
iopt-dismode = c_mode.
iopt-updmode = c_upd.
iopt-defsize = c_def_size.
     POPULATE THE DATA THROUGHSCREENS
PERFORM bdc_upload.
END-OF-SELECTION.
*DISPLY THE ERROR RECORDS
PERFORM DISPLAY-DATA.
      FORM file_upload                                              *
FORM file_upload.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
       EXPORTING
            filename                = p_file
            i_begin_col             = c_begcol
            i_begin_row             = c_begrow
            i_end_col               = c_endcol
            i_end_row               = c_endrow
       TABLES
            intern                  = int_count
       EXCEPTIONS
            inconsistent_parameters = 1
            upload_ole              = 2
            OTHERS                  = 3.
LOOP AT int_count.
    ASSIGN COMPONENT int_count-col OF STRUCTURE gu_upload TO <fs>.
    IF sy-subrc NE 0.
      EXIT.
    ENDIF.
    <fs> = int_count-value.
    AT END OF row.
      APPEND gu_upload.
      CLEAR gu_upload.
    ENDAT.
ENDLOOP.
*kishhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
LOOP AT gu_upload.
    itab-vgman = gu_upload-vgman.
    itab-valut = gu_upload-valut.
    itab-kwbtr = gu_upload-kwbtr.
    itab-chect_kf = gu_upload-chect_kf.
    APPEND itab.
ENDLOOP.
*kishiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
ENDFORM.                    "file_upload
*&      Form BDC_UPLOAD
FORM bdc_upload.
LOOP AT gu_upload.
    CLEAR bdcdata.
    REFRESH bdcdata.
*&      POPULATE THE DATA FOR FIRST SCREEN
perform bdc_dynpro      using 'SAPMF40K' '0101'.
perform bdc_field       using 'BDC_CURSOR'
                              'FEBMKA-JNAME'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'FEBMKA-BUKRS'
                              'IN14'.
perform bdc_field       using 'FEBMKA-HBKID'
                              gu_upload-hbkid.
perform bdc_field       using 'FEBMKA-HKTID'
                              gu_upload-hktid.
perform bdc_field       using 'FEBMKA-AZNUM'
                              gu_upload-aznum.
perform bdc_field       using 'FEBMKA-AZDAT'
                              gu_upload-azdat.
perform bdc_field       using 'FEBMKA-SSALD'
                              gu_upload-ssald.
perform bdc_field       using 'FEBMKA-ESALD'
                              gu_upload-esald.
perform bdc_field       using 'FEBMKA-BUDTM'
                              gu_upload-budtm.
perform bdc_field       using 'FEBMKA-MNAM1'
                              gu_upload-mnam1.
perform bdc_field       using 'FEBMKA-JNAME'
                              gu_upload-jname.
*&      POPULATE THE DATA FOR SECOND SCREEN
    DATA : fnam(20) TYPE c,
          idx      TYPE c.
    MOVE 1 TO idx.
    LOOP AT itab.
      PERFORM bdc_dynpro      USING 'SAPMF40K' '8000'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'FEBMKK-CHECT_KF(03)'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
      CONCATENATE 'FEBMKA-VGMAN(' idx ')' INTO fnam.
      PERFORM bdc_field       USING fnam
                                    itab-vgman.
      CONCATENATE 'FEBEP-VALUT(' idx ')' INTO fnam.
      PERFORM bdc_field       USING fnam itab-valut.
      CONCATENATE 'FEBMKA-KWBTR(' idx ')' INTO fnam.
      PERFORM bdc_field       USING fnam itab-kwbtr.
      CONCATENATE 'FEBMKK-CHECT_KF(' idx ')' INTO fnam.
      PERFORM bdc_field USING fnam itab-chect_kf.
      idx = idx + 1.
    ENDLOOP.
*perform bdc_dynpro      using 'SAPMF40K' '8000'.
*perform bdc_field       using 'BDC_CURSOR'
                             'FEBMKK-CHECT_KF(01)'.
*perform bdc_field       using 'BDC_OKCODE'
                             '/00'.
*perform bdc_field       using 'FEBMKA-VGMAN(01)'
                             'z001'.
*perform bdc_field       using 'FEBEP-VALUT(01)'
                             '2007/04/26'.
*perform bdc_field       using 'FEBMKA-KWBTR(01)'
                             '          5000-'.
*perform bdc_field       using 'FEBMKK-CHECT_KF(01)'
                             '1122'.
perform bdc_dynpro      using 'SAPMF40K' '8000'.
perform bdc_field       using 'BDC_CURSOR'
                              'FEBMKK-CHECT_KF(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=SICH'.
*&      POPULATE THE DATA FOR FOURTH SCREEN
perform bdc_dynpro      using 'SAPMF40K' '0101'.
perform bdc_field       using 'BDC_CURSOR'
                              'FEBMKA-BUKRS'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BUCH'.
perform bdc_field       using 'FEBMKA-BUKRS'
                              'IN14'.
perform bdc_field       using 'FEBMKA-HBKID'
                              gu_upload-hbkid.
perform bdc_field       using 'FEBMKA-HKTID'
                              gu_upload-hktid.
perform bdc_field       using 'FEBMKA-AZNUM'
                              gu_upload-aznum.
perform bdc_field       using 'FEBMKA-AZDAT'
                              gu_upload-azdat.
perform bdc_field       using 'FEBMKA-SSALD'
                              gu_upload-ssald.
perform bdc_field       using 'FEBMKA-ESALD'
                              gu_upload-esald.
perform bdc_field       using 'FEBMKA-BUDTM'
                              gu_upload-budtm.
perform bdc_field       using 'FEBMKA-MNAM1'
                              gu_upload-mnam1.
perform bdc_field       using 'FEBMKA-JNAME'
                              gu_upload-jname.
*perform bdc_dynpro      using 'SAPMF40K' '0101'.
*perform bdc_field       using 'BDC_OKCODE'
                             '/EENDE'.
*perform bdc_field       using 'BDC_CURSOR'
                             'FEBMKA-BUKRS'.
perform bdc_dynpro      using 'SAPMF40K' '0101'.
perform bdc_field       using 'BDC_OKCODE'
                              '/EABBR'.
perform bdc_field       using 'BDC_CURSOR'
                              'FEBMKA-BUKRS'.
*&      USING THE CALL TRANSACTION
    PERFORM call_transaction.
   CLEAR BDCDATA.                      "<--- Add here
   REFRESH BDCDATA.                 "<--- Add here
ENDLOOP.
ENDFORM.                    " BDC_UPLOAD
*&      Form VALIDATE_INPUT_FILE
FORM validate_input_file.
CALL FUNCTION 'WS_FILENAME_GET'
       EXPORTING
            def_path         = ' c:\ '
            mask             = ',.txt,.*.'
            mode             = 'O'
            title            = 'Upload '
       IMPORTING
            filename         = p_file
       EXCEPTIONS
            inv_winsys       = 1
            no_batch         = 2
            selection_cancel = 3
            selection_error = 4
            OTHERS           = 5.
IF sy-subrc <> 0.
IF sy-subrc <> 0 AND sy-subrc <> 3.
   MESSAGE e100(zm) WITH text-007.
ENDIF.
ENDFORM.                    " VALIDATE_INPUT_FILE
       Start new screen                                              *
FORM bdc_dynpro USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro   = dynpro.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
ENDFORM.                    "bdc_dynpro
       Insert field                                                  *
FORM bdc_field USING fnam fval.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDFORM.                    "bdc_field
*&      Form CALL_TRANSACTION
FORM call_transaction.
DATA: l_index LIKE sy-tabix.
CALL TRANSACTION c_tcode USING bdcdata
                            MODE c_mode
                            MESSAGES INTO messtab.
*POPULATE THE ERROR RECORDS INTO INTERNAL TABLE
IF SY-SUBRC NE 0.
    GU_DOWNLOAD-HBKID = GU_UPLOAD-HBKID.
   GU_DOWNLOAD-HBKID = GU_UPLOAD-HBKID.
    GU_DOWNLOAD-HKTID = GU_UPLOAD-HKTID.
    GU_DOWNLOAD-AZNUM = GU_UPLOAD-AZNUM.
    GU_DOWNLOAD-AZDAT = GU_UPLOAD-AZDAT.
    GU_DOWNLOAD-ESALD = GU_UPLOAD-ESALD.
    GU_DOWNLOAD-SSALD = GU_UPLOAD-SSALD.
    GU_DOWNLOAD-BUDTM = GU_UPLOAD-BUDTM.
    GU_DOWNLOAD-MNAM1 = GU_UPLOAD-MNAM1.
    GU_DOWNLOAD-JNAME = GU_UPLOAD-JNAME.
    GU_DOWNLOAD-VGMAN = GU_UPLOAD-VGMAN.
    GU_DOWNLOAD-VALUT = GU_UPLOAD-VALUT.
    GU_DOWNLOAD-KWBTR = GU_UPLOAD-KWBTR.
    GU_DOWNLOAD-CHECT_KF = GU_UPLOAD-CHECT_KF.
    APPEND GU_DOWNLOAD.
*DISPLAY THE PROGRESS OF PROCESS
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
   PERCENTAGE       = 0
   TEXT             = 'Downloading is in process'.
*DOWNLOADING THE ERROR RECORD
    LV_OUT = P_FNAME2.
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
        FILENAME               = LV_OUT
        WRITE_FIELD_SEPARATOR =      'X'
      TABLES
        DATA_TAB                = GU_DOWNLOAD.
ENDIF.
IF NOT messtab[] IS INITIAL.
    PERFORM format_message.
ENDIF.
ENDFORM.                    " CALL_TRANSACTION
*&      Form DISPLAY-DATA
FORM display-data.
SKIP.
WRITE: 'SY-SUBRC' , sy-subrc.
ENDFORM.                    " DISPLAY-DATA
      FORM FORMAT_MESSAGE                                           *
FORM format_message.
DATA: l_msg(100),
   l_index LIKE sy-tabix.
LOOP AT messtab.
    READ TABLE gu_upload INDEX l_index.
    CALL FUNCTION 'FORMAT_MESSAGE'
         EXPORTING
              id        = messtab-msgid
              lang      = sy-langu
              no        = messtab-msgnr
              v1        = messtab-msgv1
              v2        = messtab-msgv2
              v3        = messtab-msgv3
              v4        = messtab-msgv4
         IMPORTING
              msg       = l_msg
         EXCEPTIONS
              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.
   WRITE:/ l_msg.
ENDLOOP.
WRITE:/ l_msg.
ENDFORM.
Message was edited by:
        vijayd duvvada

Hi,
First , keep the mode "E" and check the debugger , you can exactly see where the error is and let me know, what error and where it is stoping.
By your coding, i suppose to think that, its proble in the amount (currency). When ever you are try to pass the value, and value is not there in upload file or data is mismatch, the call transaction will fail in mode 'A' and succesful in mode 'N'.
In that situation use this before the currecny field.
IF NOT FEBMKA-SSALD IS INTIAL.
   perform bdc_field using 'FEBMKA-ESALD'
                                  gu_upload-esald.
ENDIF.
tHANKS
Manju

Type of error in the log file while using using call transaction mode u2018Eu2019

Hi Gurus,
Please Answer for this qusetion urgently
what type of error exactly you will be seeing in the log file while using call transaction mode u2018Eu2019?
Thanks/
Radha.

Hi,
Can you be clear.
In call transaction , no error logs are created, you have to handle the errors explicitly using the structure BDCMSGCOLL.
Whenever you use E mode then if the transaction encounters any of the errors i.e. data type mismatching or invalid values etc, it will stop at that screen.
You can handle the errors in call transaction in the following method.
create a table using the structure BDCMSGCOLL.
then
loop at ......
      CALL TRANSACTION 'XK01' USING I_BDCDATA MODE 'N' UPDATE 'S' MESSAGES INTO I_MESGTAB.
endloop.
SORT I_MESGTAB BY MSGID MSGV1 ASCENDING.
DELETE ADJACENT DUPLICATES FROM I_MESGTAB.
LOOP AT I_MESGTAB.
    CALL FUNCTION 'FORMAT_MESSAGE'
      EXPORTING
        ID   = I_MESGTAB-MSGID
        LANG = I_MESGTAB-MSGSPRA
        NO   = I_MESGTAB-MSGNR
        V1   = I_MESGTAB-MSGV1
        V2   = I_MESGTAB-MSGV2
        V3   = I_MESGTAB-MSGV3
        V4   = I_MESGTAB-MSGV4
      IMPORTING
        MSG = MESG1.
    IF I_MESGTAB-MSGTYP = 'S' .
      WA_SUCCMESG-MESG = MESG1.
      APPEND WA_SUCCMESG TO I_SUCCMESG.
else     IF I_MESGTAB-MSGTYP = 'E' .
      WA_ERRMESG-MESG = MESG1.
      APPEND WA_ERRMESG TO I_ERRMESG.
    ENDIF.
ENDLOOP.
Hope this is clear.
Thanks and Regards.

How to use Call Transaction in AVL ........ for va02

Hi Experts,
I am using CALL TRANSACTION in ALV for VA02, but I want to go on item number. The following form i have used and it is working but I want to go on perticular item number in va02. pl. guide me.
FORM user_command USING r_ucomm LIKE sy-ucomm
                  rs_selfield TYPE slis_selfield.
CASE r_ucomm.
    WHEN '&IC1'.
    IF rs_selfield-fieldname = 'VBELN'.
      READ TABLE it_out INTO wa_itab INDEX rs_selfield-tabindex.
      SET PARAMETER ID : 'AUN' FIELD wa_itab-vbeln .
                       'APO' FIELD wa_itab-posnr.
      CALL TRANSACTION 'VA02' AND SKIP FIRST SCREEN.
    ENDIF.
ENDCASE.
ENDFORM.
*=====================================
Yusuf

Hi,
use BDC for that....
check out the BDC part of coding for it.
REFRESH itab_bdcdata.
CLEAR    itab_bdcdata.
*initial screen
PERFORM bdc_dynpro      USING 'SAPMV45A'
                                '0102'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'VBAK-VBELN'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '/00'.
PERFORM bdc_field       USING 'VBAK-VBELN'
                      <b>          g_t_atpma4-vbeln.</b>
*item overview screen
PERFORM bdc_dynpro      USING 'SAPMV45A'
                                '4001'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=POPO'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'RV45A-MABNR(04)'.
*popup screen (move item to top)
PERFORM bdc_dynpro      USING 'SAPMV45A'
                                '0251'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'RV45A-POSNR'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '=POSI'.
PERFORM bdc_field       USING 'RV45A-POSNR'
                                <b>g_t_atpma4-posnr.</b>
*item overview screen
PERFORM bdc_dynpro      USING 'SAPMV45A'
                                '4001'.
PERFORM bdc_field       USING 'BDC_OKCODE'
                                '/00'.
PERFORM bdc_field       USING 'BDC_CURSOR'
                                'VBAP-POSNR(01)'.
PERFORM bdc_field       USING 'RV45A-VBAP_SELKZ(01)'
                                'X'.
*Call transaction VA02
CALL TRANSACTION 'VA02' USING itab_bdcdata
                           MODE 'E'
                           UPDATE 'A'
                           MESSAGES INTO itab_bdcmsg.
Patil

Tracing of message in Status Bar using Call Transaction for MRBR

Similar Messages

Maybe you are looking for