cancel
Showing results for 
Search instead for 
Did you mean: 

Displaying UDM_BP on clicking of an ALV column

Former Member
0 Kudos

Hi All,

My requirement is to create a Z transaction for FDM_COLL01 and on clicking of some columns we need to display UDM_SUPERVISOR/ UDM_BP transaction.

Now for UDM_SUPERVISOR we have class CL_FDM_COLL_CONTROLLER=>DISPLAY_P2P_OVERVIEW/ DISPLAY_INV_OVERVIEW etc.
But for UDM_BP i am unable to find any class. What i can think of is a BDC recording and then calling FM 'CALL_TRANSACTION'.

Let me know if any one of you have better approach.

Thanks & Regards,

Durgesh

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi,

The original requirement is like that only as we are displaying a lot of information on screen after executing transaction FDM_COLL01. Let me know if you have any suggestion even if transaction is a Z program.

Thanks & Regards,

Durgesh

Former Member
0 Kudos

First of all, you should not discount the advise given above by Mark. Many times re-evaluating the requirement is the correct approach rather than spending a lot of time and effort on custom solutions that will not work on the long-run.

As for your requirement, see my comment above. Since you want to enhance an ALV list, there must be a form that handles user commands. Find this form and then insert a START or an END implicit enhancement to implement whatever functionality you like.

Former Member
0 Kudos

As pointed out, you should not create a Z program and instead look into using BAdI's. Another approach that can help is to use implicit enhancement spots. Find the form that handles clicking the different table cells and insert an implicit enhancement spot at the beginning or at the end. However, please be careful not to break standard functionality and not to insert commit statements that could break the flow of the different logical unit of work.

Former Member
0 Kudos

Wow - I would not advise making a z version of the screen or program. You can use BAdI's to influence the screen layout and calculations.

The process receivables screen is a complex one that calls different transactions and makes different saves to tables, I would suggest reviewing your design to see if these changes are necessary.

Former Member
0 Kudos

NOTE: Here the problem is that we cannot use SKIP FIRST SCREEN as we need to display different screens for different transactions.