PR Status = 04 : FOR OVERALL RELEASE

Hi Friends ,
We have PR status in PR ITEM DETAILS (Me53n) - STATUS Tab , which can have following status
1)Version in Process
2) Active
3) In release
4) release completed
5) For Overall Release
6) Release refused
I wanted to know the meaning of "FOR OVERALL RELEASE" here and when this status gets updated in PR.
Like to share, we have OVERALL release Strategy ( NOT Item LEVEL) implemented for PRs
Regards
Shrey

Thx for reply ...
But here in my case , the status "FOR OVERALL RELEASE" is only being appeared for few PRs, for all other PRs either the status is "IN Release" or "Release Completed".
Although all PRs are subjected to OVERALL Release.
I couldn't identify the reason why only few PRs have "FOR OVERALL RELEASE".Also like to share all such PRs has already been approved by approvers but instead of "Release complete" , system is showing me status "FOR OVERALL Release"
Appreciate if you could let me know the reason for the same.\
regards
Shrey

Similar Messages

  • Why can we only use 1 release class for overall Release of Purchase Req?

    Hi,
    After realizing that it would be beneficial to use more than one release class for overall release of Purchase Requisition with classification, in use with release groups for overall release, I now ask if someone knows why SAP has chosen to only allow 1 release class for overall release of Purchase Requisition?
    In my scenario I would like Release group US, used for release strategies for US-plant to be able to use 1 release class with a specific set of characteristics.
    For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_USD including a characteristic PR_TOTVAL_USD looking at CEBAN-GFWRT. The chosen currency for this characteristic would be USD.
    I would then like to allow Release group FR, used for release strategies for FRANCE-plant to use another release class with another set of characteristics.
    For example class REL_PREQ_CLASS_OVERALL_VALUE_IN_EUR including a characteristic PR_TOTVAL_EUR looking at CEBAN-GFWRT. The chosen currency for this characteristic would be EUR.
    In this way the release strategies for the respective release groups US and FR, could maintain their overall limit values in their respective release strategies in their own currencies.
    1. Observe that I do not want to use the same Release class for both release groups for overall release, even though I know that this is currently the only allowed option, as far as I've understood.
    2. Observe that I do not want to specify the two characteristics PR_TOTVAL_USD and PR_TOTVAL_EUR for overall value in the same release class, as this would lead to double maintenance for a large number of release strategies. Also consider the maintenance when new countries with new currencies want release strategies.
    3. Observe that I only want to use overall release.
    What I'm trying to avoid is having to continuously translate local business USD overall value limits to limits in the currency chosen for the overall value characteristic. If this for example is specified in DKK, this would lead to a need to adjust the overall value limits as soon as the exchange rate between USD and DKK changes in the system.
    Please consider this simple example:
    Local requirement is that USD purchase requisitions should be blocked when the USD value is above 1000 USD. However in my release strategy I would have to maintain a value of >5365 DDK, if DKK is chosen as the currency for overall characteristic.(e.g exchange rate 5,365).
    Next month the currency exchange rate in the system between USD and DKK has changed, and therefore I would have to go into CL24N and maintain the value to reflect the new exchange rate between USD and DKK. Lets say it has gone up to 5,435. I would now have to maintain a value of > 5435 DKK in my release strategy to correctly reflect the local business requirement of 1000 USD.
    So if anyone could please explain why SAP has taken the decision to make the Release class for overall release client specific that would be much appreciated and awarded accordingly. Also if you have any suggestion on how I could obtain the above scenario on maintaning overall value limits in different currencies than that would be awarded to.
    BR Jakob F. Skott

    You can give feed back to Apple from the iTunes drop-down menu in the iTunes menu bar..
    You can also contact the iTS Customer Service from the links on this page - http://www.apple.com/support/itunes/store/
    MJ

  • Can't use Overall Release for Purchase Requisitions

    I have two groups, AA and ZZ.  Each group has it's own Class.
    Group AA uses Cost Center Class (CN)  (uses Characteristics Cost Center and Line Amount)
    Group ZZ uses Order Class (OC) (uses Characteristic Order)
    I have built one and only one Release Strategy for each of these Groups.  These Strategies both work successfully when I select the other group to be the group for Overall Release.  That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully.  However, if I modify the req the strategy for ZZ, does not get applied.
    The opposite is true.  When AA is set to be for Overall release, then ZZ works.  However, if I modify the req, then AA's release strategy does not get applied.
    Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release.  However, neither strategy works if its group is set to be the one for Overall Release.
    What am I missing?  I only have two classes, two groups, and two release strategies.

    SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
    Release procedure is of two types
    Release Procedure without classification
                 This procedure is applicable only for Purchase Requisitions.
                 Here PR is released Item by Item only.
    Release Procedure with classification
                This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract  and scheduling agreements.
                Item by Item and Header level releases can be configured
                For PR - both item by item and Header level release can be configured
                For external purchasing documents - Release is possible only at Header level.
    Step 1:
    Create Characteristics
    In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
                1) Total value of PR more than Rs 50,000
                   create  characteristic as "Release_PR_total_value" in transaction code CT04.
                  Tab -  Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency  eg. INR or USD"
                  Tab -values key in > 50000 INR
                  Tab -  Additional Data-  Table Name "CEBAN" and Field Name "GSWRT"
                  Tab - Restrictions - class type - 032 - Release strategy
                2) Plant
                     Create characteristic "Release_PR_plant" in transaction code CT04.
                     Tab - Basic data - Data type - CHAR; Number of chars - 4
                     Tab - Values - Key in all the plants for which you are required to configure release proc.  eg. 1000,2000,3000
                     Tab - Additional data - Table name CEBAN and Field Name is WERKS.
                3) Purchaisng Group
                     Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                    Tab - Basic data - Data Type - char, Number of chars eg. 3
                    Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                    Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
    Step 2:
    Define class in transaction code CL02
    Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
    Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
    Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
    Tab - Basic data - Enter description as "PR_Release-Proc",
    status- Released, Same classification - check the push button - Warning Message
    Tab- CHAR Enter above created 3 characteristics
    1.Release_PR_total_value
    2.Release_PR_plant
    3.Release_PR_PurchasingGroup
    step3:   
    Menu path is
    SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
    here define
    1.Release Groups
    Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
    Here assign class "PR_Release_proc" against release code "01"
    check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
    2.Release codes
    Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
    PRs are released by users in transaction code ME54N.
    Eg
    Type of user            - Level -             Release code                    
    PR creator - clerk or Business user -  
    Approver    -  Supervisor                 -   R1
    Approver  -   Project Lead              -   R2
    Approver   -  Asst. Manager             -  R3
    Approver   -  HOD/General Manager  - R4
    Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
    For detailed info please refer
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    3. Release Indicator:
    Release indicators show the release status of a Purchase Requisition.
    For detailed info please refer SAP Help official site
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    4.Release Pre requisites:
    These define the order in which individuals or departments release the PR in sequence.
    3.Release strategies
    Create a new release startegy  eg ."A1" or "U1" , write its description PR release for value >1 lakh
    Now select release codes according to the Chart of Authority set by your client.
    Eg.
    Release startegy " A1 - PR release for value >1 lakh"
    R1 - Supervisor   
    R2- Project Lead    
    R3- Asst. Manager 
    R4- General Manager
    Now click on" Release  Prerequisites "push button and check all the boxes in ascending order.Save the document
    click on "Release statuses" push button, check release statuses then click on "Continue" push button.
    In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
    Classification data for example
    1. Value - > 100000
    2. Plant - 1000,2000,3000 etc
    3. Purchasing groups - 101,102,103 etc
    By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
    In this way you can configure all the required Release startegies.
    Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
    Tcode - ME54N - For Individual Release
    Tcode - ME55 - For Collective Release
    For detailed info please visit SAP HELP website
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Regards,
    Indranil

  • PR overall release

    Hi,
    I created two characterstics: one is documenty type and another one is Total value i.e. GFWRT.
    I created one class. Assgned these characterstics to the class. Created one release group and marked it for
    overall release and assigned the class to it. Created release codes, assigned them to group, set release prerequisites,
    set release statuses, assigned value limit to characterstics in classification tab page
    Now when i create the purchase requisition, the release strategy is not getting applied. I would appriciate, if somebody tells me the possible reasons behind this.
    Regards,
    Pradeep

    Hello Pradeep,
    Please let me know in which client the release start. is configured? If you are transporting the release strategy to Production client  then you need to create characteristics and assign charac. values in Production client. Then first assign the charac. values to the starategy in CL20N in production server as the assignment don't get transported along with request.then only the rel. strategy would work.
    I hope this clarifies you query.
    With regards.
    Sanjay

  • Release Group for PR Release Strategy

    Hi ,
    When i am trying to define new "Release Group" AA , with Class "Z_PR" (it has Plant and Item Value as charcteristics ) , I am receiving message "Please Check Release Classes" , Message no. ME492.It doesn't allow me to save this new release group.
    Please also note that other two release Groups are already available.
    Do u know what I am missing  and how can I save my Release group ?
    ALSO as per the LONG text of this prompted message
    "Diagnosis
    Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used."
    What does it mean ?
    Sandeep

    Hi,
    The message has explained the problem.
    You cannot have two classes for the same document release and you are tryng to break this rule by adding another entry (the fact that you have give it a different release group does not make any difference this is still another class for the same document.)
    You should be able to do what you want without the need for a new release group or additional class, after all everyone else that uses SAP is using one class per document.
    Why diod you think that you needed another release group / class?
    Steve B

  • PR overall release strategy

    Hi
    Greetings!
    Overall all release strategy had already been set up in our system and it is working fine. But When i try to create a new strategy, it is not working.
    We have a class for over all PR release with the following characteristics.
    1) Purchasing Document type
    2) Plant
    3) PR total value
    4) Cost center
    5) Purchasing group
    I have made the following settings which are relevant for overall release
    1. Materials Management --> Purchasing > Purchase Requisition> Release Procedure --> Procedure with Classification --> Set Up Procedure with Classification --> Release Groups --> "Overall release of purchase requisitions" is checked for the release group created.
    2.  Materials Management --> Purchasing > Purchase Requisition>  Define Document Types --> "Overall release of purchase requisitions" is checked for the PR document type.
    Is ther any other settings which i am missing? Please help me in resolving the issue.
    Gobinathan G

    Hi Gobinathan G,
    I am aware that you already did the following procedure:
    1. Materials Management --> Purchasing > Purchase Requisition> Release Procedure --> Procedure with Classification --> Set Up Procedure with Classification --> Release Groups --> "Overall release of purchase requisitions" is checked for the release group created.
    2. Materials Management --> Purchasing > Purchase Requisition> Define Document Types --> "Overall release of purchase requisitions" is checked for the PR document type.
    However, since you are moving towards Overall release, what you must complete in order to achieve
    the desired result, is to create a new Characteristic,  and use it within the class parameter that
    you already created to control the values in your release strategy. Then you have to associate the
    new characteristic to the field name GFWRT in table CEBAN. It may be done in the Additional Data
    Tabulator of the characteristic.
    It worked for me.
    Hope it helps.
    Alfonso Chakarji

  • PR Overall Release Startegy not working if Purchase Org Included

    Hi All,
    We are trying to configure a PR Release Strategy for Overall Release. IF purchase Org is included as one of the characteristics the strategy does not get applied to the PR. On removing PORG it works fine.
    Any suggestions / pointers how to use porg as one of the characteristics for Overall PR Release strategy.
    Thanks.
    Regards,
    Anuj

    Hi,
    Are you using alpha or numeric Purchasing orgs?
    Could it be that you have entered the values in lower case?
    Steve B

  • PR overall release strategy with acc. assignment category characteristics

    Hi,
    Here is my issue : i created an Overall release strategy but the characteristic is on item level. In some precise cases, no release is generated.
    see below more details :
    I have created the following PR release strategy with classification.
    PR type concerned " NB": overall release
    Rlease group concerned : overall release
    In this release group i have 1 class
    in this class i have 2 characteristics : PR type and Account assignement category.
    Release strategy 1 :
    PR type = NB
    Acc. assignment cat = P, W
    Release strategy 2:
    PR type = NB
    Acc. assignment cat = K, V
    TEST 1 : PR type NB, 1 item with P category
    OK the release strategy 1 is generated
    TEST 2 : PR type NB, 1 item with W category
    OK the release strategy 1 is generated
    TEST 3 : PR type NB, 2 items with P category
    OK the release strategy 1 is generated
    TEST 4 : PR type NB, 2 items with P and W category
    TEST KO, no release strategy is generated
    => what should i do to solve this issue ?
    Thank you in advance for your quick answers,
    Isabelle

    What is the specific requirement for Overall release strategy?
    Besides, once you go for Overall release strategy, you cannot have another release strategy at item level.
    Every line item generates a PO, so logically should be set to a release strategy.
    Bottomline is use release strategy at line item level Unless a specific reason exists.
    Regards,
    Sameer

  • PR overall release data inconsistencies

    Hi Guru,
    can anyone advise if anyone experience data inconsistencies issues in EBAN table if PR overall release is implemented? would appreciate if you could share the SAP OSS note if you have. Thanks in advance

    Hi,
    i recall seeing on the web that there might be data inconsistencies in EBAN if we activate header release. But i could not find the link subsequently. However, when i do testing for overall release, it seems ok so far. Thanks for replying anyway

  • PR Overall Release Workflow - Agents Determination Failed

    Dear All WF Experts,
    I have used the standard workflow WS20000077 for PR Overall Release. I have assigned the agents to the task TS20000159 by position maintained in the Workflow Organizational Management Structure. The agents' names are showing correctly in the task's agent settings.
    However,  when I execute the workflow, the error 'Agent Determination Failed' for that step (TS20000159). I have checked the agent settings in workflow and SPRO, they look fine. Could anyone please kindly give me advices how to solve this error? Thank you so much.

    Hi, to all the experts who have helped me all these while,
    Thank you very much for spending time helping me to go through this issue.
    Yesterday, I ran through the coding for the function module for the rule AC20000026 again. I found out that there is one part of the coding which is causing the failure of determining an agent. The code disregard the company code for overall release of Purchase Requisition while the business requirement involves company codes in every PR created. Thus, by changing that code, the problem is solved.
    The snippet of code of function module (ME_REL_GET_RESPONSIBLE):
       CASE t16fc-frgwf.
    * keine Ermittlung
          WHEN space.
            RAISE nobody_found.
    * Ermittlung ¨¹ber T16fW
          WHEN '1'.
            IF eban-gsfrg EQ space.
    *     Einzelpositionsfreigabe Banf
              SELECT SINGLE * FROM t16fw WHERE frggr = eban-frggr
                                           AND frgco = rm06b-frgab
                                           AND werks = eban-werks.
            ELSE.
    *     Gesamtfreigabe Banf
              SELECT SINGLE * FROM t16fw WHERE frggr = eban-frggr
                                           AND frgco = rm06b-frgab
                                           AND werks = space.
    There is always a value in werks in my business scenario...
    SELECT SINGLE * FROM t16fw WHERE frggr = eban-frggr
                                           AND frgco = rm06b-frgab
                                           AND werks = space.
    So, by changing it to
    AND werks = eban-werks
    it will work, however, I think it's better to just remove the If statement
    IF eban-gsfrg EQ space.
    , since it has no effect anymore.
    I hope this would give a hint to all the rest who might be facing the same problem as well.
    Thank you very much,
    YL

  • Problem in overall release

    Dear Expert
    we are facing one problem in release procedure of PR previously we are having line item wise release of the purchase requisition now we have change it to overall release , but in that if there is a line item which have deletion indicator then we are not able to release the PR by ME55 , where as we can do the same PR by ME54N , i.e if there is a deletion indicator system is not able to release  PR by ME55 . how can we sought the same problem
    Regards
    Edited by: usmfarhan on Nov 2, 2009 10:05 AM

    Dear Expert
    why collective release of PR not possible for overall release of PR if there is deletion indicator exist at item level
    Regards
    Edited by: usmfarhan on Nov 2, 2009 12:05 PM

  • ME28 Exit needed for PO Release

    Dear Experts,
    I am new to MM area and I would require to put some codings in MM28 TA.
    Basically before a PO is set as release we need to check some custom fields.
    Culd any one of you please help me solve the issue..?
    Regards,
    Joydip.

    user exir for t code me28 is ,
                                                                                    Exit Name           Description                                                                               
    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              
    M06B0003            Number range and document number                                         
    M06B0004            Number range and document number                                         
    M06B0005            Changes to comm. structure for overall release of requisn.               
    M06E0004            Changes to communication structure for release purch. doc.               
    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., preview)                
    MEFLD004            Determine earliest delivery date f. check w. GR (only PO)                
    MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.              
    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                                       
    MM06E011            Activate PReq Block                                                      
    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   
    AMPL0001            User subscreen for additional data on AMPL 
    regards
    manu

  • OVERALL RELEASE CHECKBOX

    WHAT FOR OVERALL RELEASE CHECKBOX IS THEIR IN PR RELEASE STRATEGY AT ITEM LEVEL i.e W/O CLASSIFICATION .
    IF ANYBODY KNOWS CORRECTLY THEN ONLY PLS QUOTE UR SOLUTION

    In an SAP R/3 client, all PRs with a particular PR Document Type can use just one of the above options. If we have more than one PR Document Type, we can set some of them use u201COverall PRu201D release procedure and others use u201CItem-wiseu201D release procedure, depends on our business process needs.
    We can set the option in the process u201CDefine Document Typeu201D of Purchase Requisition that can be accessed by u201COMEBu201D T-code or through menu paths of u201CSPROu201D T-code: Materials Management u2013 Purchasing u2013 Purchase Requisition u2013 Define Document Type, as per below image:
    If we want that a PR Document Type use u201COverall PRu201D release procedure, we must tick the u201COverall release of purchase requisitions (OverReqRel)u201D indicator. If we donu2019t tick that indicator, it means that PR Document Type will be released with u201CItem-wiseu201D procedure.
    u can select that tick and press F1 u will get proper help
    hope it clears
    regards
    kunal
    Edited by: kunal ingale on Jan 5, 2009 5:09 AM

  • Overall Release of PR

    Hi all,
    I have configured release procedure for PR. I have created 2 classes for PR. One for item-by-item release and another for overall release. I have assigned different release groups to both. I have also checked 'OvRelPReq' indicator for the release group for which overall release to trigger. When creating Purchase Reqn through ME51N 'release strategy' tab is coming in item level. But 'release strategy' tab is not coming in header level. So I am not able to release all the items in PR at a time.
    Can u pl suggest me how can I be able to release PR on overall basis also.
    Thx 
    Amitava

    Hi,
    Whatever I have learned uptill now is PR can be released at item level & PO can be at header level.(I may be wrong, if so plz correct me)
    In ME54, u can put ur PR no & execute.
    All the items will appear there under that PR.
    Select "Select All" symbol at header & click "Release+Save".
    Regards,
    Piyush

  • Exit / BADI for RFQ Release (ME45)

    Hi all,
             I need an exit or badi when an RFQ got released.
    Can anybody please help me to find the badi when an RFQ has been released.
    Thanks & Regards.
    Ranganadh.

    Hi,
    Exits for RFQ are following-
    AMPL0001            User subscreen for additional data on AMPL
    ME590001            Grouping of requsitions for PO split in ME59
    MEETA001            Define schedule line type (backlog, immed. req., preview)
    MEFLD004            Determine earliest delivery date f. check w. GR (only PO)
    MELAB001            Gen. forecast delivery schedules: Transfer schedule implem.
    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
    MM06E011            Activate PReq Block
    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
    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
    M06B0003            Number range and document number
    M06B0004            Number range and document number
    M06B0005            Changes to comm. structure for overall release of requisn.
    M06E0004            Changes to communication structure for release purch. doc.
    M06E0005            Role determination for release of purchasing documents
    Regards,
    Sujit

Maybe you are looking for