Ansicht
Dokumentation

SIMG_CFMENUOLSDVOKX - Define Access Sequences

TXBHW - Original Tax Base Amount in Local Currency   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Change access sequences for sales.

In this step, you define access sequences.

An access sequence is a search strategy that the system uses to search for valid condition records of a certain condition type.

For example, you can define for a price that the system first searches for a customer-specific price and then for a price-list price.

For condition types for which you wish to maintain conditions with their own validity period, you must assign an access sequence. With this, you define which fields the system checks when searching for a valid condition record.

• If you define your own access sequences, the key should start with the letter Z since SAP reserves these namespaces in the standard system for customers.

• If you define your own access sequences, the key must start with the letters Y or Z as SAP reserves these namespaces for new access sequences created in customer systems.

• You should not change access sequences that are included in the standard system.

1. Check to what extent you can use the access sequences contained in the standard system.
2. Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key, which can have a maximum of 4 digits and a descriptive text.
3. Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key, which can have a maximum of 4 digits starting with the letters Y or Z and a descriptive text.
4. Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. The sequence defines the order of priority of the accesses. You can display combinations of key fields using possible entries.
   

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).

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.

BAL Application Log Documentation   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 3198 Date: 20240523 Time: 193715     sap01-206 ( 64 ms )