Question:
We have set op SAP PS for use in two company codes/plants.
We want to set authorizations in such a way that staff in one cc cannot write time on networks in the other cc, but so far have not been able to find a solution for this.
Hope anybody can help here
Answer:
CLicked submit to quickly.
We are using CATS for timewriting, and have 2 separate WBS structures in each CC, with some WBS elements in CC a to a project in CC B.
We want to ensure that people in CC A do not write time on Networks in CC B.
Answer:
Your only choice is to use the user exits. You'll have to make company code and or plant codes a required fields.
Answer:
Robert,
Entering time? , I'm presuming you're referring to CATS and not performing scheduling on the projects. If CATS limitations you're looking for, you would need to explore the use of a CATS user exits. Test carefully here, CATS is tempermental enough and you're potentially impacting a large number of users that would be/could be attempting to charge to a project - support calls are on there way:
Exit to consider:
CATS0006 CATS: Validate entire time sheet
If you're looking at limiting network restrictions within PS functionality,
CNEX0002
EXIT_SAPLCNAU_003 PS Customer Exit Network Header Auth Check
EXIT_SAPLCNAU_004 PS Customer Exit Network Activity Auth Check
These same exits can be called from non-PS transactions, particularly PM, since networks are a form of order (shared by PM, QM, CO ....), so again, know what you're doing and test carefully. Just by activating these exits, and not even adding code, you'll find you've brought the logistics modules to a stand still until you've added at least one line of code to them for SAP_X_ACTVT - returning a value of 'X'.
Regards,
Vincent
Answer:
Hello all,
using a user exit indeed is the way to go.
We are currently testing, and expect that this will meet our requirements.
Thanks for the feedback!
Answer:
Robert,
Which exit did you end up using?
If you can, let the board know how it's working out, issues encountered.
Regards,
Vincent