Regarding ABAP dump

[Former Member]

Hi all,

When i execute the tcode co02 for the order number 10015447 (only) and when i change the technical information and when i press save button the system leads to ABAP dump

with parameters_not_valid message.

I tried to find out SAP notes for the problem all notes

saying that support package not required for version 4.6c.

Can anybody help me regarding this matter

with regards

chandu.

[Former Member]

Hi all,

When i execute the tcode co02 for the order number 10015447 (only) and when i change the technical information and when i press save button the system leads to ABAP dump

with parameters_not_valid message.

I tried to find out SAP notes for the problem all notes

saying that support package not required for version 4.6c.

Can anybody help me regarding this matter

with regards

chandu.

[Former Member]

Hi

It seems an exception of some functions is triggered but it isn't managed in the program.

Please give us the piece of code where the dump occurs.

Max

Message was edited by: max bianchi

[Former Member]

Hi Max,

The termination occurred in the ABAP/4 program "SAPLCXOT " in

"CX_SCHED_VIA_OPERATING_TIME".

The main program was "SAPLCOKO1 ".

The termination occurred in line 244

of the source code of program "LCXOTU01 " (when calling the editor 2440).

002260 if not i_date_end is initial.

002270 call function 'DATE_TIME_CONVERT'

002280 exporting

002290 date = i_date_end

002300 time = i_time_end

002310 importing

002320 point_in_time = i_point_in_time_end

002330 exceptions

002340 date_before_rel_date = 01

002350 date_to_big = 02.

002360 if sy-subrc <> 0.

002370 e_message_code = mc-date_out_of_pit_range.

002380 endif.

002390 endif.

002400 endif.

002410 * Eingabeparameter prüfen

002420 if i_point_in_time_start = 0 and

002430 i_point_in_time_end = 0.

> raise parameters_not_valid.

002450 elseif i_duration_sec <> 0 and

002460 i_point_in_time_start <> 0 and

002470 i_point_in_time_end <> 0.

002480 raise parameters_not_valid.

002490 endif.

[Former Member]

Look at OSS notes 413725 and 773606. What version and support pack level are you on?

[Former Member]

Hi srinivas,

I also found note 773606 useful for this context.But i dont know how to implement it.

I know the version 4.6c and i dont know the support pack level.

regards

chandu

[Former Member]

Hi

Your std program SAPLCOKO1 (trx CO02) calls fm CX_SCHED_VIA_OPERATING_TIME but doesn't check the exception PARAMETERS_NOT_VALID; all calls are like this:

CALL FUNCTION 'CX_SCHED_VIA_OPERATING_TIME'

EXPORTING

I_DATE_END = AFVGD-SSAVD

I_TIME_END = AFVGD-SSAVZ

I_DURATION = AFVGD-ZWMIN

I_UNIT = AFVGD-ZEIWM

I_ARBID = AFVGD-ARBID

I_VERSA = CAUFVD-KAPVERSA

I_FLG_EXACT_BREAKS = CAUFVD-BREAKS

IMPORTING

E_DATE_START = L_SAVD

E_TIME_START = L_SAVZ.

You can see there isn't any control on exception, so if fm raises the exception a dump occurs.

The right call should be:

CALL FUNCTION 'CX_SCHED_VIA_OPERATING_TIME'

EXPORTING

I_DATE_END = AFVGD-SSAVD

I_TIME_END = AFVGD-SSAVZ

I_DURATION = AFVGD-ZWMIN

I_UNIT = AFVGD-ZEIWM

I_ARBID = AFVGD-ARBID

I_VERSA = CAUFVD-KAPVERSA

I_FLG_EXACT_BREAKS = CAUFVD-BREAKS

IMPORTING

E_DATE_START = L_SAVD

E_TIME_START = L_SAVZ

EXCEPTIONS

PARAMETERS_NOT_VALID = 1

OTHERS = 2.

If the program called fm as above, no error would occur.

But when a FM is called in a program it isn't obligatory to check exceptions, if it's sure that error can't occur it's be able to not check exception.

So if the standard doesn't check exception PARAMETERS_NOT_VALID, it mean that error wouldn't occur. I think there are some wrong data (or missing data) in record: check it.

Max

[Former Member]

Do system-->status in the sap menu. In the subsequent screen, in the box 'SAP SYstem Data', click on the 'component information' glass icon. There you will find the support pack level.

Best thing to do is to approach your basis person and give him the details. They normally do this.

If the answers help, please reward and close when the issue is resolved.

Srinivas

[Former Member]

If I look at the note, it says that you need to write a custom report(the code is in the note) and run it. The reason for this error is

<i>"The error occurs if at least one operation has status 'Partially confirmed' (PCNF), a corresponding partial confirmation does not exist and a change, which results in a rescheduling, is performed in the order."</i>

So if the reason applies to your case, create the report with the code available in the note. Run it in your system and see if the error repeats. If you cannot see the code, let me know.

This is not part of any support pack. This will not be part of standard SAP.

You can find the code in the "Correction Instructions" tab.

If this helps, please reward and close.

Srinivas

[Former Member]

Thank alot

its solved my problem and i gave you the reward points

[Former Member]

Check OSS 591103 , 677572 or 102970.

You may find your problem in one of them

Cheers

[Former Member]

Hi sai,

Take a look at OSS Note 413725..

Sri