Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-PA-STC (Application Component) Single Transaction Costing⤷
JBTC (Package) Customizing IS-B Transaction Costing
IMG Activity
| ID | SIMG_CFJB08JB48 | Define Access Sequences |
| Transaction Code | S_KK4_13000044 | IMG Activity: SIMG_CFJB08JB48 |
| Created on | 19990830 | |
| Customizing Attributes | SIMG_CFJB08JB48 | Define Access Sequences |
| Customizing Activity | SIMG_CFJB08JB48 | Define Access Sequences |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFJB08JB48 |
In this activity you determine the sequences for the flexible procedures in Bank Profitability Analysis. Each condition type for which condition records are created is assigned an access sequence. The system uses the access sequence to search for valid data records when the flexible procedures are executed.
You have already defined the search terms i.e. the conditions for the condition records. Since you can assign alternative search strategies to a condition type you need to use the access sequence to determine in which sequence the system processes the condition combinations. You could start condition record determination with a special combination and continue with a more general combination. This condition table 'queue' ensures that a condition record is accessed on the basis of the characteristic values transferred or not transferred from the legacy systems.
Each access within the access sequence refers to one condition table.
Example
You could specify the following access sequences for the three condition tables named below:
No. Condition table
1 Risk costs dep. on rating class
2 Risk costs dep. on industry and prod.group
3 Risk costs dep. on cust.group and rating class
In the access sequence you can specify that table 3 is followed by table 1 and then by table 2 when the risk costs are determined. If the characteristic values for the characteristics rating class and customer group are transferred, the condition record is accessed and the risk costs determined accordingly. If the field customer group is not transferred, but the rating class is, the risk costs are determined purely on the basis of the rating class.
Model/Example
Access seq. 1 (ZF1) Condition table Exclusive indicator
1st level EC costs KT8
Access seq. 2 (ZF2) Condition table Exclusive indicator
2nd level EC costs KT1 x
KT2 x
KT4 x
KT3 x
KT8
Access seq. 3 (ZF3) Condition table Exclusive indicator
Operating costs KT5
Access seq. 4 (ZF4) Condition table Exclusive indicator
Provision costs transaction KT6
Access seq. 5 (ZF5) Condition table Exclusive indicator
Provision costs country KT7
Requirements
You must first create Condition tables.
Activities
For each access sequence enter a short description and an appropriate name.
On the detail screen, specify:
- with which condition tables condition records are accessed
- in which sequence the condition tables are processed
If the search is to be terminated once a condition record has been successfully accessed, click on the E (=Exclusive) button. This means that the system will search for no further condition record for that condition type.
If you have not set E and several condition records are found for a condition type, the values are added up.
On the "Access sequence: Access" screen you specify:
- with which field contents the condition tables are read
This screen must be called up for each condition table.
Example
Access sequence Z001 for condition type K001
CnN. Table Description Exclusive
-----------------------------------------------------------------------
01 501 Table business partner group/bank product X
02 502 Table business partner group
The access sequence Z001 first searches for condition records stored for a certain business partner group/bank product combination. If no matching record is found, it searches to find whether a data record is stored for the business partner group.
Activities
Enter and save your access sequences.
Warning!
Make sure you call up the "Access Sequence: Access" screen for each assigned condition table. If you do not call up this screen, the access sequence definition is incomplete and this may lead to errors when the flexible procedures are executed.
Note
You can only assign the access sequences to condition types and create condition records for the condition types once you have saved your access sequence.
Even if the condition record determination clearly depends on only one condition you still have to define an access sequence. You do not have to define access sequences for base condition types.
You can use the same access sequence for several condition types.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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_CFJB08JB48 | 0 | I070004701 | Profitability Analysis |
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 | C - View cluster | JB48 | IS-B | Access Sequences |
History
| Last changed by/on | SAP | 19990830 |
| SAP Release Created in |
