A standard report is using logical database ADA. I have requirement to enable fields from table ANLB into dynamic selection criteria. I found out, that ADA already has the needed fields in the Selections View part of of ADA (in SE36). But they are assigned to functional group node number 85 Depreciation terms. I could manage this with custom Selections View 'CUS' and assign the needed fields to other functional group node 40 Assignments or 67 Net worth valuation. But the problem is not the wrong function group, but the fact, that whenever using the standard report, and starting the dynamic selections function, the system will remove all tables (defined in LDB ADA selections view) other than ANLAV from the dynamic selection screen tree. Thus for example no ANLB fields appear in the tree in the dynamical selection.
I have debugged the standard program RSDBSPDS (called from the main program, when program gets first started) and in FORM DYNS_INIT it reads all dynpro fields from the selection screen that have attribute KIND having value 'D' and takes the table name there, which is ANLAV and passes to fm RS_DS_INT_INIT_LDB, which then filters away all the tables other than ANLAV from the selections view definitions of ADA (which holds ANLZ, ANLB,...) and this is the reason why dynamic selection tree only shows nodes that contain fields from ANLAV only. In ADA definition, the ANLB fields are all put to functional group 85 and therefore when dynamic selection tree does not show such tree node 'Depreciation terms' at all at runtime.
Question1: why ADA has definition with assigning fields from ANLB to 85 group, when the whole group does not even gets shown in the dynamic selection screen at all? Is it because there are various other reports using ADA, and some of them would allow use of other tables than just ANLAV?
Question2: To be able to see ANLB fields in dynamic selection tree, I need to add the needed fields from ANLB to structure ANLAV using an append structure? Am I correct? I got this thought when reading this article https://archive.sap.com/discussions/thread/1632678 but ANLB itself is still in the ADA definition having the same fields. Is there any issue that same fields exists twice in LDB but in different structures?
Question3: after doing tasks mentioned in question2, are selections automatically working when report it executed? I mean, filtering ANLB records with given dynamic selections is effective at runtime (GET ANLB) without any further custom development on the report itself?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.