Tienes acá la versión en español

Yesterday on LinkedIn I told you about the disaster at the chemical company. A sick leave, a volatile currency (Colombian Peso vs USD/EUR), and a manual process led to selling products at a loss.

The Mindset Shift

10 years ago, we solved this with Java programs, flat files, and EDI. It was expensive, hard to maintain, and required a developer.

Today, I still see companies doing this manually because they don't trust "new tech" with critical data like Money.

Here is the irony: You trust a human to copy-paste a number from a website to a screen (P0015A) without typos, but you don't trust a direct secure connection to the Central Bank?

The Logic

We need to stop thinking about "Data Entry" and start thinking about "Data Fetching."

  1. Source of Truth: Your Central Bank (they all have open APIs now).

  2. The Carrier: JDE Orchestrator (Connector).

  3. The Executor: JDE Orchestrator (Form Request).

  4. The Watchdog: JDE Orchestrator (Notifications).

I have designed a 7-step recipe that covers everything: fetching, updating, reporting, and alerting if something fails. It’s the exact lab I use to teach my students because it uses almost every Orchestrator feature.

I'll give you the step-by-step tutorial on Thursday. Prepare your Central Bank API URL.

Best,

Mario Garcia

Reply

or to participate