‎2010 Mar 19 6:16 PM
hi all,
we are getting short dumps when processing credit memo requests creation to assign the deductions. (Assign Credit Memo function) .
the dump is as below:
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "CANCEL_FI" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
where this happened:
ermination occurred in the ABAP program "SAPLFOAP_CDITEMS" - in "CANCEL_FI".
The main program was "SAPMV45A ".
In the source code you have the termination point in line 1003
of the (Include) program "LFOAP_CDITEMSF01".
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "CANCEL_FI" "(FORM)", but it was neither handled locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLFOAP_CDITEMS "; its source code begins in line
950 of the (Include program "LFOAP_CDITEMSF01 ".
1001 gt_items_credit[] = gt_confirm_items_credit[].
1002 gt_items_debit[] = gt_confirm_items_debit[].
===== gt_items_assigned = gt_confirm_items_assigned[].
1004 gs_cditem = gs_confirm_cditem.
Any pointers on what is wrong and how to correct this??(i cannot debug as this is in production)
what could be the probable cause
thanks
Edited by: Rob Burbank on Mar 19, 2010 2:28 PM
‎2010 Mar 19 6:37 PM
This is standard SAP functionality. Have you looked for notes??
Rob
‎2010 Mar 19 7:59 PM
hi.
yes searched for notes..found one but that is already applied .
so,shall we raise a note instead ?