Hello Community!

Today I’m trying to insert some Units of Measure using Data Migration Manager. When I try to commit my changes, I see the error description “Method MODIFY failed : ORA-20122: IsoUnit.ERRUPDUSED: The field eUSED_IN_APPL] is not valid for update for user defined codes.” in those UoM that are user defined.

Any ideas how can I approach a solution for this? So far I tried setting the “USED_IN_APP” as “Out of Scope” in the Target Table definition but that doesn’t make any difference.

Hi ​@msurasky-price 

can you share the data file that you are  using and what are you going to update on those user define UOMs ?

Kind Regards!
Niyomal

Hi @NiyomalN, thanks for taking the time to look into this!

The Units of Measure Container was created to support another file (containing Master Parts). As you probably know, Master Parts have UoM as one of their properties and, when migrating those Master Parts, you perform a Basic Data Validation to make sure the Units of Measure exists in the Data Migration Manager project. 

In my migration, the Basic Data Validation was failing because I did not have (yet) the Units of Measure as “Approved” rows in the corresponding Basic Data Container (called ISO_UNIT). 

Following the documentation and training I did on this subject, I concluded that what I needed was to extract those units of measure in the Output Container (using the Extract basic data)…

After extracting those, I ended up with a Basic Data Container (ISO_UNIT) with rows for the units of measure that I had to deploy on the system (that corresponds with the print-screen I posted in my initial question) and it is when I tried to deploy those units that I got the error. I never had a “file” with these units per se. The units were extracted from the Master Parts.

Hi @NiyomalN, thanks for taking the time to look into this!

The Units of Measure Container was created to support another file (containing Master Parts). As you probably know, Master Parts have UoM as one of their properties and, when migrating those Master Parts, you perform a Basic Data Validation to make sure the Units of Measure exists in the Data Migration Manager project. 

In my migration, the Basic Data Validation was failing because I did not have (yet) the Units of Measure as “Approved” rows in the corresponding Basic Data Container (called ISO_UNIT). 

Following the documentation and training I did on this subject, I concluded that what I needed was to extract those units of measure in the Output Container (using the Extract basic data)…

After extracting those, I ended up with a Basic Data Container (ISO_UNIT) with rows for the units of measure that I had to deploy on the system (that corresponds with the print-screen I posted in my initial question) and it is when I tried to deploy those units that I got the error. I never had a “file” with these units per se. The units were extracted from the Master Parts.

​@msurasky-price  here is the trick, before 24R1 basic data validation was done against the basic data container,  that's why you need to extract and approve those data in order to pass the basic data validation in the out put container .

here is the trick that I do, if you know that the basic data is there in the target environment (most of the UOM and currency codes, country codes etc. are out of the box and is there in the application, some time you will need to set the flag “Used in application” to true). in that case, go the master part  target table definition and scroll right to see the column “validate basic data” for UOM row. and turn off the “validate basic data” toggle. this will remove the selected raw from basic data validation at the out put container and you  will not see the error and will be able to proceed without doing this.

only thing that you need to verify is that the basic data is in the target environment. from 24R1 you can validate basic data against the target environment directly.

Kind Regards!

Niyomal