How to insert customer order header and line items in the same migration job
I'd like to know how to register new customer order headers and line items in the same migration job.
I have tried this and confirmed that adding CUSTOMER_ORDER and CUSTOMER_ORDER_LINE to the "Method List" tab allows me to update them all at once.
However, when I try to insert both the header and line items, I get the error "DEVELOPER_ERROR_03: Most likely a usage definition is wrongly defined for LU: [CustomerOrder] in table RM_ACC_USAGE_TAB, internal exception: [Ex_Get_Id]."
Page 1 / 1
Are you passing the Customer Order Number via the spreadsheet, or is the system creating the order number in the first step of the migration? If it is created in the first step of the migration job, you will have to go to Method List Attributes on your second Method List item i.e Customer_Order_Line and define Order_No@10.
@10 represents the method list “Execute Seq” the header is created.
see below screen print.
Thank you for your answer!
I'm passing the ORDER_NO field blank in the spreadsheet and passing a system-generated value.
I tried your settings and the "DEVELOPER_ERROR_03" error was resolved, but now I'm getting the error "ORA-20110: CustOrdDateCalculation.INVALSHIPDATE: Planned ship date is outside the range of the current calendar."
It seems like the problem is caused by blank values being passed for "PLANNED_DELIVERY_DATE" and "WANTED_DELIVERY_DATE," but I was entering them in the spreadsheet.
Do you know any solutions?
seems like the date format in your spreadsheet and migration job is not aligned.
You may want to set it up correctly by in the below section.
Or you may want to use a function like TO_DATE(<COLUMN_NAME>, ‘DD/MM/YYYY’) or TO_CHAR(<COLUMN_NAME>, ‘DD/MM/YYYY’) when mapping the columns in the below section
Thank you!
First of all, I'm sorry, but I managed to resolve the "ORA-20110: CustOrdDateCalculation.INVALSHIPDATE:" error myself. It appears that the problem was caused by an undefined CUSTOMER_ORDER_LINE.CONTRACT.
However, it has now been replaced with this error: "ORA-20124: Error.NULLVALUE: Field [ORDER_NO] is required for a customer order line and requires a value."
The following patterns have been confirmed: - When ORDER_NO@10 is set Insert record: An error occurs Update record: An error occurs
- When ORDER_NO@10 is not set Insert record: An error occurs Update record: No error
I forgot to mention that I'm using the "EXCEL_MIGRATION" migration job data.