Skip to main content
Solved

Migration Job failing with "ORA-01003: no statement parsed"

msurasky-price
Sidekick (Customer)
Forum|alt.badge.img+8

Today I’m trying to migrate data into INVENTORY_PART_UNIT_COST using a Migration Job (Migration Type = INSERT_BY_METHOD_NEW).

 

I configure the job and map my fields as usual, but upon execution of the job ALL 3,054 rows fail with the error ORA-01003: no statement parsed.

 

 

No additional error descriptions, just No Statement Parsed

I tried running this as a Background Job and looking at the job output but nothing useful is displayed there either.

Is there something obvious that I’m missing? is this type of error an indication of something in particular? Any ideas on how to troubleshoot this?

 

Thanks!

Best answer by msurasky-price

After some more investigation we now know why this is not migrated.

The unit cost values for Inventory Parts are determined by a cost roll-up calculation that should be done through the IFS Cloud application, and not by direct migration of the INVENTORY_PART_UNIT_COST container.
 

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

2 replies

msurasky-price
Sidekick (Customer)
Forum|alt.badge.img+8
  • msurasky-price
  • Author
  • Sidekick (Customer)
  • 44 replies
  • March 7, 2025

I'm starting to suspect that the problem is with the view itself... I tried to generate an Excel Add-In Migration Job to accomplish the same migration that was failing using a different approach and then I see the error in

Is as if the View is not the right one to migrate the rows into the table that this view support (which is inventory_part_unit_cost_tab).

 

I also looked at the API packages and INVENTORY_PART_UNIT_COST_API is indeed missing the PROCEDURE New or PROCEDURE Update (something I would have expected to see). Wouldn't that explain these issues then? I’m guessing it does. But then again. What VIEW should be used to update the Inventory Part Unit Cost page (Unit Cost field)?

INVENTORY_PART_CONFIG cannot be the one as it does NOT contain UNIT_COST

INVENTORY_PART_UNIT_COST_SUM cannot be the one either, as it is ALSO missing the PROCEDURE New and PROCEDURE Update (hence, not a “base view”)

msurasky-price
Sidekick (Customer)
Forum|alt.badge.img+8
  • msurasky-price
  • Author
  • Sidekick (Customer)
  • 44 replies
  • Answer
  • March 10, 2025

After some more investigation we now know why this is not migrated.

The unit cost values for Inventory Parts are determined by a cost roll-up calculation that should be done through the IFS Cloud application, and not by direct migration of the INVENTORY_PART_UNIT_COST container.
 

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