Product Info Effective Date changing after a discontinued date is entered and saved

[c2b30]

We are seeing a handful of publication Errors 635: discontinuedDateTime shall not be older than effectiveDateTime minus six months. Please help us understand why an EffectiveDateTime value would change after the originally population of the DSD GTIN Record becomes registered/listed. We are trying to figure out how to fix this issue, so the discontinued GTIN can be published to external recipients since the product is still out in the supply change and doesn't contain a "Last Ship Date".

[Theo]

Hello @c2b30 . Thank you for utilizing our customer community.

I have reviewed your question, and the system does not allow for a Discontinued Date that extends more than six months. This restriction applies only to dates in the past, not to dates in the future. Please see the attached screenshots for clarification.

 

[c2b30]

What I don't understand is that DSD has an effective date that is sent over in the CIC Item Modified Transaction Message, so why is 1WS IM populating the current date. See the logic below and please provide an explanation because this is causing us a huge issue for our discontinued GTINs.

Here is the logic written in the latest IM Participant Dictionary 8.65

Please note the default logic for this attribute (S1EFFDAT - GDSN BMS ID 144), as described below:

If a data source does not populate Effective Date when adding, modifying, or appending an item, 1WorldSync defaults this attribute to the current system date. The exception to this rule is when the Effective Date has been previously set to a future date (i.e., a date beyond the current system date). In that scenario, unless the “future” Effective date is updated by the data source, then that previously set future date will remain the Effective Date value (i.e., it will not default to the current system date). In other words, “future” Effective Date values will remain in effect until the next subsequent modification to the item AFTER the future date has lapsed into the past. At that point, the default logic explained above will apply unless the data source chooses to populate a new “future” Effective Date.

[CommunityJedi22]

Thank you for your detailed description.  We are looking into this and will get back to you soon.

[nancyVigo]

@c2b30, @CommunityJedi22 and @Theo, I'm not sure if this a similar case to the one we encountered after submitting a FUSE for the FSMA204 requirement.

Since all the Effective Date/Time were updated to the time we submitted the FUSE, I began seeing all kinds of error messages similar to this one because the Discontinued Date was overridden by the now Current Date.

[BLee]

Hi, can you describe to me how this is effecting the items that you have a discontinue date on?

[nancyVigo]

@BLee, for what I have understood, there cannot be a more current date than the discontinued date.

Once there is any update to a discontinued item (like the FUSE with FSMA204 attributes), it has created issues for me because the current date is automatically changed to the submission date. 

[Scott_Brown · Accepted solution]

c2b30,

Thanks for the note on this. Let me address both parts of your question separately. Then I can address how they combine in your error.

The Effective date relates to the product content which is presented in an outgoing message. it does not relate to when the product is available or when it was first published. Each time you change/update, save, or re-publish an item, the effective date has to be that date or a future date. The date previously used would be a date in the past and would not be allowed. 

The meaning of the Effective Date is the "date on which the content of the message can be used". Since the content is being updated or the item is being re-published, the content can only be available beginning on that date. 

You can set the Effective Date to be a date in the future. This allows for items to be sent over 60 or 90 days in advance of the date being used or in advance of a change.

Discontinue date is the primary date indicating the end of life of the item. Industry came together years ago and looked at business practices around the population of this date. At the time, it could not be a date in the past. It had to be the date of the save or a future date, much like Effective Date. Industry collaborated and agreed that most do not actually update their systems with discontinue dates that frequently. Most do batches 2-4 times a year. It was agreed to change the validation to allow discontinue date to be able to be populated with a date of up to 6 months in the past. This would allow companies to process batches of discontinued items 2ce per year.

For you issue when you make a change to the item, the effective date will change automatically to the date on which you are making the change. This is done systematically to represent the date from which this new set of data can be used. Then it is used as the baseline date for the discontinue date validation of not more than 6 months in the past.

I hope this helps.