T.code ME55

Hi Experts ,
I want to know where exactly the ALV GRID DISPLAY Function Module has been called in the program of T.code ME55(RM06BF00) , Actually my requirement is to add one more field (available stock of the material ) in the ALV Output of the T.code ME55 . I tried to find the field catalogue in the prog. RM06BF00 , but could'nt find it anywhere in the prog. Then I copied the prog. into a Z Report and after executing the Z report in the Selection screen I entered Release Code = G3 and Scope of List = ALV .
But an exit message comes saying ' Scope of list ALV not defined (please correct)' . However for another scope of list it is coming . Plese help .
Thanks ,
Suvendu

*& Report  ZBREAKDOWN
REPORT  ZBREAKDOWN NO STANDARD PAGE HEADING..
tables: CRHD, QMEL, QMFE, QMIH, QMUR, TQ80_T, TQ15T, QPGT, QPGR, t001w.
type-pools slis.
data : it_list type slis_t_listheader with header line,
       gt_evnt type slis_t_event with header line.
data : begin of outstand_wa occurs 0,
********Work Center Header
OBJTY       LIKE CRHD-OBJTY    ,  " Object types of the CIM resource
OBJID       LIKE CRHD-OBJID    ,  " Object ID of the resource
ARBPL       LIKE CRHD-ARBPL    ,  " Work center
WERKS       like CRHD-WERKS    ,  " Plant
VERWE       LIKE CRHD-VERWE    ,  " Work center cat.
VERAN       LIKE CRHD-VERAN    ,  " Person responsible for the work center
*********Quality Notification
CROBJTY     LIKE QMEL-CROBJTY  ,  " Object types of the CIM resource
ARBPLn      LIKE QMEL-ARBPL    ,  " Object ID of the Work Center
QMNUM       LIKE QMEL-QMNUM    ,  " Notification No
QMART       LIKE QMEL-QMART    ,  " Notification Type
QMTXT       LIKE QMEL-QMTXT    ,  " Short Text
QMDAT       LIKE QMEL-QMDAT    ,  " Date of Notification
AUFNR       LIKE QMEL-AUFNR    ,  " Order Number
**********Notification type texts
QMARTX      LIKE TQ80_T-QMARTX ,  " Notification Type Texts
*********Quality notification - items
FEKAT       LIKE QMFE-FEKAT    ,  " Catalog Type - Problems/Defects
FEGRP       LIKE QMFE-FEGRP    ,  " Code Group - Problem
FECOD       LIKE QMFE-FECOD    ,  " Problem or Damage Code
OTKAT       LIKE QMFE-OTKAT    ,  " Catalog Type - Object Parts
OTGRP       LIKE QMFE-OTGRP    ,  " Code Group - Object Parts
KOSTL       LIKE QMFE-KOSTL    ,  " Cost Center
FETXT       LIKE QMFE-FETXT    ,  " Notification Item Short Text
ERNAM       LIKE QMFE-ERNAM    ,  " Name of Person who Created the Object
ERDAT       LIKE QMFE-ERDAT    ,  " Date on Which Record Was Created
AENAM       LIKE QMFE-AENAM    ,  " Name of Person Who Changed Object
AEDAT       LIKE QMFE-AEDAT    ,  " Changed On
*****Inspection catalog type index
SPRACHE     LIKE TQ15T-SPRACHE    , " Language Key
KATALOGART  LIKE TQ15T-KATALOGART , " Catalog
KATALOGTXT  LIKE TQ15T-KATALOGTXT , " Catalog Text
**********Code group texts
CODEGRUPPE  LIKE QPGT-CODEGRUPPE  , " Code Group
KURZTEXT    LIKE QPGT-KURZTEXT    , " Short Description of the Code Group
**********Inspection catalog code groups
*KURZTEX     LIKE QPGR-KURZTEXT    , "
*********Quality message - maintenance data excerpt
MSAUS       LIKE QMIH-MSAUS    ,  " Breakdown Indicator
AUSVN       LIKE QMIH-AUSVN    ,  " Start of Malfunction (Date)
AUSBS       LIKE QMIH-AUSBS    ,  " End of Malfunction (Date)
AUZTV       LIKE QMIH-AUZTV    ,  " Start of Malfunction (Time)
AUZTB       LIKE QMIH-AUZTB    ,  " End of Malfunction (Time)
AUSZT       LIKE QMIH-AUSZT    ,  " Breakdown Duration
INGRP       LIKE QMIH-INGRP    ,  " Planner Group for Customer Service and Plant Maintenance
*********Quality notification - causes
URTXT       LIKE QMUR-URTXT    ,  " Cause Text
URKAT       LIKE QMUR-URKAT    ,  " Catalog Type - Causes
URGRP       LIKE QMUR-URGRP    ,  " Code Group - Causes
URCOD       LIKE QMUR-URCOD    ,  " Cause Code
*********Person responsible for the work center
KTEXT       LIKE TC24-KTEXT    ,  " NAME OF THE PERSON RESP.
*****Plants/Branches
stras       like t001w-stras   ,
pstlz       like t001w-pstlz   ,
adrnr       like t001w-adrnr   ,
ort01       LIKE t001w-ort01   ,
BIND(3),
KATALOG(40),
ddiff TYPE  p,
tdiff TYPE  p DECIMALS 2,
d3 type p,
t3 type minutes,
m_break type sy-uzeit,
t4(16) type p,
t6 type sy-tabix,
t7 type swl_pm_cvh-duration,
t5 type swl_pm_cvh-duration,
end of outstand_wa.
*data : outstand_hd type standard table of  outstand_wa initial size 0 with header line.
data : tab_etab type standard table of etab,
       wa_etab type etab.
DATA: is_layout TYPE slis_layout_alv.
DATA: M_TIME TYPE SY-UZEIT VALUE 24.
data: l_start     type t,
      l_end       type t,
      l_startdate type d,
      l_enddate   type d,
      l_hours     type p decimals 2.
*DATA :  DATE1 TYPE SY-DATUM,
       TIME1 TYPE SY-UZEIT,
       DATE2 TYPE SY-DATUM,
       TIME2 TYPE SY-UZEIT.
selection-screen begin of block plant with frame title text-001.
select-options : m_plant for CRHD-WERKS obligatory .  " Plant
select-options : m_work  for CRHD-ARBPL .             " Work center
select-options : m_catg  for CRHD-VERWE .             " Work center cat.
select-options : m_pern  for CRHD-VERAN .             " Person responsible for the work center
select-options : m_type  for QMEL-QMART .             " Notification Type
select-options : m_date  for QMEL-QMDAT obligatory.   " Date of Notification
select-options : m_ordr  for QMEL-AUFNR .             " Order Number
select-options : m_cost  for QMFE-KOSTL .             " Cost Center
selection-screen end of block plant.
selection-screen begin of block radi with frame title text-004.
*parameters list      radiobutton group rad1.
parameters grid      radiobutton group rad1.
parameters alv       radiobutton group rad1.
selection-screen end of block radi.
data: fieldcat type slis_t_fieldcat_alv .
select CRHDOBJTY   CRHDOBJID CRHDARBPL CRHDWERKS CRHDVERWE CRHDVERAN
       QMELCROBJTY QMELARBPL QMELQMNUM QMELQMART QMELQMTXT QMELQMDAT QMEL~AUFNR
       TQ80_T~QMARTX
       QMFEFEKAT   QMFEFEGRP QMFEFECOD QMFEOTKAT QMFEOTGRP QMFEKOSTL QMFEFETXT QMFEERNAM QMFEERDAT QMFEAENAM QMFE~AEDAT
       TQ15TSPRACHE TQ15TKATALOGART TQ15T~KATALOGTXT
       QPGTCODEGRUPPE QPGTKURZTEXT
       QMIHMSAUS   QMIHAUSVN QMIHAUSBS QMIHAUZTV QMIHAUZTB QMIHAUSZT QMIH~INGRP
       QMURURTXT   QMURURKAT QMURURGRP QMURURCOD
       TC24~KTEXT
       T001WSTRAS  T001WPSTLZ T001WADRNR T001WORT01
into table outstand_wa
     from CRHD
INNER JOIN QMEL   ON CRHDOBJID = QMELARBPL
INNER JOIN QMFE   ON QMELQMNUM = QMFEQMNUM
INNER JOIN QMIH   ON QMFEQMNUM = QMIHQMNUM
INNER JOIN QMUR   ON QMIHQMNUM = QMURQMNUM
INNER JOIN TC24   ON CRHDVERAN = TC24VERAN
INNER JOIN T001W  ON CRHDWERKS = T001WWERKS
INNER JOIN TQ80_T ON QMELQMART = TQ80_TQMART
INNER JOIN TQ15T  ON QMFEFEKAT = TQ15TKATALOGART
INNER JOIN QPGT   ON QMFEFEGRP = QPGTCODEGRUPPE
WHERE CRHDWERKS IN m_plant AND CRHDARBPL IN m_work AND CRHDVERWE IN m_catg AND CRHDVERAN IN m_pern
AND QMELQMART IN m_type AND QMELAUFNR IN m_ordr AND QMFEKOSTL IN m_cost AND TQ15TSPRACHE = 'E' AND QMEL~QMDAT IN m_date.
*AND QMEL~QMDAT IN m_date
**AND CRHDARBPL IN m_work AND CRHDVERWE IN m_catg AND CRHD~VERAN IN m_pern
**AND QMELQMART IN m_type AND QMELQMDAT IN m_date AND QMELAUFNR IN m_ordr AND QMFEKOSTL IN m_cost AND TQ15T~SPRACHE = 'E'.
*AND QPGTCODEGRUPPE = QMFEOTGRP.
if sy-subrc = 0.
LOOP AT outstand_wa.
  if outstand_wa-MSAUS = 'X'.
     outstand_wa-BIND = 'YES'.
     modify outstand_wa transporting BIND.
  endif.
  if outstand_wa-MSAUS = ' '.
     outstand_wa-BIND = 'NO'.
     modify outstand_wa transporting BIND.
  endif.
if outstand_wa-URKAT = '1'.
   outstand_wa-KATALOG = 'Characteristic Attributes'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = '2'.
   outstand_wa-KATALOG = 'Tasks'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = '3'.
   outstand_wa-KATALOG = 'Usage Decisions'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = '4'.
   outstand_wa-KATALOG = 'Events'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = '5'.
   outstand_wa-KATALOG = 'Causes'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = '6'.
   outstand_wa-KATALOG = 'Results of Defects'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = '8'.
   outstand_wa-KATALOG = 'Activities(QM)'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = '9'.
   outstand_wa-KATALOG = 'Defect Types'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = 'A'.
   outstand_wa-KATALOG = 'Activities(PM)'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = 'B'.
   outstand_wa-KATALOG = 'Object Parts'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = 'C'.
   outstand_wa-KATALOG = 'Overview of Damage'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = 'D'.
   outstand_wa-KATALOG = 'Coding'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = 'E'.
   outstand_wa-KATALOG = 'Defect Locations'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = 'F'.
   outstand_wa-KATALOG = 'Decision(SPM Returns)'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = 'G'.
   outstand_wa-KATALOG = 'Defect(SPM Returns)'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = 'H'.
   outstand_wa-KATALOG = 'Effort(SPM Returns)'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
if outstand_wa-URKAT = 'I'.
   outstand_wa-KATALOG = 'Follow-Up Activity(SPM Returns)'.
   MODIFY outstand_wa TRANSPORTING KATALOG.
ENDIF.
ENDLOOP.
ENDIF.
IF outstand_wa-MSAUS = 'X'.
BIND = 'YES'.
ELSEIF outstand_wa-MSAUS = '  '.
BIND ='NO'.
ENDIF.
*ENDLOOP.
*ENDIF.
case 'X'.
    WHEN LIST.
    PERFORM SIMPLE_LIST.
  when grid.
    perform writ_list.
    perform calculation.
  when alv.
    perform writ_alv.
    perform calculation.
   DATA: layout TYPE slis_layout_alv.
   PERFORM build_field_catalog.
   CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
     EXPORTING
       is_layout              = layout
       it_fieldcat            = fieldcat
       i_callback_top_of_page = 'TOP_OF_PAGE'
       it_events              = gt_evnt[]
     TABLES
       t_outtab               = outstand_wa.
endcase.
*&      Form  BUILD_LAYOUT
      Build layout for ALV grid report
*form build_layout.
gd_layout-no_input          = 'X'.
gd_layout-colwidth_optimize = 'X'.
gd_layout-totals_text       = 'Totals'(201).
*gd_layout-totals_text       = 'Totals'.
Set layout field for row attributes(i.e. color)
gd_layout-info_fieldname =      'LINE_COLOR'.
gd_layout-totals_only        = 'X'.
gd_layout-f2code            = 'DISP'.  "Sets fcode for when double
                                        "click(press f2)
gd_layout-zebra             = 'X'.
gd_layout-group_change_edit = 'X'.
gd_layout-header_text       = 'helllllo'.

Similar Messages

  • Badi/user exit in tcodes me54n,me55,me28 and me29n

    hi all,
    1.which is the badi/user exits that is there in me54n and me55...for saving and releasing purchase requisation(s) .
    2.which is the badi/user exits that is there in me28 and me29n...for saving and releasing purchase order(s) .
    points will be rewarded.
    regards,
    johnson

    Transaction Code - ME54N                    Release Purchase Requisition                                                                               
    Enhancement                                                                               
    MEREQ001                                Customers' Own Data in Purchase Requisition                                                                               
    Business Add-in                                                                               
    ME_COMMITMNT_PARKING                    BAdI for Redefining Commitment Interface When Parking   
    ME_MEREQ_PARKING                        BAdI Purchase Requisition: "Hold"                       
    ME_REQ_HEADER_TEXT                      Copy Header Text: Enjoy Purchase Requisition
    Transaction Code - ME55                     Collective Release of Purchase Reqs.
    Enhancement                                                                               
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N               
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number                           
    MM06E004                                Control import data screens in purchase order              
    MM06E005                                Customer fields in purchasing document                     
    MM06E007                                Change document for requisitions upon conversion into PO   
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator                 
    MM06E010                                Field selection for vendor address                         
    MMAL0001                                ALE source list distribution: Outbound processing          
    MMAL0002                                ALE source list distribution: Inbound processing           
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses                                 
    MMFAB001                                User exit for generation of release order                  
    MRFLB001                                Control Items for Contract Release Order                   
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    AMPL0001                                User subscreen for additional data on AMPL                 
    LMEDR001                                Enhancements to print program                              
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination                         
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt 
    LWSUS001                                Customer-Specific Source Determination in Retail           
    M06B0001                                Role determination for purchase requisition release        
    M06B0002                                Changes to comm. structure for purchase requisition release
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)  
    MEETA001                                Define schedule line type (backlog, immed. req., preview)  
    ME590001                                Grouping of requsitions for PO split in ME59               
    M06E0005                                Role determination for release of purchasing documents     
    M06E0004                                Changes to communication structure for release purch. doc. 
    M06B0005                                Changes to comm. structure for overall release of requisn. 
    M06E0004                                Changes to communication structure for release purch. doc. 
    M06B0005                                Changes to comm. structure for overall release of requisn. 
    M06B0004                                Number range and document number                           
    M06B0003                                Number range and document number                           
    Business Add-in                                                                               
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.  
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting                  
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer              
    ME_PO_PRICING                           Enhancements to Price Determination: Internal              
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use   
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation        
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order             
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO             
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields                 
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions     
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions     
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer 
    SMOD_MRFLB001                           Control Items for Contract Release Order                   
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order  
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address                          
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder    
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV           
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE                 
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address                   
    ME_REQ_POSTED                           Purchase Requisition Posted                                
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions     
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu. 
    ME_PURCHDOC_POSTED                      Purchasing Document Posted                                 
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer          
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal          
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders          
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant          
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active                
    ME_BSART_DET                            Change document type for automatically generated POs       
    ME_BAPI_PR_CREATE_02                                                    ME_BAPI_PO_CREATE_01                                                                               
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked     
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level    
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI                              
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data              
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)          
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)         
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders          
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active       
    ME_COMMITMENT_RETURN                    Commitment for return item                                 
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing            
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control         
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India              
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details                   
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges                      
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking         
    ME_CHECK_OA                             Check BAdI for Contracts                                   
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO    
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing                      
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation

  • ME55 - Release Purchase Request

    Hi Gurus,
    I am facing problem in T-Code ME55 throwing message by SU53 that authorization obj : M_BANF_FRG and Pur. Req. Release code x9. I have changed Role and assign the said obj. but when i exec. the t-code me55 this execute sucessfully. But there is no pur. req. pending for release. But WhenIi see the same in another login then there are so many pur. req. are pending for release, what will the cause?  pl help.
    Regards,

    Hi,
    You have problem only in configuration to the best of my understanding .
    If that is not there than in the CL20N where you create master data for release strategy.
    Try to do a check why release strategy is not applying by carefully examining the data you have key in.
    Don't do too many things at the same time.
    I suggest you to check the data.
    Also if you don't put the value for any of the release characterstic and that characterstic is assigned to the class Release strategy will not work.
    Please refer to SAP Note 207490, 365604 & 493900 for your better understanding.
    Regards
    Ankur

  • Certain PR is not showing in collective release ME55.

    Dear Experts
    My clients is experiencing one issue at the time of collective release of PR using T. Code ME55. Certain PR is not showing at the time of  executing  with  giving required input Release group and release code, however if the execution is done by giving input  Release group, release code and Purchase Requisition the same document is showing. can any one tell me the possible reason for the same. Why the PR is not displaying for release using release code and release group in ME55.
    Below Investigation has been done.
    1. For single line item single PR is created  through PS route using T.Code CJ20N.
    2. Account assignment for the PR is "Q" Project Make to Order.
    3. Line item not deleted for the same PR.
    4. Status showing as 03 In Release (In Status tab).
    5. in "Quantities/Dates" tab Closed check box in not activated.
    Regards
    Sanjib Naik
    Message was edited by: Sanjib Naik

    Hi Dev,
    By default system is taking "Sort Indicator 1" Sorting by Purchase requisition number & item. with the combination of  Release Code & Release Group.
    I have tried with giving input  Release Code, Release Group & Purchase Requisition Number
    10032658 & 10034951after executing the sysem is showing Only one PR Number i.e 10032658  with 2 line item.
    Here system is showing duplicate entry for PR. 10032658 of the first line item and ignoring to display the 10034951 details.
    Final conclusion is that, system is not showing last PR Number. Instead of that 2nd last PR is displaying with duplicate entry.Please see the screenshot.
    1. PR Number : 10034951 Delivery date is 30.08.2014 (Which is not Showing in ME55).
    1. PR Numebr:   10032658 Delivery date is 10.07.2015 (Which is showing in ME55)
    Thanks & Regards,
    Sanjib Naik

  • Enhancement for me55

    Hi ,
    A field has been added through append structure in the output structure of T. code me55 , program - RM06BF00 , That field (stock)is also available in the field catalogue of the output . Now I want to populate the field with the available stock of the material . Please help if badi or user exit can be used .
    Regards ,
    Suvendu

    Hi,
    Check these...
    MM06E008     Monitoring of contr. target value in case of release orders
    MMFAB001      User exit for generation of release order
    MRFLB001      Control Items for Contract Release Order
    M06B0001      Role determination for purchase requisition release
    M06B0002      Changes to comm. structure for purchase requisition release
    M06E0005      Role determination for release of purchasing documents
    M06E0004      Changes to communication structure for release purch. doc.
    M06B0005      Changes to comm. structure for overall release of requisn.
    SMOD_MRFLB001      Control Items for Contract Release Order
    ME_RELEASE_CREATE      BAdI: Release Creation for Sched.Agrmts with Release Docu.

  • PR Approval - Create PO

    Hello Team!
    Please help on the below.
    1) PR - There are say 2 levels of approvals Pur Mgr then Fin Controller
    There are 20 PR's for approval for both these approvers.
    How can each of them see simultaneously all of the PR's what all each one need to approve, so that they can do it ata time, instead of going into ME54N for each one of them ?
    2) How to automaticallly create PO's for all the approved PR's, INSTEAD  of going to ME21N , "document overview"  and pulling up alll  PR's and dropping them into the basket
    3) Once the PO is created for a PR , that PR should not show up or show up in the "document overiviw" of ME21N
    I created a PO for a PR and when checked by going to ME23N, clicked "document overview off" i then  selection criteria , chose the "Pur group" and even thecPR which had the PO created showed up.
    Appreciate anybody's input and help.
    Best Regards

    Hi,
    1)  Using T-CODE ME55 - Collective Release of Purchase Requisitions, cumulative PR released at a one time as follows.
        - Type ME55 and give input data's & select the below options.
             - Release Code   ________ ( Ist release code of  your Pur.Manager)
                Release Prerequisite Fulfilled ticked
                Requisns for Overall Release ticked
                Requisns for Item-wise Release ticked
             - Scope of List 'ALV' selected
             - Sort Indicator '1' selected
        Now, execute the report (click Clock) and then shown your Pur.manager approve all PR list. After Pur.manager approved all PR, the above steps doing for  your Fin.Controller and give Release Code of Fin.controller and executed it shown 2nd release of all approve PR list by Fin.controller.
    2) Using T-code ME59N - Automatic creation of Purchase Orders from Requisitions.
    3) Using ME21N - Create Purchase Order, Document overview options select Purchase Requisition and  then selected 'Open Only, Release Only and Assigned, Open  and Released ' options. it shown all Purchase requisition without create purchase order  and released PR List.
    Hope, it is useful for you.
    Regards,
    K.Rajendran

  • Error when Release Purchase Requisition

    Hi All
    I want to Release for Purchase Requisition
    I have already setup follow : http://www.sap123.com/showthread.php?t=59
    When I use T.Code ME55, I can't tick check box
    http://s37.photobucket.com/albums/e73/caodanhthang/?action=view&current=ME55.jpg.
    I can chose Select All
    Could you please tell me why and how to repair ?
    Thank and Best regards,
    Thang

    Hi,
    This Scope Of List determines how the list is edited.
    Example, the lists can be shown in one-line form, without detailed information, or in multi-line form with detailed information.
    Here Scope Of List "F" recommends Collective Releases.
    So u have to choose F and execute.
    Thanks & Regards
    Anilkumar Dalai

  • SAP Business Workflow - BUS2105

    Dear All
    I am using T-Code SWDD to run the workflow manually, its working fine and trigerring the workflow in user inbox.
    But when I relase the PR from T-Code Me55, workflow is not triggering.
    please reply.

    Hi Adnan,
    To Trigger your Workflow automatically you need to configure it along with the BUSINESS OBJECT in the tcode BSVW.
    Let me know if any clarification/help required.
    Thanks & Best Regards.
    Pavan Neerukonda.

  • Call  transaction  inside  job

    hi all,
    I have  a call  transaction program for tcode ME55, the  probleme  is when  i  execute the  program  directly  via  se38  to  release the sales  documents it work  fine,   on the other hand when i call  the program  via SM37  nothing  will  happen.
    thanks,
    karim

    Hi,
    What exactly do you want to do by calling t.code me55 ? Upload some data in background or display the transaction to a user only ?
    If you want to do a call transaction in background, you will have to pass BDC data to it as well. Then transaction will run with the passed data then. To know what data to pass, simply record your transaction in SHDB T.code and create a program for the BDC.
    ME55 is a report, so perhaps you can use SUBMIT with the selection parameters in your program to be able run that program in background.
    regards,
    Advait

  • Who released purchase requisition

    Hello,
    is there a way to find out the user name who released a purchased requisition?
    Thanks
    Anne

    hi
    goto the PR
    then in environment select item changes
    there u will find the changes with t code ME55 (release )
    from there u will get the user id who changed the PR status to released in transaction me55
    regards
    kunal

  • Authorization in Purchasing documents

    Hello,
    A couple of weeks ago a posted a question about the use of generic reléase codes for managers of different company codes or business áreas.
    As I understand the answers, one can use generic reléase codes and restrict the approval with autorization objects like M_BEST_WRK (plant-restricción) so that managers from one plant can not approve the purchasing documents of other plants for which they are not autorized (although they share the same reléase code!)
    Nevertheless I still got left with the following doubt:
    All the managers with lets say have release code "SM"  (Senior managers) in their profile, will be able to see in the ME55 and ME28 the purchasing documents of the other plants (although through restrictions with autorization object M_BEST_WRK will not be able to approve them!)?
    This is a situation my client does not want to occur. If the "visibility" of the purchasing documents for approval, is not restricted by autorization object M_BEST_WKR, how can one acomplish this. Does one need to créate a ZME55 or a ZME28 to filter?
    Thanks for any reply.
    Aart

    Aart Engbersen wrote:
    All the managers with lets say have release code "SM"  (Senior managers) in their profile, will be able to see in the ME55 and ME28 the purchasing documents of the other plants (although through restrictions with autorization object M_BEST_WRK will not be able to approve them!)?
    No. (s)he will not able to see these purchase requisitions which has created with a plant but the user is not authorized for the plant.
    For Example:
    I've two users. One is having only authorization for plant LXK1 and another is having authorization for all plants
    I've created two purchase requisitions as 10001514 for plant LX01 and 10001515 for plant LXK1.
    When I execute ME55 for the user (who is having authorization for all plants), he can see both preqs.
    But when I execute the t-code ME55 from this user (who is having authorization only for plant LXK1)
    He can able to see the preq with only for the plant LXK1.

  • Download the the user ID of Purchase Requisition Releaser.

    The user use t-code ME55 or ME54N to release the purchase requisition,
    We want to download using t-code SE16 or Query, a list of user ids who has released the Purchase Requisitions. What is the table that can give this information and downloadable via SE16 or query??

    hi
    I am not sure about table but indivisualy from PR u can get list of user id u have processed release
    In ME53/ME53N  go to menu bar>Environment>Item changes--> u will get user id and trnx. used for release
    Note --select line item before going to above path
    Vishal...

  • Report to Show PR that are not released by release codes

    Hello Experts,
    I would like to know if there is any report on SAP 6.0 that shows all the purchase requisitions that are not released which shows the releease code (the person's name who has to release the PR). In me55 only could be found by release code, and it is required, I cannot has a report
    I think that there is not, but i would like to confirm it.
    Thank you in advance,
    Best regards

    Hello,
    1)Go to ME5A t-code & select DYNAMIC SELECTIONS.
    2)Select "Purchase Requisition" section and you can make use of parameters like Release Code, Release Indicator , Release Status etc., to fetch the required results.
    Hope this helps you in resolving your matter.
    Regards
    Mahesh

  • What are the T-codes that contain the master data for material and vendor?

    what are the T-codes that contain the master data for material and vendor?

    hi ,
    - Display Material  tcodes...
    MM01 - Create Material
    MM02 - Change Material
    MM03 - Display Material
    MM50 - List Extendable Materials
    MMBE - Stock Overview
    MMI1 - Create Operating Supplies
    MMN1 - Create Non-Stock Material
    MMS1 - Create Service
    MMU1 - Create Non-Valuated Material
    ME51N - Create Purchase Requisition
    ME52N - Change Purchase Requisition
    ME53N - Display Purchase Requisition
    ME5A - Purchase Requisitions: List Display
    ME5J - Purchase Requisitions for Project
    ME5K - Requisitions by Account Assignment
    MELB - Purch. Transactions by Tracking No.
    ME56 - Assign Source to Purch. Requisition
    ME57 - Assign and Process Requisitions
    ME58 - Ordering: Assigned Requisitions
    ME59 - Automatic Generation of POs
    ME54 - Release Purchase Requisition
    ME55 - Collective Release of Purchase Reqs.
    ME5F - Release Reminder: Purch. Requisition
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB21 - Create Reservation
    MB22 - Change Reservation
    MB23 - Display Reservation
    MB24 - Reservations by Material
    MB25 - Reservations by Account Assignment
    MBRL - Return Delivery per Mat. Document
    MB1C - Other Goods Receipts
    MB90 - Output Processing for Mat. Documents
    MB1B - Transfer Posting
    MIBC - ABC Analysis for Cycle Counting
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI01 - Create Physical Inventory Document
    MI02 - Change Physical Inventory Document
    MI03 - Display Physical Inventory Document
    MI31 - Batch Input: Create Phys. Inv. Doc.
    MI32 - Batch Input: Block Material
    MI33 - Batch Input: Freeze Book Inv.Balance
    MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
    MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
    MIQ1 - Batch Input: PhInvDoc. Project Stock
    MI21 - Print physical inventory document
    MI04 - Enter Inventory Count with Document
    MI05 - Change Inventory Count
    MI06 - Display Inventory Count
    MI09 - Enter Inventory Count w/o Document
    MI34 - Batch Input: Enter Count
    MI35 - Batch Input: Post Zero Stock Balance
    MI38 - Batch Input: Count and Differences
    MI39 - Batch Input: Document and Count
    MI40 - Batch Input: Doc., Count and Diff.
    MI08 - Create List of Differences with Doc.
    MI10 - Create List of Differences w/o Doc.
    MI20 - Print List of Differences
    MI11 - Physical Inventory Document Recount
    MI07 - Process List of Differences
    MI37 - Batch Input: Post Differences
    for vendor..
    XKN1  Display Number Ranges (Vendor)
    XK01  Create vendor (centrally)
    XK02  Change vendor (centrally)
    XK03  Display vendor (centrally)
    XK04  Vendor Changes (Centrally)
    XK05  Block Vendor (Centrally)
    XK06 Mark vendor for deletion (centrally
    XK07  Change vendor account group
    XK11  Create Condition
    XK12  Change Condition
    XK13  Display Condition
    XK14  Create with cond. ref. (cond. list)
    XK15  Create Conditions (background job)
    reward points if useful,
    venkat.

  • RS232 control of a Samsung ME55A

    I am trying to setup RS232 control over a new ME55A Samsung display.  I have tried every combination of cabling and codes I can come up with but the display does not respond.  The unique thing about this setup is the display uses a mini 3.5 jack to DB9 for it's RS232C connection.  Also the TV documentation keeps mentioning it's MDC program for remote controlling it when referencing RS232.  Is this TV not capable of basic RS232 control?  Am I missing something else?
    Here is the example of how to com e up with the code (example is actually the code I need/use too):
    https://supportforums.cisco.com/docs/DOC-14104
    Here you can access the user manual for it:
    http://www.samsung.com/us/business/support/downloads/led/LH55MEPLGA/ZA
    I've been able to do this on a wide varietly of panasonics and LG's, so this is driving me nuts!
    Thanks
    -Gordy

    Oct 2, 2012 5:57 AM                             (in response to bdavenpo)
    RS232 Pinout for DMP4400G
    I have  been using the 9pin to mini 3.5mm that is included with the DMP4310 on  the DMP4400 to conect to the ME46 & ME55 Samsung. The pin out is in  the Cisco Stadium Vision PDF on page 100.
    http://www.cisco.com/en/US/docs/Sports_Entertainment/StadiumVision/Director/design/guides/3_0/SV_Video_Endpoint_DIG_3.0.pdf
    I have found several of the adapters included with the Samsung monitors don't work.

Maybe you are looking for