This document provides naming conventions for objects in the System Landscape Directory (SLD), Integration Repository, and integration Directory.
Consider the naming conventions provided as recommendations only. No particular standards for Naming Conversion in XI projects and it varies from client to client. If you choose to deviate from the recommendations, ensure that you nevertheless always follow the same general principle described.
This whitepaper, provided by SAP, is a must for those use SAP BW and it provides recommendations about jobs and tasks that have to be performed on a regular basis to ensure system performance and stability in a BW system. It may be also useful for you to check Daily BW Systems Checklist
In this paper, the term Web Service itself as the related terms WSDL, UDDI and SOAP are described to give an impression about the basic technologies in the field of Web Services.
Furthermore, information will be presented how to implement Web Services on a J2EE platform. Finally, the paper illustrates how to modify the J2EE view on Web Services in order to port them to the SAP Web Application Server.
This list of transactions is designed to guide a Basis Admin team member through the process of keeping tabs on major systems issues and root cause issues and trends for each system in the landscape.
This will only identify and help triage issues to Helpdesk, Infrastructure, OS team or DBA team, Basis or functional developers or whomever…but guarantees that each system in a landscape gets a regular, weekly look. The goal is to eliminate root causes of repeating issues.
Master data is reference data about an organization’s core business entitles. These entities include people (customers, employees, suppliers), things (products, assets, ledgers), and places (countries, cities, locations). The applications and technologies used to create and maintain master data are part of a master data management (MDM) system. MDM, however, involves more that applications and technologies, it also requires an organization to implement policies and procedures for controlling how master data is created and used.
With the launch of the NetWeaver platform, SAP introduces a new framework for developing browser based user interfaces, Web Dynpro. As it claims to be the user interface technology for all applications within the scope of NetWeaver, it comprises many complex concepts, such as a generic, platform independent meta model oriented on the Model View Controller (MVC) design pattern.
Web Dynpro allows the separation of design decisions, navigation issues and data modelling, which includes the concepts to store and transport data inside an application. Context Mapping and Model Binding, mentioned in the title, are twomechanismfor data passing inWeb Dynpro. Nevertheless this paper focuses not only on these issues, but also explains the basic principles concerning data management.
SAP NetWeaver BI Integrated Planning now has the ability to allow users to upload data directly into transactional cubes. The solution outlined in this paper provides a how-to guide to use flat file upload functionality in BEx. It also shows step-by-step how to use a query to preview the data uploaded before deciding whether to save (write) the data to the target cube. This is basically replicating the BPS file upload functionality in IP. The solution depicted in this paper provides the user with the familiarity of BEx, but with the flexibility of Integrated Planning.