Hi,
Doing some auditing reports and noticing there are circumstances where ICHIST.TRANSDATE is different than the [DATE] field from most of the document header tables (PORCPH1, POINVH1, etc) in the PO module. This isn't a high percentage amount, but I'm being asked why.
I have some specific examples where I've examined the records in PORCPH1 and PORCPAH and I've been unable to find a date in either of those tables that matches what's populated the ICHIST.TRANSDATE field. Also, data integrity found no errors.
Aside from user error is there a system logic rule for populating this field that is something other than ICHIST.TRANSDATE = the header document date?
Thanks,
Ian
Doing some auditing reports and noticing there are circumstances where ICHIST.TRANSDATE is different than the [DATE] field from most of the document header tables (PORCPH1, POINVH1, etc) in the PO module. This isn't a high percentage amount, but I'm being asked why.
I have some specific examples where I've examined the records in PORCPH1 and PORCPAH and I've been unable to find a date in either of those tables that matches what's populated the ICHIST.TRANSDATE field. Also, data integrity found no errors.
Aside from user error is there a system logic rule for populating this field that is something other than ICHIST.TRANSDATE = the header document date?
Thanks,
Ian