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_MS40 | Define Access Sequence for Price Protection |
| Transaction Code | /SAPHT/64000070 | (empty) |
| Created on | 20000411 | |
| Customizing Attributes | /SAPHT/DRM_MS40 | Define Access Sequence for Price Protection |
| Customizing Activity | /SAPHT/DRM_MS40 | Define Access Sequence for Price Protection |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPHT/DRM_SIMGMS64 |
You define access sequences in this IMG step.
The access sequence is a search strategy which the SAP System uses to search for condition records valid for a condition type.
For example, you can define a Price Protection Rule that the SAP System first searches for a customer-specific Rule and then for a material specific Rule.
Example
Requirements
Standard settings
In the standard system Access Sequence PPAS has been defined, which uses Condition table 001.
Recommendation
If you define your own access sequences, the key should start with the letter Z since SAP reserves this letter for the standard system.
Do not change access sequences contained in the standard SAP R/3 System.
Activities
Check to what extent you can use the access sequences contained in the standard SAP R/3 System.
Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key which may have up to 4 digits and a textual description.
Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. With the sequence, you define the priority of the accesses. You can display combinations of key fields using possible entries.
Generating the accesses is no longer necessary as of 3.0, as this is carried out automatically. You can generate the accesses manually, if required, by choosing "Utilities".
Improved performance by using prestep for accesses.
To improve performance, you can optimize the accesses to a condition type by having the system carry out a prestep:
You use the prestep to determine whether the system should first only search for condition records using the document header data. If the search is unsuccessful, then this access is not used to search from the individual items.
The prestep can only be used for accesses with header and item data.
The greater the average number of items in a document, the more useful prestep becomes.
The less likely it is that you will find a valid condition record, the more useful it is to use prestep (see the following example).
Further notes
Business Attributes
| ASAP Roadmap ID | 105 | Define 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 |
| V_T682 | V - View | /SAPHT/DRMRUH3AS |
History
| Last changed by/on | SAP | 20000423 |
| SAP Release Created in |
