PR Release Strategy Field

[Former Member]

Hi All,

We have a business scenario wherein we have various departments in an organization. If the user from any department raises a PR it should only go to his head. The head of department for different departments are different. Moreover the releases are based on value also.Which field in CEBAN will solve my purpose best? I have tried with Purchase Group, Tracking number, Requisitioner, Creator of PR (ERNAM) but none is fulfilling my requirement. Please suggest about the possible solution for this scenario.

[Former Member · Accepted solution]

Hi,

Your requirement can be solved using field AFNAM from eban table.

[Former Member]

Hi Dear,

we have a similar Scenario at our place, and what we have done is that we have Triggered the Release strategy based on the requisitioner.

we have maintained a Ztable for all the input fields in the Requistioner, and at the same time provided a drop-down for the same field, and the release startegy is triggered based on the requistioner. and the respective users are given the Authorizations only by the Authorized Requistioner maintained in the role.

for this again you will not find an object for the T-code ME51N, there fore we have put in the Zobject ZAFNAM.

please revert back for any more help.

Regards,

yawar Khan

[Former Member]

HI,

If you do not want to use any of the standard fields then go for enhancement add a new field for department

and add that field in CEBAN ->USRC1 (User field format character for release strategy)

Check this links

[Former Member]

Hi,

I believe you have a org structure defined which can be seen in PPOME. You can use position ( table T16FW) to release code mapping and assign the respective users to positions. Btw how do you differentiate between departments in a PR ? Foe example do you use different purchasing groups for different department ? Then you can use the same criterion to pick up correct release strategy.

Regards

Sayan

[Former Member]

Hi,

Here purchasing groups cannot be taken as departments & 1 buyer is assigned to multiple departments. Thus solution is not feasible as per their requirement. I am trying with ERNAM but again here each user ID will have to be created based on departments. I am not sure whether this will work.

Please suggest what can I do in SAP best practice. I don't want to go for any enhancement for the time being. Will this be possible in standard SAP without enhancement.

Thanks

[Former Member]

Hi,

Generally it is recommended to create different purchasing groups for different departments. That will even help in creating roles for requisitioner and approver and restrict access for release of PR.

Please let us know if you can find out any other standard solution.

Regards

Sayan

[Former Member]

AFNAM is a characrter field. So if you want to use this field please maintain Department names in this field and accordingly maintain the same in Characteristics. Kindly check if this solution works.

Sayan