Skip to main content
Solved

Migrating Customer Information

R
Superhero (Partner)
Forum|alt.badge.img+18

Whilst migrating customer master data I have an issue when attempting to migrate the information that would populate the Customer > Sales tab.   

View:  CUST_ORD_CUSTOMER_ENT

I am receiving the following message:

ORA-20111: CustOrdCustomer.ORDERATTR: Customer BDAR has no delivery address with order specific attributes specified.

 

Looking at CustOrdCustomer.plsql can see:

 

PROCEDURE Exist (

   customer_no_ IN VARCHAR2,

   customer_category_ IN VARCHAR2 DEFAULT 'CUSTOMER')

IS   

BEGIN     

                                          

   IF (NOT Check_Exist___(customer_no_)) THEN

      Error_SYS.Record_Not_Exist(lu_name_,'ORDERATTR: Customer :P1 has no delivery address with order specific attributes specified.', customer_no_);

   END IF;

   super(customer_no_);

END Exist; 

 

I have checked that customer BDAR has an address:

 

Also, checked the Sales Address Information tab:

 

Any ideas on how to resolve this?

Many thanks in advance.

Kind Regards

 

John

Best answer by Jens

Hi ​@RutJWhalen 

Only an idea to the mapping of CUST_ORD_CUSTOMER_ENT.

I assume you map the field CUSTOMER_ID (primary key) with the value ‘BDAR’ as an example.

There is also a field for the mapping which is called CUSTOMER_NO_PAY (Invoice Customer).

If CUSTOMER_ID and CUSTOMER_NO_PAY is the same/have the same value then don’t map the same value to CUSTOMER_NO_PAY, keep it blank/NULL.

If it’s different then map it but then you have to ensure that the CUSTOMER_NO_PAY already exists in the system otherwise it might be the case that you have to execute your migration job multiple time (because of the hierarchy).

 

/Jens

View original
Did this topic help you find an answer to your question?

2 replies

M
Hero (Employee)
Forum|alt.badge.img+11
  • Makede
  • Hero (Employee)
  • 101 replies
  • July 17, 2025

HI ​@RutJWhalen 

Did you map the field CUSTOMER_NO_PAY? 
If yes, if CUSTOMER_ID and CUSTOMER_NO_PAY is the same, keep the field CUSTOMER_NO_PAY empty. Only fill the field when the CUSTOMER_NO_PAY is different from CUSTOMER_ID.

Best regards
Martina

R
Grzegorz Byrski
2 people like this
  • R
    RutJWhalen
  • Grzegorz Byrski
    Grzegorz Byrski
Jens
Hero (Employee)
Forum|alt.badge.img+10
  • Jens
  • Hero (Employee)
  • 129 replies
  • Answer
  • July 17, 2025

Hi ​@RutJWhalen 

Only an idea to the mapping of CUST_ORD_CUSTOMER_ENT.

I assume you map the field CUSTOMER_ID (primary key) with the value ‘BDAR’ as an example.

There is also a field for the mapping which is called CUSTOMER_NO_PAY (Invoice Customer).

If CUSTOMER_ID and CUSTOMER_NO_PAY is the same/have the same value then don’t map the same value to CUSTOMER_NO_PAY, keep it blank/NULL.

If it’s different then map it but then you have to ensure that the CUSTOMER_NO_PAY already exists in the system otherwise it might be the case that you have to execute your migration job multiple time (because of the hierarchy).

 

/Jens

R
M
Grzegorz Byrski
3 people like this
  • R
    RutJWhalen
  • M
    Makede
  • Grzegorz Byrski
    Grzegorz Byrski

Reply


Terms & ConditionsCookie settingsAccessibility statement

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings