Hierarchy
⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷ VA (Package) Application development R/3 Sales
IMG Activity
ID | SD_BF_PRODVOR006 | Define Product Proposal Procedure and Determine Access Sequences |
Transaction Code | S_ALR_87009600 | (empty) |
Created on | 19990309 | |
Customizing Attributes | SD_BF_PRODVOR006 | Define Product Proposal Procedure and Determine Access Sequences |
Customizing Activity | SD_BF_PRODVOR006 | Define Product Proposal Procedure and Determine Access Sequences |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SD_BF_PRODVOR006 |
In this IMG activity, you define the product proposal procedure and determine the order in which the system creates the materials for the product proposal from individual data sources.
In the definition, you determine:
- The number of periods that should be displayed in sales doc. procesing. This means that if you use the order history as a data source, how many order quantity columns there should be in the sales document.
Note:
You can define a maximum of twelve columns in the sales document. - The period in which the historic order quantities should be compressed (day, week, month)
Note:
If you do not activate a period type, each column in the sales document contains the quantity from one order.
For example:
Order Creation date Material Quantity
1000 01/13/99 Mat 1 1
Mat 2 2
1001 01/14/99 Mat 1 3
1002 01/14/99 Mat 1 3
1003 01/18/99 Mat 3 4
1004 01/22/99 Mat 1 5
Product proposal: Number of orders:
Material 01/22/99 01/18/99 01/14/99 01/14/99 01/13/99
Mat 1 5 3 3 1
Mat 2 2
Mat 3 4
Product proposal: Cumulated per day:
Material 01/22/99 01/18/99 01/14/99 01/13/99
Mat 1 5 6 1
Mat 2 2
Mat 3 4
Product proposal: Cumulated per week:
Material Week 03 Week 02
Mat 1 5 7
Mat 2 2
Mat 3 4
- The output format of the column headings (date, weekday, calendar week, or month)
Note:
Ensure that the column heading matches the period type you have chosen. If you want individual columns to have different headings, you must program this specifically in the function module that the system accesses. This also applies if you want different calculation operations to take place in individual columns (for example, totalling).
The access sequence determines the order in which the system access the data sources you have specified and how it should combine the partial results from the accesses to a product proposal. In order to do this, the system needs the following information:
- Name of the function module that evaluates the data source (here you can store your own function modules)
The following function modules are defined in the standard system:
Function module name Data source
SD_DPP_CUSTOMER_MATERIAL_INFO Material from customer-info record
SD_DPP_EXCLUSION Material from exclusion
SD_DPP_HISTORY Material from order history
SD_DPP_LISTING Material from listing
SD_DPP_PRODUCT_PROPOSAL Material from product proposal
The function module called SD_DPP_READ is only for reading the product proposal from the database if you are generating the product proposal in the background. You must specify this function module in the access sequence for the online procedure.
WARNING
If you combine the background determination with a determination in the Online site, the function module SD_DDP_READ must always be listed as the first function module in the Online procedure.
- Freely-definable parameters (function module attributes) for controlling the function module
The parameters you enter here are transferred as values to the function module. For example, you can specifiy the name of a certain item proposal that the system should access, or the name of the information structure for a statistical evaluation. - Activity indicator for the function module that specifies how you should proceed with the materials or the end result determined by the function module. To form the end result of the product proposal, you can carry out one of the following operations:
- Indicator A: Add
- Indicator B: Remove (for example, for excluded goods)
- Indicator C: Check and compare (for example, for listed goods)
- Indicator D: Mix result externally
This indicator is designed for when you want to use operations or calculation rules to determine the end result but indicators A, B, and C do not meet your requirements. You have to save the operations for mixing the result in the function module itself. If you then choose indicator D, the end quantity determined at this point is transferred to the specified function module, where the system then runs the operations stored there. The final result is then used as the product proposal.
The following table illustrates how the activity indicators work when determining a product proposal:
Activity Result of Result of Result after
indicator previous current current access
accesses access
________________________________________________________________________
A Material A Material B Material A
Material B Material C Material B
Material C Material D Material C
Material D
B Material A Material B Material A
Material B Material C
Material C Material D
C Material A Material B Material B
Material B Material C Material C
Material C Material D
D Material A Material B Material B
Material B Material C Material C
Material C Material D Material D
- Indictor that specifies which data source (for example, order history, item proposal, listing), the product proposal comes from. This indicator is displayed in the sales document so that you can see where the product proposal was determined.
Note:
If the same material in the product proposal comes from several sources, for example, from the order history and from an item proposal, the system displays the indicator in the sales document for the first data source it accessed. - The sorting sequence of materials in the product proposal as displayed in the sales document. It controls which materials should appear first in the product proposal for th
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SD_BF_PRODVOR006 | 0 | HLA0006560 | Basic Functions |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
PV-SCHEMA | C - View cluster | SM34 |
History
Last changed by/on | SAP | 19990407 |
SAP Release Created in |