The objective of this guide is to
facilitate the users to navigate through the IBM Global Data Synchronization
for WebSphere Product Center and identify and operate the main application
functionalities. The document guides you through the application features using
a step-by-step approach.
The intended audiences include:
o
Line of Business Users
o
Professional Services team
o
Technical Sales team
o
Sales team
o
Marketing team
The following
related IBM Global Data Synchronization for WebSphere Product Center
documentation is also available:
§
Installation and Configuration Guide
§
Customization Guide
§
Release Notes
This document uses the following
conventions:
|
Bold
font
|
Indicates
buttons, tabs, menus, and keyboard key names. For example, the Save
button.
|
|
Courier New font
|
Indicates
commands, directory names, user names, path names, and file names.
|
|
Italics font
|
Indicates
page names. For example, the Login page.
|
|
Note
|
Indicates
important or clarifying information including exceptions, interdependencies,
and special situations.
|
|
Tip
|
Indicates a
helpful action that will simplify or streamline the current procedure.
|
|
Term/Acronym
|
Description
|
|
CIC
|
|
|
CIN
|
|
|
CIP
|
|
|
CIS
|
|
|
CISR
|
|
|
Data Pool
|
Repository of data where trading partners can obtain, maintain,
and exchange information on items and parties in a standard format. In this
guide the term data pool implies the AGENTRICS data pool services.
|
|
Global Attributes
|
A global attribute indicates that the attribute is
relevant for business cases around the world, and can only have a single
value throughout the world.
(For example, GTIN)
|
|
Global-Local Attributes
|
A global/local attribute indicates that the field is
relevant for business cases around the world. Its definition is the same but
may have a different value depending on the geography. (For example, VAT tax
values, 1.00 in France, 1.05 in Belgium)
|
|
Global Location Number (GLN)
|
This is a unique 13-digit number used to identify a trade
location. The first seven digits represent the Company prefix, the next five
digits represent the trade location, and the last digit is the check digit.
|
|
Global Trade Item Number (GTIN)
|
This is a unique 14-digit number used to identify trade
items. The first 13 digits represent the item reference number and the last digit
is the check digit.
|
|
GS1 Response Messages
|
Response messages sent to confirm GS1 processing of the
CIS, CIC, and RFCIN messages. GDS does not support these messages via the
user interface today. However, with the correct profile setup at Agentrics, these
messages can be stored and accessed in the document store.
|
|
Information Provider (IP)
|
Information provider indicates the information owner. For
example, Distributor, broker, Manufacturer or Franchisee. The retailer could
receive information from both sellers and this field indicates the
information owner.
|
|
Local Attributes
|
A local attribute is only relevant in certain
geographical areas, and the values may change based on where the product is
offered for sale. (For example, green dot – only relevant in certain European
countries.)
|
|
Recipient
|
Party responsible for subscribing and receiving items
published to them by a Source. Also referred to as Buyer, Retailer or
Demand-Side
|
|
RFCIN
|
Request for Catalog Item Notification – GS1 message used
by a Recipient to request a copy of previously received items or to erase a
rejected status on an item.
|
|
Source
|
Party responsible for creating and publishing items to
Recipients. Also referred to as Supplier, Vender or Supply-Side.
|
|
Target Market (TM)
|
Geographic areas in which a trade item is available for
sale.
|
|
Trade Item
|
Any product or service for which there is a need to
retrieve pre-defined information and that may be priced, ordered or invoiced
at any point in any supply chain.
|
|
Trading Partner
|
A party to transactions in the supply chain, such as a
supplier (seller) or a customer (buyer)
|
Global Data Synchronization is
the process by which trading partners exchange basic information about products
on an ongoing basis. The information can be on price, party, and other
relationship-specific details. This process ensures that all stakeholders for a
product are kept in “sync” about the latest information on the product.
Global Data Synchronization
enables you to:
§
Reduce costs and increase competitiveness through the efficient
and accurate transfer and on going synchronization of information
§
Lay the foundation for future supply chain collaboration
initiatives which require that trading partners are in “sync” on the basic
product, price, party and relationship specific information
This section explains the messaging process between
IBM Global Data Synchronization for WebSphere Product Center and the AGENTRICS
Data Pool Services.
Messaging Process
Using the IBM Global Data
Synchronization for WebSphere Product Center, a trading partner (retailer) first
sends a Catalog Item Subscription (CIS) message to the AGENTRICS data pool
services requesting information about an item.
After receiving a CIS message, the
AGENTRICS data pool services processes the CIS requests and sends a Catalog
Item Subscription Response (CISR) to confirm that the subscription has been successfully
processed. Today, the GDS solution does not support response messages from GS1;
however, these messages are available in the doc. Store. The data pool then
sends the Catalog Item Notifications (CIN) with the subscription criteria. These
CINs are then received by GDS and processed to create notifications of different
types. The types of Catalog Item Notifications are:
§
Initial Load Publication
§
New Item Publication
§
Item Change Publication
§
Item Correct Publication
§
Item Delete Publication
The CIN messages are processed by
the IBM Global Data Synchronization for WebSphere Product Center application
and a Catalog Item Confirmation (CIC) message is sent back to the AGENTRICS
data pool services. The types of CIC messages that are sent by the application
are:
§
Review
§
Accept
§
Reject
§
Synchronized
The IBM Global Data Synchronization for WebSphere
Product Center enables the demand side trading partner (retailer) to perform
key business functions including managing trading partners, subscriptions,
messages, items, as well as running reports.
Below, please find an overview of the
GDS business process. This should help your users understand the order of activities
that will take place within the solution.
Note:
Sending a Request for Catalog Item Notification (RFCIN) as well as sending a
CIC Reject are additional processes that can be done via the Manage Messages
section of the solution.
This chapter describes the initial steps
to start working with the application, and provides basic navigational
information.
Topics include:
Log on to GDS
Navigation
Log on to GDS
To log on to the application:
Access the IBM Global Data
Synchronization for WebSphere Product Center application. The Login page
is displayed.
Login
Enter your user name and
your password in the Username and Password fields respectively.
Click 
. The Home page is
displayed.
Each of the modules are aligned with a
user’s role and responsibility. Access to the various areas depends on the
level of access assigned to your position and user ID.
This section describes the product
layout and the methods you can use to navigate through the IBM Global Data
Synchronization for WebSphere Product Center application.
The page comprises three segments:
§
Top Navigation Bar
§
Left Navigation Pane
§
Task Area
Each segment provides you with several
methods that allow you to access various pages and views.
Top Navigation Bar: This segment
provides tabs that allow you to navigate between various tasks, such as Manage
Items, Manage Messages, and so on.
Left Navigation Pane: This
segment is located on the left side of the home page. It displays the quick
links and quick search.
Task Area: This is the largest
segment on the page. When you select a tab or a link on any of the other
segments, the related page where you can perform tasks is displayed here.
This section provides information about
the icons used in the application.
|
Icon
|
Name
|
Description
|
|
|
Calendar icon
|
Use this icon to open a calendar and select a date.
|
|
|
Dismiss icon
|
Use this icon to dismiss a notification.
|
|
|
Edit icon
|
Use this icon to edit item or trading partner information
|
|
|
Look Up icon
|
Use this icon to select target markets and information
providers.
|
|
|
Next Step
|
Use this icon to move to the next step.
|
|
|
Previous Step
|
Use this icon to move to the previous step.
|
|
|
Refresh Icon
|
Use this icon to refresh the list of notifications
displayed on the notification pages.
|
|
|
Temporary GTIN icon
|
This icon represents a temporary GTIN. While creating an
item, if the user does not specify a GTIN, then a temporary GTIN is created
automatically by the application
|
|
|
Undo Icon
|
Use this button to undo the last action performed.
|
|
|
View Details icon
|
Use this icon to view the details of a trade item or
trading partner.
|
This chapter describes the home page of
the IBM Global Data Synchronization for WebSphere Product Center application.
This page acts as a dashboard that provides an overview of the number of
notifications related to publications, subscriptions, trade items, and trading
partners.
When you log on to the application, the
home page displays the number of notifications related to items, subscriptions,
publications, and trading partners by default.
The home page displays the following
tables:
Publication Requests – This table displays the
number of notifications that you have received or sent. This includes of
notifications related to:
§
Initial Load Publications
§
New Item Publications
§
Item Change Publications
§
Item Correct Publication
§
Item Delete Publication
§
Stop Synchronization
For more information
on viewing details of publications, refer to the Managing
Messages chapter.
Subscriptions – This table displays the
number of notifications received or sent for subscriptions. This includes
notifications related to:
§
Subscription Requests
For more
information on viewing details of subscriptions, refer to the Managing Subscriptions chapter.
Item Requests – This table displays the number of
notifications received or sent for trade items/hierarchies. This includes
notifications related to:
§
New Item Request
§
Item Change Request
§
Item Hierarchy Request
For more information on viewing details
of items, refer the Managing
Items chapter.
Trading Partner Requests - This table displays
the number of notifications received or sent for trading partners. This
includes:
§
New Trading Partner Requests
§
Trading Partner Change Request
For more
information on viewing details of Trading Partners, refer the Managing Partners chapter.
The Home page appears as shown.
Home Page
You can click on each of the displayed
links to view the related list of notifications. For example, if you click on
the Initial Load Publication link, the page which shows you the list of
notifications for Initial Load is displayed.
Quick
Search - The Quick Search option is displayed in the left navigation pane
on all the main pages. You can search by trade items or trading partners. Trade
items can be searched using GTIN or the GTIN Description (GTIN Name). Trading
partner can be searched using the GLN or the name of the trading partner.
Quick Search
This chapter describes the various tasks
related to managing publications within the IBM Global Data Synchronization for
WebSphere Product Center application.
You can view information on all
published items and request (publication) information on an item from your
trading partner.
The application receives publications
for new items and item hierarchies. You can receive publications as a New Item
or as an Initial Load. The items are published when the demand-side trading
partner(s) sends a request for publication to the supply-side. Only those items
that have been added to the data pool by a supply side user will be published
on the demand side.
Topics:
View Notifications
Request for Publication
Stop synchronization
Mass Review
Explore
Processing
Publication Messages
You can request for publications from
the Home page also. The options are displayed under Quick Links
on the left navigation pane.
View
Notifications
You can view all notifications related
to publications in the Notifications page. This page contains the
following tabs:
§
Initial Load Publication
§
New Item Publication
§
Item Change Publication
§
Item Correct Publication
§
Item Delete Publication
§
Stop Synchronization
To view the list of notifications for each of these publication
types, click on the corresponding tab. The Initial Load Publication tab
view is displayed by default.
To view the details of a notification,
click on the notification message. The details of that notification are
displayed.
Notifications
that are for information only can be viewed and deleted. To remove the
notification from the list, click on the Dismiss icon.
Request
for Publication
Request for Publication in the GDS
application facilitates the Request for Catalog Item Notification (RFCIN)
process. An RFCIN message is sent to your trading partners in the event that
you require a copy of an item(s) previously received or that you would like to
receive an item(s) that has previously been rejected.
If you would like to receive a copy of
previously received item(s), excluding any previously rejected item(s), then
you should note the “Is Reload” field as “True.” If you would like to also
receive previously rejected item(s) then you should Is Reload as False.
Reload True:
Receive copy of items previously received. Do not receive rejected items.
Reload False:
Receive copy of items previously received. Receive reject items.
To request for publications:
1.
From the Home page, go to Manage Messages>Request
for Publication. The Request for Publication page is displayed.
Request for Publication
2.
You can type values in any or all the following fields.
a.
In the GTIN field, type the global trade item number of
the item for which you want to receive publications. You can also select the
GTIN using the Lookup icon.
b.
In the GLN field, type the global location number. You can
also select the global location number using the Lookup icon.
c.
In the Target Market field, select the target market using
the Lookup icon.
d.
In the Category field, using the Lookup icon,
select the category to which the item belongs. When you click on the Lookup icon the
search screen is displayed.
Browse Category
Click on Search,
the search results are displayed in two views – List view and Tree View. Click
on the category code to select the appropriate Category from the search
results.
GPC List View
GPC Tree View
Note: For AGENTRICS,
only the GPC Categories are available for selection.
e.
If you want to clear the data in the Target Market and Category
fields, click on the Undo 
icon.
f.
Select New Item or Initial Load for the type of
publication that you want to receive for the item.
Note: An item that has not yet been published to any
trading partner is called a new item.
3.
A screen showing the details you have entered is displayed.
4.
Click Preview. A preview screen is displayed with the
information entered in the previous screen.
Request for publication preview
5.
Click Back to edit the information. Click Submit to
submit the information. A message confirming the request is displayed.
This completes the request for publication process.
Stop Synchronization
You can stop synchronization for items for
which you do not want to receive any more publications.
To stop synchronization:
1.
Click on Manage Messages > Stop synchronization. The Stop
Synchronization page is displayed.
Stop Synchronization
2.
Click on the Search Item button. A window where you can
search for the item is displayed.
Stop Synchronization - Search
3.
In the Search page:
a. In
the GTIN field, type the global trade item number of the item for which
you want to stop synchronization
b. In
the GLN field, type the GLN that you want to stop synchronizing items
with.
c.
Select the Target Market of the GLN that you want to stop
synchronizing items from.
d. Click
on the Search button. The search results are displayed in the Search Results
area.
4.
From the search results click on the GTIN that you want to stop
synchronization for. The details of the GTIN will be displayed.
Stop Synchronization – Selected GTIN details
5.
To stop the synchronization for that particular Item, click Submit.
A confirmation page is displayed.
6.
If you are sure of stopping the synchronization for that
particular Item, click Submit. A message is sent to the AGENTRICS data
pool services to reject the item. A notification that a reject message has been
sent to the AGENTRICS data pool services will be sent to the appropriate user(s). The status of the item is changed to “Stop
Synchronized”
After reviewing the Catalog Item Notifications that have
come in and either accepting, rejecting, or reviewing them, the Mass Review capability
allows you to take action on multiple items at once.
To mass review
an item:
Go to Manage
Messages>Mass Review. The search page is displayed. Search for the items
by specifying the search criteria.
i.
GTIN: Enter the GTIN number of the item you want to search for.
ii.
GTIN Name: Enter the GTIN name.
iii.
Target Market: Enter the target market, or click on the Lookup
icon to
search.
iv.
Publication Type: Select from the following options:
§
Initial Load
§
New Item
v.
EAN.UCC.Code: Enter the EAN.UCC.Code
vi.
Information Provider: Enter the GLN.
vii.
Action: Select from the following options:
§
Approval
§
Category Mapping
From the
search results select the items that you want to mass approve or categorize.
Once the items
are approved, individual notifications are sent for each item, for the items to
be enriched. For approval, these notifications
appear under the Manage Items> Notifications>Item Change Request
tab
If new item
publications are categorized then approval pending notifications are sent for
each publication. These can be viewed under the Manage Messages >
Notifications > New Item Publication
Explore
The IBM Global Data Synchronization for WebSphere
Product Center application offers two search options:
o
Basic Search – The Basic Search option is displayed by default
when you access a search page. This allows you to search for information
related to the section you are currently working on. For example, Manage Items
section.
o
Advanced Search – The Advanced Search option allows you to
perform a more detailed search.
To search for messages:
1.
In the Manage Messages tab view, click on the explore
link. The Explore Transactions page is displayed.
Explore Publications
2.
You can type search parameters in any or all the following
fields:
a. In
the Transaction ID field, type the ID of the publication that you want
to search for.
b. From
the Transaction Process drop-down menu, select the type of transaction.
Options available are:
§
Initial Load Publication
§
Item Change Publication
§
Item Correct publication
§
Item Delete Publication
§
New Item Publication
§
Stop Synchronization.
c.
In the Date range from and to fields, select the dates
using the Calendar icon.
d. From
the Transaction Status drop-down menu, select the status of the
transaction. Options available are:
§
Initial Load Publication Accept Message Sent
§
Initial Load Publication Approval Pending
§
Initial Load Publication Approved
§
Initial Load Publication Auto Enrichment Failed
§
Initial Load Publication CIN
§
Initial Load Publication Disapproved
§
Initial Load Publication Enrichment Completed
§
Initial Load Publication Enrichment Pending
§
Initial Load Publication Enrichment Skipped
§
Initial Load Publication Ignored
§
Initial Load Publication Internal Sync Done
§
Initial Load Publication Internal Sync Message Sent
§
Initial Load Publication Internal Sync pending
§
Initial Load Publication Message Failure
§
Initial Load Publication Reject Message Sent
§
Initial Load Publication Revalidated
§
Initial Load Publication Review Message Sent
§
Initial Load Publication Started
§
Initial Load Publication Supplier Agreed
§
Initial Load Publication Supplier Disagreed
§
Initial Load Publication Review Pending
§
Initial Load Publication Validation Failed
§
Initial Load Publication Validation Passed
3.
Click Search. The search results are displayed in the search
results area.
Tip: If you do not know the search values, you can type
the partial search criteria with the wildcard character (*) and click Search.
For example, if you do not know the GTIN, type 1*. A list of GTINs that start
with 1 is displayed in the search results area.
Validation
Process
All Publications go through a validation
process before proceeding further. There are 3 types
of validations done within the GDS solution
•System Validations
•Customer Specific Validations
•Data Pool Validations
Systems validations are
those validations that are required to process an incoming Catalog Item Notification
message and store into the GDS solution. The same validations are run for
every CIN type (ex. Initial Load/New Item).
These validations include:
a. Missing GPC Codes
b. Missing UDEX Codes
c. Status of the Trading Partner
d. Support for the GDS extension in the release – could
be a warning
e. Validate the hierarchy in the incoming CIN
f. Validate the mapping for the UDEX/GPC
code in the incoming CIN to the internal hierarchy.
Customer
specific validations are those validations
that customers can create and have configured into the solution during their implementation.
These are additional validations beyond system validations that customers would
like to enforce to ensure item information that does not meet their
requirements is not received in the GDS solution. Custom validations are
created at the application or organization level, not the user-level.
Initial Load is a synchronization message that is
received for a trade item that has already been published to you by the
supplier.
When an Initial
Load publication is received, the publication goes through the following steps
§
Validation
§
Approval
§
Enrichment
§
Synchronization
Validations for an initial load are:
1. Check
if trading partner is present and active in system
2. Check
if Trade Item already exists in system [at least one in the hierarchy needs
to be present]
3. Product
Type should be same for the trade item existing in system
4. If
the initial load has a UDEX Category Code, check if it is a valid code as per
the system
5. If
the above step is true, it should be same as the existing item
6. If
the initial load has a GPC Category Code, check if it is a valid code as per
the system
7. If
the code is UDEX, check if mapping exists between UDEX and the internal
hierarchy [internal can be set to UDEX, Internal or GPC]
8. If
a link is present, check if the link is valid
If the item fails validation, then a notification
“Review Incorrect Initial Load publication” is sent to the appropriate
user(s).
To review an incorrect initial load:
1.
Go to Manage Messages>Notifications. The Initial Load
tab view is displayed by default. Click on the notification “Review Incorrect
Initial Load publication” for the trade item that you want to validate. The details
of the failure are displayed.
2.
If the supplier has agreed to make the changes to the item, then
click Change Pending. The status of the item is changed to “Awaiting
Changes”. If the supplier resends the item as an initial load, the initial
load goes through an approval process again. The status gets changed
accordingly.
3.
If the supplier has disagreed to make the changes click Reject.
A reject message is sent to the AGENTRICS data pool services.
4.
Click Ignore to ignore the validation. No message will be
sent to AGENTRICS data pool services and the notification will be deleted.
5.
The initial load can fail at two levels: i) User level validation
ii) System Level Validation. If the initial load has failed only the user level
validations then, you can turn off the user level validation process and
revalidate the initial load. Click Revalidate to revalidate the initial
load.
6.
Click Cancel to exit the page.
To approve an initial load item:
1.
Go to Manage Messages>notifications. The initial load
tab is displayed by default. Click on “Initial Load Approval Pending” message
for the trade item that you want to approve. Both the old and new details of
the item are displayed.
2.
To approve the entire set of attributes click Approve all.
A notification “Initial Load Enrichment pending” is sent to the appropriate
user(s).
3.
Click Reject all Items if you want to reject all the
attributes of the item.
Enriching an
Initial Load
To enrich an item that passes Initial
Load validation:
1.
After successful approval of the item, Go to Manage
Items>notifications. Click on the Item Change Request tab notification
for the trade item that has to be enriched. The details of the item are
displayed.
2.
Enter the values for various fields under the Global
attributes tab.
3.
Under the variant attributes tab, enter the values for fields under
the various tabs. These tabs are displayed with respect to the attribute
collection and security configuration.
Note: For a detailed description of all the Trade Item
attributes refer to the current AGENTRICS Data Model document
4.
After enrichment is done for all items (in case it is a
hierarchy) click Done. A notification “Initial Load Publication
Synchronization Pending” is sent to appropriate user(s).
5.
If the enrichment is not complete and you want to save the item,
click Save.
Synchronizing an Initial Load publication
To synchronize an Initial Load
Publication:
1.
Go to Manage Messages>notifications. The Initial
Load Publication tab view is displayed.
2.
Click on the notification “Initial Load Publication
Synchronization Pending”. The details of the item are displayed.
3.
You can view the details of item under the Global Attributes,
Item Link, and Variant Attributes tab.
4.
To internally synchronize the item, click Internal
Synchronization Done. A Catalog Item Confirmation Synchronized
message gets sent out and the item will be internally synchronized. A
notification “Internal Synchronization Completed” is sent to the
appropriate user(s).
When a new item is published by the
supplier, a notification “New Item Published” is displayed under the new
item publication tab. The item has to go through the following steps.
§
Validation
§
Mapping new item to an internal classification
§
New item approval
§
Item enrichment
§
Item synchronization
Validation
When a New Item publication is received, the publication goes
through an internal validation process where the following should be checked:
1. Check
if the trading partner is present and active in system
2. Check
if Trade Item already exists in system [should not be present]
3. If
the new item has a UDEX Category Code, check if it is a valid code as per the
system
4. If
the new item has a GPC Category Code, check if it is a valid code as per the
system
5. Check
if extension is supported
6. If
link is present, check if link is valid
If the item fails validation, then a notification “Review
Incorrect New Item publication” is sent to the appropriate user(s). ).
Clicking on the notification displays the reasons for validation failure. The
user can take appropriate action and revalidate the publication.
Mapping new item to an internal classification
To map a new item to an internal
classification:
When a CIN is received, it contains a
GPC classification code, a UDEX classification code or both. These codes are
pre-set by the Data Pool. The User can categorize the item into an internal
category code based on convenience. There are 2 ways in which to categorize the
CIN, Automatic or Manual.
To
automate the categorization process, set the automatic mapping flags in the
gds.properties file during the configuration process.
The
Following properties control the automatic mapping of the internal category:
§
udex_to_internal_hierarchy_mapping = true
§
gpc_to_internal_hierarchy_mapping = true
If the system is unable to automatically
map to the primary internal classification scheme, a notification for category
mapping is generated and the user needs to manually associate the item with the
appropriate internal category.
To manually map a new item to an
internal category:
1.
Click on the Manage Messages link. The Notifications
page is displayed.
2.
In the New Item publication tab view, click on a
notification that has “New Item Category Mapping Pending” status. The Assign New Item to Category page containing the
details of the item is displayed.
New Item Publication – Details
3.
Click Edit. A screen where you search for the internal
classification is displayed. In the search results, the internal classification
list view is displayed by default. In this example Internal Classification is
set as UDEX classification. Refer to the related Installation, Configuration
and Administration Guide for more information on configuring
classifications.
UDEX Classification List View
4.
Select the category to which you want to map the item. The item
will be classified as per the selected internal category. The selected category
will be mapped and the item and will be displayed on the screen.
5.
Click Done. A notification “New item Publication Approval
Pending” is sent to the appropriate user(s). The notification is displayed
under the Manage Messages->Notifications-> New Item Publication tab.
Approving a New Item Publication
1.
Click on the Notifications link under the Manage
Messages view. In the New Item Publication tab view, click on the “New
item Publication Approval Pending” notification. The Approve New item Publication screen containing the
details of the item is displayed.
2.
To approve the item, click Approve. A notification “New
Item Enrichment pending” is sent to the appropriate user(s). The notifications
will appear in the Manage items -> Notifications -> Item Change Request
tab view.
Enriching a new Item.
To enrich a new item:
1.
Go to Manage Item>notifications. Click on the Item
Change Request tab. The Item Change Request tab view is displayed.
2.
Click on the item with the status as “New Item Publication
Enrichment Pending”. The Enrich Item attributes from New Item Publication
containing the details of the item is displayed.
3.
Enter the values for various fields under the Global
attributes tab.
4.
Under the Item links tab you can view the hierarchy
existing for that particular item. You cannot edit the item links.
5.
Under the variant attributes tab, enter the values for fields
under the various tabs. These tabs are displayed with respect to the attribute
collection and security configuration.
Note: For a detailed description of all the Trade Item
attributes refer to the latest AGENTRICS Data Model document
6.
To complete the enrichment for the item, click Complete
Enrichment. When all the users to whom an enrichment notification is sent,
complete the enrichment process, a notification “New Item synchronization
pending” is sent to the appropriate user(s).
7.
If you have not completed the enrichment and you want to save the
item, click Save.
8.
Click Cancel to exit without making any changes.
Synchronizing a New Item Publication
To synchronize a New Item Publication:
1.
Go to Manage Messages>notifications. Click on the New
Item Publication tab. The New Item Publication tab view is
displayed.
2.
Click on the notification “New Item Publication Synchronization
Pending”. The Internal Synchronization Pending for New Item Publication
page containing the details of the item is displayed.
Internal Synchronization Pending for New Item Publication
3.
You can view the details of item under the Global Attributes,
Item Link, TM/IP (variant) Attributes tab.
4.
To internally synchronize the item, click Internal
Synchronization Done. A Catalog Item Confirmation Synchronized
message gets sent out and the item will be internally synchronized. A
notification “Internal Synchronization Completed” is sent to the
appropriate user(s).
When a changed item is published by the
supplier, a notification “Item change approval pending” is displayed under the Item
Change Publication tab. The item has to go through the following steps.
§
Validation
§
Item Change Approval
§
Item enrichment
§
Item synchronization
Validation:
When an Item Change publication is received, the publication
goes through an internal validation process where the following should be
checked:
1. Check
if trading partner is present and active in system
2. Check
if Trade Item already exists in system [all items should be present]
3. Product
Type should be same for the published and existing trade items
4. If
UDEX Code is coming, check if it is a valid code as per the system
5. If
UDEX is coming, it should be same as the existing item
6. If
GPC Code is coming check if it is a valid code as per the system
7. If
UDEX is coming, check if mapping exists between UDEX and internal hierarchy
[internal can be set on UDEX, Internal or GPC]
8. If
link is present, check if link is valid
If the item fails validation, then a notification “Review
Incorrect Item Change publication” is sent to the appropriate user(s). Clicking
on the notification displays the reasons for validation failure. The user can
take appropriate action and revalidate the publication.
To approve a changed item:
1.
Go to Manage Messages>notifications. Click on the Item
change Publication tab. The Item change Publication tab view
is displayed.
2.
Click on the notification “Item change approval pending”. The Approve
Item Change page is displayed containing the details of the item is
displayed.
3.
To approve the entire set of attributes click Approve all.
A notification “Item Change Publication Enrichment pending” is sent to the
appropriate user(s). The notification can be viewed under Manage
Item->Item Change Request tab view.
4.
Click Reject all if you want to reject all the attributes.
To enrich a changed Item:
1.
Under the Manage Item tab view, click on Item Change Request
tab. The Item Change Request tab view is displayed.
2.
Click on the notification “Item Change Publication Enrichment
Pending”. The Approve Item Change>Item Change Publication Enrichment
Pending page containing the details of the item are displayed.
3.
Enter the values for various fields under the Global attributes
tab.
4.
Under the Item Links tab view, the hierarchy existing for
that particular Item is displayed.
5.
Under the variant attributes tab, enter the values for fields
under the various tabs. These tabs are displayed with respect to the attribute
collection and security configuration.
Note: For a detailed description of all the Trade Item
attributes refer to the latest AGENTRICS Data Model document
6.
To complete the enrichment process, click Complete Enrichment.
A notification “Internal Synchronization Pending for Item Change Publication”
is sent to the appropriate user(s). The notification can be viewed under the Manage
Messages->Item Change Publication tab view.
Synchronizing an Item Change publication
To synchronize an Item Change
Publication:
1.
Go to Manage Messages>notifications tab. Click on the Item
Change Publication tab. The Item Change Request tab view is
displayed.
2.
Click on the notification “Internal Synchronization Pending for
Item Change Publication”. The Approve Item Change> Internal Synchronization
Pending for Item Change Publication containing the details of the item is
displayed.
3.
You can view the details of item under the Global Attributes,
Item Link, TM/IP (Variant Attributes) tab.
4.
To internally synchronize the item, click Internal Synchronization
Done. The item will be internally synchronized. A notification “Internal
Synchronization Completed” is sent to the appropriate user(s).
When a corrected item is published by
the supplier, a notification “Item correct approval pending” is displayed under
the Item Correct Publication tab. The publication has to go through the
following steps.
§
Validation
§
Item Correct Approval
§
Item enrichment
§
Item synchronization
Validation:
When an Item Correct publication is received, the publication
goes through an internal validation process where the following are to be
checked:
1. Check
if trading partner is present and active in system
2. Check
if Trade Item already exists in system [all items should be present]
3. Product
Type should be same for the published and existing trade items
4. If
the publication has the UDEX Category Code, check if it is a valid code as per
the system
5. If
the publication has the GPC Category Code, check if it is a valid code as per
the system
6. If
the publication has a Udex Code, check if mapping exists between UDEX and
internal hierarchy [internal can be set on UDEX, Internal or GPC]
7. If
a link is present, check if the link is valid
If the item fails validation, then a notification “Review
Incorrect Item Correct publication” is sent to the appropriate user(s).
Clicking on the notification displays the reasons for validation failure. The
user can take appropriate action and revalidate the publication.
To approve a corrected item:
5.
Go to Manage Messages>notifications. Click on the Item
Correct Publication tab. The Item correct Publication tab
view is displayed.
6.
Click on the notification “Item correct approval pending”. The Approve
Item Correct page is displayed containing the details of the item is
displayed.
7.
To approve the entire set of attributes click Approve all.
A notification “Item Change Publication Enrichment pending” is sent to the
appropriate user(s). The notification can be viewed under Manage
Item->Item Change Request tab view.
8.
Click Reject all if you want to reject all the attributes.
To enrich a corrected Item:
1.
Under the Manage Item tab view, click on Item Change Request
tab. The Item Change Request tab view is displayed.
2.
Click on the notification “Item Correct Publication Enrichment
Pending”. The Approve Item Change>Item Correct Publication Enrichment
Pending page containing the details of the item are displayed.
3.
Enter the values for various fields under the Global
attributes tab.
4.
Under the Item Links tab view the hierarchy existing for
that particular Item is displayed.
5.
Under the variant attributes tab, enter the values for fields
under the various tabs. These tabs are displayed with respect to the attribute
collection and security configuration.
Note: For a detailed description of all the Trade Item
attributes refer to the latest AGENTRICS Data Model document
6.
To complete the enrichment process, click Complete Enrichment.
A notification “Internal Synchronization Pending for Item Change Publication”
is sent to the appropriate user(s). The notification can be viewed under the Manage
Messages>notifications>Item Correct Publication tab view.
Synchronizing an Item Correct publication
To synchronize an Item Correct
Publication:
1.
Under the Manage Messages view, click on Item Correct Publication
tab. The Item Correct Request tab view is displayed.
2.
Click on the notification “Internal Synchronization Pending for
Item Correct Publication”. The Approve Item Correct> Internal
Synchronization Pending for Item Correct Publication containing the details
of the item is displayed.
3.
You can view the details of item under the Global Attributes,
Item Link, TM/IP (Variant Attributes) tab.
4.
To internally synchronize the item, click Internal
Synchronization Done. The item will be internally synchronized. A
notification “Internal Synchronization Completed” is sent to the appropriate
user(s).
A supplier sends an item delete
notification to inform the trading partner to delete an item from the system.
When an item publication is processed in GDS, it has to go through the
following steps.
§
Validation
§
Item Delete Approval
Validation
When an Item Delete publication is received, the publication
goes through an internal validation process where the following is checked:
§
Check if Trade Item already exists in system [all items should
be present]
If the item fails validation, then a notification “Review
Incorrect Item Delete publication” is sent to the appropriate user(s).
Clicking on the notification displays the reasons for validation failure. The
user can take appropriate action and revalidate the publication.
To approve a deleted item:
1.
Go to Manage Messages>notifications. Click on the Item
Delete Publication tab. The Item delete approval pending notification
is displayed.
2.
Click on the notification “Item delete approval pending”. The Approve
Item Delete page is displayed containing the details of the items in the
publication.
3.
Click Approve to approve the item deletion. The item will
be marked as deleted.
4.
To ignore, click ignore. The item will retain its original
status and an ignore message will be sent to AGENTRICS
This chapter describes the various tasks
related to managing subscriptions within the IBM Global Data Synchronization
for WebSphere Product Center application.
Subscriptions
Subscription is a message used to
establish a request for the update of trade item information for a data
recipient on a continuous basis within Global Data Synchronization Network.
Subscriptions can be made based on any
one of the following criteria-- GTIN, Category of the item, GLN of Information
Provider, Category of the item and Target Market. Subscriptions remain valid
until they are deleted. Subscriptions can be created for any combination of
the above criteria expect for Category and GTIN.
Validations against overlapping
subscriptions are not supported.
You can add, delete subscriptions. You
can edit a subscription that has not yet been added to the data pool.
Note: If
you make changes to the GPC code or Trading Partner, your subscriptions will
need to be updated. If you have existing subscriptions for specific Trading
Partners or Categories and try to delete them from the GDS implementation, you
will have to update the subscriptions accordingly.
Topics:
View Notifications
Create Subscription
Edit Subscription
Delete subscription
Explore Subscriptions
You can view all notifications related
to subscriptions in the Notifications page. This page contains the
following tab:
§
Subscription Requests
Manage Subscription – Subscription Request
To view the details of a notification,
click on the notification message. The details of that notification are
displayed.
Notifications that are for information
only can be viewed and dismissed. To remove the notification from the list,
click on the Dismissicon.
Create Subscription
You can create a subscription to be
added the data pool, to receive publications for an item. The subscriptions can
be based on a combination of Recipient GLN along with either the GTIN, Target
Market, Category or Data Source, except Category and GTIN
GLN of Information Provider– This should be a valid
GLN.
GTIN – This should be a valid trade item number.
Target Market – This should be a valid target market
number.
Category – This should be a valid item category.
Data Source – This should be a valid GLN of the Trading
Partner
The IBM Global Data Synchronization for WebSphere
Product Center application stores all the subscriptions that you have
previously added to AGENTRICS data pool.
Note: If there is an existing record of the subscription
in the Agentrics data pool, you get an error message saying there is a
duplication of subscription.
To create a subscription:
1.
In the Manage Subscription tab view, click on the create
subscription link. The Create Subscription page is displayed.
Manage Subscriptions –Create Subscription
2.
Specify the recipient GLN number. Using the Lookupicon
select the GLN who is supposed to receive the subscription.
3.
Specify one or a combination of the following options except for
category and GTIN:
a.
Select GTIN. Using the Lookupicon select a GTIN.
The selected GTIN is displayed in the text box.
b.
Select Target Market. Using the Lookup icon
select a target market. The selected target market is displayed in the text
box.
c.
Select Category. Using the Lookup icon, select the
category to which the item belongs. When you click on the Lookup icon the search
screen is displayed
d.
Select GLN of Trading Partner. Using the Lookup icon,
select the data source to which the item belongs. When you click on the Lookup icon the
search screen is displayed
e.
You can also subscribe based on a particular GLN and Category
combination. Using the Lookup icon select a GLN. The selected GLN
is displayed in the text box. In the Category field, specify the
category for the GTIN using the Lookup icon.
4.
Click Create Subscription. A subscription is created. No
notifications are sent for the creation of a new subscription. The screen to
submit the subscription for approval is displayed.
Edit Subscription – Subscription Details
5.
Click Submit For Approval. A notification “Subscription
Approval Pending” is sent to the appropriate user(s). The notification is
displayed in the Subscription Requests
tab view
6.
Click Save, to save a draft of the subscription without
submitting it for approval.
7.
Click Delete to delete the subscription.
8.
Click Cancel to return the previous screen. The
subscription will not be saved.
To approve a new
subscription:
1.
In the Subscription Request tab
view, click on the notification “Subscription Approval Pending”. The details of
the subscription are displayed.
2.
To approve the subscription click Approve. The
notification message “Subscription approved” is sent to the appropriate user(s).
3.
To reject the subscription, click Reject. The notification
message “Modify Subscription Rejected” is sent to the appropriate users(s).
4.
The notifications are displayed in the Subscription Requests
tab view.
Edit Subscription
Note: You can edit only those subscriptions that have not
been added to the data pool.
To edit a subscription:
1.
In the Manage Subscription tab view, click on the edit
subscription link. The Edit Subscription page is displayed.
2.
Search for the subscription you want to edit.
3.
From the list of subscriptions choose the subscription that you
want to edit. The details of the subscription are displayed.
4.
Make the appropriate changes and click Submit For Approval.
A notification “Subscription Approval Pending” is sent to the appropriate
user(s). The notification is displayed in the Subscription
Requests tab view.
5.
Click Delete to delete the subscription.
6.
Click Save the save the changes without submitting for
approval.
To approve an edited subscription:
1.
In the Subscription Request tab
view, click on the notification “Subscription Approval Pending” for a
particular subscription that you want to approve. The details of the subscription
are displayed.
2.
To approve the subscription click Approve. The notification
message “Subscription approved” is sent to the appropriate user(s).
3.
To reject the subscription, click Reject. The notification
message “Subscription Rejected” is sent to the appropriate user(s).
4.
The notifications are displayed in the Subscription
Requests tab view.
Delete
Subscription
A subscription can be deleted when it is
any one of the following status:
Draft
Approved
Added
Delete Subscription – Subscription
in Draft status:
1.
Click on the Edit Subscription link, the Search Subscription
page is displayed.
2.
Search for the subscription you want to delete.
3.
From the search results select the subscription you want to
delete. If the subscription is in “Draft” status then, the details of the
subscription are displayed as shown in the following example.
4.
Click Delete. The subscription is deleted from the local
database.
1.
Click on the Edit subscription link, the Search Subscription
page is displayed.
2.
Search for the subscription that you want to delete. From the
search results select the subscription you want to delete. If the subscription
is in “Approved” status then, the details of the subscription are displayed as
shown in the following example.
3.
Click Delete and Submit For Approval. A notification
“Subscription Deletion Approval Pending” is sent to the appropriate user(s).
1.
Click on the edit subscription link, the Search Subscription page is displayed.
2.
Search for the subscription you want to delete. From the search
results select the subscription you want to delete. If the subscription is in
“Added” status then, the details of the subscription are displayed.
3.
Click Delete and Submit For Approval. A notification
“Subscription Deletion Approval Pending” is sent to the appropriate user(s).
The notification will appear under the Subscription Request tab.
4.
Click on the “Subscription Deletion Approval Pending”
notification. The details of the subscription will be displayed. Approve the
subscription.
To send
a deletion message for the approved subscription:
1.
Click on the edit subscription and search for the
subscription that you want to delete. The details of the subscription are
displayed. Click on Send Deletion Message. A deletion message for that
particular subscription is sent to AGENTRICS data pool services.
2.
Click Cancel to exit without making any changes.
To approve a deleted subscription:
1.
In the Subscription Requests
tab view, click on the notification “Subscription Deletion Approval Pending”.
The details of the subscription are displayed.
2.
To approve the deletion, click Approve. A notification
“Subscription Deletion Approved” is sent to the appropriate users(s).
Note: When you delete a subscription, it is locally
deleted in the application but will be permanently removed from the system only
after the system administrator runs the purge scripts. The subscription will no
longer appear in the search results.
Purge scripts
are written to physically delete subscriptions from the system based on the
status.
Subscription Deletion
Pre-condition:
The system
should have subscription(s) with ‘DELETED LOCALLY’ status.
If the subscription
status is ‘APPROVED’, and the user attempts to delete it item from the GDS UI,
it goes through the deletion approval process. Eventually, the subscription
status becomes ‘DELETED LOCALLY’. This means the subscription is logically
deleted from the system. In order to physically delete any subscriptions that
are in ‘DELETED LOCALLY’ status, purge script needs to be used.
Running the purge script:
1.
The purge script is located at
$GDS_INSTALL_DIR/src/db/schema/gds/purge_scripts/purge.sh.
2.
It is run by specifying the following command line parameters –
COMPANY_CODE, SCRIPT_PATH and USER_NAME
o
COMPANY_CODE – the target company on which the subscriptions need
to be purged.
o
SCRIPT_PATH – denotes the path of the script that corresponds to
the deletion type (subscription).
In this case SCRIPT_PATH is
$GDS_INSTALL_DIR/src/db/schema/gds/purge_scripts/subscriptionPurgeScript].
o
USER_NAME – The Admin user mentioned in the gds.properties file
3. Run Command:
purge.sh --script_path=<path/to/trigo/script>
--company_code=<code> --user_name=<username>
Post-Condition:
All
the subscriptions with status ‘DELETED’ are purged from the system.
To add a subscription to the data
pool:
1.
Under the Manage Subscriptions tab, click on the add subscription
link, the Search Subscription page is displayed.
2.
Search for the subscription that you want to add to the data
pool. From the search results select the subscription you want to add to the
data pool. The details of the subscription are displayed.
3.
Click
.
4.
Review the subscription and click on Submit to add subscription
to the data pool.
Note: Only subscriptions that have been approved status
can be submitted to the data pool.
The IBM Global Data Synchronization for WebSphere
Product Center application offers the basic search option for subscriptions:
Basic Search – The Basic Search option is displayed by default
when you access a search page. This allows you to search for information
related to the section you are currently working on. For example, Manage Items
section.
To search for subscriptions:
1.
In the Manage Subscriptions tab view, click on the explore
link. The Explore Transactions page is displayed.
Explore Transactions – Search Subscriptions
2.
You can type search parameters in any or all the following
fields:
a. In
the Transaction ID field, type the ID of the transaction that you want to
search for.
b. From
the Transaction Process drop-down menu, select the type of transaction.
The available transaction processes are Subscription Approval, Subscription Deletion
and Subscription Add.
c.
In the Subscription Date range from and to fields,
select the dates using the Calendar icon. The search results
displayed will be within this date range
d. In
the Subscription ID field, type the ID of the subscription that
you want to search for.
3.
Click Search. The search results are displayed in the search
results area.
Tip: If you do not know the search values, you can type
the partial search criteria with the wildcard character (*) and click Search.
For example, if you do not know the GTIN, type 1*. A list of GTINs that start
with 1 is displayed in the search results area.
This chapter describes the various tasks
related to managing trade items within the IBM Global Data Synchronization for WebSphere
Product Center application.
You can view and process information on
trade items and item hierarchies. You can create, edit, modify, or delete items
and item hierarchies as required.
Topics include:
View Notifications
Create Items
Edit Items
Create Hierarchy
Edit Hierarchy
Note: During application setup, you can create a list of
approvers for various item category+ target market+ information provider
combinations. You can also choose to turn the approval process on or off. For
more information, refer the IBM Global Data Synchronization for WebSphere
Product Center Installation and Configuration Guide.
You can create an item and edit an item
from the Home page also. The tasks are displayed in Quick Tasks
on the left navigation pane.
View Notifications
You can view all notifications related
to item requests in the Notifications page. This page contains the
following tabs:
§
New Item Request
§
Item Change Request
§
Item Hierarchy Request
To view the list of notifications for
each, go to Manage Items> Notifications and click on the
corresponding tab. The New Item Request tab view is displayed by
default.
Each notification is represented by a
GTIN. To view the details of a notification, click on the notification. The
details of that notification are displayed.
You can create an item by providing
basic information about the item. This creates a record of that item in the
item repository of the IBM Global Data Synchronization for WebSphere Product Center
application. You can then submit the item for enrichment. Users from different
departments can then add to the working record by providing additional
information about that item.
The item is validated and a working
record of the item is stored in the item repository of the IBM Global Data Synchronization
for WebSphere Product Center application.
Procedure
To create an item:
§
Create GTIN
§
Enrich Global Attributes
§
Create Item Links (Optional)
§
Create Variant
§
Enrich Local Attributes
§
Submit for Compliance Check
§
Submit for Approval
§
Approve Item
To create the GTIN code:
Go
to Manage Item > Create Item. The Create Item page is
displayed.
Manage Item – Create New Item
1.
From the EAN.UCC Code Type drop-down menu, select the
EAN.UCC code type.
2.
In the EAN.UCC Code field, type the EAN.UCC code.
3.
In the GTIN field, type the Global Trade Item Number of the
item.
4.
In the GTIN Name field, type the name of the trade item.
5.
Select the Core Extension as FMCG. Trade Items can be
created and saved without assigning any Core Extension.
6.
From the Product Type drop-down menu, select the indicator
for the trade item. Options available are Case, Pallet, Each, Pack, Display/Shipper,
Multi-pack, Set-pack, Pre-pack, Pre-pack/Assortment and Mod Pallet (Mixed).
7.
Under Classification Information:
Depending on the classification scheme configured there are
three types of classification schemes.
If internal classification scheme is set to internal
hierarchy, the user has his own way of classifying the items. The following
categories will be displayed while creating an item
·
Internal category
·
UDEX Category
·
GPC
If the internal classification is set to UDEX, the user has
opted for UDEX classification and he does not have his own way of classifying
the items. The following categories will be displayed while creating an item.
·
Internal Category (which will be the UDEX Category)
·
GPC
If the internal classification is set to GPC, then the user
has opted for GPC classification and he does not have his own way of
classifying items. The following categories will be displayed while creating an
item.
·
Internal category (set to GPC)
·
UDEX
To specify the code:
a. Specify
the code and the description for data pool category. To do this, click edit.
The search screen is displayed. Search for the required Code.
b. Click
on the category code. The UDEX List View is closed. The category code
and the description for that category are automatically displayed in the DataPool
Category [Code] and DataPool Category [Description] fields.
Search results-UDEX
List View
c.
Specify the code and the description for the Internal category.
To do this, click edit. The search screen is displayed.
d. The
search results are displayed under two views—Internal List View and Internal
Tree View
e. Click
on the category code. The Internal Classification List View is closed.
The category code and the description for that category are automatically
displayed in the Internal Category [Code] and Internal Category
[Description] fields.
f.
You can also select the category code from the tree view. Click
on the Internal Classification Tree View tab. The Internal
Classification Tree View is displayed.
g. If
the manufacturer is GS1 enabled then a third classification called Global
Product Classification (GPC) has to be specified. To specify the GPC code click
on edit and the search screen is displayed.
GPC List View
h. Click
on the GPC code. The GPC List View is closed. The GPC code and the
description for that category are automatically displayed in the GPC [Code]
and GPC Category [Description] fields. Mandatory if GS1 enabled
8.
Click Create GTIN. The GTIN is created and the message
“Item created successfully.” is displayed along with additional fields.
Manage Item – Item Created Successfully
Note: If a GTIN is not specified by the user then a
temporary GTIN is created based on the EAN.UCC.Code prefixed with an underscore
(‘_’). This GTIN is represented by the icon.
9.
You can enrich the global attributes or send the item for global
enrichment. You have to enter values in all the mandatory fields before
submitting for enrichment. The mandatory fields are Pack, Inner Pack, Brand
Name and Short Description. For information about enriching global
attributes, refer the section “Enrich Global Attributes”.
10.
To send the item for global enrichment, click Submit Global Attributes
For Enrichment. The notification message “Item Global Attribute Enrichment
Pending” is sent to the appropriate user(s) for global enrichment.
11.
Click Delete GTIN to delete the item that is created.
12.
Click Save GTIN to save the GTIN without submitting it for
enrichment.
Attributes for which you can enter more
than one value are known as multi value attributes. It can be Locale or
Language. You can add a new value to an attributes by adding a new occurrence
of the attribute.
To view a particular occurrence:
Select the occurrence in the drop down
and click Go. The screen containing the values of that occurrence is displayed.
You can also get to a particular
occurrence by clicking on the next and the previous icons.
To get to the first occurrence click on
the first icon and to get the last click on the last icon
To add an occurrence:
Click on the Add New Occurrence
icon.
A screen to enter the new values is displayed.
Enter the values in the required fields.
Click Save GTIN to save the information.
To delete an occurrence
From the drop down, choose the occurrence
that you want to delete.
Click the delete occurrence 
icon.
A prompt is displayed to confirm the deletion. Click Ok to delete.
When an item is submitted for global
enrichment, the appropriate user(s) are notified to enrich the item.
To enrich the global attributes:
1.
Go to Manage Item>notifications. In the New Item
Request tab view, click on the notification “Item Global Attribute Enrichment
Pending”. The details of the notification are displayed.
2.
Enter the values in the various fields.
Note: If you want to create trade item links, click on the
Item Links tab. This is optional. For more information, refer to the Create Item Links section.
3.
Click Done. The notification “Item Global Attribute
Enrichment Completed” is sent to the appropriate user(s). The notification is
displayed in the New Item Request tab view.
Note: If the notification for enriching the global
attributes is sent to more than one user, then only after all the users responsible
for enrichment click Done, the notification “Item Global Attribute
Enrichment Completed” is sent.
If only one person is responsible for enriching the
global attributes, then once the enrichment is complete, the notification is
sent out.
4.
Click Done. The notification “Item Global Attribute Enrichment
Completed” is sent to the appropriate user (s). The notification is displayed
in the New Item Request tab view.
You can create item links when enriching
global attributes or while enriching TM/IP variants. These links can be created
when creating a new item or creating a hierarchy. For information about creating
a hierarchy, refer the Create Hierarchy section.
To
create item links while creating a new item:
1.
Click on the Item Links tab. The Item Links tab
view is displayed.
Create new item - Item Links Tab View
2.
To add a parent GTIN, click add. The Search page is
displayed. Search for the GTIN that you want to add as a parent and click Next.
Note: For more information on creating links, refer to the
Create Hierarchy section under the same chapter.
3.
To add children to the parent GTIN, click add, The Search
page is displayed. Search for the GTIN that you want to add as a parent and
click Next.
4.
Click Save GTIN. The links are saved.
Note: If you are creating the links when enriching the
global attributes, the notification “Item Global Attribute Enrichment Completed”
is sent to the appropriate user. If you are creating the links when enriching
the TM/IP variants, the notification “Item Variant Attribute Enrichment
Completed” is sent to the appropriate user(s). These notifications are
displayed in the New Item Request tab view.
To create a Variant:
1.
Go to Manage Item> Edit Item. The Edit Item page
is displayed.
2.
Search for the notification for which you want to create a
variant. The search results are displayed in the search results area.
3.
Click on the GTIN. The details of the GTIN are displayed.
4.
Click Submit for Variant Creation. The notification
message “Item Variant Creation Pending” is sent to the appropriate user to
create the variant and the notification is displayed in the New Item Request
tab view.
Note: You can submit only those items for variant creation for
which the global enrichment is completed. However if the option for global
enrichment is turned off then the trade item can be directly submitted for
variant creation.
5.
If you receive “Item Variant Creation Pending” notification, click
on the notification message. The Variant Attributes tab view is
displayed.
Create Item Variant
6.
Click add variant. The Add Variant dialog box is
displayed.
Add Variant
7.
To add a target market:
a.
Click on the Lookup icon. The Target Market Search
page is displayed.
b.
You have two options:
i.
In the Search String field, type the name or first letter
of the target market along with the asterisk (*) and click Search. The
search results are displayed in the search results area.
ii.
Click on the alphabet from which the name of the target market
starts. For example, if the Target Market is Venezuela, click V. All
target markets that start with the letter V is displayed in the search
results area.
Target Market Search Results
c.
Select the target market. The selected target market is
displayed in the Target Market field.
8.
To add the IP GLN:
a. Click
on the Lookup icon. The Information Provider
Search page is displayed.
b. Perform
the search to display the search results.
Information Provider Search Results
c.
Select the GLN. The selected GLN is displayed in the IP GLN
field.
9.
Click Next. The Add Variant dialog box closes and
the variant is displayed in the Select Target Market and Select
Information Provider drop-down menus in the Variant Attributes tab
view.
Create Variant – Variant Selected
10.
The screen gets refreshed to display the attributes for the
selected target market and information provider. Enter the values in the fields
under the various tabs. Click on the Undo icon to clear a field.
11.
Click Save Variant. All the variant attributes that are entered
will be saved. The screen that allows you to submit this variant for enrichment
is displayed.
12.
Click Submit This Variant for Enrichment. The
notification message “Item Variant Attribute Enrichment Pending “is sent to the
appropriate user(s) to enrich the variant attributes.
Note: If you have access to enrich the local attributes,
you can fill in values in the various fields and then click on Submit This
Variant for Enrichment for other users to enrich the same.
The IBM Global Data Synchronization for WebSphere
Product Center enables users from different functional departments to add to
the working record of an item. For example, the Logistics attributes of the
item can be entered by a user from the Logistics department.
When an item is submitted for
enrichment, the appropriate user(s) are notified by email or online
notification to enrich the item. You can enrich the variant attributes (TM+IP)
for an item. These attributes are configurable and they have to be configured.
For information about configuring these attributes, refer the IBM Global
Data Synchronization for WebSphere Product Center Installation and
Configuration Guide.
The enriched item is validated to ensure
that it complies with the data validation rules. Once validated, it is approved
by the appropriate users before it is internally synchronized.
To enrich local attributes:
1.
Go to Manage Items>Notifications. Under the New Item
Request tab view, click on the notification “Item Variant Attribute Enrichment
Pending” for the item that you want to complete enrichment. The Variant
Attributes tab view is displayed.
2.
From the Select Target Market and Select Information
Provider drop-down menus, select the target market and information provider
for which you want to enrich the attributes. Click Go.
3.
The attributes for the selected target market and information
provider are displayed. Type in the values for the fields in the various tabs
and click Done. The notification “Item Variant Attribute Enrichment
Completed” is sent to the appropriate user.
Note: If you are not ready to commit the enrichment, click
Save Variant. This saves a draft copy of the item.
Submit
for Compliance Check
Once the enrichment of both the global
and variant attributes is complete, the item details have to be checked for
compliance. This is an internal validation that is performed to check if the
values that have been entered meet the data validation rules.
To submit an item for compliance check:
1.
In the Manage Item tab view, click on the edit items
link. The Search page is displayed.
2.
Search for the item that you have to send for compliance check.
The search results are displayed in the search results area.
3.
Click on the item that you want to submit for compliance check and
click Next. The Edit Item page is displayed.
4.
Click on the Variant tab. To select the variant that needs
to be submitted for compliance check, from the Select Target Market and Select
Information Provider drop-down menus, select the target market and the
information provider. Click Go. The screen that allows you to submit for
compliance check is displayed.
5.
Click Submit for Compliance Check. An internal validation
is performed on the values that have been entered for the various fields. Once
the item passes the compliance check, it has to be approved internally by the
appropriate user.
6.
If the item passes the compliance check an icon success is
displayed else an error icon is flashed. If the item does not pass the
compliance check one of the reasons could be that all the required fields are
not entered. Ensure that all the required fields are entered under all the
variant attributes tabs.
7.
Click Submit for Approval. The notification “New Item
Approval Pending” is sent to the appropriate user to approve the newly created
item.
To approve an item:
1.
In the New Item Request tab view, click on the
notification “New Item Approval Pending”. The details of the item are
displayed.
2.
From the Select Target Market and Select Information
Provider drop-down menus, select the target market and the information
provider that you want to approve. Click Go. The screen that allows you to
approve is displayed.
3.
To approve the item, click Approve. The notification
message “New Item Approved” is sent to the appropriate user(s).
To reject the
item, click Reject. The notification message “New Item Creation Rejected”
is sent to the appropriate user(s).
The notifications
are displayed in the New Item Request tab view.
Edit Items
An item that is not yet synchronized can
be edited. You can search for the GTIN, then edit the global attributes and the
TM+IP combination of that GTIN. Once edited, the changes have to be approved by
the appropriate users before they are committed.
To edit an item:
1.
Go to Manage Item> Edit Item. The Edit Item page
is displayed.
2.
Search for the item that you want to edit. The results of the
search are displayed in the search results area.
3.
In the search results area, click on the item that you
want to edit. The details of that item are displayed.
4.
Edit the values for the various fields as explained in the Create
Items section depending on the status of the item.
Note: If the item is in draft status then the Variant
attributes tab will not be displayed.
5.
After completing the changes click Save GTIN. A notification
“Modify Item Approval Pending” is sent to the appropriate users.
To approve an edited item:
1.
In the Item Change Request tab view, click on the
notification “Modify Item Approval Pending” for the item that you want to
approve. The details of the notification are displayed.
2.
To approve the item, click Approve. The notification
message “Edit Item Approved’ is sent to the appropriate user(s).
To reject the
item, click Reject. The notification message “Edit Item Rejected” is
sent to the appropriate user(s).
The
notifications are displayed in the Item Change Request tab view.
A GTIN or a TM+IP combination can be
deleted from the application, but it will be removed from the application only
after a purge program is run by the system administrator. If the GTIN is linked
to other GTINs, those links need to be deleted first.
Deletions should be approved by the
appropriate users before they are committed.
You can delete a GTIN only when you have
finished creating the GTIN and the message Item created successfully is
displayed.
1.
Go to Manage Item > Edit Item. The Edit Item
page is displayed.
2.
Search for the item that you want to edit. The results of the
search are displayed in the search results area.
3.
In the search results area, click on the item that you
want to delete. The details of that item are displayed.
4.
Click Delete GTIN. The notification message “Item Deletion
Approval Pending” is sent to the appropriate user(s) to approve the deletion of
the item.
To approve the deleted item:
1.
In the Item Change Request tab view, click on the
notification message “Item Deletion Approval Pending”. The details of the
notification are displayed.
2.
To approve the deletion, click Approve. The notification
message “Item Deletion Approved” is sent to the appropriate user(s).
To reject the
deletion of the item, click Reject. The notification message “Item Deletion
Rejected” is sent to the appropriate user(s).
Note: When you delete an item, it is locally deleted in
the application but will be permanently removed from the system only after the
system administrator runs the purge scripts. The item will no longer appear in
the search results.
Purge scripts
are written to physically delete trade items from the system based on the trade
item status.
Global Item Deletion
Pre-condition:
The system
should have global item(s) with ‘DELETED’ status.
1.
If the current global item (trade item without a variant) status is
‘DRAFT’, the trade Item can be physically deleted through GDS UI.
2.
If the global Item status is ‘REGISTERED’, and the user attempts to
delete the global item from GDS UI, it goes through the deletion approval
process. Eventually, the global item status becoming ‘DELETED’. This means the
global item is logically deleted from the system. In order to physically delete
any global items that are in ‘DELETED’ status, purge script needs to be used.
Running the purge script:
1.
The purge script is located at
$GDS_INSTALL_DIR/src/db/schema/gds/purge_scripts/purge.sh.
2.
Go to this directory.
3.
Its run by specifying the following command line parameters –
COMPANY_CODE, SCRIPT_PATH and USER_NAME
o
COMPANY_CODE – the target company on which the trade items need
to be purged.
o
SCRIPT_PATH – denotes the path of the script that corresponds to
the deletion type (global item/ variant/ trading partner/ subscription).
In this case
SCRIPT_PATH is
$GDS_INSTALL_DIR/src/db/schema/gds/purge_scripts/globalItemPurgeScript
o
USER_NAME – The Admin user mentioned in the gds.properties file.
4.
Run Command:
purge.sh --script_path=<path/to/trigo/script>
--company_code=<code> --user_name=<username>
Post-Condition:
All
the global items with status ‘DELETED’ are purged from the system.
Variant Deletion:
1.
If the current local item status is ‘DRAFT’ or ‘COMPLETE’, the variant
can be physically deleted through GDS UI.
2.
If the local Item status is ‘APPROVED’ or ‘REGISTERED’, and the user
attempts to delete it from GDS UI, it goes through the deletion approval
process. Eventually, the local item status becomes ‘DELETED LOCALLY’. This
means the local item is logically deleted from the system. In order to
physically delete any local items that are in ‘DELETED LOCALLY’ status, purge
script needs to be used.
Running the purge script:
1.
The purge script is located at
$GDS_INSTALL_DIR/src/db/schema/gds/purge_scripts/purge.sh.
2.
Its run by specifying the following command line parameters –
COMPANY_CODE, SCRIPT_PATH and USER_NAME
o
COMPANY_CODE – the target company on which the trade items need
to be purged.
o
SCRIPT_PATH – denotes the path of the script that corresponds to
the deletion type (global item/ variant/ trading partner/ subscription).
In this case
SCRIPT_PATH is: $GDS_INSTALL_DIR/src/db/schema/gds/purge_scripts/globalLocalItemPurgeScript.
o
USER_NAME – The Admin user mentioned in the gds.properties file
3.
.Run Command:
purge.sh --script_path=<path/to/trigo/script>
--company_code=<code> --user_name=<username>
Post-Condition:
All
the local items with status ‘DELETED LOCALLY’ are purged from the system.
You can create item hierarchies in the IBM
Global Data Synchronization for WebSphere Product Center application.
Once items have been created in the
system, you can link items to create item hierarchies. This link is a unique
relationship where the highest level GTIN in the link will have no parent and
the lowest level GTIN will have no children.
Ensure that the created items in the
hierarchy are in the right order. Only the items of the lower product type can
be the children of Items of higher product type (that is, a pallet is the
parent of a case and not vice versa). If they are not in the right order, an
error message is displayed. After item links are created, it has to be
approved by the appropriate user.
To create an item hierarchy:
1.
Go to Manage Item>Create hierarchy. The Search page
is displayed.
2.
Search for the GTIN for which you want to create links. The
search results are displayed in the search results area.
3.
Click on the GTIN that you want to add links to. The Items
Links For page is displayed.
4.
Click on the displayed GTIN. The following page is displayed.
Create Hierarchy
5.
Click on the GTIN, the details of the hierarchy are displayed
along with the icon that gives the product type of that particular item.
Create Hierarchy
6.
Select the GTIN and click Add Child to add a child to the
selected GTIN. The Search page is displayed. Type in the search
parameters and click Search. The search results display only those
GTIN(s) that can be children of the selected GTIN are displayed in the search
results area.
Search
7.
Select the GTIN(s) that you want to add as the child, and click Next.
The Add Links page displays the selected GTIN(s).
Create Hierarchy – Enter Quantity
8.
Type the quantity for the GTIN(s) in the text box and click Next.
The selected GTIN(s) and the quantity are displayed in the Items Links For
page.
Create Hierarchy – With Links
If you want to add more GTIN as links,
repeat the steps 6, 7, and 8.
To delete any link, select the GTIN and
click Delete Child Link. For more information about deleting item links,
refer the section Delete Item Links.
9.
Click Submit For Approval. The notification message “New
Item Link approval Pending” is sent to the appropriate user (s) to approve the
hierarchy. The notification is displayed in the Item Hierarchy Request
tab view in the Manage Item page.
Note: Approval can be turned on or off through the
configuration of the IBM Global Data Synchronization for WebSphere Product Center
application.
Approve New Hierarchy
To approve the created hierarchy:
1.
In the Item Hierarchy Request tab view, click on the
notification “Modify Item Link Approval Pending”. The details of the notification
are displayed.
2.
In the notification details screen, Click Approve to
approve the hierarchy. The notification message “Modify Item Link Approved” is
sent to the appropriate user(s).
To reject the
hierarchy, click Reject. The notification message “New Item Link
Rejected” is sent to the appropriate user(s).
These
notifications are displayed in the Item Hierarchy Request tab view.
Edit Hierarchy
An item link that is not yet added to
the data pool can be edited.. Once edited, the changes have to be approved by
the appropriate users before they are committed.
To edit an item hierarchy:
1.
Go to Manage Item > edit hierarchy tab. The Search
page is displayed.
2.
Type the search parameters in the fields and click Search.
The search results are displayed in the search results area.
3.
From the list of GTINs displayed select the GTIN for which you
want to edit the hierarchy and click Next. The Edit Hierarchy page
is displayed.
4.
Click on the displayed GTIN. The links for the selected GTIN is
displayed.
Edit Hierarchy – Item Links
5.
Select the GTIN and click Add Child to add a child to the
selected GTIN. The Search page is displayed. Type in the search
parameters and click Search. The search results are displayed in the search
results area. Only those GTINs that can be children of the parent GTIN are
displayed.
6.
Select the GTIN(s) that you want to add as the child, and click Next.
The Add Links page displays the selected GTIN(s).
Edit Hierarchy - Add Links
7.
Type the quantity for the GTIN(s) in the text box and click Save.
The selected GTIN(s) and the quantity are displayed in the Items Links For
page.
8.
To delete any link, select the GTIN and click Delete Child Link.
For more information about deleting item links, refer the section Delete Item
Links.
9.
Click Submit For Approval. The notification message “Edit
Item Link Approval Pending” is sent to the appropriate user to approve the
hierarchy. The notification is displayed in the Item Hierarchy Request
tab view in the Manage Item page.
Note: Approval can be turned on or off through the
configuration of the IBM Global Data Synchronization for WebSphere Product Center
application.
Approve Edited
Hierarchy
To approve the created hierarchy:
1.
In the Item Hierarchy Request tab view, click on the notification
“Edit Item Link Approval Pending”. The details of the notification are
displayed.
2.
In the screen where notifications details are displayed, Click Approve
to approve the hierarchy. The notification message “Edit Item Link Approved” is
sent to the appropriate user(s).
To reject the
hierarchy, click Reject. The notification message “Edit Item Link Rejected” is
sent to the appropriate user (s).
These
notifications are displayed in the Item Hierarchy Request tab view.
An existing item link can be deleted in
the system. An Item delete approval notification would be send to the
appropriate user(s). The item link delete will be successfully completed upon
approval by all the users
Note: Item
links in "Draft" state do not require approval. User having
"Delete Link" permission can delete item links in "Draft"
state.
Note: When you delete a parent item link, all the child
item links will also get deleted.
To delete item links:
1.
Go to Manage Item>edit hierarchy link.
2.
Search for the GTIN for which you want to delete item links. The
search results are displayed in the search results area.
3.
Select the GTIN that you want to delete links for. The details of
the hierarchy are displayed.
4.
In the Items Links For page, select the link that you want
to delete and click Delete Child Link. The Delete Child Links window
displays the links that you have selected.
5.
Select the child links that you want to delete and Click Delete.
The notification message “Item Link Deletion Approval Pending” is sent to the
appropriate user. This notification is displayed in the Item Hierarchy
Request tab view.
To approve the created hierarchy:
1.
In the Item Hierarchy Request tab view, click on the
notification “Item Link Deletion Approval Pending”. The details of the
notification are displayed.
2.
In the page where notification details are displayed, Click Approve,
to approve the deletion. The notification message “Item Link Deletion Approved”
is sent to the appropriate user(s).
To reject,
click Reject. The notification message “Item Link Deletion Rejected” is
sent to the appropriate user (s).
These
notifications are displayed in the Item Hierarchy Request tab view.
The IBM Global Data Synchronization for WebSphere
Product Center application offers two search options:
Basic Search – The Basic Search option is displayed by default
when you access a search page. This allows you to search for information
related to the section you are currently working on. For example, Manage Items
section.
Advanced Search – The Advanced Search option allows you to
perform a more detailed search.
You can perform the following:
Search Items
Browse Item
Search Item Transactions
Search Hierarchy
Transactions
To search for items:
1.
In the Manage Item tab view, click on the explore
link. The Explore Items page is displayed, with Search Item tab
view being displayed by default.
Search Item – Basic Search
2.
You can type search parameters in any or all the following
fields:
a. In
the GTIN field, type the Global Trade Item Number for the trade item.
b. In
the EAN.UCC Code field, type the EAN/UCC code or number required based on
the product type.
c.
In the GTIN Name field, type the name of the GTIN.
d. In
the Description field, type the description for the GTIN.
e.
In the Brand Name field, type the name of the brand.
f.
From the Product Type drop-down menu, select the type of the
product. Options available are Case, Display/ Shipper, Each, Mod Pallet
(Mixed), Package, and Pallet, Pre Pack/Assortment, Pre-Pack, Set-Pack.
3.
For a more detailed search, click advanced. Additional
fields where you can type in search parameters are displayed.
Search Items - Advanced
a. In
the Information Provider [GLN] field, type the global location number of
the information provider.
b. In
the Target Market field, click on add TM. The Target Market
selection screen is displayed.
Target Market – Search
c.
From the Target Market search screen,
select a target market.
d. In
the Information Provider [Name] field, type the name of the information
provider.
e.
In the Language Code field, type the language code.
f.
In the Brand Owner [Name] field, type the name of the brand
owner.
g. In
the DataPool Category [Code] field, type the DataPool Category code.
h. In
the DataPool Category Description field, type the description of the
DataPool Category.
i.
In the Internal Category Code field, type the internal Category
code.
j.
In the Internal Category Description field, type the description
of UDEX Category.
k. In
the Manufacturer [GLN] field, type the global location number of the
manufacturer.
l.
In the Manufacturer [Name] field, type the name of the
manufacturer.
m. From the
drop down for Ordering Unit Indicator, select Yes, No
4.
Click Search. The search results are displayed in the search
results area.
You can browse for an item according to
a)
UDEX Classification.
b)
GPC Classification
c)
Internal Classification
To browse for an item through internal
classification:
1.
Go to Manage Item>explore link. The Explore
Items page is displayed.
2.
Click on the classification tab that you want to browse . For
example the tab displayed in the following screen is the UDEX Classification
Tab.
The selected classification tree view is
displayed on the left of the screen. In the above example the UDEX
classification tree view is displayed. When you click on the EAN.UCC code, the
details of the item are displayed on the right of the screen.
3.
You can select the GPC Classification or Internal Classification
tabs to browse
Note: During installation and configuration of the
application, if the property BROWSE_HIERARCHY_DISPLAY is set to FALSE in the
file gds.properties then the classification tree will not be displayed.
To search for item transactions:
1.
Go to Manage Item>Explore. The Explore Item page
is displayed. Click on the Item Transaction Tab. The Item
Transaction view is displayed.
Search Item
2.
You can type search parameters in any or all the following
fields:
a. In
the Transaction ID field, type the ID of the transaction that you want
to search for.
b. From
the Transaction Process drop-down menu, select the type of transaction
process.
c.
In the Date range from and to fields, select the dates
using the Calendar icon.
3.
Click Search. The search results are displayed in the
search results area.
To search for hierarchy transactions:
1.
Go to Manage Item>Explore. The Explore Item page
is displayed. Click on the Hierarchy Transaction Tab. The Hierarchy
Transaction view is displayed.
Search Item Transaction
2.
You can type search parameters in any or all the following
fields:
a. In
the Transaction ID field, type the ID of the transaction that you want
to search for.
b. From
the Transaction Type drop-down menu, select the type of transaction.
c.
In the Date range from and to fields, select the dates
using the Calendar icon.
3.
Click Search. The search results are displayed in the
search results area.
Tip: If you do not know the search values, you can type
the partial search criteria with the wildcard character (*) and click Search.
For example, if you do not know the GTIN, type 1*. A list of GTINs that start
with 1 is displayed in the search results area.
This chapter describes the various tasks
related to managing trading partners within the IBM Global Data Synchronization
for WebSphere Product Center application.
A trading partner is an organization or an
individual with whom information or data is accessed or exchanged in the supplier
chain, such as a manufacturer (seller), retailer (buyer), or distributor.
You can view and process trading partner
requests. You can also create new partners or modify information on existing
partners.
Topics include:
View Notifications
Create Trading Partner
Modify Trading Partner
Delete Trading Partner
Explore
You can create and modify a trading
partner from the Home page. The tasks are displayed in Quick Tasks
on the left navigation pane.
View Notifications
You can view all notifications related
to trading partner requests in the Notifications page. This page
contains the following tabs:
New Trading Partner Request
Trading Partner Change Request
To view the list of notifications for
each, click on the corresponding tab. The New Trading Partner Request
tab view is displayed by default.
Manage Partner - Notifications
Each notification is represented by a
GTIN. To view the details of a notification, click on the notification. The Notification
Details page is displayed.
Notifications that are for information
only can be viewed and dismissed. To remove the notification from the list,
click on the Deleteicon.
Create Trading Partner
You can create a record of a trading
partner in the system where the data synchronization is performed. You can
specify the following information in the record:
Trading Partner Identification (GLN) - The trade location of
the trading partner.
Trading Partner Role – A role can be that of an exchange, a retailer,
a supplier, or a manufacturer.
Trading Partner Contact – The contact details of the trading
partner, such as telephone numbers and e-mail addresses.
Trading Partner Name and Address – The name and address of the
trading partner.
Last Changed Date – The date when the record was last updated.
To create a trading partner:
1.
Got to Manage Partner>create trading partner. The
Create New Trading Partner page is displayed.
Create New Trading Partner
2.
Type the trading partner information in the listed fields:
a. In
the Global Location Number field, type the global location number. This
is the unique 13-digit number used to identify a trade location.
b. In
the Trading Partner name field, type the name of the trading partner.
c.
From the GLN Identifier drop down, select the type of GLN identifier.
The options are Exchange, Manufacturer, retailer, Supplier.
d. From
the Trading Partner Status drop-down menu, select the status of the
trading partner. Options available are Active and Inactive.
e.
In the Trading Partner Effective start Date
field, click on the Calendar icon to select the start date.
f.
In the Trading Partner Address field, enter the address of the
trading partner.
g. Using
the Lookup icon choose the country of the
Trading Partner.
h. In
the Trading Partner State field enter the
state to which the trading partner belongs.
i.
In the Trading Partner Language, enter the preferred Locale of
the trading partner.
j.
In the Trading Partner Postal Code enter the Postal Code of the
trading partner.
k. From
the Trading Partner Status dropdown, select the status of the trading
partner.
l.
From the Time Zone drop-down menu, select the time zone relevant
to the trading partner. Options available are Eastern, IST, GMT, and Pacific.
m. From the
Partner Type drop-down menu, select the type. Options available are Trading
Partner and Information Provider.
3.
Click Next. The trading partner is created and the Contacts
table is displayed on the same page.
Create New Trading Partner - Contacts
4.
To add contact details, click Manage Contacts. Text entry
fields where you can add contact information are displayed.
Create New Trading Partner – Manage Contacts
5.
Type the contact details in the listed fields:
a. In
the Name field, type the name.
b. In
the Email field, type the email address.
c.
From the Role drop-down menu, select the role of the contact
person for that trading partner.
d. In
the Telephone field, type the telephone number.
6.
Click Save. The contact details are displayed in the Contacts
area.
To add
details of another contact, repeat steps 5 and 6.
To edit a
contact, click on the Edit icon
.
To delete the
contact information, click on the Delete icon
. The contact information
for that contact is removed from the Contacts area.
7.
When you finish adding contacts, click Partner Details.
The Create New Trading Partner page is displayed again. The contacts
that you have added are displayed in the Contacts area.
8.
After filling in the details for the trading partner, click Submit
for Approval. The notification “New Trading Partner Pending Approval” is
sent to the appropriate user for approval. The notification is displayed in the
New Trading Partner Request tab view in the Manage Trading Partner
page.
9.
If you have not finished adding the information, and you want to
save a draft version, click Save.
10.
To delete the trading partner, click Delete Partner.
When a new trading partner is sent for
approval, the notification to approve the new trading partner is displayed in
the New Trading Partner Request tab view.
To approve a new trading partner:
1.
In the New Trading Partner Request tab view, click on the
notification “New Trading Partner Pending Approval”. The details of the
notification are displayed.
2.
To approve the Trading Partner, click Approve. The
notification message “New Trading Partner Approved’ is sent to the appropriate
user(s).
To reject the
Trading Partner, click Reject. The notification message “New Trading
Partner Rejected” is sent to the appropriate user(s).
The
notifications are displayed in the New Trading Partner Request
tab view.
Edit Trading Partner
You can modify those trading partners
that are approved.
To modify the information of a trading
partner:
1.
Go to Manage Partner> Edit Trading Partner. The Edit
Trading Partner page is displayed.
2.
Search for the GLN that you want to modify.
3.
In the search results area, click on the GLN that you want
to modify. The details of that GLN (trading partner) are displayed.
4.
Click on Start Modification. The screen to modify the
trading partner details is displayed.
Edit
the trading partner information in the listed fields.
a. From
the Trading Partner Status drop-down menu, select the status of the trading
partner. Options available are Active and Inactive.
b. In
the Trading Partner Effective start Date field,
click on the Calendar icon to select the start date.
c.
In the Trading Partner Address field, enter the address of the
trading partner.
d. Using
the Lookup icon choose the country of the
Trading Partner.
e.
In the Trading Partner State field
enter the state to which the trading partner belongs.
f.
In the Trading Partner Language, enter the preferred Locale of
the trading partner.
g. In
the Trading Partner Postal Code enter the Postal Code of the trading
partner.
h. From
the Trading Partner Status dropdown, select the status of the trading
partner.
i.
From the Time Zone drop-down menu, select the time zone relevant
to the trading partner. Options available are Eastern, IST, GMT, and Pacific.
5.
To add or modify existing contacts, click 
. The
following page is displayed.
Modify Trading Partner – Manage Contacts
6.
To add a new contact:
a. In
the Trading Partner Contact/Name field, type the name.
b. In
the Trading Partner Contact/Telephone field, type the telephone number.
c.
In the Trading Partner Contact/Email field, type the email
address (optional)
d. From
the Trading Partner Contact/Role drop-down menu, select the role
of the contact person for that trading partner.
7.
Click Save. The contact details are displayed in the Contacts
area.
8.
To modify the existing contact details, click on the Edit
icon
for that contact. The contact details are displayed in the text fields. Update
the information, and click Save. The updated information for that
contact is displayed in the Contacts area.
9.
When you finish adding contacts, click Partner Details.
The Modify Trading Partner page is displayed again. The contacts that
you have added or updated are displayed in the Contacts area.
10. After
filling in the details for the trading partner, click Submit For Approval.
The notification message “Modified Trading Partner Pending Approval” is sent to
the appropriate user for approval. The notification is displayed in the Trading
Partner Change Requests tab view in the Manage Trading Partners
page.
11. If
you have not finished adding the information, and you want to save a draft
version, click Save.
12. To
delete the trading partner, click Delete Partner.
When a modified trading partner is sent
for approval, the notification for approving the trading partner is displayed
in the Trading Partner Change Request tab view.
To approve a new trading partner:
1.
In the Trading Partner Change Request tab view, click on
the notification “Modified Trading Partner Pending Approval”. The details of
the notification are displayed.
2.
To approve the Trading Partner, click Approve. The
notification message “Modified Trading Partner Approved’ is sent to the
appropriate user(s).
To reject the
Trading Partner, click Reject. The notification message “Modified
Trading Partner Rejected” is sent to the appropriate user(s).
The
notifications are displayed in the Trading Partner Change Request tab
view.
Delete Trading
Partner
You can delete trading partners that are in the
draft status or that has been approved. If a trading partner that is in
approved status is deleted, the deletion has to be approved by the appropriate
user(s) and purge scripts have to be run in order to remove the trading partner
completely from the system.
If the Trading Partner is
in Draft Status:
In the Create Trading Partners page, click on the Delete
Partner button
If the Trading Partner is in an approved state:
1.
Go to Manage Partner>Edit Trading Partner. The Edit Trading
Partner page is displayed.
2.
Search for the GLN that you want to delete.
3.
In the search results area, click on the GLN that you want
to modify. If the Trading Partner details are in an approved status, the
details of that GLN (trading partner) are displayed.
4.
Click on the Delete Partner button. A Notification stating
Trading Partner Deletion Pending Approval is sent to the appropriate
user(s). A notification is displayed in the Trading Partner Change Request tab
view.
To approve a deleted trading partner:
1.
In the Trading Partner Change Request tab view, click on
the notification “Trading Partner Deletion Pending Approval”. The details of
the notification are displayed.
2.
To approve the trading partner, click Approve. The
notification message “Trading Partner Deletion Approved’ is sent to the
appropriate user(s).
To reject the trading
partner deletion, click Reject. The notification message “Trading
Partner Deletion Rejected” is sent to the appropriate user(s).
The notifications are
displayed in the Trading Partner Change Request tab view.
Purge scripts
are written to physically delete trading partners from the system based on the
status.
Pre-condition:
The system
should have Trading Partner(s) with ‘DELETED’ status.
Trading Partner Deletion
If the Trading
Partner status is ‘APPROVED’, and the user attempts to delete the Trading
Partner from GDS UI, it goes through the deletion approval process. Eventually,
the Trading Partner status becomes ‘DELETED’. This means the Trading Partner is
logically deleted from the system. In order to physically delete any Trading
Partner(s) that are in ‘DELETED’ status, purge script needs to be used.
Running the purge script:
1.
The purge script is located at $GDS_INSTALL_DIR/src/db/schema/gds/purge_scripts/purge.sh.
2.
Run the script by specifying the following command line parameters –
COMPANY_CODE, SCRIPT_PATH and USER_NAME
o
COMPANY_CODE – the target company on which the trade items
need to be purged.
o
SCRIPT_PATH – denotes the path of the script that
corresponds to the deletion type (trading partner).
In this case
SCRIPT_PATH is
$GDS_INSTALL_DIR/src/db/schema/gds/purge_scripts/tradingPartnerPurgeScript.
o
USER_NAME – The Admin user mentioned in the gds.properties
file
3.
Run Command:
purge.sh --script_path=<path/to/trigo/script>
--company_code=<code> --user_name=<username>
Post-Condition:
All
the Trading Partner(s) with status ‘DELETED’ are purged from the system.
Explore
The IBM Global Data Synchronization for WebSphere
Product Center application offers two search options:
o
Basic Search – The Basic Search option is displayed by default
when you access a search page. This allows you to search for information
related to the section you are currently working on. For example, Manage Items
section.
o
Advanced Search – The Advanced Search option allows you to
perform a more detailed search.
You can perform the following:
Search Trading Partners
Search
Transactions
To search for trading partners:
1.
Go to Manage Partner>Explore. The
Search Trading Partner tab view is displayed.
Explore trading partners
2.
You can type search parameters in any or all the following
fields:
a. In
the GLN field, type the GLN of the trading partner.
b. In
the Partner Name field, type the name of the trading partner.
c.
For a more detailed search, click advanced. Additional fields
where you can type in search parameters are displayed.
Explore Trading Partner – Advanced Search
d. In
the Contact field, type the contact number of the trading partner.
e.
In the City [Name] field, type the name of the city to which the
trading partner belongs to.
f.
In the Country Code field, type the code of the country to which
the trading partner belongs to or select the country code using the Look Up
icon.
g. From
the Language drop-down menu, select the language of the trading partner.
3.
Click Search. The search results are displayed in the
search results area.
To search for transactions related to
trading partners:
1.
Go to Manage Partner>Explore. Click on the Search
Transactions tab.
Explore Trading Partner - Search Transactions
2.
You can type search parameters in any or all the following
fields:
a. In
the Transaction ID field, type the ID of the publication that you want
to search for.
b. From
the Transaction Type drop-down menu, select the type of transaction.
c.
In the Date range from and to fields, select the dates
using the Calendar icon.
d. Click
Search. The search results are displayed in the Details area.
Tip: If you do not know the search values, you can type
the partial search criteria with the wildcard character (*) and click Search.
For example, if you do not know the GTIN, type 1*. A list of GTINs that start
with 1 is displayed in the search results area.
The IBM Global Data Synchronization for WebSphere Product
Center application provides pre-defined report templates to facilitate
business reporting. You can use these report templates to complete data
synchronization tasks, perform business process analysis, and generate
management-level summary reports.
Topics:
Run Reports
You can generate the following reports:
§
Time taken to enrich a new item: This report provides the
analyst the time taken (i.e. typically average time) for the demand-side
trading partner to enrich a new item.
§
Time taken to approve an initial load item: This report provides
the analyst the time taken (i.e. typically average time) for the demand side
partner to approve an item for registration.
§
Time Taken to Enrich Variants – This report provides the average
time taken for the demand-side trading partner to enrich trade item variants.
§
Time Taken to Approve Item Change – This report provides you the average
time taken for the demand-side trading partner to approve a trade item
information change.
§
Time Taken to Enrich Global Attribute – This report provides the
average time taken for the demand-side trading partner to enrich global trade item
attributes.
§
Time taken to accept a publication: This report provides an
analyst the time taken (i.e. typically average time) for the customer to accept
an initial load, new item, item change of item correction publication.
§
List of Accepted/Rejected Publications - This report provides you
the list of trade items that were accepted or rejected by the trading partner.
§
Number of Publications received- This report provides the analyst
the number of new item/initial load/item modification publications (by GTIN)
that the demand side partner has received.
§
List of Publications pending authorization: These reports
provides the analyst the list of GTINS that were received as initial load/New
Items/Item Modification publication from supply partners and require approval.
§
List of erroneous publications pending changes from trading
partner: This report provides the analyst the list of messages that are
awaiting another message with the more accurate information
§
List of Items pending internal synchronization: This report
provides the analyst the list of messages that are awaiting another message
with more accurate information.
§
Time Taken to Approve Trading Partner change – This report
provides you the average time taken for the demand-side trading partner to
approve a trading partner information change.
§
User Activity – This report provides the activities of a user
over a period of time.
Run
Reports
Each report has a fixed set of parameters for which you
can enter values.
To run a report:
1.
In the Home page, click on the Run Reports tab. The
Reports Console page displays the list of reports that can be generated.
2.
Click on the type of report that you want to generate. For
example, if you click on the Time taken to approve initial load item link,
the page to enter details to generate the report is displayed.
3.
In the listed fields, type in the values for the parameters.
4.
Click Run Report. The Results page displays the
report based on the values specified.
The fields that are displayed for various reports and
the description for the same are provided in the table. You have to enter
|
Time taken to approve initial load item creation
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Target Market
|
Allows you to select the target market.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
Report By
|
Allows you to generate report for Date, Week, Month or
Internal Item Category.
|
|
Time taken to approve item changes
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Target Market
|
Allows you to select the target market.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
Report By
|
Allows you to generate report for Date, Week, Month or
Internal Item Category.
|
|
Time taken to enrich global attributes
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Report By
|
Allows you to generate report for Date, Week, Month or
Internal Item Category.
|
|
Time taken to enrich variants
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Target Market
|
Allows you to select the target market.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
Report By
|
Allows you to generate report for Date, Week, Month or
Internal Item Category.
|
|
Time taken to enrich a new item
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Target Market
|
Allows you to select the target market.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
Publication type
|
Allows you to select the type of publication
|
|
Report By
|
Allows you to generate report for Date, Week, Month or
Internal Item Category.
|
|
List of items pending internal synchronization
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Target Market
|
Allows you to select the target market.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
Time taken to approve trading partner changes
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Target Market
|
Allows you to select the target market.
|
|
Report By
|
Allows you to generate report for Date, Week, Month or
Internal Item Category.
|
|
List of accepted/rejected publications
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Target Market
|
Allows you to select the target market.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
Publication Type
|
Allows you to select the type of publication based on
which you want to generate the report. The available types of publication are
New Item, Initial Load, Item Change and Item Correct.
|
|
Authorization Response
|
Allows you to select the publication based on whether they
are accepted or rejected by the authorized person
|
|
Number of Publications received – New Item
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Target Market
|
Allows you to select the target market.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
Publication Type
|
Allows you to select the type of publication based on
which you want to generate the report. The available types of publication are
New Item, Initial Load, Item Change and Item Correct.
|
|
Number of Publications received – Initial Load
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Target Market
|
Allows you to select the target market.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
Publication Type
|
Allows you to select the type of publication based on
which you want to generate the report. The available types of publication are
New Item, Initial Load, Item Change and Item Correct.
|
|
Report By
|
Allows you to generate report for Date, Week, Month or
Internal Item Category.
|
|
List of publication pending authorization
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Data Pool Category
|
Allows you to search and select a Data Pool category.
|
|
Target Market
|
Allows you to select the target market.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
Publication Type
|
Allows you to select the type of publication based on
which you want to generate the report. The available types of publication are
New Item, Initial Load, Item Change and Item Correct.
|
|
Report By
|
Allows you to generate report for Date, Week, Month or
Internal Item Category.
|
|
List of erroneous publications pending changes from
trading partner
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
Information Provider
|
Allows you to select the information provider.
|
|
User Activity Report
|
|
Field
|
Description
|
|
From Date / To Date
|
Allows you to select the date between which the report is
to be generated.
|
|
User Activity
|
Allows you to select the activity of the user based on
which you want to generate the report
|
|
User id
|
Allows you to select a particular user id based on which
you want to generate the report
|
For more information on roles, refer to Appendix
B – Sample Scenarios-demand side in the IBM Global Data Synchronization
for WebSphere Product Center
Installation, Configuration, and Administration Guide. This appendix also
provides the list of accessible features and operations that can be performed
by the respective roles.
This appendix provides a list for all errors
potentially encountered when sending Global Data Synchronization Messages.
Topics
§
Error and Confirmation Messages Generated by IBM Global Data
Synchronization for WebSphere Product Center
§
Error and Confirmation Messages Generated by AGENTRICS data pool
services
This section lists the error and
confirmation messages generated by IBM Global Data Synchronization for WebSphere
Product Center solution. Errors can include missing fields required by the
application, incorrect values, and so on.
|
Error Message
|
Description
|
|
invalid
notification
|
This
notification is no longer valid.
|
|
notification
not found
|
Notification
is not found for the given parameters.
|
|
access
error
|
Error
processing this page. Please try again.
|
|
invalid
notification
|
This
notification is no longer valid.
|
|
report
list failed
|
Could
not retrieve Reports List.
|
|
report
parameters
|
Could
not generate Report Input Parameters.
|
|
report
details
|
Could
not retrieve the Report Details.
|
|
no
input params
|
No
input parameters defined for this Report
|
|
duplicate
tradeitem
|
Same
Trade Item exists in the system
|
|
invalid
product type
|
Invalid
Product Type
|
|
invalid
classification
|
Invalid
Classification
|
|
invalid
category
|
Invalid
Category
|
|
action
not allowed
|
Action
not allowed for TradeItem
|
|
tradeitem
is not accessible
|
TradeItem
does not exist or user does not have enough privileges
|
|
Duplicate
GLN
|
Another
Trading Partner exists with the same GLN
|
|
Invalid
GLN
|
Invalid
GLN.
|
|
invalid
targetmarket
|
Invalid
Target Market
|
|
invalid
GTIN
|
Global
Trade Item Number is invalid
|
|
invalid
product type
|
Product
type is invalid.
|
|
invalid
uom
|
Invalid
unit of measure for the specified value.
|
|
base
unit indicator true
|
This
is a Required field, if the Base Unit Indicator is true
|
|
ordering
unit indicator true
|
This
is a Required field, if the Ordering Indicator is true
|
|
invalid
owning org GLN
|
The
Owning Organization has invalid Global Location Number
|
|
invalid
GLN
|
Global
Location Number is invalid
|
|
validate
Hi Ti Failed
|
It
is recommended that you populate this attribute, if Product Type is PL
(Pallet)
|
|
validate
num of Items per Pallet Failed
|
Do
not populate this attribute, if Product Type is PL (Pallet)
|
|
validate
product group id failed
|
This
is required when the Product Group ID Maintenance Agency attribute is
populated
|
|
validate
product group maint agency failed
|
This
is required when the Product Group ID Maintenance Agency attribute is
populated
|
|
validate
alt item maint agency failed
|
This
is required when Alternate Item Number is populated
|
|
validate
alt item failed
|
This
is required when Alternate Item Identification Maintenance Agency is
populated
|
|
validate
dimensions failed
|
The
Unit of Measure for depth, height, width and diameter must be consistent for
each Trade Item
|
|
validate
weight failed
|
The
Unit of Measure for gross weight, packaging weight, net weight and drained
weight must be consistent for each Trade Item
|
|
validate
peg failed
|
The
Unit of Measure for Peg Horizontal and Peg Vertical should be consistent for
each Trade Item
|
|
validate
tax rate failed
|
This
is required if the Tax Type attribute is populated
|
|
validate
tax type failed
|
This
is required if the Tax Rate attribute is populated
|
|
validate
trade qty failed
|
The
Unit of Measure must be consistent with order quantity for each Trade Item
|
|
validate
assoc qualifier failed
|
This
is required if Associated Item is populated
|
|
validate
assoc item failed
|
This
is required if Associated Qualifier is populated
|
|
validate
approval maint org failed
|
This
is required if Approval/Certification attribute is populated
|
|
validate
approval failed
|
This
is required if Approval/Certification Maintenance Organization attribute is
populated
|
|
validate
haz code failed
|
This
is required if Hazard mat class Code attribute is populated
|
|
validate
haz type failed
|
This
is required if Hazard Code attribute is populated
|
|
validate
prod size code failed
|
This
is required if Product Size Code Maintenance Agency attribute is populated
|
|
validate
prod size type failed
|
This
is required if Product Size Code attribute is populated
|
|
validate
mat code failed
|
This
is required if Material Code Agency attribute is populated
|
|
validate
mat code agency failed
|
This
is required if the Packaging Material Code attribute is populated
|
|
validate
list price failed
|
This
is required if List Price is populated
|
|
validate
color code failed
|
This
is required if Color Code Maintenance Agency attribute is populated
|
|
validate
color code maint agency failed
|
This
is required when the Color attribute is populated
|
|
mandatory
|
This
is a mandatory field.
|
|
invalid
packaging type
|
Invalid
packaging type
|
|
required
eanucc code type
|
EAN
UCC Code and EAN UCC Type is Required if the Product Type is Case or Each
|
|
invalid
eanucc code
|
EAN
UCC Code is invalid for the specified EAN UCC Type
|
|
required
eanucc code
|
This
is required if EAN UCC Type is populated
|
|
required
eanucc type
|
This
is required if EAN UCC Code is populated
|
|
past
date
|
Cannot
have past date
|
|
Future
date
|
Cannot
have future date
|
|
Availabilitydate
mismatch
|
Start
and end availability dates does not match.
|
|
shipdate
mismatch
|
First
and Last ship dates does not match
|
|
arrivaldate
mismatch
|
First
and Last arrival dates does not match
|
|
required
rs Price Basis Per Unit
|
This
is required if Recommended Sales Price is populated
|
|
required
rs Price Currency
|
This
is required if Recommended Sales Price Currency is populated
|
|
required
orderable
|
This
is required if Trade Item is Orderable
|
|
required
distributor attributes
|
This
is required if any retailer distributor specific attributes are populated
|
|
required
distributor Item Desc
|
This
is required if the Retailer Distributor Item Description attribute is
populated
|
|
required
distributor prop
|
This
is required if the Retailer Distributor Property attribute is populated
|
|
required
Trade Qty
|
This
is required if Maximum Order Quantity, Minimum Order Quantity, Minimum Ship
Quantity or Maximum Ship Quantity is populated
|
|
Hazard
Group Mandatory
|
This
is required if any of the following attribute is populated
|
|
Invalid
Value
|
Please
enter a valid value
|
|
Dependent
Fat Content
|
This
is required if the Fat Content attribute is populated
|
|
validate
peg failed
|
This
is required if the Tax Rate attribute is populated
|
|
required
base conc
|
This
is required if the Product is Base or Concentrate
|
|
required
prod strength basis
|
This
is required if the Product Strength attribute is populated
|
|
required
prod strength
|
This
is required if the Product Strength Basis attribute is populated
|
|
required
cert maint org
|
This
is required if Approval/Certification Maintenance Organization attribute is
populated
|
|
required
cert
|
This
is required if Approval Certification attribute is populated
|
|
AGENTRICS
WRE01 MANDATORY
|
This
is required if any of the following attribute is populated
|
|
WRE02
dependent not found
|
This
is required if any of the following attribute is populated
|
|
AGENTRICS
WRE03 MANDATORY
|
This
is required if any of the following attribute is populated
|
|
WRE04
dependent not found
|
This
is required if any of the following attribute is populated
|
|
WRE05
dependent not found
|
This
is required if any of the following attribute is populated
|
|
WRE06
dependent not found
|
This
is required if any of the following attribute is populated
|
|
WRE07
dependent not found
|
This
is required if any of the following attribute is populated
|
|
AGENTRICS
RETURNABLE PACKAGE DEPOSIT GROUP MANDATORY
|
This
is required if any of the following attribute is populated
|
|
AGENTRICS
COLOR GROUP MANDATORY
|
This
is required if any of the following attribute is populated
|
|
AGENTRICS
HAZARD GROUP MANDATORY
|
This
is required if any of the following attribute is populated.
|
|
AGENTRICS
PACKAGING GROUP MANDATORY
|
This
is required if any of the following attribute is populated
|
|
AGENTRICS
ZERO Gross Weight
|
Gross
Weight cannot be Zero
|
|
AGENTRICS
Gross Weight Invalid
|
Gross
Weight cannot be greater than Net Weight
|
|
AGENTRICS
INVALID COLOR LENGTH
|
Maximum
length for Color is 20 characters
|
|
AGENTRICS
INVALID DIAMETER
|
Diameter
value is either greater than 5 total digits or 3 decimals
|
|
AGENTRICS
INVALID GROSS WEIGHT LENGTH
|
Gross
Weight value either greater than 5 total digits to the left of decimal or
more 3 decimals
|
|
AGENTRICS
INVALID DRAINED WEIGHT LENGTH
|
Drained
Weight value either greater than 5 total digits to the left of decimal or
more 3 decimals
|
|
AGENTRICS
net Weight Invalid
|
Net
Weight cannot be less than Gross Weight
|
|
AGENTRICS
INVALID NET WEIGHT LENGTH
|
Gross
Weight value either greater than 5 total digits to the left of decimal or
more 3 decimals
|
|
AGENTRICS
INVALID SIZE METRIC IMPERIAL LENGTH
|
Value
either greater than 10 total digits to the left of decimal or more than 4
decimals
|
|
AGENTRICS
GREEN DOT INDICATOR MANADATORY
|
This
is required when Target Market is Germany
|
|
AGENTRICS
STACKING FACTOR MANADATORY
|
This
is required when Target Market is Belgium and Product Type is PALLET
|
|
AGENTRICS
INVALID LENGTH
|
Value
either greater than 5 total digits to the left of decimal or more 3 decimals
|
|
AGENTRICS
INVALID LENGTH 18
|
Value
is greater than 18 characters
|
|
AGENTRICS
INVALID EANUCCTYPE
|
WWREAGENTRICS
does not support the values U2, UK, UG, or UH
|
|
AGENTRICS
INVALID LENGTH 350
|
Value
is greater than 350 characters
|
|
AGENTRICS
INVALID LENGTH 35
|
Value
is greater than 35 characters
|
|
AGENTRICS
INVALID LENGTH 3
|
Value
is greater than 3 characters
|
|
AGENTRICS
INVALID LENGTH 4
|
Value
is greater than 4 characters
|
|
AGENTRICS
TRADEITEM GROUP DESCRIPTION MANDATORY
|
This
is required when Trade Item Group Code is populated
|
|
AGENTRICS
INVALID UOM
|
Unit
of Measure (UOM) must be same as Product Type
|
|
AGENTRICS
INVALID LENGTH 9 DIGITS
|
Value
is greater than 9 Digits
|
|
AGENTRICS
INVALID TAX RATE
|
Tax
Rate should be total 3 digits or 2 decimals
|
|
AGENTRICS
GTIN PALLET MANDATORY
|
This
is required when Product Type is Pallet
|
|
AGENTRICS
INVALID NONGTIN PALLET HITI
|
This
attribute must be blank
|
|
AGENTRICS
CASE GROUP MANDATORY
|
This
is required if any of the following attribute is populated when product type
is CASE
|
|
AGENTRICS
INVALID GTIN PALLET HITI
|
This
attribute must be blank
|
|
AGENTRICS
INVALID LENGTH 20
|
Value
is greater than 20 characters
|
|
AGENTRICS
INVALID LENGTH 30
|
Value
is greater than 30 characters
|
|
AGENTRICS
WRE02 MANDATORY
|
This
is required if List Price Effective End Date is populated
|
|
AGENTRICS
WRE04 MANDATORY
|
This
is required if Recommended Sales Price Effective End Date is populated
|
|
AGENTRICS
INVALID DRAINED WEIGHT
|
Value
either greater than either 5 total digits or 3 decimals
|
|
PRIMARY
DELIVERY METHOD INVALID
|
Primary
Delivery Method must be DSD, if DSDAttribute-PricingUPC field is populated
|
|
listpriceeffectivedate
mismatch
|
Start
and End List Price Effective dates do not match
|
|
recommendedsalespricedate
mismatch
|
Start
and End Recommended Sales Price dates do not match
|
|
listpriceeffectivedate
group validation
|
This
is required if any of the following attribute is populated
|
|
recommendedsalesprice
group validation
|
This
is required if any of the following attribute is populated
|
IBM may not offer the
products, services, or features discussed in this document in all countries.
Consult your local IBM representative for information on the products and
services currently available in your area. Any reference to an IBM product,
program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right
may be used instead. However, it is the user's responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.
IBM may have patents or
pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents.
You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
The following paragraph does
not apply to the United
Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS
MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply to you.
This information could include
technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions
of the publication. IBM may make improvements and/or changes in the product(s)
and/or program(s) described in this publication at any time without notice.
Any references in this
information to non-IBM Web sites are provided for convenience only and do not
in any manner serve as an endorsement of those Web sites. The materials at
those Web sites are not part of the materials for this IBM product and use of
those Web sites is at your own risk.
IBM may use or distribute any
of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who
wish to have information about it for the purpose of enabling:
(i)
the exchange of
information between independently created programs and other programs
(including this one)
(ii)
the mutual use of
the information which has been exchanged, should contact:
IBM Burlingame Laboratory
Director IBM Burlingame Laboratory
577 Airport Blvd., Suite 800
Burlingame, CA 94010
U.S.A
Such information may be
available, subject to appropriate terms and conditions, including in some
cases, payment of a fee.
The licensed program described
in this document and all licensed material available for it are provided by IBM
under terms of the IBM Customer Agreement, IBM International Program License
Agreement, or any equivalent agreement between us.
Any performance data contained
herein was determined in a controlled environment. Therefore, the results
obtained in other operating environments may vary significantly. Some
measurements may have been made on development-level systems and there is no
guarantee that these measurements will be the same on generally available
systems. Furthermore, some measurement may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify
the applicable data for their specific environment.
Information concerning non-IBM
products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not necessarily
tested those products and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those
products.
This information may contain
examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples may include the names of
individuals, companies, brands, and products. All of these names are fictitious
and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
All statements regarding IBM's
future direction or intent are subject to change or withdrawal without notice,
and represent goals and objectives only.
Programming interface
information, if provided, is intended to help you create application software
using this program.
General-use programming
interfaces allow you to write application software that obtain the services of
this program's tools.
However, this information may
also contain diagnosis, modification, and tuning information. Diagnosis,
modification and tuning information is provided to help you debug your
application software.
Warning: Do not use this
diagnosis, modification, and tuning information as a programming interface
because it is subject to change.
The following terms are
trademarks or registered trademarks of International Business Machines
Corporation in the United
States or other
countries, or both:
IBM
the IBM logo
AIX
CrossWorlds
DB2
DB2 Universal Database
Domino
Lotus
Lotus Notes
MQIntegrator
MQSeries
Tivoli
WebSphere
Microsoft, Windows, Windows
NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
MMX, Pentium, and ProShare are
trademarks or registered trademarks of Intel Corporation in the United States, other countries, or both.
Java and all Java-based
trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Other company, product or
service names may be trademarks or service marks of others.
