Getting error

[Former Member]

Hi All,

I am entering values to custom  module pool program, but unable to proceed because i am getting thia error'

Entry 5 IDLE 1 does not exist in QPCD (check entry)' . I have checked all check tables, foreign-key tables but data is maintained properly, this issue happening only development production ,quality systems working fine. Please help any one if you phase smiler issue.

Regards,

Sreedhar.

[kakshat]

Hi Sreedhar,

You mean to say the entry '5 IDLE 1' exists in QPCD table?

[Former Member]

Hi Kumar,

yes entry '5 IDLE 1' exists in QPCD table .

Regards,

Sreedhar.

[kakshat]

And, did you try debugging to find out where is this error coming from?

[Former Member]

Hi Kumar,

yes error is coming  at ZZIDLE-URGRP, field but i am unable to see the program where error is coming as break point is not triggering at message statement. I have tried with watch point at message number still watch point not triggered

  CHAIN.

     FIELD :
      ZZIDLE-WERKS,
  ZZIDLE-FEVOR,
  ZZIDLE-EQUNR,
  ZZIDLE-BUDAT,
  ZZIDLE-QUALF,
  ZZIDLE-ISM01,
  ZZIDLE-ILE01,
  ZZIDLE-URGRP,
  ZZIDLE-URCOD.

Regards,

Sreedhar

[kakshat]

It could be coming from a RAISE statement. Did you try setting a breakpoint on RAISE at runtime in the debugger?

[kakshat]

It could be coming from a RAISE statement. Did you try setting a breakpoint on RAISE at runtime in the debugger?

[kakshat]

It could be coming from a RAISE statement. Did you try setting a breakpoint on RAISE at runtime in the debugger?

[kakshat]

It could be coming from a RAISE statement. Did you try setting a breakpoint on RAISE at runtime in the debugger?

[kakshat]

It could be coming from a RAISE statement. Did you try setting a breakpoint on RAISE at runtime in the debugger?

[kakshat]

It could be coming from a RAISE statement. Did you try setting a breakpoint on RAISE at runtime in the debugger?

[kakshat]

It could be coming from a RAISE statement. Did you try setting a breakpoint on RAISE at runtime in the debugger?

[kakshat]

It could be coming from a RAISE statement. Maybe you can set a breakpoint at runtime on RAISE statement in the debugger.

[Former Member]

Hi Kumar,

Yes I kept break point at raise statement at run time still not triggering that message. I have checked both data and code in production system no difference.

Regards,

Sreedhar.