企業管理 > 實行 Windchill ESI > Implementing Windchill ESI in an ORACLE Applications Environment > Understanding Windchill ESI Architecture > Message Logging, Error Handling, and Return Messaging > Return Messaging to Windchill
  
Return Messaging to Windchill
Windchill ESI EAI software components send a subtransaction PostResult message for every object/action/organization (including parts, BOMs, CNs, process plans, and so on). The Message field of the ESIPostResult schema is a string field that contains explanatory text about the status of the object. For more information on the structure of the PostResult schema, see Implementing Windchill ESI. This field is populated with several pieces of information. The following table describes the structure of the message field. The fields are delimited using a global variable ESIMessaging/Delimiter, which is set to a double pipe (||) by default. This delimiter is also prepended to the entire message string field. This is a feature put in to allow the source application to be able to dynamically parse the message using the delimiter specified in the 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 Implementing Windchill ESI). For example: "Received ESI Response."
EAI Secondary Message
If applicable, 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 the Implementing Windchill ESI). Including this information in the message is enabled via a global variable ESIMessaging/EAISecondary.
Root Cause Analysis Message
If applicable, 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 Implementing Windchill ESI). Including this information in the message is enabled via a global variable ESIMessaging/RootCause.
ERP Primary Message
If applicable, the primary API return message from the ERP system.
Including this information in the message is enabled via a global variable ESIMessaging/ERPPrimary.
For example:
IMPORT SUCCESS
ERP Secondary Message
If applicable, the secondary API return message from the ERP system.
Each secondary information entry is delimited by semicolons
Including this information in the message is enabled via a global variable ESIMessaging/ERPSecondary.
EAI Additional Information
Any pertinent information from EAI components (non-ERP). This text is not localized (For more information, see Internationalization Considerations or the Implementing Windchill ESI). For example, in the case of an error, this field might contain a stack trace.
Extra Information
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.
Return Messaging Flags
Flag
Description
ESIMessaging/ERPPrimary
Enables returning ERP primary information to Windchill PDMLink.
ESIMessaging/ERPSecondary
Enables returning ERP secondary information to Windchill PDMLink.
ESIMessaging/RootCause
Enables returning root cause information to Windchill PDMLink.
ESIMessaging/EAISecondary
Enables returning functional decision/warning information to Windchill PDMLink.