Skip to main content

Add ZINACTIVE_REASONNEW to auto-generated UPD_ZACTIVE rules

Syniti Knowledge PlatformMigrate

When we update ZACTIVENEW, we should also always update ZINACTIVE_REASONNEW at the same time. Can the auto-generated shell of this update view from ADMM also include a placeholder for ZINACTIVE_REASONNEW?

Posted by emily.burnside ·
2 comments

Log in to comment and vote

Comments2

  • John Munkberg

    Team•

    Apr 25

    I’m not sure I agree with this, but happy to have a discussion. “In the old days” we used to say that every record was inactive by default, and you had to “prove” that it was relevant by defining a reason to be active (ZNEW or ZPO or ZOPENPO etc). If any of the flags had a 1, only then was a record active.

    Somewhere along the journey we changed the logic and now turn things off - assuming we use the opposite logic? If all of the flags are 0, then a record is inactive.

    There could be many reason - Not New, Not on a historic PO, not on an Open PO, not marked for Deletion in legacy, etc).

    So what would be the reason in ZINACTIVE_REASON?

    • nikhileshshirsale

      Team•

      Jun 3

      @emily.burnside Can you clarify above questions for us to proceed?