Share
Report
40eConnect10 behaves oddly when importing PM batch transactions with Inclusive tax schedule: trx in batch shows up nicely, but the Distributions validation shows tax issues and the document cannot be Saved. Tax details zoom is fine as to data shown, but the trx consistently fails validation until the tax details are manually zeroed, the purchase total re-entered, and the tax engine recalculates the tax details. Same data and details exist, to both the naked eye on the GP Payables Transaction Entry forms, and to a before and after SQL query. After the recalculation, validations pass and the trx can be saved.
Whereas, same invoice, same data (adjusted for the tax regime, naturally), and a tax exclusive (% of total purchase) schedule, goes straight in, can be saved immediately, no fuss.
Is this an undocumented feature, a known issue, or what?
Workaround is to force an Exclusive schedule via the xslt stage (we're using MSMQ and xslt transforms to get our PM data shaped for eConnect, and it should go without saying that there are no eConnect failures).
*This post is locked for comments
All responses (
Answers (
