Skip to Content
author's profile photo Former Member
Former Member

Problem with custom Value Help Popup: Field HRASR_FORM_WINDOW is empty

Hi Guys,

i have a problem with the implementation of a custom value help popup. I followed the steps of Ian Stubbings blog /people/ian.stubbings/blog/2010/02/22/hcm-processes-forms-web-dynpro-abap-search-helps and analyzed the SAP standard form scenario "S_HRMSSRCF_REQUISITION" including its form "ISR_MSSRCF_SRQ3" and the WDABAP value help component "HRRCF_C_POSITION".

What i want is a value help popup that helps me finding an applicant from the old "PB" recruiting solution. So i developed a custom WD4ABAP component "ZP_HRASR_C_APPLICANT" implementing the interface "IF_HRASR00_FORM_WINDOW".

And i added manually the form interface field HRASR_FORM_WINDOW to the ISR scenario using transaction QISRSCENARIO. The Design Time HRAS_DT did not add this field to the ISR scenario and adobe form interface for whatever reason.

In the adobe form i added an ISR On-Form Event button using the ISR Native Controls Library.

After that i added the following script code to the button

"

data.Page1.FormApplicant.BTN_SelectApplicant::click - (JavaScript, client)

//Trigger call to backend for BAdI user command processing

ContainerFoundation_JS.SendMessageToContainer(event.target, "submit", "", "", "", "");

data.Page1.FormApplicant.BTN_SelectApplicant::ready:form - (FormCalc, client)

//Toggle visibility to be visible during edit operations, ínvisible otherwise

if($record.CONTROL_PARAM.ISR_MODE == "DISPLAY" |

$record.CONTROL_PARAM.ISR_FORM_VIEW =="ISR_APPROVE" )

then

this.presence = "invisible"

else

this.presence = "visible"

endif

data.Page1.FormApplicant.BTN_SelectApplicant::mouseDown - (FormCalc, client)

//Fire Event on Button Click (Mouse Down Event) and create WD4ABAP Value Help

$record.CONTROL_PARAM.ISR_EVENT = "USER_EVENT_POPUP"

$record.HRASR_FORM_WINDOW.DATA[*].FIELD.value = "ZP_HRASR_C_APPLICANT"

"

After pressing the button a roundtrip starts but the popup does not open. I analyzed this adding a breakpoint to the WDDOMODIFY view of the view FORM_EDIT of component "HRASR00_PROCESS_EXECUTE". The context node and element of HRASR_FORM_WINDOW are retrieved. The element itsself contains no static attributes but a dynamic attribute "FIELD". Unfortunately the value reference is empty. If i manipulate this in the debugger to value ->ZP_HRASR_C_APPLICANT the popup is called.

Has anybody an idea on this one or can help me? I need this solution because a dropdown is not sufficient when browsing through all candidates/applicants of the recruiting solution.

Best regards and thanks in advance

Dirk

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Sep 29, 2010 at 11:55 AM

    I have to add that for whatever reason that field was filled 3 times. I have no idea why that field/attribute sometimes is filled and sometimes not. Is there a problem with the script editor in Adobe DS maybe with some invisible characters or something like that?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Problem solved by myself. The reason is that there is a bug in transaction HRASR_DT which removes the field HRASR_FORM_WINDOW from the form interface when editing the adobe form directly from this transaction.

      In order to get this field into the form interface i entered transaction QISRSCENARIO and started to edit the form from there. The transaction asked me whether i would like to adjust the form interface. I confirmed this. After that the field HRASR_FORM_WINDOW was present in the form interface.

      For later editing of the form i avoided to do this from HRASR_DT and entered transaction SFP directly.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.