Skip to main content
Solved

Error in migration job - Org Position Structure

  • June 22, 2023
  • 1 reply
  • 427 views

lescobar
Do Gooder (Partner)
Forum|alt.badge.img

We’re trying to get the migration done and we have an structure like this as a CSV:

CSV - source file

After we finish the first job which is the creation of the table with this data, there’s no error. The error comes after we execute the second job which is the one that migrates data, I get this error:

ORA-20124: Error.NULLVALUE: Field [BUSINESS_UNIT_ID] is mandatory for Business Unit Relation and requires a value.

 

Here is what’s been done:

To test we only try to migrate one of the rows, the one with POS_CODE=’50000008’

 

The attribute string we get is: 

COMPANY_ID=ABC
POS_CODE=50000008
POSITION_TITLE=ASSISTANT MANAGER
VALID_FROM=2023-06-22-21.29.22
VALID_TO=9999-12-31-00.00.00
TIME_FORMAT=Minute by minute
ASSIGNED_PROTECTED=FALSE
EXCLUDE_FROM_EXPORT=FALSE
EXCLUDE_FROM_ORG_CHART=FALSE
DEFAULT_ACCESS_EXTENSION=FALSE
EXPORT_EMPLOYEES=FALSE
STRUCT_BU_ID=781
BUSINESS_UNIT_TYPE_DB=COMPANY

 

Here the job execution that throws the error:

 

 

and the migration job is defined like this:

 

Best answer by NiyomalN

HI Luisa,

I was able get this done using a new migration job, we need to follow the source migration for this. I have created an import job with below columns. 

 

 

Then Created the Migration job using the view “COMPANY_POSITION6”

Mapped the Source columns with columns in the view and left the default values to be the same. if you are  not using valid from and valid to dates, then you can default it to a valid date.

I'm adding this here as anyone might also need this.(we talked about the solution already ;)) 

Kind Regards!

Niyo.

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

1 reply

NiyomalN
Hero (Partner)
Forum|alt.badge.img+10
  • Hero (Partner)
  • 102 replies
  • Answer
  • June 23, 2023

HI Luisa,

I was able get this done using a new migration job, we need to follow the source migration for this. I have created an import job with below columns. 

 

 

Then Created the Migration job using the view “COMPANY_POSITION6”

Mapped the Source columns with columns in the view and left the default values to be the same. if you are  not using valid from and valid to dates, then you can default it to a valid date.

I'm adding this here as anyone might also need this.(we talked about the solution already ;)) 

Kind Regards!

Niyo.


Reply


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