Error on Production Orders

[Former Member]

I receive the following error when I create a Production Order

"Internal error 'Items - Warehouse' (OITW) (-2118) occurred [Message 131-183]"

Edited by: Raymond Singh on Jun 7, 2010 4:50 PM

[former_member314871]

Raymond,

I also experienced the same problem after upgrading. It appears that SAP is attempting to run the formatted search against to last blank line, causing the error.

In my formatted search, I was copying the warehouse code from the header to the lines when it was changed. In order to ensure that the formatted search was only running on a line that was populated, I checked the item code on the line to ensure it was populated; otherwise, I just returned the contents of the warehouse field in the following code.

DECLARE @ItemCode nvarchar(20)

SELECT @ItemCode = $[$37.4.0]
IF  @ItemCode = '' 
     SELECT $[$37.10.0]
ELSE
     SELECT $[OWOR.Warehouse]

Ben Besel

[Former Member]

This has worked perfectly for me on a Production Order Formatted Search. Thank you.

[Former Member]

This issue might be caused by Formated Search fuctionality on warehouse relevant column.

[zal_parchem2]

Raymond - we received this message in 2007 when the Item did not have the warehouse set up on the Item Master Data record...maybe this helps???

Zal

[Former Member]

We don't see the error in 2007. The problem seems to be in 8.8

[zal_parchem2]

Mama Mia - then that is a big problem then. I wonder how that could ever get past testing by SAP???

Please let us know what the resolution is...

Take Care and Good Luck - Zal

[Former Member]

HI Raymond.......

Check the FMS, SP_transnotification or any addon connected. Stop it and the try.....

Regards,

Rahul

[Former Member]

Is the problem for particular item/warehouse or any of them?

Thanks,

Gordon

[Former Member]

It seems to be for any of them (items/whse)

[Former Member]

Also, it should be noted that this error occurred after upgrading from SBO 2007 A PL 49 to SBO 8.8. PL11

[Former Member]

If the errors are for all Production Orders, it is probably a bug or database issue. Log a support message in this case.