Skip to main content
Solved

Is it possible to modify the DEF_ADDRESS in the customer_info_addess_type using data migration ?

  • November 4, 2025
  • 8 replies
  • 33 views

Forum|alt.badge.img+3

Hi,

 

Is it possible to modify the DEF_ADDRESS in the customer_info_addess_type using data migration ?

 

When i try, i have this message:

 

ORA-20112: CustomerInfoAddressType.FND_RECORD_EXIST: The Customer Info Address Type already exists.

Best answer by N.GEORGI

in your 1st screenshot, 

Source Mapping: 

POS : 30 : ADDRESS_TYPE_CODE needs to be populated; the value from ADDRESS_TYPE_CODE_DB is not sufficient (that should correct the error you are having)

 

I don’t wan’t to put a fixed value in the field CUSTOMER_INFO_ADDRESS_TYPE.DEF_ADDRESS.

 

Could you elaborate on the rule to determine which value you want to insert please? and based on what? (source file? value already in database...etc?)

8 replies

Forum|alt.badge.img+5
  • Sidekick (Customer)
  • 47 replies
  • November 4, 2025

@Julien T.  Bonjour,

Yes it is possible.

Could you please give more contexte? which adresse type? delivery? invoice?….screenshot of the screen?

 

 


Forum|alt.badge.img+3
  • Author
  • Sidekick (Customer)
  • 6 replies
  • November 4, 2025

I would like to modify the field DEF_ADDRESS of INVOICE address type from TRUE to FALSE.

 

I have to insert a lot of rows in customer_info_addess_type using data migration who use the field DEF_ADDRESS of INVOICE address type with the value ‘TRUE’.

So i have to modify the present rows the field DEF_ADDRESS of INVOICE address type from TRUE to FALSE.

 


Forum|alt.badge.img+5
  • Sidekick (Customer)
  • 47 replies
  • November 4, 2025

@Julien T. 

The error you are getting is because the datamigration job is not able to identify the line to update so he is trying to insert a new line, maybe you are only passing the _DB value of ADDRESS_TYPE_CODE.

 

the source data to be adapted as needed :

 

All field (except OBJID) in the mapping tab are mandatory : 

 

 


Forum|alt.badge.img+3
  • Author
  • Sidekick (Customer)
  • 6 replies
  • November 4, 2025

Thank you for your answer.

 

I don’t wan’t to put a fixed value in the field CUSTOMER_INFO_ADDRESS_TYPE.DEF_ADDRESS.

 

 


Forum|alt.badge.img+5
  • Sidekick (Customer)
  • 47 replies
  • Answer
  • November 4, 2025

in your 1st screenshot, 

Source Mapping: 

POS : 30 : ADDRESS_TYPE_CODE needs to be populated; the value from ADDRESS_TYPE_CODE_DB is not sufficient (that should correct the error you are having)

 

I don’t wan’t to put a fixed value in the field CUSTOMER_INFO_ADDRESS_TYPE.DEF_ADDRESS.

 

Could you elaborate on the rule to determine which value you want to insert please? and based on what? (source file? value already in database...etc?)


Jens
Hero (Employee)
Forum|alt.badge.img+10
  • Hero (Employee)
  • 137 replies
  • November 10, 2025

Hi ​@Julien T. 

Only map the column ADDRESS_TYPE_CODE_DB with a value, the mapping for the Client value ADDRESS_TYPE_CODE must be empty:

Go to the method list, mark the line with the view CUSTOMER_INFO_ADDRESS and choose Method List Attribute:

 

Change the flag from K to - (minus sign) for the column ADDRESS_TYPE_CODE:

Now you are able to update existing records.

/Jens


Forum|alt.badge.img+5
  • Sidekick (Customer)
  • 47 replies
  • November 10, 2025

@Jens I don’t recommend changing the flag from the attribute side in this case.


It’s more logical to assign a value to the field using existing data that we already have in our source rather than removing the field as a key from the table.


Jens
Hero (Employee)
Forum|alt.badge.img+10
  • Hero (Employee)
  • 137 replies
  • November 10, 2025

Hi ​@N.GEORGI 

The value for the Client field ADDRESS_TYPE_CODE will not be removed, the API will transform the value automatically by the DB value of ADDRESS_TYPE_CODE_DB.

With this approach you will be able to update existing records as you have a DB and NON DB column in the primary key.

/Jens