Tabular Model Best Practice - use of views

Hi,
I've read in some sites that using views to get the model data is a best practice.
Is this related to the fact tables only right? Friendly names can be configured in the model, so views can be used to restrict data volume but besides from that what are the other advantages?
Model needs to know all the relation between tables, so using a unique view that combines joins to present one big view with all the data isn't useful.
Best regards

Yes, I think most people would agree that it isn't helpful to "denormalise" multiple tables into a single view. The model understands the relationships between tables and queries are more efficient with the multiple smaller related tables.
Views can be helpful in giving a thin layer of independence from the data. You might want to change data types (char() to date etc), split first/last names, trim irrelevant columns or simply isolate the model from future physical table changes.
In my view, there aren't any hard and fast rules. Do what is pragmatic and cleanest.
Hope that helps,
Richard

Similar Messages

Favorite / Best Practice / Useful MTE's ??!?!

Hi Everyone,
I'm setting up monitoring on a multi-system architecture; i've got all of the agents working and reporting to my CEN. I've even got the auto-response email all set up, great!
I've been looking around for any best practice on what MTE's (out of the 100's there!) I should be setting up virtual and rule based nodes for.
So come on everyone...what are your favorite MTE's. Of course I'm looking at Dialog Response Times, and Filesystem %'s -- but any other tips? hints? tricks? Any neat MTE's out there that you love to check.
A best practice / useful guide would be brilliant?
Thanks in advance.
Nic Doodson

??

What is the BEST practice - use BO or Java Object in process as webservice

Hi All,
I have my BP published as web service. I have defined My process input & output as BOs. My BP talks to DB through DAO layer(written in JAVA) which has Java objects. So I have BO as well as java Objects. Since I am collecting user input in BO, I have to assign individual values contained in BO to Java object's fields.
I want to reduce this extra headache & want to use either of BO or Java object.I want to know What is the best practice - use BO or Java object as process input. If it is BO,how I can reuse BOs in Java?
Thanks in advance.
Thanks,
Sujata P. Galinde

Hi Mark,
Thanks for your response. I also wanted to use java object only. When I use java object as process input argument..it is fine. But when I try to create Process web service, I am getting compilation error - "data type not supported".....
To get rid of this error, I tried to use heir (BO inheriting from java class). But while invoking process as web service, it is not asking for fields that are inherited from java class.
Then I created Business Object with a field of type java class... This also is not working. While sending request, it is giving an error that - field type for fields from java class not found.
Conclusion - not able to use java object as process(exposed as web service) input argument .
What is the Best & feasible way to accomplist the task - Process using DAO in Java & exposed as web service.
Thanks & Regards,
Sujata

Looking for best practices using Linux

I use Linux plataform to all the Hyperion tools, we has been problems with Analyzer V7.0.1, the server hangs up ramdomly.<BR>I'm looking for a Linux best practices using Analyzer, Essbsae, EAS, etc.<BR>I'll appreciate any good or bad comments related Hyperion on Linux OS.<BR><BR>Thanks in advance.<BR><BR>Mario Guerrero<BR>Mexico

Hi,<BR><BR>did you search for patches? It can be known problem. I use all Hyperion tools on Windows without any big problem.<BR><BR>Hope this helps,<BR>Grofaty

Best Practices Used in CMS

Hi,
Can anyone share the best practices used in CMS transport.
Basically, why I need this is that, we want to have a track of all the transport that are done in QA/Prod
Regards,
Sreenivas

Hi
U can try checking this document to know info about CMS
(How To Transport XI Content Using CMS)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f85ff411-0d01-0010-0096-ba14e5db6306
Also...
How to configuring the CMS for XI?
Business System Groups - CMS

Best practice to create views

Hi,
I've a question about best practice to develop a large application with many complex views.
Typically at each time only one views is displayed. User can go from a view to another using a menu bar.
Every view is build with fxml, so my question is about how to create views and how switch from one to another.
Actually I load fxml every time the view is required:
FXMLLoader loader = new FXMLLoader();
InputStream in = MyController.class.getResourceAsStream("MyView.fxml");
loader.setBuilderFactory(new JavaFXBuilderFactory());
loader.setLocation(OptixController.class.getResource("MyView.fxml"));
BorderPane page;
try {
     page = (BorderPane) loader.load(in);
     } finally {
          if (in != null) {
               in.close();
// appController = loader.getController();
Scene scene = new Scene(page, MINIMUM_WINDOW_WIDTH, MINIMUM_WINDOW_HEIGHT);
scene.getStylesheets().add("it/myapp/Mycss.css");
stage.setScene(scene);
stage.sizeToScene();
stage.setScene(scene);
stage.sizeToScene();
stage.centerOnScreen();
stage.show();My questions:
1- is a good practice reload every time the fxml to design the view?
2- is a good practice create every time a new Scene or to have an unique scene in the app and every time clear all elements in it and set the new view?
3- the views should be keep in memory to avoid performace issue or it is a mistake? I think that every time a view should be destroy in order to free memory.
Thanks very much
Edited by: drenda81 on 21-mar-2013 10.41

>
>
My questions:
1- is a good practice reload every time the fxml to design the view?
2- is a good practice create every time a new Scene or to have an unique scene in the app and every time clear all elements in it and set the new view?
3- the views should be keep in memory to avoid performace issue or it is a mistake? I think that every time a view should be destroy in order to free memory.
In choosing between 1 and 3 above, I think either is fine. Loading the FXML on demand every time will be slightly slower, but assuming you are not doing something unusual such as loading over a network connection it won't be noticeable to the user. Loading all views at startup and keeping them in memory uses more memory, but again, it's unlikely to be an issue. I would choose whichever is easier to code (probably loading on demand).
In choosing between reusing a Scene or creating a new one each time, I would reuse the Scene. "Clearing all elements in it" only needs you to call scene.setRoot(...) and pass in the new view. Since the Scene has a mutable root property, you may as well make use of it and save the (small) overhead of instantiating a new Scene each time. You might consider exposing a currentView property somewhere (say, in your main controller, or model if you have a separate model class) and binding the Scene's root property to it. Something like:
public class MainController {
private final ObjectProperty<Parent> currentView ;
public MainController() {
    currentView = new SimpleObjectProperty<Parent>(this, "currentView");
public void initialize() {
    currentView.set(loadView("StartView.fxml"));
public ObjectProperty<Parent> currentViewProperty() {
    return currentView ;
// event handler to load View1:
@FXML
private void loadView1() {
    currentView.set(loadView("View1.fxml"));
// similarly for other views...
private Parent loadView(String fxmlFile) {
    try {
     Parent view = FXMLLoader.load(getClass().getResource(fxmlFile));
     return view ;
    } catch (...) { ... }
}Then your application can do this:
@Override
public void start(Stage primaryStage) {
   Scene scene = new Scene();
   FXMLLoader loader = new FXMLLoader(getClass().getResource("Main.fxml"));
   MainController controller = (MainController) loader.getController();
   scene.rootProperty().bind(controller.currentViewProperty());
   // set scene in stage, etc...
}This means your Controller doesn't need to know about the Scene, which maintains a nice decoupling.

Best-practice for Catalog Views ? :|

Hello community,
A best practice question:
The situtation: I have several product categories (110), several items in those categories (4000) and 300 end-users. I would like to know which is the best practice for segment the catalog. I mean, some users should only see categories 10,20 & 30. Other users only category 80, etc. The problem is how can I implement this ?
My first idea is:
1. Create 110 Procurement Catalogs (1 for every prod.category). Each catalog should contain only its product category.
2. Assign in my Org Model, in a user-level all the "catalogs" that the user should access.
Do you have any idea in order to improve this ?
Saludos desde Mexico,
Diego

Hi,
Your way of doing will work, but you'll get maintenance issues (to many catalogs, and catalog link to maintain for each user).
The other way is to built your views in CCM, and assign these views to the users, either on the roles (PFCG) or on the user (SU01). The problem is that with CCM 1.0 this is limitated, cause you'll have to assign one by one the items to each view (no dynamic or mass processes), it has been enhanced in CCM 2.0.
My advice:
-Challenge your customer about views, and try to limit the number of views, with for example strategic and non strategic
-With CCM 1.0 stick to the procurement catalogs, or implement BADIs to assign items to the views (I experienced it, it works, but is quite difficult), but with a limitated number of views
Good luck.
Vadim

What is the best practice for changing view states?

I have a component with two Pie Charts that display
percentages at two specific dates (think start and end values).
But, I have three views: Start Value only, End Value only, or show
Both. I am using a ToggleButtonBar to control the display. What is
the best practice for changing this kind of view state? Right now
(since this code was inherited), the view states are changed in an
ActionScript function which sets the visible and includeInLayout
properties on each Pie Chart based on the selectedIndex of the
ToggleButtonBar, but, this just doesn't seem like the best way to
do this - not very dynamic. I'd like to be able to change the state
based on the name of the selectedItem, in case the order of the
ToggleButtons changes, and since I am storing the name of the
selectedItem for future reference.
Would using States be better? If so, what would be the best
way to implement this?
Thanks.

I would stick with non-states, as I have always heard that
states are more for smaller components that need to change under
certain conditions, like a login screen that changes if the user
needs to register.
That said, if the UI of what you are dealing with is not
overly complex, and if it will not become overly complex, maybe
states is the way to go.
Looking at your code, I don't think you'll save much in terms
of lines of code.

Set filter criteria on page 1 for page 2 OData model - "best practice"?

Hello, I have a problem with an app - where I want to filter data on a second page, based on settings from the first page. I use an OData model.
The collections on both pages are not related in terms of "navigation" properties, that is my problem and I can not change the data source...
So I am looking for ideas/best practices to solve this because sometimes my filtering doesn't work... the following problem occurred: Request aborted
I have a page with a sap.m List with items="{/tabWorkPlace}" and and a local JSON model where I store relevant data during the app lifecycle.
handleListSelect - first page
var context = evt.getParameter("listItem").getBindingContext();
var dataModel = sap.ui.getCore().getModel("dataModel");
var workplace = context.getProperty("WORKPLACE_ID");
dataModel.setProperty("/WORKPLACE_ID", workplace);
this.nav.to("SubMaster", context);
The general App.controller.js handles the nav.to function:
var app = this.getView().app;
var page = app.getPage(pageId);
if(pageId == "secondPage") {
page.getController().filterData();
And the controller of the second page:
filterData: function() {
var oModel = sap.ui.getCore().getModel("odata");
var dataModel = sap.ui.getCore().getModel("dataModel");
var workplace = dataModel.getProperty("/WORKPLACE_ID");
var items = this.getView().byId("list");
var oFilter=new sap.ui.model.Filter("WORKPLACE_ID",sap.ui.model.FilterOperator.EQ,workplace);
items.getBinding("items").filter(oFilter);
I don't write this code into the onInit() or beforeRendering() function, because they are called only once and I am navigating back and forth between the two pages, because the pages are created only once and "just" the data is changed.
The desired page looks like this - with an other collection bound to it:
<List
id="list"
select="handleListSelect"
items="{/tabWorkstep_Status}"
>
But when I call it - then the request gets aborted:
The following problem occurred: Request aborted
But despite the fact the Request is aborted, the list on the second page is filtered!
The filter criteria for the model works when I type it into the browser with URL. Maybe this fails because the data binding for the list didn't took place at this phase?
I have this pattern (filter criteria on one page and result on the second page) more times - (and I think a better data model would be better with navigation properties would be better, but I cannot change it)
But at another constellation the filtering doesn't work - same error... the following problem occurred: Request aborted
I also don't want to change the pattern (page 1 to page 2) into popup lists or this fancy new filtering possibilities because it is not suitable for my use case.
Is there maybe a more elegant solution - because sometimes filtering works, sometimes don't..., do I have an error in my solution (general approach)?
Many thanks for any input!
BR,
Denise

Hello, yeah you are right, but it works without the odata> stuff because of this in App.controller.js:
var uri = "http://localhost:32006/JsonOdataService.svc";
var oModelMS = new sap.ui.model.odata.ODataModel(uri);
sap.ui.getCore().setModel(oModelMS, "odata");
oView.setModel(oModelMS);
So my question is - how to navigate from one page to another - and on the other page first bind a collection to a select and then when selecting bind certain elements (a textfield) to the selected filtered entity.
The stuff with context and binding won't work, because the two Collections don't have a navigation/association property between them...
So for example:
page1
select a list item with property color: red and year 1985. Press one of the buttons and pass this criteria to another page.
page 2:
show a dropdown box with all car names which fullfill this criteria, and when one car is selected, then display the data for THIS car in several text fields.
This is not a master->detail navigation example, because on page 1 i select certain criterias, and then with buttons I navigate to several pages with those criterias.
But since the OData model has no relationships it is really hard to do it manually... With a dummy mock.json like in DJ Adams Fiori like SAPUI5 apps it is no problem... But with OData and no things related to each other it is hard...

Service Model, Health Model, Best Practice (SML)

Hello
I am trying to explain to semi-technical people whom do not know SCOM the principle of SCOM when it come to monitoring concepts best practice.
Therefore what I am looking for please is a set of slides/short video/Q&A etc. which explains the concepts reasoning behind taking the time to workout a Service Model and Health Model at the 'start' of a project (e.g. before installing BusinessAppA)
so it can be problem monitored and alerts on etc.
Basically I am trying to get the architects/project managers to think about what I need as a SCOM engineer so I an discover and monitor etc. the Application/System they are proposing to install, rather then picking up this after the event
Does anyone know of any good resources to explain these concepts to get the message across.
Thanks All
AAnotherUser__
AAnotherUser__

Hi,
Please refer to the links below:
Service Model
http://technet.microsoft.com/en-us/library/ee957038.aspx
Health Model Introduction
http://channel9.msdn.com/Series/System-Center-2012-R2-Operations-Manager-Management-Packs/Mod15
Health Model
http://technet.microsoft.com/en-us/library/ff381324.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

2nd Mac - best practices using iPhoto on both?

Hi -
I just got a new MacBook and have an iMac that is still the "hub" of my photo library. It is, in fact, about a 180 GB iPhoto library. I know that I can't sync libraries between Macs (a shame - someone should come up with a way to that assuming they haven't already!) so I'm just looking for any best practices?
I got the MacBook to be able to work on some photos while on the road - I can at least work on post processing in Photoshop, etc. I'm thinking now that my best strategy is to possibly work with the images on my MacBook, importing them into the iPhoto library if desired. Then use my Photo sharing service - Phanfare - to "sync" them? It requires me to download them on the other side and pull them again into the iPhoto Library on the iMac?
I don't use the Mobile Me Gallery but I suppose that would be another way to have access to them on the alternate computer?
Any other best practices or suggestions?
Thx!

So, if there are times when I'm not home to access my external drive, then going with the two libraries is the best solution, yes?
Perhaps, but you can get very small and portable external HDs these days.
I'm not sure though if I should really make both a 180 GB iPhoto library, do you? It is a back up true, but seems like a chunk to move
But you only do it once. The first time. Thereafter you're simply updating the other with the changes.
At least maybe I could split into pictures from 2009 - 2010 and have that library for both my iMac and the MacBook. I very rarely access before then (only if I need something specific) so then I could access that via the iMac exclusively?
That would be viable.
I would maintain a +full Library+ on the Desktop, the mobile versions a Smaller subset.
I'm sort of ruling out the one library on the external solution because it eliminates the possibility of being remote -
As I said above you can get tiny portable drives...
unless there is some swanky Login to My Computer or something that works with a Mac that can go remotely to my computer and then to my external drive.
*_This_* might help.
Regards
TD

Best practice using regular properties

What is considered best practice when it comes to using properties ? Example like hostname, port number when connecting towards an external resource.
Should property files be used ? Is this considered a bad practice ? Should deployment descriptors be used - if so - how do one update these properties when changed ?
Are there any utility classes that makes easy access to this kind of properties ?
---- Trond

Depends on what properties. Many properties like hostname etc can be retrieved using different API calls - such as the request object or other portal specific objects.
Properties that you applications need, that might change - can be stored in a properties file. I use a singleton to retreive them - and have a reload method on the singleton that I can call if I need to reload the properties once the server has started.
Kunal

Data Modeling for controls using XML views(SAPUI5)

Hello ,
I am trying to create Table control using XML view and binding data to it through controller onInit method.
XML View Code is as follows :
<core:View xmlns="sap.m" xmlns:l="sap.ui.layout" xmlns:core="sap.ui.core">
    <l:VerticalLayout width="100%">
        <l:content>
            <Text id="description" class="marginAll" />
            <Table id="idProductsTable" items="{
                path:'/businessData'
            }">
                <headerToolbar>
                    <Toolbar>
                        <Label text="Products"></Label>
                    </Toolbar>
                </headerToolbar>
                <columns>
                    <Column>
                        <Label text="Product" />
                    </Column>
                    <Column>
                        <Label text="Supplier" />
                    </Column>
                    <Column>
                        <Label text="Dimensions" />
                    </Column>
                </columns>
                <items>
                    <ColumnListItem>
                        <cells>
                            <ObjectIdentifier title="{COUNTRY}" text="{COUNTRY}" />
                        </cells>
                        <Text text="{REGION}"></Text>
                        <Text text="{CITY}"></Text>
                    </ColumnListItem>
                </items>
            </Table>
        </l:content>
    </l:VerticalLayout>
</core:View>
Controller onInit method Code is as follows :
var oData = {
            businessData : [ {
                'COUNTRY' : "Canada",
                'CITY' : "Toronto",
                'REGION' : "US",
                'LANGUAGE' : "English"
                'COUNTRY' : "China",
                'CITY' : "Bejeing",
                'REGION' : "Ashia",
                'LANGUAGE' : "Chinese"
        var demoJSONModel = new sap.ui.model.json.JSONModel();
        demoJSONModel.setData(oData);
        sap.ui.getCore().getElementById("idProductsTable").setModel(
                demoJSONModel);
Same thing when i tried with JS views , it worked however through XML view , I am getting empty table.
Is the data modeling correct for XML views?
Thanks,
Mahesh.

I've got it ! The reason for that is you bind items as below,
     <Table id="idProductsTable" items="{
                path:'/businessData'
            }">
This pattern is followed if you wanna add a formatter/sorter/grouping.
As you don't do any of those you can bind items as below & it doesn't require data-sap-ui-xx-bindingSyntax="complex".
<Table id="idProductsTable" items="{/businessData}">

Idoc processing best practices - use of RBDAPP01 and RBDMANI2

We are having performance problems in the processing of inbound idocs. The message type is SHPCON, and transaction volume is very high. I am a functional consultant, not an ABAP developer, but will try my best to explain our current setup.
1)     We have a number of message variants for the inbound SHPCON message, almost all of which are set to trigger immediately upon receipt under the Processing by Function Module setting.
2)      For messages that fail to process on the first try, we have a batch job running frequently using RBDMANI2.
We are having some instances of the RBDMANI2 almost every day which get stuck running for a very long period of time. We frequently have multiple SHPCON idocs coming in containing the same material number, and frequently have idocs fail because the material in the idoc has become locked. Once the stuck batch job is cancelled and the job starts running again normally, the materials unlock and the failed idocs begin processing. The variant for the RBDMANI2 batch job is currently set with a packet size of 1 and without parallel processing enabled.
I am trying to determine the best practice for processing inbound idocs such as this for maximum performance in a very high volume system. I know that RBDAPP01 processes idocs in status 64 and 66, and RBDMANI2 is used to reprocess idocs in all statuses. I have been told that setting the messages to trigger immediately in WE20 can result in poor performance. So I am wondering if the best practice is to:
1)     Set messages in WE20 to Trigger by background program
2)     Have a batch job running RBDAPP01 to process inbound idocs waiting in status 64
3)     Have a periodic batch job running RBDMANI2 to try and clean up any failed messages that can be processed
I would be grateful if somebody more knowledgeable than myself on this can confirm the best practice for this process and comment on the correct packet size in the program variant and whether or not parallel processing is desirable. Because of the material locking issue, I felt that parallel processing was not desirable and may actually increase the material locking problem. I would welcome any comments.
This appeared to be the correct area for this discussion based upon other discussions. If this is not the correct area for this discussion, then I would be grateful if the moderator could re-assign this discussion to the correct area (if possible) or let me know the best place to post it. Thank you for your help.

Hi Bob,
Not sure if there is an official best practice, but the note 1333417 - Performance problems when processing IDocs immediately does state that for the high volume the immediate processing is not a good option.
I'm hoping that for SHPCON there is no dependency in the IDoc processing (i.e. it's not important if they're processed in the same sequence or not), otherwise it'd add another complexity level.
In the past for the high volume IDoc processing we scheduled a background job with RBDAPP01 (with parallel processing) and RBDMANIN as a second step in the same job to re-process the IDocs with errors due to locking issues. RBDMANI2 has a parallel processing option, but it was not needed in our case (actually we specifically wouldn't want to parallel-process the errors to avoid running into a lock issue again). In short, your steps 1-3 are correct but 2 and 3 should rather be in the same job.
Also I believe we had a designated server for the background jobs, which helped with the resource availability.
As a side note, you might want to confirm that the performance issues are caused only by the high volume. An ABAPer or a Basis admin should be able to run a performance trace. There might be an inefficiency in the process that could be adding to the performance issue as well.
Hope this helps.

Best approach - using materialized views

Hi
We are using materialized views for structuring complex business data.
These views get refreshed every night. However, the refresh jobs runs slow in some cases.In such scenarios, the job would still be running while client applications (JDBC) try to access data from the views. This would result in client calls to wait for a long time or to timeout. I would like to know what is the best approach in such scenarios to ensure data availability and performance?
Thanks
RC

See
http://download.oracle.com/docs/cd/B19306_01/server.102/b14226/repmview.htm#i31171
http://download.oracle.com/docs/cd/B19306_01/server.102/b14226/repmview.htm#sthref491
and
http://download.oracle.com/docs/cd/B19306_01/server.102/b14223/basicmv.htm#sthref521
(which also lists the Restrictions)
You can use a Fast Refresh if it meets the restrictions. You need to have a MATERIALIZED VIEW LOG created on the source table(s).
Hemant K Chitale

Tabular Model Best Practice - use of views

Similar Messages

Maybe you are looking for