Graph - Hierarchical Layout
Hello,
I'm searching an algorithme (like the Sugiyama algorithme) made in Java.
It's for laying out the elements of a graph, with a hierarchical layout.
Is there somebody who know such program ?
And, I have another question :
I don't think that there is a package in the JDK for the graph, with Nodes, Edges, Ports, Groups and Layouts...
Will be exist this sort of package in the futur ?
Thanks
Hi,
Thanks for the prompt reply. I'm looking to incorporate the algorithm into my code. Do you know of anywhere, or anyone who can give me code or even show me examples?
Thanks in advance.
Colum
Similar Messages
-
How to Draw a graph Using layout In a module pool Program
Hello Friends
How to Represent a Graph in the layout in a module pool program.
Plz suggest me.
Thanking you all
lavanyaTHIS IS AN EXAMPLE PROGRAM FOR GRAPHICS.
Run this program & see whether it will be useful for u or not.
before running dont forget to set the pf status.
after copying double click the pf status & in application tool bar. give function code like this.
PF07 - for 2d graph.
PF06 - for 3d
PF05 - for 4d
DATA: BEGIN OF DATA OCCURS 1,
P TYPE P,
END OF DATA.
--- options-table -
DATA: BEGIN OF OPTS OCCURS 1,
C(80) TYPE C,
END OF OPTS.
DATA: BEGIN OF TDIM1 OCCURS 1,
C(80) TYPE C,
END OF TDIM1.
DATA: BEGIN OF TDIM2 OCCURS 1,
C(80) TYPE C,
END OF TDIM2.
DATA: BEGIN OF TDIM3 OCCURS 1,
C(80) TYPE C,
END OF TDIM3.
DATA: BEGIN OF MAX OCCURS 1,
D1(3) TYPE P VALUE 4,
D2(3) TYPE P VALUE 5,
D3(3) TYPE P VALUE 6,
END OF MAX.
DATA: TYEAR1(5) VALUE '#1991',
TYEAR2(5) VALUE '#1992',
TYEAR3(5) VALUE '#1993',
TYEAR4(5) VALUE '#1994'.
DATA: TPROD1(9),
TPROD2(9),
TPROD3(9),
TPROD4(9),
TPROD5(9).
TPROD1 = TEXT-P01.
TPROD2 = TEXT-P02.
TPROD3 = TEXT-P03.
TPROD4 = TEXT-P04.
TPROD5 = TEXT-P05.
DATA: TLAND1(20),
TLAND2(20),
TLAND3(20),
TLAND4(20),
TLAND5(20),
TLAND6(20).
TLAND1 = TEXT-L01.
TLAND2 = TEXT-L02.
TLAND3 = TEXT-L03.
TLAND4 = TEXT-L04.
TLAND5 = TEXT-L05.
TLAND6 = TEXT-L06.
DATA: INDEX LIKE SY-INDEX.
DATA: MAXD(3) TYPE P.
DATA: TYP.
FIELD-SYMBOLS: <F>.
SET PF-STATUS 'GRAF'.
PERFORM FILL_DATA.
MAXD = MAX-D1 * MAX-D2.
*{listdisplay
display of a list: *
for 5 countries each 4 colums (years) and 5 lines (products)
WRITE: / TLAND1.
INDEX = 1.
PERFORM LISTE.
SKIP.
ULINE.
WRITE: / TLAND2.
INDEX = MAXD + 1.
PERFORM LISTE.
NEW-PAGE.
WRITE: / TLAND3.
INDEX = 2 * MAXD + 1.
PERFORM LISTE.
SKIP.
ULINE.
WRITE: / TLAND4.
INDEX = 3 * MAXD + 1.
PERFORM LISTE.
NEW-PAGE.
WRITE: / TLAND5.
INDEX = 4 * MAXD + 1.
PERFORM LISTE.
SKIP.
ULINE.
WRITE: / TLAND6.
INDEX = 5 * MAXD + 1.
PERFORM LISTE.
PF05: 4D-graphic, general function-module *
AT PF05.
REFRESH OPTS.
--- first screen: selection -
WRITE 'FIFRST = PU' TO OPTS-C. APPEND OPTS.
--- 2D-graphic-type: perspective bars -
WRITE 'P2TYPE = TD' TO OPTS-C. APPEND OPTS.
--- kind of colours: regular -
WRITE 'P3CTYP = PL' TO OPTS-C. APPEND OPTS.
*--- dimension 1
REFRESH TDIM1.
MOVE TYEAR1 TO TDIM1.
APPEND TDIM1.
MOVE TYEAR2 TO TDIM1.
APPEND TDIM1.
MOVE SPACE TO TDIM1.
APPEND TDIM1.
MOVE TYEAR4 TO TDIM1.
APPEND TDIM1.
*--- dimension 2
REFRESH TDIM2.
MOVE SPACE TO TDIM2.
APPEND TDIM2.
MOVE TPROD2 TO TDIM2.
APPEND TDIM2.
MOVE TPROD3 TO TDIM2.
APPEND TDIM2.
MOVE TPROD4 TO TDIM2.
APPEND TDIM2.
MOVE SPACE TO TDIM2.
APPEND TDIM2.
*--- dimension 3
REFRESH TDIM3.
MOVE TLAND1 TO TDIM3.
APPEND TDIM3.
MOVE SPACE TO TDIM3.
APPEND TDIM3.
MOVE TLAND3 TO TDIM3.
APPEND TDIM3.
MOVE TLAND4 TO TDIM3.
APPEND TDIM3.
MOVE SPACE TO TDIM3.
APPEND TDIM3.
MOVE SPACE TO TDIM3.
APPEND TDIM3.
CALL FUNCTION 'GRAPH_MATRIX'
EXPORTING
TITL = TEXT-VGL
VALT = 'DM'
DIM1 = TEXT-J00
DIM2 = TEXT-P00
DIM3 = TEXT-L00
TABLES
DATA = DATA
TDIM1 = TDIM1
TDIM2 = TDIM2
TDIM3 = TDIM3
OPTS = OPTS.
PF06: 3D-graphic general function-module *
AT PF06.
REFRESH OPTS.
--- first screen: selection -
WRITE 'FIFRST = PU' TO OPTS-C. APPEND OPTS.
--- 2D-graphic-Type: perspective bars -
WRITE 'P2TYPE = TD' TO OPTS-C. APPEND OPTS.
--- kind of colours: regular -
WRITE 'P3CTYP = PL' TO OPTS-C. APPEND OPTS.
*--- dimension 1
REFRESH TDIM1.
MOVE TYEAR1 TO TDIM1.
APPEND TDIM1.
MOVE SPACE TO TDIM1.
APPEND TDIM1.
MOVE TYEAR3 TO TDIM1.
APPEND TDIM1.
MOVE TYEAR4 TO TDIM1.
APPEND TDIM1.
*--- dimension 2
REFRESH TDIM2.
MOVE TPROD1 TO TDIM2.
APPEND TDIM2.
MOVE SPACE TO TDIM2.
APPEND TDIM2.
MOVE TPROD3 TO TDIM2.
APPEND TDIM2.
MOVE SPACE TO TDIM2.
APPEND TDIM2.
MOVE TPROD5 TO TDIM2.
APPEND TDIM2.
REFRESH TDIM3.
CALL FUNCTION 'GRAPH_MATRIX'
EXPORTING
TITL = TEXT-VGL
VALT = 'DM'
DIM1 = TEXT-J00
DIM2 = TEXT-P00
TABLES
DATA = DATA
TDIM1 = TDIM1
TDIM2 = TDIM2
TDIM3 = TDIM3
OPTS = OPTS.
PF07: 2D-graphic general function-module *
AT PF07.
REFRESH OPTS.
--- first screen: selection -
WRITE 'FIFRST = PU' TO OPTS-C. APPEND OPTS.
--- 2D-graphic-type perspective bars -
WRITE 'P2TYPE = TD' TO OPTS-C. APPEND OPTS.
--- kind of colour: regular -
WRITE 'P3CTYP = PL' TO OPTS-C. APPEND OPTS.
*--- dimension 1
REFRESH TDIM1.
MOVE TYEAR1 TO TDIM1.
APPEND TDIM1.
MOVE SPACE TO TDIM1.
APPEND TDIM1.
MOVE TYEAR3 TO TDIM1.
APPEND TDIM1.
MOVE TYEAR4 TO TDIM1.
APPEND TDIM1.
REFRESH TDIM2.
REFRESH TDIM3.
CALL FUNCTION 'GRAPH_MATRIX'
EXPORTING
TITL = TEXT-VGL
VALT = 'DM'
DIM1 = TEXT-J00
TABLES
DATA = DATA
TDIM1 = TDIM1
TDIM2 = TDIM2
TDIM3 = TDIM3
OPTS = OPTS.
FORM LISTE *
displays a list with turnover figures *
(products and years) *
FORM LISTE.
DATA: CNT_MOD LIKE SY-TABIX.
DATA: CNT_DIV LIKE SY-TABIX.
WRITE: / TEXT-P00,22 TYEAR1,39 TYEAR2,56 TYEAR3, 73 TYEAR4.
SKIP 2.
DO MAXD TIMES.
READ TABLE DATA INDEX INDEX.
IF SY-SUBRC NE 0. EXIT. ENDIF.
INDEX = INDEX + 1.
CNT_MOD = SY-INDEX MOD MAX-D1.
CNT_DIV = SY-INDEX DIV MAX-D1.
IF CNT_MOD EQ 1.
CASE CNT_DIV.
WHEN 0.
WRITE: / TPROD1, ' '.
WHEN 1.
WRITE: / TPROD2, ' '.
WHEN 2.
WRITE: / TPROD3, ' '.
WHEN 3.
WRITE: / TPROD4, ' '.
WHEN 4.
WRITE: / TPROD5, ' '.
ENDCASE.
ENDIF.
WRITE: DATA-P.
ENDDO.
ENDFORM.
FORM FILL_DATA *
fills the datatable *
FORM FILL_DATA.
DATA-P = 153470.
APPEND DATA.
DATA-P = 243470.
APPEND DATA.
DATA-P = 124567.
APPEND DATA.
DATA-P = 179037.
APPEND DATA.
DATA-P = 234980.
APPEND DATA.
DATA-P = 287513.
APPEND DATA.
DATA-P = 253430.
APPEND DATA.
DATA-P = 223440.
APPEND DATA.
DATA-P = 24567.
APPEND DATA.
DATA-P = 180037.
APPEND DATA.
DATA-P = 129830.
APPEND DATA.
DATA-P = 145530.
APPEND DATA.
DATA-P = 132470.
APPEND DATA.
DATA-P = 453470.
APPEND DATA.
DATA-P = 24456.
APPEND DATA.
DATA-P = 119807.
APPEND DATA.
DATA-P = 288710.
APPEND DATA.
DATA-P = 166656.
APPEND DATA.
DATA-P = 300430.
APPEND DATA.
DATA-P = 723110.
APPEND DATA.
DATA-P = 22767.
APPEND DATA.
DATA-P = 195522.
APPEND DATA.
DATA-P = 38970.
APPEND DATA.
DATA-P = 89635.
APPEND DATA.
DATA-P = 166970.
APPEND DATA.
DATA-P = 401470.
APPEND DATA.
DATA-P = 29967.
APPEND DATA.
DATA-P = 112957.
APPEND DATA.
DATA-P = 37860.
APPEND DATA.
DATA-P = 77450.
APPEND DATA.
DATA-P = 253150.
APPEND DATA.
DATA-P = 343570.
APPEND DATA.
DATA-P = 768867.
APPEND DATA.
DATA-P = 236790.
APPEND DATA.
DATA-P = 122750.
APPEND DATA.
DATA-P = 328760.
APPEND DATA.
DATA-P = 292150.
APPEND DATA.
DATA-P = 356570.
APPEND DATA.
DATA-P = 268867.
APPEND DATA.
DATA-P = 36790.
APPEND DATA.
DATA-P = 125680.
APPEND DATA.
DATA-P = 178893.
APPEND DATA.
DATA-P = 333150.
APPEND DATA.
DATA-P = 373570.
APPEND DATA.
DATA-P = 168867.
APPEND DATA.
DATA-P = 226790.
APPEND DATA.
DATA-P = 278940.
APPEND DATA.
DATA-P = 177784.
APPEND DATA.
DATA-P = 234150.
APPEND DATA.
DATA-P = 296570.
APPEND DATA.
DATA-P = 233867.
APPEND DATA.
DATA-P = 16790.
APPEND DATA.
DATA-P = 125590.
APPEND DATA.
DATA-P = 208760.
APPEND DATA.
DATA-P = 113150.
APPEND DATA.
DATA-P = 388570.
APPEND DATA.
DATA-P = 565867.
APPEND DATA.
DATA-P = 211790.
APPEND DATA.
DATA-P = 277480.
APPEND DATA.
DATA-P = 277489.
APPEND DATA.
DATA-P = 53470.
APPEND DATA.
DATA-P = 321560.
APPEND DATA.
DATA-P = 452456.
APPEND DATA.
DATA-P = 174695.
APPEND DATA.
DATA-P = 277590.
APPEND DATA.
DATA-P = 177490.
APPEND DATA.
DATA-P = 153470.
APPEND DATA.
DATA-P = 467560.
APPEND DATA.
DATA-P = 222456.
APPEND DATA.
DATA-P = 198695.
APPEND DATA.
DATA-P = 99470.
APPEND DATA.
DATA-P = 100340.
APPEND DATA.
DATA-P = 11470.
APPEND DATA.
DATA-P = 323560.
APPEND DATA.
DATA-P = 434456.
APPEND DATA.
DATA-P = 224695.
APPEND DATA.
DATA-P = 277490.
APPEND DATA.
DATA-P = 467890.
APPEND DATA.
DATA-P = 953470.
APPEND DATA.
DATA-P = 67560.
APPEND DATA.
DATA-P = 298456.
APPEND DATA.
DATA-P = 98695.
APPEND DATA.
DATA-P = 577900.
APPEND DATA.
DATA-P = 199490.
APPEND DATA.
DATA-P = 18470.
APPEND DATA.
DATA-P = 390560.
APPEND DATA.
DATA-P = 411456.
APPEND DATA.
DATA-P = 94695.
APPEND DATA.
DATA-P = 182000.
APPEND DATA.
DATA-P = 260570.
APPEND DATA.
DATA-P = 367356.
APPEND DATA.
DATA-P = 231850.
APPEND DATA.
DATA-P = 436645.
APPEND DATA.
DATA-P = 346650.
APPEND DATA.
DATA-P = 82500.
APPEND DATA.
DATA-P = 300560.
APPEND DATA.
DATA-P = 467109.
APPEND DATA.
DATA-P = 161850.
APPEND DATA.
DATA-P = 356470.
APPEND DATA.
DATA-P = 198840.
APPEND DATA.
DATA-P = 199000.
APPEND DATA.
DATA-P = 340570.
APPEND DATA.
DATA-P = 127356.
APPEND DATA.
DATA-P = 591850.
APPEND DATA.
DATA-P = 287460.
APPEND DATA.
DATA-P = 299770.
APPEND DATA.
DATA-P = 12500.
APPEND DATA.
DATA-P = 230560.
APPEND DATA.
DATA-P = 437109.
APPEND DATA.
DATA-P = 191850.
APPEND DATA.
DATA-P = 36780.
APPEND DATA.
DATA-P = 78789.
APPEND DATA.
DATA-P = 282000.
APPEND DATA.
DATA-P = 270570.
APPEND DATA.
DATA-P = 567356.
APPEND DATA.
DATA-P = 31850.
APPEND DATA.
DATA-P = 92410.
APPEND DATA.
DATA-P = 121350.
APPEND DATA.
DATA-P = 67356.
APPEND DATA.
DATA-P = 431891.
APPEND DATA.
ENDFORM. -
BPC scaling factor off and hierarchical layout
Hi Experts,
I have the below queries in connection with the input schedules in BPC: -
1. Scaling factor: -
Can we input numbers (manually) which are in Lacs ('00000)?
2. Lets say I have two dimensions in the leads columns of a manual entry layout (input schedule). Can I have them in a heirarchical manner as below: -
GL Account 1
Customer 1
Customer 2
GL Account 2
Customer1
Customer4
Customer5
If yes, can the layout be collapsible on 'GL Account' as per above layout?
Thanks for your answers
Ragards,
SSCHi,
I dont think this will be possible. We can scale the value to '000s or '000,000s. But I was never able to scale it to '00,000s.
So, the approach can be to round the value using the round function.
Hope this helps. -
Script for overriding category axis tick marks in graphs?
Hello!
We are introducing a new graph design, but has a problem with not being able to override the tick marks in the category axis in Illustrator CS5.
A typical graph (line layout) can have 250 observations, and since we have the tick marks on full width, the graph gets "crowded" with black lines.
In the value axis there is possibilites for overriding the values, but not on the category axis.
Is there any way to script so that the tick marks in the category axis can be reduced/overrided to e.g. 1 in 20?
Please help!Script has NO access to live graph data… It can only break them… then fish in the group for bits…
-
Hello!
We are introducing a new graph design, but has a problem with not being able to override the tick marks in the category axis in Illustrator CS5.
A typical graph (line layout) can have 250 observations, and since we have the tick marks on full width, the graph gets "crowded" with black lines.
In the value axis there is possibilites for overriding the values, but not on the category axis.
Is there any way to script so that the tick marks in the category axis can be reduced/overrided to e.g. 1 in 20?
Please help!Script has NO access to live graph data… It can only break them… then fish in the group for bits…
-
External characteristics and postable nodes in BW hierarchy in BPS layout
Hi!
Short question: If using a hierarchical layout in BW-BPS what are the constraints on the hierarchy for values to be able to be planned on the individual levels of the hierarchy?
Typically if one has a product hierarchy with one hierarchy basic characteristic: product and an external characteristic: product group which are connected in a hierarchy. How can values be planned on the product group level? And how does this relate to postable nodes in the BW documentation: http://help.sap.com/saphelp_nw04/helpdata/en/c1/493d3854129f68e10000009b38f8cf/content.htm. Is it only postable nodes that can be planned?
Regards,
ChristianChristian,
The attached document would answer most of your questions.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20plan%20in%20bps%20using%20hierarchies%20with%20several%20characteristics.pdf
Hope this helps.
Cheers
Srini -
CUSTOMIZING GRAPH USING XML AND SRW.APPLY_DEFINITION
Hello,
I'm trying to use the document
http://www.cs.uvm.edu/oracle9doc/appdev.901/a88894/adx14rep.htm#1017323
and trying to modify a graph property. I keep getting "Rep-6106 Error in
Report Definition at Line 1", whenever I add the graph tag.
Is graph allowed to be changed through XML and SRW.APPLY_DEFINITION?
Here's how I'm giving it in the report:
'<report name="esummarytestg" DTDVersion="1.0">
<layout>
<section name="main">
<field name="F_1" source="ACTIVE_INSTANCES" textColor="red">
<graph name="CT_2">
<geometryInfo x="0.25000" y="0.25000" width="9.06250" height="3.68750" />
<generalLayout verticalElasticity="variable"
horizontalElasticity="variable" />
<graphDefinition>
<![CDATA[
<rw:graph id="CT_2" src="G_RTG" groups="RTG"
dataValues="NUM_OF_WEEKS">
<!--
<?xml version="1.0" ?>
<Graph version="3.2.0.22">
<LegendArea automaticPlacement="AP_NEVER"
position="LAP_BOTTOM"/>
<MarkerText visible="true"/>
<SeriesItems defaultFitlineType="FT_NONE"/>
</Graph>
-->
</rw:graph>
]]>
</graphDefinition>
</graph>
</section>
</layout>
<customize>
</customize>
</report>'Come on, guys. Help! :(
-
The option to create a web gallery from lightroom is great.
I only miss the possibility to create not only one gallery level, but a hierarchical layout such as I can do with the collections. Thus it would be really useful to create a structural web-gallery sorted e.g. by countries or themes directly from within Lightroom.if only it was possible to use the collections as the "folder structure" for the export.
Maybe Adobe can consider adding in the Export Location section a new option like 'Put in Subfolder' called 'Put in Current Collection Folder' which will export the images to folders named after the collection hierarchy or have a parameter that can be used that will bring back the collection hierarchy.
I would appreciate if Adobe can kindly comment on this or consider creating a function to check the collection set\collection associated with an image. -
Hi,
I'm new to this forum and to javafx, so hi everybody :-)
I'm currently evaluating possible client technologies for a customer that is planning to create an application to edit big annotated graphs with a fixed layout.
Basically, those graphs consist of lines between nodes and "glyphs" denoting various annotations arranged on those lines.
Graphs are sized in the range of about 10.000 to 1.000.000 displayable objects, but not more than 1.000 visible at the same time.
I was able to build a prototype using javafx and encountered some performance issues with scrolling, panning, rotating and zooming a test graph that consists of about 40.000 javafx.Nodes. Those nodes are partially arranged hierarchically according to their position.
The hardware my customer uses does not support hardware accelerated rendering and the customer is not willing to upgrade just for that application, so I had to optimize.
When I tried to enable caching for areas in my graph, the performance for scrolling and panning was OK, but for rotating and zooming it wasn't. In addition I ran into problems when zooming in too far - probably because of the size of the cached images involved.
During my experiments I found out that it was possible to markedly improve performance for all operations mentioned above by selectively turning subareas of the graph invisible.
Consequently, my next try was to add a ChangeListener to the hvalueProperty of the enclosing ScrollPane that selectively toggles the visibility of subgraphs to show only those near the current viewport (aided by a data structure to give me quick access to subregions by position).
This works well except for one thing:
Toggleing the visiblilty of a subgraph via setVisible() invokes a layout pass in the scene graph that makes my viewport jump around during scrolling and panning.
I already added a background rectangle to the ScrollPane's content Group to avoid a change of the bounds of the content. Still, when the visibility of one subgraph is toggled, the scene jumps to an incorrect position for one mouse event and jumps back after that.
I also already tried to declare the subregions unmanaged - this didn't change anything.
h3. So finally, my questions:
1) Are there other means of performance optimizations built into the framework I'm not aware of?
2) Is it possible to subclass Group in a way that allows me to set its visibility without triggering the properties dependents? (Since the invisibility is a techincal optimization and not a real property of the graph, a layout pass is neither necessary nor desired).
3) Are any optimizations of this kind planned for those of us that cannot use hardware acceleration (i.g. arrange the children of a Group in a quad-tree and process only the visible parts)?
4) Would hardware acceleration even help here?
5) Is anyone aware of other means to performance tweak very large scene graphs in javafx?
6) Is the jumping of the viewport a bug I should enter into JIRA ?
Thank you for following my ramblings up to this point and thank you for your help (if you do help ;-) ).Cool, i didnt realize there was an Opengl pipeline for java2d in the 1.5 api =)
And i who got the LWJGL library to play with, seems like overkill, gonna try it out someday!
Thx for the replies, the game progresses good and i got some cool features that is gonna be implemented.
At this point i got a full working editor with easy file loading,monster/waypoint system, able to choose between 3 different towers and placing them on the playfield, upgrading 4 different aspects of every tower or sell them, kill monsters -> gain money/kills, monsters can finish the map and thus reducing number of lives of the player until game over. So basically i just need a lot of graphics and create more types of monsters/turrets with cool effects. (got homing missiles/slowing shots and normal bullets atm) and figure out how to get a nice background working on my current playground, and then probably some sweet menu to start the game from =) Ofc some balancing needs to be done, with respect to monster HP and towers damage etc. Anyone interested in creating graphics for monsters/towers/projectiles for this project are free to contact me and get credit for their work if this shit ever comes out to be any good :P -
How do I move a page to a new location that is offscreen to the left or right on the planning screen
When I'm in the planning screen mode, even though I have the thumbnails set on their smallest size, my website is so large that the branches of the hierarchal layout of webpages and their various subpages stretch out to the left and right far distances off the screen. When I try to move one of the little rectangular webpage icons in the hierarchal layout in Plan Screen mode, I can't move it off screen to the left or right to change its position in my website's horizontal menu. In other words, even at the smallest setting for the icon webpage thumbnails, there's so many icons that they go off page and I can't move a webpage icon to a position that is currently off-screen to the left or right in the menu layout.
Any ideas how to do that? Is there a non-graphical way to do it? Thanks!!!Your best bet is to reduce the thumbnail size to the smallest, then turn off thumbnails (to speed redraw), then drag in multiple steps, scrolling the Plan view each time. In the upcoming release of Muse (June 17th) you will be able to collapse vertical stacks of pages, which will means your Plan view won't be as wide. If you collapse each stack, you will only see the top level pages, and you won't have to scroll as many times. Or maybe they will all fit. What you really need is autoscroll in Plan view, which we don't currently have.
Paul Sorrick
Muse Engineering -
Cant printing of a logo in a script.
hi all,
i have printed everyting in a script except a logo in the window assigned to that .
instead it is printing its logoname in that.
i went to se38 and typed medruck and i copied everything in that .but all of it cant print.
so , tell me how to print that .HI jyothsna,
we are using ECC 6.0 version..
when i cpoy "rvorder 01" to "zrvorder01"
every thing is copied into my sscript with eng lang.
after uploading the logo into se78 i', trying to create a graph window in script.
it is giving no errors but..
1.creating elements is ged out..
2. when i 'm trying to create a graph from layout it is not giving options to create
her i want to create a seperate window for company logo...
thanks in advance... -
Hi experts
when I run Network UI Element
to presnt org Chart
I get in IE->Tools->Java Console
the follow error:
<<<--- Applet.destroy(): AppWin0/JNET --->>>
<<<--- EXIT for AppWin0/JNET --->>>
java.lang.NullPointerException
at sun.plugin.javascript.ocx.JSObject.eval(Unknown Source)
at com.sap.tc.webdynpro.ace.Acf2JavaScriptClient$1.run(Acf2JavaScriptClient.java:55)
at java.lang.Thread.run(Unknown Source)
ACF 7.1000.0.71
<<< frog.jar: version 5.4.6 02/01/06 sap.theme: null >>>this is the file:
// This file has been generated partially by the Web Dynpro Code Generator.
// MODIFY CODE ONLY IN SECTIONS ENCLOSED BY @@begin AND @@end.
// ALL OTHER CHANGES WILL BE LOST IF THE FILE IS REGENERATED.
package co.il.bnhp;
// IMPORTANT NOTE:
// ALL IMPORT STATEMENTS MUST BE PLACED IN THE FOLLOWING SECTION ENCLOSED
// BY @@begin imports AND @@end. FURTHERMORE, THIS SECTION MUST ALWAYS CONTAIN
// AT LEAST ONE IMPORT STATEMENT (E.G. THAT FOR IPrivateOrgTree).
// OTHERWISE, USING THE ECLIPSE FUNCTION "Organize Imports" FOLLOWED BY
// A WEB DYNPRO CODE GENERATION (E.G. PROJECT BUILD) WILL RESULT IN THE LOSS
// OF IMPORT STATEMENTS.
//@@begin imports
import java.io.ByteArrayInputStream;
import java.io.File;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.io.StringWriter;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.parsers.FactoryConfigurationError;
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.transform.OutputKeys;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerFactoryConfigurationError;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.sax.SAXSource;
import javax.xml.transform.stream.StreamResult;
import org.w3c.dom.DOMException;
import org.w3c.dom.DOMImplementation;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Entity;
import org.w3c.dom.Node;
import org.w3c.dom.Text;
import org.xml.sax.SAXException;
import co.i.bnhp.model.Zhr_Rfc_Disp_Manger_Employees2_Input;
import co.il.bnhp.wdp.IPrivateOrgTree;
import co.il.bnhp.wdp.IPublicOrgTree;
import com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException;
import com.sap.tc.webdynpro.progmodel.api.WDResourceFactory;
import com.sap.tc.webdynpro.services.sal.deployment.api.WDAliasResolvingException;
import com.sap.tc.webdynpro.services.sal.url.api.WDURLGenerator;
import com.sap.tc.webdynpro.services.sal.url.api.WDWebResource;
import com.sap.tc.webdynpro.services.sal.url.api.WDWebResourceType;
//@@end
//@@begin documentation
//@@end
public class OrgTree
Logging location.
private static final com.sap.tc.logging.Location logger =
com.sap.tc.logging.Location.getLocation(OrgTree.class);
static
//@@begin id
String id = "$Id$";
//@@end
com.sap.tc.logging.Location.getLocation("ID.com.sap.tc.webdynpro").infoT(id);
Private access to the generated Web Dynpro counterpart
for this controller class. </p>
Use <code>wdThis</code> to gain typed access to the context,
to trigger navigation via outbound plugs, to get and enable/disable
actions, fire declared events, and access used controllers and/or
component usages.
@see co.il.bnhp.wdp.IPrivateOrgTree for more details
private final IPrivateOrgTree wdThis;
Root node of this controller's context. </p>
Provides typed access not only to the elements of the root node
but also to all nodes in the context (methods node<i>XYZ</i>())
and their currently selected element (methods current<i>XYZ</i>Element()).
It also facilitates the creation of new elements for all nodes
(methods create<i>XYZ</i>Element()). </p>
@see co.il.bnhp.wdp.IPrivateOrgTree.IContextNode for more details.
private final IPrivateOrgTree.IContextNode wdContext;
A shortcut for <code>wdThis.wdGetAPI()</code>. </p>
Represents the generic API of the generic Web Dynpro counterpart
for this controller. </p>
private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdControllerAPI;
A shortcut for <code>wdThis.wdGetAPI().getComponent()</code>. </p>
Represents the generic API of the Web Dynpro component this controller
belongs to. Can be used to access the message manager, the window manager,
to add/remove event handlers and so on. </p>
private final com.sap.tc.webdynpro.progmodel.api.IWDComponent wdComponentAPI;
public OrgTree(IPrivateOrgTree wdThis)
this.wdThis = wdThis;
this.wdContext = wdThis.wdGetContext();
this.wdControllerAPI = wdThis.wdGetAPI();
this.wdComponentAPI = wdThis.wdGetAPI().getComponent();
//@@begin javadoc:wdDoInit()
/** Hook method called to initialize controller. */
//@@end
public void wdDoInit()
//@@begin wdDoInit()
buildDOM();
//@@end
//@@begin javadoc:wdDoExit()
/** Hook method called to clean up controller. */
//@@end
public void wdDoExit()
//@@begin wdDoExit()
//@@end
//@@begin javadoc:wdDoPostProcessing()
Hook called to handle data retrieval errors before rendering.
After doModifyView(), the Web Dynpro Framework gets all context data needed
for rendering by validating the contexts (which in turn calls the supply
functions and supplying relation roles). In this hook, the application
should handle the errors which occurred during validation of the contexts.
Using preorder depth-first traversal, this hook is called for all component
controllers starting with the current root component.
Permitted operations:
- Flushing model queue
- Creating messages
- Reading context and model data
Forbidden operations:
- Invalidating model data
- Manipulating the context
- Firing outbound plugs
- Creating components
@param isCurrentRoot true if this is the root of the current request
//@@end
public void wdDoPostProcessing(boolean isCurrentRoot)
//@@begin wdDoPostProcessing()
//@@end
//@@begin javadoc:wdDoBeforeNavigation()
Hook before the navigation phase starts.
This hook allows you to flush the model queue and handle any
errors that occur. Firing outbound plugs is allowed in this hook.
Using preorder depth-first traversal, this hook is called for all component
controllers starting with the current root component.
@param isCurrentRoot true if this is the root of the current request
//@@end
public void wdDoBeforeNavigation(boolean isCurrentRoot)
//@@begin wdDoBeforeNavigation()
//@@end
//@@begin javadoc:wdDoApplicationStateChange()
Hook that informs the application about a state change.
<p>
This hook is called e.g. to tell the application that will be
<ul>
<li>left via a suspend plug and therefore should go into a suspend/sleep
mode with minimal need of resources. errors that occur. Firing
outbound plugs is allowed in this hook.
<li>left due to a timeout and could write it's state to a data base if the
user comes back later on
</ul>
The concrete reason is available via IWDApplicationStateChangeInfo
<p>
<b>Important</b>: This hook is called for the top level component only!
@param stateChangeInfo contains the information about the nature of the state change
@param stateChangeReturn allows the application to ask for a different state change.
The framework is allowed to ignore it considering i.e. the current resources situation.
//@@end
public void wdDoApplicationStateChange(com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeInfo stateChangeInfo, com.sap.tc.webdynpro.progmodel.api.IWDApplicationStateChangeReturn stateChangeReturn)
//@@begin wdDoApplicationStateChange()
//@@end
//@@begin javadoc:buildDOM()
/** Declared method. */
//@@end
public void buildDOM( )
//@@begin buildDOM()
// File fileName = new File ("orgchart.xml");
wdThis.wdGetEmpUserIdInterface().getemp();
wdContext.currentContextElement().setPernrRet(wdContext.currentContextElement().getPernrRet());
Zhr_Rfc_Disp_Manger_Employees2_Input input = new co.i.bnhp.model.Zhr_Rfc_Disp_Manger_Employees2_Input();
wdContext.nodeZhr_Rfc_Disp_Manger_Employees2_Input().bind(input);
input.setP_Pernr("1511");
//input.setP_Pernr(wdContext.currentContextElement().getPernrRet());
try{
String xmlFile =WDURLGenerator.getResourcePath(wdComponentAPI.getDeployableObjectPart(), "//tmp//tipex.xml");
File file = new File(xmlFile);
//Creating an empty XML Document
//We need a Document
input.execute();
wdContext.nodeSource().invalidate();
DocumentBuilderFactory dbfac = DocumentBuilderFactory.newInstance();
DocumentBuilder docBuilder = dbfac.newDocumentBuilder();
// DOMImplementation impl = docBuilder.getDOMImplementation();
Document doc = docBuilder.newDocument();
//Creating the XML tree
Element SapJNETData = doc.createElement("SAPJNetData");
SapJNETData.setAttribute("version","1.0");
doc.appendChild(SapJNETData);
// Element typeRepository = doc.createElement("TypeRepository");
// typeRepository.setAttribute("href","
tmp
TypeRepository.xml");
// SapJNETData.appendChild(typeRepository);
Element typeRepository = doc.createElement("TypeRepository");
typeRepository.setAttribute("id","orgchart");
typeRepository.setAttribute("version","1.0");
SapJNETData.appendChild(typeRepository);
Element color = doc.createElement("COLOR");
typeRepository.appendChild(color);
Element type1 = doc.createElement("type");
type1.setAttribute("name","OCBlue");
Element rgb1 = doc.createElement("rgb");
Text textRGB1 = doc.createTextNode("0,0,128");
color.appendChild(type1);
rgb1.appendChild(textRGB1);
type1.appendChild(rgb1);
Element type2 = doc.createElement("type");
type2.setAttribute("name","OCGray");
Element rgb2 = doc.createElement("rgb");
Text textRGB2 = doc.createTextNode("215,220,216");
color.appendChild(type2);
rgb2.appendChild(textRGB2);
type2.appendChild(rgb2);
Element type3 = doc.createElement("type");
type3.setAttribute("name","OCGrayer");
Element rgb3 = doc.createElement("rgb");
Text textRGB3 = doc.createTextNode("195,200,196");
color.appendChild(type3);
rgb3.appendChild(textRGB3);
type3.appendChild(rgb3);
Element type4 = doc.createElement("type");
type4.setAttribute("name","OCLighter");
Element rgb4 = doc.createElement("rgb");
Text textRGB4 = doc.createTextNode("235,240,236");
color.appendChild(type4);
rgb4.appendChild(textRGB4);
type4.appendChild(rgb4);
Element layout = doc.createElement("LAYOUT");
typeRepository.appendChild(layout);
Element typeLayout = doc.createElement("type");
typeLayout.setAttribute("name","OCLayout");
Element style = doc.createElement("style");
Text textStyle = doc.createTextNode("VERTICAL_FLOW");
layout.appendChild(typeLayout);
typeLayout.appendChild(style);
style.appendChild(textStyle);
Element label = doc.createElement("LABEL");
typeRepository.appendChild(label);
Element typeLabel1 = doc.createElement("type");
typeLabel1.setAttribute("name","OCLabelBase");
Element colorLabel = doc.createElement("color");
colorLabel.setAttribute("type","Black");
Element font1 = doc.createElement("font");
Element size1 = doc.createElement("size");
Text textSize1 = doc.createTextNode("12");
Element multiLine =doc.createElement("multiLine");
Text textMultiLine=doc.createTextNode("TRUE");
Element hAlign = doc.createElement("halign");
Text textHalign = doc.createTextNode("CENTER");
Element hAlignText = doc.createElement("halignText");
Text textHalignText = doc.createTextNode("CENTER");
Element border1 = doc.createElement("border");
Element insets1 = doc.createElement("insets");
insets1.setAttribute("top","3");
Element typeLabel2 = doc.createElement("type");
typeLabel2.setAttribute("name","OCLabelOrgUnit");
typeLabel2.setAttribute("inherits","OCLabelBase");
Element colorLabel2 = doc.createElement("color");
colorLabel2.setAttribute("type","OCBlue");
Element fillColorLabel2 = doc.createElement("fillColor");
fillColorLabel2.setAttribute("type","OCGrayer");
Element font2 = doc.createElement("font");
Element style2 = doc.createElement("style");
Text textStyle2 = doc.createTextNode("BOLD");
Element border2 = doc.createElement("border");
Element thickness = doc.createElement("thickness");
Text textThickness = doc.createTextNode("1");
Element Side = doc.createElement("sides");
Text textSide = doc.createTextNode("SOUTH");
Element typeLabel3 = doc.createElement("type");
typeLabel3.setAttribute("name","OCLabelNumber");
typeLabel3.setAttribute("inherits","OCLabelBase");
Element colorLabel3 = doc.createElement("color");
colorLabel3.setAttribute("type","OCBlue");
Element size3 = doc.createElement("size");
Text textSize3 = doc.createTextNode("40,0");
Element halign3 = doc.createElement("halign");
Text textHalign3 = doc.createTextNode("RIGHT");
Element multiLine3 = doc.createElement("multiline");
Text textMultiLine3 = doc.createTextNode("FALSE");
Element border3 = doc.createElement("border");
Element Thickness3 = doc.createElement("thickness");
Text textThickness3 = doc.createTextNode("1");
Element insets3 = doc.createElement("insets");
insets3.setAttribute("top","0");
Element Sides3 = doc.createElement("sides");
Text textSides3 = doc.createTextNode("NORTH,WEST");
Element typeLabel4 = doc.createElement("type");
typeLabel4.setAttribute("name","OCLabelChief");
typeLabel4.setAttribute("inherits","OCLabelBase");
Element font4 = doc.createElement("font");
Element style4 = doc.createElement("style");
Element border4 = doc.createElement("border");
Element insets4 = doc.createElement("insets");
insets4.setAttribute("top","6");
Element edgeT = doc.createElement("EDGE");
Element typeEdge= doc.createElement("type");
typeEdge.setAttribute("name","OCLink");
Element Shape = doc.createElement("shape");
Element ThickNess =doc.createElement("thickness");
Element targetDeco = doc.createElement("targetdeco");
targetDeco.setAttribute("shape","NONE");
Element nodeT = doc.createElement("NODE");
Element typeNode = doc.createElement("type");
typeNode.setAttribute("name","OCNodeBase");
Element shape = doc.createElement("shape");
shape.setAttribute("type","Box");
Element fillColor = doc.createElement("fillColor");
fillColor.setAttribute("type","OCGray");
Element borderNode = doc.createElement("border");
Element styleNode = doc.createElement("style");
Element plugs = doc.createElement("plugs");
plugs.setAttribute("min","0");
plugs.setAttribute("position","SOUTH");
plugs.setAttribute("positionMode","CENTRIC");
Element socket = doc.createElement("sockets");
socket.setAttribute("min","0");
socket.setAttribute("position","NORTH");
socket.setAttribute("positionMode","CENTRIC");
Element OCNode = doc.createElement("type");
OCNode.setAttribute("name","OCNode");
OCNode.setAttribute("inherits","OCNodeBase");
Element OCNodeShape = doc.createElement("shape");
Element OCNodeSize = doc.createElement("size");
OCNodeSize.setAttribute("pack","true");
Element OClayout = doc.createElement("layout");
OClayout.setAttribute("type","OCLayout");
Element OCNodeArrowUp = doc.createElement("type");
OCNodeArrowUp.setAttribute("name","OCNodeArrowUp");
OCNodeArrowUp.setAttribute("inherits","OCNodeBase");
Element OCNodeArrowShape = doc.createElement("shape");
Element OcNodeArrowSize = doc.createElement("size");
Element OcNodeArrowLabel = doc.createElement("label");
Element OcNodeArrowicon = doc.createElement("icon");
Element OcNodeArrowHalign = doc.createElement("halign");
Element OCNodeArrowDown = doc.createElement("type");
OCNodeArrowDown.setAttribute("name","OCNodeArrowDown");
OCNodeArrowDown.setAttribute("inherits","OCNodeArrowUp");
Element OCNodeArrowDownLabel = doc.createElement("label");
Element OcNodeArrowDownIcon = doc.createElement("icon");
Element NodeGraph = doc.createElement("Graph");
Element OCGraph = doc.createElement("type");
OCGraph.setAttribute("name","OCGraph");
Element direction = doc.createElement("direction");
Element components = doc.createElement("components");
Element OCGraphLayouts = doc.createElement("layouts");
Element types = doc.createElement("types");
Element OCGraphlayout = doc.createElement("layout");
OCGraphlayout.setAttribute("type","TREE");
Element property1 = doc.createElement("property");
property1.setAttribute("name","STYLE");
property1.setAttribute("value","VARIABLE_SIZE");
Element property2 = doc.createElement("property");
property2.setAttribute("name","OFFS_X");
property2.setAttribute("value","50");
Element property3 = doc.createElement("property");
property3.setAttribute("name","OFFS_Y");
property3.setAttribute("value","30");
Element Graph = doc.createElement("Graph");
Graph.setAttribute("type","OCGraph");
Graph.setAttribute("version","1.0");
Element layouts = doc.createElement("layouts");
layouts.setAttribute("onLoad","TREE");
Element view = doc.createElement("view");
Element grid = doc.createElement("grid");
Text TextGrid = doc.createTextNode("80,80");
Element UserInterface = doc.createElement("userInterface");
UserInterface.setAttribute("version","1.0");
Element mode = doc.createElement("mode");
label.appendChild(typeLabel1);
typeLabel1.appendChild(colorLabel);
typeLabel1.appendChild(font1);
font1.appendChild(size1);
size1.appendChild(textSize1);
typeLabel1.appendChild(multiLine);
multiLine.appendChild(textMultiLine);
typeLabel1.appendChild(hAlign);
hAlign.appendChild(textHalign);
typeLabel1.appendChild(hAlignText);
hAlignText.appendChild(textHalignText);
typeLabel1.appendChild(border1);
border1.appendChild(insets1);
label.appendChild(typeLabel2);
typeLabel2.appendChild(colorLabel2);
typeLabel2.appendChild(fillColorLabel2);
typeLabel2.appendChild(font2);
font2.appendChild(style2);
style2.appendChild(textStyle2);
typeLabel2.appendChild(border2);
border2.appendChild(thickness);
thickness.appendChild(textThickness);
border2.appendChild(Side);
Side.appendChild(textSide);
label.appendChild(typeLabel4);
typeLabel4.appendChild(font4);
font4.appendChild(style4);
style4.appendChild(doc.createTextNode("BOLD"));
typeLabel4.appendChild(border4);
border4.appendChild(insets4);
label.appendChild(typeLabel3);
typeLabel3.appendChild(colorLabel3);
typeLabel3.appendChild(size3);
size3.appendChild(textSize3);
typeLabel3.appendChild(halign3);
halign3.appendChild(textHalign3);
typeLabel3.appendChild(multiLine3);
multiLine3.appendChild(textMultiLine3);
typeLabel3.appendChild(border3);
border3.appendChild(Thickness3);
Thickness3.appendChild(textThickness3);
border3.appendChild(insets3);
insets3.setAttribute("top","0");
border3.appendChild(Sides3);
Sides3.appendChild(textSides3);
typeRepository.appendChild(edgeT);
edgeT.appendChild(typeEdge);
typeEdge.appendChild(Shape);
Shape.appendChild(doc.createTextNode("BENT"));
typeEdge.appendChild(ThickNess);
ThickNess.appendChild(doc.createTextNode("1"));
typeEdge.appendChild(targetDeco);
typeRepository.appendChild(nodeT);
nodeT.appendChild(typeNode);
typeNode.appendChild(shape);
shape.appendChild(fillColor);
shape.appendChild(borderNode);
borderNode.appendChild(styleNode);
styleNode.appendChild(doc.createTextNode("RAISED"));
typeNode.appendChild(plugs);
typeNode.appendChild(socket);
nodeT.appendChild(OCNode);
OCNode.appendChild(OCNodeShape);
OCNodeShape.appendChild(OCNodeSize);
OCNodeSize.appendChild(doc.createTextNode("150,0"));
OCNode.appendChild(OClayout);
nodeT.appendChild(OCNodeArrowUp);
OCNodeArrowUp.appendChild(OCNodeArrowShape);
OCNodeArrowShape.appendChild(OcNodeArrowSize);
OcNodeArrowSize.appendChild(doc.createTextNode("22,21"));
OCNodeArrowUp.appendChild(OcNodeArrowLabel);
OcNodeArrowLabel.appendChild(OcNodeArrowicon);
OcNodeArrowicon.appendChild(doc.createTextNode("apps/orgchart/arrow-up.gif"));
OcNodeArrowLabel.appendChild(OcNodeArrowHalign);
OcNodeArrowHalign.appendChild(doc.createTextNode("CENTER"));
nodeT.appendChild(OCNodeArrowDown);
OCNodeArrowDown.appendChild(OCNodeArrowDownLabel);
OCNodeArrowDownLabel.appendChild(OcNodeArrowDownIcon);
OcNodeArrowDownIcon.appendChild(doc.createTextNode("apps/orgchart/arrow-down.gif"));
typeRepository.appendChild(NodeGraph);
NodeGraph.appendChild(OCGraph);
OCGraph.appendChild(direction);
direction.appendChild(doc.createTextNode("TOP_BOTTOM"));
OCGraph.appendChild(components);
components.appendChild(doc.createTextNode("OCNode"));
OCGraph.appendChild(OCGraphLayouts);
OCGraphLayouts.appendChild(types);
types.appendChild(doc.createTextNode("TREE"));
OCGraphLayouts.appendChild(OCGraphlayout);
OCGraphlayout.appendChild(property1);
OCGraphlayout.appendChild(property2);
OCGraphlayout.appendChild(property3);
SapJNETData.appendChild(UserInterface);
UserInterface.appendChild(mode);
mode.appendChild(doc.createTextNode("SELECTONLY"));
SapJNETData.appendChild(Graph);
Graph.appendChild(layouts);
Graph.appendChild(view);
view.appendChild(grid);
grid.appendChild(TextGrid);
for (int i=0; i<wdContext.nodeZhr_Rfc_Employees2().size(); i++) {
IPublicOrgTree.IEmpElement Emp = wdContext.nodeEmp().createEmpElement();
IPublicOrgTree.IZhr_Rfc_Employees2Element curEmp = wdContext.nodeZhr_Rfc_Employees2().getZhr_Rfc_Employees2ElementAt(i);
Element node = doc.createElement("node");
node.setAttribute("id",curEmp.getEmp_Pernr());
node.setAttribute("type","OCNode");
Element label1 = doc.createElement("label");
label1.setAttribute("type","OCLabelOrgUnit");
Text TextLabel1 = doc.createTextNode(curEmp.getEmp_Name());
Element label2 = doc.createElement("label");
label2.setAttribute("type","OCLabelChief");
Text TextLabel2 = doc.createTextNode(curEmp.getEmp_Pernr());
Graph.appendChild(node);
node.appendChild(label1);
label1.appendChild(TextLabel1);
node.appendChild(label2);
label2.appendChild(TextLabel2);
wdContext.nodeEmp().addElement(Emp);
for (int i=0; i<wdContext.nodeZhr_Rfc_Employees2().size()-1; i++) {
IPublicOrgTree.IEmpElement Emp = wdContext.nodeEmp().createEmpElement();
IPublicOrgTree.IZhr_Rfc_Employees2Element curEmp = wdContext.nodeZhr_Rfc_Employees2().getZhr_Rfc_Employees2ElementAt(i);
for (int j=i1; j<wdContext.nodeZhr_Rfc_Employees2().size(); j+)
if (wdContext.nodeZhr_Rfc_Employees2().getZhr_Rfc_Employees2ElementAt(i).getEmp_Pernr().equals(wdContext.nodeZhr_Rfc_Employees2().getZhr_Rfc_Employees2ElementAt(j).getEmp_Manager()))
Element edge = doc.createElement("edge");
edge.setAttribute("type","OCLink");
Element from = doc.createElement("from");
from.setAttribute("node",curEmp.getEmp_Pernr());
Element to = doc.createElement("to");
to.setAttribute("node",wdContext.nodeZhr_Rfc_Employees2().getZhr_Rfc_Employees2ElementAt(j).getEmp_Pernr());
Graph.appendChild(edge);
edge.appendChild(from);
edge.appendChild(to);
// typeLabel3.appendChild()
// Element font = doc.createElement("font");
// .appendChild(color);
// type1.appendChild(rgb1);
//create a comment and put it in the root element
// Comment comment = doc.createComment("Just a thought");
// type1.appendChild(comment);
//create child element, add an attribute, and add to root
// Element child = doc.createElement("child");
//child.setAttribute("name", "value");
//type.appendChild(child);
//add a text element to the child
//Output the XML
//set up a transformer
TransformerFactory transfac = TransformerFactory.newInstance();
Transformer trans = transfac.newTransformer();
trans.setOutputProperty(OutputKeys.ENCODING, "ISO-8859-8");
trans.setOutputProperty(OutputKeys.INDENT, "yes");
//create string from xml tree
StringWriter sw = new StringWriter();
StreamResult result = new StreamResult(file);
DOMSource source = new DOMSource(doc);
trans.transform(source, result);
wdContext.currentContextElement().setXmlString(sw.toString());
} catch (DOMException e) {
wdComponentAPI.getMessageManager().reportException("2-"+e.getMessage(),true);
} catch (TransformerConfigurationException e) {
-
Printing list of drive contents
How can I print out the list of folders names contained in an external drive? Copy and paste to a file folder won't work, because it wants to copy the contents of all the folders. i just want the list of folders for ID purposes.
Hi S,
This way I mentioned I can only have one level listing, if I use the List View I can expand folders and also have it's contents listed (this handle only copy names). But using this I miss two features, manage Finder to expand all folders in List View; and have a paste with hierarchical layout, as this way I get contents of expanded folders placed in first position of new lines just like parent folder.
Do you have a hint about any of these?
Thank you, K. -
Exception messages in CM21 or CM25
Dear Group,
Where can I find information regarding the indicators used in column EM for chart 3 when using profile SAPSFCG011? Layout ID says this should field STEUS from table PLPOB, that is not what is displayed. Some of the indicators that appear are self-explained such as RSIN and RSOT but DLV is not because if you look at the order in question that status is not active.
Thanks,Here is what we have:
Capacity planning table: SAPSFCL010 SFC: only main cap. (3 graf.)
Graphics profile SAP___X002 BARC 1 Default profile 2 Capa. planning board
Chart sequence SAPSFCT002 SFC: Main caps. (3 graph.)
Layout ID SAPSFCLA10 SFC: Work center view (graphical)
Chart nr. 01 1st Chart
Chart nr. 02 1st Chart (dispatched)
Chart nr. 03 3rd Chart (not dispatched)
Sort SAPSFCGS02 SFC: Late start/prio/mat.no./order/op.no
Grouping SAPSFCGR03 Group 3
Gr Layout key H
04 SAPSFCAS11 X View work center - prod. order
Item Table Field name Description Heading
001 CAUFVD MATNR Material Number Material
002 CAUFVD MATXT Material description Material description
003 CAUFVD AUFNR Order Order
004 AFVGD VORNR Operation/Activity Op.
005 KBEDD MGVRG Operation Quantity Operation quantity
006 KBEDD KRUEREST Remain.setup rqmts Rem.setup
007 KBEDD KBEAREST Rem.rqmts-Processing Rem.-Pro
008 KBEDD SSTAD Latest start / date Latest start
009 PLPOB STEUS Control key EMsg
010 PLPOB USR08 User field date Rschl.date
011 AFVGD LTXA1 Operation short text ORTXT
012 PLPOB LTXA1 Operation short text PLTXT
013 PLAF PLNUM Planned order Plnd order
05 SAPSFCAS12 View work center - planned order
06 SAPSFCAS12 View work center - planned order
We have not altered what was delivered. Hope this helps. -
Policies & Procedures Management
Hi everyone,
I have a large Word document which contains policies and procedures for our company. It has somewhat of a hierarchical layout, divided into numbered sections and subsections with a table of contents. Management would like me to move the document into SharePoint
in a way that would:
1) Allow linking directly to certain sections from other documents and pages.
2) Ideally allow tagging of individual sections for aggregating and searching. (i.e. Accounting, HR, Expenses, etc)
3) Allow individual sections to be edited with and approval an publish process. Multiple sections could be under edit simultaneously by different users.
4) Allow new sections to be inserted while automatically altering the numbering scheme and table of contents.
5) Allow the entire document to be printed at once.
I've been trying to wrap my head around how to structure this that will allow me to meet the above criteria. Should I use a list, pages, or documents, or some combination?
Thanks!Hi Jeremy,
To print documents in a library, you could consider the methods to programatically print items in a .NET page, please refer to the threads below:
https://social.msdn.microsoft.com/Forums/en-US/a603fb5b-2028-4e12-8c74-9e4b0f06591d/printing-documents-at-shared-printer-from-sharepoint-library-programmatically?forum=sharepointgeneralprevious
https://social.msdn.microsoft.com/Forums/en-US/3350da78-e9f5-414c-b7a8-8bf0772157b0/printing-documents-at-shared-printer-from-sharepoint-2010-library-programmatically?forum=sharepointdevelopmentprevious
As for the second requirement, I'm not quitely understand. How do you like to number the documents?
Regards,
Rebecca Tu
TechNet Community Support
Maybe you are looking for
-
[SD] table for Schedule line date
If we display a sales order through Va03 and Go to tab Item overview. There is a excel sheet kind of display showing all items. The 12th col is 'First Date' and the f1 help says its 'Schedule line date'. I need to display this date in my report. <i>F
-
How to assign values for more than one field
Hi, I have written following code constants: fieldname(30) value '(SAPMF02D)KNA1-AUFSD'. constants: fieldname1(30) value '(SAPMF02D)KNA1-LISFD'. constants: fieldname2(30) value '(SAPMF02D)KNA1-FAKSD'. field-symbols: <L_FIELD> TYPE ANY. field-symbols
-
my daughter and i logged onto same icloud and now i can see her messages and vice versa.. how can i fix this?
-
Why i can't enter into the Apple net
What happen about the Apple net? I can't enter into it now.
-
Multiple Validity Dates in Contract Pricing Agreements
Hi We are using Quantity contracts in ECC 5.0. Now business wants to maintain multiple validity dates in price agreement of contract. When we try to create the agreement with multiple validity dates, i am getting following message: The condition is b