Skip to main content

Extract and Process

The Extract and Process screen runs an extraction followed by a processing step in a single click. It is the runtime equivalent of running one of the Extract pages and then the matching Processing page back-to-back, with the same parameters surfaced on a single form.

The extraction half offers the same three sources documented under Extract:

  • Extract Archive — pull an archived document from the NomaUBL database (F564230 source XML or F564231 generated UBL) by document key.
  • Extract FTP — download a file from an SFTP server using the JDE-style report / version / language / job key.
  • Extract BIP — extract a JD Edwards BIP Print Queue job (input XML, rendered output, or both).

The processing half offers the same two pipelines documented under Processing:

  • Process Document — single processing entry point. The pipeline (XML transformation or direct UBL validation) is selected by the document template's source property. Replaces the legacy Process XML and Process UBL pages.

The page applies regardless of source system — JD Edwards, SAP, NetSuite or a custom ERP — except for the BIP source, which is JD Edwards-specific.

At a glance​

Extract and ProcessSourceArchiveFTPBIP (JDE)JOB NUMBER42803LANGFREXTRACT MODEInput (XML) ▾Process TypeXMLUBLTEMPLATEinvoices ▾MODEAUTOSend to PAUse settings▶ Run extract + processExtraction Result✓ BIP job 42803 extracted → dirInput/invoices/R42565_FBL00001_42803.xmlProcess ResultSEVERITY · MODULE · SUBMODULE · MESSAGESUCCESSXSL · transform · 1 document → UBL 2.1SUCCESSPA · submit · 200 Submitted · post-gen applied to BIP 42803Source selectorArchive · FTP · BIPSource-specific fieldsreshape with sourceProcess typechains XML or UBL pipelineSingle CTAruns both stepsTwo result panelsextraction halts processing

Pipeline at a glance​

▶ Run⚙ Sourcedecision📦 Extract ArchiveF564230 / F564231🌐 Extract FTPSFTP server🖨 Extract BIPJDE Print QueueArchiveFTPBIP📄 Extracted filein dirInput/template/⚙ Extraction OK?decision⛔ Haltskip processingNo⚙ Process TypedecisionYes⚙ Process Document (XML)SINGLE / BURST / UBL / AUTO⚙ Process Document (UBL)Validate / Persist / SubmitXMLUBL⚙ Post-generationJDE job status update📋 Process Resultaggregated outcome

The chain runs in two steps. The extraction step writes a file to dirInput/<template>/; on success, the matching processing pipeline picks it up. Any failure on the extraction step stops the chain — the processing step is skipped and only the Extraction Result carries a message.

Source​

The Source selector at the top picks one of the three extraction channels. The form below adapts to the chosen source.

Archive​

Pulls an archived document by its database key.

FieldDescription
DOCDocument number — primary key of the archived document.
DCTDocument type code (e.g. RI, RN).
KCOCompany code (e.g. 00070).

The extracted file is written to dirInput/<template>/ (with %TEMPLATE% resolved) under the name <DOC>_<DCT>_<KCO>.xml (or _ubl.xml if the source side is UBL). See Extract Archive for the full reference.

FTP​

Downloads a file from the configured SFTP server.

FieldDescription
ReportJDE-style report name (e.g. R42565).
VersionReport version (e.g. XJDE0001).
LanguageLanguage code (e.g. FR).
JobJDE job number.

The extracted file is written to dirInput/<template>/<REPORT>_<VERSION>_<LANG>_<JOB>.xml. See Extract FTP for the full reference.

BIP​

Extracts a job from the JDE BIP Print Queue.

FieldDescription
Job NumberJDE BIP job number (RJJOBNBR).
LanguageOptional BIP language filter.
Extract ModeExtract Input (XML), Extract Output or Extract Both. See Extract BIP for the semantics of each.

The extracted file's base name (<report>_<version>_<job>) is reused as the input for the processing step.

Processing​

Below the source selector, the Process Type picks between the two pipelines.

Process Type = XML​

Equivalent to running the Process Document page on the just-extracted file when the chosen template's source = XML.

FieldDescription
TemplateDocument template — required. Drives the XSL pipeline and the validation rule set.
ModeAUTO, SINGLE, BURST or UBL. See Process Document — Modes (XML source).
ReplaceSkip keeps existing invoices untouched; Overwrite re-imports them.
Send to PAUse settings (default) or Skip sending.

After a successful run, when the source is BIP, an additional Apply post-generation call updates the JDE job status — typically marking the BIP job as processed.

Process Type = UBL​

Equivalent to running the Process Document page on the just-extracted file when the chosen template's source = UBL. The extracted file must already be UBL — typical when:

  • the Archive source is set with the UBL flavour;
  • the upstream system emits UBL directly;
  • the BIP source is set with Extract Output and the JDE report emits UBL XML as its output (not PDF). In that case the UBL files retrieved from F95631 are picked up directly by the UBL pipeline — no XSL transformation runs.
FieldDescription
ModeProcess & Validate (full pipeline) or Validate only.
Replace ModeOverwrite existing (default) or Skip.
Send to PAUse settings, Force send or Skip sending.

The (doc, dct, kco) primary key is parsed from the invoice's cbc:ID via the document template's idPattern regex — filenames can be anything. See Documents → Key extraction from cbc:ID for the regex setup.

Combinations not supported​

SourceProcess TypeStatus
BIP, Extract Mode = BothUBLNot supported — the extracted set contains both XML and rendered output, which cannot be processed as UBL.
BIP, Extract Mode = Both with multiple output rowsXMLRejected — the extraction produces several files, the XML pipeline expects a single file per run.

A clear error appears in the Process Result section when one of these combinations is attempted.

Results​

The screen splits the outcome into two sections:

  • Extraction Result — the message returned by the extraction API; populated first.
  • Process Result — the structured log table from the processing step (same columns as on the XML and UBL pages: Severity / Module / Submodule / Message); populated only when the extraction succeeded and the processing actually ran.

If the extraction fails, the processing step is skipped — the chained run halts on the first failure.

Tips & best practices​

  • Use Extract and Process for single ad-hoc runs. The page combines two operations on one screen, so retrieving and processing one document needs a single click. For repeated unattended runs, prefer Sync → Fetch Input — it iterates the same pipeline in batch.
  • Match the Process Type to the extraction output. The combinations table above lists the unsupported pairs; cross-check the BIP extract mode against the chosen process type before clicking Run.
  • For a BIP-driven workflow, leave the Process Type at XML. It runs Apply post-generation on success, which updates the JDE job status — without it, the same job will be re-extracted on the next run.
  • The Extract Result keeps the raw API output. When something goes wrong on the extraction side (missing job, file not found, SFTP credentials), the message returned by the extract API is the canonical diagnostic — read it before re-running.
  • Skip sending while iterating on a template. Both halves expose the option (No send / Skip sending) — use it during template development to avoid producing duplicate PA submissions across iterations.