Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-HT-DRM (Application Component) Distributor-Reseller-Management⤷
/SAPHT/DRM14 (Package) DRM Customizing for ES only
IMG Activity
| ID | /SAPHT/DRM_DR2 | Map Sales Document & Item Category to transaction codes |
| Transaction Code | /SAPHT/64000014 | (empty) |
| Created on | 20000223 | |
| Customizing Attributes | /SAPHT/DRM_DR2 | Map Sales Document & Item Category to transaction codes |
| Customizing Activity | /SAPHT/DRM_DR2 | Map Sales Document & Item Category to transaction codes |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPHT/DRM_SIMGDR2 |
In this IMG activity, assign DRM relevant transaction codeand processing code to a combination of sales document type and sales document item category.The mapping is used by the system to:
1. Identify sales order and item category combinations that are relevant for DRM processing.
2. Identify DRM process that should be triggered for each such combination.
However, the system will use this information only if the output type for the Delivery document and Billing document are configured to trigger DRM processing.
For each such DRM process, you need to map a unique combination of sales document type and item category to the appropriate transaction code. These processes that are identified through combination of sales document type and item category are:
Sell-in
Sell-through
claim processing
Example
In the standard system, sales document type OR and item category TAN are mapped to DRM sell-through (transaction code: DSST). When DRM processing is triggered via output for a Delivery, the system determines the sales document type and item category of the Delivery document item. It then looks if this combination is defined in customizing, and if so, which DRM process the combination maps to.
If you trigger the DRM processing using Output type for a Delivery and Billing document, but do not maintain entries for the upstream sales document type and item category, then the system logs an error while processing the output.
Requirements
DRM transaction codes to which the sales document type and item category combinations are mapped must have already been defined in the Customizing step Define new transaction codes
Standard settings
In the standard system, the following mappings exist:
Order Type Item Category Transaction Code Processing Code
ZDOR TAN DSST C
JOR JRE DRMS F
JPCD G2N DPPC R2
JPDD L2N DPPD R2
JSDC G2N DCLS P2
JBDM L2N BUDP V2
Recommendation
Activities
Further notes
1. You can map more than one combination of sales document type and item category to the same DRM transaction code.
2. You can not map the same combination of sales document type and item category to more than one DRM transaction code.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
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 |
| /SAPHT/DRMVSDXN | V - View | /SAPHT/DRM_C43 |
History
| Last changed by/on | SAP | 20001207 |
| SAP Release Created in |
