Skip to main content
Solved

Data Migration for PROD_STRUCTURE_HEAD

  • October 29, 2025
  • 3 replies
  • 71 views
M
Hero (Partner)
Forum|alt.badge.img+15

Hi All,

I’m trying to create a data migration job for the Product Structure Header.

When the structure type is ‘Manufacturing’ and if the record is already exists, I get an error ‘ORA-20112: ProdStructureHead.FND_RECORD_EXIST: The Prod Structure Head already exists.’ 

I have enabled modify option but it’s not letting me updating the record.

I would really appreciate it if there’s any other ways we can try to make this work, please.

 Already tried to get the idea from the below post and unfortunately it didn’t work for me.

Create Migration Jobs to Update Custom Fields(CF) | IFS Community

 

also tried the bellow API call in objid field

INTFACE_METHOD_LIST_API.GET_OBJID_FROM_KEY('PROD_STRUCTURE_HEAD', 'CONTRACT;PART_NO;ENG_CHG_LEVEL;BOM_TYPE_DB', CONTRACT||';'||PART_NO||';'||ENG_CHG_LEVEL||';'||BOM_TYPE_DB||';')


Thank you in Advance!

Best answer by FlorianTauber

Hi ​@MitDenukN,

thanks for sharing.

The root cause of the error message is most likely that the migration job cannot uniquely identify the record and therefore tries to create a new one.
In such cases, we need to review the key composition (flags P and K).

I assume that you are populating either BOM_TYPE or BOM_TYPE_DB in the source mapping.
For the column that is NOT being used, the K flag must be removed in the Method List Attribute (replace it with, for example, “-” or “x”).

Kind regards

3 replies

FlorianTauber
Hero (Partner)
Forum|alt.badge.img+6
  • FlorianTauber
  • Hero (Partner)
  • October 29, 2025

Hi,

pls share a screenshot from the Method List Attribute (RMB) on the Method in tab Method List.

 

KR

Regards, Florian from FLEXiCODE
M
Hero (Partner)
Forum|alt.badge.img+15
  • MitDenukN
  • Author
  • October 29, 2025

Hi ​@FlorianTauber , thank you so much for you quick response, the current method list looks like bellow:

 

 

FlorianTauber
Hero (Partner)
Forum|alt.badge.img+6
  • FlorianTauber
  • Hero (Partner)
  • Answer
  • October 30, 2025

Hi ​@MitDenukN,

thanks for sharing.

The root cause of the error message is most likely that the migration job cannot uniquely identify the record and therefore tries to create a new one.
In such cases, we need to review the key composition (flags P and K).

I assume that you are populating either BOM_TYPE or BOM_TYPE_DB in the source mapping.
For the column that is NOT being used, the K flag must be removed in the Method List Attribute (replace it with, for example, “-” or “x”).

Kind regards

Regards, Florian from FLEXiCODE
M
M
Hero (Partner)
Forum|alt.badge.img+15
  • MitDenukN
  • Author
  • October 31, 2025

Hi ​@FlorianTauber, appreciate your help and your suggestion solved the issue.

FlorianTauber
Terms & ConditionsCookie settingsAccessibility statement