Sap How Run Code Inspector Download The Xpiinspectorx

Overview The XPI Inspector tool was developed by SAP for collecting information about the configuration and traces and to improve the troubleshooting of PI issues.

The SAP note 1514898 - XPI Inspector for troubleshooting XI contains information about the tool and the link to download it.

This wiki contains the steps to install the XPIInspector tool, the types of trace the tool can take, the available examples, the guides for tracing specific issues in PI and the relevant documentation.

Sap How Run Code Inspector Download The Xpiinspectorx

Installing the XPI Inspector tool Download the xpiinspectorx.ear file from the link provided in the SAP note 1514898.

Reference to SAP note 2010715 for deploying the XPIInspector tool.

Open telnet. For this, use putty system or call the command telnet Login as administrator user Insert the following commands: add deploy deploy versionruleall When the tool is correct deployed the following log will appear: Using the XPI Inspector tool The tool can be called at.

Authorization needed A PI user with Administrator access is required in order to run the tool.

If the user used does not have the required authorization, a 403 error will be raised when trying to access it.

Figure 2 Items in the SYCM overview are grouped according to category Figure 3 Each item in the SYCM overview links to a corresponding SAP Note that explains the change You can learn more about which objects will be affected by a change by drilling down into the details of a simplification item from the SYCM overview screen.

As moving to SAP S4HANA increasingly becomes more a question of when rather than if, most SAP customers are looking at how to make this move from an SAP Business Suite implementation centered around SAP ERP, the latest version being enhancement package 8 running on the SAP NetWeaver 7.5 technology stack.

Since SAP S4HANA is a completely new product version with a new data model built on core data services, customers making this transition need to perform a system conversion from SAP Business Suite to SAP S4HANA and migrate to the SAP HANA database if it is not already in use.

In addition, they must adapt any custom code created for SAP Business Suite that is incompatible with SAP S4HANA.

Adapting custom code is never a trivial undertaking for any organization, and to support its customers in this task, SAP delivers analysis tools as a part of SAP NetWeaver that enable you to fully manage this process, including extended syntax checks and the Code Inspector tool.

In the past, these tools were delivered individually as part of the standard SAP NetWeaver shipment.

As of SAP NetWeaver 7.5x, these tools are combined in ABAP Test Cockpit, which enables you to get an overview of the project scope, analyze the adaptation requirements, and perform the adaptions directly in the code with the help of the Eclipse-based ABAP development tools, all from a single tool.

This article shows developers and development project managers how to adapt custom code for SAP S4HANA using ABAP Test Cockpit.

While a previous SAPinsider article covered in detail the process of migrating from SAP Business Suite to SAP S4HANA, this article focuses on the portions of the process that involve adapting custom code for SAP S4HANA, which takes place after the system migration (see the sidebar The SAP S4HANA Migration Process at a Glance for a brief overview of the overall migration process).

You will learn how to create a preliminary overview of potential issues with your custom code that you can use to prepare for your adaptation project, and how to then use ABAP Test Cockpit to identify and resolve incompatibilities between your custom code and the new SAP S4HANA data model, including a look at how to address three commonly identified issues.

Preparation During this first phase, the customer continues operating the traditional SAP Business Suite while undertaking important steps to prepare for the system conversion.

First, you need to get rid of obsolete custom code that has piled up over the years (in many cases, you dont want to move these assets to the new house).

Next, you need to adapt ABAP coding that is not ready for SAP HANA.

In general, ABAP is fully database-independent and portable, but there are cases in which you need to adjust the code (for example, ABAP uses implicit sort order while SAP HANA uses explicit sort order in accordance with the SQL standard).

Experience shows that this step should be carried out carefully before the system migration.

Realization During this second phase, the system conversion to SAP S4HANA has been completed using SAPs lifecycle management tools.

The new SAP S4HANA data model, which is built on core data services, is already in place, and your custom code most likely has dependencies on objects that have been changed or removed in the new model.

As a result, you must adapt your custom code in the SAP S4HANA system.

Creating an Overview with Transaction SYCM Once the technical migration is complete, it is a good idea to get an overview of the impact SAP S4HANA will have on your custom code before you begin the adaptation project, so that you can plan for the adaption effort that will be required.

Transaction SYCM, which is included with SAP NetWeaver 7.5x, can provide this overview.

The SYCM overview screen shows how your custom code objects relate to the items in the Simplification Database, which contains documentation on the SAP data objects that have been changed or removed for SAP S4HANA.

You can view the full contents of the Simplification Database in the SYCM overview screen (see Figure 1 ) or you can refine the results using a selection screen.

Figure 1 The SYCM overview screen displays the contents of the Simplification Database Items in the Simplification Database are grouped into different categories, such as Functionality not available or Syntactically incompatible change of existing functionality.

In the latter category (see Figure 2 ), you will find the most well-known data element change in the SAP S4HANA data model: The length of the material number field has been extended from 18 characters in SAP Business Suite to 40 characters in SAP S4HANA.

Each simplification item is documented in a corresponding SAP Note, which explains the change and its impact for example, the item for the material number field change links to SAP Note 2215424, which includes all the general information for the extension of the material number field from 18 to 40 characters (see Figure 3 ).