BDC
BDC
BDC
goto sm35
select the option background process
Recording Function
With recording, user can avoid manual search for fields and
tables required in a program including screen numbers.
SHDB is the transaction code.
Use: After developing any object we should write a test case proving that the
object is working properly or not. This is done by the ABAPer. This is UNIT
TEST CASE.
When you do your recording you will have a tab for Next line or Insert. You have
to capture that in your recording. If your transaction code doesn't have that in the
recording then you have to set up a page down (=P+) and loop it based on the line
entries u c on teh screen.
Suppose we are transfer data through BDC from leagacy to SAP and their is
some duplicate data in legacy system but we don't want this in SAP system .So
how can we check that this data is already exist?
In BDC you would have all your legacy data in an internal table. Use Delete
Adjacent dulpicates syntax to delete duplicate entries.
Can we use two transaction code in one BDC like XK01 & XD01 if yes how?
Yes, we can do that by combining the two bdc program codes together. Then you
perform the program routine accordingly. However, it will make your BDC
program very long and complex.
Can we use Session method & Call transaction both in one BDC if yes please
give me example and scenerio where we use this?
You start your dataload using Call Transaction and if any errors occur push all
those errors in a session so that your dataload takes place uninterrupted and you
can processs ur errors later.