Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

KFS has its web services to perform account validation. Making web services to perform accounting line validation is probably a good idea.  We'll need to survey the feeder folks to determine which webservice protocols they're able to use and the expected volumne of transactions.  Given the complexity of accounting-line validation, this is probably something we'll want to release during our roll-out.

14)  It appears from the documentation that the scrubber posts the valid transactions from the pending area to the GL and the pending area is
cleared. The error transactions are moved into a separate file ("demerge"). Need more information on this step. Do any notifications go
out informing us of failed transactions? Am I correct in understanding that we would then fix the offending transactions in the external system
and then send them again via the feeder system to this GLPE area? Since transactions will be every day in the GL customers should not need our
Financial Report and could get that information from Kuali.  

Again, a direct feed does not use the Pending Table (pending is only for on-line transactions).  The scrubber posts output of Collector or Enterprise job.
Any error transactions are moved to an error file where the accounting staff will make corrections and push them through – we have a UI for it (GLCP document).The access to this screen is limited to the super user in the accounting area. They will work the people in the functional areas when correcting the errors the same as they do now.  The error file is one single file which will contain feeds from various feeder
systems.