Before You Begin

This 30-minute Oracle by Example (OBE) shows how to use the Enterprise Process Modeler tool to import a preconfigured Requisition template to build a process model with connected process that drills down into the purchase order process from the requisition process. You can also view and analyze these connected processes.

In this OBE, you will:

• Use the Enterprise Process Manager tool to import a preconfigured process template and create a process model for the Requisition process.
• Connect the Purchase Order process from the requisition process.
• Analyze the Requisition process and the connected Purchase Order process.

Important: This OBE uses standard demo data available in the JD Edwards EnterpriseOne Trial Edition, as well as most EnterpriseOne development and test environments. Depending on the data in your system, the process models and metrics may look different to what is shown in this OBE.

For more details about analyzing the features in Enterprise Process Modeler see, Analyzing Business Processes Using Enterprise Process Modeler.

Background

Enterprise Automation is the next evolutionary step after process automation. The tools, techniques, and disciplines of Enterprise Automation enable the ingestion of data that has been collected for years in JD Edwards systems, the visualization of that data as process models and metrics about how the enterprise is running, and its analysis toward the aim of improvement. At its core, Enterprise Automation uses process models, metrics, and key performance indicators (KPIs) to help see a data-driven picture of the business. Beginning with JD Edwards EnterpriseOne Release 25, you can use Enterprise Process Modeler with Connected Processes (Tools Release 9.2.9.3) to accomplish this.

Scenario

In this 30-minute OBE, let’s consider a scenario in which you are the process owner for your company’s Requisition and Purchase Order processes. Your job is to be vigilant over that processes and look for ways to optimize and improve them. To that end, you want to visualize the end-to-end Requisition process and drill-down to the Purchase Order process.

For this scenario:

• Acting as a business analyst or power user, you will create a Requisition process and drill-down to the Purchase Order process using a preconfigured template.
• Acting as a process owner, you will interact with the Requisition and Purchase Order process models to analyze the data and identify the opportunities for improvement.

When you complete the steps in this OBE, your process model will look similar to this:

What Do You Need?

To perform the steps in this OBE, you will need:

• Access to a JD Edwards EnterpriseOne environment with Release 25 (Tools Release 9.2.9.3) or later. JD Edwards EnterpriseOne Trial Edition running on Oracle Cloud Infrastructure is suitable, but you can use any environment with the proper Tools release.
• Feature security and UDO action security for Enterprise Process (PROCESS).
• Availability of enterprise process templates. These templates are available as user-defined objects (UDOs) from the JD Edwards Update Center and can be applied by your system administrator.

Creating a Process Model from a Process Model Template

A process model template contains many preconfigured components, for example, a mapping to the EnterpriseOne tables from which data is read, the metrics, and KPIs for the process. You can create one or more process models from the same template.To demonstrate the steps described in this section, the Requisition process template is used.

1. Sign in to the EnterpriseOne web client.
2. From the EnterpriseOne home page, click the drop-down list under your user ID, click Manage Content, and then click Processes. The Create Process window is displayed, prompting you to select a process template.

   

   Note: The Create Process window is only displayed when you are creating a new enterprise process. After creating a process, when you click Processes again, the system displays the previously created process layout along with the template used for its creation and the design time options. To create a new process, select (Create) from the Name drop-down list.

3. On the Create Process window, from the Import Process Template drop-down list, select JDE TMPL Requisition, and click OK.

   The following fields are displayed with default values:

   Field Name	Default Value	Description
   Order Type	OR	Process models are based on tracking the flow of a document through its statuses. This input lets you choose what order type to track. “OR” indicates requisition order type.
   LineType	S	Process models further track the line type for orders. “S” indicates stock items.
   Purchase Order Type	OP	“OP” indicates purchase orders.
   Requisition Process (Parent Template)
   Color Theme		Select the color from the Color Theme drop-down list and select the node from the Start Status drop-down list.
   Start Status	Enter Purchase Requisition (100)	Enterprise Process Manager creates the process model from data in the order activity rules for purchase requisitions. This field indicates the status at which the parent process starts.
   Purchase Order Process toggle is enabled by default. You can disable the option to remove the connected template.
   Color Theme		Select the color from the Color Theme drop-down list and select the node from the Start Status drop-down list.
   Entry Status		The Entry Status node determines the node from where the connected process starts from the parent process. The node you select in the Start Status field becomes the first (start) node in the child process.
   Start Status	EnterPurchaseOrder (220)	Enterprise Process Manager creates the process model from data in the order activity rules for purchase orders. This field indicates the status at which the process starts.

   

4. Accept the default values and click OK.

   Enterprise Process Manager reads data from the EnterpriseOne tables and generates the process model.

5. Click Save. The Enter New Name window is displayed.
6. In the Enter New Name window, enter a name for your process model, such as Reqn Demo, and click OK.

   To indicate that a child template is linked to a node, the Enterprise Process Manager shows a circular node in the specified color scheme. In the following example the child template linked from the Generate PO from Requisition node (indicated by the Cyan color).

   

7. Click Close.

   You have now created a process model that your users can interact with to analyze the Requisition process and Purchase Order process.

   Note: Within the EnterpriseOne system, process models are managed as user-defined objects (UDOs). You must follow the UDO life cycle management processes to create, revise, publish, and approve process models for use by selected users or roles using UDO security.

Analyzing Parent and Child Processes Using Enterprise Process Modeler

In the previous section, you took on the role of business analyst to create a process model from a preconfigured template. In this section, you will take on the role of a user, likely a business process owner or a process improvement specialist, to interact with the process model and analyze the Requisition process based on actual data from the EnterpriseOne tables and drill down to the Purchase Order process.

1. If you are not already signed in, sign in to the EnterpriseOne web client.
2. From the EnterpriseOne home page, click the drop-down list under your user ID, and then click Enterprise Processes.

   The Enterprise Process Modeler window is displayed showing the process model you created by following the steps described in the previous section.

   Note: If a different process model is displayed, you can select your process model from the Select Process drop-down list.

   In the following steps, you will navigate through the Enterprise Process Modeler user interface and discover ways to visualize and analyze the Requisition process model, its connected child process,and associated metrics.

3. The fundamental part of the Enterprise Process Modeler is the model pane, which depicts the process model as a set of nodes connected by links. Notice that both nodes and links have associated metrics.

   

   Hover over the circular node to view information, such as the connected process, status code, and metric details on the hover form.

4. The child process is displayed based on the selected color themes. In the following example, the connected child process is indicated by a circular node in cyan color (Purchase Order). You can right-click this node and click Drill into Connected Process to open the child process window.

   

   You can select the processes from the hierarchy window that displays the parent (Requisition) and child (Purchase Order) processes. To view and analyze the child Purchase Order process from the hierarchy window, click Purchase Order (in cyan color).

   

Conclusion

In this Oracle by Example (OBE), you learned how to:

• Use Enterprise Process Manager to create a process model from a preconfigured template.
• Connect to the purchase order process from the requisition process.