OAC0 SAP TCode - CMS Customizing Content Repositories

Search SAP Transaction Codes

CMS: Maintain Content Repository SAP screen

What is OAC0 (CMS Customizing Content Repositories) and how is it used? Within an SAP system there are numerous transaction codes (TCode) that each serve different purposes and provide easy access to a variety of different functionality. One such TCode is OAC0, which provides access to CMS Customizing Content Repositories / CMS: Maintain Content Repository SAP screen functionality within R/3 SAP (Or S/4HANA) systems, depending on your version and release level.

Below for your convenience is a few details about this tcode including any standard documentation. In-order to use this transaction within your SAP system simply enter it into the command input box located in the top left hand corner of the SAP GUI, and press enter. You can also add additional command options such /o to trigger in new window..See full list of command options available.

Program Name: SCMS0
Screen Number: 0000

OAC0 Authorisation objects

In-order to be able to use a SAP transaction code you need to have the correct authorisations setup for your user ID. To check if you have the required level of authorisation to run this use tcode SU53 via a new session (i.e. /N). Simply execute OAC0 and then execute /NSU53 immediately afterwards. A report of all authorisations checked will then be displayed...See check tcode authorisation for full details and screenshots of how to check what authorisations you are missing to use a tcode.

SAP GUI Support for tcode OAC0

When a tcode is created you can select which SAP GUI it has support for from HTML, Java and the main Windows GUI you are probably most familiar with.

SAPGUI for HTML
OAC0 includes support for the HTML web based GUI. The SAP GUI for HTML generates HTML pages for each screen of the SAP transaction so that it can be executed within a standard web browser. Please note there are technical restrictions and possible incompatibility issues with certain browsers which means some transaction functionality may not function correctly.

SAPGUI for Java
OAC0 includes support for the Java based GUI. The SAP GUI for Java support provides more controls than the SAP GUI for HTML, but requires a plug-in to be downloaded and installed on the users PC so is less popular than the SAP GUI for HTML.

SAPGUI for windows
OAC0 does not support the Windows based GUI. Windows(WinGUI) support is the most popular option and transactions can be run under SAP GUI for Windows.

SAP Program associated with transaction OAC0

For further details and documentation see program SCMS0

Search for further information about these or an SAP related objects