Wednesday, December 15, 2010

Setting up the ITS in SAP ERP and in SAP CRM

ITS stands for Internet Transaction Server, and was incorporated in SAP Netweaver as of version 04 Before that time, the ITS was a service that ran outside of SAP.

The ITS renders the SAPGUI screens online into a browser-supported format. This means that any changes that have been made in the SAPGUI screen will automatically also be available via the ITS.

The ITS is a plug-and-play service, which enables you to call your SAPGUI transactions in the webclient without building them in a web-page. This can be a very well affordable solution if you have created for instance a maintenance view or SAP query that you need to have available in the CRM Webclient. Of course it is also very usefull if you want ERP data to be visible or even maintainable for SAP CRM users without the big costs of rebuilding the functionality in BSP applications.

The downside of the tool is that the screens in the browser will not 'remember' the last entered values like the SAPGUI does, and because the screens are rendered real-time, the performance of the screens will not meet up to the performance of the SAP Webclient screens or the SAPGUI itself.

If you want to enable the ITS, you have to enable the following services in SICF of the system where you want to use the ITS.
default_host > sap > bc > gui > sap > its.

If you want to call screens from SAP CRM using the ITS, you will also need to set up the ABAP connection between the systems in SM59, maintain the logical system in BD54, map the logical system to the ABAP connection in BD97, and maintain the ITS URL in transaction CRMS_IC_CROSS_SYS.

When setting up the above, make sure the settings meet up to the following:
  • The logical system must have the same name as the ABAP connection. You won't notice during customizing, but the connection will not work if you don't.
  • Make sure the ABAP connection is one where the user logs on with the own username. This will prevent anonymous changes in the system.
  • Make sure the ABAP connection is a trusted connection. This will prevent that the user has to log on every time he calls the transaction.
  • The URL should be as follows (Note that in ERP the transaction to be called is LTXE, while in CRM it is LTX.
  • Implement logon tickets in SSO 1 and exchange server certificates in transaction SSO1 to prevent that the user has to log on when calling the ERP system.
In CRMS_IC_CROSS_SYS, enter the following, where you should change the values between the <> to the values of your system.

If you don't know the port that is used for HTTP traffic, check transaction SMICM, in the menu choose GOTO --> Services (SHIFT-F11). Note the portnumber in the HTTP value.

When calling a BOR method from SAP CRM using the ITS, the system actually calls a transaction (LTX or LTXE) in the system, which on his turn calls the BOR-method with the parameters that you have specified.