| Close Project (tipcs2250m000) |  |
| Use this session to close projects whose production and financial processes have been completed. Final project results are calculated when projects are closed. Before a project is closed, ERP LN checks the current status of the project. Only projects with the status Finished can be closed. ERP LN checks that: All subprojects have the status Closed, if there is a main project. All production orders for the project are closed. All purchase orders have the status Closed. All purchase receipts have been invoiced, and the invoice matching procedure carried out in the financial accounting. All sales orders have been closed with the Process Delivered Sales Orders (tdsls4223m000) session. All service orders for the project have been processed in history. All transaction hours for the project have been processed. No project inventory is still present. The project inventory value cannot exceed the value entered by the users. Remaining inventory less than this value is automatically deleted by ERP LN. All internal invoices from the PCS project to the financial companies of the sales office, service department, and/or warehouse are sent and completed. If these conditions are not met, ERP LN does not close the project. If the project can be closed, the following steps are taken: Any current inbound and outbound advice for warehousing orders in the Inventory by Warehouse, Item and Effectivity Unit (whwmd2116s000) session is deleted. Project costs and results are calculated. To do this, ERP LN automatically starts the Calculate Cost Prices by Project (tipcs3250m000) session. The project status is changed to Closed. Note If there is a main project, all subprojects are closed first according to the previous procedure, before the main project is closed. If you select the COGS and Revenues restricted to Financial Company of PCS Project check box in the Project Control Parameters (tipcs0100m000) session, financial transactions are posted on the financial companies of the sales office, service department, and/or warehouse instead of on the financial company of the PCS project. If internal invoices are sent from the PCS project to those departments, and the internal invoices are not completed yet, the Close Project (tipcs2250m000) session sets the project status to To be Closed instead of to Closed. You must first complete the internal invoices, and then run the Close Project (tipcs2250m000) session again to set the project status to Closed. Performance aspects The settings in this session could affect system performance and database growth. For more information, refer to Delete and archive in Project Control . Related topics Financial integrations - overview COGS and revenue postings for PCS projects in a multisite environment
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.
Delete Project Inventory up to Value | The currency in which the maximum project inventory amount is expressed. If this amount is greater than the value of the inventory, the inventory will be deleted.
Delete Inventory up to Value | Enter the maximum project inventory amount, up to which any project inventory on hand may be automatically deleted from ERP LN.
Reason for Adjustment Orders | When an order is adjusted, you use a reason code to indicate why this was done.
Overrule Posting Date for Project Related Transactions | If this check box is selected, and a date is present in the Posting Date Cost/Turnover Sales field, then the Posting Date Cost/Turnover Sales can be used as the transaction date for the following integration transactions that are created during closing of the PCS project: Project (PCS) / Project Surcharges Project (PCS) / Cost of Goods Sold (General) Project (PCS) / General Results However, the previously mentioned integration transactions only use the Posting Date Cost/Turnover Sales in the Close Project (tipcs2250m000) session if for the involved PCS project the Post Project Transactions on Current Date check box in the Project Details (tipcs2130m000) session is cleared. In that case, the Close Project (tipcs2250m000) session overwrites the Posting Date Cost/Turnover Sales in the Project Details (tipcs2130m000) session during PCS project closure. If this check box is cleared, the transaction date of the previously mentioned integration transactions equals the Posting Date Cost/Turnover Sales in the Project Details (tipcs2130m000) session, if the Posting Date Cost/Turnover Sales is present. If the Posting Date Cost/Turnover Sales is not present in the Project Details (tipcs2130m000) session, the transaction date equals the moment that you started the Close Project (tipcs2250m000) session. Note If the previously mentioned integration transactions are created by the Calculate Cost Prices by Project (tipcs3250m000) session before the PCS project is closed, the transaction date is the Posting Date Cost/Turnover Sales in the Project Details (tipcs2130m000) session. This date can be overwritten by the Close Project (tipcs2250m000) session.
Posting Date Cost/Turnover Sales | The date entered in the Posting Date Cost/Turnover Sales field for projects which are to be closed and for which the Overrule Posting Date for Project Related Transactions field is Yes.
Commands | Description
Continue | Executes the process that you set up in this session.