1. Demand Flow Manufacturing Implementation Guide
  2. Understanding Scenario Setup

Understanding Scenario Setup

Before you can use JD Edwards EnterpriseOne Demand Flow Manufacturing, you must define scenarios using the DFM Scenario Master program (PF30L010). Scenarios control all activities in JD Edwards EnterpriseOne Demand Flow Manufacturing. Use this functionality to create what-if scenarios. You have to determine which scenario is the active scenario in the system. Only one scenario can be active at one time. Scenarios enable you to:

  • Hold a set of imported JD Edwards EnterpriseOne Manufacturing data or base data that was created in JD Edwards EnterpriseOne Demand Flow Manufacturing and is specific to the scenario.

  • Define control parameters for line design and planning.

  • Perform data retrieval and storage during any JD Edwards EnterpriseOne Demand Flow Manufacturing function.

The system uses scenarios to segment the business data tables in JD Edwards EnterpriseOne Demand Flow Manufacturing; thus, you can work with a set of data without affecting data that is associated with a different scenario.

When you set up a scenario, the system automatically adds the following hard-coded components to the scenario:

  • SCRAP and END_OF_LINE process.

  • Default labor and machine resources.

  • Default cell.

You use scenarios to define parameters for line design and for planning, For line design, you can specify default values for shift information, sequencing, and units of measure. For planning, you can associate a branch calendar, for example a shop floor calendar that you have defined in JD Edwards EnterpriseOne Manufacturing, with the scenario to use for back scheduling. The planning parameters are stored in the DFM Planning Parameters table (FF34S003).

Note: Because data is specific to a scenario, you have to specify the scenario when you are importing data into JD Edwards EnterpriseOne Demand Flow Manufacturing. In the same way, for exporting data, you specify which scenario to export the data from. You cannot export the scenarios themselves to other JD Edwards EnterpriseOne systems, because scenarios are not supported in these systems.

To use JD Edwards EnterpriseOne Demand Flow Manufacturing, you first have to define the default user scenario using the DFM Default User Scenario program (PF30L013). You associate the scenario with the user profile based on the login ID. When you use any of the JD Edwards EnterpriseOne Demand Flow Manufacturing applications, the scenario that you have defined as the default user scenario automatically becomes the default scenario for the application. You can also associate a branch/plant with the default user scenario. This branch/plant becomes the default branch/plant for all applications that use a branch/plant.

Note: When you set up a scenario, the system displays a message asking you whether you want to make the scenario that you just created the default user scenario.

Deleting a scenario also deletes all records in JD Edwards EnterpriseOne Demand Flow Manufacturing that are associated with the scenario. When you attempt to initiate a deletion, the system issues a warning that you have to accept before the deletion is accomplished. The system does not delete the default unit-of-measure conversion that you set up for JD Edwards EnterpriseOne Demand Flow Manufacturing because this conversion is not associated with a scenario.

For copying scenarios, the system provides you with two different copy functions. You can use the Copy button on the Search for Scenarios form to copy the line design and planning parameters from the current scenario to a new scenario that you want to create.

If you want to copy not only the scenario information, but also the entire set of Demand Flow base data or imported JD Edwards EnterpriseOne Manufacturing data that is associated with the scenario, you use the Copy Data Within Scenario batch program (RF30L010). This program also copies line design data that you have created in the original scenario, for example, processes, lines and mixed model families, to the new scenario. By using this batch program, you can avoid having to set up base data for the new scenario or reimport them from JD Edwards EnterpriseOne Manufacturing.