List of Monthly Overall Released PR

Hi,
I want to generate a list of over all released ( Authorized by Highest Authority )  PR for a particular Month. Is there a Standard Report Available ?
Please give your expert views.
Regards
Shyam Kogta
09871894536

Dear Shyam,
Standard report ME5A has the selection option as Release date, but this is not the actual release date.
This date is only statistical date by which PO should be initiated.
To have a report based on actual release date you have to develop the zreport.
Manoj

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

  • PR Overall Release Strategy Problem

    Hi Expert,
    I have set the following
    Characterisrtic Name:
    1) ZPR_Release_Plant, Char : CEBAN-WERKS (Char format : 4)
    2) ZPR_Release_DOC_Type , char : CEBAN-BSART (Char format : 4)
    3) ZPR_Release_Pur_Grp, Char: CEBAN_EKGRP (Char format : 3)
    4) ZPR_Release_Total_Value, Char: CEBAN-GFWRT   (Curr format : 15 and  EUR)
    I assign the above to Class : ZPR_Overall_Rel
    I created Release Grp R1 and assign the class and tick "Overall Release" checkbox. There is only one class, no others in the list
    I created two Release codes, F1 - Senior Finance Manager, C2, CEO
    I created two purchasing group, LLL and LYL
    I used the standard indicators for S - block  2 - RFQ/PO and I created two release strategies A1 and A2 for Rel grp R1.
    A1 - release Code: F1, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LLL
    A2 - release Code: C2, Classfication: Plant 0001, Doc Type : NB, Value : > 0.00 EUR, and Pur Grp : LYL
    The problem is when I tried to created the PR, it doesn't work at all. No trigger whether I click the "check" button at the toolbar of the PR (i.e., the release strategy tab not appearing at the header). I also tried saved and display the PR and see if the Release strategy appears at the header but still not triggering.
    Can you folks advise?
    Thanks
    Lo

    Forgot to check the box "Overall Release" forthe Nb doc Type. The problem is now solved.

  • If not listed under "Known Affected Releases", is it considered "Confirmed Not Vulnerable"?

    I have a hard time believing only this version of UCS is vulnerable... Since there is no distinction to identify versions  "Confirmed Not Vulnerable"; If the version is not listed under "Known Affected Releases", does it mean it is not vulnerable or could it also mean it wasn't tested/verified?
    While we are on the topic, how many versions back does cisco check?

    My daughter has had her Razr for about 9 months now.  About two weeks ago she picked up her phone in the morning on her way to school when she noticed two cracks, both starting at the camera lens. One goes completely to the bottom and the other goes sharply to the side. She has never dropped it and me and my husband went over it with a fine tooth comb. We looked under a magnifying glass and could no find any reason for the glass to crack. Not one ding, scratch or bang. Our daughter really takes good care of her stuff, but we still wanted to make sure before we sent it in for repairs. Well we did and we got a reply from Motorola with a picture of the cracks saying this was customer abuse and that it is not covered under warranty. Even though they did not find any physical damage to back it up. Well I e-mailed them back and told them I did a little research and found pages of people having the same problems. Well I did not hear from them until I received a notice from Fed Ex that they were sending the phone back. NOT FIXED!!! I went to look up why and guess what there is no case open any more for the phone. It has been wiped clean. I put in the RMA # it comes back not found, I put in the ID #, the SN# and all comes back not found. Yet a day earlier all the info was there. I know there is a lot more people like me and all of you, but they just don't want to be bothered so they pay to have it fix, just to have it do it again. Unless they have found the problem and only fixing it on a customer pay only set up. I am furious and will not be recommending this phone to anyone. And to think I was considering this phone for my next up grade! NOT!!!!

  • PR Overall release issue

    PR release  strategy issue comes when Line items in PR added by two different persons, PR Release strategy(overall release)  not getting triggered.
    Release strategy is working fine if i create PR with only one user id.
    Both id's maintained in classification.
    Is this sap standard behavior??
    Created PR 4201001933  line item 10. using  User ID  - 20061704
    Triggered correct release strategy TD QH.
    Added line item 20  using user Id  -  345045 --- (release startegy gone)
    classification Maintained  for TD QH

    We have a similar equirement since we have cost center as one of the characteristics in PR overall release strategy.
    In our case we agreed with Business that the CC in the first PR line item will decide the release strategy. (Or the first CC of thefirst line item in case of multiple account assignment.) We wrote a small piece of code to achieve this, to enter that CC in ceban-kostl.
    If your business requirement permits, you may follow this strategy, where user id of the first line item will derive release strategy.
    Regards.
    Satish Patankar.

  • Need Help on List of Months between Two Dates

    Hello everyone,
    I have a table which has startdate & enddate, and need a SELECT statement to list all months between these two dates for each given ID.
    I did some test, and could not figure out how to get the startdate & enddate from testing table (instead of hard code them) in the select statement.
    Could anybody please help on it (Oracle 11gR2),
    Thanks in advance!!!
    create table testing(
    id          number,
    start_date  date,
    end_date    date);
    insert into testing values(100, to_date('05-FEB-2011', 'DD-MON-YYYY'), to_date('28-MAY-2011', 'DD-MON-YYYY'));
    insert into testing values(200, to_date('20-JUN-2011', 'DD-MON-YYYY'), to_date('28-DEC-2011', 'DD-MON-YYYY'));
    commit;
    select * from testing;
            ID START_DAT END_DATE
           100 05-FEB-11 28-MAY-11
           200 20-JUN-11 28-DEC-11
    Elapsed: 00:00:00.01
    *for testing.id = 100:*
    select to_char(add_months(to_date('05-FEB-2011', 'DD-MON-YYYY'), l - 1), 'YYYY-Mon') Dates
    from (select level l
           from dual
        connect by level <= months_between(trunc(to_date('28-MAY-2011', 'DD-MON-YYYY'), 'MONTH'),
                                           trunc(to_date('05-FEB-2011', 'DD-MON-YYYY'), 'MONTH')) + 1);
    DATES
    2011-Feb
    2011-Mar
    2011-Apr
    2011-May
    Elapsed: 00:00:00.01
    *for testing.id = 200:*
    select to_char(add_months(to_date('20-JUN-2011', 'DD-MON-YYYY'), l - 1), 'YYYY-Mon') Dates
    from (select level l
           from dual
        connect by level <= months_between(trunc(to_date('28-DEC-2011', 'DD-MON-YYYY'), 'MONTH'),
                                           trunc(to_date('20-JUN-2011', 'DD-MON-YYYY'), 'MONTH')) + 1);
    DATES
    2011-Jun
    2011-Jul
    2011-Aug
    2011-Sep
    2011-Oct
    2011-Nov
    2011-Dec
    7 rows selected.

    SQL> select * from testing
      2  /
            ID START_DAT END_DATE
           100 05-FEB-11 28-MAY-11
           200 20-JUN-11 28-DEC-11
    SQL> select  id,
      2          to_char(add_months(start_date,column_value - 1),'YYYY-Mon') dates
      3    from  testing,
      4          table(
      5                cast(
      6                     multiset(
      7                              select  level
      8                                from  dual
      9                                connect by add_months(trunc(start_date,'MM'),level - 1) <= end_date
    10                             )
    11                     as sys.OdciNumberList
    12                    )
    13               )
    14    order by id,
    15             column_value
    16  /
            ID DATES
           100 2011-Feb
           100 2011-Mar
           100 2011-Apr
           100 2011-May
           200 2011-Jun
           200 2011-Jul
           200 2011-Aug
           200 2011-Sep
           200 2011-Oct
           200 2011-Nov
           200 2011-Dec
    11 rows selected.
    SQL> SY.

  • Purchase Requisition Overall Release problem with several CostCenter

    Hello Gurus!!
    I need your comments!!! 
    I define the Purchase requisition as Overall Release, and woks !!  but I have a Issue.
    I have an entry in the CL24N txn as follow:
    AccAssgCat = K
    Plant              = CC01
    CostCenters = 10001
                            10002
                            10003
    totalAmt        = 1USD to 1000US
    So when I create my purchase requisition with only 1 Cost Center the release strategy is called and PR can be released.
    But When I create the purchase requisition with CC 10001 and 10003, the requisition is not subjet to release!!! (note TotalAmt = 15usd)
    I assume that as both are into the release strategy the system will take both CC and ask for release!!
    What I can do to fix this situation??

    Dear Marco Antonio,
    I have never faced your issue, but have an idea of what you can do.
    Activate Enhancement M06B0005   EXIT_SAPLEBND_004
    Then in the program zxm06u31 put the following code line:
    e_ceban = i_ceban.
    and also  a breakpoint so that it stops automatically upon PR verification or saving.
    Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
    Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
    I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
    Well, tell me what happens
    Best Regards,
    Sebastián Ligueros

  • Overall release of PR in Release Strategy

    I have created item-wise release of PR using with Classification of Rel Str.
    But when I am creating overall release of PR I am not getting the tab.
    I made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR.
    Pl guide
    regards
    VS

    Hi VS
    Am confused. You wrote 'Have created item-wise release strategy' and also asking 'Overall release'.
    If you have "made settings in Rel Gp screen (ticked te check box for overall rel) & also ticked the check box in the document type of PR", then you have configured Overall release.
    If PR does not get release strategy tab at header, it could be due to incomplete release strategies. No release strategy might have been triggered for your PR data. Do you see release strategy tab at item level ?
    Best regards
    Ramki

  • 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

  • Purchase Requisition Overall release amount

    Hi,
      I am working on PR overall release amount workflow.
      How can i find the overall release amount in the tables of PR while entering into the workflow.
      Depending on this amount we need to further proceed for approval process.
    Regards,
    Gopinath Addepalli.

    Dear Marco Antonio,
    I have never faced your issue, but have an idea of what you can do.
    Activate Enhancement M06B0005   EXIT_SAPLEBND_004
    Then in the program zxm06u31 put the following code line:
    e_ceban = i_ceban.
    and also  a breakpoint so that it stops automatically upon PR verification or saving.
    Activate and then create a PR with the problem you are facing. On saving the program will stop in your breakpoint.
    Look at structure i_ceban there you will find the values that your release strategy is getting from the document and with which it will try to determine the strategy based on your classification.
    I the standar logic is not what you want maybe you can put some logic of your own based on account assignments in structure C_EBKN.
    Well, tell me what happens
    Best Regards,
    Sebastián Ligueros

  • Overall release strategy in purchase requisition

    hi,
    how do i configure overall release in case of  purchase requisition. i have done item wise release in PR. but in case of overall release what field I should take in characteristics?  is their required two seperate classes for item and overall release? i've allready chosen the field BSART and GSWRT for item wise release,
    plz help me in details
    regards
    Aniruddha

    Hi
    For PRs, there are two types of release procedures available
    With classification
    With this we can release the PRs both items wise and in their entirety
    Without classification
    With this we can release only at item level
    When you create the Release Group under the release procedure with classification
    you check the box " ov Rel P Req (Overall release of purchase requisitions
    This  Determines that the items in a purchase requisition are all released at
        the same time (rather than individually).
    This should help to relsove your problem.
    Regards
    Vikrant

  • 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

  • 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 shared PR document types)

    We are asked to configure 'overall' PR release for some of the plants of our client.Now ,we know,  this needs to be configured in two places in SPRO. One, in release group definition & two, document type (PR) definition. Our issue is that the doc types involved here is shared by some other plants as well who doesn't need 'overall' release. Is it possible to configure the requirement without disturbing the unwilling plants ?

    Hi ,
    The PR release strategy can be done at Item level also ,which has to be set that the PR has to be released at item level and after doing it ,all the item values can become characteristics values for the release strategy
    The Plant can be taken as one of the characteristic.
    The view CEBAN gives all the related views.
    check the below LInk for Futher information on the same.
    http://www.scribd.com/doc/531679/Release-Procedure-for-Purchase-Requisitions
    hope so it helps
    Regards
    Anjanna.

Maybe you are looking for