on 10-11-2011 3:37 PM
Hi,
When implementing authorisations for APO standard transactions have found, analyzing by trace, an inconsistency in authority checks for Transportation Lanes transaction: /SAPAPO/SCC_TL1.
Aparently when selecting origin location and target location at selectin screen, the program checks:
C_APO_LOC
ACTVT - 16
APO_LOC - (location origin)
C_APO_LOC
ACTVT - 16
APO_LOC - (location target)
C_APO_MOD
ACTVT - 02, 03 (depending on the action to perform regardless the location)
whereas the transaction itself drags -and should check within the code- the object:
C_APO_TLAN
APO_LOCFR - (location origin)
APO_LOCTO - (location target)
ACTVT - (action to perform: display, change, etc ...)
The problem here comes when the activity to perform should be restricted accordingly to the locations selected: when just change activities should be allowed for some specific locations and display mode for another ones.
I will appreciate any help or workaround for this issue or anything that I might have missed in my analysis.
Many thanks.
Edited by: Natalia García Santos on Oct 11, 2011 4:38 PM
This message was moderated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Natalia,
please try BAdI /SAPAPO/MD_CHK_AUTH. Best regards/Tiemin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
4 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.