Posted: Thu Apr 20, 2006 8:49 am Post subject: Is it really mandatory to use encoding field within SAPH ?
Newbie
Joined: 20 Apr 2006 Posts: 1
This week I started to see the following error messages in a test system
(CSD03 was applied a month ago).
04/17/06 08:20:39 SMQ4197: EDI: Field SEGNAM in data record is default
EXPLANATION: The above text details an error that occurred in a SAP R3 Rfc function.
ACTION: None.
-----------------------------------------------------------------------------------------------------------------------
04/17/06 08:20:39 SMQ4187: The attempt to put the message into SAP failed.
EXPLANATION: The call to RfcIndirectCall for INBOUND_IDOC_PROCESS failed.
ACTION: For more information re-run the server with trace and RFC trace enabled.
I inspected the idoc and found out that the encoding field was set to blanks. We changed the field to match the value in the message descriptor and idocs were accepted by SAP.
Later, for no apparent reason, IDOCS were rejected again with the same error messages despite the CCSID and encoding fields were correctly coded.
The R3LINK documentation states that these fields SHOULD be coded but I
am looking for a stronger statement like MUST.
Here is the idoc fragment (starts with the SAPH) as it looked the first time it errored (EBCDIC)
E2C1D7C8000000010000006C40404040000001F4 âÁ×È.......l@@@@...ô
D4D8E2E3D9404040404040404040404040404040 ÔØâãÙ@@@@@@@@@@@@@@@
4040404040404040404040404040404040404040 @@@@@@@@@@@@@@@@@@@@
4040404040404040404040404040404040404040 @@@@@@@@@@@@@@@@@@@@ _________________ Jose Luis Quintero Rea
Basis, MQ, ALE and Archiving Support
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum