Overall release of purchase requisitions

[Former Member]

In our company, we're needing to change the purchase requisition release strategy from item release to overall release of PRs. We're planning to keep all existing characteristics as they are defined, just want to set the overall release indicator on the existing release group.

We're in ECC 5.0, release 640. Please let me know if there's any additional information that I can provide about our current R/3 enviroment.

There are two places that I have set the overall release indicator (OvRelPReq) using SPRO -

Define Document Types

Setup Procedures with Classification / Release Groups

Using SWECTYPV and I have activated the WS20000077 with BUS2105 at the RELEASESTEPCREATED event. I have activated the WS20000077 workflow template using PFTC.

When I create a PR, no release strategy is assigned.

Am I missing any critical step(s)? Any input would be great appreciated.

Thank you.

[KKilhavn · Accepted solution]

You haven't said anything about your characteristics definition. If I recall correct from the documentation, a characteristic that does not have the same value for all items will be left blank in the CEBAN structure.

If this is the problem, the solution depends on what you want/need to do. You can use the user exit for the CEBAN structure to make sure there is always a value, or you can change your release strategies, or add new release strategies, to handle those situations where a characteristic has no value.

[Former Member · Accepted solution]

Thank you for the helpful hint. Our current characteristic definition is

PUR_REQ_RELEASE 032 class

Charateristics:

PREQ_VALUE_RANGE_USD CEBAN.GSWRT

PREQ_INTERNAL_ORDER_TYPE CEBAN.AUART

PREQ_PURCHASING_ORGANIZATION CEBAN.EKORG

Z_PO_REQUISITION_ITEM_CATEGORY CEBAN.PSTYP

I will work with my functional counter part based upon your helpful recommendation.

[KKilhavn · Accepted solution]

The item value is not likely to be the same for all items, and in any case you probably want the total requisition value if you use overall release. So you should use GFWRT instead.

The field AUART doesn't exist in the system I have access to now, so that's probably in an append structure for an industry solution or something along those lines. Still, the internal order type can probably vary, and the purchasing organization and item category can definitely vary unless you have put special measures in place to prevent it.

You should in any case probably replace the current class with a new one, since either you will have to change all the characteristics, or at least they will take on a new meaning. The value is OK, that's just a field change. For the other three, you may wish to take them out of consideration, or you may wish to implement the user exit (enhancement M06B0002) to set your own values.

I mentioned that a characteristic that does not have the same value for items will be left blank, but as far as I have observed it seems this only applies to the items currently involved (changed). So for instance, assume you wish to not require release if the internal order type = 'F' for all items. I think you would then need to implement the user exit and set the order type yourself, checking all the items in the requisition. This is of course not a problem for new requisitions, but it is relevant for changes to existing items and when adding new items.

[Former Member · Accepted solution]

Thank you for your last note regarding the user exit. That helped us solved the item_category & internal order type characteristics issue.

Here's the steps that we followed to change approval from item release to overall release. Hope the note would be some help to someone.

SAP_BASIS SAPKB64016 SAP Basis Component

SAP_ABA SAPKA64016 Cross-Application Component

SAP_APPL SAPKH50009 Logistics and Accounting

SAP_HR SAPKE50020 Human Resources

Here’s what we have in our release strategy characteristics:

PUR_REQ_RELEASE 032 class

Charateristics:

PREQ_VALUE_RANGE_USD CEBAN-GSWRT

PREQ_INTERNAL_ORDER_TYPE CEBAN-AUART

PREQ_PURCHASING_ORGANIZATION CEBAN-EKORG

Z_PO_REQUISITION_ITEM_CATEGORY CEBAN-PSTYP

Steps for the Reconstruction

We have completed the below steps:

To change the CEBAN-GSWRT to CEBAN-GFWRT

1) Create a new characteristic PREQ_VALUE_RANGE_USD1 and reference

CEBAN-GFWRT

1) Create a new class PUR_REQ_RELEASE1 with using the below

characteristics:

PREQ_VALUE_RANGE_USD1

PREQ_INTERNAL_ORDER_TYPE

PREQ_PURCHASING_ORGANZATION

Z_PO_REQUISITION_ITEM_CATEGORY

3) Create a new release Group using the new class

There are two places that I have set the overall release indicator

(OvRelPReq) using SPRO -

Define Document Types

Setup Procedures with Classification / Release Groups

Read the above note from Kjetil Kilhavn regarding the user exit.

Message was edited by:

Jennifer Tran

[Former Member]

This seems to be a Configuration problem. Please review your Release Procedures for PR in SPRO.

Thanks

Arghadip