Binding Function

RFDIASF

Binding ID

IMPORT_ASSET_FOLDER

Binding Description

Imports Object Data from Folder

Purpose

This is an data import Binding that is used to import customer Object data from files placed into a folder.  This includes Base Items, GTINS, Parts, Products, PDI Data as well as serialized asset data including Asset UDA's. This binding is based on RFDIAST and is more flexible as it does not require that the customer specify a specific file name and/or sheet name. See below on bottom of page for examples.

Logic

This Binding function performs the following logic:

üProcesses the folder path specified, validates the data and then produces an audit log with any errors

üCan be run automatically at selected intervals using the Scheduled Task Manager

üAn example of the Import layout can be found here

üNOTE: When importing Asset data 1:1 do not make the Asset ID and the Base Item the exact same value as this will cause issue with TagNet resolving to Object Type. For example if Asset ID = 'M-100245' make its corresponding Base Item identifier 'M100245' (no dash)

üImport logic can be modified using Asset Import Templates defined in Asset Master Settings. As an example, the Asset referenced Base Item ID can be auto generated with a specified prefix and length using Template ID *AUTOGEN_BASEITEM. An example of the import sheet can be seen here with logic specifics below:

ØThe [Item Brand Name] + [ERP Item] are concatenated together to make a match on TagNet Product Master, if a match is found then that BaseItem is used, if no match then a BaseItem (GTIN) will be created as below:

ØThe logic to create the next Base Item (GTIN) will follow that of Asset ID using the System Settings. That is, it looks at the last one issued in Asset Master (of that prefix) and adds one. If none exists it starts at XX0000001

ØAction column not required if ADD or UPD.  If the Asset ID exists its an update, else is an Add.  Only if the asset needs to be specifically deleted is action column required using DLT action code.

ØThe Short name and long description will default from ERP Item # (if values are blank). Example  'CISCO 1002' or 'DL 580' or 'HP BLC7000'. ** note that many Make/Model values start with Manf so it is redundant to include the Manf as well in description.

ØThe UCCITMGTN column is not req'd as the import will always include base Item info so it is redundant.

Restrictions

** there are no restrictions on the file name or XLS sheet name

Files Updated

RFDASSM, RFDASSEX, UCCRCIM

Program Name

URI set to RFDIASF

Binding Setup

Binding Properties