MACom Channel Transaction Detail

---

In this screen you define the connection between a channel and a transaction type, for incoming as well as for outgoing transactions. You can also activate the surveillance for a particular channel and transaction type.

 

Channel Id – is the ID for this particular channel. The identity can consist of digits and/or letters.
Clicking on the hyperlink opens the MACom Channel Detail screen.

Channel Description - Description of the channel.

Data Format - the information field will tell you the data format of the transaction. XML or File.

Transaction Type – here you can see what kind of transaction type you have defined.
Clicking on the hyperlink opens the MACom Transaction Types Overview screen, where you can see the complete list of transaction types in PipeChain Supply and well as PipeChain FlowProduction.

Direction – the information in this field will tell you the direction of the transaction. OUT means outgoing and IN means incoming transaction.

Sender – the sending system’s ID. Filling out this field is optional.
This ID can be found in the transaction’s sender field.

Receiver – the receiving system’s ID. Filling out this field is optional. This ID can be found in the transaction’s receiver field.

High Level Acknowledge – check this box if you want to be sure (i.e. get a receipt) that the (outgoing) transaction was received by the receiving system. PipeChain will not set the transaction to successfully sent (Transaction OK) until a CS00 acknowledge transaction has been received from the receiver. Incoming transactions will also generate a CS00 acknowledge transaction if this box is checked.

Inactive – check this box if you want to temporarily disable sending this transaction type on this channel.

 

- Outgoing transaction Only-

 

State Active – this is the status the transaction is created in. The default value should always be ”Shall be sent”.

Create Inactive – must be checked in order for you to create a transaction with the inactive status defined. However, we don’t recommend that you go ahead and create an inactive transaction. The reason for this is that PipeChain does not handle inactive transactions.

State Inactive – Which status do you want the transaction to have if you decide to create it as inactive?

Release Number – here you can state which version of the transaction you want to send to the receiving system. The version stated here must be the same version of PipeChain’s interface that is used by the receiving system.

BMQ Messages – is only used by the BMQ channel        
                      Type – the BMQ message will be sent with this type.
                      Class – the BMQ message will be sent with this class.
You can label the BMQ message so the receiving system is able to filter on Type and Class.

Transaction Surveillance Active – check this box if you want to activate the surveillance of the transactions. By enabling this function it becomes possible to edit the next two fields.

Expected time for next transaction – the value in this field is calculated, by PipeChain and based on the initial value and time frame you have set up.

The small square shows the status of the surveillance. The status can be either gray = no surveillance, green = OK or red = late.

Expect next transaction in – this is the time frame between two expected transactions. The default value is always 1d(ay). In order to get a smooth flow of transactions PipeChain recommend that you increase this time frame slightly, e.g. to 1d  1h.

Time for most recent transaction – the value in this field is automatically updated by PipeChain when the transaction type has been sent/received by this channel.