Google+ EnjoySAP Introduction and SAP XML in ALE,IDOC,BAPI WEB Technologies - SAP ABAP

EnjoySAP Introduction and SAP XML in ALE,IDOC,BAPI WEB Technologies

EnjoySAP is the new generation ERP technology which makes the job of the people working with this great erp made easy.Here in this post we are going to deal with what is that enjoyment and how this technology is used in business connections with sap xml in ale,idoc,bapi and web technologies.

XML and the Business Connector :


Enterprise Connector is the SAP XML enabler. The Enterprise Connector allows SAP systems to ship and receive paperwork in XML format by way of the Internet. Business Connector is based on software from the company webMethods and is included free of cost in the standard SAP software.

XML within the Business Connector

As we have already talked about, XML is the new commonplace for sending documents by means of the Internet. One of the benefits of XML is the reuse of current Inter-internet expertise already in place like a language similar to HTML,HTTP as transmission protocol, and utilizing the proxies and firewalls already working in most of the present companies.

There are a quantity of substandards for XML in the ERP industries. Ariba has cXML, Microsoft defines the BizTalk initiative, RosettaNet has a multivendor initiative, and so on. So if your system desires to speak XML, it is going to need a translator from your inner doc illustration to the XML customary your companion speaks.

What Is the Business Connector?

Business Connector is Java-primarily based software program that speaks customary Web protocols like HTTP, HTTPS, FTP, or SMTP (e-mail). It is also capable of receive SAP IDOCs and remodel them into XML or vice versa, receive an XML document and send it to the SAP system as an IDOC. Enterprise Connector additionally has the possibility to receive XML BAPI calls and send them to SAP as RFC calls and vice versa, obtain a RFC call from SAP and remodel it into an XML doc to be despatched by the Internet to the next Business Connector and SAP system. It has built-in RFC client and server capabilities on one facet and Web protocols like HTTPS on the opposite side.

webMethods B2B Integration Server

Enterprise Connector has two essential components: the server and the developer. The server is a server program that is listening to HTTP, HTTPS, or FTP at customizable TCP/IP ports and listens to RFC calls on the other facet out of your SAP systems. You'll give you the chance to administer the server from a Internet server and define there which protocols and SAP programs it should use. Additionally, you outline the safety setting like person, person groups, and ACLs (access control lists) in an effort to define who can entry which Business Connector companies or functions.

The server additionally has routing capabilities. When the Enterprise Connector server receives an XML document or a BAPI name, it determines tips on how to route this by wanting on the supply, vacation spot, and doc sort information. Within the route definition you specify which protocol ought to be used and how you can tackle the true target. For instance, you can say that for IDOC types ORDERS from the SAP system C11 to the receiver SUPPLIER1, the FTP protocol should be used and determine which is the FTP server and person/password on the supplier side.

The server also has cache functions, used to improve the performance. For instance, to find a way to call a function module in R/3, the server needs the interface specification (export/import parameters). That is saved within the cache to keep away from wasting time within the future calls. One other instance is the standard Web cache like Net browsers when accessing to Internet server functions. Cache use is defined service by service as properly because the expiration time for the cache.

The developer is the second component in Enterprise Connector. It's a graphical Java-primarily based developer surroundings where you presumably can define or modify present providers within the Enterprise Connector server. The developer connects to the server usually by HTTP, so it could be put in in a distinct machine. The developer allows you to define the so-known as flow services. You can define circulate providers graphically, linking existing providers at Business Connector.

Enterprise Connector has a selection of defined services, for HTML, HTTP, or RFC, for example. Theses companies are grouped in interfaces, and the interfaces are grouped in packages that correspond to a Java class from the technical level of view. You can embody MAP functions in these providers, outline enter and output records, and graphically link the fields between both records with arrows. You'll give you the option to outline data based mostly on current DTD, DTD stored in a Internet server, or by hand. In this manner, it is extremely straightforward to map the SAP XML to the XML to be used in the conversation.You can even define new companies with Java, C/C++, and even Visual Basic.

From ALE/IDOCs to XML

SAP Business Connector is able to obtain XML from a SAP system and rework it routinely in SAP XML. In this means, Enterprise Connector can be utilized to attach ALE logical systems by the Web reusing your firewall and proxy settings and an affordable communication media to send and obtain the XML messages between the systems.

Alternatively, Business Connector can send and receive IDOCs in other scenarios, like in provider/vendor relationships, and remodel the incoming XML in an SAP IDOC or vice versa. On this approach, XML is expected to be a substitute of EDI in SAP systems.

From BAPIs to XML

With the XML RFC and XML BAPI specification, you possibly can ship an RFC name to the Business Connector, which is accountable for routing the call in an XML RFC document to the following Business Connector, which transforms it in an RFC name to the target system. The result's back in XML again and remodeled in customary RFC on the end. In this method we are ready to call functions between SAP methods (or exterior RFC servers or clients) utilizing XML and HTTPS as the protocol via the Internet. Right here you may see what an XML RFC call looks like.

Enterprise Connector additionally allows you to call a BAPI or RFC from a Web browser and get the result again, merging the parameters with an HTML template. In case you need to name BAPIs or RFCs from a browser, you should also have a look on the ITS functionality, as a consequence of it's extra highly effective for this particular issue.

Net Automation

Another functionality within Business Connector is the possibility to execute actions in a Internet server and examine the ensuing page. Think about that you want to know the supply status of your order and your courier company has a Internet server the place you may go online, enter the delivery number, and get the information. You'll give you the option to automate these steps in a service in Enterprise Connector and name this from ABAP, for example. This is a nice characteristic if your courier company has not XML-enabled the delivery standing functionality. Then again, a change in the Web server can power a change in your server definition. That’s why XML is beneficial to standardize dialogs between systems.

Use of XML in mySAP.com

XML is utilized in different SAP options like BBP for procurement with a browser with Internet catalogs to ship and receive orders. Typically, XML and the Business Connector are utilized in any SAP enterprise situation the place documents are exchanged by means of the Internet.The Enterprise Listing and Doc Alternate The SAP Marketplace solution included within the mySAP initiative has two important pieces. The Business Listing allows finding companions in the Marketplace that can aid you in your transaction. For instance, if you need to buy tins, you would like to know companies in a sure space that produce tins. Within the Business Listing, you will get an inventory of the chosen companies and different info like the URL the place the corporate has its catalog on the Internet. Clicking on the URL, you get transferred to the vendor catalog, where you probably can select the products you want and switch them to your purchasing basket with a protocol referred to as OCI (Open Catalog Interface). You then create your Purchase Order in your Purchasing system, which sends an XML purchase order to your Market mailbox.

Then the doc is handed within the Marketplace to the Enterprise Document Alternate, one other essential piece of software program within the Marketplace. It routes the order to the recipient mailbox and later will create a gross sales order within the vendor backend system. The Enterprise Doc Trade is utilized in different scenarios like auctions (public or closed) and routes the paperwork to the relevant mailboxes. Functions of Business Connector in mySAP.com Portals In truth, Enterprise Connector can be used within the SAP Marketplace solution so as to send and obtain XML documents with your partners. Also, the Business Connector you install in your system already has an entry for mySAP Marketplaces in order to configure the transport very easily. If you need to join your SAP backend system to a mySAP Marketplace, you need only to configure in a display in your Enterprise Connector the URL of the Market and the logon information, just like the mailbox assigned to you in the marketplace. It's only a matter of hours to
be linked to a mySAP Marketplace with the Business Connector.

Extended Integration

The Internet and the Marketplace solutions will create new scenarios where the again-finish techniques of the partners can be integrated. New enterprise processes will seem that go through methods as properly as the enterprise processes in your organization undergo modules or departments. For these scenarios, new software program is required within the marketplace and within the back-end systems to allow a seamless integration.

To date, the main eventualities used within the market are sell/buy scenarios, growing step by step to dynamic pricing eventualities, like auctions. However other scenarios are appearing based mostly on collaboration between companies. Collaboration to be a part of purchases to get higher situations is clear, but there's additionally collaboration to transport the bought merchandise collectively or to forecast along with our partners. The mixing of processes could be achieved at completely different layers, like at the presentation layer, the application layer, and even the database layer.

Presentation Stage

Presentation level implies that a consumer connects to the companion portal and interacts with it. In this case, the consumer creates a doc in the associate system, however has to create additionally the doc in his own system. Technologies like mySAP Office will allow us to create Enterprise Portals with personalised interfaces with a goal to help this situation for our customers, suppliers, or resellers.

Application Stage: WebFlows

The integration at software level relies usually on trade of XML messages between the partners or between the marketplace and the partners.WebFlows or Workflows through the Internet will appear to allow the methods to send Workflow requests between them, additionally based mostly on XML standards. This is the most built-in approach with the applying logic and is what all distributors are making an attempt to supply.

Data Distribution Stage: Net Projector

The other possible integration layer may very properly be at the database level. The likelihood is to update database information or objects directly by the Internet utilizing XML SQL messages. Some databases are already permitting this, however the integration between totally different companies will probably be tougher at this degree as a result of it requires the knowledge of the internal representation at database level. This case might be successful for inner use in a company.

EnjoySAP and SAP R/3 Launch 4.6

EnjoySAP is the SAP initiative with the person on the center. As a friendly and more ergonomic interface, EnjoySAP has become the mySAP person interface.The EnjoySAP interface can be utilized with any release of SAP R/three above 3.1I. Nevertheless, it is just fully practical with releases 4.6 and upward, which are the releases prepared for supporting position-primarily based situations, personalization, Internet access from the Favorites menu, and so on. Due to the tight integration between the EnjoySAP interface and launch 4.6, initially (in 1999) release 4.6 was also referred to as the EnjoySAP release; nonetheless, it should be famous that EnjoySAP is the interface and must not be confused with the R/three release.

First releases of SAP R/3 4.6 included mainly the identical software functionality of the previous 4.5 releases but with many technical advances. The kernel (applications on the operating system stage) of 4.6D was, for a really lengthy time, the basis system for most of the mySAP parts till the arrival of the SAP Internet Utility Server. In the next sections, among the typical SAP Foundation components are introduced briefly for a better understanding of the system.

With the arrival of new Internet technology and the alternative of having a Javabased, platform-independent GUI, the strategy for consumer interfaces changed with the brand new world of mySAP.com e-business solutions. Let’s first evaluation the user interface technique, but think about that regardless of the platform or the implementation of the GUI, the look and feel of each of them is EnjoySAP, that is, with a common graphical setting, personalization services, and so on.

Person Interface Platforms

Over the years, SAP, in its great effort to be open and supportive of all platforms, has offered the normal SAPGUI in all available graphical environments, akin to Microsoft Home windows, OS/2, MacOS, OSF/Motif, and eventually browser support. In all these cases, the SAPGUI offered a common feel and look for all those platforms and behaves exactly the same from an software point of view.

It has always been crucial that the customers may perceive the system as pleasant and as easy as attainable, in addition to having as many personalization capabilities to make the day by day duties as efficient as possible. The user acceptance of the system usually had to do with how they perceived this graphical interface. The steady improvement of the interface, and the SAP personalization challenge again in late ’90s, had been key to the discharge of the EnjoySAP interface.

The EnjoySAP interface is centered on the usability of the systems. The EnjoySAP interface is supported in the traditional SAPGUI for Home windows, the SAPGUI for HTML, and the Java GUI. Different previously supported platforms should now use certainly one of these interfaces; as an example, there isn't any such thing as a extra development for the Mac or the Motif platforms because they can use both the SAPGUI for HTML or the Java GUI. Let’s briefly evaluate in the subsequent sections among the features of these GUI platforms.

SAPGUI for Windows

The SAP graphical user interface, generally recognized as SAPGUI, acts because the presentation
server, and it was typically accessible in all Microsoft Windows working methods, Motif, OS/2, and Macintosh. All of them look identical whatever underlying system SAPGUI was operating on. Since release 4.6 of R/three, and now with releases 6.10 and later, this interface will solely be available on the Microsoft Home windows platforms corresponding to ninety eight, NT/2000, or XP.

The SAPGUI consists of all graphical capabilities of modern Home windows interfaces, with push buttons, menu bars, toolbars, hypertext hyperlinks, on-focus descriptions, proper-clicking options, tab strips, and so on. The graphical design and performance is homogeneous across the complete system, which makes training simpler and simple for all ranges of SAP users. Determine 2-11 exhibits an example of the SAPGUI for Windows.



Relying on which R/three application or processing duties are going to be run, screens can be quite simple or can include a quantity of fields and graphical elements. Clients may also customise and create new menus and screens with the assistance of the Improvement Workbench or with the personalization capabilities available. The SAP R/3 presentation interface behaves very equally to another typical Home windows application.

Before EnjoySAP, there have been some shortcomings of the traditional SAPGUI, equivalent to:

1. Partitioned screens
2. Restricted personalization prospects
3. Many screens for single transactions

With EnjoySAP, the interface supplied a brand new interaction design the place it was attainable to entry full transactions from a single display screen, to have many personalization possibilities, tab-based mostly screens, and to have position-based mostly situations, so that different kinds of customers could have just the needed performance of their screens. It was even doable to have completely different fields in the same transactions for different sorts of users.

SAPGUI for HTML

The SAPGUI for HTML refers to the ITS on the server facet along with a Net browser on the desktop.With the SAPGUI for HTML, nearly all enterprise features of SAP functions-including enterprise capabilities for skilled energy customers-could be accessed. The ITS, and thus the SAPGUI for HTML, are also part of the mySAP Workplace. The SAPGUI for HTML requires no further software program on the desktop besides a Net browser. SAPGUI for HTML routinely maps the display screen components in enterprise transactions to HTML using Enterprise HTML functions obtainable throughout the SAP ITS. As a result, SAP ITS can dynamically generate a HTML model of a business transaction display screen that is related in layout.

To enhance the platform availability of the ITS, SAP has taken the primary steps towards providing a W-Gate for the Apache Net server on each Windows NT and Linux platforms. Which means the ITS now supports a 3rd Internet server-particular protocol Apache module in addition to ISAPI (Microsoft Web Information Server) and NSAPI (Netscape Enterprise Server) or any CGI Net server.

As of ITS 4.6D, the W-Gate architecture has been changed completely. The model new W-Gate configuration signifies that you now not have to connect each virtual ITS to a separate virtual Net server. Furthermore, one W-Gate can now communicate with multiple A-Gate, and these A-Gates can either be installed on the identical machine or completely different machines.

SAPGUI in Java

The event of GUIs in environments akin to Motif for UNIX methods, Mac or OS/2 developed into the Platform Independent GUI. Platform Unbiased (Platinum) GUI is the model new technology of SAPGUI, which is being designed with the goal of getting the identical look and working in precisely the same way, no matter the underlying platform and operating system. It additionally has the design goal of integrating all new obtainable applied sciences within the person interface. Java SAPGUI is the R/3 interface for connecting to the system by means of an intranet or the Web[ JC1][ JAH2], with the basic benefit of providing an amazing degree of independence on the platform when executing transactions.

Related Posts:



SAP definition,full form,over veiw and introduction
SAP Full form of planning and distribution of goods
SAP full form for mrp,sales and materiel planning

No comments :

Post a Comment