PR Release Strategy- transport of charact/class/ values using ALE

Does anyone have the information relative to ALE set up for release strategy-
I am using transactions BD91 for characteristics; BD 92 for Class and BD 93 for the actual values into release strategy.
I need the information as to what needs to be set up in Development client and receiving clients ( Q and Prod) for these transactions i.e., RFC destinations, define ports, Identify Message types & setup partner profile configurations etc
This will be a great help.
Thanks
Raj

Hi Raj,
Please check the below notes for more inrofmation:
86900 - Transport of Release strategies (OMGQ,OMGS)
799345    Transport of release strategy disabled
10745     Copying classification data to another client
45951     Transporting class data: system / client. - has details of what you are looking for.
Hope this helps.
Regards,
Ashwini.

Similar Messages

Release strategy Assign objects to class (CL20N)

Hi,
I am entering values for characteristics for release strategy in CL20N Transaction,
For purchasing group (characteristic) I need to enter all the purchasing groups in values. (Around 50 purchasing groups).
Now the requirement is user cannot able to enter purchasing groups every time in value (CL20N) so he need to enter asterisk "*" which should applicable to all purchasing groups.
For example: characterstics is Purchasing group and values are 001,002,003,....etc.
if we enter "*" u2018(Asterisk). Is that applicable for all purchasing groups?
Asterisk will allow in values?
If not what is the solution if any new purchasing groups used in PO it should trigger release strategy.
Please any expert gives solution for above issue.
Regards
Kumar

Hi,
Just like Sai mentioned its better to remove the Pur Grp from the Characteristics Value rather than entering all of them.
I would suggest to check if you have some additional Characteristics that would qualify to prevent Release Strategy from not populating on those documents example doc type or company code or item category or account assignment category.
Hope this helps.
Thx
MJ

Release strategy transport using BD91/ BD92 and BD93

I would like to move Characteristics/ Class and Release strategy using ALE transactions BD91/ BD92 and BD93.
The question I have is that do I run the ALE transaction from the Source enviornment( Development box) to export it toTarget box( QA)?
Or do I run it in Target box (QA) to import it from DEV box?
Thanks
Raj

Hello,
You need to setup Customer Distribution Model (BD64) and Partner Profiles in DEV (Outbound) and QA (Inbound) systems with ALE Port. Then run the transactions BD91, BD92 and BD93 in DEV. If the partner profile in DEV is setup to transfer immediately, IDOCs will be transferred to QA.
Thanks,
Venu

Release Strategy for New & Change PO's - Using characteristic CEKKO-REVNO

Hi All,
I have the following requirement/scenario
1. If PO is created manually no reference to PR, then the PO needs to be approved through a release strategy.
2. If the PO has been created automatically either from a req or through SRM (for,eg) then the PO needs to be approved only if this PO has been changed. So this would need to go through a second release strategy.
To distinguish between the two, we are using Version number field CEKKO-REVNO in the communication structure CEKKO to be a characteristic in the release strategy.
This is what I hoped for would work after doing the necessary config,
For create PO's, in my classification I have CEKKO-REVNO as >=0. So any PO whose version number is >=0, will trigger relase strategy S1 (for e,g).
For change PO's in my classification I have CEKKO-REVNO > 0 And whenever you change PO, it will generate versions 1,2,3 and so on, and hence the release strategy will trigger.
The problem
Whenever I use CEKKO-REVNO as one of my characteristics, the release strategy is not triggered at all no matter what the conditions are on the PO. When i removed the REVNO from my classification, release strategy is getting triggered as per plan. I have also activated version management and done all the necessary config. I would like to know why release strategy is not getting triggered when REVNO field is used from communication structure CEKKO. Have any of you experienced this issue before??
Is their any other identifier I can use to address the requirement above? Let me know.
Thanks
Ashvin

Thanks Charlie for your response.
The conditions in the PO is not equal.
On one occasion when I create the PO, I have given the classification as REVNO >=0 with a document type ZB for create (S1). So when I create the PO manually, the version starts with 0, so condition should satisfy here
On the other when I change the PO (with/without reference to PR), I have given the classification as REVNO as > 0 with document type ZC (S2), so when the PO is created initially it will not satisfy strategy S1 as doc type is different for S1. When I change the PO created with ref to req, S2 should take into effect because when i change the version will change to 1 and S2 should trigger because REVNO is > 0 and doc type matches.
So I dont know where the release strategy matches in both S1 & S2 for the system to not propose the release startegy.
Let me know your thoughts.
Thanks for your feedback.

PO Release Strategy trigger based on PR value

Hello All,
We have one requirement where PO Release should trigger if amout of PO is greator then PR value. Let me know how this can be achived as I understand that both have different communication structure like CEKKO & CEBAN.
Pls advise.
Rgds,
AC

We have one requirement where PO Release should trigger if amout of PO is greator then PR value. Let me know how this can be achived as I understand that both have different communication structure like CEKKO & CEBAN.
Hi,
You can try doing it with a WorkFlow as you identified communication structures differ.
Regards
Shiva

P Req. Release Strategy not Transported

Hi,
For Configuring the Purchase Requsition Release Strategy, We have Created Characteristics and Class in the Configuration Development Client. Created Release Groups, Assigned Release Codes with the Release Group, and Assigned Release Group with Release Strategy with Classification. Tested PR Release Strategy for the given Classification Values the Release Strategy triggered.
We have Created same Charateristics and Class in the Testing Development Client (Since the Characteristics and Class are not Transportable). Transported Release Groups, Release Codes and Release Strategy from Configuration Development Client to Testing Development Client. When we check the Release Strategy Classification in the Testing Developmemnt Client, system showing Classification Error.
Please let us know whether the Release Strategy Classification Requests are Transportable or not.
Ravi

Dear Ravi,
The Release Strategy Configurations can be transported, in respect to the requests transported.
But the assignment of the Characteristic Values to the respective classes needs to be done in respective destination clients. Since teh assignment will get transported.
To Do the same, please use transaction CL24N, Enter the classes Used in your release strategy and assign the respective Characteristics Values.
Hope this will serve the need.
Njoy SAP
- Regards,
Saravanaganesh

NUMBER OF CHARACTERISTICS AND VALUES IN RELEASE STRATEGY

Hi there, how R U.
Please, can any body help my with this one ?
How many characteristics may I have in a release estrategy for purchase order an contracts ?, how many values could a characteristic have ?, if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
I hope you can help me.
Have a nice day.

How many characteristics may I have in a release estrategy for purchase order an contracts ?,
You can have as many number of characteristics you want for release strategy, no restirction
how many values could a characteristic have ?
You can have as many as you want, no restiction
if I´am using a user exit to get the release codes, could this reduce the number of values that I can have in every characteristic ?
Release code you can define only 8 and if oyu want more release code than create new release group and assign more release code
An ABAP consultant told me that in table AUSP the release startegy can only have 8 values or less, but not more than that, is this true ?, to be candid, I don´t thik so, otherwise if I had a characteristic with 20 values what would happen?
the release strategy can hold only 8 release code but every release strategy you can have more than 8 charcteristics and each char can have n number of values and that can be decied at char creation level

Po release strategy - if value decreased

Dears,
If the Po value is decreased, I need the release strategy to be re triggered. As I know in standard its not possible. But can you help Is there any BADI or user exits can be used to accomplish this task.
Regards
Kamesh

Hi,
Use release indicator '4' or '6" during designing of release strategy.
And
If you want PO release strategy should trigger for reduced value ,then you can for User exit EXIT_SAPLEBND_002 or check to modify standard function module ME_REL_STRATEGIE_EKKO which help to reset existing release strategy for reduced/increased and/or values.
For more check the SAP note:493900
Regards,
Biju K

Why we Maintain the data in Trxn # CL20N / CL24N for Release Strategy ?

Dear All Gurus,
Please resolve my Query , that during maintaining the Release strategy for a P.O , i used to create characteristics for defined values such as plant , currency , doc. type etc, then creating class and assigning these characterstics with this class created.
Now after this i had create Release Group , Release Code and Release Strategy and assigned the Rel. Code with the Rel . Str and in Classification tab i had manually mentioned all those created Characterstics in CT04 and finally saved this Process.
Till now i had not at all made any entry in Trxn # cl20n.
But when i had create a P.O with all the values as same as defined in characteristsc , the Rel Str got triggered succesfully.
My Question is that , what is the use of mainiating data in Trxn # CL20N & CL24N ?
Please clarify my doubt.
Many Thanx in advance.
Rgds
sap11
Edited by: Rajeev Chaturvedi on Jan 20, 2011 5:08 PM

it is just another way to maintain the same thing in the same tables. Classification notspecific to release strategies, materials and batches, vendors and customers can be classified too.
You can do this from withion those objects, or from the central classification menu using the classification transactions.
People here recommending this for production system after you have transported the strategy from developement to production. Becaues classification is master data and cannot be transported the usual way. And many here do not know how this can be done with ALE

PO Release strategy release procedure

Hi
Any body can suggest
what is the procedure for release strategy transport to anther system means D to Q

Hi,
Release strtagy Configuration can be transported from one client to various client[Like creation Class,characterstic,Release code,release strtagy definations etc]
Where as assignments of Objects / class and various parameter for release strategy has to be done in individual clients in -T-code: CL24N.
Example : For Class -PO Release we need to assign -Values for Class -characteristic values has to assign in CL24N
with regards
Shrinivas Gangoor
Edited by: Shrinivas Gangoor on May 22, 2009 3:06 PM

Release strategy problem in RFQ

Dear cons
In release strategy of P.O we are using three characterstics. I.e- net order value, purchase group & plant. Wehave not made any Release strategy setting for RFQ..while we are creating RFQ the system ask to release the RFQ. wHY.wHAT IS THE REMEDY FOR THAT. BECAUSE WE DONOT WANT TO RELEASE THE RFQ. I saw which data I have entered for P.O release strategy The same data is available In RFQ path.The path is img-material mang- purchasing- P.o- rel. PROCEDURE for P.O- DEFINE REL. PROCEDURE FOR p.o. you can check same data is avaiable in RFQ PATH.
PL. GIVE ME SOME HINTS.

Hi,
Please use document category or document type or both as chanracteristics for the release class.

Release strategy modification

Hi all,
I've a query regarding PR release strategy configuration. Already in our system there are release strategies working based on two characteristics i.e. 1. Purchase Requisition Document & 2. Purchasing Group .
Now, my client wants me to add one more characteristics to the existing release strategies. I've identified this field in communication structure CEBAN (CFWRT - Total value of requisition for overall release procedure).
My requirement is in few release strategies Ive to check a condition for PR total value (CFWRT) is less than 5000 Rs.
To achieve this condition I've created one more charterictics for CEBAN - CFWRT and included that in existing class and modified the release strategy. But, when I created a PR (satisfying this release condition) with total value greater than 5000 Rs. still this release strategy is picking. which shouldnt be the case.
Please help! How can I achieve this...
Thanks,
Rajan U

Hi,
As needed, you created one more charterictics CEBAN - CFWRT and included it in existing release class.And also you redesigned the release strategies but,you have issue for triggering right release statergy for correct value with conditions.
Now just cross check you should have following u201CValuesu201D in the release charterictics {CEBAN u2013 CFWRT} as
1. <= 5000 INR
2. > 5000 INR
Craete release group as PO and create two release codes C1 & C2.
Now as needed you can design your release strategy or create two release strategies as T1 & T2. Keep value <= 5000 INR with release code C1 under release strategy T1 and Keep value > 5000 INR with release code C2( or keep C1 & C2 as required) under release strategy T2.
When you will create PR with value less then 5000,system will triggers release strategy T1 and PR with value more then 5000,system will triggers release strategy T2.
Regards,
Biju K

Release strategy does not reset after PO change - tried changeability 4 & 6

Hi,
After my PO is released, I change the item quantity/price such that the net PO value (increased) is changed MORE than the tolerance % set in the changeability. I expect that the PO release should be reset but it does not.
However if my PO value is changed (increase) such that my PO value is now in a different "release bracket/range" -- as it falls into a different release strategy, then the release is reset.
Could anyone advise me what is wrong? I tried everything - i tried changeability = 4 and 6. i deleted the whole release class, release strategies and recreated -- nothing.
According to OSS note 493900 below, it should reset when the tolerance % is breached.
I'm on SAP 4.7.
Anyone could advise?
thanks!
     3. Question :
     Why is the release strategy not reset ?
     Answer :
     A reset of the release strategy only takes place if
            - the changeability of the release indicator is set to '4' in
               case of a purchase requisition and '4' or '6' in case of
               another purchasing document (purchase order, request for
               quotation, contract, scheduling agreement),
            - the document is still subject to the previous release
               strategy,
            - the new TOTAL NET ORDER VALUE is higher than the old one.
     The total net order value is linked to CEKKO-GNETW for a purchase order,
     CEBAN-GSWRT for a purchase requisition item-wise release and CEBAN-GFWRT
     for a purchase requisition overall release.
     If you have maintained a Tolerance for value changes during release
     (V_161S-TLFAE), the release strategy is reset when the value of the
     document is higher than the percentage you have specified and if the
     document is still subject to the previous release strategy.

Hi,
Thanks.
The release strategies are able to be determined correctly when the PO is created so I guess that means its all setup correctly?
The issue is only with PO change - how to cause the reset when the PO value increases by more than the tolerance %.
cheers.

Release strategy control fields

I am doing release strategy in my project for P.O. Please answer follow question
a) by what fields we can control release strategy, and how we know can use only those particular fields control by these field
b) What is the difference between EKKO and CEKKO? Why CEKKO should use? Is that should use always C before EKKO? If yes, why?

Hi,
a) by what fields we can control release strategy, and how we know can use only those particular fields control by these field
--> You can use the fields to configure release startegy which are available in communication structure CEKKO. All fields in communication structure can be used to control release strategy.
b) What is the difference between EKKO and CEKKO? Why CEKKO should use? Is that should use always C before EKKO? If yes, why?
---> As said by Indranil, it is a communication structure and it is copied from the table EKKO to enable the release strategy.
System follows the below described procedure to apply release strategy. This will understand you more clearly.
When you process a purchase order (PO), the system passes on the data from the PO document to the communication structure CEKKO.
After the data has been passed on to the communication structure, the system initiates an object search:
1. The system checks which class is defined in Customizing for the release procedure.
Note
There can be only one class for all purchasing documents (POs, contracts, scheduling agreements, etc.). This one class (032)then constitutes the basis for the release procedures for all purchasing documents.
2. The system assigns the values from the communication structure CEKKO to the characteristics of this class.
3. Via the object search function, the system then identifies a release strategy whose characteristics accord with the values from the communication structure or lie within the specified interval.
The following search results are possible:
Just one release strategy is found.
The system assigns this release strategy to the purchasing document.
Several release strategies are found.
The system assigns the first release strategy found to the purchasing document.
No release strategy is found.
The system does not assign a release strategy to the purchasing document.
Hope above explaination helps you.
Deepak.

PRs not finding a release strategy

Hi All,
I am having a issue with creating PRs, when i create PR with one line item, it is finding the release strategy but when i create PR for more than one line item SAP can't find the release strategy.
The only common factor for the problem would appear to be that they are multi-line PRs.
Please help what should i do.
Thanks in advance.

Hi Madhur,
Kindly check below
1.If for each line item the material group is different
2.Using Header level release strategy
Thus this material group is aggregated at header level and " " value
used as document in the below note
47089 Release procedure for purching docs - Aggregation
The release procedure for purchasing documents is carried out on header
level. For this, the following values are aggregated from the items on
header level:
item value
plant
material group
Example WERK:
The plant is only aggregated on header level if all items coThe same fun
same plant. If only one alternative plant exists, ' ' is aggregated on
header level.
A release strategy is then searched for with this value.
Of course, a corresponding strategy is only found if the value ' ' was
maintained for the characteristic 'Value' as an object value.
The same functionality applies to the material group as for the plant.
If one item has material class x and the
other y the system does not know with which material class it should
look for a release strategy. Now the system sets the material class
to 'blank' and tries to find a release strategy. If you do not have
defined a blank entry in the customizing.
(: OLME >release procedure for PO > rel. strategy)
system won't find a release strategy.
Add a blank value to your allowed characteristic values in your
release strategy. To do this you can define a blank value in your
characteristic (CT04). On the values screen leave the char.value
blank and add a description and save.
THIS PART YOU HAVE ALREADY DONE
CT04 > PO_MATERIAL_GRP has blank entry
SO JUST maintain it in customising of Release strategy.
Please also have a look into the attached note 365604 point 2d)
regards,
Lalita

PR Release Strategy- transport of charact/class/ values using ALE

Similar Messages

Maybe you are looking for