- SAP Community
- Groups
- Interest Groups
- Application Development
- Discussions
- Regarding calling transaction codes
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Regarding calling transaction codes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2009 6:13 AM
Hi,
Users are trying to access MM02 transaction, when they are using this transaction some where it is calling CS13 transaction,(summarized BOM). Where users are telling they dont want this CS13 to be called, as it is a critical transaction.
Could you guide me to fix this.
Thanks!
Edited by: Julius Bussche on Dec 3, 2009 7:30 AM
CAPS-LOCK removed to stop the shouting...
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2009 6:32 AM
What you are looking for is in the FAQ sticky thread at the top of the forum page --> Functional description of transaction SE97.
Cheers,
Julius
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2009 6:25 AM
>
Where users are telling they dont want this CS13 to be called, as it is a critical transaction.
If a user wont have access to CS13 than he wont be able to execute it, CS13 would be called only if it is programmed to be called. There can be 2 possibilities first it may be a standard feature or programmed in one of your user exits. You will have to just debug and see where it is being called from.
Regards,
Chinmaya
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2009 6:32 AM
What you are looking for is in the FAQ sticky thread at the top of the forum page --> Functional description of transaction SE97.
Cheers,
Julius
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2009 6:45 AM
Very intresting note, it seems I did have a few mis-conceptions about this one..
Pavithra please refer to the note mentioned by Julius and ignore my earlier post.
Regards,
Chinmaya
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2009 6:45 AM
Hi,
Many thanks for the response. But could you please tell me where the funcatinol description of SE97 is been updated?Iam searching it ,pls help me to find it.
Thanks!
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2009 6:48 AM
Its right there in the FAQ section of this forum!
Note 358122 - Function description of transaction SE97 - Coupled "CALL TRANSACTION" pairs and restrictions.
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2009 7:35 AM
Hi,
Thanks for this... I want a list of critical transactions , sensitive transactions & critical authorization objects of ABAP Team,as i need to work on SOD.
So please guide me on this.
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2009 7:49 AM
The most exhaustive way would be to get a list of all the transaction assigned to your ABAP team. and than check all the objects assigned to those objects. SOD's are generally compnay specific so something that may work for me may not work for someone else. Its best to do this from scratch so that you are sure you have covered everything that is in use by your team.
Best Wishes,
Chinmaya
- SAP Managed Tags:
- Security
