A trade hierarchy / channel is set to 'Lags behind' when a trade hierarchy is successfully published to a data channel and something is changed on the trade hierarchy which makes sure the trade hierarchy data is lagging behind in the data channel.
The Publication status widget
Whenever a trade hierarchy with status Draft, In revision or Released (so Archived is left out) is (going to be) published to a channel, you will notice the 4 icons to the left of the product Digital Life Cycle (DLC) status switch button; the publication status widget. These 4 icons are standing for all trade hierarchy channel combinations this product is part of.
So for example a product is part of 3 trade hierarchies.
- The first trade hierarchy is published to GS1
- The second trade hierarchy is published to GS1 and PS in Foodservice
- The third trade hierarchy is not published to a channel
The numbers in the publication status widget will in this case sum up to 3. For every trade hierarchy channel combination.
Explanation of the statuses
Not published
- The trade hierarchy is not yet published to the channel.
Latest
- The trade hierarchy is successfully published to the channel and it's the latest data which is published to the channel. The latest publication result is in this case 'Succeeded'.
- OR the user has just published the trade hierarchy to the channel, but there is no response yet. The latest publication result is in this case 'Pending'.
Lags behind
- The trade hierarchy is successfully published to the channel but it's NOT the latest data which is published. The data in the channel is so to say 'lagging behind' the data which is available in SyncForce. The latest publication result is in this case 'Succeeded'.
Failed
- The trade hierarchy publication to the channel failed. The errors can be checked on the 'Publication status' tab of the product. The latest publication result is in this case 'Failed'.
Clicking on the widget
Clicking on the widget opens the pop-up in which the trade hierarchies are listed with the channels:
Whenever the latest publication result is:
- Green
- and the text is 'Succeeded' and the trade hierarchy data is not lagging behind in this channel, the trade hierarchy cannot be published to the channel. There is no checkbox in front of the channel in the pop-up above.
- and the text is 'Pending', the trade hierarchy cannot be published to the channel. There is no checkbox in front of the channel in the pop-up above.
- Orange
- and the text is 'Succeeded' and the trade hierarchy data is lagging behind in this channel, the trade hierarchy can be published to the channel. There is a checkbox in front of the channel in the pop-up above.
- Red
- and the text is 'Failed', the trade hierarchy can be published to the channel. There is a checkbox in front of the channel in the pop-up above.
When is the trade hierarchy / channel combination set to 'Lags behind'?
There are a number of reasons why the trade hierarchy / channel combination is set to 'Lags behind':
- A product which is part of the trade hierarchy is released.
- So the product and the trade hierarchy are both released and successfully published to the channel. Something on the product got changed and therefor the Product Manager will release the product again. The released product data is now different from the product data which was sent to the channel and thus is the trade hierarchy set to 'Lags behind'. This is the case for any product in the trade hierarchy. So for multi product trade hierarchies, the release of each product in the trade hierarchy will trigger the 'Lags behind'.
- The Product Manager clicks for the product on 'Release for publication'. The trade hierarchy / channel combinations which were successfully published to the channel are set to 'Lags behind'. The Product Manager is prompted with the pop-up to right away publish the trade hierarchies to the channels. When the Product Manager does not click on 'Publish' but closes the pop-up, the trade hierarchy channels stay on 'Lags behind'.
- An item in the Bill of Materials is released
- So the product, the trade hierarchy and the packaging component linked in the Bill of materials (BOM) of the product are all on released. The trade hierarchy is successfully published to the channel. Something on the packaging component (from the BOM) got changed and therefor the Product Manager will release the packaging component again. The released data of the packaging component is now different from the product data which included in the publication of the product & trade hierarchy to the channel and thus is the trade hierarchy set to 'Lags behind'. This is the case for any components linked to the Bill of materials of the product in the trade hierarchy as for any components linked in the Bill of materials of the shipping units in the trade hierarchy.
- A channel is added to the trade hierarchy via the user interface or import
- A GS1 target is added to a Released trade hierarchy
- An inactive GS1 target is released for publication again
- An active GS1 target is changed (dates got changed)
- The trade hierarchy is released (from Draft)
- An archived trade hierarchy is released
- The trade hierarchy is released again (from In revision)
- The publication to the channel failed
- The data check failed
When is the trade hierarchy / channel combination no longer on 'Lags behind'?
The trade hierarchy / channel is no longer on 'Lags behind' when:
- The trade hierarchy is published successfully to the channel