Assembly Processing in SD and PS

INTRODUCTION

 

Assembly processing is one of the rarely used but extremely robust process used in various industries. This process encompasses the functionalities of receiving the order and planning all the requirements of the order by passing the requirements to various other related modules. Once all the components are received they are assembled and handed over to customer.

Based on the business requirement, a sales order can lead to any of the orders including  production order, planned order, a network or a process order. Based on this linkage configurations are to be done in the respective modules along with configurations in sales and distribution.

This chapter explains about the creation of a network in project systems while creating a sales order in SD. The functionality of assembly request can also be linked with various other functionalities like milestone billing in SD, milestone management in PS, Schedule and cost management in PS etc. However this document concentrates only on the configuration required for creating a network automatically when a sales order is created. During the course of the document, some of the obvious configurations are assumed to be known to the basic consultant and hence not dealt in much detail.

PROCESS FLOW

 

The process starts with the creation a sales order using a material code. The material codes in this case are very limited and are specific to every variation.

The sales order item will trigger a requirement transfer. As a result the requirement class triggers a network considering the requested delivery date of the sales order as the finished date of the network. At the same time, a project is created for the entire sales order and WBS element will be created for each of the line item.

If the network is enabled with milestones for activities, then milestone billing can be automatically triggered in sales order if the item category is also accordingly configured.

Now we have a sales order, a project for it, various line items each item having a WBS element and a network. Now it is possible to manage each of these line items in PS using schedule and milestone management. Accordingly when milestones are confirmed in PS, milestone billing can be triggered in sales orders.

At the end when all the items are delivered the project can be settled and closed. This document doesn’t deal about deliveries for project as my knowledge level in this area is minimal.

CONFIGURATION TRANSACTION CODES

 

Though I have the system with me, I don’t want to put the screen shots because of customer confidentiality. Hence I am trying to explain as much as information through text. In case of any doubt the same can be discussed in the comment on this content.

VOV8

VOV7

VOV6

Configuration Paths in Transfer of Requirements

CN91

CN08

CL24N

CN01

STEPS IN CONFIGURATION

The first of the configuration is the sales order type. This is the basic configuration in SD and hence I skip this configuration.

The header configuration is followed by the item category configuration. If milestone billing functionality is to be used, then the Billing plan type in the item category should have a value indicating the Milestone billing. A copy of billing plan type can be made by copying the billing plan type 01. Similarly the billing relevance can be maintained as I for billing based on billing plan and order related billing. Except this all the other settings for item category is same for assembly processing as for any other processes. Also it should be remembered that variant configuration is a robust functionality used in assembly processing to dynamically determine various project and sales parameters and hence the item category should also consider the use of variant configuration if needed.

Schedule line configuration is same as the normal schedule line configuration and hence I am not dealing much about it.

These are followed by the configuration for transfer of requirements. This is where the SD module is integrated with the PS module. It involves the following steps to determine the strategy group or the strategy type. It can be based on the normal rules for TOR. The strategy group can be determined from any one of the following methods viz…the combination of item category and MRP type,from  material master and so on.  Using this configuration either the requirement class is determined using the strategy group (if the strategy group is maintained in material master) or using the requirement type (if the MRP type is maintained in material master). The requirement class is the one which dictates the integration between SD and PS and the desired requirement class can be seen from the transaction code OVZG. The configuration at the requirement class should have the following fields filled.

The availability button should be switched off as the material availability is not enabled in assembly processing.

The field Requirements transfer should be ticked on in the requirement class

The assembly type should be 2. This will ensure that a network is created automatically if the relevant configurations are done.

The field Order type should be filled with the network type which is to be created while creating sales order.

The field Capacity check can have the value as 1 or 2 based on requirement of capacity

The fields related to costing and configuration can be left empty here as they can also be handled in other places which will take precedence over this configuration.

The field special stock can have the value as E to make sure that stock is reserved against the sales order.

The field Account Assignment Category should be enabled with the value D. This will ensure that the project or its subordinate levels can be used as account assignment objects. Based on the configuration in PS either the network and activity number or the WBS elements can be used as the account assignment objects.

The field Consumption should be configured with the value P to ensure project based consumption.

These fields are the mandatory fields to be updated. The remaining fields are optional and can be configured based on need. The fields related to costing, settlement, and valuations are best left empty here and configured in the respective modules.

Once these configurations are done in SD the process will work as follows.

When a sales order item is put, based on its item category, schedule line category configuration, the transfer of requirements is triggered and the correct requirement class is determined. Using the requirement class the system will try to create a network. However to create a network system will need another set of data from PS module. The set of data needed after doing the basic set of PS configuration are explained here.

At first a standard project should be created in PS using the transaction code CJ91.  In order to do this the project definition, the project profile etc are needed and the PS consultant will be in the best position to configure the project profile for this activity.

A standard project should also include a standard WBS element with all the necessary set up like planning element, account assignment element, billing element and other organisational elements. The creation of standard project and standard WBS element should follow the coding mask and the coding mask should take care of the number of characters for the sales order. Because any operative project or the WBS element will have the sales order number in the project as a standard functionality in assembly processing. For example if the coding mask is enabled as A/xxxxxxxxxx/ _____ then the characters xxxxxxxxx represent the sales order and the code with 10 characters will be used to fill up the sales order number while creating the project.

This is followed by the creation of standard network in CN01. The network can have the standard WBS element at the header and item level for all the activities if necessary.

Also in parallel the material master should also be set up by the MM consultant to be used in Sales order. The material master should have all the four MRP views and the MRP type should be kept as ND or the relevant MRP type to trigger the correct requirement type and hence the correct requirement class. If the MRP type is maintained as ND, then the strategy group should be maintained as the correct group which directs to the desired requirement class for the customer requirement.

Once these set up are completed, the final set up will be in the transaction code CN08 where the material code will be linked to a standard network.  This data should have the correct network order type as maintained in the requirement class. Also the standard WBS element maintained in this transaction code should be the one which is used in the network. Generally in standard network we use only one standard network. If multiple standard WBS elements are used in standard network activities, then in CN08, this field can be maintained with empty values.  The values MRP controller and the network profile are mandatory and should be maintained by the PS consultant.

If this is done in PS the transfer of requirements while trying to search for the network will have the necessary set up in CN08 and it will create an operative network.

It is also possible to have variant configuration enabled in assembly processing. Using this for example based on the complexity of the configuration and the activities required, different standard networks can be mapped to the same material using CL24N. 

Assembly Process in Project Systems With Screenshots

Assembly Process
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. 


      

How to create a new class type

How to create a new class type.

1. If the object table, you want to classify with, does not exist
- you have to add it to table TCLO using following customizing transaction:
SPRO -> Cross-Application Components -> Classification System -> Classes -> Maintain Object Keys.
If the object table already exists, please go to 2.



Add the table and maintain transaction code and key fields.



2. In transaction O1CL, you also have to add the new object table.
SPRO -> Cross-Application Components -> Classification System -> Classes -> Maintain Object Types and Class Types



3. Then, select the new object table and go to 'Class Types'. Here you can add a new class type.

 

4. The last necessary step is to maintain the classification status.
Now, the new class type is ready for use.
For more information about class types in general, please have a look at SAP Library:
--> Cross Application Components
   --> Classification System (CA-CL)
      --> Class Types
 

Few PS Interview Questions and Answers

http://www.scribd.com/doc/60828011/SAP-PS-Interview-Questions-Answers-and-Explanations

Why project profile is used?

What are different types of cost planning?

What is difference between ECP and unit costing?

What is allocation structure?

How to configure settlement rule?

Why settlement is made for the WBS?

How settlement is made for the WBS?

What are difference types of billing?

What is resource related billing?

What is the integration between PS and FICO?

What are the basic tables in PS?

Why and how budgets are used in PS?

What are the basic steps for budget functionality?

What is the difference between customer project and investment project?

What is coding mask?

What can be created from the project (PReq, PO, SO..etc)?

What is substitution and where it is used?

What is validation and where it is used?

What is the difference between standard PS and cProjects, which one is more convenient?

How to block user from entering time for the last year in CATS?

What is the AUC and Final Asset?

What are the basic configurations needed for creating a project?

1. What are the parameters of Project System?

There are several parameters to define in here at the structures level. First, its the Project Definition (Proj. Profile), then we have the WBS Level, and then, if used, the Network/Activity/Subactivity Level. You may include components and services. The configuration goes into Proj. Definition, WBS and Activity profiles.

2. What is the accounting and Logistical information that gets defined with a Project Definition?

In the Project Profile, you define the Controlling area, Company Code, Business Area, Plant, Functional Area, Profit Center and Project Currency for the project. If it is a sales project, you can also define Sales Organization, Distribution Channel, Division and DIP Profile. In addition, you also define the Object Class, Planning Profile, Budget Profile, Costing Sheet, Interest Profile, Investment Profile (CAPEX), Result Analysis Key (CO-PA), Settlement Profile and Settlement Rule Strategy. You will also define whether costs are actual or statistical. This information is then copied to lower level WBS elements.

3. What do Activities, NTW, WBS represents?

WBS and Networks are two structures that differ in the way in which they enable you to structure projects and in the functions provided for them in the SAP system. For example, if you need a hierarchical budget management function for a project, you would want to use a WBS structure. If, in addition, you also want to do capacity planning, you would have to use one or several networks as well. Depending on the specific requirements you may be able to map a project only via a WBS structure, or by using only one or several networks, or a combination of both.

4. What is the menu path & T. Code for defining special characters for Projects?
 

It can be found at the following location:

Project System >>> Structures >>> Operative Structures >>> Work Breakdown Structures >>> Project Coding Mask >>> Define Special Characters for Projects

Transaction is OPSK

5. The structure of NTW is similar to what type of order?

Maintenance order.

6. What is the impact of coding mask on the project and where is it created (menu path)?

Coding masks contain the sections for the external identification of projects, and they are separated by special characters. A section consists either of numbers that are represented by "0" characters in the coding mask, or alphanumeric characters that are represented by "X" characters in the mask. You can store a descriptive text for each coding mask and use lock indicators to control whether the key and the associated mask can be used for operative or standard WBS structures.

Project System >>> Structures >>> Operative Structures >>> Work Breakdown Structures >>> Project Coding Mask >>> Define Project Coding Mask

Transaction is OPSJ

7. How to set field status of WBS as mandatory, (WBS Element, NTW)?

There are five different transactions. Project Definition, WBS Elements, Network Header, Networks Overview and Network Details. There you will see a table with radiobuttons that indicate whether a field should be set as Input, Required (mandatory), Display, Hide. You can also define Influence Fields and Field Groups.

For Project Definition and WBS Elements:

Project System >>> Structures >>> Operative Structures >>> Work Breakdown Structures >>> User Interfase Settings >>> Define Field Selection for Work Breakdown Structures

Transactions are OPUK (Project Definition), OPUJ (WBS Elements)

For Networks:

Project System >>> Structures >>> Operative Structures >>> Network >>> User Interfase Settings >>> Define Field Selection for Networks

Transactions are OPUA (Header), OPUB (Overview), OPUC (Details)

8. Diff between validation & substitution

Substitution enables to automatically change master data fields of Project Definitions, WBS Elements, Network Headers and Activities. For example, you can automatically set the cost center 9999 for those WBS Elements into which responsible persons with number 0 to 20 have been entered.

Validation enables you carry out self-defined checks for master data fields of the same elements. But the result of validations consists of informational messages, warnings or error messages. For example, you can validate that projects with a specific project profile always begin with the same key.

9. What do time profiles do?

This profile is part of the "Planning Board Profile" and it determines the begginning and the end of the evaluation and planning periods. This means that preevaluation and post evaluation periods are defined automatically. This is how the Planning Board is displayed graphically.

10. Where do we define time profiles? What is evaluation period?

Evaluation period is the period in which you want to control your project, and it will be displayed in your planning board. Dont get confused with scheduling, which is how time is managed in a project.

Project System >>> Structures >>> Project Planning Board >>> Define Time Profiles

Transactions is OPTY

11. What are the different time profiles?

There are two, but you can define your own. SAPPS_Z001 and SAPPS_Z002.

12. What is value categories required for? Where are they maintained?

13. What are the important terms in a costing sheet?

14. How to create and change planning profile? What is the Menu path?

15. How and where do you control the budget for the project & what is the menu path?

Through the Budget Profile, in transaction OPS9. Path is:

Project System >>> Costs >>> Budget >>> Maintain Budget Profile

Among other things, you will have to define the Time Frame (Annual or Total), Exchange Rate type, whether or not Availability Control will be used, and the Budgeting Currency. There are additional settings in that path, such as defining a Budget Profile for a Project Definition among others.

16. How do you control that the project does not run over allocated budget?

You use Availability Control by defining tolerance limits, which will allow you to define by how much you can overspend. For example, you can set the system to send you a message wuen 95% of the budget has been spent, and stop al PR´s when you have reached 100% or 110% of the budget. Path is Project System >>> Costs >>> Budget >>> Maintain Budget Profile >>> Define Tolerance Limits

17. What does project version do? How do you define the project version (menu path)?

18. What governs the way scheduling is to be performed? What is the menu path?

19. What setting does NTW scheduling contains? Where are these settings done (menu path)?

Control Key in transaction OPSU defines whether an activity can be confirmed, scheduled, capacity requirements determinarion, costs, etc. Other important settings include Network Types, Parameters for Network Types, Network Profiles and Control Keys. There settings are found in the following paths:

Project System >>> Structures >>> Operative Structures >>> Network >>> Settings for Networks

Project System >>> Structures >>> Operative Structures >>> Network >>> Settings for Network Activities

20. What is the organizational structure of PS module?

PS structure consists of Project Definition, WBS Elements and Networks. PS uses structures from FI/CO, MM, SD, etc. There is no structure of PS but the one provided above. - See more at: http://www.saptechies.org/sap-ps-question/#sthash.ghLTqN3i.dpuf

21. What are the important or major difference in Customer projects and Investment projects integration?

By using the integration of SAP PS & IM in the SAP system, you can plan, distribute monitor budgets of projects.

Investment programmas in the investment management for the basis for the comprehensive planning & budgeting of costs for a company's plans or investments. Investment programs consist of an investment program definition with general specifications and default values for entire programmes & hierarchically arranged IM Program positions.

After you create structure of an investment program, you can use this to plan costs hierarchically and to allocate budget.

Maintenance order, internal orders and projects that you assign to investment program positions are called investment measures. ( in SAP terminology create Appropriation request IMA11) to map project proposals, ideas other plans before their possible implementation in system. you can create variant within the AR for the different investmemy options

Using status & workflow you can map multiple approval process for AR in IM.

After you approve the AR you can transfer this to the Investment measure when you create project from AR, you can use operative & std WBS as template. when you transfer AR to project, project receives master data of AR.

After you have assigned AR & Investment measure to investment program positions, you can roll up their planned cost to relevant program positions ( IM34)

Cost planing of Investment program can be use for the budgeting process in IM. Fist step to allocate budget of diff. prog. positions & second to allocate budget to IM measure i.e. in PS terms projects.

Settlement of Investment projects :

If you assign an investment profile to a WBS, the system may automatically generate one or more AUC when you release WBS. Based on requirement of your you create fixed asset & diff. part to be capitalized as FXA & not.

22. Primary integration for PS

Below is a brief overview of the primary integration points for PS – there are others, such as Fixed Assets and Human Resources but they do not play as substantial a part as the ones shown below.

Controlling (CO) – Substantial integration exists between PS and CO. This is because PS relies on so many objects that belong to CO for Integrated Cost Planning, Settlement, Results Analysis, Resource Planning and any reporting that involves Cost Elements. Controlling Area is the most obvious connection, without which PS could not function. In Workforce Planning via Work Centres/Activity Types, there is integration with Human Resources (HR) to register personnel who are assigned to projects.

Materials Management (MM) – Based on Materials and BOMs, PS has the ability to create Reservations, Purchase Requisitions and Purchase Orders via Easy Cost Planning Execution Services and Networks in general. This powerful integration makes PS a key player in the logistics cycle, including the ability to handle Services via Service Masters. Further, the ability of Networks to work with Catalogues takes PS into SRM (Supply Relationship Management), where the internet plays a large part in sourcing materials. Additionally, PS can help manage the MRP (Material Requirements Planning) cycle with its MRP Grouping functionality. PS is the ‘owner’ of the ProMan facility which tracks and helps manage all the Procurement document flows.

Sales and Distribution (SD) – PS has a fairly straight-forward integration with SD via Order Numbers. All SD Orders (Quotations, Sales Orders, Consignment Orders etc) can be assigned to a project for the purpose of planning revenue, creating Billing Plans and attracting costs. DIP Profiles (Dynamic Item Processors) assist in the process of simulating and automatically creating Sales Documents, plus providing a means to bill customers based on activity within a project (Resource-Related Billing). Additionally,

Assembly Processing provides the means for a Sales Order or Quotation to automatically generate a Project using Configurable Materials.

Finance (FI) – As PS is primarily a Cost Planner and Cost Collector and therefore a slave to FI/CO, its primary objects (WBS and Network) rely on actual expenditure to manage Account Determination, which is really the Chart of Accounts. Ultimately, all costs end up somewhere in Finance. Cash-flow management is also a feature that PS can be used for, via Funding Areas in Treasury.

Production Planning (PP) – Though not a major player in the PS side of integration, it is via MM that PP is informed of Production Orders using special settings in the Material Master.

Plant Maintenance (PM) – At the heart of this integration is Maintenance Orders, which like most external orders can connect to PS for Planning and Settlement purposes. Generally, Maintenance and Service Orders apply to Capital or Customer-based projects, where equipment serviced on-site can be managed in a Project.

Investment Management (IM) – Quite a substantial amount of integration here. IM seamlessly integrates with PS to manage Assets Under Construction (AUCs). Cost Planning can be managed in PS, sent to Investment Programs and returned to the project as a managed Budget. AUCs are automatically generated when a project is released, so there is relatively important connection to Fixed Assets.

23. How to create a new Project Profile?

We have a new location (company code, etc). When I enter CJ20N to create a new project I need to have a project profile for the new location available.

Transaction OPSA.

24. What is SAP-Project System?

    Project System is a Project management tool from SAP. Which has a very good integration with the other modules of SAP like FI, CO, MM, SD, PP, HR, DMS. This module basically co-ordinates and controls all the phases of a project, in direct co-ordination with purchasing and controlling, from quotation to design and approval, to resource management and cost settlement.

    Also beside the integration with the SAP module this Project system also has an integration with the third party popular Project management tools like Microsoft Projects and Primavera.

25. What is Project Definition ?

    Project definition is a binding framework in SAP for all organizational element created within a project (e.g. WBS and Networks). Data like company code, plant and person responsible can be defaulted into WBS if initially entered in the project definition. Such data can also be defaulted into the project definition via project profile which will then default it to subsequent WBS.

26.    What is WBS ?

    A Work Breakdown Structure (WBS) is a model of a project, and shows the project activities to be fulfilled in hierarchical form. It forms the operative basis for planning costs, revenues, and payments, as well as for scheduling, and budgeting. It also shows the responsibility.

    One definition from the Project Management Institute is as follows:

    The Work Breakdown Structure (WBS) is a key planning tool used to define a project in terms of its deliverables while providing a method for breaking these deliverables into meaningful work efforts.

    It is the functional basis for further planning steps in a project, for example, for process planning, cost planning, scheduling, capacity planning or costing, as well as project control.

    It provides a clear picture of the project and facilitates the coordination and implementation of the project from a management standpoint.

    It shows the work involved in a project.

    Work Breakdown Structures (WBS) is created under an object known as Project definition.

27. What is a Network ?

    A Network in Project System module is used to represent the flow of activities or tasks within a project. During the life cycle of a project, networks are used as a basis for planning, analyzing, controlling and monitoring schedules, dates and resources.

    A Network header contains all the project activities and can be used to default certain values for the entire network. Some of these fields include assignment to WBS, profit center, basic start and finish dates of the network as well as indicators for scheduling (forwards, backwards).

28. What is Standard Project Structure ?

    Standard structures in Project System can be found in Standard project definitions and in Standard WBS These standard structures can be used as a template to standardize project management.

    This brings about the advantage of Making the processing of projects more transparent (everyone create an operative project from a standard project), Enabling comparison of projects with similar structures, Facilitates project controlling

    Standard project templates CANNOT be used to capture any actual data (e.g. costs, actual materials used) and they serve as a quick way to create an operative project during implementation stage. As such, it is recommended that nominated users maintain these standard project templates at least once a year or whenever there are process changes for each type of project.

29.   What is Project type ?

    Project type is an object that groups projects according to criteria. Authorization and security can be done based on the project types.

30.  What is Project Coding Mask ?

    Project Coding helps display complex project numbers. They can also be used to indicate the position of a WBS element in the project hierarchy.

    We can create a mask for every key you want to use in project coding. Project Definition has to be unique in the SAP System and also WBS Element has to be unique in the SAP System.

    Project code is changeable and the hierarchy can be changed up to certain point of project status.

    Project Code has 2 parts

    Part 1: Project Identifier (Project Coding Mask)

    Part 2: Project Number (usually a serial number)

    Every project begins with a Project-ID (max. 5 Characters), Using separators to distinguish the different WBS levels. e.g.: "/", "-", "."

31. What is Project Management?

32. What is unit costing?

33. What is Project planning board?

34. What is Gantt chart?

SAP PS Business Blueprint

http://www.docstoc.com/docs/document-preview.aspx?doc_id=89088115