| Projects (tipcs2101m000) |  |
| Use this session to create, maintain and/or list projects. In the details session, you can create and maintain projects that are used to calculate, plan and perform logistic activities that are directly related to customer orders. You can only delete a project if: The project has the Free status. It is not linked to a sales quotation or a sales order. Note If you have started this session by zooming, you can only find and select a record.
Fields | Description
Project | A collection of manufacturing and purchasing actions that are performed especially for a particular customer order. A project is initiated by a customer order for items having a To Order order policy. The purpose of a project is to plan and coordinate the production of these items. For a standard-to-order production, the project is only used to link the item with the customer order. Otherwise, a project can include: Customized item data (BOMs and routings) Project planning (activity planning) A budget is a special type of project. A budget is used to plan and estimate, not to carry out production. Related topics Project types
Project Status | Indicates the current progress of the project. The following status values are available: Allowed values Possible values
Description | An additional field for the project description if the project description does not fit on a single line.
Reference | Displays the reference data of the project. This field is only used for providing information. You can determine the reference data to enter, for instance, the number of a customer's sales order. This field enables you to quickly search for project data using an argument other than the project code.
Search Key | An alternative form of a description used for convenience during searching. Typically, it is an abbreviation, an acronym, or a mnemonic alternative to a full description. Related topics To use search keys
Project Type | Project types
Calculation Group | A code representing a group of projects the user wants to compare financially. You can assign a calculation group to: A budget A main project (as long as the calculation group is not assigned to another project or single project) A single project (as long as the calculation group is not assigned to another main project or single project) In case of a budget, you must always enter a calculation group. If you copy the budget to a main project or a single project, the calculation group is automatically copied so that the project's calculation group equals the budget's calculation group. It is not allowed to overwrite the project's calculation group with a calculation group that is in use with any other project. Also if you copy a budget to a new project, and the calculation code is already in use in another project, the budget's calculation code is not copied to the new project. For subprojects, the calculation group must be the same as the main project's calculation group. If the sub project is linked to the main project, the calculation group is automatically copied from the main project to the sub project.
Sold-to Business Partner | The business partner for whom the project is carried out.
Project Employee | The person who is in charge of the execution of the project.
First Free Item Code | The first item code which is used as a default value for the input of new customized items. Related topics To use number groups and series
Price Calculation Code | A specification of how a cost price, valuation price, or sales price is calculated. The code stores specific cost calculation data. The price calculation code that is defined in the Cost Price Calculation (CPR) Parameters determines the standard cost price. Other price calculation codes are used for simulation purposes. The price calculation code for customized items is stored by project. Example Specific operation rates Subcontracting rates Simulated purchase prices Surcharges
Calculation Office | By default, ERP LN displays the calculation office of the number group. If necessary, you can fill in a different calculation office.
Engineering Allowed | If this check box is cleared, all end items of the project are standard-to-order items. No customized BOM or routing can therefore be maintained. As soon as a customized item is added to the project, ERP LN automatically selects this check box. If this check box is cleared, the following PCS functionalities do not apply: Customized item data (BOMs and Routings). Project Planning. Project structures (main/sub projects). Activities. Network planning. Module planning. General costs. Service orders are not allowed on the project. Project surcharges. Cost calculation at project level. Note Projects for which the Engineering Allowed check box is not selected in the Projects (tipcs2101m000) session, cannot be copied.
Reference Date | The date on which the bill of material and the routing operations are exploded when a customized product structure is generated with either the Generate (Project) Structure for Sales Orders (tdsls4244m000) session or the Generate (Project) Structure for Product Variant (tipcs2220m000) session. The Reference Date is used as a default for the Reference date field in the Generate (Project) Structure for Product Variant (tipcs2220m000) session. If you generate a project using the Generate (Project) Structure for Sales Orders (tdsls4244m000) session, the Reference Date field is filled according to the setting of the Configuration Date (PCS) field in the Sales Parameters (tdsls0100s000) session. The following settings are possible: Order Date System Date Delivery Date If the Configuration Date (PCS) field in the Sales Parameters (tdsls0100s000) session is System Date, the Reference Date field is empty after generating a project structure. The Reference Date field is also used in cost-price calculation of the project, and when transferring RRP orders. Note This reference date in Project Control overrules reference dates entered in Product Configuration or Sales Control.
Text | If this check box is selected, additional project text is available.