topic Re: Difference in the screen for the same Tcode in Application Development and Automation Discussions

Difference in the screen for the same Tcode

former_member488128 — Tue, 19 May 2015 07:23:40 GMT

Hi,

When I go to T code F-30, I could see lesser input fields when compared to what I can see from a BDC call transaction

and use a display mode (A). I guess this relates to parameter IDs and get, set. But is there a way I could see the same

set of fields I see while using BDC, when I run F-30 independently.

Thanks,

Abdul Samad

Re: Difference in the screen for the same Tcode

RaymondGiuseppi — Tue, 19 May 2015 07:34:42 GMT

Many transactions (as FB05 which is the transaction hidden behind F-30) check value of some system fields and adapt dynpro.

sy-binpt - batch input execution
sy-calld - CALL TRANSACTION"
sy-batch - in background job

Regards,

Raymond

Re: Difference in the screen for the same Tcode

former_member488128 — Wed, 20 May 2015 02:56:07 GMT

Thanks Raymond, that was helpful.

However, is there a way to see what we see in BDC when we run the tcode independently or is it not possible?.

Re: Difference in the screen for the same Tcode

Former Member — Wed, 20 May 2015 05:12:11 GMT

Hi Abdul,

have you tried tcode SHDB (Transaction Recorder) ? Maybe this will be helpful.

But not only Batch-Input mode may have influence on the fields you can see. Also some other input values like the Document Type (BKPF-BLART) may cause fields to be available or hidden.

To see all fields please call tcode SE51.

Regards,

Klaus

Re: Difference in the screen for the same Tcode

Former Member — Wed, 20 May 2015 05:17:56 GMT

Try to use BAPI for those posting ....BDC field may change

Re: Difference in the screen for the same Tcode

RaymondGiuseppi — Wed, 20 May 2015 06:03:50 GMT

Most of those fields (as the original document link) were provided to be used by calling applications and not in pure FI document.

Tricks: To "trick" the system, try with some SPA.GPA parameters as' FOP' and 'FO2' (structures RFOPT and RFOPT) or setting sy-calld thru use of SUBMIT AND RETURN statement in some two level wrapper program as well as some CALL TRANSACTION with correct OPTIONS FROM (e.g. dismode = 'D')

But why would you require those/which fields?

Regards,

Raymond