BW authorizations for standard development

For a training workshop, I need to define some authorizations for the trainees. They shouldn't be allowed to do whatever they want on the BW and R/3 systems. So I can't give them the SAP_ALL profile!
On the source system, the users would be allowed to do something like the following:
- Activate DataSources as local objects (in the package $TMP or in test packages T*);
- Edit the DataSource's active version;
- Edit the function EXIT for the LO DataSources (can the EXIT be a local object?)
On the BW side:
- Replicate the DataSources;
- Create DataSources for the FILE source system;
- Create export DataSources for the myself source system;
- Develop data models and flows;
- Start InfoPackages;
- Develop and run BEx queries.
All these BW objects would be local (yes, this is the default behaviour in BW -- but how can I be absolutely sure a user is prevented altogether from putting an object in a productive package by mistake?)
I'm not a security expert.. Can you give me some good advice and send me some links to useful docs on this topic?
Thanks, <a href="https://wiki.sdn.sap.com/wiki/display/profile/Davide+Cavallari">Davide</a>

Hello David,
using BI Authorizations in BW and then adding data level security in the Universe on top of that will only lead to situations like you have now.
Data Level security goes into BW alone or into the Universe alone, mixing both will lead to issues and remember that the Universe has far less capabilities in this area.
0BI_ALL is only related to data level security, so the fact that you see the request for 0BI_ALL in the trace clearly shows that your defined data level security entries contradict each other somehow and that BW then requires 0BI_ALL for the user to give the data that was requested.
like I said above, not a good idea to mix those data level security concepts. all data level security should be in BW already.
Also - why even use the Universe inbetween ?
regards
Ingo Hilgefort, SAP

Similar Messages

Do you know rule for standard development ?

Hi exeprt,
do you know some document about creation of standard development ? I mean that a document where is explained all object to name on system to start a development in a new system.
tks.

Well for starters, here is a list of (all) possible objects to be created for which naming convention must be established:
Global booleans
Global constants
Global internal tables
Workarea global internal table
Global ranges
Global statics
Global structures (records)
Global types
Global variable (character)
Global variable (date)
Global variable (integer)
Global variable (packed)
Global workarea database table
Parameters
Check boxes
Radio buttons
Select options
Class
Interface
Local booleans
Local constants
Local internal tables
Workarea local internal table
Local ranges
Local statics
Local structures (records)
Local types
Local variable (character)
Local variable (date)
Local variable (integer)
Local variable (packed)
Local workarea database table
Forms using parameters
Forms using parameters (table)
Forms changing parameters
Forms changing parameters (table)
Forms tables parameters
Tables parameters must not be used anymore
Function Module/Method importing parameters
Function Module/Method importing parameters (table)
Function Module/Method exporting parameters
Function Module/Method exporting parameters (table)
Function Module/Method changing parameters
Function Module/Method changing parameters (table)
Function Module tables parameters
Tables parameters must not be used anymore
Function Module/Method exceptions
Method returning parameters
I'm not saying this list is complete, for example objects specific for module pool programming are not included, neither are BAdI's (or enhancements in general for that matter), Web Dynpro development (etc.) , but it will help you on your way. If somewhere along the line, some new objects are created at this customer, you should enhance this document.

Roles and transaction authorizations for XI developer

Hi All,
Can anyone validates my requirements to Basis gui in SAP-XI installation.
Transactions authorizations needed are:
SXMB_IFR
SXMB_MONI
SXMB_MONI_BPE
SXI_Monitor
SXI_Cache
IDX1
IDX2
ALERTCATDEF
SM59
WE21
WE20
Do we require any other transactions as a developer.
2) During File-XI-Idoc scenario, we need to place Idocs in one SAP directory with read/write and delete permisions
Can any one suggests howmuch size should be allocated for this directory.
Regards,
venu

HI Venu
As a developer you need to have also the authorization of SE80..SE38..etc which are there in ABAP
There is predifined Authorization Group for Developer ..Just ask him to add you into that group...You will automatically gain those authorization...
Regarding
File-XI-Idoc Scenario...
You need not to place any IDOC in any of You directory..
You just place a text file which contains all the required information in such a format that can be easily converted into XML using File Adapter...Once You will convert that text file into XML format after that you need to MAP this XML Formated Data to Your IDOC Message Type.
Also Check out these links
it could be helpful for your scenario...
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
Cheers:-)
Mithlesh

Authorizations for Developer/ABAPer

Are there any SAP delivered authorizations for ABAP developer on ECC 6.0 system.
    For now, I have given
      SAP_BC_DWB_ABAPDEVELOPER
       SAP_BC_TC_DEVELOP_ALL
    But, my our developer is not happy at all, complaining, she could do nothing.
This is a development system and I need suitable authorizations for unit test and development client.
    Also please advice what should be security settings on SCC4 for development client and unit testing ?
Many Thanks,
N

Search this topic forum for "John Cleese"
Kind regards,
Julius

PI Developer Authorizations for ABAP and Netweaver

Hello,
I was wondering if anyone had the basic authorizations for a developer in PI? I also need to know what they need access to in the Configuration Tool? I have the Security Guide but I was looking for a little more specifics? Anyone that could help would be fantastic.
James

Hi James,
I find this one useful
http://www.erpgenie.com/sap/netweaver/xi/xiauthorizations.htm
As for the Config tool, i don't think developer should have access to it. It should be restricted to BASIS Team only
Cheers !!
Zaheer

Auth Group for Accounting Doc and Account authorization for Vendors

Hi guys,
I have question regarding Accounting Doc for Vendor and G/l Account. I have a security client whree I build my business roles for end user but we we configuration client where all the functional focus wokring and doing configuration. My questiion when I start creating business roles and start going into these authorization objects and filling up the field values (F_BKPF_BEK, F_BKPF_BES, F_BKPF_BLA).
I won't see auth group that will be c reated by functional cocus because they are working on configuration Client and they probably create auth group for above authorization objects in Config lcient and I'm building Roles in my security client.
If it is true what would be the best way to create business role. I'm in realization face of the project Should I build my roles in Config client? Please advise.
Thanks in advance
Faisal

What is the benefit of a "security client" in DEV? I don't get it...
You anyway need to protect the namespace... and the authorizations for role development (SU24) and admin (PFCG).
Anyway, you have closed your question so we can only lick our wounds now
Cheers and good luck on your project (let is know how it goes if you stick around for long enough to experience a release upgrade...
Julius

BI7 InfoObject Value Level Authorization for Queries

Hi Guys/Gals,
this is my requirement.....
we have a HR ODS which has personal information of employees from 72 Companies.
we have a query based on this ODS ....
My requirement is when User A runs the query only data from Company A must be displayed...
and when User B runs the same query only data from Company B must be displayed....
no pop-ups for the company code .....
i posted this question yesterday & got a few replies....i tried them out... but there is this issue...
i used the RSECADMIN & created the AO which includes the 0COMP_CODE....
then i added it to the role using PFCG....
when i add the AO i created in the " BI Analysis Authorizations: Na " section...
the query gives a "no authorization" error.....
then one of u guy asked me to add it in to the
"SAP Business Information Warehouse - Reporting" section,,,, so i did that....
but unless i also add " BI Analysis Authorizations: Na " with * the query doesn't work....
and when i add " BI Analysis Authorizations: Na " with * &
"SAP Business Information Warehouse - Reporting" with the AO i created...
the filter doesn't work... it displays all the data
please help me.....

Hello Christopher,
your thread is a little bit confusing and unclear. I just had a look at the other two threads you posted and here are my comments:
Prerequisite for the use of BI 7.0 analysis authorizations:
- each user needs authorizations for the three special dimensions (0TCAACTVT, 0TCAIPROV and 0TCAVALID) otherwise queries won't run!
As a consequence you will have to create analysis authorizations like this:
ZCOMP_1000
0COMP_CODE I EQ 1000
0TCAACTVT I EQ 03
0TCAIPROV I EQ your HR DSO
0TCAVALID I EQ *
ZCOMP_2000
0COMP_CODE I EQ 2000
0TCAACTVT I EQ 03
0TCAIPROV I EQ your HR DSO
0TCAVALID I EQ *
You can then assign these authorizations directly to your specific users using RSU01 or you will create a role and add the authorization object S_RS_AUTH with value ZCOMP_1000 and another one that contains S_RS_AUTH with value ZCOMP_2000.
Of course your users will need authorizations for standard reporting such as S_RFC, S_RS_COMP, S_RS_COMP1.
S_RS_ICUBE, S_RS_ODSO, S_RS_MPRO, S_RS_ISET are not necessary any more for reporting because they were replaced by 0TCAIPROV in the analysis authorization.
Finally the query selection must be COMPLETELY be a part of the user's authorizations. This is best done by an query variable that is filled from the user's authorizations at runtime.
Good luck,
Petra

What is standard authorization object for Personal development P_PLOG

Hi,
Recently i got a object in HR and i dont have any experince in HR.Could you guide me how to asssign standard authorisation object for the personal development p_plog? how to see the infotypes and what is the header field in innfotypes?

1-First of all the object is "PLOG" for personal planning. Theres no object with p_plog , most of time to maintain HR master we use object P_ORGIN.
2- You want to assign authorization for certain infotypes?
if yes, you have to go TR.PFCG and assign the authorization to that specific role.
Now you might have question , how youll will track down the roles against the authorization object .
Therere several ways , you can go to Tr.SUIM and find reports by user , roles etc.
You can also go SE16-> give table AGR_1251, give object and you can see the values in table.
After finding the suitable roles you can go to PFCG and assign the values to the roles.
As a good practice its better to create your OWN role Z:hrXXXX and assign it to users.
Hope thisll give you idea!!
P.S award the points.
Good luck
Thanks
Saquib Khan
"Knowledge comes but wisdom lingers!!"

Authorization-problem for standard users when running WDR_TEST_ZCI

hi
we've developed a WDA application incorporating several interactive forms. it all runs fine in QA--environment when a user with developer-role are running the application, but when standard users are running it, it fails.
the same happens with the demo-app WDR_TEST_ZCI.
i so belive this to be caused by missing authorizations for the users. can anyone shed any light on which these might be?
the error as reported in the browser:
The following error text was processed in the system Q97 : Access via 'NULL' object reference not possible.
The error occurred on the application server xx-x168_Q97_05 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: PARSE_XML_SCHEMA of program CL_WD_ADOBE_SERVICES==========CP
Method: GET_SCHEMA_VERSION of program CL_WD_ADOBE_SERVICES==========CP
Method: CONSTRUCTOR of program CL_WD_ADOBE_SERVICES==========CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/LADOBE==================CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/LADOBE==================CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L7STANDARD==============CP
Method: IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT of program /1WDA/L8STANDARD==============CP
any input appreciated.
cheers
tom

Hi Tom,
When you are familiar with authorizations in PFCG trabsaction you are finaliar with S_DEVELOP if not ask the authorization team on your project.
Basically this authorization object handles the read/write etc authorization related to devlopment objects. If you implement Adobe forms you will probably develop your own forms or at least copy the SAP forms to customer namespace.
For Adobe you will therefore have 2 custom development objects (1 for the form and 1 for the interface that is automatically generated). The end-user shoulf have at least READ access to these objects. If not the portal will trow an error on this.
To determine the tech names of the objects find the form and related interface in transaction SFP. These should be inserted in the object S_DEVELOP in the role for the end users.
You may want to consider to put the value Z* in the object which will give authorization for all the custom developed objects.
If you can't find the object reply again and i will send a screenshot.
Finally, make use of the splended transaction ST01!! It will make your life a lot more easy in portal! It traces all the authorizations needed and missing for any user you specify. After activating the trace and running a portal scenario the log will tell you want went OK and what not on an authorization object level.
Good luck,
Thomas
ps. Thanks for the appreciation you gave in my other thread. Now we have the answers in both threads as well. Take Care.

How to set naming standards for SQL Developer

I am using SQL Developer version 3.0.04.
In the newly integrated and very useful Data Modeler, we can set preferences for the naming standards to be applied when creating logical and relational model objects ( primary keys, foreign keys, et cetera). I would like to know if there is a way to set naming standards for the relational objects we create in SQL Developer on existing tables ( ( primary keys, foreign keys, et cetera).
Any help in setting such preferences would be appreciated.

Hi,
If you want to set up a diagram for an existing database, you can use File/Data Modeler/Import/Data Dictionary to import its definitions.
Alternatively you can open a Data Modeler Browser (using View/Data Modeler/Browser), expand the node for Design "Untitled_1",
expand the node for Relational Models, and select Show from the Right-click drop-down menu for "Relational_1" to create a Relational Model diagram.
You can then drag Tables from SQL Developer's Connections tree onto the diagram.
Once you have a Relational Model you can reverse engineer it to an Entity-Relationship model using the << button in the button bar
(or by selecting "Engineer to Logical Model" from the drop-down menu for the Relational Model).
Note that there is now a separate forum for SQL Developer Data Modeler topics: SQL Developer Data Modeler
David

Responsibles for standard application log development (SBAL)

Hi,
does anyone know, who is responsible for the development of the standard application log (SBAL).
Best regards,
Fabian

Hi Fabian,
I think one of them is,
 Brigitte Rousseau ([email protected])
He replies to some of the critical problems in app log.
One such note is 575143
Hope this helps..
Sri

Authorizations For User Defined Forms

Hi Experts !!!
I have created a user form , and would like to apply authorization for that user form.
Whether it is possible.I tried using standard method,but it seems that no such provision available ,
And also I have created UDT . and would like to provide series for that UDT . My client wants that particulat UDT should be by 2 different users .and they need Series for that .
Suggestions are appreciated
Regards
Krishna Vamsi

Hi,
You Can give authorizations to your customized (user developed) screens.
Administration --> System Initialization --> Authorizations --> Additional Authourization Creator
In right hand side you can find the structur.
There defaultly XL reporter autorization will be there select the any one and click add same level button in bottom of the screen.
Then in Right hand Side
Authorization ID - give some unique id
Name --> Description of Authorization
In Option --> Select Full/read/None
Item --> Tick as Item
Then Come down you can find big text box, near to that you can find edit button, just click that it will open a popup window.
In that window you please enter the Form Id of your user form
to find the form id --> Just Enable the system information menu in menu bar and move the cursor to any item in your user screen, you can find the form id.
Just type that form id in that pop up box.
then Add the window.
now Open the General Authorization.
There in last row you can find the user authorization. just expand that you can find your authorization id and name there which you have created.
Give your authorization there.
thats it.
There is no need for SDK Developement for Authorization.

Necessary Authorizations for BI Consultant

Dear All,
What are the necessary Authorizations for BI 7.0 Consultant to work on a BI development system ?
I have created source system (ECC Dev system), installed Bex analyser and I would like to verify if there are any standard tasks to be performed to make the system ready for BI consultant and required authorizations to perform all the activities.
Thanks,
Nick.

Hi,
The basic authorizations you need are RSA1, then you need to have access to all the infoareas, objects. You need access to modify, create, activate objects. In addition you'll need access to maintain master data for master data objects, monitor job loads, process chain access, query creation and change access. Query execute access. Authorizations to replicate datasources, activate them and access for creation, change and activation of DTPs, Infopackages and Transformations is also needed.
These are some of the basic authorizations you need in the development system.
For all other systems, you only need display authorizations for all objects.For data viewing, it'll be based on what security you get. Based on the client strategy in some places, you might get authorization to create, change and activate infopackages and DTPs. But to maintain the integrity of the Process chains and the environments, the best practice would be create these objects in dev and then transport them.
Cheers,
Kedar

GeoRaptor 3.0 for SQL Developer 3.0 and 2.1 has now been released

Folks,
I am pleased to announce that, after 5 months of development and testing, a new release of GeoRaptor for SQL Developer 2.1 and 3.0 is now available.
GeoRaptor for SQL Developer 3 is available via the SQL Developer Update centre. GeoRaptor 3 for SQL Developer 2.1 is being made available
via a download fro the GeoRaptor website.
No release notes have been compiled as the principal developer (oops, that's me!) is currently busy doing real work for a change (another 3 weeks), earning a living
and keeping the wolves at bay. More extensive notes (with images) will be compiled when I get back. (Unless anyone is offering! See next.)
We are still looking for people to:
1. Provide translations of the English dialog menus etc.
2. Write more extensive user documentation. If you use a particular part of GeoRaptor a lot and think
you have found out all its functionality and quirks, contact us and offer to write a few pages of
documentation on it. (Open Office or Microsoft Word is fine.) Easiest way to do this is to simply
make screen captures and annotate with text.
3. Conduct beta testing.
Here are the things that are in the new release.
New functionality:
Overhaul of Validation Functionality.
1. User can specify own validation SELECT SQL as long as it returns three required columns. The SQL is thus totally editable.
2. Validation update code now allows user to associate a PL/SQL function with an error number which is applied in the UPDATE SQL.
3. UPDATE SQL can use WHERE clause of validation SELECT SQL (1) to update specific errors.
 NOTE: The generated UPDATE statement can be manually edited. It is NEVER run by GeoRaptor. To run any UPDATE, copy the statement
 to the clipboard and run in an appropriate SQL Worksheet session within SQL Developer.
4. Main validation table allows:
 a. Sorting (click on column header) and
 b. Filtering.
 c. Copying to Clipboard via right mouse click sub menu of:
 - Geometry's SDO_ELEM_INFO array constructor.
 - SDO_GEOMETRY constructor
 - Error + validation string.
 d. Access to Draw/Zoom functions which were previously buttons.
 e. Added a new right mouse click menu "Show Feature's Individual Errors" that gathers up all the errors
 it can process - along with the ring / element that is host to the error (if it can) - and displays
 them in the Attribute/Geometry tabs at the bottom of the Map Window (where "Identify" places its results).
 The power of this will be evident to all those who have wanted a way of stepping through errors in a geometry.
 f. Selected rows can now be deleted (select rows: press <DELETE> key or right mouse click>Delete).
 g. Table now has only one primary key column, and has a separate error column holding the actual error code.
 h. Right mouse click men added to table menu to display description of error in the new column (drawn from Oracle documentation)
 i. Optimisations added to improve performance for large error lists.
5. Functionality now has its own validation layer that is automatically added to the correct view.
 Access to layer properties via button on validation dialog or via normal right mouse click in view/layer tree.
Improved Rendering Options.
1. Linestring colour can now be random or drawn from column in database (as per Fill and Point colouring)
2. Marking of SDO_GEOMETRY objects overhauled.
 - Ability to mark or LABEL vertices/points of all SDO_GEOMETRY types with coordinate identifier and
 option {X,Y} location. Access is via Labelling tab in layer>properties. Thus, coordinate 25 of a linestring
 could be shown as: <25> or {x,y} or <25> {x,y}
 - There is a nice "stacked" option where the coordinate {x,y} can be written one line below the id.
 - For linestrings and polygons the <id> {x,y} label can be oriented to the angle between the vectors or
 edges that come in, and go out of, a vertex. Access is via "Orient" tick box in Labelling tab.
 - Uses Tools>Preferences>GeoRaptor>Visualisation>SDO_ORDINATE_ARRAY bracket around x,y string.
3. Start point of linestring/polygon and all other vertices can be marked with user selectable point marker
 rather than previously fixed markers.
4. Can now set a NULL point marker by selecting "None" for point marker style pulldown menu.
5. Positioning of the arrow for linestring/polygons has extra options:
 * NONE
 * START - All segments of a line have the arrow positioned at the start
 * MIDDLE - All segments of a line have the arrow positioning in the middle.
 * END - All segments of a line have the arrow positioning in the END.
 * END_ONLY - Only the last segment has an arrow and at its end.
ScaleBar.
1. A new graphic ScaleBar option has been added for the map of each view.
 For geographic/geodetic SRIDs distances are currently shown in meters;
 For all SRIDs an attempt is made to "adapt" the scaleBar units depending
 on the zoom level. So, if you zoom right in you might get the distance shown
 as mm, and as you zoom out, cm/m/km as appropriate.
2. As the scaleBar is drawn, a 1:<DEMONINATOR> style MapScale value is written
 to the map's right most status bar element.
3. ScaleBar and MapScale can be turned off/on in View>Properties right mouse
 click menu.
Export Capabilities.
1. The ability to export a selection from a result set table (ie result of
 executing ad-hoc SQL SELECT statement to GML, KML, SHP/TAB (TAB file
 adds TAB file "wrapper" over SHP) has been added.
2. Ability to export table/view/materialised view to GML, KML, SHP/TAB also
 added. If no attributes are selected when exporting to a SHP/TAB file, GeoRaptor
 automatically adds a field that holds a unique row number.
3. When exporting to KML:
 * one can optionally export attributes.
 * Web sensitive characters < > & etc for KML export are replaced with > < & etc.
 * If a column in the SELECTION or table/view/Mview equals "name" then its value is
 written to the KML tag <name> and not to the list of associated attributes.
 - Similarly for "description" -> <description> AND "styleUrl" -> <styleUrl>
4. When exporting to GML one can optionally export attributes in FME or OGR "flavour".
5. Exporting Measured SDO_GEOMETRY objects to SHP not supported until missing functionality
 in GeoTools is corrected (working with GeoTools community to fix).
6. Writing PRJ and MapInfo CoordSys is done by pasting a string into appropriate export dialog box.
 Last value pasted is remembered between sessions which is useful for users who work with a single SRID.
7. Export directory is remembered between sessions in case a user uses a standard export directory.
8. Result sets containing MDSYS.SDO_POINT and/or MDSYS.VERTEX_TYPE can also be written to GML/KML/SHP/TAB.
 Example:
 SELECT a.geom.sdo_point as point
 FROM (SELECT sdo_geometry(2002,null,sdo_point_type(1,2,null),sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)) as geom
 FROM DUAL) a;
 SELECT mdsys.vertex_type(a.x,a.y,a.z,a.w,a.v5,a.v6,a.v7,a.v8,a.v9,a.v10,a.v11,a.id) as vertex
 FROM TABLE(mdsys.sdo_util.getVertices(mdsys.sdo_geometry(2002,null,null,sdo_elem_info_array(1,2,1),sdo_ordinate_array(1,1,2,2)))) a;
9. A dialog appears at the end of each export which details (eg total) what was exported when the exported recordset/table contains more
 than on shape type. For example, if you export only points eg 2001/3001 from a table that also contains multipoints eg 2005/3005 then
 the number of points exported, and multipoints skipped will be displayed.
10. SHP/TAB export is "transactional". If you set the commit interval to 100 then only 100 records are held in memory before writing.
 However, this does not currently apply to the associated DBASE records.
11. SHP/TAB export supports dBase III, dBase III + Memo, dBase IV and dBase IV + Memo.
 Note: Memo allows text columns > 255 characters to be exported. Non-Memo formats do not and any varchar2 columns will be truncated
 to 255 chars. Some GIS packages support MEMO eg Manifold GIS, some do not.
12. Note. GeoRaptor does not ensure that the SRID of SDO_GEOMETRY data exported to KML is in the correct Google Projection.
 Please read the Oracle documentation on how to project your data is this is necessary. An example is:
 SELECT OBJECTID,
 CODIGO as name,
 NOME as description,
 MI_STYLE,
 SDO_CS.TRANSFORM(shape,'USE_SPHERICAL',4055) as shape
 FROM MUB.REGIONAL;
13. NOTE: The SHP exporter uses the Java Topology Suite (JTS) to convert from SDO_GEOMETRY to the ESRI Shape format. JTS does not handle
 circular curves in SDO_GEOMETRY objects you must "stroke" them using sdo_util.arc_densify(). See the Oracle documentation on how
 to use this.
Miscellaneous.
1. Selection View - Measurement has been modified so that the final result only shows those geometry
 types that were actually measured.
2. In Layer Properties the Miscellaneous tab has been removed because the only elements in it were the
 Geometry Output options which have now been replaced by the new GML/KML/etc export capabilities.
3. Shapefile import's user entered tablename now checked for Oracle naming convention compliance.
4. Identify based on SDO_NN has been removed from GeoRaptor given the myriad problems that it seems to create across versions
 and partitioned/non-partitioned tables. Instead SDO_WITHIN_DISTANCE is now used with the actual search distance (see circle
 in map display): everything within that distance is returned.
5. Displaying/Not displaying embedded sdo_point in line/polygon (Jamie Keene), is now controlled by
 a preference.
6. New View Menu options to switch all layers on/off
7. Tools/Preferences/GeoRaptor layout has been improved.
8. If Identify is called on a geometry a new right mouse click menu entry has been added called "Mark" which
 has two sub-menus called ID and ID(X,Y) that will add the labeling to the selected geometry independently of
 what the layer is set to being.
9. Two new methods for rendering an SDO_GEOMETRY object in a table or SQL recordset have been added: a) Show geometry as ICON
 and b) Show geometry as THUMBNAIL. When the latter is chosen, the actual geometry is shown in an image _inside_ the row/column cell it occupies.
 In addition, the existing textual methods for visualisation: WKT, KML, GML etc have been collected together with ICON and THUMBNAIL in a new
 right mouse click menu.
10. Tables/Views/MViews without spatial indexes can now be added to a Spatial View. To stop large tables from killing rendering, a new preference
 has been added "Table Count Limit" (default 1,000) which controls how many geometry records can be displayed. A table without a spatial
 index will have its layer name rendered in Italics and will write a warning message in red to the status bar for each redraw. Adding an index
 which the layer exists will be recognised by GeoRaptor during drawing and switch the layer across to normal rendering.
Some Bug Fixes.
* Error in manage metadata related to getting metadata across all schemas
* Bug with no display of rowid in Identify results fixed;
* Some fixes relating to where clause application in geometry validation.
* Fixes bug with scrollbars on view/layer tree not working.
* Problem with the spatial networks fixed. Actions for spatial networks can now only be done in the
schema of the current user, as it could happen that a user opens the tree for another schema that
has the same network as in the user's schema. Dropping a drops only the network of the current connected user.
* Recordset "find sdo_geometry cell" code has been modified so that it now appears only if a suitable geometry object is
in a recordset. Please note that there is a bug in SQL Developer (2.1 and 3.0) that causes SQL Developer to not
register a change in selection from a single cell to a whole row when one left clicks at the left-most "row number"
column that is not part of the SELECT statements user columns, as a short cut to selecting a whole row. It appears
that this is a SQL Developer bug so nothing can be done about it until it is fixed. To select a whole row, select all
cells in the row.
* Copy to clipboard of SDO_GEOMETRY with M and Z values forgot has extraneous "," at the end.
* Column based colouring of markers fixed
* Bunch of performance improvements.
* Plus (happily) others that I can't remember!If you find any bugs register a bug report at our website.
If you want to help with testing, contact us at our website.
My thanks for help in this release to:
1. John O'Toole
2. Holger Labe
3. Sandro Costa
4. Marco Giana
5. Luc van Linden
6. Pieter Minnaar
7. Warwick Wilson
8. Jody Garnett (GeoTools bug issues)
Finally, when at the Washington User Conference I explained the willingness of the GeoRaptor Team to work
for some sort of integration of our "product" with the new Spatial extension that has just been released in SQL
Developer 3.0. Nothing much has come of that initial contact and I hope more will come of it.
In the end, it is you, the real users who should and will decide the way forward. If you have ideas, wishes etc,
please contact the GeoRaptor team via our SourceForge website, or start a "wishlist" thread on this forum
expressing ideas for future functionality and integration opportunities.
regards
Simon
Edited by: sgreener on Jun 12, 2011 2:15 PM

Thank you for this.
I have been messing around with this last few days, and i really love the feature to pinpoint the validation errors on map.
I has always been so annoying to try pinpoint these errors using some other GIS software while doing your sql.
I have stumbled to few bugs:
1. In "Validate geometry column" dialog checking option "Use DimInfo" actually still uses value entered in tolerance text box.
I found this because in my language settings , is the decimal operators
2. In "Validate geometry column" dialog textboxs showing sql, doesn't always show everything from long lines of text (clipping text from right)
3. In "Validate geometry column" dialog the "Create Update SQL" has few bugs:
- if you have selected multiple rows from results and check the "Use Selected Geometries" the generated IN-clause in SQL with have same rowid (rowid for first selected result) for all entries
Also the other generated IN clause in WHERE-clause is missing separator if you select more than one corrective function
4. "Validate geometry column" dialog stays annoyingly top most when using "Create Update SQL" dialog

Excel Output For Standard Report In R12

Hi Experts,
My Client wants Excel Output for Standard Reports ( ex:-Open Purchase Order Report (by cost center)_xml)
I changed the default output to Excel in Template of xml publisher administrator Responsibility.
Now it is showing the Excel output, but The layout of report is not same as layout which in text output of standard report.
Please guide me is there any solution to develop the reports layout in ms-excel using xml file rather than rtf template.
Thanks
Durga.

Hi Alex,
Thanks for your replay.
Generating the new rtf template which is same as standard layout is difficult task for us. Actually we have 120 reports which have same requirement.
Is there any other solution for this . please guide me
Thanks
Durga
Edited by: 805567 on Jan 23, 2012 12:33 PM

BW authorizations for standard development

Similar Messages

Maybe you are looking for