SAP Exchange Infrastructure, or SAP XI, is a component of NetWeaver that aids in the exchange of information between internal and external parties.
Its now SAP PI Process Integration, that means its not only Exchange Infrastructure (XI) its Process Integration (PI), integration of business Processes
SAP Enterprise Portal
The Enterprise Portal is an environment that allows everyone (Employees, Suppliers, Partners, etc) to get a perspective of required information in one place. The Enterprise Portal is cantered on the user. It creates an environment that provides all type of information to the user, from all sources, allowing the user to stay in the portal for 80% – 90% of the time.
The Enterprise Portal provides users with a centralized, easy-to-use access to all the information, applications and services they need to participate in collaborative business processes. A Enterprise Portal Solution must provide all users (Employees and External Communities) personalized convenient access (Point & Click, Drag & Relate, Single Sign-On) to everything needed (Information / Applications / Services) anytime, anywhere (Web Browser / Mobile Devices) in a secure way (Robust Security Features) to get their task or job done.
SAP NetWeaver is a business oriented integration platform, able to streamline current IT solutions and infrastructure. Microsoft .NET, Sun’s J2EE, and IBM WebSphere can be used along with SAP Netweaver.
SAP NetWeaver consists of 4 main layers: people integration (with components Multi Channel Access, Portal & Collaboration), information integration (with components Business Intelligence, Knowledge Management, Master Data Management), Process Integration (with the integration broker, business process management) and the application platform (with the Web Application Server - J2EE & ABAP). Over those 4 main layers you have the composite application framework and life cycle management.
Central User Administration (Extended)
An improved Central User Administration is available to you as of SAP NetWeaver ‘04. In particular, the following functions have been improved or added:
Central User Administration (CUA). These changes have also previously been delivered by
SAP Note. – The partner profiles and the corresponding Application Link Enabling model are automatically created when creating the CUA. – The synchronization of the company addresses has been integrated into the transaction Central User Administration Structure Display (user migration). – The improved RSDELCUA significantly simplifies the removal of the CUA. – The log display of the central user administration (CUA) for checking the status of IDoc distribution has a new, user-friendly interface. Performance when starting has also been significantly improved. You can also update the display in the result list, and select and distribute multiple users there.
For more information, see the SAP Library under SAP NetWeaver Components -> Security-> Identity Management -> Users and Roles -> Central User Administration.
Improvements to the User Master Comparison (transaction PFUD)
To improve the operability of transaction PFUD, the selection options were modified on the selection screen: – The option Manual Selection of Profiles has been removed. – The Complete Reconciliation option has been replaced with Perform User MasterComparison, with which you can execute the transaction in dialog. – The newly structured selections creen allows you to select four processing modes separately in dialog; profile comparison, composite role comparison, HR organizational management comparison, and cleanups. – The Replicate Local HR Assignments in the CUA Central System has been extended. You can choose this option if you are in a child system of a CUA, and HR organizational management is active. Indirect role assignemnts, which result from the local HR model are transferred to the CUA central system for information, and can be displayed in user maintenance there.
For more information, see the SAP Library under SAP NetWeaver Components -> Security-> Identity Management -> Users and Roles -> User Maintenance -> User Maintenance Functions -> Comparing User Master Records.
Statistical Functions in the Menu Maintenance for Role Maintenance (Transaction PFCG) The function Menu Statistics is now available on the Menu tab page. It provides information about the number of menu nodes and hierarchy levels. The system also differentiates between different types (folders, transactions and reports, URLS) for the number of nodes. – New and Changed Reports in the User Information System (Transaction SUIM) – The evaluation report RSUSR200 offers the extended selection criteria By User Type, By Validity of the User and By User Status.
For more information, see the SAP Library under SAP NetWeaver Components -> Security -> Identity Management -> Users and Roles -> User Information System -> Determining Users with the Users Node.
The new evaluation report RSSCD100_PFCG for determining change documents provides more selection options than report RSSCD100, which it replaces. This means that you receive a clear results list without unnecessary data.
For more information, see the SAP Library under SAP NetWeaver Components ->
Security -> Identity Management -> Users and Roles -> User Information System
-> Determining Change Documents.
Evaluation report RSUSR010 was extended so that you can determine which transactions can be started with a particular composite or single role.
For more information, see the SAP Library under SAP NetWeaver Components -> Security -> Identity Management -> Users and Roles -> User Information System -> Determining Transactions.
You can use Customizing switches to specify for the password generator in user maintenance (transactions SU01 and SU10) whether the passwords should contain special characters, and the maximum numbers of letters and numbers that are to be contained in the passwords.
The following new Customizing parameters, which you maintain in table PRGN_CUST are
introduced for this purpose:. – GEN_PSW_MAX_LETTERS (Maximum number of letters in generated password) – GEN_PSW_MAX_DIGITS (Maximum number of numbers in generated password) – GEN_PSW_MAX_SPECIALS (Maximum number of special characters in generated password)
For more information, see the SAP Library under SAP NetWeaver Components -> Security -> Identity Management -> Users and Roles -> User Maintenance -> Logon and Password Security in the SAP System -> Customizing Switches for Generated Passwords.
The authorization concept in the area of user and role administration has been refined by the introduction of the new authorization object S_USER_SAS and the adjustment of the existing authorization objects. With authorization object S_USER_SAS, you can make system-specific assignments in the user maintenance transactions (SU01 and SU10), the role maintenance transaction (PFCG) and the User Master Data Reconciliation (PFUD), and check the BAPIs of the Business Object USER.
For more information, see SAP Note 536101 and the SAP Library under SAP NetWeaver Components -> Security -> Identity Management -> Users and Roles -> SAP Authorization Concept -> Organizing Authorization Administration -> Organization if You Are Using the Profile Generator -> Authorization Objects Checked in Role Maintenance.
BI 7.0 Source System Definition for Source System with Basis Release lower than 640 is quite different.
As of release 640, you can use upper and lower case characters for user passwords. This is only uppercase characters for previous releases. Remember that your passwords are automatically converted to uppercase in previous releases.
As BI System has Basis 700 in bottom, upper and lower case passwords are important.
So, for defining source system is almost same as ordinary BW source System definitions.
One more important thing is that you have to take into account the EDI Ports. This may cancel your system definition if the settings are not correct. This settings must be controlled on both BI and Source System.
Here are the steps to configure Source System with Basis Relase lower than 640 in BI 70:
1. Take a look at table EDIPORT of your BW system and note the next free number for the field “Port”. This is the adjacent number of the highest entry like ‘A0000000123’ for example. In this case e.g. take ‘124’.
2. Choose transaction “snum” and object “ediport”.
Select “number ranges” from the menu “Goto” and here the button “status”.
Change the CURRENT NUMBER of the ranges to the next free number you noted from table EDIPORT.
If the number range of your BW system is correct please check the same in your OLTP system.
3. Call TCODE RSA1 on BI System in BI Client.
4. Select Source Systems on Left Menu
5. Left Click SAP System and Choose Create
6. Important think is, as source system has Basis Release Lower than 640, You have to give All Passwords (For BI ALEREMOTE User and for Source System ALEREMOTE User) in UPPERCASE.
My Favourite is giving RFCCPIC for ALEREMOTE Passwords.
7. It Must Be OK.
Symptom
SAP NetWeaver uses the usage type ‘Process Integration’ (this usage type includes all previous functions of the SAP NetWeaver Exchange Infrastructure and the Business Process Management functions) to support cross-system applications. In addition to their product, cross-system applications that are based on SAP NetWeaver deliver interface descriptions, mappings and other objects that are relevant for the exchange of messages. Customers must import these contents, the ‘Process Integration Content’ (XI Content) into the Integration Repository of SAP NetWeaver. The import is the prerequisite for configuring the cross-system application in the Integration Directory.
For SAP NetWeaver 7.0 (previously called SAP NetWeaver 2004s), you can import XI Content from SAP NetWeaver 7.0, XI 3.0 and also from XI 2.0 into the Integration Repository (all databases that are released for XI 3.0 or SAP NetWeaver 7.0 are also supported when you import XI 2.0 Content). The Integration Builder migrates the objects from XI 2.0 to SAP NetWeaver 7.0. The XI Content from XI 3.0 and the XI Content from SAP NetWeaver 7.0 are always compatible and can be imported into the Integration Repository without migration. The procedure described in this note applies to the migration and to the import of XI Content based on SAP NetWeaver 7.0.
Other terms
XI Content, Integration Repository, delivery, Integration Builder, Process Integration Content
Reason and Prerequisites
SAP NetWeaver 7.0 must already be installed in your system with the relevant Support Packages and the usage type “Process Integration”. A general description of the installation process is available in the Installation Guide on SAP Service Marketplace at http://service.sap.com/instguidesNW70. Also see the notes of the Master Guide for your cross-system application. The export and import of XI Content is not a task for individual developers, but rather for administrators or for those who are responsible for the organization of XI Content. Therefore, the functions for exporting and importing must be called only for users with the role SAP_XI_ADMINISTRATOR or SAP_XI_CONTENT_ORGANIZER.
Solution
The XI Content for an SAP application is available on SAP Service Marketplace at service.sap.com/swdc -> Download -> Support Packages and Patches -> Entry by Application Group -> SAP Content -> ESR Content (XI Content) ->
1. Obtain the export files for the XI Content of the cross-system application. The files are generally stored as zip files on SAP Service Marketplace (see above). You can use the naming convention of these zip files to determine their Support Package level (SP level):
2. Copy the export files into the import directory for the Integration Repository (“
3. Start the Integration Builder for the design time. To do this, log on to the SAP system in which the Integration Builder has been installed. To call the initial screen of the Integration Builder, use your user menu or call transaction SXMB_IFR. Then choose “Integration Repository”.
4. After you start the Integration Builder, follow the menu path “Tools -> Import design objects…” to import the XI Content. When you do this, only the files from the import directory (see above) are available for the import. The sequence in which you import the export files is not important.
5. After a successful import, the Integration Builder moves the imported tpz files into the directory “
If the release and the Support Package level are clear from the file name of the tpz file, simply leave the files in the directory “importedFiles” (see above). Note that the Integration Builder adds the date and time of the import to the file name of the imported export files if a file with the same file name already exists in the directory “importedFiles”. This enables you to check which file was last imported.
After a successful import, you can keep the packed files, from whose naming convention you can derive the Support Package level. Move them into the directory “importedFiles”, for example.
More information is available in the SAP Help Portal at http://help.sap.com, in the online documentation for SAP NetWeaver, in the section “SAP NetWeaver Exchange Infrastructure -> Design and Configuration Time -> Software Logistics for XI Objects”.
Purpose
SAP Exchange Infrastructure (XI) enables you to implement cross-system business processes. The aim of the Exchange Infrastructure is to integrate different versions of SAP and non-SAP systems implemented on different platforms (Java, ABAP, and so on). The Exchange Infrastructure is based on an open architecture, makes uses of open standards (in particular those from the XML and Java environments) and offers services that are essential in a heterogeneous and complex system landscape: Namely a runtime infrastructure for message exchange; configuration options for managing business processes and message flow; and options for transforming message contents between the sender and receiver systems.
Integration
The infrastructure is tailored to general standards so as to remain open for the integration of external systems. At the center of the infrastructure is a message-orientated communication that uses HTTP (Hyper Text Transfer Protocol). The application-specific contents are transferred in messages in freely defined XML (eXtensible Markup Language) schema from the sender to the receiver using the Integration Engine. The structure of a message is therefore determined by the interface data structures used.
The central concept is that, during the design phase, all interfaces required are initially developed independently of a platform and made available in the form of a WSDL description (WSDL: Web Service Description Language). Using this description you can, for example, define mappings between interfaces without this having an effect on an existing system landscape. All design phase data is saved in the Integration Repository to be implemented later in a particular system landscape. In this second phase, configuration time, you can select components, interfaces, and mappings saved in the Integration Repository that are appropriate for your system landscape and business processes and assign them to each other in logical routing. The result of this configuration process is saved in the Integration Directory and you can call and evaluate it from the Exchange Infrastructure runtime.
The integration knowledge of a shared process is therefore saved centrally in the Integration Repository at design time and in the Integration Directory at configuration time. In this way, SAP Exchange Infrastructure follows the principle of Shared Collaboration Knowledge: Information about a shared process need no longer be accessed in each of the systems involved, but called centrally instead. This procedure considerably reduces the costs for the development and maintenance of the applications shared.
Features
The Exchange Infrastructure enables you to do the following:
· Develop cross-system applications that exchange a multitude of system messages using the runtime infrastructure and synchronous or asynchronous communication. Develop new platform-independent interfaces or connect existing interfaces to the runtime using adapters.
· Produce a bird’s eye view of the business processes by using Business Scenarios and derive the interfaces and mappings required from them.
· Adjust message values and structures for the receiver using mappings.
· Centrally maintain the message flow between logical systems in the system landscape using logical routing.
· Connect the logical receiver to a technical system using end points; this system can be exchanged easier using this abstraction level (technical routing).
· Control access to your system using logon data.
· Describe your system landscape as the foundation for the description of your cross-system business processes by using the System Landscape Directory.
