MySAP Market Place Customer Interface

MySAP market place has a comfortable customer interface that helps the people who are using it with ease.Customers entry Content Engine (iMerge) and its catalogs by approach of a Web browser.This Web-based mostly interface gives the benefits like

As lengthy as users know the catalog’s URL and have been granted the acceptable entry rights, they will entry the catalog from any laptop with a Net browser.
No other utility must be installed on a person’s computer. Content material Engine (iMerge) routinely generates catalog pages each time a person accesses the catalog.
Any changes made by the administrator or to the supply knowledge are instantly mirrored on catalog pages.
Customers navigate the interface through familiar Web techniques, comparable to looking out and following hyperlinks.

Administration
Directors use an interface much like the one seen by end users. The distinction between end-consumer interfaces and the one used by administrators involves the types of gadgets seen and the actions that can be carried out on those items. In brief, administration interfaces are for creating and managing catalogs, whereas end user interfaces are for looking catalogs. The administrator can create different administration interfaces; for example, it is attainable to divide up administrative responsibilities by roles, utilizing a unique interface for every role.

Every kind of things in Content material Engine (iMerge) (together with lessons, relations, agents, chores, and others) are classes. Administrators can create, modify, search for, and delete courses and situations of classes. Directors may also customize the appearance and conduct of present classes. For example, you presumably can management the order and styles (examine bins, menus, and so forth) of attribute relations showing on classes.

Constructing a Schema and Defining a Reference Schema

One of many key duties in utilizing Content Engine (iMerge) to create catalogs is to construct schemas. The true power of Content Engine (iMerge) comes from the flexibility to mixture catalogs from multiple knowledge sources, which requires designing a reference schema. Lastly, you'll have the opportunity to create person schemas, which are subsets of the reference schema.

A schema determines which objects customers see and which items of data they can view and update. It consists of a set of classes and a set of relations. A schema could comprise a group of lessons, their attributes, and a few tables. Info organized in numerous schemas poses some challenges, notably in searching and updating. Content Engine (iMerge) integrates a broad range of schemas into a flexible, accurate, and responsive information source. By enabling you to create a single catalog out of multiple catalogs (every with its own schema), Content material Engine (iMerge) resolves two varieties of heterogeneity:

Bodily heterogeneity. Data is distributed amongst totally different places and saved in different formats.
Conceptual heterogeneity. Problems of conflicting terminology, totally different structures, and missing information exist.

Writing Rules

Probably the most powerful features of Content material Engine (iMerge) is the way it handles rules, which let you specific relationships between tables. Guidelines play a key role in fixing the integration problem. Additionally they provide assist to implement constraints;for example, you may implement enterprise rules and verify for knowledge-entry errors.

No programming is necessary to construct a catalog in Content Engine (iMerge). The administrator defines guidelines in Content Engine (iMerge) via a degree-and click interface. This approach is more modular and makes it a lot simpler to write down and debug rules; you strategy every downside case by case. Modifications in information or guidelines for a vendor or buyer do not affect other distributors and buyers. Also, if one vendor’s knowledge supply goes down, only that vendor’s data goes down (until the catalog is cached in Content material Engine [iMerge]).

View Management

Content material Engine (iMerge) enables varied groups of customers to see totally different views.Whereas the general expertise is analogous for all customers, some groups require completely different levels of access than different groups. The catalog administrator controls access. For example, the catalog administrator can:

Create a view that shows price information and one other that doesn't ? Prevent users from accessing a view that they are not approved to see by using a few of the security mechanisms obtainable in Content Engine (iMerge)

Relational Logic Aggregation

The RLA (Relational Logic Aggregation) in Content material Engine (iMerge) is exclusive in its potential to deal with catalog issues. Relational logic extends the relational algebra present in commercially obtainable databases with functions to deal with lacking or incomplete information.RLA extends this highly effective relational logic to take care of enterprise guidelines and data from heterogeneous sources.

RLA contains a browser-based mostly mapping facility that allows non programmers to add new provider mappings, discrete purchaser mappings, and different crucial specifications with none programming. Through a sequence of dialogs, the issues dealing with information sources, incomplete or missing knowledge, and knowledge access are all addressed.

RLA addresses differences in information format. A multi vendor catalog should cope with the fact that completely different distributors store catalog data in several formats, together with relational databases, XML (out of date), tab-delimited text, and Net pages. Even when a single widespread format may very well be discovered, requiring distributors to change to a single format would not be desirable or practical.With its distinctive instruments, iMerge permits distributors to maintain most of their information in the unique form. iMerge can:

Connect with knowledge in relational databases directly, without importing the knowledge
Import information in many structured formats
Extract information from unstructured sources

Dynamic Sourcing Architecture

What makes the RLA and the PCCS usable is the unique DSA (Dynamic Sourcing Architecture) of Content material Engine (iMerge). DSA consists of three parts:

In-memory object-relational database engine
Dynamic caching
Powerful question optimizer

Content Engine (iMerge) has a novel in-memory object-relational database engine. This in-memory structure eliminates the overhead usually related with disk access and sophisticated relational databases. When dealing with a whole lot or thousands of consumers and suppliers, the fast response time and scalability provided by Content material Engine (iMerge) are critical.

The in-memory engine also permits the administrator of the Content Engine (iMerge) software to dynamically change the finest way knowledge is accessed with out altering the purposes using the database. More specifically, data might be cached locally reasonably than accessed from a distributed website simply through point and click. The catalog administrators have the pliability to deal with points such as security, community performance, availability, and backup/recovery.

Content material Engine (iMerge) makes use of the metadata for the Commerce-ready Catalog and the mappings for suppliers and buyers to implement the most recent query optimization techniques. Content material Engine (iMerge) is conscious of if knowledge is cached or remote and, more importantly, which suppliers may doubtlessly have the correct information. Entry plans are calculated to provide the perfect entry to the data. Data is then passed to the in-memory database for processing and presentation to the user.

DSA for Catalog Updates

One other challenge in aggregating data from a number of sources is preserving the information in the grasp catalog contemporary whilst distributors update information in their own particular person catalogs. Content Engine (iMerge) uses dynamic sourcing to ensure data foreign money when the information just isn't stored in Content Engine (iMerge). By means of dynamic, real time queries to individual sources with altering structures, Content Engine (iMerge) maintains a continuing flow of correct information. A related problem overcome by Content material Engine (iMerge) is holding the catalog running as distributors are added and removed. Due to Content Engine (iMerge)’s modular architecture and the rule-based approach in which relationships in a catalog are outlined, directors can take away a vendor’s catalog without disrupting the master catalog; no software needs to be recompiled, so the catalog can function with no downtime. Similarly, including a new vendor’s catalog is largely a matter of writing guidelines that map the brand new source to the master catalog. The adjustments are immediately visible in the application. Finally, if one of many sources goes down as a end result of of site-specific technical issues, users can proceed to get solutions from the remaining sources.

Other parts of the catalog are:

ACP (Auto Catalog Publisher). ACP creates catalogs out of supplier texts and pictures and deposits the created catalog on MarketSet. e-mails are sent to the provider, to registered consumers, and finally to Content material Refinery if conversion is requested.
Content Refinery/XCP (XML Content Pipeline). XCP adjustments formats of the catalog, for instance, from Requisite catalog to a different format.
MarketSet Analytics. The BIConnect (Enterprise Intelligence Connector) component from SAPMarkets converts XML paperwork into BWXML, a format suitable with the SAP BW (Business Data Warehouse). This enables marketplace house owners to simply apply the powerful analytics and reporting capabilities of BW to the marketplace data.

BIConnect is based on SAP Enterprise Connector with new Java providers for integration with the completely different information sources from the marketplace.

MarketSet Bulletin Board

The Bulletin Board (BB) enables companies to quickly share and locate info any form, together with enterprise opportunities (for example, auctions, RFP/RFQ processes, exchanges, categorized commercials) from the DPE. Any XML-enabled utility can put up communications on the Bulletin Board with a fixed XML format.

The Bulletin Board helps the full life cycle of broad-based mostly enterprise communications, from posting and publishing by means of tracking and retiring. Every of these postings known as a “word,” like a word posted on an actual bulletin board. Initiators (marketplace users creating a be aware) might use the Bulletin Board immediately

Respondents (market users enthusiastic about discovering and replying to a word) could browse or seek for notes in a big selection of ways utilizing the Bulletin Board. The Bulletin Board is scalable to the needs of the largest electronic marketplaces and fully supports integration with different marketplace services. In addition to being carried out using servlets, JSPs (Java Server Pages), and EJBs (Enterprise JavaBeans), the Bulletin Board communicates with different market companies using XML messages passed with XML Commerce Connector (XCC). These XML messages are written to the xCBL normal published by CommerceOne.As a end result of XML messages are designed for transport over the Internet, the Bulletin Board can obtain messages from companies on other marketplaces or from enterprises. This allows one marketplace to combination listings from a bunch of marketplaces or companies.

The Bulletin Board is constructed in a 3-tier architecture.

The presentation layer supplies an intuitive interface and a uniform way of creating notes.
The enterprise logic layer manages the notice life cycle.
The info layer shops the data.

This architecture permits owner/operators to scale their system from setups as small as one machine for all layers, up to one or more machines for every layer. In addition to scalability, this architecture additionally supplies software flexibility and service manageability.

Bulletin Board Options

The following are the main options of the Bulletin Board:

Connectivity with any marketplace service on any marketplace enabled with a laborious and fast XML format
Normal integration with MarketSet Enterprise and Market-Set DPE
Readily available integration with enterprise back-end techniques, for example SAP R/three
Enabling free-kind communication (be aware descriptions) and promoting by certified parties in a controlled atmosphere
Analysis of respondent requests for each posted observe
Full life cycle assist for initiators
Templates that pace creation of postings
Bookmarks and Favorites for a extra customized experience

SAP ABAP

MySAP Market Place Customer Interface

No comments :

Post a Comment