07-20-2007 3:43 PM
Inside a custom piece of code, I have duplicated the "GOS ToolBox" toolbar that SAP displays inside IW22 for attaching documents, pictures, etc. to notifications. The code to pop this toolbox isn't much:
CLASS lcl_event_receiver IMPLEMENTATION.
METHOD on_function_selected.
DATA:
ls_lporb TYPE sibflporb,
ls_lpor TYPE sibflpor,
ls_borident TYPE boriden
CASE fcode.
WHEN '%GOS_TOOLBOX'.
ls_borident-objkey = viqmel-qmnum.
ls_borident-objtype = 'BUS2038'.
CREATE OBJECT go_manager.
CALL METHOD go_manager->display_toolbox
EXPORTING
is_object = ls_borident
is_bc_object = ls_lpor
EXCEPTIONS
OTHERS = 2.
ENDCASE.
ENDMETHOD. "lcl_my_event_handler
But when my toolbox pops, it does not have the same functionality as the GOS toolbox that pops under SAP control in IW22 itself.
In particular, the "create menu" in my toolbox only has "Store Business Document" active. But the "create menu" in the SAP IW22 toolbox has all of the following active:
<b>Create document
Create note
Create external document (URL)
Store business document</b>
So my questions are:
1) where is SAP IW22 getting its "model" for what's functional in the create menu?
2) do I need to set up a "customer version" of this "model" to duplicate the SAP functionality?
3) if so, is this a "config" function or is it done somewhere else ???
I've got less than 36 hours to figure this one out, so any advice would be helpful.
Thanks for considering this matter
djh
07-20-2007 5:25 PM
Ferry and Rich -
Thanks very much for taking the time. I've tagged each of your replies with 6 because they were each useful in their own way: 1) Ferry - you gave me the links which led to the BADI (see below); 2) Rich - you confirmed my suspicion that this is a "privs" question, not a code question.
Anyway, it turns out that what I really need to do is implement BADI "GOS_SRV_REQUEST" to get accesibility to the methods of CL_BDS_DOCUMENT_SET.
Reason why I have to go this way is that the customer wants to maintain picture attachments in IW22 via the standard SAP toolbox invoked from the title bar,
but wants me to display the first three attached pictures in the fifth custom subscreen of an IW22 custom tab
So what I have to do is use the get_info method of CL_BDS_DOCUMENT_SET to
find out what's there, and then figure out how to retrieve the pictures and pop them into picture controls.
I will probably be posting subsequent separate questions on these matters when I get there ... hope you'll be checking over the week-end once in a while ... heh heh heh.
Anyway, thanks again to both of you and Rich - to answer your question from last night - yes - two weeks, 1 person, five subscreens with as many longtext edit controls to be retrieved from SAPEditor, plus this picture nonsense. It's a wonderful learning experience, but a little stressful.
Regards
djh
07-20-2007 4:01 PM
Hi David,
Please check documents perhaps they may help.
They seem a lot of code driven (technical) than config driven (functional).
I never work on GOS area and perhaps one day I may ask you
http://www.geocities.com/rmtiwari/Resources/Training/BusinessWorkflow/SAPApplicationDevelopment.pdf
Regards,
Ferry Lianto
07-20-2007 4:27 PM
David,
I've tested the following coding in both a 46c system as well as a NetWeaver 7.0 system. In both cases, I get all options under "Create" except for the last one.
REPORT zrich_0001.
data: docking type ref to cl_gui_docking_container.
data: go_manager type ref to cl_gos_manager.
data: ls_borident type borident.
data: repid type sy-repid.
parameters: p_check.
at selection-screen output.
repid = sy-repid.
create object docking
exporting repid = repid
dynnr = sy-dynnr
side = docking->dock_at_left
extension = 1500.
ls_borident-objkey = '000010000001'.
ls_borident-objtype = 'BUS2038'.
create object go_manager.
call method go_manager->display_toolbox
exporting
io_container = docking
is_object = ls_borident
exceptions
others = 2.
Regards
Rich Heilman
07-20-2007 5:25 PM
Ferry and Rich -
Thanks very much for taking the time. I've tagged each of your replies with 6 because they were each useful in their own way: 1) Ferry - you gave me the links which led to the BADI (see below); 2) Rich - you confirmed my suspicion that this is a "privs" question, not a code question.
Anyway, it turns out that what I really need to do is implement BADI "GOS_SRV_REQUEST" to get accesibility to the methods of CL_BDS_DOCUMENT_SET.
Reason why I have to go this way is that the customer wants to maintain picture attachments in IW22 via the standard SAP toolbox invoked from the title bar,
but wants me to display the first three attached pictures in the fifth custom subscreen of an IW22 custom tab
So what I have to do is use the get_info method of CL_BDS_DOCUMENT_SET to
find out what's there, and then figure out how to retrieve the pictures and pop them into picture controls.
I will probably be posting subsequent separate questions on these matters when I get there ... hope you'll be checking over the week-end once in a while ... heh heh heh.
Anyway, thanks again to both of you and Rich - to answer your question from last night - yes - two weeks, 1 person, five subscreens with as many longtext edit controls to be retrieved from SAPEditor, plus this picture nonsense. It's a wonderful learning experience, but a little stressful.
Regards
djh
07-20-2007 5:47 PM
07-20-2007 6:18 PM
Hi David, thanks for shipping the complete code over. I have found your problem, and it is quite an easy fix. No, need to do anything more to your coding other than this.
In your global definitions, you have....
data: GO_MANAGER Type Ref To CL_GOS_VIEW_MANAGER.
Instead, use its subclass.....
data: GO_MANAGER Type Ref To CL_GOS_MANAGER.
You should then see all of the options(except last one) in your toolbox.
Regards,
Rich Heilman
07-20-2007 5:26 PM
07-20-2007 6:21 PM