Deletion of Transaction History
Over time, the amount of transaction history maintained by the system can get very large and cumbersome. SinceWindchill ESI needs this transaction history to determine which objects need to be published in future publishing activities, the actual data cannot be deleted from the system. Instead, the history can be marked as deleted so that it can be hidden from the end-user and not shown in the reports.
Windchill Integration for MES uses ISA-95 B2MML for data exchange. This standard defines its own Transaction model. This integration maps one ESI Transaction to many B2MML transactions; the message for one ESI transaction is transformed into many B2MML transactions and then all these messages are zipped and sent over a delivery channel.
B2MML supports the following transaction model:
Sr. No.
Model
Request Verb
Response Verb
Notes
1
Pull
GET
SHOW
Request for data.
2
Push
PROCESS
ACKNOWLEDGE
Typically an add request.
The definition of word “process” as meaning “deal with” or “handle”. A PROCESS verb is often the equivalent of a command to add the data, but usually the receiving entity performs further actions as a result of receiving the data.
CHANGE
RESPOND
CANCEL
n/a
Typically a delete request. May optionally request a ConfirmBOD response message.
* 
The request to cancel indicates that the sender no longer needs the data. Because the CANCEL is not sent by the owner of the data, the data are not necessarily deleted.”
3
Publish
SYNC‑ADD
n/a
May optionally request a ConfirmBOD response message.
SYNC‑CHANGE
n/a
May optionally request a ConfirmBOD response message.
SYNC‑DELETE
n/a
May optionally request a ConfirmBOD response message.
A “Publish” model is used for data exchange for a B2MML transaction.
Each B2MML message has the information about the ESITransaction and ESIRelease object for Windchill Integration for MES that can be used to correlate messages with the Windchill ESI transaction.
Windchill
B2MML
Object
Attribute
Object
Attribute
ESIRelease
Number
ApplicationArea\Sender
LogicalID
ESITransaction
Number
ApplicationArea\Sender
ComponentID
PrimaryBusinessObject
Ufid
ApplicationArea\Sender
ReferenceID
CreatedBy
ApplicationArea\Signature
ID
CreatedDate
ApplicationArea
CreationDateTime
ApplicationArea\Sender
ConfirmationCode
Locale
ApplicationArea\UserArea\ValueString
languageLocaleID
Destination
ApplicationArea\Receiver
LogicalID
com_infoengine_user
ApplicationArea\Sender
AuthorizationID
B2MML Transaction messages and zip packages for ESI Transactions consists of following messages:
B2MML Transaction for Data Exchange
Request Verb
Comment
B2MML TXN Sequence
File Name Format
SyncMaterialInformation
SYNC ADD
01
B2MML_<OrgContainerName>_<ESI Txn Numbe>_MaterialInformation_01.xml
SYNC CHANGE
02
B2MML_<OrgContainerName>_<ESI Txn Numbe>_MaterialInformation_02.xml
SYNC‑DELETE
Windchill does not allow deletion of object once published
03
B2MML_<OrgContainerName>_<ESI Txn Numbe>_MaterialInformation_03.xml
SyncProductInformation
SYNC ADD
16
B2MML_<OrgContainerName>_<ESI Txn Numbe>_ProductInformation_16.xml
SYNC CHANGE
17
B2MML_<OrgContainerName>_<ESI Txn Numbe>_ProductInformation_17.xml
SYNC‑DELETE
Windchill does not allow deletion of object once published
18
B2MML_<OrgContainerName>_<ESI Txn Numbe>_ProductInformation_18.xml
SyncEquipmentInformation
SYNC ADD
04
B2MML_<OrgContainerName>_<ESI Txn Numbe>_EquipmentInformation_04.xml
SYNC CHANGE
05
B2MML_<OrgContainerName>_<ESI Txn Numbe>_EquipmentInformation_05.xml
SYNC‑DELETE
Windchill does not allow deletion of object once published
06
B2MML_<OrgContainerName>_<ESI Txn Numbe>_EquipmentInformation_06.xml
SyncPersonnelInformation
SYNC ADD
07
B2MML_<OrgContainerName>_<ESI Txn Numbe>_PersonnelInformation_07.xml
SYNC CHANGE
08
B2MML_<OrgContainerName>_<ESI Txn Numbe>_PersonnelInformation_08.xml
SYNC‑DELETE
Windchill does not allow deletion of object once published
09
B2MML_<OrgContainerName>_<ESI Txn Numbe>_PersonnelInformation_09.xml
SyncProcessSegmentInformation
SYNC ADD
13
B2MML_<OrgContainerName>_<ESI Txn Numbe>_ProcessSegmentInformation_13.xml
SYNC CHANGE
14
B2MML_<OrgContainerName>_<ESI Txn Numbe>_ProcessSegmentInformation_14.xml
SYNC‑DELETE
15
B2MML_<OrgContainerName>_<ESI Txn Numbe>_ProcessSegmentInformation_15.xml
SyncPhysicalAsset
SYNC ADD
Not for PfMD
10
B2MML_<OrgContainerName>_<ESI Txn Numbe>_PhysicalAsset_10.xml
SYNC CHANGE
Not for PfMD
11
B2MML_<OrgContainerName>_<ESI Txn Numbe>_PhysicalAsset_11.xml
SYNC‑DELETE
Not for PfMD
12
B2MML_<OrgContainerName>_<ESI Txn Numbe>_PhysicalAsset_12.xml
Was this helpful?