Job Inteview Ps Quiestions

Project System provides tools to track project milestone, costs and resources. SAP's Project System module contains tight integration to the Controlling, Human Resources, and Logistics modules. It utilizes personnel records from HR, rolls costs into Controlling and links to materials or customers in the Logistics modules.

Two key objects that define the Project in SAP are:

Work Breakdown Structure - defines tasks and assign resources to those tasks

Network - defines the dependencies within the Work Breakdown Structure (WBS)

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

One definition from the Project Management Institute is as follows:

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

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

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

It shows the work involved in a project.

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

It can be linked through DIP Profile and do Resource Related Billing for raising billing.

No, it can be done at WBS level with 'Billing' operative indicator.

Yes, You can use Progress Analysis (EVA) for this.

When a project status is set back to REL from TECO or CLSD status, the workforce planning done is getting deleted completely at the activity. Run cmp9(Evaluation again) and you will have workforce planning back.

It is another function for planning costs at WBS elements level. It uses the existing Controlling, purchasing or MM data in the form of costing items. Also you can have predefined costing models to simplify repeated entries.

Settlement rules are nothing but settling the account for a cost center.Which WBS are account assigned the cost of corresponding WBS should be settled to the respective cost center assigned for that WBS.Settlement rule is assigned in settlement profile in which you will define (like asset) the rules of settlement.

A project is a system which involves 1. project, sub-project, activities & tasks. It will have the good integration with the other modules like MM, Fi/co, & PM modules.

Settlement will take place via profitability segment . Level 1 WBS should have settlement rule define to be settled to PSG and level 2 WBS should be settled to superior one WBS element .The main one level 1 WBS/ Project will be settled to PSG , and variance will be posted to COPA .

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

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

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

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

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

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

Project Code has 2 parts

Part 1: Project Identifier (Project Coding Mask)

Part 2: Project Number (usually a serial number)

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

Unit costing is a means of recording all the costs - direct and indirect - associated with the delivery of services. Total cost of service provision divided by the total amount of service provided.

Whenever the confirmation of activities done and if the milestone is attached with that particular activity the milestone triggers the milestone as per the configuration done and it will do the billing through SD module.

LSMW is an encapsulated data transfer tool. It can provide the same functionality as BDC in fact much more but when coming to technical perspective most the parameters are encapsulated.

To list out some of the differences :

LSMW is basically designed for a functional consultant who do not do much coding but need to explore the functionality while BDC is designed for a technical consultant.

LSMW offers different technique for migrating data: Direct input ,BAPI,Idoc,Batch input recording. While bdc basically uses recording.

LSMW mapping is done by SAP while in BDC we have to do it explicitly .

LSMW is basically for standard SAP application while bdc basically for customized application.

Level 1 WBS should have settlement rule define to be settled to PSG and level 2 WBS should be settled to superior one WBS element .The main one level 1 WBS/ Project will be settled to PSG , and variance will be posted to COPA . ??????

KKA2 for calculating result Analysis;

KKAJ - for calculating WIP

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

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

It can be found at the following location:

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

Transaction is OPSK

Maintenance order.

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

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

Transaction is OPSJ

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

For Project Definition and WBS Elements:

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

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

For Networks:

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

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

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

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

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

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

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

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

Transactions is OPTY

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

What are the fields in pricing procedure?

There are 16 fields that are given below:

Step

Counter

Condition type

Description

From

To

Manual

Mandatory

Statistic

Print

Subtotal

Requirement

Alternative calculation type

Alternative condition base value

Account key

Accrual

BA00 for order LD00 for delivery RD00 for billing and RD03 for Cash sales

Condition type is a pricing element such as discount,freight,surcharge.This are used in pricing procedure to represent condition record.

Delivery document is an electronic document where store when how much quantity of materials and where the materials should go on the other side, scheduling represent when materials will be delivered in that case backward scheduling and forward scheduling is used.

In general item category determination is happened through sales document type+item usage+item category group+higher level item category +default item category

In the creating from reference document item category determination is happened from copy control where source item category to target item category.if it is not maintained ,item category determination is happened though normal determination like sales document type+ item usage+item category group + higher level item category+default item category.

Condition table+Access sequence+Condition type+pricing procedure=condition technique. The above extract is used to find suitable condition record.

A plant may be delivering plant and production plant and storage plant. In Sales and Distribution, since plant is assigned with sales organization and distribution channel, it is called delivering plant.

The transaction code is the short path to reach a specific screen in SYSTEM. Instead of going through the routine menu, you can enter the Transaction Code and then press “Enter,” which would directly take you to the specific transaction. For exam-ple, you can access the VA22 transaction code to reach the Change Quotation screen. However, the VA01 transaction code is used to create Sales document in SYSTEM.

The comparison key that helps you to find the key of a specific database record, depending on the field value entered in the record, is known as match code. On the basis of the match code, the system then displays a list of records from which you can select the appropriate one.

Customer master is a part of the SD module and forms the basis for customer-related transactions. It is divided into three areas:

General Data—It is used for the maintenance of general customer details such as name, address, phone/fax nos., and so on.

Sales Area Data—It is used for Sales-related data maintenance.

Company Code data—It is used for accounts-related data maintenance.

The Implementation Guide (IMG Menu) is used to collectively group the areas that must be configured and customized, and form a basic structure of an organization in the System to run.

To maintain a company code, navigate the following menu path:

Customizing Implementation Guide (MG Menu)). Enterprise Structure > Definition > Financial Accounting > Edit, Copy, Delete, Check Company Code.

ERP is a way to integrate processes and data of an organiza-tion into a single system to provide easy access and workflow in an organization. It refers to the way in which large organizations efficiently plan to use resources to their fullest.

The advantages of implementing an ERP system in an organization are as follows:

Various processes and workflow of an organization are integrated in a single system.

Efficient utilization of resources in an organization.

Ability to easily share organizational data across different departments.

Improves efficiency and productivity levels.

Lower costs

Better customer service.

Relationship basically denotes how activities in a network order are related to each other.They can be classified into 4 categories - SS (Start-Start), SF(Start-Finish), FF (Finish-Finish), FS (Finish - Start). For 2 activities say A and B

SS -->> Both A and B start together

SF -->> Start of A coincides with finish of B and so on.

We can also specify the time gap between which these relationships work. Say in an SS relationship, there can be a 10 minutes gap between start of A and B and so on.

In Valuated stock every material in stock is managed on a both a quantity basis and a value basis. The monetary value of each quantity of material is calculated separately. while non valuated material is maintained as per quantity and not on the basis of its value.

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

Materials Management (MM) – Based on Materials and BOMs, PS has the ability to create Reservations, Purchase Requisitions and Purchase Orders via Easy Cost Planning Execution Services and Networks in general. This powerful integration makes PS a key player in the logistics cycle, including the ability to handle Services via Service Masters. Further, the ability of Networks to work with Catalogues takes PS into SRM (Supply Relationship Management), where the internet plays a large part in sourcing

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

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

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