- SAP Community
- Groups
- Interest Groups
- Application Development
- Discussions
- Use of SE16N discontinued in SCM EWM Ver 7.01
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Use of SE16N discontinued in SCM EWM Ver 7.01
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2009 6:44 PM
Hi there
We have implemented EWM ver 7.01 and I now find that TxCde SE16N is no longer available but SE16 is still there.
Is there a way to re-activate this or is it gone for ever?
Regards
Carl.
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2009 8:45 PM
Ths is long story, but to cut it short...
It was developed as a utility in the SAP_APPL component CO-PA (controlling) but has BC (Basic Components) capabilities and now makes those same checks (S_DEVELOP and S_TABU_DIS primarily) which "normal" endusers should not need...
It is however still located in CO-PA and many corrections are backported to lower releases (it first appeared in 46C) so such a change is not easy for software logistics using the package concept.
This means that an installed system (e.g. BW or EWM etc...) which does not have the SAP_APPL CO-PA component installed does not have the transaction code nor other objects (reports, function modules, etc) related to it.
Perhaps once it is sufficiently secured to be a mainstream transaction (in the wild it certainly is... and is MUCH more usefull than SE16 if you have the "same" and "correct" authorizations...) then SAP can use a major release change to switch the component to BC (Basis).
I sometimes think that it would be best suited in an IS component (Industry Solutions) but then again we would all be digging for oil in our backgardens if that was the requirement..
Hope that makes sense,
Julius
- SAP Managed Tags:
- Security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2009 8:45 PM
Ths is long story, but to cut it short...
It was developed as a utility in the SAP_APPL component CO-PA (controlling) but has BC (Basic Components) capabilities and now makes those same checks (S_DEVELOP and S_TABU_DIS primarily) which "normal" endusers should not need...
It is however still located in CO-PA and many corrections are backported to lower releases (it first appeared in 46C) so such a change is not easy for software logistics using the package concept.
This means that an installed system (e.g. BW or EWM etc...) which does not have the SAP_APPL CO-PA component installed does not have the transaction code nor other objects (reports, function modules, etc) related to it.
Perhaps once it is sufficiently secured to be a mainstream transaction (in the wild it certainly is... and is MUCH more usefull than SE16 if you have the "same" and "correct" authorizations...) then SAP can use a major release change to switch the component to BC (Basis).
I sometimes think that it would be best suited in an IS component (Industry Solutions) but then again we would all be digging for oil in our backgardens if that was the requirement..
Hope that makes sense,
Julius
- SAP Managed Tags:
- Security
