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_DR3 | Map Purchasing Document & Item Category to transaction codes |
| Transaction Code | /SAPHT/64000015 | (empty) |
| Created on | 20000223 | |
| Customizing Attributes | /SAPHT/DRM_DR3 | Map Purchasing Document & Item Category to transaction codes |
| Customizing Activity | /SAPHT/DRM_DR3 | Map Purchasing Document & Item Category to transaction codes |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPHT/DRM_SIMGDR3 |
In this IMG activity, assign DRM relevant transaction codeand processing code to a combination of purchasing document type and purchasing document item category.
The mapping is used by the system to:
1. Identify purchase order type and item category combinations that are relevant for DRM processing.
2. Identify the DRM process that should be triggered for such a combination.
However, the system will use this information only if the output type for the materia document and logistics invoice document are configured to trigger the DRM processing.
You need to do this mapping for the DRM process: Sell-In from manufacturer/supplier. Both normal as well as special buy sell-in are mapped to the same transaction code. In the standard system this is DSSI.
Example
In the standard system, purchase document type NB and item category 0 are mapped to DRM sell-in (transaction code DSSI). During goods receipt and logistics invoice verification process, if the upstream purchase document type and Item category are determined as NB and 0 respectively, then the DRM processing for this material docuemnt or invoice document is triggered.
Requirements
DRM transaction codes to which the purchase document type and item category combinations are being mapped, must have already been defined in the Customizing step Define new transaction codes
Standard settings
In the standard system following mappings exist:
Order Type Item Category Transaction Code Processing Code
NB 0 DSSI A
NB 5 DDIW B1
Recommendation
Activities
Further notes
1. You can map more than one combination of purchase document type and item category to the same DRM transaction code.
2. You cannot map the same combination of purchase 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/DRMVMMXN | V - View | /SAPHT/DRM_C12 |
History
| Last changed by/on | SAP | 20000302 |
| SAP Release Created in |
