Enterprise Administration > Implementing Windchill ESI > Implementing Windchill ESI in an SAP Environment > Understanding Windchill ESI Architecture > Message Logging, Error Handling, and Return Messaging > Return Messaging to Windchill > Components of ESIPostResult Message
  
Components of ESIPostResult Message
Field
Description
EAI Primary Message
Text generated by EAI software components that describes the object/action/status of the subtransaction. This text is localized based on the locale (from the com_infoengine_locale property) of the data in the Windchill ESI Response. For more information see Internationalization Considerations or theWindchill Enterprise Systems Integration Open Application Programming Interface Guide. For example: "Successfully created part in SAP."
EAI Secondary Message
Text generated by EAI software components that tells the user of any warning or functional decision messages. This text is localized based on the locale (from the com_infoengine_locale property) of the data in the Windchill ESI Response (For more information see Internationalization Considerations or theWindchill Enterprise Systems Integration Open Application Programming Interface Guide for more details). Including this information in the message is enabled via a global variable ESIMessaging/EAISecondary. For more information, see Return Messaging Flags. For example: "Creating document version failed but assuming functional success."
Root Cause Analysis Message
Text generated by EAI software components that indicates the possible root causes of the error or provides hints and tips on where to find additional information about the error. This text is localized based on the locale (from the com_infoengine_locale property) of the data in the ESIResponse (For more information see Internationalization Considerations or the Windchill Enterprise Systems Integration Open Application Programming Interface Guide for more details). Including this information in the message is enabled via a global variable ESIMessaging/RootCause.
For more information, see Return Messaging Flags. For example, "For more information about this error, see the SAP Internal Application Log (transaction SLG1)."
ERP Primary Message
If applicable, the primary API return message from the ERP system. For SAP distribution targets, when using SAP BAPIs, this may include the following SAP message parameters, delimited by colons, with leading and trailing spaces removed:
Type (A, E, S, I, W, X)
ID
Number
Text
For SAP CCAP and CSAP remotely-enabled API function modules, this field may be the object name or internal SAP object number.
This text is not localized (See the Internationalization Considerations section in the Windchill Enterprise Systems Integration Installation and Configuration Guide - SAP for more details).
Including this information in the message is enabled via a global variable ESIMessaging/ERPPrimary.For more information, see Return Messaging Flags.
For example:
S:MM:356: The material GS_700_IB4D has been created or extended
ERP Secondary Message
If applicable, the secondary API return message from the ERP system. For SAP distribution targets, when using SAP BAPIs, this may include the following SAP message parameters, delimited by colons, with leading and trailing spaces removed:
Type (A, E, S, I, W, X)
ID
Number
Text
For SAP CCAP and CSAP remotely-enabled API function modules, this field will typically remain empty.
Each secondary information entry is delimited by semicolons
This text is not localized. For more information, see the Internationalization Considerations section in the Windchill Enterprise Systems Integration Installation and Configuration Guide - SAP.
Including this information in the message is enabled via a global variable ESIMessaging/ERPPrimary.
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
Any pertinent information from EAI components (non-ERP). This text is not localized. See the Return Messaging Flags section for more details. For example, in the case of an error, this field might contain a stack trace.
Extra Information
An additional field for customization.
Unlike logging, return messaging to Windchill does not contain flags to determine when to send messages - messages are required to be sent for every object/action/organization. However, there are flags that determine what can be returned to Windchill PDMLink. The following table describes these flags.