Maintaining Assignment Details 
Use
Maintenance of assignment details is an expert function. Previous to BW 3.0A, a BAdl or user exit was available for these types of assignments. This is now obsolete and only still exists for reasons of compatibility.
In general you should be able to implement the BBS by creating the sender-receiver assignment only, without adding more assignment details.
In specific cases, it may however be necessary to maintain these assignment details, for example
· If you do not want to transfer specific selections, for example various dates
· If an assignment is not clear, for example, the buyer should be assigned to the supplier.
The system does not check the assignment details you maintained to see whether they are meaningful.
Prerequisites
You have created a sender-receiver assignment.
Procedure
...
1. Highlight 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 desired settings using input help. You can specify the processing method (Type) for the selection of characteristics and the permissible Selection Type, as well as designating the field as a Required Entry Field.
The following possible entries are available:
Processing method (Type) |
Effect |
generic (default) |
Selections are automatically transferred to the jump target by the report-report interface. We recommend to first execute the jump with this setting and to only make the other settings when the jump does display the desired result. Because only then is the full functionality of the BBS available to you. |
V Variable |
Selections are transferred directly to the specified variables. The technical name of the variable has to be entered into the Field Name column. The Data Element, Domain and Parameter-ID columns are automatically filled using the characteristics of the variables. This processing method is only applicable to BEx queries. It is useful when an assignment is not unique and if a certain characteristic is to be explicitly transferred. The characteristics assigned in this way have to have the same (non-compounded) key. For example, the characteristics 0MATERIAL and 0MATPLANT can be assigned to one another. |
I InfoObject |
Selections are transferred directly to the specified characteristic. The technical name of the characteristic has to be entered into the Field Name column. The Data Element, Domain and Parameter ID columns are automatically filled using the characteristics of the variables. This processing method is only applicable to BEx queries. It is useful when an assignment is not unique and if a certain characteristic is to be explicitly transferred. The characteristics assigned in this way have to have the same (non-compounded) key. For example, the characteristics 0MATERIAL and 0MATPLANT can be assigned to one another. |
3 Table field |
Selections are transferred directly to the specified field. This setting is only useful for non-BW jump targets. The Field Name, Data Element, and Domain must be filled correctly. Beyond that it is advisable to fill the Parameter ID column with the correct parameter ID. You can normally find the parameter ID in the ABAP Dictionary under data elements. On this, see Creating transactions as Receivers. |
P URL parameters |
This setting is only useful for the Web Address jump target. Specifying a field name is then mandatory. On this, see Creating Web Addresses as Receivers. |
Delete X |
All selections for this characteristic are then deleted and are not transferred to the jump target. This setting is useful if you do not want to transfer specific selections. For example, you may not want to transfer selections on one characteristic to another characteristic that has the same reference characteristic. |
The selection of a selection type makes sense if the jump target is a longer-running query or transaction. By selection a selection type in connection with the Mandatory 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 unnecessarily overloading the system. Before the jump, the system checks whether the selection that is marked as a mandatory entry exists in the jump target, otherwise the jump is not executed.
For example, for a jump to an R/3 system, you can mark the InfoObject Material with selection type P Parameter in transaction MM03 as a mandatory entry. The jump is only executed if the InfoObject Material is found in the R/3 system.
Permissible Selection Type |
Effects |
* (default) |
No restriction of the type of selection. Single values, intervals, free selection options and hierarchy nodes can all be transferred. |
P Parameters |
Only a single value is permissible in the report-report interface. |
E Individual values |
A list of values is permissible in the report-report interface. |
I Interval |
Only a single interval is permissible in the report-report interface. |
S Selection option |
Single values, intervals, and free selection options (for example >, <, <>, ...) can be chosen. Hierarchy nodes are broken down into lists of single values. |
H Hierarchy nodes |
Only hierarchy nodes are permitted. |
When the system calls up the receiver, 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 defined are saved and are considered when the jump target is called.