Project Functionality of - SAP-PS (Project System) The Project System module of SAP (PS) is specifically designed to provide comprehensive and fully integrated project management functionality for SAP customers. When it was originally designed and developed its core functionality was borrowed from and shared with the PP and CO modules. So most of the PS objects (WBS elements, networks, activities, activity elements) are cost objects similar to cost centers in CO, while networks have scheduling and resource management capabilities that are very similar to PP. Whenever you need flexibility and frequent user interaction for resource loaded scheduling activities, you still feel the remnants of an architecture and user interface that was originally designed for the more static context of PP. Shortcomings include user-friendliness since SAP did not manage to satisfactorily put the end user in control to easily manipulate the data. In that respect, SAP's unsurpassed enterprise functionality often is perceived as an issue by end-users. Also, and somewhat ironically, PS and PP are not seamlessly integrated. This means that costs or dates do not roll up or cannot be pushed down between PS &PP. What is SAP PS? Projects are generally part of the internal processes of a company. To be able to control all tasks in project execution, you need an organizational form that is specific to the project and which is shared by all departments involved. Before you can carry out a project in its entirety, the project goals must be precisely described and the project activities to be carried out must be structured. A clear, unambiguous project structure is the basis for successful project planning, monitoring, and control. The high degree of integration between the Project System (PS) and other R/3 application components means that you can plan, execute, and account for projects as part of your normal commercial procedures. This means the Project System has constant access to data in all the departments involved in the project. The R/3 PS guarantees close and constant monitoring of all aspects of your project including both technical and commercial aspects of the project. Versions in Project Systems Explain the type of version in SAP Project Systems. Basically, there are different kinds of versions in PS. They are: 1. Project versions - these are basically snapshots of a project at different stages of a project. Based on how the system is set up, a version could be created everytime the system status of a project object is changed, for example. Or, you could manually create a project version in transaction CNS41 or the like. You could create a version with a key and then you could compare the different snapshots of a project against each other or against version 0 (operative project). 2. Simulation versions - these are essentially "play around with" versions. Meaning that you could use them to try "what if" kind of scenario by changing dates, structure, milestones, etc... and compare results with the operative version. For example, you may want to determine what
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Project Functionality of - SAP-PS (Project System)
The Project System module of SAP (PS) is specifically designed to provide comprehensive and fully integrated project management functionality for SAP customers. When it was originally designed and developed its core functionality was borrowed from and shared with the PP and CO modules.
So most of the PS objects (WBS elements, networks, activities, activity elements) are cost objects
similar to cost centers in CO, while networks have scheduling and resource management capabilities that are very similar to PP. Whenever you need flexibility and frequent user interaction for resource loaded scheduling activities, you still feel the remnants of an architecture and user interface that was originally designed for the more static context of PP.
Shortcomings include user-friendliness since SAP did not manage to satisfactorily put the end user in
control to easily manipulate the data. In that respect, SAP's unsurpassed enterprise functionality often is perceived as an issue by end-users. Also, and somewhat ironically, PS and PP are not seamlessly
integrated. This means that costs or dates do not roll up or cannot be pushed down between PS &PP.
What is SAP PS?
Projects are generally part of the internal processes of a company. To be able to control all tasks
in project execution, you need an organizational form that is specific to the project and which is
shared by all departments involved. Before you can carry out a project in its entirety, the project
goals must be precisely described and the project activities to be carried out must be structured.
A clear, unambiguous project structure is the basis for successful project planning, monitoring,
and control.
The high degree of integration between the Project System (PS) and other R/3 application
components means that you can plan, execute, and account for projects as part of your normal
commercial procedures. This means the Project System has constant access to data in all the
departments involved in the project.
The R/3 PS guarantees close and constant monitoring of all aspects of your project including
both technical and commercial aspects of the project.
Versions in Project Systems
Explain the type of version in SAP Project Systems. Basically, there are different kinds of
versions in PS. They are:
1. Project versions - these are basically snapshots of a project at different stages of a project.
Based on how the system is set up, a version could be created everytime the system status of a
project object is changed, for example. Or, you could manually create a project version in
transaction CNS41 or the like. You could create a version with a key and then you could
compare the different snapshots of a project against each other or against version 0 (operative
project).
2. Simulation versions - these are essentially "play around with" versions. Meaning that you
could use them to try "what if" kind of scenario by changing dates, structure, milestones, etc...
and compare results with the operative version. For example, you may want to determine what
the impact is going to be of a certain change to the project before making the actual change to the
operative project. Then, you could create a simulation version, play around with it to make sure
it does what you want it to do, then make the actual change to the operative change or you could
convert the simulation version to the operative version also. I am not sure if they are hidden
issues in doing this, but to make the point here, the simulation version is a "play ground" for
"what if" scenarii for the project. The main difference, I believe, between the project and
simulation versions is that project versions cannot be changed/modified once they are copied,
while simulation versions can be. Also, you cannot copy a project version to an operative
version, but you can copy a simulation version to an operative version.
3. Planning/Controlling versions - these are the versions used for storing different kinds of
planning details for the project. Essentially, these versions are also "operational" and can be
changed as needed. For example, you may want to keep the operative version (version 0) always
for actual costs, while you will use planning version P1 to store planned values from ECP, then
version P2 for Unit Costing values, etc... Unlike simulation versions however, you cannot copy a
planned version to the operational
project (I don't think). You can however, copy one plan version to the other.
4. Progress Versions - These versions are used for carrying out Earned Value Analysis and
other measurements against project progress based on POC, etc. Progress version is controlling
area specific and defines the control data for POC and earned values. It is mandatory to maintain
progress version along with method of calculation. The system records progress analysis data in
the progress version. That is why you can get the result only if you maintain it in the progress tab
of WBS.
SPRO -> Project System -> Progress-> Progress Analysis -> Define Measurement Method as
Default.
Here you define the Version, Object Type, Plan/Actual, Default Measurement Method.
After that Version would be defaulted for the object in the hierarchy.
SAP PS – Basics of Project System- http://www.sap-basis-abap.com/sapps.htm
This course covers basic SAP Project System in 10 lessons, including master data, project
planning, acquisitions, network activities and settlements using the new Project Builder. This is
an interactive simulation course and includes simulated SAP screens. This allows you to interact
with the screens just like a real SAP system, including entering data in fields and clicking on
buttons or links.
SAP PS Training Goals- This course will help you become familiar with SAP’s PS (Project
System) module using the Project Builder. You will learn how to:
Create a Project with Work Breakdown Structures (WBS) & Network Activities
Create Project Plans with Easy Cost Planning and Project Planning Board
Create Requisitions and Purchase Orders for WBS
Run Settlements
Run Project Reports
This SAP PS training uses ECC 6.0 (newest SAP release) and includes 420+ training slides,
study guide for each lesson, 60+ pages of additional SAP documentation and email support.
“The training is very clear and easy to understand. The fact that it can be done anytime is a
“great” feature as I could do it at home with no interruptions. Also having the capability to back
up and repeat a process is extremely helpful. With no set time limits, when I was ready to book
an asset, I could review just that section and get pointers right on the spot.”
Pat Z., Whirlpool Corporation
Training Content
Lesson 1 Create Project Structure & Work Breakdown Structures
Project Functionality of SAP-PM (Plant Maintenance)
The SAP Plant Maintenance module (PM) is designed to handle the management and execution of integrated maintenance processes. Such processes include preventative, routine and turnaround maintenance, all fully integrated with purchasing, MRP, controlling and financial accounting performed in SAP. The main objects used in PM are work orders, a series of which (often grouped by revisions)
are what typically is thought of as a "project". Such maintenance projects are planned by describing the estimated work effort per "operation" (activity) and work center performing that work effort. By linking operations inside work orders or across them a generic project schedule is created. Unfortunately SAP-PM has only limited scheduling capabilities. Therefore effective enterprise project
scheduling for maintenance purposes requires either the use of the SAP PS module, the integration with external scheduling tools like Primavera or MS Project, or for less complex projects the use of external tools like GWOS (for more information about these tools please search this web site).
The basic master records used by Plant Maintenance are:
- Maintenance Notifications;
- Maintenance Orders;
- Functional Locations;
- Equipments;
- Materials; and
- Work Centers (Resources).
Functional Locations and Equipments contain fields that allow grouping by units, locations, or plant
locations.
Project Functionality of SAP-CO (Controlling)
There are several important touchpoints between SAP projects and the SAP Controlling module (CO).
All SAP cost planning and budgeting (in SAP terminology: budget = approved cost plan) functions are
handled using standard CO functionality. Objects relevant to project management in SAP are cost objects. This means that planned, committed and actual costs can be charged to them like to a cost center or an internal order in CO. Among these cost objects are WBS elements, networks, activities, activity elements, maintenance orders, operations and suboperations.
Costs may be planned on many levels and in many ways, starting as investment management (IM)
level or WBS structure level cost planning, through primary cost element planning, and going on to purchase requisitions, planned allocations, planned hourly use of resources with associated standard cost rates, and many more.
Actual costs may be charged to SAP project objects in many ways, typically through goods or service
receipts, accounts payable invoices, general ledger (GL) postings, cost allocations or settlements. The SAP system will automatically perform the relevant controlling postings in the background so that CO plan-actual or plan-commitment-actual reports can be run in PS or PM.
Standard costing using standard cost rates associated with work centers (resources) are defined in
SAP CO, either internally calculated or manually assigned. This then means that cost center-based controlling transactions have a direct impact on project costing. The moment you say "costs" in SAP, you say "CO" automatically, even when dealing with projects in PS or PM.
Project Functionality of SAP-PP (Production Planning)
Production planning and project management in SAP have many touchpoints. They intersect
particularly in a make-to-order environment involving sales-driven projects. In principle there are a lot of similarities between the production planning module (PP) of SAP and the Project System (PS) or even Plant Maintenance (PM). Production orders are very similar to networks or maintenance
orders/work orders.
The main difference is that PP deals with ongoing operational aspects while PS and PM deal with
projects. Projects are defined as a series of activities with a start and finish date in order to complete clearly specified deliverables at a high quality standard. From that perspective the main conceptual difference to PP is the limitation in time. PP, PS and PM all define a series of tasks, link them through relationships with each other, assign work centers to them to define where and by whom the tasks are supposed to be completed, and then schedule and cost these tasks out.
Even the tools used in SAP are very similar or often the same (like work centers, definition of
relationships, resource leveling). This should not be surprising as particularly the PS module, and also to some degree PM, has been built by combining PP and controlling (CO) functionality. It does indeed seem that one reason why project management in SAP often is perceived as not user-friendly is due to
that fact. Many of the "logistics" functions of the dynamically changing PS and PM modules are rooted in the much more static PP module. The result is great functional power but often clumsy screens and transactions.
The assignment of internally produced materials (components) to projects in PS or PM reflects another area where these modules intersect. In that case PP provides input to PS or PM, and the timing of this input is synchronized through scheduling and MRP (materials requirements planning) transactions.
There are a number of limitations in the way PP on the one side and PS and PM on the other side
interact. At least in the standard SAP R/3 system costs and dates are not naturally rolling up or synchronizing between these modules.
Project Functionality of SAP-SD (Sales & Distribution)
What does Sales and Distribution (SD) functionality have to do with the management of enterprise
projects? It does for more companies than may seem obvious at a first glance. For contractors using their own SAP system to manage and deliver capital investment projects the SD module is where the billable deliverables of their projects are defined. The same is true for everybody who uses the SAP
project system (PS) to manage the make-to-order production of complex products, whether they are powerplants, aircraft parts, or the concrete bridges.
SAP has functionality that allows to tie reference (template) project structures to product codes so
that at the time of sales order creation the setup of a project structure can automatically be triggered. This does then link SD and PS seamlessly, at least on a high level. As the project progresses,
milestone billing set up in SAP-PS can then trigger payments in SD, which again results in revenue postings in the SAP financial accounting module (FI). There are a number of other reasons where SD
can interact with projects managedf in SAP. Mostly, however, it does so only when you take a comprehensive look at the overall process, trying to ensure full integration. Not doing so may lead to
inconsistencies between what sales people or customer relationship personnel sees in SD and the actual status of the delivery of products. One may just consider a situation where SD data from a suppliers' system needs to be tied into a project master schedule managed by a general contractor. To overcome the latter it is helpful to mirror and match purchase orders and sales orders between supplier and customer, also in line with the way the general project is managed.
Project Functionality of SAP-IM (Investment Management)
The potential significance of SAP's Investment Management module (IM) is too often overlooked
when considering the management of complex enterprise projects. Nevertheless it should in most cases be considered when designing scalable project management solution that center around SAP.
SAP IM is a tool designed to enable program management in SAP. Program management as defined
by SAP in that context means the process of defining a hierarchy on top of many projects with the purpose of planning and controlling costs, including project appropriation management and budget authorizations. Its strongest integration points, besides PS, are with the SAP Controlling (CO) and Asset Management (AM) modules.
While IM was originally developed for the budgeting and high-level management of capital investment
initiatives, its functionality has been extended to allow its use for similar functions. It simply is a tool
that can perform such functions on top of any kind of PS projects.
Preferred Project Management Tool is...
SAP Project System (PS)
Primavera Enterprise/P3e
Microsoft Project
SAP with Primavera
Difference between SAP PS and PM?
The SAP world makes an important distinction between "PS" and "PM". The acronym "PM" is a source of frequent confusion. For many project management professionals it simply stands for "Project Management", while in the SAP community it is the abbreviation for the "Plant Maintenance" module of SAP.
The SAP PM module was not designed as a project management module. It still contains a lot of components very similar to the SAP PS module, which is the project management module called "Project System". SAP define their modules by function more so than by the process they cover.
The Process Building Blocks for Projects with SAP
Forget about technology and do not pay attention to modules: The key process blocks of Enterprise
Projects deal with functional aspects! To set up an effective project management system, these
functional aspects need to be clearly defined. If multiple tools are used, responsibilities per functional
aspect and project management layer need to be assigned to one tool only, for each layer of the enterprise project (enterprise, project, and contractor).
I want to validate the customer number in one of the user fields in WBS. The formula builder in the validation screen, it seems, does not support table fields other than fields from PRPS. Can this be done thru some user exits ?? If yes how ?? Can you guide me in this ??
Answer :
To use a user exit in validations, you have to perform following steps;
- copy SAP standard program GGBS002 to ZGGBS002 - create a user exit in this program (such as U902, U903 etc) - the user exit you defined in the above mentioned program will be visible in validations on screen tab 'Exits' - configure your validation with 'User exit' as option
How To Create a Multilevel BOM and How Does It Work
{mosbanner:id=23}
Multi level bom is a Bom which it has different components at different level..for example:
- A ( finished material)
- B ( semi finished)
- C ( Raw material)
When you run the MRP, Bom will explode upto last level and it will plan the requirement of each individual material.
What ever may be the kind of BOM to be created transaction codes are as below:
- CS01 : BOM create
- CS02: BOM Change
- CS03: BOM display
Pre requisites are material master record for the materials.
What you have to keep in mind is:
1. BOM creation is through CS01 only.
2. When you have to create multilevel BOM, you have to carry craetion of BOM level by level.
3. First create BOM for assemblies (means materials which are produced inhouse, means materials with procurement
type "E" in the material master MRP 2 view).
4. Finally create BOM for the finished product using these assemblies as components.
5. When you see the BOM of finished part after creation through CS03, you can find these assemblies with a tick
mark in the field "Assembly". When you double click you can see the susequent BOM of these assemblies.
6. Example would be for a vehicle suppose engine, front wheel, back wheel are the "E"parts. Create BOM first for
these engine, front wheel and backwheel with respective material components.
Then create BOM for vehicle with these three "E".
When you see the BOM of vehicle after creation, you can see a tick mark against these E parts which shows that
they have BOM furtehr down and you can double click and see the components of these
Validation in PS
am trying to use validation in the Project. Can any one tell when are the call up points 110 and 120 trigerred ?
I want to validate one of the user defined fields in WBS.
Everything is working fine when I simulate the validation. But when I enter a value in the user defined field and save the project then I do not get the error message as expected.
Does anybody have an idea what could be wrong ??
Answer :
Please see if you have checked the check box for Automatic validation in the relevant project profile.
WBS Elements
1. What is WBS element? 2. What is the Tcode to get to that screen? 3. What is the need and pupose of WBS element?
The project definition is the binding framework for all organizational elements within a project.
Work Break down Structure:
With a work breakdown structure you can divide the project into useful steps, specify fixed or
"basic" dates, specify the work involved, and determine project costs. The individual levels of
the hierarchy in a work breakdown structure enable you to organize a project into steps.
Work Break down Structure Element (Sub WBS):
You can further break down these steps into individual elements. Maximum steps supported
are 99.
Network:
It is a special type work order on which cost can be planned, controlled and monitored.
Activities:
These are the actual tasks that are to be executed for the completion of the project
The SAP PS consultant is responsible for the analysis, design, configuration & support of the SAP PS area to meet
the business needs of company. Knowledge and min. End-to-End Implementations and at least two Support
Projects ,· 2 years Project Management or work scheduling experience. Working closely with our customers to
deliver, maintain and troubleshoot and enhance SAP functionality and through knowledge of the FI module and
knowledge of its integration with other modules.
SAP R/3 is based on a three tier client/server technology. Typically, it is made up of three functionally distinct layers namely: the user interface, business logic and database. The user interface, which is otherwise known as the presentation server displays the interface for users' communication with the SAP system. It is often referred to as the SAP GUI. As a matter of fact, it is a program called sapgui.exe. The application server is where the business logic and data manipulation takes place. Data processing, SAP administration tasks and client request/feedback management are handled within the business layer. The database layer is synonymous to the database server and it typically acts as a data repository for tables and other database objects and structures
Ideally, an R/3 system is composed of one database server, one or more application servers and one or more presentation servers. SAP Business One on the other hand is composed of a database server and one or more presentation servers.
the difference between SAP Business One and SAP R/3. The non technical answer to this question is that; SAP Business One is SAP's offering for small and mid size companies, while R/3 is SAP's offering for large companies.
Procedure: What to Do in Case of Power Failure in SAP Project.
The procedure to be followed in case of a power failure in the power sources of either the
productive or backup server.
1. Check the UPS Make sure the UPS is functioning properly, and check the remaining
time. You should have approximately XX minutes to shut down the system.
2. Log onto SAP and check for users and processes If any users are still on SAP, send a
system message for them to log off immediately. Check for background processes,
interrupted user processes, and other processes that may need attention before shutting
down, and record them in the Power Failure Log.
3. Stop SAP and Shut Down the Database Refer to Starting/Stopping the Database and SAP
for detailed instructions on shutting down SAP and the database.
4. Shut down the Server Refer to Powering On/Off the Server and the UPS for detailed
instructions on powering off the server
5. Power Off the UPS Refer to Powering On/Off the Server and the UPS for detailed
instructions on powering off the server
cProjects ( Capital Projects ) :
cProjects (Collaboration Projects) is the SAP web-based application built on the Web
Application Server (WAS). cProjects is a component of the cProjects Suite. cFolders is another
component of cProject Suite.
cProjects was designed for organizations that need to manage multi-phase projects with high
quality control can benefit from cProjects. cProjects supports flexible project management and
team collaboration.
cProjects provides project structuring capabilities (project definition, phases, checklists and
tasks), roles-based resource management, flexible authorization control and scheduling
functionalities, in conjunction with broad project management and monitoring features.
cProjects requires WAS 6.2 and cProjects Suite prior to deploying cProjects.
Being a beginner in SAP PS is a challenge. As a techie, When I started my ABAP Program in PS Module, I found a lot of scattered information but there is no article or blog with consolidated information even on basic terminologies of SAP PS. This blog is my attempt to provide an insight of basic techno-functional aspects and terminologies of SAP PS to a novice.
In my first blog you will find the important terms of the PS module. I have tried to explain them with the help of an example. Following this is the next blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/9659 where the technicalities of the same are covered.
The Project System (PS) module of SAP is specifically designed to provide comprehensive and fully integrated project management functionality for SAP customers. A Project is a complex undertaking, bringing with it huge data of different type.
At the beginning of each project, whether it involves developing a new product, make-to-order engineering or internal organization, you need to define and set up the structures necessary to manage your project and incorporate them into your existing organizations and processes. 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 a basis for successful project planning, monitoring and control.
You create and manage your project structure in SAP R/3 Project System, by means of work breakdown structures and
networks.The WBS describes individual phases and functions of a project. Network contains the individual project tasks and
the dependencies between them in the form of activities and relationships
Some important terms:
Project Definition Project Definition is general description of the project that you want to manage. It is a framework laid down for all the
objects created within a project. It contains organizational data that is binding for the entire project.
Work Breakdown Structure (WBS)
WBS is a hierarchical model of the tasks to be performed in the project. It provides overview of the project and forms
basis for the project organization and coordination.It shows work, time and money spent on the project. You can use it to
plan dates & costs and allocate budget. The Work Breakdown Structure can be displayed according to:
Phase
Function
Object
Individual tasks required to carry out the project is called WBS elements.
Network The network describes project processing. Thus the Network contains instructions on how to carry out activities in a specific
way, in a specific order and in a specific time period.Main elements of network are activities and relationships. It forms the
basis for planning, analyzing and monitoring time schedules, costs, & resources.
Activities Activities are used to plan project staffing, capacity, material, PRTs, and service requirements. When activities are assigned
to WBS elements, detailed view of costs, dates, and capacities at WBS element could be obtained. It’s a task in a network
which has a defined start and finish. An activity can be broken down into activity elements.Three categories of activities in
the Project System:·
Internal Activities
External Activities
General Cost Activities
Activity element Activity element is an activity which is subordinate to another activity. Activity elements contain the same information as
activities.Three categories of activity elements in the Project System:
Work elements
External Elements
General Cost Elements
Activity Type It’s a physical measure of activity output of a cost center .e.g. hours, number of units produced, machine times, production
times.
Milestones Milestones are the events in the project to which particular importance is attached Or which trigger predefined functions. In
general they indicate transition between different departments or phases. Milestones are assigned to activities and WBS
elements:In PS milestones are used to:
Trigger predefined functions in network activities.
Carry out earned value analysis.
Determine dates in billing plan for sales orders.
Relationships You use relationships to depict chronological and technical dependencies between activities. The relationship determines the
nature of the link between the individual activities. :
FS Relationship : An activity does not start until the preceding activity is completed.
SS Relationship : An activity can not start unless another activity has started.
FF Relationship : An activity can not be completed until another activity has been completed.
SF Relationship : An activity can not be completed until another succeeding activity has stared.
Confirmations It is a part of network control. It documents the state of processing for the network activities and activity elements. There
are two types of confirmations Partial & Final.Confirmations are used to record:
The work center where the activity was carried out.
The person who carried out this activity.
The yield and scrap produced in an activity.
The actual values for the duration and dates.
Settlement As a rule, projects are used to collect and monitor costs, but are not usually the final cost object. For this reason the costs
in atypical project will be settled at the end of the period.To this end, you store settlement rules in the activity / WBS
element requiring settlement. They contain information on settlement receivers, cost apportionment and control data.
Settlement receivers could be cost centers, G/L accounts. Etc.
Budget The budget is the approved cost structure for an action or project in a particular period.Budgeting differs from cost plan in
that it is binding. In the approval phase you prescribe your project funds in the form of budget. It is possible to allocate
overall and annual budget in parallel.
Work Centers Work center represents the resources responsible for executing an activity. In a work center, you can enter the available
capacity and an operating time. You can arrange the work centers in a hierarchy for capacity evaluation purposes. Internal
activities are assigned to work centers (resources) to be completed.A work center is a physical unit within a company where
an activity is performed.
Profit Center It is subdivision of business organization which is set up for internal management control purposes. Profit centers divide
business up on a management basis. The basic aim of profit center accounting is to present areas of the business as entities
operating independently in the market.
Lots of jargons ….let me site an instance of the construction project of a building..
Let say there is a construction company that is going to construct a Multi-Storey building.
The first thing that needs to be created in the system is Project Definition. The entire activity plan for this project
will come under this project definition. Overall budget needs to be estimated, assigned and get approved for the
project. Project timeline needs to be decided. Project could be then subdivided into separate parts which are actually
WBS elements lets say in this e.g. we have 4 main WBS elements:
1. Land Acquisition
2. Procurement
3. Construction
4. General
To every above WBS, budget and time line need to estimated.
Now to take an example we will drill down two WBS elements namely Land Acquisition and Construction.
- Land Acquisition could be sub divided into activities as in
Generation of request document for the land.
Soil testing
Approval for construction
Preparation of purchase order of the land
Above 4 activities should be done in sequence. As in second activity will start only after request document for the land is completed and so on. Hence these activities have FS Relationship between them.
- Now take WBS element Construction.
It could be sub divided in to floor wise tasks. Let say, we have four story building and each floor has 4 flats. So under WBS
element ‘Construction’ we may create separate sub WBS element for each floor. Each sub WBS element
of floor may be divided further into last level of WBS elements one for each flat on the floor. This way we
will have hierarchy of the WBS elements.Finally last level of WBS elements i.e. WBS elements of the flats
will have activities like
1. Plumbing
2. Electrical work
3. Flooring
4. Painting
5. Furniture
These activities form the Network.
Let say Plumbing and Electricity work are the external activities as they are given to a outside contractor. While
the other activities are done by company labor so they are internal activities. Plumbing and Electrical work could
be started simultaneously.While flooring needs be done once the plumbing and Electrical work is complete. Hence they have
FS relationship and so on…. Now if we talk about milestones:
1. First milestone could be purchasing the land
2. Second could construct the base of the building.
3. Third could be construct the floors
4. Fourth could be completion of plumbing and electrical work for all the flats. And so on….
As I have said that Work center represents the resources responsible for executing an activity For the above activities, work centers could be the company labor required for the construction, labor provided by the external service center for plumbing and Electricity work. while Profit Centers could be the finally constructed flats.
Sr NO
Project
Elements
Examples
1 Project Def Constructing the Buiding
2 WBS Generation of request document for the
land
Soil testing
Approval for construction
Preparation of purchase order of the
land
3 Activities (Under
3rd WBS)
Plumbing( external Activities)
Electricity work( external Activities)
Flooring (internal activities)
Painting (internal activities)
Furniture
4 Relationship Flooring needs be done after the plumbing and
Electricity work. Hence they have FS
relationship
5 Milestones First milestone could be purchasing the
land
Second could construct the base of the
building.T
hird could be construct the floors
Fourth could be completion of plumbing
and electricity work for all the flats
6 Network Plumbing and Electricity installation are to be
one contractor each. Therefore, there exist a
network within on the activities of it under
different WBSs.
Referencee : The book : Functions in Detail : R/3 System - Project Management in Engineering
& Construction )
hi sheetal i am working on a report in PS and need to pull the last posting date with amount spend on the
project.... where can i those.
This is a very useful blog for all the techis...Very simple language and a lot of useful content...
Keep it up.
Both the parts are very much descriptive and can be used as reference for techies.
Starting point for beginners.
PS module generally remains behind in implementations for various reasons.
This would motivate ps-related persons in
understanding basics & methodology of how
SAP makes it easier in doing so.
keep up
PS module generally remains behind in implementations for various reasons.
This would motivate ps-related persons in
understanding basics & methodology of how
SAP makes it easier in doing so.
A good one . Will really help beginners to understand the concepts of SAP PS.
GRM4 Requirements Grouping: Assign WBS Elements Individually
GRM3 Requirements Grouping: Assign WBS Elements Using List
GRM1 Requirements Grouping: Display Assigned WBS Elements
GRM5 Requirements Grouping: Assign Planning Groups
GRM2 Requirements Grouping: Display Assigned Planning Groups
GRM7 Requirements Grouping: Display Assigned Planning WBS Elements
Claim Management
Technical name: SAP_PS_CLAIM
Tasks
You can use the transactions for this role to create and edit notifications of type "Claim" and to obtain an overview of existing claims.
Activities in the Project System
Transaction Function
CLM1 Create Claim
CLM2 Change Claim
CLM3 Display Claim
CLM10 Claim Overview
CLM11 Claim Hierarchy
Collaboration
Technical name: SAP_PS_CEP
Tasks
You can use the transactions for this role to depict business process between your business and external business partners (producers, sub-suppliers) based on the Internet.
The aim is efficient information and knowledge transfer between a person responsible for a project in your business and external partners, within the framework of a joint project. With the help of Collaborative Engineering and Project Management you can make project structures, product structures, and documents from the R/3 System that are relevant to the joint project available over the Internet to selected participants. The change objects or comments are sent back to you for you to check and return to the R/3 System.
Activities in the Project System
Transaction Function
CMWO CEP: Configuration Management
CEP_R3_MON CEP: Monitoring
CEO1 CEP: Display Folder
CEO2 CEP: Transfer Folder
CEO3 CEP: Check Folder
Executing Controlling Reports
Technical name: SAP_PS_EXECUTE_CO_REPORTS
Task
You can use the transactions for this role to execute hierarchy reports and cost element reports.
Activities in the Project System
Transaction Function
CJE0 Execute Report: Hierarchy Report
CJEB Execute Report: Hierarchy Report in Background
GR55 Execute Report: Cost Element Report
Displaying Documents
Tasks
You can use the transactions for this role to display texts and documents for a project and its objects.
Activities in the Project System
Transaction Function
CN05 Display Project Texts
CV03N Document Management: Display Documents
Integration
See also:
Maintaining and Displaying Documents
Maintaining and Displaying Documents
Technical name: <SAP_PS_DOCUMENTS>
Tasks
You can use the transactions for this role to maintain and display texts and documents for a project and its objects, and to conduct targeted document searches using a search engine.
You can use the transactions for this role to manually plan costs and revenues in the work breakdown structure. You can have the system calculate plan values in the network, or you can copy existing planning and use that as a template for fresh planning.
Activities in the Project System
Transaction Function
CJ40 Change Overall Costs in the WBS
CJ41 Display Overall Costs in the WBS
CJ42 Change Revenues in the WBS
CJ43 Display Revenues in the WBS
CJ9K Network Costing
CJ9FS Copy Planning
Progress Information System
Technical name: SAP_PS_REP_PROGRESS
Tasks
You can use the transactions for this role to display progress analysis reports.
You can use the transactions for this role to create and edit report forms in the Report Painter, and execute inheritance runs, to draw data from the system for, among other things, the Executive Information System (EIS).
Activities in the Project System
Transaction Function
CJE4 Hierarchy Reports: Create Form
CJE5 Hierarchy Reports: Change Form
CJE6 Hierarchy Reports: Display Form
CJE1 Hierarchy Reports: Create
CJE2 Hierarchy Reports: Change
CJE3 Hierarchy Reports: Display
CJE0 Hierarchy Reports: Execute
GRR1 Cost Element Reports: Create Report Painter Report
GRR2 Cost Element Reports: Change Report Painter Report
GRR3 Cost Element Reports: Display Report Painter Report
GRR4 Cost Element Reports: Delete Report Painter Report
CJH1 Summarization: Inheritance
CJH2 Summarization: Inheritance Evaluation
KKRC Summarization: Summarization
KKR0 Summarization: Hierarchy
CJSA Data Transfer to EIS
Actual Payments in Projects
Technical name: SAP_PS_PAYMENTS_PLAN
Tasks
You can use the transactions for this role to transfer actual payments and display the transfers.
Activities in the Project System
Transaction Function
FMWA Create Funds Transfer
FMWC Display Funds Transfer
Project Year-End Closing
Technical name: SAP_PS_PROJ_YEAREND
Tasks
You can use the transactions for this role as part of the fiscal year-end closing to carry forward commitment values that are still open into the first period of the next fiscal year, and to carry forward unused project budgets to that fiscal year.
Activities in the Project System
Transaction Function
CJCF Carry Forward Commitment
CJCO Carry Forward Budget
Cost Reports
Technical name: SAP_PS_REP_COSTS
Tasks
You can use the transactions for this role to display all cost reports.
You can use the transactions for this role to execute mass changes for projects and evaluate them in the log.
Activities in the Project System
Transaction Function
CNMASS Execute Mass Changes
CNMASSPROT Mass Changes: Log
Materials in Projects
Technical name: SAP_PS_MATERIAL
Tasks
You can use the transactions for this role to plan and monitor project material requirements and costs, and to regulate and schedule the flow of materials.
Activities in the Project System
Transaction Function
MM01 Create Material
MM02 Change Material
MM03 Display Material
CN33 BOM Transfer
MD51 Project Material Requirements Planning
MD50 Sales Order Material Requirements Planning
MD4C Order Report
CO46 Order Progress Report
CO24 Backlog Processing: Missing Parts Information System
CO06 Backlog Processing: Materials
V_RA Backlog Processing: Sales Orders
MDUP Sales Order/Material Assignment: Edit
MDUS Sales Order/Material Assignment: Display
CNL1 Create Delivery Information
CNL2 Change Delivery Information
CNL3 Display Delivery Information
CNSO Delivery from Project
Displaying Materials in Projects
Technical name: SAP_PS_MATERIAL_DISPL
Tasks
You can use the transactions for this role to display project material requirements and costs.
Activities in the Project System
Transaction Function
MM03 Display Material Master Data
MD4C Order Report
CO46 Order Progress Report
S_ALR_87015076 Material Components
Project Funds Commitments
Technical name: SAP_PS_FUNDS_COMMITMENT
Tasks
You can use the transactions for this role to enter expected costs or revenues, even at an early stage when you do not know which transaction (purchase order, material reservation, and so on) will actually cause them. This enables you to reserve portions of the budget early.
Activities in the Project System
Transaction Function
FMZ1 Create Funds Commitment
FMZ2 Change Funds Commitment
FMZ3 Display Funds Commitment
FMZ6 Reduce Funds Commitment
Project Period-End Closing: Individual Processing
Technical name: SAP_PS_PEREND_PROJ_IND
Tasks
You can use the transactions for this role as part of period-end closing to carry out period-related commercial transactions for each project individually. You thus ensure that, on the one hand, all the data belonging to a project can be determined and, on the other, that the data is available to your company's management.
Activities in the Project System
Transaction Function
CJB2 Settlement Rule: Individual Processing
PSW5 Periodic Repostings
CPTK Template Allocation: Individual Processing
CJN1 Revaluation at Actual Prices: Individual Processing
CJ08 Overhead: Individual Commitment Processing
CJ44 Actual Overhead Calculation: Individual Processing
CJZ2 Interest Calculation: Individual Processing
CJ9L Cost Forecast: Individual Processing
CJA2 Incoming Orders: Individual Processing
CJ88 Settlement: Individual Processing
CJIC Settlement: Investment Project Line Items
KKA0P Change Cutoff Period for Planned Results Analysis
You can use the transactions for this role as part of period-end closing to carry out period-related commercial transactions for several projects simultaneously. You thus ensure that, on the one hand, all the data belonging to a project can be determined and, on the other, that the data is available to your company's management.
Activities in the Project System
Transaction Function
CJB1 Settlement Rule: Collective Processing
PSW5 Periodic Reposting
CPTL Template Allocation: Collective Processing
CJN2 Revaluation at Actual Prices: Collective Processing
You can use these transactions to determine all the plan data to be taken into account for a period, and to compile project plan data for enterprise controlling purposes.
You can use the transaction for this role to evaluate human resources.
Activities in the Project System
Transaction Function
CMP9 Workforce Planning - Reporting
Planning Human Resources
Technical name: SAP_PS_PERS_RES_PLAN
Tasks
You can use the transactions for this role to display reports on human resources, in a project view and a work center view.
Activities in the Project System
Transaction Function
CMP2 Workforce Planning: Selection Project View
CMP3 Workforce Planning: Work Center View
Planned Payments
Technical name: SAP_PS_PAYMENTS_PLAN
Tasks
You can use the transactions for this role to plan revenues and expenditures in one or more WBS elements, and to display the planned payments.
Activities in the Project System
Transaction Function
CJ48 Payments in the WBS: Change
CJ49 Payments in WBS: Display
Project Budgeting
Technical name: SAP_PS_BUDGET_PROJ
Tasks
You can use the transactions for this role to execute budgeting and availability control for your project.
Activities in the Project System
Transaction Function
CJ30 Create Original Budget
CJ31 Display Original Budget
CJ37 Budget Supplement: Within Project
CJ36 Budget Supplement: To Project
CJ38 Budget Return: Within Project
CJ35 Budget Return: From Project
CJ32 Change Budget Release
CJ33 Display Budget Release
CJ3a Change Budget Document
CJ3b Display Budget Document
CJBV Budget: Activate Availability Control
CJBW Budget: Deactivate Availability Control
OPSX Budget: Reset "Budgeted" Status
CJ34 Budget Transfer
Maintaining and Displaying Project Structures
Technical name: SAP_PS_STRUCT
Tasks
You use the transactions for this role to maintain the structures for your project. A clear project structure is the foundation of successful project planning, monitoring, and control.
Activities in the Project System
Transaction Function
CJ20N Project Builder
CJ27 Project Planning Board: Create Project
CJ2B Project Planning Board: Change Project
CJ2C Project Planning Board: Display Project
CJ2D Structure Planning: Create Project
CJ20 Structure Planning: Change Project
CJ2A Structure Planning: Display Project
CJV1 Create Simulation
CJV2 Change Simulation
CJV3 Display Simulation
CJV5 Delete Simulation
CJV7 Simulation: Logs
CN60 Change Documents: On Project/Network
CJ01 Work Breakdown Structure: Create
CJ02 Work Breakdown Structure: Change
CJ03 Work Breakdown Structure: Display
CN21 Network: Create
CN22 Network: Change
CN23 Network: Display
Display Project Structures
Technical name: SAP_PS_STRUCT_DISPL
Tasks
You can use the transactions for this role to display the structures of your project. A clear project structure is the foundation of successful project planning, monitoring, and control.
Activities in the Project System
Transaction Function
CJ20N Project Builder
CJ2C Project Planning Board: Display Project
CJ2A Structure Planning: Display Project
CJV3 Display Simulation
CJ03 Display Work Breakdown Structure
CN23 Display Network
CJ13 Display WBS Element
KJH3 Display WBS Element Group
PS Input: Line Manager Generic Role
Technical name: SAP_PS_LINE_MANAGER
Tasks
<required>
Activities in the Project System
Transaction Function
CNR3 Work Center: Display Master Record
CR13 Work Center: Display Capacity
CMP3 Workforce Planning: Work Center View
CMP9 Workforce Planning - Reporting
CM01 Capacity Evaluation, Work Center View
Confirmations
Technical name: SAP_PS_CONFIRM
Tasks
Here, you can enter and process confirmations for activities and activity elements.
You can use the transactions for this role to display all the dates in the work breakdown structure.
Activities in the Project System
Transaction Function
CJ26 Display WBS Dates
CJ22 Display Basic Dates
CJ24 Display Forecast Dates
CJ2C Project Planning Board: Display Project
Monitoring Dates for Materials
Technical name: SAP_PS_MONITOR_MAT_DATES
Tasks
You can use the transaction for this role to monitor dates for materials.
Activities in the Project System
Transaction Function
NWTM Monitoring Dates
Actual Transfer Prices
Technical name: SAP_PS_TRANSFER_PRICE_ACTUAL
Tasks
You can use the transactions for this role to allocate a transfer price from a transfer price agreement, so that actual revenues are posted in the sender and actual costs in the receiver. You can also display the transfer price allocation and cancel it.
Activities in the Project System
Transaction Function
CJG4 Transfer Price Allocation: Enter Using List
CJG3 Transfer Price Allocation: Display
CJG5 Transfer Price Allocation: Cancel
Integration
See also:
Planned Transfer Prices
Planned Transfer Prices
Technical name: SAP_PS_TRANSFER_PRICE_PLAN
Tasks
You can use the transactions for this role to agree a transfer price for the rendering of a particular service between two WBS elements, display, and change the agreement.
You can use the transactions for this role to combine a number of projects with like characteristics, thereby effecting more efficient project control. This enables you to carry out analyses that allow for clearer costs at higher level, such as project manager level.
You can use the transaction in this role to calculate the sales price for a customer inquiry re a product or service, and save the result in a document. You can carry out as many sales pricings as you want, and compare them.
If required, you can also create a detailed quotation for a project-assigned customer inquiry, based on project planning in the SD application component. You can use a billing plan to record the sales price calculated as planned revenue in the project.
You can use the transactions for this role to carry out template-allocation to allocate overhead costs. Costs are not simply allocated, but the quantities used by the relevant receiver object are determined. The costs are calculated by the valuing quanti ti es at a rate.
Activities in the Project System
Transaction Function
S_ALR_87004530 Create Selection Variants for Collective Processing
S_ALR_87005496 Stipulate Reposting Cycles
S_ALR_87007996 Maintain Templates
OKG1 Stipulate Capitalization Percentage Rates
S_ALR_87005128 Copying Costs and Revenues: Create Plan Version
S_ALR_87004530 Allocation: Create Selection Variants for Collective Processing
A dynamic allocation tool that uses functions and formulas to calculate numerical values and the values of Boolean expressions (true or false).
This tool is used for various purposes such as sender-receiver allocations and as an aid for formula planning. Instead of preassigned allocation data, the template uses a generic description for any data (such as the sender object, quantities, and costs). Since this data is not known at the time the template allocation is performed, it is determined dynamically when the values are calculated.
The system uses the transactions in this role to represent the value flow of project-related payment data in a single project, in partial projects, or across projects according to hierarchical points of view.
Activities in the Project System
Transaction Function
S_ALR_87100191 Payments: Receipts/Expenditures for a Fiscal Year
KSB5 Document Display: Actual Costs/Revenues
CJ3B Document Display: Budget
CJIG Document Display: Payments
S_ALR_87013573 Payments: Receipts/Expenditures for all Projects
S_ALR_87013575 Payments: Receipts
S_ALR_87013574 Payments: Expenditures
Payment Transfer for Project Period-End Closing
Technical name: SAP_PS_PEREND_PROJ_PAYMENT
Tasks
The system uses the transaction for this role to record partial payments and payments that reference invoices in Project Cash Management. You use the payment transfer facility to display cleared invoices under the value type "Payment" in Project Cash Management and to record partial payments and remaining items that reference projects in Project Cash Management.
The system uses the transactions in this role to represent the value flow of project-related payment data in a single project, in partial projects, or across projects according to hierarchical points of view.
Activities in the Project System
Transaction Function
S_ALR_87100191 Payments: Receipts/Expenditures for a Fiscal Year
KSB5 Document Display: Actual Costs/Revenues
CJ3B Document Display: Budget
CJIG Document Display: Payments
S_ALR_87013573 Payments: Receipts/Expenditures for all Projects
S_ALR_87013575 Payments: Receipts
S_ALR_87013574 Payments: Expenditures
Summarized Cost Reports
Einzelpostenberichte
Technical name: SAP_PS_REP_COST_SUMMARIZ
Tasks
You can use the transactions for this role to combine a number of projects with like characteristics, thereby effecting more efficient project control. This enables you to carry out analyses that allow for clearer costs at higher level, such as project manager level.
SpecifyStatus Profile&Assign to Program type GenerateInvestment Program from Profit center&Cost centerhierarchy MaintainingPlanning&Budget Profile&assigning it to Program type
Maintainingappropriation request types
SpecifyingSpecial symbols for appropriation request number
Maintainingcoding masks for appropriation request number
ConfiguringInternal orders as Investment measures DefiningTolerance limits for availability control Configuringprojects as Investment measures
ProjectSystem Configuration
DefineProject Profile
Define Investment Profile
MaintainBudget Profile
DefiningSpecial Characters for Projects and Project coding mask Creating Project type for WBSelements Creating user defined fields for WBSelements Maintainingsubstitution rule Maintainingnetwork types and its parameters Maintainingnetwork profiles
DefiningMilestone usage DefiningTime profiles for Project planning board Definingprofiles for the project planning board DefiningValue categories
Maintainingbudget profile Creatingsettlement profile&specifying default profile in projectdefinition Definingstrategies for determining settlement rules Assigningstrategies and default rules to network types Specifydefault settlement profiles for networks Definingparameters for Availability check Definingconfirmation parameters
Investment Management configuration
Define Program Types
Define User Fields
Specify Status Profile & Assign to Program type
Generate Investment Program from Profit center & Cost center hierarchy
Maintaining Planning & Budget Profile & assigning it to Program type
Maintaining appropriation request types
Specifying Special symbols for appropriation request number
Maintaining coding masks for appropriation request number
Configuring Internal orders as Investment measures
Defining Tolerance limits for availability control
Configuring projects as Investment measures
Project System Configuration
Define Project Profile
Define Investment Profile
Maintain Budget Profile
Defining Special Characters for Projects and Project coding mask
Creating Project type for WBS elements
Creating user defined fields for WBS elements
Maintaining substitution rule
Maintaining network types and its parameters
Maintaining network profiles
Defining Milestone usage
Defining Time profiles for Project planning board
Defining profiles for the project planning board
Defining Value categories
Maintaining budget profile
Creating settlement profile & specifying default profile in
Project definition
Defining strategies for determining settlement rules
Assigning strategies and default rules to network types
Specify default settlement profiles for networks
Defining parameters for Availability check
Defining confirmation parameters
Project Systems (PS)
End-to-end Project Management-environments developed from SAP WBS-elements
and networks. Specialty solutions include – user status settings, project
version control, CATS (Cross Application Time Sheet), resource related
quote and billing tie in with SD. Provided: BPR, configuration as well as
requirements definition for specialty ABAP/4 reports and outputs.
SAP Project System (PS) - SD integrations:
The PS SD Integration is mainly for the customer projects.
System will generate projects/network during creation of sales order.
Your sales order value will go to PS as planned revenue.
When you do billing in sales order you will get actual revenue in the
project.
When the milestone is achieved or confirmation of the network activity,
billing block will be removed in your sales order for billing.
Also the DIP profile is another area to check out in PS-SD. The idea is to
use this in Resource Related Billing scenarios. It’s a very interesting
feature that has been introduced in 4.6C onwards. This enables you to
select at various levels (like Cost element etc) how the billing needs to
be done.
Use the following path for DIP profile configuration.
SPRO-Project Systems-Revenues and Earnings-Integration with SD Documents-
Create Quotations and Project Billing-Maintain Profiles for Quotations &
Billing.
The order should be project order. (PS1). In the material master strategy
group should be 85 (tab MRP 3) also put item category group as 0005 (tab
Sales Org.2)
First to create standard wbs and network as per project requirement.
Please also attach mile stones for billing plan. attach the material to
the network with the tcode cn08.
to create the sales order with the material then project will be created
in the back ground, the sales order number and project number will be the
same.
The revenue planning will be done automatically, only we need to plan the
cost. Any changes in the sales order will effect the project and vise
versa.
Additional:
1. During inquiry you can enter your WBS element, and do your project
planning cost and after that become your estimate price send to customer
thru quotation.
2. If you use variant configuration, you determine activity and component
for your project from sales order variant.
3. You can run availability check based on project planning to check you
can deliver on time.
If there is down payment request on your project please post the down
payment request by tcode F-29. Once the full payment is received please
clear the down payment by tcode F-39.
To find PS1 document type in transaction VOV8?
If you have IDES, pls. copy the settings of PS1 (which is available in
IDES) into development as ZPS1.
The details of CO settings for PS - SD integration
The CO Setting is: -
Maintain Assignment of SD-Conditions to CO-PA Value Fields
Controlling > Profitability Analysis > Flows of Actual Values > Transfer
of Billing Documents > Assign Value Fields (KE4I)
Assign Sales Orders to Project Account
This section describes which standard settings and values must exist in
Customizing for you to be able to assign a sales document (customer
quotation or sales order) to a WBS element manually.
The settings you need to line projects and sales documents manually are
prescribed by SAP. If you use these standard settings, you do not need to
make any additional settings in Customizing.
Strategy Groups
SAP has predefined strategy group 21 (with strategy 21) for the link
between sales documents and projects.
Notes:
If you do not maintain the strategy group for the material in the sales
and distribution document item, you cannot assign that item to a WBS
element.
Alternatively, you can assign the strategy group to a material using MRP
group 0021 (also predefined).
Requirements Classes
SAP has predefined requirements class 80 with account assignment category
D (assignment to WBS element) for the link between projects and sales and
distribution documents. Requirements class 80 is assigned to strategy 21
using requirements type KP (also predefined).
Recommendation
do not change the standard settings supplied by SAP.
You need to set the SD/PS Assignment indicator on the control tab page of
the standard project definition, for PS-SD integration, assembly
processing.
During inquiry you can enter your WBS element, and do your project
planning cost and after that become your estimate price send to customer
thru quotation.
To ensure a one-to-one match between the project and its related sales
document, the number of the standard WBS element should always be longer
than ten characters.
Some more steps related to IDES data...
1).Requirement class 80 and requirement type KP.(Tcode OVZH)
2). Maintain the above in strategy 85 in planning strategy in SPRO.
3). Maintain requirement type and class for item category in VV07.
3) Create standard templates thru CJ91 and CN01.
4).Create materials thru MM01 and select material type as KMAT and
strategy group 85 as defined above and maintain item category as u have
maintained in spro.
5).Assign materials to network and WbS thru CN08.
With currency with PS and SD? We have ATO process and have some issue with USD and CAD currency with PS
andSD
we are using a group currency in the controlling area (type 30 set as
USD). In addition we have object currency turned on for the Controlling
Area so we have company currency in parallel for each company assigned to
the controlling area. Within CO everything is working fine, the issue
appears to be when the CO-PS planned amount is passed to the sales order
EK01 condition. In this case, CO-PS has both object currency and
controlling area currency but it uses the controlling area currency as the