REPOSITORY COPYING COMMANDS

CLIX cpyArchive MDMHostSpec RepositorySpec [-A filename]

[-S segSize] [-F] [-N] [-O] [-D] [-XS] [-XSOVT]

Saves an MDM repository to an .a2a archive file. Use –A to specify the

filename rather than accept the MDM Server generated filename. Use –

S to split the file into smaller segments; segment size is suffixed with ‘K’,

‘M’, or ‘G’ to specify kilo-, mega-, or gigabytes respectively. Use the –F

flag to force the overwriting of an existing .a2a archive file. Use the –XS

flag to create a schema-only archive. Use the –XOVT flag to exclude

originals (O), variants (V) and thumbnails (T) from the archive (any

combination of O, V, and T is permitted, such as –XV to exclude only

variants).

Normally CLIX will wait until the MDM Server completes the archive

operation; use the –N flag to return immediately, leaving the archive

activity to run in the background. If you do so, you can check the status

later with the mdsInfo command.

386
MDM Console

CLIX Commands

CLIX cpyDuplicate MDMHostSpec sourceRepositorySpec

targetRepositorySpec Credentials [-Pn] [-F] [-N] [-O]

[-D]

Duplicate a mounted MDM repository to a new repository. You can

overwrite an existing target repository by using the –F flag. Use the –N

flag to perform the operation asynchronously. Use the –P2 or –P4 flags

to specify 2 or 4 storage partitions rather than the default of 1.

CLIX cpyInfo MDMHostSpec [-D]

Whenever a cpyArchive command completes, the MDM Server

surveys and analyses every .a2a file in the MDM Server archive

directory. This command lists the contents of that report file.

CLIX cpyListArchives MDMHostSpec [-D]

Returns a list of the files in the MDM Server archive directory. You can

then choose one of these as the filename for the repUnarchive

command.

CLIX cpySlave MDMHostSpec sourceRepositorySpec

slaveRepositorySpec Credentials [-Pn] [-F] [-N] [-O]

[-D]

Duplicate a mounted MDM repository to a new repository and modify

the new repository to be a slave repository. You can overwrite an

existing target repository by using the –F flag. Use the –N flag to

perform the operation asynchronously. Use the –P2 or –P4 flags to

specify 2 or 4 storage partitions rather than the default of 1.

CLIX cpyUnarchive MDMHostSpec RepositorySpec filename [-Pn]

[-F] [-N] [-O] [-D]

Creates an MDM repository from an .a2a archive file specified by

filename. Use the –F flag to force the overwriting of an existing

repository by the same name on the same DBMS instance. Use the –N

flag if you wish to perform the processing in the background rather than

have CLIX wait until the operation finishes. Use the –P2 or –P4 flags to

specify 2 or 4 storage partitions rather than the default of 1.

A lesson in information as an enterprise asset from the airline industry

All you travelers out there have undoubtedly heard about Southwest Airline's issue last Friday: A Boeing 737-300 experienced a ripped fuselage shortly after take-off. Southwest has since voluntarily cancelled at least 600 flights since Friday's emergency landing. Photo cutesy of Ross D Franklin/AP.

After further inspection and information analysis, the "Federal Aviation Administration (FAA) said it will issue an emergency directive Tuesday to require operators of certain Boeing 737-300, -400 and -500 models that have accumulated more than 30,000 takeoff-and-landing cycles to conduct electromagnetic inspections for early signs of incipient fatigue damage. Those inspections must be repeated at intervals not more than 500 cycles." (See the Seattle Times article here.)

Imagine the information governance that both the FAA, Boeing, and individual airlines must have in place. First they must (very quickly!) identify the causal issue, based on detailed maintenance logs, manufacturer data, and even the specific manufacturing processes involved.

Next, they must (just as quickly) do some predictive analytics to find where similar problems may be lurking to stop a disaster before it occurs. These predictive analytics had to be run across the individual airlines, and take into account multiple parameters: manufacturer, manufacturing process, model numbers, inspection logs, and more.

As if that wasn't enough, Southwest Airlines alone had to cancel flights, notify passengers, move aircraft around, and rebook at least 600 flights.Pronto. One example follows:

"Last night, another Southwest flight was diverted. The flight, headed from Oakland, Calif., to San Diego, Calif. made an emergency landing because of a burning electrical smell. "

To track all of this information and react quickly, these organizations had to, in advance, clearly identify critical data elements that they needed to track (maintenance logs, manufacturing processes, etc.). They also had to document their information policies: how long to keep information, how to analyze information in maintenance logs, service level agreements (SLAs) for notifying passengers of flight changes, and so on.

I can't understate how the business processes above absolutely rely on clean, consistent information. If a model number is not stored according the defined data standard, quick access to that aircraft would not happen. The risk of NOT applying information governance principles is well-known and unacceptably high.

Now think about your business. Which information elements are absolutely critical to your business? Which business processes depend on those information elements being of high quality? What does "high quality" mean to each individual business process? Which elements must be dealt with first? Who owns understanding the ramifications of poor governance and driving the information governance program forward? Do you have an accurate assessment of where you are now? Could you quickly use predictive analytic techniques to proactively avoid large problems? Of course, SAP tools and services can help you with these tasks. Check out our Enterprise Information Management Suite, and throw in a healthy dash of SAP BusinessObjects Business Intelligence (for your predictive analytics), and SAP NetWeaver Business Process Management (for your business processes).

Above all, get your organization talking about how quality, timely information is critical to business function, value, and risk reduction. In independent agencies, government contractors, and the federal government can do it, it's hard for you to say "it's too hard." :-)

SAP MDM Tutorials | SAP MDM Training | SAP MDM Interview Questions |SAP MDM Books

Don't Rush at the End to Load Data - Plan Ahead!

One of the things I see all too often is that the data stream of a project is left to the last moment.  This causes all sorts of problems – when people are busy and stressed trying to do system testing they find they have no REAL data to test with.  They get a few records of made up data that bears no resemblance to the actual data users will see in the production system – and means nothing to them in the context of their legacy system.

Is it any wonder then that the users have trouble validating that the system works the way that it should, they can’t tell because the data that was used didn’t mean anything to them.  It is difficult to tell if it is right or wrong.

The best way to overcome this problem is to plan the data migration and cleansing tasks early, align this with the ERP implementation plan and schedule the first Trial Data Conversion (TDC) to happen just before the first round of system testing. This way the users will have real data to use for testing and can focus on the functionality they are getting from their brand new system rather than complaining about the bad data they saw in the system that didn’t mean anything to them.

New ERP Hated by All…Because No One Cleaned the Data

Users don't like the new system - why?  Because they see the same information they had in the old system – but in a new format.

How many companies have spent millions of dollars on a new ERP system, then added a few more for a BI system, then added Balanced Score Cards and very pretty dashboards, then the CEO still gets reports from an Excel spreadsheet.  Ever wonder why?  There are many reasons; however one we find common is that when the new shiny ERP system was implemented no one cleaned the data from the old system(s) BEFORE it was loaded into the new system.

As a result all the reports that had wrong information before – still have wrong information – but they do look really pretty :)

Why does this happen?  Often time it is because the data migration/conversion stream of the ERP project did not receive the attention that it deserved.  It was left to the business – you know the old story – here is the file format we need – provide the data in this format and we’ll load it for you – but the responsibility for the quality of the data is with you.

It doesn’t have to be this way.  There are tools and processes available that help organizations structure the data migration stream of an ERP implementation project to minimize the risk of poor data getting into the new ERP system.  These methodologies have been developed based on the experience of professionals that have been doing data migrations for many years and have used that to ensure the methodology is practical and proven to result in business ready data loaded into the new ERP system.

SAP MDM Tutorials | SAP MDM Training | SAP MDM Interview Questions |SAP MDM Books

SAP Master Data Management - Governed Customer Data Creation