PO Release characteristics

Dear All,
What all release characteristics can be used for PO.
Can Purchasing Organization be used as release characteristic.
Regards,
Vikas

Hi,
For PO release charecterstics always user Header options like Doc type, Purhcase organization, Purchase Group and Net order Value.
If you use Item level charecters like Mat grp, Plant etc., release strategy will not work properly in case more than one two mat grp or plant in same PO.
Regards,
Siva

Similar Messages

Vendor account group as PO Release characteristics

Dear All,
I want to use Vendor account Grp as PO Release strategy characteristics.
Whether can i use Vendor account grp as characteristics ? If so, what field to be used in CT04 to create?
Regards
Edited by: Venkateshwaran Balaji Kannan on Feb 29, 2012 9:24 AM

Hi,
Please take into account that in standard design system only considers
characteristics from CEKKO structure for release strategy consideration.
But it will not stop you in selecting the other characteristics.
Please go through the IMG help of release strategy, will give good
information.
I think you have already read the note:
       The characteristics of the class used must all be linked to the
       corresponding fields of structure CEBAN or CEKKO (for purchase
       orders)...."
Characteristics which are created for the release strategy with
classification MUST access communication structures CEBAN or CEKKO since
during the strategy determination, the system cannot access any other
tables or structures.
If the characteristics refer to fields which are not contained in
structures CEBAN or CEKKO, the corresponding fields can be added to
communication structure CEKKOZZ or CEBANZZ, or an append structure can
be created for CEKKO or CEBAN in which new fields can be included.
If you want to use new defined fields as part of the
release strategy clasification, you should use enhancement M06E0004
(User exit "exit_saplebnd_002").This user exit allows you to use the
user fields in strucure CEKKO to include additional data.
Use the user fields of this structure: USRC1, USRC2, USRN1 or USRN2 and
control them through user exit "EXIT_SAPLEBND_002. Otherwise new field
will not work.
BR
Nadia Orlandi

PO Release Strategy - Only for Non MRP generated materials

Hello,
I have a requirement in which any material which was generated via MRP (via PR) should not go through a release strategy at the PO level, but a non MRP generated PR should...
Is this possible at all? I know its possible at the PR level, but not sure at the PO... Would this be a case where we would need to added a field to the CEKKO structure thats for MRP generated PRs ?
Thanks

Hi,
By business any PO created, should follow release procedure as PO a committed document which will further send to vendor.
If you are sure about your requirement, PO created from MRP PR should not follow release strategy, then no need to go for any User Exit.
Just create separate document type for PR (ZMNB) , create separate document type MRP PO( ZMNB) and link MRP PO document type ( ZMNB) with MRP PR document type( ZMNB) in flowing path:
SPRO>MM>Purchasing>Purchase Order>Define Document Types
Now select your ZMNB B Purchase Order Document type and click link purchase requisition document type in Dialog Structure, enter ZMNB Purchase Requisition Document type with a new entry & save.
As you created release characteristics of document type (CEKKO with BSART), then do not keep Value u201CMRP PO document type (ZMNB) u201Cin the release characteristics of document type and design your release strategies.
Now create your PO with MRP PO document type (ZMNB) and see no release strategy triggered.
Regards,
Biju K

Purchase Order Release Strategy Approval

HI All,
I have an issue with the Purchase Order Release Strategy, I need to set the Release strategy at 2 levels.
Level one will have 1 approver
Level two must have two approvers.
The scene is:
Level one will approve all purchase orders betwee 400 to 5000 euros. 1 approver only
Level two will approve all purchase orders above 5000 euros. 2 approvers.
The problem is that the level two approvers must have the same Purchasing Group, Release strategy and Code, that is.
Pur. group G70, Release Group GC and release strategy DF.
I have completed the customising and the Release simulation is working correctly but when the PO is created the is no release strategy proposed.
CL20N is completed for both levels and works correctly for level one approval but not for level two
Can any please help
Leslie

Hi,
May be in your case the values are not properly designed in release strategy for PO Value (ZPO_GNETW) release characteristic.Now go for creation of following release characteristics
1. PO Order Type (ZPO_BSART),
2. Company Code (ZPO_ BUKRS),
3. Purchasing Organization (ZPO_EKORG),
4.Plant (ZPO_WERKS)
5. Purchasing Group (ZPO_ EKGRP) and
6. Total net PO Value (ZPO_GNETW)
Create one release class ZPO_CLASS & then add all above release characteristics
And then design your release strategies as required.
AND under release characteristic for PO Value (ZPO_GNETW) keep following values
A. <= 400 EUR
B. 400.01- 5000 EUR
C. >5000 EUR
As you already created Release Group GC & release strategy DF (1st level), now create another release strategy DS (2nd level).
NOTE: As you needed one releaser at 1st level and then two releasers in 2nd level. So create three release codes C1 for 1st level and C2 & C3 for 2nd level.
In designing release strategies for PO , you can keep value 400.01- 5000 EUR with release codes C1 under DF release strategy and Keep value >5000 EUR with release codes C2 & C3 under DS release strategy.
Regards,
Bijju K

RFQ release procedure deactivation

Hi Experts,
I have configured PO release strategy & its working fine.
But even its applicable to RFQ. My client dont want release strategy for RFQ.
How to deactivate RFQ release stategy.
Please suggest.
Thanks,
Jack

Hi,
Create NEW Release characteristics as purchasing document category CEKKO-BSTYP and during release strategy design you can keep VALUE as F for Purchase Order and save withy other vital release values.
This will not effect release procedure for RFQ or automatically deactivate release process fro RFQ and only Applicable for Purchase Order ONLY!
Regards,
Biju K

P.O can't be released message

Dear Experts ,
I have configured P.O release strategy long time back and it was working fine till yesterday after I configured release strategy for service entry the below message appeared while I am trying to release whether stock or service P.O :
(Purchasing document 3051000045 cannot be released
Message no. MEPO823)
Please help to solve this problem
Best Regards

Hi,
How PO release process links when SES release procedure . PO release & SES release process is different.In PO release,release characteristics created with structure CEKKO with respective field and in SES release , release characteristics created with structure CESSR with respective field.
Check you should have separate release class for PO & SES and should be assigned to individual release group.
Check any setting changed for PO release process during designing SES release process.( quickly check /compare with other client, you are having)
Regards,
Biju K

Service PR release strategy

Dear all,
We need to configure release strategy for Only Service PR which consist Account Assignment Category 'K' and Item Category 'D'.
How can we configure it?
We have release strategy in general.That means no service specific release triggered.Release effected for both Service and Material PR.
Thanks & Regards
Dipayan Bose

Hi,
As per your post, you require separate release strategy for Material PR and Serivce PR.
now as per my pervious post, you can assign two more charcaterstic to your calss used in release of PR.
Now for Service PR, you can put value as given above.
Now for material PR, these field should be blank not you need to assign blank values to these chaacterstics in CT04 and other valuse applicable.
First of all, you should go to Transaction CT04 and add this 'blank' value to your related 'account assignment category' release characteristics & Item Category. This addition is done by not entering any particular value into the 'Char. value' column but with related description (you can name it as 'Blank Account Assignment Category'). Then go back to CL20N Transaction where you can manually select it for your respective characteristic value of your release strategy.
Regards,
Pardeep Malik

Release strategy based on costcentre for PR

Hi Experts
I want to add Cost Centre as my release criteria in the existing release strategy . Presently I have Purchase grp and amount as my release criteria . Pls advise me how to proceed on this . Kindly also let me know how the user can be mapped to cost centres for approval as the user wants to have different approvers for different cost centres. We have searched for the authorisation obj for cost centre but could not get mor information .Pls help .
Thanks
Edited by: Devashish Lenka on Sep 6, 2010 2:10 PM

Hi,
Option-1:
You can create release characteristics with field KOSTL and add this characteristic with release class with other release characteristics. And you can design your release strategy based on requirement & then limit the cost center via authorization object K_REPO_CCA
Option-2:
Create Purchasing Group (OME4) as Department & assign the department to Cost center(KS02/KS01). Now create purchasing group as release characteristics with field EKGRP add this characteristic with release class with other release characteristics. And now you can design your release strategy based on requirement.
Regards,
Biju K

Error in Release strategy : Inconsistent Characteristic Value assignment

Hello Gurus ,
Good Day ...
Need your help in release strategy in purchase order .
Thanks in advance .......
Characteristics characteristics value
R2R_PURCH_ORD_TYPE NB
R2R_PURCH_GRP1 001
R2R_PURCH_ORD_VALUE 0,00 - 1000,00 USD
1001,00 - 2000,00 USD
2001,00 - 10000,00 USD
Class assigned char
Z_CLASS R2R_PURCH_ORD_TYPE
R2R_PURCH_GRP1
R2R_PURCH_ORD_VALUE
Rel grp assigned class
PH Z_CLASS
rel grp rel codes
PH 1 -director/VP
PH 2 - manager
PH 3 - buyer
rel grp rel strategy
PH A1
PH A2
PH A3
Now in SPRO -
> define Release Procedures for Purchase ORder -
> Release Strategies
PH A1 Release Strategy 1 (rel. prereq , rel statuses, classification , rel simulation ) working fine
PH A2 Release Strategy 2 (rel. prereq , rel statuses, classification , rel simulation )
ERROR MSG: INCONSISTENT CHARACTERISTIC VALUE ASSIGNMENT
DETAILS :
You want to change the value assigned to a characteristic. However, the change causes inconsistency, so the new value is not allowed.
The inconsistency may be for the following reasons:
A precondition or selection condition is violated.
The characteristic is a single-value characteristic, and different values have been set by constraints, actions, or procedures.
In classification, inconsistencies occur when you change the value set of a characteristic if objects or classes have already been classified with values from the previous value set.
Procedure
Choose Inconsistencies to see what triggered the inconsistency. You can also use the explanation facility for more information.
Delete the values that triggered the inconsistency.
You can only change or delete a value or value set that has already been used to classify objects if you delete the existing allocations.
PH A3 Release Strategy 3 -
> SAME AS ABOVE
regards,
ajay

Hi,
Inconsistency due to different "VALUE" in the Release Strategy & "VALUE" present in the Release Characteristics . Check details with value assignment with designed Strategies.
Also keep following VALUE Release Characteristics for value
<=1000,00.00 USD
1000,00.01 USD- 2000,00 .00USD
2000,00 .01- 10000,00.00 USD
instead of (0,00 - 1000,00 USD,1001,00 - 2000,00 USD,2001,00 - 10000,00 USD )
Regards,
Biju K

PR Release Strategy for MRP & Manually created PR

There is a scenario in which it's required when,
PR is generated automaticaly through MRP then Release strategt should be applicable and when
PR is created manually then release strategy won't be applicale.
Please suggest about this..........
Thanks in advance.

Hi,
You should have two document types ( as required by you here), MRP PR document type & Manual PR document type.Link plant, MRP group and the default order types as MRP PR document type in OMDT t.code.
You should create release characteristics (CT04) with the table & field and add all release characteristics in release class. For document type release characteristics with CEBAN & BSART and do not keep value ZNB which you do not want, just keep value ZMNB. During design of release strategy keep value only for document type ZMNB with other character values.
Regards,
Biju K

Release Strategy not triggered in PO

Release Strategy not triggered in PO and also in PR. Release Strategy stimulation is working fine but release tab is not coming in Po and also Pr.
What step I have to do after release strategy stimulation.
Regards
cns

Hi,
Unless you provides details, difficult to suggest an answer.
What are release criteria's you selected for PO and PR release strategy?
What are the release characteristics you have for PO and PR release procedure?
If you configure perfectly the PO and PR release strategy, did you transfers the "Vital Release Values" with your release strategy with release group and release class.
Refer few threads , may help full to you!
http://scn.sap.com/thread/1973324
http://scn.sap.com/thread/3212400
Also refer SCN wikiblog
https://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
Regards,
Biju K

Release Procedure with materia No. as characterstic.

hi SAPERS,
I am trying to put Release procedure for P.R. by keeping Material No, Plant, Purchase Group as characterstics.
When I assign the Plant, Purchase Group charactersic to Class the Release Procedure is working fine.
By instanct I assign the Material No. charactersic to same class the Release Proocedure is not working.
Please explain me where i did mitake? Can we add the Materia No as characterstic in Release Procedure, If no what are all the reasons.
Thanks in Advance.
Venkat.

Hi
It advisable not to add material number as a release characteristics for PO wheras for PR you can add it ..the job of the release characteristics is to to find the data in the purchasing document and apply the appropriate release stategy to it .this is done through communication structures .CEBAN is the communication structure for PR and CEKKO for PO.
note: if u add material no as a release characteristics u need to add each and every material number created into the class for your release strategy and release group through t code cl20n.
Regards
Sandeep

PO release by approving officer

Dear All,
Good Day!
How can i config release strategy with 2 approving officer using authority matrix
1. 1st approving officer release up to 500 thousand
2. 2nd approving officer will also released po if more than 500 thousand
Request to please explain step by step procedure of setup/config
Thanks in advance
Ermin D. Concepcion

Hi,
As I understand, U have 2 approving officers which in turn release two levels, so then create release codes{A1 (1st approving officer) & A2 ( 2nd approving officer )}.
Now create release characteristics(CT04) for PO VALUE with CEKKO with GNETW & keep with values <= 500,000 & >500,000. Add release characteristics for PO VALUE with other release characteristics ( PO document type, Plant, Pur.Org, Pur. Group) in a single PO Release Class(CL02).
You should have release Group(PO) for PO & Create two Release strategies (T1 & T2). Now during designing release strategy, you can keep value <= 500,000 with A1 release code under T1 release strategy and keep value > 500,000 with A2 release code under T2 release strategy.
Regards,
Biju K

Release procedure setup for changed Purchase orders

Hello All,
I have below scenario
1. After PR creation, it will be approved. and get converted to PO. At this time no need for approval (release) again. But once the same PO has been changed it should be subjected for release (approval). Can we have release strategy setup which will get trigger only when PO is changed.
2. Similarly, if PO is created without PR, then it should get subjected to release.
How can we configure the above business process in the SAP system?
Regards
Krishna Prasad
+41 61 3237548

Hi,
Do you have version mangement active in your system for PO's . If you have then you can use the filed CEKKO - REVNO
Maintain the Character Value as > 0,
So any PO whose version number goes above 0 , the relase strategy will trigger.
If not, then first of all you have to configure Version Management.
Go to SPRO > MM > Purchasing > Set Up Version Management for External Purchasing Documents > Here activate Version Management for the PO Doc Types you want. Here activate the following indicators.
Version active
Version 0 OK
So whenever PO will get created the Version 0 will get activated automatically. And whenever you change PO, it will generate versions 1,2,3 and so on.
Now in PO Release Characteristics use Field CEKKO-REVNO
And in "Clasification", maintain value > 0 (Greater than Zero)
And then check in ME21N, release strategy will not be applicable but for ME22N, it will get applied.

Contract Release Procedure

Hi Experts,
I am new to the Release procedure,can anyone please tell me the configuration steps for this contract release procedure.
My client needs a release procedure for the quantity contract.
Please guide me how to configure this in the system.
Thanks in Advance.
Regards,
Venu

Hi,
Your question is not clear, you asked two level but each level values are not clear.Ok.
As I understand , if you want release two levels, create release charactristics with CEKKO with GNETW & with values <=15000 & >15000, Create two release codes(C1 & C2) & cretae two Release statergy( T1 & T2). Now during designing release statergy, you can keep value <=15000 with C1 release code under T1 release statergy and keep value >15000 with C2 release code under T2 release statergy
if you want release three levels, create release charactristics with CEKKO with GNETW & with values <=5000 , 5000.01-15000.00 & >15000, Create thre release codes(C1 ,C2 & C3) & cretae three Release statergy( T1 , T2 &T3). Now during designing release statergy, you can keep value <=5000 with C1 release code under T1 release statergy, keep value 5000.01-15000.00 with C2 release code under T2 release statergy and keep value >15000 with C3 release code under T3 release statergy.
For Contract Document type MK( quantity), create release characteristics with CEKKO with BSART & keep value MK only(if WK not required)
For Value in Contract, create release charactristics with CEKKO with GNETW & with values as required.You need to add all release characteristics under a release class.
Regards,
Biju K

PO Release characteristics

Similar Messages

Maybe you are looking for