2148552 - Item connector creates new items when the revision date is not provided for an update of an existing item -LMS

While attempting to update items through the Item Connector, the connector creates new items and inactivates the existing items.

SAP SuccessFactors Learning

1. Create an item data file for an item connector with 1 to 2 records.
2. Provide existing Item ID (CPNT_ID) and Item Type ID (CPNT_TYP_ID) but do not provide the REV_DTE (Revision Date for the items) in the item data file.
3. Save the data and upload the file on the SFTP server
4. Reschedule the Item Connector.
5. Search the item with old revision.
6. System inactivates the old item revision item and creates a new item with new revision date.

• There are 3 fields that must be provided in the item data file that identifies the item as unique. There are CPNT_ID, CPNT_TYP_ID and REV_DTE. If any of these data are different than the original item, system will identify it as a new item revision and hence it will create a new item and deactivate the old revision.
• If revision date field (REV_DTE) is not provided in Item connector data file then the connector defaults to the current runtime date. The revision date uses the database time zone.
• You can control the system action against the old revision with this Connector Property "item.connector.defaultValue.revision.inactivatePriorRevisions". You will find it in the Connector Property file.

• Provide the original creation date or last revision date of the item in Revision Date field (REV_DTE). Make sure the date has correct format according to the connector workbook.
• You may find how to get the correct revision timestamp by referencing 2168610

Examples with item.connector.defaultValue.revision.inactivatePriorRevisions setting:

1. item.connector.defaultValue.revision.inactivatePriorRevisions=Y

• Example 1: When Revision 1 of an item, say Item Rev1(Active) exists and you try to revise this item with Item Rev2 using connector, then if the flag value is Y, then after revision, Item Rev1 is made inactive and Item Rev2 is the active version.
• Example 2: When 2 revisions exist for an item, say Item Rev1(Active), Item Rev2(Active) and you try to revise this item with Item Rev3 using connector, then if the flag value is Y, then after revision, Item Rev1 and Item Rev2 are made inactive and Item Rev3 is the active version.

2. item.connector.defaultValue.revision.inactivatePriorRevisions=N
• Example 1: When Revision 1 of an item, say Item Rev1(Active) exists and you try to revise this item with Item Rev2 using connector, then if the flag value is N, then after revision, Item Rev1 remains active and Item Rev2 is also active.
• Example 2: When 2 revisions exist for an item, say Item Rev1(Active), Item Rev2(Active) and you try to revise this item with Item Rev3 using connector, then if the flag value is N, then after revision, Item Rev1 and Item Rev2 remain active and Item Rev3 is also active.

Connector, Item, revision created, new, modify update, inactivatePriorRevisions , KBA , LOD-SF-LMS-CON , Connectors , Problem