To trigger Overall release for PR workflow (WS20000077)

Hi,
I want to know that how can i trigger overall release for PR workflow ( WS20000077 ) of BUS 2105.
rightnow in my system workflow WS0000038 is activated & when i perform ME51N it is triggred perfectly. and in SWEL BUS2009 is triggered, but it wont trigger BUS2105.
So how can i trigger BUS2105 & instead of BUS2009, so it will trigger WS20000077 workflow.
Which seetings needs to be done in SPRO, so it will trigger BUS2105?
And please give me some idea about overall release for PR workflow & item level release for PR workflow.
Regards,
Smit

Hello,
Right now, the release strategy is configured item-wise for the PR and so the business object BUS2009 is triggered. To make the release of PR from Item-wise to overall, please make the following configurations in SPRO
SPRO -> MM -> Purchasing -> Purchase Requisition -> Define Document Types and check the 'OvrelReq' checkbox and then
SPRO -> MM -> Purchasing -> Purchase Requisition -> Release Procedure-> Procedure with classification->Set Up Procedure with Classification and maintain the Release Groups by checking the 'OvrelReq' checkbox.
Once these configurations are done, first check whether the event 'RELEASESTEPCREATED' is published in the system from the event log(SWEL). Once an entry is found,deactivate the linkage between template WS0000038 and activate the linkage of the template WS20000077 which is for the BO BUS2105.
Hope this will help.
Thanks,
Samson

Similar Messages

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

Overall Release for PR

The overall Release strategy of the PR is not coming up, I tcik on the doc type, tick on the release group and also the use CEbAN-GFWRT, buut it is till not working, what am I doing wrong. When I try the item release, it works perfectly. Can I have item release for stock items and oveall release for non-stock items.

Hi,
Could you please check the SAP note 365604 which gives very useful information. Please check all these information and if you still can not solve your issue, I would suggest to open a SAP ticket, so that an expert can have a look in your system.,
Best Regards,
Arminda Jack

Workflow WS00400012 Release for Payment not getting triggred

Hi,
As mentioned in the help docs we have done the following settings for Release for payment, yet the Workflow is not getting triggered.
SPRO->Financial Accounting (New)->Accounts Receivable and Accounts Payable->Business Transactions->Release for Payment
Create Workflow Variant for Release for Payment
XX01     WS004MSBT Payment release
     Workflow var.   XX01
     Currency        INR
     WF var.name     WS004MSBT Payment release
     Prelimenary posting release
      Release from    1.00
      Subworkflow     WS00400012
     Payment release
     Release payment          X
     Creater permitted          X
      Payt release    1.00
      Pmnt rel.var.   CC
Assign Company Code Workflow Variant for Release for Payment
     Compamy Code     Workflow Var     WF Var. Name
     XXXX     XX01     WS004 Payment release
Define Release Approval Groups for Release for Payment
     0001     Vendor A
     0002     vendor B
     0003     Vendor C
     0004     G/L accounts
Define Release Approval Paths for Release for Payment
     0001     Vendor high
     0002     Vendor middle
     0003     Vendor low
     0004     G/L accounts
     0005     Other
Assign Release Approval Paths for Release for Payment
     Workflow Variant      Doc. Type      Release Group     Approval Path
     XX01     KR     0001     0001
     XX01     KR     0002     0002
     XX01     KR     0003     0003
     XX01     KZ     0001     0001
     XX01     KZ     0002     0002
     XX01     KZ     0003     0003
     XX01     SA     0001     0001
     XX01     SA     0002     0002
     XX01     SA     0003     0003
Assign Release Approval Procedure for Release for Payment
     Wrkf      ApPath     Amt To            Curr     Rel levels     Swf Amt rel     Swf pnmt rel
     XX01     0001     5,000.00      INR     1     WS10000052     WS00400011
     XX01     0001     10,000.00     INR     2     WS10000053     WS00400021
Define Relevant Document Types for Release for Payment
     Workflow Variant     Type
     XX01                       KR
     XX01                       KZ
     XX01                     SA
Define Users with Authorization to Payment Release
     XX01     1     1     5,000.00     INR
     Assigned Authorization Object
     Production manager
     XX01     1     2     10,000.00     INR
     Assigned Authorization Object
     Comp Admin
Carry Out Function Enhancements for Release for Payment
Define Payment Block Reason for Payment Release
           Free for payment
     *     Skip account
     A     Locked for payment
     B     Blocked for payment
     I     CML:InvestorContract
     N     Postprocess inc.pmnt
     P     Payment request
     R     Invoice verification
     V     Payment clearing
We are using Tcode FV60 for Park Vendor invoice
We are trying to post the Document thru Tcode FBV0 , But the Post field is grey and system shows error: func not possible as document is in not released. The Workflow is not getting triggered. And hence its not possible to release the doc.
The workflows have been activcated
We have done Eventlinkage and activated it.

In future when you post question please do some formatting. It seems like a novel.
Have you checked in SWEL whether the event CREATED of Business Object BSEG getting triggered. I hope you have activated the linkage between event and workflow from PFTC or SWE2 transaction code.
Thanks
Arghadip

Purchase Requisition, overall release

Hi All,
I am using the overall release for my release groups. The releasing strategy depends on the cost center.
The releasing is workling fine so far, after I created a PR, the release tab appears in the header. BUT if I enter several items in one PR with different cost centers, the release tab does not appear. This also happens, if I enter 2 items with different cost centers in the PR and both of them are assigned to the same release strategy.
Are there any configuration in SAP to prevent this or do I have to use the itemwise release for that?
Thank you!

Use userexit
Enhancement : M06B0005
Component   : EXIT_SAPLEBND_004
CR : RDAK903063 SPOREDDY 04/05/07 changes to pick the release
              strategy if all the cost centers are same for all
                line items. Since the user Exit is activated the
                program is forcing the data to go through import and*
             field I_CEBAN-KOSTL is not blank the user exit is
                filling blank values to E_CEBAN during export.

Error in Workflow for PR Overall Release

Dear SAP Fans,
I am getting error in workflow (WS20000077) after release of Purchase Requisition with first person and getting message in OutBox with the following errors and is unable to go to next person's Inbox for release PR.
   Error when creating a work item
   Error when processing node '0000000004' (ParForEach index 000000)
   Error when creating a component of type 'Etapa'
   Error when starting work item 000000392108
   Agent determination for step '0000000004' failed
   Error in resolution of rule 'AC20000026' for step '0000000004'
   No configuration for workflow WS20000077 version 0001
   Work item 000000392108: Object FLOWITEM method EXECUTE cannot be executed
How can I correct the above errors. Please help me !!!.
Thanks in advance,

HI,
Just a thought,
Please check, If some one changed WF-USER password.
also check if the WF-USER is a Service user and not dialog user.
Regards,
-Venkat.

Additional PR release step while using standard workflow WS20000077

Our current PR release strategy is overall release and based on 3 characteristics: doc type, creation indicator and total value of PR. Release code is relevant to standard workflow WS20000077 with role resolution using user-exit. User exit is based on the position of PR creator to navigate HR org structure for assigning manager who has sufficient release authority as workflow approver.
There is a request for additional release step in case the PR contains item for a particular material group or fixed vendor, then the 1st release step should be taken by a dedicated position/user.
I found that it is quite confusing while PR release strategy is overall release but referring PR item level data. Please advise is it possible and how to implement the additional release step. Thanks.

Thanks for your quick response.
I also think about this to keep workflow side untouch by including one additional release code in MM release strategy configuration. Unfortunately material group is item-wise, material group of item 1 may not be the same as item 2 (unless we restrict all items' material group to be identical by user-exit). Otherwise, I'm not sure how to incorporate this into a document level overall release strategy.

PR overall release workflow

Hi All,
I am working on PR overall release workflow (WS20000077) and had activated workflow for PR rejection 'wf_pur_rejo' (WS65400029). When i create a PR using ME51N workitem gets created. When we reject the PR by executing the workitem i receive the workitem for rejection also. Everything is fine till here.
But when i try to execute the workitem (Purchase Requisition XXXXX Rejected) i get an <b>error 'No Administrator found for the task'</b> and i observed that in workitem log it is shown in READY STATE. This happens for some user ids and it works fine with some other user ids.
Can any please tell me where i am going wrong and if i am then eloborate on what should i be doing?
Thanks in advance,
Regards,
Lakshmi Narayana.S

I have got it, ran the Transaction SWU_OBUF to synchronize the buffers and re-logged into SAP. Now the problem is solved.
Regards,
Lakshmi Narayana.S

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

Workflow WS400012 Release for payment (frame)

Hi, I need to know if the WS400012 Release for payment (frame) is trigger when a invoice is register to
I need to know if workflow to shoot when a logistic invoice is registered from the MIRO transaction, since a book entry is registered (type RE),
I tested and single an the workflow to shoot with financial transactions (FB01, FB60), although I formed in the payment liberation the type of document RE.
Regards
Dayana

Hi,
Just go through the following links
1. http://help.sap.com/saphelp_nw04s/helpdata/en/fb/135d89457311d189440000e829fbbd/content.htm
2.http://aiokeh.wdf.sap.corp:1080/SAPIKS2/contentShow.sap_SCLASS=IWB_STRUCT&_SLOIO=9B4460FF454711D189430000E829FBBD&TMP_IWB_TASK=DISPLAY&RELEASE=647&LANGUAGE=EN&_SEQNUM=104&_LOIO=84CB8D3880B8E060E10000009B38F842&_CLASS=IWB_EXTHLP
<b>Reward Points if Useful</b>

PR Release Workflow WS20000077

Hi Workflow Gurus,
I am using SAP provided standard workflow (WS20000077)for PR Release. This workflow is triggered when event Release step generated is raised in the system.
I have PR with two release code L1 and L2. If i see the workflow it has only one level.
My question is that is it necessary to add another level insiade my workflow?
or
When level one (L1) releases,current workflow will be completed with L1 release and agin workflow will be triggered for the same PR with release code L2.
Please help.
Thanks in advance.
Regard
Sagar

Hi Sagar,
If it is value based, then u need to create characteristics for price value and include that characteristics in class and then use that class in release strategy. And u need to give the range of value in Classifications in Release Strategy. you can refer the following link for release strategy,
http://help.sap.com/saphelp_47x200/helpdata/en/04/92761846f311d189470000e829fbbd/frameset.htm
Regards,
JMB

Overall purchase requisition's Workflow : mechanism of release code

Hi all,
i need to implement Overall purchase requisition standard workflow ; i need to have 2 actors for process's validation, so i set release code like this :
01 - ACTOR1
02 - ACTOR2
The workflow is launched, the ACTOR1 received a work item in his workplace, whe he execute the work item, the transaction ME54N is launched. Well. But the ACTOR1 can a decision for him but also for ACTOR2, why ? the process is not good for me. If ACTOR1 has taken a decision the workflow of release code 01 is finished. An other workflow is launched for release code 02, when the ACTOR2 go to the transaction ME54N he can take a decision for his relase code but he can also cancel the previous decision of ACTOR1, it's not good for me, can you explain to me ?
Thanks for help.
Cheers.

Interesting solution using the user-exit.
I just finished modifying the delivered overall purch req approval WF. I needed to add a few fields for reporting so I created virtual attributes via delagation on BUS2105. I created approval and initiator agent attributes and email addresses. It works fine and I don't have maintain any further code other than what is in my business object which I can use again and again.
Many roads on the way to Rome

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

Release Strategy with Workflow for PR & PO

Hi Experts,
I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
So User should get the information about the releases for PR & PO.
But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
Points will be awarded .
thanks & rgds
Swamy

Hi Swamy,
The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
How to configure?
Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
Maintain the details u already have in hand:
For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO. After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
Hope this will give you an idea how the workflow works and how to configure it.
Rgds.

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

To trigger Overall release for PR workflow (WS20000077)

Similar Messages

Maybe you are looking for