Transaction Management
ERP Connector provides transaction management for publication of data from Windchill to an ERP system. By default, an ERP Connector transaction is assumed to have succeeded if the ESI response could be delivered successfully to a given destination. Thus, the Enterprise Systems Transaction Administration UI displays the status of a transaction based on whether or not the response data could be delivered successfully to the relevant destination. Once the ESI response is delivered to a destination, the data should be published to an ERP system either by manual or automated means, which is beyond the scope of ERP Connector.
Customization Points
The status of a transaction may be updated in Windchill based on whether or not product data was successfully published to an ERP system, rather than on the status associated with delivering the response message to the required destination (such as a file, FTP or an Email target). This may be achieved via a certain ERP Connector preference setting, coupled with customization. See the following sections for more information.
Configurable Options
The following ERP Connector preference allows recording the status of a transaction in Windchill, either based on the status of delivery of the response data to a destination, or on the status of actual import (or publication) of product data to an ERP system:
◦ Specifies whether or not ERP Connector should invoke the PostResult RPC based on status associated with delivering the ESI response to a given destination.
Preference name: Enable Post Result
Default value: Yes
 |
This preference defines whether or not ESI services would initiate PostResult RPC requests for transactions in a release. The preference has relevance to closed loop transaction scenarios. When set to No, the status of each subtransaction in a transaction (and so also that of the transaction) is set to Pending (or to Failed), according as the ESI response was delivered successfully (or not) to the distribution target relevant for the transaction. When set to Yes, the status of each subtransaction in a transaction (and so also that of the transaction) is set to Succeeded (or to Failed ), according as the response was delivered to the relevant distribution target (or not). In cases where the status of a transaction was set to Failed , an ESI Failure is generated and assigned to the user. This preference has relevance only to ERP Connector.
|
Possible Customization
Modify ERP Connector to cater to closed loop transaction scenarios. This may be achieved by having the response data (that is delivered to a destination) processed appropriately and imported into an ERP system, and sending back the results of the import to Windchill. The product data may be imported in a batch (viz., as an offline process), or via an online process where the importing application interacts with ERP Connector can be customized for both types of processes.