| Description |
Issue happens when conversion team converts the inventory transactions first prior to converting the Contracts. We setup the commodities on i21 only upon Contracts conversion since it is not generally used if there are no contracts. Error below pops up when there are already inventory transactions since the commodity conversion is trying to update the assignment of commodities among the items used on the contracts. Hence, we cannot convert/import the contracts on such cases. This constraint constantly stops us to assign a commodity on items, even though it has blank commodity in the first place.
!pastedImage_d179400_0.png|height=422,width=560!
First option is to inform the conversion team to prioritize conversion of Contracts before converting actual transactions.
Second option, which is what this JIRA is for, is to disable the check constraint before doing the update of commodity on items, and then re-enable it right after that.
*STEPS*
1. Imports and Conversions.
2. Duplicate an item.
3. Create Inventory Receipt.
4. Verify details in duplicated item.
*ISSUE*
Unable to import Contract when Inventory transaction are already existing
*ACCEPTANCE*
The item must show an Error/Warning message that the commodity of item cannot be updated because there is already a transaction.
|