Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
in the debugging mode..after filling the data check the internal table ...
Because if you have declared inside a subroutine and if you have check the internal table value after the subroutine is executed..Then cannot see the internal table..
While generating the Transfer rules, BW automatically generates a program by its own including your routines. While kicking off the infopackage, it is calling the respective transfer rule program to process the data. Since it is called in different manner, it won't break at break points. For that purpose only, BW has standard break points and it can be activated after the loading got failed to dig the issue.
In RSMO, make the request as RED and delete the request from Target. Go to Details Tab, keep your cursor on any data package and right click to see 'Simulate Update' option. It will give a window where you can check to activate the transfer rules debugging. Then it will show to select the data package from PSA. Select minimum amount of records (two or three) records and start processing. It will stop the processing once it is reached just before your routines.
If the control is in the same Start routine..yes you will see the contents... if you are out of that routine...you will notbe able to see the contents...
If you want to access internal table data everywhere in the flow/prg...declare the internal table in Global declarations.
Bluesky
