Standard program modification logs

Hi,
Is there any way/transaction we can view or store logs from a modified standard program ?
Something like the version management in the abap editor but it must display all the standard program that has been modified .
The purpose is to easily keep track of all the changes, in case of system refresh/update.
Thank you.

version management will report changes for ALL ABAP objects, including those in SAP namespace.  is that what you're asking for?

Similar Messages

  • How to find a program which modifies the variant of a standard program?

    Hi,
    I have an issue where the variant values of the standard program RKEVEXT3 (Transaction : KEFC), is getting changed by a background job.I need to find the program which modifies the values of the variant.
    Any input on this will be helpful.
    Regards,
    Raj

    hi Raj,
    you can change variants with FM RS_VARIANT_CHANGE. I would suggest to run a where used list for this variant in your system.
    hope this helps
    ec

  • How can I display error log of a standard program in my custom program?

    Hello Experts,
    I have a requirement where I submit a standard program from my custom module pool program as a background job. I use the TO SAP-SPOOL and thus the log is available when I go to SM37 and check the spool list. I have a requirement that I display this log in a tab within my module pool after the completion of the program. I am unable to fins a proper solution to this. I have both the spool number & the log number but I am unable to find function modules which will help me print them within my program. I found many ways to display it but as full screen and not with in my program.
    Could someone please help me with this.
    Thank You

    Hi,
    FM to read a spool request is "RSPO_RETURN_ABAP_SPOOLJOB".
    If the error log is displayed as a list output in the standard program, you can also use the syntax SUBMIT Program... and RETURN with export to memory addition.
    Then you will be able to read the list output from memory.
    Regards,
    Munesh.

  • Modification of standard programs

    Hi experts,
    i want to modify cursor movment in the transaction COIB. Pls tell me how can i achieve this.   Pls tell me the procedure and process required for this task.
    Thank u.

    hi,
    folow these link for modification of standard programs...
    http://www.sap-img.com/basis/manually-applying-the-oss-note.htm
    http://www.sap-img.com/ab025.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18c5de6e11d195460000e82de14a/content.htm
    we can set the cursor position in two way's.
    <b>Static Cursor Position</b>
    To define the cursor position statically, enter the name of the required screen element in the Cursor position screen attribute in the Screen Painter.
    <b>Dynamic Cursor Position</b>
    To set the cursor position dynamically, use the following statement in an ABAP dialog module in the PBO event:
    <b>SET CURSOR FIELD <f> [OFFSET <off>].</b>
    <f> can be a literal or a variable containing the name of a screen element. You can use the OFFSET addition to place the cursor at a particular point within an input/output field.
    regards,
    Ashok reddy

  • Modification in SAP standard programs.

    Hi All
    I am trying to make modification in SAP standard program by using a copy of code from the original program to my program..but facing many errors like the statement BEgin of block syntax is wrong..
    i am trying to mdify the foloowing program--RFSSLD00...
    Please help me and guide to make changes to this prog..
    Also tell me that do we need to again create all the functiongroup and global data declarartion part.
    thank u.

    hi,
    Please note that when you copy a standard Sap Program ,make sure all the objects are copied following your compays naming conventions.
    Now RFSSLD00 can be copied without any difficuly.after that compare the new copied program with the standard program. going to version mngmt->remote comparison . doing this you can get the differences
    check all the includes.. and type pool declartaion and gui status etc....by going to se80
    regards,
    Safel

  • Short dump in standard program

    Hi Friends,
    below description is short dump for standard program.
    Please see the below and help me how to correct the program.
    The current application triggered a termination with a short dump.            
    What happened?
    The current application program detected a situation which really             
    should not occur. Therefore, a termination with a short dump was              
    triggered on purpose by the key word MESSAGE (type X).                      
    Error analysis
    Short text of error message:                                                  
    Internal error: Program   , include   , form   .                                                                               
    Technical information about the message:                                      
    Diagnosis                                                                    
         An unexpected error has occurred.                                        
    Procedure                                                                    
         If you can reproduce the error, contact the SAP Hotline quoting the      
         error number.                                                            
    Message classe...... "GR"                                                     
    Number.............. 214   
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.       
                                                                                    You may able to find an interim solution to the problem                       
    in the SAP note system. If you have access to the note system yourself,       
    use the following search criteria:                                                                               
    "MESSAGE_TYPE_X" C                                                            
    "SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"                                     
    "F80_FILL_COL_TAB"                                                            
    If you cannot solve the problem yourself, please send the                     
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                  
       To obtain this, select the "Print" function on the current screen.         
                                                                                    2. A suitable hardcopy prinout of the system log.                             
       To obtain this, call the system log with Transaction SM21                  
       and select the "Print" function to print out the relevant                  
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,            
       supply the source code.                                                    
       To do this, you can either use the "PRINT" command in the editor or        
       print the programs using the report RSINCL00.                                                                               
    4. Details regarding the conditions under which the error occurred            
       or which actions and input led to the error.                               
    Thanks & Regards,
    Sree
    Edited by: adepus on Oct 7, 2009 12:39 PM
    Edited by: adepus on Oct 7, 2009 12:39 PM

    Hi Clemens,
    I am getting a dump error as shown below. Could you please find some resolution for this issue. we just made some changes to the transaction GS02(Just added a GL account to one of the sets).
    Runtime Error MESSAGE_TYPE_X
    ShrtText
    The current application triggered a termination with a short dump.
    What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    Short text of error message:
    Internal error: Program , include , form .
    Technical information about the message:
    Diagnosis
    An unexpected error has occurred.
    Procedure
    If you can reproduce the error, contact the SAP Hotline quoting the
    error number.
    Message classe...... "GR"
    Number.............. 214
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    to correct the error
    Probably the only way to eliminate the error is to correct the program.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "MESSAGE_TYPE_X" C
    "SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"
    "F80_FILL_COL_TAB"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    Source Code
    79 MESSAGE x214.
    80 ENDIF.
    81 PERFORM e08_read_object_index(sapfgsb0)
    82 USING fcolumns-dim_index.
    83 IF c-subrc 0. MESSAGE x214. ENDIF.
    84 c_dsentry = c-tval-from.
    85 IF c_dsentry '='.
    86 READ TABLE data_fields BINARY SEARCH
    87 WITH KEY tab = rep_table
    88 dsentry = c_dsentry.
    >>>> IF sy-subrc 0. MESSAGE x214. ENDIF.
    90 ENDIF.
    91 WHEN OTHERS.
    92 c_dsentry = '*'.
    93 ENDCASE.
    94 ENDIF.
    Regards,
    Pavan

  • How to find out if ENQUEUE_ESRDIRE is used inside a standard program!

    Hi All,
    I have run VFX3 to rellease billing document using VF02 BDC that is called inside VFX3.
    I used debugging to find out in ENQUEUE_ESRDIRE, or ENQUEUE_E_TRDIR is used anywhere in the process.
    I also used System Debugging and Break-point at statement functions. But I have not ben stopped at these function modules.
    However, I checked using ST05 with enqueue trace enabled, and I found the below entries.
    255 ESRDIRE    ENQUEUE     1      0 Excl(***) TRDIR GP3VOFY4EM1BE5DHB1155DUU8H
    37 ESRDIRE    DEQUEUE     1      0 Excl(***) TRDIR GP3VOFY4EM1BE5DHB1155DUU8H
    My query is how can we debug to a point where these lock objects are used or Do these lock objects are not identified in debug mode but are logged while enqueue trace used i.e., SAP uses internally?
    Please help me as this helps me in resolving an issue where locking issue is there that fails to update VFX3 becuase for one user
    in SQL trace it is logged as VF02  TRDIR Lock > 6 hours VF02 TRDIR
    and for another job "UPD 42 050 BATCHFIN          GZZ K > Obj: ESRDIRE # enxxhead7727" is logged in ST05.                        
    Regards,
    Pratyusha

    Hi Clemens,
    I was unable to trigger the exact point from where this lock object has triggered.
    But I am sure that it is a standard SAP process which is locking while releasing the billing documents.
    Now my query is why SAP why SAP'S standard program VF02 that is internally called by VFX3 (RVFAKSPE) and that can be submitted in background mode will use ESRDIRE lock whil each time it releases the block?
    The problem I am facing is - there are different BATCH jobs and all are for VFX3 with different variant so that no billing document is processed by two different jobs at same time. However the lock entries ENQUEUE_ESRDIRE is creating problem as it is creating locking issue and hence the jobs are processed longer than expected. This is evident from ENQUEUE trace of ST05.
    Is VFX3 ( In version 4.5B) is meant for running 1 background job of VFX3 at a time?
    Regards,
    Pratyusha

  • How to know changes in Standard program of SAP

    hi
       suppose some one has made some manual changes in SAP standard code with the help of access key. The another person wants to know what changes has been made by him?

    Hi,
    To find out modifications in a standard SAP program, check out modification overview. It is a part of modification assistant. When you open a SAP standard program, you will see some extra buttons on the tool bar i.e.Insert, Replace etc., just besides them there is a button for modification overview. Click on that and it will give you the list of modifications done on the program.
    If you just want to check out when modifications are done & their request nos, go to the version management and you will get the whole list of requests that the program has.
    Reward points if the answer is helpful.
    Regards,
    Mukul

  • Problem in saving a standard program

    hello
    I have a problem while making changes to a standard program. We are doing an upgrade of 4.6 C to Ecc 6.0.We are doing SPAU activity now and while putting back a customer modification of standard code done in 4.6C version, i face this problem.
    I able to change the standard program, but while saving it, i get an error message "Internal error". I tried debugging it and i understand that it is because of checking some enhancement points related things.
    I have not worked in enhancement points; can you please suggest why is this error appearing?
    Thank you.

    Can you tell us how was the customer modification implemented in 4.6c system i.e. User-exit or BAdI etc.
    Are you trying to copy the source-code of 4.6c (inside user-exit) into enhancement points.
    I have encountered "Internal error" many a times while working with ABAP Dictionary. I cannot tell exactly why it happened, but most of the times when i made changes to multiple fields of views it happened.
    In order to temporarily solve the problem, I split my work into small portions & made changes to only one field and saved and activated. That way it worked. May be you can try that too.
    Regards,
    Saurabh

  • Problem in SAP standard code modification for FB03

    Hi Experts,
    I am adding 4custom fields in FB03 tcode by doing a SAP standard code modification in SE51.
    The program name is SAPMF05L and screen no. is 302(In some SAP verion, it is 304). This is the screen for document line item of an invoice.
    My problem is:
    When I add the fields in the screen, in which module will I put logic in the PBO and PAI as I am unable to figure out the German comments and the program structuring.
    Also, if anybody can tell me what to write as I am little bit confused about the logic of populating my fields with the values.
    FB03 is a display transaction so I have to keep my custom screen fields disabled.
    Regards,
    Sangeeta.

    Hi Sangeeta,
    For enhancing the screen of this Tcode, first of all search is there any Screen enhancement is provided by SAP or not and in case if it is provided then use that only.
    Regards
    Jagesh Lakdawala

  • How to modify standard programs

    HI FRIENDS..........
    is there any way to modify standard programs.....

    Hi Suresh,
    in the past it was necessary to modify standard programs. Today SAP offers lots of possibilities to modify programs without doing what SAP calls MODIFICATION.
    Have a look at the <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/94/9cdc40132a8531e10000000a1550b0/frameset.htm">Enhancement Framework</a>, especially the different <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/70/63da4023a28631e10000000a1550b0/content.htm">Enhancement Technologies</a>
    If you do not understand everything, don't worry: Nobody does but it gives you some hints.
    Let us know why and where you think about modification. I'm convinced there are many nice solutions on hand.
    Regards,
    Clemens

  • I'm having trouble with My adobe Creative Suite 4 Design Standard programs opening. They will bounce to open but won't open up and eventually I will need to force quit as they aren't responding.  I'm thinking it may be a font issue but need some support A

    I'm having trouble with My adobe Creative Suite 4 Design Standard programs opening. They will bounce to open but won't open up and eventually I will need to force quit as they aren't responding.  I'm thinking it may be a font issue but need some support ASAP!

    Nobody can tell you anything without proper system info or other technical details like the crash logs.
    Mylenium

  • Standard program on good received statement

    Hi all,
    can anyone tell me any standard program on good received statement .

    Hi
    check this code
    report zmmgnrep0001
           line-count 58
           line-size 234
           no standard page heading
           message-id zpp.
    TABLES *********************************
    tables : mseg,
             mkpf,
             bkpf,
             ekbe,
             bseg,
             rseg,
             rbkp.
    DATA DECLARATION ****************************
    *data xekbe like ekbe occurs 0 with header line.
    *data zxekbe like ekbe occurs 0 with header line.
    *data :mirodoc like ekbe-belnr,
         mbudat like ekbe-budat.
    data xekbe like ekbe occurs 0 with header line.
    data zxrbkp like rbkp occurs 0 with header line.
    data zrseg like rseg  occurs 0 with header line.
    data :mirodoc like rseg-belnr,
          mbudat like rbkp-budat.
    data : begin of icheck occurs 0,
             checkdoc like rseg-belnr,
           end of icheck.
    data: begin of itab occurs 0,
            mblnr  like mkpf-mblnr,
            mjahr  like mkpf-mjahr,
            budat  like mkpf-budat,
            bldat  like mkpf-bldat,
            xblnr  like mkpf-xblnr,
            zeile  like mseg-zeile,
            bwart  like mseg-bwart,
            ebeln  like mseg-ebeln,
            ebelp  like mseg-ebelp,
            lifnr  like mseg-lifnr,
            lfbnr  like mseg-lfbnr,
            lfbja  like mseg-lfbja,
            lfpos  like mseg-lfpos,
            belnr  like bkpf-belnr,
            bxblnr like bkpf-xblnr,
            bbudat like bkpf-budat,
            wrbtr  like bseg-wrbtr,
            dmbtr  like bseg-dmbtr,
            kursf  like bkpf-kursf,
            grri   like bseg-hkont,
            accn   like bkpf-belnr,
           mirodoc like ekbe-belnr,
           mbudat  like ekbe-budat,
            mirodoc like rseg-belnr,
            mbudat  like rbkp-budat,
          end of itab.
    data : xmseg like mseg occurs 0 with header line,
           xmkpf like mkpf occurs 0 with header line.
    Modifed  by Raja Robinson,TTIL pune *****************************
    data: counter(10),
          counter1(10),
          flag,
          belnr like bkpf-belnr,
          xblnr like bkpf-xblnr,
          budat like bkpf-budat,
          totlc like bseg-dmbtr,
          totfc like bseg-wrbtr,
          kursf like bkpf-kursf,
          grri like bseg-hkont,
          nilcount(5).
    data: begin of hdg occurs 10,
            f1          type c   value '|',
            line(232),
            f2          type c   value '|',
          end of hdg.
    SELECTION SCREEN ****************************
    selection-screen begin of block input with frame.
    select-options: pos_date for mkpf-budat,
                    mat_no   for mseg-matnr,
                    mv_type  for mseg-bwart,
                    vend_cd  for mseg-lifnr,
                    po_no    for mseg-ebeln,
                    hkont    for bseg-hkont.
    selection-screen end of block input.
    BEGIN OF CODE ******************************
    BEGIN OF MAIN CODE ***************************
    start-of-selection.
      perform initialization.
      perform get_data_for_input.
      perform filter_data.
      perform getmirodata.
      perform format_data.
      perform print_data.
    *&      Form  INITIALIZATION
          text
    -->  p1        text
    <--  p2        text
    form initialization.
    endform.                               " INITIALIZATION
    *&      Form  GET_DATA_FOR_INPUT
          text
    -->  p1        text
    <--  p2        text
    form get_data_for_input.
      select a~mblnr                       " Material Document (GRN No.)
             a~mjahr                       " Material Document Year
             a~budat                       " Material Document Posting Date
             a~bldat                       " Material Document Date
             a~xblnr       " Reference Document (Invoice No.)
             b~zeile                       " Material Document Item No.
             b~bwart       " Movement Type (101 - GR Iss., 102 - GR Reverse)
             b~ebeln                       " Purchase Order
             b~ebelp                       " Purchase Order Line Number
             b~lifnr                       " Vendor Code
             b~lfbnr " Reference Document No(Contains 101 No in case of 102)
             b~lfbja                       " Reference Document Year
             b~lfpos                       " Reference Document Item No.
             into corresponding fields of table itab
             from mkpf as a
             inner join mseg as b
             on  amblnr = bmblnr
             and amjahr = bmjahr
             where a~budat in pos_date
             and   b~bwart in mv_type
             and   b~ebeln in po_no
             and   b~matnr in mat_no
             and   b~lifnr in vend_cd.
      if sy-subrc <> 0.
        message e000(zpp) with 'No Data Found for the Input Criteria.'.
      endif.
    endform.                               " GET_DATA_FOR_INPUT
    *&      Form  GETMIRODATA
    form getmirodata.
    select * from rseg into table zrseg for all entries in itab
                  where  ebeln = itab-ebeln
                     and ebelp = itab-ebelp.
    select * from rbkp into table zxrbkp for all entries in zrseg
                   where  belnr = zrseg-belnr.
    endform.
    *&      Form  FILTER_DATA
          text
    -->  p1        text
    <--  p2        text
    form filter_data.
      sort itab by lifnr mblnr ebeln.
      loop at itab.
        if itab-bwart = '102'.
          delete itab where mblnr = itab-lfbnr
                      and   mjahr = itab-lfbja
                      and   zeile = itab-lfpos.
          delete itab.
        endif.
      endloop.
    endform.                               " FILTER_DATA
    *&      Form  FORMAT_DATA
          text
    -->  p1        text
    <--  p2        text
    form format_data.
      loop at itab.
        clear : ekbe,bkpf.
    *select * from ekbe
                into corresponding fields of table zxekbe
               where ebeln = itab-ebeln   "xmseg-ebeln
               and   ebelp = itab-ebelp   "xmseg-ebelp
               and   bewtp  in ('R', 'Q').
        select * from ekbe
                 into corresponding fields of table xekbe
                where ebeln = itab-ebeln   "xmseg-ebeln
                and   ebelp = itab-ebelp   "xmseg-ebelp
                and   lfbnr = itab-mblnr   "xmseg-mblnr
                and   lfgja = itab-mjahr   "xmseg-mjahr
                and   lfpos = itab-zeile   "xmseg-zeile
                and   bewtp in ('E', 'R').
        if sy-subrc = 0.
          loop at xekbe.
            case xekbe-bewtp.
              when 'E'.
                select single * from bkpf
                               where bukrs = 'GMI'
                              and   belnr like '%'
                              and   gjahr like '%'
                               and   bstat = space
                               and   xblnr = xekbe-xblnr
                               and   blart = 'WE'.
                              and   budat = xekbe-budat
                              and   bldat = xekbe-bldat and  blart = 'WE'.
                itab-wrbtr = xekbe-wrbtr.
                itab-dmbtr = xekbe-dmbtr.
                itab-kursf = bkpf-kursf.
                itab-accn = bkpf-belnr.
              when 'R'.
                select single * from bkpf
                               where bukrs = 'GMI'
                               and   belnr = xekbe-belnr
                               and   gjahr = xekbe-gjahr.
                move bkpf-belnr to itab-belnr.
                move bkpf-xblnr to itab-bxblnr.
                move bkpf-budat to itab-bbudat.
            endcase.
            select single * from bseg where bukrs = bkpf-bukrs and gjahr =
            bkpf-gjahr and belnr = bkpf-belnr and buzid = 'W'.
            itab-grri = bseg-hkont.
            clear bkpf.
          endloop.
        endif.
      read table zrseg with key  ebeln = itab-ebeln
                                 ebelp = itab-ebelp.
               on change of zrseg-belnr.
              if not icheck[] is initial.
              read table icheck with key checkdoc = zrseg-belnr.
                if sy-subrc <> 0.
                icheck-checkdoc = zrseg-belnr.
                 append icheck.
               move zrseg-belnr to itab-mirodoc.
               read table zxrbkp with key belnr = zrseg-belnr.
               if zxrbkp-budat >= itab-budat.
                  move zxrbkp-budat to itab-mbudat.
                endif.
               endif.
             else.
              move zrseg-belnr to itab-mirodoc.
               icheck-checkdoc = zrseg-belnr.
                 append icheck.
                endif.
                read table zxrbkp with key belnr = zrseg-belnr.
               if zxrbkp-budat >= itab-budat.
                  move zxrbkp-budat to itab-mbudat.
                endif.
               endon.
    read table zxekbe with key ebeln = itab-ebeln
                                       ebelp = itab-ebelp.
              move zxekbe-belnr to itab-mirodoc.
              move zxekbe-budat to itab-mbudat.
           clear: zxekbe.
    ********- SZ398R on 22.04.2008
        modify itab.
      endloop.
      sort itab by mblnr.
      counter = 0.
    endform.                               " FORMAT_DATA
    *&      Form  PRINT_DATA
          text
    -->  p1        text
    <--  p2        text
    form print_data.
      if hkont <> ''.
        delete  itab where not  grri in hkont.
      endif.
      loop at itab.
        clear flag.
        mirodoc = itab-mirodoc.
        mbudat  = itab-mbudat.
        on change of itab-mblnr.
          counter = counter + 1.
          write:/0(12)  itab-lifnr,        " to out-line+0(12).
                 13(10) itab-mblnr,        " to out-line+13(10).
                 24(10) itab-budat,        " to out-line+24(10).
                 36(16) itab-xblnr,        " to out-line+36(16).
                 53(10) itab-bldat,        " to out-line+53(10).
                 64(10) itab-ebeln,        " to out-line+64(10),
                 160(12) itab-accn,
                180(15) itab-grri.
          flag = 1.
        endon.
        if belnr = '   '.
          belnr = itab-belnr.
          xblnr = itab-bxblnr.
          budat = itab-bbudat.
          kursf = itab-kursf.
        endif.
        totlc = totlc + itab-dmbtr.
        totfc = totfc + itab-wrbtr.
        counter1 = counter1 + 1.
        at end of mblnr.
          if belnr = '   '.
            belnr = 'Nil'.
            nilcount = nilcount + 1.
          endif.
          write: 75(16)  totlc no-zero,
                 92(16)  totfc no-zero,
                 109(8)  kursf no-zero,
                 118(10) belnr,
                 129(16) xblnr,
                 146(10) budat,
                 198 mirodoc,
                 215 mbudat.
               CLEAR:mirodoc,mbudat  .
          clear: totlc, totfc, belnr, xblnr, budat.
        endat.
      endloop.
      uline.
      write : / counter, 'GRNs Selected'.
    write : / counter1, 'records selected.'.
      write : / nilcount, 'GRNs have no JV attached'.
      write : 69 '***END OF REPORT*****'.
    endform.                               " PRINT_DATA
    TOP OF PAGE *******************************
    top-of-page.
      uline.
      clear hdg-line.
      write : 'General Motors India Confidential' to hdg-line+90.
      write : hdg color col_heading intensified.
      clear hdg-line.
      write : 'Report : ZMM4' to hdg-line+1.
      write : hdg color col_heading intensified.
      clear hdg-line.
      write : 'Date   :' to hdg-line+10.
      write : sy-datum to hdg-line+20.
      write : sy-uzeit to hdg-line+39.
      write : 'Requested By :' to hdg-line+55.
      write : sy-uname to hdg-line+70.
      write : hdg color col_heading intensified.
      clear hdg-line.
      write :  'Goods Receiving Report' to hdg-line+45,
               'Page No.     : '    to hdg-line+75,
               sy-pagno             to hdg-line+91(3).
      write : hdg color col_heading intensified off.
      uline.
      clear hdg-line.
      write :/0(12)   'Vendor',            "          to hdg-line+0,
              13(10)  'GRN No.',           "          to hdg-line+13,
              24(10)  'GRN Date',          "          to hdg-line+24,
              36(16)  'Invoice No.',       "          to hdg-line+36,
              53(10)  'Inv. Dt.',          "          to hdg-line+53,
              64(10)  'PO No.',            "          to hdg-line+64,
              75(16)  'Amount in LC' right-justified, " to hdg-line+153,
              92(16)  'Amount in FC' right-justified, " to hdg-line+179,
              109(8)  'Exchg Rt' right-justified,     " to hdg-line+167,
              118(10) 'JV No.',            "          to hdg-line+193,
              129(16) 'JV.Reference',      "          to hdg-line+204,
              146(10) 'Post.date',         "          to hdg-line+221.
              160     'Account No',
              180     'Acc Post',
             198     'MIRO Document',
             215     'MIRO Post'.
    END OF CODE *******************************
    thanks
    sitaram

  • Changing a standard program

    hello
    hw to change the field names and output format of a standard program.

    What program is this ?
    Easier way to do will be to copy it into a Z program and then make modifications.
    Thanks

  • Suppress Information message during submit a standard program

    Hi experts,
    I am calling standard program RCATSCO from a report using following code:
    SUBMIT rcatstco WITH p_pernr  IN s_pernr
                      WITH p_date   IN lt_r_date
                      WITH p_belnr  IN s_belnr
                      WITH s_rkdauf IN s_rkdauf
                      WITH p_budat EQ sy-datum
                      WITH p_warn   EQ gc_x
                      EXPORTING LIST TO MEMORY
                      AND RETURN.
    When all data are already transferred to controlling this standard program displays a popup information message 'No data for transfer'. I need to suppress this popup and continue execution of the report. Please help.
    Thanks,
    Arnab

    One option is to do that check yourself and bypass submitting the program if there is no data to transfer. Another option is to submit the program via job. That way the the message will go to the job log. I see that you are using the option exporting list to memory, which means you want to read the spool after the program is executed. With the "via job" option, you may need to monitor the status of the job for completion and then read its spool.

Maybe you are looking for