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.

Similar Messages

Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

Hi Friends,
I have a issue to fix. The issue is releated to PR.
There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
I have to retrigger the release strategy for all the affected PR's.
The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
Regards,
Manjunath K

Hi,
Refer the discussion to triggers release again on release code addition/change in release strategy.
release code is changed on PR release strategy - old PR can´t be approved
Regards,
Biju K

Release strategy for PO and Contract

Hi,
I maintain characteritic for PO
Plant
Doc Type
Net Order Value
Purchasing Group
I maintain characteristic for contract
Company code
Target Value
Doc Type
Purchasing group
My class consist of
Plant
Doc Type
Net Order Value
Purchasing Group
Company code
Target value
Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
Q2: What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
Thank for your advice

First of all
For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
You have to maintain all the characteristic value then only it will trigered release.
Check the release indicator as well.
Hope it will help.

Release Strategy for SA/Contract/PO

Hi friends,
Should we have different release groups and release codes in contracting/ SA/ PO.
Because...
I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
But i want to maintan only 2 characteristics in release strategy for contract [plant, total net order value]
because the same is reflecting in contract config also.
Is it possible..please help me frnds.
Prabhu

Hi Prabhu,
Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
Regards

Restrict PO creation for multiple plants for same company code

Hi Gurus,
We want to restrict PO creation for multiple plants in the same company code. Based on Standard SAP settings for Purchasing organization assignment with multiple Plant and multiple Plant assignment with single company code, this is happening. Is there a way that we can restrict by doing some customization change.
Any thoughts or ideas will be highly appreciating.
Thanks and Best regards,
Karun Kumar

Hi,
Said functionality is not available in SAP standard.
To avoid the same ,i can suggest implement release strategy for PO,and then higher authority / commercial team can check created PO,if multiple plants available in single po then they have the option of rejection for the same.
Or else check BADI-ME_PROCESS_PO_CUST,take the help from abapor and apply the restriction to select multiple plant in PO.
Hope this will resolve your query,
Thanks & Regards,
Sandesh Sawant

How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

Purchase Order not subject to release strategy for contract rel. strategy

Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
So I have checked this release strategy with this codes:
CL24N ok,
CT04 ok,
CL30N ok,
CL20N ok,
Release simulation in release strategy works,
Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
Thank you for your help in advance.

I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
Also compare your release strategy settings with many existing documents in SCN.
Check your Classification should be like that.
You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

Release strategy for Release POs

Hi Every one,
We have a requirement.
A contract is created and approved as per the regular strategy.
The releases (POs) are created against it and sent directly to the vendor.
As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
But the business wants the PO releases too to follow the release strategy.
Can you please look in to this and let me what changes we need to make this happen.
Regards
Pavan

As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
So that the Release Process is applicable to PO's created w.r.to Contract also..
For ex: if you use the field purchase Doc category as a Character in the Release , it differentiates whether it is PO or Contract..
So that you can define different Release Strategy for PO & Contract
Or if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
then the release strategy applies to PO also..

Want to change my existing Release strategy for - PR, PO & Service Entry

Hallow Experts ,
Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
regards
vb

Dear Vikrant,
1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
Sol: Not Required but , doing it is recomandaed
2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
thanks in advance.
Sol: No Only thing you have to do is that go to your class 32 and chek what is the charaterstic define for the purchasing group copy it
2 Now go to Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group , that group will now in fact of release Strategy

Contract for multiple company codes

Hi,
The requirement is to process the Sales Contract for multiple company codes, the concern is
while creating the Contract document in VA41 we get the Sales area as mandatory.
How to achieve this? if we suppress or make it as optional with some kind of ABAP customisation (what it should it be? usereixt/VOFM routines or what?) would it solve the problem ? if yes ,what would be the impacts on the other transactions.
Kindly suggest.
Regards
SR

Hi
If it is a customer contract (SD contracts) then it is not possible to create the document without specifying the sales area. In the overview screen, even if the sales area is not specified, it takes the value from the 'Sold To' customer master record. If the SP exists in multiple sales areas, then the system displays the different sales areas in a popup and we have to select the appropriate one. To my knowledge, even if you manage to create the contract without those details, you cannot refer them for creating the release orders.
Thanks,
Ravi

Derivation Rules Not Working for other company codes

Hi,
I have 5 Company codes and only for one FM was activated. now i want to activate FM for all 5 company codes. for which i have assigned the FM area to all 5 company codes. I have also assigned the derivation strategy to all 5 company codes as well. now when i post a transaction for any other company code derivation rules is not being process hence no commitment item or fund center is derived. however for the original company code for which FM was activated in the first derivation rule are working fine means system is deriving commitment item and fund center. can any one tell me why derivation rules are not working for other company codes? do i have to add Company code in source field of derivation strategy? could this be the reason? because in beginning there was no other company code so we did not included any company code field in the first place.
Regards,

Faizan,
Go to Funds Management Government> Actual and Commitment Update/Integration> Activate/Deactivate Funds Management.
In the screen create an entry for each Company Code and Funds Management Area combination.
Activate the AA Derivtn flag if you want the derivation to be called and the Update flag if you want to update commitments and actuals in FM.
Thanks
Shyam

Release Strategy for PO not kicking in

Hello SAP Experts,
I have gone through all the steps of configuring release strategy for PO. I checked at the end with the transaction code OMGSCK and everything is good with no error. But when I test the strategy by creating a PO, the 'Release Strategy' tab does not come on in the PO Header. This means that the Release Strategy did not work. I have troubleshot over and over again right from the Characteristics/Class, all the way to the Release Strategy, but no breakthrough.
I will appreciate and award points for helpful hints.
Thank you in advance.
Joel.

Please list all your char you have created and the value of char.
Than please tell the PO details.
once i got this info than only i can see the problems.
you can do one more thing
goto CL30n and enter the class and class type 032
than hit enter and enter the value of char which you have used in the PO and then hit find initial class button from top menu
see if any release strategy is pulled or not?
if it is determine morethan one that means you have same value exist in more than one release strategy

No release strategy for service PO

Purchasing document xxxxxxx cannot be released
Message no. MEPO823
I created release strategy for service entry sheet through following process.
1. Created three characterstics(service_val, serv_plant & ZSER_DOC TYPE) and assigned it to class 032 (gave it name service entry sheet) Communication structure CESSR and fields WERKS etc...
2. Than maintained all the config setting for service entry sheet through External service management..Maintained release groups, release codes, release strategy and r and maintained all the values .
3.I made a service PO with doc type FO
Now i dont get a tab of release on the service PO tab and get the above error.
Just let me know step by step how to config release strategy for service entry sheet.Do we need to maintain all above entries...?
For PO we have release strategy maintained for all document types and i am able to release the PO.
Regards,
Shailendra

Keep the release strategy at Plant level only....All the purchasing docs will get blocked

Purchase Requisition Release strategy for MRP based Requisition

Hello Gurus
We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
Thanks
Nick

Hi,
If you want include the MRP related PR in Release strategy.
You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
But it will not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
I think first one is best suited.
rgds
Chidanand

Release strategy for Purchase order

Hi Friends,
My client was using Release strategy for purchase order. Now we want to know the T-code for showing list of Rejected Purchase orders, T-code for for showing list of approved purchase orders, T-code for showing list of blocked purchase order.
Thanks and regards
Krishna

HI,
You can go to SE16N view table name EKKO
FRGKE   Release ind. = B
FRGZU   Release status = <blank>
mean, this PO yet to approve/ rejected.
FRGKE   Release ind. = R
FRGZU   Release status = X
means, this PO has been approved.
Hope this helps

PO Release Strategy for 3 company codes

Similar Messages

Maybe you are looking for