topic Function PM_ORDER_DATA_READ exception in Application Development and Automation Discussions

Function PM_ORDER_DATA_READ exception

Former Member — Fri, 18 May 2007 19:22:07 GMT

Hi All,

I am using fm PM_ORDER_DATA_READ in a dialogue program to get operation details for a particular production order.

Its works fine on its first execution, but throws a short dump on subsequent execution saying ...

A RAISE statement in the program "SAPLCOIT" raised the exception

condition "ITAB_ERROR".

Trigger Location of Runtime Error

Program SAPLCOIT

Include LCOITU41

Row 67

Module type (FUNCTION)

Module Name CO_IT_GET_PROV_OF_OPERATIONS

I've checked the function call & parameters passed to it in debug mode during its second execution. Everything seems to be fine.

M using ECC 6.0

Kindly guide if someone had got d same error & had got it solved.

You can also realize this by just executing PM_ORDER_DATA_READ in SE37 twice, each time using different order numbers.

Re: Function PM_ORDER_DATA_READ exception

ferry_lianto — Fri, 18 May 2007 19:32:53 GMT

Hi,

Please try to add FREE MEMORY statement before ENDLOOP or calling second time the above FM.

Regards,

Ferry Lianto

Re: Function PM_ORDER_DATA_READ exception

Former Member — Sat, 19 May 2007 04:50:59 GMT

Hi Ferry,

I did it. But there is no change. Still the program throws a dump.

Re: Function PM_ORDER_DATA_READ exception

Former Member — Sun, 06 Jul 2008 14:45:37 GMT

Implement Note 575491. It helps for me.

Best regards, Dusan

Re: Function PM_ORDER_DATA_READ exception

aditya_niyogi — Tue, 29 Jul 2008 06:55:58 GMT

Hi Jethendra,

I faced the same problem - however SAP has just recently come out with the solution. Please apply OSS Note (#1179835) to resolve this error. This was happening because a particular field that should have been freed was not during the second run. This note was released recently by SAP (June 18, 2008).

Additionally if you want to code without this particular note - then just call this FM - "CO_EXT_ORDER_RESET" before calling PM_ORDER_DATA_READ.

Code Sample:

CALL FUNCTION 'CO_EXT_ORDER_RESET'.

*Obtain the relevant information for a particular order.

CALL FUNCTION 'PM_ORDER_DATA_READ'

EXPORTING

ORDER_NUMBER = <FS_AUFNR>-AUFNR

CALL_FROM_NOTIF =

IMPORTING

WCAUFVD = CAUFVD

WILOA = ILOA

WRIWO1 = RIWO1....

This solved my problem and hopefully it will solve yours.

Reward with points if helpful

Thanks &Regards,

Aditya

Edited by: Aditya Niyogi on Jul 29, 2008 8:56 AM

Re: Function PM_ORDER_DATA_READ exception

antony_paul2 — Mon, 23 Feb 2009 07:18:22 GMT

Thanks Aditya ..

FM u had mentioned, CO_EXT_ORDER_RESET, solved the puzzle for me ...

Rgds,

Antony

Re: Function PM_ORDER_DATA_READ exception

Former Member — Mon, 05 Aug 2013 12:10:46 GMT

Try CALL FUNCTION 'CO_IT_SET_FLG_ITAB_NEW' Before PM_ORDER_DATA_READ

Re: Function PM_ORDER_DATA_READ exception

Former Member — Mon, 08 Sep 2014 09:20:54 GMT

Hi All,

The use of FREE MEMORY without the addition ID is obsolete. I rather prefer the solution from Aditya Niyogi, calling function module CO_EXT_ORDER_RESET before calling PM_ORDER_DATA_READ.

Thanks to Aditya, it worked fine for me.

Regards,

Sergio Alonso

Re: Function PM_ORDER_DATA_READ exception

Former Member — Wed, 11 Feb 2015 12:24:00 GMT

Thanx Adi,

FM "CO_EXT_ORDER_RESET" works for me.

Br,

Abhijit.