1 Solution
Accepted Solutions
In Item Management, look for publications, and let the drop open.
Then we open the Refine Search to filter as needed. This can be by Recipient, GTIN, or by date.
Check the box(es) and then click Withdrawal or Delete publication.
A Withdrawal Publication is used to withdraw a published hierarchy by performing a Publication Delete. The difference between Publication Delete and a Withdrawal is how the recipient sees this item flagged. If a Withdrawal is performed, it will tell the recipient they can expect to receive data on this item again.
Publications should only be deleted from IM to accomplish the following:
To stop synchronization with a recipient
To modify item links for published items
To change the Qty of Next Level Item(s) information on published items
To change the values of Consumer Unit Indicator, Base Unit Indicator or Special Item Code on published items
Per the GDSN process, it is required by the Source Data Pools to notify the data recipients who receive synchronization messages for such GTINs. The notification is in the form of a CIN ‘Delete’ message. In IM, the synchronizations (Master subscriptions) are time-scheduled to run at least once every 24 hours. Each Master subscription (1 for each data recipient) is setup differently and can range from every 2 hours to every 24 hours. It is therefore essential to prevent data sources from changing hierarchy related information before the CIN deletes are successfully sent to the data recipients, if synchronized. This will be achieved through the enforcement of a “pause” (before subsequent updates to specific hierarchy-related attributes) of up to 24 hours after performing a Publication delete transaction in IM. It is best practice to wait until after the 24-hour pause before publishing the item hierarchy again.
Due to the timing of job/file processing in IM, the total “pause” period could be as long as 25 hours. If a user is trying to re-initiate synchronization rather than update hierarchy-related attributes, then the “Publication Republish” functionality should be used instead of the “Publication Delete” functionality.
In Item Management, look for publications, and let the drop open.
Then we open the Refine Search to filter as needed. This can be by Recipient, GTIN, or by date.
Check the box(es) and then click Withdrawal or Delete publication.
A Withdrawal Publication is used to withdraw a published hierarchy by performing a Publication Delete. The difference between Publication Delete and a Withdrawal is how the recipient sees this item flagged. If a Withdrawal is performed, it will tell the recipient they can expect to receive data on this item again.
Publications should only be deleted from IM to accomplish the following:
To stop synchronization with a recipient
To modify item links for published items
To change the Qty of Next Level Item(s) information on published items
To change the values of Consumer Unit Indicator, Base Unit Indicator or Special Item Code on published items
Per the GDSN process, it is required by the Source Data Pools to notify the data recipients who receive synchronization messages for such GTINs. The notification is in the form of a CIN ‘Delete’ message. In IM, the synchronizations (Master subscriptions) are time-scheduled to run at least once every 24 hours. Each Master subscription (1 for each data recipient) is setup differently and can range from every 2 hours to every 24 hours. It is therefore essential to prevent data sources from changing hierarchy related information before the CIN deletes are successfully sent to the data recipients, if synchronized. This will be achieved through the enforcement of a “pause” (before subsequent updates to specific hierarchy-related attributes) of up to 24 hours after performing a Publication delete transaction in IM. It is best practice to wait until after the 24-hour pause before publishing the item hierarchy again.
Due to the timing of job/file processing in IM, the total “pause” period could be as long as 25 hours. If a user is trying to re-initiate synchronization rather than update hierarchy-related attributes, then the “Publication Republish” functionality should be used instead of the “Publication Delete” functionality.
