Adding critical objects to the transport check tool

The transport check tool is a very good SAP delivered tool to check sequences in SAP transports. It also has a feature on the import timing.

The option for online import criticality check is not always understood. The power of this option will be explained in this blog.

Questions that will be answered in this blog are:

  • How can I check for critical objects in my transport?
  • How can I filter on the settings per system?

Critical object definition

A critical object is content in your transport that you consider as import for live operations. Examples of critical objects:

  • Indexes (upon import of index of huge table, your system will be very slow or halted)
  • Customer extends of tables (upon import the ABAP code will recompile and all current user sessions using that table will terminate with a short dump)
  • Critical user exits like SAP MV45AFZZ
  • Any other object you think basis team should validate before importing to productive system

Critical object check implementation in target system

In the target system for import (normally user acceptance system and productive system), you have to maintain table /SDF/OI_CRITOBJ in SM30 with the transport objects:

This is the implementation for the 3 checks mentioned above. Notice the use of the * wildcard.

You can take the values from a transport in the SE10 transaction.

This table you need to fill per target system. This enables you also differentiate per system. For your ECC productive system the values can differ from the BI productive system, etc.

Also make sure that the Solution manager user in the managed system has sufficient rights to remotely read this data. See OSS note 2257213 – Authorizations for RFC users for SAP Solution Manager 7.2 SP02 and higher.

Running the critical object check

When you run the transport check tool transaction /SDF/TRCHECK select the option for Online Import Criticality:

This will now start the analysis. If a critical object is found it will show like this:

Double click on the line will give the details:

In this case it reports on a table extend to EKPO table and it shows that EKPO is read intensively.

This should warn you not to import this with many users in the system, but on a quiet time or even when all users locked out of the system.

Transport set up for FIORI in app extensibility

In the previous blog we explained how to execute in app extensibility for an out-of-the-box FIORI app. This blog will explain how to transport the changes done.

Questions that will be answered in this blog are:

  • What setup do I need to do for transporting the in app flexibility content?
  • How to activate the needed apps for transporting in app flexibility content?
  • How to use the needed apps for transporting in app flexibility content?

Initial setup

To set up the transport mechanism for in app extensibility start transaction S_ATO_SETUP:

These are packages used to only store the data for the key user.

For the final transport, create in SE80 once a final package, for example ZKUFLEX:

Background explanation on this transaction is present in OSS note 2807979 – Information to setup Adaptation Transport Organizer for S/4HANA On Premise system via S_ATO_SETUP.

FIORI apps activation for transports of key user flexibility content


Activate the FIORI app Configure Configure Software Packages. Full instructions are available on the FIORI reference library.
Short summary:

  • Activate SICF services: NW_APS_ATO_CONF, NW_APS_ATO_LIB and NW_APS_LIB
  • Activate ODATA service: APS_EXT_ATO_PK_CFG_SRV
  • Acitvate PFCG roleSAP_NW_APS_EXT_ATO_PK_CFG_APP and assign to your user

Activate the FIORI app Register Extensions for transport. Full instructions are available on the FIORI reference library.
Short summary:

  • Activate SICF services: NW_APS_ATO_REGI, NW_APS_ATO_LIB and NW_APS_LIB
  • Activate ODATA service: APS_EXT_ATO_PK_AI_SRV
  • Activate PFCG role SAP_NW_APS_EXT_ATO_PK_AI_APP and assign to your user

Use of FIORI apps for transports of key user flexibility content

Add the apps to on the FIORI launchpad:

In the app Configure Software Packages add your permanent package you created in SE80:

Also assign a transport request here.

Now you can use the Register Extensions for Transport app to assign you extension to the package and transport:

Select the field and press the button Reassign to Package.

SAP references

Excellent overview blog can be found here.

SAP full help reference can be found here.

Bug fix OSS notes

3282241 – Enhancement of consistency check in S_ATO_SETUP