What Spro Stands For 6o352a

c SPRO stands for SAP Project Reference Object . It is used to configure the setting as per your client requirement by using the standard setting present in the system. This where you can do all the SAP configuration work. It is also known as the Configuration Menu. c IMG :- Implementation Guide. SPRO :- SAP Project Reference Object. SPRO------>IMG. Type in the T-Code SPRO under That got to Main Menu which is IMG. SPRO is basically used to organize the consultant customizing during the SAP Project Phrase. If we want to stop a transaction in the middle, Right click on the end button (X) on the top right corner of the window. Then select "stop transaction". As we dont have STOP icon as we have in WINDOWS, this will help in the same way. Its a very small tip, but will help a lot. ! " - Dynamic Menu - Command Field c # They supply defaults to R/3 fields. If a field is indicated, the system automatically fills in default value. Depending on the field definition, the entry can also be replaced with a value entered by the . (Concept of PARAMETER ID) ! $ %&"c A message can have five different types. These message types have the following effects during list processing: A (=Abend): The system displays a message of this message type in a dialog window. After the confirms the message using ENTER, the system terminates the entire transaction (for example SE38).

E (=Error) or W (=Warning): The system displays a message of this message type in the status line. After the chooses ENTER, the system acts as follows: While creating the basic list, the system terminates the report. While creating a secondary list, the system terminates the corresponding processing block and keeps displaying the previous list level. I (=Information): The system displays a message of this message type in a dialog window. After the chooses ENTER , the system resumes processing at the current program position. S (=Success): The system displays a message of this message type on the output screen in the status line of the currently created list. c Central catalog that contains the descriptions of an organization's data and provides information about the relationships between the data and its use in programs and screens. The data descriptions in a Data Dictionary is also called metadata, i.e., data that describes other data. The ABAP/4 Dictionary stores system-wide data definitions. When you create a new data definition, the Dictionary tool does all the processing necessary to create the definition. You can use the Dictionary tool to look up the "definition" of objects in your R/3 System. c Comparsion key. A matchcode allows you to locate the key of a particular database record (e.g. number) by entering any field value contained in the record. The system then displays a list of records matching the specifications. $$ $ %&' maintenance transactions allow the system to create and maintain master records. This includes the generation and assignment of authorizations and authorization profiles.

c () By: Kunal Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD. - DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test. - QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training. - PROD may have something like a 200 Production. These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario. Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example). You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients. But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory. The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation. Landscape : is the arrangement for the servers IDES : is purely for education purpose and is NOT INCLUDED in the landscape. DEVELOPMENT ---> QUALITY ----> PRODUCTION

DEVELOPMENT : is where the the consultants do the customization as per the company's requirement. QUALITY : is where the core team and other test the customization. PRODUCTION : is where the live data of the company is recorded. A request will flow from Dev->Qual->Prod and not backwards. 1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process. 2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server. 3. Production Server: This is the last/ most refined client where the will work after project GO LIVE. Any changes/ new develpoment is done is development client and the request is transported to production. These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server. Presentaion Server- Where SAP GUI have. Application Server - Where SAP Installed. Database Server - Where Database installed. c $ ** %& R/3 stands for realtime three tier architecture. This is the kind of architrecture SAP R/3 system has. R/3 means three layers are installed in Different system/server and they are connected with each other. 1) Presentation 2) Application 3) Database c +++$ Golden client contains all the configuration data and master data so some extent. All the configuration settings are done in golden clients and then moved to other clients. Hence this client acts as a master record for all transaction settings, hence the name "Golden Client".

( ( SAP was founded in 1972 in Walldorf, . It stands for Systems, Applications and Products in Data Processing. Over the years, it has grown and evolved to become the world premier provider of client/server business solutions for which it is so well known today. The SAP R/3 enterprise application suite for open client/server systems has established a new standards for providing business information management solutions. SAP product are consider excellent but not perfect. The main problems with software product is that it can never be perfect. The main advantage of using SAP as your company ERP system is that SAP have a very high level of integration among its individual applications which guarantee consistency of data throughout the system and the company itself. In a standard SAP project system, it is divided into three environments, ,- '. ( . The development system is where most of the implementation work takes place. The quality assurance system is where all the final testing is conducted before moving the transports to the production environment. The production system is where all the daily business activities occur. It is also the client that all the end s use to perform their daily job functions. To all company, the production system should only contains transport that have ed all the tests. SAP is a table drive customization software. It allows businesses to make rapid changes in their business requirements with a common set of programs. -exits are provided for business to add in additional source code. Tools such as screen variants are provided to let you set fields attributes whether to hide, display and make them mandatory fields. / ( 0. The table driven customization are driving the program functionality instead of those old fashioned hard-coded programs. Therefore, new and changed business requirements can be quickly implemented and tested in the system. Many other business application software have seen this table driven customization advantage and are now changing their application software based on this table customizing concept. In order to minimized your upgrading costs, $ $ " The main purpose of using a standard business application software like SAP is to reduced the amount of time and money spend on developing and testing all the programs. Therefore, most companies will try to utilized the available tools provided by SAP.

c 1 c 1 2 1 $

The difference between cutomizing and configuration is: - CONFIGURATION: we will configure the system to meet the needs of your business by using the existing data. - CUSTOMIZING: we will customise or adapt the system to your business requirements, which is the process of mapping SAP to your business process. - CLIENT: A client is a unique one in organizational structure, can have one or more company codes. Each company code is its own legal entity in finance. 1 $ -"1 2 When considering enterprise software of any type, it is important to understand the difference between configuration and customization.The crux of the difference is complexity. Configuration uses the inherent flexibility of the enterprise software to add fields, change field names,modify drop-down lists, or add buttons. Configurations are made using powerful built-in tool sets. Customization involves code changes to create functionality that is not available through configuration. Customization can be costly and can complicate future upgrades to the software because the code changes may not easily migrate to the new version.Wherever possible, governments should avoid customization by using configuration to meet their goals.Governments also should understand their vendor's particular terminology with regard to this issue since words like "modifications" or "extensions" often mean different things to different vendors. *--- ' c (& We know that SAP R/3 is software, it particular it is client-server software. This means that the groups/layers that make up a R/3 System are designed to run simultaneously across several separate computer systems. When you install Microsoft Excel on your PC, each component of Excel (printing components, graphing components, word processing components, and etc.) is stored, managed, and processed via the hardware of your PC. When a company installs SAP¶s software each component (or "layer´ in R/3¶s case) is stored, managed, and processed via the hardware of separate and specialized computer systems. Each of the various layers is capable of calling upon the specialty of any of the other installed layers in order to complete a given task. Those components/layers that are requesting services are called ³clients´, those components/layers that are providing services are called ³servers´. Thus the term ³client/server´

c (/11 SAP is an ERP (Enterprise Resource Planning) module, ECC is the version of SAP, like 4.6, 4.6c and 4.7 in that series new version is ECC-6. Its known as Enterprise core component.

(c c , 3 SAP Business Information Warehouse (BW) is SAP s Data Warehouse solution. It has been specially developed to allow you to gather and analyze all kinds of statistical information in the best possible way. The SAP Business Information Warehouse (SAP BW) is a core element of mySAP.com. SAP BW is an enterprise-wide information hub that enables data analysis from R/3 and other business application, including external data sources such as databases and the Internet. SAP BW also offers easy integration with other mySAP solutions, such as mySAP Supply Chain Management (mySAP SCM), mySAP Strategic Enterprise Management (mySAP SEM), and mySAP Customer Relationship Management (mySAP CRM). SAP BW is a comprehensive end-to-end data warehouse solution with optimized structures for reporting and analysis. To help knowledge workers quickly mine an enterprise¶s business data, SAP BW is equipped with preconfigured information models and reports, as well as automatic data extraction and loading methods. With an easy-to-use Microsoft Excel-based interface, you can create, format, and analyze reports, and publish those reports to the web. Built for high performance, SAP BW resides on its own dedicated server. Online Transaction Processing (OLTP) and reporting activities are therefore separated, and system performance is not compromised. If you have any SAP Business Information Warehouse queries, please feel free to raise it in the SAP BW Forum .