Technical Name of Business Function |
FIN_PDCE_COSTQUOT |
Type of Business Function |
Enterprise Business Function |
Available as of |
SAP Enhancement Package 3 for SAP ERP 6.0 |
Technical Usage |
Strategic Enterprise Mgmt |
Application component |
Business Analytics (FIN-BA) |
Directly dependent business function that you have to activate in addition |
Not relevant |
This business function, contained in the Product Design Cost Estimate (PDCE) further supports you in cost of production planning and optimization for the design, construction and offer phases. This means that with PDCE, you can direct cost estimates at particular objectives, such as customer quotation costing, cost saving measures, price changes, enhanced cost component splits (currency shares, production plants, price rating, and so on).
You can also make use of the enhanced functions in this business function if you want to use PDCE in connection with SAP Cost and Quotation Management (SAP xCQM), for example.
In the product design cost estimate you can use data that you have already created in other applications:
You use plan costings from Product Cost Controlling (CO-PC-PCP).
You use activity-related data from Cost Center Accounting (CO-OM-CCA), such as prices of processes, prices of activity types, or templates.
You employ material master data and movement data, for example, prices from Materials Management (MM).
You can use BOMs in the master data of your Production Planning (PP).
You can use variants in PLM iPPE.
You can work with external systems via XML mapping.
You can include additional fields in your cost estimates that you define in SAP Business Intelligence (SAP BI).
Note
SAP Business Intelligence is used within the Product Design Cost Estimate as a source for additional characteristics and key figures that you can use in your cost estimates. Updating the costing data takes place locally in application-specific tables of the system in which you operate the Product Design Cost Estimate. You can extract the costing data from your operational system into SAP BI and analyze it there.
Moreover, PDCE can be used as a back-end system for SAP Cost and Quotation Management (SAP xCQM). If you want to use the Web application of SAP xCQM, then you have to implement the corresponding business package.
Note
You should note that SAP xCQM is not part of this business function. You can find information on the Web application for xCQM in the SAP Library for SAP Collaborative Cross Applications under .
You have installed the following components as of the versions given:
Type of component |
Component |
Only required for the following functions |
Software Component |
SEM-BW 603 |
|
Business Intelligence Content |
SAP BI 703 |
If you are not using SAP BI in the same system as PDCE, you have set up an RFC destination for the appropriate BI system.
In SAP Business Intelligence, you have activated the InfoObjectCatalogs PDCE key figures (0SEM_PDCE_KYF01) and PDCE characteristics (0SEM_PDCE_CHA01) delivered as business content.
Make sure that for PDCE in SAP ERP Enhancement Package 3 for ERP 6.0, you use SAP BI 703 as the correct basis.
You have created the data basis and the logical system connection, and then registered the data basis at the BI object directory.
You have generated the PDCE structure having registered the PDCE data basis.
If you activate the business function Cost and Quotation Management, the following functions are available:
You can use reports to define selection variants and to create variants for the cost estimate. The creation of dynamic or static selection is supported by a wizard. Further, you can schedule the calculation of the costing structure for background processing.
For more information, see the application documentation under Background Processing for Costing.
The copy as function for an object in the structure (transaction UAMO) enables you to change the object type, and supports other key fields for the entry.
For more information, see the application documentation under Copying of Objects and Structures; Costing Versions.
This new function enables you to make a change to the status irrespective of the existing status flow logic. Permitted status changes are pre-defined in a table. If you change a status by skipping, the appropriate status inheritance and the transfer of the status results at the same time.
For more information, see the application documentation under Status Management.
The where-used list for an object in the structure (transaction UAMO) is supported by a wizard. Using the wizard, you can find all usages or assignments of the object selected in the database, across a variety of work environments, and also usages for an object in a structure without a working environment.
For more information, see the application documentation under Where-Used List.