+ All Categories
Home > Documents > Data Sync Users Guide v67

Data Sync Users Guide v67

Date post: 26-Feb-2018
Category:
Upload: hemalatha
View: 223 times
Download: 0 times
Share this document with a friend

of 59

Transcript
  • 7/25/2019 Data Sync Users Guide v67

    1/59

    Copyright 2004, LANSA, Inc. 1All rights, domestic and international, reserved

    DDAATTAASSYYNNCCDDIIRREECCTT

    UUSSEERRGGUUIIDDEE

    VVEERRSSIIOONN66..77

  • 7/25/2019 Data Sync Users Guide v67

    2/59

    Copyright 2004, LANSA, Inc. 2All rights, domestic and international, reserved

    ContentsI ntroduction & Concepts ............................................................................................................5

    Introduction ......................................................................................................................................... 5

    What is Global Data Synchronization? ......................... ........................... ......................... .................... 5Data Sync Direct ................................................................................................................................. 6

    Training and Documentation ........................ ......................... .......................... ......................... ............ 7

    Basic Terminology .....................................................................................................................8What is a GTIN? ........................ .......................... .......................... ......................... ........................... .. 8

    What is Containment? ......................................................................................................................... 8

    What is a GLN? ................................................................................................................................... 8

    What is a Subscription? .......................... .......................... ......................... .......................... ................ 9

    What is a Publication? ......................................................................................................................... 9

    What is Schema? ................................................................................................................................ 9What are Class Extensions? ........................ ......................... .......................... ......................... ............ 9

    Getting Famili ar wi th Data Sync Direct ................................................................................... 10Primary Components .......................... ......................... .......................... .......................... .................. 10

    Secondary Components .................................................................................................................... 10

    Authority and Access .......................... ......................... .......................... .......................... .................. 10

    User Access .......................... .......................... .......................... ......................... .......................... . 10

    GLN Authority ............................................................................................................................... 10

    Environments ................................................................................................................................ 10

    Data Sync Di rect Login Page ................................................................................................... 12

    GTINs Overview ....................................................................................................................... 13

    Preamble ........................... ......................... .......................... .......................... .......................... ..... 13

    Secured Access to GTINs by GLN Authority .......................... ......................... .......................... ..... 13

    Role-based User Attribute Permissions ......................................... ......................... ....................... 13

    Intelligent Life Cycle Messaging .................................................................................................... 13

    Validation Rules Integrated with GTINs ........................ ......................... .......................... .............. 13

    Components ...................................................................................................................................... 13

    GTINs Search and Instance List .......................... .......................... ......................... ....................... 13

    GTIN Details ................................................................................................................................. 14

    GTINs....................................................................................................................................... 15

    GTINs Search and Instance List ........................................................................................................ 15

    GTIN ............................................................................................................................................. 15Information Provider ...................................................................................................................... 15Target Market ........................ .......................... .......................... ......................... ........................... 15

    Description .................................................................................................................................... 15

    Status ........................................................................................................................................... 15

    GPC .............................................................................................................................................. 16

    Brand Name .......................... .......................... .......................... ......................... .......................... . 16

    Product ID ......................... ......................... .......................... .......................... .......................... ..... 16

    Effective Date ........................ .......................... .......................... ......................... ........................... 16

    Product Type................................................................................................................................. 16

    Link ............................................................................................................................................... 16

    Additional Links ......................... .......................... .......................... ......................... ....................... 16

    GTINs List : Search Component ......................... .......................... .......................... ......................... . 16

    GTINs List : Adding a New GTIN ........................ .......................... .......................... ......................... . 17

    Listed GTIN Details Tab .................................................................................................................... 18

    GTIN Messaging ............................................................................................................................... 19GTIN Registration Options ........................... ......................... .......................... .......................... ......... 20GTIN Details PageDate ................................................................................................................. 20

    GTIN Details PagePackaging ........................................................................................................ 21

  • 7/25/2019 Data Sync Users Guide v67

    3/59

    Copyright 2004, LANSA, Inc. 3All rights, domestic and international, reserved

    GTIN Details PageMisc ................................................................................................................. 22

    Net Change Management ......................................................................................................... 23

    Contai nment M anager ............................................................................................................. 24Overview ........................... ......................... .......................... .......................... .......................... ..... 24

    Mixed Pallets ..................................................................................................................................... 25

    Publ ication Manager ................................................................................................................ 26Tr ansaction Wizard .................................................................................................................. 28

    Overview ........................... ......................... .......................... .......................... .......................... ..... 28

    Automating Your Transactions ......................... ......................... .......................... .......................... ..... 28

    Step 1: Determine the transaction type you want to run ............................................. ....................... 30

    I want to run............................................................................................................................... 30

    Step 2: Identify the data ......................... .......................... .......................... ......................... .............. 30

    Using these Items...................................................................................................................... 30

    Step 3: Filtered by......................................................................................................................... 31

    Step 4: Review the results .......................... ......................... .......................... .......................... ......... 31

    Spreadsheet Upload in the Transaction Wizard ..................................... ........................... ................. 32Processing Publications in the Transaction Wizard ........................ .......................... ......................... . 33

    Tr ading Par tners ...................................................................................................................... 35

    Overview ........................... ......................... .......................... .......................... .......................... ..... 35Trading Partners List PageDisplay Fields .......................... .......................... .......................... ......... 35

    GLN Manager Detail PageMaintainable Fields ........................... .......................... .......................... 36

    Products ................................................................................................................................... 37Overview ........................... ......................... .......................... .......................... .......................... ..... 37

    Products ListDisplay Fields ............................................................................................................ 37

    Products Search Component ........................... ......................... .......................... .......................... ..... 37

    Catalogs.................................................................................................................................... 38

    Overview ........................... ......................... .......................... .......................... .......................... ..... 38

    Details Tab ....................................................................................................................................... 38

    Adding a new Catalog .................................... ........................... ......................... .......................... ..... 38

    Catalogs Tab ..................................................................................................................................... 39

    Distribution List Tab ....................... .......................... .......................... ......................... ....................... 39

    My Workf low ............................................................................................................................ 41

    Overview ........................... ......................... .......................... .......................... .......................... ..... 41

    To Dos Display Fields ................................................................................................................ 41To Dos Search.............................................................................................................................. 42Workflow Step Detail ......................................................................................................................... 42Workflow Step DetailDisplay Fields .......................... ........................... ......................... .................. 43

    Transfer To ................................................................................................................................... 44

    Messaging H istory .................................................................................................................... 45

    Overview ........................... ......................... .......................... .......................... .......................... ..... 45

    Messaging History List PageDisplay Fields ....................... .......................... .......................... ......... 45

    Messaging History Search Component ........................ ........................... ......................... .................. 46

    Publ ications .............................................................................................................................. 47Overview ........................... ......................... .......................... .......................... .......................... ..... 47Publications List PageDisplay Fields ........................ ........................... ......................... .................. 47

    Catalog Item Notification.................................................................................................................... 47

    Conf irmations .......................................................................................................................... 49Overview ........................... ......................... .......................... .......................... .......................... ..... 49

    Confirmations List PageDisplay Fields .......................... ......................... .......................... .............. 49

    Creating Confirmations ...................................................................................................................... 50

    Subscription Manager .............................................................................................................. 51

  • 7/25/2019 Data Sync Users Guide v67

    4/59

    Copyright 2004, LANSA, Inc. 4All rights, domestic and international, reserved

    RFCIN/CIS .............................................................................................................................. 52Overview ........................... ......................... .......................... .......................... .......................... ..... 52

    Creating Requests and Subscriptions ................................................................................................ 52

    Dashboards .............................................................................................................................. 54Overview ........................... ......................... .......................... .......................... .......................... ..... 54

    My User I nf ormation ............................................................................................................... 56Overview ........................... ......................... .......................... .......................... .......................... ..... 56

    Util i ties ..................................................................................................................................... 57

    I nterfaces ................................................................................................................................. 58Overview ........................... ......................... .......................... .......................... .......................... ..... 58

    Table of F igures ....................................................................................................................... 59

  • 7/25/2019 Data Sync Users Guide v67

    5/59

    Copyright 2004, LANSA, Inc. 5All rights, domestic and international, reserved

    Introduction & Concepts

    Introduction

    The purpose of this guide is to familiarize you with LANSAs Data Sync Direct solution.

    This Product Management System manages your companys products, leverages yourexisting product data you already have in other systems, integrates business process viathe workflow engine and provides tools to keep your product data in synchronization

    with your trading partners.

    LANSA Data Sync Direct is a direct integration solution that on the Supply side,leverages existing item information on your production server and synchronizes that

    information with your data pool, the Global Registry and your Trading Partners. On theDemand side, it receives item data from your suppliers via the Global Registry andsynchronizes their item data with your internal Item Catalog. Data Sync Direct is based

    on LANSAs core technology, proven for more than 20 years, which can be deployed on

    IBM i, Microsoft Windows, Linux or UNIX servers.

    What i s Global Data Synchronization?

    Global Data Synchronization (GDS) is an industry-endorsed initiative that was created toeliminate product data inaccuracies in the supply chain. Using GDS means that

    inefficiencies and costs inherent in using manual or proprietary systems are avoided.Instead, all companies using GDS only enter their product/item data once, in a single

    place and can send/synchronize this data to multiple users, nationally and globally. Thestandards body that governs GDS is GS1.

  • 7/25/2019 Data Sync Users Guide v67

    6/59

    Copyright 2004, LANSA, Inc. 6All rights, domestic and international, reserved

    Figure 1: GDS Overview

    Data Sync Direct

    Data Sync Direct is a rapidly implementable solution that supports all the requiredsupply-side and demand-side messaging required for manufacturers, distributors,

    retailers, brokers and importers to synchronize item information with their tradingpartners. Data Sync Direct goes beyond basic messaging and allows you to manage all of

    your GTIN activity with your trading partners via GDSN synchronization services usinga point-and-click, browser-based interface.

    http://www.lansa.com/images/resources/jargonbuster_gds_imglg.jpg
  • 7/25/2019 Data Sync Users Guide v67

    7/59

    Copyright 2004, LANSA, Inc. 7All rights, domestic and international, reserved

    Figure 2: LANSA Data Sync Direct

    Training and Documentation

    This guide is intended for all audiences that will be general users of Data Sync Direct. Inorder to adequately prepare you for the Data Sync Direct software implementation, you

    should have gone through the LANSA Concepts & Fundamentals training course.

    Besides this user guide, you might also want to look at the following additional guides:

    Data Sync Upgrade Guide iSeries v67

    Data Sync Upgrade Guide Windows v67

    Data Sync Administrators Guide v67

  • 7/25/2019 Data Sync Users Guide v67

    8/59

    Copyright 2004, LANSA, Inc. 8All rights, domestic and international, reserved

    Basic Terminology

    What is a GTI N?

    GTIN is an acronym meaning Global Trade Item Number. It is a 14-digit identifier for

    any trade item in a unique package configuration.

    The most basic example of a GTIN is one that represents an individual product unit that aconsumer would purchase. Other GTINs might represent the same product in a case pack

    or pallet configuration.

    The GTINs 14 digits arecomprised of four components. They are:

    Package indicator (position 1)

    Company prefix as designated by EAN/UCC (positions 29)

    Unique number within the organizations product set (positions 1013)

    Check digit (position 14)

    The exact constructs of the GTIN can vary based on a number of factors, depending onthe GTIN assignment rules adopted by each organization.

    Typically an existing 12-digit UPC is left-filled with zeros to make a compliant 14-digitGTIN. Below is a sample matrix of GTINs for an existing UCC-12 code:

    Package level GTIN UPC UPC Type

    Each 0001547892001C 01547892001C UCC-12

    Case 1001547892001C 01547892001C Case code number

    Pallet 2001547892001C 01547892001C EAN/UCC-14

    What is Containment?

    Containment is the term representing multiple packaging variations of the same item (orUPC) as seen in the chart above. An each is contained in an inner pack which is

    contained in a case which is stacked on a pallet.

    What is a GLN?

    GLN is an acronym meaning Global Location Number. It is a unique 13-digit numberrepresenting a physical, functional or legal entity. It is used to set up relationships

    between organizations that want to sync item information with each other.

    Every subscriber or trading partner is issued a GLN for their organization. When a GTIN

    is added to the Global Registry, a suppliers GLN is associated with it . A supplier thenpublishes that GTIN to another trading partner GLN in the supply chain (such as aretailer). When the retailer receives a publication, they will recognize the publishing

    trading partner by their GLN.

    Additionally, there can be a hierarchy of GLNs within an organization. These are known

    as sub-organizations. For example, a major retailer could configure all their distributioncenters (or even individual stores) as sub-organizations underneath their master GLN.

    This facilitates the following:

  • 7/25/2019 Data Sync Users Guide v67

    9/59

    Copyright 2004, LANSA, Inc. 9All rights, domestic and international, reserved

    A supplier could publish either to the top-level GLN or to a specific sub-organizations GLN.

    A supplier could have multiple sub-orgs within their own organization torepresent different manufacturing divisions or brands. This way a supplier sub-organization (such as the power tool division) could publish to a retailer sub-organization (such as a chain store).

    What i s a Subscri ption?

    A subscription allows one organization (GLN) to maintain synchronization for a givenitem (GTIN) whose information is maintained by a different organization (GLN). This isalso referred to as data alignment.

    As an example, if the manufacturer issues an item correction message to the Data Pool,all those trading partners that had subscribed to that GTIN will be notified of the new

    data content.

    What i s a Publication?

    Publication is initiated when the maintainer of an item updates that item and sends thatupdated item information to other organizations that have subscribed to it.

    Publication has also been referred to as notification.

    What is Schema?

    The information necessary to describe an item varies by industry.

    What are Class Extensions?

    This is the Schema term for attributes specific to an industry. In addition to the coreattributes that can represent any trade item, each industry can have additional attributes to

    more accurately identify a GTIN. Examples of industry extensions include HBC (health,beauty, and cosmetics), OTC (over-the-counter), Produce, Shelf-Stable, FMCG (fast-moving consumer goods), Hardlines, Food Service and Healthcare.

  • 7/25/2019 Data Sync Users Guide v67

    10/59

    Copyright 2004, LANSA, Inc. 10All rights, domestic and international, reserved

    Getting Familiar with Data Sync Direct

    Primary Components

    LANSAs Data Sync Direct solution consists of four major business functions:

    GTINsmanages all GTIN information.

    Trading Partnersmanages trading partner relationships.

    Productsallows you to view ERP items that have GTINs assigned.

    To Dostracks subscription events and workflow participation.

    Secondary Components

    Data Sync Direct also includes the following secondary functions:

    Messaging Historyallows you to obtain detailed audit information for allregistry messages.

    Publicationsallows you to obtain detailed audit information for publications.

    Subscription Managerallows you to subscribe to registry events that are ofinterest.

    My User Informationallows changes to your user profile information.

    Au thor ity and Access

    Access to Data Sync Direct is password-protected by user profiles. These profiles are setup in the Data Sync Direct Utilities menu. There are a number of security features

    associated with user profiles, such as:

    User Access

    Each user is associated with a Role. This universal role may be applied to groups of

    users such as Production, Sales, Logistics, etc. Roles control permissions such as:

    Menu access rights

    Workflow authorities

    GLN Authority

    Internal and external GLNs affect your access to GTIN information.

    Internal GLNsrepresent entities within your own organization such asdivisions, manufacturing plants or possibly brands.

    External GLNsare those trading partners to whom you publish GTINinformation. As an example, one account manager may be able to publishGTINs to one retailer but not another.

    Environments

    Environments allow for logical partitioning of the Data Sync Direct application.Environments can represent test or production environments.

  • 7/25/2019 Data Sync Users Guide v67

    11/59

    Copyright 2004, LANSA, Inc. 11All rights, domestic and international, reserved

    Environments can logically separate activity of one division from another. DataSync Direct environments are a primary feature used to segment subscriber

    activity when using Data Sync Direct in a hosted or ASP mode (wherein asupplier can only see his registry message history).

    In summary, different people can see different information within Data Sync Direct based

    on their job functions. Speak with your Data Sync Direct administrator to confirm or toset up your authority and access rights.

  • 7/25/2019 Data Sync Users Guide v67

    12/59

    Copyright 2004, LANSA, Inc. 12All rights, domestic and international, reserved

    Data Sync Direct Login Page

    Access to all Data Sync Direct functionality is controlled by the User Login page. An

    example of the URL for this is shown below, however, your company may set up a

    shortcut so that it can be easily remembered and bookmarked.

    http://your.domain/CGI-BIN/lansaweb?webapp=LPMLOGINW+webrtn=LPMLOGINWR

    +ml=LANSA:XHTML+partition=UCP+language=ENG+F(VF_ELCLS)=NET2007BLUE

    A Data Sync Direct user profile requires setup in the User Manager menu. See your Data

    Sync Direct administrator if this has not been done for you.

    Note: Your Data Sync Direct user profile is in addition to any iSeries or

    Windows profiles.

    It is important to understand that the Data Sync Direct user name and password are both

    case sensitive.

    If for some reason you forget your password, clicking the Forgotten your password?link will email you a system-generated password that can be subsequently changed in theMy User Information menu option.

    Figure 3: Data Sync Direct Login Page

  • 7/25/2019 Data Sync Users Guide v67

    13/59

    Copyright 2004, LANSA, Inc. 13All rights, domestic and international, reserved

    GTINs Overview

    Preamble

    The GTINs menu option is the focal point of activity for maintaining GTIN information

    and submitting messages to the item registry. From this interface, GTIN information canbe searched in a multitude of ways and item information can be viewed and maintainedbased on the users authority.

    This function can be mapped directly to your existing item/product database so certain

    attributes may come from your existing ERP system and some will come from LANSAsGTIN extensions.

    The following features of GTINS make it a robust tool for gathering item information

    gathering and collaboration.

    Secured Access to GTINs by GLN Authority

    A person can be restricted to viewing only those GTINs that pertain to the GLN to which

    they are assigned. If you have the authority to update, you can only apply GLNs towhich you are authorized to GTINs to which you are authorized.

    Role-based User Attribute Permissions

    For a given role, a user can be restricted to the following within the GTIN Manager:

    GTIN maintenancecan they update any fields?

    Can they submit any messages to the registry?

    Can they add a new GTIN?

    Can they perform spreadsheet uploads?

    What attributes can they see and update?

    Intelligent Life Cycle Messaging

    GTINs will display messages based on their status in the registry. This minimizes the

    confusion for users new to the registry.

    Validation Rules Integrated with GTINs

    All rules such as mandatory fields, allowable values and dependencies are built in, which

    makes GTINs a data cleansing tool. It does not allow messages to proceed unless all the

    GTIN attributes are in compliance. This ensures successful acceptance of the message by

    1SYNC with no time wasted on errors that should have been discovered earlier in themaintenance cycle.

    Components

    GTINs contains two major components:

    GTINs Search and Instance List

    Search for GTINs by GTIN, item number or item description

    Add or clone a new GTIN

  • 7/25/2019 Data Sync Users Guide v67

    14/59

    Copyright 2004, LANSA, Inc. 14All rights, domestic and international, reserved

    Drill down to the GTIN details

    View messages for a specific GTIN

    View publications for a specific GTIN

    GTIN Details

    View and maintain GTIN attributes

    Link various GTIN package variations (item containment)

    Submit messages to the registry (Add, Modify)

    View publications for a GTIN

    View messages for a GTIN

    Now that you have an overview of the capabilities of the GTINs menu option, pleaserefer to the following sections on specifics for processing messages.

  • 7/25/2019 Data Sync Users Guide v67

    15/59

    Copyright 2004, LANSA, Inc. 15All rights, domestic and international, reserved

    GTINs

    GTI Ns Search and I nstance L ist

    Shown below inFigure 4: GTINs Search and Instance Listis a sample of the main

    GTIN presentation list.

    Figure 4: GTINs Search and Instance List

    You can choose what fields to display and the order in which you want them to bedisplayed. You can also click on any column to sort the list by that column, ascending ordescending. Listed below are some of the commonly displayed fields.

    GTIN

    This is the GTIN assigned by your company. When you click on a GTIN, its details aredisplayed in a frame below the list. An to the left of the GTIN indicates that there are

    actions that need to be taken in order for the GTIN to get back in synch with the Data

    Pool registry. A indicates the GTIN is synchronized. The does notmean that an

    error has occurred or that there is something wrong with the GTIN. A GTIN that has notyet been registered wont display either symbol.

    Information Provider

    This is the GLN of the information provider that registered the GTIN (note that Schema

    allows multiple occurrences of the same GTIN).

    Target Market

    This is the target country of the GTIN.

    Description

    This is the item name description as entered or mapped from your ERP system.

    Status

    This is the status of GTIN as it relates to the Data Pool.

    Unregistered means the GTIN has been defined locally in Data Sync Direct buthas not been added to the Global Registry.

    Listed means the GTIN has been added to the Global Registry via an Item Add.

  • 7/25/2019 Data Sync Users Guide v67

    16/59

    Copyright 2004, LANSA, Inc. 16All rights, domestic and international, reserved

    Cancelled means the GTIN has been completely removed from the Data Pool andis no longer useable.

    GPC

    This is the GPC code and description assigned to the GTIN.

    Brand Name

    This is the brand that you have assigned to the GTIN.

    Product ID

    This is your internal Item Number from your ERP Item Master.

    Effective Date

    This is the date the GTIN becomes effective in the Registry.

    Product Type

    This is the packaging for this GTINfor example, Each, Pack, Case, or Pallet.

    Link

    This shows the relationship that another GTIN has to this GTIN the other GTIN is the

    Parent or Child of this GTIN. If the GTIN is listed, it can be linked to other GTINs to

    form a logical containment of packaging levels.

    Additional Links

    When you right-click on a GTIN, you will see the following links if they are applicable to

    the GTIN:

    Product ID: clicking on this choice will result in a display only of the GTINsassociated with the Product ID of this GTIN.

    Net Change: clicking on this choice will bring up the Attribute Change Actionsto be taken in the frame below the GTIN list.

    Publish: clicking on this choice will bring up the Publication Manager in theframe below the GTIN list. If the GTIN is listed, it can be communicated to

    trading partners via Publication.

    Relationships: clicking on this choice will bring up the Containment Manager inthe frame below the GTIN list.

    Transactions: if there is at least one message posted against the GTIN, you willsee a Transactions choice when you right-click on the GTIN. Clicking on this

    choice will bring up the Transaction Details in the frame below the GTIN list.

    Delete: If the GTIN is unregistered, you will see a Delete choice when you right-click on the GTIN. Clicking on this choice will delete the GTIN from Data SyncDirect. This is acceptable since the Global Registry is not aware of the GTIN.

    GTI Ns L ist : Search Component

    To the left of the rows of GTIN details is a search component that allows you to build theGTIN list by certain criteria. To search, enter the desired data, then either tab out of the

    search field or click Go. Searches can be conducted using the following criteria:

  • 7/25/2019 Data Sync Users Guide v67

    17/59

    Copyright 2004, LANSA, Inc. 17All rights, domestic and international, reserved

    GTIN searches for a specific GTIN assigned to your ERP item description.

    Provider GLN lists GTINs that match this information provider GLN.

    Product ID searches for an ERP Item Number. Entering a partial Product IDstring will produce a list of GTINs whose Product ID begins with that number.

    Product Description searches over the GTIN short description. This query is notcase sensitive.

    EAN/UCC code lists all GTINs matching this code.

    Brand Name lists all GTINs matching this brand name. Note that the selection isa drop-down containing all of your brand names.

    Filters: you can narrow your returned list of GTINs using and/or filter logic.

    o Status allows you to select only GTINs who status matches yourselection from this dropdownSynchronized, Not-Synchd,Unregistered, Listed, Published, and Discontinued.

    o Product Type allows you to select only GTINs whose product typematches your selection, such as Each or Case.

    Note that there is a Result Count dropdown that allows you to limit the numberof returned rows of GTIN data.

    GTINs L ist : Adding a New GTIN

    To add a new GTIN to your data, click the New button on the left side of the screen, near

    the top. This allows you to define a new GTIN within Data Sync Direct. Users will entera new GTIN and associate it with valuesseeFigure 5: Add New GTINbelow.

    Figure 5: Add New GTIN

    Product IDis your ERP item number associated with this GTIN. If your ERPsystem is integrated with Data Sync Direct, the mapping function will populate

    this new GTIN with all mapped fields specific to this Product ID.

    Clone attributes fromallows you to populate this new GTIN with all theexisting values of another GTIN, in preparation for changing only the fields thatare unique to the new GTIN. This can save a lot of keystrokes when the new

    GTIN is similar to an existing GTIN. Using the Prompt button presents you with

  • 7/25/2019 Data Sync Users Guide v67

    18/59

    Copyright 2004, LANSA, Inc. 18All rights, domestic and international, reserved

    a list of your current GTINs and an option to filter that list so you can easily find

    the GTIN that you want to clone.

    GTINis the 14-digit number you are going to create. The last digit of the GTINis the check digit and can be calculated using the Append Check Digit button.

    GLNis the information provider GLN that identifies the organization actuallyregistering the GTIN. Only those GLNs you have authority to will be displayedin the dropdown list (see User Access).

    Target Countryis also referred to as Target Market (such as United States,Canada, or Mexico). It is possible that a product could have different attributes(such as physical dimensions) for different countries where it is sold.

    Once the values have been entered and selected, clicking the Add button willproceed to the GTIN Details Page, which will allow you to specify all the 200+

    attributes for that GTIN.

    Note that the key structure of a GTIN in Schema is GTIN + GLN + TM (Target

    Market). The same GTIN could be registered by multiple organizations such asdistributors or Private Label Manufacturers.

    L isted GTIN Details Tab

    Shown below inFigure 6: Listed GTIN Details Tabis a sample of the GTIN Details

    Tab, showing the core attributes to register a GTIN. The system will validate requiredfields as well as edit for valid values as determined by the specifications of the Data Pool.

    All date fields are entered using the calendar button to the right of the field.

    Figure 6: Listed GTIN Details Tab

    After entering the Item information, click Update Details to save the data. Pressing

    Update Details on any attributes tab will update the data included on all tabs.

    Validations will be performed and, if all required fields have been properly populated, the

    Item Add button will appear, as shown below inFigure 7: Unregistered GTIN.

  • 7/25/2019 Data Sync Users Guide v67

    19/59

    Copyright 2004, LANSA, Inc. 19All rights, domestic and international, reserved

    Note: Setting a GTIN to public on the GTIN Details tab allows third parties to

    query the Registry and view the GTINs master data. But if the Private Product

    dropdown is set to true, only specific users will be able to view the master data.Also, if a GTIN is set to private, you will need to populate the GLN ReceivingPrivate Data field on the Misc tab with the GLN of the trading partner you

    intend to notify.

    There are a number of actions that can be launched from the GTIN Details tab as well as

    a number of navigation actions that jump to other functions.

    If you see an to the right of the GTIN in the GTIN Details tab, you can click on it to

    received detailed instructions on how to bring the GTIN in synch (see the section entitled

    Net Change Management).

    When a GTIN is first created, it goes into an unregistered status as displayed below. Thisindicates that the GTIN has yet to be made known to the Data Pool. The Item Add

    physically creates the GTIN in the Global Registry, which is identified by 42 attributes.

    Figure 7: Unregistered GTINshows a GTIN that is ready to be added to the Global

    Registry through the Data Pool, via the Item Add button.

    Figure 7: Unregistered GTIN

    Once a GTIN has been registered as above, additional options become available,depending on the authority granted to your user ID (see GTIN Registration Options

    below).

    GTI N Messaging

    All messaging is submitted to your Data Pool via AS2. When submitting messages, be

    sure to have a Notification Query monitor job running, in order to receive and processconfirmations from the Data Pool. The monitor is set up within the Notification Monitoroption on the Utilities list.

  • 7/25/2019 Data Sync Users Guide v67

    20/59

    Copyright 2004, LANSA, Inc. 20All rights, domestic and international, reserved

    Note: When submitting transactions via AS2, the messages will be processed

    behind the scenes allowing you to continue entering data without waiting forthe transaction to complete. This is different from the Pending Batches optionon the menu which applies only to messages submitted in batch during theupload process. (See Transaction Wizard for more details.)

    GTI N Registration Options

    Figure 8: Registered GTIN & Available Messagesshows a registered GTIN thatis ready to accept additional Item messages as shown in the dropdown list on the left side

    of the screen (Change item). After a message type is selected, the page will refresh and a

    Process button will appear. Click that button to submit the Change Item message.

    Figure 8: Registered GTIN & Available Messages

    The Change item option is used to make changes or corrections to item data, creating anew version of the item.

    Figure 9: Additional Tabsshows additional options available to you that are listedabove the GTIN DetailsNet Change, Publish, Relationships, Transactions, Catalogs,

    and Attribute Change.

    Figure 9: Additional Tabs

    GTI N Detail s PageDate

    Shown below in Error! Reference source not found.are the various Date attributesyou might need on the GTIN. To remove a date, highlight the content of the field and

    delete the value.

  • 7/25/2019 Data Sync Users Guide v67

    21/59

    Copyright 2004, LANSA, Inc. 21All rights, domestic and international, reserved

    Figure 10: Date Attributes

    GTI N Detail s PagePackaging

    Shown below inFigure 11: Packaging Attributesare the attributes related topackaging of the GTIN.

    Note: There are two groups of attributes with dependent conditioning. Within

    each group, if any one of the following attributes is populated, then the otherattributes in the list must also be populated in order for the attributes to beincluded in the message to the Data Pool.

    Group 1

    Material Code

    Material Maintenance Agency

    Packaging Material Composition

    Packaging Material Code Description

    Packaging Terms And Conditions

    Group 2 Packaging Type Code

    Packaging Type Description

  • 7/25/2019 Data Sync Users Guide v67

    22/59

    Copyright 2004, LANSA, Inc. 22All rights, domestic and international, reserved

    Figure 11: Packaging Attributes

    GTI N Detail s PageM isc

    You can build the data on the Misc Tab to fit the needs of your product synchronization.In fact, all of the tabs are customizable via the GTIN Views selection in Utilities.

    Further, you can exclude some of the tabs if you have no use for them in the way you

    handle your GTIN data.

    Figure 12: Miscellaneous Details

  • 7/25/2019 Data Sync Users Guide v67

    23/59

    Copyright 2004, LANSA, Inc. 23All rights, domestic and international, reserved

    Net Change Management

    A high level overview of the status of each GTIN can be viewed within the GTINs List

    Page, allowing users to see at a glance the GTINs not in sync with the registry.

    When you see an next to a GTIN as inFigure 13: GTINs List Net ChangeIndicator,you can view all the actions required to bring the GTIN back intosynchronization with the registry by clicking on the Net Change tab, shown inFigure

    14: Required Actions for Synchronization.

    After performing the required actions, the GTIN will be back in synch with the registry

    and a will replace the .

    Figure 13: GTINs List Net Change Indicator

    Figure 14: Required Actions for Synchronization

  • 7/25/2019 Data Sync Users Guide v67

    24/59

    Copyright 2004, LANSA, Inc. 24All rights, domestic and international, reserved

    Containment Manager

    Overview

    Shown below inFigure 15: Containment Manageris a sample of the Containment

    Manager screen. This is a summary page that is divided into a header section (the sourceGTIN) and a relationship section (those GTINs that have a parent / child relationship with

    the source GTIN). In order to build a hierarchy of related GTINs by Product Type, you

    will link the GTINs in the Containment Manager, as shown below. During the linkingprocess, a transaction to link will be sent to the Data Pool. If a GTIN needs to be

    removed from the Containment Manager, you will submit an Unlink transaction. Theestablishment of the parent / child relationship is an internal transaction that you perform

    within Data Sync Directno message is sent to the Data Pool that the relationship hasbeen established (or removed). It is the Link transaction, which you perform after you

    have established the parent / child relationship, which is sent to the Data Pool to definethe hierarchy within the registry.

    Figure 15: Containment Manager

    Listed below is an explanation of each display field on the Containment Manager screen:

    Containment for GTIN is the GTIN and description of the source GTIN.

    GLN is the information provider GLN associated with the GTIN.

    Target Country is the ISO country code associated with the GTIN.

    Package is the Product Type of the source GTIN.

    When you click on the Child or Parent radio button in the Product Type gray bar,a Prompt is shown where you can search for the target GTIN.

    Note: For GTINs to be linked they must share the same GPC/UDEX code.The Prompt will position to the same ERP Item Number as the source GTIN.You can find other GTINs by using the search options on the left side of the

    GTIN list.

  • 7/25/2019 Data Sync Users Guide v67

    25/59

  • 7/25/2019 Data Sync Users Guide v67

    26/59

    Copyright 2004, LANSA, Inc. 26All rights, domestic and international, reserved

    Publication Manager

    This function serves the purpose of notifying, or publishing, GTIN information to

    recipient GLNsyour trading partners. This function is performed on the Publish tab.

    Shown below isFigure 16: Publication Manager.

    Figure 16: Publication Manager

    Within the header section of the Publication Manager, Status indicates if the GTIN isRegistered (Listed) with the Data Pool. Eff. Date is usually the date that the GTIN was

    entered into Data Sync Direct.

    Below the header section you could see a list of subordinate GTINs in the hierarchy, if

    they are Linked at the Data Pool with the parent GTIN selected.

    You will enter the following additional information on the page in preparation forpublishing the GTIN hierarchy.

    Publish To GLN refers to your trading partner that you will be notifying. Onlythose trading partners that you have been authorized to will be displayed. You

    can enter their GLN or you can click Prompt for a list.

    Market Group is a collection of GLNs that has been created at the Data Pool byyour trading partner, so that you can publish to the group rather than having to

    publish to each of their GLNs. You will need to set up the Market Group via

    Utilities before you will see them in the dropdown. You can publish to one

    Market Group at a time. You will not specify the GLNs that are included withthe Market Group.

    Publication Date specifies when the GTIN publication is effective. Click thecalendar button to select the date; this assures that the date is entered in thecorrect yyyy-mm-dd format.

  • 7/25/2019 Data Sync Users Guide v67

    27/59

    Copyright 2004, LANSA, Inc. 27All rights, domestic and international, reserved

    Select Publication Type is a dropdown that allows you to choose ADD,DELETE, or REPUBLISH.

    Initial Load or New Item: The radio button that is already selected is the properdefault value based on GTIN status and the GLNspublication history for thisGTIN:

    o Initial Load is used when providing information for products of whichthe trading partner is already aware.

    o New Item is used when this is the first time this item is being publishedto this trading partner.

    Click Process to send the Publication to your trading partner via the Data Pool.

  • 7/25/2019 Data Sync Users Guide v67

    28/59

    Copyright 2004, LANSA, Inc. 28All rights, domestic and international, reserved

    Transaction Wizard

    Overview

    The Transaction Wizard is a robust method for mass processing of GTINs and

    Publications. You access the Transaction Wizard through the Propogation selection.

    Shown below is Figure 19: Transaction Manager Search.

    Figure 17: Transaction Manager Search

    Automating Your Transactions

    Figure 18: Transaction Wizard Overviewprovides a high level overview of thedata selections and processes available within the Transaction Wizard.

  • 7/25/2019 Data Sync Users Guide v67

    29/59

    Copyright 2004, LANSA, Inc. 29All rights, domestic and international, reserved

    I want to run...

    Upload

    SpreadsheetPublications

    Item

    Transactions

    Select

    transaction

    type

    Load GTINDetailsNo

    validation

    Load GTIN

    DetailsValidate

    Load GTIN

    Transactions

    Load

    Publications

    Browse for the

    spreadsheet

    then

    Using these

    items...

    Saved

    Transactions

    Show me all

    GTINs (select a

    category of

    GTINs)

    Select a

    previously-run

    and saved

    transaction from

    dropdown

    Publications

    or GLN-specific

    selection of

    GTINs?

    Select

    recipient GLN

    from

    dropdown

    Yes

    No

    Enter

    date

    range

    Sold to Recipient GLN

    Modified

    Published

    With Outstanding Net Change

    With Unregistered Status

    With Registered Status

    With Mixed Module Package

    With Pallet Package Type

    With Display Shipper Pkg Type

    With Case Package Type

    With Inner Pack Package Type

    With Each Package Type

    Not Linked

    Failed Transactions

    Filtered by Information ProviderTarget Country

    Brand Owner

    Brand Name

    GPC Code

    Final batch

    submission tothe Data Pool

    Verify data

    Figure 18: Transaction Wizard Overview

  • 7/25/2019 Data Sync Users Guide v67

    30/59

    Copyright 2004, LANSA, Inc. 30All rights, domestic and international, reserved

    Step 1: Determine the transaction type you want to run

    I want to run

    Publications, Item Transactions, or GTIN data uploaded from a spreadsheet.

    Step 2: I denti fy the dataUsing these Items

    There are two options.

    A saved transaction is one whose parameters were saved at the time of thelast run.

    Note: If selecting a saved transaction, the system will check to make sure thesaved transaction is the type of transaction you are currently requesting to run.For example, if you want to run publications, the saved transaction must also be

    for publications.

    You can query the Data Sync Direct tables, as shown inFigure 19: Using

    These Items.The dropdown selections can be narrowed further by populatingthe Recipient GLN field and date ranges. For publications, the Recipient GLN

    will be required.

    o Sold to Recipient GLNsearches for GTINs in the Pricing X-Ref tableset up within the GLN Manager. This table can be set up manually and

    is also populated automatically when a publication is sent to a trading

    partner.

    o Publishedsearches the publication history for GTINs that have had apublication sent to a trading partner.

    o With Outstanding Net Changesearches for GTINs showing an out ofsync in the GTINs List Page.

    o With Unregistered Statussearches for GTINs not yet sent to theregistry.

    o With Registered Statussearches for GTINs already sent to the registry.

    o With Pallet Package Typesearches for GTINs showing a specificPackage Type.

    o Not Linkedsearches for GTINs that have not yet been linked at the DataPool with any of your other GTINs.

    o Failed Transactionssearches for GTINs that were not processed

    successfully.

  • 7/25/2019 Data Sync Users Guide v67

    31/59

    Copyright 2004, LANSA, Inc. 31All rights, domestic and international, reserved

    Figure 19: Using These Items

    Step 3: Filtered by

    You can further narrow the group of GTINs returned in the initial query by InformationProvider, Brand Owner, Brand Name, and GPC Code. This is an AND conditionthe

    preceding criteria in the list must be defined before the next one can be selected.

    Step 4: Review the resul ts

    Click the Get these itemsbutton to run the query. Figure 20: Result Screen

    Optionsshows the results from selecting Item transactions.

  • 7/25/2019 Data Sync Users Guide v67

    32/59

    Copyright 2004, LANSA, Inc. 32All rights, domestic and international, reserved

    Figure 20: Result Screen Options

    Note: If a GTIN is in error, the Information Provider and Target Market fields

    will appear in red. Review the information next to the GTIN in order todetermine how best to proceed. To omit the GTIN, select the check box next to

    the GTIN in error, then click to delete the GTIN from the processing list.

    Spreadsheet Upload in the Transaction Wizard

    You can upload GTIN attributes as well as perform a mass upload of Item andPublication messages.

    If the Upload Spreadsheet option is selected, the upload interface will appear as shown in

    Figure 21: Upload Selections. Select the transaction type, browse to the spreadsheetto be uploaded, and then click Upload. It is recommended that the transaction type

    Load GTIN Details No validation be used rarely and only in special circumstances,

    as this could allow corrupted data into the tables.

    Figure 21: Upload Selections

    In order to load multiple data fields into a GTIN (or into many GTINs) from an Excelspreadsheet, you can choose any name you want for the spreadsheet but the sheet name

    containing the data must be ITEM UPLOAD. In order to publish GTINs to your trading

    partners by uploading a spreadsheet, the sheet name containing the data must beNOTIFY. In order to register GTINs from a spreadsheet, the sheet name must beRCITRAN. These can be Item Add, Item Modify, or Link transactions.

    Do not combine these functions within a spreadsheetuse three spreadsheets. LANSAcan provide you with boilerplate spreadsheets that you can use as a starting point to

    build your data.

    Be sure that you do not use any formatting of the cells in the spreadsheet. Its a goodidea to precede each data field with a tic mark (), which is a signal to the spreadsheet

    software to leave the data as is.

    After uploading the spreadsheet, the remainder of the processing will be the same as

    selecting the Publication or Item Transactions options from the I want to run screen.

    If there are records in the spreadsheet already in the Data Sync Direct tables, those

    records can either be ignored or updated based on the values in the spreadsheet. Further,

    if Update is selected, blank cells in the spreadsheet can either be copied over to the

  • 7/25/2019 Data Sync Users Guide v67

    33/59

    Copyright 2004, LANSA, Inc. 33All rights, domestic and international, reserved

    database (Update Blank Columns) updating any values in the database to blank or blank

    spreadsheet values can be ignored (Do Not Update Blank Columns).

    Note: When using the Transaction Wizards GTIN Upload, you can also force

    specific fields in the Data Sync Direct tables to be cleared out by entering

    %CLEAR in the cell you want updated to blank within the database.

    Processing Publi cations in the Transaction Wizard

    Once the returned list has been reviewed, the publication process is similar to the onedescribed earlier on the Publish tab. Refer to the Publication Manager section for detailson how to publish. SeeFigure 22: Results Page for Publicationsfor an example of alist of GTINs that have been selected for publication.

    Figure 22: Results Page for Publications

    When GTINs are submitted via the Transaction Wizard, the batch is sent immediately to

    the Data Pool for processing. As shown inFigure 23: Completed Batch,themessage stating Publication staged for processing indicates that the AS2 batch is beingtransmitted to the Data Pool. Response time for completion will vary depending on a

    number of factors. For faster notification of the batchs completion, you could run the

    Notification Monitor more frequently or you could subscribe to the workflow batchcompletion event.

  • 7/25/2019 Data Sync Users Guide v67

    34/59

    Copyright 2004, LANSA, Inc. 34All rights, domestic and international, reserved

    Figure 23: Completed Batch

  • 7/25/2019 Data Sync Users Guide v67

    35/59

    Copyright 2004, LANSA, Inc. 35All rights, domestic and international, reserved

    Trading Partners

    Overview

    The GLN Manager is accessed by selecting Product Information Management and then

    Trading Partners. This is whereGLNs are maintained (added, changed, or deleted).These could be your internal organizations GLN (you could have more than one) thatyou assign to yourGTINs,or they could be external trading partners to whom you

    publish. Additionally, this is where you can search for a specific GLN so that you can

    look at their GTIN publications. SeeFigure 24: Trading Partners List Pagefor anexample of the GLN list.

    Figure 24: Trading Partners List Page

    Trading Partners List PageDisplay Fields

    SeeFigure 25: GLN Manager Detail Pagefor an explanation of the data elements thatare displayed on each row.

    Figure 25: GLN Manager Detail Page

  • 7/25/2019 Data Sync Users Guide v67

    36/59

    Copyright 2004, LANSA, Inc. 36All rights, domestic and international, reserved

    GLN M anager Detail PageMaintainable F ields

    Rep Party GLNis the actual GLN issued for that entity. When you click on that row inthe list above, the details for that GLN are displayed below the list. The GLN will be

    automatically validated for the correct number of digits (13) and for the correct check

    digit in position 13.

    Partner Nameis the name you have assigned to that GLN.

    Parent GLNallows you to associate an Internal GLN with its parent GLN for the

    purpose of building hierarchical relationships. You can see an example of such a

    hierarchy on the right side ofFigure 25: GLN Manager Detail Page.

    Statuscan be Active, Inactive, Assigned or Withdrawn.

    Brand Owner Capableis set to yes if the GLN can be specified as a Brand Owner of

    GTINs.

    Published Itemsindicates whether or not you have published GTINs to that GLN.

    Information Provider Capableis set to Yes if the GLN can provide information to you

    about GTINs.

    Registered Nameis the description of the GLN.

    Partner Role, or GLN Type, can have one of four values: Internal, Recipient, Source,

    and Non-Publishable Demand.

    Internal refers to your organizations GLNs. Depending on the complexity ofyour company, you might have more than one.

    Recipient refers to those trading partners GLNs to whom you will be publishing.

    Source refers to trading partners who publish GTIN information.

    Undefined refers to trading partner sub-organizations associated with a demand-

    side GLN that send back a publication notification that was issued to a higher-level parent GLN.

    Primary Contactand the subsequent contact data allows you to capture address,telephone, and mail information about the GLN.

    To update GLN information, use the Save GLN button. There is also the option to

    Delete GLN if you have authority to do so and if the GLN is not being used.

  • 7/25/2019 Data Sync Users Guide v67

    37/59

    Copyright 2004, LANSA, Inc. 37All rights, domestic and international, reserved

    Products

    Overview

    When you click on Product Information Management and then on Products, you can view

    the relationship between your existing Item Master or ERP numbers and their associatedGTINs.

    Most suppliers only have their item information set up for the most common packaging

    variations they sell (usually Case). For GDSN compliance, a unique GTIN must be

    defined for each packaging variation of an existing UPC regardless if it is a orderable unitor not. As an example, 500 UPC codes may require the assignment of 1,500 GTINs in

    order to represent the Each, Case, and Pallet levels of packaging. To make this taskeasier, Data Sync Direct allows you to quickly clone one GTIN package variation toanother (for example, a Case to a Pallet) using the Clone attributes from feature when

    entering a new GTIN.

    Using the Products feature allows you to easily identify those ERP item numbers that

    have not been assigned GTINs, as well as allowing you to view/confirm/maintain thoseGTINs already assigned.

    Products Li stDi splay Fields

    Productis your internal item number from your ERP Item Master.

    Descriptiondisplays how the item is described in your ERP Item Master.

    UPCis the existing UPC code as stored in your ERP Item Master.

    Brandis the existing brand code or name associated with the product.

    Listed below each Product are those GTINs that have been assigned (if any).

    Products Search Component

    To the left of the Products list is a set of search components that allows you to filter theProducts list by Item Number, UPC Code, Description, or Brand Name. Also, you canfilter by GTIN Status. Entering a full or partial Product string will display all Products

    that begin with that string.

  • 7/25/2019 Data Sync Users Guide v67

    38/59

    Copyright 2004, LANSA, Inc. 38All rights, domestic and international, reserved

    Catalogs

    Overview

    Catalogs allow a user to create a grouping of GTINs, called a Catalog. The owner of

    the catalog can determine if other users can use and/or update their catalogs. If the user isan owner or administrator, they can add and remove GTINs from the catalog. A catalogcan be used to search on GTINs from within the GTIN Manager.

    Details Tab

    From the Catalog Maintenance option, you can create new catalogs, update the catalog

    description and delete the catalog. Only the catalogs you are authorized as either the

    owner or administrator will been shown.

    Figure 26: Catalog Maintenance

    Adding a new Catalog

    To add a new Catalog, click the new button on the left side of the screen, near the top.This allows you to define the name of the Catalog.

  • 7/25/2019 Data Sync Users Guide v67

    39/59

    Copyright 2004, LANSA, Inc. 39All rights, domestic and international, reserved

    Catalogs Tab

    This tab shows the GTINs assigned to the specific catalog.

    Figure 27: Catalogs Tab

    Distri bution L ist Tab

    This tab allows the administrator(s) of the catalog to add and remove users from thecatalog. Users listed on the left have been authorized to the catalog. If the Admin box is

    checked, that user will also have administrative rights so they can add and remove GTINsfrom the catalog.

    To add a user to the catalog, select them at the right and click the

    button.

    To authorize All users to the catalog, select the *All Users entry.

  • 7/25/2019 Data Sync Users Guide v67

    40/59

    Copyright 2004, LANSA, Inc. 40All rights, domestic and international, reserved

    Figure 28: Distribution List

  • 7/25/2019 Data Sync Users Guide v67

    41/59

    Copyright 2004, LANSA, Inc. 41All rights, domestic and international, reserved

    My Workflow

    Overview

    If you are enrolled in Workflow, you will be automatically directed to your To Dos

    upon login. You may also view the page at any time by selecting To Dos afterclicking on My Workflow.

    To Dos displays all events that require your immediate attention. You can obtain

    information on each event by clicking on its Event ID. You can then issue a response

    indicating that you have taken action. Based on the workflow setup done in other menuchoices after clicking on Workflow Configuration, that event may then be passed on to

    the next individual in your User Group.

    You can use the To Dos list to glimpse into future events that will affect you as wellas review prior closed events that you were involved with, such as critically importantaudit trail information of the approval process.

    Setup of all the Workflow options as well as a detailed discussion of workflow concepts

    can be found in the LANSA document Data Sync Administrators Guide v66.

    Figure 29: To Dos

    To DosDisplay F ields

    As with other display lists, you can click on a column heading to sort the list by thatcolumn.

    Event IDis a numerically assigned number to each workflow event. When you click thislink, you are directed to the Master Worklist Manager Detail page.

    Statusshows you where this worklist event is in the process. The valid statuses are:

  • 7/25/2019 Data Sync Users Guide v67

    42/59

    Copyright 2004, LANSA, Inc. 42All rights, domestic and international, reserved

    Openmeans that the event is still active, either with a workgroup or anindividual user.

    Closedmeans that the event has been closed, either directly by a user for theirindividual subscription or the last step in the workflow event has been completed.

    Futuremeans that the event has yet to require action by you.

    Retiredmeans that all actions for the event are complete.

    Event Date - Timeis when the event was triggered.

    Eventis the description of the workflow event. The GTIN is displayed if applicable.

    Action Takenrefers to your last action step on this event.

    Optionindicates the next action that you could take on this event. For example, youmight want to retire your closed events so they will no longer appear on the list. You can

    get back to them at any time by selecting the Retired status within the To Dos search

    options.

    To Dos Search

    Event IDallows you to search for a specific workflow event.

    Start Dateand End Dateenable you to search your To Dosby a specific dateor date range. Click the calendar icon to select your dates.

    Statusprovides a dropdown list of event statuses by which you can filter your ToDos.

    Event Typeprovides a dropdown list of all available events by which you canfilter your To Dos.

    Work fl ow Step Detail

    When you click on a row in your To Dos list, the Workflow Step Detail is displayedbeneath your list. SeeFigure 30: Workflow Step Detail. You can then review the

    details of a workflow event and respond to an action for which you are responsible.

    Within the detail page are all of the relevant event details, including the list of actionsthat need attention in order to fully resolve the event.

  • 7/25/2019 Data Sync Users Guide v67

    43/59

    Copyright 2004, LANSA, Inc. 43All rights, domestic and international, reserved

    Figure 30: Workflow Step Detail

    Work fl ow Step Detail Di splay Fields

    Initiated Byindicates the user that triggered this event and may include their contactphone number. The usersname is displayed as a mail to link.

    GTIN Affecteddisplays a link to the GTIN referred to by this workflow step, if any.

    When you click on the GTIN, you are taken to the Catalog Item Notification page for thisGTIN. You could then drill down to the GTIN Details page as needed in order tocomplete any work required so that you can satisfy this workflow step and respond to the

    action. You can return to this Workflow Step Detail page by clicking on Back toWorkflow Event ID:2580.

    This Step Statusindicates the status of this specific step, for a given user, within theworkflow from step to step.

    OPENmeans that at least one required action remains unresolved.

    CLOSEDmeans that all required actions have been resolved and you can retire

    this event if you wish.

    Event Specificsdisplays additional attributes that apply to each event definition. This

    will vary based on the attributes that may be appropriate to more fully describe any givenevent type.

    The bottom portion of the page shows a list of Required Actions related to the event as

    well as an Options Alloweddropdown that allows for the management of those actions.

  • 7/25/2019 Data Sync Users Guide v67

    44/59

    Copyright 2004, LANSA, Inc. 44All rights, domestic and international, reserved

    Required Actionsis a brief description of the actions to be carried out.

    Action Completed byis the name of the user responsible for this action. Once theuser has responded to the action in some way, the response and a date/time stamp will be

    shown here.

    Options Allowedis a dropdown from which you can select your response. The availableoptions are dependent on the event type and your level of authority.

    Approveindicates you have completed your due diligence and has approved thisaction step, thus passing control to the next user in the workflow (or closing the

    event if you are the last user in the group).

    Suspendindicates to the rest of the workgroup for this event that the userresponsible for the action requires additional time to review this step. Thesuspend status can also be used to enter notes regarding an action in progress.

    This option would then be followed by another response in order to move theworkflow along to the next step.

    Cancel Eventallows you to cancel the workflow event. This would be used if

    you feel that the event occurred in error or does not require completion throughthe remainder of the workflow steps.

    Pass Backallows you to pass control back to the previous action step so that theuser for that step can take another look.

    Roll Backapplies in the case of events that were triggered due to an attributechange. This option will allow you to set the attribute back to its original value

    and effectively cancel the event.

    Transfer To

    Just above the list of Required Actions you may see a Transfer todropdown. Thiswill contain the names of users to whom the responsibility for a task may be transferred.

    Only users with the same User Role that you have will be listed. This feature will notdisplay under the following conditions:

    If no other users exist with the same role.

    Your role does not have authority to the transfer option.

    To transfer responsibility to another user, just select a name from the list and click the

    Transfer button. This will close the event for you and alert the target user about the

    event.

  • 7/25/2019 Data Sync Users Guide v67

    45/59

    Copyright 2004, LANSA, Inc. 45All rights, domestic and international, reserved

    Messaging History

    Overview

    Every message sent to the Data Pool is logged at a very detailed level in LANSAs audit

    table. This information is the basis for non-repudiation. That is, neither the registry nor atrading partner can repudiate the fact that you successfully posted the message. Normallythis information does not have to be scrutinized. However, in the event that a trading

    partner claims they did not get a specific publication, then this information can be

    reviewed to establish the publication status.

    Figure 31: Messaging History

    Messaging H istory List PageDi splay Fi eldsMessage Idis the unique code assigned to the message prior to delivery to the Data Pool.When you click on a row in this list page, you will see the Message Inquiry details belowthe list.

    Message Typeindicates the action that was initiated that resulted in this message.

    Completedindicates where the message is in the processing cycle.

    SUCCESSFULindicates the processing cycle completed without errors.

    FAILEDindicates that the action requested by the message content did notcomplete due to one or more errors. You can see the error message returned bythe Data Pool by clicking on that row in the list; the Message Inquiry details

    below the list will show the error message.

    UNDERWAYindicates that the message has not yet completed the full cycle ofoutbound to the Data Pool, processed at the Data Pool, inbound to Data SyncDirect, and processed completely back into Data Sync Direct.

    There is a quick visual of the message status on the left side of each row youll see

    either or .

  • 7/25/2019 Data Sync Users Guide v67

    46/59

    Copyright 2004, LANSA, Inc. 46All rights, domestic and international, reserved

    Messaging H istory Search Component

    Immediately to the left of the Messaging History list is a filter panel where you canspecify search parameters or filter the content of the list. You can see the choices above

    inFigure 31: Messaging History.

  • 7/25/2019 Data Sync Users Guide v67

    47/59

    Copyright 2004, LANSA, Inc. 47All rights, domestic and international, reserved

    Publications

    Overview

    Every publication made to the Data Pool is logged at a very detailed level with Data Sync

    Directs audit table. This information is the basis for non-repudiation. That is, neitherthe Data Pool nor a trading partner can repudiate the fact that you successfully posted the

    publication. Normally this information does not have to be scrutinized. However, in the

    event that a trading partner claims they did not get a specific publication, then this

    information can be reviewed to establish the publication status.

    As shown inFigure 32: Publications,you can view a list of publications you have sent

    to your trading partners. You access the list by clicking on Propagations and thenPublications. By using the search criteria to the left of the list, you can reduce thequantity of data presented. Search options include GTIN, Information Provider GLN,

    Recipient GLN, and Publication Date.

    Figure 32: Publications

    Publ ications L ist PageDisplay Fi elds

    Information Provideris usually your companys GLN unless the product is aprivate label item that you set up on behalf of your retailer/customer.

    Recipient GLNis the GLN of the trading partner to whom the publication wassent.

    Dateis when the publication was sent from Data Sync Direct.

    In/Outwill display Inbound or Outbound, referring to whether you sent orreceived the publication.

    Initiated bydisplays the User ID of the person who initiated the action, the last

    action taken and the date the action was performed.

    ERP #displays your internal Product ID (which is not sent to the tradingpartner).

    Catalog I tem Notifi cation

    Because in Schema each publication of the same GTIN to different trading partners(GLNs) can potentially contain different attributes, Data Sync Direct captures the

  • 7/25/2019 Data Sync Users Guide v67

    48/59

    Copyright 2004, LANSA, Inc. 48All rights, domestic and international, reserved

    specifics of each publication. When you click on a row in the Publications Display List,

    the Catalog Item Notification page for that GTIN is displayed below the list ofpublications. SeeFigure 33: Catalog Item Notificationbelow. You can click on the

    GTIN to view the GTIN Details as they existed at the time you published the GTIN to

    that trading partner. You cannot update the details of the GTIN here, as you are simply

    viewing a historical record of the GTIN.

    Figure 33: Catalog Item Notification

  • 7/25/2019 Data Sync Users Guide v67

    49/59

    Copyright 2004, LANSA, Inc. 49All rights, domestic and international, reserved

    Confirmations

    Overview

    Trading partners who receive a publication can reply back to the sender, confirming the

    receipt of the publication. The Catalog Item Confirmation (CIC) is the recipient tradingpartners response to apublication from a source trading partner.

    The CIC is generated by the recipient trading partner and routed back to the source

    trading partner. The CIC document:

    acknowledges receipt of the distributed publication (CIN).

    indicates the recipient trading partners action taken against the Catalog Item.

    informs the source trading partner whether future Catalog Item changes shouldbe communicated to the responding GLN.

    communicates the specific reason why a Catalog Item is not being synchronizedor includes any other free-form note to the source trading partner regarding

    action taken on the Catalog Item.

    confirms successful synchronization with the source trading partner.

    You access the Confirmations page by clicking on Propagation and then Confirmations.When a trading partner receives your publication, they authorize or decline the message.

    The Confirmations page allows you to verify the trading partners confirmation status.

    Figure 34: Confirmations

    Confi rmations List PageDisplay Fi elds

    Information Provideris the GLN associated with the GTIN listedusually yourcompanys GLN, unless the product is a private label item that you set up on behalf ofyour retailer/customer.

    Responding Party GLNidentifies the trading partner who sent the confirmation.

    Dateis when the confirmation was processed.In/Outspecifies IN for confirmations that you have received and OUT for confirmationsthat you have sent.

    Statuswill contain one of four possible values, as defined by the Data Pool:

    Acceptedindicates that the the recipient trading partner is interested in theCatalog Item and wants to integrate it into their enterprise system. Any

  • 7/25/2019 Data Sync Users Guide v67

    50/59

    Copyright 2004, LANSA, Inc. 50All rights, domestic and international, reserved

    subsequent changes to the Catalog Item should be targeted to the recipient

    trading partner, as defined by their subscriptions.

    Rejectedindicates that the recipient trading partner is no longer interested inreceiving publications for this Catalog Item. When using the Rejectedconfirmation action, a reason must be provided.

    Reviewindicates that the recipient trading partner does not want to take aconfirmation action at the present time. Typically, the confirmation state will bechanged in the future by the recipient trading partner, as defined by their

    subscriptions. When using the Review confirmation action, a reason must be

    provided.

    Synchronizedindicates that the recipient trading partner has incorporated theCatalog Item into their enterprise system. Any subsequent changes to theCatalog Item should be targeted to the recipient trading partner, as defined by

    their subscriptions.

    Action Neededprovides instructions when the publication is not yet Synchronized.

    Creating Confi rmations

    If you are using Data Sync Directs workflow functionality, inboundpublications willtrigger a workflow event for subscribed users. Within the Worklist event, you can clickon a row for a Notification(s) Received event, and the Workflow Step Detail page will be

    displayed beneath the list. Then clicking on the GTIN will display the SendConfirmation page as shown inFigure 35: Send Confirmation.

    Note: The options available to you will depend on your role permissions.

    Figure 35: Send Confirmation

    To reply to the publication that you received, select the appropriate Status from the

    dropdownrefer to the list of Status definitions above. If you are sending a Rejected orReview response, also select a Reason from the dropdown list. You can alsocommunicate a Corrective Action from that dropdown. The Additional Info free-text

    field allows you to send specific, custom messages to the publications sender.

  • 7/25/2019 Data Sync Users Guide v67

    51/59

    Copyright 2004, LANSA, Inc. 51All rights, domestic and international, reserved

    Subscription Manager

    The workflow feature within Data Sync Direct allows users to be notified of events

    happening both within and external to the Data Sync Direct application. Data Sync

    Direct comes shipped with the most common GTIN life cycle events in which you would

    be interested. New events can be defined by the Data Sync Direct system administrator.There is a full discussion of the Subscription Manager and related concepts in theworkflow section within Data Sync Administrators Guide v66.

  • 7/25/2019 Data Sync Users Guide v67

    52/59

    Copyright 2004, LANSA, Inc. 52All rights, domestic and international, reserved

    RFCIN/CIS

    Overview

    You can request item information by submitting a Request for Catalog Item

    InformationRFCINto a trading partner or by submitting a Catalog ItemSubscriptionCISto the Data Pool.

    The Request for Catalog Item Notification is used when a recipient trading partner wishes

    to obtain Catalog Item information from source trading partners without setting up a

    permanent subscription. During the thirty-day period following submission of theRFCIN, the recipient trading partner may examine the item information it has received

    and determine if it wishes to continue to receive the Catalog Item data. While no actionis necessary to continue to receive item information, the submission of a Catalog ItemConfirmation (CIC) is recommended.

    After reviewing the publications during the 30-day temporary subscription, the recipient

    should confirm their desire to receive the information by issuing an Accept, Review, or

    Synchronization confirmation to the supplier. If the recipient decides not to continuereceiving the notifications, a Reject confirmation should be sent.

    Creating Requests and Subscri ptions

    You can access the RFCIN/CIS page by clicking on Propagation and then clicking onRFCIN/CIS. Since this option is role-based and depends on the authorities granted to

    your user ID, this option may or may not appear on your menu.

    Figure 36: RFCIN/CIS Manager

    From the dropdown, select the Schema-enabled GLN from whom you would like catalogitem information. You will then see a details page where you enter your request.

  • 7/25/2019 Data Sync Users Guide v67

    53/59

    Copyright 2004, LANSA, Inc. 53All rights, domestic and international, reserved

    Figure 37: RFCIN/CIS Manager: Details Page

    Enter either a specific GTIN via the Prompt button or select a Category from the SelectGPC code dropdown. Leaving both selections blank will generate a request for allGTINs from the trading partner. The ability to target specific GTINs or GPC Codes

    allows you to avoid the submission of broad, open ended requests that could reduce

    messaging resources and consume processing capabilities at the registry.

    If the information was previously received from the trading partner but you would like toreceive it again (if the data was erroneously deleted, for example), click the True radio

    button in answer to the Is Reload? question. The trading partner will then resend the

    GTIN information or all of the partners GTINs within the GPC Code. A temporary 30-day subscription will also be entered into the registry to facilitate your receiving the

    publications.

    If the information has never been received before, answer the Is Reload? question False.The trading partner will then send information for all of their GTINs within the GPCCode specified. A temporary 30-day subscription will also be entered into the registry tofacilitate the receiving of the publications.

    If previous requests have been made by or to the selected trading partner, they will appear

    in the bottom portion of the screen. The GTIN or GPC Code, Reload status, DateRequested, GLN of the requester, Inbound/Outbound type, and Requested by User are

    displayed for each request.

    If the request has not yet been sent, press Add Request to submit the request to the

    trading partner.

    Note: Catalog Item Subscriptions are stored in a subscription table at the DataPool. The individual trading partners will not receive a subscription record intheir Data Pool work list.

  • 7/25/2019 Data Sync Users Guide v67

    54/59

    Copyright 2004, LANSA, Inc. 54All rights, domestic and international, reserved

    Dashboards

    Overview

    Dashboards give a quick glance at key pieces of information within your Data Sync

    Direct System. Key indicators and key transactions are highlighted.

    Figure 38: Dashboard Home

    Home This allows the user to view multiple task in one page. The page is divided into four

    quadrants that the user can personalize. The user can choose among these views:

    o Trading Partner PublicationsThis displays the same view as seen in Trading Partner

    Publicationsunder Dashboard. The report is displayed in a graphical chart in different

    formats (Area, Bar, Bubble, Column, Line, Point, etc.)

    o Confirmations This can also be accessed in Confirmations under Propagation.

    Trading partners who receive a publication can reply back to the sender, confirming the

    receipt of the publication.

    o Most Recent Publications All recent publications made by the user are listed in this

    portion.

    o Recent ActivityThis displays the recent activity of the user.

    o GTIN Statistics This display can also be seen in GTIN Statistics under Dashboard.

    Reports are represented in a graphical chart in different ways.

  • 7/25/2019 Data Sync Users Guide v67

    55/59

    Copyright 2004, LANSA, Inc. 55All rights, domestic and international, reserved

    o LANSA SupportThe LANSA Support Website can also be accessed in the Home page

    that allows user to navigate the website for support.

  • 7/25/2019 Data Sync Users Guide v67

    56/59

    Copyright 2004, LANSA, Inc. 56All rights, domestic and international, reserved

    My User Information

    Overview

    Information about the user is displayed in this page. Details can be modified by clicking

    the Changebutton. The user will be notified via the Recent Activity Dashboard inreference to the selection made in the Show me whenportion.

    Figure 39: My User Information

  • 7/25/2019 Data Sync Users Guide v67

    57/59

    Copyright 2004, LANSA, Inc. 57All rights, domestic and international, reserved

    Utilities

    The Utilities menu allows you to perform many administrative tasks. You level of

    security with Data Sync Direct will control what functions are available to you. Take a

    look at the list of tasks you might access inFigure 40: Utilitiesbel


Recommended