JDE product · Transactions, testing and interfaces

Run JD Edwards like an orchestration.
Without building one.

Define a JDE transaction once. Swivio posts it through the JDE forms you already use and tests it again after every ESU, tools update or Code Current cycle: with full business logic, your users' security and test runs that save nothing.

Five problems you know.

Each video shows a problem from everyday JDE work and how Swivio solves it.

A thousand orders, after every updateIn developmentThe whole sales process as a test: order to sales update, a thousand times, overnight in the test environment, documented and signed off.
No orchestrationEvery new process needs an orchestration and a developer. Swivio builds the app from the program itself.
From ExcelTyping in a hundred orders? Upload the file, test, post. Every order number comes back.
A warehouse without paperScan, enter the quantity, posted. With Swivio Go on the phone, with your own JDE user.
After the updateAfter an ESU, tools update or Code Current: your processes run overnight as a test suite, the report is there in the morning.

Narration: AI-generated voice. Images from the Swivio demo, no customer data.

What Swivio looks like

Screenshots from the Swivio demo against a real JD Edwards, no customer data.

  1. Build it automatically
    Tested on JDE

    Build it automatically

    Name the program and version, for example P4210. Swivio reads the forms and event rules, takes example values from your JDE data, builds the app and proves it with a test run that saves nothing.

  2. App designer with phone preview
    Tested on JDE

    App designer with phone preview

    Set per field how it is entered: keyboard, scan, choice, default or fixed value. The preview beside it is Swivio Go itself; every change shows at once.

  3. Swivio Go on the phone
    Tested on JDE

    Swivio Go on the phone

    Sign in with your own JDE user, fill in or scan the fields, post. The order number from JDE shows on the phone at once.

  4. Excel and CSV upload
    Tested on JDE

    Excel and CSV upload

    Download the template, fill it in, upload. A test run first, then post to JDE. Every row gets its order number and a test report.

Automated testing

After every ESU, tools update and Code Current cycle: your processes tested end to end.

Today key users test by hand for days after every update, or nobody tests at all. With Swivio you set up your processes once. From then on the complete run is meant to go through the test system at the push of a button, from order to invoice, with the documentation ready. Test runs and a log per transaction exist today; test suites with the report as a document are built and in trial, the whole sales process as a test is in development.

  1. 1Set up onceDescribe processes from the JDE forms you already use.
  2. 2Real casesTest cases from real documents of a period.
  3. 3Apply the updateESU, tools release or Code Current into the test system.
  4. 4Run end to endAll processes post in the test system, compared field by field with the original.
  5. 5DocumentationReport per process and case: passed or not, with every form and message. For sign-off and auditors.
  • Test run without posting

    JDE checks every value right up to saving, nothing is posted.

    ✓ Available
  • Log of every run

    Which form, which value, which button, which JDE message.

    ✓ Available
  • Production protected

    Tests only run in approved test environments; production is locked in the code.

    ✓ Available
  • Check forms after updates

    The form catalog shows which fields or buttons are missing after the update.

    ✓ Available
  • Test suites

    Many cases at once, on a schedule, compared with the last run.

    In trial
  • Whole process chains

    The sales process from order to sales update as one test, a thousand times.

    In development
  • Test report as a document

    For sign-off, change management and auditors, to file or as PDF.

    In trial
Test suite with report
In trialTest suite with reportEvery run compared with the run before, a report to print or save as PDF, and sign-off.
The whole sales process as a test
In developmentThe whole sales process as a testDiagram: order (P4210), acknowledgement (R42565), pick slip (R42520), shipment (P4205), invoice (R42565), sales update (R42800).

Pilot customers wanted: we test your next ESU or tools update together with you, in your test system and with your real processes.

Apply as a pilot

This is what the log looks like today

02:17:00ERRORFor every transaction a developer builds its own orchestration: create form requests, map fields, test, roll out per environment.
03:34:01ERRORAfter every ESU or tools update every orchestration has to be checked again.
04:51:02ERRORFull extracts run every night, although hardly anything changed.
Swivio

Define it once.
Post it through the forms.

Swivio reads the JDE forms itself: fields, grid and buttons. A transaction is defined once and then posts straight through the forms. Business functions, processing options and validations apply as they do for a user. Nothing is built in JDE. For data out of JDE, interfaces detect every change in JDE tables and pass exactly that on.

Four steps to the first posting

  1. Read the formsSwivio reads fields, grid and buttons from your test environment, never from production.
  2. Define the transactionSet inputs, steps and mapping once, plus a key against double postings.
  3. Test runUp to just before saving: JDE checks every value, nothing is posted.
  4. PostIn approved environments, with the JDE user. After an interruption it continues from the last successful step. If the outcome is unclear, a person decides – never an automatic retry.

And afterwards

02:17:00OKDefine the transaction once
03:34:01OKSwivio reads the forms itself
04:51:02OKThe catalogue shows what changed
05:08:03OKChanged records only
swivio.properties
swivio.jde = No JDE objects changed. Apps need only AIS; interfaces read the JDE database
swivio.runtime = Windows setup or Linux package
swivio.data = Own state database, PostgreSQL

What Swivio is used for

  • Sales orders from other systems

    A web shop, portal or partner system calls Swivio. The order is created in JDE, with JDE pricing and checks.

  • Intercompany

    An order in company A creates the purchase order in company B.

    In development
  • Quote becomes order

    An accepted quote becomes a sales order, without retyping.

    In development
  • Shortage becomes purchase order

    On a shortage or reorder point, Swivio creates the purchase order.

    In development
  • Data out of JDE

    Interfaces detect every change in JDE tables and deliver it via REST, to a database, as a file or via SFTP.

  • EDI and inbound data

    Inbound messages enter JDE through the JDE interface tables and JDE logic.

The sales order has been proven in a test against JD Edwards (tools 9.2.26.3). Transactions started by JDE data need triggers from JDE data; those are in development.

Everything Swivio does

39 features

In development Announced and in progress, not yet in the current release. Ask us for the current status.

In trial Built and part of the release, currently being tried with real processes on JD Edwards.

Capture

Change data capture

Through update stamps or a change log; only real changes become events.

Capture

Real-time trigger from JDE

Optional: an orchestration in JDE reports changed keys, Swivio reads at once. Without it, Swivio polls.

optional
Capture

Status changes and deletes

Recognised as events of their own.

Deliver

REST and SOAP

With signature, OAuth 2.0 and retries on errors.

Deliver

Databases

PostgreSQL, SQL Server, Oracle, IBM i, with upsert.

Deliver

Files, SFTP, mail, AS2

Kafka and message queues too.

Deliver

Order and safety

Order per key, circuit breaker per target, test mode without sending.

Into JD Edwards

Inbound interfaces

Data into Z and EDI tables, processed by JDE logic.

Into JD Edwards

Required fields and number ranges

Fixed values, batch and transaction numbers by rulebook.

Into JD Edwards

EDI

Orders and ship notices through EDI tables.

Operations

Incidents and escalation

One incident per problem, escalation by mail, Teams or Slack.

Operations

Resend

Snapshot, replay or resend of single events.

Operations

Four eyes

New and changed interfaces go live only after approval.

Operations

Sign-in

OpenID Connect or Active Directory, roles in the portal.

Apps: posting transactions into JDE

Posting through the JDE forms

Through AIS, without an orchestration per transaction. The JDE logic and the user's security apply. Tested against JD Edwards (Tools 9.2.26.3): a sales order created this way, document number returned.

Apps: posting transactions into JDE

Test run

Up to just before saving: JDE checks every value, nothing is posted.

Apps: posting transactions into JDE

No double posting

One key per transaction. A run resumes after the last successful step. If the outcome is unclear, a person decides instead of an automatic retry.

Apps: posting transactions into JDE

Production protected

Tests and reading the forms never run in production. Apps write only to approved environments.

Apps: posting transactions into JDE

With your own JDE user

Every run signs in with the JDE user, no technical super user. Passwords are not stored.

Apps: posting transactions into JDE

Form catalogue

Swivio reads the structure of the JDE forms. Every run compares the form with the catalogue and reports fields or buttons that went missing after a tools update, an ESU or a personalisation.

Apps: posting transactions into JDE

Triggers

Via REST from any system that can call a web API, by Excel and CSV upload and with Swivio Go on the phone. Schedules and triggers from JDE data are next.

Apps: posting transactions into JDE

AIS is all it needs

Apps run without database access, also with self-signed AIS certificates.

Apps: posting transactions into JDE

Keep what you have

Swivio does not replace the Orchestrator. Existing orchestrations stay as they are. Swivio saves you the orchestration per transaction.

Swivio Go: phones and scanners

Web app without an app store

Add it to the home screen, sign in with the JDE user. Every app as a tile with large fields.

Tested on JDE
Swivio Go: phones and scanners

Scanning

With the camera or a handheld or Bluetooth scanner.

In development
Swivio Go: phones and scanners

Posting offline

Without a network the posting waits on the device and goes out once it is online again. Sent twice, it posts only once.

In development
Swivio Go: phones and scanners

Look-ups before posting

A scanned item shows its description from JDE at once, or “not found”.

In development
Swivio Go: phones and scanners

Photo and signature

After posting, attached to the record in JDE as a media object, e.g. a delivery note or damage.

In development
Swivio Go: phones and scanners

Approvals on the phone

Approve or reject with a summary; a rejection needs a reason.

In development
Processes, approvals and tests

App editor without code

Enter a program such as P4210, pick the fields or record the transaction in test. Templates for sales order and receipt.

Tested on JDE
Processes, approvals and tests

Excel and CSV upload

Download the template, fill it in, upload. Rows become postings, in the background and without double postings when uploaded again.

Tested on JDE
Processes, approvals and tests

Processes

Apps and JDE reports (UBE) in sequence; results such as the order number pass to the next step. Templates in the process library.

In development
Processes, approvals and tests

Check steps

After posting, Swivio reads JDE tables and checks that everything is as expected, e.g. the next status.

In development
Processes, approvals and tests

Approvals

Rules by amount or role, four eyes, reminders and escalation. Small amounts can pass automatically. The approver posts with their own JDE user.

In development
Processes, approvals and tests

Test suites

Many cases at once in test, on a schedule, compared with the last run, with sign-off and a report.

In trial
Processes, approvals and tests

Test report per run

Every run records each form, value, button and JDE message involved.

Design and migrate

Interface designer

Map fields by dragging, target structure from OpenAPI, XSD or a sample.

Design and migrate

AI interface designer

A draft from a description, with questions instead of guesses.

optional
Design and migrate

Taking over legacy interfaces

Read existing programs and compare in shadow mode.

Your path with Swivio

Swivio logs every run step by step: actions sent, messages from JDE, results such as the document number, JDE user and time.

  1. Stage 1

    First transaction

    Read the forms, define the transaction, test run, post.

    Your progressPosted without an Orchestrator project.
  2. Stage 2

    More transactions

    Every new app is a definition. Test run, adjustment and approval happen in one place.

    Your progressNew transactions without a project each.
  3. Stage 3

    After the next update

    Re-read the forms in test after the update. The catalogue shows changed fields and buttons.

    Your progressYou see it before an app fails in production.
  4. Stage 4

    Data out of JDE

    Interfaces pass changes on to web shop, CRM or logistics.

    Your progressTransactions and interfaces in one portal.

See Swivio in your environment?

Tell us briefly what it is about. We will get back to you within two working days.

Talk to us