Locate Log Switch Interval on Day/Hourly Basis

–List Timing for Log Switch on different clustered instances with thread details

SET LINESIZE 150
COLUMN TIMESTAMP FORMAT A30
COLUMN THREAD_ID FORMAT 999
COLUMN INSTANCE_ID FORMAT 999
SELECT  to_char(first_time,’DD-MON-YYYY HH24:MI’) TIMESTAMP,thread# THREAD_ID,inst_id INSTANCE_ID
FROM    GV$log_history
where INST_ID=&&INST_ID and trunc(first_time) =trunc(sysdate)
ORDER BY 1 desc;

– Will return a graph indicating log switches done on daily/hourly basis

SET LINESIZE 150
COLUMN DAY FORMAT A3
COLUMN Total FORMAT 99G990
COLUMN h00 FORMAT 999
COLUMN h01 FORMAT 999
COLUMN h02 FORMAT 999
COLUMN h03 FORMAT 999
COLUMN h04 FORMAT 999
COLUMN h05 FORMAT 999
COLUMN h06 FORMAT 999
COLUMN h07 FORMAT 999
COLUMN h08 FORMAT 999
COLUMN h09 FORMAT 999
COLUMN h10 FORMAT 999
COLUMN h11 FORMAT 999
COLUMN h12 FORMAT 999
COLUMN h13 FORMAT 999
COLUMN h14 FORMAT 999
COLUMN h15 FORMAT 999
COLUMN h16 FORMAT 999
COLUMN h17 FORMAT 999
COLUMN h18 FORMAT 999
COLUMN h19 FORMAT 999
COLUMN h20 FORMAT 999
COLUMN h21 FORMAT 999
COLUMN h22 FORMAT 999
COLUMN h23 FORMAT 999
COLUMN h24 FORMAT 999
BREAK ON REPORT
COMPUTE MAX OF “Total” ON REPORT
COMPUTE MAX OF “h00″ ON REPORT
COMPUTE MAX OF “h01″ ON REPORT
COMPUTE MAX OF “h02″ ON REPORT
COMPUTE MAX OF “h03″ ON REPORT
COMPUTE MAX OF “h04″ ON REPORT
COMPUTE MAX OF “h05″ ON REPORT
COMPUTE MAX OF “h06″ ON REPORT
COMPUTE MAX OF “h07″ ON REPORT
COMPUTE MAX OF “h08″ ON REPORT
COMPUTE MAX OF “h09″ ON REPORT
COMPUTE MAX OF “h10″ ON REPORT
COMPUTE MAX OF “h11″ ON REPORT
COMPUTE MAX OF “h12″ ON REPORT
COMPUTE MAX OF “h13″ ON REPORT
COMPUTE MAX OF “h14″ ON REPORT
COMPUTE MAX OF “h15″ ON REPORT
COMPUTE MAX OF “h16″ ON REPORT
COMPUTE MAX OF “h17″ ON REPORT
COMPUTE MAX OF “h18″ ON REPORT
COMPUTE MAX OF “h19″ ON REPORT
COMPUTE MAX OF “h20″ ON REPORT
COMPUTE MAX OF “h21″ ON REPORT
COMPUTE MAX OF “h22″ ON REPORT
COMPUTE MAX OF “h23″ ON REPORT

SELECT TRUNC(first_time) AS “Date”,
TO_CHAR(first_time, ‘Dy’) AS “Day”,
COUNT(1) AS “Total”,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’00′,1,0)) AS “h00″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’01′,1,0)) AS “h01″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’02′,1,0)) AS “h02″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’03′,1,0)) AS “h03″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’04′,1,0)) AS “h04″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’05′,1,0)) AS “h05″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’06′,1,0)) AS “h06″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’07′,1,0)) AS “h07″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’08′,1,0)) AS “h08″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’09′,1,0)) AS “h09″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’10′,1,0)) AS “h10″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’11′,1,0)) AS “h11″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’12′,1,0)) AS “h12″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’13′,1,0)) AS “h13″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’14′,1,0)) AS “h14″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’15′,1,0)) AS “h15″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’16′,1,0)) AS “h16″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’17′,1,0)) AS “h17″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’18′,1,0)) AS “h18″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’19′,1,0)) AS “h19″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’20′,1,0)) AS “h20″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’21′,1,0)) AS “h21″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’22′,1,0)) AS “h22″,
SUM(DECODE(TO_CHAR(first_time, ‘HH24′),’23′,1,0)) AS “h23″
FROM V$log_history
GROUP BY TRUNC(first_time), TO_CHAR(first_time, ‘Dy’)
ORDER BY 1;
CLEAR BREAKS;

How to reset SPAM/SAINT queue

Reset SAINT queue / reset SPAM queue / reset OCS queue

Find below steps to Reset the OCS queue while applying add on / support packs.

While applying add on or support packs, if process hang up in IMPORT_PROPER phase of DDIC activation phase etc and if you are not able to re import or reset the queue, please follow below procedure.

At command line on prompt

Run below command

tp r3i all pf=/usr/sap/trans/bin/TP_DOMAIN_.PFL tag=spam -Dclientcascade=yes -Drepeatonerror=8

After this it will again come on your prompt.

Then go in se37 run below program

ocs_reset_queue

Hit F8

Give following parameter

IV_TOOL = SPAM / SAINT

IV_FORCE = X

Hit execute.

Now run SPAM or SAINT and redefine your queue

OS Unix locations of the device files on the respective systems

All you have to do is remember the locations of the device files on the respective systems. The following tables will help you do that for the most commonly used devices.

AIX File System Device Files

Block	Character
/dev/hd1	/dev/rhd1
/dev/hd2	/dev/rhd2
/dev/hd3	/dev/rhd3
/dev/hd*	/dev/hd*

HP-UX File System Device Files

Block	Character
/dev/dsk/c201d0s0	/dev/rdsk/c201d0s0
/dev/dsk/c201d1s0	/dev/rdsk/c201d1s0
/dev/dsk/c201d2s0	/dev/rdsk/c201d2s0
/dev/dsk/c201d*s0	/dev/rdsk/c201d*s0

AIX Tape Drive Device Files

File	Meaning
/dev/rmt*	Rewind on close, no retension on open, high density
/dev/rmt*.1	No rewind on close, no retension on open, high density
/dev/rmt*.2	Rewind on close, retension on open, high density
/dev/rmt*.3	No rewind on close, retension on open, high density
/dev/rmt*.4	Rewind on close, no retension on open, low density
/dev/rmt*.5	No rewind on close, no retension on open, low density
/dev/rmt*.6	Rewind on close, retension on open, low density
/dev/rmt*.7	No rewind on close, retension on open, low density

HP-UX Tape Drive Device Files

File	Meaning
/dev/rmt/c201d*c	Rewind on close, compress data
/dev/rmt/c201d*cb	Rewind on close, compress data, Berkeley style
/dev/rmt/c201d*cn	No rewind on close, compress data
/dev/rmt/c201d*cnb	No rewind on close, compress data, Berkeley style
/dev/rmt/c201d*h	Rewind on close, high density
/dev/rmt/c201d*hb	Rewind on close, high density, Berkeley style
/dev/rmt/c201d*hn	No rewind on close, high density
/dev/rmt/c201d*hnb	No rewind on close, high density, Berkeley style
/dev/rmt/c201d*l	Rewind on close, low density
/dev/rmt/c201d*lb	Rewind on close, low density, Berkeley style
/dev/rmt/c201d*ln	No rewind on close, low density
/dev/rmt/c201d*lnb	No rewind on close, low density, Berkeley style
/dev/rmt/c201d*m	Rewind on close, medium density
/dev/rmt/c201d*mb	Rewind on close, medium density, Berkeley style
/dev/rmt/c201d*mn	No rewind on close, medium density
/dev/rmt/c201d*mnb	No rewind on close, low density, Berkeley style

Note: High density is 6250 bpi, medium is 1600 bpi, and low is 800 bpi. For AT&T-style devices the tape is positioned after the EOF following the data just read. For Berkeley-style devices, the tape is not repositioned in any way.

AIX Floppy Drive Device Files

Block	Character
/dev/fd0	/dev/rfd0

HP-UX Floppy Drive Device Files

Block	Character
/dev/floppy/c201d0s0	/dev/rfloppy/c201d0s0

Howto Install SAPlpd Print server (Can be apply for SAPSprint)

Prerequire

-          NT resouce kit (ntreskit) 

INSTSRV.EXE,and SRVANY.EXE

-          Create New SAPlpd.reg Regedit for SAPLpd  and modify content (below information)

Step

1.      Login Local Administrator and install saplpd on Print server

2.      Copy folder ntreskit to c:\Program Files\

3.      Run DOS prompt and change to c:\Program Files\ntreskit .

4.      Run command :
instsrv.exe SAPlpd “c:\Program Files\ntreskit\srvany.exe“

5.      Check values in SAPlpd.reg for saplpd installation path

Value-Name                     String:
Application                     C:\Program Files\SAP\FrontEnd\SAPgui\SAPlpd\SAPlpd.exe
AppDirectory                  C:\Program Files\SAP\FrontEnd\SAPgui\SAPlpd
AppParameters              -d

6.      Double click  SAPlpd.reg to add in regedit

Check

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services
-> SAPlpd ->

    ObjectName -> value LocalSystem

-> SAPlpd ->

    -> ObjectName -> value ImagePath

And

-> SAPlpd ->Parameters

  -> ObjectName -> value ImagePath

7.      Open services on windows and start service SAPLPD and verify automatic start(and click start)

8.      Check port 515 Run command :

netstat -an|more

Active Connections

  Proto  Local Address          Foreign Address        State

  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING

  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING

  TCP    0.0.0.0:515            0.0.0.0:0              LISTENING

-----------------------

SAPlpd.reg content

------------------------

REGEDIT4

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAPlpd]

"Type"=dword:00000010

"Start"=dword:00000002

"ErrorControl"=dword:00000001

"ImagePath"=hex(2):63,3a,5c,50,72,6f,67,72,61,7e,31,5c,6e,74,72,65,73,6b,69,74,\

  5c,73,72,76,61,6e,79,2e,65,78,65,00

"DisplayName"="SAPlpd"

"ObjectName"="LocalSystem"

C:\Program Files\SAP\FrontEnd\SAPgui\SAPlpd

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAPlpd\Parameters]

"Application"="C:\\Program Files\\SAP\\FrontEnd\\Sapgui\\SAPlpd\\SAPlpd.exe"

"AppDirectory"="C:\\Program Files\\SAP\\FrontEnd\\Sapgui\\SAPlpd"

"AppParameters"="-d"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAPlpd\Security]

"Security"=hex:01,00,14,80,c0,00,00,00,cc,00,00,00,14,00,00,00,34,00,00,00,02,\

  00,20,00,01,00,00,00,02,80,18,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\

  00,00,20,02,00,00,02,00,8c,00,05,00,00,00,00,00,18,00,8d,01,02,00,01,01,00,\

  00,00,00,00,01,00,00,00,00,74,00,73,00,00,00,1c,00,fd,01,02,00,01,02,00,00,\

  00,00,00,05,20,00,00,00,23,02,00,00,76,00,63,00,00,00,1c,00,ff,01,0f,00,01,\

  02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,76,00,63,00,00,00,1c,00,ff,01,\

  0f,00,01,02,00,00,00,00,00,05,20,00,00,00,25,02,00,00,76,00,63,00,00,00,18,\

  00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,25,02,00,00,01,01,00,00,\

  00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAPlpd\Enum]

"0"="Root\\LEGACY_SAPLPD\\0000"

"Count"=dword:00000001

"NextInstance"=dword:00000001

SCSI Evolution

SCSI Evolution

Common Name(s)	Maximum Speed (MB/second)	Signaling	Maximum Devices	Cable Lengths
SCSI-1	5	single-ended	7	up to 6m
SCSI-2 Fast SCSI	10	single-ended, high-voltage differential	7 15	up to 6m single-ended up to 25m differential
SCSI-3 Fast & Wide SCSI	20	single-ended, high-voltage differential	7 15	up to 6m single-ended up to 25m differential
Ultra SCSI	40	single-ended, high-voltage differential	7 15	up to 6m single-ended up to 25m differential
Ultra2 SCSI	80	low-voltage differential	15	up to 25m point-to-point up to 12m for multiple devices
Ultra3 SCSI or Ultra160 SCSI	160	low-voltage differential	15	up to 25m point-to-point up to 12m for multiple devices
Ultra320 SCSI	320	low-voltage differential	15	up to 25m point-to-point up to 12m for multiple devices

Download : Step by step to install EHP 4 on SAP ERP 6

Here are simple and step by step document on installing EHP 4 for SAP ERP 6.0.

You can download it here (http://www.ziddu.com/download/15658960/HowtoInstallSAPEnhancementPackage4forSAPERP6.pdf.html).

Clean Up Transport Directory

Q: We are out of space on /usr/sap/trans directory. I do not know what to do. I’ve been deleted all transported list from STMS, but the file system still full.

Answer:

Hi, you should do transport directory clean-up from file system, at least once a month.

To do that, please follow this:

1. Go to operating system and logon using user adm

2. Run: cd /usr/sap/trans/bin

3. Run: tp check all pf=TP_DOMAIN_.PFL

4. Run: tp clearold all pf=TP_DOMAIN_.PFL

This will move more than 6 months file from /usr/sap/trans/data to /usr/sap/trans/olddata

and also will delete more than 1 year ../cofiles and ../logs

OS DB Migration Key- SAP Netweaver 7

Q: I am migrating SAP Netweaver 2004s SP9 from Solaris – Oracle to Windows – MSSQL 2005.

While I request Migration Key from Service Marketplace, it gave me error that said the Migration Key is invalid. The migration key is generated by SAP.

Answer:

Hi, you may refer to SAP Note 970518.

The source license is already use new License type, which is Digital-Sign License (The generated license key, longer that the previouse version.

You may use this General Migration key:

1G5fdEM50TMIrBzjt6TE5Pae

, which valid until end of 2008.

Forgot SAP* Password

Q1: Please help me. I would like to update Support Package from Client 000, but I forgot all the password (DDIC and SAP*). How can I logon?

Q2: My temporary license Expired! I need to install new license, but all user can’t login except SAP*, but I forgot SAP* Password.

Answer:

To reset SAP* password, please follow this step:

1. Set the profile parameter login/no_automatic_user_sapstar to 0 from RZ10 (If you can’t logon, you can edit your Instance Profile directly from the OS level, folder /usr/sap//SYS/profile, )

2. Restart Application Server.

3. Logon to your SQL command (eq: SQL PLUS for Oracle) and connect as SYSDBA.

4. Run: SELECT * FROM [DBSID].USR02 WHERE BNAME=’SAP*’ AND MANDT=’’

Example: SELECT * FROM PRD.USR02 WHERE BNAME=’SAP*’ AND MANDT=’000′

5. If exist, then run:

DELETE FROM PRD.USR02 WHERE BNAME=’SAP*’ AND MANDT=’000′

Make sure the user deleted by re-run step 4.

6. Logon to Client 000 with user SAP* and password: pass

Understanding the clients 000, 001 and 066

Clients 000, 001 and 066 are standard clients that are pre-delivered by SAP. These clients are not supposed to be used in development, quality and production environments.

Client 000 is basically used as working client only when you do support pack upgrade or ABAP load generations (SGEN) and implementing additional languages, etc. Otherwise, client 000 should not be used as a working client. The same applies to client 001. But the only exception with 001 is, with Solution Manager, 001 will be your working client. You will do all configurations and obtain support from SAP through this client. With other Systems like BW and CRM, this client (001) will not be a working client. Two standard users (SAP* and DDIC) are defined in the clients 000 and 001.

The client 066 is used only for EarlyWatch functions (Monitoring and Performance). The user EarlyWatch is delivered in client 066 and is protected using the password SUPPORT. This password needs to be changed for security purposes.

Understanding Background Job Processing

In background processing, the SAP System automatically runs any report or program in the specified time or time intervals. The background processing system starts your job and runs the program(s) that you specify. Afterwards, you can check whether your job was executed successfully and display a log of any system messages.

Features:

• Running a report in the background does not tie up the SAP sessions you are currently working with.
• You can shift the execution of reports to the evening or other periods depending on load on the SAP System.
• Background processing is the only way you can execute long-running jobs.

Background jobs run in a special type of work process—the background work process—that is different from dialog work processes in two ways:

• A dialog step has a run-time limit that prevents users from interactively running especially long reports. By default, the system terminates any dialog step in a transaction that exceeds 300 seconds. Although the limit can be changed (in the system profile parameter rdisp/max_wprun_time ), it is always in effect for dialog work processes. No such limit applies to background work processes.
• Background work processes allocate memory differently than dialog work processes so that background work processes can become as large as they need to in allocated memory to allow for processing large volumes of data.

Tips on Patch Installation

Patches shouldn't be directly applied on the production system (PRD). We first need to apply it on the development (DEV) system and test the same.

Whenever there are patches available for installation, Please make sure that:

• Whenever you are applying ABAP and BASIS patches, it is recommended to have one version less than the latest.
• After you apply these patches, plan for your kernel upgrade which will work better in sync with the new BASIS and ABAP patches.
• Also, need to check for any SAPGUI patch available, otherwise dumps might error.
• ABAP+BASIS+Kernel+SAPGUI should be planned together and to be implemented together.

When applying Application Patches, we need to be very careful. This might affect the total functionality and your business process may get affected. Specially when you have modified many SAP objects to suit your business.

How to Verify whether a system is Unicode or non-Unicode

We can verify whether a system is Unicode or non-Unicode by using the command JCMON . This provides you with the version information similar to the following:

E:\usr\sap\EP7\JC01\exe>jcmon

--------------------
jcmon information
--------------------
kernel release 700
kernel make variant 700_REL
DBMS client library
compiled on NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10
compilation mode UNICODE
compile time Nov 21 2005 20:42:48
update level 0
patch number 0
source id 0.033
---------------------
supported environment
---------------------
database (SAP, table SVERS) 700

operating system
Windows NT 5.0
Windows NT 5.1
Windows NT 5.2

BAPI to change the User's password

The BAPI "BAPI_USER_CHANGE" could be used to change the User's password. Please check the sample code below:
              CALL FUNCTION 'BAPI_USER_CHANGE'
                EXPORTING
                  username   = userid
                  password   = new_password
                  passwordx  = 'X'.

How to Restrict the user sessions to 3 or any other number

By default, the number of sessions for a user is set to 6. To change this, do the following:

• Go to Profile Maintenance by choosing Tools --> CCMS --> Configuration  --> Profile Maintenance or the transaction RZ11.
• Maintain the parameter rdisp/max_alt_modes . Enter the number of sessions you want to restrict your users.

How to Transport Table entries from one server to another

Scenario:  In this scenario, we would try to transport the table entries of table SCARR.

 

Go to transaction SE10. Click on Create.  

 

Following pop-up appears. Select Workbench request. (If the table is customizing table, then select customizing request)

 

Provide a short description to the request.

 

The request is displayed as shown below

 

Now double-click on the request, 

 

Go to change mode, and enter the following details:

 

Now click on the key button available under the name “Function” (As shown in the screenshot above). Following screen appears. Double-click on the first empty line. 

 

Here we can provide the entries that we would need to transport. For our demo purpose, we are transporting all the entries in SCARR belonging to client 800. 

 

Press Enter. Screen would look as follows:

 

Now you can check for the entries that would be transported as per the given condition, by clicking on the table button highlighted in the screenshot above. 

Select the third radio button “Table contents specified by current key”. 

 

Following entries would appear:

 

Click on Save. A warning message would appear. 

 

SAP issues a warning message when an application table is used. Following is the SAP help that would appear when we click on the message:

Ignore the warning message and click on Save. The request would appear as follows: 

 

Now transport this request to transport the data to any other system.

How to detect whether a system is of Production/Test/Development client programmatically?

In this tip, we would look into the procedure for determining whether the system is of Production/Test/Development client programmatically. 

Go to transaction SE11. 

Enter the table name T000 (Clients). 

 

The field CCCATEGORY determines the category of the client. Following are the various possible values of the same: 

How to get password downward compatibility

Scenario: An SAP system has been upgraded from 4.6C to ECC6.0. But in ECC 6.0, the password can consist of 40 characters. For some reasons, this has to be restricted to 8 characters (same as old release). 

Solution: In this case, the password has to be enabled for backward compatibility. To achieve this, do the following: 

Go to transaction RZ11. 

Enter the parameter "login/password_downwards_compatibility". 

 

Click on Display:

 

By default, the parameter is set to 1. 

Click on the documentation to get the possible values of the parameters:

 

Now click on "Change Value" 

 

Change the parameter value from 1 to 5 for backward compatibility:

How to get HARDWARE KEY for SAP License in Solaris / UNIX /Windows)

Introduction: Hardware key is required for getting a license from SAP Service Market Place.  

Steps:  

For Solaris/ UNIX/ Windows  

1. Login to the server with SIDADM user
2. Use command: saplicense –get

SAP R3 (Idocs) To XI -- Steps Summarized

A SUMMARY OF THE STEPS TO BE CARRIED OUT TO ENABLE A SAP R/3 SYSTEM SEND IDOCS TO SAP EXCHANGE INFRASTRUCTURE.

---

First - Maintain the Sender R/3 System:

• SM59 : Create a RFC destination to XI
• WE21 : Create a TRFC Port ->Specify the RFC Destination Created
• BD54 : Create a Logical System for the Idoc Receiver
• WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters

Second - Log on to XI System:

• SM59 : RFC Destination for Sender System
• IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP. eg. SAPID1 [Optional Step. Not mandatory]
• IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.

To Enable Acknowledgement:

• SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
  • Category: RUNTIME
  • Parameters: ACK_SYSTEM_FAILURE
  • Current Value: 1

GO TO SLD:

• Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System

• Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
  • Business System Role: Application System
  • Related Integration Server: Integration Server

Idoc Tunneling in XI

To prevent performance consuming XMLization and de-XMLization IDOCs are tunneled through SAP XI IDOC adapter meaning no XMLiziation is executed before the IDOC is passed onto the pipeline. Note the message is converted to UTF-8 codepage.

Start transaction SXMB_ADMIN on SAP XI.

Select option Configuration->Integration Engine Configuration and add two parameter EXTERNAL_MAPPER in the category IDOC.

Configure the parameter according to the conditions below:

If Message Code and Message Function are specified in the partner profile:
..ReceiverPort...

If only the Message Code is specified in the partner profile:
..ReceiverPort..

If only Message Function is specified in the partner profile:
..ReceiverPort...

Integration Builder

 Integration Directory:

•  Add Business System:  Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System  
•  IDoc Receiver Communication Channel: port the same as XI System IDX1