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_DR12 | Define DRM Profile |
| Transaction Code | /SAPHT/64000066 | (empty) |
| Created on | 20000406 | |
| Customizing Attributes | /SAPHT/DRM_DR12 | Define DRM Profile. |
| Customizing Activity | /SAPHT/DRM_DR12 | Define DRM Profile. |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPHT/DRM_SIMGDR12 |
DRM Profile for the Manufacturer
You can create DRM profile to maintain a set of business rules.
If you want to attach a DRM profile to a manufacturer/supplier, you need to do the following:
First, you must maintain a valid Customer in the Vendor Master record maintained for the manufacturer/supplier. You can do this in the Control View of the Vendor Master Maintenance. You can then attach the DRM profile in the Sales Area view of the Customer maintained in the above step.
For every DRM relevant transaction, the system first determines the applicable manufacturer from the material master. It then finds out the Customer defined in the manufacturer's Vendor Master. It then tries to find out if there is a profile attached to this customer for the relevant sales area. If the system does not find any DRM profile, it tries to use the default DRM profile defined for the sales area. If the system still does not find a profile for the sales area, it does not process the transaction.
Price Protection
Auto Pay: If this flag is set, then on processing the price protection due list, the system does not create any price protection credit/debit memo request. However, the DRM lots are updated with latest price.
Debit Memo Request Billing Block: If this flag is set for the customer, then the system creates the price protection debit memo request with a billing block. In the standard system, price protection debit memo is created with the billing block 09 Check Debit Memo.
Credit Memo Request Billing Block: If this flag is set for the customer, then the system creates the price protection credit memo request with a billing block. In the standard system, price protection credit memo request is created with the billing block 08 Check Credit Memo.
Ship-and-Debit
Credit Memo Request Billing Block: If this flag is set for the customer, then the system creates ship-and-debit credit memo request with a billing block. In the standard system, ship-and-debit credit memo request is created with the billing block 08 Check Credit Memo
End Customer Returns
You need to set up the following parameters to take care of situations arising out of end customer returns without reference to original sell-through invoice.
Sell-in Date: The system creates a lot when you process the credit memo for an end customer return without reference to the original sell-through invoice. In this field, you can define what should be the Latest Sell-in date for the lot created. The following options are available:
Transaction Date: The system stamps the date on which the transaction is getting processed as the Latest Sell-in Date of the Lot.
Ship/ Bill Date: The system stamps the billing date of the credit memo as the Latest Sell-in Date for the lot.
Earlier of Ship/ Bill Date and Transaction Date.
Later of Ship/ Bill Date and Transaction Date.
When the end customer returns goods to you, you may create the return order with or without reference to the resale invoice. When you process an end customer return without reference, the system creates a new DRM lot. Information on the new DRM lot is derived from an existing lot, called the Reference Lot. The system allows you to define the following parameters that are used by the system to zero in on the reference lot.
Lots not in sell-in: If this flag is set then lots which were not created in sell-in are also considered when the system searches for the reference lot.
Lots with Zero Qty: If this flag is set then lots with zero quantity are also considered when the system searches for the reference lot.
Lot Type: The system searches for the reference lot based on the lot type selected. The lot types here are latest and oldest.
Distinguish between Special Buy returns and Stock Returns.
If you switch on this flag, the system will first determine if the return is a special buy or normal return. In the standard system, DRM finds out this based on the presence of an active DRM condition type. After this, for a normal return, the system will only consider normal lots with matching key as a reference, and for a special buy return, the system will consider only the special buy lots with matching key as reference. If no such lots are found, system will error out.
Sort Order of Lots: If the flag is not switched on, the system will search for reference lot in the order specified. For example, if you have specified N,B,BB as the sort order, then the system first finds out if there is a normal lot that can be used as a reference; if not it will look for special buy lots; and if there is still no success system will look for blanket special buy lots.
Lot Price: Based on this setting the system will assign the price protectable price to the DRM lot created. The following options are available:
1. Current Sell-in Price: The system will find out what will be the price protectable price of quantities in a purchase order that gets created today. The details of this purchase order are derived from the purchase order that last updated the reference lot.
2. Reference lot price protectable price: The system puts the price protectable price of the reference lot as the price protectable price of the newly created DRM lot.
3. Minimum of Current Sell-in Price and Reference Lot Price Protectable Price.
4. Maximum of Current Sell-in Price and Reference Lot Price Protectable Price.
Options 1, 3 and 4 will require the system to execute remote functions calls in a DRM OLTP system in an ALE configuration. This will reduce the performance of processing any end customer return transaction.
Example
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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/DRMVPRO | V - View | /SAPHT/DRM_PRFD | Define DRM Profile. |
History
| Last changed by/on | SAP | 20000412 |
| SAP Release Created in |
