Beruflich Dokumente
Kultur Dokumente
Applies to:
SAP Project Systems irrespective of version
Summary
This Document guides through the basic integration scenario of the Project Systems with Sales &
Distribution Module. Integration of Project Systems to Sales Scenario is generally followed business practice
in any industry which involves customized delivery of final product to the customer
Author: Amarendra M
Company: Intelligroup Inc.,
Created on: 29 December 2008
Author Bio
M Amarendra has a Bachelors degree in Engineering and has been working in the different modules of SAP
from last 7 years. He is working as a Senior Business Consultant with Intelligroup Inc. He has expertise in
SAP PS, SAP SD, SAP CO, Variant configuration.
Table of Contents
Project Systems – Customer Oriented Project Implementation Situation ..........................................................3
Integration of Projects Systems (PS) and Sales and Distribution (SD) ..........................................................3
While Creating Project Structure.....................................................................................................................3
Project Customization Prerequisites – OPSB, OPSA.....................................................................................4
Customization Settings from Sales and Distribution (SD) Perspective (OVZG):............................................6
Requirement Type Determination: ...............................................................................................................................6
SD Order Creation ..........................................................................................................................................8
PS Transactions (CJ43) ................................................................................................................................10
Costs Structure Creation in Projects (CJ20N) ..................................................................................................11
CN41 – PS Information Report.........................................................................................................................13
Disclaimer and Liability Notice..........................................................................................................................14
The planning profile should have the tick maintained in the check box “ from the sales order” if the values
need to come from sales order as shown by below screen shot.
The above configuration step of requirement class is the most important in terms of integrating
Project system with SD and MM modules.
In this, Account assignment category setting - Q or D decides if the Sales Order can be linked to
Project System.
Q is for Value & Stock management at Project level while D does the same at Sales order level
SD Order Creation
When an item is added in the Sales Order is being created, System automatically checks for the requirement
type in the background and issues the message as the below screen shows :-
The ‘requirement type” can be checked in the columns you get when “Procurement “ tab is selected at the
sales order header.
Such Sales order only gets saved when “WBS element” value is inputted in the Account Assignment tab.
Then the billing plan should be maintained for each billable item in the sales order.
When the billing plan is maintained in the sales order item, then only values flow from SD to PS.
PS Transactions (CJ43)
Transactions CJ42/CJ43 (revenue planning) or CN41 (PS Financial reports) can be used to check if the
revenues had transferred to the WBS element from the sales order.
In this scenario, as only 30% is to be billed at “contract sign” this year and the remaining in next year as
shown by the dates in the billing plan, the “sales order value” column in CJ43 shows the distribution of the
revenues across the periods in 2008 and in next year 2009 .
Cumulative column shows entire values for both years ( = Sales order Value + Prev year)
The “Sales order Value” shows the amount to be billed in 2009.
When the actual billing is done as per the dates in the billing plan, the actual revenue too gets posted to the
WBS elements.
The below structure shows the layering of the network & assignment of activities and components to all the
procurement & production items
These activities and the components assigned to them are used to collect costs which are totaled up to each
WBS element and to finally the top most WBS element.
Thus, the superior WBS elements/project definition can act as the pivotal point on which costs and revenues
can be compared and thus a superlative analysis can be done to monitor the profitability of the project.
In a project scenario where the costs and revenues can get easily out of track , such mapping in the system
helps for project managers to better monitor their cash ,cost & revenue flows.
The real scenario in an industry can have multiple instances of above described scenario, with WBS
elements being billing relevant and the Project sales order having 500-5000 items with assignments to WBS
elements.