Custom field in Purchase Requisition Release

Hi all,
I have create a popup with a custom field when the user releases first step of a Requisition Release, via ME54N.
The system don't save my custom field, I have used this exit:
EXIT_SAPLMEREQ_005 of the ampliament MEREQ001.
my code:
   CALL SCREEN 999 STARTING starting at 5 10                 MOVE: eban-zzsubmi       TO ls_item-zzsubmi,
            eban-zzappunto     TO ls_item-zzappunto,
            zzautfor           TO ls_item-zzautfor,
            eban-zzattautor    TO ls_item-zzattautor,
            eban-zzdatattoauto TO ls_item-zzdatattoauto.
   CALL METHOD im_req_item->set_data( ls_item ).
the ls_item, is ok, with my custom field, but seeing in debug this method, the system don't save my field.
Maybe we don't have the permission of change custom field on EKKO during Release step?
Thanks all.
Reward for all.

Hi ,
Try with create new tab in PR item level, add field in custom tab example Final release Tab.
Try to fetch data from EBAN table when final release happened ( based on status ) the date will update in this table. I hope this is helpful.
Use user exit to create custom tab and custom field 
enhancement MEREQ001 : check this enhancement.
user exit EXIT_SAPLMEREQ_0*
I hope it is helpful

Similar Messages

  • Customer field to purchase requisition

    Hello,
    I add the customer field at subscreen of purchase requisition ( at the data base table i add the relative field in ci_ebandb include ) by EXIT_SAPLMEREQ_001 and
    EXIT_SAPLMEREQ_002 and EXIT_SAPLMEREQ_003.
    I add the same customer field at subscreen of purchase order ( at the data base table i add the relative field in ci_ekpodb include ) by EXIT_SAPLMEREQ_016 and EXIT_SAPLMEREQ_017 and EXIT_SAPLMEREQ_018.
    The problem is: when i convert the purchase requisition in purchase order, the data into customer field of
    purchase requisition not are transfert in the customer field of purchase order.
    thanks for help,
    Roberto Baldassarre.

    correction **
    tks for your help,
    but i had just done it. I explain with detail my step:
    I add the customer field at subscreen of purchase requisition by
    EXIT_SAPLMEREQ_001 and EXIT_SAPLMEREQ_002 and EXIT_SAPLMEREQ_003 (at
    the data base table I add the relative field on ci_ebandb include).
    I add the same customer field at subscreen of purchase order by
    EXIT_SAPMM06E_016 and EXIT_SAPMM06E_017 and EXIT_SAPMM06E_018 (at
    the data base table i add the relative field on ci_ekpodb include).
    Step followed:
    1. add field at EBAN table by CI_EBANDB include
    2. add same field at EKPO table by CI_EKPODB include.
    3. write code at EXIT_SAPLMEREQ_001,EXIT_SAPLMEREQ_003 following
    document's help.
    4. write code at EXIT_SAPMM06E_016, EXIT_SAPMM06E_017 ,
    EXIT_SAPMM06E_018 following document's help.
    5. build dynpro 0111 on function group XM02
    6. build dynpro 0111 on function group XM06
    The problem is: when i convert the purchase requisition in purchase
    order (ME59n), the data into customer fields of purchase requisition
    not are copied in the customer fields of purchase order (this field are
    empty).
    Tks for your help!

  • Overall Purchase requisition Release strategy : Changed after Rejected

    Hi All,
        I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
      Problem I have is when PR is rejected .
    When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
    But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point. 
    ME52 changes for PR is not trigerring any event which can trigger the WF.
    Is there any way we can trigger Workflow in this scenerio.
    Please suggest.

    Hi Subhashini,
    This all depend on release strategy. release should reset completely on tha change.
    For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
    When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
    If no other release strategy is determined by the reduction of the
    amount or value, the system will keep already existing releases.
    changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
    Sanjeev

  • Customer Subscreen for Purchase Requisition

    Hello All,
    I need a custom subscreen on requisition at <b>HEADER</b> level.  'MEREQ001' adds a screen at item level. Is there any Screen Exit / BADI to add a custom screen at header level? Any kind of help is really appreciated.
    Thank you all,
    Chandni

    Hi Chandi Reddy,
    The t.code is ME51 For this available exits are :
    AMPL0001  User subscreen for additional data on AMPL
    LMEDR001  Enhancements to print program
    LMELA002  Adopt batch no. from shipping notification when posting
    LMELA010  Inbound shipping notification: Transfer item data from
    LMEQR001  User exit for source determination
    LMEXF001  Conditions in Purchasing Documents Without Invoice Rece
    LWSUS001  Customer-Specific Source Determination in Retail
    M06B0001  Role determination for purchase requisition release
    M06B0002  Changes to comm. structure for purchase requisition rel
    M06B0003  Number range and document number
    M06B0004  Number range and document number
    M06B0005  Changes to comm. structure for overall release of requi
    M06E0004  Changes to communication structure for release purch. d
    M06E0005  Role determination for release of purchasing documents
    ME590001  Grouping of requsitions for PO split in ME59
    MEETA001  Define schedule line type (backlog, immed. req., previe
    MEFLD004  Determine earliest delivery date f. check w. GR (only P
    MELAB001  Gen. forecast delivery schedules: Transfer schedule imp
    MEQUERY1  Enhancement to Document Overview ME21N/ME51N
    MEVME001  WE default quantity calc. and over/ underdelivery toler
    MM06E001  User exits for EDI inbound and outbound purchasing docu
    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 P
    MM06E008  Monitoring of contr. target value in case of release or
    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 proces
    MMAL0004  ALE purchasing info record distribution: Inbound proces
    MMDA0001  Default delivery addresses
    MMFAB001  User exit for generation of release order
    MRFLB001
    For t.code we51n the available exits and badi are :
    Enhancement/ Business Add-in            Description
    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
    o.of Exits:          1
    o.of BADis:          3
    Rewards some points.
    Rgds,
    P.Naganjana Reddy

  • Purchase requisition release strategy tab missing

    Hi all
    I configured purchase requisition release strategy and ME51N is working issuing no error but it is not displaying Release Strategy Tab , please help me where i am wrong.

    hi,
    check few reasons:
    1. There might be more than 1 release strategy using the same class, due to which it is not possible for sap system to determine the unique rel. strategy..this normally happens when you copy the exsisting class and assign it to own new one...
    2. check the release strategy OMGSCK, is there any problem with your release strategy...
    3. Check whether you have maintained all the classified field in the document or not..
    4. check whether the release is assigned to any workflow...if so, then check the inbox pls...
    regards
    Priyanka.P

  • Custom Event for Purchase Requisition Create, Change & Delete

    Hello Experts,
    I want to create a custom event which triggers on Purchase Requisition Create, SAP provide's standard event's for purchase requisition release but not for create.
    What are all the steps and how to create a new event.
    Thanks in Adavance,
    Sandhya.

    Hi Sandhya,
    may i know the reason why you are trying to create custom methods.
    You have business object BUS2009(for PR line item wise release) and BUS2105(for PR overall release).
    Both those business object have events RELEASESTEPCREATED (for PR creation) and SIGNIFICANTLYCHANGED(For PR change).
    Even then if you want to create custom events, create a subtype of the standard business object, then click on events, and then select create. Now create your Z-events, say ZCREATED (For creation), ZCHANGED (for changed) and ZDELETED (for deleted). Now select each event, click on edit -> Change release status -> object type component -> to be implemented. Follow the same for all the events. Then select each event, click on edit -> Change release status -> object type component -> to be released.
    Now click on your custom object, click on edit -> Change release status -> object type component -> to be implemented.Then click on your custom object, click on edit -> Change release status -> object type component -> to be released.
    After this in SWEC tcode, click on new entries. Select change document object as BANF, business object as say ZBUS2105 and event as ZCREATED. make sure radio button on create is checked.
    Similary create entries for ZCHANGED event and ZDELETED.
    Select on change and on delete radio button for event ZCHANGED and ZDELETED event respectively.
    let me know if you have any queries.
    Regards,
    Raj

  • Purchase Requisition release

    Hi,
    Could anybody help me out with the configuration settings of purchase requisition Release.
    Client want to set release status for Purchase Requisition , where two persons will be responsible to release the requisition . when the first person releases the requisition , it will come to the second or final person for release ,when he releases then the requisition is released for purchase orders.
    Could anybody help me out with the configuration settings.
    Thanks N Regards,
    Siddhartha

    Use this steps. below is for PO same do it with PR. that is in place of PO take it as PR.
    Releasing Procedure for Purchase Documents
    Use
    This setting is incorporated to just give demonstration of how SAP Release procedure works.  The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle.  The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
    3.4.24.1     Creation of Characteristics
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Characteristic
    Transaction Code     CT04
    2.     On the Characteristic screen, make the following entries.
    3.     In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
    Field name     Description     User action and values     Note
    Select Addnl Data tab                
    Table Name     Table Name     CEKKO     
    Field Name     Field Name     GNETW     
    Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
    Select Basic Data tab               
    Description     Description     Total net order value     
    Status     Status     Released      
    Data Type     Data type     Currency format     Selected by system
    Number of characters     Number of characters     15     
    Decimal places     Decimal places     2     
    Currency     Currency     INR     
    Interval vals allowed     Interval values allowed     Check this tick box     
    Multiple Values     Multiple values allowed     Select this radio button      
    4.     Choose Enter to complete the entries
    5.     Choose Save icon or Ctrl + S to save the characteristic.
    3.4.24.2     Creation of Class
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Class
    Transaction Code     CL02
    2.     On the Class screen, make the following entries:
    Field name     Description     User action and values     Note
    Class     Class     PORELPROC     
    Class Type     Class Type     032     
    Choose Create icon or white paper icon to create new class.
    Description     Description     Purchase Order Release Procedure     
    Status     Status     Released     
    Choose Char. Tab to input characteristic name.
    Characteristic     Characteristic     POVAL     Created in above step
    3.     Choose Enter to complete the entries
    4.     Choose Save icon or Ctrl + S to save the characteristic.
    Result
    Class type 032: Class PORELPROC created.
    3.4.24.3     Configuration of Release Procedure
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Define Release Procedure for Purchase Orders
    Transaction Code     SPRO
    2.     On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
    3.     Choose New Entries icon and make the following entries:
    Field name     Description     User action and values     Note
    Rel. Group     Release Group     02     
    Class     Class Name      PORELPROC     Created in above step
    Description     Description     PO Release Procedure     
    4.     Choose Enter to complete the entries
    5.     Choose Save icon or Ctrl + S to save the entries.
    6.     Choose yellow arrow to go back to popup screen.
    7.     Choose Release Codes to select.
    8.     Choose New Entries icon and make the following entries:
    Field name     Description     User action and values     Note
    Grp     Release group     02     Created in above step
    Code     Release Code     01     
    Workflow     Workflow     Leave it blank     
    Description     Description     Purchase Officer     
    Grp     Release group     02     Created in above step
    Code     Release Code     02     
    Workflow     Workflow     Leave it blank     
    Description     Description     Materials Manager     
    9.     Choose Enter to complete the entries
    10.     Choose Save icon or Ctrl + S to save the entries.
    11.     Choose yellow arrow to go back to popup screen.
    12.     Choose Release indicator to select.
    13.     Choose New Entries icon and make the following entries:
    Field name     Description     User action and values     Note
    Release ind.     Release Indicator     1     
    Released     Released     Leave it blank     
    Chgable     Changeability     4     
    Value change %     Change of value     10%     
    Description     Description     Purchase Order Blocked     
    Go to 2nd line and input the following values:
    Release ind.     Release Indicator     2     
    Released     Released     Select Check box     
    Changeable     Changeability     6     
    Description     Description     Purchase Order Released     
    14.     Choose Enter to complete the entries
    15.     Choose Save icon or Ctrl + S to save the entries.
    16.     Choose yellow arrow to go back to popup screen.
    17.     Choose Release Strategies to select.
    18.     Choose New Entries icon and make the following entries:
    19.     System will give new screen New Entries: Details of Added Entries
    Field name     Description     User action and values     Note
    Release Group     Release group     02     
    Rel. Stategy     Release Strategy     S1     
              Capital Items Release     
    Release Code     Release Code 1     01     
    Release Code     Release Code 2     02     
    20.     Choose Enter to complete the entries.
    21.     Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
    22.     Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default.  Choose Continue.
    23.     Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
    24.     Choose Next Screen icon or choose F8 to continue.
    25.     If you want to simulate the release procedure you can choose Release Simulation icon.
    26.     Choose Enter to complete the entries.
    27.     To save the settings choose Save icon or Ctrl + S.
    Result
    Release procedure is saved.
    3.4.24.4     Assignment of Values to Release Procedure 
    As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step.  If you do not want release procedure you may change the value to Zero.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Cross-Application Components  Classification System  Assignments  Assign Object to Classes
    Transaction Code     CL20N
    2.     On the Class screen, make the following entries:
    Field name     Description          User action and values     Note
    Class Type     Class Type          032     
    Choose Enter to Assign values.
    Release group     Release Group          02     
    Rel. Strategy     Release strategy          S1     
    Choose Enter.
    System will give Class name in Assignments, Double choose Class Name.
    System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR  against filed Value.
    3.     Choose Enter to complete the entries
    4.     Choose Save icon or Ctrl + S to save the characteristic.
    Regards
    S

  • User Exit for me54n on purchase Requisition Release i.e EXIT_SAPLMEREQ_05

    HI   All Experts ,
                          I have one Requirement that  , i want to insert  data in Ztable  using all details from header data in me54n  on purchase release i.e When i will Click on Purchase release Requisition i want to insert records using few fields such as , matnr ,menge , item, quantity ,requisioner,plant storage locaton , date etc  . i am using user exit on this i.e smod EXIT_SAPLMEREQ_005 in mereq001  which is called when clicked on purchase requisition release , now how to collect that details  in this user exit .
    need some help regarding this .
    Thanks And Regards
    Deepak Dhamat

    Dear Peter ,
                   yes you are correct that ebeln is part of structure MEREQ_ITEM but  it is always empty .i want Purchase Requisition no i.e     PR. Manual           2000009940  which is present in me54n first line of screen  i.e above the header note .
    after looking at the property  of that field it show as given
      below
      Struct.          MEREQ_TOPLINE               
      Field name       BANFN_EXT                   
      Data element     BANFN                       
      DE supplement    0                           
      Parameter ID     BAN                                                                               
    Screen field     MEREQ_TOPLINE-BANFN_EXT     
      Program name     SAPLMEGUI                   
      Screen no.       0014

  • Release Purchase Requisition - "Release strategy"

    Hi there,
    I am trying to release a purchase requisition. I looked in the table "EBAN" and i can see the entry or in other words, the requisition i created. In the Release indicator, Release status and Release strategy fields, these are empty. How do i add information to these fields which appear to have missing data?
    Speedy repsponse would be very much appreciated.
    Thanks
    Motolani Fatuga

    Hi Motolani
    spro>Materials Management>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Release strategy
    Select release strategy> Go to details>classification
    here check what are the charactaristic and what are the values maintained for it
    Check this for all release strategy
    Mostly PR release strategy is based on Document type and PR Value
    Check whether UR PR fits in release strategy criteria
    Suppose Total value of requisition is maintained as 1000-2000
    If UR PR value is less than 1000 Then PR will not subject to release
    Vishal...

  • Customised Field in Purchase Requisition

    Our requirement is to have a 4 digit departmental section (0001 - Finance dept, 0002 - HR dept, etc) in the Purchase Requisition line item (Table EBAN), there is no such field in standard SAP.
    How to add this addiitonal customised field to Purchase Requisition document (table eban) so that we can enter the data in create/change PR transaction  - ME51N or ME52N??

    hi,
    check these USER EXITS:
    MEQUERY1 - Enhancement for document overview ME21N / ME51N
    MM06E005 - Customer fields in purchasing documents
    MEREQ001 - Customer's own data in purchase requisitions
    Hope it helps..
    Regards
    Priyanka.P

  • User exit MM06E005 - Customer fields in purchasing document

    Hi,
    I am using user exit MM06E005 - Customer fields in purchasing document to validate the line items in PO and display the value at header level.
    My requirement is when the user enters the line items and press enter the validated value should get populated at header level.I had included a tab (customer tab) in that the value should get displayed.
    likewise for each and every line items the value should keep on changing.
    And
    I the field that i had added at header shows the value during the save but once we come out and enter again,it is not displaying the same.
    Regards
    Manoj

    Hi,
    Indeed the exit which you have specified MM06E005 comprises the enhancement for customizing fields and screens associated with it. may be you might not have activated the screen associated with the exit. the screen might have been created but missed while activating.
    Regards,
    Jagath

  • MM06E005 - Customer fields in purchasing document

    Hi,
    I am using user exit MM06E005 - Customer fields in purchasing document to validate the line items in PO and display the value at header level.
    My requirement is when the user enters the line items and press enter the validated value should get populated at header level.I had included a  tab (customer tab) in that the value should get displayed.
    likewise for each and every line items the value should keep on changing.
    And
    I the field that i had added at header shows the value during the save but once we come out and enter again,it is not displaying the same.
    Regards
    Manoj

    got my solution...

  • Purchase Requisition Release Procedure Modification

    Hi
    In Purchase Requisition Release, we have two deviations in business requirement from standard SAP behaviour:
    1. In multistep release, system allows PR release to be revoked by a lower level release authorized person even though higher level release has been done. Example, PR Release has release codes A1, A2 and A3, A2 can revoke release even after A3 has released the same. How do I prevent this from happening?
    2. If business requirement is to have release procedure based on item cost per unit and not on total value of the line item, how can this be achieved?
    Appreciate any guidance on these issues
    Thanks
    Sriram

    Hi,
    There is BADI ME_REQ_POSTED 
    in method POSTED  you can write your code to trigger the workflow and get the information related to release strategy and
    Purchase requisation  .
    for more than one PR use below logic .
    LOOP at im_eban into gwa_im_eban .
        concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
      add data into container -----------------
          gwa_event_container-element = 'PurchaseRequisition'.
        gwa_event_container-value = gwa_im_eban-banfn.
        append gwa_event_container to gi_event_container.
        clear: gwa_event_container.
        gwa_event_container-element = 'ItemOfRequisition'.
        gwa_event_container-value = gwa_im_eban-bnfpo.
        append gwa_event_container to gi_event_container.
    get the other details and create event to start workflow .
    select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                                  and bnfpo = gwa_im_eban-bnfpo .
            if sy-subrc <> 0 .
          call function 'SWE_EVENT_CREATE'
            exporting
              objtype           = 'BUS2009'
              objkey            = gwa_objkey
              event             = 'zcreated'
            tables
              event_container   = gi_event_container
            exceptions
              objtype_not_found = 1
              others            = 2.
    ENDLOOP .
    Hope this will resolve your issue.
    Thanks and Regards,
    Deepanker Dwivedi

  • Customer Field in purchase order (ECC 6.0)

    Hi,
    I need a help on custumer field in ECC 6.0.
    I would like to know if there is a standard way to see customer fields in purchase or sales order.
    Thanks very much.
    Diego

    Customer fields (as in KUNNR)  or custom fields?
    Bothe sales orders and POs have user-exit screens that can be employed to show <b>custom </b>fields both at header and item levels.  In the case of sales orders, it is oft-referred to as "Additional Data B" screen.  This is the last tab screen of the sales order.
    Caveat: The above is from 46C, but am willing to bet that this feature still exists in the ECCs.

  • WS2000077 (Purchase Requisition Release) problem

    Dear all
    workflow task WS2000077 (Purchase Requisition Release) causes the following problem:
    While executing an approval release (ME54N) through workflow, the result is always 'requisition release refused'.
    Does anyone know why?
    I appreciate your help in advance

    Hi,
      Go through the below links it may help you...
    Workflow Definition WS20000077 and sequence of the events, significantly...
    po release workflow issue/problem
    PR Workflow problem
    std workflow ; user to role agent assignment ?
    Regards,
    Udaya.

Maybe you are looking for