An Introduction to SAP

An Introduction to SAP

SAP was founded in 1972 in Walldorf, Germany. 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 new standards for providing business information management solutions.

SAP products are considering excellent but not perfect. The main problems with software product are 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, Development, Quality Assurance and Production.

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 users use to perform their daily job functions.

To all company, the production system should only contains transport that have passed all the tests.

SAP is table drive customization software. It allows businesses to make rapid changes in their business requirements with a common set of programs. User-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.

This is what makes ERP system and SAP in particular so flexible. 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 standard programs and tables should not be changed as far as possible. 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.

What is Client? What is the difference between Customization and Configuration?

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.

Configuration vs. Customization 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. *-- Sivaprasad, Sonali Sardesai

What is SAP R3? 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 SAPs software each component (or "layer in R/3s 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.

What is SAP Land scape?

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 landscape DEV, QAS and PROD.

- DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test. - QAS may again have multiple 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 (remember, 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.

In summary: 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 members and other members 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 user 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.

Find the list of SAP Transaction codes

Where I can find the list of transaction codes and their usage, I heard that there is some table which contains all the transaction codes with their descriptions.

Does anyone know about the Table that consist all the T-Code?

Listed here are the various ways you can find the list of transaction codes and their usage:

Use transaction SE11 - ABAP Dictionary:

Fill in the Database table name and click the Display button. - TSTC table will contain all the Tcodes and - TSTCT table will contain all the Tcodes with Texts.

Once you entered the screen, click in Top Menu - Utilities - Table contents - Display

If you want to display all the transaction code (total - 57,048) you have to change the Fields: Maximum number of hits to 99999 (default 500).

or

Simply goto transaction SM01, although this tcode is to Lock/Unlock any transaction code, you can also view all the tcode available in the R/3 system from here.

or

Goto transaction SE93

There are two ways where you can find the list of transaction codes in SE93.

Method 1: You must be familiar with the starting characters strings for each of the R/3 application modules.

Assuming you know that most Materials Management transaction codes start with MM.

In the Fields: Transaction code, type in MM* and press the function key F4

The list of transaction code starting with MM will be displayed.

Method 2: On the Top Menu, click Utilities - Find - Execute and the first 500 transaction will be display.

If want to display all the tcodes, make sure you remembered to change the Fields: Maximum no. of hits right at the bottom of the screen.

I know a particular T Code and can enter and work on it. How do I know what is the menu path for that T Code?

Enter Search_SAP_Menu in the command box and when the pop box appears enter, the Tcode and it will give the nodes and menu path. This is helpful only in case of SAP Menu not in case of SPRO - ie IMG.....

Easy to Remember (SAP Transaction Codes)

SPRO DEFINE ITEM CATEGORY

MM01 CREATE MATERIAL

MM02 MODIFY MATERIAL

MM03 DISPLAY MATERIAL

MMS1 CREATE MATERIAL MASTER

MMS2 CHANGE MATERIAL MASTER

MMS3 DISPLAY MATERIAL MASTER

MB1C MAINTAIN STOCK

MMPI INITIALISE PERIOD FOR MASTER MATERIAL RECORDFROM CO CODE

MMBE CREATE STOCK

MM60 MATERIAL LIST

XD01 CREATE CUSTOMER

XD02 MODIFY CUSTOMER

XD03 DISPLAY CUSTOMER

VA01 CREATE ORDER

VA02 CHANGE ORDER

VA03 DISPLAY ORDER

VA11 CREATE INQUIRY

VA12 CHANGE INQUIRY

VA13 DISPLAY INQUIRY

VA21 CREATE QUOTATION

VA22 CHANGE QUOTATION

VA23 DISPLAY QUOTATION

VD02 CHANGE SALES PROSPECT

VD03 DISPLAY SALES PROSPECT

VD04 DISPLAY CHANGES

VD06 FLAG FOR DELETION

VK11 MAINTAINING PRICING

VK0A ASSIGN G/L ACCOUNT GENERAL

VOK0 PRICING

VOR1 DEF COMMON DIST CHANEL

VOR2 DEF COMMON DIV

VOV6 DEFINE SCHEDULE LINES

VOV8 DEFINE SALES DOC TYPE

VOFA CREATE/OR CHANGE BILLING TYPES CONFIGURATION

V129 DEFINE INCOMPLETENESS SCHEMAS FOR FOREIGN TRADE

V149 ASSIGN INCOMPLETENESS SCHEMAS FOR COUNTRY CODE

CA01 CREATE ROUTING

CA02 EDIT ROUTING

CA03 DISPLAY ROUTING

CS01 CREATE BOM

CS02 CHANGE BOM

CS03 DISPLAY BOM

OVK1 DEFINE TAX DET RULES

OVK3 DEF TAX REL OF MASTER RECORDS CUSTOMER TAXES

OVK4 DEF TAX REL OF MASTER RECORDS MATERIAL TAXES

OVR6 DEF LEGAL STATUSES

OVS9 DEF CUSTOMER GRP

OVRA MAINT STATISTICS GRPS FOR CUSTOMERS

OVRF MAINT STATISTICS GRPS FOR MATERIAL

OVXC ASSIGN SHIIPING POINT TO PLANT

OVX6 ASSIGN PLANT TO S.O AND DIST CHANEL

OVLK DEFINE DELIVERY TYPE

OVSG DEFINE INCOTERMS

OVLH DEFINE ROUTES

OVXM ASSIGN SALES OFF TO SALES AREA

OVXJ ASSIGN SALES GRP TO SALES OFFICE

OMS2 MATERAIL UPDATE

OVLP DEFINE ITEM CATEGORY FOR DELIVERY

OX10 ASSIGN DEL PLANTS FOR TAX DET

O/S2 DEFINE SERIAL NO PROFILE

O/S1 DEFINE CENTRAL CONTROL PARAMETERS FOR SR NO

OBB8 DEFINE TERMS OF PAYMENT

OKKP ACTIVATION OF COMPONENETS

VB01 CREATE REBATE AGGREMENTS

VB02 CHANGE REBATE AGREMENT

VB03 DISPLAY REBATE AGGREMENT

VB31 CREATE PROMOTION

VB32 CHANGE PROMOTION

VB33 DISPLAY PROMOTION

VB21 CREATE SALES DEAL

VB22 CHANGE SALES DEAL

VB23 DISPLAY SALES DEAL

VB25 LIST OF SALES DEAL

VB35 PROMOTION LIST

VKA4 CREATE ARCHIVE ADMINISTRATION

VKA5 DEL ARCHIVE ADMINISTRATION

VKA6 RELOAD ARCHIVE ADMINISTRATION

VC/1 CUSTOMER LIST

VC/2 CREATE SALES SUMMARY

VDH2 DISPLAY CUSTOMER HIERARCHY

VF01 CREATE PROFORMA INVOICE

VF02 CHANGE PROFORMAINVOICE

VF03 DISPLAYPROFORMA INVOICE

VF07 DISPLAY FROM ARCHIVE

VF11 CANCEL BILL

VFX3 BLOCKED BILLING DOC

VFRB RETRO BILLING

VF04 MAINTAIN BILL DUE LIST

VF06 BACKGROUND PROCESSING

VF21 CREATE INVOICE LIST

VF22 CHANGE INVOICE LIST

VF23 DISPLAY INVOICE LIST

VF44 MAINT REVENUE LIST

VF45 REVENUE REPORTS

VF46 MAINT CANCELLATION LIST

VF31 ISSUE BILLING DOC

VFP1 SET BILLING DATE

VARR ARCHIVE DOCUMENTS

VL01N CREATE DELIVERY

VL02N TO CHANGE DELIVERY WHICH IS ALREADY CREATED

VL03N DISPLAY DELIVERY

V/08 TO CHANGE CONDITION (PR PROCEDURE)

V/30 DEFINE PRINT PARAMETERS

FD32 SETTING CREDIT LIMIT FOR CUSTOMER

/NSM12 TO REMOVE LOCK ENTRY

SM30

ND59 LIST CUSTOMER MATERIAL INFO

VB0F UPDATE BILL DOC

These are alternate Tcodes which are not

listed in SAP front end 4.7 enterprise edition either. Some examples are:

OY05 is also SCAL.

S_AHR_61016362 - PAR1- SAP Standard flexible report is also PAR1

S_AHR_61016369 - Employee List - PAR2.

Name two ways to start a transaction. - Dynamic Menu - Command Field

Why do you create user-specific parameters? 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 user. (Concept of PARAMETER ID)

Name the three different kinds of messages in the R/3 system. What is the difference between them? 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 user 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 user 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 user 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.

What is a data dictionary or repository? 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.

What is a matchcode? Comparsion key. A matchcode allows you to locate the key of a particular database record (e.g. account number) by entering any field value contained in the record. The system then displays a list of records matching the specifications.

If you want an end user to see a specific menu after logging on the R/3 system, how could you do that? User maintenance transactions allow the system administrator to create and maintain user master records. This includes the generation and assignment of authorizations and authorization profiles.

SAP FI/CO Tips and Financial Accounting/Controlling Discussion Forum

Practical and helpful SAP FI Stuff to assist those supporting the SAP Financial Accounting Modules. There are also sample questions and answers, interview questions, faq, importable tables on the SAP FICO module. If you have any SAP Financial Accounting and Controlling question, please feel free to raise it in the SAP FI/CO Forum.

The Financial Accounting (FI) application component fulfills all the international requirements that must be met by the financial accounting department of an organization. All accounting-relevant transactions made in Logistics (LO) or Human Resources (HR) components are posted real-time to Financial Accounting by means of automatic account determination. This data can also be passed on to Controlling (CO).

This ensures that logistical goods movements (such as goods receipts and goods issues) are exactly reflected in the value-based updates in accounting