SAP: how to turn customizing transactions into functional transactions

For sure, more than once, you required certain transactions like OB08, OB52, OB58, OBB8, OBB9 and many others to be maintained frequently (also daily in some cases), which implicates many hours of customizing, transports, documentation and so on, to do all this in the Development environment, to test this in the Quality Assurance environment and for being used later in the Production system.

Well, the good news is that you can perform this in a more friendly way.

The whole details can be found in the OSS note 356483. It explains how certain tables or views can be set as “non-transportable” to convert them to functional objects. By doing this the user can maintain these tables directly in the Production system, without the need of using the customizing or transporting the changes.

These changes must be performed by using transaction SE54. Before you execute the SE54 transaction, you need to know which is the object to be modified, since you will need to register this change in the OSS.

The modification to the specific object will be included in a workbench transport order. When you transport this order, the specific table adopts this new characteristic and allows the user to maintain it in the target system directly.

In some cases, depending on the modified table or view, you may also need to change the error messages properties in transaction OBA5.

Please consider that by performing this, by using transaction SE54, and by changing the table content in a specific system, you lose the configuration consistency between the different landscape systems. That′s why it is recommendable to perform the same changes in all the systems (Development, Quality Assurance, Production) at the same time.

I hope this helps you in your daily activities!

Adrian Wilder - Websites: www.infoaval.com – www.sap-ob08.com

Twitter: @adrianwilder