We stopped complaining and started designing. The problem wasn't JDE. The problem was the rigid rule.

We needed JDE Orchestrator to act like a sensible human being. So, we defined the "Common Sense Criteria":

  1. Is the excess less than 5% of the total limit?

  2. Does the customer have zero invoices overdue by more than 30 days?

If the answer is YES, the risk is negligible. We didn't need a button. We needed an Orchestration to ask these questions for us.

If you know someone drowning in manual JDE checks, forward this. If you agree, let me know.

Reply

Avatar

or to participate