Duaer

Guides

Kingdee EAS purchase to pay and order to cash: see where each order waits

Connect Kingdee EAS to Duaer. A read-only database user reads the steps of each purchase or sales order.

What does Duaer read from Kingdee EAS?

Each purchase or sales order is a case, with the supplier or customer, the company, currency and amount.

  • Purchase to pay: purchase orders (T_SM_PurOrder), purchase receipts (T_IM_PurInWarehsBill), AP bills (T_AP_OtherBill), payments (T_CAS_PaymentBill).
  • Order to cash: sales orders (T_SD_SaleOrder), sales issues (T_IM_SaleIssueBill), AR bills (T_AR_OtherBill), receipts (T_CAS_ReceivingBill).
  • Only audited or closed documents are read; AP and AR bills, payments and receipts reach the order through their core bill.

How do you connect Kingdee EAS to Duaer?

  1. Ask your database administrator for a read-only user with SELECT on the tables above and the supplier, customer, company and currency tables.
  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 Kingdee EAS under Purchase to pay or Order to cash, choose the credential, enter the schema when the tables are not in the user's own, select Check connection and confirm.

How often does it read, and how much?

Each run reads orders, receipts or issues, AP or AR bills, and payments or receipts by their last update, one page each at most; a step is never written twice. Queries only.

What are the limits?

  • The tables and fields read follow the vendor's published data dictionary and are not yet checked against a real system; the first real read may need adjustments.
  • Kingdee EAS on Oracle Database only for now.

Questions

Is this for Kingdee K/3 Cloud too?

No. K/3 Cloud is Kingdee Cloud Galaxy, which has its own source reading its WebAPI.

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

NetSuite purchase to pay and order to cash: see where each order waits

Connect NetSuite to Duaer. It reads the documents each purchase order and sales order goes through with SuiteQL, so you see where orders wait and for how long.