Pcs UP055A US Baan

BaanERP Manufacturing
Project Control System
Module Procedure UP055A US

Documentinformation
Document
Document code : UP055A US
Document group : User Documentation
Document title : Project Control System
Edition :A
Date : May 1998
© Copyright 1998 Baan Development B.V. All rights reserved

The information in this document is subject to change without notice. No part of this document
may be reproduced, stored or transmitted in any form or by any means, electronic or mechanical,
for any purpose, without the express written permission of Baan Development B.V.
Baan Development B.V. assumes no liability for any damages incurred, directly or indirectly, from
any errors, omissions or discrepancies between the software and the information contained in this
document.

Table of contents
1. The Project Control System (PCS) module in BaanERP 1-1

1.1 The concept as applied in BaanERP 1-1
1.2 BaanERP Project Control’s functional procedures 1-2
1.3 The modules that are related to PCS 1-3
1.4 The functionality of PCS’s business objects 1-5
2. The create a project procedure 2-1
2.1 The create a project procedure 2-1
2.2 The sessions that are related to the main procedure 2-7
2.2.1 Copy Project (tipcs2210m000) 2-7
2.2.2 Delete Project (tipcs2270m000) 2-7
2.2.3 Print Inventory Values of Projects to Close (tipcs2402m000) 2-7
2.2.4 Maintain Project Details (tipcs2530m000) 2-7
3. The create a budget procedure 3-1
3.1 The create a budget procedure 3-1
3.2.1 Create Sales Order (tdsls4500m000) 3-5
3.2.2 Generate Sales Order Line (tdsls4501m000) 3-5
3.2.3 Generate Project Structure for Sales Order (tdsls4244m000) 3-5
4. The engineer a project procedure 4-1
4.1 The engineer a project proocedure 4-1
4.2.1 Delete Customized Product Structure (tipcs2233m000) 4-5
5. The project-calculation procedure 5-1
5.1 The project-calculation procedure 5-1
6. The network-planning procedure 6-1
7. The Link with Finance business object 7-1

i
ii
The Project Control System (PCS) module in BaanERP
About this document

Read this document to get an overview of the Project Control System (PCS)
module’s functionality and to learn more about the functional procedures that
are related to PCS.
You need no detailed knowledge of the BaanERP software to read this
document. However, you are more likely to understand the contents if you are
familiar with:
n The overall structure of packages, modules, and sessions within the
BaanERP software
n The general business procedures used in everyday business practice
n The basic concepts of enterprise resource planning
For detailed descriptions of the module’s sessions, refer to BaanERP’s
comprehensive online Help.
To use this document

Read Chapter 1, The Project Control System (PCS) module in BaanERP, if you
want to know more about:
n The module’s functionality
n The relationship of the module with other modules
n The functionality of the module’s business objects
Read Chapters 2, 3, 4, 5, 6, and 7 if you want to know more about:
n The sessions in the procedures
n The results of the procedures
n The sessions that are related to the procedures
n The optional procedures that are related to the procedures

1
Acronyms used in this document

BOM Bill of Material
CF Configurator
CP Constraint Planning
CPR Cost Price Accounting
FAS Final Assembly Schedule
HRA Hours Accounting
IBD Item Base Data
IPD Item Production Data
PCS Project Control System
PUR Purchase
ROU Routing
SFC Shop Floor Control
SLS Sales
SOC Service Order Control
TP Project package
TRP Tools Requirerments Planning
TS Service
WH Warehousing
Legend
Mandatory Indicates a mandatory session
session
Optional Indicates an optional session

session
Mandatory Indicates a mandatory business object

business object
Optional Indicates an optional business object

business object
Indicates a package
CF
Indicates a module
PCS
Indicates a module that is described in the module procedure

PCS

2
1. The Project Control System (PCS) module in BaanERP
This chapter provides information on:

n The concept as applied in BaanERP
n The functional procedures of BaanERP PCS
n The functionality of the business objects of PCS
1.1 The concept as applied in BaanERP

The BaanERP Project Control System (PCS) module is used in to-order
production situations. You can also maintain projects in the BaanERP Project
package. Projects from the BaanERP Project package (TP) are mostly long-term
projects. For example, the building of a power plant or the building of a bridge.
PCS covers the following components of customer order-driver production and
purchasing:
n Estimating
n Engineering
n Planning
n Costing
n Control
The items can be of the following types:
n Standard anonymous
Standard anonymous items can be sold by a project. The item will be
delivered from the warehouse. The cost of goods sold and the revenues
gained are taken into account in a project’s estimated and actual costs. The
item cannot be produced by the projects.
n Standard-to-order
With standard-to-order items, PCS is used for material planning and
production. Project engineering can be carried out when the Project
Engineering check box is selected.
When the project is created, the standard product structure is copied to the
project. This means that standard bills of material, and routing and costing
structures are taken from:
− The BaanERP Bill of Material (BOM) module
− The BaanERP Routing (ROU) module
− The BaanERP Cost Accounting (CPR) module
When the project is created, engineering of the project is created.
n Customized
The bills of materials and the routing and costing structures can be defined
for specific projects. Customized items can be derived from engineering
items, standard items, or generic items.

1-1
n Product variants
A product variant can be produced in two ways:
− By using a job-shop type of production. The planning and production is
fully controlled by PCS. The order system of the generic item must be
planned.
− By using a line assembly production. The planning is controlled by the
Configurator package. The order system must be final assembly
schedule (FAS).
1.2 BaanERP Project Control’s functional procedures

BaanERP Project Control contains a few functional procedures, which control
the planning, production, and execution of a project. Project control consists of
a main procedure (main flow), displayed in Figure 1, and a few functional
procedures.
Project Data
Project Engineering
Project Calculation
Project Planning
Project History
Figure 1, The main flow of PCS

1-2
The procedures of PCS are:

n Creating a project
n Creating a budget
n Project Planning
n Project Engineering
n Project Calculation
n Project History
1.3 The modules that are related to PCS
IPD ROU SLS

BOM WH
IBD TRP PUR
CPR PCS TS
HRA CF
SFC TP
CP
Figure 2, The modules that are related to PCS
PCS is related to the following BaanERP Manufacturing modules:

n The BaanERP Item Production Data (IPD) module contains production data
such as routing unit and phantom yes/no.
n The BaanERP Bill of Material (BOM) module provides the standard bill of
material data. The data is copied to the project for customized items,
standard-to-order items and anonymous items.
n The BaanERP Routing (ROU) module provides the standard routing data.
The data is copied to the project to customize standard to order and
anonymous items.
n The Cost Accounting (CPR) module is used for the calculation of estimated
project costs. Operation rates, subcontracting rates, material surcharges, and
operation surcharges for the production of customized items are defined by
price calculation code in the CPR module. In addition, project specific rates
and surcharges are defined in the Project Control (PCS) module.

1-3
n The Hours Accounting (HRA) module is used to retrieve the number of

hours spent on the project. The number of hours spent on a project are used
to calculate the actual project costs.
n The Shop Floor Control (SFC) module is used to retrieve calculation data,
which is then used to calculate actual project costs.
PCS is related to the following BaanERP modules:
n The Item Base Data (IBD) module in BaanERP Common is used to define
the order system and order method of standard and generic items.
n The Sales (SLS) module in BaanERP Warehousing contains actual costing
data.
n The Purchase (PUR) module in BaanERP Distribution contains actual
costing data.
n The Service Orders (SOC) module in BaanERP Service can contain service
order costs.
n In BaanERP Configurator, generic item structures (bills of material, routing,
and option based prices) are defined. As a result product variants can be
generated. Two possibilities then occur:
− There is an order for a normal generic item (not FAS). You can use the
Generate Product Variant for Project Item (tipcs2220m000) session to
create a project.
− There is an order for a generic item with order system FAS. In this
situation, planning, forecasting, critical material explosion, and order
acceptance is done in BaanERP Configurator.
n Projects from BaanERP Project can be linked to projects in the BaanERP
Projects module. The project drives the requirements for the PCS project
items. BaanERP transfers financial information from the PCS project
module to BaanERP Project when the PCS project is closed. The progress
on a PCS project can be monitored from BaanERP Project.

1-4
1.4 The functionality of PCS’s business objects

Depending on the type of project (main project or subproject) the Network
Planning business object and the Module Planning business object are not
mandatory.
n Project Data
With this business object you can maintain a variety of data, for example:
projects, project status, project type, project stages, project parts, and
project structure. Projects can be closed, archived, deleted or copied.
n Network Planning
The purpose of network planning is to deliver rough materials planning and
capacity planning of the project. This is used to estimate project lead time
and required capacity. The Network Planning business object is used to
maintain the data required to carry out a network planning. It is possible to
define activities and relations between activities. Capacity load tables
indicate how the rough capacity requirement is divided over the activity
duration. The rough utilization for each project shows the rough capacity
requirement per activity per week.
n Module Planning
This business object is used to establish relations between the activities of
the network planning and the project items. Network planning must have
been generated first. If a module is defined, the delivery date of items is
always calculated from the activity network. A module can be used to
define items quantities that are different from the sales-order quantity.
Module planning can be used for the planning of critical materials with long
lead times or delivery times, and for the control of delivery dates when non-
production activities take place after production.
n Project Engineering
A product variant structure can be generated for a project, but only if the
generic item is of the type planned. It is possible to copy a standard or
customized product structure to a project and to copy a customized product
structure to a standard product structure. The definition of a customized bill
of materials and routing is done in the BOM and ROU modules.
n Project Calculation
This business object allows the user to maintain the data required for the
estimated cost price calculations as well as the actual cost price calculations
of a project. Operation rates, subcontracting rates, and cost price surcharges
can be defined by project in the CPR module. The estimated item price is
calculated in the CPR module. In the Project Calculation business object it
is possible to define general project costs and calculate the total project cost.
The project cost is based upon the cost of items and the cost of activities.

1-5
n Project History
With the Project History business object you can display or print the
historical data of projects and production orders. The data related to
purchase orders, sales orders, and inventory transactions is stored in the
Distribution package and Warehousing package. Figure 1 shows how the
module is positioned in BaanERP.
n Link to Finance
With the Link to Finance business object you can view, delete, and print the
work in process (WIP) transactions that are posted to the Finance package
from PCS.

1-6
2. The create a project procedure
This chapter describes:

n The main procedure
n The sessions that are related to the main procedure
2.1 The create a project procedure

The procedure describes the ways a project can be created. You can create a
project in several ways:
n Enter a project manually in the Projects (tipcs2501m000) session
n Copy a budget to a project or copy an existing project to a project using the
(tipcs2210m000) session
n Generate a project from a sales order with the Generate Project Structure for
a Sales Order session (tdsls4244m000)
n Customize an item in the Activity Budget Material Lines (tpptc2510m000)
session
n Customize an item in the Element Budget Material Lines (tpptc1510m000)
session

2-1
The create a project procedure
Figure 3 shows the steps in the create a project procedure.
2
Calculation office
(tcmcs0565m000)
1 Generate Project
Structure for Sales 3
Orders (tdsls4244m000) Calculation office
(tcmcs0565m000)
Copy Projects
(tipcs2210m000)
4
Element Budget Projects
Material Lines (tipcs2501m000)
(tpptc1510m000)
Activity Budget 5
(Material Lines) Maintain Project
(tpptc2510m000) Structure (tipcs2530m000)
6
Project Parts
Project Engineering
(tipcs2511m000)
7
Network Planning
9
Project Status
Module Planning
(tipcs2502m000)
Project Calculation
8
Close Project
(tipcs2250m000)
10
Archive Project
(tipcs2260m000)
Figure 3, Creation of a project

2-2
The procedure consists of the following steps.

Step 1 Creation of a project
You can create a project without having to manually enter a new project in the
Projects (tipcs2501m000) session. You can:
n Generate a project from a sales order with the Generate Project Structure for
a Sales Order (tdsls4244m000) session. For example, the sales order can be
a product variant from BaanERP Configurator.
n Copy a budget to a project or copy a project to a budget with the Copy
Projects (tipcs2210m000) session. (See also paragraph 2.2.1).
n Customize an item in the Activity Budget Material Lines (tpptc2510m000)
session.
n Customize an item in the Element Budget Material Lines (tpptc1510m000)
session.
Step 2 Calculation Office (tcmcs0565m000)
When you decide to create a project, you must assign a calculation office to the
project. A calculation office is a work center that determines the enterprise unit
for a project or production order. The calculation office has a purely
administrative function. You can assign a calculation office in two ways:
1 You define a calculation office, which you then link to the number
group/series combination used (tipcs0103m000) for the project. The
calculation office is entered by default when you enter a project.
2 You define a project after a calculation office is assigned to it.
Step 3 Price Calculation Codes (ticpr1500m000)
You can only define a project after you have assigned a price calculation code
to it. A price calculation code is a specification of how the cost price, valuation
price, or sales price of the project is calculated. The price calculation code for
customized items is stored by project.
Step 4 Projects (tipcs2501m000)
In this session you can manually enter a project or maintain data of existing
projects. A project is a collection of manufacturing and purchasing actions that
are performed especially for a particular customer order. A project is initiated
by a customer order for items that have a to-order policy. The purpose of a
project is to plan and coordinate the production of these items.
Common data for a project, such as customer name and project type, can be
entered in this session. Depending on the value of the Project Series parameter
in the Maintain PCS Parameters (tipcs0100m000) session, a series can be used
for the project code.

2-3
The Engineering Allowed field in the session is important. When this check box
is cleared, project engineering is not allowed. As a result, the check box value
changes when the project is maintained. Thus, project calculation and project
planning use the standard costing structures.
The Project Type field in the session is important. The field indicates the
project’s functionality and the method of operation. A project can be of the
following types:
Main project
A main project is a set of related subprojects. The network planning of
subprojects is controlled by the main project. This means that the main project
controls the start or end dates in subprojects. The total costs of the subprojects
are aggregated to the main project.
For a main project you can:
n Maintain project activities
n Define a network planning
n Enter a price calculation code
n Enter operation rates
n Enter subcontracting rates
n Enter surcharges
n Assign a service order
For a main project you cannot:
n Define a module planning for a project
n Engineer the project
n Link items to the main project
Subproject
A subproject is part of a main project, and makes it is possible to manufacture
customized products. The network planning of the main project determines the
planning method and the start and delivery dates of the subproject.
Single project
A single project is never part of a main project. The purpose of this project type
is to produce customized items. The logistical actions for these projects are
determined by the Project Planning business object, although it can use the
Network Planning business object.
Step 5 Maintain Project Structure (tipcs2115m000)
This session is only relevant if the project type is a main project or a subproject.
The project structure defines the relation between a main project and its
subprojects. If only one level of subprojects is allowed, they are all defined on
one level. The start date for a subproject is determined by the start date of the
main project's activity. In other words, the main project’s activity is entered as
the start activity of the subproject.

2-4
Step 6 Project Parts (tipcs2511m000) and Project Engineering

Project engineering is the process that you use to maintain the product structure
so that you can manufacture the products according to the customers wishes.
This means you either create routing and BOM structures or you adapt existing
routing and BOM structures.
The routing BOM structures are assigned to an item. The item is assigned to a
project part. In order to calculate the costs of the customized product,, the
project parts must be defined.
Step 7 Network Planning, Module Planning, Project Calculation
Before you can carry out the planning procedures, project engineering must be
carried out. After project engineering has been carried out, the material
requirements and resource requirements required to produce the item are
known.
Before you can carry out the project calculation, the production requirements of
an item must be known so that you can calculate the costs of material, and so
on. The calculation is performed for each project part, so the project parts must
also have been defined.
Step 8 Close Projects (tipcs2260m000)
You can use this session to close a project after the logistic and financial
processes have been completed. Final project results are calculated when
projects are closed. Only projects that have the status Finished or Canceled can
be closed.
If a network is present, the subprojects must be closed first. You can then close
the main project.
Step 9 Project Status (tipcs2502m000)
The project status determines which project functions can be carried out. During
the project, and depending on the stage that the project is in, the status changes.
The status of a subproject can only be changed based on the status of the main
project.
Note The status of the main project depends on the status of the subproject.

2-5
To work with project statuses

If the status is Free you can:
n Carry out project engineering
n Define the project master schedule (PMS) by using the Module Planning
business object
n Maintain the project structure
n Maintain the customized product structure by using customized bills of
material and routing sheets
n Carry out project estimation
If the status of the project is Simulation, you can:
n Simulate the rough capacity requirements planning
n Simulate the detailed material requirements planning
n Simulate the resource requirements planning (RRP) based on the network
planning
If the status of the project is Active, you can:
n Release planned orders, so that the required purchase and production
activities can be started and completed
If the status of the project is Cancelled, you cannot:
n Release new orders for the project
If the status of the project is Finished, you:
n Closed or completed all purchase and production activities
n Delivered all sales orders
If the status of the project is Closed, you:
n Computed the financial project results
n Cannot post financial project transactions to the project
If the status of the project is Archived, you:
n Stored all the project data in archive files. This means that the data is
removed from the original files
Step 10 Archive projects
This session is used to transfer the data to another set of tables, by storing it in
another BaanERP client company. Although archived data is partly removed
from the hard disk, individual project records within the primary table cannot be
removed.
This session moves the data from a closed project to an archive company
number. The project data is deleted from the original tables. One exception to
this is the data in the Maintain Projects (tipcs2501m000) session, which has
references with other parts of BaanERP.

2-6
2.2 The sessions that are related to the main procedure
2.2.1 Copy Project (tipcs2210m000)
If an existing project is the same as, or very similar to, the new required project,
the Copy Project session can be used to copy a project to another project. The
target project can be a new project or an existing project. If it is an existing
project, new data will be added without existing data being overwritten. The
data in the Project Engineering and Project Costing business objects will also be
copied. The data that is to be copied to a project can be maintained.
2.2.2 Delete Project (tipcs2270m000)
This session is used to remove a selected row of projects and the associated
project data. Only projects with the status Free can be removed.
2.2.3 Print Inventory Values of Projects to Close (tipcs2402m000)
In the Close Project (tipcs2402m000) session, current project inventory is

removed until a value is defined. This report will give information about the
project inventory of customized items and the value of the inventory. This
report can be printed before a project is closed.
2.2.4 Maintain Project Details (tipcs2530m000)
This session is not mandatory. In this session you can maintain additional
project details, such as the planning method.

2-7

2-8
3. The create a budget procedure
This is in contrast to projects, which are related to actual orders. The purpose of
a budget is to estimate project costs and revenues, without requirements being
generated.
Budgets can be copied to a single project or a subproject, or the other way
around. This includes the copying of:
n Bills of material
n Routings
n Costing structures
3.1 The create a budget procedure

The creation of a budget procedure ends when the budget is copied to a project
in the Copy Project (tipcs2210m000) session or when the budget is deleted in
the Delete Project (tipcs2270m000) session. For more information about further
steps in the procedure, for example how to maintain project data, see the how to
create a project procedure.
A budget:
n Cannot have a project structure
n Cannot use the network-planning procedure
n Cannot use the module-planning procedure
n Cannot generate material-requirements planning or capacity-requirements
planning
n Can have relations with the BaanERP Configurator package (you can make
a product variant for a budget)
n Does not have relations with the BaanERP Hours Accounting (HRA)
module
n Does not have relations with the BaanERP Sales (SLS) module
n Does not have relations with the BaanERP Purchase (PUR) module

3-1
The create a budget procedure
Calculation Groups Calculate Sales Prices

1 (tipcs0110m000) 7 (tipcs2241m000)
Generate Sales Quotations

Price Calculation Code
2 8 for Project
(tipcs1500m000)
(tipcs2240m000)
Projects Sales Quotations

3 (tipcs2501m000) 9 (tdsls1500m000)
Budget Details Quotation Lines

4 (tipcs2540m000) 10 (tdsls1501m000)
Project Parts Process Quotations

5 (tipcs2511m000) 11 (tdsls1200m000)
Quotation Results
6 Project Calculation 12 (tdsls1101s100)
Copy Project
13
(tdsls2210m000)
Figure 4, Procedure to create a budget

Step 1 Calculation Groups (tipcs0110m000)
You can only define a project after you have assigned a calculation office to it.
A calculation office is a work center that determines the enterprise unit for a
project or production order. The calculation office has a purely administrative
function.
Step 2 Price Calculation Codes (ticpr1500m000)
You can only define a project after you link a price-calculation code to a
project. A price-calculation code is a specification of how the cost price,
valuation price, or sales price of the project is calculated. The price-calculation
code for customized items is stored by project.
In this session the project is defined as a project of the type Budget. You must
set the Project Type field to Budget. The purpose of a budget is to estimate
project costs and revenues, without generating requirements.

3-2
Step 4 Maintain Budget Details (tipcs2540m000)

This session is optional. In this session you can determine the way the budget
calculation is performed.
Step 5 Project Parts (tipcs2511m000)
The Project Parts session is mainly used for calculation purposes. Costs for a
budget can only be calculated with project parts. Project parts are assigned to
the routing data and bill of material data, which supply data on which the cost
price is based.
Step 6 The project is calculated (tpcs3250m000)
The purpose of a budget is to calculate prices so that customers can be quoted
sales prices. For information on how the budget is calculated, see Chapter 5,
The project calculation procedure.
Step 7 Calculate Item Sales Prices by Budget (tipcs2241m000)
The sales price can be generated for the different budget parts, based on the cost
price of a budget. The sales price is calculated by adding budget costs and the
desired profit margin. The selling price is used in sales quotations.
You can change the generated selling price in the Generate Sales Quotations for
Budget (tipcs2240m000) session.
Calculation groups can be entered for the budget. As a result, different cost
structures and different item structures can be defined for the same budget.
Parallel simulations of cost and revenues can be compared and analyzed. For
budgeted items, estimated sales prices can be calculated in the CPR module.
Step 8 Generate Sales Quotations for a Project (tipcs2240m000)
You can use this session to generate a sales quotation, based only on a budget.
As a result, you can quickly submit a quotation to a customer. During the
process, a sales quotation line is generated for each budget part. The sales price
is based on the budget costs and includes a desired profit margin.
Step 9 Sales Quotations (tdsls1500m000)
You must use this session to gain access to the Quotation Result
(tdsls1101s000) session. The Quotation Results (tdsls1101s000) session is a
mandatory step in the procedure.
Select, in the Quotations (tdsls1500m000) session, the sales quotation you
generated in the Generate Sales Quotations for Project (tipcs2240m000)
session. By means of the Quotations (tdsls1500m000) session and the Quotation
lines (tdsls1501m000) session to access the Quotation Result (tdsls1101s000)
session. You must run the Quotation Results (tdsls1101s000) session in the
procedure.

3-3
In the Quotations (tipcs1500m000) session you can maintain information that is

in the quotation header. For example:
n Business partner data
n Terms of payment
n Terms of delivery
Quotations can be created manually or copied from an existing quotation.
Step 10 Quotations Lines (tdsls1501m000
You must use this session to gain access to the Quotation Result
(tdsls1101s000) session. The Quotation Result (tdsls1101s000) session is a
mandatory step in the procedure.
You selected in the Quotations Lines (tdsls1500m000) session the sales
quotation you generated in the Generate sales quotations for project session
(tipcs2240m000). When you select the quotation line in the Quotation Line
(tdsls1501m000) session you can zoom in the specific menu to the Quotation
Result (tdsls1101s000) session.
Step 11 Quotation Results (tdsls1101s100)
You can only start this session using the Quotation Order Lines (tdsls1101s000)
session.
You can record the business partner’s response to the quotation with the
Quotation Results (tdsls1101s100) session. The business partner can either
accept or reject the submitted quotation line. You can also record the reason for
success or failure, and the competitor that lost or obtained the order line. This
information can be important for future quotations.
You can assign the following statuses to the quotation:
n Free
A quotation line receives this status as soon it is entered in the quotation
line.
n Confirmed
If a business partner accepts the quotation line, the line is confirmed for
processing.
n Canceled
The status assigned to the quotation line, which is no longer valid, and can
be deleted.
n Processed
The status that is assigned to the quotation, when the quotation has been
transferred to a sales order.

3-4
If the business partner accepts the quotation, you can manually update the sales
quotation with the following information:
n Delivery date
n Confirmed status
n Reason for success
n Competitor code
Step 12 Copy Project (tipcs2210m000)
If a customer agrees with a budget, you can copy the budget to a project using
the Copy Project (tipcs2210m000) session. Budgets that customers do not
approve can be deleted using the Delete Project (tipcs2270m000) session.
When the budget is copied to the project all data assigned to the budget is
copied to the project. All check boxes in the Copy project (tipcs2210m000)
session are selected by default. You must select the Item Data check box.
The creation of a budget procedure ends when the budget is copied to a project.
If you need information about further steps in the procedure, for example how
to maintain project data, see the How to create a project procedure).
3.2.1 Create Sales Order (tdsls4500m000)
You can maintain sales orders that were created from a quotation using the
Sales Orders (tdsls4500m000) session. Afterwards, the other sessions of the
sales-order procedure are carried out.
3.2.2 Generate Sales Order Line (tdsls4501m000)
During the process, a sales-quotation line is generated for each budget part. The
sales price is calculated by adding budget costs and the desired profit margin.
3.2.3 Generate Project Structure for Sales Order (tdsls4244m000)
You can generate a product variant structure for an exisiting budget by using a
defined budget calculation code.
A product variant is generated for every generic item on a sales-order line.
A customized item is generated for every to order standard item.
You can also generate a budget with a budget calculation code defined to it.

3-5

3-6
4. The engineer a project procedure
The engineer a project procedure is described below. Project engineering is the

process in which the item data, routing data, and bill of material data is
maintained. This data is used to customize the project items to the customers
own wishes. Before you can engineer a project, the project must exist. The
method used to create a project is described in Chapter 2, The procedure to
create a project. You can also engineer projects that already exist.
4.1 The engineer a project proocedure

As was mentioned above, project engineering is the process in which you
maintain the product structure in order to manufacture the products according to
the customers wishes. This means that you either create routing and bill of
material structures or you adapt existing routing and bill of material structures.
A product structure is used to calculate costs and for planning purposes. The
structure consists of the operations that must be carried out and the materials
needed for the product. The data in the product structure is stored in the
following sessions:
n Item data (tcibd0501m000) session
n Routing data (tirou1501m000) session
n Bill of material data (tibom1510m000) session
Project engineering can be carried out before the project-calculation procedure
and the module-planning procedure are defined.

4-1
The engineer a project procedure
Figure 5 shows the steps in the engineering a project procedure.
Copy Project Maintain Sales Orders

1 (tipcs2210m000) 2 (tdsls4500m000)
Generate Project Structure

3 for Sales Orders
(tdsls4244m000)
Projects
4
(tipcs2501m000)
5 Project Parts
(tipcs2511m000)
General Item data

6 (tcibd0501m000)
Routing Operations
7 (tirou1501m000)
Bill of Material
8 (tibom1510m000)
Copy Standard Product

9 Structure to Customized
Structure (tipcs2230m000)
Copy Cust. Product

10 Structure to Cust. Product
Structure (tipcs2231m000)
Copy Customized Structure

11 to Standard Structure
(tipcs2232m000)
Figure 5, The product-engineering procedure

4-2

Step 1 Copy project (tipcs2210m000)
You can use the Copy Project (tipcs2210m000) session to copy a budget to a
project. You can choose which data is assigned to the budget or existing project,
and then copy that data to the new project. This results in a new project that has
the product structure of the budget or existing project assigned to it. You can
maintain the product structure by using project engineering.
Step 2 Maintain Sales Orders (tdsls4500m000)
The second way to create a project, and thus to start project engineering, is to
enter a sales order in the Maintain Sales Order (tdsls4500m000) session. You
can then zoom to the Sales Order Line (tdsls4501m000) session and enter the
items and the quantity of items the customer ordered. You can enter items with
the order policy to-order and anonymous.
You can also enter a sales order when there is a demand for a generic item. The
generic item is a product model that is used to create an item, based on the
options available in the Configurator package.
Generate Project Structure for Sales Orders (tdsls4244m000)
In the Generate Project Structure for Sales Orders (tdsls4244m000) session a
project structure is generated for the sales order (step 4). A project structure is
defined as follows:
n A project (subproject, budget, or single project) with a project structure.
This means the project is divided into main projects and subprojects
n A single project with a project structure assigned to it
In the Generate Project Structure for Sales Orders (tdsls4244m000) session, you
must specify how BaanERP must generate a project structure. The following
options are available:
n BaanERP generates for each sales order line a single project
n BaanERP generates one single project for all sales order lines
After you have run this session, BaanERP creates a new project and new items.
In the case of standard-to-order items, the BOM and ROU structures assigned to
the original items are copied to the items created by BaanERP. You can use the
project engineering procedure to alter the standard structures.
Step 3 Generate Product Variant for Project Item (tipcs2220m000)
In this session you create project data, not a project.
In the Projects (tipcs2501m000) session, the project that you created in the
previous steps or the project that is generated by BaanERP is displayed. You
can engineer the project by using steps 6 until 8 in this procedure.

4-3
Step 5 Project Parts (tipcs2511m000)

The Project Parts (tipcs2511m000) session is mainly used for maintaining
project parts that are used for calculation purposes. Costs for a project can only
be calculated for project parts. The second reason to use the Project Parts
(tipcs2511m000) session is that you can maintain the product structure with the
options on the Specific menu.
Step 6 General Item Data (tcibd0501m000)
Item data is entered in the General Item Data (tcibd0501m000) session. Items
can be entered manually or generated by means of steps 2 and 3.
Step 7 Bill of material (tibom1510m000)
The bill of material is maintained in the Bill of Material (tibom1510m000)
session. The bill of material is assigned to the item, and thus the project part,
and is used to define the product structure. The order in which steps 6 until 11
are carried out is entirely optional. However, an item first has to be defined
before you can put it in a bill of material. If there are any items in the bill of
material that can be linked to an operation, you must carry out step 6 before
step 7.
Step 8 Routing (tirou1502m000)
In the Routing (tirou1502m000) session you maintain the operations that must
be carried out to produce a product. The routing is used to define the product
structure. The order in which steps 6 until 11 are carried out is entirely optional.
However, an item first has to be defined before you can put it in a bill of
material. If there are any items in the bill of material that can be linked to an
operation, you must carry out step 6 before step 7.
Step 9 Copy Standard Product Structure to Project (tipcs2230m000)
You can use the Copy Standard Product Structure to Project (tipcs2230m000) to
copy a standard product structure to a project. A product structure is routing and
bill of material data linked to the item and is used to create a product.
This session can be used after or before the project and its parts are defined. The
order policy of the items is very important in the standard product structure.
Depending on the copying method used in the session and the order policy of
the items, items either remain as standard items or become customized items.
The order policy of an item is specified in the Item Ordering Data
(tcibd0501m000) session by means of the Order Policy field. This functionality
can be used if the required customized product structure is almost the same as a
standard product structure.
Step 10 Copy Customized Product Structure to Project (tipcs2231m000)
The Copy Customized Product Structure (tipcs2231m000) session can be used
if a customized product structure is (almost) the same as the existing structure
of another project. The product structure of one customized item is then used to
copy the data to the product structure of another customized item.

4-4
Step 11 Copy Customized Product Structure to Standard (tipcs2232m000)

The customized product structure can be used to create a standard product
structure. This is the case if the customized product structure is used on such a
scale that it would be wise not to define a new customized product structure for
every new request.
If stock is available on the project after all the products have been delivered to
the customer, the stock for the customized items can be transferred to standard
items. This can be accomplished by means of a warehouse order. By using the
project engineering business object, the item data of the desired standard
product can be generated without having to enter it manually.
4.2.1 Delete Customized Product Structure (tipcs2233m000)
If the customized product structure is deleted, the customized BOMs,

customized operations, and customized items, which include the cost price data,
are deleted consecutively. Before the customized items are deleted, BaanERP
checks whether these items are still active in other parts of the project. If they
are active, they are not deleted.
Customized product structures are active if:
n They are used in a production order which is not completed
n Inventory is available
n They are used as project parts

4-5

4-6
5. The project-calculation procedure
This chapter outlines how the cost price of a project and a budget are calculated.
The procedure outlines how to:
n Define project rates
n Define project surcharges
n Calculate estimated costs
n Calculate actual costs
5.1 The project-calculation procedure

Special project rates and surcharges are defined in this procedure. If no project
rates are entered, the standard rates of the BaanERP Cost Accounting (CPR)
module are used. For example, the rates of work centers, operations, machines,
and tasks.
The calculation of the estimated and actual costs is performed in this procedure.
Although the project rates can be defined at different stages in the project, they
are best calculated after the project structure has been defined.
Project Engineering
(Procedure)
Project Surcharges
1 (tipcs3520m000)
Calculate Cost Price by

2 Project (tipcs3250m000)
Cost Price by Customized

3 Item (tipcs3550m000)
Figure 6, The project-calculation procedure

5-1
The project-calculation procedure

Step 1 Project Surcharges (tipcs3520m000)
This session is optional. You can record surcharges for each estimated and
actual project calculation. Surcharges form the basis for extra costs or discounts
(in percentage or in amounts) in the project’s cost-price structure.
Step 2 Calculate Cost Price by Project (tipcs3250m000)
This session is mandatory. In this session the estimated costs or actual costs are
(re)calculated. The data for the estimated costs are defined by:
n Bill of material data
n Routing data
n Project Surcharges
The actual costing data is retrieved directly from the various BaanERP modules.
For instance, the Shop Floor Control module. In the SFC module, the issuing of
materials and posting of hours are used to accumulate actual project costs. All
of this information is aggregated to the project and the customized items when
the cost price calculation is performed for the project.
Step 3 Cost Price Calculation by Customized Item (tipcs3550m000)
This display session is optional. The cost calculation for standard items that are
used in a project differs from the cost calculation for customized items. The
standard item costs are calculated based upon the standard costs, while
customized item costs are calculated during the project cost price calculation.

5-2
6. The network-planning procedure
The network-planning procedure consists of all the activities required to carry

out a project. An activity can represent one or more operations. Each activity
has a specific lead time. The relations within the network indicate which
activities depend on each other. The primary function of the network-planning
procedure is to:
n Deliver a rough materials and capacity planning of the project. This is
needed to estimate project lead time and required capacity.
n Coordinate the activity dates of main projects and subprojects, with the
possibility of monitoring progress.
n Check the planning, based on network messages.
n Book non-order related time to a project.
n Be able to use the module-planning procedure.
n Plan the material requirements based on the activities, and link rough
capacity requirements to them. Based on the capacity utilization reports for
a work center, decisions can be made regarding the planning for that work
center.
The network-planning procedure is used after the project-data procedure and
after Project Engineering business object. Progress control is used during the
entire procedure.

6-1
The network-planning procedure
Figure 7 shows the steps in the procedure.
Capacity Load Table

1 Codes (tipcs4130m000)
Capacity Load Table

2 (tipcs4131m000)
Maintain Activities
3 (tipcs4501m000)
Maintain activities using

Maintain Activity
4 Relations (tipcs4110m000) 7 planning board
(tipcs4105m000)
Generate Network
5 Planning (tipcs4210m000)
Generate Network
6 Messages (tipcs4211m000)
Generate Module
8 Planning (tipcs4520m000)
Figure 7, The network-planning procedure

Step 1 Maintain Capacity Load Table Codes (tipcs4130m000)
This session is used to define a code that can be used to create an activity-load
table.
Step 2 Maintain Capacity Load Tables (tipcs4131m000)
In this session you can maintain a capacity-load table. Capacity-load tables
indicate how the rough capacity requirement is divided over the activity
duration. The capacity-load table is a graph. The percentage of the lead time
(activity duration) is on the horizontal axis. The vertical axis shows the
percentage of the capacity requirement (that part of the activity which must be
finished after a certain activity duration). This capacity requirement is the rough
capacity recorded for the activity.
By linking different percentages of the capacity to different percentages of the
lead time, the capacity load is described and can be linked to activities. This is
only required if the capacity load is required to be something other than linear.

6-2
Step 3 Maintain Activities (tipcs4501m000)

Activities are the steps that must be performed to complete a project. By
establishing links at a later stage between the various project activities, a
network can be created. The raw materials and capacity requirements of a
project are planned through activities.
Step 4 Maintain Activity Relations (tipcs4110m000)
The Maintain Activity Relations (tipcs4110m000) session is used to maintain
the sequence of activities if relationships between project activities must be
defined. This session is also used to determine the start times and end times of
an activity against the next activity. In addition to the relation between the
preceding activity and the following activity, the float time is indicated.
If a network-planning procedure is used to log nonorder costs, only one activity
will be entered. In this case, this step is optional.
Step 5 Generate Network Planning
The network-planning procedure sets the activities against time, and calculates
the earliest and latest start date and end dates for each activity. Depending on
the planning method of the project, calculation begins at a start date (planning
method: forward) or it starts at a delivery date (planning method: backward).
Network planning roughly calculates the capacity requirement, but only if the
project status is set to simulation or active.
Step 6 Generate Network Messages (tipcs4211m000)
This session is used to check the actual progress of activities per project. If the
actual progress deviates from the planning, network messages are generated.
This session must be used each time step 5 is carried out.
Step 7 Maintain Activities Using Planning Board (tipcs4105m000)
This session is used to maintain project activities that enable the generation of a
network-planning procedure. Activities are expressed on a chart planning graph.
Step 8 Generate Module Planning (tipcs4520m000)
This session is used to establish relations between the activities of the network-
planning procedure and project items. As a result, the network-planning
procedure must have been generated first. A module is a planning unit for a
customized, manufactured, or purchased part. If a module is defined, the
delivery date of items is always calculated from the activity network. A module
can be used to define items quantities that are different from the sales-order
quantity. Module planning can be used for the planning of critical materials
with long lead times or delivery times. It can also be used to control delivery
dates, when nonproduction activities take place after production.

6-3

6-4
7. The Link with Finance business object
The Link with Finance business object allows you to view, print, and delete the
WIP transactions that are posted to BaanERP Finance from PCS. A WIP
transaction is generated when:
n Materials are issued for a production order
n Hours are booked on a production order
n Finished products are delivered into inventory
n WIP transfers are carried out between work centers
n Surcharges are applied
n And so on
BaanERP Project automatically generates the transactions, and posts them to the
BaanERP General Ledger (GLD) module within BaanERP Finance. The
transactions are posted to specific ledger accounts and dimensions, based on a
mapping scheme for BaanERP Manufacturing, which is defined in the GLD
module in BaanERP Finance. Mapping schemes are based on:
n The transaction’s logistic transaction origin (TROR), for example, Project
(PCS)
n The classification of the financial transaction (FITR), for example, Project
Surcharge
BaanERP uses the combination of transaction origin and financial transaction to
select the ledger accounts to which the financial transactions are posted.
Figure 8 shows the sessions that you can use to display the link with BaanERP
Finance.
WIP Transactions by
Transaction Origin and
Financial Transaction
1 (tcfin1500m000)
WIP Transactions by
WIP Transactions by WIP Transactions by
Financial Period
2 Project (tcfin1500m001) 3 Order (tcfin1500m002) 4
(tcfin1500m003)
WIP Transactions
5 (tcfin1100s000)
Print WIP Transactions

6 (tcfin1400m000)
Delete WIP Transaction

by Project/Order
7
(tcfin1200m000)
Figure 8, The link with BaanERP Finance

7-1
The Link with Finance business object

Step 1 WIP Transactions by Transaction Origin and Financial Transaction
(tcfin1500m000)
This is the most important overview session. In this session, you can view all
the transactions related to projects and production orders that were posted to
Finance from PCS or other origins. The transactions are grouped by their
transaction origin and the classification of the financial transaction. For
example, you can view a list of all transactions that were posted to the GLD
module from project control, with regard to general hours.
Step 2 WIP Transactions by Project
In this overview session you can view all the transactions regarding projects to
Finance grouped by project code.
Step 3 WIP Transactions by Order (tcfin1500m002)
In this overview session you can view the transactions grouped by the order,
within the project to which they are related.
Step 4 WIP Transactions by Financial Period (tcfin1500m003)
In this overview session you can view the transactions that are grouped by the
financial year and period in which they were posted to the GLD module within
Finance. The transactions are sorted by their transaction date.
Step 5 WIP Transactions (tcfin1100s000)
If you double-click a transaction record in one of the sessions mentioned above,
the WIP Transactions details session is started. You can view detailed
transaction data about:
n The project
n The order
n The item
n The postings to GLD:
− The debit posting in the From box
− The credit posting in the To box)
n The financial period
Step 6 Print WIP Transactions (tcfin1400m000)
This session gives you extensive selection capabilities to print reports about
your WIP transactions. You can specify how the transactions in the report must
be sorted. You can define a selection of transactions to be printed based on any
of the transaction details displayed in the WIP Transactions details sesson. You
can print only the transactions that were already posted to GLD (processed), or
both processed and unprocessed transactions.

7-2
Step 7 Delete WIP Transactions by Project/Order (tcfin1200m000)

You can use this session to delete (old) WIP transactions from Finance.
Transactions can only be deleted when the project status is closed. The same
applies to production-order transactions.
You can define the range of transactions to delete in different ways:
n If you use the Horizon deleting method, you can define a range of financial
periods. The WIP transactions that were posted within the period range are
deleted.
n If you use the Order, Project deleting method, you can define a range of
projects and/or order numbers for which the WIP transactions must be
deleted.

7-3

7-4

Pcs UP055A US Baan

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Pcs UP055A US Baan

Enviado por

Direitos autorais:

Formatos disponíveis

BaanERP Manufacturing

Project Control System

Module Procedure UP055A US

© Copyright 1998 Baan Development B.V. All rights reserved

Project Control System

1. The Project Control System (PCS) module in BaanERP 1-1

Project Control System

About this document

To use this document

Project Control System

Acronyms used in this document

Optional Indicates an optional session

Mandatory Indicates a mandatory business object

Optional Indicates an optional business object

Indicates a module that is described in the module procedure

Project Control System

This chapter provides information on:

1.1 The concept as applied in BaanERP

Project Control System

1.2 BaanERP Project Control’s functional procedures

Figure 1, The main flow of PCS

Project Control System

The procedures of PCS are:

1.3 The modules that are related to PCS

IPD ROU SLS

Figure 2, The modules that are related to PCS

PCS is related to the following BaanERP Manufacturing modules:

Project Control System

n The Hours Accounting (HRA) module is used to retrieve the number of

Project Control System

1.4 The functionality of PCS’s business objects

Project Control System

Project Control System

This chapter describes:

2.1 The create a project procedure

Project Control System

Figure 3 shows the steps in the create a project procedure.

Figure 3, Creation of a project

Project Control System

The procedure consists of the following steps.

Project Control System

Project Control System

Step 6 Project Parts (tipcs2511m000) and Project Engineering

Project Control System

To work with project statuses

Project Control System

2.2 The sessions that are related to the main procedure

2.2.1 Copy Project (tipcs2210m000)

2.2.2 Delete Project (tipcs2270m000)

2.2.3 Print Inventory Values of Projects to Close (tipcs2402m000)

In the Close Project (tipcs2402m000) session, current project inventory is

2.2.4 Maintain Project Details (tipcs2530m000)

Project Control System

Project Control System

3.1 The create a budget procedure

Project Control System

Calculation Groups Calculate Sales Prices

Generate Sales Quotations

Projects Sales Quotations

Budget Details Quotation Lines

Project Parts Process Quotations

Figure 4, Procedure to create a budget

The procedure consists of the following steps.

Project Control System