Enterprise Administration > Implementing Windchill ESI > Implementing Windchill ESI in an SAP Environment > Understanding Windchill ESI Architecture > Message Logging, Error Handling, and Return Messaging > EAI Logging Process > Components of a Log Entry
  
Components of a Log Entry
The following table describes the components of a log entry, in the order in which they are placed. The fields in the log are delimited by a configurable delimiter that is set to a comma (,) by default
Field
Length
Description
Transaction Number
200
TheWindchill ESI transaction number that is being processed.
Target
25
Uniquely identifies the target where the object is being published and has the following format:
<Destination>,<TargetID>
where:
<Destination> exists as a child of the <Transaction element in the Windchill ESI response. It takes a value of the form <SAP System ID> . <SAP Client> where SAP System ID and SAP Client are mandatory parameters that are provided while creating an SAP type distribution target in Windchill.
<Target ID> takes a value of the form <TargetNumber>:<Plant>.
where:
<Target Number> is the number attribute on the ESITarget object representing the distribution target in Windchill and <Plant> is the plant name associated with the SAP destination. < Plant> will have an empty value if the distribution target represents a “No Plant” destination.
For example:
The following Target indicates an object being published to plant 1100 of SAP system PTCPROD, client 800 and represented by an ESITarget object having the number PTC_1:
PTCPROD.800,PTC_1:1100
A Target that is not plant-specific might look like this:
PTCPROD.800,PTC_1
Application
1
Identifies the application that originated the message. For further details, see the section Application.
Type
1
Indicates the type of message. For further details, see the section Type.
Severity
1
Indicates the severity level of the message. For further details, see the section Severity.
Message Code
5
Unique message code identifier, used as the cross reference key to the appropriate localized message text. This field is hard-coded by the developer or a customizer when invoking the Logging_Service. For further details, see the section Message Code .
EAI Primary Message Text
Descriptive text such as a message description (corresponds to the Message Code).
This text is localized based on the ESILog/Locale global variable. For more information see Internationalization Considerations.
For example: Received ESI Response.
Descriptive Text
Any descriptive text. For example: Object Number.
Root Cause Analysis Message
Text describing possible root cause of error, or where user may find more information about the error.
This text is localized based on the ESILog/Locale global variable. For more information see Internationalization Considerations.
The logging of this information is enabled via a global variable ESILog/RootCause. See the Logging Flags section for more details.
For example: "For more information regarding this error, please refer to the SAP Application Log (transaction SLG1)"
ERP Primary Message
300
If applicable, this is the primary API return message from the ERP system. For SAP distribution targets, this includes the following SAP message parameters, delimited by colons, with leading and trailing spaces removed:
Type (usually A, E, S, I, W, or X)
ID
Number
Text
This text is not localized. For more information see Internationalization Considerations.
The logging of this information is enabled via a global variable ESILog/ERPPrimary. See the Logging Flags section for more details. Since this information applies to different message types and severities, it may be repeated several times in the log.
For example:
S:MM:356:The material GS_700_IB4D has been created or extended
ERP Secondary Message
300
If applicable, the secondary API return message is sent from the ERP system. For SAP distribution targets, this includes the following SAP message parameters, delimited by colons, with leading and trailing spaces removed:
Type (usually A, E, S, I, W, or X)
ID
Number
Text
Each secondary information entry is delimited by semicolons
This text is not localized. For more information see Internationalization Considerations.
The logging of this information is enabled via a global variable ESILog/ERPSecondary. See the Logging Flags section for further details. Since this information applies to different message types and severities, it may be repeated several times in the log.
For example:
H:MK:102:Trying to create: GS_700_IB4D 1200; S:M3:800:Material GS_700_IB4D created; H:MK:103:Trying to change: GS_700_IB4D 1200; S:M3:810:No changes made
EAI Additional Information
2500
Any pertinent information from EAI components (non-ERP). This text is not localized. For more information see Internationalization Considerations. Since this information applies to different message types and severities, it may be repeated several times in the log.
For example, in the case of an error, this field might contain a stack trace.
Extra Information
2500
Additional field for customization.