Creating & Managing Publication Lists in IM

[CommunityJedi22]

Item Management offers users functionality to help with the process of publishing to multiple trading partners.  Create a List of Recipients with an easy-to-remember name and easily publish to the list your products to the same group of trading partners GLNs.  You can create multiple lists for different groups of GLNs for publication as needed.

You can share Lists with colleagues in your company.  Lists are only visible to the user who creates it if the list is marked as Private which is the default. If you want to share your list with another user from your own Company GLN, you can share the list with your company and other users within your GLN will see it.

If you have multiple GLNs and the user you want to share the list with is set up with a user id under another GLN, they can see the List if you share the list with All Companies. This will allow any user within any GLN to see and use the list.

Please click the attachment for more details on setting up your publication "Lists" in IM

To create a list, you have two options:

From the Dashboard menu > LISTS > click Items  > click New List  to create one

or

From the ITEMS list, by selecting the GTIN and using the Add to List option to add the GTIN to a new/or existing list:

1. Input all requested items that need updating: from the ITEMS List, you can select the GTINs that you need to maintain for a specific recipient and add them to the List you created for that recipient, using the Add to List option
2. Publish all in bulk -

Use the Publish option under LISTS > Items > Select the List  > click the Publish button:

Or you can click on the list to open it and see and select the GTINs that you want to publish, then click the Publish button

Please note that a List will be visible to the user account that created it, but a user can choose to share it with other users in the company, using the Share/Unshare function under LISTS > Items 

Please note, these were also called Market Groups in Classic IM.

[KataBumble]

Can lists be seen by all who access a company's item management platform or just by that user? For example, if I am making a brand list based say on size ie 50lb or 25lb.

Can others see it?

[Theo]

Hello @KataBumble, and thank you for utilizing our customer community.

After you create a list, all users with access to Item Management will be able to view it under the "Manage Item Lists" tab, as demonstrated in the screenshot below:

[KataBumble]

That's fantastic news! Thanks @Theo! 

[josejaramillo]

Can these lists be used to save/send an attribute change to a select Recipient, instead all recipients to whom that item has been published to in the past?

We will be handling a unique pallet configuration for customer/recipient X, which will differ from the pallet configuration we had to initially publish to them and that continues to apply to all other recipients.

I am trying to find a workaround that will allow me to change the pallet configuration attributes for just this single recipient X, and not send a Catalogue Item Notification to all the other recipients.

[ana_neamtu]

Hello, @josejaramillo, and welcome back!

An Item List can be used to Publish items in bulk. A Save on an item will trigger an update transaction to be sent to all Recipients to whom the item is successfully published.

Regarding the value sent for an attribute, you can provide different values for different Recipients only for the attributes or group of attributes that have a GLN qualifier. These are called RDD fields (Relationship Dependent Data). Such fields are “Product Description”, “Ordering Unit Indicator”, “First Ship Date/Time (Start Availability Date)” etc (if a GLN is not provided for these fields, the value applies to ALL )

You can verify if a field is RDD using the Item Managemnt Participant Dictionary at the link below as well > the IM Participant Dictionary tab contains the attributes that exist in Item Management> you can filter it by the attribute name in column C and check column U for the RDD value > Yes or No:
https://community.1worldsync.com/t5/IM-Participant-Dictionary/Current-IM-Participant-Dictionary-IMPD...

Have a wonderful day!

[josejaramillo]

Thank you @ana_neamtu for this clarification and guide.

I've checked as instructed and it seems the attributes I am interested in providing different values for (from the base profile) to only a specific Recipient are all in-fact Relationship Dependent Data (Y) types.
How, then, would I proceed to provides these Recipient-specified values to just this Recipient's GLN, but not trigger an update transaction to be sent to all Recipients to whom the item is successfully published?

[Val]

Hello @josejaramillo and thank you for the follow-up.

Any item Save will always trigger an auto-resync with all retailers the item is published to. There is no workaround this as this is the expected behavior of items published through GDSN.

As long as all attributes are retailer specific and can be added as such in Item Management, the data refresh should not interfere with all other publications to other retailers as the other data recipients receive the same information for your items again, without any changes. Thank you.

[josejaramillo]

Hello @Val , thank you for the clarification, understood on the expectations for an item Save.

However I don't follow on exactly on your second point, what data refresh are you referring to here, what would trigger such a data refresh?

Do you mean, for example, I could edit these retailer-specific attributes and Publish to a specific Recipient, without using an item Save prior to Publishing? So that the intended Recipient would receive the edited values on that Publication, but no auto-resync would be triggered for all other retailers the item is published to?

[Val]

Hello @josejaramillo and thank you for the follow-up.

Publishing data without Saving the item first is not possible, so any changes you would like to send to any retailer need to be preceded by an item Save, please. As long as the changes only affect RDD attributes, the other retailers will not see attribute changes, but they will receive the item information once again anyway and this cannot be blocked or stopped through GDSN. I hope this helps. Thanks.

[josejaramillo]

Hello @Val , thank you for the clarification.

So then, if I understand correctly, to achieve the editing of only RDD-attribute values for a specific Recipient only, I should:
1. Update the RDD attributes with values intended for specific Recipient

2. Save

3. Publish to intended Recipient GLN only

And by doing this I would expect that my intended Recipient GLN would receive the updated values on the Publication made to them, and all other retailers would only receive the same item information they already had again, with the same attribute values from before the edits made?

[Val]

Hello @josejaramillo and thank you for the follow-up.

As long as the item is already published, publishing again is not necessary as the new item attributes will sync automatically with the retailer upon Saving the item. Republishing is needed only if an item was initially Rejected. Otherwise, everything you mentioned applies and will work as intended, please. Thank you.

[josejaramillo]

Hello @Val ,

The item is already published to the intended Retailer and various other Retailers as well, yes.

But so if all I do is edit the RDD attributes and Save, at what point would I be indicating the edited values to go to only the intended Retailer? If I only Save, I believe the edited attribute values be sent to all retailers to whom the item has been published, which is not the intention here.

Would I need to do something prior to editing the RDD attribute values so that when I Save, the changes made only go to my intended Retailer?

[Val]

Thank you for the follow-up, @josejaramillo.

An attribute added as RDD will only be sent to the retailer that is filled out for that attribute. That is how the system is built intentionally. If it is not an RDD attribute, it will go to all retailers.

Here is an example:

Description 1 above goes to all retailers. Description 2 goes to Kroger only. Description 3 goes to Albertsons only. The retailer must be added next to the value intended for that retailer as RDD.

Thank you.

[josejaramillo]

Hello @Val , I see how you mean to do this now, thank you so much for your patience! This does seem to be exactly what I was looking to do and I've proceeded as such.  Thank you!

[Val]

It is a pleasure, @josejaramillo. Thank you for your questions and for clarifying this with us. 🙂