cancel
Showing results for 
Search instead for 
Did you mean: 

Authorization by plant in CK40N/CK11N

neeraj_bhardwaj4
Contributor
0 Kudos

Hi

I was trying to apply Plant specific authorization in CK11N as well as CK40N selection but it seems not working.

Can anyone share how it can be achieved...?

Neeraj

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member513101
Active Contributor
0 Kudos

Hi Neeraj,

I believed you already knew that these 2 T-codes' authorization are by company code and costing variant only. If you would like the program to check the authorization at plant level you can try to get your abaper to put the authorization-check syntax in this BAdi MAT_SELECTION_CK (note 1019389) and then assign the authorization object ot the user profile.

Bear in mind, if you are using "transfer control" for costing. You need the authorization for the "source plant" also.

Thanks.

neeraj_bhardwaj4
Contributor
0 Kudos

Thanks Lam for your reply.

I am already exploring the option to use enhancement Spot as suggested. ABAPer will come back to me on this shortly.

Regarding your other point, yes we are using the special procurement type for stock transfer and will use the same to pull the product cost from other plant. I thought of using the Transfer control for cross plant for checking the current cost estimate as 1st strategy and no transfer for 2nd and 3rd option. I did not do cost estimate in source plant but still system in destination plant was able to get the cost as it went to PIR to check the price. My expectation was that system should have thrown error. Not sure what is the use of giving strategy as no transfer. Also it updated the KEKO/CKIS for source plant which I think is wrong. system should only read data from source plant and not update anything in tables.

I need to figure out how can I control the access for these shared materials.

thanks for your reply.

neeraj_bhardwaj4
Contributor
0 Kudos

By using MAT_SELECTION_CK, we were able to restrict at selection step in CK11N and CK40N. Now, the issue appears when you have special procurement key with sourced from other plant. Selection works well but structural explosion picks the material from other plant. Strangely, it also costed/marked/released the material in other plant as well. It is getting a bit messy now. System tries to cost the material in other plant. I have tried using the cross plant transfer structure with 1st strategy as Future std price, 2nd as current standard price and 3rd as no transfer. In case I don't have future and current price in source plant, system cost the material in source plant instead of giving error.

We have multiple plants in a company code and these are pretty much managed separately. It is the reason, we want to segregate the authorizations by plant. Complexity is because of shared materials.

Any suggestions how we can further refine it..?

former_member513101
Active Contributor
0 Kudos

Hi Neeraj,

I suggest you test with CK11N first.

Let say user A authorize to release material X for plant Y and but not authorize to release material X for plant W. So, you only assign the plant authorization object to user A for plant Y only. Then you configure the special procurement key and assign it to material X in plant Y. Ensure material X in plant W have a valid standard price. Test the user A ID for cost calculation CK11N for plant Y and W. Please ensure material X for plant Y getting the cost from plant W by checking the quantity structure tab. check this example ck11n-costing-with-spk.png and the cost is same as plant W. Ensure user A can perform CK11N for plant Y but hit error for plant W.

Then only you test it for CK40N. I believe it should be working fine for CK40N if it is working fine for CK11N.

Thanks

lingaiahvanam
Active Contributor
0 Kudos

Hi,

You can explain the authorization object and transaction code to the security team they will set up a new role based on plant specific.

The role contains the authorization object/value and organization elements like sales organization, costing variant, plant.

1.png

2.png

3.png

Best Regards,

Lingaiah