This page (revision-32) was last changed on 26-Nov-2021 10:22 by Karen Parrott

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
32 26-Nov-2021 10:22 12 KB Karen Parrott to previous
31 26-Nov-2021 10:22 12 KB mmcfarland to previous | to last
30 26-Nov-2021 10:22 12 KB kparrott to previous | to last
29 26-Nov-2021 10:22 12 KB jmyers to previous | to last
28 26-Nov-2021 10:22 12 KB JMyers to previous | to last
27 26-Nov-2021 10:22 12 KB JMyers to previous | to last
26 26-Nov-2021 10:22 13 KB JMyers to previous | to last
25 26-Nov-2021 10:22 16 KB JMyers to previous | to last
24 26-Nov-2021 10:22 16 KB JMyers to previous | to last
23 26-Nov-2021 10:22 16 KB RForbes to previous | to last
22 26-Nov-2021 10:22 16 KB JAiken to previous | to last
21 26-Nov-2021 10:22 15 KB JEscott to previous | to last

Page References

Incoming links Outgoing links
IPSN
IPSN

Version management

Difference between version and

At line 7 changed one line
The processing frequency for the sundry transaction may be defined through the [IPPF] form. If the sundry transaction has a frequency of one time only, once it becomes a pay line in a pay header ([IPPH]), it is removed as a sundry (IPSN). The history is then kept with the pay header.
The processing frequency for the sundry transaction may be defined through the [IPPF] form. If the sundry transaction has a frequency of one time only, once it becomes a pay line in a pay header ([IPPH]), may be removed depending on the IPPF toggle [KEEP_HISTORY]. If this toggle is turned ON, then the IPSN record will not be removed, but the status will be changed to 'Completed-1 time'.
This page (revision-32) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop