Change Purchase Req. Release strategy

[pavanm592]

Hi,

I have a Requirement to Re-trigger the Release strategy for a PR which is already released.

Here i have different release strategies A1 A2 etc.

A1 < 20,000 SAR

Now  my PR the value is in A1 Range initially and it is released,when i am changing the quantity(Consider only when increasing QTY case)

in ME52n the PR value is still less than 20000 SAR in that case release strategy is not triggered again .

My requirement is to change the Release strategy to "Release Possible" in this case.

Looking for some help.

Thanks,

PAVAN

[pavanm592]

Hi,

I have a Requirement to Re-trigger the Release strategy for a PR which is already released.

Here i have different release strategies A1 A2 etc.

A1 < 20,000 SAR

Now  my PR the value is in A1 Range initially and it is released,when i am changing the quantity(Consider only when increasing QTY case)

in ME52n the PR value is still less than 20000 SAR in that case release strategy is not triggered again .

My requirement is to change the Release strategy to "Release Possible" in this case.

Looking for some help.

Thanks,

PAVAN

[Former Member]

Dear Pavan,

Check your PR release strategy in -

Spro->MM->Purchasing->Purchase Requisition->Release Procedure->Procedure with Classification->Release indicator

in Here according to your release indicator setting, choose in "changeabil." option(4 Changeable, new release in case of new strat. or val. change) .

Reg,

Bhg.

[pavanm592]

Hi Bhg blr,

Thanks for the reply,

is there any way to change the status technically,

One more thing i want to say is if the PR value after changing the qty is

>20000 then A2 is automatically triggered by the system,

But  after the release of PR user changes the qty again and its value lies in same range(i.e A1/A2 range) then

as per standard release strategy is not triggering now i want to change the status from "released" to "To be Released"

for that PR item.

Regards

Pavan

[Former Member]

Hi Pavan,

This may help you,

Check table EBAN (Plant), CEBAN (item).

T16FD - Release Codes

T16FK  - Rel. Indicator.

In functionally - system has to grayed out the Qty and Value fields  in me52 after release, so user has to reverse the release option than these fields to be allowed to edit.        

refer

http://scn.sap.com/thread/2064957

Reg,

Bhg.

[Former Member]

Hi Pavan,

Can you try as suggested below. May be you can achieve it technically!

I believe the release strategies will only be revoked if the value change is in the positive direction and is greater than the set percentage. You may be able to put some special coding in the following user exit in SAP's note 365604.

. User exit
During the individual release for purchase requisitions, the user exit is called in function module ME_REL_STRATEGIE_EBAN, in the overall release, it is called in function module ME_REL_GENERAL_STRATEGY_EBAN.
(Enhancement M06B0002, EXIT_SAPLEBND_001, ZXM06U13)

Important tables for Release strategies.

T16FS - Release Strategies

T16FG- Release Groups

T16FC- Release Codes

INCLUDE ZXM06U13.

e_eban-frgst = i_eban_old-frgst.

e_eban-frggr = i_eban_old-frggr.

e_eban-frgkz = i_eban_old-frgkz.

e_eban-frgrl = i_eban_old-frgrl.

e_eban-frgzu = i_eban_old-frgzu.

Thanks,

Kiran.

[pavanm592]

Hi Bhg blr,

QTY field is in enable mode i can change the value even after the release of item,

Thanks,

Pavan

[pavanm592]

Hi Kiran,

Thanks For u r suggestion i will try and get back to you.

Thanks,

Pavan

[Former Member]

Hi Pavan,

If you want to change it to display mode,

Check,

Materials Management -> Purchasing -> Purchase Requisition -> Define Screen Layout at Document Level -

(FZ01 - FZ02 - FZ03 or which layout is suitable)

Assign in -

Spro->MM->Purchasing->Purchase Requisition->Release Procedure->Procedure with Classification->Release indicator -> Field Selection Key.

Reg,

Bhg.

[Former Member]

is your issue resolved!

Thanks,

Kiran

[pavanm592]

Hi Kiran,

No, the import parameter I_CEBAN does not have those field you have mentioned.

Thanks

Pavan

[Former Member]

Hello Bhg blr

there was never the requirement to make the quantity field ready-for-input (which is was, by the way) or disable the input. You're on the complete wrong track, as Pavan want's to reset the release, whenever the quantity field becomes changed.

Florin

[Former Member]

Hi Kiran,

the release strategy itself can't be changed within the user exit modifying CEBAN.

Florin

[pavanm592]

Hi Florin Wach,

I need to trigger the release strategy every time the user changes the quantity in higher values after release(with in same release strategy),

one more thing we have made a customization for making quantity field editable,

can you please suggest me a way to achieve this task.

Thanks,

Pavan

[Former Member]

yeah, please see below.

[Former Member]

This message was moderated.

[Former Member]

What is the tcode for being assign the release strategy from one type of PR to another please?

[former_member15255]

Hello Pavan,

Re-trigerring of purchase requistion is possible by implementing the following customer exit

Enhancement : M06B0005

User exit        : EXIT_SAPLEBND_004

Regards

Suresh Nair

[Former Member]

Yeah, Suresh,

can you please explain exactly, how to achieve this? Would be very interesting to know, as I can't see this working yet, after having the analyzed, but I'm happy to see a more simple solution than the ones that I have outlined in my post below.

Thank you.

Florin

[Former Member]

Hello Pavan,

the Release Strategy for purchase requisitions does only consider the value field, regardless of any other fields that may have changed. So the outcome of the value per line item (or total amount, when using header release) is important.

If you need to react on other fields to enforce a reset of the given releases (but keeping the same release strategy) you'd need to make some tricky coding. There are some possible places to do so:

- The BADI functionality to treat customer enhanced fields on the level of EBAN, when the customer data is checked. On that situation you will be able to compare the quantity-field old/new. The reaction would be a side-call into form routine RESET within function group EBND. You may need to deeply look into the implementation starting with function module ME_REL_GENERAL_STRATEGY_EBAN.

If you're unsure there, what the coding exactly does, you should set a break-point and look how it works within the posting and changing of a requisition until you've understood the functionality -- otherwise I would strongly recommend not to follow that advice.

- Secondly, it is still very tricky but more workable, to influence the RESET at the start of the implementation of function module ME_REL_GENERAL_STRATEGY_EBAN. Having enabled an Implicit Enhancement option you could investigate the quantity fields old/new (or whatever sensible fields you'd like to check). This information is present in the given tables T_GEBAN_OLD and T_GEBAN_NEW.

If you catch the situation for a reset of the release strategy, you may try to modify - and clear - the values of T_GEBAN_OLD-FRGST and -FRGGR. This will bring line #146 and #146 of that function module to turn over your release strategy.

However, I would not recommend to make such changes, unless fully aware and familiar with the Release Strategy.

- There could be another possibility, moving a quantity-changed flag into the CEBAN structure and make your release strategy customizing sensible to that situation. This would be more modification-free, modification-less, but a more complicated approach as you need to trigger some background processes for the quantity-change situation, which isn't easy.

So after all, I'd say that the SAP Standard is not designed the way to make release procecure changes on other fields than the value-base. And if you need to do so, you're in some trouble

With the very best wishes

Florin