PR release strategy

[Former Member]

I need to create a new release strategy.

My problem is there is an existing release strategy with classification. The new release strategy require exactly the same classification. Same document type, same material, same account assignment category etc. The only different is that if the PR is raise by certain user, then it will go to the new release strategy, otherwise it will still use the old release strategy.

I tried to add "Name of requisitioner/requester" to identify the user who raise the PR. When I raise the PR by entering the requisitioner name in "Requisitioner" column, the PR created still go to old release strategy.

May I know what is the problem? How can I identify who create the PR?

May I know whether what I am trying to do is the correct way or maybe there is another better way to do it?

Thanks and regards,

JT

[Former Member · Accepted solution]

Hi JT

In your case, there are two issues.

a) requisition created by : the person who loged in

b) requisition requested by : the person who needs the material in the palnt, but the person who actually entering in the system is different.

Please choose which is your case.

Solution :

First case :

Add another characteristic with CEBAN-ERNAM. --> Assign this characeteristic to the existing class. Created a new release strategy with this (login person name for whom different strategy required). Also add the value of the other login names for the exisiting release strategies.

Second case :

Add another characteristic with CEBAN-AFNAM. --> Assign this characeteristic to the existing class. Created a new release strategy with this (requisitioner name for whom different strategy required). Also add the value of the other requisitioner names for the exisiting release strategies.

One more setting is, you have to do "Requisitioner" field as required entry instead of optional. But, any name can be entered manually. So you can't restrict teh input and hence release strategies may not trigger always. Better choose first case. Log in names are limited and hence release strategy triggers automatically always without fail.

Hope, your question is answered.

Rgds

Atchyuth

[Former Member]

Hi all,

Problem solved.

I've created a new document type for the user with new release strategy instead.

Thanks & regards,

JT

[Former Member]

Hi all,

I still encounter problem for my release strategy.

Although the new release strategy is working fine but old release strategy doesn't work now.

What value should I put into the CEBAN-ERNAM for old release strategy?

Thanks & regrads,

JT

[Former Member]

Hi

Add the new chracteristic created with structure CEBAN & field ERNAM

Add it to the relase class being used.

Configure the new release strategy

now goto CL24N, enter the PR release class

two release strategy will be displyed old & the new one.

In the old one for the ERNAM charactrerisitic add the Value Notequal to requisitoner XYZ (symbol for not equla to is less than & gretaer than)

Now in the new one add equla to requsitioner XYZ

This way the relase strategy will work if the user raises the PR then new one will trigger.

Thanks & regards

Kishore

[Former Member]

Hi Kishore,

I'm sorry but can you show me in detail on how to put the Not Equal To sign in the release strategy?

I will just leave the value blank for other release strategy? Will it have any effect to the other release strategy other than the two release strategy involved?

Thanks & regards,

JT

Edited by: JT on Jun 16, 2008 3:06 PM

[Former Member]

Hi

Blank chracterisitc values do not work for release startegy,

not equla to sign is (put a less than symbol & gretear than symbol)

I am not able to put it here as it will not display.( diamond symbol placed horizontally)

its the same symbol as used in SAP programs

You need to put this symbol in one release strategy the only it will work.

Thanks & Regards

Kishore

[Former Member]

Hi Kishore,

Where do I need to put the symbol?

Do I include in the value itself?

'less than symbol & greater than symbol' USER-ID? Any space needed in between the symbols and the ID?

Thanks and regards,

JT

Edited by: JT on Jun 16, 2008 3:25 PM

Edited by: JT on Jun 16, 2008 3:26 PM

[Former Member]

Hi

In the characteristic values, give The not equal to symbol, space & the user ID

In the old strategy put not equal to user ID

In the new strategy give User ID

[Former Member]

Hi Kishore,

After adding the new chracteristic CEBAN-ERNAM, I added value into few release strategy.

It is actually working fine now. But all the other release strategy in the same class is not working. PR creation does not trigger any release strategy except those few release strategy with value in CEBAN-ERNAM.

May I know why? Do I need to add the value into every single release strategy?

My situation:

Release Strategy A - User ID

Release Strategy B - Not Equal To User ID

Release Strategy C - Blank

Release Strategy D - Blank

Release Strategy E - Blank

Only A & B same characteristic.

Should I do this?

Release Strategy A - User ID-A

Release Strategy B - Not Equal To User ID-A

Release Strategy C - User ID-C

Release Strategy D - User ID-D

Release Strategy E - User ID-E

Thanks & regards,

JT

[Former Member]

Hi expert,

Anyone else can help me on this?

Thanks & regards,

JT

[adwait_bachuwar]

Hi JT

as far i know this may be the cause. see in oyur old strategy the release strategies c d and e have same values that is blank. now when system is trying to find out the release strategy it gets confused about which to follow. to overcome this either you have to keep only one strategy with blank value and assign other strategies other values or remove them. since a and b are taking care of user id. blank will take care of no requisitioner.

let me know if this solves your problem

[Former Member]

Hi Adwait,

FYI, for my old release strategy, there are some other characteristic that I didn't list out. Maybe I should list it out for better understanding.

Current Release Strategy:

Release Strategy A - User ID, Doc Type A

Release Strategy B - Not Equal To User ID, Doc Type A

Release Strategy C - Blank, Doc Type C

Release Strategy D - Blank, Doc Type D

Release Strategy E - Blank, Doc Type E

After I added User ID into CEBAN-ERNAM, only Release Strategy A and B is working. Release strategy C, D and E are not working at all.

Should I add all the respective user ID into the release strategy like this?

Release Strategy A - User ID-A, Doc Type A

Release Strategy B - Not Equal To User ID-A, Doc Type A

Release Strategy C - User ID-C, Doc Type C

Release Strategy D - User ID-D, Doc Type D

Release Strategy E - User ID-E, Doc Type E

Thanks & regards,

JT

[Former Member]

Hi

U can edi old release strategy Add new charactaristic Name of requisitioner/requester ( Field AFNAM structure ( table) CEBAN )

Add required values in modified Release strategy

Vishal....

[Former Member]

Hi Vishal,

I have actually addded "Name of requisitioner/requester" to identify the user who raise the PR but it still cannot work.

When I raise the PR, I should enter the value in "Requisitioner" column?

Thanks and regards,

JT

[Former Member]

Hi

U need to enter Name of requisitioner/requester who has requested to order material

Pls confirm. what values u have maintained for Requisitioner while defining charactaristic

Vishal...

[pankaj_singh9]

Create a new characteristics in CT04 as Name of requisitioner/requester using Structure CEBAN and field AFNAM.

Assign this char in the class you r already using for Release Strategy.

Create a new Release Strategy for the same Release group and in "Classification" option assign "Name of requisitioner/requester" for which this Strategy to be applied.

And for Old Strategy Assign rest of the "Name of requisitioner/requester" and SAVE.

[Former Member]

Hi,

view the table EKKO and find the field name ERNAM the creator of the object and the same field can be found in the structure CEBAN

In classification u can use this field as one of the character.

And you specify the character in the strategy.

Hope this will solve ur issue.

Regs