Story

As a admin, I would not like the vendor import process to update existing discontinue dates.

Details

Confluence: https://cfacorp.atlassian.net/wiki/spaces/IN/pages/53344825/Vendor+Item+Import
Update: Do not update Vendor Entity Item JP Edit 3/1/2021

In an effort to solve the UOM issue, a directive

{UpdateVendorEntityItem}

was added to the vendor item import. Once the import ran with this directive, all discontinue dates were updated to "Null". The result of this was all previously inactivated items were activated again. This was a bit of an issue for CFA.

In an effort to prevent this, we want to update the directive or vendor item import so that the discontinue date is never updated via the import if a discontinue date exists in our system. This decision was made because the discontinue dates should be handled by rules in the order guide and not by data from the import.

Also, it would seen that a future dated artifact (4712/12/31 00:00:00) was partially responsible for the update. CFA passed this waaaaaaay in the future value to us via the import and the dates were set to null. By ensuring that existing discontinue dates are never updated via import, the null problem is fixed and we don't have to worry about a date 2,691 years in the future. Chicken 4-Eva.

The rules of this directive should be updated so that:

If a record in our database includes an existing discontinue date, the date is not updated when the Vendor Item import is run.
Records that do not include an existing discontinue date are updated by dates provided in the Vendor Item import.

AC

Confirm

If a discontinue date of an item is not NULL in the InFORM database, do not update the discontinue date via the Vendor Item import.
If a discontinue date is NULL in the InFROM database, update the discontinue date via the Vendor Item import.