One of three delivery methods available in the content distribution service (the other two being push and pull).
In a Database Unifier project, the first table in the FROM clause of the query upon which a query component or presentation component is based.
Component that generates instances of repository managers as required for accessing particular repositories.
A management cockpit is a tool for the efficient presentation of measures in the context of performance measurement.
Specifies how the Collaboration Room properties are transferred to the iViews that are part of a Collaboration Room. This transfer connects the iViews to this room when it is created. Collaboration Room properties are values that you can use to configure a room when creating it. You can specify any number of Collaboration Room properties.
An action that triggers an operation on several resources.
A function that has an effect on several resources and is carried out in one workstep by the system, for example, Copying several documents in one step.
Static data (data that rarely changes) describing characteristics.
Example: A customer's master data can be Phone, Address.
Master Data Attributes
Are not stored in an InfoCube. They are joined to the master data.
Display Attributes: Subordinated to a characteristic and cannot be selected in a query.
Navigational Attributes: InfoObjects that are logically assigned attributes which you can select in the query.
master data ID
Internal key of type INT4 used for master data for master data-bearing characteristics, especially for hierarchy nodes and for characteristic names. Master data IDs (SIDs) and characteristic values are stored in master data tables (SID tables). Information about time-independent or time-dependent master data, which is stored in a P table or a Q table, is saved again in an X or Y table, using SIDs instead of characteristic values.
Master Data Management (MDM)
MDM uses data import, consolidation, and distribution mechanisms to provides a complete view for customer, product, retail article, employee, supplier, or user-defined data objects. Master-data management features the IT scenario variants master-data consolidation, master-data harmonization, and central master data management.
Portal component that consists of three parts: Java code, profiles (configuration and personalization properties) and resources (images, scripts, applets, etc.)
When uploading a portal component to the portal, a master iView is created in the Portal Content Directory. Based on master iViews, the administrator can create Java iViews or External Services with different parameters that are executed in the Java iView Runtime.
A collection of interdependent projects. Master projects enable project executives and project managers to get a high-level overview of a group of projects in the Project Dashboard:
- At master project level, they can drill down and display the key performance indicators for each sub-project
- At project level, they can drill down and display the project details
A part of the out-of-the-box header area of the portal, serving as an entry point to the portal. It contains branding elements, user identification, and other portal links, such as Log off, Help, and Personalize Portal.
An iView that fits into a medium page column and is marked by an "M" in the Layout tab.
Message Oriented Middleware (MOM)
MOM is a category of inter-application communication software that relies on asynchronous message-passing as opposed to a request/response metaphor. Most message-oriented middleware depends on a message queue system, although some implementations rely on broadcast or on multicast messaging systems.
Messaging Application Programming Interface (MAPI)
MAPI allows client programs to become messaging-enabled, -aware, or -based by calling MAPI subsystem routines that interface with certain messaging systems and message stores. MAPI refers both to the application programming interface as well as the proprietary protocol that Microsoft Outlook uses to communicate with Microsoft Exchange.
Data about data. Metadata describes the origin, history, and other aspects of data.
Provides central access to information about metadata objects in the Business Information Warehouse such as active objects in the system (activated objects) and SAP delivery objects in the system (Business Content).
The metadata repository provides the following functions:
- Metadata search
- Metdata exchange
- HTML page exports
- Graphical object display
SAP-specific implementation of an MOF-compatible Metadata Repository for models and metadata in terms of an Object Management Group (OMG). The Metamodel Repository is implemented in Java and meets the JMI standard. Models and metadata is exchanged via XML in accordance with the XMI standard.
Metamodel Repository Designer
Graphical user interface for the Metamodel Repository. It is a plug-in for the Eclipse Java development environment.
Meta-Object Facility (MOF)
One of the OMG-recognized (Object Management Group) standards that determine guidelines for the definition of metadata models and provide programming tools for saving and accessing metadata in repositories.
The MOF standard is integrated in XMI. You can find the current MOF specifications on the OMG homepage.
Microsoft Excel form
An ASP template made available by the Unification Server. This form enables the display of retrieved data in Microsoft Excel sheet format. The Microsoft Excel form offers basic Excel capabilities.
Mobile Application Part (MAP)
MAP is a GSM protocol that provides an application layer for the various nodes in the core mobile network to communicate with each other in order to provide services to mobile phone users.
Mobilizing Business Processes (MBP)
Users of mobile devices can be included in automatic business processes with the back end, making manual and paper-based processes redundant. Managers, truck drivers, and warehouse workers are examples of typical users involved in mobile business processes.
Model-based process execution
Model-based process execution includes a Business Process Management (BPM) runtime supporting both application-unbounded as well as application-embedded processes.
Model driven integration
Model-driven integration focuses on abstracting the information content into a model that describes the enterprise's information resources. This model captures the nature of the information the enterprise has within its systems and the way the enterprise uses data in its daily operations.
MVC is a design pattern used in software engineering. In complex computer applications that present lots of data to the user, you can separate data (Model) and user interface (View) concerns, so that changes to the user interface do not impact the data handling. The MVC design pattern decouples data access and business logic from data presentation and user interaction, by introducing an intermediate component: the Controller.
See Meta Object Facility.
Multidimensional Expressions (MDX)
MDX is a query language for queries about data that is saved in multidimensional cubes.
A Unification Server correlation enhancement which, after a Drag andRelate action between remote and local objects, enables a search for the bridge object having the lightest weight.
MultiProviders, like InfoProviders, are objects or views that are relevant for reporting. MultiProviders combine data from several InfoProviders and make it available for reporting. The MultiProvider itself contains no data; its data comes exclusively from the InfoProviders on which it is based (collated using a union operation). You can assemble a MultiProvider from different combinations of InfoProviders.
The existence of alternative multiple relationships between two objects (representing database tables) in a unifier repository.
System that is connected to itself for data extraction by using the data mart interface. Thus, the user can update data from one data target into other data targets.
my key terms
An iView in SAP xRPM where employees can freely define their areas of key knowledge. Key terms describe "what I know" skills describe "what I can do."
My Portal Contacts
Contact list in the portal, containing names of portal users with whom one most often conducts online synchronous collaborative sessions. Each portal user maintains his or her own contact list.