Skip to Content
avatar image
Former Member

Update of a DSO using an end routine - field not updated

Hi all,

Our end routine, located between two DSO is aimed at filling a field of the target DSO through a lookup to another table (or a third DSO). At the end of this end routine, according to the debugger, the result_package contains the record as it should be written in the DSO : the concerned field contains the right value.

However, after having been loaded, the DSO does not contain any value for this field. What is the possible cause of this issue ?

Thanks for your feedback,

chris

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Oct 11, 2007 at 08:15 AM

    Hi,

    what is the code of the end routine?

    so that we can suggest a solution?

    Janardhan KUmar

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Dear all,

      Finally, the best solution we found consisted in making the lookup to the other table through the start routine and to put the results in an internal table. Then, in the update rules, the field gets the result through a read of the internal table.

      Thanks & regards - Some points rewarded.

      chris

  • avatar image
    Former Member
    Oct 11, 2007 at 08:08 AM

    Hi Chris,

    Check the end routine, last statement should be ..modify result package ..

    Regards,

    Ravi

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 11, 2007 at 01:49 PM

    Hi

    Ensure all the related objects are active and then debug

    Regards

    N Ganesh

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 19, 2007 at 03:19 AM

    FYI -

    Just to let you know, there is a bug in NW 7.0 with un-mapped fields being filled in the End Routine. I don't have the OSS note handy, but we had this issue on SP 7, and saw the issue again on SP 13.

    Add comment
    10|10000 characters needed characters exceeded