Hierarchy

⤷

⤷

IMG Activity
ID | /SAPHT/DRM_MS2 | Map Sales document & item category to transaction codes |
Transaction Code | /SAPHT/64000003 | (empty) |
Created on | 20000223 | |
Customizing Attributes | /SAPHT/DRM_MS2 | Map sales document & item category to transaction codes |
Customizing Activity | /SAPHT/DRM_MS2 | 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_SIMGMS2 |
In this IMG activity, assign the DRM relevant transaction code andprocessing code to a combination of sales document type and sales document item category. The mapping is used by the system:
1. To identify the Sales Document Type and Item Category combinations that are relevant for DRM processing.
2. To identify the DRM process that should be triggered for such a Sales Document Type and Item Category combination.
However, the system will use this information only if the Output Type for the Delivery document and Billing document are configured to trigger the DRM processing.
You need to map a unique combination of Sales Document Type and Item Category for the following DRM processes:
Sell-in to Distributor/ Reseller . Both the Normal and special buy sell-in are mapped to the same transaction code. In the standard system this is MSSI (mapped to processing code G).
Drop Ship Sell-in to Distributor/ Reseller. Sales Document Type and Item Category combination that is used for a normal and special buy sell-in to distributor/ reseller can also be used for Drop Ship Sell-in. However, system proceeds with dropship processing if the sales order line item has the dropship flag set. For this, the standard system has transaction code MDSI mapped to processing code H.
Return by the Distributor. Sales Document Type and Item Category that identify a return of material by the distributor/ reseller are mapped to a DRM transaction code. In the standard system this is MRMS mapped to processing code I.
Claim Processing. Sales Document Type and Item Category that identify price protection, ship-and-debit, bill-up claim are mapped to appropriate transaction codes.
Example
In the standard system, Sales Document Type OR and Item Category TAN are mapped to the DRM Sell-in (transaction code MSSI ). 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 the customizing and if so to 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 system logs an error while processing the Output of the document.
Requirements
DRM transaction codes to which the Sales Document Type and Item categories are being mapped, must have already been defined in the Customizing step Define new transaction codes
Standard settings
In the standard system following mapping exists:
Order Type Item Category Transaction Code Processing Code
OR TAN MSSI G
JRE REN MRMS I
JPCM G2N MPPC Q2
JPDM L2N MPPD M2
JSDC G2N MCLS M2
JBDM L2N BUMP W2
Recommendation
Activities
Further notes
You can map more than one combination of Sales Document Type and Item Category to the same 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_C02 |
History
Last changed by/on | SAP | 20000302 |
SAP Release Created in |