Creating a User-Defined Process (Release 9.2.26.2)
You can configure a user-defined process model, as well as metrics and analytics related to that model, for any business process for which there is data in the EnterpriseOne system using the Enterprise Process Manager.
For example, you can configure a process model, along with metrics and analytics, for the lifecycle of a lease, or the tracking of work order stages if a preconfigured template is not available.
The business process you design must have the following data in your EnterpriseOne system in order to define the process:
-
Some type of document, item, or other record on which the lifecycle of the process can be based. For example, you might design a process around the lifecycle of a work order, a lease, an expense report, and so on. That document, item, or other record might even be defined by multiple fields. For example, the preconfigured template for Order to Cash is based on the lifecycle of a document type (DCTO = SO) and is further defined by a line type (LNTY = S).
-
Some data item associated with that document, item, or record that describes a state that changes, such as a status. The values for those states are defined in user-defined code (UDC) tables. For example, the preconfigured template for Order to Cash is based on tracking the Last Status (LTTR) and Next Status (NXTR) fields of sales order documents, and the allowable values for Last Status and Next Status (220, 230, 240…) are stored in a UDC table. You will use those states to define the nodes and links in the Process Definition application, which in turn generates the process diagram. This data is also used as a context sensitive filter to provide metrics and analytics on nodes and links. If you want to add metrics to links, then you will need two states to identify and filter data based on the start of the link and the end of the link.
Before you begin to use Enterprise Process Manager to create an enterprise process model, study your JD Edwards business data for these data elements.