BDC on Selection Screen report

[Former Member]

Hi Experts,

Is there any norm of NOT using BDC for selection screen reports? Please share your experience if someone had used it and faced issues later.

Thanks,

Chirantan

[naresh_bammidi]

Hi Chirantan,

I could not get your question correctly.

1. Do you want to use BDC code in report? If yes

    Yes you can use.

2. Do you want capture selection screen in BDC recording?

    No,Not possible.Recording is only possible with module pool screens not for selection screen.

Thanks

Naresh Bammidi

[Former Member]

Hi Naresh,

My question is if one should use BDC to run a Selection Screen report.

Also, I would disagree with you on the point that BDC is not possible for a selection screen report - by default we have screen 1000 created for a report; this integration between normal reports and module pool enables creation of BDC.

Thanks,

Chirantan

[Former Member]

hi,

can you repeat your query one's more time in brief .

[Former Member]

Hi Puneet,

To be brief my question is "Should we use BDC for Selection Screen Report". If so then in which cases should we avoid it.

Thanks,

Chirantan

[VijayaKrishnaG]

Hi,

Actually your query is little bit confusing. What do you mean by 'Selection Screen Report' in your query?

Regards,

Vijay

[Former Member]

Hi Vijay,

By that I mean a report with Parameters and Select-Options.

Thanks,

Chirantan

[VijayaKrishnaG]

Hi,

I did not understand what exactly are you expecting from this. Whether do you want to write a BDC with out selection screen like with no option to browse the flat file and make the path hard code or what?

Vijay

[ThomasZloch]

You can see how confusing your question is, as there is no direct dependency between these two technical topics.

Why don't you tell us what you actually want to do, or why you need to know this.

If you expect meaningful help (I guess you do), then provide as much relevant information as possible.

Thomas

[yogendra_bhaskar]

Hi Chirantan ,

I would advice you to use submit report option instead of BDC.

First capture your selection screen parameters into a selection_table and fill it with suitable data .

Use submit report and there you go......... report is executed.

ALL FUNCTION 'RS_REFRESH_FROM_SELECTOPTIONS'

            EXPORTING

              CURR_REPORT               = 'ZREPORT'

*         IMPORTING

*           SP                        =

            TABLES

              SELECTION_TABLE           = LT_SELSCREEN

*           SELECTION_TABLE_255       =

*         EXCEPTIONS

*           NOT_FOUND                 = 1

*           NO_REPORT                 = 2

*           OTHERS                    = 3

                    .

          IF SY-SUBRC <> 0.

* Implement suitable error handling here

          ENDIF.

* Fill LT_SELSCREEN

          LOOP AT LT_SELSCREEN INTO LW_SELSCREEN.

            CASE LW_SELSCREEN-SELNAME.

*           

*           WHEN OTHERS.

            ENDCASE.

          ENDLOOP.

            SUBMIT ZREPORT

                  USING SELECTION-SCREEN 1000

            WITH SELECTION-TABLE LT_SELSCREEN

            AND RETURN .

Regards ,

Yogendra Bhaskar

[Former Member]

Hi Yogendra,

One of my friends also suggested to do the same;although he isn't sure of the reason behind it. Can you shed some light on why BDC isn't a preferred choice.

Thanks,

Chirantan

[matt]

Simply it's the wrong tool and requires more complicated coding. Yes, I can use sandwich toaster to heat my porridge, but it's far better to use a pan on the stove.

Using submit you can get whatever was written the screen back and do something with it.

However, if you're need to run a report in this way that you wrote, you'd be better off creating a BAPI-like function module to do the work, and use that in the report as well.

If I saw one of my developers do this, they'd get a virtual clip around the ear and told to do it properly.

[Former Member]

1. If we have direct way of calling reports, transactions then its always prefdered to use CALL transaction, SUBMIT report statement.

2. During the upgrade or patches run by Basis, then screen no. field name might change which will fail ur BDC if we have done it based on previous tp upgrade.

3. Second point is - from coding prospective, wirting BDC is ltille time consuimg than jusr writing SUBMIT REPORT statement.

4. Also in terms memory usage, it is advisable to use SUBMIT report than BDC.

[Former Member]

I am glad I am not a developer with you

The moto behind this question was just to understand if there was any technical constraint which limits BDC. I was told by one my friends that BDC is only to be used for module pool; which I found strange since screen 1000 is created for reports as well and that should do the job.

[matt]

After a few virtual clips around the ear though, you'd be a decent programmer.