Solved

Migration Job : create a unicity check and a block

  • 24 January 2024
  • 1 reply
  • 55 views
K
Rank
Badge +3
  • ksebf
  • Sidekick (Partner)
  • 7 replies

Hello everyone,

I need to create a migration job for customer orders. My customer would like a unicity check to be performed on the field CUSTOMER_PO_NO when the job is launched.  

If the value already exists on IFS, the line that should be imported by the job should be blocked. 

 

 

Is it possible to add this control and blocking directly to the migration job? Knowing that, the field is optional. 

 

 

icon

Best answer by FlorianTauber 24 January 2024, 16:04

View original

1 reply

FlorianTauber
Rank
Badge +2

Hey there,

if I got you right: Yes, it is possible.

I assume you’ll have a migration job with procedure “MIGRATE_SOURCE_DATA” for migrating those values from your “CREATE_TABLE_FROM_FILE”-job.

Looking at your screenshots you’ve added a column DUMMY_1 for checking the existence / uniqueness of the customer order line / planning to do so?

If so, you can add the column DUMMY_1 to the conditions at the Method_List_TAB.

Please refer to https://docs.ifs.com/techdocs/22r1/030_administration/050_data_management/050_data_migration/070_references/020_tips_and_tricks/tipsandtricksmethodconditions/#condition_on_source_column. “Condition on Source Column”.

I know the docs are for IFS Cloud, but it’s the same within IFS Apps 10 and below.

Hope this helps.

Otherwise: Pls add more information.

 

BR

Florian

FLEXiCODE GmbH

Reply


Terms & ConditionsCookie settings