Pre-Determined Pricing Engine 1 - SAP - SAP Help Portal · PDF filePre-determined pricing...

© 2012 SAP AG Dietmar-Hopp-Allee 16

D-69190 Walldorf

SAP Custom Development

Pre-Determined Pricing Engine 1.0

User Guide

Version Status Date

1.0 Final June 19, 2012

Customer

User Guide Customer

© 2012 SAP AG Dietmar-Hopp-Allee 16 D-69190 Walldorf

Title: Pre-Determined Pricing Engine 1.0 Version: 1.0 Date: June 19, 2012

of 17

Typographic Conventions

Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example

text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more

information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

User Guide Customer



of 17

Content

1 Overview ........................................................................................................ 4

1.1 Prerequisites ................................................................................................................... 4

1.2 Assumptions ................................................................................................................... 4

1.3 Login and Site Authorization ........................................................................................... 4

1.3.1 Authorizations ............................................................................................................ 4

1.3.2 Special Notes ............................................................................................................ 4

1.4 Glossary .......................................................................................................................... 4

1.5 User Roles within Pre-Determined Pricing Engine ......................................................... 7

2 Pre-Determined Pricing Engine Functionality ............................................ 7

2.1 Enhancements That Do Not Impact the User Interface.................................................. 7

2.2 Enhancements That Impact the User Interface .............................................................. 8

2.2.1 Introduction ................................................................................................................ 8

2.2.2 Details and Execution .............................................................................................. 10

2.3 Area Menu Options under Application .......................................................................... 10

2.3.1 PDP Engine Browser ............................................................................................... 10

2.3.2 PDP Engine Output Profile Maintenance ................................................................ 12

2.3.3 Display Output Sensitivity Index .............................................................................. 13

2.3.4 Activation and Deactivation ..................................................................................... 15

User Guide Customer



of 17

1 Overview

1.1 Prerequisites

Please ensure that your system has the following release level, as this is required to run the pre-determined pricing engine 1.0 application:

SAP ERP 6.0 EHP4, components SAP_APPL 604, SP 7 and EA-APPL 604, SP 7

1.2 Assumptions

This guide assumes that you have some level of familiarity with the terminology and functionality associated with pre-determined pricing.

This guide is intended to provide you with all the information you need to navigate through the pre-determined pricing engine application. It is recommended that this guide be used in conjunction with hands-on operation of the application.

1.3 Login and Site Authorization

1.3.1 Authorizations Pre-determined pricing engine functionality is executed from enhancements within standard SAP ERP transactions (such as VK11 and VK12 for maintaining SD pricing conditions). Since no separate screens are provided, no special logon procedures apply.

1.3.2 Special Notes Graphics are used throughout this guide to highlight and illustrate various details. The detail displayed in the graphics may differ from the detail you see in the same areas in your working session. Similarly, this guide may also define working areas and functions to which you do not have access. Your specific access depends on your specific authorization.

This document has been created from the pre-determined pricing engine perspective, as this is the system on which all application features and functions are available.

1.4 Glossary

Term Definition

SAP application SAP software that serves a specific business area – for example, SAP ERP, SAP Customer Relationship Management, SAP Product Lifecycle Maintenance, SAP Supplier Relationship Management, and SAP Supply Chain Management.

User Guide Customer



of 17

Term Definition

Business scenario From a microeconomic perspective, a business scenario is a cycle that consists of several interconnected logical processes in time. Typically, a business scenario includes several company departments and involves other business partners.

From a technical point of view, a business scenario needs at least one SAP application (SAP ERP, SAP SCM, or others) for each cycle and possibly other third-party systems.

A business scenario is a unit that can be implemented separately and reflects the customer’s prospective course of business.

CDM delay Defines the object- or subobject-specific delay parameter used when PDP engine data maintenance processes a PDP engine worklist. The delay is defined in seconds. It is recommended that this setting is set higher than the profile parameter rdisp/bufref time for buffered objects. It can be left blank/zero for unbuffered objects.

Change detection This component of the PDP engine detects master data changes and captures the structures and tables that contain the old and the new values of the master data object. A generic interface is then implemented to pass the data to the PDP engine, which encodes and dispatches the data to the change relevance determination.

Change detection registry

A list of objects and fields that are tracked for change in the PDP engine data change detection service.

Relevance determination This component of the PDP engine determines if the change to the master data object is relevant for further processing. . This service also determines if processing must be executed immediately (known as active change), be deferred into the future (known as passive change), or both. The scope of the change is assigned at this point in the process.

Change relevance This functionality within data maintenance identifies if a tracked change requires further processing by the change collector service and whether the subsequent collector service processing should occur immediately or should be delayed.

Change collector This component of the PDP engine is used to expand or reduce the worklist of possible PDP engine entries that can be reevaluated based on the detected change. The change collector also persist the data to worklist storage for the data maintenance service to further process the worklist.

Change collector service The PDP engine functionality that provides pre-processing of change events before PDP engine data maintenance is invoked.

Change collector worklist

A list of PDP engine data changes that is returned to the collector service.

Collector service profile The identifier used when assigning object class-specific worklist expansion and reduction function modules. These function modules provide object-specific context handling and scope and span determination of a detected data change. They are used to build a change collector worklist for the PDP engine.

User Guide Customer



of 17

Term Definition

Component The smallest individual unit considered within the Solution Development Lifecycle.

Components are separately produced, delivered, installed, and maintained.

Data maintenance The data maintenance tier processes the collector service work list and updates the PDP engine data such as the customer’s current price for a material.

Eligibility The ability of the PDP engine to use a configured set of rules and functions to determine if a material should be included or excluded for sale or distribution to a specific customer, such as a sold-to party.

Object class A group of master data objects that are monitored by PDP engine change detection for any transactional changes to the master data.

Output profile A container for technical parameters that are used by the Format and Delivery service. These parameters control various aspects of PDP engine format rendering and distribution. The retrieval API provides output profile details. Output profiles are assigned to customers using the customer master maintenance transaction.

Output sensitivity A component of the PDP engine used to identify business object-level table name and field name combinations that are relevant for customer-specific PDP engine output generation. Output sensitivity is only relevant for delta outputs.

Passive change The deferred processing of change relevant master data objects in the PDP engine.

Passive detection span A value, less than 25 years, that specifies the maximum time span for passive change to be effective in the PDP engine. After the specified time, a worklist entry is not triggered for this passive change.

PDP management framework

A framework that provides the ability to flexibly assign an independent flow of business logic for a particular object or process across all PDP engine processing subsystems. The PDP management framework uses sequenced activity sets to control the processing logic.

Price layering Decides whether or not the price should be recalculated for a customer/material combination in the PDP engine. The rules implemented in the Price Layering BAdI are intended to reduce the number of customer/material combinations that need to be re-priced and therefore improve PDP engine performance.

Price verification A tool that looks at discrepancies that arise over time in the prices in sales orders compared with the prices in the PDP engine for quality management purposes.

Pricing The process for determining price information. The system uses condition techniques for pricing to determine the relevant price information that a customer pays for a material.

User Guide Customer



of 17

Term Definition

Pre-determined pricing engine

An SAP ERP-resident engine that calculates in near-real time, and stores the customer’s current price data. As changes to the sources of master data occur during the course of business operations the PDP engine identifies master data changes relevant for pricing, recalculates the effected customer’s prices and updates the customer’s current price data within the PDP engine.

Scope The scope identifies which activities must be performed for the data maintenance component– for example, price determination or output sensitivity.

Usage A purchase history based on sales and distribution billing functionality that creates customer invoice documents.

Worklist expansion The process of calling the worklist expansion function module, which performs the scope and relevancy determination.

Worklist reduction The process of using coding and configuration provided by the customer to optimize processing of data changes that are not business relevant. In this way, it is possible to bypass data maintenance activities that are resource or processing intensive (for example, pricing and eligibility check).

1.5 User Roles within Pre-Determined Pricing Engine

A single user role is delivered as part of pre-determined pricing engine. This role is required to set up a specific user for configuring background RFC (bgRFC). The role is not created for use with an end user ID.

2 Pre-Determined Pricing Engine Functionality

Pre-determined pricing engine functionality is executed from enhancements within standard SAP ERP transactions. The following sections describe these enhancements and give details of how to use the functionality they provide.

The pre-determined pricing engine comprises the following:

Enhancements that do not impact the user interface

Enhancements that impact the user interface

Area menu options under Application

2.1 Enhancements That Do Not Impact the User Interface

The following standard SAP ERP transactions contain pre-determined pricing engine enhancements that do not impact the user interface.

These enhancements take a snapshot of the transaction data before and after a change. The “before” and “after” data is then passed to PDP engine for further processing. PDP engine processing then determines whether the change is relevant for pricing and whether a delta output change is required.

User Guide Customer



of 17

Transaction Functionality

XD01/VD01 Sales and Distribution: Customer Create

XD02/VD02 Sales and Distribution: Customer Change

VDH1N Sales and Distribution: Customer Hierarchy

VB01 Sales and Distribution: Product Listing/Exclusion Create

VB02 Sales and Distribution: Product Listing/Exclusion Change

VF01 Sales and Distribution: Billing Create

VF02 Sales and Distribution: Billing Change

VK11/VK31 Sales and Distribution: Pricing Create

VK12/VK32 Sales and Distribution: Pricing Change

MM01 Material Master: Material Create

This is merely an example of a generic transaction; “special” material transactions also use the material enhancement for pre-determined pricing.

MM02 Material Master: Material Change

This is merely an example of a generic transaction; “special” material transactions also use the material enhancement for pre-determined pricing.

ME01 Purchasing: Vendor Source List Create

ME04/ME0M Purchasing: Vendor Source List Maintain

MK01/XK01 Purchasing: Vendor Create

This is merely an example of a generic transaction; “special” purchasing transactions also use the purchasing enhancement for pre-determined pricing.

MK02/XK02 Purchasing: Vendor Create

2.2 Enhancements That Impact the User Interface

2.2.1 Introduction In addition to the enhancements that do not impact the user interface, the following transactions contain functionality that is visible to the user in the form of an extra pushbutton:

XD01/VD01 Sales and Distribution: Customer Create

XD02/VD02 Sales and Distribution: Customer Change

User Guide Customer



of 17

The Pre-determined Pricing for customer pushbutton is visible if the PDP engine is installed in the SAP ERP system.

This functionality enables the user to see whether the activation switch for the PDP engine is turned on for a particular customer. It also allows the user to maintain the appropriate output profiles required for the customer when the PDP engine output sensitivity functionality is implemented.

Figure 1: Pre-determined Pricing for customer Pushbutton

User Guide Customer



of 17

2.2.2 Details and Execution When you choose the Pre-determined Pricing for customer pushbutton, the system displays the Pre-determined pricing for Sales Area tab page below the customer data.

This tab page contains the PDPE Active for customer checkbox, which is always grayed out on this screen. This checkbox is only selected if PDP engine functionality has been activated for the customer in the sales area shown.

The tab page also shows which output profiles have been defined for the customer using the Activate Output Profile for Customer option (transaction /n/PDPENG/ACTV_OUTPROF) available from the Pre-Determined Pricing Engine Menu (transaction /n/PDPENG/) under Application.

For more information about the Activate Output Profile for Customer option, see Section 2.2.7.3 of this document.

Figure 2: Pre-determined pricing for Sales Are Tab Page

2.3 Area Menu Options under Application

You use the options in this section of the area menu to display information about particular customer/material combinations, display and maintain output profiles, and activate and deactivate the PDP engine functions for specific customer/material combinations.

2.3.1 PDP Engine Browser

You use this option to display various types of information about a particular customer/material combination.

User Guide Customer



of 17

You can access this option from the Pre-Determined Pricing Engine area menu under Application → PDP Engine Browser or directly by entering /n/PDPENG/CAT_BROWSER in the transaction field at the top of

the screen.

On the initial screen, you must enter values for all parameters in the Customer screen area. You can also enter a material if required.

Figure 3: Initial Screen of PDP Engine Browser

When you choose the Execute icon or press F8, the system displays the information recorded for the

customer you have specified:

Figure 4: Result Screen of PDP Engine Browser

User Guide Customer



of 17

The first table shows the materials for which the customer is eligible. When you select a row from this table, the system displays further details about this material in the second table on the screen.

Figure 5: Detailed Customer Information in PDP Engine Browser

This table is divided into the following tab pages:

Tab Page Description

Pricing Shows pricing information for the customer-material combination, for example, the pricing type and the currency used.

Usage Shows information about the last time the material was sold to the customer, for example, the billing document number, billing date, and price.

Item EANs (from MEAN) Shows the International Article Numbers of the materials

2.3.2 PDP Engine Output Profile Maintenance You use this option to view and maintain output profiles, which you can then assign to customers using the Activate Output Profile for Customer option (for more information, see Section 2.3.4.3 of this document).

Output profiles contain technical parameters that control various aspects of catalog format rendering and distribution.

You can access this option from the Pre-Determined Pricing Engine area menu under Application → PDP Engine Output Profile Maintenance or directly by entering /n/PDPENG/OP_MAINTAIN in the transaction

field at the top of the screen.

On the initial screen, you specify the output profile that you want to display, edit, or delete; alternatively, you can choose the New icon to create a new output profile.

Figure 6: Initial Screen of PDP Engine Output Profile Maintenance

User Guide Customer



of 17

If you choose to display an output profile, the system displays the criteria that have been configured for the output profile and gives you the option to change these by choosing the Edit icon:

Figure 7: Result Screen of PDP Engine Output Profile Maintenance

2.3.3 Display Output Sensitivity Index You use this option to view the changes that have occurred since the last time the customer requested data. Once the customer confirms that they have received the new data, the delta cache is cleared and the system starts collecting new changes.

You can access this option from the Pre-Determined Pricing Engine area menu under Application → Display Output Sensitivity Matrix or directly by entering /n/PDPENG/D_OSDINDX in the transaction field

at the top of the screen.

You must enter a value for each of the fields and then specify whether the delta index is to be ready from

the delta cache or recovery cache. To view the results, choose Execute or press F8.

The recovery cache is a temporary file that is updated at the start of the process that transmits the delta cache information to a customer. If the information is transmitted to the customer successfully, the recovery cache records are deleted.

User Guide Customer



of 17

Figure 8: Initial Screen of Display Output Sensitivity Index

Figure 9: Result Screen of Display Output Sensitivity Index

User Guide Customer



of 17

Below is an explanation of the fields in the output display:

Field Description

Customer Customer number that you entered on the initial screen

O/P Profile Output profile that you entered on the initial screen

Material Material affected by the delta change

Action Type of change; possible values:

A: Add

D: Delete

U: Update

Total count Number of delta records that exist for the selection; customer, sales area, output profile

2.3.4 Activation and Deactivation

You use the options in this section to activate and deactivate the PDP engine functions for specific customers and to assign and unassign predefined output profiles to specific customers.

2.3.4.1 Activate PDP Engine for Customer

You use this option to activate the PDP engine functions for a particular customer in a specific sales area. When the PDP Engine functions are activated, pricing changes for this customer are recorded.

You can access this option from the Pre-Determined Pricing Engine area menu under Application → Activation / Deactivation → Activate PDP Engine for Customer or directly by entering /n/PDPENG/CAT_ACT in the transaction field at the top of the screen.

If you select the Test Mode checkbox, the changes you make are not committed to the database.

Figure 10: PDP Engine Activation

User Guide Customer



of 17

2.3.4.2 Deactivate PDP Engine for Customer

You use this option to deactivate the PDP engine functions for a particular customer. When the PDP Engine functions are deactivated, pricing changes for this customer are not recorded.

You can access this option from the Pre-Determined Pricing Engine area menu under Application → Activation / Deactivation → Deactivate PDP Engine for Customer or directly by entering

/n/PDPENG/CAT_DEACT in the transaction field at the top of the screen.

If you select the Test Mode checkbox, the changes you make are not committed to the database.

Figure 11: PDP Engine Deactivation

2.3.4.3 Activate Output Profile for Customer

You use this option to activate a defined output profile for a customer. For more information about output profiles, see Section 2.3.2 of this document.

You can access this option from the Pre-Determined Pricing Engine area menu under Application → Activation / Deactivation → Activate Output Profile for Customer or directly by entering

/n/PDPENG/ACTV_OUTPROF in the transaction field at the top of the screen.

Figure 12: Activate Output Profile for Customer

User Guide Customer



of 17

2.3.4.4 Deactivate Output Profile for Customer

You use this option to deactivate a defined output profile for a customer. For more information about output profiles, see Section 2.3.2 of this document.

You can access this option from the Pre-Determined Pricing Engine area menu under Application → Activation / Deactivation → Deactivate Output Profile for Customer or directly by entering

/n/PDPENG/CAT_PDEACT in the transaction field at the top of the screen.

Figure 13: Deactivate Output Profile for Customer

Pre-Determined Pricing Engine 1 - SAP - SAP Help Portal · PDF filePre-determined pricing...

Documents

Transcript of Pre-Determined Pricing Engine 1 - SAP - SAP Help Portal · PDF filePre-determined pricing...