Tags
1.1 Introduction
In Baan IV the Project PCS costing logic is different compared with the costing logic in SSA ERP 6.1 LN. As a result the PCS Work in Process in Baan IV is different as the PCS Work in Process in SSA ERP 6.1 LN.
In SSA ERP 6.1 LN each item, so also customized items, will have an inventory valuation method per warehouse. In Baan IV only standard items do have an inventory valuation method. In Baan IV the whole PCS Project is considered as an entity for the mechanism of creating PCS / Cost of Goods Sold integration transactions.
In SSA ERP 6.1 LN several processes can make Cost of Goods Sold integration transactions. These processes are for example; Central Invoicing for Sales, Central Invoicing for Service and Central Invoicing for Warehousing and even a PCS Project itself can create its “own” PCS / Cost of Goods Sold” integration transactions.
This makes the process of migration complex because individual transactions can’t be migrated on a one to one basis. Each ERP system has its own different accounting rules.
This document will describe how the migration software and the standard software will take care of the different costing concepts for migrated Baan IV PCS Projects.
This document is still under construction (GdG) and discussion.
1.2 Feedback
Please send your feedback, related to this document to: Gert.de.Groot@infor.com with subject “Feedback Migration PCS / WIP from Baan IV into SSA ERP 6.1 LN”.
1.3 Definitions, acronyms and abbreviations
Definitions, acronyms and abbreviations used in the document are listed in alphabetic
Order.
Term |
Description |
b4 |
ERP system Baan IV |
BOM |
Bill of Material |
FIFO |
First in First Out (inventory valuation method) |
FTP |
Fixed Transfer Price (inventory valuation method) |
MAUC |
Moving Average Unit Cost (inventory valuation method) |
LIFO |
Last in First Out (inventory valuation method) |
LN |
ERP system SSA ERP 6.1 LN |
PCS |
Project Control System, module within the Package Manufacturing |
SFC |
Shop Floor Control |
ticst300 |
Table “WIP and Inventory Transactions (SFC)” in SSA ERP 6.1 LN |
tipcs300 |
Table “PCS WIP and Inventory Transactions” in SSA ERP 6.1 LN |
tfgld410 |
Table “Integration Transactions” in Baan IV |
tgld482 |
Table “Integration Transactions in SSA ERP 6.1 LN |
tisfc001 |
Table “Production Orders” |
WIP |
Work in Process |
Figure 1.1 Definitions, Acronyms and Abbreviations
2.1 End situation in Baan IV before migrating to SSA ERP 6.1 LN
In Baan IV all costs are considered as PCS / Work in Process. At an SFC production order, related to a PCS Project, costs have been made, because 10 pieces of a specific standard item (component) have been issued. This has brought 100 € as material costs in the PCS Project, see the step 1 in the figure 2.1 on the next page.
We also have booked general hours on the PCS Project of 50 €, see the step 2 in the figure 2.1; because a project manager did some “general” work for the PCS Project.
It is important to see that we have two categories of costs:
- Cost related to an Item.
- Costs related to the PCS Project.
At the SFC order we have reported 10 pieces of the main item into inventory. From Logistical point of view we can consider this as inventory but from Finance point of view this is Project Work in Process. In Baan IV customized items do not have an inventory valuation method. All costs are directly considered as PCS / Work in Process.
From the 10 pieces main item only 3 pieces are shipped and invoiced to the customer. The other 7 pieces are in the warehouse at moment of migration and they are still in the PCS WIP from Finance point of view. All the items are sold and invoiced for the same amount, 25 € each.
Session “Calculate Cost Prices by Project” (tipcs3250m000) has created an integration transaction “PCS / Actual Cost of Goods Sold” (steps 3 + 4). Based on the mechanism:
(*) Realized Revenue PCS / Actual Cost of Goods Sold = ———————– * Actual Costs on the Project Expected Revenue
|
Note (*):
- The above mechanism will only apply when the flag “Book Item Cost Price Sales” (tipcs021.bcbi) is “No” and the actual costs per cost price component are higher as the estimated costs per cost price component at level of PCS Project.
- In other scenario’s more complex algorithms are applicable.
- This scenario is most common and it will demonstrate the logic.
Based on the above example the integration transactions “PCS / Actual Cost of Goods Sold” are created for 0.30 x 150 = 45 €. Instead of making one booking, several bookings will be created per cost component.
With this example the impact is expressed on the ledger accounts in Finance.
In this example the involved customized item has an estimated cost price of 12 € and an actual cost price of 10 €.
A customized manufactured item will only get an actual cost price in case the related SFC order has been closed and the session “Calculate Cost Prices by Project” (tipcs3250m000) has been executed.
The “End” PCS / WIP of this PCS Project is 105 € on the ledger accounts in Finance. This is the PCS / WIP at the moment of migration, so this must also be the start situation in the new ERP system; SSA ERP 6.1 LN.
2.2 Start situation and continuation in SSA ERP 6.1 LN
The PCS Project from the previous chapter will be continued in SSA ERP 6.1 LN. In SSA ERP 6.1 LN no new costs will be created. The “other” 7 pieces will be shipped and invoiced and the PCS Project will be closed.
The migration software will insert “dummy” records in table “PCS WIP and Inventory Transactions” (tipcs300). Dummy records represent the things which have happened in Baan IV. The dummy records have the value “Yes” in the field “Migrated from Baan IV” (tipcs300.mib4). These “dummy” records are only in the table “PCS WIP and Inventory Transactions” (tipcs300) and not in any other related table.
Dummy “Purchase / Receipt” transactions are migrated from table “Cost Prices by Project” (tipcs360) from Baan IV, for a total amount of 150 €. The dummy “Purchase Receipt” records reflect a total value of the costs at the aggregated level of cost component. The dummy “Purchase / Receipt” is not referring to any purchase order.
This amount is directly corrected with a dummy “Purchase / Receipt” record for non-item related costs of 50 €. This because non-item related costs are inserted as for example dummy “Project (PCS) / General Hours” of 50 €, based on data in table “Integration Transactions” (tfgld410) from Baan IV. So we have a start situation in SSA ERP 6.1 LN equal as the end situation from Baan IV, with respect to the “Actual Costs”. See the steps 1, 2 and 3 in the figure 2.2 on the next page.
In Baan IV the “Actual Costs” from a PCS Project from session “Display Cost Price by Project” (tipcs3560m000) could be traced by its original transaction in session “Display Integration Transactions by Project / Order” (tfgld4510m000). In the start situation of SSA ERP 6.1 LN we only have the costs at an aggregated level coming from Baan IV from table “Cost Prices by Project” (tipcs360). In SSA ERP 6.1 LN we can not trace back to individual transactions for the migrated costs.
The migration software will also insert the integration transactions Project (PCS) / Cost of Goods Sold from Baan IV. The Project (PCS) / Cost of Goods Sold are migrated from the table “Integration Transactions” (tfgld410). See the step 4 in the figure 2.2 on the next page.
At this moment in time, directly after the migration we have an exact match between the PCS / WIP in Baan IV (end-situation) and the PCS / WIP in SSA ERP 6.1 LN (start-situation).
Directly session “Calculate Cost Prices by Project” (tipcs3250m000) will create an integration transaction “Project (PCS) / Cost of Goods Sold of -30 €, without that anything has happened in the new SSA ERP 6.1 LN ERP system. This because with the session “Calculate Cost Prices by Project” (tipcs3250m000) a calculation is made what should be booked (15 €) compared what already has been booked (45 €). The difference is booked (-30 €), which will come into the Finance Package via the “normal” way of integration transactions. See the step 5 in the figure 2.2 on the next page.
The 7 pieces of inventory will be shipped and invoiced and they will leave the PCS Project as an integration transaction “Warehouse Issue / Issue” (step 6a) and “Sales Order / Issue” (6b).
The invoicing process will create the integration transaction “Sales Order / Cost of Goods Sold” for 7 multiplied with an Estimated Cost Price of 12 €, which is 84 € in total (step 7).
The PCS Project is closed. In the background automatically the sub process “Calculate Cost Prices by Project” (tipcs3250m000) is started in order to book the remaining “Project (PCS) / Cost of Goods Sold” transactions (step 8).
The above figure 2.2 is drawn based on the records in table tipcs300 and not based on the records in Finance. The figure 2.2 will show the end situation in Baan IV and the continuation in SSA ERP 6.1 LN.
It is important to see that the PCS / WIP can’t be good from Logistic point of view, although the PCS Project has the status closed.
The PCS / WIP = 150 – (84 -30 + 35 + 45) = 16 from table tipcs300 point of view.
The PCS / WIP can only be printed with the session “Print Project Work in Process” in the view “By Project / Order” (tipcs3480m000), because it handles a migrated PCS Project. This is also in line with the migration document guide.
2.3 Problem in Finance on Ledger Accounts
Finance has started with an opening balance of 105 € in PCS / Work in Process which is directly migrated from the Project Work in Process from Baan IV.
Immediately an integration transaction “Project (PCS) / Cost of Goods Sold” of -30 € will come in from the process “Calculate Cost Prices by Project” (tipcs3250m000).
Further in the process an integration transaction “Sales Order / Cost of Goods Sold” of 84 € will come in via the integration transactions when the 7 pieces are invoiced.
A second integration transaction “Project (PCS) / Cost of Goods Sold” of 35 € will come in when the session “Calculate Cost Prices by Project” (tipcs3250m000) is started after the 7 pieces have been invoiced or when it is started as sub process during Project closure.
This will bring the PCS / WIP on Ledger Account level at 105 – (-30 + 84 + 35) = 16 € equal as the value in Logistics but not equal as zero, which should have been the case because the PCS Project is closed.
Problem
- The “PCS / Actual Cost of Goods Sold” booking of 30 € from Baan IV (item related) should not have been taken into account by the session “Calculate Cost Prices by Project” (tipcs3250m000) in SSA ERP 6.1 LN. We can however not distinguish from Baan IV in item and non-item related Project / Cost of Goods Sold bookings, because all is created on the level of PCS Project per cost component.
- In SSA ERP 6.1 LN the customized items will leave the PCS Project for and Fixed Transfer Price (FTP) of 12 €. In Baan IV the Actual Cost Price for the item was 10 €. The difference multiplied with 7 will be 14 €.
- The difference between 30 € and 14 € is the 16 €, which is left in the PCS / WIP.
2.4 Example of a PCS Project total executed in Baan IV
In the previous chapter an example has been given of a PCS Project started in Baan IV and continued in SSA ERP 6.1 LN. This paragraph will demonstrate the flow as if the PCS Project would have been started and finished totally in Baan IV. This is done because it will give insight in the complexity of the migration process.
In the below text often the remark is made “no integration transaction is created”. This is done in order to show the difference as when the PCS Project would have been started and finished within SSA ERP 6.1 LN, which is demonstrated in the next paragraph.
The numbers in the steps will be a reflection of the numbers in the T-accounts drawn in the figure 2.4 on the next page.
Step 1(a + b)
Standard components, 10 pieces, have been issued for the SFC order. The material is needed in order to make the main item. The integration transactions are “Production Order (SFC) / Inventory Transfer” (1a) and “Production Order (SFC) / Material Costs” (1b). The standard component has a fixed transfer price of 10 €.
The production order has been reported completely, which resulted in no integration transaction.
The main item has been received in the warehouse which resulted in no integration transaction.
The production order has been closed and no integration transactions are created.
Step 2
General costs are booked on the PCS Project; this will result in the integration transaction “Project (PCS) / General Costs”.
The main item is shipped to the customer, no integration transactions are created.
The sales order line is invoiced to the customer, no integration transactions are created on the involved PCS Project.
Step 3
The session “Process Delivered Sales Order” (tdsls4223m000) is executed; no “Cost of Goods Sold” integration transactions are created. Only a “Sales / Revenue” integration transaction is created. This integration transaction is however an input signal for the session “Calculate Cost Prices by Project” (tipcs3250m000) that it is allowed to make integration transactions “Project (PCS) / Actual Cost of Goods Sold”.
The session “Calculate Cost Prices by Project” (tipcs3250m000) is executed which will result in an integration booking “Project (PCS) / Actual Cost of Goods Sold”.
The other 7 main items are shipped and invoiced to the customer, no integration transactions are created.
Step 4
The PCS project is closed. This will result in the integration booking “Project (PCS) / Actual Cost of Goods Sold”.
The PCS project is closed and the PCS / WIP has a value of zero €, which is good.
2.5 Example of a PCS Project total executed in SSA ERP 6.1 LN
In the previous paragraphs an example has been given of a PCS Project started in Baan IV and continued in SSA ERP 6.1 LN. This paragraph will demonstrate the flow as if the PCS Project would have been started and finished totally within SSA ERP 6.1 LN.
The numbers in the steps will be a reflection of the numbers in the T-accounts draws in the figure 2.6.
Step 1(a + b)
Standard components, 10 pieces, have been issued for the SFC order. The material is needed in order to make the main item. The integration transactions are “Warehouse Issue / Issue” (1a) and “Production Order / Issue” (1b). The component has a fixed transfer price of 10 €.
Step 2
The production has been reported completely, which resulted in the integration transaction “Production Order / Completion”.
Step 3
The main item has been received in the warehouse for a fixed transfer price of 120 €. Although the costs for the item are only 100 €, the warehouse has no other possibilities to receive it for 120 €. Integration bookings are “Production Order / Receipt” (3b) and “Warehouse Receipt / Receipt” (3b).
Step 4
The SFC order will be closed. An integration booking “Production Order / Additional Calculation Office Variance” is generated as an indication of the efficiency of the production process.
Step 5
The interim variance from step 4 is processed by warehousing. The inventory needs to be adjusted by a “Warehouse Receipt / Variance Adjustment” (5a). The inventory can’t be adjusted because the inventory valuation method is FTP. As a result of this directly an integration transaction “Warehouse Receipt / FTP Result” (5b) is created.
Step 6
General costs are booked on the PCS Project; this will result in the integration transaction “Project (PCS) / General Costs”.
Step 7
The main item is shipped to the customer. Only 3 pieces are shipped to the customer. The inventory value of 1 piece is 12 €. Two integration bookings are created “Warehouse Issue / Issue” (7a) and “Sales Order / Issue” (7b).
Step 8
The sales order line is invoiced to the customer, which will result in the integration transaction “Sales Order / Cost of Goods Sold” (8). At the same moment also the integration transaction “Sales Order / Revenue Analysis” is created but this has no direct influence on the PCS / WIP, so it is not drawn in the figure 2.6.
Step 9
The session “Calculate Cost Prices by Project” (tipcs3250m000) is executed which will result in an integration booking “Project (PCS) / Cost of Goods Sold”.
Step 10
The other 7 main items are shipped to the customer. Two integration bookings are created “Warehouse Issue / Issue” (10a) and “Sales Order / Issue” (10b).
Step 11
The sales order line is invoiced to the customer, which will result in the integration transaction “Sales Order / Cost of Goods Sold”. At the same moment also the integration transaction “Sales Order / Revenue Analysis” is created but this has no direct influence on the PCS / WIP, so it is not drawn in the figure 2.6.
Step 12 + Step 13
The PCS project is closed. This will result in the integration booking “Project (PCS) / Cost of Goods Sold” (12) but it will also result in the integration booking “Project (PCS) / Additional Cost of Goods Sold” (13).
The session “PCS financial Transactions by Project” (tipcs3500m001) can demonstrate all the involved integration transactions.
All the integration transactions are also drawn in T-account in order to show the behaviour within Finance on ledger accounts. The PCS / WIP will show an amount of zero €, which is good.
3.1 Start situation SSA ERP 6.1 LN equal as end situation in Baan IV
In order to have a solution direction which is approved by all internal departments but which is also approved by external auditors the end situation in the Baan IV should be equal to the start situation in SSA ERP 6.1 LN.
The PCS / WIP on the report “Project Work in Process” of session “Print Financial Project Transactions” (tipcs8410m000) in Baan IV should be equal to the PCS / WIP printed with the session “Print Project WIP” (tipcs3480m000) in the view “By Project / Order”.
In order to get in such a situation all individual transactions need to be migrated.
3.2 Data model in SSA ERP 6.1 LN
All PCS Projects have a record in the table “Project Details” (tipcs030). In the table definition we have the field “Migrated from Baan IV” (tipcs030.mib4).
Figure 3.1 Migrated from Baan IV (tipcs030.mib4) in table tipcs030
For migrated PCS Projects this has the value “Yes”. For new created PCS Projects in SSA ERP 6.1 LN this has the value “No”.
All events on a PCS Project which will have influence the PCS / WIP are logged in the table “PCS WIP and Inventory Transactions” (tipcs300). This table is used for PCS costing and this is more or less an equivalent of the table “Integration Transactions” (tfgld482).
Within the table definition of the table “PCS WIP and Inventory Transactions” we also have the field “Migrated from Baan IV” (tipcs300.mib4).
Figure 3.2 Migrated from Baan IV (tipcs300.mib4) in table tipcs300
When an integration transaction was created in Baan IV and migrated to SSA ERP 6.1 LN then the field “Migrated from Baan IV” (tipcs300.mib4) has the value “Yes”. This also applies for Dummy “Purchase / Receipt” records, which are created during the migration process.
All new events in SSA ERP 6.1 LN and which have an influence on the PCS / WIP are logged also in table “PCS WIP and Inventory Transactions” (tipcs300) but they have the field “Migrated from Baan IV” on “No”.
So at transaction level we can distinguish in which ERP system it was created.
3.3 Standard Software for PCS Project which are not closed
With the current data model we should be able to solve the problem mentioned in the previous paragraphs.
Session “Calculate Cost Prices by Project” (tipcs3250m000) must be modified in such a way that when this session is started for a migrated PCS Project the integration transactions “Project (PCS) / Cost of Goods Sold” and “Migrated from Baan IV is Yes” will be skipped. They should be skipped for PCS Projects with the status not equal to closed or archived.
In Baan IV we did have other accounting rules for PCS / WIP as in SSA ERP 6.1 LN. An integration transaction “Project (PCS) / Cost of Goods Sold” was created for the whole PCS Project. The integration transactions where created at the level of cost component. The integration transactions themselves will not tell whether they are related to item related costs or to non-item related costs.
Besides the PCS Projects can have many different parameter settings which will influence the moment of creating the “Project (PCS) / Cost of Goods Sold” integration transaction and the parameters will influence the amount in the integration transactions.
In most of the PCS Projects the item related costs will be higher as the non-item related costs both in Baan IV as in SSA ERP 6.1 LN. In SSA ERP 6.1 LN the integration transaction “Project (PCS) / Cost of Goods Sold” will only cover the non-item related costs. The item related costs will leave the PCS project with bookings like “Sales Order / Cost of Goods Sold”.
Based on this it will be “fair” to skip the integration transactions “Project (PCS) / Cost of Goods Sold” and “Migrated from Baan IV is yes” when the PCS Project does not have the status closed.
3.4 Standard Software for PCS Project which are being closed
During the closure of a PCS Project basically the normal flow should be followed but before the PCS project status is set to “closed” and additional check should be done for migrated PCS Projects only.
For migrated PCS Projects the Total Actual Project Costs (tipcs360) should be compared with all the outgoing values (basically Cost of Goods Sold transactions). In case they both are not equal an additional “Project (PCS) / Cost of Goods Sold” should be created (MIG-DELTA) in order to bring the PCS / WIP into balance. This MIG-DELTA transaction has also the flag “Migrated from Baan IV” (ticst300.mib4) at Yes although it has been created with software in SSA ERP 6.1 LN.
The words of the paragraphs 3.3 and 3.4 are drawn in the figure 3.3 of the next page.
Figure 3.3 Modify the standard software
3.5 Incoming and Outgoing Integration Transactions
All the incoming integration transactions which will bring costs into the PCS Project are logged in the table “PCS WIP and Inventory Transactions” (tipcs300). Session “Calculate Cost Prices by Project” (tipcs3250m000) will aggregate them on the level of cost component to the table “Cost Prices by Project” (tipcs360).
The outgoing transactions which will decrease the PCS / WIP are also stored in the table “PCS WIP and Inventory Transactions” (tipcs300). The outgoing transactions can come from all kind of processes like for example; Central Invoicing of Sales, Central Invoicing of Service and Central Invoicing of Warehousing but also from PCS Project itself.
Below the complete formula:
PCS / Cost of Goods Sold (Correction per cost component on order MIG-DELTA) =
Σ Actual Costs from table tipcs360 (Actual Cost Prices by Project) –
Σ Sales / Cost of Goods Sold –
Σ Sales / Cost of Goods Sold Price Variance –
Σ Service Order / Cost of Goods Sold –
Σ Service Order / Cost of Goods Sold Triangular –
Σ Service Order / Cost of Goods Sold Price Variance –
Σ Service Order / Field Change Order Costs –
Σ Service Order / Internal Service Costs –
Σ Service Order / Warranty Costs –
Σ Service Order / Repair Warranty Costs –
Σ Service Order / Contract –
Σ Service Order / Goodwill –
Σ Service Order / Transfer to project WIP –
Σ Service Order / Cost of Goods Sold Quotation –
Σ Warehouse Issue / Cost of Goods Sold –
Σ Warehouse Receipt / Receipt (kind of order is warehouse transfer manual) +
Σ Warehouse Receipt / Shipment Variance –
Σ Project (PCS) / Cost of Goods Sold–
Σ Project (PCS) / COGS (Triangular) –
Σ Project (PCS / Additional Cost of Goods Sold +
Σ Adjustment Order / Adjustment +
Σ Adjustment Order / Item Surcharge Issue +
Σ Adjustment Order / Warehouse Surcharge Issue +
Σ Adjustment Order / Item Surcharge Receipt +
Σ Adjustment Order / Warehouse Surcharge Receipt +
Σ Adjustment Order / Lot Result +
Σ Cycle Counting Order / Adjustment +
Σ Cycle Counting Order / Item Surcharge Issue +
Σ Cycle Counting Order / Warehouse Surcharge Issue +
Σ Cycle Counting Order / Item Surcharge Receipt +
Σ Cycle Counting Order / Warehouse Surcharge Receipt +
Σ Cycle Counting Order / Lot Result
4.1 Start in Baan IV and continuation in SSA ERP 6.1 LN
Step 1 in Baan IV
Standard material is issued for an SFC order related to a PCS Project. Integration transactions are “SFC / Inventory Transfer” and “SFC / Material Costs”.
Step 2 in Baan IV
General hours are booked on the PCS Project. The integration transaction “Project (PCS) / General Hours” is created.
Step 3 in Baan IV
After delivering and invoicing 3 pieces to the customer, session “Calculate Cost Prices by Project” (tipcs3250m000) is executed which will create the integration transaction “Project (PCS) / Actual Cost of Goods Sold”.
Migration from Baan IV into SSA ERP 6.1 LN
Before migration it will be mandatory to run the session “Calculate Cost Prices by Project” (tipcs3250m000) full range with both form flags on Yes, as instructed in the migration guide.
The PCS / WIP on the report “Project Work in Process” of session “Print Financial Project Transactions” (tipcs8410m000) in Baan IV should be equal to the PCS / WIP printed with the session “Print Project WIP” (tipcs3480m000) in the view “By Project / Order”. Both sessions will show and PCS / WIP of 105 €.
Step 4 in SSA ERP 6.1 LN directly after migration
Session Calculate Cost Prices by Project” (tipcs3250m000) is started which will create an integration transaction “Project (PCS) / Cost of Goods Sold” of 15 €. This is directly after the migration and nothing has happened within the new ERP system.
This has to do with the fact that we have in SSA ERP 6.1 LN new accounting rules compared with the mechanism in Baan IV and because the migrated “PCS / Cost of Goods Sold” records from Baan IV are skipped. After the integration transactions are posted to the Finance Package, we still have within Logistics and within Finance the same amount in PCS / WIP, which is 105 € – 15 € = 90 €.
Step 5 in SSA ERP 6.1 LN
The 7 pieces migrated from Baan IV are sent to the customer on a sales order. Integration transactions “Warehouse Issue / Issue” (5a) and “Sales Order / Issue” (5b) are created, this for the quantities delivered multiplied with the FTP of the customized item. In this example 7 x 12 € = 84 €.
Step 6 in SSA ERP 6.1 LN
The 7 pieces are invoiced to the customer. This will result in an integration transaction “Sales Order / Cost of Goods Sold” of 84 €. Also an integration transaction “Sales Order / Revenue Analysis” is created, but this has no impact on the PCS / WIP.
Step 7 in SSA ERP 6.1 LN
The session “Calculate Cost Prices by Project” (tipcs3250m000) is run which will create an additional “Project (PCS) / Cost of Goods Sold” transaction of 35 €.
Step 8 in SSA ERP 6.1 LN
The session “Close Project” is started and the PCS Project is closed. An additional new calculation is done:
PCS / Cost of Goods Sold Correction (MIG-DELTA) = Σ Actual Costs from tipcs360 – Outgoing Integration Transactions = 150 – 84 -15 – 35 – 45 = – 29.
The amount of -29 € is created in the integration transaction “Project (PCS) / Cost of Goods Sold” with the order number “MIG-DELTA”.
PCS / WIP
The PCS / WIP on the report “Print Project WIP” (tipcs3480m000) in the view “By Project / Order” will show 150 – 84 -15 – 35 – 45 – 29 = 0 €, and the PCS Project has the status closed. Also in Finance, on ledger accounts, the amount of PCS / WIP will show a value of zero €.
The whole process is drawn in the figure 4.1 on the next page.