SAP Note 17520 - ISHCM Receiver data is shifted in the batch session

Symptom:

Data is not processed correctly for data transfer with the SAP R/3 Communications Module (also known by the name HCM Transceiver). The created batch input sessions hold the data somewhat shifted. It would appear that some offset is incorrect. The original file (transfer file) contains the correct data in the correct format.

The receiver program (RNCGET00, RNCGET01, RNCGET02, ...) may work through the transfer file despite this. However, you may then find no receiver logs appear in the corresponding log file NCI0. The program does not recognize the error.

Cause and prerequisites

There are several possibilities:

1. The data is not actually correct: check whether the correct message format has been stored for the partner in IS-H, and whether the data corresponds exactly to this format.

2. The ISHCM rule of thumb "one message equals one file line" is not taken into account in the file. The only exception to this rule: if the line is longer than 4096 (4K) characters, it is terminated after this number of characters.

3. An incorrect line end in the transfer file (hexadecimal '0d' + '0a' mandatory).

Solution

1. Check whether the correct message format is stored for this partner in IS-H, and whether the data corresponds exactly to this format. Correct if necessary.

2. Check whether several messages are in one line, or whether one message is divided over several lines. This is only allowed if the message contains more than 4096 (4K) characters. In this case, the line end must be inserted after exactly 4096 characters (hexadecimal '0d' + '0a'; see 3).

3. Check whether every line in the transfer file is correctly ended with the hex codes '0d' and '0a' (also known as CR and LF). In UNIX there is a simple aid for this: the command 'od':
od -xc
(possibly link with 'more' or 'pg'). The file is displayed character by character, both as characters (c) and as hexadecimal codes (x).
You can analyse some of these points using program RNCCHK02. The results of this analysis can possibly play a decisive role in detecting the type and location of the error.

Additional key words

HCM, incoming, data transfer, transceiver, RNCGET*, data record, offset, consultation