Search Help with Export Text and Import Parameters http://fuller.mit.edu/tech/search_helps.

html

Search Help with Export Text and Import Parameters

Also check out a introduction to Search Help Presentation by Allan Davidson. The following solutions were also provided by Allan.

Problem # 1: I needed a search help to return both the selected org unit & department name. I wanted both these items to populate fields on my dialog screen (this
would have worked for report selection screens also), without requiring an additional user action, such as ENTER, to trigger a PAI/PBO event cycle. This is the
default action for the field that the search help is associated with, org unit in this case, but the text description does not automatically populate a screen field
without a PBO event. So, how do I make this happen for the text without rolling my own PROCESS ON VALUE-REQUEST code, which can entail pages of
coding.

Problem #2: I needed this returned org unit to be input into a subsequent search help, as a restriction. The subsequent search help was on valid room sets
belonging to the DLC, aka org unit, chosen above. Again this needed to happen immediately without an intervening triggering event such as an ENTER.

All of this work is in SF8

Problem # 1
Search Help Exporting Text

The only element below that is necessary to solve this problem is making sure both the code and description are exported.

In this particular example, I'm not using a table or view for the "Selection method" because the field type ZZRE_DLCCODE, which is necessary to solve Problem
#2, is of a different type (char 12) than the org unit (numc 8) within the table holding the department name. NOTE: LPos should match the order of the
parameters!

Exported text (P_DLCNAME) not automatically picked up on screen - Structure necessary

I created a structure, ZEHDLC_RMSETS to hold all the fields on my dialog screen. Here are the fields necessary to solve Problem #1:

1 of 4 25/10/2012 10:55 AM
Search Help with Export Text and Import Parameters http://fuller.mit.edu/tech/search_helps.html

In order for this to work, the fields on the report selection or dialog programming screen must reference the search help via the data dictionary reference and
NOT by a direct reference. A direct reference would override the data dictionary reference, decoupling the search help parameters, p_dlc & p_dlcname. If you
are referencing a transparent table instead of a structure then you must attach the help to the field. Also, in a dialog programming screen it can be tricky:

MODULE get_equi_details ON REQUEST.

needs to be associated with both export fields in order for the reference to "stick."

Text is populated instantly without PAI/PBO events or coding your own PROCESS ON VALUE-REQUEST

To test run transaction ZCAFHAZMAT in SF8:

Also, the exported code can be used instantly as an import parameter to another search help - Problem # 2:

Problem #2
Search Help Importing Code and Exporting Text

2 of 4 25/10/2012 10:55 AM
Search Help with Export Text and Import Parameters http://fuller.mit.edu/tech/search_helps.html

Imported code (ZZDLCCODE) not automatically picked up by Search Help - Structure necessary

I created a structure, ZEHDLC_RMSETS to hold all the fields on my dialog screen. Here are all the fields necessary to solve both Problem #1 and #2:

In order for this to work, the fields on the report selection or dialog programming screen must reference the search help via the data dictionary reference and
NOT by a direct reference. A direct reference would override the data dictionary reference, decoupling the search help parameters, smenr, xmetxt & zzdlccode.

Code is available instantly without PAI/PBO events or coding your own PROCESS ON VALUE-REQUEST

To test run transaction ZCAFHAZMAT in SF8:

3 of 4 25/10/2012 10:55 AM
Search Help with Export Text and Import Parameters http://fuller.mit.edu/tech/search_helps.html

Problem # 3 Payroll Pernr Search Help

See Payroll Results Purge Program

4 of 4 25/10/2012 10:55 AM