JUMP (RSBBS) from a query on a transaction(local)

Question

Hi,
Can You help me ?
I want to do a jump from a query on a transaction RSDMD (on local system).But particullary, I want to put in parameter the data  (doc number) with wich I jumped.
So How I have to define the assignement detail in RSBBS for the transaction RSDMD?
Because, for the moment I have a popup where I must fill the name of my charactéristic and after the number of my doc number (for example), and it's with the doc number that I do my jump.
But, I don't want to fill characteristic and doc number, I want that it's automaticaly...
Thank you for your help...
Carine.

Answer 1

Calling the RRI with a transaction or an ABAP/4 Report as the receiver is done with the RRI
from the SAP NetWeaver Application Server. This is possible in an ERP system, a CRM
system or within the BI system. The selections are prepared by the BI system that does not
recognize the transaction or the report. The assignment is transferred from the RRI of the
SAP NetWeaver Application Server using inverse transformation rules. There must also be a
complete chain from the DataSource of the source system to the InfoSource, through
transformations up to the InfoProvider. This does not mean that data absolutely has to be
loaded using this chain. If this chain does not exist, the RRI cannot transfer the selections to
the source system. Calling the RRI only works for fields with dictionary reference. For ABAP reports, this means that the parameter has to be PARAMETERS param LIKE <table_field>
For transactions, this means that the Dynpro has to have a dictionary reference. Not every
transaction can be called with the RRI of the SAP Application Server.
These are the steps to do this
If you want to jump from a Web application to a transaction or ABAP/4 report using the
RRI, an ITS for the target system has to be assigned beforehand.
● The value of the input field to be supplied must be known at the time of the jump (for
example by entering a single value on the selection screen of the sender or by the
cursor position at the time of the jump).
● Sender and receiver fields that correspond to one another generally must link to the
same data element or at least to the same domain, otherwise the values cannot be
assigned to one another.
● The assignment of sender and receiver fields must always be a 1:1 assignment. For
example, the transactions called from the start screen cannot have two input fields of
the same data type. Then it is not clear which of the fields is to be supplied, which
means neither of them is supplied.
● There has to be a complete chain from the DataSource of the source system to the
InfoSource, through update rules up to the target.
Proceed as follows after you have created the sender-receiver assignment as described
above.
1. As the type, choose Table Field. The columns Field Name, Data Element, Domain and
Set-/Get Parameter become input ready.
2.  Specify the field name, data element, domain and parameter ID for the receiver
transaction. You need to know this information because input help is not available. You
can usually find the parameter ID in the ABAP dictionary entry for the data element.
If this does not always make jumping to the transaction possible, it may be necessary to
program a short ABAP start program. For more information on how to do this, see SAP Note
number 383077