Trigger of a event from a report

Hi Experts,
I need to trigger a event Price blocked of the business object BUS2081 from my report how can this be done
Is there any function module to do this
Thanks in Advance

Hi Karthick,
We have a standard function module ' SAP_WAPI_CREATE_EVENT' that triggers an event either from a report or from another fucntion module where the import parameters:
OBJECT_TYPE = <Object name>
EVENT = <Event name under the object?>
The object is identified using parameters OBJECT_TYPE and OBJECT_KEY .
Kindly reward if helpful.

Similar Messages

How to trigger an xi communication from abap report?

Hello,
I would like to ask if there is a blog, howto or something about How to trigger the communication in an abap programm. The communication will be either rfc->ftp or rfc->jdbc. So how can I tell XI to call that rfc to start the communication (from r/3 as abap programm)?
thank you.

>
RAJEEV GUPTA wrote:
> Hi Daniel,
>
> you can tell rfc to send the rfc response to XI.............but for this you have two options:
> 1. by se38 report you can execute rfc in r/3 and send its response to XI destination target system by executing the function module of rfc in your abap report
> 2. you can send the rfc req msg from XI to r/3 and then you will automatically get the rfc response from r/3 in XI via this synch msg.
>
>
> Regards,
> Rajeev Gupta
Hello,
about nr1:
When I set the DESTINATION parameter in a abap report, doesn't this mean the system where the rfc is available? Because when I do it like that my abap report would look for the rfc there and not in r/3 itself. Isn't that right?
e.g.
CALL FUNCTION 'RFC_on_r3'
DESTINATION 'XI.rfc.dest'
So you think that should work?

Can't trigger Process Lifecycle events from Visual Studio

Hi,
I'm writing a Windows Phone 8.1 Silverlight Application and am trying to trigger lifecycle events (Suspend, Resume, Background
Tasks) using the "Debug Location" toolbar. For some reason all the events are marked as disabled.
Didn't find anything on why this might happen. I'm running Visual Studio 2013 Update 4.
Any Ideas?

Hi Nir0,
The Lifecycle Events are available when we are debuging the Windows Phone 8.1 Runtime app.
For more information, please try to the the following
Application lifecycle for Windows Phone 8.1 Runtime app:
Then for the Windows Phone 8.1 Silverlight app, it is disable, for more information, please try to refer to the following article about lifecycle in Windows Phone silverlight app:
http://msdn.microsoft.com/en-us/library/windows/apps/ff817008(v=vs.105).aspx .
Best Regards,
Amy Peng
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Is it possible to trigger the next event from within the event case?

I have a rather complicated event that is triggered by a change in value of a particular button in the interface. In some cases, I want to alter that button's value when handling other events. But when I do this, the event handling a change in value for that button does not get triggered. Is there a way to make sure the value change event gets handled at the next iteration of the while loop in which the event structure sits?
Solved!
Go to Solution.

Hi Mike,
Thanks! I was using properties and did not previously know what the value(signaling) was. Knowing this will really help me clean up a lot of redundant code.

How can I trigger an onchange event for hidden or never displayed item

hi -- I have an item that I don't want displayed on my page -- more info than the user wants or needs; call it B. It needs to be
set by an onchange event from a visible item (A); then, the change of B triggers on onchange to set another item (visible) -- C.
When B is visible on the page, it all works. If I make it hidden or conditionally never displayed, it doesn't work. From the looks of
it, B never gets changed.
How can I trigger this onchange event (from B to set C) with B not visible?
Thanks,
Carol

hi Varad -- Probably more info than you want... but here's the whole chain of events.
Hope it answers your question.
C
**** 1
In A's html form element attributes (simplified; I took out the irrelevant call to jsLookupValue that sets another item).
onchange='jsLookupValue($v("P142_SITE_ID"),"site_id","P142_OBJECTTYPE_ID","objecttype_id","hdb_site_syn");'
**** 2
jsLookupValue is the following.
The statement that actually sets the value of B is: $s(dest_item_name, jsonobj.row[0].RETURN_VAL);
function jsLookupValue(source_item_value, source_column_name, dest_item_name, dest_column_name, lookup_table_name){
// Continue only if there are valid values
if (valueOf(source_column_name)&&valueOf(dest_item_name)&&valueOf(dest_column_name)&&valueOf(lookup_table_name)){
//Check to see if the source_item_value is null (either all spaces or empty
//If it is, set the dest item to null, but only if it's not already --
//otherwise we get into a loop.
source_item_value = trim(source_item_value);
dest_item_value = trim($v(dest_item_name));
if (source_item_value.length==0) {
if (dest_item_value.length != 0) {
$s(dest_item_name, null);
}else{
//This is the AJAX call to the Application Process from step 1
ajaxRequest = new htmldb_Get(null,&APP_ID.,'APPLICATION_PROCESS=LOOKUP_VALUE',0);
//Here we are adding that x01 parameter we use in the app process with the value of the objecttype_name field
ajaxRequest.addParam('x01', source_item_value);
ajaxRequest.addParam('x02', source_column_name);
ajaxRequest.addParam('x03', dest_item_name);
ajaxRequest.addParam('x04', dest_column_name);
ajaxRequest.addParam('x05', lookup_table_name);
//Now do the actual AJAX call and put the result in ajaxResponse
ajaxResponse = ajaxRequest.get();
//Check if there is a response
if (ajaxResponse) {
//We need to format the JSON return string and put it in a JSON object
// the formatting is done by a function in the external JSON library
// the jsonobj can be used to retrieve the data returned by the App process
var jsonobj= ajaxResponse.parseJSON();
// And finally, we set the DNAME item with the value of the jsonobj.DNAME
// an array was created in the object with the name row, so that is why you have to include row[0] to retrieve the data
if (jsonobj.row[0].RETURN_VAL != $v(dest_item_name)) {
$s(dest_item_name, jsonobj.row[0].RETURN_VAL);
}else{
} //not setting
}else{
alert('No response from app process');
} //no response
} //no source item value
} //no bad nulls
} //function
**** 3
I won't bore you with app process LOOKUP_VALUE. It just builds an sql query that gets the value for B, aliased to RETURN_VAL.

Trigger a Begin event running Global Automatic activity

Hi
I have a situation explained as follows:
The BPM Process flow would be triggered when a message comes into a JMS Queue.
I have configured the JMS Messaging Service as an external resource and used a Global Automatic Activity as an Automatic JMS Listener to listen on that queue.
Once the message is received on the queue, I want my actual process flow to be instantiated and activities following the begin activity to be executed.
In the Studio Reference document, it is mentioned that
You can trigger a Begin event running Global Automatic activity.
Can someone tell me the steps to trigger the Begin Event from Global Automatic Activity and create the process instance.
Thanks

You have to call this method
ProcessInstance.create(arguments : args, argumentsSetName : "BeginIn")
Args is Any[String] where you put you input arguments that you have in your begin activity and BeginIn is the set of arguments you have in the begin activity.
HTH

Avoiding first select event from chart ?

Hi,
I trigger a select event from a chart to another BI query to drill down into details. Unfortunately, when the chart is build up, without any user interaction a first select event is already triggered. Is it possible to avoid this event (for instance by a guard condition) ?
Regards, Christian

Hi Christian
Sorry about the delay. The solution here is to use a data store and a guard condition, the data store should be triggered on the first select event in the chart, its default value should be itself+1, this means that when the first select event is triggered the value will be 1, you can then use your guard condition to check for this and only if the value is greater than 1 it should continue.
Jarrod Williams

EBS: Email XML publisher output, from After Report Trigger in Data Template

Here is what I'm trying to do:
-- In EBS (11.5.10 CU2), I'm using XML publisher (5.6.2) data template and layout template to generate Output files (PDF, EXCEL etc)
--In the Data Template's AfterReport Trigger, I'm using the Concurrent Request Id to locate the Output file name and trying to Email that output file.
Problem:
-- When the AfterReport trigger code is executed, the code is NOT seeing the output file and hence the file is NOT emailed.
Observations/Questions:
-- From what I observe, the Output Post Processor ( that generates the Excel / PDF files) is running AFTER the code in AfterReport trigger... and hence the AfterReport trigger is Not quite seeing / able to access the output file.
So, the sequence of execution seems to be:
-- Before Report Trigger
-- Data Query (SQL statement)
-- After Report Trigger
-- Output Post Processor
Because the AfterReport Trigger is running before the Output Post Processor, it is Not able to see the output file. Is that a True statement?
If Yes, how else can the DataTemplate access the Output file?
If No, what could cause the AfterReport trigger to not see the output file?

Because the AfterReport Trigger is running before the Output Post Processor, it is Not able to see the output file. Is that a True statement?
I believe so, as the OPP works on the output of the Report after the Report has completed execution.
You could use the same approach as we do for bursting the report to different users. Write a Java Concurrent program based on "oracle.apps.xdo.oa.cp. XMLPReportBurst" with delivery channel Email to send the email output. You would need to add code to launch the Concurrent child request in your AfterReport Trigger:
function AfterReport return boolean is
jreq_id number;
begin
srw.message (100, 'DEBUG: AfterReport_Trigger +');
jreq_id:= FND_REQUEST.SUBMIT_REQUEST ('XDO','XDOBURST','','',FALSE,:P_CONC_REQUEST_ID,'Y',chr(0),
If (jreq_id=0)
then
srw.message (100,'Request id is zero');
end if;

Run Crystal Reports in background on event from asp

How would I run a Crystal Report file in the background after an onClick event from an ASP web page?
Are there any code samples of how this can be configured?
I have Crystal Reports Server 2008 and Crystal Reports 2008.

See if the solution in [this|Re: CR2010 Production Release; thread will help.
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]

EM12c User Reported Event from PL/SQL

Hi,
Is there a way to create a user reported event from PL/SQL (similar to emcli publish_event) ?
Thanks

Can you describe your use case? Maybe there are other ways to address the issue.
-Mughees

ProjectUID selected from the reporting database from Project Server OnPublished event is taking some delay

Hi all,
I'm invoking a stored procedure from the reporting database from the project server onPublished event. I'm having some issues in getting the details of that particular project from the published event handler. This i noticed that there is some
delay is taking place in moving the data(project uid ) from the published to the reporting database .
My stored procedure select statement is as follows:
SELECT ProjectUID, ProjectName FROM MSP_EpmProject_UserView
　WHERE ProjectUID=value
This stored procedure is invoked from the onPublished event of the project server event handler where that particular projectuid is passed in that stored procedure.I have noticed that some delay is taking palce to move the data into the reporting database.
My stored procedure got invoked from the onPublished event of the project server event handler before the delay is complete. So the row selected from the stored procedure is alwys zero (0). Is there any other method to wait for repoting database
to get refreshed. Please help me .

Hi sabithad,
The issue you are facing is because of the conflict of permissions, event handlers always works through administrative user credentials whereas the project is open in edit mode by the logged-in user. And you are tyring to update custom field at the back
end with Administrative credentials, while project queue is in process by logged-in users credentials. Its not gonna work this way :)
The best option is to use Javascript on your PDP using CEWP, you can either build your complete logic in JavaScript and place that code on your PDP. OR you can use the combination of JavaScript and PSI and create a webpart to be placed on PDP.
below blog link willgive you directions to go ahead with, but for sure the solution to your query is
JavaScript :)
http://epmxperts.wordpress.com/2012/05/21/generate-unique-id-for-project-using-a-webpart/
hope this helps.
Khurram Jamshed - MBA, PMP, MCTS, MCITP (
Blog, Twitter, Linkedin )
If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”.

Events in Interactive reports

hi gurus,
i want detailed explanation each n every event of standard report...
Regards
baskar

HI
INITIALIZATION
This event keyword defines an event block whose event is triggered by the ABAP runtime environment during the flow of an executable program, directly after LOAD-OF-PROGRAM and before the selection screen processing of any existing standard selection screen. This gives you the one-time opportunity to initialize the input fields of the selection screen, including those defined in the logical database linked with the program.
When an executable program defines a standard selection screen, it is called again by the ABAP runtime environment after execution, which triggers the INITIALIZATION event again. In this case, initializing parameters or selection criteria of the selection screen has no effect, because they are automatically supplied with the preceding user inputs from the selection screen during the selection screen event AT SELECTION-SCREEN OUTPUT. To explicitly initialize the selection screen for each call, you must use the event AT SELECTION-SCREEN OUTPUT.
START-OF-SELECTION
This event keyword defines an event block whose event is triggered by the ABAP runtime environment when calling the executable program selection screen processing of a selection screen.
In an executable program, all statements that are not declarations, and are listed before the first explicit processing block, are assigned to this event block. If the program does not contain an explicitly defined event block START-OF-SELECTION, these statements form the complete event block START-OF-SELECTION. If a program contains an explicitly defined event block START-OF-SELECTION, these statements are added to the beginning of the event block. If the program contains no explicitly defined event blocks, these statements form the entire event block START-OF-SELECTION.
If the program is linked to a logical database, preparations can be made here before the logical database reads data. If the program is not linked to a logical database, this event block even displays a "main program" from which procedures or screen layouts are called.
GET node
Use GET to handle two types of events after submitting executable programs: Get events and events at the end of a hierarchy level of a logical database. If during a GET event a list is written, previously an automatic line feed is created.
The event blocks after GET are implemented internally as procedures. Declarative statements in GET event blocks create local data.
END-OF-SELECTION
This statement defines an event block, whose event is raised by the ABAP-runtime environment during the calling of an executable program , if the logical database, with which the program is linked, has completely finished its work.
In this event block, all data read by the logical data base , can be processed summarically. In an executable program without logical data base, there is no need to implement the event block END-OF-SELECTION.
LOAD-OF-PROGRAM
This event keyword defines an event block whose event is triggered by the ABAP-runtime environment when an executable program, a module pool, a function group or a sub-routine pool is loaded in the internal session.
When calling a program through SUBMIT or through a transaction code, then, at every call, a new internal session is opened and the event block is executed once at every call. You can initialize global data objects of the program here.
At the first call of an external Procedure (sub-program or function module), the framework program of the called procedure is loaded into the internal session of the caller, thus triggering the event LOAD-OF-PROGRAM. The event block is executed before the called procedure. At any further call of a procedure of the same framework program by a caller of the same internal session, the event LOAD-OF-PROGRAM is triggered no longer.
The event LOAD-Of-PROGRAM should mainly be used to initialize global data when calling external procedures or Transactions. If you call executable programs with SUBMIT, we recommend that you use the event INITIALIZATION, as the Starting values for parameter and selection criteria are set after LOAD-OF-PROGRAM (see program flow after SUBMIT).
AT SELECTION-SCREEN
AT SELECTION-SCREEN selscreen_event.
This statement defines event blocks for different events selscreen_event that are triggered by the ABAP runtime environment during selection screen processing.
Selection screen events occur immediately before sending a selection screen and after certain user actions on a displayed selection screen. They assist in selection screen processing in the ABAP program.
AT SELECTION-SCREEN is triggered at least twice during actions on selection screens that are linked into another selection screen as a subscreen - first for the linked selection screen itself, and then for the linking selection screens.
The event blocks after AT SELECTION-SCREEN are implemented internally as procedures. Declarative statments in these event blocks create local data.
AT SELECTION-SCREEN OUTPUT
This event is triggered at the screen event PBO of a selection screen. In the event block, the selection screen can be prepared through assignments to the data objects of parameters and selection criteria and through dynamic screen modifications.
The assignments to input fields in the event block AT SELECTION-SCREEN OUTPUT always affect the selection screen and overwrite the user inputs from previous displays of the same selection screen. Assignments in the event blocks LOAD-OF-PROGRAM oder INITIALIZATION, on the other hand, only have an effect at first program start.
AT SELECTION-SCREEN ON {para|selcrit}
This event is triggered at the screen event PAI of a selection screen if the content of the input field of a parameter para or a line of a selection criterion selcrit was passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or an error message in the event block makes the fields para and selcrit ready for input again.
No parameter that is defined as a radio button can be specified. For this purpose, the addition ON RADIOBUTTON GROUP is provided.
If a user action takes place in the dialog box for the multiple selection of a selection criterion selcrit, the entries of the selection table are passed to the program, line by line. For each line, the event AT SELECTION-SCREEN ON selcrit is triggered.
AT SELECTION-SCREEN ON END OF selcrit
This event is triggered after the selection table selcrit has been fully passed to the program after a user action in the dialog box for the multiple selection has taken place. In the event block, the entire selection table can be checked.
AT SELECTION-SCREEN ON BLOCK block
This event is triggered at the screen event PAI of a selection screen if all the input fields of a block block of the selection screen were passed to the ABAP program. In the event block, the user inputs can be checked. Sending a warning or an error message in the event block makes all the fields of the block block ready for input again.
AT SELECTION-SCREEN ON RADIOBUTTON GROUP radi
This event is triggered at the screen event PAI of a selection screen if all the fields of a radio button group radi of the selection screen were passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or error message in the event block makes all the radion buttons of the block radi ready for input again.
The individual fields of a radio button group are not passed individually and do not trigger the event AT SELECTION-SCREEN ON par.
AT SELECTION-SCREEN { ON { HELP-REQUEST | VALUE-REQUEST } FOR
{para|selcrit-low|selcrit-high} }
The two events ON HELP-REQUEST and ON VALUE-REQUEST are triggered at the screen events POH and POV of a selection screen if - for the input field of a parameter para or one of the input fields of a selection criterion selcrit - the field help F1 or the input help F4 was called. Other selection events are not triggered.
In the event blocks, a self-defined field or input field can be programmed, which overrides any helps possibly defined in the ABAP Dictionary.
These event blocks can only be implemented for fields of the selection screen that are defined in the same ABAP program and not in a possibly linked logical database.
With the events for the field and input help, no data is transported between the selection screen and the ABAP program. As with general screens, suitable function modules must be used for these. The parameters and selection criteria changed for the input help are transported to the selection screen.
AT LINE-SELECTION
This statement defines an event block whose event is triggered by the ABAP runtime environment during the display of a screen list - provided the scren cursor is on a list line and you select a function using the function code PICK. Through the definition of this event block, the standard list status is automatically enhanced in such a way that the function code F2 and, with it, the double-click mouse function is linked up to the function code PICK.
If the function key F2 is linked with a function code different than PICK, each double click will trigger its even, usually AT USER-COMMAND, and not AT LINE-SELECTION.
AT USER-COMMAND
This statement defines an event block whose event is triggered by the ABAP runtime environment if, during the display of a screen list, a function with a self-defined function code was chosen.
Self-defined function codes are all those that include character combinations, except for the following:
The function codes PICK and PF## ("##" stands for 01 to 24) do not cause the event AT USER-COMMAND, but the events AT LINE-SELECTION and AT PF##.
All function codes that start with the character "%" are interpreted as system functions and do not cause the event AT USER-COMMAND. The system functions for lists are listed in the following table 1.
The function codes in the following table 2, likewise, do not cause the event AT USER-COMMAND, but are handled by the list processor.
AT PF##
This statemet defines an event block whose event is triggered by the ABAP runtime environment during list display - provided the screen cursor is on a list line and a function is selected using the function code PF##. Here ## stands for a number between 01 and 24. In the= standard list status, these function codes are assigned to the function keys of the input device.
Instead of AT PF## , AT USER-COMMAND should always be used and special function codes should be assigned to the required function keys.
TOP-OF-PAGE
Effect
This statement defines an event block whose event is triggered by the ABAP runtime environment during the creation of a list. This occurs when a new page is started - that is, immediately before the first line in a new page is to be output. All list outputs that take place in the event block are placed below the standard page header of the list. You cannot output more lines than are available in the page within the event block. The NEW-PAGE statement is ignored within this event block.
The entire output written to the list in the event block belongs to the page header of the current list page. The top page header cannot be moved when you scroll vertically in a list displayed on the screen.
TOP-OF-PAGE DURING LINE-SELECTION
If you do not use an addition, an event block is triggered for event TOP-OF-PAGE during the creation of a basic list. If you use the addition DURING LINE-SELECTION, an event block is triggered for the corresponding events during the creation of details lists. You have to use system fields like sy-lsind to distinguish between the individual details lists.
END-OF-PAGE
This statement defines an event block that is raised by the ABAP-runtime during creation of a basic list, if there is a line reservation in the addition LINE-COUNT of the initiating statement for a page footer, which was reached while writing to this page. A list output that takes place in the event block, is placed in this area. Output statements that exceed the reserved area will be ignored.
Reward if usefull

How to trigger a background job from BADI method.

hi friends,
i need to trigger a background job from the badi method CHANGE_AT_SAVE for the BADI BOM_UPDATE.
for this i think i need to create an event which i should give with parameters during job creation.
can you pls help me solve this issue.
thank u all.

Hi Saravanan,
Here is an example of what you have to do.
Regards,
Eric
Reward any helpful sugestion.
*&      Form generar_job
FORM generar_job .
Generar Variante
PERFORM generar_variante.
w_fecha = sy-datum + 3.
CALL FUNCTION 'DATE_COMPUTE_DAY'
    EXPORTING
      date = w_fecha
    IMPORTING
      day = w_weekday.
Si la fecha cae en sabado o domingo se debe continuar el lunes.
CASE w_weekday.
    when '1'.
      ADD 2 TO w_fecha.
    WHEN '6'.
      ADD 2 TO w_fecha.
    WHEN '7'.
      ADD 1 TO w_fecha.
ENDCASE.
w_jobname = 'ZQM_CIERRE_LOTE_INSPECCION'.
CALL FUNCTION 'JOB_OPEN'
    EXPORTING
      jobgroup         = 'QUEUE'
      jobname          = w_jobname
    IMPORTING
      jobcount         = w_jobcount
    EXCEPTIONS
      cant_create_job = 1
      invalid_job_data = 2
      jobname_missing = 3
      OTHERS           = 4.
IF sy-subrc EQ 0.
    CALL FUNCTION 'JOB_SUBMIT'
      EXPORTING
        authcknam               = sy-uname
        jobcount                = w_jobcount
        jobname                 = w_jobname
        report                  = 'ZQM_CIERRE_LOTE_INSPECCION'
        variant                 = w_var
      IMPORTING
        step_number             = w_stepnum
      EXCEPTIONS
        bad_priparams           = 1
        bad_xpgflags            = 2
        invalid_jobdata         = 3
        jobname_missing         = 4
        job_notex               = 5
        job_submit_failed       = 6
        lock_failed             = 7
        program_missing         = 8
        prog_abap_and_extpg_set = 9
        OTHERS                  = 10.
    IF sy-subrc EQ 0.
      CALL FUNCTION 'JOB_CLOSE'
        EXPORTING
          jobcount             = w_jobcount
          jobname              = w_jobname
          sdlstrtdt            = w_fecha
          sdlstrttm            = w_hora
        IMPORTING
          job_was_released     = w_rel
        EXCEPTIONS
          cant_start_immediate = 1
          invalid_startdate    = 2
          jobname_missing      = 3
          job_close_failed     = 4
          job_nosteps          = 5
          job_notex            = 6
          lock_failed          = 7
          OTHERS               = 8.
      IF sy-subrc EQ 0.
        IF w_rel EQ 'X'.
          WRITE:/ w_jobname, 'FUE LIBERADO. VER SM37.'.
        Guardamos los destinatarios
          PERFORM destinatarios_job.
        Guardamos la información a utilizar al ejecutar el job
          PERFORM guardar_datos_job.
        ELSE.
          WRITE:/ w_jobname, 'NO FUE LIBERADO'.
        ENDIF.
      ELSE.
        WRITE:/ w_jobname, 'NO FUE CERRADO'.
      ENDIF.
    ELSE.
      WRITE:/ w_jobname, 'NO FUE ENVIADO'.
    ENDIF.
ELSE.
    WRITE:/ w_jobname, 'NO FUE CREADO'.
ENDIF.
ENDFORM.                    " generar_job

External trigger for internal event

Hello,
I would like to use an external trigger on a PFI-line to trigger an
internal event, e.g. the switch of an indicator on the front panel from
"1" to "2".
How do I do that?

Thanks for your answer!
The problem was that I wanted to use a PFI-line on a PCI-board
(BNC-2110) from NI to trigger the start of a voltage output task. On
the other hand, I wanted to use the same trigger event for stopping a
while-loop which would otherwise abort the task after some seconds if
the trigger didn't come; the data generation itself is rather long, so
you have to set the "timeout" terminal of "DAQmx Wait Until Done" to "
-1". The problem was that it is not possible (at least on this board)
to use a digital in-line for triggering the task and the PFI-line for
getting a digital input. So I splitted the signal up: it was weird to
both lines and worked as trigger on the PFI and was monitored on a
DI-line.
This setup worked, but as there were still some problems, I changed it
again. Now I check for some digital in-lines (which provide a stimulus)
in a while-loop while waiting for the trigger; if the stimulus changes,
the task (which is waiting for the trigger) is aborted. The problem is
that if the stimulus doesn't change and the task is triggered as usual
and is completed, I can't report that fact to the while loop! So the
while-loop goes on and blocks the rest of the diagram. I just wrote
another posting concerning that thing, if you would have a look... It
can be really a little hard sometimes, can't it...
This thing concerning the event structure and value (signaling) sounds
interesting, I'm just trying to figure out the possibilities how to use
an event structure; but it's not always really intuitive.
Best regards,
Mitja
Message Edited by Mitja on 11-14-2005 07:09 PM

Excel fiel from ALV report

Hi Gurus,
    is der any way to download data from ALV report to excel sheet depending on layout set dyanmically.
I mean to say that if I choose a layout then data has to transfer to excel sheet according to layout fields automaticaly.

I think this can be done by oops ALV , are u using reusealv F.M to call output in ALV ?
Try the below kind of ALV
IN PBO -
>
SET PF-STATUS 'PROJREP'.
SET TITLEBAR text-046.
DATA: g_container TYPE scrfname VALUE 'ALV',
      g_grid1 TYPE REF TO cl_gui_alv_grid,
      g_custom_container TYPE REF TO cl_gui_custom_container.
IF g_custom_container IS INITIAL.
    CREATE OBJECT g_custom_container
           EXPORTING container_name = g_container. (Name of the container )
CREATE OBJECT g_grid1
           EXPORTING i_parent = g_custom_container.
PERFORM create_field_catalog_ce
CALL METHOD g_grid1->set_frontend_fieldcatalog
      EXPORTING
        it_fieldcatalog = t_fcat_ce.
ALL METHOD g_grid1->set_table_for_first_display
      EXPORTING
        i_structure_name = 'ST_DISPLAY'
      CHANGING
        it_outtab        = t_display_io
        it_fieldcatalog = t_fcat_ce.
->Create Object to receive events and link them to handler methods.
When the ALV Control raises the event for the specified instance
the corresponding method is automatically called.
    CREATE OBJECT g_event_receiver.
    SET HANDLER g_event_receiver->handle_double_click FOR g_grid1.
ENDIF.
CALL METHOD cl_gui_control=>set_focus
    EXPORTING
      control = g_grid1.
IN PAI -->
CALL METHOD cl_gui_cfw=>dispatch.

Trigger of a event from a report

Similar Messages

Maybe you are looking for