Project planning#
Project planning is presented below. It shows how a project can be structured and organized and how planned values can be stored.
Project (card)#
The structure of the project card is identical regardless of the status: Planning, Offer, Open, Completed. Depending on the status, some functions cannot be executed.
KUMAVISION factory365 extends the project(s) card of Microsoft Dynamics 365 Business Central1 with the fields and functions described below:
General information register#
| Field | Description |
|---|---|
| Project type | Specifies the type of project. If the following data has already been stored in the project type, it is adopted when |
| the project type is assigned to the project: - Project booking group - Project number series - Template project no. - Project type dimension code - Dimension code - Dimension value prefix - Task structure - Reserve - Order type See project types |
|
| Task breakdown | Specifies the task structure to be used for the project. The project task structure helps you to record and maintain your project tasks quickly and efficiently with predefined numbering. See project breakdown. |
Information register Tasks#
See project tasks.
Information register Invoice and shipping#
| Field | Description |
|---|---|
| Storage location code | The field is pre-assigned from the Projects setup by the standard project storage location (if available). If no default project storage location is stored in the setup, a selection list of the regular storage locations appears here. Note If "Create project storage location" is active in the Projects setup, the newly created storage location is entered in this field. The field is used when creating a project plan line of type "Article" to fill the "Storage location code" field in the project plan line. |
| Stock transfer from storage location code | The field is pre-assigned with the field of the same name from the Projects facility (if available). If no "Stock transfer from storage location" is stored in the setup, a selection list of all regular storage locations (no project storage locations) appears here. The field is used when changing the procurement method to "Stock transfer" in |
| a project plan line to fill the "Stock transfer from storage location" field in the project plan line. |
Information register Dates#
| Field | Description |
|---|---|
| Display forecast by | Options: - Day - Week - Month - Quarter - Year - Accounting period |
| WIP date | End date of the WIP evaluation. Later project bookings are no longer taken into account. |
Functions in the ribbon#
| Function | Description |
|---|---|
| Home Area | |
| Project Task Lines | Shows the task lines including the forecast matrix. |
| Project Termination | Executes the Project Termination function. |
| Duplicate Project Tasks | Starts the dialog for selecting the project tasks to be duplicated. |
| Project Gantt viewer | Opens the Gantt Viewer and shows the visualization of the project tasks including the stored predecessor/successor link and project plan lines. See Projekt Gantt Viewer |
| Project Chart of Accounts | Shows the project chart of accounts. |
| Project Account Schedule Overview | Shows an overview of the project account schedule. |
| Create Interact | Starts the Create Interact dialog. |
| Documents | Shows the list of project documents per document type and their number. |
| Create Obligo Entries | Create the Obligo Entries. See Create Obligo Entries. |
| Project Forecast Registration | Registers the forecast items. see Forecast registration. |
| Project area | |
| Project plan lines | Displays the project plan lines of all project tasks. |
| Navigate area | |
| Project plan lines | Displays the project plan lines of all project tasks. |
| Project plan lines Dispo | Displays the project plan lines of all project tasks, filtered to the line type "Budget" and "Budget and billable" of the project plan line. |
| Project plan lines Sales | Displays the project plan lines of all project tasks, filtered by the line type "Billable" and "Budget and billable" of the project plan line. |
| Project plan lines Purchasing | Displays the project plan lines of all project tasks, filtered to the "Budget" line type of the project plan line. |
| Actions area - Copy | |
| Insert outline structure | This function inserts a new outline structure at the end of the structure details. Note The function has been discontinued and is no longer available with version BC 2026 Wave 1. |
| Insert outline structure to bookable | This function inserts an outline structure up to and including the first bookable outline structure. Note The function has been discontinued and is no longer available with version BC 2026 Wave 1. |
| Area Belonging | |
| Shipping unit | Opens the shipping units. |
| Cross-country articles overview | Opens the cross-country skiing article overview. See cross-country skiing articles overview. |
| Tasks | Opens the overview of tasks (task list). |
| Postponed activities | Shows an overview of the activities on hold. |
| Project team | Opens the overview of the project teams. See project team. |
| Create project location | This function create a project location based on the settings. The project location represents the place of performance of the project. |
| Risk management | Opens the risk management lines. See Risk Management. |
| Inventory overview | Opens the stock overview with filtering to the storage location of the project. |
| Time sheets | Opens the working time items filtered to the respective project. |
| Activity log | Opens the activity items filtered to the respective project. |
| Project Forecast | Opens the project forecast items filtered to the respective project. |
| Commitment items | Opens the commitment items filtered to the respective project. |
Project task#
The project tasks that are/will be planned in the project are first defined on the "Tasks" information tab of the project card. This is where the "rough planning" for the project takes place for the first time.
KUMAVISION factory365 extends the project tasks of Microsoft Dynamics 365 Business Central1 with the fields and functions described below:
| Field | Description |
|---|---|
| Type of service | In this field, assign the activity type for the project task in the case of an account. You use the activity type to influence project account determination and have the option of influencing the maintenance of the project plan lines. See activity type. |
| Status | Indicates the current status of the project. The following options are available: - Planning - Offer - Open (order) - Completed These are pre-assigned from the project (header) and can be changed at project task (level). The status of the project task is inherited by the project plan lines. Note: A change to the project task status "Open" requires that the project status is "Open". When the project status is changed, all project tasks with the same initial status are changed to the new status of the project (header). If the status in the project is set to "Completed", the status of all project tasks is also set to "Completed". |
| Cross-country articles | A project task is identified as a task for cross-country items by the "cross-country item" label. See cross-country items. |
| Project task for forecast | This field enables account assignment of the forecast items to a project task with the type: "Posting". This allows forecast values to be entered on global totals lines and differentiated later. |
| Forecast cost price | See Forest post table. |
| Forecast sales amount | See forecast item table. |
| Remaining order amount | See remaining order amount (order commitment) |
| Stock cost amount (expected) | See warehouse cost amount (expected) (warehouse commitment) |
| Stock cost amount (actual) | See warehouse cost amount (actual) (warehouse commitment) |
| Production Cost amount (expected) | See production Cost amount (expected) (production commitment at target costs) |
| Production Cost amount (actual) | See production cost price (actual) (production commitment at actual cost) |
| Assembly Cost price (expected) | See assembly Cost amount (expected). |
| Working time Cost price (expected) | See working time commitment. |
| Total exposure | Sum of the above individual exposure values grouped according to the respective exposure type with drill-down to the exposure items. |
| Number of previous tasks | Shows the number of predecessors of the current project task(s), as several predecessors can be defined for a project task in order to organize the project tasks chronologically. Note: The predecessors/successors are displayed in the "Project task dependencies" info box. |
| Number of subsequent tasks | Displays the number of successors of the current project task(s), as several successors can be defined for a project task in order to organize the project tasks chronologically. Note: The predecessors/successors are displayed in the "Project task dependencies" info box. |
| Planned start date | Indicates the planned start of the project task and represents a target for the detailed planning in the planning lines. The field can be calculated using the "Project scheduling" function. See "Project scheduling". |
| Planned end date | Indicates the planned completion date of the project task and represents a target for the detailed planning in the planning lines. The field can be calculated using the "Project scheduling" function. See "Project scheduling". |
| Duration | Duration of the planned activity of a project task. |
| "Fixed" milestone | Indicates the "Planned end date" of the project task as a milestone (fixed point). |
| Statistics area | |
| Initial commissioning Amount (MW) | Represents the sales amount of the initial order. Filtering the project plan lines according to the order type: "Initial order". |
| Follow-up order(s) Amount (MW) | Represents the sales amount of the follow-up order. Filtering the project plan lines according to the order type: "Follow-up order" |
| Deviation(s) Amount (MW) | Filtering the project plan lines according to the order type: "Deviation" Allow synchronization from VK Only the marked project tasks can be selected / linked in the sales document. |
| Default line type | When linking from a sales document, project plan lines of the default line type ("Budget and billable" or "Billable") are automatically created. |
| Task | Description will follow shortly. |
| Tasks Status | Description will follow shortly. |
Functions in the ribbon#
| Field | Description |
|---|---|
| Set Project Location | The function checks whether a project location exists and transfers it to the current task. If there are several locations, a selection page opens. |
| Project task statistics | Displays the project task statistics by resource, article, G/L account and total. |
| Project task card | Opens the project task card. |
| Project chart of accounts | Opens the project chart of accounts. |
| Project charts of accounts | Opens the project chart of accounts. See Project chart of accounts and Project account setup. |
| Engaging/disengaging | The "Move in/out project tasks" function only works with a defined task structure in the project card and project task type account. You can call up the "Indent/outdent" functions via the "Tasks" info tab using the "Line" menu selection. Indent When the "Indent" function is called up, the current line is indented one level down and bracketed by a from-total and a to-total line. The description of the indented line is assigned to the from/to total line. The new project task receives the description from the default. The plan lines already entered are also assigned to the new line. Outdent When the Outdent function is called up, 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 area is used. If it is the last position, the task block is deleted and the task number is assigned to the "from total". |
| Create Project Location | The function creates a project location depending on the setup. The project storage location represents the place of performance of the project task. |
| Register forecast item project | See Forecast registration. |
| Task numbering | Task determination is based on the outline structure and depends on the current item and project task type of the line. If a line is inserted between existing items, the system inserts a continuation line for the top line. If a line is inserted at the bottom, the next project task number is inserted based on the top line. |
| Tasks | Opens the overview of tasks (task list). |
| Create tasks | You can use "Create tasks" to 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 have selected. You can create the tasks in the project area via "Tasks" in the project card, project tasks and from the project team. Note: Please note that the creation of an Outlook task is only possible with the corresponding setup. Further information on the connection / setup can be found in the Microsoft Dynamics 365 Business Central1 online help. Note The plan lines can only be changed via the CRM task (contact tasks). In the "Projects setup", use the "CRM task increment", "CRM task separator" and "CRM task counter" fields to define how the project task number is created. Further information can be found here. Alternatively, you also have the option of creating a task directly from a contact card by entering a project number. |
| Create sales offer | You can create a sales quotation directly from the project using the project plan lines. See sales offer. |
| Create sales order | If the customer has already commissioned the project, you can also create a sales order directly from the project via the project plan lines. See sales order. |
| Display sales documents | Displays a sales document linked to the project. |
| Receipts | Displays an overview of the documents associated with the project. |
| Postponed activities | Displays an overview of the activities on hold. |
| Activity log items | Opens the activity items filtered to the respective project. |
| Project forecast items | Opens the project forecast items filtered to the respective project. |
| Overview of requirements | Opens the requirements overview. |
| Cross-country articles overview | The "Long-running item overview" is used to display the links of the available quantities to the long-running item project plan lines for the FA components. See Long-running items. |
Project plan lines#
KUMAVISION factory365 extends the project plan lines of Microsoft Dynamics 365 Business Central1 with the fields described below:
| Field | Description |
|---|---|
| Type of assignment | Initial order When the first sales order is created, the order type is set to initial order. Follow-up order When a follow-up order is created, the order type is set to follow-up order. Deviation When maintaining the forecast, the project plan lines created during the forecast release (archiving) are marked as a deviation. Plan line Initial value when creating a new plan line. |
| Duration | Represents the duration in days, calculated from the start date/planning date. |
| Start date | Represents the start date of the project plan line. Note: The start and planning date is pre-assigned from the project task. |
| Planned delivery date | Specifies the planned delivery date of the item linked to the project planning line. For a resource, the planned delivery date is the date on which the resource is used for the project. |
| Cross-country articles | If the "Long-running item" indicator is active for the project task to which the project plan line belongs, the items of the "Item" type are automatically assigned the "Long-running item" indicator. See Cross-country items. |
| Long-running article Linked quantity (basis) | Shows the linked quantity (base) and links to the cross-country item link items. See Handling of cross-country article links. |
| Article Version code | If you are working with article versions, define the article version for procurement here. |
| Stock transfer from storage location code | Is taken from the "Invoice and shipping" information tab if the procurement method in the planning line is set to "Stock transfer". |
| Reserved by | Displays the document reserved for the project plan line. |
| Vendor no. | For the rapid procurement of your project requirements, the option has been created to transfer items directly from the project plan lines to the planning proposal, inquiry, order, invoice and credit note. Use this field to specify the vendor from whom you would like to procure this item. |
| Type of service | This field shows you the transferred activity type from the project task. See activity type. |
| Sales account no. | You will see the sales account determined by the system in this field. |
| Consumption contr. | 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 this is different; if a stock data card already exists, it is updated based on the specification. With the "Simulation" procurement method, a costing production order is created in the background. If you want to trigger a purchase order for the item, set the procurement method to "Purchasing" and the inventory data for the item and storage location will be updated. |
| Sales document Document type | Specifies the document type of the sales document. |
| Sales document no. | Specifies the sales document number of the sales document. |
Functions in the ribbon#
| Function | Description |
|---|---|
| Create sales offer | You can create a sales quotation directly from the project using the project plan lines. See Project - Sales offer |
| Create sales order | If the customer has already commissioned the project, you can also create a sales order directly from the project via the project plan lines. See Project - Sales order |
| Create sales complaint | If a customer complains about the delivered goods, the complaints process can be started from within the project. See Project - Complaint. |
| Create purchase request | You can use the "Create purchasing request" function to send the request to the supplier directly from the project plan line. See Project - Purchasing complaint. |
| Create order | You can use the "Create order" function to directly create a purchase order for the project plan line. See Project - Purchase order. |
| Create purchase invoice | You can use the "Create purchase invoice" function to create a purchase order directly from the project plan line. |
| Create a purchase credit note | You can use the "Create purchase credit note" function to create a purchase order directly from the project plan line. |
| Set Project Location | The function checks whether a project location exists and transfers it to the current project plan line. If there are several locations, a selection page opens. |
| Receipts | The "Project vouchers" overview shows an overview of the vouchers associated with the project. |
| Pre-text / post-text | You can describe a project plan line in detail using a long text. See Project plan line document texts. |
| Cross-country articles overview | The "Long-running item overview" is used to display the available quantities for the long-running item project plan lines for the FA components for the links. See Long-running items. |
| Create activity | You can use "Create activity" to create activities and/or communications from Microsoft Dynamics 365 Business Central1 to create activities and/or communications and store associated documents. The Microsoft Dynamics 365 Business Central1 online help provides you with further information on the topic of "Creating activities". |
| Display sales document | Displays a sales document linked to the project. |
| Display purchase receipt | Displays a purchasing document linked to the project. |
Project Gantt Viewer#
In KUMAVISION factory365, a Gantt Viewer is available to you within a project.
The functions within the Gantt Viewer are described below:
| Function | Description |
|---|---|
| Zoom (+) | Zooms into the image section of the Gantt Viewer. |
| Zoom (-) | Zooms out of the image section of the Gantt Viewer. |
| Full screen | Shows the Gantt Viewer in full-screen view. |
| Go to Today | Moves the display so that the current date is within the display. |
| Refresh | Re-imports the data from the project. |
| Expand totals rows / collapse totals rows | You can use this toggle function to expand and collapse the totals rows of the Gantt. |
| Expand plan lines / collapse plan lines | This toggle function allows you to expand and collapse the plan lines of the Gantt. |
A click on the timeline of the project task will take you directly to the associated project task card. Clicking on the timeline of the project plan line will take you to the project plan lines.
Project Document texts#
Document texts project header#
You can describe a project in detail using a long text.
To define a document text for a project, select "Pre-text" or "Post-text" in the ribbon.
The project document text card opens.
Call up the "Format Editor" via the ribbon and enter your desired text in the editor text field. After confirming your entry with "OK", your text will be displayed in the "Preview" field.
Note
Please note that pre- and post-texts on the project header and project tasks are not passed on to subsequent documents. This is only possible with texts on project plan lines.
Document texts Project tasks#
You can describe a project task in detail using a long text.
To define a document text for a task, first select the desired task line from the "Tasks" info tab.
Then select the menu item "Document text" via the "Line" menu selection on the "Tasks" info tab.
You can now decide whether you want to enter a prefix or suffix for the line.
The project document text card opens.
Call up the "Format Editor" via the ribbon and enter your desired text in the editor text field. After confirming your entry with "OK", your text will be displayed in the "Preview" field.
Note
Please note that pre- and post-texts on the project header and project tasks are not passed on to subsequent documents. This is only possible with texts on project plan lines.
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 have defined.
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 pre- and post-texts are entered in the same way as the tasks. Further information can be found in the "Task document texts" section.
The reports listed here print the project texts depending on the "Show additional text" button:
- Project plan lines
- Project analysis
- Budget comparison project
- Account proposal project
- Project offer
Cross-country items#
Long-running items can be used for long-running planning and management. Article items with a long procurement time are created as project plan lines in the project. These items can later be used as components in project-related production orders. In this way, the requirements for these long-running items are triggered directly from the project, even if a production order does not already exist or the position of the component in the production order is not 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 lead time article in the project.
Setup#
Cross-country items are set up in the project via the project tasks. Separate tasks should be created in the project for cross-country items. A project task is identified as a task for a cross-country ski item by ticking the "Cross-country ski item" box.
Note
Checking the "Cross-country item" box in a project task means that only project plan lines of the type "Item" and "Text" can be created for this project task. The lines with the type "Article" represent the cross-country items. The lines with the type "Text" can be used for groupings or notes.
If project plan lines are now entered for the project task, the items with the type "Article" are automatically assigned the "Long-running article" indicator.
Note
The transfer of project plan lines that are marked as "long-running items" to project book sheets or the posting of these lines is not permitted and is intercepted by corresponding error messages.
After creating the project plan lines for the corresponding long-running items, procurement documents / procurement processes can be triggered for these project plan lines in order to achieve corresponding requirements coverage for these long running items.
Note
The procurement documents created should always be 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-running item" 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.
Long-Dated Items Overview#
If a Long-Dated Item has been defined in the project, you can view it in the Long-Dated Items Overview within the assigned production orders of the project.
For a component to be recognised as a Long-Dated Item in the production order and the E+D Order, the following criteria must be met:
- 1:1-reservation between the production order and a project planning line must exist.
- Item Number, Variant Code and Location Code must match between the project planning line marked as a Long-Dated Item and the production order component.
The Long-Dated Items Overview can be opened for Production Order Components, E+D Order Components, as well as E+D Order Lines. It can also be shown for the Production Order, the Production Order Lines, and the E+D Order.
The Long-Dated Items Overview is also available directly from the project. It can be accessed there for individual project planning lines, project tasks, as well as for the entire project.
With the Long-Dated Items Overview, the available quantity for allocations can be viewed. The available quantity of a long-dated item is always calculated at runtime. This calculation occurs both when opening the Long-Dated Items Overview page and when executing the Recalculate function in the Long-Dated Items Overview.
In addition, the overview allows links to be created or cancelled between production order components and long-dated item project planning lines. As a result, the procurement quantity already reserved for the project planning line is transferred to the production order component, or in the event of cancellation, is returned from the production order component back to the project planning line.
The structure of the Long-Dated Items Overview, as well as the individual accesses and functions of the page, are described below.
Address of origin#
The "Called from" field at the top of the cross-country skiing article overview shows the location from which the cross-country skiing article overview was called up.
The long-running item overview can be called up for FA components and project plan lines. It can also be called up for FA lines, production orders, project tasks and the entire project.
The calls are described below and the structure of the overview items for each call is explained.
| Call | Description |
|---|---|
| FA components / E+D order lines of the MRP type "Stock item" | The "Long-running item overview" can be called up for FA components and E+D order lines of the MRP type "Stock part" using the "Long-running item overview" action. In both cases, the long run item overview is called up for the respective, referenced FA component. Here you can now view the possible, requirement-covering long-running |
| item project plan lines for the component and create or delete a link between the FA component and the project plan line. | |
| FA components / E+D order lines of the MRP type "Stock item" | The "Long-running item overview" page can be called up for FA components and E+D order lines of the MRP type "Stock part" using the "Long-running item overview" action. In both cases, the long run item overview is called up for the respective referenced FA component. Here you can now view the possible, requirement-covering long-running item project plan lines for the component and create or delete a link between the FA component and the project plan line. |
| FA lines / E+D order lines of the MRP type "Production part" | The "Long-running item overview" page can be called up for FA lines and |
| E+D order lines of the MRP type "Production part" using the "Long-running item overview" action. In both cases, the long-running item overview is called up for the referenced FA line. In this call, the MRP components of the respective MRP line that have |
|
| been identified as long run items are displayed as main items. The project plan lines are displayed as sub-items for the respective FA components, which can be used as requirement cover if necessary. If the "Set link" or "Delete link" actions are used when calling up an FA line, the displayed FA components are run through one after the other and the selected functionality is carried out for each individual FA component. |
|
| Production order / E+D order | The "Long-running item overview" page can be called up for an entire production order or an E+D order. In both cases, the long run item overview is called up for the referenced production order. 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. The project plan lines are displayed as sub-items for the respective FA |
|
| components, which can be used as requirement cover if necessary. If the "Set link" or "Delete link" actions are used when calling up the entire production order, the displayed FA components are run through one after the other and the selected functionality is carried out for each individual FA component. |
|
| Project plan line | The "Cross-country item overview" page can also be called up for a project plan line. To do this, the respective project plan line must be marked as "Cross-country item". The corresponding project plan line is displayed as the caller in the called |
| up cross-country ski item overview. 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 "Set link" or "Delete link" actions 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. This means that the individual FA components are run through one after the other and the selected action is executed for each individual component. The assignment of the long-running item therefore always takes place from the component's point of view. |
|
| Project task | The "Cross-country item overview" page can also be called up for a project task. To do this, the respective project task must be marked as a "Crosscountry item". The corresponding project task is displayed as the caller in the crosscountry item overview. The corresponding project plan lines for this task are displayed as main items in this overview, which are marked as "Cross-country items". The respective FA components that could be covered by this project plan line are then displayed as sub-items for each main item. If the "Set link" or "Delete link" actions 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. This means that the individual FA components are run through one after the other and the selected action is executed for each individual component. The assignment of the long-running item therefore always takes place from the component's point of view. |
| Project | The "Cross-country article overview" page can also be called up for an entire project. The corresponding project is displayed as the caller in the cross-country ski item overview. All project plan lines for this project that are marked as "Cross-country items" are displayed as main items in this overview. The respective FA components that could be covered by this project plan line are then displayed as sub-items for each main item. If the "Set link" or "Delete link" actions 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. This means that the individual FA components are run through one after the other and the selected action is executed for each individual component. The assignment of the long-running item therefore always takes place from the component's point of view. |
Lines Overview#
The lines of the Long-Dated Items Overview are formed based on production order components and project planning lines, and are created as main lines and sub-lines. If the Long-Dated Items Overview is accessed from a production order or E+D order, the main lines are created based on production order components. The associated sub-lines are formed based on the project planning lines, which are considered as potential demand coverers for these long-dated items. Conversely, if the Long-Dated Items Overview is accessed from a project, the main lines are formed based on project planning lines, and the sub-lines are created by the production order components, as potential demand generators.
Date Fields in the Long-Dated Items Overview#
The planning date is shown for the project planning line.
The due date is shown for the production order component.
Representation of quantities in the Long-Dated Items Overview#
The Long-Dated Items Overview is to illustrate how the required quantity for production order components can be covered by the long-dated item project planning lines that have already been considered during disposition. For this reason, the quantities of long-dated items are also represented accordingly.
| Field | Description |
|---|---|
| Available Qty. (Base) | Shows the quantity in base units that are available for this production component in the production component line. Shows in the project planning line the quantity in base units that are available for all applicable production components. |
| Required Qty. (Base) | Shows in the production component line the quantity in base units required for this production component to meet the demand. In the production component line, the quantity in base units required to meet the demand for this production component is shown. |
| Related Qty. (Base) | Shows in the production component line the quantity of base units that has already been related to this production component. Shows in the project planning line the quantity of base units that has already been related to the production order components. |
Note
If the quantity reserved for the project planning line has a date conflict, this quantity is not available and cannot be related to the production order component.
Functions in the ribbon#
In the Long-Dated Item Overview there are the following actions:
| Action | Description |
|---|---|
| Recalculate | This action is used to update the overview. By using this action, the data on the page is recalculated and shown. |
| Show Document | With this action, you can access the related project for the project plan line or the associated production order for the production component line. |
| Set Relation | With this action, links between the long-dated item project plan lines and the corresponding production order components are established. |
| Remove Relation | With this action, the links between the long-dated item project plan lines and the corresponding production order components are deleted again. |
| Set Relation (Selected Line) | With this action, a link is established between the selected production component line and the corresponding long-dated item project plan line. |
| Remove Relation (Selected Line) | This action deletes the link between the selected production component line and the corresponding long-dated item project plan line. |
| Show Entries | With this action, you can display the existing links between the project plan line and the production component for a position or item. |
Handling of Long-Dated Item Relation#
Set Relation
The relation is established for the production component line using the function Set Relation or Set Relation (Selected Line).
After the relation has been established, corresponding Long-Dated Item Relation Entries are created. These entries record which production component is linked to which project plan line and in what quantity. The relation entries can be viewed in the Long-Dated Item Overview.
In the Long-Dated Item Overview, the Related Qty. (Base) is increased in the production component line and the corresponding project plan line. Additionally, the Available Qty. (Base) and the Required Qty (Base) in the production component line and the project plan line are reduced accordingly.
By establishing the relation, the reservation is transferred from the project plan line to the production component. This results in a direct linkage between the demand-covering document (such as a purchase order) and the production component.
Additionally, in the project plan line, the Quantity is reduced by the linked amount, as there is no longer a requirement for this quantity of the long-dated item in the project plan line.
Remove Relation
The relation for the production component can be removed using the Remove Relation or Remove Relation (Selected Line) function.
By deleting the relation, the associated long-dated item relation entries are removed.
In the Long-Dated Items Overview, the Related Qty. (Base) in both the production component line and the corresponding project plan line is reduced or set to zero. Additionally, the Available Qty. (Base) and the Required Qty. (Base) in the production component line and project plan line are increased accordingly.
The reservations are transferred from the production component back to the project plan line. This means that the demand coverage is once again available to the project plan line. In addition, the Quantity in the project plan line is increased by the amount of the deleted relation.
Outsourcing 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. The recorded demand coverage (reservations) is also outsourced or reintegrated accordingly. Therefore, the long-dated item relation entries are also outsourced or reintegrated together with the separate production order.
Delete a production component
When a production component is deleted, it is not checked whether it is already a related long-dated item. If the production component is deleted, the reservations are lost. The project plan line for the long-dated item remains unchanged. If you wish to transfer the reservations back to the linked long-dated item project plan line, please first use the Remove Relation function in the Long-Dated Items Overview before deleting the production component.
When production order lines or an entire production order is deleted, it is not checked whether related production components already exist. When deleted, the reservations are lost. The project plan line for the long-dated item remains unchanged.
Reduce the quantity of production components
When reducing the quantity in a production component, it is not checked whether it is already a linked long-dated item. If the production component is deleted, the reservations are lost. The project plan line for the long-dated item remains unchanged.
Cancellation of reservation from a production component
If a production component is specified as a Long-Dated Item, manual cancellation of the reservation for this component is not possible (initiating reservation cancellation directly from the production component).
The cancellation of the reservation for a production component that is marked as a long-dated item is therefore aborted with an error message.
Cancellation of reservation from the demand cover document
If a production component is marked as a Long-Dated Item and has a reservation to the demand cover document, the reservation can be cancelled from the demand cover document. This is necessary because changes must be possible in the demand cover document, for example, if the planned delivery date cannot be met.
If a reservation is cancelled in a demand cover document that refers to a production component for a long-dated item, the project plan line of the long-dated item remains unchanged.
Note
If you want the reservations to be transferred back to the linked project plan line of the long-dated item, please first use the Remove Relation or Remove Relation (Selected Line) function in the Long-Dated Item Overview. Only after that should you delete production components, reduce the quantities of production components, or cancel reservations.
Consumption posting of a production component
After posting the consumption for a production component marked as a Long-Dated Item, the long-dated item relation is adjusted to match the reserved quantity. This is necessary because, with the consumption posting, the reserved quantity may be consumed (reservation against stock). Therefore, the long-dated item relation must also be reduced accordingly.
Change from Released to Finished
When a production order is finished, all remaining (unused) reservations for long-dated items linked to the production order are deleted. The project planning line remains unchanged. If the reservations need to be transferred back to the long-dated item project planning line, please use the Remove Relation or Remove Relation (Selected Line) function in the long-dated item overview before changing the status of the production order.
As part of the processing of project plan lines#
When processing project plan lines that are marked as "long-running items", the system must carry out corresponding checks and actions in relation to long-running item links (long-running item link items). These are described below.
Creating book sheets for long-running items 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 to prevent project plan lines for cross-country items from being posted. A project plan line for slow-moving items offers the option of generating requirements in advance for parts that are required for production and have a long procurement time. It only serves as a trigger for procurement, the actual consumption takes place as a component in the production order.
Posting long lead time items project plan lines
Posting project plan lines that are marked as "long lead time items" is not permitted. A project plan line for long lead time items offers the option of generating requirements in advance for parts that are required 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-running article project plan lines with link items
If a project plan line that is marked as a "long running article" is deleted, the long-running 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 requirement cover remains in the FA components. If it was the only long-running item project planning line for the item / variant / storage location combination, then the "long-running item" checkmark is also removed from the corresponding FA components, as there is no longer a reference to a long-running item in the project.
Project scheduling#
With the help of project scheduling, you have the option of creating a rough schedule at any point in the project. Scheduling can be defined both at project level and at project task and project plan line level. Forward, backward and midpoint scheduling is possible.
Project tasks using predecessor and successor structure#
Project tasks can be related by means of predecessors/successors. To create a predecessor/successor structure, click on the number in the "Predecessor/successor" field of the respective project task line. The "Project task dependencies" page opens on which you can assign the predecessors/successors to the project task via "New" in the "Project task dependencies" selection field.
Set project task duration#
Enter the expected duration of the respective project task in the "Duration" field. You can enter this information in the following fields:
- T = Tag(s)
- W = week(s)
- M = month(s)
- Q = Quarter(s)
- J = Year(s)
Terminate#
Using the "Project scheduling" function in the ribbon, you can calculate the planned start date and the planned end date of the project tasks based on the predecessor and successor structure and the duration of the project task.
When the function is executed, the "Project scheduling" option window opens.
| Field | Description |
|---|---|
| Termination direction | You can use the field to specify the termination direction. The following options are available: - Forward - Backward - Center point scheduling |
| Termination type | The scheduling fixed point is selected in the field. The options "Project" or "Project task" are available. If you select the "Project task" option, the additional "Scheduling task" field appears, which you can use to select the corresponding task. |
| Scheduling task | The field is visible as soon as you have selected the "Project task" option in the "Scheduling type" field. You can select the corresponding task here. |
Confirm your selection to perform the calculation.
Note
Scheduling does not shift any existing planned start or end date of project tasks with the "Milestone" indicator.
Tipp
It is a good idea to create a project template for similar projects, which you can use to transfer a project task structure, a predecessor and successor structure, as well as the project task duration to a new project. Only a fine adjustment is then made in the project. Only predecessors and successors that exist in the original project template are transferred. New relationships to existing project task lines are not taken into account.
Procedure Termination direction#
Forward scheduling
Starting from the scheduling fixed point, all project tasks are scheduled as follows:
Project task planned start date + duration = planned end date Planned end date of predecessor = planned start date of successor tasks
Backward scheduling
Starting from the scheduling fixed point, all project tasks are scheduled as follows:
Project task planned end date - Duration = planned start date Planned start date successor = planned end date of predecessor
Center point scheduling
Starting from the scheduling fixed point (only possible for project tasks), all successors are scheduled forwards and all predecessors are scheduled backwards.
Note
When scheduling on the basis of the project, the planned start date of all project tasks without predecessors is set to the project start date.
Project tasks of the From total type receive the earliest planned start date of the subordinate tasks of the Booking type as the planned start date and the latest planned end date of the subordinate tasks of the Booking type as the planned end date.
Only the self-contained predecessor and successor structure is calculated for a midpoint termination.
Project location#
For the correct presentation of the transfer of risk, goods are transferred from their production site to the construction site or to the customer and not delivered directly and thus consumed. The project is then debited upon acceptance through a deliberate consumption posting.
A project location is always created for a project. This can be a location for several projects or a location explicitly for one project.
Setup#
For each Project Type, you can specify whether you want to create a project location or use one location for several projects.
Project Location#
If you opt for the automated creation of a project location using the Project types settings, you also have the option of storing a location template in the respective project type, from which the necessary facilities for the newly created project location are pre-assigned.
- Bins,
- Inventory Posting Setup,
- Transfer Routes,
- Location
- Zones
- Warehouse Employees
Note
An event is available for project-specific extensions, which can be used to copy additional points.
It is recommended to create a location only for the templates and not to use the template location as the actual location.
Project Location for multiple projects#
If you decide against the automated creation of a project storage location, you have the option of storing an existing storage location that is to be used by default for the projects.
| Field | Description |
|---|---|
| Standard project storage location | The field is a selection list of the storage locations available in the system. It specifies the default project storage location for all projects and is automatically transferred to the "Storage location code" field on the "Invoice and shipping" info tab. |
| Standard stock transfer-from storage location | The field is a selection list of all regular storage locations (not project storage locations). It specifies the stock transfer route and is transferred to the "Stock transfer from storage location code" field on the "Invoice and shipping" info tab of the project card. |
Manual creating#
In addition to the automatic creation of a project warehouse, you also have the option of manually creating a project warehouse location for each project.
To create a project location, click on the project card in the "Related" > "Setup" > "Create project location" ribbon.
When the function is executed, a query opens where you can decide whether you want to use the number for the location from the number series from the Projects setup or assign a manual number. You also have the option of specifying whether the project location should be entered in the project header.
The details for "Name", "Name 2" and the address information are transferred from the "Delivery to address" to the new project location.
The "Create project storage location" function is also available at project task level (task > line).
Inventory data#
When creating an article item in the project plan line, if a storage location is found, a storage data card is created directly 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 stock data card via the "Procurement method" field.
If the "Stock transfer" procurement method is selected, a stock transfer route is created directly in the background for the standard warehouse in accordance with the settings in the "Projects setup".
Project team#
A project team can be defined for each project. The definition takes place on the project card in the 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 specify the type of project member. The following selection options are available to you: Resource These are usually internal and external employees. ContactThese are project members of the customer or further project participants. If "Contact" is selected, the "Company no." field is filled by the system using the customer number on the project card, from which the company name is also derived. User This is a specific user who can be selected in the "No." field. |
| No. | Here you can make a specific selection depending on the type. |
| Role Code | Specifies the role of the project team member. To assign code to the roles, the roles must first be set up in the table of the same name. See also: Project Role |
| Role | Specifies the name of the roll. |
| Start Date | Specifies the start date for the use of the resource. The start date is automatically preset with the start date of the project and can be changed manually. |
| Name | Specifies the name of the resource, contact or user. |
| Specifies the E-Mail Address of the resource, contact or user. | |
| Phone No. | Specifies the phone number of the resource, contact or user. |
| Mobile Phone No. | Specifies the Mobile Phone Number of the resource, contact or user. |
| Ending Date | Specifies the end date for the use of the resource. The end date is automatically preset with the end date of the project and can be changed manually. |
| Company No. | Specifies the company number of the contact as soon as the field Type=Contact |
| Company Name | Specifies the company name. |
| Business Relationship | Indicates the business relationship. |
| Salesperson Code | Indicates the sales person of your company. |
| Persons Contact No. | Specifies the person contact no. |
Note
If the "Responsible" and / or "Project manager" fields are maintained on the project card, the project team data records are also created with the Responsible / Project manager role.
If you maintain a resource in the project plan lines, project team data records are also generated for this.
Please note that when creating from the project plan line, the team record is not deleted when the resource is changed or the record is deleted.