What happened to tcode OMGS in rel 4.7?

Question:
Hi,
Purchase order release procedure tcode OMGS no longer exists in rel 4.7. Does anybody know which tcode has replaced it? We want to be able to give display access to this function in production, without giving the user SPRO.
The IMG path in SPRO is:
Materials Management > Purchasing > Purchase Order > Release Procedure for Purchase Orders > Define Release Procedure for Purchase Orders.
I have searched the TSTC table and performed a trace, but no luck.
Thanks,
Dorsal.
Answer:
Hello Dorsal,
That's funny, I'm working on an upgrade to 4.7.2 and just asked the very same question today. I'll let you know if I get the answer. Several configuration tcodes are now obsolete in 4.7 (we were on 4.6b): OMGS
OMGQ, OMF6, TEFK, TEAK, TEKK, TEBP. I'm sure there are lots more!!
Answer:
Hi,
There is not any replacement of such transaction code in Enterprise version. Basically, many transaction codes such as OMGS, OMEB, OMEC etc... are no longer 'recognized' by 4.7 version despite of the fact that the path is similar to that of 4.6C.
Cheers,
HT
_________________
Moderator:

Answer:
I found foullowing statement in OSS 642828 note:
In general, we expect the customer to have to adapt less code than in the past and we do not expect the end user to have to remember lots of view (cluster) names (if the IMG path is used, the end user does not have to remember the names of views, view clusters, or transaction codes).
The difference between handling in R3E and the old handling is that now the view name is important and not the transaction code. If you know the name of the view or view cluster, use transaction code SM30/SM34 directly and enter the object name (or use the IMG path).
But this OSS note is for IS OIL, I have not seen one for standard R3 till now. If anybody knows one, s/he may post it here.

More Articles:

No FI doc for special stock "E"(Sale order stock)?
need help?
No multiple selection for material number in MMBE?
Very Urgent(Problem When i am posting the good receipts)?
Repair Process?
Warehouse Management issue?