Duaer

Guides

JD Edwards purchase to pay and order to cash: see where each order waits

Connect JD Edwards EnterpriseOne to Duaer. A read-only database user reads the steps of each purchase or sales order.

What does Duaer read from JD Edwards?

Each purchase order (order type OP) or sales order (SO) is a case, with the supplier or customer, the company, currency and amount. The steps are:

  • Purchase to pay: Order created (F4301), Goods received (F43121 receipt records), Invoice posted (F0411 vouchers), Paid (F0413/F0414).
  • Order to cash: Order created (F4201), Goods issued (the actual ship date in F4211), Invoice created (F03B11), Paid (F03B13/F03B14).
  • Lines at status 980 (canceled) are left out. The steps match the purchase to pay or order to cash template.

How do you connect JD Edwards to Duaer?

  1. In JD Edwards' Oracle database, create a read-only user with SELECT on the tables above and F0101 and F0010 in the data schema (usually PRODDTA).
  2. If the database is only inside your network, start the Duaer on-premises data gateway (0.2.0 or later) there with tcp://database-host:port in ALLOWED_TARGETS; the credential's host and port must match it.
  3. In Duaer, create an Oracle Database Credentials API credential for this user.
  4. As an owner or admin, open Data sources, select Add source, choose JD Edwards under Purchase to pay or Order to cash, choose the credential, enter the schema when it is not PRODDTA, select Check connection and confirm.

How often does it read, and how much?

Each run reads orders, receipts or shipments, invoices and payments by their last update date, one page each at most. JD Edwards update dates carry no time, so each read starts at the beginning of the day again; a step is never written twice. Queries only.

What are the limits?

  • The tables, entities and fields read follow the vendor's published documentation and are not yet checked against a real system; the first real read may need adjustments.
  • JD Edwards on Oracle Database only for now; SQL Server and DB2 follow.

Questions

Which schema do I enter?

The schema of JD Edwards business data: usually PRODDTA in production, often CRPDTA in a test environment. Empty means PRODDTA.

In this section

Process

Add a process source in Duaer

A process source tells Duaer where to read the steps of your cases: a CSV or XLSX file, files dropped in an S3 or SharePoint folder, PostgreSQL, MySQL, Microsoft SQL, Oracle, TiDB, OceanBase, KingbaseES, SAP HANA, IBM Db2, Dameng DM8, Teradata, Vertica, Snowflake, BigQuery, Databricks, Microsoft Fabric, Amazon Redshift, Azure Synapse Analytics, ClickHouse, Trino, a Feishu Base, or Feishu, DingTalk or WeCom approvals. The wizard takes you through columns, mapping, a preview of issues and a schedule; after you confirm, Duaer reads new rows on that schedule.

Process

See the process in your data and generate workflows in Duaer

Duaer reads the steps every case went through from the tables, databases or Feishu apps you already have: where cases wait too long, where they branch and who did each step. From that it generates three kinds of workflow, Watch, Coordinate and Execute, and replays each over past days before you publish it.

Process

Process findings and SOP conformance in Duaer

Process findings list the steps where cases wait too long or are done again, and which kind of case they happen to most. Propose any of them as a card rule and compare the 30 days before and after it was adopted. SOP conformance compares the SOP in your knowledge base with the steps cases really took.

Follow-through

Oracle EBS purchase to pay and order to cash: see where each order waits

Connect Oracle E-Business Suite (R12) to Duaer. A read-only database user reads the steps of each purchase or sales order.

Follow-through

PeopleSoft purchase to pay: see where each purchase order waits

Connect PeopleSoft FSCM to Duaer. A read-only database user reads each purchase order's steps from requisition to payment.