Article

Article Body

Overview

Project-based manufacturing is typically used by a manufacturer that builds to order or engineers to order. Also, a manufacturer might have a requirement to operate and manage a contract-by-contract basis. The operational and financial activity for a specific contract can be managed with the Project Capability.

The Project control functionality provides a centralized point to access and review all the operational aspects of a Project. The main activities associated with the Project are shown in the diagram below.

The manufacturing activities associated with a Project are the normal manufacturing activities. These include Requisitions, Purchase Orders, Inventory Transactions, Work Orders, Labor transactions, Sales Orders, Demand Forecasts, and a history of all operational transactions. Also, the Project Master record contains the subtotaled Project Cost and Project Cost Details.

Application

The Project function supports the identification of Sales Orders, Forecasts, Inventory (by Project), Purchase Requisitions, Purchase Orders, and Work orders to a Project. Also identified in the Project are all operational transactional activities including Shipments, Labor, Purchase Receiving, Work Order Receiving, and Inventory movement, including any Indirect or Service purchases specified for the Project. Material Requirements Planning (MRP) can also be run by the Project.

The Project master is the base or fundamental record for Project manufacturing. Once a division has been configured with Projects active, the Project Masters are set up. From then on, all manufacturing activities are associated with a Project.

Terminology

Types of Projects – “Home” and “Non-Home”

There are two types of projects defined in Rootstock. One project per division is identified as 'Home,' and automatically created and assigned as the “Home” Project when a Manufacturing Division record is created. All other Projects in that Division are defined as 'Non-Home' Projects.

Home Project: The common items used within a Project Control Division are typically associated with the 'Home' Project. A single Home Project is established for a Division and is always defined as the Home Project. Examples of items assigned to a Home Project might be fasteners or common wiring items used in multiple Projects.
Non-Home Project: The 'Non-Home' Projects are set up for a particular Customer or Customer order. An example of an item assigned to a 'Non-Home' type of Project might be a unique drive set to be manufactured only for this Project. 'Non-Home' assigned items are those acquired or manufactured only when there is demand in a Project for the item.

User-added image NOTE A Project may use both 'Home' and 'Non-Home' items.

Material Requirements Planning (MRP)

When the Project control function is active in a Division, and the MRP planning run is launched, it may be selected to run for a specific Project or for all Projects. When selected for a single Project, only Demands and Supplies with that specific Project identifier are planned.

NOTE image.png NOTE However, when a single Project is planned, all 'Home' Project items are planned with Demands from all Projects. When MRP is run for all Projects, all Projects within the Division are planned.

Navigation

Project Master

Processing

Header

Fields

Division: Division in which the Project Master is being entered.

Project No: A unique identifier for this project in this Division. This is blank for Home Projects.

Description: Description of the Project.

Project Status: Select from the Project Status picklist dropdown. There is no system logic associated with the Project Status. It is available for each customer to use in any way that suits the organization's needs. For example, it could be used to represent Milestones, providing easy visibility to the completion stage of each project.

Job Codes Active: This is an optional field. If the field is checked, then the use of Job Codes is active for this Project.

Project Charge Code Active: This is an optional field. If the field is checked, then the Charge Code is active for this Project.

Details Tab

Fields

Account, Negative Variance:  This account is only used if the option for Account Source on the Division Master is set to use Project Accounts; otherwise, the account will default to the Inventory Commodity Code accounts of the Commodity Code assigned to the Item. If the Division option is set to use Project Accounts, then the account entered here will be used to capture transaction costs for all negative inventory variance amounts.

Account, Inventory Adjustment:  This account is only used if the option for Account Source on the Division Master is set to use Project Accounts; otherwise, the account will default to the Inventory Commodity Code accounts of the Commodity Code assigned to the Item. If the Division option is set to use Project Accounts, then the account entered here will be used to capture transaction costs for all inventory adjustment amounts.

Account, Inventory:  This account is only used if the option for Account Source on the Division Master is set to use Project Accounts; otherwise, the account will default to the Inventory Commodity Code accounts of the Commodity Code assigned to the Item. If the Division option is set to use Project Accounts, then the account entered here will be used to capture transaction costs for all inventory amounts.

Account, Non-Nettable Inventory:  This account is only used if the option for Account Source on the Division Master is set to use Project Accounts; otherwise, the account will default to the Inventory Commodity Code accounts of the Commodity Code assigned to the Item. If the Division option is set to use Project Accounts, then the account entered here will be used to capture transaction costs for all non-nettable inventory amounts.

Account, WIP:  This account is only used if the option for Account Source on the Division Master is set to use Project Accounts; otherwise, the account will default to the Inventory Commodity Code accounts of the Commodity Code assigned to the Item. If the Division option is set to use Project Accounts, then the account entered here will be used to capture transaction costs for all WO WIP amounts.

Account, WO Scrap:  This account is only used if the option for Account Source on the Division Master is set to use Project Accounts; otherwise, the account will default to the Inventory Commodity Code accounts of the Commodity Code assigned to the Item. If the Division option is set to use Project Accounts, then the account entered here will be used to capture transaction costs for all WO scrap amounts.

Account, WO/Subc PO Variance:  This account is only used if the option for Account Source on the Division Master is set to use Project Accounts; otherwise, the account will default to the Inventory Commodity Code accounts of the Commodity Code assigned to the Item. If the Division option is set to use Project Accounts, then the account entered here will be used to capture transaction costs for all WO or Subcontract PO variance amounts.

Accounting Dimension Value:  If Dimensions are being used, then this field will have a list of selections available for selection if the Project is configured as one of the Dimensions. If so, the selectable values are created in the Rootstock Company Master for whichever Dimension value is designated as the Project Dimension. If a value is selected here, then any transactions where the Project is pertinent will have the selected value stamped as the Project Dimension.

Project Completed:  When checked, the system will disable transactions from being processed for this Project. If the field is not checked, this Project is available for all transactions.

MRP (Planning) Bypass:  When checked, the system will exclude this Project for all MRP runs. If the field is not checked, this Project is available for all MRP runs.

User-added image NOTE This flag can be checked on the Project Master record only if the below conditions are satisfied:

MRP Bypass cannot be set for the Home Project
A project must be set to Completed
Quantity Outstanding must be ZERO on all Supplies and Demands
All Supplies and Demands must be closed

The last three (2, 3, and 4) conditions need not be satisfied if the flag 'Allow MRP Bypass on Open Projects' is checked on the Division Master record.

PO Charges Allowed Ind:  This is an optional field that will disable Purchase Order transactions from being processed for this Project. If the field is checked, this Project is available for all Purchase Order transactions.

WO Charges Allowed Ind:  This is an optional field that will disable Work Order transactions from being processed for this Project. If the field is Checked, this Project is available for all Work Order transactions.

SO Allowed Ind:  This is an optional field that will disable the creation of Sales Orders for this Project. If the field is Checked, this Project can create new Sales Orders.

SO Shipments Allowed Ind:  This is an optional field that will disable the shipment of Sales Orders for this Project. If the field is Checked, this Project is available for all Sales Order shipment transactions.

Related Project:  This is an optional field for specifying a related project. The selected value must be a valid Project. This field is for reference only and no logic is connected with it.

Default Payment Gateway:  Select from the Payment Gateway picklist dropdown. The selected Payment Gateway will be used as default.

Title	Project Master

URL Name	Project-Master