data modelling and database design

Data Modelling and Database Design in ABAP – Part 4
Tobias Trapp

Let’s Start an Experiment

In the last instalments of this weblog series I dealt with semantic data models, SERM and SAP Data Modeller. Now I cover an completely different topic. Let’s start with an experiment and create a transparent table:

Then we use transaction se16 to enter some data:

Now we add another column and activate the transparent table:

Now here’s an effect that might be surprising to you: every search using se16 for a CONN_ID value won’t find anything:

But what went wrong? Let’s switch on the flag “Initial Values”:

And finally after activation we get the expected result:

What happened? When we appended the column the new fields have been filled with NULL values which didn’t match the expression SELECT COUNT() FROM ZTEST WHERE CONN_ID EQ SPACE. Let’s have a look at the F1-documentation of the “Initial Values” in detail:

Indicator that NOT NULL is forced for this field

Select this flag if a field to be inserted in the database is to be filled with initial values. The initial value used depends on the data type of the field. Please note that fields in the database for which the this flag is not set can also be filled with initial values. When you create a table, all fields of the table can be defined as NOT NULL and filled with an initial value. The same applies when converting the table. Only when new fields are added or inserted, are these filled with initial values. An exception is key fields. These are always filled automatically with initial values.

Restrictions and notes:

• The initial value cannot be set for fields of data types LCHR, LRAW, and RAW. If the field length is greater than 32, the initial flag cannot be set for fields of data type NUMC.
• If a new field is inserted in the table and the initial flag is set, the complete table is scanned on activation and an UPDATE is made to the new field. This can be very time-consuming.
• If the initial flag is set for an included structure, this means that the attributes from the structure are transferred. That is, exactly those fields which are marked as initial in the definition have this attribute in the table as well.

What are NULL Values?

There are different semantics for NULL values in database tables:

• unknown value (there is value but we don’t know it),
• not existing value (we can’t apply the attribute),
• missing information (there may be a value but we don’t know it).

SQL standard defines some rules for NULL values:

1. You can’t insert a NULL value in a column that that is defined NOT NULL,
2. The result of a comparison between two NULL values is not true – you have to use the IS NOT NULL and IS NULL.
3. If a column contains NULL values it will be ignored when using aggregations: MAX, AVG and SUM.
4. When doing grouping using GROUP BY then there are special rows for the results.
5. If a table contains NULL values in joins there apply rules for outer joins.

In fact above rules apply for ABAP as well. I suggest reading details in transaction ABAPHELP.

What are NULL Values Used For?

We already saw how to create NULL values in a database table by appending a row with the flag “initial values” set off. But there is another possibility: insert a new row using a view that doesn’t affect a column with the flag “initial values” switched off. But even if you don’t have NULL values in two transparent tables it is easy to create NULL values in a left outer join which is left as an easy exercise to the reader.

In fact NULL values are not very useful because there is no NULL in ABAP and is difficult to set a database field to NULL. Usually we use working areas (resp. internal tables) to update a transparent table – but if we select a row into a working area the NULL value will be converted to an initial value and after the update the NULL value is lost.

But there is one interesting application for NULL values. If we need a post processing after appending a row to a transparent table to calculate values for new fields it is very useful to be able to distinguish between new fields and already calculated fields with initial values.

Tobias Trapp is SAP Mentor and developer for AOK Systems GmbH

Calculating Dates in MDM-Kristin Patterson

Calculating Dates in MDM
Kristin Patterson

Hi, MDM Users,

I have been asked many a times about the formulas used in the MDM Expression Editors. There are examples throughout the MDM Data Manager Guides but even with these it takes some interpretation to figure out what is happening behind the scenes. As there are millions of expressions, I decided to write an article using just Dates as this seems to be a common field used within MDM and the expression editor.

Calculating Dates in SAP NetWeaver MDM

Even though the examples in the article are related to Dates, the formulas can be applied to other fields. Also, these formulas are used in Calculated Fields, Assignments, and Validations. These being important components of the MDM Workflow.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b025fab3-b3e9-2910-d999-a27b7a075a16
I hope this leads you to the exploration of even more MDM formulas.

Kristin Patterson

Kristin Patterson is a member of the SAP NetWeaver Solution Office.

Do you know the SAP Management Console (SAP MC)? Dirk Jenrich

Do you know the SAP Management Console (SAP MC)?
Dirk Jenrich



If you are using windows, then you probably know the Microsoft Management Console (MMC), which provides a common framework for system management. SAP has developed the SAP Systems Manager snap-in which allows you to monitor, start or stop SAP systems centrally from the MMC, this simplifying system administration. Under Unix, however, for a long time no such tool was available.

But with SAP NetWeaver 7.0, things finally got moving:

* A new start service (sapstartsrv) is available on all platforms. It is offering web service interfaces to applications for centrally administering and monitoring SAP systems.
* With a similar UI to the SAP Systems Manager snap-in of the MMC, the SAP Management Console (SAP MC) was developed, which uses the web services mentioned above. The SAP MC is a browser-based, platform-independent user interface providing basic monitoring and administration of SAP systems.
* Within the development of SAP NetWeaver 7.1 the web service interfacs were further improved. These functions are already available to you in the SAP NetWeaver Composition Environment 7.1. To some degree, a downport of these functions to NW 7.0 is planned.

This weblog introduces the SAP MC. Technically, it's a Java applet running in a Java Runtime Environment on the front end host.

Summarized, the SAP MC allows you to monitor and perform basic administration tasks on SAP systems centrally, thus simplifying system administration. Among other things, it provides the following functions:

* Monitor and control (start, stop, or restart) SAP systems (ABAP and Java) and its instances with a single tool.
* Display SAP log and trace files, start profiles, instance parameters, the system environment, SAP environment, and so on.
* Display and control Java and ABAP processes.
* Monitor system alerts.

If you want to use the SAP MC, you need a Java Runtime Environment with a release as of release 1.4 on your front end. Besides, the corresponding Java Plug-In has to be active on your browser. To start the SAP MC, simply enter the following URL into your web browser:

http://:513

is the name of the host, where the application server is installed.

is the instance number of the application server mentioned above.

The URL is automatically forwarded to:

http://:513/sapmc/sapmc.html?SID=&NR=&HOST=

Now, simply choose Start.

image

Depending on the patch level of the SAP system, the values of the system entered in the URL are shown. If not, you can always add instances manually, using the pushbutoon "Add new instance":

image

Now specify the host parameters of the SAP system you want to display:

image

As you can see, the UI is similar to the MMC:

image

I suggest that you click a little bit around to find out about the different functions. Don't worry! You have to confirm every potentially dangerous command (for example stopping an instance) by entering user and password in order to prevent misuse. Or - if you one of the rare breed, who prefer reading the documentation first - follow this link: http://help.sap.com/saphelp_nwce10/helpdata/en/44/c707c053550f2ce10000000a1553f7/frameset.htm.

Note

Remember that this the documentation of the SAP NetWeaver Composition Environment, so for your NW 7.0 system not all of the functions mentioned there are available.

Some remarks about the UI:

* Right click an instance or a system to get more commands on that level:

image
* Entries below instance levels often contains sub trees; the corresponding icons appear after you've chosen the corresponding entry. As an example, you can see the sub trees for system monitoring, which show the current status and open alerts reported to the CCMS monitoring segments of the corresponding instance.

image

One remark about monitoring of Java instances. In release SAP NetWeaver 7.0, there is the entry AS Java containing a process table with information about the Java processes:

image

In SAP NetWeaver 7.1 however, you can see much more. If you add a Composition Environment (CE) instance, you can see a whole bunch of extremely important monitoring values - representing one of the most complete and comprehensible collection of metrics about Java monitoring. In detail, it contains:

* information about the AS Java threads, sessions, caches, aliases, Enterprise JavaBeans (EJB) sessions, remote objects
* Java Virtual Machine garbage collection and heap memory information of the application server

image

Is there anything more that might be interesting to know?

* You can use the SAP MC for systems with release SAP NetWeaver 2004 as well; see SAP note 1014480.
* If you want, you can install the SAP MC locally; see SAP note 1014480 as well.
* You can use https for calling the SAP MC; for details see SAP note 1036107.

If the notes are not visible to you now, please have some patience - the notes will be released soon.

Dirk Jenrich is info developer for SAP and specializes in central monitoring.

MDM 5.5: Performance problems while loading repositories solved through SP5 & Technical Changes Steffen Ulme

MDM 5.5: Performance problems while loading repositories solved through SP5 & Technical Changes
Steffen Ulme

In this blog I will document the performance improvements which we made at a MDM-project with a very large repository. Maybe you have also problems with your repository (MDM 5.5 < SP5) regarding:
- Loading the repository,
- Adding/ Deleting fields via the SAP MDM Console,
- Modifying record values via the Portal Busienss Package.

If you have these problems, switching to MDM5.5 SP5 can solve these difficulties.

Let me describe our system landscape:
We used MDM5.5 SP4 with a very large repository (~200 tables, many taxonomy records). We had bad response times within the Portal UI as well as it took very long to add or delete fields within the SAP Console. The mayor problem was that it took around 3 hours to load the repository after it was stopped. This handicaped the project team very much, because during the loading of the repository nobody was able to work with it.

Solution description
To enhance the performance we implemented the following tasks:
1. Upgrade to MDM 5.5 SP5: We decided to upgrade to MDM5.5 SP5. Together with the upgrade we made the following

2. Landscape changes:
- we devided the Portal and the MDM Server into two machines, and
- we installed a new database on the local MDM-server.
Further we checked the repository modelling and changed the follwoing technical settings in the repsoitory in order to enhance the performance:

3. Keywords: Set the property "Keyword" for all repository fields to "None" if there is no need to set it to "Normal".

4. Sort Index Exists: Change "Sort Index Exists" for all fields from "Normal" to "None", excepts the fields which should be sorted via the result set in the Data Manager (e.g.: Name, Description, ID). The sort index enables the sorting of the data in the named column in the Data Manager

5. Display fields: Reduce the number of display fields within the repository. Reduce the number in all tables! (also in lookup, qualified tables as well as the main table)

6. Delete unused tables and fields: Check your repository if there are unused tables or not used fields. You should delete these fields and tables.

As a summary these are the reasons for the huge performance improvements:
- Upgarde to MDM 5.5 SP5,
- extra hardware (previously MDM was installed with Portal on one Box),
- newly installed Database SW => repository was newly unarchived => no fragments
- Technical Changes in the repository.


I hope that these experience will help you in your project if you have the described performance problems.

Steffen Ulmer

Steffen Ulmer is a SAP NetWeaver Technology Consultant.

A General Idea on SAP Master Data Management By Ron Victo

Working across Sap heterogeneous forums systems at multiple places, SAP Master Data Management leverages accessible IT assets in business-critical data, delivering greatly reduced data repairs charges and very useful for sap business jobs. Moreover, by ensuring cross-system data consistency, SAP Master Data Management speed ups the implementation of business processes for jobs. SAP MDM is a key enabler of SAP Enterprise Service-Oriented Architecture forums.

SAP is at present on its second iteration of MDM software. Facing restricted acceptance of its primary release, SAP changed path and in 2004 purchased a small vendor in the PIM space known as A2i. This code has happen to the basis for the presently shipping SAP MDM 5.5, and for itself, most analysts believe SAP MDM to be more of a PIM than a broad MDM product at this time.

The components & tools of SAP NetWeaver master data management integrates business courses across the comprehensive value chain, delivering features and functions to help: Master data consolidation, Synchronization and distribution of master data , Centralized management of master data, Administration of master data, Management of internal content, Catalog search, Print catalog customization , Multichannel syndication of product catalog content, Business process support and Business analytics and reporting.

There are five normal execution scenarios:

Content Consolidation, Central Master Data Management, Master Data Harmonization, Rich Product Content and Global Data Synchronization With the SAP (MDM), you can:

1. Control customer relationships efficiently through streamlined visibility across various systems 2. Simply allocate master data to assigned systems through automated distribute and subscribe models 3. Lessen the number of part masters maintained worldwide by removing duplicates 4. Analyze and statement on spending by part, supplier, or other master data 5. Negotiate superior sourcing contracts based on analytical insights 6. Lessen supply chain charges by ensuring exact exchange of data involving manufacturers and dispensers or dealers. SAP Master Data Management is the basis for harmonized, reliable information that can be offered to client applications across the enterprise. It offers you a great way to attain information steadiness across your business or jobs and IT landscape. It enables improved decision-making, translating chance charges into gains, and reducing the charge of IT maintenance. SAP Master Data Management allows you to go with information across myriad applications and topographies -- whether that details resides in SAP, non-SAP, or legacy applications. Therefore, you can lessen costs, develop decision-making, and attain business goals on jobs. The sap news says that SAP (MDM) increases the sap jobs search and by training this sap certified course education module, it supports and gives more vacancies for permanent sap jobs for all developers or trainers worldwide.

Ron Victor is a SEO copywriter for SAP jobs
He written many articles in various topics like SAP news,SAP Forums,SAP Articles.For more information visit sap employment
Contact him at ron.seocopywriter@gmail.com.

Article Source: http://EzineArticles.com/?expert=Ron_Victor

SOA and MDM - Two Integration Solutions That Go Great Together? By Loraine Lawson

I just happened to receive notice today in my inbox of a Webinar on master data management (MDM) and SOA. Normally, I save these announcements for Friday's integration news round-up, but the event is scheduled for this Thursday, March 20, at 11 a.m. ET.

This event caught my eye for a couple of reasons.

First - though perhaps not the best reason - it's like a meeting of the products on opposite sides of the "peak of inflated expectations" on the famous Gartner hype cycle: Master data management is on its way up and SOA...well, I suspect SOA may be headed for the trough of disillusionment. I know I'm feeling pretty disillusioned since I learned people can't even agree on a definition for the "service" in SOA. But I won't go there...for now.

Second, both SOA and MDM involve, in one way or another, integration - so I can't help but wonder what happens when you marry the two, which is precisely what the event promises to discuss.

Third, MDM is all about the data and, as regular readers know, SOA has data "issues," whether you're talking data integration or data services. So, it'll be interesting to see how the two even fit together. The promo e-mail entices with this bit of marketing:

"More than just the latest three-letter acronym, SOA case studies demonstrate that in order to be successful, you must spend time on the data contents of all those messages flying around your ESB or EAI infrastructure (hint: it's not just web services!). Conversely, MDM isn't just the latest trend....Combined, MDM and SOA provide the best of best worlds and increase your chance of succeeding with an enterprise-wide future data architecture."

Marty Moseley, the CTO of Initiate Systems, is the presenter in this event, which is the latest in an ongoing vendor-sponsored MDM University Webinar Sessions. You'll need to select the presentation and fill out a basic form to preregister. After submitting the form, you'll gain access to the previous presentations, which are available for on-demand viewing.

One thing that SOA and MDM do have in common: Neither are supposed to be tied to specific technologies or vendors. While that's well-publicized with SOA, it's perhaps not so often said about MDM.

If you're just starting an MDM initiative, you might want to check out my February interview with Rob Karel, a Forrester Research principal analyst specializing in master data management (MDM) and data integration.

Karel explains what you need to know about MDM and what you should do before you talk to vendors about specific solutions, including this list of questions you should answer before you talk to vendors:

* Do I have sufficient business sponsorship and participation in the MDM effort?

* Am I solving for operational MDM, analytical MDM, or both?

* What sources and targets do I need to integrate my MDM solution with?

* What data integration solution should I leverage (ETL, SOA, EII, EAI, etc.)?

* Am I looking for a single vendor solution or best of breed to build out my MDM ecosystem?

* Have I scoped our MDM strategy appropriately?

Karel also walks through the MDM adoption steps you should take - assuming you want a solution that fits your needs, rather than just buying what a vendor offers. Given that Thursday's MDM/SOA Webinar is vendor-sponsored, the Q&A with Karel might be a useful pre-event read.

Article Source: http://EzineArticles.com/?expert=Loraine_Lawson

Loraine Lawson - EzineArticles Expert Author

MDM - Road Ahead Ketan Phanse

MDM - Road Ahead
Ketan Phanse

The road ahead for MDM seems bright and shiny... atleast as per a recent survey published by MDM Institute!http://www.tcdii.com/0809milestonesonmdmroadmap.html

So as SAP MDM continues to be rated as one of the most valued SAP skills, MDM's market would continue to mature and grow in 2008-09. What does that mean for all of us?

• As more verticals/industries would move into MDM we will see more niche master data objects being mastered. Some of them can be Patients for Healthcare, Well for Oil & Gas, MRO for Manufacturing, Fixed Assets for Service industry etc. This would mean that the limited repositories provided by SAP would not be sufficient. More functional knowledge and expertise would be required to model such niche repositories.
• One of the strong business case for MDM is M&A and in 2007-08 we saw lot of M&A within the MDM space itself! The SAP-BO, Microsoft-Siperian, Oracle-Cognos etc would enhance the functionalities of these core MDM products. This means a fast continuous skills upgrade for us and to keep pace with the technology. It started with SAP ERP, then to BI, SRM and now Business Objects. To learn all these new technologies as they begin to integrate with SAP MDM would be a task we all need to be upto for.
• As mentioned in the roadmap, throughout 2009-10, skill shortages will greatly inflame project costs as demand for data stewards, enterprise data architects, & individuals with data governance experience outstrip market supply. Hence SAP MDM Consultants on the SI side must try to build an identity for themselves on their skill set and experience.

These are some of the learning’s/outlooks we must look forward in MDM trends in up-coming years. The roadmap also throws light on SOA, data governance for MDM etc. Given all this speculation & competition, one can hope that SAP MDM continues to mature and out-pace and out-perform its competitors in technology, capability and functionalities!

Ketan Phanse is a SAP MDM Business Analyst in Wipro Technologies

MDM - Road Ahead
Ketan Phanse

Upgrade MDM on Discovery System to SP6 Markus Gerber

Upgrade MDM on Discovery System to SP6
Markus Gerber

The Discovery System gives you a great opportunity to get in touch with enterprise SOA. To use the latest software, the one on the Discovery System needs to be updated. For MDM, it is not a big deal doing so.

The easiest way to upgrade your MDM installation is following the SAP NetWeaver MDM 5.5 SP6 Upgrade Guide. The most important information are in chapter 4 (Preparation) and chapter 5 (Upgrade Process). If you only use the Out-of-the-Box demonstrations from the Discovery System, there is no need to adapt the API Calls. If you already have own scenarios on the system, be sure to check before the upgrade if any API Calls need to b e adjusted.

After upgrading the MDM Server as described in the Upgrade Guide, you should upgrade the MDM Portal content as well. Download and deploy on the J2EE server the following components:

• JavaAPI
  MDM 5.5 SP06 Java API Patch 2 Hotfix 6
• WebUI (Change Tracker App)
  MDM 5.5 SP06 Web UI Patch 2 Hotfix 5
• Web Services
  MDM 5.5 SP06 Web Services Patch 2
• Portal Content (iViews, ...)
  MDM 5.5 SP06 Application Patch 2 Hotfix 6
  MDM 5.5 SP06 Technology Patch 2 Hotfix 6

Be sure to restart the J2EE server thereafter, otherwise some components won't be activated.

After the MDM upgrade to SP6, check that all the scenarios are working like they were before.

Markus Gerber is a Business Technology Consultant at SAP Switzerland.

Upgrade MDM on Discovery System to SP6
Markus Gerber