Maintaining Assignment Details
Use
The maintenance of assignment details is an expert function. Before BW 3.0A, a BAdI or user exit was available for this type of assignment. This is now obsolete and only exists for reasons of compatibility.
In general, you should be able to use the RRI to create the sender-receiver assignment, without having to specify any other assignment details.
In certain cases, however, it may be necessary to maintain these assignment details:
● If you do not want to transfer certain selections, for example if you have differing date information.
● If an assignment is not clear, for example, if the vendor needs to be assigned to the purchaser.
The system does not check the feasibility of the assignment details that you maintained.
Prerequisites
You have created a sender-receiver assignment.
Procedure
...
1. Select your sender-receiver assignment in the Receiver table.
2.
Choose 
Assignment Details. The Field Assignments dialog box appears.
3. If you want to make changes to the individual fields, choose the required settings using the input help. You can assign the processing method (type) of selections for characteristics and the permitted Selection Type, as well as mark the field as Required Entry Field.
You can choose between the following input options:
Processing Method (Type) |
Effects |
Generic (default) |
Selections are automatically transferred from the Report-Report Interface to the jump target. We recommend that you execute the jump with this setting first and that you only change the settings if the jump does not display the required result. Only then is the full functionality of the RRI available. Here is a description of the rules used to transfer the selections: |
V Variable |
Selections are transferred directly to the specified variables. In the Field Name column, you have to enter the technical name of the variables. The Data Element, Domain and Parameter ID columns are automatically filled using the properties of the variables. This processing method is only applicable for BEx queries. This is recommended if you want to fill a variable in the receiver query and the variable has no technical connection to the InfoObject of the sender query. |
I InfoObject |
Selections are transferred directly to the specified characteristic. In the Field Name column, you have to enter the technical name of the characteristic. The Data Element, Domain and Parameter ID columns are automatically filled using the properties of the characteristic. This processing method is only applicable for BEx queries. This method is useful if an assignment is not unique and if a specific characteristic is to be transferred. The characteristics assigned to each another must have the same (non-compounded) key. For example, the characteristics 0MATERIAL and 0MATPLANT can be assigned to each another. |
3 Table field |
Selections are transferred directly to the specified field. This setting is only useful for non-BI jump targets. The setting is designed to enable jumps into other applications and fills the selection fields of programs or transactions. The Field Name, Data Element and Domain columns have to be filled correctly. It is also advisable to fill the column Parameter ID with the correct parameter ID. You can usually find the parameter ID in the ABAP dictionary entry for the data element. More information: Creating a Transaction as a Receiver |
P URL parameters |
This setting is only useful for the Web Address jump target. It is therefore mandatory to specify a field name. More information: Creating a Web Address as a Receiver |
Delete X |
All selections for this characteristic are deleted and not transferred to the jump target. This setting is useful when you do not want to transfer certain selections. For example, you may not want selections for a characteristic to be transferred to a characteristic that has the same reference characteristic. |
When using these explicit rules, make sure that the assignment is already set in the sender system. If you jump to another system, note that the sending and receiving InfoObjects of the assignment must exist in the sender system. Otherwise the jump will not work.
Choosing a selection type is worthwhile if the jump target is a longer-running query or transaction. When you choose a selection type with the Required Entry indicator, during the jump you can prevent a called report from starting if it does not fulfill certain conditions. In this way, you avoid putting unnecessary load on the system. Before the jump, the system checks whether the selection that is marked as a required entry exists in the jump target. If this is not the case, the jump is not executed.
For example, for a jump to an ERP system in the transaction MM03, you can mark the InfoObject Characteristic with selection type P Parameter as a required entry field. The jump is only executed if the InfoObject Material is found in the ERP system.
Permitted Selection Type |
Effects |
* (default) |
No restriction for selection type. Single values, intervals, user-defined selection options and hierarchy nodes can be transferred. |
P Parameters |
In the report-report interface, only one single value is permitted. |
E Single values |
In the report-report interface, a list of values is permitted. |
I Interval |
In the report-report interface, only one single interval is permitted. |
S Selection option |
You can choose single values, intervals and user-defined selection options (such as >, <, <>, …). Hierarchy nodes are expanded as lists of single values. |
H Hierarchy nodes |
Only hierarchy nodes are permitted. |
When the system calls the recipient, the settings made in the Field Assignments dialog box are set. The system proposes all other field assignments generically.
4. Choose Close. The assignment details you have defined are saved and are applied when the jump target is called.