Problem withn Release strategy having Multiple release codes

Hi
I am working on a Release Strategy which has 2 Release codes say 01 and 02.
The PR document can be released only when 01 and 02 both releases.
But suprisingly, the first code 01 is able to release the 02 code also.
How to remove this problem.
Kindly relpy ASAP !!
Cheers
MaruthiRam

Hi,
This can be controlled through authorisation.Ask your Basis team to assign the Release code and release group in authorisation object "M_EINK_FRG" .Here give only the release code applicable to the concerned user only and remove the other release code .
Also please check if you have mantained the release prerequisite in img.That is for release code 02 the release pre requisite must be 01.Check the required boxaccordingly.
Dhruba

Similar Messages

PR Old Release Strategy - triggering NEW Release strategy any change OLD PR

Dear Gurus,
We have implement item level PR release strategy,
characteristic used: 1. Document type, 2. PR item Value, 3. Material Group, 4. Change date & 5. Account Assignment Category.
BEfore the above implementation, there is a OLD PR release Strategy existing in the system at one level release.
Now the issue, the OLD release Strategy status is release completed, now the user goes and change the PURCHASING GROUP in old PR, new release gets triggered. How to Stop this, system should not trigger NEW STRATEGY,
Please advice
REgards
RS

HI,
If i use date created as a characteristic, then Old release strategy get reset and the no release strategy will be trigger henceforth, the status of the PR will be INACTIVE.
ANy charateristic we use, there will be only 2 options for old released PRs, 1) It will reset the strategy to new one or 2) the old strategy will be reset and make the PR status as INACTIVE.
Is this is standard behaviour? pleae advice
Regards
RS

Dynamic release strategy and static release strategy

Hi,
What is the difference between dynamic release strategy and static release strategy.
What the customization setting required to activate dymanic and static release strategy.
Thank you
REgards,
Yshu

Dear Yshu,
What do you mean by dynamic and static release strategy. In SAP, we don'y have this term.
Please kindly give more explanation so we can help you.
We only have with classification and without classification.
Normally, release strategy without classification is used in R/2, and out of support in
R/3. However the functionality still available in case you want to use it.
You can not use Release without classification and Release with classification.
If there is an entry present in Release Group table (T16FG-FRGOT), only release with
classification can be used.
If you are in R/3, then forget the release strategy without classification but just
use the release strategy with classification as it had more flexibility than the old
system design.
Thanks
Ian

Purchase order release strategy with multiple characteristics

Hi All,
We have Purchase order release strategy based on the following characteristics:
Total Net Order Value
Purchasing Organization
Release strategy Type
a few other custom fields
We would like to have PO's with release strategy based on a particular Material Group [say X]. I have created a new Characteristic with respect to CEKKO-MATKL and added this characteristic to the same class.
I have created a new release code [HR] [we need a different person to sign off] and a new release strategy [TR] for which I have assigned the release code HR. In this release strategy, I have set it to get activated for a particular Material Group that does seem to work, but the remaining PO's are not getting triggered for other material groups. For other release strategies, I have left the material group field blank, because they need to be triggered for any material groups except X.
Could you please let me know if I am missing something or is there an alternate approach to this ?
Thank you,
Satish

Hi,
Obviously system will not trigger release strategy in ur case since in the classification data for other strategies u have left it blank excepting X for one strategy.
Since u have added a new characteristic Material group and assigned it to class then system expects an input for Material group for triggering release tab.If this is left blank then system by default will not trigger release strategy tab.
Solution:
First add all existing material groups in values tab of mat group characteristic then maintain the required set of material groups except X in other strategies in classification data.
Hope this is clear to you.
Regards,
Uzair

Release strategy: User should release only with his highest release code

Hello,
Because of personel absences we want to configure the release strategy so that:
User A or user B releases in the normal case the first level of a PO (with release code 01).
User C (Manager) releases after release code 01 with release code 02.
User A is deputy of user C. In this case user B will release with code 01 and user A will release with code 02.
Because user A can use depending of the case release code 01 or 02 (C deputy) it must be avoided that user B sets release code 01 and 02 for the same purchase order.
Do you know about a solution for this issue
Br
Manuel

Dear W1N,
But the systems knows that A released with code 01 and when A tries to release with code 02 the system knows that the same person of release code 01 is trying with release code 02.
<b>The aim is to avoid the second release from the same person and not to automate the release strategy.</b>
In such a case A has to cancel the release for code 01 (ME28) and wait until B is reachable to do the release of code 01.
When C is absent A knows that his task is to release code 02.
Is this check really not possible?
Best regards
Manuel

PO Release Strategy for 3 company codes

Hi
I am working on PO release procedure for 3 company codes in a client.I have created a one charecteristics called Order Type & assigned to class -POVALUE_NEW .I am using the same charecteristics & class in 3 company codes. I have created a different Rel Group & release Codes & assign as shown below
Group                       Class
AA     2     POVALUE_NEW
AB     2     POVALUE_NEW
F1     2     POVALUE_NEW
F2     2     POVALUE_NEW
V1     2     POVALUE_NEW
V2     2     POVALUE_NEW
Group     Rel Code
AA     L1
AA     L2
AB     L1
AB     L2
F1     F1
F2     F2
V1     A1
V1     A2
V2     A1
V2     A2
Created a Rel strategy as below
Group       Strategy
AA     P1------Vendor PO
AB     P2-------STO PO
F1     F1------Vendor PO
F2     F2-------STO PO
V1     V1------Vendor PO
V2     V2-------STO PO
I have maintained all the Doc type in value coloum of the cherecteristics .For vendor PO combination of Group & strategy , I have selected the respective Doc types in clasification .*When I raise the PO I am not getting the Release Strategy Tab in PO header* & when I remove the value in clasification any strategy , I will get the Rel Strategy Tab but this will appear in all company code POs .I want to give different lease codes for each company codes I am unable to find a solution to this issue . I am looking for a valuable suggesion from you all .
Thanks
Venkat

Hi,
1.in addition to existing Characteristic, create one more characteristic for Co. Code. Table CEKKO Field: BUKRS
2. Assign this new char. to your PO Release Class
3. Define your Release Codes for each Co. Code.
4. Define Strategies with characteristic values Co. code and Doc. Type.with co. code relevantRelease codes.
Ex: Co. Code1   Rel Grp-1 G1; Codes: A1, A2, A3
      Co. Code2   Rel Grp-2 G2; Codes: B1, B2, B3
      Co. Code3   Rel Grp-3 G3; Codes: C1, C2, C3
Strategy-1:
              G1   S1     A1 A2 A3;   values: CCd-1, Doc. type1
Strategy-2:
              G1   S2     A1 A2    ;   values: CCd-1, Doc. type2
Strategy-3:
              G1   S3     B1 B2 B3;   values: CCd-2, Doc. type1/Doc Type2
Strategy-4:
              G1   S4     B1 B2 ;   values: CCd-2, Doc. type2/Doc Type3
Like this you can make as many strategies to meet your requirement.

Release strategy for multiple currencies

Hi Experts,
I am new to PO release strategy. Need your advices.
We only have one release class FRG_EKKO in our system. Currently, this release class has the following characteristics:
FRG_EKKO_BSART (for PO doc type)
FRG_EKKO_GFWRT (for currency USD)
1. Is it possible to create another characteristic FRG_EKKO_GFWRT_ID (for currency ID) and assign to the same release class?
2. At PO release strategy, either one of the currency value is leave blank?
Regards,
April

You can create n number of characteristics...but leaving a characteristic value blank willnot enable the release strategy to trigger in PR/PO
Regards,
Indranil

Having Multiple Material Codes with Different Profit Centers in one Plant

Hi,
Can someone explain me what impact it will have, if there are different Material Codes with multiple profit centers in a single plant? For example, say Material 1 has Profit Center as PC1 and Material 2 has Profit Center as PC2 and they are in a single plant. Will this have impact on Financial Transactions?
Thanks and Regards,
Sameer Joshi

Hi Sameer
No negative impact.. It is very much possible and logical
All the purchases made - > Stocks and vendor liability will be tagged to the PC of the Material
All the sales made -> COGS, Revenue and Customer Liability will be tagged to the PC of the material, unless you overwrite using a Substitution
Br, Ajay M

Problem in uploading data for multiple company code in FB60

Hi Experts,
I am uploading data to tcode FB60 using bdc. If I have say 2 records in my file with same company code,
It;s successfully posting the invoices.
But if there are records with different company code, it's posting only the first one.
Please suggest me some solution.
Thanks.
Krishan

Hi,
This is a njoy tcode....U have to do some settings before using the tcode....
Go to tcode FB60 and give the company code ( if it is ur first login to the tcode then only it wil ask) .then u will get the screen to enter the document number and other stuffs....
In that screen go to EDIT OPTIONS BUTTON on application tool bar on the right hand upper corner...
U will get another screen in that check the check box which says NO COMPANY CODE PROPOSAL..and click on save .....
After use this tcode for the bdc program and no error will come.
Please let me know if u have any problems...
Regards,
Rohan.
Edited by: Rohan on Feb 2, 2009 12:29 PM

Incorrect Release code called which is not defined in a Release Strategy!

Dear Gurus,
I am facing a problem in Release strategy for a specific Purchase Requisition document type. My Release Strategy has two Release Codes for the Approval of a PR. When i create that document type of Purchase Requsition, Same Release Strategy is called, system picks the Two release codes from my Strategy but also pick another Release code which is not defined in my Release Strategy.
Kindly help me and let me know.
Thanks in Advance.
Johi Kapoor

Hi,
In Release Simulation (segment of Release Statergy), just click and you will have small pup up screen and there just double click the release codes all you have and you can see all unwanted release codes will be dissapeared and you have only now needed release codes what you configured for the release statergy. Now similuate release & set/reset release .
Regards,
Biju K

PR RELEASE STRATEGY PROBLEM

I am getting the following two error messages in the error log, while creating the PR Release strategy,
1.No release group exists
2.Characteristic CG_COE_RS_1 not linked to communication structure CEBAN
Please suggest

Hi,
Point wise answers as below:
1) SPRO>MM>Purchasing>PR>Release Procedure>Set up Procedure with classification>Release Group and release code
Create Release Group and also give release class, which you have created and assign this release group to your release codes.
2) SPRO>MM>Purchasing>PR>Release Procedure>Set up Procedure with classification>Edit Characteristics or (T.Code:CT04).
For the respective characteristic, in the additional tab you have to give Table name as "CEBAN" and field name as your corresponding field name
Regards.
Chinna

Class and release group and code in release strategy??

hi experts ,
Can some body explain me..
I have created Characteristics and Class for for release strategy.
But while creating release group , i should assign my class with release group , after doing this when i save , its giving error as check the release classes????
I m using the same class what i have created for my company..
So how to over come this issue
Thanks

Release Prerequisites
Definition
The release prerequisites indicate the sequence in which a purchase requisition or an external purchasing document must be approved via the release codes. The release prerequisites are defined in the Purchasing Customizing facility (in the release strategy).
The approval procedure for purchase requisitions in an enterprise may be set up in such a way that a department manager must approve a requisition item before the next level of authority (e.g. the cost center manager). In this case, approval by the department manager is a prerequisite for approval by the cost center manager.
Release Indicator
Definition
When a requisition or an external purchasing document has been processed via a release code, a release indicator is assigned to it.
When the system sets which release indicator is defined in the Customizing facility for Purchasing (in the release strategy via the release statuses).
What does the release indicator determine?
Requisitions...
External purchasing documents....
Whether the item may be changed by Purchasing or Materials Planning and Control after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether an RFQ or a PO may be created with reference to the item
Whether the document may be changed by Purchasing after the start of the release procedure
Whether a new strategy is determined and whether existing releases must be cancelled in the event of changes
Whether the purchasing document is released for transmission
Alternative Release
Definition
Within the release sequence, you can define alternatives. This means that several employees can effect release (signify approval) at a certain point in the sequence. If just one of these employees has effected release, the next release status is reached. The other employees thus need take no action.
Five release codes are defined for purchase requisitions in an ascending hierarchy. The requisition item can be converted into either an RFQ or a PO if release has been effected either with the release codes 01, 02, 03 and 04 or - alternatively - with release code 05.
The box with the information on the release strategy also offers you the possible alternatives for selection (see Displaying Release Information).
An alternative release cannot be a prerequisite for the next release code. In the above example, the releases with codes 01, 02, 03 and 04 could not be prerequisites for release with 05.
Release w. Classification (PReqs./Ext. Pur. Docs.)
Use
The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual control principle.
The person responsible processes the requisition or other purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
This release procedure can be used to approve requisitions and the external purchasing documents RFQ, PO, contract, scheduling agreement, and service entry sheet.
Purchase requisitions are released either at item level or in total. There is no provision for item-wise release (i.e. partial approval) in the case of the external purchasing documents. The latter can only be released in their entirety.
If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated.
Prerequisites
The release procedure with classification must have been set up in Customizing for Purchasing. In addition, a class with characteristics must have been created for each document (requisition, purchase order, etc.).
If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
How to do this is outlined in the Implementation Guide (IMG) for Purchasing in Define Release Procedure for the relevant documents and in Set Up Release Procedure with Classification for purchase requisitions. You will find detailed information on classification in the R/3 Library in the documentation CA Characteristics and CA The Classification System.
This procedure offers a wide range of possible combinations of release criteria. Should you nevertheless have other requirements, use the enhancement provided by SAP.
Operation of Release Procedure w. Classification
The characteristic values from a requisition or external purchasing document are passed on to the classification system.
The system checks whether the values correspond with release conditions. If so, it assigns a release strategy.
The persons responsible for the release codes process the document in the sequence defined in the release strategy.

P.O Release Strategy Problem

Hi,
I have a case in our production system, where we have a release strategy for P.O, which has got 3 release codes.. Say strategy is A and Release group is B.
When I create the P.O, The release strategy B A is being called, but inexplicably, I see 4 release levels, I go to SPRO and check the Release Strategy B A but in that strategy too, only 3 levels are maintained.
I went to release simulation, here I see 4 levels !! Where if the approval is given at the 3rd level, the 4th level is automatically shown as approved, and the P.O gets released.
I am curious to know, from where did this 4th level of approval come from, even though it is not defined in the config of the release strategy.
The release code description for the 4th level (the additional level) is Financial release, I was wondering whether this additional level has got something to do with some setting done in FIAR/AP-Business Transactions...
Can someone throw some light on this.
Many Thanks
Shailesh

Hi Nick,
I also thought the same, but to my utter surprise, I see only 3 levels in the release pre requisites, while when I click on simulation, I see 4 !!!
However in the P.O as well as in simulation, once the 3rd level approves, the 4th one which is the Finance release happens automatically .
I am trying to understand how did the 4th level come in from, Is it some other finance config setting?
Thanks
Shailesh

Release strategy and code authorizations

Hi,
We need to create a new release strategy for PO. After setting strategy, we are assigning existing release codes A1 and A2 to strategy. The same release code is also used in existing release strategy.
Now, will this create any authorization issue if we assign same release codes to different strategies, and different users in user roles.
Thanks
Alex

Hi,
I am confused with your requirement. When you have a business requirement to control the release, may be a new department created or new character value requires for adding to release process.
Option-1:--- >When you decided to create new release strategy, you should have gone for creating new release codes & design your release process with new release strategy with new release codes. Do not use same release codes, use different release codes for new release strategy which will be easy to control for authorization based on respective users.
Option-2:--- > When you added a new release characteristic to release class based on requirement, then check assignment of release group to release class ( just make change & TR need to be transported),release strategy design which trigger on how release is to be affected & which manner with a logic. Also check the new value you are entering with your release class, release group & release strategy in Cl20N/CL24N t.codes. Also check during creation of new release characteristic, you have values with correct field name.
Regards,
Biju K

Release Strategy @ Company Code Level

Hi Guys:
We have a two plants under one compant code, when we issue PO to the vendor it consists quantities that are required for both plants ( Central purchasing org).
Release strategy for PO is at header level , I.e Total PO Value can we release strategy @ company code Level?
with Characteristics as Company Code ,PO Document Type and PO Value?
Thanks
Sweth

Hi
For example if the release strategy set at c.code level all the documents created for several plants belonging to the c.code will affect the release strategy,so that is not the purpose of release strategy,
The main purpose of release strategy is certain documents created for particular plant or particular purchasing group or more than the value need to be blocked based on your business,so you cant able to set the release at c.code level because thre is no logic.
The characteristics for release strategy for external purchasing documents are
Plant                - WERKS
Pur.group        - EKGRP
Pur.org            -EKORG
Acc.assignment category-KNTTP
Document value-GNETW
Document type-BSART
The table is CEKKO
Thanks

Problem withn Release strategy having Multiple release codes

Similar Messages

Maybe you are looking for