Project System - Assembly Processing

Project System – Assembly processing

Settings and process sequence for make to order

1. Master Data Required

Create a standard WBS Tcode CJ91

For SD and PS integration you have to check SD/PS assignment in control tab. If there are two line items (referring to two networks) in sales order no: 1563 with no SD/PS assignment – project number generated will be T-1563.

With SD/PS assignment ticked – there will two numbers generated T-1563-10, T-1563-20 for two line items (referring to two networks).

Only one root indicator is not set in the project profile to avoid any errors.Assignment of standard milestone to respective WBS/network.

Select the WBS item to which you want to attach milestone than select WBS element milestone overview

Note: you require Standard milestone to assign to WBS or network activity.

Creation of Standard milestone: Tcode CN11

Here you have to enter description and usage of milestone and select sales document date (which is used for billing milestone)

2. Create a standard network Tcode CN213. Finished product that is required to manufacture through assembly process.

Tcode MM01

You have to select industry type and material type which you want to produce. Than this will configure material according to sales area/plant.

4. Allocation of standard material to network

Tcode CN08 defines the relation between material/std WBS/std Network/Network type/Network profiles.

This assignment is very important for assembly processing because when you use material to be produce in sales order, based on that material a project is to be created with using this assignment. Otherwise this will gives pop up window to assign std WBS and std network. End user may select different WBS and network. So to avoid this error we have to assign material to std WBS and std network

Setting required in SD module

1. Define requirement class with network type as PS01 or PS04 and with account assignment category as Q project make to order if you want all operational as well as materials cost to be accounted at project level with assembly option as 2.

Tcode OVZG (requirement class)

Assembly type as 2 (production order, network or service (static processing)) Order type as PS04 (network for sales order) Account assignment as Q (project make to order). Now we have to check strategy group as 85 (assembly processing with network/project)

2. Check strategy group assigned to requirement typeTcode OPPT

3. Tcode OPPS

In this Strategy please check requirement type should be assigned as KMPN

4. Tcode OVZHdefines the requirement type and assigns the requirement class to requirement type.

Note: Standard settings available in SAP or we can define by own also

5. Check requirement class Tcode OVZG

Setting in PP

1. Create BOM in Tcode CS012. Creating routing for the production operations Tcode CA013. Configuration Settings - MRP Group

If System not able to find the Requirement class based on the above strategy it will tries to find out based on MRP Group.

If planning strategy is not maintained in the material master, system picks the same from MRP group, in the MRP group we have planning strategy and the above cycle is repeated to get the requirement class.

Tcode - OPPU

Note: for routing we need work center and activity type defined already. Cost for activity type in KP26. Not these activity costs related cost elements should be part of product costing for cost to flow in all reports as to know the cost for finished product

Setting in PS

In PS if you want all the operational cost also to be accounted for at project level from planning onwards then set in Tcode OPSV “order level updating” ensure check box for 10 and 20.

Setting in MM

In material master in MRP view we need to set the MRP group and strategy group relevant for assembly process. As strategy will have requirement type.

Tcode MM01

Item category group is important for selecting the item category in the sales order. Strategy group as 85 and MRP as PD (MRP).

Settings in SD

1. Create a separate sales document type if required Tcode VOV82. To maintain Item category, configuration settings – item category

If system not able to find the requirement class based on the above two strategies (i.e., requirement type and requirement class) it will tries to find out based on item category. From item category group maintained in the material master and sales document type entered in the sales order system determines item category.

Item category linked with requirement type and requirement type is linked to requirement class Tcode VOV7

Tcode VOV4

Path: SPROSales and DistributionBasic FunctionsAvailability check and transfer of requirementTransfer of requirementDetermination of requirement type using transaction.

Execution steps

1. Create an inquiry in VA112. Create Quotation in VA21 with reference to inquiry3. Create sales order in VA01, while creating sales order, as soon we assign the material

component in SD line item a pop will come for entering std WBS, std network, network profile. Once we enter this at bottom we can see that scheduling is carried out.

Note: if we define materials/std WBS/std network in CN08 then pop will not come. Now check for errors and save the sales order, at bottom we can see that project order is created.

Note: Project number is same as sales order number.

4. In billing plan tab at item level we can see the milestones for new project.5. In sales order we can see that billing lock is set against the milestones.6. Now open the project in CJ20N and go to network we can see sales order no with line item no7. Now verify the milestones in the project.8. Check the requirement list in MD04 against the finished product we can see that requirement

is generated against project with respect to sales order.9. Run MRP in MDBT/MD02/MD01, based on procurement type in MM, PR’s and planned order

will generated. Note: All PR’s and planned orders are account assigned to WBS.10. Now do PR->PO->GR> (All accounted against project)11. Convert planned order to production order release the orderGoods issues against

production order.12. Confirm the production order with respect routing operation one by one in C011N.13. In cost element reports at projects we can see the cost breakup for all production activities as

well as for material.14. Settle the production order.15. Confirm all activities in project16. Do billing in SD as when milestone reaches to post actual revenues.17. Run RA in KKA2 and save the RA results18. Run Settlement in CJ8819. Set the status of project as TECO and CLSD