Search Help hierarchy

Hi,
If for a field in a table I have the following search helps implemented:
References are as under
Ztab ->- Zfield --> ZdataE --> ZDomain
1. Search help at field level in table (Zfield)
2. Search help at data element (ZdataE)
3. Value Range in Domain (ZDomain)
4. This Z Field is used in a report which has another at-selection-screen on value request for the field referring to ZField.
Now when I press F4 on the selection screen of ZREPORT --? what would be displayed when I do F4 on the field referring to ZFIELD. And what would be the levels in which the options from above be used for F4.
Thanks-
HS.

Hi J@y,
Sorry Iam still didn't understood after I read in the direction where you given me, can you give me the coding regarding about my case ? I confused now. sorry I am stupid about this case since Iam the first time build the search help exit like that.
I did the one exp about my case. the thing is I cannot pass the value of the industry code 1 to my function module. and also don't know how to return the value out of the field screen. Thank you
Best Regards,
Kohokoho
Edited by: kohokoho on Aug 10, 2009 3:50 AM

Similar Messages

Field values are repeating for search help.

Hello Friends.
I have a problem. When I create a search help for a field the identical field values are repeating. What should I do to trigger only the first time.
for example:
<u>Field-name</u>-                        <u>field-value</u>
Supplier Nr ---                                 Commodity
5001 -
                                           casting
5002 -
                                           casting
5003 -
                                           casting
So when I create the search help for commodity it is showing 'casting' 3 times in a pop-up window. It should not repeat. Can you please give me the solution what should I do?

Hi
Search helps
Standard search help
Types of search helps
Concept of search help
Search Help Interface
Dialog behavior of search helps
Selection method for search helps
Performance of search helps
Attaching search helps
Hierarchy of search helps
Standard Search Help
The input help (F4 help) is a standard function of the R/3 System. It permits the user to display a list of possible values for a screen field. A value can be directly copied to an input field by list selection.
The fields having an input help are shown in the R/3 System by the input help key to the right of the field. This key appears as soon as the cursor is positioned on the corresponding screen field. The help can be started either by clicking on this screen element or with function key F4.
If the number of possible entries for a field is very large, you can limit the set of displayed values by entering further restrictions.
Further meaningful information about the displayed values is included in the display of possible entries, especially if the field requires that a formal key be entered.
TYPES OF SEARCH HELPS
Elementary search helps
Describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
Collective search help
Combine several elementary search helps. A collective search help thus can offer several alternative search paths.
Search Help Interface
Search help interface determines how the exchange of values between the screen template and the selection method is implemented.
The search help interface defines the context data that can be used in the input help and the data that can be returned to the input mask. Analogously to the interface of a function module, the search help interface comprises interface parameters.
When you define an interface parameter of a search help, you must also define whether it should be used to copy data to the input help (IMPORT parameter) or whether it should be used to return data from the input help (EXPORT parameter). A parameter of a search help can also have both attributes at the same time.
The location from which the IMPORT parameters of a search help get their values and the screen fields in which the contents of the EXPORT parameters of the search help are returned are defined in the search help attachment. The search help itself should always be attached to an EXPORT parameter of the search help. If this parameter is also the IMPORT parameter, its contents are only used in the input help if it is a search string (that is, if it contains a ´*´ or a ´+´).
You must define the parameter types of a search help. You can do this by assigning them data elements.
Value Transport for Input Helps
NOTE:In the above example, screen fields A, B and C are linked with parameters of the search help. As a result, values can only be transported between the screen and the search help for these three fields. Existing contents of screen fields A and B can be used for selecting the hit list since they are linked with an import parameter of the search help. The values of parameters A and C can be returned to the screen from the hit list since these parameters are declared as export parameters of the search help.
Description of dialog behavior
A hit list might contain plentiful number of entries. A
dialog provides the user with an option to restrict the
entries displayed on the hit list.
In an input help process, the set of possible entries is presented in the dialog box as a list for displaying the hit list. The user selects the required value from this list by double clicking. Since the possible entries are often formal keys, you must be able to display further explanatory information about the possible entries in the list.
If the set of possible entries is very large, the user should be able to define additional conditions for the attributes of the selected entry. Restricting the set of data in this way both increases the clarity of the list and reduces the system load. Additional conditions can be entered in a further dialog window, the dialog box for restricting values.
Specifying the dialog type of a search help defines whether the dialog box for restricting values should be offered and if so under what conditions.
The attributes in the dialog box for displaying the hit list or in the dialog box for restricting values must be defined as internal parameters of the search help. An internal parameter can also be used in only one of the two dialog boxes. It can also belong to the search help interface.
The internal parameter types are also defined with data elements. These data elements define how the parameters are displayed in the two dialog boxes.
Reward if usefull

Hi, tell me abt creation of search helps in detail

hi, tell me abt creation of search helps in detail

Hi
Search helps
Standard search help
Types of search helps
Concept of search help
Search Help Interface
Dialog behavior of search helps
Selection method for search helps
Performance of search helps
Attaching search helps
Hierarchy of search helps
Standard Search Help
The input help (F4 help) is a standard function of the R/3 System. It permits the user to display a list of possible values for a screen field. A value can be directly copied to an input field by list selection.
The fields having an input help are shown in the R/3 System by the input help key to the right of the field. This key appears as soon as the cursor is positioned on the corresponding screen field. The help can be started either by clicking on this screen element or with function key F4.
If the number of possible entries for a field is very large, you can limit the set of displayed values by entering further restrictions.
Further meaningful information about the displayed values is included in the display of possible entries, especially if the field requires that a formal key be entered.
TYPES OF SEARCH HELPS
Elementary search helps
Describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
Collective search help
Combine several elementary search helps. A collective search help thus can offer several alternative search paths.
Context data: You first have to define the context data to be used in the input help process. The context contains the information obtained in previous dialog steps and the entries already made by the user in the current input mask. This information is normally used to restrict the possible values for the current input field.
Dialog behavior: It describes the order of the dialog windows to be displayed during the input help and what they should look like.
Data collection method: It defines where the values offered to the user for selection come from.
Return values: When a value is selected from the list of possible entries, it is stored in the search field. This often results in the contents of further screen fields, such as explanatory text, being updated. You therefore should define which values can be returned to the screen.
In addition to describing an input help, you must define the fields for which it should be used. This is part of the field definition (of the search fields).
In Release 4.0, the search help was introduced in the ABAP Dictionary as a new object type. A search help is an object that describes the input help process. The individual components of such a description can be defined with attributes of the search help.
Search helps are subject to the same rules concerning their maintenance, activation and transport as all other objects of the ABAP Dictionary.
Search helps provide greater flexibility and functionality for defining input helps than the matchcode and help view object types offered up to Release 3.x.
Search Help Interface
Search help interface determines how the exchange of values between the screen template and the selection method is implemented.
The search help interface defines the context data that can be used in the input help and the data that can be returned to the input mask. Analogously to the interface of a function module, the search help interface comprises interface parameters.
When you define an interface parameter of a search help, you must also define whether it should be used to copy data to the input help (IMPORT parameter) or whether it should be used to return data from the input help (EXPORT parameter). A parameter of a search help can also have both attributes at the same time.
The location from which the IMPORT parameters of a search help get their values and the screen fields in which the contents of the EXPORT parameters of the search help are returned are defined in the search help attachment. The search help itself should always be attached to an EXPORT parameter of the search help. If this parameter is also the IMPORT parameter, its contents are only used in the input help if it is a search string (that is, if it contains a ´*´ or a ´+´).
You must define the parameter types of a search help. You can do this by assigning them data elements.
Value Transport for Input Helps
NOTE:In the above example, screen fields A, B and C are linked with parameters of the search help. As a result, values can only be transported between the screen and the search help for these three fields. Existing contents of screen fields A and B can be used for selecting the hit list since they are linked with an import parameter of the search help. The values of parameters A and C can be returned to the screen from the hit list since these parameters are declared as export parameters of the search help.
creation of Elementary Search Help
Enter the search help name and click on create.
Choose elementary search help radio button option as the search help type.
Enter the search help parameters, the selection method and activate the search help.
Collective Search Help steps
Enter the search help name and click on create.
Choose Collective search help radio button option as the search help type.
Enter the search help parameters.
Note that there is no selection method to be entered for a collective search help.
Instead of the selection method, we enter the included
search helps for the collective search help.
We need to assign parameters for each of the included
search helps.
Complete the parameter assignment by clicking on the push button
Collective search help offers the user to obtain F4 help
using any of the included search helps.
Attaching a search help to a field
A search help can influence the behavior of a field when the input help is called. The search help must be assigned to the field in order to do this. You have the following options for this assignment:
Attach search help to a data element / table or structure field / screen field / check table.
Conventionally search helps are attached to table fields or data elements. We shall see the same.
Attaching a search help to a screen element
A search help can be directly assigned to a screen field in two ways.
The name of the search help must be entered in the Screen Painter in the Attributes for the field in the field Search help.
The name of the search help can be defined for selection screens in ABAP reports in the PARAMETERS or SELECT-OPTIONS statement directly following the supplement MATCHCODE OBJECT.
However, input help is only available for this particular screen.
In this case, the search help is only available for this screen.
OR by useing FM
refer this code
TYPES : BEGIN OF ST_OBJID_SH,
OTYPE TYPE HRP1000-OTYPE,
OBJID TYPE HRP1000-OBJID,
END OF ST_OBJID_SH.
DATA : IT_OBJID_SH TYPE STANDARD TABLE OF ST_OBJID_SH.
DATA : WA_OBJID_SH TYPE ST_OBJID_SH.
***********SELECTION SCREEN DESIGN***********************
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
*SELECT-OPTIONS : S_OTYPE FOR HRP1001-OTYPE NO INTERVALS .
SELECT-OPTIONS : S_OBJID FOR HRP1001-OBJID NO INTERVALS .
SELECT-OPTIONS : DATE FOR SY-DATUM NO-EXTENSION OBLIGATORY.
SELECTION-SCREEN END OF BLOCK B1.
**********END OF SELECTION SCREEN DESIGN*****************
*********VALIDATION FOR SCREEN FIELDS********************
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_OBJID-LOW.
IF S_OBJID IS NOT INITIAL.
SELECT OTYPE OBJID FROM HRP1000
INTO TABLE IT_OBJID_SH
WHERE OTYPE = 'D'.
IF SY-SUBRC EQ 0.
SEARCH HELP FOR QUALIFICATION.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
DDIC_STRUCTURE = ' '
RETFIELD = 'OBJID'
PVALKEY = ' '
DYNPPROG = SY-REPID
DYNPNR = SY-DYNNR
DYNPROFIELD = 'S_OBJID'
STEPL = 0
WINDOW_TITLE =
VALUE = ' '
VALUE_ORG = 'S'
MULTIPLE_CHOICE = ' '
DISPLAY = ' '
CALLBACK_PROGRAM = ' '
CALLBACK_FORM = ' '
MARK_TAB =
IMPORTING
USER_RESET =
TABLES
VALUE_TAB = IT_OBJID_SH
FIELD_TAB =
RETURN_TAB = RETURN_TAB
DYNPFLD_MAPPING =
EXCEPTIONS
PARAMETER_ERROR = 1
NO_VALUES_FOUND = 2
OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDIF.
Elementary search helps Describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
Collective search help Combine several elementary search helps. A collective search help thus can offer several alternative search paths.
steps
Elementary Search Help
1) Goto SE11
Enter the search help name and click on create.
2)Choose elementary search help radio button option as the search help type.
3)Enter the search help parameters, the selection method and activate the search help.
Collective Search Help
1)Enter the search help name and click on create.
2)Choose Collective search help radio button option as the search help type.
3)Enter the search help parameters.
Note that there is no selection method to be entered for a collective search help.
4)Instead of the selection method, we enter the included
search helps for the collective search help.
5)We need to assign parameters for each of the included
search helps.
6)Complete the parameter assignment by clicking on the push button
7)Collective search help offers the user to obtain F4 help
using any of the included search helps.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee2b446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee5f446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee86446011d189700000e8322d00/content.htm

Search Help for Hierarchy Node in SAP BW 7.3

Hi Experts,
We were previously using SAP BW 7.1 system and we had a table which used to be maintained through SM30 which has a customed search help on one of the fields for a hierarchy object. And it was working perfectly.
However, one of our systems have just been migrated into 7.3 version and the above functionality is no longer working.
This is what is happening now:
- User selects a hierarchy and after selection nothing is being displayed on field on the table.
We have tried to debug this customed search help in both environments to distinguish what is wrong. We have noted that a standard function module (RRSV_IOBJ_VALUE_OUTPUT) is not behaving similarly. In 7.1 system, the C_T_DATA table is being filled whereby in the 7.3 system, it is empty.
Do you think this is the issue?
Please do advise and propose what can be done to make it work. Or any idea on how to create a new search help for a hierarchy node in 7.3?
Thanks in advance.

hi,
one more thing i will like to add here is in BW 7.3 you get a new security admin feature that allows you to make mass changes to authorizations instead of one-by-one. This can be done by cut-and-paste in a worklist, hierarchy nodes, and you can also add users to multiple analysis authorizations.
The u2018newu2019 authorizations has both the data value and hierarchy restrictions. You can still build using the u201CRSECADMINu201D transaction
Also make sure that all objects are in the TLIBG library and they will be 'shielded' during the upgrade.
regards
laksh

How to display Hierarchy in WDA Search help

Hello Experts,
Please let me know if i can display hierarchy (tree like structure) in WD ABAP search help,i am quite new to WD ABAP.
Any suggestions and inputs would be very helpful.
Thanks & Regards,
Siddharth

I think tree UI element will be useful to you. Pls refer following links for more help:
[Link1|http://help.sap.com/saphelp_nw70/helpdata/en/21/ad884118aa1709e10000000a155106/content.htm]
[Link2|http://help.sap.com/saphelp_nw70/helpdata/en/59/a98b411fb4b05fe10000000a1550b0/frameset.htm]
[Link3|http://help.sap.com/saphelp_nw70/helpdata/en/5a/088b41b4b3b25fe10000000a1550b0/frameset.htm]
I had similar requirement of search help in my project. I had created component with tree ui element and called it using component usage in another component on click of button. I hope this will help you.
Regards,
Saket.

Transaction VB02 - Search help for product hierarchy

Hi Experts,
I have a requirement to add a search help for product hierarchy in transaction VB02. Has anybody done this before? I am not able to assign the program & screen to a Z package.
Thanks,
Vitz.

there are already search helps attached to it.. which fields exactly are you talking about?
try to find BADI for that screen

Search Help - Product Hierarchy

Hi all,
is there a specific Webdynpro searchhelp for Product hierarchy?
when i use the automatically selected one PRODH, i get dumps on the
browser, complaining there is no connection to the user.
thanks in advance,
Koen

Hello Koen,
Seems like the search help for PRODH uses call screen or some other dynpro statement inside. Probably, SAP already provided a fix to be applied to this search help so that it can be used within Web Dynpro ABAP. Might be worth opening an oss ticket towards the oss queue to which the package of the search help points to.
Best regards,
Thomas

Standard Search Help in Custom Search Help

I've created a Custom Search Help for Product Hierarchy. But when search help window appears, I want to put a standard search help of Product Hierarchy on Product Hierarchy field which is located on Resctricted section. Is that possible? Let me know if there's a way...
Thank you

hello ibnu,
it is not possible i attach a standard search help mara
no such feature available .

Custom Search Help for the field Equipment number

Hi,
I have enchanced sales order transaction and included a field Equipment number(EQUI-EQUNR).
Here after pressing F4(Search help) standard search help is display.
I have a requirement wherein, the standard search help should not appear and a customised search where a specific Equipment category type values should appear in the search help.
Ex. Field equipment category (EQTYP).EQUNR(Equipment Number).
Please let me know how to work for the customised search help.

Hi,
You need to create a customized search help.
[Elementary Search Help - Structure|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21ee38446011d189700000e8322d00/content.htm]
[Creating Elementary Search Helps|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21ee5f446011d189700000e8322d00/content.htm]
Then you need to attach the search help to the screen field..
[Assigning Search Helps to Screen Fields|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21ee93446011d189700000e8322d00/content.htm]
[Hierarchy of Search Help Call|http://help.sap.com/saphelp_nw04/helpdata/EN/0b/32e9b798da11d295b800a0c929b3c3/content.htm]
regards
Nitesh

Do we have search help facility in variable selection (F4 help).

Hi All,
At my client place users are comfort with R/3 search help (F4), and looking for the same feature in Bex Reporting. Is it possible to have the same kind of feature in Bex reports.
Example.
In R/3 T-Code MB5B, user searches with material description or with some other options like sales material by general product hierarchy. Can we get the same kind of feature.
And my client says that if we drop down for material it is taking huge amount of time to display the material numbers and description, we want to know how to reduce the time for displaying the material or customer master data text in variable selections.
In Bex we are aware of material text is going to display as small or medium or long descriptions, when we drop down.
Your suggestions are most valuable to us.
Thanks in Advance.
Akash

Goto se11
in data type : put KIDNO change mode   ... avoid the messges ....
there in theDefinition   : put your new Search Help   activate it ....
so that   it will be attached..
otherwise there so many ways of attaching the serach help   for F4 ..
Implementing search Helps
Search helps can be implemented in a variety of ways:
1 .Add to Table field Added via SE11: Place cursor on desired field within database and select menu path Goto->Search help->for field
Effect: If field used to create screen field, search help will be called when user executes F4/drop down input help. All fields on screen will be populated if appropriate fields exist in search help and screen.
2.Add to Table Added via SE11: Place cursor on desired field within database and select menu path Goto->Search help->for table
3.Add to Data element Added via SE11: Select desired data element (double click), enter search help name and parameters in appropriate fields on screen. Will be applied to all fields associated with that data element
4.Add to Screen field Added via screen painter: One of field attributes is search help. Will only populate the one screen field.
5.Add to Sel. screen parameter (MATCHCODE) Added using 'matchcode' addition for parameters declaration: Search help name must be no more than 5 characters long.
e.g. PARAMETER p_prog LIKE trdir-name MATCHCODE OBJECT zsh.
Rewatrd points if it is usefull ...
Girish

Calling a standard search help from MS Office

One of the companies I work for has integration with Microsoft Office so users can create SAP DMS (document management system for those who aren't familiar with it) entries directly from e.g. Microsoft Word. The integration solution is a custom .Net application.
In addition to the obvious integration to create the DMS info record and assign the document as an original the integration solution lets the user provide classification data. Some changes are now being planned, and one of them is challenging as a new characteristic (for the classification) will be used to store an organization unit. This is straightforward when the user is in the SAP GUI, as the standard search help can easily be displayed from custom code.
Being a technology optimist I was hoping that with the new fancy technologies SAP would have provided a way to use .NET integration to display a standard search help from the MS Office integration dialogue - but so far I have not been able to find any information supporting this hope. Luckily I am not the developer working with the integration dialogue, but unless the mentioned possibility exists it looks like we have to resort to passing all organization units to the interface so a hierarchy can be constructed and displayed to the user for selection.
Another alternative (I think) is to recreate the dialogue as a web dynpro screen, which will give us all the advantages of operating "inside" SAP. However, I am not sure if this is possible either. Can a web dynpro screen be called from an MS Office application (.Net), and can that web dynpro screen return values to the (external) calling application? In my simple view of the world this should be doable, if not otherwise it should at least be possibly by wrapping the screen in a function module that is exposed so the .Net application can call it - either by RFC or as a web service.
Microsoft Office version is 2003.
SAP release is ECC 6.0 (Netweaver 7.0).
I think this is the right forum for my question. My apologies if it isn't (and any guidance towards a more appropriate forum would then be appreciated).

Not solvable I suppose. There should be a way to close messages without marking them as answered.

VA01 and VA02 Search Help Mitigation

Hello Everyone,
I need to restric several search help results to users without authorization to see these values. All these search helps are in transactions VA01, VA02, and VA03. And that is my problem, since they are SAP Standard transactions I can't just modify the way these Search Helps are handle directly.
I did try looking for Search Help Exits or some other Enhancement point where I could place my code and manipulate the Search Helps Information, but I couldn't find something that could help me. If you could please let me know if you know a way to do this, the Search Helps are:
1. Restrict all the searches available in the account assignment tab at the header and item level of the sales order which allow access to view WBS information and projects. Search Help COBL_EX_PRPM.
2. Restrict the plant search that is within the engine model field at the header level of the sales order which that provide access to view the plants names and addresses. Search Help H_T001W_C.
3. Restrict all the sales group searches within the transaction. Search Help H_TVBVK.
4. Restrict all the sales office group searches within the transaction. Search Help H_TVKBZ.
5. Restrict all the product hierarchy searches within the transaction. I think the Search Help is PRODH.
Thanks in advance,
Carlos.
Edited by: SapFigue on Feb 10, 2010 7:06 PM

Please tell how did you do it. Because i have the same problem. I need to add extra field in the search help of the ORDER in SALES ORDER (VA01, VA02). I want to see both the ORDER and the DESCRIPTION in the search help of ORDER field.

F4 search help as tree structure in a module for one field

hi experts,
i have created a z module by copying standard module SAPMV23N of vbg1/2/3 transaction and i have added one tab in vbg1/2/3. the 5th tab is working. i am calling a subscreen using 5 tabstrip. there are one field MAKTL i want to use a F4 search as tree structure for that MAKTL field.
in code for displaying tree structure i am using function module RS_TREE***
please help me

Hi,
Please study this search help, there is a search help exit in which the hierarchy part it written,
Search Help: PRCTH
Search help exit: K_F4IF_SHLP_STANDARD_HIERARCHY
Hope this helps you,
Regards,
Abhijit G. Borkar

How to implement the search help exit to MM01 for Material by product hiera

Hi,
How to implement the search help exit to MM01 T-code for Material by product hierarchy,
but system default it gives the data from MVKE table, my client wants from MARA table,
i created the one Function Module, write this code in that FM.
IF CALLCONTROL-STEP EQ 'DISP'.
REFRESH RECORD_TAB.
SELECT * FROM MARA INTO TABLE RECORD_TAB
WHERE PRDHA =
ENDIF.
I Face the problem what variable i have to pass in WHERE CONDITION, FROM THE MM01 T-code.
is't require to IMPORT variable from MM01 program, what is that import variable, please give me the solution.
thanks to all.

Hi there..
check my web blog on search help exit...
[Search help exit code|https://wiki.sdn.sap.com/wiki/x/du0]

TREE NODE IN F4 SEARCH HELP

Hi All,
Can anyone help me to implement Tree node in F4 Search help?
Thanks
E Karthikeyan

SAP has provided a lot of sample programs for developing tree structures. Just go to SE38, type BCALVTREE and hit F4. You'll get different sample programs with a range of operations on trees
Go through the link,
http://www.sapdevelopment.co.uk/reporting/alv/alvtree.htm
Slowly check this code..you will get idea of how to develop tree structure.
REPORT y_hierarchies_in_tables
NO STANDARD PAGE HEADING.
PARAMETER: g_group TYPE grpname. " DEFAULT 'Z_GLAB0000'.
DATA:
g_setid TYPE setid,
g_class TYPE setclass.
DATA: lt_hier TYPE STANDARD TABLE OF sethier,
lt_val TYPE STANDARD TABLE OF setvalues.
DATA: hier LIKE sethier OCCURS 0 WITH HEADER LINE,
val LIKE setvalues OCCURS 0 WITH HEADER LINE,
setinfo LIKE setinfo OCCURS 0 WITH HEADER LINE.
DATA: zaccbas(20) TYPE c OCCURS 0 WITH HEADER LINE.
DATA: miss_val LIKE setvalues-from OCCURS 0 WITH HEADER LINE.
DATA: table_name TYPE tabname,
field_name TYPE setfld.
DATA: ambiguity_flag TYPE c.
Ambiguity check
PERFORM ambiguity_check.
Display Records
PERFORM display_records.
*& Form AMBIGUITY_CHECK
Ambiguity check
FORM ambiguity_check .
DATA: it_abaplist LIKE abaplist OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF it_ascilist OCCURS 0,
zeile(256) TYPE c,
END OF it_ascilist.
DATA: flag.
SUBMIT rgsovl00 "VIA SELECTION-SCREEN
WITH p_shrtn = g_group
WITH path = 'X'
EXPORTING LIST TO MEMORY
AND RETURN.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
listobject = it_abaplist
EXCEPTIONS
not_found = 1
OTHERS = 2.
CALL FUNCTION 'LIST_TO_ASCI'
TABLES
listasci = it_ascilist
listobject = it_abaplist
EXCEPTIONS
empty_list = 1
list_index_invalid = 2
OTHERS = 3 .
LOOP AT it_ascilist.
IF it_ascilist-zeile = text-001.
flag = 'X'.
ENDIF.
IF flag = 'X' AND
it_ascilist-zeile = text-002.
ambiguity_flag = 'X'.
CLEAR flag.
ENDIF.
ENDLOOP.
FREE MEMORY.
ENDFORM. " AMBIGUITY_CHECK
*& Form DISPLAY_RECORDS
Display the Records
FORM display_records .
PERFORM get_records.
PERFORM header_data.
PERFORM item_data.
ENDFORM. " DISPLAY_RECORDS
*& Form GET_RECORDS
Get all the Node values
FORM get_records .
Get the ID name for the Hierarchy
CALL FUNCTION 'G_SET_GET_ID_FROM_NAME'
EXPORTING
shortname = g_group
setclass = g_class
old_setid = g_setid
IMPORTING
new_setid = g_setid.
Get the Table and Field name for the Top Node
CALL FUNCTION 'G_SET_GET_INFO'
EXPORTING
setname = g_setid
no_set_title = 'X'
use_table_buffer = 'X'
IMPORTING
info = setinfo.
table_name = setinfo-tabname.
field_name = setinfo-fld.
Get all the Nodes for the Hierarchy
CALL FUNCTION 'G_SET_TREE_IMPORT'
EXPORTING
no_descriptions = ' '
no_rw_info = 'X'
setid = g_setid
TABLES
set_hierarchy = lt_hier
set_values = lt_val.
hier[] = lt_hier.
val[] = lt_val.
SELECT (field_name) FROM (table_name) INTO TABLE zaccbas.
LOOP AT zaccbas.
READ TABLE val WITH KEY FROM = zaccbas.
IF sy-subrc = 0.
DELETE zaccbas.
CLEAR zaccbas.
DELETE val INDEX sy-tabix.
CLEAR val.
ENDIF.
ENDLOOP.
ENDFORM. " GET_RECORDS
*& Form HEADER_DATA
Header Data
FORM header_data .
DATA: desc TYPE settext.
READ TABLE hier WITH KEY fieldname = field_name
shortname = g_group.
IF sy-subrc = 0.
desc = hier-descript.
ENDIF.
SKIP.
WRITE: 'Node :',g_group.
WRITE:75 'User name :', sy-uname.
WRITE:/ 'Description :', desc.
WRITE:75 'Date:', sy-datum.
WRITE:/ 'Table Name :' , table_name.
WRITE:75 'Time:', sy-timlo.
WRITE:/ 'Field Name :', field_name.
write:75 'Client:', SY-MANDT.
skip.
IF ambiguity_flag = 'X'.
WRITE:/ 'Ambiguity Check :'. WRITE: 'Success' COLOR 5.
ELSE.
WRITE:/ 'Ambiguity Check :'. WRITE: 'Failed' COLOR 6 .
ENDIF.
WRITE:/ sy-uline.
WRITE:/37 'Validation for Hierarchy'.
WRITE:/ sy-uline.
ENDFORM. " HEADER_DATA
*& Form ITEM_DATA
Output Report for Nodes
FORM item_data .
IF NOT zaccbas[] IS INITIAL.
WRITE:/ 'Missing Records from Hierarchy' COLOR 3.
LOOP AT zaccbas.
WRITE:/ zaccbas.
ENDLOOP.
ENDIF.
IF NOT val[] IS INITIAL.
SKIP 1.
WRITE:/ 'Additional Records in Hierarchy' COLOR 3.
LOOP AT val.
WRITE:/ val-from. ", 28 val-DESCRIPT.
ENDLOOP.
ELSEIF ZACCBAS[] IS INITIAL.
WRITE:/ 'No Missing Records Found' COLOR 3.
ENDIF.
ENDFORM. " ITEM_DATA
Thanks,
Sakthi C
*Rewards if useful*

Search Help hierarchy

Similar Messages

Maybe you are looking for