Balco ps configuration manual

SSAAPP PPRROOJJEECCTT SSYYSSTTEEMM

CCOONNFFIIGGUURRAATTIIOONN MMAANNUUAALL

PREPARED BY

KALLOL SENGUPTA

BHARAT ALUMINUM CO. LTD.

CONTENTS

1 PROJECT STRUCTURES AT BALCO................................................................................................3

2 PROJECT PROFILE ....................................................................................................................... 8

3 NETWORKS .................................................................................................................................14

5 MILESTONES ...............................................................................................................................25

6 PROJECT PLANNING BOARD ..................................................................................................26 7. COSTS..........................................................................................................................................33

8. BUDGET....................................................................................................................................... 43

9. MATERIAL PROCUREMENT .........................................................................................................47

10. MONITORING DATES..................................................................................................................50

11. CONFIRMATION OF WORK........................................................................................................52

12. PROJECT PROGRESS ANALYSIS..................................................................................................55

13. INFORMATION SYSTEM...............................................................................................................62

14. AUTHORIZATIONS IN PROJECT SYSTEM ....................................................................................68

15. REPORTS FROM PROJECT SYSTEM..............................................................................................69

16. TRANSACTION CODES............... ................................................................................................72

13/12/200213/12/200213/12/2002

R/3 implementation for BALCO Hewlett-Packard - confidential -

Prepared by Kallol Sengupta

13/12/20021

1 PROJECT STRUCTURES AT BALCO

Menupath : IMG-> Project System -> Structures -> Operative Structures -> Work Breakdown Structures-> Project Coding mask -> Define Special characters for Projects In this step, you specify how a project number is coded for editing. You can maintain the following parameters for editing the project number:

• the length of the key for project coding You can assign up to five places for the key.

• an indicator specifying whether the key must have this exact length or whether it can also be shorter

• special characters to enter WBS elements faster

• an indicator specifying whether only coded project numbers can be used to create projects

PROJECT SYSTEM USER MANUAL for BALCO

Hewlett-Packard - confidential -

Prepared by : Kallol Sengupta

13/12/20022

Menupath : IMG-> Project System -> Structures -> Operative Structures -> Work Breakdown Structures-> Project Coding mask -> Define Project Coding mask




13/12/20023

In this step, you create masks for editing the project number. Masks help display complex project numbers. They can also be used to indicate the position of a WBS element in the project hierarchy.

You can create a mask for every key you want to use in project coding.

The following characters are available for editing:

• X for alphanumeric characters

• 0 for numeric characters

• special characters to organize the project numbers

The Project Code for Balco is based on the following codification:

Project ID :

First two digits are based on the project executing agency (e.g. Smelter & Power)

CP/000-XX-XX-XX-XX-XX BALCO 540 MW Captive Power Plant

SM/000-XX-XX-XX-XX-XX BALCO Smelter Project

Third character is a separator ‘/ ‘

Numeric part is to be used for running project number.

Alphanumeric part is to be used for coding WBS hierarchy

The subsequent coding mask follows logic as explained below: 000 Project serial number. XX 1st Level of the WBS element - Major work packages (e.g. EPC,NEPC for Power Project) XX 2nd level of the WBS element : Major Work packages based on person responsible (e.g. under EPC -- Boiler, Turbine, BOP, Electrical, C&I) XX 3rd level WBS Element for further breakdown of the Major Work packages XX 4th level WBS Element for further breakdown of the structure XX 5th level WBS Element for breakdown of the structure




13/12/20024

WBS USER STATUS : CREATE STATUS PROFILE

Menu path: IMG-> Project System -> Structures -> Operative Structures -> Work Breakdown Structures->WBS User status -> Create status profile

PROJECT STATUS :

A project is not a static object. It has it own life cycle that begins when it is created and continues till completion. During this period various business transactions change the project. For instance you plan tasks, post costs and perform settlements.

Each project passes through various system statuses. One of which is always set. For example,

• Created In this status you cannot, for instance, make actual postings.

• Released In this status virtually all business transactions are permitted. In this status you can assign costs In Released status you can create new WBS elements and change the project hierarchy. The status is passed on to subordinate WBS elements




13/12/20025

Technically Completed

You use this status for WBS elements that are completed from a technical point of view, but where you still expect costs to accrue. The prerequisite is ‘Created’ or ‘Released’ status must have been set.

In status Technically completed, you can create new subordinate WBS elements (with a warning). The status is passed on to subordinate WBS elements.

The status allows

o You from assigning networks, production orders or CO orders to the WBS element.

o You to post actual costs

o You to transfer actual costs

You can cancel the Technically completed status. In this case the system sets the Released status.

Closed Status

You use this status for a work breakdown structure or WBS element that has been completed from both a logistic and an accounting point of view.

Prerequisite : You can only set the Closed status, if the project definition or the WBS element have either the Released or the Technically completed status.

In the Closed status you can no longer make any changes to the project hierarchy. The status is passed on to subordinate WBS elements.

The status allows you to post actual costs to orders and networks that are assigned to the WBS

element, as long as their status permit this

The status prohibits • You from assigning networks, production orders or CO orders to the WBS element.

• You from posting actual costs to the WBS element

The status deactivates assets in construction that are assigned to the WBS element. You can cancel the Closed status. In this case the system sets the Technically completed status

In BALCO, the system has been configured to raise purchase requisition automatically once the WBS elements & Networks are released.




13/12/20026

DEFINE AUTHORISATION KEY FOR WBS

Menu path: IMG-> Project System -> Structures -> Operative Structures -> Work Breakdown Structures->WBS User status -> Define authorization key for WBS

In this step you define authorization keys which you can use to set up authorization checks when you manually set or delete a user status. When the system sets a user status as a reaction to business transaction, it does not perform an authorization check.

When you set or delete a user status, the system checks whether the user is authorized for this action. In addition to the status profile and the object type, the system also checks the authorization key assigned to the user status in question.

In BALCO the following authorization keys have been defined :

Z0000001 -> BALCO: Auth key to sub for approve

Z0000002 -> BALCO :Auth key to approve

Z0000003 -> BALCO: to release WBS/Network

PROJECT PROFILE

Menu path: IMG-> Project System -> Structures -> Operative Structures -> Work Breakdown Structures->WBS User status -> Create Project Profile

The project profile contains default values and other control parameters such as the planning method for dates and costs.

In case of BALCO, select Z000002 (Balco -SMELTER Capital Project )

Z000003 (Balco -POWER (CPP) Capital Project)

The project profile contains default values and other control parameters such as the planning method for dates and costs.

The data that you enter in the project profile will be copied into a project in its project definition or in the WBS elements which can later be overwritten.

Examples

• To call up the graphic, you must first have specified various graphic profiles in the project profile.

• To carry out cost planning you must specify a planning profile.

• To carry out financial budgeting you must specify a financial planning profile

The values in the project profile determine the functionality of certain areas of the Project System and cannot be changed without careful thought. Do not change profiles and key from related functions which are defined in the project profile, such as the costing sheet or the results analysis key. These changes could effect existing objects.

You must maintain the following sections for the project profile:




13/12/20027

• Basic data

• Time scheduling

• Costs/revenues/finances

• Organizational data Standard settings In the standard R/3 System, SAP has predefined a project profile containing the most important control parameters. Activities

1. Determine the organizational and control criteria for you company.

2. Create the project profiles reflecting these criteria and enter the relevant data.




13/12/20028




13/12/20029




PROJECT STOCK Use this indicator to specify for materials requirements planning (MRP)/procurement whether the project has its own stock. With project stock you can for instance:

• In multi-level production, keep track of the cost in a work breakdown structure in a detailed manner.

• Examine the material components required in a project with regard to inventory management or MRP planning seperately. This is particularly useful for components that have a long procurement lead time.

In valuated project stock the materials are managed on both a quantity basis and a value basis; all goods movements trigger corresponding postings in the stock accounts in Financial Accounting.

INDICATOR: ALL WBS ELEMENTS ARE ACCOUNT ASSIGNMENT ELEMENTS With this indicator you determine that all the WBS elements you create are account assignment elements (An element in a work breakdown structure (WBS) to which the following postings can be made:

• Actual postings

• Commitment postings )

13/12/200210

INDICATOR: WBS CAN ONLY HAVE ONE WBS ELEMENT WITH LEVEL 1 Use this indicator to specify that there can only be one WBS element at the first level (root) for each project definition WBS SCHEDULING PROFILE : The indicator is copied as a default value from the project profile; it can be changed in the control data when you create a project. It is valid for all WBS elements.

The system calculates the scheduled start and finish of the activities in the WBS elements, their capacity requirements, and the float times, when the work breakdown structure (WBS) is scheduled.

The start and finish dates of the WBS elements are the basis for determining the scheduled dates.

SCHEDULING SCENARIO The following scheduling scenarios are avaialable :

• Top-Down Scenario (2) The scheduling dates are defined by top hierarchy elements, that is the project definition or the WBS elements, and limit the dates of the activities. The dates of the activities must lie within the basic dates of the WBS elements to which the activities are assigned. Similarly the basic dates of a WBS element must be within the basic dates of its superior WBS element.

• Bottom-Up Scenario (1) The dates are passed on from the bottom of the hieratrchy to the top, that is from the activities to the corresponding WBS elements and then up through the hierarchy to the project definition. The dates of the superior WBS element are checked to see whether they include the dates of the subordinate activity or WBS element. If this is not the case, the basic dates of the superior WBS element or project definition are changed correspondingly. If no activities or other WBS elements are assigned to a WBS element, the system uses the basic dates of the WBS elementa as scheduled dates.

• Free scheduling ( ) You can choose the scheduling parameters as you like.

INDICATOR: READ PROJECT WITH ACTIVITIES You can use this indicator to determine whether all activities in the WBS elements will be read in when the Project Builder, time scheduling, structure planning or the project planning board is activated. You can improve the performance of the system by not setting this indicator for projects that contain a lot of activities

PLANNING METHOD FOR PROJECT BASIC DATES To plan basic dates you must specify a planning method. This only to the work breakdown striucture and not to activities:

• In Top Down Planning you plan the dates starting from the top WBS element in the hierarchy. The dates that you maintain in the subordinate WBS elements must lie within the dates periods of the superior WBS elements.

• In Bottom Up Planning you plan the dates starting from the subordinate WBS elements. The dates of the superior WBS elements are only changed, if thery do not include the dates of the subordinate WBS elements.




13/12/200211

• In Strict Bottom Up Planning you specify that the dates of subordinate WBS elements determine the dates of the superior elements. If you have already entered dates for the superior WBS elements, the system deletes them, and calculates new dates based on the dates of the subordinate WBS elements.

• In Free Planning you plan the dates without hierarchical dependencies.

DEFINITION: OBJECT CLASS

CONTROLLING (CO) The object class categorizes Controlling objects according to their business function and enables you to analyze cost flows within Controlling from different business perspectives. The following object classes are available:

• Overhead

• Production

• Investment

• Profitability analysis and sales While certain object types automatically belong to a particular class (for example, cost centers belong to the "Overhead" class), others need to be explicitly assigned to an object class in their master record (this is the case with internal orders and work breakdown structure elements, for example). In addition to the functional area, the object class is required to determine or explain certain values in the external accounting components.

DEFINITION: SETTLEMENT PROFILE A requirement for creating a settlement rule. You define the following parameters in the settlement profile:

• Allowed settlement receivers (such as cost center or asset)

• Default values for the settlement structure and the PA transfer structure

• Allocation bases for defining the settlement shares (using percentages or equivalence numbers - or both)

• Maximum number of distribution rules

• Residence period of the settlement documents

• Document type for settlements relevant to accounting (more specifically, to the balance sheet)

• Definitions for the settlement of actual costs or the cost of sales

STRATEGY FOR DETERMINING SETTLEMENT RULE IN WBS ELEMENT Key describing the strategy for generating settlement rules automatically in WBS elements. You use the strategy to determine the following for each settlement parameter:

• Control parameters for the objects to which the strategy applies, such as billing elements




13/12/200212

• Account assignment category - example: responsible cost center

• Treatment of sales and distribution document items in the event of multiple assignment to WBS element

PROJECT TYPES:

The project type does not influence program control or screen selection. You can use the project type as a filtering criterion in the information system.

SPECIFY PERSONS RESPONSIBLE FOR BALCO PROJECTS

Enter the name of the persons responsible (Transaction code OPS6) for reporting purpose

DEFINE PRIORITIES FOR WBS ELEMENTS You can specify the priority criteria individually. The priority does not influence the program or the screen selection. You can use the priority as a filter criterion in the information system.




13/12/200213

NETWORKS

Menu path: IMG-> Project System -> Structures -> Operative Structures -> Network

MAINTAIN AUTHORIZATION KEY FOR NETWORKS In this step you define authorization keys which you can use to set up authorization checks when you manually set or delete a user status. When the system sets a user status as a reaction to business transaction, it does not perform an authorization check. When you set or delete a user status, the system checks whether the user is authorized for this action. In addition to the status profile and the object type, the system also checks the authorization key assigned to the user status in question. Example You want to define that certain user statuses can be changed only by a specified employee group. To do this, create an authorization key and assign it to the relevant user statuses. In the general authorization maintenance you can then assign authorizations for this key via the authorization object B_USERSTAT. Activities

1. Check whether you want to define authorizations for your user statuses.

2. If necessary, create authorization keys as follows:

a) Choose "New entries".

b) Enter a key and an explanatory text in the appropriate fields and choose "Save".

You have now created the authorization key.

3. Assign the authorization key to one or more user statuses in your status profile.

4. Define corresponding authorizations and include them in the relevant authorization profiles.




13/12/200214

SETTINGS FOR NETWORK Menu path: IMG-> Project System -> Structures -> Operative Structures -> Network-> Settings for network -> Maintain network types The network type contains information for controlling and managing networks.

In the SAP System, the network is a special form of the work order which has a structure in common with production, maintenance and inspection orders.

Every network you create must have a network type allocated to it.

The network type determines:

• the order category

• the CO (controlling) partner update With the indicator, you specify whether a summary record should be written per network if a CO partner object (for example, cost center) is settled with a network of this type.

• whether the network is used for planning and does not add to the assigned values

• residence times 1 and 2 for the archival and deletion of networks

• a default value for the settlement profile

• a default value for a status profile, if you want to use the user status in status management

• allocation of the network type to a number range You have to allocate a number range to every network type.

Note In addition to the general parameters at plant level, the network also requires parameters at plant level, showing, for example, whether the network is header-assigned or activity assigned. You maintain these parameters in the step "Define parameters for networks". Requirements You must have already processed the menu option "Number range".




13/12/200215




13/12/200216




INDICATOR: ACCOUNT ASSIGNMENT ON ACTIVITY LEVEL Indicator which specifies that the account assignment is to be carried out at activity level. If you do not set this indicator, the account assignment is carried out at order header level.

MAINTAIN NETWORK PROFILES Menu path: IMG-> Project System -> Structures -> Operative Structures -> Network-> Settings for network -> Maintain network profiles The network profile contains default values and parameters for controlling the processing of networks, such as control keys for activities. The data which you enter here in the network profile is copied into the header, activities, and activity elements when you create a network. You can overwrite these values in each new network. Examples

• To be able to call up the network structure graphic, you must have entered a graphic profile in the network profile.

• To be able to create a project version for the network, you must have entered a version profile in the network profile.

13/12/200217




13/12/200218

SETTINGS FOR NETWORK ACTIVITIES Menu path: IMG-> Project System -> Structures -> Operative Structures -> Network-> Settings for network -activities> Define control key

DEFINE CONTROL KEY In this step, you create the control keys for different activities and activity elements. The control key determines which business transactions are carried out when an activity is processed. You specify the indicators and keys for the various functions in the control key. Example

• The capacity planning indicator controls that the capacity requirements for the activity and activity element are calculated.

• The costing indicator controls that the activity and activity element are costed.

• The general costs activity indicator specifies that the activity is a general costs activity or that the activity element is a cost element.

Notes

• Note when processing externally:




13/12/200219

o If you select the key Data for ext.processing possible, you can maintain data for an externally processed activity.

o If you select the key Data for ext.processing required, you must maintain data for the externally processed activity. The activity then becomes an externally processed activity.

o If you select the key Data for ext. processing not permitted, you cannot maintain data for an externally processed activity.

Externally processed activity : A category of network activity describing activities that are performed outside your company.

For example, if you request an engineering firm to design a machine, this is an activity processed externally.

• For capacity planning and scheduling, please note:

o The indicator capacity_planning determines the capacity requirements for a certain date. If you have not set any constraints in the activities, you have to maintain the Scheduling indicator so the system will calculate the capacity requirements using the activity duration.

• When changing control keys, please note:

o Changes to the control keys change business transactions and if necessary also the activity data.

Standard settings Control keys are created in the standard SAP R/3 System for every transaction type. Activities

1. Check whether you can use the pre-defined control keys. 2. If necessary, define further control keys for the different transaction types.

INDICATOR: SCHEDULING This indicator specifies that the following objects are scheduled if specified in the control key you selected:

activities and activity elements in the Project System (PS) The earliest and latest dates for activity elements are determined. Note Note that sub-operations and activity elements are scheduled in relation to the superior operation or activity and secondary resources are scheduled in relation to the superior phase. Therefore, you should only use a control key with this indicator for a sub-operation, activity element or secondary resource, only if the superior operation, activity or superior phase is also scheduled.

If the indicator is not set, for example, for operations used as documentation, the following applies:

• Activities (PS) are scheduled with a duration of 0, which means start and finish dates correspond to the finish of the previous operation, activity or phase, even if you entered a duration different than 0 in the operation, activity or phase.

• Activity elements (PS) keep the dates from the superior operation, activity or phase.




13/12/200220

ACCOUNT ASSIGNMENT CATEGORIES AND DOCUMENT TYPES FOR PR

ACCOUNT ASSIGNMENT CATEGORIES AND DOCUMENT TYPES FOR PR Use this step to specify purchasing item categories and a purchasing document type for purchase requisitions in the network. Purchase requisitions can be assigned to:

• the network

The planned costs are updated in the network.

• the WBS element, if the network is assigned to a WBS element

The planned costs are updated in the WBS element.

• the sales order, if the network is assigned to a sales order

The planned costs are updated in the sales order.




13/12/200221

CHANGE MANAGEMENT : Menu path: IMG-> Project System -> Structures -> Operative Structures -> Network-> Define change profile For BALCO, Change profile ZS0001 has been created. You use this profile to determine how configuration changes in networks are treated.

The parameters are divided into following groups:

• Settings

Here you define whether the necessary changes steps are executed all together or whether individual steps can be executed.

• Handling conflict situations You can specify whether particular situations for an action constitute a conflict and whether this conflict has informative character or a warning or an error is issued.

The actions change, delete, create or reassign for objects activity, activity element, componnent or PRT are taken into consideration. The situation can also be handled differently, depending on the status of the object, for whether the (superior) activity has been released, partially confirmed or finally confirmed.

Activities 1. Define the profile for configuration change management for networks.

2. Assign the profiles to:

o Materials (material master: tab page Work Scheduling)

and/or

o Network types

If you create a project using assembly processing, the profile in the material master is used first; if no profile has been entered in the material master, the profile is taken from the network type.




13/12/200222




13/12/200223




13/12/200224

MILESTONE USAGE Menu path: IMG-> Project System -> Structures -> Operative Structures -> Milestones -> Define milestone usage

In this step you define milestone usages.

Example

With the usage, you can specify:

• what the milestone is used for, such as a trigger for milestone functions or for earned value analysis

• the area in which the milestone is used, for example in engineering or design You can also use the value for usage for selection in the information system.




13/12/200225

PROJECT PLANNING BOARD Menu path: IMG-> Project System -> Structures -> Project planning board The project planning board is based on the SAP Gantt chart. In the following steps make only those settings, which you require specifically or additionally for working with it in the Project System.

Start date for an evaluation : Date of the first day of the period, for which the data is evaluated

End date for an evaluation : Date of the last day of the period for which the data is evaluated.




13/12/200226

TYPE OF ENTRY Key used to specify the type of entry you want to use to enter the limits for the evaluation period. You can enter the evaluation period in two different ways:

• Entry with specific date

• Entry relative to the current date

EXAMPLE

Example of an entry with a specific date:

Type of entry Start Finish

CalMonth 3.1994 6.1994

CalDay 3.2.1994 11.31.94

Examples of an entry relative to a current day, for example, the 01.14.1994:


CalDays -10 +20

This generates an evaluation period from 01.04.1994 to the 02.03.1994.


CalWeeks -1 +2

This generates an evaluation period from 01.03.1994 to the 01.30.1994.

DEFINE PROFILES FOR TIME SCALES In this work step you define the time scale profile. A time scale profile describes the properties of all possible scales using headings for the time axis (day scale, week scale etc.).

The time fence is derived from the possible scales.

Depending on the current scale the time scale is generated from one or more scales.

There are scales with the following headings:

• Yearly split

• Quarterly split

• Monthly split

• Weekly split

• Daily split

• Hourly split

• Minute split




13/12/200227

• Shift split To show the shift scale you have to select a capacity in the capacity planning table whose shift calendar determines the shift split. It you set the indicator Show shift then the shift calendar for the first capacity is displayed automatically in the capacity planning table.




13/12/200228

DEFINE SCALE FOR THE TIME AXIS In this step you define

• the scale for the various segments on the time axis (see next section)

• whether when the capacity planning table is called up the non-work times that are common to all capacities are hidden.

Segments of the time scale: In the capacity planning table you see a segment of the (infinite) time scale. This segment is defined by the evaluation period in the time profile. You define the time scale of the time axis for the following segments:

• Pre-evaluation period

This represents the period between the start of the evaluations until the start of planning.

• Planning period

This represents the period between the start and the end of planning.

• Post-evaluation period

This represents the period between end of planning and end of evaluation. A scale is defined as the length per unit of time e.g. 40 mm per day.




13/12/200229




SCALE FACTOR EVALUATION LEAD PERIOD/PLANNING PERIOD Gives the relationship between the scale for the pre-evaluation period and that for the planning period. The relationship is shown in percentage terms.

EXAMPLES You selected 40 mm (=4 cm) per day as a scale for the planning period. If you now enter 20.00 (%) as the relationship then the scale for the evaluation lead-time is: 40 mm * 20 % = 8 mm, that is, 0.8 cm per day.

LENGTH PER UNIT OF TIME FOR THE EVALUATION Value giving the length over which a unit of time of the evaluation preliminary lead-time is displayed.

DEFINE PROFILES FOR THE PROJECT PLANNING BOARD Menu path: IMG-> Project System -> Structures -> Project planning board -> Define profiles for the Project Planning Board You can maintain different values in the profile of the project planning board:

• Default values

Default values are copied when you call up the project planning board and you can change them interactively once you're in the project planning board at any time.

• Graphics profile

A graphics profile must exist in order for you to be able to call up the project planning board. The graphics profile has a name and a group and is composed of several simple profiles for colors and forms, for example. You can maintain the graphics profile in Customizing for all SAP graphics.

• Fields that are displayed in the table area of the project planning board

You can group all fields to be displayed in the table area into a profile.

13/12/200230

• Parameters for the time display

To display time periods in the project planning board, you need

o a time profile which specifies the periods in which data is to be displayed

o a scale for the time axis

o a profile for the scale which specifies the characteristics of different time scales, for example, scale and text for time periods of a year.

• Change indicator

You can protect the profile against changes.

You specify with this indicator whether activities should be shown on the project planning board.

Use this key to specify whether the earliest or latest dates of the activity will be displayed in the project planning board.

You use this indicator to specify that the planning board profile can only be changed in Customizing.




13/12/200231




Description that should appear to the left of the date bar in the Gantt chart.

13/12/200232

PROJECT SYSTEM : COSTS

Menu path: IMG-> Project System -> Costs

ACTIVATE PROJECT MANAGEMENT IN CONTROLLING AREA In this step, you can use the control indicators in the controlling area to activate project management and commitment management for a controlling area. Requirements You must have created a controlling area in full. Activities Activate project management and, if desired, commitment management for projects in the controlling area, as follows:

1. Choose the controlling area for which you want to activate project management.

2. Choose "Activate components/Control indicators".

3. If the controlling area was created for more than one year, choose the a fiscal year. The control indicators take effect from the fiscal year chosen and are relevant for all fiscal years following the one last maintained. Press the "Details" pushbutton.

4. Set the indicator for "Projects".

5. Enter "1" in the "Commitment mgmt" field if you want to use commitment management for projects.




13/12/200233




MAINTAIN CURRENCY EXCHANGE RATES FOR PROJECTS

Note : It will be maintained by BALCO FINANCE department.

Transaction code : OB08

You use this step to stipulate how currencies are translated. The exchange rates are required for plan and actual postings to, among other things:

• translate foreign currency amounts on posting or clearing

• verify rates entered manually

• determine the profit/loss on exchange rate differences

• value open items in foreign currency

• value foreign currency account balances

• determine the controlling area currency equivalents of amounts posted in different company code currencies

13/12/200234

• allow project settlement to take account of different controlling area, sender and receiver currencies

The currency translation rates are time-dependent, coming into force on the date entered. Note The SAP system uses the currency translation rates stored under rate type "M" to translate currencies when you post or clear actual transaction data. The rates apply to all company codes. For translation of plan postings, you define a fiscal-year-dependent rate type in the version. A number of SAP application components use the currency translation rates.




13/12/200235

MAINTAIN VALUE CATEGORIES In this step, you define value categories. Value categories are intervals of:

• Cost elements

• Commitment items

• Statistical key figures

These are required for:

• Updating the project information database

• Calculating project interest

• Defining structure reports for costs, revenues, and payments

• Updating quantities in the project info database RPSQT

Activities 1. Define keys and names for value categories.

2. If you want to evaluate quantities in EIS or for the progress values, assign a unit of measure to the value category.

3. Assigne the debit category to the value category.

• Costs and outgoing payments

• Revenues and incoming payments

• Statistical key figures with totals values

• Statistical key figures with fixed values

Further notes You should group cost elements and commitment items into value categories to reduce data volume. For value categories according to cost elements or commitment items, you can let the system generate the value categories automatically.




13/12/200236

ASSIGN COST ELEMENTS TO VALUE CATEGORIES In this step, you define a cost element, a cost element interval or a cost element group as a value category. Recommendation The check for whether cost elements exist is faster if you enter a cost element interval rather than a cost element group. Activities

1. Choose a value category and access the detail screen.

2. Define a cost element, a cost element interval or cost element group as the value category. ADDITIONAL HINTS If you change the value categories later, you will have to reconstruct the project information database (transaction CJEN) if plan data already exists. This is necessary to avoid data inconsistencies. Value categories can be created automatically. To do this, go to the implementation guide and choose Information System -> General Functions -> Project Info Database -> Set update control. When value categories are automatically created, a value category is created for each posted cost element with the same description. For example, if you post cost element 415000, the system creates value category 415000.

EASY COST PLANNING AND EXECUTION SERVICES Easy cost planning is method of costing that enables costs to be planned quickly and easily for objects such as Work breakdown structure elements

CREATE COSTING VARIANT You can use costing variants to combine all the controlling parameters for costing. The costing variant represents the link between the application and customizing because all costings must reference a costing variant as they are made and stored. The costing variant controls how the costing is to be carried out. With it, you control:

• Whether the costing results are to be regarded as plan costs or actual costs

• Which prices are used to value the materials, internal activities and external activities

• How overhead surcharges are calculated

The following are part of the costing variant:

• costing type 08 for the project unit costing

• valuation variant Note It is technically possible to have more the same costing type and valuation variant in more than one costing variant, but you should avoid this because it can lead to one variant overwriting the data for another. The reason for this is the key format for costing results in the database. This key form is based on the costing type and valuation variant, no the costing variant. Standard Settings The SAP standard system contains a number of predefined costing variants




13/12/200237

SAP Recommendation When you use Easy Cost Planning, we recommend you use costing variant PS06, which we deliver as standard. Assign a different valuation variant to each of the costing variants you want to use to store costings. If you do this, you will subsequently be able to change the valuation strategies as and when you want. Activities

1. Enter an alpha-numeric key and an appropriate short text for the costing variant.

2. In the detail screen, assign a costing type and a valuation variant to the costing variant.

If you want to use your own paramters, you must carry out the steps Define costing types and Define valuation variants.

3. If you are using the costing variant for a model costing, you stipulate whether cost elements have to be assigned to the costing items. The costs for other reference objects in the unit costing must be totaled using cost elements.

Further notes You need the costing variant for:

• The costing (plan costs) and cost determination (actual costs) for networks and network activities.

Store two costing variants: one for plan costs and one for actual costs

o As default values for the application in the Project System implementation guide in the network parameters for the network type

o In the application, in the extras for the network header (if you did not define a costing variant in the network parameters In the network header data, choose Goto -> Network header -> Supplement.

• The unit costing for projects or WBS elements

You define the costing variant:

o As a default value for the application in the cost planning profile

o In the application, when you access the unit costing from structure- oriented cost planning




13/12/200238

ASSIGN PLAN PROFILE TO COSTING VARIANT In this process step you assign the costing variant to the plan profile. This assignment determines how the system costs and valuates a project with the appropriate plan profile. You should bear in mind that the system uses the costing variant from the plan profile only as a default value. You can override this assignment when you create the cost estimate by entering a different costing variant. Activities Assign a costing variant to the plan profile.

ASSIGN PLAN PROFILE TO PROJECT PROFILE In this step, you assign the plan profile to the project profile.




13/12/200239

MANUAL COST PLANNING IN WBS In this step, you enter the settings, which enable you to plan costs manually in the WBS element. You can choose the following planning forms in the Project System:

• Hierarchy planning

o Costs (cost-element independent)

• Detailed planning

o Primary costs

o Activity input

o Statistical key figures

o Overhead

• unit costing

Menu path: IMG-> Project System -> Costs -> Planned Costs -> Manual Cost planning in WBS -> Hierarchical Cost Planning

In this step, you enter the settings for structure planning.

CREATE/CHANGE PLANNING PROFILE In this step, you create new plan profiles or maintain existing ones. You need planning profiles for the planning methods below:

• Overall planning for internal orders

• Hierarchy cost planning for projects

• Preliminary costing for production orders that do not have a quantity structure (CO production orders).

• Cost planning for investment programs or investment measures, and for appropriation requests.

• Financial budgeting

You can create new planning profiles, or change existing ones. The following settings are important:

• Time frame

You can specify which values are to be planned, and in which fiscal years.

• Value display

You can specify which standard view the system is to display with the plan value, when you call up the initial screen for planning. You can default the number of decimal places and the display factor.

• Detail planning

This is where you store default values for cost element planning, activity input planning, and unit costing. You use the plan profile to regulate the following project-specific settings:




13/12/200240

• Planning on all WBS elements or only on planning elements

• Bottom-Up planning within hierarchical planning

• Automatic revenue planning

You can decide whether the system updates plan revenues on the corresponding billing elements. Where necessary, the same applies to plan payments from sales documents that have been assigned to projects.

Prerequisites To include the following as default values in planning, you need to do the following IMG activites and maintain the parameters.

• Maintain Cost Element Groups

o Primary costs

o Revenues

• To plan activity input

o Maintain Cost Center Groups

o Maintain Activity Types

o Maintain Activity Type Groups

• Maintain Statistical Key Figure Groups

• For unit costing

Create Costing Variant Activities Activities

1. Check the planning profiles provided by the SAP standard.

2. If necessary, change the detail settings for the existing planning profiles. Alternatively, create new planning profiles by choosing "New entries".

3. Assign the planning profile to an order type, program type, appropriation request type, project or FM area.

ADDITIONAL INFORMATION You can assign planning profiles to a project as follows:

o As a default value in the Implementation Guide (IMG) for the Project System

- In the project profile of a project definition (operative structures) - In the project profile of a standard project definition (basic data)

o In the application menu for the project system

o In the control data of the project definition, if there is planning profile was stored in the project profile (In the maintenance screen for the project definition, choose "Detail -> Control").




13/12/200241




Now Assign plan profile of BALCO to project profile of BALCO

13/12/200242

BUDGET

In this step, you make the system settings for budget allocation. In this step, you

• create new budget profiles

• define parameters for new budget profiles

• change existing budget profiles To be able to budget projects, you must create a budget profile or use an existing one. The following parameters are relevant for project budgeting:

• Time horizon Here you define:

o the number of years in the past from the start year, for which budgeting is possible

o the number of years in the future from the start year, for which budgeting is possible

o budgeting start year, a relative specification referring to the current fiscal year

o budgeting for overall and/or annual values

• Display

o standard view as well as the budget value when you access the function

o decimal places and scaling factor as default values

• Currency translation

o exchange rate type

o value date

• Availability control

o activation type and percentage of consumption for background activation

o of annual/overall budget

o of releases




13/12/200243

In the project budget profile, the "Overall" indicator, working in conjunction with the "Releases" indicator, has the following effect:

Ind. "Overall" Ind. "Releases" Avail. control against...

X X Released overall budget

- X Released annual budget

X - Overall budget

- - Annual budget

The activation type controls availability control. There are three activation types:

0 = cannot activate

This activity type may cause an already active availability control to be deactivated.

1 = automatic activation when budget is assigned

You must maintain at least one tolerance limit for the budget profile.

2 = background activation when percentage of consumption is exceeded

You must enter a percentage of consumption in background activation. The percentage of consumption represents the relationship of committed funds to the budget as a percentage.

You must maintain at least one tolerance limit for the budget profile to have the system check the posting.

Note

o If you change the availability control configuration after budgeting, you should have the system recalculate the assigned values. To do this, restart availability control for your project.

o If you are also using the Funds Management component, you can greatly improve performance by only activating availability control in Funds Management or only activating it for projects.

Activity 1. Use "Details" to check the standard budget profiles delivered with the system.

2. Change the detail settings for the budget profiles or create budget profiles using "New entries". Additional information You can assign a budget profile to a project

• as a default value in Project System configuration

o in the project profile for a project definition (operative structures)

o in the project profile for a standard project definition (basic data)

• in the Project System application menu




13/12/200244

o in the control data for the project definition (Operative structures menu, Work breakdown struc -> Change -> Project definition, Details -> Organization -> Plan profile

STIPULATE DEFAULT BUDGET PROFILE FOR PROJECT DEFINITION In this step, you assign the budget profile to the project profile.




13/12/200245

DEFINE TOLERANCE LIMITS In this step you enter the tolerance limits for availability control. Availability control can identify budget overruns in a project at an early stage and initiates various actions. You activate availability control for a certain budget profile. You can specify one or more tolerance limits for each activity group for a budget profile. Selected actions (warning, warning with mail to person responsible for project, error message) are triggered when these limits are reached. Requirements You must have maintained the appropriate activation type in the budget profile to activate availability control. Activities Define the tolerance limits for each activity group for the budget profile you are using. Further notes You define the tolerance limit for all activity groups with activity group ++. This activity group should make entry easier. You can use it if you do not want to define a separate tolerance limit for each activity group. You can also define a limit for a specific activity group in addition to a tolerance limit which is defined for "all activity groups". This additional tolerance limit has priority over the "generally" valid tolerance limit.

Here in BALCO, the system will not allow the procurement once the budget is exceeded over 100%.




13/12/200246

MATERIAL PROCUREMENT In this section you set up the system for procuring materials:

• You can define combinations of settings for component procurement that are frequently used, so that you do not have to maintain these settings for each component.

• You can check the following settings:

o Account assignment types and purchasing document type of the purchase requisitions for networks

o Movement types for goods movements in the Project System

You only have to make changes here, if you do not want to use the SAP standard settings.

• You can activate MRP groups for requirements grouping.




13/12/200247

Important : For change in decision only : For making all items as non stock items (if required) , the following can be used along with the changes in the Project Profile




13/12/200248

DEFINE MOVEMENT TYPES FOR PROJECT MATERIALS




13/12/200249

MONITORING DATES Menu path : Project system -> Material -> Monitoring dates-> Define events In the following steps you configure the system for Monitoring Dates. You can use this function to define events for components in a project and to monitor the dates of these events.

DEFINE EVENTS In this activity you define events for components in a project. You can then monitor dates for this event. Activities

1. Create a new event by choosing New entries.

2. Enter a name and description for the event.

3. Save the event

ASSIGN REFERENCE DATES TO EVENTS In this activity you assign a reference date to a date type for an event. You can use date fields as reference dates. These date fields could, for instance, come from the network activity or a sales document. Requirements You must have already defined the event. Activities

1. Choose New entries.

2. Enter an event and a date type.

3. Assign a reference date to the date type and event by selecting a table and a field in this table.

If you select Confirmations for purchase order item as the table, an additional field appears in which you have to enter the Confirmation category.

4. If the assigned reference date is not unique, determine which date the system should use by selecting an entry in Display.

5. Save your data.




13/12/200250




DEFINE PROFILES FOR MONITORING DATES In this activity you define profiles for monitoring dates. Here you specify which date types the system should display in the dates overview and how date variances should appear on the screen. You do not have to define profiles, you can make the same settings in the dates overview. Activities

1. Choose New entries to create a new profile and enter a name and description for the profile.

2. Set an indicator for those date types that you want to display in the dates overview.

3. Click on the traffic lights to determine how variances between the date types should be portrayed.

4. Save the profile.

13/12/200251

CONFIRMATION OF WORK Menu path : Project system -> Confirmation

DEFINE CONFIRMATION PARAMETERS The configurations for the confirmation are specified for each plant and network type. You can specify the following parameters:

• when confirming, a final confirmation is automatically proposed

• the dates of the confirmation may lie in the future

• the error log for cost calculation is displayed

• percentages for the allowed deviation from work and duration

Define the confirmation parameters per plant and network type.




13/12/200252




PARTIAL/FINAL CONFIRMATION Specifies what sort of confirmation is to be automatically proposed. For automatic final confirmation, the confirmed quantity of the operation or the order (yield qty + rework qty + scrap qty) determines whether the confirmation is saved as a partial or final confirmation:

• If the confirmed quantity is less than the quantity possible, the confirmation is saved as a partial confirmation.

• If the confirmed quantity is more than (that is, greater than or equal to) the quantity possible, the confirmation is saved as a final confirmation.

The quantity possible corresponds to the planned operation or order quantity, or to the confirmed yield of operations that have been finally confirmed, provided that finally confirmed operations exist.

PROPOSE DATES Specifies that for the confirmation of operations, the system is to propose the start and finish dates of the individual operation segments, as calculated by lead time scheduling. The system differentiates between the proposed dates before the first confirmation and the proposed dates before all other confirmations: The following dates are proposed for the first confirmation:

• In the start of work field: The earliest start date of the operation or, if this date is in the future, the current date with the time

13/12/200253

• In the end of work field: The current date with the time

The following dates are proposed for all other confirmation:

• In the start of work field: The actual finish of the last confirmation

• In the end of work field: The current date with the time

DEFINE CAUSES FOR VARIANCES You can define causes for variance from the defaults in confirmation. Example Variances can be:

• excess activity consumption

• longer execution time

• activity was carried out at a different work center

By linking the key for a cause for variance with a user status, you can trigger a milestone function automatically based on the cause.




13/12/200254

PROJECT PROGRESS ANALYSIS

MAINTAIN PROGRESS VERSION In this step, you maintain the progress version. You define the control data for POC/earned value calculation. You enter this setting separately for each company code. Example Recommendation Use the standard progress version. Activities

1. In the section General Version Definition, create a CO version with only the usage progress analysis.

2. Save this version.

3. Select the version and choose Project Progress Analysis Settings.

4. Enter the control data for the progress version and choose Save.

DEFINE STATISTICAL KEY FIGURE FOR PERCENTAGE OF COMPLETION In this activity, you stipulate the statistical key figures in which the percentages of completion (POCs) are recorded. You make the settings per controlling area. A statistical key figure must be assigned so that you can evaluate the POC in reporting.




13/12/200255

You can define three different key figures for each controlling area. They differ in how they are used. The following usage types are possible.

• Nonaggregated POC

• Aggregated POC

• POC for results analysis

Activities Define the statistical key figures required for a controlling area.

DEFINE MEASUREMENT METHODS In this step, you can define the measurement methods to be used for determining a percentage of completion. A measurement method is made up of a measurement technique that is predefined in the SAP System, and additional parameters, such as a starting percentage of completion.

EXAMPLE For the measurement method start-finish rule, the following measurement methods are specified:

• Method 0-100 with a start percentage of completion of 0.

• Method 20-80 with a start percentage of completion of 20.

You can use the following measurement techniques in the SAP System: Start-finish rule When you use the start-finish rule for progress analysis, the percentage of completion at the start is zero (0) or the "start" percentage of completion. If the finish date is reached, the percentage of completion is 100%. For the start-finish rule, you enter a percentage rate for the start percentage of completion and a short text in the measurement method. The usual values for the start-finish rule are:




13/12/200256

o 0 - 100: The start percentage of completion is 0 %



You can use the start-finish rule to make a quick rough initial estimate of project progress. You should only use the start-finish rule if want an analysis of an entire project structure. Milestone method Each milestone corresponds to the portion of an activity or WBS element that was performed or produced:

• If the fixed date of the milestone is reached, the planned percentage of completion of the WBS element or the activity is set to the percentage of completion which you entered for the milestone.

• If the actual date of the milestone is reached, the actual percentage of completion of the WBS element or the activity is set to the percentage of completion which you entered for the milestone.

For the milestone method, you only have to enter a short description. Estimate For the measurement technique "estimate", you enter the percentage of completion manually in the work breakdown structure or in the network. Enter a maximum percentage of completion and a short description for the estimate. As long as an activity is not completed, that is, no actual finish date has been entered, the actual percentage of completion cannot exceed the maximum percentage of completion. The maximum percentage of completion should prevent an overvaluation of activities that are "almost finished" (the "90% syndrome"). SAP recommends that you use 80% as the maximum percentage of completion for estimates. Degree of processing The degree of processing from the confirmation is copied as the percentage of completion. You can use the degree of processing measurement technique for internally processed activities which are confirmed. You only have to enter a short description for the degree of processing. Actual=Plan The plan percentage of completion is adopted as the actual value. Time proportionality This measurement method determines the percentage of completion proportional to the time required. The system assumes linear project progress over time. You can use this measurement technique for short report periods or for activities such as consulting or administration. For time proportionality, you enter a maximum percentage of completion and a short description. Cost proportionality This method determines the percentage of completion proportional to the cost distribution. Quantity proportionality This method determines the percentage of completion proportional to the quantities used. Secondary proportionality For this measurement technique, the work performed for one project object depends on the progress of work in another project object. Example of secondary proportional method There are two activities in a network, "Create drawings" and "Check drawings". A drawing is complete only after it has passed inspection. The percentage of completion of activity "Check drawings" is copied for the activity "Create drawing" when you use this measurement technique. You only have to enter a short description for the secondary proportional method. Standard settings Measurement methods for all measurement techniques are available in the standard system. Activities

1. Check the available measurement methods.

2. Define your own measurement methods, if necessary.




13/12/200257




13/12/200258

DEFINE MEASUREMENT METHOD AS DEFAULT VALUE In this activity, you define the measurement methods for the calculation of the percentage of completion (POC) as default values for the various object types in the Project System. The settings are made per controlling area. Activities

1. Enter a controlling area as the work area.


3. Maintain the following data:

o Earned value version

o Object type

o Whether the POC is calculated for plan or actual values

o Measurement method

Further notes The measurement method defined here is a default value which you can overwrite when maintaining object master data. The measurement method is only displayed in the detailed data for an object if you maintain a progress version for the object. You define the measurement method for orders assigned to the project in the activity Define default value for measurement methods for orders.




13/12/200259

MAINTAIN ASSIGNMENT OF COST ELEMENT GROUP In this activity, you define cost elements for cost element groups used in evaluation for earned values by cost element and stipulate the default cost element. The percentages of completion (POCs) calculated for an original cost element group are recorded in summarized form under the relevant cost element; you can evaluate them in the information system. This procedure means you can make various analyses of the POCs. Activities

1. Enter a controlling area as the work area.


3. Specify the following:

a) Cost element under which the POC is recorded.

The cost element must have cost element type 61.

b) Cost element group containing the basis values

4. Select the Def indicator.

If the indicator is not set, the POCs are recorded under this cost element at basis values and not by cost element

STATISTICAL KEY FIGURES In the following steps, you make the system settings you need to work with statistical key figures. You will work with statistical key figures if you want to administer an additional measuring point in WBS elements and activities: for example, earned value analysis or internal activity allocations.




13/12/200260

ASSIGN STATISTICAL KEY FIGURES TO VALUE CATEGORIES In this step, you define statistical key figures as value categories. Requirements The value categories must have been maintained. For more information, see Maintain value categories.

MAINTAIN VALUE CATEGORIES In this step, you define value categories. Value categories are intervals of:

• Cost elements

• Commitment items

• Statistical key figures

These are required for:

• Updating the project information database

• Calculating project interest

• Defining structure reports for costs, revenues, and payments

• Updating quantities in the project info database RPSQT

Activities

1. Select a value category which is allowed for the posting of statistical key figures.

2. Call up the detail screen.

3. Enter a statistical key figure or an interval. Further notes Note that the unit of measure for the value category must agree with aggregation processing in the statistical key figure. For example, if the unit of measure in the value category is HRS; the total value or fixed value in the statistical key figure must also be HRS.




13/12/200261

INFORMATION SYSTEM

DEFINE DATABASE SELECTION PROFILES All data in the information system comes from or is derived from the logical Project System database (PSJ). You need the profile for this database for all analyses in the Project System. In the database profile, you determine:

• the project view according to which the selected data is displayed on the screen, for example, sorted according to profit center.

• the maximum explosion level for the selection.

The level of detail depends on the project view and the selection criteria. Example: You select the following objects in the database:

o a work breakdown structure that has five hierarchy levels

o a network, including subnetworks, that has four hierarchy levels.

You maintain 5 as a maximum level. In this case, the network objects will not be displayed in the information system.

• the objects that are selected in the database.

Notes Once you are within an analysis, you cannot select any more objects from the database. You determine the scope of selection on the relevant initial screens. Standard settings Database profiles are available with the standard R/3 System. Activities

1. Create a database profile.

2. Enter the database profile in the overall profile.




13/12/200262




13/12/200263

DEFINE PROJECT VIEW FOR INFORMATION SYSTEM You can enter a structure for the data selected from the database. The information system then displays the data according to this structure. The hierarchy type in the detail screen determines the view:

View Hierarchy type

Project structure 1

Profit Center 2

Cost centers 3

Classificaition 4

Capital-inv.prog. 5

Sales & dist. 6

Customer-specific 99

The presentation of the data according to hierarchy category 7 is basically the same as that of hierarchy category 4 . However objects below a summarization node in a list are displayed without hierarchy information. This results in much better performance. Notes The project view no longer selects data from the database, but merely determines how the data is displayed in the information system. Standard settings The standard system contains the following project views:

• project structure

• Profit Center

• cost centers

• characteristic hierarchy from classification

• capital-investment programs

• sales and distribution

Activities 1. Create your own project view as required. When doing so, note the following:

o In hierarchy types 1, 5, 6, 99, enter just the name of the view and the hierarchy type.

o In hierarchy types 2, 3, enter the name of the view, the hierarchy type and the set name for the profit center or the cost center hierarchy.

o In hierarchy type 4and 7 , you enter the name of the view, the hierarchy type and the hierarchy name.

2. Store the project view in the database selection




13/12/200264




13/12/200265

PROJECT INFO DATABASE (COSTS, REVENUES, FINANCES) In this step, you control the update of the project information database. The project-relevant costing, revenue and payment data is updated from the operative systems (FI, CO, MM, SD and so on) in it. It allows fast database access for:

• Hierarchy reports

• Interest calculation

• Earned value analysis

• Planning board

• Project versions

For this reason, the cost elements and commitment items are grouped together in value categories. The update can either be carried out at real-time (V1 update) or delayed (V2 update). The V2 update makes sure that the performance of the posting functions is not impaired by the update of the project information database. When you change releases, take over data or make subsequent changes to control data for the update, you must reconstruct the project information database.

V2 UPDATE Indicator which controls how summarized project data is updated.

• Indicator set = V2 update

There are delays in updating data. For performance reasons, the indicator is set in the SAP standard.

• Indicator not set = V1 update (direct update)




13/12/200266

CREATE VALUE CATEGORIES AUTOMATICALLY If this indicator is set, automatically creates a value category for each commitment item or cost element newly posted to, giving it the same description. If the indicator is not set, you must maintain the assignment of cost elements and commitment items to value categories manually. The advantage of doing this is that you can assign groups or ranges of cost elements/commitment items to one value category. This significantly improves performance. If you set this indicator after postings have already been made, you must maintain the missing assignments manually or reconstruct the project information database. Otherwise, no value category is assigned to cost elements/commitment items to which postings have already been made.




13/12/200267

AUTHORIZATIONS IN THE PROJECT SYSTEM OF BALCO The Project System distinguishes between two forms of authorization:

• object-related authorizations

• authorizations for functions, which are also used in other applications

All the authorizations, which you need for working in the Project System, are included in the standard SAP authorization profile C_PS_ALL In BALCO, the following ROLES for authorizations have been defined: ROLE Activity Z-PS_DISPLAY To display transactions Z-PS_OPR_WBS_CREATE To create WBS, Network, activities Z-PS_PROJ_BUDG_APPR To approve the Budget Z-PS_PROJ_CLSR To close the project Z-PS_PROJ_COST_PLNR To plan the cost of the project Z-PS_PROJ_REL To release the project (to start procurement etc.) Z-PS_PROJ_RES_ACT_CNFR To confirm the activities Z-PS_PROJ_SCHED_PLNR To schedule the project Z-PS_REPORTS To view reports The transaction codes are attached against the above role for a particular activity.




13/12/200268

REPORTS FROM PROJECT SYSTEM

1 PS01 Logistics-Project Systems-Information Systems Tree (All Reports)

2 CN41 - Structure Overview

3 CN42N - Project Definitions

4 CN43N - WBS Elements

5 CN46N - Networks

6 CN47N - Activities

7 CN49N - Relationships

8 CN53N - Milestones

9 S_ALR_87013531 - Costs/Revenues/Expenditures/Receipts

10 S_ALR_87013532 - Plan/Actual/Variance

11 S_ALR_87013533 - Plan/Actual/Commitment/Rem.Plan/Assigned

12 S_ALR_87013534 - Plan 1/Plan 2/Actual/Commitments

13 S_ALR_87013535 - Actual in CO Area/Object/Transaction Currency

14 S_ALR_87013536 - Plan/Actual/Down Payment as Expense

15 S_ALR_87013537 - Commitment Detail

16 S_ALR_87013538 - Project Version Comparison: Actual/Plan

17 S_ALR_87100185 - Actual Costs for Each Month (Current Fiscal Year)

18 S_ALR_87100186 - Planned Costs for Each Month (Current Fiscal Year)

19 S_ALR_87100187 - Commitments for Each Month (Current Fiscal Year)

20 S_ALR_87100188 - Cumulated Actual Costs

21 S_ALR_87100190 - Plan/Actual/Variance for Each Project and Person Respon

22 S_ALR_87013557 - Budget/Actual/Variance

23 S_ALR_87013558 - Budget/Actual/Commitment/Rem Plan/Assigned

24 S_ALR_87013559 - Budget/Distributed/Plan/Distributed

25 S_ALR_87013560 - Budget Updates

26 S_ALR_87100191 - Receipts/Expenditures in Fiscal Year

27 S_ALR_87013573 - Receipts/Expenditures for All Fiscal Years

28 S_ALR_87013575 - Plan/Actual/Commt

29 S_ALR_87013574 - Expenditures

30 me5j Purchase requisitions

31 ME2J Purchase Orders




13/12/200269

32 MBBS Stock Overview

33 CN40 Project Overview

34 CN41 Structure Overview

35 CN42 Overview: Project Definitions

36 CN43 Overview: WBS Elements

37 CN46 Overview: Networks

38 CN47 Overview: Activities/Elements

39 CN48 Overview: Confirmations

40 CN52 Overview: Components

41 CN53 Overview: Milestones

42 CNB1 Display Purchase requisitions for project

43 CNB2 Display Purchase orders for project

44 CNE1 Project progress (individual proc.)

45 CNE2 Project progress (collective proc.)

46 CNE5 Progress Analysis

47 CNMT Milestone Trend Analysis

48 CJ74 Project Actual Cost Line Items

49 CJ76 Project Commitment Line Items

50 CJ7M Project Plan Cost Line Items

51 CJI3 Project Actual Cost Line Items

52 CJI4 Project Plan Cost Line Items

53 CJI5 Project Commitment Line Items

54 CJI9 Project Struct.Pld Costs Line Items




13/12/200270

TRANSACTION CODES IN PROJECT SYSTEM

1 CJ20n Create Work Breakdown Structure

2 CJ02 Change Work Breakdown Structure

3 CJ06 Create Project Definition

4 CJ07 Change Project Definition

5 CJ11 Create WBS Element

6 CJ12 Change WBS Element

7 CJ20 Structure planning : Change

8 CJ20N Project Builder

9 CJ21 Change Basic Dates

10 CJ25 Change Actual Dates

11 CJ27 Project planning board

12 CJ2B Change project planning board

13 CJ2D Structure planning : Create

14 CJ40 Change Project Plan

15 CJ91 Create Standard WBS

16 CJ92 Change Standard WBS

17 CJ9BS Copy Project Planning

18 CJ9CS Copy Project Actual Data to Plan

19 CJ9D Copy Plan Versions

20 CJR2 PS: Change plan CElem/Activ. input

21 CJR4 PS: Change plan primary cost element

22 CJSG Generate WBS Element Group

23 CN01 Create standard network

24 CN02 Change standard network

25 CN04 Edit PS Text Catalog

26 CN11 Create standard milestone

27 CN12 Change standard milestone

28 CN21 Create Network

29 CN22 Change Network

30 CN24 Overall Network Scheduling

31 CN25 Confirm Completions in Network

32 CN27 Collective confirm.




13/12/200271




33 CN29 Cancel Network Confirmation

34 CJ30 Change Original Budget

35 CJ34 Transfer Project Budget

36 CJ35 Return Budget from Project

37 CJ36 Supplement Budget to Project

38 CJ37 Budget Supplement in Project

39 CJ38 Return Budget in Project

40 CJ3A Change Budget Document

41 ME51 PR Creation

42 CJ88 Individual settlement for relevant WBS

43 CJ02 Change relevant WBS status to "PTU"

44 CJ02 Change relevant WBS status to "TECO"

45 AIAB Maintence of settlement rule for AUC

46 AIBU Settle AUC to Fixed Asset

Education

Balco ps configuration manual