Closed as program error.
This issue only happens when SAP uses ALE to transfer files from SAP to Gentran:Server and there is more than one set of outbound connection parameters configured in the SAP Configuration. Intermittently Aleserver.exe is overwriting the IDOC data with a status message that should be written to a log file when the connection is being re-established with the SAP server. This causes the IDOC to fail translation in Gentran:Server. Symptoms include: - IDOCs being imported into Gentran:Server are failing translation but re-importing them works fine. - Error data file from translation session or IDOC file contains "Established the connection at <date> <time>." in the data, usually in an IDOC header record
RTC 369668 CF/CF Circumvention: turn off the timer to check for connection in Gentran's SAP configurations - Advanced Multi-Port features 1) Open Gentran's SAP Configuration settings 2) Click Advanced 3) Disable the box marked "Set timer for checking the connection" 4) Click Save, click OK
Users Affected: Customer using aleserver with the -interval program argument parameter. Problem Description: If the -interval argument parameter is small enough that the program checks for connection with the SAP server while the aleserver is receiving IDocs from the previous cycle, the IDoc EDI_DC control record could become overwritten with the trace log entry text "Established the connection".
Resolution Summary: Correct multithreading within aleserver to handle overlaps between connection checking and IDoc reception cycles.
Reported component name
STR GENTRAN MS
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
STR GENTRAN MS
Fixed component ID
Applicable component levels