Skip to content

Plant engineering#

General#

The "Plant Engineering" deliverable describes complementary deliverables to the standard Microsoft Dynamics Business Central™ project.

The following diagram depicts the process of plant construction from the quotation phase to the service and maintenance phase:

)

Resource master data#

Resources include employees or machines. Resource management allows you to plan capacity and deployment in detail and for an unlimited period of time.

Furthermore, resources can be grouped into resource groups. Purchase and sales prices can be recorded in detail and budgeted and invoiced for resources and resource groups.

Establishment#

To create a resource in KUMAVISION factory365, the following setups have to be done in advance:

Number series for resource#

Set up the number series for the resources so that when a new resource is created, the system automatically assigns a sequential identifiable number for the resource.

To do this, call up the "Number series" via the user search. You can create a new number series via "New" in the menu ribbon.

Afterwards, the created number series is stored in the "Resources setup" in the "Resource numbers" field.

Further information can be found in the Microsoft Dynamics Business Central™ Helpsite (F1).

Units#

Set up the "Units" table according to your individual requirements to be able to make the assignment when creating a resource (base unit code).

Call up the "Units" via the user search and create the units according to your requirements (for resources it is recommended to set up the unit "Hour").

Further information can be found in the Microsoft Dynamics Business Central™ Helpsite (F1).

Basic calendar#

The "Base calendar" can be used for several processes in KUMAVISION factory365. In connection with the resource, you can store a corresponding base calendar, with the help of which, for example, the different holidays in a (federal) country can be taken into account.

Example:
In Germany, January 6 (Epiphany) is viewed completely differently - while in Baden-Württemberg and Bavaria, for example, this is handled as a normal holiday, in North Rhine-Westphalia it is a normal working day. With the help of the stored calendar, resource availability can be calculated accordingly.

To create a base calendar, call up "Base calendar" via the user search. You can create a new base calendar via "New" in the menu ribbon.

The assignment of the possible different base calendars is done when the resource is created on the respective resource card.

Further information can be found in the Microsoft Dynamics Business Central™ Helpsite (F1).

Qualifications#

Qualifications can be stored in the resources according to your skills. To define the qualifications, first call them up via the user search.

Via "New" in the ribbon you can create a new qualification with the help of the table below.

Field Description
Code Assign a meaningful abbreviation for the qualification.
Description Assign a description for the qualification.

Further information can be found in the Microsoft Dynamics Business Central™ Helpsite (F1).

Working Time Template#

The working time templates allow you to store the different working time models of your employees in the system. Call up the "Working time templates" via the user search.

Via "New" in the menu ribbon, you can define a new working time template that can be assigned to a resource when it is created. Further information can be found in the Microsoft Dynamics Business Central™ Helpsite (F1).

Capacity units#

Resource management and capacity determination of production work with different unit tables. For linking the units, the resource unit is assigned to the capacity unit.

To do this, call up the capacity units via the user search. Via the menu item "Edit list" in the menu ribbon you can edit already existing capacity units and thus link the resource unit of the capacity unit in the field "Resource units".

Resources#

To create a new resource in the system, first call up the "Resources" via the user search. Via "New" in the menu ribbon you can create a new resource with the help of the table below.

Inforegister General#

Field Description
No. Specifies the number of the resource according to the specified number series. Alternatively, a manual assignment can be made.
Name Specifies the name of the resource.
Name 2 Specifies the name 2 of the resource.
Type Indicates what type of resource it is. Choice between "Person" or "Machine".
Base unit Specifies the base unit of the resource e.g. "hour", "piece".
Number of text modules Specifies the number of stored text modules.

The text modules are stored in the ribbon - Navigate - Text modules.

Further information on the topic of "Text modules" can be found in the section of the same name.
Search Keyword Specifies an alternative name / abbreviation that you can use to search for the record.

The system will automatically preset the field with the field content "Name", a manual change is possible.
Res. group no. Specifies the resource group assigned to the resource.
Locked If active, the resource cannot be used in the processes
Privacy lock Specifies whether to restrict access to data of the data subject in daily operation.
Locked (user) Field that activates the lock of the master record (as before). However, the field can now no longer be changed directly.
Care This indicates whether the record is currently in maintenance or not.
Status mandatory field check This field displays whether the mandatory field check was not performed (no check), completely checked, or incompletely checked.

The lookup on the field can be used to view the missing mandatory fields.
Locked from This shows whether the record is locked by the mandatory field check or by the user.
Corrected on Date of the last correction.
Plan resource Indicates whether the resource is a planned resource.
The field is set automatically when the planning resource is assigned with the resource group and cannot be edited by the user.

As soon as the "Plan Resource" switch is active, the calls "Resource Capacity" and "Set Resource Capacity" are not executable, because a "Plan Resource" must not have any capacities

Basic calendar code Specification of the base calendar

Note:
You can define non-working days in the base calendar. For more information, see section "Base calendar" or Microsoft Dynamics Business Central™ Helpsite (F1).
Specific calendar Indicates that the base calendar was used, for a custom calendar.
Working Time Template By assigning a working time template, the capacity quantity per weekly working day is determined when creating the resource capacity. If no working time template is assigned, this is skipped when the capacity creation function is executed.
Use timesheet If the switch is activated, the resource is available for bookings via the timesheets.
User ID of the time sheet owner Specifies the user ID of the timesheet owner.
User ID of the timesheet approver Specifies the user ID of the timesheet approver.
Workplace type Defines the type of linking of the resource. The link is taken into account in the resource utilization.

The following options are available:

Workstation group

when the resource is linked to a workstation group.



Workplace

when the resource is linked to a workstation group.



Resource

if the resource is not linked.
Job no. Defines the linked workstation (group) depending on the workstation type.
External resource Marks the resource as External so that it can also be used in the procurement process.
Vendor no. Specifies the vendor to which the external resource belongs.

The system automatically determines the company contact number by entering the vendor number.
Company Contact no. Indicates the company contact to which the resource belongs.
People contact no. Specifies the person contact number to which the external resource belongs.

Invoicing information register#

Field Description
EK price Specifies the purchase price of a unit of the resource.
Indirect costs % Indicates the percentage of the last purchase price of the resource from which indirect costs arise, such as freight/travel costs or similar associated with the purchase of the resource.
Cost price Indicates the cost of one unit of the resource.
VK Price / DB Calculation Indicates the relationship between the fields "Cost price", "Sales price" and "DB %".

The choices are:
• DB=VK-EP
• VK=EP+DB
• No reference
DB % Specifies the profit margin at which you want to sell the resource. You can enter a contribution margin manually or have it entered according to the "VK Price / DB Calculation" field.
UK price Indicates the price of one unit of the resource. You can enter the price manually or have it entered according to the "VK Price / DB Calculation" field.
Credit delivery valuation group code Specifies the item group code for the supplier rating.

Further information on the topic of supplier evaluation can be found in the section provided for this purpose.
Product posting group Specifies the product type of the resource to perform transactions for this resource with the corresponding G/L account.

VAT - Product booking group Specifies the VAT details of the involved resource to perform transactions according to the posting matrix.
Standard Accrual Template Specifies how revenues and expenses are accrued from periods.
Automatic. Text module Specifies that a text module is added to the documents for this resource.
IC partner Deposit G/L account no. Specifies the number of the IC G/L account in your partner's company to which the amounts of the respective resource are posted.
Product Commission Group Code Specifies the product commission group.

With the help of commission groups, resources can be grouped and commissioned separately.

This classification into commission groups is inherited in the sales process in the posted documents.

For further information, please refer to the "Commission management" section.

Inforegister Personal Data#

Field Description
Function Specifies the function of the resource.
Address / Address 2 Specifies the address of the resource.
Location Specifies the location of the address of the resource.
Zip code Specifies the postal code of the resource's address.
Country/Region Code Specifies the country/region of the resource's address.
Social security no. Specifies the social security number of the resource (person).
Training Indicates the education of the resource (person).
Convention Specifies the convention for the resource (person).
Date of employment Indicates the date when the resource was hired.

Qualification#

On the respective resource card, you have the option of assigning a qualification to the respective resource via "Qualifications" in the menu ribbon. If no qualifications have been set up in the table of the same name, they must be created beforehand.

Depending on the "Projects setup" in the "Check resource qualification" field, the system checks whether the necessary qualifications for an activity type are available when a resource is entered in the project plan lines.  

Set capacity#

The capacity of a resource is the amount of work that can be done within a defined period of time (one day). To calculate and define the capacities of the resource, call up the "Define capacity" function via the menu ribbon in the "Navigate" menu tab.

The "Calculate Res. Capacity" mask opens on which the filtering of the resource is already preset. By specifying the start/end date, the capacity items can be determined and defined.

Note

The capacity is calculated on the basis of the assigned base calendar and the assigned working time template on the respective resource card.
If no allocation of one/both fields has been made, no calculation of capacity can be made.

Note

If capacity items already exist for the calculated resource, the Calculate Res. Capacity application deletes them and creates new items.

Resource capacity#

By calling up "Resource capacity" via the user search, you have the option of viewing the capacity of the resources.

The "Set capacity" function is also available via the "Planning" menu selection on the "Resource capacity matrix" info tab.

The difference between the call on the resource map and the call in the resource capacity is that when calling from the resource map a pre-filtering is set on the resource. The call via the resource capacity is not, so that the capacity can be calculated over all available resources.

Plan resource#

General#

Especially in the initial stage of a project, usually no actual employee resources can be assigned behind positions, it is worked with a substitute, a so-called "planned resource".

A planned resource is equivalent to a normal resource, but has no capacities itself. A resource group is also defined for each department or team, which serves as a bracket for resources. All resources of a team are assigned to the resource group of the team.

(Plan) resource#

To create a planning resource in the system, first call up the "Resources" via the user search. A planning resource is usually created in the same way as a conventional resource. For further information on creating resources, please refer to the "Resources" section.  

Resource Group#

To actually make a resource a "planned resource", it is necessary to assign the resource to a resource group intended for this purpose.

Call up the resource groups via the user search.

Via "New" in the menu ribbon you can create a new resource group by entering an abbreviation and a description.

Then assign the resource that is to be used as a "planned resource" in the future to the resource group in the "Accumulation resource no. " field.

Note

Please note that only resources with the status "Maintenance completed" can be assigned.

By assigning the resource as an accumulation resource, the system automatically sets the "Planned resource" field on the resource card and it is not editable by the user.

Note

As soon as the switch "Plan resource" is active, the calls "Resource capacity" and "Set resource capacity" are not executable, because a "Plan resource" must not have any capacities.

Capacity#

A planned resource corresponds to a normal resource, but has no capacities. An overview of which capacities are available and their requirements is shown in the resource group availability.

Posting behavior of the planning resource#

No consumption postings may be made for a planning resource, posting via the billing document is possible. Especially for the case that the planning resource is to be settled instead of the executing resource.

Create timesheet#

Via the function "Create timesheet..." in the menu ribbon under the menu tab "Actions" you can create a timesheet for the respective resource.

To do this, enter the start date from which the timesheet is to be created. As well as the number of periods.

Using the timesheets, the resource can record and submit for your projects, the corresponding project tasks and the times for the corresponding period.

Further information on this topic can be found in the Microsoft Dynamics Business Central™ Helpsite (F1).

Project Management#

Projects in Microsoft Dynamics BC™ are dynamic business transactions that extend over a longer period of time. These can be planned, controlled and invoiced in detail with the help of activities and budgets.

You can track the use of working hours, machine running times and material for individual projects. This is managed via project tasks and their associated project plan lines, via which the expenses and revenues are managed.

A project consists of a three-tier structure:

Stage Description
Project Bracket with the essential key data
Project tasks Project tasks subdivide the project into different tasks, such as project management, incidental project costs, design and development, production, but also meetings, for example.
Project plan lines Project plan lines represent the means for task completion such as items, resources, or even item

The development of a project can thus be traced down to the smallest detail.

In addition, with the help of integrated invoicing in the Accounts Receivable & Sales and Accounts Payable & Purchasing modules, all related revenues and expenses are recorded.

The project structure and its processes are shown in a diagram below:

)

Project facility#

Establishment projects#

In the "Project setup" the necessary settings for the later project creation and implementation are made.

In the following the fields are explained to you on the basis of the table below:

Inforegister General#
Field Description
Automatic posting of project item prices Cost changes are automatically regulated as soon as the batch processing "Stock reg. fakt. Sett. Prices" is executed.
Apply consumption link by default Specify whether project items are linked to project planning lines by default.
Allow budget/billed line definition Specifies whether the type of project lines can be "Budget and Billable" by default.
WIP Standard Method Sets the default method to be used for calculating the circulating stock.
Default WIP booking method Defines how to apply the default working capital method when posting the working capital in the G/L item.
Default project booking group Sets the default booking group to be applied when creating a new project.
Logo position on documents Sets the position of the company logo on the business documents.
Inforegister numbering#
Field Description
Project numbers Specifies the number series to be used for assigning the numbers of a project.
Project WIP numbers Specifies the number series to be used for assigning the numbers of the project GDP documents.
Inforegister plant engineering#
Field Description
Project type Dimension If you define a dimension here, you can define in the project types which dimension value for the dimension should be assigned to a project by the system when assigning the project type.

By setting project type dimensions, you can create analyses about your projects according to the dimension value.
Check resource qualification When entering a resource in the project plan lines, the system checks whether the necessary qualifications for an activity type are available.

The following selections are available:

No
check is made when resources are used

Planning onlyWhen
maintaining project plan lines, the resource is checked against the necessary qualifications

Booking onlyIt is
checked for the sufficient qualification at the time of booking

Planning and BookingCombination of
Planning Only and Booking Only
Sale position no. from project plan lines If the check mark is set, the project task is transferred to the sales document as item no., otherwise the item is calculated individually for each order.
Use dimensions from project references If the checkmark is set, the dimensions defined in the referenced project plan line are used instead of the standard dimension line determination of the tables concerned.

The switch takes into account the following tables:

  • purchase Row
  • FA line
  • FA Components
  • Stock transfer
  • Assembly order
  • Assembly order items
Information register production#
Field Description
When the project status changes, automatically change the FA status to You can use this switch to specify whether any existing production order should also be changed from status to status when the status of the project is changed, and if so, to which FA status.
Inforegister Logistics#
Field Description
Create project storage location For the procurement and logistics processes, you use this to specify whether the system should create a project storage location for each project.

The project storage location hereby represents the place of performance of the project.
Stock entry entry storage location code For the procurement and logistics processes you define here a warehouse from which the warehouse setup for the financial accounting is to be copied.

The field "Stock entry one location code" can only be maintained if the storage location creation is activated ("Create project storage location").
Preferred transit code For the procurement and logistics processes, enter the transit code for the project warehouse transfer route here.

The "Preferred transit code" field can be maintained only if the storage location creation ("Create project storage location") is enabled.
Preferred delivery code For the procurement and logistics processes, enter the delivery agent code for the project warehouse transfer route here.

The field "Preferred delivery code" can only be maintained if the storage location creation ("Create project storage location") is activated.
Preferred carrier transport code For the procurement and logistics processes, enter the delivery agent transport type code for the project warehouse transfer route here.

The field "Preferred delivery transport code" can only be maintained if the storage location creation ("Create project storage location") is activated.
Inforegister Outlook ToDos#
Field Description
Step CRM task If you are working without a project outline, use this field to specify the increment for creating new project tasks.
Separator CRM task If you work without a project breakdown, use this field to specify the separator for creating new project tasks.
Counter CRM task If you work without project breakdown, set the counter for creating new project tasks in this field.
Inforegister Commitment#
Field Description
Smallest FA status for target cost consideration Define here from which FA status the target costs are to be displayed as planned costs.
Inforegister Version comparison#
Field Description
First archiving version no. In this field, specify the first archiving number of a version number assignment.
If only in left version,
If only in right version,
If version identical,
If versions different,
If subordinate line differs You can use these fields to specify the visual display in the version comparison. You can choose from:

None:
Display in black font color (serves as an identifier that no deliberate setup has been done yet)

Standard:
Display in black font color

StandardAccent:
Display in blue font color

Strong:
Display in black font color, bold

StrongAccent:
Display in blue font color, bold

Attention:
Display in red font color, italic

AttentionAccent:
Display in blue font color, italic

Favorable:
Display in green font color, bold

Unfavorable:
Displayed in red font color, italic, bold

Ambiguous:
Displayed in yellow font color

Subordinate:
Displayed in gray font color
Compare only set up fields With this switch you can globally define whether only set up fields should be compared or possibly individual comparison setups should be allowed via the "Version comparison field setup".

If the switch is activated, individual comparison setups can be made via the "Version comparison field setup" via the "Consider in field comparison" column.

If the switch is deactivated, the "Consider in field comparison" column is not editable.

Project accounts#

In the projects for plant construction, consumption and sales postings are displayed on a project chart of accounts, which is used for project controlling. The selection of the corresponding project accounts is controlled via the project account setup.

Project Chart of Accounts#

The project chart of accounts is used for project controlling and contains all sales and cost accounts that are to be used for a differentiated project view. The project chart of accounts is not dependent on the FIBU chart of accounts.

In the "Account type" field you can choose between five options:

Field Description
Account A bookable account can be selected.
Headline Text line in which a heading can be entered as a structure feature.
Total A sum defined by the "Total" field.
From-Sum An initial marker for a totaling project account series that ends with the To Total account type.
To-Sum An end marker for a totalizing project account series that starts with the From Total account type. The total is defined using the Totalization field.

After you have set up the project account, select "Actions" > "Indent Chart of Accounts" in the ribbon. Then select the "Yes" option in the message window.  

Project account setup#

The procedure is almost identical to setting up the posting matrix in the financial accounting area.

The project account setup determines the project accounts to which consumption and revenues are posted or budgeted in plant engineering. The project account setup is a matrix that defines the consumption and sales accounts for product posting groups. Here, the setup can be controlled by the project type and/or the activity type. Each project item is assigned either a consumption account or a sales account depending on its item type (consumption or sales). When determining the project account, the field contents of the project item are used.

Project Roles#

The project roles define in the later projects which role (e.g. project manager) the resource takes in the respective project.

To define the project roles in advance, call them up via the user search. Via "New" in the menu ribbon you can create a new project role with the help of the table below.

Field Description
Code Assign a meaningful abbreviation for the project role.
Description Assign a description for the project role.
Type Assign an applicable type. You can choose from the following:
• Responsible
• Project Manager
• Sale to contact no.
• Invoice to contact no.

Service type#

It is important for the later task planning in the projects to set up the activity types. To do this, call up the activity types via the user search.

Via "New" in the menu ribbon you can define a new service type with the help of the table below.

Field Description
Code Assign a meaningful abbreviation for the activity type.
Description Assign a description for the service type.
Type Specifies the type that the record is. You can choose from the following:

• Account
• Headline
• Total
• From-Sum
• To-Sum
Counting up Here you can now specify the interval or other filter specification of numbers of the service type.
The results of the specified service type are added to a total balance.

For the From sum or Heading type, this field must be left blank.

For the To-total type, the field is automatically filled when the chart of accounts is indented. Only the types that are between a From total and a To total are added together.
Qualifications Indicates the number of qualifications required for the service type.

Via a LookUp on the number, qualifications can be assigned to the activity type and already existing ones are displayed to you.

Further information on the subject of qualifications can be found in the section of the same name.
Usage NoneThere is
no task scheduling, the fields are not editable in the project task.

Task planningYou
can enter planning directly in the project tasks.

ForecastThere is
no task planning, the fields are not editable in the project task.

BothYou
can enter planning directly in the project tasks.
Type planning Via the type of planning you determine the type with which the task planning is to be entered in the planning line.

You can choose from the following:
- Resource
- Article
- G/L account
Planning no. Via the planning no. you determine, depending on the type of planning, with which account the task planning is to be displayed in the planning line.
Work type code Specifies the work type code for the activity type.
Art Forecast Specifies the type forecast for the service type.

You can choose from the following:
• Resource
• Article
• G/L account
Forecastnr. Specifies the forecast no. in the context of the "Type Forcast" field.
Forecast work type code Specifies the forecast work type code.
Cross country skiing articles Identifies a project task with the assigned activity type as a "long-run item".

Project types#

When creating a new project, you can define the type of project by assigning a "project type". Here you can already enter some data such as a project template, order type or similar.

To define the project types in advance, call up the project types via the user search. Via "New" in the menu ribbon you can define a new project type with the help of the table below.

Stage Description
Code Assign a meaningful abbreviation for the project type.
Description Enter a description for the project type.
Project booking group Enter the project booking group for the project type to be used when assigning the project type.

Please note that if the "Template project no." is maintained (see below), this information is ignored. (see below) this information will be ignored.
Project number series Specify the project number series for the project type to be used when creating a project and assigning the project type.
Template Project No. Specifies the project no. to submit the project for the project type.
Project type Dimension value Specifies the dimension value for the project type.
Dimension code Specifies the dimension code.
Dimension Value Prefix Specifies the dimension value prefix.
Task breakdown Specifies a task breakdown for the project type.

Please note that if the "Template project no." is maintained (see above), this information is ignored. (see above) this information will be ignored.
Reserve Specifies the reservation method for the project type.

The following are available for selection:
• Never
• Optional
• Always
Order type In the project type, you can set up an order type for the creation of sales documents, if required. This will be used when creating the documents.

Project breakdown#

The project structure helps you to enter and maintain your project tasks quickly and efficiently with predefined numbering.

Call up the "Project outline" via the user search.

Via "New" you can create a new project outline using the table and procedure below.

Field Description
Code Define a unique code for the record here.
Description Define a short description for the outline here.
Status Indicates the status of the outline.

The following are available for selection:
• New
• Certified
• In development
• Expired

Note
Please note that only project members with the status "Certified" can be used in the processes.

To define the outline for the created dataset, call up the "Outline structure" menu item via the ribbon.

Field Description
Level Level or indentation of the task.
Description Enter a description for the layer here
Increase Define with which intervals the system should assign tasks, 1 for one step, 10 for ten steps etc.
Based on the increment, the Counter field is initialized.
Counter Here you can define with which value the level should be started and how wide the level can be. For example, enter 001 if the layer can reach a maximum value of 999. Please note that the Project task field only has a maximum width of 20 characters.
Separator Define a separator here, e.g. period, comma, hyphen
Count type • Numeric
• Alphanumeric
please specify alphanumeric if your counter contains letters.
Bookable Specify whether it is possible to post on the level
Example Represents the current definition, as a project task.

Project Document Text Template#

For easy editing/creation of the document texts in the projects, you can define project text templates in which you specify how and when which data record is to be printed in which document.

To do this, call up the "Project document templates" via the user search.

Via "New" you can create a new project document template using the table below.

Field Description
Project table Use this field to specify for which table the definition is valid.

The following selection is available:
• Project Task
• Project planning line
Line type Use this field to specify for which line type the definition is valid.

The following selection is available:
• Plan
• Contract
• Plan and contract
Position In this field, specify how the definition is valid for which position.

The following selection is available:
• Pretext
• Post text
Service Contract Offer Printing In this field, specify whether the text should be printed on Service contract offer.
Service contract printing Use this field to specify whether the text should be printed on the service contract.
Service offer printing Use this field to specify whether the text should be printed on the service offer.
Service Order Printing Use this field to specify whether the text should be printed on the service order.
Service Geb. Invoice Printing Use this field to specify whether the text should be printed on the service invoice.
Service Geb. Credit Print Use this field to specify whether the text is to be printed on the service credit note.
Service Geb. Delivery Print In this field, specify whether the text is to be printed on the service delivery.
Service work ticket printing In this field, specify whether the text should be printed on service work ticket.
VK offer pressure In this field, specify whether the text should be printed on VK offer.
VK Order Printing Use this field to specify whether the text should be printed on VK Order.
VK Geb. Invoice Print Use this field to specify whether the text should be printed on VK Geb. Rechnung.
VK Geb. credit print Use this field to specify whether the text should be printed on VK Geb. Gutschrift.
VK Blanket order printing Use this field to specify whether the text should be printed on VK Blanket Order.

Project planning#

In the following, you will be introduced to project planning. It will be shown how a project can be structured and how plan values can be stored.

Project Assistant#

For a quick and easy creation of a project KUMAVISION factory365 offers a wizard for project creation.

For this, it is first necessary that the user has assigned the role center "Project Manager" in the user customization.

On the start page of the "Project Manager" role center, the "New Project" call is located in the activities area.

After clicking on the call, the wizard will be started.

Creation progress#

The "Creation progress" screen is used for the navigation/status overview of the project wizard.

This is divided into four sub-areas with their respective statuses:

  • Copy project
  • General project data
  • Sale to data
  • Invoice to data

Furthermore, the current processing step with the overall progress status is displayed.

In the lower area of the mask you have the following selection options:

Copy project#
Field Description
Project type Specifies the type of project it is.
Template Project No. Specifies the project no. to submit the new project.

If a project template is already stored in the project type, it will be preset automatically.
Transfer from project:
(Copy project awards,
Copy quantity,
Copy milestones,
Copy document texts)
From the "Template Project No.", if it is activated, the following data can be transferred from the template to the new project:

• Copy project prices
• Copy quantity
• Copy milestones
• Copy document texts
Copy risks Here the risks from the "Template project" can be taken over for the project to be created.

The following selection options are available:

• No
• Risks only
• With values
• with probabilities
Project task no. from Here the project tasks can be taken over from the "Template project" for the project to be created. Specification of the "Project task no. from" value.
Project task no. until Here the project tasks can be taken over from the "Template project" for the project to be created. Specification of the "Project task no. to" value.
Start date / End date Specifies the scheduled start/end date of the project.
Origin Set:

None:
Do not create plan lines when copying

Project plan lines:
Project plan lines to be copied from the template project using the project plan lines

Project items:
Generate project plan lines based on the project items from the template project.
Line type Depending on the project plan line origin, you can define which line type(s) you want to transfer:

Project plan lines:
- Budget + BillableAll
project plan lines
- BudgetOnly budget
marked project plan lines
- BillableOnly
billable marked project plan lines.

Project item:
- Consumption+SalesAll
project plan lines
- Consumption
Only consumption marked project items
- SaleOnly sale marked project items
General project data#
Field Description
Responsibility unit code With this field the project can be assigned to a unit of responsibility. Analogous to assigning a sales / purchase document to a unit of responsibility, projects can only be viewed by members of the same unit of responsibility.
Responsible Specifies the person who is responsible for the job.
Project Manager Specifies the person who is responsible for project management.
Project description / Project description 2 Specifies the project description
Start date / End date Specifies the start date / end date of the project.
New storage location code Specifies a new storage location code.
Sale to data#
Field Description
Sale to contact Specifies the contact at the customer who is responsible for the order.
Sales to debtor Specifies the customer no. to which the cost of the project is to be charged.

If you have previously maintained the "Sales to contact" field, this field will automatically default to the linked customer.

If you have gone through the project wizard and have filled in all the necessary fields with the corresponding data, you can create the project by clicking on "Create project".

The project map will be opened for you after creation in order to be able to enter further information. Alternatively, you can close the project map.  

Project map#

Inforegister General#

On the "General" info tab, the general data of the project are defined first. These are explained in more detail below:

Field Description
No. Specifies the number of the project of the correspondingly defined number series.
Description / Description 2 Specifies the description of the project.
Project type Indicates what type the project is.

If the following data has already been stored in the project type, it will be transferred to the project when the project type is assigned:

• Project booking group
• Project number series
• Template Project No.
• Project type Dimension code
• Dimension code
• Dimension Value Prefix
• Task breakdown
• Reserve
• Order type
Sell to deb. no. Indicates the number of the customer who usually bears the costs for the project.
Sell to deb. template code To create a project to a contact, the corresponding contact number is specified and the "Sales to deb. template code" field is filled with the appropriate template.
Sell to contact no. Indicates the contact of the customer, who usually bears the costs for the project.

In the Planning and Offer statuses, it is also possible to work with pure contact addresses. When the status changes to Open, a customer is created for the contact.

Note
Pleace note, that in case of using contacts, the field "Sales to deb. template code" or "Invoice to deb. template code" must be maintained. To deb. template code" field must be maintained.
Sell to name / name 2 / name 3 Specifies the name of the customer who usually bears the costs for the project.
Sell to address / address 2 Specifies the address of the customer to whom you usually send the invoice.
Rech. to deb. no. Indicates the number of the customer who usually bears the costs for the project.

By assigning the "Sales to customer no." field, the "Invoice to customer no." field is automatically preassigned with the "Sales. To customer no." field automatically.

If there is a different invoice recipient, the corresponding number must be changed manually.
Rech. to deb. template code Specifies the "Rech. an Deb. template code".
Rech. to contact no. Specifies the contact no. of the invoice recipient.
Rech. to Name / Name 2 / Name 3 Specifies the names of the invoice recipient.
Rech. to address / address Specifies the address of the invoice recipient.
Rech. to zip code Specifies the postal code of the invoice recipient.
Rech. on site Specifies the location of the invoice recipient.
Rech. to country/region code Specifies the country/region code of the invoice recipient.
Rech. to contact Specifies the name of the customer who usually bears the costs for the project.
Phone no. / Mobile phone no. Specifies the stored phone number of the customer.
E-mail Specifies the deposited e-mail address of the customer.
Search Keyword Specifies the search term of the project. This is automatically pre-populated with the description of the project and can be changed manually.
Responsibility unit code With this field the project can be assigned to a unit of responsibility. Analogous to assigning a sales / purchase document to a unit of responsibility, projects can only be viewed by members of the same unit of responsibility.
Responsible Specifies the person who is responsible for the job.
Locked Please transfer from the customer or other master data
Task breakdown Specifies the task breakdown to be used for the project.
Archived version Indicates the number of archived versions. A lookup makes it possible to view the versions.
Corrected on Indicates when the project data of the project map was last changed.
Project Manager Specifies the person who manages the project.
Inforegister Tasks#

On the "Tasks" info tab, the project tasks that are/will be planned in the project are first defined. This is the first "rough planning" for the project.

Task breakdown#

The task outline is used for the systematic and clear presentation of the project tasks and enables a uniform structure across the projects by means of predefined outline structures. The task outline is assigned to the project in the "Task outline" field in the project map. Using the following functions, you can insert the task outline into the project task lines.

Insert Outline Structure Function#

You can call up the "Insert Outline Structure" function on the respective project card via the ribbon. This function inserts a completely new outline structure at the end of the structure details.

Insert outline structure to postable" function#

You can call up the "Insert outline structure up to bookable" function on the respective project card via the ribbon. This function inserts an outline structure up to and including the first bookable outline structure.

Project tasks#

If you have previously inserted an outline structure in the project task rows, you have the option to insert a new row below an outline structure level via the [...] Assist button.

The system inserts a new line with the position numbering and description of the layers above.

Now enter the project tasks that occur / are planned in the project using the table below.

Field Description
Project task no. Specifies the number of the project task
Description Specifies the description of the project task
Project Task Type Specifies the type of project task.

The choices are:
• Account
• Headline
• Total
• From-Sum
• To-Sum
Service type In this field, assign the activity type for the project task in case of an account.

With the activity type you influence the project account determination and have the possibilities to influence the maintenance of the project plan lines.
Previous milestone Indicates a dependency on a previous milestone.
Milestone Specify here that the task is a milestone. A task can only be set as a milestone if type=total.

Due to the type=total, the values for a milestone can be easily tracked using the flowfields for costs and revenues. Based on the flowfields, the user can also dive into the plan lines or project items to analyze the milestone situation.
Milestone date Set here when the milestone is due.
Belongs to Milestone Specify here to which milestone the task belongs.
Status Indicates the status of the project task.

If a project task is finished, the corresponding plan lines are set to 100% during task progress.
Cross country skiing articles The checkmark "Long run item" identifies a project task as a task for long run items.

For more information on "cross-country skiing articles", see the section with the same name.
Task See a possible CRM task created from this here
Task status Status of the task, see for details there
Distribution type Define here which distribution type should be used to distribute the possibly created project plan lines between start and end time.
Maintenance is necessary if you carry out quick planning directly via the project tasks and the planning type is set to Resource.
Start date Specifies the start date for the project task.
If you have activated date maintenance at task level, you can change the planning date of the start line via the task.
The system creates a new project plan line with the type text and the default text code stored in the setup. The date is transferred to the Planning date field.
End date Specifies the end date for the project task.

If you have activated date maintenance at task level, you can change the planning date of the end line via the task.

The system creates a new project plan line with the type text and the default text code stored in the setup. The date is transferred to the Planning date field.
Working days The number of working days between the start and end dates, provided that the planning type is Resource and the resource capacity has been defined for the resource.
Budget (cost price) Specifies the budgeted cost price for the project task depending on the time period of the "planning date filter".
Actual cost amount Specifies the cost amount for the consumption of items, resources, and expense line items posted to the project task depending on the "Planning Date Filter" period.
Archived consumption Cost amount (MW) See consumption in an archived version for comparison.
Billable (sales amount) Specifies the billable sales amount for the project task depending on the period of the "planning date filter".
Invoiced (sales amount) Specifies the billable sales amount for the project task depending on the period of the "planning date filter".
Purchase commitments Amount (MW) See here the purchase order commitment (MW) (values of open purchase orders) for the project task.
Actual messages (MW) See here the value for the production orders/articles already created for the project task.
Capacity costs (MW) See here the value for the capacity costs (machine and personnel costs) already paid for the project task.
Consumption costs (MW) See here the value for the material consumptions already done for the project task.
Planned consumption costs production order (MW) Indicates the planned consumption costs (planned material requirements) based on a generated production order.
Planned capacity costs production order (MW) Indicates the planned capacity costs (planned machine usage) based on a generated production order.
Initial order Amount (MW) Represents the sales amount of the initial order.
Follow-up order(s) Amount (MW) Represents the sales amount of the follow-up order.
Variance(s) Amount (MW) Represents the amount generated via the forecast.
Actual progress % Indicates the actual progress of the project task in %.
Actual progress date Indicates the date of the actual progress of the project task.
Forecast (MW) If you set the forecast to "Project task", use this field to specify the total costs you currently expect for the project task.

For the calculation of the forecast (MW), the system determines it as follows:

(Consumption (cost price)
Time commitment Amount (MW)
Purchase commitments Amount (MW)
Stock commitment Amount (MW)
Production commitments Amount (MW))
Actual progress %
Forecast(MW)
Engage/disengage#

The function Project Tasks Move In and Move Out only works with defined task breakdown in the project map as well as project task type Account.

You can call up the "Engage/disengage" functions via the "Tasks" info tab using the "Line" menu selection.

Indent:
When the function "Indent" is called, the current line is indented one level down and bracketed by a from-sum and a to-sum line.

The description of the indented line is assigned to the from/to sum line. The new project task gets the description from the default. The already entered plan lines are also assigned to the new line.

Disengage
When the Move function is called, the current line is moved up one level. If it is not the last position of the task block, the next number of the upper range is used. If it is the last position, the task block is deleted and the task number is assigned to the from total.

Task numbering
Task determination is based on the outline structure and depends on the current position and project task type of the row.

If a line is inserted between existing positions, the system inserts a continuing line to the upper line.

If a line is inserted at the bottom, the next project task number is inserted based on the top line.

Document texts Project tasks#

You can describe a project task in detail using a long text. This long text is printed on the documents you define.

To define a document text for a task, first select the desired task line in the "Tasks" info tab.

Using the "Line" menu selection on the "Tasks" info tab, you then select the "Document text" menu item.

You can now decide whether you want to enter a pre-text or a post-text for the line.

The project document text map opens.

Call up the "Format Editor" via the menu ribbon and enter your desired text in the editor text field. After confirming the entry with "OK", your text will be displayed in the "Preview" field.

Using the fields below, you can define on which documents the text should be displayed.

Field Description
Project task printing Use this field when you add printing to project tasks reports
Project line print Use this field when you add printing to project plan lines reports
VK offer pressure Use this field to specify whether the text should be printed on VK offers.
VK Order Printing Use this field to specify whether the text should be printed on VK orders.
Proforma invoice printing Use this field to specify whether the text should be printed on proforma invoices.
VK Geb. Invoice Print Use this field to specify whether the text should be printed on VK Geb.
VK Geb. credit print Use this field to specify whether the text should be printed on VK Geb. credit notes.
VK Blanket order printing Use this field to specify whether the text should be printed on VK blanket orders.
VK Complaint print Use this field to specify whether the text should be printed on VK Complaints.
VK Geb. delivery pressure Use this field to specify whether the text should be printed on VK Geb. deliveries.
VK Geb. retraction pressure In this field, specify whether the text should be printed on VK Geb. Rücknahmen.
EK request pressure Use this field to specify whether the text should be printed on EK requests.
EK Order Printing Use this field to specify whether the text should be printed on EK orders.
EK Geb. Invoice Print Use this field to specify whether the text should be printed on EK Geb. invoices.
EK Geb. credit print Use this field to specify whether the text is to be printed on EK Geb. Gutschrift.
EK Frame order print Use this field to specify whether the text should be printed on EK Geb. blanket orders.
EK Complaint Printing In this field, specify whether the text should be printed on EK Reclamation.
EK Geb. Delivery Print In this field, specify whether the text should be printed on EK Geb. delivery.
EK Geb. return print Use this field to specify whether the text should be printed on EK Geb. returns.
Service Contract Offer Printing Use this field to specify whether the text should be printed on service contract offers.
Service contract printing Use this field to specify whether the text should be printed on service contracts.
Service offer printing Use this field to specify whether the text should be printed on service offers.
Service Order Printing Use this field to specify whether the text should be printed on service orders.
Service Geb. Invoice Printing In this field you can specify whether the text should be printed on service invoices.
Service Geb. Credit Print Use this field to specify whether the text is to be printed on the service bid credit notes.
Service Geb. Delivery Print In this field, specify whether the text is to be printed on Service Geb. deliveries.
Service work ticket printing Use this field to specify whether the text should be printed on the service work ticket.

The reports listed here print the project texts depending on the "Show additional text" switch:

  • Project plan lines
  • Project analysis
  • Budget comparison project
  • Account proposal project
  • Project offer  
Create tasks#

Via "Create tasks" you can create tasks or Outlook tasks such as a meeting invitation.

When you create a task, a project task is created for you in the background. The project task is created within the From task you selected.

You can create the tasks in the project area using the Tasks call in the Project Map, Project Tasks as well as from the Project Team.

Note

Please note that the creation of an Outlook task is only possible with the corresponding setup. Further information about the connection / setup can be found in the Microsoft Dynamics Business Central™ Helpsite (F1).

Note

The plan lines can only be changed via the CRM task (contact tasks).

In the "Project setup" you define how the project task no. is created via the fields "Step size CRM task", "Separator CRM task" as well as "Counter CRM task". Further information can be found here.

Alternatively, you can also create a task directly from a contact card by entering a project number.

Create activity#

Via "Create activity" you can create activities and/or communications such as telephone calls from Microsoft Dynamics Business Central™ and file associated documents. The time defined at this point is transferred to the timesheet.

You can call the "Create activity" function from the project map, project overview, project task, project plan line as well as from the project team map.

Assign the activity type as well as description of the activity. The seller code is determined based on your registration.

In the project fields, specify to which project task the document should be assigned and to which plan item the times should be recorded.

If you have selected the project plan position, the system will create an entry for you in the work time table (the prerequisite for this is the use of working times).

For further information on the topic of "Creating activities", please refer to the Microsoft Dynamics Business Central™ Helpsite (F1).

Milestones#

Milestones serve as intermediate goals within a project. Based on these goals, "smaller stages" can be logged as project progress within a project or dependencies to further milestones or tasks can be defined.

In KUMAVISION factory365 you have the possibility to assign milestones to the project tasks.

Establishment#

In the "Projects setup" you can globally control the behavior for all milestones via the "Milestone behavior" field. You can choose from the following options:

Field Description
Behavior milestone Define here how the system should behave when maintaining milestones in the area of date violations:

NoneThe
milestone is ignored
WarningThe
system alerts you to a violation
ErrorThe
system prohibits you from a time violation
Capture#

A milestone is entered on the respective project card on the "Task" info tab in the respective task line via the "Milestone" field. In the following, the relevant fields on the task line for the identification of a milestone are explained in more detail:

Field Description
Milestone In this field, specify that the task line is a milestone.

A task line can only be set as a milestone with type=sum.

Due to the type=total, the values for a milestone can be easily tracked using the flowfields for costs and revenues. Based on the flowfields, the user can also dive into the plan lines or project items to analyze the milestone situation.

When you mark a project task as a milestone, any maintained "Belongs to Milestone" field is cleared.
Field Description
Milestone date In this field you can set the due date of the milestone.
If you have not set the Milestone behavior to None in the project setup, the system checks:

• If the project task is marked as a milestone
• The project end date is not before the milestone date
• The project start date is not after the milestone date
• If the milestone has already been assigned project tasks, the milestone date also checks against existing project plan lines as well as project items of the assigned tasks.
The milestone date of the associated project task is also updated with the milestone date of the milestone in this process.

If a milestone date is not already maintained, this is initialized with the end date of the project.
When deactivating (unchecking) the "Milestone" field, the milestone date will be cleared.
Belongs to Milestone Specify here to which milestone the task belongs.
Maintaining the field updates the Milestone Summary field and the Milestone Date checks are run as described there.
Milestone behavior#
For maintenance start and end date#

The maintenance of start and end date in the project task is checked against a possibly assigned milestone. See also description for milestone date

For care status#

If the status of a milestone is set to completed, the system will ask you whether all associated project tasks should also be set to completed and will also execute this if confirmed.

Note

If you also use KUMAVISION Down Payment Accounting, it will also check here if a down payment plan by milestone is maintained and generate the down payment invoice assigned for it.

When care summation#

You can assign the milestone to the project tasks defined in the "Filter criterion" by maintaining the "Total" field.

The same checks or updates are performed as for the assignment via the Belongs to milestone field.

For maintenance project task type#

If the project task type is set to Account, the start and end dates will be processed, with all other settings any milestone information will be deleted.

Cross country skiing articles#

By means of the long run articles a long run planning and administration can be accomplished. Article items with a long procurement time are created as project plan lines in the project. Later, these articles can be used as components in project-related production orders. In this way, the requirements for these long-run items are triggered directly from the project, even without a production order already existing or the position of the component in the production order being known. If the production order is then created and the components are defined in the order, the requirements coverage of the component can be linked directly to the long-run item in the project.

Establishment#

The cross-country items are set up in the project via the project tasks. For this purpose, separate tasks should be created in the project for long-run items. The "Cross-country item" check mark identifies a project task as a task for a cross-country item.

Note

The checkmark "Long-run article" in a project task means that only project plan lines of the type "Article" and "Text" may be created for this project task. The lines with the type "Article" represent the long-run articles. The lines with the type "Text" can be used for groupings or notes.

If now for the project task, project plan lines are entered, the items with the type "Article" are automatically provided with the indicator "Long run article".

Note

Transferring project plan lines that are marked as "long-run items" to project book sheets or posting these lines is not allowed and is intercepted by corresponding error messages.

After the project plan lines have been created for the corresponding long-run items, procurement documents / procurement processes can be triggered for these project plan lines in order to achieve the corresponding coverage of requirements for these long-run items.

Note

The created procurement documents should be compellingly reserved for the project plan lines. On the one hand, the quantity in the procurement document is then considered reserved, and on the other hand, only reserved procurement quantities can be transferred from the project plan line "Long-run items" to the corresponding FA component. Only the quantity that is already covered by the procurement documents can be assigned to an FA component, regardless of the quantity of the project plan line itself.

Cross-country skiing articles as components in FA and E+D order#

If a long-run item has been defined in the project, it can also be viewed in project-related production orders. In this case, the "Long-run item" label is managed in the FA components in the "Long-run item" field itself.

In order for a component to be recognized as a long-run item in the production order and in the E+D order, the following criteria must be met:

  • Project number must be set as project reference in the FA component.
  • The article number, variant code and storage location code must match between the project plan line marked as a long-run item and the FA component.

In addition, the quantity that has already been linked / used for this FA component by a long-run item project plan line can be viewed in the "Long-run item linked quantity (base)" field.

The fields "Long-run item" and "Long-run item linked quantity (base)" can also be viewed accordingly in the lines of an E+D order.

Although it is possible to display directly for an FA component or E+D order line whether it is a long-run item, the available quantity of the long-run item cannot be displayed directly. This is due to the fact that it is calculated based on the reservations for the long-run project plan lines, taking into account the due date of the FA component and the planning date of the project plan lines. Further, there is the fact that a long-run article project plan line can serve several FA components, but there can also be several long-run article project plan lines for one article. Therefore, the available quantity of a long-run article is always calculated at runtime. This is done in the "Long-run article overview" screen. This overview can be called from the FA components and E+D order lines respectively.

To do this, call up the cross-country skiing article overview via the "Line" > "Line" > "Cross-country skiing article overview" info tab.

By means of the "Long-run item overview" mask, not only the quantity available for allocations can be viewed. This screen is also used to set or cancel links between FA components and long-run item project plan lines. In this way, the procurement quantity already reserved for the project plan line is transferred to the FA component or, in the case of cancellation, written back from the FA component to the project plan line.

Note

The "Long run item overview" screen can be called up not only for FA components or E+D order lines. It can also be displayed for the entire production order / E+D order. The overview can also be used from the project. Here it can be called up for project plan lines, project tasks and the entire project. The information and handling of the "Cross-country items overview" mask is described in the following sections.

Structure of the cross country skiing article overview#

The "Long-run item overview" screen shows the quantities available for links to the long-run item project plan lines for FA components. Furthermore, this mask offers the possibility to directly set links between FA components and long-run article project plan lines and thus to transfer the already reserved quantity from the project plan line to the FA component. It is also possible to delete these links.

The structure of the cross-country article overview, the individual calls and functions of the mask are described below.

Data areas of the cross country skiing article overview#
Origin address#

In the upper area of the long run article overview, the field "Called from" shows from where the long run article overview was called. E.g. from the FA component, the production order or the project.

Overview post#

The summary items are displayed in the rows area. The overview items are formed on the basis of FA components and project plan lines and are created as main items and sub-items. If the long-run item overview is called up from a production order or E+D order, the main items are created on the basis of FA components. The associated sub-items are created on the basis of the project plan lines, which are possible requirement coverers for these long-run items. If, on the other hand, the long-run article overview is called up from a project, the main items are created on the basis of project plan lines and the sub-items are created by the FA components as possible requirements originators.

Note text#

This area displays a short note text for the selected item. (If a note exists for this item).

Post details#

In the info boxes area, the details of the respective item are displayed. The item origin (FA line / project plan line), the item type (main item / sub-item), item and variant information as well as the due date and the storage location where the item is required are displayed. In addition, the quantity information is displayed here and whether the item is to be considered "Available". The quantity display in the overview items is explained below.  

Quantity display in the cross country article overview#

The aim of the long-run item overview is to show how FA components can be covered by the long-run item project plan lines already in the MRP. For this purpose, the quantities of the long-run items must also be displayed accordingly. The display of the quantities in the long-run item overview depends on whether they are main items or sub-items. In addition, there are separate fields for each reference (FA component, project plan line) that represent the quantities. Basically, for each main item, the sum of the sub-items is also calculated.

Example:

If the main item is an FA component, the sum of the quantities of its sub-items (project plan lines) that can be used to cover the requirements of the FA component is also formed for this main item. If the main item is a long-run project plan line, the FA components that could be covered by this project plan line are displayed as sub-items.

Basically, the quantity fields have the following meaning:

Quantity fields FA component

Field Description
Residual quantity (base) Displays the remaining quantity of the FA component line to the base unit. The remaining quantity represents the portion of the expected component quantity that has not yet been consumed.
Reserved quantity (base) The quantity in base unit that has already been reserved for the component line from procurement documents or warehouse stock is displayed here.
Linked quantity (base) This field displays the quantity in base unit that has already been linked to project plan lines for long-run items.
Open quantity (base) The "Open quantity" for the base unit is displayed here. The open quantity is the quantity that still has to be covered by reservations or links to long-run article project plan lines in order to ensure procurement for the remaining quantity of the FA component.
Open quantity = Remaining quantity - Reserved quantity

Quantity fields Project plan line

Field Description
Quantity (base) This field displays the quantity of the project plan line as a long-run item for the base unit. This field is purely informative and shows the planned quantity of the project plan line.
Linked quantity (base) This field displays the already linked quantity of the project plan line with FA components.
Available range (base) In this field the quantity of the project plan line available for links to the base unit is displayed. The available quantity is the reserved quantity of a project plan line, because only the quantities that are reserved on procurement documents or warehouse stock can be passed on to an FA component.

Note

For a main item (FA component or project plan line), sub-items can be displayed that have the "Unavailable item" checkmark set. These items cannot be covered or used to cover requirements.

An item is marked as "not available" if there is a date conflict between the FA component and the planning line. I.e. the FA component cannot be covered in time based on the planning date of the project plan line. Another reason would be if the quantity of the FA component is already completely covered (the remaining quantity is completely reserved) or if there is no available quantity in the project plan line. These items are then no longer used for requirements coverage, but they are still displayed to show the overview of the links that already exist between the project plan lines and FA components and to indicate date conflicts. These positions are marked accordingly and provided with a note text.

Actions of the cross country skiing article overview#

The mask "Long run article overview" has actions with which the view of the mask can be controlled, but also links between long run article project plan lines and FA components can be created or deleted again. The individual actions are described below:

Action Description
Recalculate By means of this action the data in the mask are recalculated and displayed. This action is used to update the mask.
Set shortcut This action sets links between the long-run article project plan lines and the corresponding FA components.
Delete link This action deletes the links between the long-run article project plan lines and the corresponding FA components again.
Show post By means of this action, the already existing links between the project plan line and FA component can be displayed for a position / item.
Setting and deleting long-run article links#

Setting and deleting links between long-run article project plan lines and the corresponding FA components is triggered from the long-run article overview. The actions "Set link" and "Delete link" are used for this purpose.

The setting and deletion of links is explained below on the basis of the call of the cross-country article overview for an FA component. The reason for this is that the setting and deletion of links always starts from the FA component, regardless of how the "Cross-country skiing article overview" screen was called up. Depending on the call, only the filtering of corresponding FA components takes place, which are then processed one after the other, in which the links are set or removed accordingly.

When setting a long-run article link for a FA component line, the system checks whether this component corresponds to a long-run article in project plan lines. For this purpose, the system checks whether the component has a project reference and whether these project plan lines marked as long-run articles have the same article / variant / storage location combination. If this is the case, the corresponding project plan lines are used as possible default lines. In this case, the planning date of the project plan lines is filtered so that they are before or the same as the due date of the component. The date filtering is important so that the requirement-covering documents for the project plan line can also be used for the FA component line. The link can now be set until the FA component "open quantity" is 0 (zero) or there is no more available quantity in the filtered long run item project plan lines.

The link is set with the "Set Link" function for the FA component line.

After the link has been set, a corresponding "long-run article link item" is also created. This item records which FA component was linked to which project plan line with which quantity. The fields "Linked quantity (base)" in the FA component and the project plan line are also calculated on the basis of these items.

The linking items can also be viewed in the cross-country article overview.

The link transfers the reservation (proportionate to the linked quantity) from the project plan line to the FA component. This also results in a direct link of the requirement-covering document (e.g. a purchase order) with the FA component.

However, the link also has a direct effect on the project plan line. In order to reduce the demand for the long-run article for the project accordingly and to minimize redundancy of the demand between the FA component and the project plan line, the quantity of the project plan line itself is also reduced.  

Delete shortcuts#

The deletion of link items has two integrated steps. Firstly, resetting the existing link according to the long-run item link. The other is the transfer of the reservation without the long-run item link.

In the first stage, using the long-run article link items, the link is undone by moving the reservation in the amount of the linked quantity from the FA component to the project plan line listed in the item.

In the second stage, the system checks whether there is still a reserved quantity for the FA component beyond the link. I.e. after deleting the link, there is still a "Reserved quantity" for the FA component, which may have been set by manual reservations. If this is the case, the reservation is also transferred to the first matching project plan line. The aim of this transfer is to always concentrate the existing requirement coverage for the long-run items of a project at the long-run item project plan lines. If the surplus reservation quantity were only cancelled in this way, it would then be available for other projects/consumption. However, the transfer ensures that the demand cover remains reserved for the project.

The link for the FA component is deleted again using the "Delete link" function.

By deleting the link, the long-run article link item is deleted and therefore the linked quantity in the FA component and the corresponding project plan line is also reduced / set to 0 (zero).

Furthermore, the "Open quantity (base)" is also set high again in the FA component, since there is no longer any requirement coverage for the remaining quantity of the FA component.

On the other hand, the quantity and the available quantity in the project plan line and the available quantity in the project plan line are set high. As a result, the reservation on the demand cover passes from the FA component to the project plan line and the demand cover is still available to the project.

Calls of the cross-country skiing articles overview from the production and project#

As described in previous sections, the long-run article overview can be called for FA components and project plan lines. However, it can also be called for FA lines, production orders as well as project tasks and the entire project.

This section describes the calls and explains the structure of the summary items per call.

Call for FA components / E+D order lines of the MRP type "warehouse part#

The "Long-run item overview" screen can be called up for FA components and E+D order lines of the MRP type "Stock item" using the action "Long-run item overview".

In both cases, the long-run article overview for the respective referenced FA component is called.

Here you can now view the possible, requirements-covering long-run article project plan lines for the component and create or delete a link between the FA component and the project plan line.

The individual actions for this can be taken from the previous section.  

Call for FA lines / E+D order lines of the MRP type "Production part#

The "Long-run item overview" screen can be called up for FA lines and E+D order lines of the MRP type "Production part" using the action "Long-run item overview".

In both cases, the long-run article overview is called for the referenced FA line.

The FA components of the respective FA line that have been identified as long-run items are displayed as the main items in this call.

As a sub-item, the project plan lines are shown for the respective FA components, which can serve as requirement cover if necessary.

If the actions "Set link" or "Delete link" are used for a FA line, the displayed FA components are run through one after the other and the selected functionality is performed for the individual FA component.

Call for a production order / E+D order#

The "Long-run item overview" screen can be called up for an entire production order or an E+D order.

In both cases, the long run article overview for the referenced production order is called. In the case of the E+D order, it is the production order that is listed in the header of the E+D order.

All FA components of the production order that have been identified as long-run items are displayed as main items in this call.

As a sub-item, the project plan lines are shown for the respective FA components, which can serve as requirement cover if necessary.

If the actions "Set link" or "Delete link" are used for the entire production order, the displayed FA components are run through one after the other and the selected functionality is performed for the individual FA component.

Call for a project plan line#

The "Long-run item overview" screen can also be called up for a project plan line. For this purpose, the respective project plan line must be marked as "Long-run item".

In the called cross-country article overview, the corresponding project plan line is displayed as the caller.

The corresponding project plan line is displayed as the main item in this overview. The FA components that could be covered by this project plan line are displayed as sub-items for this project plan line.

If the actions "Set link" or "Delete link" are executed from this view, they do not refer to the project plan line as the main item, but to the individual FA components as sub-items. I.e. the individual FA components are gone through one after the other and the selected action is executed there for each individual component. The assignment of the long-run item therefore always takes place from the view of the component.  

Call for a project task#

The "Long-run item overview" screen can also be called up for a project task. For this purpose, the respective project task must be marked as "Long-run item".

In the cross-country item overview, the corresponding project task is displayed as the caller.

As main items, the corresponding project plan lines for this task are displayed in this overview, which are marked as "long-run items". For each main item, the respective FA components that could be covered by this project plan line are then displayed as sub-items.

If the actions "Set link" or "Delete link" are executed from this view, they do not refer to the project plan lines as main items, but to the individual FA components as sub-items. I.e. the individual FA components are gone through one after the other and the selected action is executed there for each individual component. The assignment of the long-run item is therefore always done from the component's point of view.

Call for entire project#

The "Cross-country item overview" mask can also be called up for an entire project.

In the cross-country article overview, the corresponding project is displayed as the caller.

All project plan lines for this project that are marked as "long-run items" are displayed as main items in this overview. For each main item, the respective FA components that could be covered by this project plan line are then displayed as sub-items.

If the actions "Set link" or "Delete link" are executed from this view, they do not refer to the project plan lines as main items, but to the individual FA components as sub-items. I.e. the individual FA components are gone through one after the other and the selected action is executed there for each individual component. The assignment of the long-run item is therefore always done from the component's point of view.

Handling of long-run article links#

This section describes the handling of long-run article links for different actions in the processing of production orders / E+D orders and in the project.

Within the framework of production order / E+D order processing#
Separating and reintegrating separate production orders#

In E+D orders, individual subassemblies can be outsourced to separate production orders or reintegrated from a separate production order. In this case, the noted requirements coverage (reservations) is also outsourced or reintegrated. Therefore, the long-run article link items are also outsourced or reintegrated with the separate production order.

Deleting an FA component#

When an FA component is deleted, the system checks whether it is a long-run item. If this is the case and there are reservation items for the FA component, the reservation is transferred to the corresponding long-run item project plan line before the component is deleted.

For more information, see the section "Deleting cross-country article links".

Deleting a production order/ individual FA lines#

When deleting the entire production order or individual production order lines, the system checks for the entire production order or the corresponding production order line whether it contains components that are marked as long-run items. If this is the case, the reservations are transferred to the corresponding long-run article project plan lines before these components are deleted.

For more information, see the section "Deleting an FA component".

Reducing the quantity in an FA component#

If an FA component is marked as "long-running" and a quantity reservation exists for this component, then the existing reservation is converted to a long-running article project plan line before the quantity is reduced. After the reduction of the quantity, the system restores the reservation for the FA component according to the following scheme:

If the new "Expected quantity (base)" is smaller than the originally reserved quantity, then the reservation is only made according to the new "Expected quantity (base)". If, on the other hand, the new "Expected quantity (base)" still exceeds the originally reserved quantity, the reservation is set back to the originally reserved quantity.

This ensures that after the quantity reduction, the portion of the reservation that is no longer needed is assigned to a corresponding project long-runner and the component retains its reservation again up to the maximum previously reserved quantity.

Cancellation of the reservation from a FA component#

If an FA component is marked as a "long-run item", it is not possible to cancel the reservation for this component manually (call the reservation reversal directly from the FA component). This is due to the fact that reservations for long-run items in the production order are not simply cancelled and made available again for all consumptions, but are moved to the corresponding long-run item project plan lines. As a result, the reserved requirements coverers still remain linked to the project.

The cancellation of the reservation for a FA component that is marked as a long-run item is therefore aborted by an error message. Instead, the "Delete link" function in the "Long-run item overview" is to be used to transfer the existing reservation to a corresponding long-run item project plan line.

If the reservation was transferred to the project plan line, it can be cancelled there for the respective project plan line. This then represents a conscious decision, so that the reserved requirement cover for the long-run article is to be decoupled from the project.

Cancellation of the reservation from the demand deck#

If an FA component is marked as a "long-run item" and has a reservation for the requirement cover, the reservation cannot be cancelled directly from the FA component.

However, it is possible to cancel the reservation from the demand-covering document. This is due to the fact that changes to the requirement-covering document must be possible. E.g. if the planned delivery date cannot be met.

If a reservation is cancelled in a requirement-covering document that references an FA component for a long-run item, the long-run item link for this component is also adjusted accordingly.

Consumption posting of a FA component#

After posting the consumption for a FA component that is marked as a "long-run item", the long-run item link is adjusted to the reserved quantity again. This is due to the fact that the reserved quantity may be consumed with the consumption posting (reservation to stock). Therefore, the long-run article link must also be reduced accordingly.  

Status change in the production order#

When status changes are made in the production order, the long-run article links for this production order must also be taken into account accordingly. There are two options that must be taken into account:

Change from "Firmly Planned" to "Released":
With this status change, the long-run article link items must also be moved from the firmly planned production order to the released production order in parallel with the reservations.

Change from "Released" to "Finished":
If a production order is terminated, all remaining (unused) reservations for long-run items that are linked to the production order are distributed again to the corresponding long-run item project plan lines and are thus still available in the project.

In the context of editing project plan lines#

When editing project plan lines that are marked as "long-run items", the system must perform appropriate checks and actions with regard to long-run item links (long-run item link items). These are described below.

Creating book sheets for cross-country article project plan lines#

It is not possible to create project book sheets for project plan lines that are marked as "long-running items". This is prevented by a corresponding error message. The purpose of this is that project plan lines for long-run items must not be posted. A project plan line for long-run items offers the possibility to generate requirements in advance for parts that are needed during production and have a long procurement time. It serves the long-run article only as a trigger of the procurement, the actual consumption takes place as a component in the production order.

Booking cross country article project plan lines#

Posting project plan lines that are marked as "long-run items" is not permitted. A project plan line for long-run items offers the possibility to generate requirements in advance for parts that are needed during production and have a long procurement time. It therefore only serves as a trigger for procurement, the actual consumption of the component takes place in the production order.

Deleting long-run article project plan lines with link items#

If a project plan line that is marked as a "long-run article" is deleted, the long-run article links of this project plan line to the corresponding FA components are also deleted. However, the reservation that has already been transferred to the requirements planner remains in the FA components. If it was the only long-run article project plan line for the article / variant / storage location combination, then the "Long-run article" check mark is also removed from the corresponding FA components, since there is no longer a reference to a long-run article in the project.  

Project plan lines#

In the project plan lines you can define the "detailed planning" for the project. Per project task line you have the possibility to define which items, resources and expense financial accounting items should be used.

To do this, first select the desired project task line and then call up the project plan lines via the "Tasks" info tab.

Define the project plan line using the table below.

Field Description
Project task no. Specifies the number of the associated project task.
Automatically preset by the system.
Line type Specifies the type of planning line.

The following are available for selection:

• Budget
• Billable
• Budget and billable
Order type Initial orderWhen the first sales order is created, the order type is set to initial order

Follow-up orderWhen
creating a follow-up order, the order type is set to Follow-up order

DeviationWhen
maintaining the forecast, the project plan lines created during the forecast release (archiving) are marked as a deviation.

Plan lineInitial
value when creating a new plan line
Planning date The planning date of the plan line is initialized depending on the set working date with the working date (working date <> today) or with the set start date of the project. If the start date is not set on the project card, the working date is always assigned.
Planned delivery date Specifies the scheduled delivery date of the item associated with the project planning row. For a resource, the scheduled delivery date is the date when the resource will be used for the project.
Desired delivery date Specifies the date when the customer wants the order to be delivered.
Promised delivery date Specifies the date on which you committed the delivery of the order based on the result of the Delivery Date Commitment function.
Goods issue date Specifies the goods issue date.
Planned goods issue date Specifies the date when the goods should be delivered from the warehouse. If the customer requests a specific delivery date, the application calculates the scheduled delivery date by subtracting the transportation time from the requested delivery date. If the customer does not want a delivery date or the requested delivery date cannot be met, the application calculates the contents of this field by adding the transportation time to the delivery date.
Start date If you work with the "Distribute planned quantity" function, the specified day from which the times were distributed is displayed in this field.
End date If you work with the "Distribute planned quantity" function, the specified day up to which the times are distributed is displayed in this field.
Belongs to Milestone If the associated project task is assigned to a milestone, this is displayed in the field.
Document no. If the project plan line is created by the system, the document no. of the originating document is specified here. The field can also be maintained manually if required.
Type Specifies the type of planning line.

The following are available for selection:
• Resource
• Article
• G/L account
• Text

As soon as you create a new project planning line with type=article as well as storage location, so a new stockkeeping data card for the entered article no. and the storage location code of the project is created by the system.

During the initial creation, the data is transferred from the article card to the inventory data.
No. Indicates the number of the item, resource or G/L account.

Note
In the "Nr" field, the Assist button is available to you for article/resource search in a simplified way.

Type=Article:
The characteristics for the search can be defined in the characteristic search. In the column Number of result the number of articles with the defined characteristic are displayed.

Type=Resource:
Resource search based on qualifications. If qualifications have been stored in the specified activity type, these are checked against the qualifications of the resources. If these match, the check mark is set in the "Qualified" field.
Description Specifies the description of the item, resource or G/L account.
Cross country skiing articles If the associated project task is marked with Long run item=Yes, the marker is automatically set on the project plan line.
Long-run article Linked quantity (base) This field displays the already linked quantity of the project plan line with FA components.
Belongs to Milestone If the associated project task is assigned to a milestone, this is displayed in the field.
Article version code If you work with article versions, then you specify here the article version for the procurement.
Storage bin code Indicates the storage bin where the items are picked/put away.
Quantity Specifies the quantity of units of the resource, item or G/L account.
Distribution type Specifies the distribution type for the "Distribute planned quantity" function.

The following selection options are available:
• Empty
• Forward
• Backward
• Manual
Belongs to line no. If you work with the function "Distribute plan quantity", the field "Belongs to row no." indicates to which base row the "distributed" row belongs.
Distributed quantity If you work with the function "Distribute planned quantity", the field "Distributed quantity" shows how much of the quantity has been distributed.
Distributed quantity (Original) If you work with the "Distribute planned quantity" function, the field represents the originally defined quantity.
Distributed purchase price (MW) See here the cumulative cost amount of the distributed lines.
Reserved from Specifies the reservation of.
Vendor no. For a quick procurement of your project requirements, the possibility was created to transfer positions directly from the project plan lines into the planning proposal, inquiry, order, invoice as well as credit note.

In this field, specify the vendor from which you want to procure this item.
Purchasing document type If you have transferred the plan line, you will see the document type of the purchasing document here.
Purchase document no. If you have transferred the plan line, you will see the no. of the purchasing document here.
Cost price Maintain here in project currency the cost price of the position.
Calculation tracking lines available If a check mark is set here, an article calculation has already been created for the position.
Cost amount Indicates the cost amount of the position in project currency.
UK price Maintain here in project currency the sales price of the position.
Line amount Specifies in project currency the line (sales) amount of the item.
Quantity to be transferred in book. sheet Specifies the quantity to be transferred to the project book. sheet.
Invoiced amount (MW) See here the already invoiced amount in client currency of the positions.
Actual progress % Indicates the actual progress of the project plan line in %.
Actual progress date Represents the maintenance date of the Actual Progress.
Forecast (MW) If you set the forecast to "Project plan line", use this field to specify the total costs you currently expect for the project task.

For the calculation of the forecast (MW), the system determines it as follows:


(Consumption (cost price)
Time commitment Amount (MW)
Purchase commitments Amount (MW)
Stock commitment Amount (MW)
Production commitments Amount (MW))
Actual progress %
Forecast (MW)
Service type This field shows you the transferred activity type from the project task.
Sales account no. You will see the sales account determined by the system in this field.
Consumption account no. You will see the consumption account determined by the system in this field.
Procurement method If you set the procurement method to stock transfer, the system creates a stock transfer route from the standard storage location to the storage location of the project planning line if it is different.
If a stock data card already exists, it will be updated based on the default.
With the procurement method simulation a calculation FA is created in the background.

If you want to trigger a purchase order for the item, set the procurement method to purchase, this will update the inventory data for the item and storage location.
Sales document Document type Specifies the document type of the sales document.
Sales document no. Specifies the sales document no. of the sales document.
Document texts project plan lines#

You can describe a project plan line in detail using a long text. This long text is printed on the documents you define.

Call up the project plan lines via the desired project task using the call of the same name on the "Tasks" info tab.

Select the project plan line for which you want to enter a document text. Then call up the "Document texts" menu selection via the ribbon. You can now decide whether you want to enter a pre- or post-text for the line.

The entry of the pre- or post-texts is done in the same way as for the tasks. Further information can be found in the section "Document texts for tasks".

The reports listed here print the project texts depending on the "Show additional text" switch:

Project plan lines Project analysis Budget comparison project Account proposal project *Project offer

Distribute plan quantity#

It often happens that tasks take longer than one working day, for a more accurate resource planning it is now necessary to distribute the estimated hours over the working days.

Note

Before splitting, in the case of the Budget and Billable line types, it is necessary to clarify how billing is to be performed:
-Flat rate billing

The line must be divided into a billing and budget line beforehand on the project task via Functions\Split plan line. Billing is then done via the original plan line.

-Resource statement

The line type remains unchanged and is then settled via the line item.

The prerequisite for the distribution is that the line type is Budget.

To distribute the planned quantity, call up the "Distribute planned quantity" function via the menu ribbon.   The Distribute Planned Set screen opens where you can specify the following distribution criteria:

Field Description
Project no. Specifies the project no. of the project. The project no. is automatically preset by the system.
Task no. Specifies the task no. to be distributed. The task no. is automatically preset by the system.
Description Specifies the description of the task no. to be distributed. The description is automatically preset by the system.
Type planning Specifies the planning type of the distribution. You can choose from the following options:

EmptyNo distribution is made.

ForwardStarting from the
start date, the system compares the available resource capacity and creates a new project plan line for
the capacity quantity until the quantity of the line to be distributed is distributed.

Backward
Starting with the end date, the system compares the available resource capacity and creates a new project plan line for the capacity quantity until the quantity of the line to be distributed is distributed.

Manual
Enter the quantity and date manually here.
Consider resource group assignment If you activate the switch, only resource assigned to the resource to be distributed will be offered.
Start date Define here from which day the times are to be distributed.
End date Define here up to which day the times are to be distributed.
Resource selection Specify here how it wants to distribute:

NoneThe
system starts from the first resource and tries to distribute the quantity in the period until the quantity is distributed.

ResourceThe
system considers the resource filter and distributes as for resource.

QualificationThe
system checks against the qualifications assigned to the activity type of the project task/project plan lines and searches for those resources with matching qualifications and distributes the quantity as under none.
Resource filter Set a filter here to specify under resource selection defined decision.
Quantity New line Set the quantity for the distribution here in case of manual distribution.

Confirm your entry with "OK" to distribute the planned quantities.

The daily residual amount is calculated as follows:

Resource capacity * Quantity in order (Proj.) * Quantity in assembly order * Quantity in service order * FA time requirement Remaining quantity available for the day

If the line to be distributed is a budget and billable line, the line will be split into a budget and billable line in the course of quantity distribution. The billing line item is inserted before the original line item.

FA Calculation#

The calculation in KUMAVISION factory365 has been extended so that also project plan lines can be calculated. New cost prices can be calculated and taken over, however, deviating from the calculation for sales, no sales prices.

Establishment#

Call up the "Evaluation & costing setup" via the user search. Via the info tab "General" you have the possibility to set up the costing on project plan lines in the field "Cost E+D order (project)".

The following selection options are available to you:

Selection option Description
Calculate only A simulated FA is created and a calculation is generated.
Calculate+Advertise A Simulated FA and a calculation are created and the created FA is then opened via page 5232961 "Simulated E+D order (calculation)".
Calculate+Take Over A Simulated FA and cost estimate are created and the cost price is transferred to the project plan line.
Preparation of a calculation#

A prerequisite for creating a cost estimate is that a project plan line has the type "Article" and the procurement method "Simulated".   To create the cost estimate, call up the function "Calculate production cost estimate" for the desired project plan line via the menu ribbon > "Actions" > "Functions" > "Costing".

Note

Please note that the project must not be in "Order" or "Finished" status.

Already when selecting the procurement method "Simulated", the calculation is performed automatically.

In addition, a cost estimate can also be created subsequently using the "Calculate production cost estimate" function.

Through the costing, a simulated FA is set up and a costing is performed depending on the setup, the FA is then also displayed or the costing result is taken over as the cost price for the project plan line.

The calculation can be checked via the "Calculation tracking lines" action.

Transfer of the calculation into a sales quotation#

If a project plan line is transferred to a quotation, a cost estimate existing for the project plan line is automatically linked to this quotation line as well.

From the quotation, you can view the reference to the simulated FA of the project plan line. To do this, select the "Functions" menu item via the "Line" info tab and execute the "Costing tracking lines" function.

Post calculation#

If the cost estimate has to be changed subsequently or a new costing run has been carried out, the newly calculated cost price can be adopted again in the costing proposals using the "Adopt costing proposal (preferred)" function. The price is also adopted in any existing sales document.

Addition in simulated production order#

Simulated production orders additionally have the identifier "FA used in calculation" on the info tab "General". This indicates whether the respective production order is used in one or more calculations.

A lookup on the identifier will display the "Calculation Tracking Lines (Sales + Project)" overview.

If a calculation is linked in project and sales in parallel, only the information for the project plan line is displayed in the "Calculation tracking lines (sales + project)" overview, as this is the leading document.  

Information register booking#
Field Description
Status Indicates the current status for the project.
Project booking group Specifies the booking group set up for the project according to the booking matrix setup.
WIP method Specifies the method used to calculate the working capital value for the project.
Allow budget/billable lines Here you can control whether you want to allow project plan lines of the type "Budget" or "Billable".
Apply consumption link Indicates whether consumption items, e.g. from the project posting sheet or purchasing line, are linked to project planning line.
% completed Indicates the percentage of the project's expected resource consumption that has been posted as used.
% Invoiced Specifies the percentage of the project's invoice value that has been posted as invoiced.
% of overdue plan lines Indicates the percentage of the project's planning lines for which the planned delivery date has expired.
Status#

The course of a project is largely determined by the status. The individual options are described in detail below:

Planning:
In this project phase you can perform preliminary calculations. In addition, the project structure can be defined, i.e. you can define project tasks as well as associated project plan lines. No bookings can be made yet.

Offer:
The project is offered to a customer. Preliminary calculations are also possible at this stage. You can also change the structure and budget of the project. Postings cannot be made.

Open (=order):
Expenses from purchasing as well as from time recording are now recordable and postable. With the posting of sales invoices and credit notes, project revenues can be posted to the project. Postings are only possible in this phase.

Completed:
You can no longer change the project structure and budgets. This status is used to perform recalculations The real costs of a project can be compared with the budgeted amounts. Completed projects can no longer be posted.

Inforegister dates#
Field Description
Start date Specifies the date when the project starts.
End date Specifies the date when the project should be completed.
Establishment date Specifies the date when the project was created.
Foreign Trade Information Register#
Field Description
Currency code Specifies the currency code for the project. By default, the field is empty. If you enter a foreign currency code, the project will be planned and invoiced in this currency.
Invoice currency code Specifies the currency code to be applied when creating invoices for the project. By default, the currency code is based on the currency code that has been stored on the customer card.
Exchange rate calculation (cost price) Specifies how project costs are calculated when you change the Currency Date or Currency Code fields in a project plan row.

The choices are:

MW fixed
The project costs in the local currency are fixed. A change in the currency exchange rate changes the value of project costs in a foreign currency.

FW fixed
The project costs in the foreign currency are fixed. A change in the exchange rate changes the value of the project costs in the local currency.
Exchange rate calculation (sales price) pecifies how project sales prices are calculated when you change the Currency Date or Currency Code fields of a project plan row.

The choices are:
MW fixed

The project prices in the local currency are fixed. A change in the currency exchange rate changes the value of the project prices in a foreign currency.

FW fixed
The project prices in the foreign currency are fixed. A change in the exchange rate changes the value of the project prices in the local currency.
Inforegister WIP and revenue recognition#
Field Description
WIP posting date Indicates the posting date that was entered during the last execution of "Calculate WIP project".
Total WIP invoice value Indicates the total WIP sales amount that was last calculated for the project.
WIP maintenance amount (total) Indicates the total WIP maintenance amount that was last calculated for the project.
Deactivated sales amount Indicates the amount of declared sales that was last calculated for the project.
Deactivated cost amount Indicates the declared cost amount that was last calculated for the project.
Disabled DB Specifies the disabled DB for the project.
Disabled DB % Indicates the deactivated contribution margin in percent for the project.
Posting date WIP to G/L item Indicates the posting date entered during the last execution of "Post WIP to G/L Project".
Total WIP invoice value in G/L accounts Indicates the total WIP sales amount that was last posted for the project.
WIP balance for G/L accounts (total) Indicates the total WIP balance that was last posted to the project.
Deactivated sales amount in G/L accounts Indicates the total declared sales amount that was last posted for the project.
Deactivated cost amount on G/L accounts Indicates the total deactivated cost amount that was last posted for the project.
Deactivated DB on G/L accounts Indicates the contribution margin that will be realized for this project.
Deactivated DB (financial accounting) %. Indicates the contribution margin in percent that will be realized for this project.
Inforegister Forecast & Commitment#

On this Inforegister the Forecast & Obligo information of the project is presented. At this point, the Inforegister is mentioned for the sake of completeness.

For further information, please refer to the section "Forecast & Commitments".

Project storage location#

For the correct representation of the transfer of risk, goods are transferred from their production site to the construction site or to the customer and not directly delivered and thus consumed. The project is then debited upon acceptance by means of a deliberate consumption posting.

For this purpose, a project storage location is always created for a project.

After defining the "Sale to customer no. ", a new storage location can be created based on the customer details.

The system offer the user to create a storage location based on the customer card as well as possible delivery addresses.

The respective storage location can be called up via the project map by calling up "Storage location" in the menu ribbon.

Note

If there is only one "project warehouse", it will be updated when the project is changed.

If there are several "project warehouses", they must be updated manually.

Establishment#

For the project storage location, the following setups must be made in advance in the "Projects setup":

Field Description
Create project storage location For the procurement and logistics processes, you use this to specify whether the system should create a project storage location for each project.

The project storage location hereby represents the place of performance of the project.
Stock entry entry storage location code For the procurement and logistics processes you define here a warehouse from which the warehouse setup for the financial accounting is to be copied.

The field "Stock entry one location code" can only be maintained if the storage location creation is activated ("Create project storage location").
Preferred transit code For the procurement and logistics processes, enter the transit code for the project warehouse transfer route here.

The "Preferred transit code" field can be maintained only if the storage location creation ("Create project storage location") is enabled.
Preferred delivery code For the procurement and logistics processes, enter the delivery agent code for the project warehouse transfer route here.

The field "Preferred delivery code" can only be maintained if the storage location creation ("Create project storage location") is activated.
Preferred carrier transport code For the procurement and logistics processes, enter the delivery agent transport type code for the project warehouse transfer route here.

The field "Preferred delivery transport code" can only be maintained if the storage location creation ("Create project storage location") is activated.
Attachment#

To create a project storage location, click "Associated" > "Setup" > "Storage location" on the project map in the ribbon.

During creation, the (new) fields are set as follows:

Field Description
Address fields According to customer or delivery address
Project no. Project number of the project
Debtor no. Customer number of the project

Note

When creating the project storage location, you must create the necessary stock transfer routes. The system supports you in this in such a way that it carries out the essential setups when creating the project warehouse on the basis of the information stored in the project setup. To set up the stock transfer routes, the system determines the warehouse that was defined as the storage location in the "Components of storage location" field in the production setup.

Storage location determination#

The system determines the storage location hierarchically when creating a new project plan line with an item:

  1. Project storage location if available
  2. Unit of responsibility, if any
  3. Company data, if available
Stock data#

When creating an article position in the project plan line, in case of the storage location found, a stockkeeping data card is directly created in the background for the article and the corresponding project warehouse.

In the project plan line, the procurement method can then be defined directly on the inventory data card via the "Procurement method" field.

If the procurement method "Stock transfer" is selected, a stock transfer route is directly created in the background according to the settings in the "Setup projects" for the standard warehouse.

Project Team#

A project team can be defined for each project. The definition takes place on the project card in the menu ribbon under "Project team".

Create the project team members using the table below:

Field Description
Project no. Specifies the number of the project to which the project team is assigned.
This field is filled in automatically.
Type Here you define which type the project member has. You can choose between resources (internal and external employees) and contacts (project members of the customer or further project participants).
In the case of the contact type, the system fills the Company no. field using the customer no. of the project card, from which the company name is also derived.
No. Here you can select depending on the type of member.

Type=Resource: Selection of the respective resource no.
Type=Contact: Selection of the respective contact no.
Type=User: Selection of the respective UserID
Roll code Specifies the role of the project team member.

To assign code to the roles, roles must have been previously set up in the table of the same name.
Roll Specifies the name of the role.
Start date Specifies the start date for the deployment of the resource. The start date automatically defaults to the project start date and can be changed manually.
Name Specifies the name of the resource, contact or user.
E-mail Specifies the e-mail address of the resource, contact or user.
Phone no. Specifies the phone number of the resource, contact or user.
Cell phone no. Specifies the cell phone number of the resource, contact or user.
End date Specifies the end date for the deployment of the resource. The end date automatically defaults to the end date of the project and can be changed manually.
Company no. Specifies the company number of the contact as soon as the Type=Contact field.
Company name Specifies the company name.
Business relationship Indicates the business relationship
Seller code Specifies the seller of your company
People Contact No. Specifies the persons contact no.
Planned quantity Specifies the plan quantity of the project team member.
Quantity plan lines Specifies the amount of plan lines for the project team member.
Residual quantity Plannable Indicates the remaining quantity that can be planned by the project team member.
Amount of time Indicates the amount of time already recorded for the project by the project team member.
Project quantity Specifies the project quantity for the project team member.
Total consumption Indicates the total consumption of the project team member.
Rest plan lines Specifies the remaining amount of plan lines for the project team member.
Rest plan Specifies the remaining plan quantity of the project team member.

Note

If the fields "Responsible" and / or "Project Manager" are maintained on the project card, the project team records are also created with the Responsible / Project Manager role.

If you maintain a resource in the project plan lines, data records are also generated for this project team.

Please note that when creating from the project plan line, the team record is not deleted when changing the resource or deleting the record.

Risk Management#

Risk management allows you to calculate, monitor and counteract project risks. Using the task management within the risk line, you can define preventive measures.

To calculate and monitor the project risks, call up the "Risk management" via the menu ribbon. The corresponding fields are explained in more detail below:

Field Description
Comments This field indicates whether a comment of the risk line is deposited.
Risk no. This field must be filled. It controls the position of the risk line and thus the clarity of the entire risk list.
Description This field can be used to store a description for the risk.
Risk type In this field you enter the type of risk.

This field offers the following options:

- RiskIndicates
the risk

- HeadingSpecifies
a heading

- SumWith
this option you can create a sum over several risk rows. You define the range using the "Total" field.

- From-totalAs
in the chart of accounts, you can create a from-total - to-total over several rows in Risk Management.

- To-totalAs
in the chart of accounts, you can create a from-total - to-total over several rows in Risk Management.
Counting up This field specifies which risks are added together. This field works for the "From-total", "To-total" and "Total" risk types. When using the "From-total" and "To-total" risk types, the system automatically fills the "Add up" field of the row with the "To-total" risk type.
Number of open tasks Indicates the number of open tasks (measures) generated by the task creation.
Entry date In this date field, you store the date on which the risk may occur.
Responsible In this information field a user can be assigned as responsible for this risk.
Damage (MW) This field is used to specify the amount of damage.
Cum. Damage (MW) This field is automatically filled based on the "Damage (MW)" field and indicates the cumulative damage.
Probability % In the "Probability %" field, the probability of the risk that could occur is indicated.
Cum. Damage assessed (MW) This field is automatically filled based on the calculation of the "Damage (MW)" and "Probability %" fields.
Damage n. Completion (MW) This information field can be used to specify the damage after the completion of the project.
Cum. Damage n. Completion (MW) This field is automatically filled with the cumulative value of the field "Damage n. Completion".
Prob. n. completion % This information field can be used to indicate the probability of the risk after completion of the project.
Cum. Damage assessed n. closure (MW) This field is automatically filled based on the calculation of the fields "Damage after completion (MW)" and "Probability after completion %". It describes the assessed damage after completion of the project.
Active This identifier controls whether the risk is active or not.
Identified by This field is automatically filled with the user name that entered the risk line.
Identified on This field is automatically filled with the working date on which the risk line was created.
Cause Description A description of the cause can be stored here.
Damage description A description of the possible damage can be stored in this field.
Measure costs (MW) The measure costs of the risk can be entered here.
Cum. Measure costs (MW) This field is automatically populated based on the "Measure Costs (MW)" field and indicates the cumulative measure costs.
Damage Actual (MW) In this field you enter the actual damage.
Cum. Damage Actual (MW) Based on the "Damage Actual (MW)" field, this field is automatically filled.

Project effort#

In the following, the individual areas are explained in more detail, through which the project, effort and consumption can be assigned.

Thus, on the one hand, the expenses of the resources are recorded in the form of working hours, and on the other hand, article consumption is recorded via stock or project purchasing.

This results in the actual values of a project. Subsequently, these actual values are compared with the planned values.

Personnel / benefit expenses#

The implementation of projects includes consumption as well as sales. Project consumption primarily includes the expenditure of resources. Resources can be employees, machines and subcontractors.

Resource expenditures are always made in the resource base unit via the timesheet. All person resources should have this code as the base unit on the resource card.  

Record timesheet#

Using the time sheet, the resources can record their expenses with a corresponding description on the projects. For each resource, the time sheet must have been created beforehand for the corresponding period. For more information, see "Creating timesheets" or the Microsoft Dynamics Business Central™ Helpsite (F1).

Release of the transmitted working times#

The submitted working times of the employees are then approved by the timesheet approver.

To release the transferred working times, call up "Time sheet for manager" via the user search.

The time sheet for manager card opens on which the transferred working times are listed. Via the menu ribbon you have the possibility to approve or reject the transmitted working times via the calls "Approve"/"Reject".

Further information on this topic can be found in the Microsoft Dynamics Business Central™ Helpsite (F1).

Project book sheet#

The time sheet is used to record the project time consumption. To ensure that the projects are also debited with the posted project time items, i.e. the project time items are transferred to so-called project items, the posted time consumptions must be entered via the project book.sheet.

The project posting sheet is used to post project items of all types. For example, material from the warehouse can also be posted here as project consumption. At this point, only the transfer of project items from the project time items will be discussed.

The menu item "Suggest project book. sheet lines" creates an input mask in which the filters for the retrieval can be set specifically.

This function is used to retrieve project time items that have not yet been transferred to project items. As a rule, each project manager retrieves the project time items for which he is responsible. For this purpose, each individual project can be edited or the "Responsible" filter can be used.

The call fills the project book.sheet with all necessary data from the project time item. One book.sheet line is created per project time item.

After updating, the project book sheet is empty again and the corresponding project items have been created.

External resources#

External resources can be purchased via purchasing documents.

For external resources, a vendor can be specified on the resource card. This creditor is the invoicing party, e.g. a personnel service provider. In the case of a freelancer, the freelancer must be created as a resource and as a vendor and linked accordingly.

If an external resource is entered in the project plan lines, this vendor is transferred to the field of the same name in the project plan line. Thus, a cost price determination can be carried out specifically for the combination resource / vendor. Also a creation of a purchase order of the external resource from the project plan line takes place with the creditor of the project plan line.

In addition to cost prices, sales prices and purchase prices can also be defined for external resources.

Cost of materials#

In addition to the time spent on resources, projects also have material costs. This is managed via articles. The demand is defined and planned in the planning lines. The missing parts are ordered or produced via purchasing or production.

Project Purchasing#

Plant engineering allows you to trigger purchasing documents directly from the project plan lines.

Create purchase request#

Using the "Create purchase request" function, you can send the request to the supplier directly from the project plan line.

The following requirements must be met:

  • it is not a position already transferred
  • for each line a vendor no. is maintained
  • the project is not in the "Locked" status
  • if it is an item without a planning date, it must be a comment line

Otherwise, a corresponding message appears.

After a successful check, a window will open where you can make the following decisions:

Field Description
Create new document Specify whether you want to create a new document or attach the items to an existing purchase request.
Document date Specify which document date the purchase request should receive.
Attach to document If you want to add to an existing purchase request (Create new document = No), you can specify the document to be updated here.

Determine to which document you want to assign the selected lines. A list of possible documents is displayed for this purpose.
Lines outline Specify here whether a row outline should be created when a new document is created.

When adding documents, you will not be offered the choice and the outline type of the existing document will be kept.

Confirm your selection with "Ok".

Subsequently, all selected lines marked on the line type "Budget" or "Budget and Invoiceable" are transferred to the purchasing request. In addition, the project no. in the header of the purchasing document is maintained with the project no. from the project from which it was generated. The requested quantity corresponds to the remaining quantity of the project planning line minus the quantity already reserved for it.

The document number of the generated request is displayed in the "Purchasing document number" field. By clicking on the number you can open and view the document.

You can convert the purchase request to a purchase order later in the process. In doing so, the "Purchasing document number" field in the project plan line is adjusted with the number of the purchase order.

If one of the following fields is changed in the project plan line, the system tries to transfer the change to the purchase line as well:

  • Description
  • Description 2
  • Type
  • No.
  • Work type
  • Variants code
  • Quantity
  • Unit code
  • Cost price
  • UK price (MW)
  • Line discount %
  • Planned delivery date
  • Storage location
  • Stockyard
  • Currency code

Note

Please note that the new currency code must match the currency code of the purchase document, if not, an error message will appear.

Create order#

Using the "Create Purchase Order" function, you can directly create a purchase order for the project plan line out.

The following requirements must be met:

  • it is not a position already transferred
  • for each line a vendor no. is maintained
  • the project is not in the "Locked" status
  • if it is an item without a planning date, it must be a comment line

Otherwise, a corresponding message appears.

After a successful check, a window will open where you can make the following decisions:

Field Description
Create new document Specify whether you want to create a new document or attach the items to an existing purchase order.
Document date Specify which document date the purchase order should receive.
Attach to document If you want to add to an existing purchase order (Create new document = No), you can specify the document to be updated here.

Determine to which document you want to assign the selected lines. A list of possible documents is displayed for this purpose.
Lines outline Specify here whether a row outline should be created when a new document is created.

When adding documents, you will not be offered the choice and the outline type of the existing document will be kept. Confirm your selection with "Ok".

Subsequently, all selected lines marked on the line type "Budget" or "Budget and Billable" are transferred to the purchase order. In addition, the project no. in the header of the purchasing document is maintained with the project no. from the project from which it was generated. The quantity to be ordered corresponds to the remaining quantity of the project planning line minus the quantity already reserved for it.

Depending on the maintenance of the field "Reserve", the order line will be created in such a way that the project no. as well as the project task will be taken over from the plan line into the purchase line when reserving "Never". By posting the document, the position is directly debited to the project.

From Reservation "Optional" onwards, the fields (Project no. and Project task) are not filled and the project consumption must be done manually.

The project line type is always set to Budget.

Note

KUMAVISION factory365 specific referencing fields are filled in the background, so that the purchase order item is considered in the project chart of accounts or also in the commitment consideration.

If one of the following fields is changed in the project plan line, the system tries to transfer the change to the purchase line as well:

  • Description
  • Description 2
  • Type
  • No.
  • Work type
  • Variants code
  • Quantity
  • Unit code
  • Cost price
  • UK price (MW)
  • Line discount %
  • Planned delivery date
  • Storage location
  • Stockyard
  • Currency code

Note

Please note that the new currency code must match the currency code of the purchase document, if not, an error message will appear.

Planning proposal#

Alternatively, you can generate the purchase requisition/purchase order conventionally via the planning proposal. To do this, select the "Planning proposal" function via the respective project plan line.  

Project manufacturing#

As for project purchasing, plant engineering offers the possibility to trigger the manufacturing or assembly processes directly from the project plan lines. The following options are available for this purpose:

Planning proposal#

Using the "Planning proposal" function, you have the option of generating a production order via the planning proposal.

The production document number is displayed in the "Reserved by" field. By clicking on the number you can open and view the document.

Assembly order#

Microsoft Dynamics Business Central™ enables an assembly order for an assembly item to be generated from a sales order via the so-called "order assembly". In the course of the sales delivery, the corresponding assembly order is posted in the background.

This functionality has been transferred to plant engineering. This means that you can enter the assembly item directly in a project plan line and generate the assembly order accordingly via the fields "Quantity for order assembly" and "Quantity for order assembly (basis)". The document number of the generated assembly order can be seen in the "Reserved by" field and the document can be called up directly from this point.

If a sales order with the corresponding item already exists in the system, it can be viewed via the fields "Sales document type = order" and "Sales document no. ".

Otherwise, they can be created from the project card via the "Tasks" > "Line" > "Documents" > "Create sales order..." info tab.

As soon as the sales line of the related assembly item is delivered via the order, the assembly order is posted.

Please refer to the Microsoft Dynamics Business Central™ Helpsite (F1) for the maintenance and handling of assembly items.

Project accounting#

The sales document forms the commercial basis vis-à-vis the customer. From the project tasks, the sales calculation can be transferred into a quotation and / or order.

General behavior#

Project type#

In the project type, you can set up an order type for the creation of sales documents, if required. This will be used when creating the documents.

Status#

When creating documents, it should be noted that this is only possible from the project tasks / project plan lines if the project has the required status:

  1. Quotation can be created only with project status "Quotation" as well as "Order".
  2. Order as well as complaint can be created only with project status "Order
  3. An offer can only be converted into an order if the project status is "Order".
  4. Only project plan lines with the Billing item "Yes" flag (line type "Budget and Billing" as well as "Billing") can be transferred to a sales document.  
Document quantity#

The documents can be created from the project plan lines as well as from the project tasks. The system uses the field "Quantity to be transferred to invoice" to determine the quantity of documents (offer, order, invoice, credit note and complaint).

Address data#

The sales header takes over the address data from the project header. This means the sales to information of the project is transferred to the sales to information of the offer or order the same with the invoice to data. The delivery address is derived from the sales to address.

Position numbering#

The item numbering in the sales documents depends on the creation of the plan lines as well as on the task breakdown.

Task planning#

If you have used the task planning, the position number is filled with the planning project task.

Use of the project outline#

The position numbering is based on the project task. The from line has the project task as item no., the plan line supplemented by the extension of the next level of the project outline.

Consecutive numbering#

If there is no project structure, the item number is determined on the basis of the project task no. '.' and the consecutive number. If the maximum length of 20 characters is exceeded, the project task will be shortened so that the sequential number can be added up to the maximum value of 99. When the consecutive number reaches 100, an error message appears.

Order type#

The order type represents whether the order is the initial order or a follow-up order. If, when creating a new sales document, it is determined that a document already exists, the system switches the order type to follow-up order.

Updating the vouchers#

The project is the leading bracket in plant engineering and thus allows updating sales documents from within the project.

An update from the sales documents and thus an indirect change of the project plan by the order department is not possible. However, a maintenance of order specific data such as the assignment of the article tracking is allowed.

The project plan is updated by posting results, which are made by the system in the background.

Posting result depending on the line type#

Please note that only lines with the line type "Billable" and "Budget and Billable" will be included in the sales document.

Billable lines do not create any items in case of deliveries, in case of billing they create a project item with the item type "Sales".

Budgetable and billable lines also generate project items with the item type "Consumption" for deliveries.  

Function support#

Below you will find the functional support for VK documents generated from a plant engineering project in tabular form:

Function call via Function Support
Manage rows Attribute search Disabled
Lines Article availability according to Event Active
Lines Article availability according to Period Active
Lines Article availability according to Variant Active
Lines Article availability according to Storage location Active
Lines Article availability according to BOM level Active
Rows\Line\Related information Reservation item Reference to project plan line
Rows\Line\Related information Item tracking lines Reference to project plan line
Rows\Line\Related information Select replacement item Disabled
Rows\Line\Related information Dimensions Reference to project plan line
Rows\Line\Related information Comments Active
Rows\Line\Related information Article Allocation of additions/deductions Disabled
Rows\Line\Related information Delivery date commitments Reference to project plan line
Lines\Row\Linked information\Order assembly Program production lines Disabled
Lines\Row\Linked information\Order assembly Calculate multilevel price Disabled
Lines\Row\Linked information\Order assembly Calculate multilevel costs Disabled
Rows\Line\Related information Document line tracking Active
Line\Line Calculation tracking lines Disabled
Rows\Line\Related information Incoming orders Active
Lines\Row\Linked information\Document texts Pretext Active
Lines\Row\Linked information\Document texts Post text Active
ROW FEATURES Get price Disabled
ROW FEATURES Retrieve line discount Disabled
ROW FEATURES Unfold parts list Disabled
ROW FEATURES Insert text modules Active
ROW FEATURES Reserve Reference to project plan line
ROW FEATURES Demand creator Reference to project plan line
ROW FEATURES Select catalog item Disabled
ROW FEATURES Calculate manufacturing cost estimate Disabled
Line order direct delivery Order Disabled
Line order special order Order Disabled

Offer for sale#

You can create a sales quotation directly from the project via the project plan lines. The function calls can be found on the one hand on the project map via the "Tasks" info tab and on the other hand via the project plan lines.

If the document creation is triggered from the project plan line, the system tries to transfer all selected project plan lines to the sales quotation.

When creating from the project tasks, all the billable lines of the tasks are transferred to the sales document.

If you want to create a sales quotation for all lines, the "Tasks" info tab can be used to call up the quotation. By means of the row selection you can control which task rows are to be considered.

Note

Please note that only project tasks of line type="Budget and Billable" or "Billable" can be transferred in a UK document

Sales documents are created at the project customers. For this purpose, the information stored in the project is used. Thus, sales to customer, invoice to customer, the delivery address and the payment terms of the project are used to create the sales documents.

After commissioning, the sales quotation can be converted into an order in the system as usual using the "Create order" function.

Sell order#

If the customer has already ordered the project, you can also create a sales order directly from the project via the project plan lines. The function calls can be found on the one hand on the project map via the "Tasks" info tab and on the other hand via the project plan lines.

If you want to create the sales order over all lines, the call via the "Tasks" info tab is suitable at this point. By means of the row selection you can control which task rows are to be considered.

Sales documents are created at the project customers. For this purpose, the information stored in the project is used. Thus, sales to customer, invoice to customer, the delivery address and the payment terms of the project are used to create the sales documents.

The order processing corresponds to the standard order processing.  

Delivery#

Maintain the quantity to be delivered in the "Quantity to be delivered" field. In case of an activated item tracking please maintain the concerned serial no. or batch no. via the item tracking. Item tracking maintenance from the order is the same as item tracking maintenance from the project plan lines.

Invoice#

Maintain the quantity to be invoiced in the "Quantity to invoice" field. Please note that if item tracking is enabled, no item tracking can be specified for the billing case.

Dimension expansion#

For easy evaluation of the projects, the creation as well as assignment of dimensions has been optimized.

Dimension specification by the activity type#

Dimension specifications can be assigned to the activity type, so that when the activity type is selected in the project task, the dimension is assigned to the task.

Project type#

In the project setup you can define that for reporting purposes a dimension Project type is maintained and assigned to the system in parallel to Project type.

Project Chart of Accounts#

For effective project controlling, all project movements can be assigned and evaluated via a separate chart of accounts.

Down payment accounting#

Within financial accounting, KUMAVISION's "Down Payment Accounting" module enables the simple planning, creation and management of down payment invoices. The add-on module is fully integrated into the standard processes of accounts receivable and accounts payable, such as dunning and payment transactions, and can likewise be used for plant engineering in KUMAVISION factory365.

Note

Please note that the "Down payment accounting" module is an add-on module that requires additional licensing. If you do not have this license integrated in your solution, the following functionality from this section will not be available to you.

The following adjustments were made for this purpose:

Down payment plan#

The following fields have been added to the down payment plan in KUMAVISION factory365:

Field Description
Project task no. Contains the project task number you assigned.
Maintenance is possible only for projects.
Milestone Define herewith that when completing a milestone, the defined down payment invoice is generated by the system in the background. The FiBu department then only has to post and send this.

You can access the down payment plan for projects as well as project tasks via Down payment plan in the project card.

By maintaining the project task, you specify that you want to set the down payment schedule at the project task level.

Note

Please note that if you select a project task defined as a milestone, the system will also activate the milestone billing functionality (the Milestone field defined with a check mark). A combination of the source types Project as well as Project task is not allowed.

Down payment plan by milestone#

If you have assigned a milestone for invoice creation in the down payment plan, the down payment invoice is created when the status of the milestone changes to completed.

For more information, see "Down payment accounting".

Forecast & Commitment#

The goal of a project forecast is to determine a preview of the expected costs at the end of the project (Estimate at Completion EAC) as well as the currently achieved project value (Earned Value EV) on the basis of the current project planning, the costs already incurred and the assessment of the project manager.

You can forecast the following areas in KUMAVISION factory365:

  • Project
  • Project Task,
  • Project planning line
  • Project task account

In the following, the fields on the "Forecast & Commitments" info tab are first explained in more detail:

Field Description
Planned cost price (MW) Indicates the planned cost price (MW) for the project.

Forecast on You can enter the forecast at the following level:

Empty:
No forecasting

Project:
In addition, in the "Forecast (MW)" field on the "Forecast & Commitment Amounts" info tab, specify the total costs you currently expect for the overall project.

Project Task:
On the corresponding task line, in the "Forecast (MW)" field, you can see the total costs that you are currently calculating for the project task.

Project planning line:
On the corresponding project plan line, in the "Forecast (MW)" field, you can see the total costs that you are currently calculating for the project plan line.

Project task by account:
On the project plan line aggregated by project account (Project task - Edit - Project plan line aggregated by project account) you can see in the "Forecast (MW)" field the total costs you are currently calculating for the account.

Note:
If you change the "Forecast to" setting, any existing forecast items will be disabled.

Note:
Please note that the field "Forecast Maintainable" must be activated for the maintenance of the field "Forecast (MW)".
Forecast Maintainable Check the box to maintain the "Forecast (MW)".
Actual progress % The solution enables you to define an objective progress definition by the project manager or consultant on the levels project - project task - project plan lines in addition to the calculated progress definitions.
The definition is made in the Actual progress % or Forecast (MW) field. The Actual progress date field is also always defined with the current date.
Forecast (MW) If you set the forecast to "Project", use this field to specify the total costs you currently expect for the entire project.

For the calculation of the forecast (MW), the system determines it as follows:

(Consumption (cost price)
Time commitment Amount (MW)
Purchase commitments Amount (MW)
Stock commitment Amount (MW)
Production commitments Amount (MW))
Actual progress %
Forecast (MW)
Actual progress date Specifies the date of actual progress for the project.
Stock commitment Amount (MW) Indicates the amount of stock allocated/reserved for the project.
Purchase commitments Amount (MW) Specifies the amount of the captured order lines for the project.
Time commitment Amount (MW) Specifies the amount of recorded working hours for the project.
Production commitment (MW) Indicates the amount of production items recorded for the project.
Cost price (MW) Specifies the cost price of the project in client currency.
Last booking day Specifies the last booking day for the project.
Planned costs for production order (MW) Indicates the amount of production orders assigned/reserved for a project.
Capacity costs (MW) Specifies the capacity items for the project.
Consumption costs (MW) Indicates the consumption costs for the project.
Actual messages (MW) Specifies the value of the actual messages for the project.

When you change the "Forecast MW", the Forecast Argumentation window always opens. In the Forecast Argumentation window you can define or influence the creation of the plan lines. If you exit this window by clicking Cancel, your entry will be discarded. To save the change, you must have maintained the "Argumentation" field.

Note

Please note, a subsequent deletion of the Forecast Argumentation is only possible in reverse chronological order (the last record then the second to last etc.).

Field Description
New value Enter the new total value for the position here. In this field, the value from the forecast (MW) is transferred when creating from the project task as well as project plan line.
The system also determines the "Additional Cost Amount (MW)" value from this.
The "Additional cost amount (MW)" value is also transferred to the Additional sales amount (MW) field.
Additional purchase price (MW) In this field, the system displays the budget change in absolute terms in client currency.
Argumentation Here you can justify why the task was budgeted again.
Order type Use the Order Type field to specify which type of budget adjustment you currently want to make.

You can make the following selections in the option field:

Option value - Description
'' - Empty, No definition
Initial commissioning - First commissioning, planning
Follow-up order - Budget change, but with sales increase
Deviation - Budget change, without sales adjustment.

The Additional sales amount (MW) field is not editable.

Please note that you can already make a global setup in the project setup, so this selection is hidden.
Project Contract Item No. If the point was created as a project plan line, this field refers to the generated plan line.
Additional sales amount (MW) In this field, maintain the extent to which the budget change is also converted as an increase. The field is initialized by the additional cost amount (MW) for the order types initial order and follow-up order.

Establishment#

For the later forecast creation within a project, some settings have to be made in advance. In the following, the facilities for the possible forecast levels are explained in more detail:

Project#

Forcasting at the project level requires the following fields to be set up in the "Projects setup":

Field Description
Art Forecasting Specify here whether and if so via which type (and no.) you want to transfer the determined budget variance to the project.

No budgetingThe
defined forecast has no deviation on the plan lines

ResourceThe
defined forecast is created with a project plan line of the type Resource.

ArticleThe
defined forecast is created with a project plan line of the type Article.

G/L accountThe
defined forecast is created with a project plan line of the type G/L account.

Project accountThe
defined forecast is created
with a project plan line of type "Rework".
No. Forecasting Specify here whether and if so via which no. you want to transfer the determined budget variance to the project.
Only deviation in the forecast Define here whether the forecast should create pure deviation plan lines or (deactivation of the switch) these can also be set to billable.
Forecast project task no. At this point, define on which project tasks the recorded forecast deviation should be realized.

The system records a new project plan line with the variance amount in the project task when versioning the forcast.

The following applies:
- positive deviation = creation negative project plan line
- negative deviation = creation of positive project plan line
- neutral: No creation of a project plan line
Service type for project forecast In case of forecasting on project, you define here with which activity type the project task for the deviation should be created.
Project Task#

Forcasting at the project task level requires the following fields to be set up in the "Projects setup":

Field Description
Art Forecasting Specify here whether and if so via which type (and no.) you want to transfer the determined budget variance to the project.

No budgetingThe
defined forecast has no deviation on the plan lines

ResourceThe
defined forecast is created with a project plan line of the type Resource.

ArticleThe
defined forecast is created with a project plan line of the type Article.

G/L accountThe
defined forecast is created with a project plan line of the type G/L account.

Project accountThe
defined forecast is created
with a project plan line of type "Rework".
No. Forecasting Specify here whether and if so via which no. you want to transfer the determined budget variance to the project.

In addition, the following fields must be maintained in the "Activity types":

Field Description
Art Forecast Define here with which type of project plan line the forecast position should be created.
Forecastnr. Define here, depending on the type of forecast, to which master record the project plan line should be linked.
Forecast work type code In case of the type Forecast resource, define here a work type with which the forecast should be created. (Optional)
Project plan line#

When forcasting to project plan line, the system uses the values directly from the respective line, therefore no further setup is required.

Project task account#

Forcasting at project task account level requires the following fields to be set up in the "Projects setup" or in the

"Activity types":

Field Description
Type Forecasting Specify here whether and if so via which type (and no.) you want to transfer the determined budget variance to the project.

No budgetingThe
defined forecast has no deviation on the plan lines

ResourceThe
defined forecast is created with a project plan line of the type Resource.

ArticleThe
defined forecast is created with a project plan line of the type Article.

G/L accountThe
defined forecast is created with a project plan line of the type G/L account.

Project accountThe
defined forecast is created
with a project plan line of type "Rework".
No. Forecasting Specify here whether and if so via which no. you want to transfer the determined budget variance to the project.

In addition, the following fields must be maintained in the "Activity types":

Field Description
Art Forecast Define here with which type of project plan line the forecast position should be created.
Forecastnr. Define here, depending on the type of forecast, to which master record the project plan line should be linked.
Forecast work type code In case of the type Forecast resource, define here a work type with which the forecast should be created. This setup is optional.

Capture#

You define the level at which you want to make the forecast on the project map on the "Forecast and Commitment Amounts" info tab in the "Forecast on" field.

Note

Please note that the "Forecast maintainable" switch must be activated for maintaining the forecast. This ensures protection against error recording.

Project#

You can enter the forecast at the project level on the respective project card, on the "Forecast & Commitment Amounts" info tab in the "Actual Progress %" field.

Note

The "Actual progress %" field is automatically pre-populated with the calculated progress from the system for the first time when "Forecast on=Project" is selected.

Project Task#

You can enter the forecast at the project task level on the project card on the "Tasks" info tab or in the project task card (info tab "Lines" > "Line" > "Project task card").

The fields "Actual progress %" and the field "Forecast (MW)" are available for the entry. You can thus maintain the forecast either as a percentage or with an absolute amount. The fields calculate each other.

Project plan line#

You can enter the forecast at the project plan line level in the project plan line as well as in the project task cards on the "Project plan lines" info tab.

The fields "Actual progress %" and the field "Forecast (MW)" are available for the entry. You can thus maintain the forecast either as a percentage or with an absolute amount. The fields calculate each other.

Project account#

You can enter the forecast on a project account of a project task in the project task map on the info tab "Project plan line aggregated by project account".

The fields "Actual progress %" and the field "Forecast (MW)" are available for the entry. You can thus maintain the forecast either as a percentage or with an absolute amount. The fields calculate each other.  

Release#

After maintaining your forecast for a project, you can have the deviations resulting from the forecast written to the project, depending on their settings, via the call Associated\Archive\Version Release in the project card.

Please note that the Forecast field is cumulative:

Cost amount (MW) Forecast (MW) Variance item Cost amount (MW)
Initial commissioning 5000,00 €
Forecasting 1 5000,00 € 7000,00 €
After archiving 5000,00 € 7000,00 € First position 2000,00 €
Forecasting 2 5000,00 € 10000,00 € 2000,00 €
After archiving 5000,00 € 10000,00 € Other position 3000,00 €

Project controlling#

In this section, the possibilities of project controlling are presented. It will be discussed how project results with multi-level contribution margin accounting can be presented in the Projects module with the help of the project chart of accounts. In addition, the project information that can be called up immediately is presented.

Project controlling is basically based on budgeted and actual values. The realization should correspond to the planned values. In order to be able to manage the project properly and promptly, a comprehensive evaluation of the planned values and the actual values incurred, related to the stored time periods, is immensely important. Microsoft Dynamics Business Central™ offers this evaluation.

The project items show the actual values that are charged to the project from daily work. These are usually goods or time postings. The plan values are defined via the project tasks and its project plan lines. This enables a target/actual comparison of certain cost types. On the basis of this project chart of accounts, evaluation schemas can be formed, with which, combined with correspondingly generated column layouts, specific information can be formed from the values. The procedure corresponds to the account evaluation in the financial accounting area.

Data basis and structure#

The creation of the project account framework is fundamental for project controlling via Microsoft Dynamics Business Central™. This contains the most important areas (cost types and revenue types) that are important for the company for the evaluation of projects. The level of detail of the accounts can be freely selected. Thus, a very compact or also a very elaborate project chart of accounts can be the basis.

Based on this, the project items or plan values are formed. These items are combined using a project account scheme.  

Project chart of accounts and project account setup#

All project entries can be posted to project accounts via the project account setup, similar to the G/L items in financial accounting. This enables evaluation possibilities to an undreamt-of extent.

The project account and the project chart of accounts have already been explained in the section "Project setup", so only the project account setup will be discussed in detail here.

Project account determination is based on the combination of product posting group, project type and activity type. Each combination is assigned a consumption and sales account from the project chart of accounts.

The information is used to determine the respective project account as follows:

Field Description
Product posting group From the consumed or invoiced item, resource, G/L account. The product posting group is the only mandatory field in the matrix.
Project type From the project
Service type From the addressed project task to which the consumption or revenue was posted or planned.

With the above information can be e.g.

  • the resource expenditure for project management on research projects with internal resources
  • the cost of small materials for assembly on site
  • the travel times of external employees on major projects
    can be determined.

Depending on what is to be evaluated later, the project chart of accounts and especially the matrix must be set up accordingly.

Project items = actual values#

With each posting where a project is addressed, the system creates a project item. Project items form the basis for project settlements (expense items) and reflect the revenues of these settlements (revenue items). Project valuation is also built on the project item.

For project controlling, the project item provides all ACTUAL information from consumption and from sales.

As soon as a project booking is made, a project account is assigned to the resulting project items via the matrix mentioned above. In this way, actual consumption and actual sales can be used directly for project controlling.

Down payment plan / payment schedule#

Both options behave the same. The only difference is the data source. While the payment plan is a general payment plan for projects, the down payment plan is a part of the down payment accounting module.

Project account schemeta#

As soon as project plan lines and bookings are formed, projects can be evaluated. How and according to which criteria these projects are evaluated on the basis of this data is mapped in the project account schemes. The thinking and procedure of these project account schemes corresponds completely to the procedure in financial accounting with the account schemes on the basis of the G/L accounts and G/L items there.

To set up the project account schemes, call up the "Project account schemes" via the user search.

Several structures can be defined via the project account schemes, which can be used to throw different views on the project results. E.g. internal projects should be evaluated differently than customer projects. The project account scheme defines the structure of the rows. In the following the setup fields are explained in more detail:

Field Description
Code Specifies a meaningful abbreviation of the project account scheme.
Description Specifies a description of the project account scheme.
Standard column layout In the field "Standard column layout" you can define the criteria for the evaluation in the column view. The column layout stored there is always used as a basis when calling up a project account scheme. However, it is possible to assign a different column layout at any time.
Project account schemes lines#

A report structure is set up in the project account scheme itself, in which the corresponding project accounts are assigned to the individual lines. Totals lines or formulas can also be entered.

The important fields are:

Field Description
Heading no. A logical line numbering is to be stored in the field "Rubric no.".
Description In the "Description" you have to enter which area you want to display in this line.
Counting type In the "Totals type" field, specify whether an account total, a grand total or a formula should be stored.

When specifying the account total, the values of one or more accounts are displayed.

If the Totals selection is activated, totals lines from the project chart of accounts can be taken into account.

If the Formula type is selected, a formula can be defined within the project accounts scheme.
Counting up In the "Totals" field, according to the previously defined type, project accounts, totals rows or calculation formulas can be specified.
Line type This field can be used to define whether the line is a main line or an auxiliary line.
Hide row This field can be used to control whether the line should be shown/hidden.
Line color By means of the selection it can be indicated whether the line is to be printed "black" or "blue".
Boldface The check mark can be used to specify whether the line should be printed in bold.
Project account schemes column layout#

When you call the "Set up column layouts" function, the Column layout project page is opened. Among other things, the column layout TARGET - ACTUAL is stored in the database.

Field Description
Column no. In the "Column no. " an identification of the line is to be indicated.
Column heading In the field "Column header" you have to enter the name of the column as it should appear in the printout.
Column type In the "Column type" it is possible to specify what will be done in the column:

Formula:
Calculations are performed between the columns.

Motion:
Pure transaction data is displayed.
Item type In the field "Item type" the respective item type (depending on the field "Column type=Movement) must be specified.
Archive source Depending on the "Item type" field, the archive source must be specified if necessary.
Document type The type of document is defined in the Document type field. This field depends on the item type. E.g. Item type=Purchase line can be defined as document type "Offer".
Amount type The "Amount type" field specifies what type it is, e.g. "Cost amount".
Assignment type filter In this field, a filter can further narrow down this line.
Comparison date formula In the "Comparison date formula" field, you can define which comparison period is to be displayed. The entry is made in relation to the time period specified in the date filter in the report requests. Entries can be made with the known time specifications (T, TW, W, M, Q, J).
Formula In the "Formula" field, the formula can be entered if the column type is the Formula selection.
Rounding factor In the "Rounding factor" field, you can specify whether and if so how to round. This allows large values to be displayed clearly.
View The "Display" field can be used to define whether the column

• always,
• never,
• if positive
• If negative

is displayed.
Red color The display is in red color.
Green color The display is in green color.
Project account schemes matrix#

You can call it up via the menu item "Matrix". It shows you the values resulting from the defined rows of the account scheme and the columns of the column layout.

Archive project versioning and project status#

The project planning in Microsoft Dynamics Business Central™ is always supplemented and corrected, so that a comparison of different plan statuses is not possible. In the plant engineering solution, you can carry out a versioning of the project planning in order to have access to older planning statuses and to compare two planning statuses with each other.

Project version#

To create a project version, execute the function "Release version" in the respective project via the menu ribbon. The current version of the complete project status has thus been archived and can be viewed via the number of the "Archived versions" field on the "General" info tab or via the menu ribbon under the "Project archive" menu item.

The archived project states contain a complete copy of the project map with the following additional information on the "Version" info tab:

field description
Version number Indicates the version number of the archived project state.
Archived by Indicates who created the version.
Archived on Gives the date when the version was created.
Archived at Indicates the time when the version was created.
Archiving comment If an archiving comment has been stored during archiving, it is displayed at this point.
Last current no. project item Indicates the number of the last project item at the time the version was created.
Last Item Sequence No. No. Specifies the number of the last item at the time of version creation.
Last value item no. Specifies the number of the last value item at the time the version was created.
Last no. of resource items Specifies the number of the last resource item at the time the version was created.
Last no. of capacity item - Specifies the number of the last capacity item at the time the version was created.
Project structure version#

The project structure version can be viewed via the "Project structure" menu item in the project version ribbon. This corresponds to the project structure at the time of archiving with the additional identifier of the version number.

Note

When archiving from the project structure, the project map is also always archived.

Project version comparison#

By means of the project version comparison you can compare different project statuses with each other.

Setup#

To be able to use the project version comparison to the full extent, global settings must first be defined on the "Version comparison" info tab in the "Project setup". You can find more information here.

Version comparison field setup#

You can set up the version comparison field setup on the one hand via the "Projects setup" and on the other hand via the project version comparison mask. The difference between these two calls is that the call from the project setup is user-independent (field UserIDFilter = "empty") and the call from the project version comparison is made in relation to the user (field UserIDFilter = "UserID").

In the header of the version comparison field setup, general information is displayed first:

Field Description
UserIDFilter With the field "UserIDFilter" you have on the one hand the possibility to make a global setup for all users or to define specifically per user (by specifying the corresponding UserID) an individual comparison setup.
Number of Assigned Fields This field shows you the number of fields that have currently been activated in the "Visible" field.

In the lines you can make the actual setup. The individual fields and their meaning are explained in more detail below:

Field Description
Position Use the position numbering to determine the positioning in the version comparison in the version detail overview.
Field No. Indicates the number of the corresponding field.
Field Name Gives the field name of the field.
Field label Gives the field label of the field.
Visible Check the box if you want the field changes to be displayed in detail in the version detail overview.
Consider in field comparison By activating this checkbox, you control whether a comparison of the corresponding field of two versions should be considered in the version structure.

If the checkbox is not activated, the line will not be visually displayed accordingly in the version structure when a change or similar is made.
Compare project versions#

You can compare different project versions via the respective project card using the call of the same name located in the menu ribbon.

Note

Please note that two released project versions must exist in the system in advance for the version comparison.

The header of the project version comparison card contains the following fields:

Field Description
Project number Indicates the number for which a version comparison is to be made.
Calculate The switch serves as an identifier for the calculation.

By calling the version comparison, the system automatically creates a new calculation based on the two currently released versions.

As soon as you change a version, the switch deactivates. By the function "Recalculate" this is activated again.

(Switch is not editable for the user)
Version left Specifies the version to be compared with another opposite version.

Note:
Please note that when the project version comparison mask is called up, the two current released versions are always preset first.

To compare the versions specified in the header, the "Recalculate" function is executed in the ribbon.

A comparison structure with colored highlighting of the lines is inserted in the main window. The color scheme is similar to the one defined in the project setup .

Leading for the comparison structure is always version left. Means, all lines of the version left are inserted into the version structure under consideration (appropriate coloring) with version right. If there are additional lines in version right, these are also inserted in corresponding representation and position.

If version left has no opposite version for comparison, only version left is inserted.

For a better orientation of the coloring, the legend located in the footer offers you.

In the version details, either the fields of the line or the comparison of the fields, if the line is included in both versions, are displayed to you. Which fields are displayed how in the version details is defined in the version comparison field setup.

System logging#

The activity log items from the purchase and sales document printouts are marked with the project numbers from the header and can be seen from the project via activity log items.

Shipping preparation#

When manufacturing complex articles, the situation can often arise during shipping that the manufactured article has to be disassembled and packed in a manner suitable for shipping. The plant engineering solution offers you the possibility to handle this via the "shipping units". Here, the shipping units are supported in manufacturing and logistics.

Currently 3 different scenarios can be covered by the shipping units, which are described below:

Relocation of components#

An FA is set up whose components are to be transferred to a production warehouse for assembly. The components are grouped into shipping units that are easy to transport. From a released E+D order, these components can be inserted into a stock transfer order.

To do this, select the desired component lines and execute the "Transfer selected shipping units" function.

The system checks that the components to be transferred have already been consumed.

If the appropriately marked components have been consumed, then a transfer order is created that transfers the shipping units from the component storage location to the FA storage location. The "In-Transit Code" is preassigned by the "Preferred Transit Code" field in the project setup when using the plant engineering solution. Otherwise, the first storage location is pre-populated with the "Use as transit storage" identifier.

If the storage locations are subject to goods issue or goods receipt, they can be created and posted according to the standard.

During the posting process, no new item items are created in the background because the components have already been consumed. Through the postings, shipping unit items are formed. These can be used to check the status of the shipping units (opens by the lookup on a shipping unit).

After posting the receipt, the order is completed. The shipping unit can now no longer be shipped because it has already delivered the complete quantity. In addition, it can no longer be assigned to further components.  

Shipping units in goods issue#

If a production item is sold, the shipping units stored in the FA can also be inserted in a goods issue. For this purpose, the function "Insert shipping units" can be used in the goods issue.

If the sales line was reserved on a corresponding item line, then the shipping units from this FA will be automatically inserted. If there is no reservation, a selection of items will be opened and the user can decide which item to sell.

After selection, the shipping units belonging to the item are inserted into the goods issue.

If the FA associated with the item is not yet finished, the user must confirm that they wish to continue.

The original line remains, but the quantities are removed, since this item is automatically posted in the background after posting the shipping units. The posting of the goods issue with shipping units is now done as in the standard. After complete posting, the original item is also delivered and can be invoiced.

Shipping preparation#

In the production of complex articles, the situation can often arise in shipping that the manufactured article must be disassembled and packed in a manner suitable for shipping. In connection with the plant engineering solution, it is also possible to use shipping units across FAs within a project. For this purpose, it is necessary that the production orders have a project reference, e.g. that they are generated by MRP in the project.

Project-specific shipping units can now be assigned to these production orders by setting the "Project-specific shipping unit" checkbox in the component lines. This is set for all component lines of the production order.

Now shipping units can be assigned. They are no longer FA-specific, but can be assigned in all FAs that have the corresponding project number.

The assignment can also be assigned from the "Material structure" in the project. Here, all FAs linked to the project plan lines are directly visible. If the corresponding lines are transferred to a sales order, the shipping units can be used in the goods issue. For this purpose, the function "Insert project-specific shipping units" is used in the goods issue. To do this, all lines that belong to FAs that use project-specific shipping units are selected.

The goods issue can then be posted normally. After the shipping units have been fully posted, the original lines are automatically posted in the background and the sales delivery is completed. When inserting the project-specific shipping unit, the system checks whether each FA that uses one of the shipping units is also linked to this goods issue. If this is not the case, the system terminates with an error and points out the FA.

Basic information about shipping units can be found here

Complaint and credit note#

Complaint#

Should the case arise that a customer complains about the delivered goods, the complaint process can be started from within the project.

To do this, select the corresponding project plan line and execute "Create sales complaint" via the menu item.

A window will open where you can make the following decisions:

Field Description
Create new document Specify whether you want to create a new document or attach the items to an existing claim.
Archive existing document If the document is to be attached to an existing document, it is recommended to activate the "Archive existing document" button.

The existing document is archived again beforehand when activated.
Document date Specify which document date the complaint should receive.
Attach to document If you want to add to an existing complaint (Create new document = No), you can specify the document to be updated here.

Determine to which document you want to assign the selected lines. A list of possible documents is displayed for this purpose.
Lines outline Specify here whether a row outline should be created when a new document is created.

When adding documents, you will not be offered the choice and the outline type of the existing document will be kept.

Confirm your selection with "Ok".

Credit#

Detached from a complaint process, you also have the option to create a value credit note via a project plan line.

To do this, select the corresponding project plan line and call up the menu item "Create sales credit memo".

A window will open where you can make the following decisions:

Field Description
Create new credit note Specify whether you want to create a new document or attach the items to an existing credit note.
Posting date Specify which posting date should receive the credit note.
Attach to credit memo no. If you want to add to an existing credit note (Create new credit note = No), you can specify the document to be updated here.

Determine to which document you want to assign the selected lines. A list of possible documents is displayed for this purpose.