Skip to end of metadata
Go to start of metadata

Purpose

Introduce Assembly Process in Project Systems.

Overview 

Assembly Process is used to plan products or services that are produced or carried out repetitively.
Advantage being changes made in the sale document automatically updated in the network and vice versa. Helps keeping project team and sales team on same page.
Assembly process omits MRP planning and generates an operative order directly. 

Assembly Process Flow: Example

Create sales order, quotation, RFQ  with Requested delivery date, quantiy - requirement qty and date copied from sales order to the network, backward scheduling is carried out for the network and availablility check is done for Material. system proposed date if we cannot meet the given date.

Material with Network is populated

Planned cost, confirmed delivery date provided by the system - Based on the quantities the network is adjusted accordings with respect to Execution factor.

Save the Sales order

Operative structure will get generated up on saving of Sales order.

1. SD / PS Process

i) Network - Header assigned network without a project will be generated, sales doc is the cost object.

ii)WBS and Network - Generate a network through sales order and when you save system create WBS and assigns the sales order item to a WBS element. Project is controlling object.

iii)WBS - we can assign a saled document item to WBS element, Project is controlling object.

iv)WBS and Production Order - production orede is manually assigned to the project.

2. Project number from Sales Document

TCode - CJ91

 



If there are two line items (refering to two networkss) in a 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( refering to two networks).

Only one root indicator is not set in the project profile to avoid any errors.

3. Prerequisites for Assembly Processing.

  • Standard network as template (and possibly standard WBS).
  • Material with sales views ( and possibly MRP views).
  • Material is assigned to Standard network.
  • Requirements class that enables assembly in the sales order.


 

Material views

Item category group is important for selecting the item category in the sales order.



 


Material is assigned to Standard network

TCode - CN08

   


Requirements class that enables assembly in the sales order

TCode - OVZG 

 
 

4. Determining the Requirement Class  - Configuration Settings  
 a)Main Strategy  - Determining Requirement Class by Main Strategy

Planning strategy is linked to requirement type

Requirment type is linked to requirment class.

i) TCode - OPPT

 


 

ii) TCode - OPPT

 

iii) TCode - OPPS

 

iv) TCode - OVZH
 

 

v) TCode - OVZG
 

 

Comparision between Strategy and Requirement Classes  - illustrates the data is same in both plannig strategy and requirement class. This is the reason this method is main strategy as if we have planning strategy in material master directly we are giving requirement class to the system.
   

 

b)Cofiguration Settings - MRP Group 

If System not able to find the Requirement class based on the above stragegy 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
   
   

 

c) Cofiguration Settings - Item Category 
If System not able to find the Requirement class based on the above two stragies 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
   
Requirement type is linked to requirement class.  

i)   TCode - VOV7
     

 ii)  TCode - SPRO

    

iii)  TCode - VOV4

    

 iv)  TCode - OZVI

    

 v) TCode - OVZH

   

5. Typical Example 

Create a sales order - Input order type, sales org, distribution channel, division.

Sales order overview - provide sold to party, ship to party and req. deliv date. 
 



      

 Sales order overview - Enter the material
 



     

Sales order oveiw- Enter order quantity



     

Sales order oview - At this point of time there is no WBS reflecting against the material. once we save the sales order, network is scheduled and proposes the delivery date and generates the operative structure.

      

 Sales order overview - once the sales order is saved , open the same sales order and we can see the project is created and sales order is assigned to this project.


     

Project - We can open the project in CJ20N, look at the assignment details and Req.dlv dt.  


      

 

Project  - illustrates the execution factor. Network is adjusted accordingly ,for the activities dependent on the quantity of the material. execution factor is equal to the quantiy based on which the multiplication happens and nework is adjusted to suit the production of required quantity. 


      

 This is the detailed illustration of configuration and a typical case study for a assembly process

Thanks,

Srihari Gubbala 

PS: A very good explanation,  apart from what Srihari has presented here, can be found here by Vikas Sharma with steps to test in IDES.

1 Comment

  1. Unknown User (j6gjpci)

    thank you very much............ this is very help full for me.....