Business BluePrint PS1 Version2.1

© Zensar OBT Technologies Ltd.

s

Page 1 of 82

Business Blueprint

Project Systems (PS)

document.doc1

Submitted to

Flat Products Equipments (I) LTD.MUMBAI

By

Oct’ 2008


Document Control

Document ID : OBT/2007/PRJ-/00

Compliance Status : Mandatory

Security Classification : Company Restricted

Issue Date : 13.10.2008

Document Status : Draft, Revised, Final

Prepared by : Mr. Nara Prasanth

Quality Review : consultant

Authorized by : Zensar OBT

Distribution : Client PM

Document History : V3.1

Page 2 of 82

2008. ZENSAR

The information in this proposal shall not be disclosed outside CMI Flat Products Ltd. and shall not be duplicated, used or disclosed, in whole or in part, for any purpose other than to evaluate the proposal. Provided that if the contract is awarded to Zensar OBT as a result of or in connection with the submission of the proposal, CMI Flat Products Ltd. shall have the right to duplicate, use, or disclose the information to the extent provided by the contract. This restriction does not limit the right of CMI Flat Products Ltd. to use information contained in the proposal if it is obtained from another source without restriction.

All other company or product names mentioned in this document are used for identification purposes only and may be trademarks of their respective owners.


INDEX

(A) PROJECT SYSTEM

(A.1) Introduction to Project Structuring(A.1.1) Project Definition(A.1.2) Work Breakdown structure (WBS)(A.1.3) Network & Activities(A.1.4) Relationships(A.1.5) Milestones(A.1.6) Time Scheduling(A.1.7) Network Scheduling(A.1.8) Confirmation(A.1.9) Cost Planning/Controlling

(A.2) Organization structure(B) SAP PROCESSES

(B.1) Organization structure – Sap System(B.2) Project Objects with Structure(B.3) Coding Mask(B.4) Project Tools(B.5) Scheduling(B.6) Material Components to WBS/activities

Delivery from Project(B.7) Procurement of Bought out items(B.8) Planned & Actual costs in PS structure.(B.9) Project Version(B.10) Project Closing(B.11) Status Management(B.12) Work centers

(C) SAP Process Tree

(D) PS SAP Standard Reports(E) Appendix

Page 3 of 82


PROJECT SYSTEM

A.1 Introduction to Project Structuring

Project Structuring

Before you can run a project in its entirety, you must first describe the project goals precisely and create a structure for the project activities to be carried out. A clear project structure provides the basis for successful project planning, monitoring and control.

You create and manage your project structure in the R/3 Project System by means of work breakdown structures (WBS) and networks. The WBS describes the individual phases and functions of a project. You plan the processing itself in the network. This contains the individual project tasks and the dependencies between them in the form of activities and relationships.

Project system module will be covering Project structuring along with the following:

A.1.1) Project Definition A.1.2) Work Breakdown structure ( WBS) A.1.3) Network & Activities A.1.4) Relationships A.1.5) Milestones A.1.6) Time Scheduling A.1.7) Network Scheduling A.1.8) Confirmation A.1.9) Cost Planning/Controlling

A.1.1Project Definition

The Project definition is a general description of the project you want to manage. You use it to record the idea behind the project. The Project definition is the frame work for all the objects you create in later project planning phases.

Page 4 of 82


SAP AG 1999

Project definitions

Project Definition and Work Breakdown Structure

Project definitions

Work Breakdown Structures

WBS elements

A.1.2 Work Break down Structure (WBS)

The work breakdown structure (WBS) is the hierarchical model of the tasks to be performed in the project. It provides an overview of the project and:

o Forms the basis for project organization and co-ordination.o Shows the work, time and money spent on a project.

The WBS is the operative basis for a wide range of further planning steps. You can use it to plan dates and costs.

WBS elements

The individual tasks required to carry out the project are called work breakdown structure elements (WBS elements).Depending on the project phase, you can further breakdown the work with subordinate WBS elements.

Page 5 of 82


A.1.3 Networks & Activities

SAP AG 1999

Network Structure

* if the network is header assigned** if the network is activity assigned

Networkheader

NetworkInternal/external numbers

Network headerDefault values, control valuesAccount assignment object*

ActivitiesPlanning elementAccount assignment object**

Activity elements

Relationships

The network describes project processing. The essential elements comprising a network are activities and relationships. Networks form the basis for planning, analyzing and monitoring time schedules, costs, and resources (such as personnel, machines, production resources/tools and materials)

Activities

You use activities in the network to plan your project staffing, capacity, material, and service requirements. You can add detail to your planning by using sub networks and activity elements. When you assign the activities to WBS elements, you then obtain the detailed view of costs, dates, and capacities at the WBS level.

Activity types

You use different activity types depending upon on which tasks you want to carry out in the project.

Page 6 of 82


SAP AG 1999

Control key

Type ofactivity

Workpapers

Relevance toCapacity

Relevance toCosting Relevance to

Scheduling

Confirm-ation

Network Activities

Internal Processing

Work/services performed inhouse

External Processing

Purchasing of work/services

Services

Purchasing of services with service specifications

Costs activity

Planning of additional primary costs

For tasks that require capacity (machines or personnel) in your business, create internally processed activities.

For tasks that involve outside contractors, create externally processed activities. When you use such an activity, you create a link with purchasing referencing a purchasing info record. The purchasing info record (maintained by Purchasing department) contains prices and delivery dates for external activities. The system automatically creates a purchase requisition based on the data in the purchasing info record.

If you want to plan costs without referencing other objects in the R/3system, use general costs activities. An example would be planning travel expenses. In our case, you can plan at WBS level as actual costs are entered by FI at WBS level.

You can use activity elements to plan your work in more detail. You can use one or more elements of any type to achieve the level of detail you need.

You assign the material components to the appropriate activities to plan the materials you need to execute your project.

A.1.4 Relationships

Page 7 of 82


You use relationships to depict chronological and technical dependencies between activities. The relationship you define determines the nature of the link between the individual activities.

o FS relationshipAn activity does not start until the preceding activity is completed.

o SS relationshipAn activity cannot start unless another activity has started.

o FF relationshipAn activity cannot be completed until another activity has been completed.

o SF relationship

An activity cannot be completed until the activity succeeding it has started.

You can use relationships to link activities in different networks. This means, for example, that you can produce a time schedule for the whole project, regardless of whether you are planning in an overall network or in individual networks.

SAP AG 1999

Relationships

AssemblyAssemblyProductionProduction

Time sequence

Work Work schedulingscheduling

EngineeringEngineering

EngineeringEngineeringBestellung

Purchase orderPurchase order

TestTestrunrunTÜV

AcceptanceAcceptance

Logical sequence

FS relationship

SS relationship

FF relationship

SF relationship

A.1.5 Milestones

Page 8 of 82


Milestones are events within a project to which particular importance is attached or which trigger a predefined function implies sales document is triggered for milestone billing. In general, they indicate transitions between different phases or departments. You can assign milestones to activities and WBS elements.

A.1.6 Time Scheduling

Time scheduling is based on the project structure. When the work breakdown structure (WBS) represents the structure of the project, you use activities to plan the actual course of the project. This means that you first plan dates that are independent of each other. You plan the dates manually in the WBS to create a first, rough-cut schedule.

For more detailed planning you create activities and relationships, stipulate scheduling constraints, and plan durations. As part of scheduling, the R/3 Project System automatically calculates the start and finish dates that material will be required. You can then reconcile the dates calculated with those maintained manually in the assigned WBS elements.

Date types

The Project system distinguishes between the following date types:

o Basic datesFixed dates which you enter manually in the network or WBS element. You can use basic dates in scheduling as the framework for activity dates.

o Forecast datesExpected dates which you enter manually in the network or WBS element. You can use forecast dates to depict different scheduling situations. Example: best or worst case scenarios.

o Scheduled datesDates calculated by the system as part of the scheduling or confirmation processes.

o Actual datesDates reflecting current state of the project. You usually enter them manually in a confirmation, but can also have the system determine them from internal activity allocations or confirmations.

o Scheduling constraintsConditions for the start or finish date of an activity.

Time Scheduling in Work Breakdown Structures

You plan the dates manually in the work breakdown structure. The system supports you with consistency check, date comparison and date leveling tools. You can plan basic and forecast dates on any level in the hierarchy.

Various time scheduling methods are available:

Page 9 of 82


o In top-down planning, you plan dates starting from the top WBS element. All dates planned in subordinate WBS elements must fall within the time-span of the dates planned in the superior WBS element.

o In bottom-up planning, you plan dates starting from the subordinate WBS elements.

o In free planning, you can plan dates without any hierarchy dependencies and on any level.

Time Scheduling with Activities

The system automatically calculates activity dates as part of scheduling. The dates are calculated on the basis of the planned activity duration. In addition, you can plan time dependencies for activities in the form or relationships and constraints. For example, you can stipulate that an activity must be completed by a particular date.

Scheduling

Forwards and backwards scheduling are always carried out using activities and relationships. They calculate the earliest start and latest finish dates for activity execution. You can trigger scheduling from a network or WBS.

A.1.7 Network Scheduling

In network scheduling, the R/3 System determines the earliest and latest start and finish dates for activities. The resulting data is used to calculate floats. Floats supply information on the time reserves available for carrying out individual activities. In evaluations use the floats highlight activities where time is critical.

Overall Network Scheduling

If you have used relationships to link a number of networks, you can also use the overall network scheduling facility whereby all the linked networks are scheduled together using one start date and one finish date. The result is a consistent schedule covering the whole network.

WBS Scheduling

You schedule the project structure and all the activities assigned to it starting from one WBS element, sub hierarchy or from the whole project. You can copy the resulting dates to the basic or forecast dates for the assigned activity and can use them as the basis for new WBS scheduling.

Rescheduling with Actual Dates

Rescheduling may also be necessary if you already have made confirmations for activities-that is, if execution has already begun. Scheduling can start either from the actual finish date or from today’s date.

Controlling

Page 10 of 82


The project Information System will help you control your schedules effectively. You can compare the planned dates with actual dates or the expected date of completion. Statistics give you a quick overview of variances from the schedule due to for, example, late starts or delays during processing. In addition, you can display data according to different criteria –for example, you might want to see all the activities which are running late. This way you can spot delays early and take corrective action.

You can use project versions to record how the dates in your project have developed, starting with those originally planned through intermediate stages to the current dates.

A.1.8 Confirmation

Another important step in project execution is entering actual times. You can only find the answers to the following questions if you have access to up-to-date, reliable actual values for your project:

o Is the project running on schedule?o Are delays likely?

You enter actual values in the form of confirmations by entering actual start, actual finish and the degree of processing.

A.1.9 Cost planning / controlling ( Relevant for CO module)

Cost Controlling

Unlike dates and resources, which you can change directly, costs are usually calculated from valuation methods or agreed prices for internal and external materials and services. Accordingly, costs in the R/3 Project System are automatically calculated wherever a price and/or quantity structure exists. In the process, the system takes account of the dates of the planned project activities by assigning the planned costs calculated to the appropriate periods. Alternatively, you can enter planned costs manually.

Cost for External Procurement

You plan external activities, such as services, using externally processed activities. Material procurement is represented using material components. In both cases, you can copy procurement conditions, such as prices, discounts and so on from a purchasing info record. The system automatically uses this information to calculate the relevant planned costs.

Costs from Use of stock material

You use material components to plan stock material usage for an activity. The system calculates the plan costs by taking account of material stock valuation. When you later draw the materials, the system automatically charges costs to the appropriate activity.

Costs from Assigned orders

You can have the system automatically display costs from, calculated using either planned orders .This applies to the orders from Controlling (CO), etc.

Page 11 of 82


Travel Expenses, Insurance & other Costs at WBS level

You can plan other costs, such as travel expenses and insurance as general costs activities in the project which is done WBS level for cost elements defined by FI. Actual values are entered by FI for the cost element, amount, and currency in the WBS element defined in the structure.

Unplanned Costs (Actual costs booked by FI)

It is possible to enter actual costs which have not been planned or which do not reference any planning. So for example, in Controlling, you can make an internal activity allocation directly for an activity in your project .This ensures that actual costs are recorded correctly.

Actual Cost & Controlling (Not relevant, but used by FI & CO, MM)

As the project is executed, actual costs are incurred, arising from example:o Postings in Financial Accounting and Materials Managemento Activity Confirmationso Orders assigned to the project

To monitor and control actual costs and compare them with the planned values, you need a comprehensive cost controlling system.

Effective cost controlling requires very different aspects and level of detail. With R/3, you can generate evaluations from the project manger’s viewpoint and evaluations showing the view from further down the line. The flexible database system means you can choose individual valuations and display them in summarized form.

Highlights:

Automatic cost calculation keeps planning work to minimum.

The Project system is comprehensively integrated with systems such as Controlling

( CO),Financial Accounting ( FI),Production Planning(PP),and Materials

Management(MM)

Cost planning is possible in any level of detail.

Cost planning is correct by period and date.

The Project system is well integrated with the Enterprise controlling, ensuring that the

project agrees with the Cost Center Accounting and Profit & loss accounting.

(B) Organization Structure

In SAP System the several structures represent the legal and organizational structure of the

company. The organizational structures form a framework in which all business transactions can

Page 12 of 82


be processed. The organization structure of Project System is linked with Organization structure

of Financial Accounting and Materials Management.

This is the structure of the company, whereby each area of the business is represented in a hierarchical element.

(For details refer the FI & CO blue print)

Controlling areaControlling areas are the organizational units in a group which require their own complete, self contained cost accounting.You can use one controlling area to conduct joint cost accounting for a number of company codes.

Cost centerA cost center is an organizational unit within the controlling area. It represents a sharply delineated area within which costs arise. The delineation can be based on functions, cost settlement techniques, physical location or responsibility.

Company CodeA company code is an organizational unit within a client for which a separate balance sheet is drawn up. The balance sheets and Profit & loss statements required by legislation are produced at company code level.(For Material Management structure refer blue print of MM)

Purchasing Organization The purchasing organization is an organizational unit which procures materials or services for one or more plants and negotiates terms with suppliers.

Purchasing groupThe purchasing organization is divided into purchasing groups which are responsible for particular purchasing activities.

PlantPlants are units within logistics which divide the business as viewed from production, procurement, maintenance and material requirements. They manage their own inventory and material requirements.A plant can be production site or simply adjacent locations with their own stock of materials.

Storage location You can use storage locations to distinguish between material stocks within a plant .The term “storage location” usual refers to the physical location of the stock.

Work centerWork centers are means of dividing a plant into organizational units which perform a particular service. Examples include machines and employees.

Page 13 of 82


(II) SAP Processes

Page 14 of 82


(B.1) Organization Structure – SAP System

TO-BE DocumentFor SAP R/3 Implementation at Flat Products Equipments (I) Ltd

Version Number: 1.0 Date: 02/09/2008Name of Business Process: Organisation StructureModule: Project System Sub module: Organisation Structure –

SAP systemVersion Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table

B.1.01 to Be Process

SAP Project System does not have the organization structure of its own. It uses the structure as defined in the TO-BE Process of the core modules Materials Management, Financial Management, Sales & Distribution.

For details we have to refer to the Blue print of the above modules.

In SAP Project System (PS), we shall be using the organization structure as defined by the other modules.

Following is the relevant Organization structure mentioned for SAP system.

a. The Company is defined as FPG – Flat Products Group.

b. The Controlling area is FPNT- Flat Products Controlling Area.

c. Under the Controlling area there are two Company Codes- FPE - Flat Products Equipments- NTS - N.T Strips & Automation.

d. The Plants & the Sales Organization associated with the Company code FPE & NTS is as follows:

Company Code

-FPE -Flat Products Eqp -NTS -N.T.Strips & Automation

Plant

-1000 - Flat HO -FPE -2000 -Flat HO- NTS-1100 - Taloja plant -2100 - Ghodbander Plant

Page 15 of 82


-1200 - Silvassa Plant -2200 - Bhayendar Plant

Purchasing Organization

-1000 -Purchasing flat -2000 -Purchasing NTS

Sales Organization

-1100 FPE Domestic Sales -2100 - NTS Domestic Sales-1200 FPE Export Sales -2200 - NTS Export Sales

-1300 FPE Misc Sales -2300 - NTS Misc Sales

The plants will be mapped as follows:

Plant Code DESCRIPTIONHO 1000 Flat Products Equipment (I) LTD- HOMfg 1100 Flat Products Equipment (I) LTD- TalojaMfg 1200 Flat Products Equipment (I) LTD- SilvasaHO 2000 NT Strips -HOMfg 2100 N T Strips & Automation Pvt Ltd- GhodbunderMfg 2200 N T Strips & Automation Pvt Ltd- Bhayendar

Following is the relevant Organization structure mentioned for SAP system.

Page 16 of 82

Company Code FPE NTS


1000 2000

Bhayendar (2200)

Plant

Project SAFAL

HO(2000)

Godbhunder (2100)

HO(1000)

Taloja(1100)

Silvasa(1200)


a. The Controlling area is 2000- Controlling Area CMI FPE.

b. Under the Controlling area there are two Company Codes- 3000 - CMI FPE LIMITED- 4000 - CMI Industry Automation.

c. The Plants & the Sales Organization associated with the Company code CMIFPE & CMI INDUSTRY AUTOMATION is as follows: Company Code

-3000- CMI FPE LIMITED -4000 -CMI Industry AutomationPlant -3100 - CMIFPE HO -4100 -CMI Indutry Automation HO-3200 - Taloja plant -4200 - Bhayendar Plant-3300 - Silvassa Plant

Purchasing Organization-3000 -Purchasing CMIFPE -4000 - CMI Industry Automation Sales Organization-3100 CMIFPE Domestic Sales -4100 - CMI Industry Automation Domestic Sales-3200 CMIFPE Export Sales -4200 - CMI Industry Automation Export Sales

-3300 CMIFPE Misc Sales -4300 - CMI Industry Automation Misc Sales

Page 17 of 82

Company Code FPE NTS


3000 4000

Bhayendar (4200)

Plant

Project PARIVARTHAN

HO(4100)

HO(3100)

Taloja(3200)

Silvasa(3300)


The plaCMI Industry Automation will be mapped as follows:

Plant Code DESCRIPTIONHO 3100 CMIFPE- HOMfg 3200 CMIFPE - TalojaMfg 3300 CMIFPE- SilvassaMfg 3400 CMIFPE- Navi MumbaiMfg 3700 CMIFPE-Taloja IITrd 3800 CMIFPE- ChennaiHO 4100 CMI Industry Automation -HOMfg 4200 CMI Industry Automation - GhodbanderO&M 4300 CMI Industry Automation - Jamshedpur

H.O- Head Office

Mfg- Manufacturing Plant

Trd- Trading Plant

O&M-Operation & Maintenance

Page 18 of 82


Page 19 of 82


Plant

Purchasing Organisation

Company Code CMI Industry Automation

4000

4100

Head Office

4200

Ghodbander

4300

Jamshedpur

Page 20 of 82


(B.2 ) : Project Objects with Structure

PS Process overview


Version Number: 1.0 Date: 05/09/2008Name of Business Process: Project Management- StructuresModule: Project System Sub module: Project objects with

StructureVersion Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table

B.2.01 AS-IS Process

There is no project object tool available in the present system. Till date the project software like MS project or Primavera was not used in the organization for project planning & monitoring.

B.2.02 TO-BE Process

SAP Project System uses the following project objects for the purpose of making the Project Structure planning & monitoring:

i. Project definition ii. WBS element iii. Network headers iv. Activity v. Activity elements vi. PS texts vii. Material components

I) Project Definition

The project definition contains default values and profile data for the WBS elements for example assignments to particular organizational units in the R/3 system. The basic dates for the entire project and the planning parameters for costs and dates are stored at the project definition level. The project definition thus forms a frame round the project.

Note: A project definition is not an account assignment object (that is, you cannot post to it).

In our case every customer project is unique with a defined basic start & finish date, defined revenue & cost associated for it. Thus for each customer there will be a unique Project definition.

Page 21 of 82


The Project definition contains the basic data, Control data, Administration data & long text.

Basic data: Under the basic data we can furnish the basic start & finish of a customer project which varies from 12 months-18months which is agreed between the customer & organization during the award. The required fields are description, Person responsible, start & finish dates which are made mandatory.

Control data: The control data requires the project profile. The Project profile is the most important profile for work break down structure & it contains default values and profile data for the project. The Project profile is mentioned in the appendix.

Page 22 of 82

Project Definition

WBS element

WBS Elements WBS Elements WBS Elements

Networks Networks Networks

Internal Activities

Gen. Cost Activities

Internal Activities

External Activities

Material Components


Administration data : It contains the user data and date like created by ( PS core),changed by ( PS consult) ,created on ( the day project definition is created), Last change (date on which latest changes made ) etc.

Long text: We can define the required project text in pages which is not available in the Project Definition screen.

ii) WBS element

WBS elements form the operative basis of a work Break down structure. WBS elements are the structure elements of the work break down structure .A WBS element describes a task or partial task that can be divided

WBS Elements inherit most of the Master Data from Project Definition.

a) Basic Data: Project Type – In our case the Project type is CP (Customer Project)

Basic Data: Project Type – In our case the Project type is

Sr.No. Project type Description

1 Z1 Rolling Mills

2 Z2 Coating Lines

3 Z3 Processing Lines

4 Z4 Finishing Lines

5 Z5 Miscellaneous/Modifications

6 Z6 CMI Projects

7 Z7 SPARE PROJECTS

8 Z8 SERVICE PROJECTS

Operative Indicators: The operative indicators are used to determine the controlling characteristics of a WBS element and define the tasks of the WBS element while realizing the project.

Planning Elements: WBS elements for which you want to plan costs are flagged as planning elements.

Account Assignment Elements: WBS elements for which we want to post actual costs are flagged as account assignment elements.

Page 23 of 82


Billing Elements: WBS elements for which we want to plan or post revenues are flagged as billing elements.

In our case we are checking in the operative indicators so that there will flow of all data from 4th level to top level WBS.

b) Dates:

Basic Start & Finish Dates with Duration & Unit Forecast Start & Finish Dates with Duration & Unit

Actual Start & Finish Dates with Duration & Unit

Calendar.

c) Assignments:

Organization:

CO Area Company Code

Plant

Currency

d) Control: Project profile for customer project.

iii) Network Headers

The network header of a network contains default organizational assignment data and control that applies to the entire network (similar to the Project definition for WBS elements).

A). Scheduling: Network header contains the field for basic start & finish of the networks as well as indicators for scheduling

Dates:

Release: Scheduled Actual Start Date Basic Scheduled Actual

Finish Date Basic Scheduled Actual

Scheduling:

Planning Type

Page 24 of 82


Scheduling Type

Reduction Indicator (Not Relevant)

Schedule Automatically

Capacity Requirements ( Not Relevant)

Exact Break Times (Not Relevant)

b). Assignments – Network header denotes the assignment to other object like Project definition, WBS element etc.

Allocation: Project Definition, WBS Elements

Organization:


Currency

c) Control

General:

Network Profile Network Type

Plant

Costing:

Costing Variant Plan Costing Variant Actual

Plan Cost Calculation

Components:

Reservation/ Purchase Requisition: Immediately / release / never. Never is used & the authorized person has to change to immediately for generating requirement.

iv) Activities

Activities in SAP Project system are categorized in four categories

Page 25 of 82


1). Internal Activities (With or without costing)

2). External Activities.

3). External Service Activities.

4). General Cost Activities

The control keys identify these activities in the system. Different Tab Screens Identifies type of activity & system will automatically opens the relevant screen for Data maintenance based on the selection of activity.

a) Internal Activities is maintained for in house work to be carried for the project Like we are manufacturing a assembly in our premises. In this control key is PS01 which governs the type of activity,

b). External: is used for procuring activities outside the organization .It incurs purchasing process. The control key used is PS02.

Page 26 of 82


(This Indicator specifies if any service exists for the activity or Operation)

We are not using the Purchase requisition generated from external activity & never is greyed out.

We are not using external activity in our organisation

c) External Service Activity or Service Activity

A Service master record is used to maintain the descriptions of all services that may need to be procured, with Unit of measurement and Rate per Unit. Also it can be indented via Requisition. The Control key is PS05 & service Master is required to be maintained by MM module.

Dates:

Page 27 of 82


All service activities procured for project should assign to the project, no manual purchase requisition should be generated.

d) General Cost Activity : Used to planning the of additional primary costs for example travel costs. (Planning can be done at WBS level & actual costs will be booked by FI at WBS level)

We are not using the general cost activity

v) Activity elements

Activities are given detail by activity elements. Activity elements have almost the same functionality as activities. All activity elements have a date reference to the activity to which it is assigned. They do not affect the scheduling & do not have any relationships or durations.

In case of we can detail our activity Manufacturing of assembly recoiler by activity elements for detailing purposes. It functions same as activity with restrictions like assigning material components, scheduling etc.

Note: You cannot assign material components or relationships to the activity elements.

We are not using activity elements in the project

vi) PS texts

Ps text is similar to word file. We can enter PS text for each WBS element or activity. We can create the texts in SAP script editor or with Microsoft word.

vii ) Material Components

Material components can be either defined in the Material Master.

The material master contains information on all the materials that a company procures or produces, stores, and sells. It is the company's central source for retrieving material-specific data.

Material component can be assigned directly to the activity. It is required to define the item category and the procurement parameters.

In case of item category you have two options: 1) If you do not want to include the components in Inventory management but want to use them immediately in the network, choose item category (N), 2) If you want to post the components to a ware house & use the components in the network at a later stage, choose item category (L).

Initially we get the default values for procurement indicator; however we can change based on our requirement. The various options available for non stock item (N) & stock item (L) is as follows:

Page 28 of 82


---- Non Stock item (N) (No inventory Management)

You can choose between the options as Purchase requisition for network or Third –party order i.e. Block Transfer / Third Country i.e. from vendor to customer.

---- Stock item (Stock item)

You can choose between the options as Purchase requisition & reservation for WBS element or Reservation for network or planned independent requirement for WBS element.

Based on the project objects as per the SAP Process, the following is the structure of the project structure along with project objects.

a) The Project definition will be the customer project number given by the design department which is four digit number. We shall enter the basic start & finish date of the project before the detailed project planning. Based on the project profile defined, all the default values will be stored in the project definition level for use in further WBS elements or structure.

Every Project is a unique for a customer and for which different Projects, spare orders etc is treated as an individual project.

Page 29 of 82


The proposed project structure will be as follows:

Page 30 of 82

Customer Project

Proc. Bought out

Design Manufacturing

Assembly-2

Assembly-1

Assembly -10

Ist level WBS

2nd level WBS

3rd level WBS

Sub- Assembly-(1A)

Sub Assembly-(1B)

Sub Assembly – (1C)

Sub Assembly- (2A)

Sub Assembly-(10A)

Project Definition- Customer Project

4th Level WBS


b) The first level WBS element is the customer project number as defined in the project definition. It shall be the root WBS with operative indicators (Planning, Account Assignment & Billing element).

c)The second level WBS element is the function or logical unit within the organization i. e Sales ,Design ,Procurement Bought out, Manufacturing ,Erection & commissioning etc with operative indicator Planning, Account Assignment.

The second level WBS element is the function or logical unit within the organization i.e. Design, Third party, Manufacturing –Taloja, Manufacturing – Silvassa, unplanned costs, expenses, Erection & commissioning etc with operative indicator Planning, Account Assignment and billing element.

Page 31 of 82


d) The third level WBS element will contain the assemblies under the Procurement Bought out, Manufacturing, Automation, Hydraulics etc. with operative indicators planning, account assignment.

The third level WBS element will contain the assemblies under the Procurement Bought out, Manufacturing, Automation, Hydraulics etc. with operative indicators planning, account assignment and billing element and assignment of material components as per the billing schedule.

e) The fourth level WBS element is the sub-assemblies of the assemblies. Network activities with material components are assigned to

The fourth level WBS element is the sub-assemblies of the assemblies. Network activities with material components are assigned as per the billing schedule

f) The network header is assigned to the first level WBS element or as required within the structure. We can give the basic dates for start & finish i.e the Project start & finish date committed to the customer.

The network header created automatically when ever we assign activity to WBS element or as required within the structure.

g) We shall define activities with relationships within the network along with the normal duration for scheduling.

h) Regarding the types of activities, all the in-house manufacturing activities are internal processing, Procurement BO as external processing etc

i) Scheduling is carried out with network determines the dates & scheduling type is forwards or backwards as per the requirement.

Page 32 of 82


(B.3): Coding Mask

PS Process overview


Version Number: 3.0 Date: 10/6/2006Name of Business Process: Project Management- StructuresModule: Project System Sub module: Coding MaskVersion Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table

B.3.01 As- Is Process

As per the requirement & part of standardization, the design department has furnished the number range for projects & for use in the SAP system.

Based on the drawing number furnished by the design department for SAP system

1001 2000 ROLLING MILLS2 HI, 4-HI, 6-HI, SPM, HSM,TWIN STAND, TANDAM MILL ETC.

2001 3000 COATING LINES CGL, EGL, CCL, ETL, ETC

3001 4000PROCESSING LINES

PICKLING, ECL, ARP

4001 5000 FINISHING LINESREWINDING, CTL, SLITTING, TENSION LEVELLING, CORRUGATING M/C, ROLL FORMING ETC

5001 6000 MISCELENEOUSREVAMP / EQUIPMENT SUPPLY IN EXISTING LINE e.g. TENSION LEVELLER, PAY-OFF ETC.

XXXX-YYY-ZZ-XX

XXXX PROJ NO 1001 TO 9999

YYY ASSY 001 TO 999

ZZ SUB-ASSY 01 TO 99

XX SHEET NO A1 FOR ASSEMBLY DRG

B1...8 TO Z1…8 FOR DETAIL DRGS

e.g.

1001-010-15-B6

Page 33 of 82


B.3.02 To- Be Process

Project coding mask

Project coding mask serves as a display option for complex project numbers.

In this case the project coding mask will be defined in the following way

Prj ID Coding Mask DescriptionStart & end four digit number

R - 0000.0000.000.00 Coding mask for Rolling Mills1001 to 2000

C -0000.0000.000.00 Coding mask for Coating lines2001 to 3000

P -0000.0000.000.00Coding mask for Processing lines

3001 to 4000

F -0000.0000.000.00Coding mask for Finishing lines

4001 to 5000

M -0000.0000.000.00Coding mask for Miscellaneous

5001 to 6000

N -0000.0000.000.00 Coding Mask for NTS Projects 1001 to 6000

In the above scenario, following are in the indications of the coding mask,

i) The first letter R, C, P, F, M & N stands for the projects pertaining to Rolling mills,

Coating lines, processing lines, Finishing lines, Miscellaneous & Projects pertaining

CMI INDUSTRY AUTOMATION .

ii) -0000.0000.000.00 - The underlined four numeric digits indicates the project number

for the customer as given by the design department. In our case, it will denote the

Project definition & First level root WBS element.

iii) -0000.0000.000.00 - The underlined four numeric digit indicates the function or the

departments in the project structure i.e Sales(1000), Design(2000),

Manufacturing(3000), Automation(4000) , Electrical

( 5000),Hydraulics(6000),Erection & Commissioning(7000) etc . In our case , it is the

2nd level WBS element which is assigned to First level WBS element.

iv) -0000.0000.000.00 - The underlined three alphanumeric digit indicates the assembly

i.e. like Uncoiler (010), Recoiler (015) as defined the by the design drawing. In our

case, it is the third level WBS element which is assigned to the 2nd level WBS

element .Further the 2nd level is already assigned to Ist level WBS (Customer

Project).

Page 34 of 82


v) -0000.0000.000.00 – The underlined two alphanumeric digits at the end of the mask

indicate the sub –assembly as defined by the design drawing. In our case it is the

fourth (4th Level) WBS element which is assigned to the 3rd level WBS element

(Assembly). Further the 3rd level is already assigned to 2nd level WBS element

(Manufacturing / Procurement -BO) & 2nd level WBS is already to Ist level WBS

element (Customer Project).

vi) Example for the Project coding mask is R-1023.3005.010.00 Indicates the Rolling

Mill with Project number 1023, involving manufacturing 3005 & assembly

number 010 & sub-assembly -00

Project coding mask

Project coding mask serves as a display option for complex project numbers. Since previously

different types of projects are defined in different number ranges. Now standardise the prefix of

the project as follows

In this case the project coding mask will be defined in the following way

Prj ID Coding Mask Description

Z - 0000.0000.XXX.XX Coding mask for CMI FPE

T -0000.0000.XXX.XXCoding mask for CMI Industry Automation - Mechanical

A -XXXXXXX.0000.XXX.XXCoding mask for CMI Industry Automation- Automation

0 – numerical valuesX – Alphanumerical Values

Page 35 of 82


PS Process overview

Page 36 of 82


(B.4) Project Tools- Project Builder, Project Planning board


Version Number: 1.0 Date: 15/1/2006Name of Business Process: Project Management- StructuresModule: Project System Sub module: Project Tools-Project

Builder, Project Planning boardVersion Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table

B.4.01 As-Is Process

Till date the existing software tools like MS Project or Primavera was not used to plan & monitor the Project. There is no legacy data available for the Project planning & monitoring.


We shall be using the project tools provided by SAP Project system i.e., the Project Builder & Project Planning board.

Project Builder

i) The Project Builder is a clearly –structured tool in SAP Project System (SAP PS)

that is extremely user friendly and allows projects to be edited quickly and efficiently.

It covers almost 90 to 95% Functionality of the Project System Module.

ii) The Project builder consists of window divided into three areas: the structure

overview is in the top left of the window(Ex. Symbolic view of Project structure

Pickling line of WBS elements, Network, Activities) , the work list on the bottom left ,

and on the right is an area for displaying and editing data.

iii) The structure overview (top left of the window) contains the selected project data.

The work list tab (bottom left window) contains the list of last five projects edited; the

templates tab (bottom left window) contains project objects which can be added to

the project with further integration. The work area (right area of the window) displays

a detail view of the selected object directly.

Page 37 of 82


SAP AG 1999

Project Builder

Project Edit Goto Extras Settings System Help

Project - E-1145

Project structure: Identification

Templates: Identification

Identification and view selection

WBS element

Detail

Overview(s)

Engineering

Basic data Dates Assignments Control User fields Administr.

Proj. type

Priority

System status REL

Short ID

Project sum.

Responsibilities

System status

Responsibilities Operative Indicators

Respons. person

Applicant no.

Resp. cost cntr

Req. cost center

Req. co. code

Planning element

Acc. assign. element

Billing element

Grouping WBS el.Individual objects

Project definitions

WBS element

Network

ActivityActivity element

Material components

Milestone

PS text

Documents

Worklist and

Templates

Currentproject

Selectedobject

Detail Screenof objectselected

Overviewsof objectselected

iv) We can use work area to edit the individual project elements. We can navigate

between the various views (detail views and overviews), graphics, and project

planning board quickly and efficiently in the Project builder in order to maintain the

structures.

Project planning board

i) The project planning board is a graphical interface for creating and maintaining

project data: Project definition, WBS elements, activities, relationships, milestones,

PS texts. It is based on an interactive SAP Gantt chart and is especially suitable for

scheduling and monitoring. It also serves the 95 % functionality in Project System

module.

Page 38 of 82


ii) The planning board consists of the table area, diagram area and shows the

hierarchical set up of the project and corresponding scheduling situation. Along

with the dates view, we can show or hide the various other overviews of the project

in the lower part of the Gantt chart, such as capacity overview.

iii) The entire period we see in the project planning board is called the evaluation

period. The evaluation period consists of pre-evaluation period (prior to project

start), a planning period (Project period), and a post-evaluation period (after

completion of project).

iv) The planning board profile determines the appearance of the planning board. We

can adapt the graphical display of the project planning board to our needs by using

the project planning assistant. It is available as tool bar on the application.

Page 39 of 82



Version Number: 1.0 Date: 10/1/2006Name of Business Process: Project Management- LogisticsModule: Project System Sub module: SchedulingVersion Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table

B.5.01 As- Is Process

It does not reflect the Schedule of the project .However till date it is managed with knowing the

start & end date of the project. The schedule of the project was not known as the project

planning & monitoring was not implemented.

B.5.02 To-Be Process

i) Project Dates ( Can be done using project tools Project builder, Planning board or transactions mentioned in SAP Process tree)

The following types of dates are available in the system, and occur at all levels:

Basic dates are defined manually, and are often binding for lower-level objects. In case

of maintaining the full project, enter basic dates in Project definition which is unique for

any customer project.

Activities can be fixed by means of time constraints. In case, use types like Must start on

/Must finish on.

Scheduled dates (or earliest and latest dates for activities) are determined automatically

when network activities are scheduled. Scheduled dates are determined for WBS

elements by summarizing the scheduling data of the corresponding activities.

In the realization phase of the project, actual dates are set by entering actual dates for

WBS elements, or by confirming activities.

Forecast dates are a means of storing a specific scheduling scenario for information

purposes.

ii) Scheduling

Each time a network is scheduled; the system carries out forward and backward

scheduling and determines floats (if activated) and capacity requirements.

Page 40 of 82


Forward scheduling determines the earliest dates.

Backward scheduling determines the latest dates. Floats occur if the earliest dates are different from the latest dates.

The scheduling results:

Scheduled start and finish for the network header.

Earliest start and finish dates (earliest dates) and the latest start and

finish dates (latest dates) for

the activities.

Earliest and latest dates for the relationships.

Float times (total and free float) for the activities.

(Use project planning board which is based on Gantt chart is most user friendly in case of Scheduling)

iii) Scheduling –Duration

When scheduling internally processed activities and general costs activities, the system

uses the normal duration you maintained in the activity.

When scheduling externally processed activities, the system uses the number of

planned delivery days you maintained for an external activity. You can, however, also

use the normal duration from the internal processing screen of the external activity if you

activate this explicitly in the control key of the external activity.

Scheduling interprets the time interval for relationships as the minimum time interval.

When calculating the dates, scheduling can increase the time interval but not reduce it.

iv) Actual Dates for WBS & Activities

If You do not have details on dates for a WBS element in date scheduling via activities,

the following conditions apply to maintaining actual start and finish dates:

You can always maintain the actual start.

You can only maintain the actual finish if all lower-level WBS elements have an

actual finish date .In other terms the Work Manufacturing cannot be completed

unless all the associated assemblies are finished.

If we have details on dates for a WBS element in date scheduling via activities, the

following conditions apply to maintaining actual start and finish dates:

We can only maintain the actual start if the activity has the status "partially released"

or "released".

Page 41 of 82


We can only maintain the actual finish date if all the lower-level WBS elements also

have an actual finish date and all the activities for the WBS element have the status

"Finally confirmed

Actual dates are entered in networks by confirming activities. This can be carried out

using individual, collective confirmations, etc.

Once an activity has been finally confirmed, the earliest and latest dates match the

actual start and actual finish dates.

Partial confirmations affect the scheduling result for the earliest date in accordance with

the "shift order" indicator.

The "shift order" indicator is not set. The actual start date and forecast duration of the

partial confirmation are taken into account when the earliest date is calculated.

The "shift order" indicator is set: Neither the actual start date nor the forecast

duration of the partial confirmation is taken into account when the earliest date is

calculated.

To call up an overview of our planned dates at a certain point in time (baseline), you can

use either project versions.

v) Confirm activities.

You can confirm one activity or activity element using an individual confirmation. You

enter the data on the detail screen. The data includes for the actual start, actual finish or

duration in the confirmation screen activity. On the display mode you can know the

confirmed activities & you can also cancel/reverse the confirmation.

To get the progress of activities in the projects, we should confirm the activities in the

projects; without confirmation of activities we cannot close the project. We should select

each and every activity in a project and confirm

Page 42 of 82


(B.6)- Material Components to WBS/activities and Delivery from Project.


Version Number: 3.0 Date: 10/6/2006Name of Business Process: Project Management- LogisticsModule: Project System Sub module: Material Components to

WBS / Activities & Delivery from Project.

Version Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table


It does not contain the Materials required & delivered for the customer project in total.


i) We are maintaining the project through project builder with WBS elements along with activities.

We are doing the planning & monitoring of the project in total. As per the structure defined by us

earlier, the third level Work Break down structure / package is the assembly. All our monitoring

is based on the assembly wise. In case if required it can be further divided to fourth level Work

Break down structure (i.e. Sub-assembly level).

The material component / BOM can be assigned to the WBS element with the activity

associated to it. To make our structure complete for the project all the material component /

BOM should be assigned to WBS element or the Project in totality.

This assignment to activity of the WBS serves the following purposes:

The requirement quantity & date is given by which the material is required for the

activity. During the scheduling run if the activity is delayed then the requirement date of

the material component is delayed accordingly. We can set an offset to the finish date of

the activity so as to maintain the buffer.

Based on the requirement the system will generate the purchase requisition for non-

stock item & reservation for stock item.

Based on the reservations, the MRP run will be carried out for which planned order and

purchase requisition will be created.

Page 43 of 82


The materials to the customer can be delivered from Project. For the material to be

delivered from Project, the deliverable materials should be available in the project stock

which states it is a special stock for projects.

ii) The Materials for the project system has integration with MM & PP module.

To plan the material requirements for a particular project, we can assign material to the activities. The system differentiates between stock items (item category L) and non-stock items (item category N).

Stock items are entered for materials that are kept in stock (warehouse, sales order, or

project stock). Reservations are generated for stock items. Based on the reservation,

MRP is run under the PP module.

Non-stock items are entered if materials are to be procured directly for the network (that

is not using MRP). Purchase requisitions are created for non-stock items. These

requisitions are passed directly to Purchasing.

Material Plant Item category Procurement indicator

Remarks

Material produced

1100/1200/2100/2200

L ( Stock item) 130 Reservation for WBS .

Material with Procurement type F or X

1100/1200/2100/2200

L ( Stock item) 131 Purchase requisition generated from Project

Material with Procurement type E,F or X

1100/1200/2100/2200

L(Stock item) Remove default indicator (130) & put blank

On selecting third party WBS, Acc cat. Z will be made with PR & add custom add.

BOM to be exploded & assigned for third party

1100/1200/2100/2200

L(Stock item) Remove default indicator (130) & put blank

On exploding BOM, top item is text, child compo with Acc.cate N is assigned for TP

Page 44 of 82


Material Plant Item category Procurement type RemarksMaterial to be produced plant

3200/3300/3700/4200

L ( Stock item) Reservation for WBS

Material Procured from vendor and kept stock

3100/3200/3300/3700/4100/4200/4300

L ( Stock item) Preliminary purchase requisition for WBS element

Material Third party procurement

3100/3200/3300/3700/4100/4200/4300

N(Non Stock item)

Third party order for procurement

Now we have taken the approved billing schedule in to SD module. We should procure the components and delivery of components with the coincidence of the billing schedule. We have listed different types procurement process in corporate the sequence of steps to be followed in the detailed document in annexure.

SAP AG 1999

Integration with MM and PP:

Reservation(MRP)

PPPP MMMMMMMM

Purchaserequisition

DefinitionDefinition

Item categoryItem categoryItem category

Stock itemStock item"L""L"

NonNon--stock stock item "N"item "N"

Material required for performingan activity or manufacturinga product

MaterialMaterialMaterial

Page 45 of 82


iii) Procurement using Requirement planning stock items. (L)

The item category "stock item" ("L") is used for components kept in stock. When we

save, the system creates a reservation for the required material.

The main function of material requirements planning is to ensure material availability i.e.

It uses the Inventory Management to check the stock for availability (in other words, to

procure the required quantities on time - both in-house and for sales). This includes

monitoring stocks and, above all, creating procurement proposals for purchasing and

production.

We have assigned the material component to activity i.e. it contains the name of the

material, requirement quantity, item category as stock item (L). This trigger

requirements planning. In order to cover the requirements, order quantities and dates

have to be determined, and the corresponding procurement elements scheduled. The

procurement element for requirements planning is a planned order and, for external

procurement, a purchase requisition. Also, the dependent requirements for materials

produced in-house (in other words, the quantity of components required to manufacture

the assembly) are determined by exploding the bill of material. Planned orders are

created at each BOM level to cover requirements when a material shortage occurs.

( MRP is not relevant in PS module as the same will be done by the Production module)

Page 46 of 82


SAP AG 1999

Procurement Using Requirements Planning, Stock Item


“L”

Material component procured via requirements planning.

Reservations are generated for stock items.

Item category

“L”

Materialreservation

MRPrun

Planned order/purch. req.

Convertplanned order/

purch. req.

Order/purch. order

handling

Warehousereceipt

Materialwithdrawal

Once quantities and dates have been planned in requirements planning, these planned

procurement elements are converted into "exact" procurement elements: for production,

this is the production order and, for external procurement, the purchase order by the

respective modules of PP & MM.

Page 47 of 82


SAP AG 1999

Total Purch.

Components

Item Material Plant Quantity Un Procurement Item cat Res. SLoc Description Reqs date ST FD RD

Cabin door

Engine Unit

Assigning Stock Items

T-20600

1

1 10.01.2000

Committed quantity

General data

General data

Proc. param. Long txt

Req. quantity

Req. date

Reservation

Recipient

Unloading point

Offset

Withdrawal quantity

13406 1 Reservation for WBS element

Manual req. date

Algn.Startdate.Comp

Align finish date

CostRel

UnitCost

Storage location

Batch

Sort string

ProcurementUnit cost.

1 PC

10.04.2000

In the above detail screen of component assignment for stock items with item category L

as mentioned, we can select the "General data" tab page to change the requirements

date, check the withdrawal and confirmed quantity, and check the reservation number.

On the "Procurement parameters" tab page, we can determine when the reservation will

take effect for planning.

The reservation either takes effect a) immediately, b) after release, or c) never. In case

of case c) this enables us to release the activity but leave the reservation inactive for

planning. We can make the reservation active for planning at a later stage.

Page 48 of 82


iv) Direct procurement of items i.e. Non stock items (N), which implies material procured

directly by means of activity

SAP AG 1999

Direct Procurement, Non-Stock Items


“N”

Material procured directly by means of the activity.

Purchaserequisition

Bidinvitation

Entry ofquotation

Vendorselection

Orderprocessing

Purchase order

monitoring

Invoiceverification

Item category

"N"Goodsreceipt

Page 49 of 82


Non-stock item (N): where in Direct Purchase is involved without inventory

management.

The item category "non-stock item" ("N") is used for components that are not procured

by way of warehouse stock, project stock, or sales order stock, but are procured directly

by the network activity.

Purchase requisitions are created for these components. These requisitions are passed

directly to Purchasing. When the goods are received, they are not placed into stock, but

posted to the activity.

Non-stock items cannot be managed as project stock.

SAP AG 1999

Assigning Non-Stock Items

Total Purchasing

Components

Item Material Plant Quantity SU Procuremnt Item cat Res. Lag. Description Req. date ST FD RD

Cabin Door

Engine Unit

General data Purch. data Procmnt par. Long text

PReq Invoic. plan Unit costing Procurement PS text

Req. tracking no

Purch. data

Purch. requisition

Req. quantity

Req date

Offset

Purchasing group

Info record

Outl. agreement

Vendor

Material group

Requisitioner

Unloading point

POrg

PR for network

Costing

Unit costing

Man. requirements date

Align. finish date

Algn. Startdate. Comp

Price/currency

Price unit

UNI

FixPrice

G/L account

GR proc. time DelTime (T)

Sort string

Recipient

1002

If we choose direct procurement with item category N, we can choose between two

procurement types: Either "purchase requisition for the network" or "third-party

requisition for the network". The procurement type is displayed on the "Purchasing data"

Page 50 of 82


tab page on the detail screen for the assigned component. We can change the

procurement type at a later stage.

The purchase requisition number is displayed on this tab page. We can call up the

purchase requisition directly from here. If a purchase order is already available, its

number will be displayed on the "Procurement parameters" tab page. We can also call

up the purchase order from here.

In the Information system for materials in project system, we can know the reservations,

Purchase requisitions, purchase orders for the project i.e. WBS element, Network,

activity.

v) Delivery of items from Project.

SAP AG 1999

Delivery

PPP

P -1P P --11 P -2P P --22

Withdrawalquantity

SD SD

Sales orderSales orderDelivery noteDelivery note

Picking andgoods issuePicking andgoods issue

Quantity indelivery

Selecting thematerial

Orderdata

(optional)

AssemblyAssembly

After the assembly is manufactured in house, through Production order the assembly is

posted to stock & it has to be transferred to project stock.

Page 51 of 82


We can select material components that are to be delivered to the customer and create

an SD delivery note. Billing will be done in the SD module.

We can select components by specifying the project definition, the WBS element, a

sales order or a network.

By selecting the deliveries, we can select the delivery created .On the picking tab page

we can select the Pick quantity field to enter the delivered quantity. Further the goods

issue is to be done. All the Billing related item will be covered in the SD module.

By this case, the Project stock which was build up due to the production process of the

assembly is reduced due to by the goods issue from delivery.

After the assembly is manufactured in house, through Production order the assembly is

posted to stock & it has to be transferred to project stock.

Select the material components from sales order line items and delivery should be done

from sales order. With respect to the delivery Billing will be done in the SD module.

By this case, the Project stock which was build up due to the production process of the

assembly is reduced due to by the goods issue from delivery.

Page 52 of 82


(B.7) Procurement of Bought out items


Version Number: 1.0 Date: 12/1/2006Name of Business Process: Project Management- LogisticsModule: Project System Sub module: Procurement Bought

out items Version Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table


i) The Project department is involved in the procurement for Bought out items for the

customer project. It receives the BOM/drawings for the design department.

ii) The Bought out items are either for manufacturing of the assembly in house or Block

transfer i.e. sending from the vendor to the customer directly without coming to the

premises.

iii) The Bought out item is checked with stock & if the same is available then it is

informed to stores to reserve for the project.

iv) If the Bought out item is not found in stock, it is classified under two heads like long

lead items which is planned manually and other normal Bought out items through the

existing system.

v) Enquires are floated and quotations are received from the approved vendors.

vi) Technical evaluation & comparison of technical specification, Price Payment terms

along with purchase department & Design.

vii) Order is finalized with the purchase department for final approval.


i) Under the SAP system, it is related to the Material Management module.

In this procedure the MRP controller will be identified as Projects in the material

master created in the system.

ii) Following are the brief terms relevant to the Purchasing of materials.

a) Purchase Requisition

Page 53 of 82


A Purchase Requisition is a request or instruction to Purchasing to procure a certain

quantity of a material or a service so that it is available at a certain point in time. This is

an internal document and not used for outside communications.

Purchase requisition can be generated manually or By Automatic Assignment of Requirements

to Orders or Operations.

All Purchase requisition created manually will set for a release, which will be approved by

Authorized Person.

b) Request for quotation

A Request for Quotation (RFQ) is an invitation extended to a vendor by a purchasing organization to submit a quotation (bid) for the supply of materials or performance of services

c) Price comparison based on Quotations:

The Quotation received from the vendor is maintained in the system. The Price comparison is based on the minimum value/mean value comparison of the quotations.

d) Procurement of Non-stock bought out items: (Partly relevant for Projects & Purchase)

Page 54 of 82


Non-stock materials are not taken into inventory. The amount incurred in purchase is expensed

out. For any such Ad hoc requirements the procurement process may be with or without

material masters.

Purchase requisition will be created with an account assignment. Ideally account assignment

would be “N” which specified\s the Network with Activity. G/L account and the Network of the

Project for the specific requirement are filled in the PR.

Purchase requisition created will set for an approval process, which will be approved by the

Authorized person. Approved purchase order will be converted to purchase order. The Head of

Projects will approve purchase order.

Goods receipt will be done with reference to the purchase order.

e) Procurement of stock bought out items: (Partly relevant for Projects & Purchase)

Procurement of materials/Services required for projects will be routed through Materials

Management module.

Materials can be procured for stock as well as for consumption in Projects.

Procurement of project stock is identified in the system by the use of Account assignment (Q)

defined in the Purchase Requisition or Purchase Order.

Procurement cycle for project is similar to all other procurement process.

PO will be generated referring to the PR and for the approved Vendor.

PO created will set for a release by the purchase department with approval from projects.

For the third party order we should do logical GR and do invoice verification and no delivery for the third parties.

Page 55 of 82


iii) Under the above conditions the MRP controller Projects will be handling the purchasing

process. As defined earlier in the purchasing cycle, it involves the Request for quotation of

bought out item from vendors, Receipt of quotations from vendors, Price comparison and

evaluation, selection of vendor based on quotation comparison & final Purchase order will be

placed by the Purchase Department.

Page 56 of 82


(B.8)- Planned and Actual Costs


Version Number: 1.0 Date: 16/1/2006Name of Business Process: Project Management- AccountingModule: Project System Sub module: Planned and Actual

costs in PS structureVersion Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table

B.8.1 As-Is Process

The costs for individual projects are not available in the present system.

B.8.2 To –Be Process

i) As defined in our earlier Processes, we have created the structure of the project

based on the customer. The structure of the project includes the WBS elements ( i.e.

First level for the customer project with one root,2nd level is the function

/department/logic functions like Sales, Design, Manufacturing, Procurement – BO,

Erection & Commissioning etc, 3rd level is the Assemblies under the Manufacturing

or Procurement-BO)

As defined in our earlier Processes, we have created the structure of the project

based on the customer. The structure of the project includes the WBS elements ( i.e.

First level for the customer project with one root,2nd level is the function

/department/logic functions like Design, Manufacturing -Taloja, Third party,

Expenses, unplanned costs, Erection & Commissioning etc, 3rd level is the

Assemblies under the Manufacturing or Procurement-BO)

ii) The WBS elements are known for the particular project within the organization.

iii) All the relevant modules in SAP i.e. PP module, CO module, MM, SD module shall

be assigning their orders to the relevant WBS element defined in the structure. In this

scenario, the costs of the orders from the respective modules will be assigned to the

WBS element. This gives rise to the planned cost for the WBS element. Due to the

hierarchical structure of the WBS elements, the planned costs will be rolled up to the

top WBS element giving the planned costs in total.

iv) Regarding the actual costs, it is based on the actual costs incurred in the relevant

modules in SAP. All the costs will be aggregated to the top WBS element.

Page 57 of 82


v) We can know the hierarchal based i.e. WBS element wise planned /actual costs from

the Information system of financials.

i) For planned costs, by using unit cost planning under CO Version 1 WBS

element wise detailed cost planning will be done.

ii) Regarding the actual costs, it is based on the actual costs incurred in the

relevant modules in SAP. All the costs will be aggregated to the top WBS

element.

iii) To analyse the variance between plan and actual cost of project, select plan

version for 1 and actual costs and revenues will default come from version 0

Page 58 of 82


(B.09)- Project Version.


Version Number: 1.0 Date: 17/1/2006Name of Business Process: Project Management- StructuresModule: Project System Sub module: Project Version(Base

line Project)Version Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table

B.09.1 AS – IS Process

There is no existing mechanism to prepare the base line programme for any customer project &

monitor the project based on baseline Programme.


i) In the SAP system, we are creating any project; say the Pickling line after award of

the order from clients by sales department.

ii) We can get all the inputs from the existing similar projects or design /create the

structure based on the contractual start, finish of project assemblies to be

dispatched, scope of work at client location etc.

iii) The initial plan or structure which is agreed upon is the base line programme. In SAP

system the same can be stored as Project Version.

iv) In Simple terms, the Project version is the snapshot of the project at any specific

point of time for documentation. It cannot be changed. It stores the data existing at

that point of time.

v) After creating the Baseline Programme, we shall store it using the Project Version.

As our operative Project is dynamic this is based on the latest scheduled dates,

actual dates, etc. In this scenario, we can compare it with the base line stored as

Project version.

vi) Additionally, during the course of the Project as and when required, we can create

Project version to know the status of the Project at that particular point of time.

Page 59 of 82


(B.10) Project Closing


Version Number: 2.0 Date: 06/10/2008Version Management This Document is subject to change control. Every change of the document has to undergo change control procedure and has to be registered in the following table


There is no concept of project closing in previous system.


vii) In the SAP system, once the activities under WBS elements are completed and

confirmed, we will technically close the WBS element.

viii) We can technically close the WBS elements individually or we can technically close

the total WBS elements at a time

ix) Once the WBS element come to technically close and all the transactions pertaining

to the WBS element is complete, then we will close the WBS element.

x) Once all the WBS elements in a project are closed, finally we will close the project

Page 60 of 82


(B.11) Status Management




In previous system, status management was created to control the business processes.


I. Status management is used to control the business processes

II. As well we can status management without to know the progress of the activities in the

reports.

III. Status management without number are created as follows

Ass - Assembly

Des - Despatch

Drg - Drg / Engg Issue

Ins - Inspection

Man - Manufacturing

Pro - Procurement

Page 61 of 82


(B.12) Workcenters



B.12.01 As-Is Process

In previous system, no concept of work centre


In present system, we are using work centre concept is to capture the cost of internal activities and required for confirmation of activities where the actual costs not to be calculated but required to get the progress of activity with order quantity(Procurement scenarios). The following are the work centres created under different plants.

Sr.No. Work Centre Work Centre Description Plant1 DESGFURN Design - Furnace 31002 DESGMECH Design- Mechanical 31003 DESGPROC Design - Processing 31004 PROJDMUM Projects Dummy-mum 31005 PROJELEC Project - Electrical 31006 PROJMECH Project - Mechanical 31007 PROJSYST Project - Systems 31008 ERENCOMM Erection & Commissioning 31009 PROJDTLJ Projects Dummy-Taloja 320010 PLTALOJA Planning Taloja 320011 QATALOJA QA Taloja 320012 PROJDSIL Projects Dummy-Silvassa 330013 PLSILVAS Planning Silvassa 330014 QASILVAS QA Silvassa 330015 QATALEXT QA Taloja II 370016 AUTONMFG Automation Non Manufacturing 420017 AUTOTHER Automation Others 420018 PLGODH Planning Ghodbander 420019 PRSGODH Pre- Sale Activity Ghodbander 420020 QAGODH Quality Ghodbander 420021 RDPRJMEC R&D Project Mechanical 4200

Page 62 of 82


(C)SAP Process Tree

Business Scenario

Process Groups

Business Processes

BPP

Project SystemProject Structure

Project Builder

Building a new Project (CJ 20 N) involving all objects like WBS, Network, Activities, Activity Elements, Material Components, Milestone, and PS texts etc.

Project Planning Board

Creating a new Project (CJ 27) using the Gantt chart board & Project objects.Making Changes to existing Project ( CJ2B)Viewing a Project but changes cannot be made i.e. Display Project ( CJ2C)

Work Break down Structure

In case of WBS only ,Create WBS ( CJ01)

Change WBS ( CJ02) Display WBS ( CJ03)

Project Definition Create Project Definition ( CJ06) Change Project Definition ( CJ07) Display Project Definition ( CJ08)

Network In case of network only, Create Network ( CN21) Change Network ( CN22) Display Network ( CN 23)

Project version Used for creating the base line i.e. Create Project version using Structure overview ( CN71)

Scheduling Basic DatesAfter the Project is created, in case basic dates is be changed then Change Basic dates ( CJ21)Display Basic dates ( CJ22)

Forecast DatesAfter the project is created in case forecast dated is to be changed then Change Forecast Dates ( CJ23)Display Forecast Dates ( CJ24)

Actual Dates Change Actual dates ( CJ25)

Page 63 of 82


Display Actual dates ( CJ26)Project Scheduling Project Scheduling (CJ29)Network Scheduling Overall Network Scheduling ( CN24)Individual Confirmation

Create Individual Confirmation (CN25)

Display Individual Confirmation(CN28)Cancel/Reverse Confirmation (CN29)

Collective Confirmation

Collective Confirmation (CN27)

Capacity Planning

Work Centre Master Record

Create Work Center(CNR1)

Change Work Center(CNR2)Display Work Center(CNR3)

Work center view View based on Load(CM01),Variable (CM07),Extended work center view (CM50)

Project view Project view based on WBS element (CM53)

MaterialMaterials in Project & Delivery

Stock/Requirement List ( MD04)

Project-Oriented Procurement (CNMM)Delivery from Project (CNS0)

Procurement- Bought out

Purchase requisition Creation of Purchase requisition (ME51N)

Change of Purchase requisition(ME52N)Display of Purchase requisition(ME53N)

Quotation & RFQ Maintaining Quotation & RFQ (ME41,ME47)Changing RFQ’S (ME42)Display RFQ’s(ME43)Price Comparison for Quotations by Different vendors(ME49)

Contract Creating Contracts (ME31K) Displaying Contracts(ME33K) Changing Contracts(ME32K)

Reservation Creating reservation manually (MB21)Displaying reservation (MB23)Changing reservation (MB22)

Business Scenario

Process Groups

Business Processes

BPP

Project SystemProject Structure

Project Builder Building a new Project (CJ 20 N) involving all objects like WBS, Network, Activities, Activity

Page 64 of 82


Element, Material Components.

Project version Used for creating the base line i.e. Create Project version using Structure overview ( CN71)

Scheduling Project SchedulingProject Scheduling will be done in project builder (CJ20N)

Individual Confirmation

Create Individual Confirmation (CN25)

Confirmations will be done through project builder (CJ20N)Cancel/Reverse Confirmation (CN29)

Capacity Planning

Work Centre Master Record

Create Work Centre(CNR1)

Change Work Centre(CNR2)Display Work Centre(CNR3)

Work centre view View based on Load(CM01),Variable (CM07),Extended work centre view (CM50)

Project view Project view based on WBS element (CM53)Material Procurement

Material procurement will be done by assigning materials to activities in projectsProject-Oriented Procurement (CNMM)

DeliveryDelivery of assemblies and sub assemblies will be done from sales order (vl01n)

Quotation & RFQ Maintaining Quotation & RFQ (ME41,ME47)Changing RFQ’S (ME42)Display RFQ’s(ME43)Price Comparison for Quotations by Different vendors(ME49)

Contract Creating Contracts (ME31K) Displaying Contracts(ME33K) Changing Contracts(ME32K)

Page 65 of 82


(D)PS SAP Standard Reports

Standard Reports available in SAP – PS

SL DescriptionTransac

tion Code

Selection CriteriaOutput

Page 66 of 82


1 Structure Overview CN41Project Definition and / WBS element, and/Network, and /Activity

Project Objects, Basic dates, Scheduled dates, Person Responsible, System Statuses based on choose fields.

2 Work Center View CM01Work centre, Plant, and/capacity planner group.

Requirement, Available capacity, load %,Remaining available capacity, Unit.

3 Variable Overview CM07 WBS element, and/ Network,Plant,Work center

Requirements, Available capacity, load %,Remaining available capacity, Unit.

4Information system for Material based on Stock /Requirements

MD04 Material ,PlantDynamic up to date stock, Recd./Required qty, Available stock.

5Information System for Material based on Reservations

MB25

WBS element and/,Network and/,Activity and/,Material and /,Plant and / ,Requirement Date

Reservation number, Requirement date, material, Quantity.

6

Information System for Material based on Purchase Requisition for Project

ME5JDatabase Profile, Project Definition and/,WBS Element and /,Network, and /Activity

Material Requisitions, Required Qty, Delivery date, Release date, plant.

7

Information System for Material based on Purchase Order for Project

ME2JDatabase Profile, Project Definition, WBS Element, Network, Activity.

Purchase order, Vendor, Material, Plant, Order Qty, Price.

8

Information System for Material Based on Valuated Project Stock

MBBSSpecial Stock Indicator Q, Project Definition

Material, Plant, WBS element, Stock, Total Value.

9Material Planning Based on Execution by using Pro Man

CNMMProject Definition, Proman Profile

Details for Project material components Orders/ documents, Quantities, Dates, Stock, Deliveries

10Information System Based on Progress Analysis for Structure

CNE5Database Profile, Project Definition and/,WBS Element and/,Network, and/Activity

Project Object, choose fields, Agg.Plan compl, Agg.actual completion.

11

Information System under Financials for Plan Based Hierarchal structure involving Plan/Actual/ Variance

S_ALR_87013532

Database Profile, Project Definition and/,WBS element and/,Network and/,Activity and/,Plan Version

Project object, Planned-total, Actual-total, Variance.

12 Information System under Financials for Plan Based on Cost

S_ALR_87013542

Database Profile, Project Definition, Controlling Area, Version, From Fiscal Year to

Cost elements, Actual, Commitment, Total, Plan

Page 67 of 82


element structure involving Actual/ Commitment/Total/Plan In CO Currency

Fiscal year

13

Information System Under Financials for Costs/Revenues/Expenditure/Receipts

S_ALR_87013531

Database Profile, Project Definition/WBS Element/Network /Activity, Plan version

Objects, Plan Costs, Actual costs, Planned revenue., actual Revenue

SL DescriptionTransaction Code

Selection CriteriaOutput

1 Structure Overview CN41Project Definition and / WBS element, and/Network, and /Activity

Project Objects, Basic dates, Scheduled dates, Person Responsible, System Statuses based on choose fields.

2 Work Center View CM01Work centre, Plant, and/capacity planner group.

Requirement, Available capacity, load %, Remaining available capacity, Unit.

3 Variable Overview CM07 WBS element, and/ Network, Plant, Work centre

Requirement, Available capacity, load %,Remaining available capacity, Unit.

4

Information System for Material based on Purchase Requisition for Project

ME5JDatabase Profile, Project Definition and/,WBS Element and /,Network, and /Activity

Material, Requisition, Required Qty, Delivery date, Release date, plant.

5

Information System for Material based on Purchase Order for Project

ME2JDatabase Profile, Project Definition, WBS Element, Network, Activity.

Purchase order, Vendor, Material, Plant, Order Qty, Price.

6

Information System for Material Based on Valuated Project Stock

MBBSSpecial Stock Indicator Q, Project Definition

Material, Plant, WBS element, Stock, Total Value.

7Material Planning Based on Execution by using Pro Man

CNMMProject Definition, Proman Profile

Details for Project material components, Orders/documents, Quantities, Dates, Stock, Deliveries

8

Information System under Financials for Plan Based Hierarchal structure involving Plan/Actual/ Variance

S_ALR_87013532

Database Profile, Project Definition and/,WBS element and/,Network and/,Activity and/,Plan Version

Project object, Planned-total, Actual-total, Variance.

9 Information System S_ALR_ Database Profile, Project Cost element, Actual,

Page 68 of 82


under Financials for Plan Based on Cost element structure involving Actual/ Commitment/Total/Plan In CO Currency

87013542

Definition, Controlling Area, Version, From Fiscal Year to Fiscal year

Commitment, Total, Plan

10

Information System Under Financials for Costs/Revenues/Expenditure/Receipts

S_ALR_87013531

Database Profile, Project Definition/WBS Element/Network /Activity, Plan version

Objects, Plan Costs, Actual costs, Planned revenue., actual Revenue

Page 69 of 82


(E)Appendix

1. Project Profile:

The Project profile is divided into four sections: Control, organization, planning board / dates and controlling.

Page 70 of 82


Masters:

a) Control Data: Project Profile

Planning Dates:

Network Profile WBS Scheduling Profile

Scheduling Scenarios

Planning Method / Basic

Planning Method / forecast

Network Assignment

Accounting:

Planning Profile

Project Stock: Valuated / Non Valuated / No Project Stock.

b) Basic Data:

System Status: Automatically Maintained by the System.

Dates:

Start Date Finish Date

Factory Calendar

Time Unit

Forecast Start Date

Forecast Finish Date

Organization:


Plant

Currency

Page 71 of 82


2) Icons used in the project planning board

SAP AG 1999

Icons Used in the Project Planning Board

Page 72 of 82


Projects department have different procurement cycles as per the billing schedule is considered. Detailed steps of procurement to dispatch will be discussed below.

1) Dispatch of complete assembly

Assign component to the WBS element

Select the appropriate plant

Select the item category ‘L’

Select the procurement type Reservation for WBS element

Delivery of complete assembly from plant

2) Dispatch of single assembly from main assembly

Block the single assembly from main assembly

Assign the single assembly for WBS element




3) Dispatch of single Bought out materials from Production Plant

Create a semi finished/finished material having same description of bought out material

Create the BOM for semi finished/finished material with assigning bought out material to the BOM

Assign the BOM material to WBS element



Delivery of complete BOM from plant

4) Procurement of single bought out material from vendor to customer (no liability of FPE) and billing to single line item

Assign material to 3100 plant

Assign component to WBS element

Page 73 of 82


Select the item category ‘N’

Page 74 of 82


Select the procurement type Third party order for network

Logical GR

Billing for the component once the Logical GR is happened

5) Procurement of Multiple bought out material from vendor to customer (no liability of FPE) and billing to single line item

Assign all materials to 3100 plant

Page 75 of 82


Assign components CMI Industry Automation to WBS element


Select the procurement type Third party order for network

Logical GR

Create a material for billing purpose assign same in the sales order line item

Sum of the procurement quantity should be equal to the order quantity in the sales order line item

Billing for the component once the Logical GR is happened

6) Procurement of single bought out material from vendor to customer (liability of FPE) and billing to single line item


Assign component to WBS element


Select the procurement type Preliminary Requisition for WBS element/Third party order for WBS element

GR and delivery of material

Billing for the component.

7) Procurement of Multiple bought out material from vendor to customer ( liability of FPE) and billing to single line item

Create a semi finished/finished material having same description of bought out material






Delivery of BOM from plant

8) Dispatch of multiple Bought out materials from Production Plant and billing to single line item with different quantities

Page 76 of 82


Create a semi finished/finished material having same description of bought out materials with the quantities in the billing head


Assign material to production plant




Delivery of complete BOM from plant

Assign all different BOM items in Sales order line item with quantity

9) Procurement of materials for site modifications and billing is not done for those materials

Assign the materials under un planned cost WBS element and follow the appropriate procurement type as mentioned above.

Procurement scenario for procuring assembly from CMI INDUSTRY AUTOMATION and issue of free goods from Flat products to CMI INDUSTRY AUTOMATION

1) Procurement of assembly from CMI INDUSTRY AUTOMATION (Dispatch from Production Plant) and issue of free goods from production plant to CMI INDUSTRY AUTOMATION

Flat Products

Assign assembly to the WBS element which we want to procure from CMI

INDUSTRY AUTOMATION



Select the procurement type Preliminary requisition for WBS element

Assign free issue goods to WBS element which we want to procure from vendor

Page 77 of 82



Select the procurement type Preliminary requisition for WBS element and Document

type ZNB


For issue of free goods to CMI INDUSTRY AUTOMATION create free issue PR


type ZFI

Creation of PO for assembly incorporating all free issue PR’s in the PO

Issue of free issue goods to project with movement type 281 Q

Once assembly received from CMI INDUSTRY AUTOMATION GR will be done in

FPE


CMI INDUSTRY AUTOMATION

Creation of sales order

Creation of project

Assign all free issue goods as non valuated materials in BOM and block the valuated

materials

Assign the assembly to the WBS element


Take all non valuated materials in to stock

MRP run for WBS Element

Delivery from CMI INDUSTRY AUTOMATION to FPE

2) Procurement of assembly from CMI INDUSTRY AUTOMATION (Dispatch from Production Plant) and Third party procurement of free goods to CMI INDUSTRY AUTOMATION

Flat Products


INDUSTRY AUTOMATION

Page 78 of 82




Select the procurement type Preliminary requisition for WBS element


Select the item category ‘N’ and select the 3100 plant

Select the procurement type Third party requisition for network and give CMI

INDUSTRY AUTOMATION as an vendor in PR

Creation of PO for assembly

Logical GR for Free issue goods

Once assembly received from CMI INDUSTRY AUTOMATION GR will be done in

FPE




Creation of project


materials





Delivery from CMI INDUSTRY AUTOMATION to FPE

3) Third party Procurement of assembly from CMI INDUSTRY AUTOMATION and issue of free goods from production plant to CMI INDUSTRY AUTOMATION

Flat Products


INDUSTRY AUTOMATION

Page 79 of 82


Select the 3100 plant


Select the procurement type Third Party requisition for Network




type ZNB


For issue of free goods to CMI INDUSTRY AUTOMATION create free issue PR


type ZFI

Creation of PO for assembly incorporating all free issue PR’s in the PO

Issue of free issue goods to project with movement type 281 Q

Once assembly Delivered from CMI INDUSTRY AUTOMATION logical GR will be

done in FPE



Creation of project


materials





Delivery from CMI INDUSTRY AUTOMATION to customer

4) Third party Procurement of assembly from NTSCMI INDUSTRY AUTOMATION and Third party procurement of free issue goods

Flat Products


INDUSTRY AUTOMATION

Page 80 of 82


Select the 3100 plant


Select the procurement type Third Party requisition for WBS element


Select the item category ‘N’ and select the 3100 plant

Select the procurement type Third party requisition for network and give CMI

INDUSTRY AUTOMATION as an vendor in PR

Creation of PO for assembly

Logical GR for Free issue goods

Once assembly Delivered from CMI INDUSTRY AUTOMATION logical GR will be

done in FPE



Creation of project


materials





Delivery from CMI INDUSTRY AUTOMATION to customer

Page 81 of 82


Summarized scenario’s - CMI INDUSTRY AUTOMATION

Scenarios Inputs(free goods) Finished Goods

(assembly)

Remarks

1 FPE issues inputs to

CMI INDUSTRY

AUTOMATION under

excise annexure

FG returned by CMI

INDUSTRY

AUTOMATION to FPE

and FPE does

dispatch to customer

2 Vendor issues inputs

to CMI INDUSTRY

AUTOMATION excise

invoice W/o tax,

showing ship to party

is CMI INDUSTRY

AUTOMATION and

bill to party is FPE

FG returned by CMI

INDUSTRY

AUTOMATION to FPE

and FPE does


3 FPE issues inputs to

CMI INDUSTRY

AUTOMATION under

excise invoice W/o

tax, showing ship to

party and sold to party

is CMI INDUSTRY

AUTOMATION

FG can be directly


from CMI INDUSTRY

AUTOMATION. CT1

issued by FPE

4 Same as scenario 2 Same as scenario 4

Page 82 of 82