2006 Dec 27 3:57 PM
Hi All,
Please tell me how the following command works and how can we see the contents which are being returned from this memory Id.
IMPORT /ICO/MO_RUP-BERNR TO WLV_BERNR FROM MEMORY ID 'ZOR'.
Also,
GET PARAMETER ID 'ZOR' FIELD WLV_BERNR.
Thanks,
Archana.
2006 Dec 27 4:05 PM
Hi All,
Please tell me how the following command works and how can we see the contents which are being returned from this memory Id.
IMPORT /ICO/MO_RUP-BERNR TO WLV_BERNR FROM MEMORY ID 'ZOR'.
Also,
GET PARAMETER ID 'ZOR' FIELD WLV_BERNR.
Thanks,
Archana.
2006 Dec 27 4:00 PM
In both teh cases the variable WLV_BERNR willhold thevalue imported..
just use write: / WLV_BERNR .
~Suresh
2006 Dec 27 4:06 PM
I know the variable WLV_BERNR will hold the value, and also this is being used in a User Exit so cannot use the write statement.
I can manage to see the value being imported in the variable while debugging but I want to see the value which is in the memory id and if the value which is there is the correct one which is to be imported.
Can you help on that.
Thanks,
Archana.
2006 Dec 27 4:09 PM
>>I can manage to see the value being imported in the variable while debugging but I want to see the value which is in the memory id and if the value which is there is the correct one which is to be imported.
You cannot get into the memory id.. the only way is to IMPORT from it.. just clear the variable before you IMPORT.. & whatever value it holds after the IMPORT is what is in the memory..
~Suresh
2006 Dec 27 4:12 PM
2006 Dec 27 4:20 PM
Ok Thanks guys this gives me some hint...
Thanks again...
Archana.
2006 Dec 27 4:05 PM
2006 Dec 27 4:30 PM
1 .check what is the screen field for parameter id ZOR in that transaction, say VBAP-VBELN
2.so when debugging the user-exit or transaction check the value of the that screen field , that value will be stored
2006 Dec 27 5:35 PM
Hi Archana,
If you want to see what you're importing, if it's correct, you can start debugging in the start os the transaction and create a breakpoint related to the command EXPORT. Then you probably can see if the content exported to memory it's correct.
If you use this solution, don't stop debugging at the 1st EXPORT command, because it can be repeated before you import it.
I hope it helps.
Regards,
Paulo Sousa
| User | Count |
|---|---|
| 6 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |