SAP was founded in 1972 in Walldorf, Germany. It stands for Systems, Application s and Products in Data Processing.

Over the years, it has grown and evolved to b ecome the world premier provider of client/server business solutions for which i t is so well known today. The SAP R/3 enterprise application suite for open clie nt/server systems has established a new standards for providing business informa tion management solutions. SAP product are consider excellent but not perfect. The main problems with soft ware product is that it can never be perfect. The main advantage of using SAP as your company ERP system is that SAP have a ve ry high level of integration among its individual applications which guarantee c onsistency of data throughout the system and the company itself. In a standard SAP project system, it is divided into three environments, Develop ment, 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 mov ing the transports to the production environment. The production system is wher e all the daily business activities occur. It is also the client that all the e nd users use to perform their daily job functions. To all company, the production system should only contains transport that have p assed 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. User-exi ts are provided for business to add in additional source code. Tools such as sc reen variants are provided to let you set fields attributes whether to hide, dis play and make them mandatory fields. This is what makes ERP system and SAP in particular so flexible. The table driv en customization are driving the program functionality instead of those old fash ioned 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 customizati on 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 sho uld not be changed as far as possible. The main purpose of using a standard bus iness application software like SAP is to reduced the amount of time and money s pend 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 requiremen ts, 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 differenc

e is complexity. Configuration uses the inherent flexibility of the enterprise s oftware to add fields, change field names,modify drop-down lists, or add buttons . Configurations are made using powerful built-in tool sets. Customization invol ves code changes to create functionality that is not available through configura tion. Customization can be costly and can complicate future upgrades to the soft ware 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 termin ology 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. Th is means that the groups/layers that make up a R/3 System are designed to run simultaneously across several sepa rate computer systems. When you install Microsoft Excel on your PC, each component of Excel (printing c omponents, graphing components, word processing components, and etc.) is stored, managed, and processed via the hardware of your PC. When a company installs S AP s software each component (or "layer in R/3 s case) is stored, managed, and proces sed via the hardware of separate and specialized computer systems. Each of the v arious layers is capable of calling upon the specialty of any of the other insta lled layers in order to complete a given task. Those components/layers that are requesting services are called clients , those com ponents/layers that are providing services are called servers . Thus the term - cli ent/server . *-- Shailesh Kumar (shailesh_das@yahoo.com) What is meant by SAP ECC? 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 Enterpr ise core component.

Successfully inplementing sap Implementing a package can be a traumatic affair for both the customer and the v endor. Get it wrong and the vendor may get paid late or have to resort to lawy ers to get paid and tarnish their reputation. For the company the new package may not work the way they expected, be late or cost a more than budgeted for and take management will take their eye off running their business. Recently a client asked me what I would consider to be the five most important t hings one should consider before embarking on an implementation. This isn't a simple question, although there are many factors to think about after some consi deration for me the top five are way ahead of the others. My top five factors to consider would be: 1. 2. 3. 4. 5. Set up a Project Board, Secure the resources, Complete the GAP Analysis, Have detailed Cut Over Plans, Train the users.

Taking each one in turn:

The Project Board The correct set up and operation of the Project Board in my view is major factor in the success failure of the project. The Project Board will consist of the stakeholders, key users and the vendor. The Project Board is part of the gover nance of the project. The Project Board will meet regularly to ensure that the project plans are created and being executed as planned, moves from stage to st age with all the deliverables being signed off is resourced properly. The Resources Three types of resources are absolutely necessary -- end users, change team and technicians. Early involvement by the end users is absolutely necessary, as they will be the ones living with the system for hopefully many years to come. They will want t o feel involved in its implementation. Buy in from the end users of the system is absolutely essential if the system is to have a long and stable life in any organisation. The Change Team will identify the gaps between the package and the business requ irements, re-engineer some of the businesses process to cope with the package, t rain the users to ensure implementations is smooth as possible into the business . The Technical Team will prepare the systems environment for the package, apply a ny software fixes from the vendor, implement the software in the best way possib le for the organisation set up and tune the software for the particular technica l environment. GAP Analysis A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed a nd customised software can be developed close the gap, GAP must be closed but so ftware cannot be written therefore a workaround is required, GAP does not need t o be closed. In simple terms: Gap means small cracks. In SAP world. In information technolog y, gap analysis is the study of the differences between two different informatio n systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that spa ce. Actual gap analysis is time consuming and it plays vital role in blue print stag e. Cut Over Plans Detailed plans need to be developed for cutting over from the old system(s) to t he new. Parallel runs of what will happen over the conversion period using tes t data, convert and watch for a period after wards to ensure nothing unexpected happens. Train Users Well trained users will support and defend the system on site. Unsupportive use rs will continually undermine the system and eventually it will be replaced. T herefore the more effort you put into helping the users master the system early the better.

Explain Cutover Activities/Strategies in SAP FI. Cutover Activities or Master Data Uploading Strategies Depending upon the when w e are going live. As per that, you have to give the information to your core te am. If you goling live at the middle you have to upload the all P&L Account ite ms and B/S Items. If you going live at the financial year start, you have to on ly Upload the B/S Items. Activities for Golive: 1. G/L Master Upload Thru BDC or LSMW (TC-Fs00 and extended one co code to ano ther company code Fs01) 2. Vendor Master Upload Thru BDC Or LSMW (Will be Taken Care By MM) 3. Customer Master Upload Thru BDC or LSMW (Will be Taken Care By SD) 4. Asset Master Upload(Thru As90) 5. Cost Element Master Upload 6. Cost Center Master Upload 7. Profit Center Master Upload 8. G/L Balances Thru F-02 10. Vendor Balances thru F-43 11. Customer Balances thru F-22 12. Customer Advances thru f-29 13. Vendor Advances thryu F-48 Before uploading Vendor Balances you have to take care of WHT(TDS) Information. *-- Satynarayana Difference between the User Exit & Gap analysis. Both are quiet a different and has a small relation. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench. its not new functio nality which we are trying to build in sap but its slight enhancement within the same code. Gap analysis is start point of Realization and once blue print is finished we ha ve to find the realization of sap system for client requirment and there will be certain gaps when compared to system fit. Those gaps can be closed either by r e-engineering of business process to fit with SAP or we have to use USER exits i n case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system. *-- V. Sridhar What is roll out of SAP Project? As per dictionary, Rollout means uct . Inauguration or initial exhibition of a new prod

As per SAP specific definition, rollout is the strategy for international SAP im plementation. Rollout strategy normally include the following - Whether to implement SAP simultaneously (also known as big-bang) in all the co untries, or - Go live in sequence of phased manner - Or to go for the combination of both (phased manner implementation for some of the countries and big-bang for others). Rollout strategy is the most important decision that a client can make during S AP implementation. Normally, steering committee decides the rollout strategy. SAP Basic

What is Purpose of R/3 The sole purpose of an R/3 system is to provide a suite of tightly integrated, l arge-scale business applications. The standard set of applications delivered with each R/3 system are the followin g: PP (Production Planning) MM (Materials Management) SD (Sales and Distribution) FI (Financial Accounting) CO (Controlling) AM (Fixed Assets Management) PS (Project System) WF (Workflow) IS (Industry Solutions) HR (Human Resources) PM (Plant Maintenance) QM (Quality Management) CRM (Customer Relationship Management) These applications are called the functional areas, or application areas, or at times the functional modules of R/3. All of these terms are synonymous with each other. Traditionally, businesses assemble a suite of data processing applications by ev aluating individual products and buying these separate products from multiple so ftware vendors. Interfaces are then needed between them. For example, the materi als management system will need links to the sales and distribution and to the f inancial systems, and the workflow system will need a feed from the HR system. A significant amount of IS time and money is spent in the implementation and main tenance of these interfaces. R/3 comes prepackaged with the core business applications needed by most large c orporations. These applications coexist in one homogenous environment. They are designed from the ground up to run using a single database and one (very large) set of tables. Current production database sizes range from 12 gigabytes to near 3 terabytes. Around 8,000 database tables are shipped with the standard deliver y R/3 product. What is SAP Ticket Handling tickets is called Issue Tracking system. The errors or bugs forwarded b y the end user to the support team are prioritized under three seviority High, M edium and Low. Each and every seviority as got its time limits before that we ha ve to fix the error. The main job of the supporting consultant is to provide assistance on line to th e customer or the organisation where SAP is already implemented for which the pe rson should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the ri ght solution in right time.This is the job of the support consultant. The issues or the tickets(problems) which are arised is taken care of on priorit y basis by the support team consultants. The work process in support projects are given below for your reference. 1. The customer or the end user logs a call through any tool or by mail (RADIX

). 2. Each one of the support team is a part of support group. 3. Whenever a customer logs a call he /she has to mention to which work group (by name). 4. Once the calls came to the work group the support consultant or the team nee d to send an IR (Initial Response) to the user depending upon the priority of th e calls. (Top,High,Med,Low,None) 5. Then the error is fixed, debugged by the support consultant or the team. The n after testing properly by generating TR(Transport Request through the basis ad min) 6. Then it is informed to the end user/customer/super user about the changes wh ich have moved to the production server by CTS process. These are the process. In summary, what I understand is that if any configurati on or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after ap proval the BASIS consultant has to transport it to the PRODUCTION client. An example: Tickets in SD can be considered as the problems which the end user or the employ ee in the company face while working on R/3. Tickets usually occur during the i mplementation or after theimplementation of the project. There can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline. To begin with , we should give "TICKET" to you for not knowing it. Here is an eg of a ticket raise: End user is not able to 1. Create Sales order for a customer from a New plant , since shipping point de termination is not happened . ( Without Shipping point the document becomes INCO MPLETE and he will not be able to proceed further like DELIVERY, BILLING). He raises a ticket and the priority is set in one of the below: 1. Low 2. Medium 3. High. Now you need to solve this ticket. You would analyze the problem and identify th at the SP configuration has to be done for the new plant. You would request a transport for DEV CLIENT to BASIS. You do the change and Req uest one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it. Finally, you request a transport to move the changes to PRODUCTION. Once the cha nge is deployed in production the TICKET is closed. What I have given is a smal l example. You would get some real issues with severity HIGH in your day-day sup port. Role of a mySAP Functional Consultant What are the differences between a functional and business consultant? The difference between Functional consultant and Business consultant are as foll

ows: 1) A funcitonal consultant is able to configure the system unlike business consu ltant. 2) Functional consultant know more about business process unlike Business consul tant. 3) A business consultant will bring business process knowledge and provide it to functional consultant who in turn used this knowledge to configure the system. 4) Functional consultant has more configuration knolwledge then Business consult ant. *-- Rocky The responsibilities of a support consultant are: - Primarily responsible for Handling tickets and application support to the endu sers - When an issue comes diagnose, analyse and solve the issue - Responsible for any enhancements - Writing functional specs and interacting with Abapers to develop any user exit s - Training the end users and preparing end user training material *-- Sistla For those who wished to know the role of a functional consultant. Below is one view: A functional consultant evaluates the demands in talking with the customer's rep resentatives, transforms the essence into an abstract and algorithmic business m odel. Hence, he identifies the use cases and transforms them into logical and te chnical views. Then the main task starts: customizing the respective business area and making s ure the system reacts in the manner according to the constraints of the requeste d use case. The consultant documents the settings and prepares proper guidelines that allow other consultants to do further changes or repairs with due efforts. The consultant takes care that proper training is given to the users and that th e system is usable, performing appropriately and the business flow is complete a nd correct. During go live he assists the technical staff by testing the behaviour of the sy stem. After go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enhancements. The main duty of a consultant is to transfer external know-how to the client. It is not manpower that counts but intelligence, understanding of processes, a fee ling for defects and general a common sense. Role of a Functional Consultant in an End To End Implementation When you talk about the role of a Functional consultant in an end to end impleme ntation, I think it won't be possible for me or anybody to define everything but I will try to summarize it: 1. Functional consultant is expected to generate knowledge about the current bus iness process, design current business flows, study current business processes a nd its complication, in all we can say getting through with current business set up. Flow diagrams and DFD are prepared, most of the time in Vision format, all t

his forms the part of AS IS document. 2. Everything configured has to be documented as per their categories in the for m of predefined templates, these have to be then approved by the team leads or w ho ever the consultant is reporting to. 3. Mapping and GAP analysis is done for each module, I have seen people defining integration after mapping, gap analysis and configuration is done, but as per m y experience in implementation, it is a simultaneous process. 4. Before starting configuring future business processes in SAP, the DFD/ERD ar e prepared, this documentation is called TO BE, which can be also siad as the re sult of mapping and gap analysis. 5. Sometimes Functional consultants are also expected to prepare test scripts fo r testing the configured scenarios. 6. End user manual and user training is also expected from F.Consultants. The project normally starts off with a Kick off meeting in which the team size, team members, reporting system, responsibilities, duties, methodlogy, dates and schedules, working hours which have been predicided are formally defined. ASAP, it won't be possible for me to explain it here, but all I can tell you abo ut it is that it is SAP standard implementation methodology, which SAP prescribe s but is not mandatory for any company to follow, such as IBM follow some blue M ethodlogy, some companies follow typical SDLC steps, ASAP stands for Accerlated SAP, you can find all the steps on SAP site, through google, reading it from the re won't give you a great knowledge about ASAP but will obviously get you to kno w the definitions of various term. Landscape is like a server system or like a layout of the servers or some may ev en call it the architecture of the servers viz. SAP is divided into three differ ent 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 th ey have been using in their previous implementations or how is the client's busi ness 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 c an 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 r equest pop up upon saving everytime. You save it under a transport request and g ive your description to it. Thus the configuration is transported to the Unit Te st 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 tran port by the Basis guy, you have all the configuration in the Testing client, jus t 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 satisfactor y unit test, you move the good configuration to the next SERVER (DEV). The incor rect or unsatisfactory configuration is corrected in Golden (may again as well b e 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 satisf actory. 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 fi nal 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 compa ny's requirement. QUALITY : is where the core team members and other members test the customizatio n. 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 t he 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 Pro duction 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 t hree way. Developer develop their program in Development server and then transpo rt it to test server. In testing server tester check/test the program and then t ransport 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. What is the meaning of "R" in R/3 systems? R/3 stands for realtime three tier architecture. This is the kind of architrectu re SAP R/3 system has. R/3 means three layers are installed in Different system/server and they are con nected with each other.

1) Presentation 2) Application 3) Database Why do we call client 000 as golden client? 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 ot her clients. Hence this client acts as a master record for all transaction setti ngs, hence the name "Golden Client". What SPRO stands for? 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 confi guration work. It is also known as the Configuration Menu. What is full form IMG and SPRO? How are they different from each other? 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 Pro ject Phrase. How to close a window? 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. Tips by : Bhaskar 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 automati cally fills in default value. Depending on the field definition, the entry can a lso 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 differ ence 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 transac tion (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 process ing 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 posit ion. S (=Success): The system displays a message of this message type on the output screen in the s tatus 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 pro vides information about the relationships between the data and its use in progra ms and screens. The data descriptions in a Data Dictionary is also called metadata, i.e., data t hat 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 creat e 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 databas e record (e.g. account number) by entering any field value contained in the reco rd. 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 maint ain user master records. This includes the generation and assignment of authoriz ations and authorization profiles. Master PA10 PA20 PA30 PA40 PA41 PA42 PRMD PRMF PRML PRMM PRMO PRMP PRMS PRMT PS03 PS04 Data Personnel file Display HR Master Data Maintain HR Master Data Personnel Events Change Hiring Data Fast Data Entry for Events Maintain HR Master Data Travel Expenses : Feature TRVFD Set Country Grouping via Popup Personnel Events Travel Expenses : Feature TRVCO Travel Expenses : Feature TRVPA Display HR Master Data Update Match code Info type Overview Individual Maintenance of Info types

Time Management PA51 - Display Time Data PA53 - Display Time Data

PA61 PA62 PA63 PA64 PA70 PA71 PBAB PT01 PT02 PT03

Maintain Time Data List Entry of Additional Data Maintain Time Data Calendar Entry Fast Data Entry Fast Entry of Time Data Maintain Vacancy assignments Create Work Schedule Change Work Schedule Display Work Schedule

Payroll PC00 - Run Payroll PC10 - Payroll menu USA PE00 - Starts Transactions PE01 PE02 PE03 PE01 - Schemas PE02 - Calculation Rules PE03 - Features PE04 - Create functions and Operations PE51 - HR form editor PRCA - Payroll Calendar PRCT - Current Settings PRCU - Printing checks USA PRD1 - Create DME SM31 - Maintain Table SM12 - Locked Secessions TSTC - Table Look up SPRO - IMG SE16 - Data Browser (Table Reports) PP03 - PD Tables PPOM - Change Org Unit PO13 - Maintain Positions PO03 - Maintain Jobs Benefits PA85 - Benefits - Call RPLBEN11 PA86 - Benefits - Call RPLBEN07 PA87 - Benefits - Call RPLBEN09 PA89 - COBRA Administration PA90 - Benefits Enrollment PA91 - Benefits - Forms PA92 - Benefits Tables - Maintain PA93 - Benefits Tables - Display PA94 - Benefits - Access Reporting Tree PA95 - Benefits IMG - Jump to Views PA96 - Benefits reporting PA97 - Salary Administration - Matrix PA98 - Salary Administration PA99 - Compensation Admin - rel. Changes PACP - HR-CH : Pension fund, interface General Reporting PM00 - Menu for HR Reports PM01 - Dialogs in HR - Create Custom info types PRFO - Standard Form PSVT - Dynamic Tools Menu PAR1 - Flexible Employee Data PAR2 - Employee List Organizational Management

PPOM PO03 P013 PO10 PP01 PP02 PP03 PP05 PP06 PP07 PP69 PP90 PP01 PP02 PP03 PP04 PP05 PP06 PPOA PPOC PPOM PPOS PQ01 PQ02 PQ03 PQ04 PQ06 PQ07 PQ08 PQ09 PQ10 PQ11 PQ12 PQ13 PQ14 PQ15 PSO5 PSOA PSOC PSOG PSO1 PSOO PSOS PSOT

Change org Unit Maintain Jobs Maintain Position Maintain Organizational Unit Maintain Plan Data (menu-guided) Maintain Plan Data (Open) Maintain Plan Data (Event-guided) Number Ranges Number Ranges Maintenance HR Data Tasks/Descriptions Choose Text for Organizational Unit Setup Organization Change Cost Center Assignment Display Cost Center Assignment Change Reporting Structure Display Reporting Structure Change Object indicators (O/S) Change Object indicators OS Display Menu Interface (with dyn.) Create Organizational Unit Maintain Organizational Plan Display Organizational Plan Events for Work Center Events for Training Program Events for Job Events for Business Event Type Local Events Resource Events Events for External Person Events for Business Event Group Events for Organizational Unit Events for Qualification Resource Type Events Events for Position Events for Task Events for Company PD : Administration Tool Work Center Reporting Job Reporting Org Mgmt General Reporting Tools Integration PA-PD Organizational Unit Reporting Position Reporting Task Reporting

Recruitment PB10 - Initial Entry of applicant master data PB20 - Display applicant master data PB30 - Maintain applicant master data PB40 - Applicant events PB50 - Display applicant actions PB60 - Maintain Applicant Actions PB80 - Evaluate Vacancies PBA0 - Evaluate Advertisements PBA1 - Applicant Index PBA2 - List of applications PBA3 - Applicant vacancy assignment list PBA4 - Receipt of application

Execute the program RPDTRA00 to list all HR Transactions. The followings are some useful SAP HR Tcodes: PC00 PC10 PE00 PE01 PE02 PE03 PE04 PE51 PRCA PRCT PRCU PRD1 SM31 SM12 TSTC SPR0 SE16 PP03 PP0M P013 PO03 Run Payroll Payroll menu USA Starts Transactions PE01,PE02,PE03 Schemas Calculation Rules Features Create functions and operations HR form editor Payroll calendar Current Settings Printing Checks USA Create DME Maintain Tables Locked Secessions Table lookup IMG Data Browser (Table reports) PD Tables Change Org Unit Maintain Positions Maintain Jobs.

SE16 allows you to view data stored in different fields in tables ,structures et c . eg: absences stored for pernrs can be viewed in PA2001 also check out PA0000 , PA0001, PA0002 SM30/31 would allow you to maintaining the values in these tables eg: absences t o be configured can be done thru SM30 check out v_001p_all ; v_503_all ......etc What the difference between the transaction codes SE16 & SE16N? SE16 is a normal transaction. SE16N is an Enjoy Transaction. Enjoy Transaction is nothing but having some graphics and look is completely dif ferent with the normal transaction. 1. What is the role of SD Consultant in Testing while implementing the project? 2. What is Unit testing and Integration Testing? Testing : the core team members along with endusers will test whether the postin gs done in SAP is resulting as per the requirements of the organisation. They w ill test whether the output documents such as purchase order, invoice document a re printed in the required format and showing the correct data. Unit testing is refer to the module which are going to implement. SD, MM, FICO e tc. there will be test script based on that testing will be performed. Integration testing will be cross the modules. MM-SD-FICO for example. Integrat

ion testing is also called SIT ( System integration testing) Testing mathologies and types: there are 6 types of testings: 1. Unit Testing 2. System Testing 3. System Integration security Testing 4. Performance Testing 5. User Acceptance testing 6. Regression Testing Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then in voice. Whrereas System testing you will be testing the full cycle with it's integration , and you will be testing using test cases which give a full cyclic test from or der to invoice. Security testing you will be testing different roles and functionalities and wil l check and signoff. Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software. Regression testing is reffered to a test which verfies that some new configurati on doesnot adversly impact existing functionality. This will be done on each ph ase of testing. User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various bu siness processes. The user test model is comprised of a sub-set of system integr ation test cases. We use different software during testing. Most commonly use are Test Director: which is used to record requirement, preparing test plan and the n recording the progress. We will be incorporating defects that are coming duri ng these testings using different test cases. Mercury Load Runner: is used for performance testing. This is an automatic too l. What does the following terms means : - Technical Unit Testing - Functional Unit Testing - IntegrationTesting - Volume Testing - Parallel Testing? Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the de veloped code works and that it performed the process as as designed. Functional Unit Testing= Test of configuration, system settings or a custom deve lopment (it may follow the technical unit testing) These usually use actual data

or data that is masked but essentially the same as a real data set. A successfu l test shows that the development or configuration works as designed and the dat a is accurate as a result. IntegrationTesting= Testing a process, development or configuration within the c ontext of any other functions that the process, development or functionality wil l touch or integrate . The test should examine all data involved across all modu les and any data indirectly affected. A successful test indicates that the proce sses work as designed and integrate with other functions without causing any pro blems in any integrated areas. Volume Testing= testing a full data set that is either actual or masked to insur e that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test i ndicates that the processes will not slow or crash the system due to a full data set being utilized. Parallel Testing= Testing the new system or processes with a complete data set w hile running the same processes in the legacy system. A successful test will sho w identical results when both the legacy system and new system results are compa red. I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several. What kind of testings that are carried out in testing server? 1. Individual Testing ( Individually which we've created) 2. Regressive Testing ( Entire Process) 3. Integration Testing ( Along with other integrated modules) The 3 types of testing is as follows:1. Unit testing (where an individual process relevant to a SD or MM etc is teste d) 2. Integration testing (where a process is tested that cuts across all areas of SAP). 3. Stress testing (where lots of transactions are run to see if the system can h andle the data) Roles and Responsibilities of End User What is the Difference between Consultant & End users? SAP consultant role is to build the system, changes & modification/updation in c urrently installed SAP system for the end users. SAP End user only use the SAP system just to fetch some info, or to create new t hing. So a end user is just using the final product which it is meant for and co nsultnat design the product/updation and modification. The roles and responsibilities of end users is working in easy access menu they will not have authorizations of using img settings if they get doubt they will s end query to the implemented company and just entering day to day transactions. Roles and Responsibilities of End User:

Using the software at the end or after the implementation is an End User. In sap HR , we do come across entire Org Management creation by an end user afte r the Personnel strucutre is created. OM objects like creation of Org Unit mean s functional area or dpt , creation Job and Position and its occupancy is with i n the limits of an enduser. Initiallly the OM is created by sap consultant . In course of time a new department has appeared in the company of the client .. th is has to be created by the enduser rather than depending up on the implementor. .. similarly new job and position..like this small things are always done by the enduser. The entire work of OM is purely depends upon the enduser. After from this running Work Schedules) of each the show run of payroll es are there for an end periodical payroll and Ensuring of the Time schedules ( employee is done from sap easy access by an enduser and everymonth is by the enduser only. Like this lot of rol user.

Whatever the problems come across during the enduser utilisation of sap ...that will reach as ticket to the support team Tips by: Pascal, Nitin, Sushil Pandey, Somasekhar Explain what are the job responsibilities of END user & POWER user. One would need user id and password to access SAP be it a developer, consultant, administrator, or end user. End user is the one who performs transactions in SAP after it goes live. Such as posting an invoice, goods receipt, creating purchase orders, sales orders etc. Power Users are users with advanced knowledge in certain applications and with s pecial permissions or roles. They work in the specialist departments in the comp any and are available to other users as contact persons. During the SAP Implementation Project, what is the Role of Core Team Membere & C onsultants? The main responsibility of the core team member will to impart knowledge about t he companies processes to the SAP Consultants. The consultants will be providing the core team members with templets, that will describe the format of the AS-IS documentation wherein the core team members will write the different processes of the company into these documents and submit it to the SAP Consultants. The SAP consultants will then start mapping this into the system and provide the best possible solution that can be incorporated using the TO-BE documents. The main aim is to map the companies processes into the system. The SAP consultants will then train the core team members for how to use the SAP system. SAP HR Interview Questions 1) What is internal recruitment ? Internal recruitment is search for internal applicants. when you integrate with personal development, you can use profile match up which help to search for reso urces internally. Also In recruitment it is represented by 'P' as Person and 'AP" as external per

son. 2) What are problems generally faced while posting result to FICO ? Normally mismatching of amount get posted. 3) What is controlling area, what does it do, and how were is it assigned ? Controlling area is under of FI person which helps to set for costing purposes a lso based on thses fiscal variant is set. 4) What is the purpose of creating symbolic a/c, what is transaction code for sa me ? Can we assign one symbolic a/c to multiple wage types ? It depends upon your payrol requirement to create salary head like expense accou nt etc. 5) What is REPORT VARIANT FOR OFF CYCLE ACTIVITIES, what do we do in this step ? Variant is to save all input field parameters. once you saved as a variant , yo u can use the same for future purposes. 6) What all infotypes which has to be created at the time of hiring OR PA40 and cannot be maintained later with PA30 ? Why you require creation of infotypes... 7) If we have to create multiple positions, what method OR tool we can use to av oid errors due to creating them manually. You can create muliple position by LSMW or batch programs for the Tcode PP01 or PPOCE 8) What do is LANDSCAPE in SAP Project, I think its related to no. of servers us ed, Pls correct me if I am wrong, Or what it is ? It is related to Basis 9) What is the role of a administrator in PA ? To restrict access to Personnel administration based on PA/PSA. Administrator: we come across for Personnel admininstration, Time management, an d Payroll in sap . Each admiinistrator is reponsible for each individual activity. You can get the name of the administrator in the pay slip so the employee for any clarification he can meet the responsible administrator (accessed through payslip) This administrtor (is created in PA of PM) is responsible for recruitment. *-HR Tips by : Somasekhar 10) What is golive actually ? What is the role of a functional consultant in it ? Go live is transfering of data from Development server to Production server. Development -----> Quality server In Quality you need to Unit, Integration testing, Once it is OK in Qulaity serve

r, Then you need Development ----> Production See also; Implementing SAP 1) How to group employees for their allowances in payroll? Go to basic salary of india in Payroll india and group the employee first depend ing on the allowances to be paid and this is applied for even differantiating the employees into groups depending on their pa y structures. 2) In OM, how to get the details for group of employees (ex.) group of Drivers i n the organisation? Drivers can be identified depending on their position at which they are working and you can have a different job codes for them who do you want to look into. 3) How is Time managment and payroll is integrated? TM MGMT and Payroll are integrated in ways are time data is collected from the i nfo type 0007 and these hours are taken in basic as Number of hours worked or u tilizwed, and even with time evaluation and last with schemas integration. X000 schema carries xt00 and these data can be transfered between other modlues. 4) What are the other modules integrated with OM? OM contains all the modules to be integrated, depending client requirement it is done. As OM-PA, OM -RECT, OM-BENEFITS, OM-TRAINING & EVENT MGMT, OM - PD AND OT HERS. CHECK THIS BY GOING TO IMG --> CTRL F AND GIVE INTEGRATION WITH OM ) CHECK ALL OF THEM , GO FOR PROGRAM RHINTE00 PHINTE10 , PRHINTE20 , PHINTE30 AND 40 ALSO. 5) In TM, if group of employees get 10 days of annual leave, what will be the ti me evaluation status? TIME evaluation shows the exact details maintained over to the employee through his 2006 and 2001. if they are all allowed to take leave it shows leave as paid or unpaid depending on the configuration done by the consultant for these situat ion. in processing time data in payroll or even Time evaluation ( Valuation of absences ) also. 6) Find the scenario and give the result : A,B,C are employees, where A,B will get basic,HRA,DA. C gets Basic and DA. How to group for the allowances?. Allowances are paid depending on his gradation and even wages are also paid on t his criteria, if AB are paid bas, hra and DA then take three wage types ans assi gn to the ES Grouping and don't give HRA wage type to C. Check basic salary of inda and ALlowances in indian payroll thorougly, bcos firs t of all v have to undestand this first and then you have to decide the emp sub gtroupings. *-- Karthik