Object Event: RollOver

Using MovieClipLoader and onLoadInit, I dynamically load TN's
from a file and align them. onRollOver, I want them to scale up.
I have added ListenerObject to the ClipLoader, but the only
Events it seems to handle are those detectable by the
MovieClipLoader Class (eg. onLoadError, onLoadComplete, onLoadInit,
LoadProgress...). How to I get my TN's to react to Mouse
Events?

This what you want?
ListenerObject.onLoadInit = function(TargetMC2){
TargetMC2.onRollOver = function(){
this._yscale += 25;
this._xscale += 25;
Erick Souza
www.ericksouza.com

Similar Messages

Issue regarding [Work Flow] Business Object Event Raise in ABAP Program

Hi All,
I have one issue regarding [Work Flow] Business Object Event Raise in ABAP Program.
Actual TDS is as below:
If E message type written, raise Business object BUS2005 (Production order) Event PickShortage for production order passing warehouse, transfer request
(BUS2065 Object key) in event container. Also include table of text version of error
messages for this set of Transfer
Request.
Can anybody tell me how can i write it technically in ABAP Code.
Can anybody solve this issue!
Thanks in advance.
Thanks,
Deep.

Hi,
Can anybody solve above posted issue!
Thanks,
Deep.

RE: Re[2]: Service Object events and LockMgr

I think there are a lot to implement a lock manager. If several objects
should be updated in one transaction, the lock manager should be able to
handle rollbacks. Other things like release lock when exception happens,
avoiding dead locks, etc. Most of the features are provided by DBMS, so
I think using a option 2 would be a better solution.
-----Original Message-----
From: Dimitar Gospodinov [mailto:[email protected]]
Sent: Wednesday, July 28, 1999 2:44 PM
To: Peter Sham
Cc: Duncan Kinnear; [email protected]
Subject: Re[2]: Service Object events and LockMgr
Hello Peter,
Wednesday, July 28, 1999, 9:19:10 PM, you wrote:
PS> Hi,
PS> Just wonder exactly how this Lock Manager can be
implemented. Do you mean that you are
PS> going to cache every object that is instantiated from the
database? Or you just cache
PS> the object id, primary key, etc?
PS> Frankly speaking, I won't attempt to due with this kind
of currency coding myself as
PS> the database vendor has spent years in coding just to do this.
PS> Regards.
The second one - you just need some unique value that will identify
the object being locked. You should register with the Lock
Manager only
the objects that you want to lock.
For me, one of the goal of such pattern is to give you some freedom
from the specifics of the database lock mechanism.
Another benefit that I can see is that using such approach you can
always answer to the question: "Can I modify/delete this object?".
Best regards,
Dimitar mailto:[email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

I think there are a lot to implement a lock manager. If several objects
should be updated in one transaction, the lock manager should be able to
handle rollbacks. Other things like release lock when exception happens,
avoiding dead locks, etc. Most of the features are provided by DBMS, so
I think using a option 2 would be a better solution.
-----Original Message-----
From: Dimitar Gospodinov [mailto:[email protected]]
Sent: Wednesday, July 28, 1999 2:44 PM
To: Peter Sham
Cc: Duncan Kinnear; [email protected]
Subject: Re[2]: Service Object events and LockMgr
Hello Peter,
Wednesday, July 28, 1999, 9:19:10 PM, you wrote:
PS> Hi,
PS> Just wonder exactly how this Lock Manager can be
implemented. Do you mean that you are
PS> going to cache every object that is instantiated from the
database? Or you just cache
PS> the object id, primary key, etc?
PS> Frankly speaking, I won't attempt to due with this kind
of currency coding myself as
PS> the database vendor has spent years in coding just to do this.
PS> Regards.
The second one - you just need some unique value that will identify
the object being locked. You should register with the Lock
Manager only
the objects that you want to lock.
For me, one of the goal of such pattern is to give you some freedom
from the specifics of the database lock mechanism.
Another benefit that I can see is that using such approach you can
always answer to the question: "Can I modify/delete this object?".
Best regards,
Dimitar mailto:[email protected]
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

Re: Service Object events and LockMgr

On the option that you have considered, I have implemented the same model
in my previous project (using Java/RMI), but I felt that it is more than
what is normally needed for concurrency protection.
I can suggest another option that is worth considering which is in place in
our app for concurrency.
Almost every table in our db has created By, created On, modifed By,
modified On columns. The parent class of all business objects has
attributes that correspond to these four columns. In addition to these
four, there is a fifth attribute (introduced when concurrency was built)
called originalModifiedOn. Upon retrieval from the db, it is set to
modifiedOn value (from the db), during UPDATE, the value in this column is
added part of the WHERE clause. So when the second user tried to do save
the same object, the underlying db update will get a 'zero rows updated'
which is translated into an application error 'possible concurrency
error'. The user re-retreives the now 'stale' object before applying their
edits.
A lot of these things are and can be built into the framework imposing very
little work that each Object needs to do to have concurrency protection.
I am not sure if there is a mention in the Patterns paper of this model,
but it is very easy to implement and supports what is needed.
Kishore Puvvada's Mail
[email protected] on 07/28/99 01:47:00 AM
To: [email protected]@INTERNET
cc: (bcc: Kishore Puvvada/HQ-IS/TAL)
Subject: Service Object events and LockMgr
Hi folks,
We're currently looking at strategies for dealing with the simultaneous
updates to the database from multiple clients (concurrency
management). That is when two (or more) clients load the same object to
edit it, then make different changes and save them to the database.
We have a copy of a Forté document (from the "Patterns" course, I
think) which describes three methods of dealing with this:
1) Lock the database table row as soon as a client select it for editing
and hold the lock until it is saved.
2) Immediately before 'saving' check that the database hasn't changed
(either by reading what's there before updating, or by using a huge
'where' clause that contains all unchanged fields)
3) The Forté "LockMgr" pattern, which uses a service object with notifier
proxies to allow locking and updating notification between the clients.
Option 3 is obviously the most robust method, but it requires a fair
amount of coding and could also be a bottleneck for database reads and
writes.
But I have another option for which I was looking for opinions. What if
we had a "Change Event manager" which broadcast an event every time
a change is made to the database. Each business class would have its
own event. If the event had the object's primary key as a parameter, then
clients editing that particular object type could check to see if the object
currently on screen is the one that changed. That way you could disable
the 'save' until they had refreshed their on-screen data.
It's not particularily elegant, but it's reasonably simple to implement. It
also deals with changes sent across our WAN from other database
servers.
But this option is only worthwhile if you can replicate the "Change Event
manager" SO and still register for an event on the client. Can clients
register for SO events and receive an event generated by any of the SO's
replicates? Or when you register for an SO's event do you register for
only one instance of the SO?
Thanks in advance for any answers.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email:
[email protected]
PO Box 764, McLean Towers, Phone: +64 6 834 3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834 3369
Providing Integrated Software to the Meat Processing Industry for over 10
years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:
http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

On the option that you have considered, I have implemented the same model
in my previous project (using Java/RMI), but I felt that it is more than
what is normally needed for concurrency protection.
I can suggest another option that is worth considering which is in place in
our app for concurrency.
Almost every table in our db has created By, created On, modifed By,
modified On columns. The parent class of all business objects has
attributes that correspond to these four columns. In addition to these
four, there is a fifth attribute (introduced when concurrency was built)
called originalModifiedOn. Upon retrieval from the db, it is set to
modifiedOn value (from the db), during UPDATE, the value in this column is
added part of the WHERE clause. So when the second user tried to do save
the same object, the underlying db update will get a 'zero rows updated'
which is translated into an application error 'possible concurrency
error'. The user re-retreives the now 'stale' object before applying their
edits.
A lot of these things are and can be built into the framework imposing very
little work that each Object needs to do to have concurrency protection.
I am not sure if there is a mention in the Patterns paper of this model,
but it is very easy to implement and supports what is needed.
Kishore Puvvada's Mail
[email protected] on 07/28/99 01:47:00 AM
To: [email protected]@INTERNET
cc: (bcc: Kishore Puvvada/HQ-IS/TAL)
Subject: Service Object events and LockMgr
Hi folks,
We're currently looking at strategies for dealing with the simultaneous
updates to the database from multiple clients (concurrency
management). That is when two (or more) clients load the same object to
edit it, then make different changes and save them to the database.
We have a copy of a Forté document (from the "Patterns" course, I
think) which describes three methods of dealing with this:
1) Lock the database table row as soon as a client select it for editing
and hold the lock until it is saved.
2) Immediately before 'saving' check that the database hasn't changed
(either by reading what's there before updating, or by using a huge
'where' clause that contains all unchanged fields)
3) The Forté "LockMgr" pattern, which uses a service object with notifier
proxies to allow locking and updating notification between the clients.
Option 3 is obviously the most robust method, but it requires a fair
amount of coding and could also be a bottleneck for database reads and
writes.
But I have another option for which I was looking for opinions. What if
we had a "Change Event manager" which broadcast an event every time
a change is made to the database. Each business class would have its
own event. If the event had the object's primary key as a parameter, then
clients editing that particular object type could check to see if the object
currently on screen is the one that changed. That way you could disable
the 'save' until they had refreshed their on-screen data.
It's not particularily elegant, but it's reasonably simple to implement. It
also deals with changes sent across our WAN from other database
servers.
But this option is only worthwhile if you can replicate the "Change Event
manager" SO and still register for an event on the client. Can clients
register for SO events and receive an event generated by any of the SO's
replicates? Or when you register for an SO's event do you register for
only one instance of the SO?
Thanks in advance for any answers.
Cheers,
Duncan Kinnear,
McCarthy and Associates, Email:
[email protected]
PO Box 764, McLean Towers, Phone: +64 6 834 3360
Shakespeare Road, Napier, New Zealand. Fax: +64 6 834 3369
Providing Integrated Software to the Meat Processing Industry for over 10
years
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:
http://pinehurst.sageit.com/listarchive/forte>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/forte>

[AGENT] socket error: [object XrayWrapper [object Event]]; readyState=3. Perhaps Helper is not running on ws://127.0.0.1:14821/2 or is shutting down? console.error: onepassword:

hi
in terminal, i am seeing this message.
[AGENT] socket error: [object XrayWrapper [object Event]]; readyState=3. Perhaps Helper is not running on ws://127.0.0.1:14821/2 or is shutting down?
is something missing that should be running
i dont understand this message
thankyou

solved. was a firefox addon called 1password
solved by deleting the desktop version of hte app and reinstalling
1password support was useless. didnt even know a piece of their own software. suggested it was a ffox profile issue. red herring.

"new object" event in JDI?

I'm surprised that there seems to be no "new object" event in the JDI. As far as I can tell, the only way to identify a new instance of a class is by requesting MethodExitEvent, checking Method.isConstructor(), and then iterating over ClassType.instances() for objects you haven't seen before. This seems really inefficient. Is there no better way?

Weak. NO DUKE STARS FOR YOU!!!

Regarding [Work Flow] Business Object Event Raise in ABAP Program

Hi All,
I have one issue regarding [Work Flow] Business Object Event Raise in ABAP Program.
Actual TDS is as below:
If E message type written, raise Business object BUS2005 (Production order) Event PickShortage for production order passing warehouse, transfer request
(BUS2065 Object key) in event container. Also include table of text version of error
messages for this set of Transfer
Request.
Can anybody tell me how can i write it technically in ABAP Code.
Can anybody solve this issue!
Thanks in advance.
Thanks,
Deep.

Hi,
Can anybody solve above posted issue!
Thanks,
Deep.

Access ECC business object event in CRM

Hi Experts,
We have a requirement in which we need to check whether a business object event is triggered in ECC system and access the related business object details in CRM system.
The ECC and CRM systems are already integrated.
Any help on how to access business object events in the other system would be highly appreciated.
Regards,
Saumya

Closing due to lack of replies

ABAP Object Event

Hi All,
      Could anybody send me a document for ABAP Object events.
And simple programs for Events.
My id - [email protected]
Thanks,
Ponraj.s.

Hi,
Go thru this basic simple program with documentation which demonstrates how to handle events, for nodes in a tree using abap objects
REPORT YLIST_TREE MESSAGE-ID ZER_INFO.
CLASS LCL_EVT_HDLR DEFINITION DEFERRED. " definition is given later
CLASS CL_GUI_CFW DEFINITION LOAD. " global class to be loaded
DATA:G_EVENT(50),    " to hold the event
     G_NODE_KEY TYPE TV_NODEKEY, "holds the node key
     G_ITEM_NAME TYPE TV_ITMNAME,
     G_KEY TYPE TV_ITMNAME.
DATA:G_EVT_HDLR TYPE REF TO LCL_EVT_HDLR,
     G_CUSTOM_CONTAINER TYPE REF TO CL_GUI_CUSTOM_CONTAINER,
     G_TREE TYPE REF TO CL_GUI_LIST_TREE,
     G_OK_CODE TYPE SY-UCOMM.
TYPES:ITEM_TABLE_TYPE LIKE STANDARD TABLE OF MTREEITM
      WITH DEFAULT KEY.
      CLASS lcl_evt_hdlr DEFINITION
CLASS LCL_EVT_HDLR DEFINITION.
PUBLIC SECTION.
    METHODS:
*---- methods for action handling for nodes
    NODE_DBL_CLK
     FOR EVENT NODE_DOUBLE_CLICK
     OF CL_GUI_LIST_TREE
     IMPORTING NODE_KEY,
    HANDLE_NODE_KEY_PRESS
     FOR EVENT NODE_KEYPRESS
     OF CL_GUI_LIST_TREE
     IMPORTING NODE_KEY KEY,
*---- methods for action handling for Items
    ITEM_DBL_CLK
     FOR EVENT ITEM_DOUBLE_CLICK
     OF CL_GUI_LIST_TREE
     IMPORTING NODE_KEY ITEM_NAME,
    HANDLE_ITEM_KEY_PRESS
     FOR EVENT ITEM_KEYPRESS
     OF CL_GUI_LIST_TREE
     IMPORTING NODE_KEY ITEM_NAME KEY,
*---- Common methods for action handling
HANDLE_RIGHT_CLICK
FOR EVENT RIGHT_CLICK
OF CL_GUI_LIST_TREE,
    HANDLE_EXPAND_NO_CHILDREN
     FOR EVENT EXPAND_NO_CHILDREN
     OF CL_GUI_LIST_TREE
     IMPORTING NODE_KEY.
ENDCLASS.                    "lcl_evt_hdlr DEFINITION
      CLASS lcl_evt_hdlr IMPLEMENTATION
CLASS LCL_EVT_HDLR IMPLEMENTATION.
METHOD NODE_DBL_CLK.
this method handles the node double click event of the tree control
and shows the key of the double clicked node in a dynpro field
    G_EVENT = 'NODE_DOUBLE_CLICK'.
    G_NODE_KEY = NODE_KEY.
    G_ITEM_NAME = ' '.
ENDMETHOD.                    "node_dbl_clk
METHOD ITEM_DBL_CLK.
    G_EVENT = 'ITEM_DOUBLE_CLICK'.
    G_NODE_KEY = NODE_KEY.
    G_ITEM_NAME = ITEM_NAME.
ENDMETHOD.                    "ITEM_DBL_CLK
METHOD HANDLE_NODE_KEY_PRESS.
    G_EVENT = 'NODE_KEYPRESS'.
    G_NODE_KEY = NODE_KEY.
    G_ITEM_NAME = ' '.
    G_KEY = KEY.
ENDMETHOD.                    "HANDLE_NODE_KEY_PRESS
METHOD HANDLE_ITEM_KEY_PRESS.
    G_EVENT = 'ITEM_KEYPRESS'.
    G_NODE_KEY = NODE_KEY.
    G_ITEM_NAME = ITEM_NAME.
    G_KEY = KEY.
ENDMETHOD.                    "HANDLE_ITEM_KEY_PRESS
METHOD HANDLE_RIGHT_CLICK.
   G_EVENT = 'RIGHT_CLICK'.
ENDMETHOD.                    "handle_right_click
METHOD HANDLE_EXPAND_NO_CHILDREN.
    G_EVENT = 'EXPAND_NO_CHILDREN'.
    G_NODE_KEY = NODE_KEY.
ENDMETHOD.                    "handle_EXPAND_NO_CHILDREN
ENDCLASS.                    "lcl_evt_hdlr IMPLEMENTATION
*------   start-of-selection.
START-OF-SELECTION.
*data: G_EVT_HDLR TYPE REF TO LCL_EVT_HDLR.
CREATE OBJECT G_EVT_HDLR. "create an object for the class lcl_evt_hdlr
SET SCREEN 100.
MODULE pbo_100 OUTPUT
MODULE PBO_100 OUTPUT.
SET PF-STATUS 'BUT'.
IF G_TREE IS INITIAL.
the tree control has not yet been created
create a tree control and insert nodes into it.
    PERFORM CREATE_AND_INIT_TREE.
ENDIF.
ENDMODULE.                    "pbo_100 OUTPUT
MODULE pai_100 INPUT
MODULE PAI_100 INPUT.
DATA:RETURN_CODE TYPE I.
CL_GUI_CFW=>DISPATCH must be called if events are registered
that trigger PAI
this method calls the event handler method of an event
CALL METHOD CL_GUI_CFW=>DISPATCH
    IMPORTING
      RETURN_CODE = RETURN_CODE.
IF RETURN_CODE <> CL_GUI_CFW=>RC_NOEVENT.
    " a control event occured => exit PAI
    CLEAR G_OK_CODE.
    EXIT.
ENDIF.
*at user-command.
g_ok_code = sy-ucomm.
CASE G_OK_CODE.
    WHEN 'BACK'. " Finish program
      IF NOT G_CUSTOM_CONTAINER IS INITIAL.
        " destroy tree container (detroys contained tree control, too)
        CALL METHOD G_CUSTOM_CONTAINER->FREE
          EXCEPTIONS
            CNTL_SYSTEM_ERROR = 1
            CNTL_ERROR        = 2.
        IF SY-SUBRC <> 0.
          MESSAGE A000.
        ENDIF.
        CLEAR G_CUSTOM_CONTAINER.
        CLEAR G_TREE.
      ENDIF.
      LEAVE PROGRAM.
ENDCASE.
CAUTION: clear ok code!
CLEAR G_OK_CODE.
ENDMODULE.                    "pai_100 INPUT
*&      Form create_and_init_tree
      text
--> p1        text
<-- p2        text
FORM CREATE_AND_INIT_TREE .
DATA:NODE_TABLE TYPE TREEV_NTAB,
       ITEM_TABLE TYPE ITEM_TABLE_TYPE,
       EVENTS TYPE CNTL_SIMPLE_EVENTS,
       EVENT TYPE CNTL_SIMPLE_EVENT.
create a container for the tree control.
CREATE OBJECT G_CUSTOM_CONTAINER
   EXPORTING
    the container is linked to the custom control with the
    name 'TREE_CONTAINER' on the dynpro
     CONTAINER_NAME = 'TREE_CONTAINER'
   EXCEPTIONS
      CNTL_ERROR = 1
      CNTL_SYSTEM_ERROR = 2
      CREATE_ERROR = 3
      LIFETIME_ERROR = 4
      LIFETIME_DYNPRO_DYNPRO_LINK = 5.
IF SY-SUBRC <> 0.
    MESSAGE A000.
ENDIF.
create a list tree control
CREATE OBJECT G_TREE
   EXPORTING
    PARENT = G_CUSTOM_CONTAINER
    NODE_SELECTION_MODE = CL_GUI_LIST_TREE=>NODE_SEL_MODE_SINGLE
    ITEM_SELECTION = 'X'
    WITH_HEADERS = ' '
   EXCEPTIONS
    CNTL_SYSTEM_ERROR           = 1
     CREATE_ERROR                = 2
     FAILED                      = 3
     ILLEGAL_NODE_SELECTION_MODE = 4
     LIFETIME_ERROR              = 5.
IF SY-SUBRC <> 0.
    MESSAGE A000.
ENDIF.
*------- KEY = enter
CALL METHOD G_TREE->ADD_KEY_STROKE
    EXPORTING
      KEY               = CL_TREE_CONTROL_BASE=>KEY_ENTER
    EXCEPTIONS
      FAILED            = 1
      ILLEGAL_KEY       = 2
      CNTL_SYSTEM_ERROR = 3.
IF SY-SUBRC <> 0.
    MESSAGE W006 WITH 'ADD_KEY_STROKE'.
ENDIF.
   define the events which will be passed to the backend
node double click
EVENT-EVENTID = CL_GUI_LIST_TREE=>EVENTID_NODE_DOUBLE_CLICK.
EVENT-APPL_EVENT = 'X'.
APPEND EVENT TO EVENTS.
EVENT-EVENTID = CL_GUI_LIST_TREE=>EVENTID_ITEM_DOUBLE_CLICK.
EVENT-APPL_EVENT = 'X'.
APPEND EVENT TO EVENTS.
EVENT-EVENTID = CL_GUI_LIST_TREE=>EVENTID_NODE_KEYPRESS.
EVENT-APPL_EVENT = 'X'.
APPEND EVENT TO EVENTS.
EVENT-EVENTID = CL_GUI_LIST_TREE=>EVENTID_ITEM_KEYPRESS.
EVENT-APPL_EVENT = 'X'.
APPEND EVENT TO EVENTS.
EVENT-EVENTID = LCL_EVT_HDLR=>EVENT_RIGHT_CLICK.
EVENT-APPL_EVENT = 'X'.
APPEND EVENT TO EVENTS.
EVENT-EVENTID = CL_GUI_LIST_TREE=>EVENTID_EXPAND_NO_CHILDREN.
EVENT-APPL_EVENT = 'X'.
APPEND EVENT TO EVENTS.
*------ register the events
CALL METHOD G_TREE->SET_REGISTERED_EVENTS
    EXPORTING
      EVENTS                    = EVENTS
    EXCEPTIONS
      CNTL_ERROR                = 1
      CNTL_SYSTEM_ERROR         = 2
      ILLEGAL_EVENT_COMBINATION = 3.
IF SY-SUBRC <> 0.
    MESSAGE A000.
ENDIF.
assign event handlers in the application class to each desired events
SET HANDLER G_EVT_HDLR->NODE_DBL_CLK FOR G_TREE.
SET HANDLER G_EVT_HDLR->ITEM_DBL_CLK FOR G_TREE.
SET HANDLER G_EVT_HDLR->HANDLE_NODE_KEY_PRESS FOR G_TREE.
SET HANDLER G_EVT_HDLR->HANDLE_ITEM_KEY_PRESS FOR G_TREE.
SET HANDLER G_EVT_HDLR->HANDLE_RIGHT_CLICK FOR G_TREE.
SET HANDLER G_EVT_HDLR->HANDLE_EXPAND_NO_CHILDREN FOR G_TREE.
add some nodes to the tree control
PERFORM BUILD_NODE_AND_ITEM_TABLE USING NODE_TABLE ITEM_TABLE.
CALL METHOD G_TREE->ADD_NODES_AND_ITEMS
    EXPORTING
      NODE_TABLE                     = NODE_TABLE
      ITEM_TABLE                     = ITEM_TABLE
      ITEM_TABLE_STRUCTURE_NAME      = 'mtreeitm'
    EXCEPTIONS
      FAILED                         = 1
      CNTL_SYSTEM_ERROR              = 3
      ERROR_IN_TABLES                = 4
      DP_ERROR                       = 5
      TABLE_STRUCTURE_NAME_NOT_FOUND = 6.
IF SY-SUBRC <> 0.
    MESSAGE A000.
ENDIF.
ENDFORM.                    " create_and_init_tree
*&      Form build_node_and_item_table
      text
     -->P_NODE_TABLE text
     -->P_ITEM_TABLE text
FORM BUILD_NODE_AND_ITEM_TABLE USING
          NODE_TABLE TYPE TREEV_NTAB
          ITEM_TABLE TYPE ITEM_TABLE_TYPE.
DATA:NODE TYPE TREEV_NODE,
       ITEM TYPE MTREEITM.
build the node table
node with key 'root'.
CLEAR NODE.
NODE-NODE_KEY = 'Root'. " key of the node
CLEAR NODE-RELATKEY.    " root node has no parent node
CLEAR NODE-RELATSHIP.
NODE-HIDDEN = ' '.      " the node is visible
NODE-DISABLED = ' '.     " selectable
NODE-ISFOLDER = 'X'.    " a folder
CLEAR NODE-N_IMAGE.     " folder-/ leaf symbol in state "closed"
"use default.
CLEAR NODE-EXP_IMAGE.   " folder-/ leaf symbol in state "open"
"use default.
CLEAR NODE-EXPANDER.    " the width of the item is adjusted to its "
" content (text)
APPEND NODE TO NODE_TABLE.
node with key 'child1'.
CLEAR NODE.
NODE-NODE_KEY = 'Child1'. "key of the node
NODE-RELATKEY = 'Root'.
NODE-RELATSHIP = CL_GUI_LIST_TREE=>RELAT_LAST_CHILD.
NODE-ISFOLDER = 'X'.
APPEND NODE TO NODE_TABLE.
node with key 'Subchild1' for child1.
CLEAR NODE.
NODE-NODE_KEY = 'SubChild1'.
NODE-RELATKEY = 'Child1'.
NODE-RELATSHIP = CL_GUI_LIST_TREE=>RELAT_LAST_CHILD.
NODE-ISFOLDER = 'X'.
APPEND NODE TO NODE_TABLE.
node with key 'subchild2' for child1.
CLEAR NODE.
NODE-NODE_KEY = 'SubChild2'.
NODE-RELATKEY = 'Child1'.
NODE-RELATSHIP = CL_GUI_LIST_TREE=>RELAT_LAST_CHILD.
APPEND NODE TO NODE_TABLE.
node with key 'subchild3' for child1.
CLEAR NODE.
NODE-NODE_KEY = 'SubChild3'.
NODE-RELATKEY = 'Child1'.
NODE-RELATSHIP = CL_GUI_LIST_TREE=>RELAT_LAST_CHILD.
APPEND NODE TO NODE_TABLE.
node with key 'child2'.
CLEAR NODE.
NODE-NODE_KEY = 'Child2'. "key of the node
NODE-RELATKEY = 'Root'.
NODE-RELATSHIP = CL_GUI_LIST_TREE=>RELAT_LAST_CHILD.
NODE-ISFOLDER = 'X'.
NODE-EXPANDER = 'X'.    " The node is marked with a '+', although
" it has no children. When the user clicks on the
" + to open the node, the event expand_nc is
" fired. The programmerr can
" add the children of the
" node within the event handler of the expand_nc
" event (see callback handle_expand_nc).
APPEND NODE TO NODE_TABLE.
items of the nodes
item with key 'root'.
CLEAR ITEM.
ITEM-NODE_KEY = 'Root'.
ITEM-ITEM_NAME = '1'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT. " text item
ITEM-ALIGNMENT = CL_GUI_LIST_TREE=>ALIGN_AUTO. "the width of the item
"is adjusted to its content
ITEM-FONT = CL_GUI_LIST_TREE=>ITEM_FONT_PROP. "use proportional font
" for the item
ITEM-TEXT = 'object'.
APPEND ITEM TO ITEM_TABLE.
item with key 'child1'.
CLEAR ITEM.
ITEM-NODE_KEY = 'Child1'.
ITEM-ITEM_NAME = '11'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT.
ITEM-ALIGNMENT = CL_GUI_LIST_TREE=>ALIGN_AUTO.
ITEM-FONT = CL_GUI_LIST_TREE=>ITEM_FONT_PROP.
ITEM-TEXT = 'dynpros'.
APPEND ITEM TO ITEM_TABLE.
item with key 'child2'.
CLEAR ITEM.
ITEM-NODE_KEY = 'Child2'.
ITEM-ITEM_NAME = '12'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT.
ITEM-ALIGNMENT = CL_GUI_LIST_TREE=>ALIGN_AUTO.
ITEM-FONT = CL_GUI_LIST_TREE=>ITEM_FONT_PROP.
ITEM-TEXT = 'programme'.
APPEND ITEM TO ITEM_TABLE.
items of node with key 'Subchild1'.
CLEAR ITEM.
ITEM-NODE_KEY = 'SubChild1'.
ITEM-ITEM_NAME = '111'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT.
ITEM-LENGTH = 11.
ITEM-TEXT = 'include'.
APPEND ITEM TO ITEM_TABLE.
items of node with key 'SubChild2'.
CLEAR ITEM.
ITEM-NODE_KEY = 'SubChild2'.
ITEM-ITEM_NAME = '112'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT.
ITEM-LENGTH = 4. " the width of the item is 4 chars
ITEM-IGNOREIMAG = 'X'. " see documentation of structure treev_item
ITEM-USEBGCOLOR = 'X'.
ITEM-T_IMAGE = '@01@'.
APPEND ITEM TO ITEM_TABLE.
CLEAR ITEM.
ITEM-NODE_KEY = 'SubChild2'.
ITEM-ITEM_NAME = '113'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT.
ITEM-LENGTH = 4. " the width of the item is 4 chars
ITEM-USEBGCOLOR = 'X'.
ITEM-TEXT = '0100'.
APPEND ITEM TO ITEM_TABLE.
CLEAR ITEM.
ITEM-NODE_KEY = 'SubChild2'.
ITEM-ITEM_NAME = '114'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT.
ITEM-LENGTH = 11.
ITEM-USEBGCOLOR = 'X'.
ITEM-TEXT = ' mueller'.
APPEND ITEM TO ITEM_TABLE.
CLEAR ITEM.
ITEM-NODE_KEY = 'SubChild2'.
ITEM-ITEM_NAME = '115'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT.
ITEM-ALIGNMENT = CL_GUI_LIST_TREE=>ALIGN_AUTO.
ITEM-FONT = CL_GUI_LIST_TREE=>ITEM_FONT_PROP.
ITEM-TEXT = ' comment to dynpro 100'.
APPEND ITEM TO ITEM_TABLE.
items of node with key 'SubChild3'.
CLEAR ITEM.
ITEM-NODE_KEY = 'SubChild3'.
ITEM-ITEM_NAME = '121'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT.
ITEM-LENGTH = 20.
ITEM-IGNOREIMAG = 'X'.
ITEM-USEBGCOLOR = 'X'.
ITEM-T_IMAGE = '@02@'.
ITEM-TEXT = ' 0200 harryhirsch'.
APPEND ITEM TO ITEM_TABLE.
CLEAR ITEM.
ITEM-NODE_KEY = 'SubChild3'.
ITEM-ITEM_NAME = '122'.
ITEM-CLASS = CL_GUI_LIST_TREE=>ITEM_CLASS_TEXT.
ITEM-ALIGNMENT = CL_GUI_LIST_TREE=>ALIGN_AUTO.
ITEM-FONT = CL_GUI_LIST_TREE=>ITEM_FONT_PROP.
ITEM-TEXT = ' comment to dynpro 200'.
APPEND ITEM TO ITEM_TABLE.
ENDFORM.                    " build_node_and_item_table
also i have sent a material to ur id
I hope you will get a clear idea on events
Regards,
Sowjanya

Example programs on abap object events?

Hi Experts,
I need some example programs on abap object events.
regards,
vijay

Hi,
go thru the below program. hope it could help you.
   REPORT sapmz_hf_alv_grid .
Type pool for icons - used in the toolbar
   TYPE-POOLS: icon.
   TABLES: zsflight.
To allow the declaration of o_event_receiver before the
lcl_event_receiver class is defined, decale it as deferred in the
start of the program
   CLASS lcl_event_receiver DEFINITION DEFERRED.
G L O B A L   I N T E R N A L   T A B L E S
   *DATA: gi_sflight TYPE STANDARD TABLE OF sflight.
To include a traffic light and/or color a line the structure of the
table must include fields for the traffic light and/or the color
   TYPES: BEGIN OF st_sflight.
           INCLUDE STRUCTURE zsflight.
      Field for traffic light
   TYPES: traffic_light TYPE c.
      Field for line color
   types: line_color(4) type c.
   TYPES: END OF st_sflight.
   TYPES: tt_sflight TYPE STANDARD TABLE OF st_sflight.
   DATA: gi_sflight TYPE tt_sflight.
G L O B A L   D A T A
   DATA: ok_code         LIKE sy-ucomm,
    Work area for internal table
         g_wa_sflight    TYPE st_sflight,
    ALV control: Layout structure
         gs_layout       TYPE lvc_s_layo.
Declare reference variables to the ALV grid and the container
   DATA:
     go_grid             TYPE REF TO cl_gui_alv_grid,
     go_custom_container TYPE REF TO cl_gui_custom_container,
     o_event_receiver    TYPE REF TO lcl_event_receiver.
   DATA:
Work area for screen 200
     g_screen200 LIKE zsflight.
Data for storing information about selected rows in the grid
   DATA:
Internal table
     gi_index_rows TYPE lvc_t_row,
Information about 1 row
     g_selected_row LIKE lvc_s_row.
C L A S S E S
   CLASS lcl_event_receiver DEFINITION.
     PUBLIC SECTION.
       METHODS:
        handle_toolbar FOR EVENT toolbar OF cl_gui_alv_grid
          IMPORTING
            e_object e_interactive,
        handle_user_command FOR EVENT user_command OF cl_gui_alv_grid
          IMPORTING e_ucomm.
   ENDCLASS.
      CLASS lcl_event_receiver IMPLEMENTATION
   CLASS lcl_event_receiver IMPLEMENTATION.
     METHOD handle_toolbar.
Event handler method for event toolbar.
       CONSTANTS:
Constants for button type
         c_button_normal           TYPE i VALUE 0,
         c_menu_and_default_button TYPE i VALUE 1,
         c_menu                    TYPE i VALUE 2,
         c_separator               TYPE i VALUE 3,
         c_radio_button            TYPE i VALUE 4,
         c_checkbox                TYPE i VALUE 5,
         c_menu_entry              TYPE i VALUE 6.
       DATA:
           ls_toolbar TYPE stb_button.
Append seperator to the normal toolbar
       CLEAR ls_toolbar.
       MOVE c_separator TO ls_toolbar-butn_type..
       APPEND ls_toolbar TO e_object->mt_toolbar.
Append a new button that to the toolbar. Use E_OBJECT of
event toolbar. E_OBJECT is of type CL_ALV_EVENT_TOOLBAR_SET.
This class has one attribute MT_TOOLBAR which is of table type
TTB_BUTTON. The structure is STB_BUTTON
       CLEAR ls_toolbar.
       MOVE 'CHANGE'        TO ls_toolbar-function.
       MOVE icon_change    TO ls_toolbar-icon.
       MOVE 'Change flight' TO ls_toolbar-quickinfo.
       MOVE 'Change'        TO ls_toolbar-text.
       MOVE ' '             TO ls_toolbar-disabled.
       APPEND ls_toolbar    TO e_object->mt_toolbar.
     ENDMETHOD.
     METHOD handle_user_command.
Handle own functions defined in the toolbar
       CASE e_ucomm.
         WHEN 'CHANGE'.
           PERFORM change_flight.
       LEAVE TO SCREEN 0.
       ENDCASE.
     ENDMETHOD.
   ENDCLASS.
S T A R T - O F - S E L E C T I O N.
   START-OF-SELECTION.
     SET SCREEN '100'.
   *&      Module USER_COMMAND_0100 INPUT
   MODULE user_command_0100 INPUT.
     CASE ok_code.
       WHEN 'EXIT'.
         LEAVE TO SCREEN 0.
     ENDCASE.
   ENDMODULE.                 " USER_COMMAND_0100 INPUT
   *&      Module STATUS_0100 OUTPUT
   MODULE status_0100 OUTPUT.
     DATA:
For parameter IS_VARIANT that is sued to set up options for storing
the grid layout as a variant in method set_table_for_first_display
       l_layout TYPE disvariant,
Utillity field
       l_lines TYPE i.
After returning from screen 200 the line that was selected before
going to screen 200, should be selected again. The table gi_index_rows
was the output table from the GET_SELECTED_ROWS method in form
CHANGE_FLIGHT
     DESCRIBE TABLE gi_index_rows LINES l_lines.
     IF l_lines > 0.
       CALL METHOD go_grid->set_selected_rows
           EXPORTING
             it_index_rows = gi_index_rows.
       CALL METHOD cl_gui_cfw=>flush.
       REFRESH gi_index_rows.
     ENDIF.
Read data and create objects
     IF go_custom_container IS INITIAL.
Read data from datbase table
       PERFORM get_data.
Create objects for container and ALV grid
       CREATE OBJECT go_custom_container
         EXPORTING container_name = 'ALV_CONTAINER'.
       CREATE OBJECT go_grid
         EXPORTING
           i_parent = go_custom_container.
Create object for event_receiver class
and set handlers
       CREATE OBJECT o_event_receiver.
       SET HANDLER o_event_receiver->handle_user_command FOR go_grid.
       SET HANDLER o_event_receiver->handle_toolbar FOR go_grid.
Layout (Variant) for ALV grid
       l_layout-report = sy-repid. "Layout fo report
Setup the grid layout using a variable of structure lvc_s_layo
Set grid title
       gs_layout-grid_title = 'Flights'.
Selection mode - Single row without buttons
(This is the default mode
       gs_layout-sel_mode = 'B'.
Name of the exception field (Traffic light field) and the color
field + set the exception and color field of the table
       gs_layout-excp_fname = 'TRAFFIC_LIGHT'.
       gs_layout-info_fname = 'LINE_COLOR'.
       LOOP AT gi_sflight INTO g_wa_sflight.
         IF g_wa_sflight-paymentsum < 100000.
      Value of traffic light field
           g_wa_sflight-traffic_light = '1'.
      Value of color field:
      C = Color, 6=Color 1=Intesified on, 0: Inverse display off
           g_wa_sflight-line_color    = 'C610'.
         ELSEIF g_wa_sflight-paymentsum => 100000 AND
                g_wa_sflight-paymentsum < 1000000.
           g_wa_sflight-traffic_light = '2'.
         ELSE.
           g_wa_sflight-traffic_light = '3'.
         ENDIF.
         MODIFY gi_sflight FROM g_wa_sflight.
       ENDLOOP.
Grid setup for first display
       CALL METHOD go_grid->set_table_for_first_display
         EXPORTING i_structure_name = 'SFLIGHT'
                   is_variant       = l_layout
                   i_save           = 'A'
                   is_layout        = gs_layout
         CHANGING it_outtab        = gi_sflight.
   *-- End of grid setup -
Raise event toolbar to show the modified toolbar
       CALL METHOD go_grid->set_toolbar_interactive.
Set focus to the grid. This is not necessary in this
example as there is only one control on the screen
       CALL METHOD cl_gui_control=>set_focus EXPORTING control = go_grid.
     ENDIF.
   ENDMODULE.                 " STATUS_0100 OUTPUT
   *&      Module USER_COMMAND_0200 INPUT
   MODULE user_command_0200 INPUT.
     CASE ok_code.
       WHEN 'EXIT200'.
         LEAVE TO SCREEN 100.
         WHEN'SAVE'.
         PERFORM save_changes.
     ENDCASE.
   ENDMODULE.                 " USER_COMMAND_0200 INPUT
   *&      Form get_data
   FORM get_data.
Read data from table SFLIGHT
     SELECT *
       FROM zsflight
       INTO TABLE gi_sflight.
   ENDFORM.                    " load_data_into_grid
   *&      Form change_flight
Reads the contents of the selected row in the grid, ans transfers
the data to screen 200, where it can be changed and saved.
   FORM change_flight.
     DATA:l_lines TYPE i.
     REFRESH gi_index_rows.
     CLEAR   g_selected_row.
Read index of selected rows
     CALL METHOD go_grid->get_selected_rows
       IMPORTING
         et_index_rows = gi_index_rows.
Check if any row are selected at all. If not
table gi_index_rows will be empty
     DESCRIBE TABLE gi_index_rows LINES l_lines.
     IF l_lines = 0.
       CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
            EXPORTING
                 textline1 = 'You must choose a line'.
       EXIT.
     ENDIF.
Read indexes of selected rows. In this example only one
row can be selected as we are using gs_layout-sel_mode = 'B',
so it is only ncessary to read the first entry in
table gi_index_rows
     LOOP AT gi_index_rows INTO g_selected_row.
       IF sy-tabix = 1.
        READ TABLE gi_sflight INDEX g_selected_row-index INTO g_wa_sflight.
       ENDIF.
     ENDLOOP.
Transfer data from the selected row to screenm 200 and show
screen 200
     CLEAR g_screen200.
     MOVE-CORRESPONDING g_wa_sflight TO g_screen200.
     LEAVE TO SCREEN '200'.
   ENDFORM.                    " change_flight
   *&      Form save_changes
Changes made in screen 200 are written to the datbase table
zsflight, and to the grid table gi_sflight, and the grid is
updated with method refresh_table_display to display the changes
   FORM save_changes.
     DATA: l_traffic_light TYPE c.
Update traffic light field
Update database table
     MODIFY zsflight FROM g_screen200.
Update grid table , traffic light field and color field.
Note that it is necessary to use structure g_wa_sflight
for the update, as the screen structure does not have a
traffic light field
     MOVE-CORRESPONDING g_screen200 TO g_wa_sflight.
     IF g_wa_sflight-paymentsum < 100000.
       g_wa_sflight-traffic_light = '1'.
C = Color, 6=Color 1=Intesified on, 0: Inverse display off
       g_wa_sflight-line_color    = 'C610'.
     ELSEIF g_wa_sflight-paymentsum => 100000 AND
            g_wa_sflight-paymentsum < 1000000.
       g_wa_sflight-traffic_light = '2'.
       clear g_wa_sflight-line_color.
     ELSE.
       g_wa_sflight-traffic_light = '3'.
       clear g_wa_sflight-line_color.
     ENDIF.
     MODIFY gi_sflight INDEX g_selected_row-index FROM g_wa_sflight.
Refresh grid
     CALL METHOD go_grid->refresh_table_display.
     CALL METHOD cl_gui_cfw=>flush.
     LEAVE TO SCREEN '100'.
   ENDFORM.                    " save_changes
regards
-Rakesh

How to find the WhereUsed List for a Business Object Event?

How to find the WhereUsed List for a Business Object Event?

Can anybody let me know how to get which
Whereused function will get the data from
different Werks in multi-level?
Any sample program please!!!

TCA Business Object Events: Raise Events Program

Hi,
We are integrating two ebiz instances using SOA and both the instances currently are on 11.5.10. We have back ported patches from ebiz 12i into these instances to use TCA Business Objects functionality(Business Object API's and events). I have a few questions realted to the concurrent program "TCA Business Object Events: Raise Events Program":
1) Do I need to schedule this concurrent program to raise business object events?
2) Is there an alternate way to raise these business object events(any profiles)?
Appreciate if someone can answer these questions.
Thanks,
Sak

Hi,
We use AIA and TCA Business Object Events program to integrate from one Ebiz instance to another.
To achieve what you want I would not do anything in SOA.
In out integration TCA ends up putting messages into WF_BPEL_Q.
I would use the following process: (Assuming offline time is a possibility)
1. Retire the parts of AIA that dequeue from WF_BPEL_Q. (depending on how messages are picked up.)
2. Create a PLSQL script that dequeues all messages from WF_BPEL_Q but dosn't process them. Using relevant select statements you can dequeue by message ID and select only relevant messages
3. Run whatever process you need that puts fires the Raise Events Program
4. Run the script to dequeue the messages that does nothing with them.
5. Re-activate the parts of AIA that dequeue from WF_BPEL_Q
This should give you the desired effect. Just be careful you don't screen out messages that do need to be transfered.
Robert

Difference between busniess Event and object event

Hi All,
Can anyone explain to me what the difference between business event and object event in Beehive?
thanks

Business events are events that are exposed for integration with policies, audit, workflows, user notifications etc.
Object events are an internal-to-beehive system service that are consumed within Beehive Services and are not exposed for application or user consumption.
Richard

Business Objects - Events

Please let me know to find the where used list for a business object - event?

There are many events defined for each Business Object. But I find either none or just a few of these events for the business objects defined through the event linkages.
Only events that start a follow on process using a workflow, standard task or an FM or defined in event linkages. Not all entries available will be flagged as active. Some of these could be supplied as standard and you activate them as needed and may involve additional config steps. Some of them might have been active once and deactivated later.
I am assuming that all events for a business object must have been defined for a specific purpose and that they must be getting triggered/created somewhere.
Every object can have certain standard entries like Created, Changed etc. There could be object specific events also. There are standard SAP objects with no events defined at all. You can also extend an object with your own events. How you want to react to an event is specific to your business needs. Also, not all the events defined for an object are triggered/created. You may have to do it yourself with various tools provided by SAP. You can test what events get published for an object by activating event trace and taking the object thorough various stages.
a) Is there a way to get a where-used list for events?
One way is to look at the event linkages (txn SWETYPV) as you have already done. Another way is to txn SWU0 to simulate an event and see how the system would react to that event.
b) Are there some SAP-defined events that never get created?
Answered above.
ANd checkout this link
http://help.sap.com/saphelp_46c/helpdata/en/a5/3ec8534ac011d1894e0000e829fbbd/content.htm
Thanks,

What exactly is Object Event Repository?

Hello,
I´ve just read a marketing article about the new SAP Object Event Repository. Precisely because it is a marking article the key-facts and functions are missing. It sounds like a reduced AII with extended database functions for Tag-tracking. Can somebody explain the benefit, technology and functions of the OER? What is the different between AII and OER?
Thank you, Bastian

Hi,
SAP OER serves as a system of record for uniquely identified objects (like EPCs). So you are right in saying it like an extended database functions for tag tracking.
But it will not reduce the AII functionalities. AII will still remain as the data capturing application (tag read) and the repository of these reads for the tags will be maintained in the OER. So these two are two different applications.
OER allows for tracking any id or document for which information has been sent from AII. OER will also have the capability of generating reports (business intelligence) for these data reads maintained in its repository.
SAP has recently unveiled is PTA (Product Tracking & Authentication) feature in OER. Read at http://www.sap.com/company/press/press.epx?PressID=7440
Since this product has not come in the market yet, we need to wait till the time of its release for documents on the product. Then we might know the exact benefits/technology on OER.
Thanks,
Ashish

Object Event: RollOver

Similar Messages

Maybe you are looking for