The error flag for AWTDIFF says "AWTDIFF is populated but AWTARGET and/or one of [ADY,ARELTM] are not both present and populated."
In one BDS dataset, we have used ASTDT, and ASTDY, instead of ADT, because we have start and end dates and the records are coming from sdtm.CE (CESTDTC, CEENDTC). We do have values for ASTDY nonnull in these records. (We have no column for ADY, just have ASTDY.)
Logic says those data should cover us, but the rule logic is firing. Since the IG for BDS data allows and defines ASTDT as "The start date associated with AVAL and/or AVALC", does it make sense that AWTDIFF and its error checking is limited to ADT / ADY scenarios and doesn't take into account the column ASTDT / ASTDY?
Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.
Hi,
The error flag for AWTDIFF says "AWTDIFF is populated but AWTARGET and/or one of [ADY,ARELTM] are not both present and populated."
In one BDS dataset, we have used ASTDT, and ASTDY, instead of ADT, because we have start and end dates and the records are coming from sdtm.CE (CESTDTC, CEENDTC). We do have values for ASTDY nonnull in these records. (We have no column for ADY, just have ASTDY.)
Logic says those data should cover us, but the rule logic is firing. Since the IG for BDS data allows and defines ASTDT as "The start date associated with AVAL and/or AVALC", does it make sense that AWTDIFF and its error checking is limited to ADT / ADY scenarios and doesn't take into account the column ASTDT / ASTDY?
What do you think?
Thanks very much. Best, Joan