topic CALL_FUNCTION_CONFLICT_LENG when using FM BILLING_SCHEDULE_STATUS in Application Development and Automation Discussions

CALL_FUNCTION_CONFLICT_LENG when using FM BILLING_SCHEDULE_STATUS

Former Member — Mon, 02 Mar 2009 17:32:16 GMT

Hi all!

It's a curious situation. I'm using function module BILLING_SCHEDULE_STATUS. But unfortunately I receive evyertime the dump CALL_FUNCTION_CONFLICT_LENG (CX_SY_DYN_CALL_ILLEGAL_TYPE

ST22 said: An exception occurred that is explained in detail below. The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_TYPE', was not caught in procedure "SET_FPLT_STATUS" "(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:

The call to the function module "BILLING_SCHEDULE_STATUS" is incorrect:

In the function module interface, you can specify only fields of a specific type and length under "FPLT_NEW". Although the currently specified field " " is the correct type, its length is incorrect.

But from my point of view this could not be! I copied the data declaration from ME23N coding - doe not work. Try own declaration - does not work. Does anybody knows whats wrong?


" first try
  DATA lt_fplt_old TYPE STANDARD TABLE OF fplavb.
  DATA lt_fplt_new TYPE STANDARD TABLE OF fplavb.
  DATA lt_fpla_old TYPE STANDARD TABLE OF fplavb.
  DATA lt_fpla_new TYPE STANDARD TABLE OF fplavb.

  DATA lt_tfplts   TYPE STANDARD TABLE OF fplts.


" second try
DATA: lt_fplt_old LIKE fplavb OCCURS 0 WITH HEADER LINE,
        lt_fplt_new LIKE fplavb OCCURS 0 WITH HEADER LINE,
        lt_fpla_old LIKE fpltvb OCCURS 0 WITH HEADER LINE,
        lt_fpla_new LIKE fpltvb OCCURS 0 WITH HEADER LINE.

  DATA: lt_tfplts LIKE fplts OCCURS 0 WITH HEADER LINE.

I call the function module in this way:


  CALL FUNCTION 'BILLING_SCHEDULE_STATUS'
    EXPORTING
      i_fplnr  = ld_fplnr
    TABLES
      fpla_new = lt_fpla_new 
      fpla_old = lt_fpla_old
      fplt_new = lt_fplt_new
      fplt_old = lt_fplt_old
      i_fplts  = lt_tfplts.

Thanky you for your help!

Florian

Edited by: Florian Teepen on Mar 2, 2009 6:33 PM

Re: CALL_FUNCTION_CONFLICT_LENG when using FM BILLING_SCHEDULE_STATUS

Former Member — Mon, 02 Mar 2009 17:41:26 GMT

Hi,

Check this


Check the Tables declaration for the  FPLT_OLD  & FPLT_NEW .
TABLES
*"              FPLA_OLD STRUCTURE  FPLAVB
*"              FPLA_NEW STRUCTURE  FPLAVB
*"              FPLT_OLD STRUCTURE  FPLTVB
*"              FPLT_NEW STRUCTURE  FPLTVB
*"              I_FPLTS STRUCTURE  FPLTS


" first try
  DATA lt_fplt_old TYPE STANDARD TABLE OF FPLTVB.        " Change
  DATA lt_fplt_new TYPE STANDARD TABLE OF FPLTVB.      " Change
  DATA lt_fpla_old TYPE STANDARD TABLE OF fplavb.
  DATA lt_fpla_new TYPE STANDARD TABLE OF fplavb.
 
  DATA lt_tfplts   TYPE STANDARD TABLE OF fplts.




" second try
DATA: lt_fplt_old LIKE FPLTVB OCCURS 0 WITH HEADER LINE,       " Change
        lt_fplt_new LIKE FPLTVB OCCURS 0 WITH HEADER LINE,       " Change
        lt_fpla_old LIKE fpltvb OCCURS 0 WITH HEADER LINE,
        lt_fpla_new LIKE fpltvb OCCURS 0 WITH HEADER LINE.
 
  DATA: lt_tfplts LIKE fplts OCCURS 0 WITH HEADER LINE.

Edited by: Avinash Kodarapu on Mar 2, 2009 11:11 PM

Re: CALL_FUNCTION_CONFLICT_LENG when using FM BILLING_SCHEDULE_STATUS

Former Member — Mon, 02 Mar 2009 17:47:52 GMT

DOOOOH! This can't be real! Well it's late! I think I should switch the light off!

Thank you very much!