Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VIZ (Package) Introductory guide R/3 central functions
IMG Activity
ID | SIMG_CFMENUOLSDT_07 | Define Access Sequences |
Transaction Code | S_ALR_87005916 | IMG Activity: SIMG_CFMENUOLSDT_07 |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUOLSDT_07 | Define access sequences |
Customizing Activity | SIMG_CFMENUOLSDT_07 | Define access sequences |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUOLSDT_07 |
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 for a price that the SAP System first searches for a customer-specific price and then for a price list price.
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.
Actions
- 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).
Example
In pricing, you use a customer-material discount. The condition records you create are based on customer data from the document header and material data from each document item. The discount is only valid for 2% of your customers, however. Normally, this would mean that the system would needlessly search through every available item for 98% of your customers. In this case, prestep would improve system performance.
Further notes
The pre step perfomance improvement described above is not available for shipment costing within the framework of the Transportation component.
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_CFMENUOLSDT_07 | 0 | HLA0100740 | Freight Processing |
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 |
VVC_T682_FA | C - View cluster | SM34 | 0000000040 | Define access sequences |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |