My Oracle Support Banner

E1: 40: Subsystem Processing (Doc ID 625418.1)

Last updated on MARCH 21, 2018

Applies to:

JD Edwards EnterpriseOne Sales Order Entry - Version XE and later
JD Edwards EnterpriseOne Sales Order Management - Version XE and later
JD Edwards EnterpriseOne Sales Order Processing - Version XE and later
JD Edwards EnterpriseOne Inventory Foundation - Version XE and later
JD Edwards EnterpriseOne CRM Sales Order Entry - Version XE and later
Information in this document applies to any platform.

Purpose

Overview

Subsystem jobs are batch processes that continually run independently of, but asynchronously with, EnterpriseOne applications. These EnterpriseOne subsystem jobs function with the system’s logical process or queue defined for the server platform. This type of job runs until a user requests an end to the job. Subsystem jobs read records one at a time from a subsystem table, retrieve information from the particular record, and run a configurable processing engine for each record. At the end of processing a record the subsystem job will wait for a specific period of time and then retrieve the information for each subsequent record. For each subsystem job, there can be multiple records in the subsystem table.

When an EnterpriseOne application issues a request for a job to run in an EnterpriseOne subsystem, it places a record in the table F986113 via the ubeReport_AddSubsystemRecord Tools API. This record is identified by a subsystem job name and version, and contains status and operational indicators. Embedded in the record is key BLOB (Binary Large Object) information that allows the EnterpriseOne subsystem to process the record without additional interaction with the requesting application. The continuously running subsystem job monitors the records in the F986113 table. If the subsystem finds a record with its name, version, and appropriate status indicators then it processes the record and updates the status accordingly. Once a record is processed it is deleted from the table.

Since a subsystem job runs continuously it must be run in a separate print queue or run in a multi-threaded print queue.

Scope

 

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Subsystem Kernel
 Server INI Settings
 OCM Mappings
 Defining a UBE to Run In Subsystem Mode
 Example of Subsystem Process Flow
 Application/Middleware side
 UBE/Middleware side
 Terminating a Subsystem UBE
 Troubleshooting Subsystem Examples
 ISSUE 1 - Unable to End Subsystem
 ISSUE 2 - Subsystem Waiting Jobs
 ISSUE 3 - Subsystem Pick Slips not going to the printer
 ISSUE 4 – Subsystem R42520 does not process order at Next Status 521
 ISSUE 5 – Subsystem R42525 does not launch from P4205
 ISSUE 6 – What is the difference between stopping and ending subsystem processes?
 ISSUE 7 – What is the correct sequence to start and stop subsystem processes such as R00460?
 ISSUE 8 – Overwrite PDF in subsystem
 ISSUE 9 – Subsystem vs. Submitted UBEs
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.