This chapter contains the following topics:
To use JD Edwards EnterpriseOne Engineer to Order, you must set up information that the system needs to process various project components correctly. JD Edwards EnterpriseOne Engineer to Order setup includes UDCs and other required information, such as document type constants. To be able to roll up project costs correctly, you also must set up project-specific items, as well as a cost classification scheme.
If you use features of JD Edwards EnterpriseOne Project Costing for a project, you also must create job-master and chart-of-account information for the project.
To facilitate project communication with individuals who do not have access to the Project Workbench program (P31P001), you can set up a process for exporting project information to Microsoft Project.
This section discusses:
Task types for ETO projects.
Line type and line type constants for ETO.
JD Edwards EnterpriseOne Engineer to Order enables you to use several different task types as part of the work breakdown structure. Each task type represents a different type of activity that is related to the project that might require different actions on the part of the project manager and responsible project employees. You can use only task types that are set up in the Document Type Maintenance program (P40040).
JD Edwards EnterpriseOne Engineer to Order includes two categories of tasks: production and nonproduction tasks. Nonproduction tasks include summary or detail tasks, equipment orders, and service orders. Production tasks consist of discrete manufacturing work orders that you use to build something. Production tasks are always associated with an item, whereas item numbers are optional for nonproduction tasks. All tasks in a work breakdown structure are work-order master records that are stored in the Work Order Master Table (F4801).
The task type also determines how the cost roll-up is set up and performed. For production tasks, costs are mapped by cost type and are stored in the Production Cost table (F3102). For nonproduction tasks, costs are mapped by account and are stored in the Account Ledger table (F0911).
When you work with ETO projects, you must be able to distinguish the material that you purchase or produce for the project from general inventory. If you do not define the items that you use for the project as project specific, you might experience difficulties in terms of project supplies. Defining project-specific material enables you to:
Maintain project-specific inventory commitments.
Recognize end items as project specific at completion.
Perform project-specific financial commitments.
You do not have to setup all inventory as project-specific inventory. Only items that are critical to the project should be setup as project-specific. You use material requirements planning to plan all items that are used across various projects.
You define project-specific items by assigning them one of two codes from the Stocking Type Code UDC table (41/I) when you set up the item in the Item Branch/Plant program (P41026). The system currently provides two predefined codes: G (for items that are manufactured for a project) and H (for items that are purchased for a project). Both codes include a special handling code of P to indicate that items that are set up with these two stocking types are treated as project specific by the system. For planning purposes, the Description 2 field contains the code that indicates whether the item should be purchased or manufactured.
In addition to defining items as project specific by assigning them a specific stocking type, you also set up project-specific items with a line type that enables you to maintain financial commitments for items that are used in projects. When you set up project-specific items in the Item Branch/Plant program (P41026), you assign them a line type that is defined with an inventory interface of C. You set up the inventory interface along with other line type constants for the line type in the Line Type Constants program (P40205).
This inventory interface enables you to make financial commitments for stock items. Inventory Interface C combines the features of inventory interface Y (Inventory) with A (GL Account) and B (GL Account and Non-Stock). The ability to create financial commitments enables the project manager to calculate projected final cost by using the JD Edwards EnterpriseOne Job Cost system.
Note:To make financial commitments, you must define commitment document types in the Commitment Document Type UDC table (40/CT).
You can also select the Call Materials Issue option for the line type to enable the system to automatically issue material that is purchased for a work order upon receipt of the material.
Define document type constants.
|Order Type (48/OT)||This table enables you to distinguish each work order record in the Work Order Master table (F4801) from other records with different work order types. For example, you do not use the same document type and work order type to represent both an equipment work order and a manufacturing work order.|
|Cost Classification (31P/CC)||This table lists the cost buckets that are used in the Project Workbench program (P31P001) to categorize the costs that are stored in the Production Cost (F3102) and Account Ledger (F0911) tables for visibility and rollup in the work breakdown structure for a project.|
|Project Quote Status (31P/QP)||This table provides the definitions of the statuses that the system uses to track the progress of the different quote versions that you create when you generate a proposal for a customer. The system provides five quote statuses that are hard-coded.|
|Project Quote Inactive Reason Code (31P/RC)||This table lists reasons why quotes are set to an inactive status.|
|Task Dependency Type (31P/DT)||This table lists the standard task dependency types that you can use to establish dependencies between the tasks on the work breakdown structure.|
|Stocking Type Code (41/I)||This table lists the stocking types that you assign to items in the Item Master program (P4101). You use the stocking type code to designate an item as project specific.|
|Commitment Document Types (40/CT)||This table lists the document types that are considered for financial commitments.|
|Project Accounting (31P/AI)||This table lists the automatic accounting instructions (AAIs) that are set to enable project accounting.|
|Project Billing Method (31P/PB)||This table lists the available project billing methods that you can select for the project on the Add/Revise Project form.|
|Distribution Requirements Planning (34/DR)||This table lists project-specific quantity types for distribution requirements planning (DRP).|
|DRP Unadjusted (34/DU)||This table lists project-specific quantity types for unadjusted DRP.|
|Electronic Mail Boxes (02/MB)||This table includes electronic mailboxes for project notifications.|
|Inventory Interface (H40/IV)||This table includes inventory interface C to enable financial commitments for projects with a Job Cost interface.|
|Maintenance Material Planning (34/MM)||This table lists project-specific quantity types for material maintenance planning.|
|Master Production Schedule (34/MS)||This table lists project-specific quantity types for master production scheduling (MPS).|
|Plant Maintenance Management (34/PM)||This table lists project-specific quantity types for plant maintenance management.|
|Material Requirements Planning (34/MR)||This table lists project-specific quantity types for material requirements planning (MRP).|
|Quantity Type (34/QT)||This table lists project-specific quantity types for supply and demand.|
|Resource Assignment Level (48/RL)||This table specifies whether resource assignments are at the level of the work order or the work-order labor detail, based on the document type of the work order. To make assignments at the labor detail level, you must use this UDC table to specify the work order document type. You use resource assignments UDC 48/RL for equipment and service orders only. UDC 48/RL is not used for manufacturing work orders.|
This section provides an overview of cost and account classifications and discusses how to:
Set processing options for Cost Classification (P31P301).
Set up cost classifications.
Set up account classifications.
One of the most important priorities for a project manager is the ability to control the costs that are associated with a project. To maintain control of the budget, the project manager must be able to review the actual costs that are reported for any project task at any point in time throughout the project life cycle. The actual costs must be associated with the same cost buckets that are available for the estimated costs so that the project manager can compare the estimated, budgeted, or planned costs with the actual costs at any stage of the project. In addition, mapping costs to the correct cost buckets enables the system to roll up costs for each level of detail to the next parent level in the work breakdown structure and to the project level. Examples of cost buckets that are used in the Project Workbench program (P31P001) are labor, material, other, and special. You set up these cost buckets as UDCs in the Cost Classification UDC table (31P/CC).
The Cost Classification program (P31P301) enables you to map costs to cost buckets either by cost type or by account number. These options accommodate the fact that a project can contain two types of tasks: production tasks, such as discrete manufacturing work orders, and nonproduction tasks, such as project management tasks, travel, and so on. You can retrieve the actual costs that are associated with production tasks from the Production Cost table (F3102), where they are stored by cost type. The costs that are associated with nonproduction tasks are stored in the Account Ledger table (F0911). Therefore, you must associate the appropriate accounts with the user-defined cost buckets to make costs for nonproduction tasks visible to a project manager and roll them up to higher levels in the project structure.
You can define cost type and account mappings for one of these combinations:
Branch/plant and project number of a particular project.
Branch/plant of a project, where the project number is blank.
All branch/plants and projects (both fields remain blank).
The previous list defines the hierarchy that the system uses to retrieve the correct categories for displaying costs in the Project Workbench program and for rolling up actual costs. This information is stored in the Cost Classification table (F31P21).
|Work with Cost Types||W31P301A||Cost Classification (G31P31), Cost Classification||Locate and review cost types or accounts.|
|Revise Cost Types||W31P301B||Click the Add button on the Work with Cost Types form.||Set up cost classifications.|
|Revise Account Numbers||W31P301B||Click the Add button on the Work with Account Numbers form.||Set up account classifications.
Note: Set the processing options to display the account number or cost type form.
This processing option controls whether you can work with cost types or with account numbers when using this program.
Specify how the system displays the program. Values are:
Blank or 1: Cost Type.
2: Account Number.
Enter a code that designates each element of cost for an item. Examples of the cost object types are:
A: Purchased raw material.
B1: Direct labor routing rollup.
B2: Setup labor routing rollup.
C1: Variable burden routing rollup.
C2: Fixed burden routing rollup.
Dx: Outside operation routing rollup.
Xx: Extra add-ons, such as electricity and water.
The optional add-on computations usually operate with the type Xx (extra add-ons). This cost structure enables you to use an unlimited number of cost components to calculate alternative cost rollups. The system then associates these cost components with one of six user-defined summary cost buckets.
Select a value from the Cost Classification UDC table (31P/CC) to associate cost types or account numbers with cost buckets, such as material costs, labor costs, other costs, or special costs. Correct cost classification ensures that costs are rolled up into the correct cost bucket in the Project Workbench program (P31P001).
To display the Revise Account Numbers form, you must set the processing option for the Cost Classification program (P31P301) to display the program by account, rather than cost type.
This section provides an overview of Job Cost integration, lists a prerequisite, and discusses how to add a chart of accounts for a project.
Depending on the company's business requirements, you can select to integrate the JD Edwards EnterpriseOne Job Cost system with JD Edwards EnterpriseOne Engineer to Order. You can use the features of JD Edwards EnterpriseOne Job Cost to perform profitability analysis and to use the service and contract billing features that you can access from the JD Edwards EnterpriseOne Job Cost system. Using the JD Edwards EnterpriseOne Job Cost and JD Edwards EnterpriseOne Engineer to Order systems together might be particularly beneficial in a complex manufacturing environment that includes long-term projects.
You need JD Edwards EnterpriseOne Job Cost integration to perform financial commitments for manufacturing work orders. To make financial commitments for manufacturing work orders, you must set up the manufacturing work order document type in the Commitment Document Types UDC table (40/CT).
To enable project-specific accounting, you use the Special Handling Code field in the Project Accounting UDC table (31P/AI) to set up these AAIs to include project-specific accounts:
3110 (Inventory/Raw Material)
3120 (Work in Process)
3130 (Subassembly/Finished Goods)
3140 (Project Contra)
To activate the JD Edwards EnterpriseOne Job Cost system when you set up the attributes for a project, you select the Interface to Job Cost option in the project attributes. To use the features of the JD Edwards EnterpriseOne Job Cost system, you must define a GL class code. Next, you must create a record in the Extended Job Master table (F5108). The business unit from the extended job master record becomes the default business unit for the project header and tasks. You must add a chart of accounts that provides the subsidiary accounts that you assign to the project and the tasks. If job cost integration is activated, each task in the work breakdown structure requires a subsidiary.
Note:If you set the processing option for creating a job master record, the system automatically calls the Job Cost Master Revisions program (P51006) as you are adding or copying a project.
To add a chart of accounts, you use the Job Cost Code Structures program (P51091). Instead of adding the chart of accounts interactively, you can set a processing option to copy the chart of accounts from another record. In this case, you must specify the source (chart of accounts or job) and the name of the chart or job from which to copy the chart-of-account information.
After you add the chart of accounts, you assign subsidiary accounts to the ETO project and tasks. You can use the Subsidiary field to enter the desired subsidiary account for a task. You can also set a processing option to copy subsidiaries from a parent task to all its child tasks.
To copy the chart of accounts in the background, use the processing options for the Project Workbench program (P31P001) to select either a chart of accounts or a job as the copy source for the job.
|Search for Projects||W31P001B||Project Workbench (G31P12), Project Workbench||Locate the project for which you want to set up job cost integration.|
|Add/Revise Project||W31P011A||Select Attributes from the More Row Actions field and select >> on the Search for Projects form.||Specify integration with Job Cost.|
|Copy Cost Codes||W51091J||Select Copy Chart of Acc from the Form menu on the Add/Revise Project form.||Add a chart of accounts for a project by specifying the name of the chart of accounts or job from which to copy chart-of-account information.|
Enter the chart of account type to copy to the job for the project.
Note:If you specify in the processing options that the copy source is a job, this field appears with the label Job, and you select the job from which to copy cost codes.
Select the job or business unit to which you want to copy cost codes for the selected project.
Define the range of subsidiary accounts to copy to the project. The system uses this information to determine cost allocation.
Define the range of object accounts for the project.
Specify the level of detail for the project accounts. The system uses this value to summarize and classify the accounts in the general ledger.
This section provides an overview of the ETO export and import process and discusses how to:
Set processing options for Export to MS-Project (R31P404) and Import from MS-Project (R31P801).
Export ETO project information to Microsoft Project.
Import ETO project information from Microsoft Project.
When working with JD Edwards EnterpriseOne Engineer to Order, you can use Microsoft Project to take advantage of some of the features of that program that complement ETO features. You can export the work breakdown structure (WBS) that you created in the Project Workbench program (P31P001) to a Microsoft Project file. After you export the WBS, you can use the graphical features that are provided by Microsoft Project, such as Gantt charts, PERT diagrams, and so on, to represent project information in a more visual format. You can make changes to the Microsoft Project file to perform what-if analyses without affecting the original WBS. Finally, you can also share the exported project information with an audience that might not have access to the project information in the Project Workbench program.
These processing options control how the system moves files between JD Edwards EnterpriseOne Engineer to Order and Microsoft Project.
Specify the name of the flat file. This includes the directory path where the flat file exists.
(Ex. C: \Project.csv)
Specify the format of a date as it is stored in the database. The date format that you specify in the processing option must match the system date format. The date format in the MS Project file should also match the system date format.
For JD Edwards EnterpriseOne programs, these date formats are valid: YMD, MDY, DMY, EMD. If you leave this field blank, the system displays dates based on the settings of the operating system on the workstation. In Microsoft Windows NT, the regional settings in the Control Panel control the settings for the operating system of the workstation.
When you export project information, the system creates a comma-delimited flat file (.csv) that contains all of the fields in the Work Order Master table (F4801) for all of the task records in the WBS. The system saves the flat file to the location that you specified in the processing options for the Export to MS-Project program (R31P404).
To ensure that the export runs successfully, you must define this information in MS Project:
Open MS Project, name a project file, and save it with a Microsoft Excel Workbook filetype.
Click the Save button to display the Export Mapping form.
Click the New Map button on the Selective Data tab.
Enter a name for the import/export map on the Define Import/Export Map form.
On the Options tab, verify these selections and values:
Tasks option in the Data to import/export group box.
Export header row/Import includes headers in the Microsoft Excel options group box.
Text delimited value of '.'.
When you open the flat file in Microsoft Project, the system prompts you to map flat file fields to corresponding fields in the Microsoft Project file that you want to create. For the integration to work properly, you must map these fields to the corresponding Microsoft Project fields:
|Flat File||Microsoft Project||Comment|
|SEQN||Unique ID||The system uses the task sequence field to determine the Microsoft Project task ID.|
|DL01||Name||In Microsoft Project, all tasks must be named.|
|STRT||Start||This field is required to create a Gantt chart.|
|DRQJ||Finish||This field is required to create a Gantt chart.|
|Successors||Successors||This field is required to display task links in Microsoft Project.|
|Outline Level||Outline Level||This field is required to display parent/child relationships in Microsoft Project.|
|DOCO||Text01||This field is required to import information from Microsoft Project.|
|DCTO||Text02||This field is required to import information from Microsoft Project.|
|PARS||Text03||This field is required to import information from Microsoft Project.|
All other fields are optional. Save the export mappings.
To be able to re-import the Microsoft Project file back to the Project Workbench program, you must correctly map the files as defined in the table in the previous section. JD Edwards EnterpriseOne Engineer to Order provides a Microsoft Project template that includes a standard mapping.
After you set up the project in Microsoft Project, you can make changes as needed and communicate the information to others. When you save the file, you save it as a .csv file and select the same mapping that you used for importing the flat file into Microsoft Project. The resulting .csv file contains all of the fields that are listed in the mapping specification.
Note:The inbound import capability is limited.
When working with the project in Microsoft Project, you must apply these rules to be able to import the project file back to the Project Workbench program successfully:
You cannot add tasks to or delete tasks from the WBS.
The system enables you to import records that you originally exported back to the Project Workbench program.
You cannot change some fields.
You must express the lag time for dependencies in days.
After you make changes, you can import the .csv file back to the Project Workbench program. You use a processing option for the Import from MS-Project program to specify the location of the flat file that you are importing.
Note:When you export project information to a flat file to be read by Microsoft Project, you must specify the location of the flat file. Depending on the operating system and server, you can specify the location of a file in various ways. For example, in a UNIX environment, the flat file is a binary file, and the directory structure is different from the folder structure in a Microsoft Windows environment.
To run the export and import process smoothly, use a Microsoft Windows-based file system to specify the path and the file name, mainly because Microsoft Project works best in Microsoft Windows.
Other setup might include setting the date format on the workstation to be consistent with the processing options for the Export to MS-Project and Import from MS-Project programs.