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_MS21 | Define DRM Profile |
| Transaction Code | /SAPHT/64000052 | (empty) |
| Created on | 20000401 | |
| Customizing Attributes | /SAPHT/DRM_MS21 | Define DRM Profile. |
| Customizing Activity | /SAPHT/DRM_MS21 | Define DRM Profile |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPHT/DRM_SIMGMS21 |
DRM Profile for the Distributor
In this IMG Activity, you can create DRM profile to maintain a set of business rules. You can attach the profile to a tracking partner. DRM processes for the tracking partner will, then, be governed by the settings you have done in the attached profile.
Price Protection
Auto Pay.
If this flag is Set, then on processing the price protection due list, 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 tracking partner, then system creates the price protection debit memo request with a billing block. In the standard system, price protection debit memo request is created with the billing block 09 (Check Debit Memo).
Credit Memo Request Billing Block.
If this flag is set for the Customer, then system creates the price protection credit memo request with a billing block. In the standard system, price protection debit memo is created with the billing block 08 (Check Credit Memo).
DRM Close Calendar
The distributor profile will show such things as the distributor's close calendar (5-4-4 or month end or 4-4-5, etc.) Transmission frequency (daily/ weekly/ monthly) of resales /claims/ inventory report and user input tolerance percent and tolerance amount.
Close calendar type
Distributor close calendar type describes about the period close dates for that distributor.
Examples
5-4-4 indicates for each quarter there are 3 monthly close period dates which are 5 weeks, 4 weeks, 4 weeks.
4-4-5 indicates for each quarter there are 3 monthly close period dates which are made up of 4 weeks, 4 weeks, and 5 weeks.
LASTCDAY indicates that the last calendar day of each month is the period close date.
Transmission frequency
This indicates how often transmission of feeds of each type (resale, claims, inventory report) are sent by the distributor/ reseller.
Example: 3 times in 1 month, 4 times in 2 weeks.
Military flag indicates whether the distributor deals with military materials.
DRM tolerance percentage
This phone tolerance percentage indicates the maximum permissible percentage difference between the distributor/ reseller reported phone total and the actual feed value.
DRM total amount
This amount indicates the maximum permissible difference between the distributor/ reseller reported phone total amount and the actual feed value.
Ship and Debit
Billing Block
If this flag is set for the tracking partner, then system creates ship-and-debit debit memo request with a billing block. In the standard system, ship-and-debit debit memo request is created with the billing block 09 (Check Debit Memo)
Ship and Debit Claim Created Against
This refers to the type of partner against whom the ship and debit claim document is to be created. The possible partner types are tracking partner and sold-to party. If you set sold to party, then system will create the ship-and-debit creadit memo request against the branch reported by the distributor/ reseller. However, if the branch is not reported, it will create the claim against the tracking partner.
Samples
Samples Claim created Against
This refers to the type of partner against whom the samples claim document is to be created.The possible partner types are tracking partner and sold-to party.
Bill-up
Debit Memo Request Billing Block.
If this flag is set for the tracking partner, then system creates the Bill-up debit memo request with a billing block. In the standard system, bill -up debit memo request is created with the billing block 09 (Check Debit Memo).
Bill Up Claim Created Against
This refers to the type of partner against whom the bill-up claim document is to be created.The possible partner types are tracking partner and the sold-to party.
Schema Rules
Schema identifies a set of rules that should be applied before various claims are approved or duplicate resales or duplicate claims are checked.
Rule Determination Procedure for Samples
A schema identifies a set of rules that will be applied before a Sample claim is approved.
Examples:
A set of rules could be
"Sample quantity not exceeding 100pcs and the net value not exceeding 100 USD".
Schema Rules for Duplicate Resale Check
A schema identifies a set of rules that will be applied for duplicate resale check.
Examples
A set of rules for duplicate resale check could be
"If the same End Customer invoice no and ship date repeat for 2 resale records then they are duplicates."
Schema Rules for Duplicate Claim Check
A schema identifies a set of rules that will be applied for duplicate claim check.
Examples
A set of rules for duplicate claim check could be
"If the same End Customer invoice no, item no and claim sequence no repeat for 2 claim records then they are duplicates."
Schema rules for Bill-up Claims
A schema identifies a set of rules that will be applied for identifying a matching ship-and-debit claim for a resale return.
Examples:
A set of rules for Bill-up claim could be "The ship-and-debit claim with the same End Customer Invoice No, item no, ship date are duplicates"
Schema rules for matching of Resale and Claim
A schema identifies a set of rules that will be applied for identifying a matching resale record for a ship-and-debit claim.
Examples
A set of rules for matching of resale and claim record could be "The resale record with the same End Customer Invoice No, item no, ship date and device".
Drop Ship or Stock Resale
Distinguish between Drop Ship or Stock Resale.
This flag indicates whether the distributor/ reseller is able to differentiate a stock sell-through from a drop ship sell-through. If this flag is set for a distributor, system will increase the available quantity in a DRM lot even in the case of dropship.
Special Buy or Stock Resale.
Distinguish between Special Buy or Stock Resale
If this flag is set, it implies that for the distributor/ reseller, DRM system is able to differentiate between a stock resale and a special buy resale.
Sort Order of Lots
If the Distinguish between Special Buy or Stock Resale flag is not switched on, system can consume from both special buy and normal lots for the resale sell through reported by the distributor. You can direct the system to follow a particular sequence while consuming quantity from DRM lots. For example, if you have specified N, B, BB as the sort order, then system first finds out if there are quantity available in normal lots that can be used for consumption. If not, it will look for special buy lots, and if there is still a shortfall, system will look for blanket special buy lots.
End Customer Returns Without Reference to Resale Invoice -- Reference Lot
When you process an end customer return without reference, system creates a new DRM lot. Information on the new DRM lot is derived from an existing lot, called Reference Lot . System allows you to define the following parameters that are used by the system to zero in on the reference lot.
Lot Type
System searches for the reference lot based on the lot type selected.The types of lot types can be latest and oldest. That is, whether the latest or the oldest DRM lot with matching logical key is to be used as reference lot.
Sort Order of Lots
If Distinguish between Special Buy Returns and Stock Returns flag is set, it implies that this distributor/ reseller sends in return information dsitinguishing between returns from special buy and normal returns.
In this case, the system will first determine if the return is a special buy or normal return. In a standard system, DRM finds out this based on the presence of an active DRM condition type. After the system determines this, for a normal return system will only consider normal lots with matching logical key as a reference, and for a special buy return system will consider only the special buy lots with matching logical key as reference. If no such lots are found, system will error out.
If the Distinguish between Special Buy returns or Stock Returns flag is not switched on, 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, system will assign the price protectable price to the
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/DRMVPRF | V - View | /SAPHT/DRM_PRFM | Define DRM Profile. |
History
| Last changed by/on | SAP | 20000412 |
| SAP Release Created in |
