Binding Function

RFDUEVT

Binding ID

UNIVERSAL_TAG_EVENT

Binding Description

Universal Tag Event API

Purpose

This Binding was designed to notify SAP (via an in-house EAI broker) when raw material is issued to production through one of many portals. The EAI would consume this RFID event and update SAP on the back end with respect to inventory. The Binding utilizes internal variables so the end customer can use this in a variety of use cases thus the 'Universal' branding in name.

The specification detailed in this topic reflects an update to the existing RFDUEVT binding released with TagNet version 8.17.  The original RFDUEVT binding had the data field UCCRCIM.UCCERPITM (Part ID) mapped to the ConsignmentKey element in the JSON payload. Due to variable ConsignmentKey values that can be selected at print time, the data field is now a location UDA called SUPPLIER_NO.  When a tag is mapped, the SUPPLIER_NO UDA will have a value of the selected consignment key (for example, “303893”) or the value “N/A” to indicate that there is no supplier.

Logic

This Binding function performs the following logic:

üCollects whatever tags are read during a given read event cycle from a given portal, and sends them in real time.

üSupports full GPIO script as a result of standard MATCH / NOMATCH / ERROR / NOTAG variables.

üThe chart below shows what attributes are sent in the JSON payload

üCan be used in RSSI zone configurations and supports system logging.

Restrictions

Comments

 This binding is based on customers specification and can be tested with a backend system emulator that will return various reply states

Files Updated

RFDTAGVS

Program Name

URI set to RFDUEVT

Binding Setup

Binding Properties

Email Notification

The email address to send binding specific alerts. Note: This overrides the default SMTP Recipient value under System Settings

Dwell Time

Dwell time prevents the tag from being included in the web service request when seen again at the same gate when vehicle dwells there.  Refer to the the Binding Change for detailed explanations of this directive.

Inventory Movement Rules

In the example below, the Inventory Movement Rules are set to *YES. Refer to the the Binding Change for detailed explanations of each directive.

UDA Update

Updates the UDA Element Name with the Supplier No.  When a tag is mapped, the SUPPLIER_NO UDA will have a value of the selected consignment key (for example, “303893”) or the value “N/A” to indicate that there is no supplier

Note: that Supplier is written regardless of what the intent of the UDA element is and its data type.  Refer to the the Binding Change for detailed explanations of this directive.