1) What is the difference between SAP ERP and SAP ECC?

A) SAP introduced the mySAP ERP Application as a follow-up product of the SAP R/3 software. The latest release of mySAP ERP application is ECC 6.0. SAP ECC is part of the SAP ERP application. SAP ECC 5.0 is part of SAP ERP 2004. SAP ECC 6.0 is part of SAP ERP 6.0 (2005). Different SAP systems are Ex: ECC to CRM; ECC to SRM. ERP application is an integrated enterprise resource planning (ERP) software manufactured by SAP that targets business software requirements of midsize and large organizations in all industries and sectors. The company that provides the enterprise resource planning solution has upgraded the package and launched it as SAP ECC 6.0 in 2005. ECC stands for Enterprise Central Component. The purpose of positioning it as ECC is to enable SAP to build and develop an environment of other products that can function upon the foundation of the central component We can define ERP as a whole sum package and ECC as its main component. With the passage of time, a need for a business suite that would run on a single database and offer a pre-configured system with various scenarios was felt. This led to the introduction of the mySAP Business suite, which includes various applications such as mySAP CRM, SCM, SRM etc. ----------------------------------------------------------------------------------------------2) Types of Project(In notes). 3) Different phases of project (or) ASAP methodology(In notes) ----------------------------------------------------------------------------------------------4) What is meant by IDOC? A) IDOC is a 16-digit data container which SAP understands and is used to transfer the data b/w different SAP systems. IDOC means "Intermediate Document". IDOC transfers the data in the form of packets. The IDOC is a unique no. and will not be same for any 2 IDOCs. IDOC is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. In order to communicate with a non-SAP system, an IDOC is first transmitted to an intermediary system that translates the data to a format that will be understood by the receiver. Return data also passes through the translating system, where it is again encapsulated into an IDOC. The IDOC is transmitted to the receiver, which may be an R/3, R/2, or some external system. When we execute an outbound ALE or EDI Process, an IDOC is created In an inbound ALE or EDI process, an IDOC serves as input to create an application document. In the SAP System, IDOCs are stored in database. Every IDOC has an unique number(within a client). IDOCs are independent of the sending and receiving systems.(SAP-to-SAP as well as Non-SAP) IDOCs are based on EDI standards, ANSI ASC X12 and EDIFACT. In case of any conflict in data size, it adopts one with greater length IDOCs are independent of the direction of data exchange e.g. ORDERS01: Purchasing module : Inbound and Outbound

 IDOCs can be viewed in a text editor. Data is stored in character format instead of binary format. IDoc (Intermediate Document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs are used for data transfer in SAP's Application Link Enabling (ALE) system. Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. EX:- Lets take an example to understand this: Whenever a Purchase Order (PO) is created we want to send the IDOC to a vendor. The PO is sent in the form of an IDOC to the vendor (partner). That partner has to be EDI enabled in that system. SAP should realize that it could send doc to this vendor electronically. (Creating a vendor is not sufficient). Partner Profile should be EDI enabled i.e. A partner profile should exist in the sap system. Quotation, RFQ, PO, SO, Invoice, delivery challan etc are some of the commonly exchanged documents through IDOCs. We create only one profile for both inbound and outbound IDOCs. Partner profile should contain message typeto be able to exchange the IDOC. We define partner type, partner function and message type (it distinguish if an IDOC is being sent to same person in same function for different reason e.g. SO) There are 2 types of IDOCs. (i) Inbound IDOC: The data goes from our system to another system. (ii) Outbound IDOC: The data comes from other system to our system. ----------------------------------------------------------------------------------------------5) What is Partner Profile? A) We must maintain the business partners with whom we communicate via IDocs, in Partner Profiles. Steps to create Partner Profile - Goto Transaction WE20. - Click on Create Button. - Enter the Number of Vendor Created in Partner No. and LI in Partner Type fields. - Save the Data. - For Outbound Partner Profile we have to create Outbound Parameters - Specify Partner Function, Message type created, Port (create a port in WE21),Basic Type and Output Mode. - Goto Message Control Tab and link the Message Type and Process Code created. - Save. Change Application Data to be transmitted Change Purchase Order Created using transaction ME22n for the Vendor to which partner profile has been created. Go to Messages , add the new Message Type to the list and Save the Purchase Order.

 An IDOC will be created for the purchase order and will be dispatched to PORT mentioned. Check the status of IDOC (WE02). The IDOC status can be checked using transaction WE02. If the status is 03, it implies that IDOC is passed to Port. ----------------------------------------------------------------------------------------------6) What is meant by IDOC Filtering? A) I Doc filtering is nothing but wipeout unwanted IDOCs that are not required to receving partner. Let us suppose some message type iam sending from my central datbase sever to 5 Application Severs. Let it take as some plants in my company code. The master IDOC will contains the data pertaining to the five plants. In this case for Plant1 date is not reqiured pertaining to all the remaining plants i.e 2 3 4 5. In this case while creating the distribution model, we have to mention the filter keys. Then when ever the master IDOC passes through ALE service layer it will check for filter key' values for a receiver and it will wash out all the IDOCs otherthan the values and creates the communication IDOC. Always communication Idoc is the subset of Master Idoc. ----------------------------------------------------------------------------------------------6) What is the difference b/w Master IDOC and Communication IDOC? A) Let us suppose some message type iam sending from my central datbase sever to 5 Application Severs. Let it take as some plants in my company code. The master IDOC will contains the data pertaining to the five plants. In this case for Plant1 date is not reqiured pertaining to all the remaining plants i.e 2 3 4 5. In this case while creating the distribution model, we have to mention the filter keys. Then when ever the master IDOC passes through ALE service layer it will check for filter key' values for a receiver and it will wash out all the IDOCs otherthan the values and creates the communication IDOC. Always communication IDOC is the subset of Master IDOC. ----------------------------------------------------------------------------------------------7) What is meant by ALE(Application Link Enabling)? A) ALE Application Link Enabling is a mechanism by which SAP systems communicate with each other and with non-SAP EDI subsystems. Thus it helps integration of distributed systems. It supports fail-safe delivery which implies that sender system does not have to worry about message not reaching the source due to unavoidable situations. ALE can be used for migration and maintenance of master data as well as for exchanging transactional data. There are three layers in the ALE system: application services, distribution services, and communication services. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system. If the data is distributed from a master system, the same transaction performed by the sender will be performed by the receiving system, using the information contained in the IDoc. The messages that are exchanged are in the form of IDocs or Intermediate Documents. IDocs act like a container or envelope for the application data. An IDOC is created as a result of execution of an Outbound ALE. In an Inbound ALE an IDOC

serves as an input to create application document. In the SAP system IDocs are stored in the database tables. They can be used for SAP to SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data. Data from custom tables (created in customer namespace) is to be formatted into an IDoc and sent from one SAP R/3 system to another using ALE service. We need to have two instances of SAP R/3 systems or we can simulate this on two clients of the same SAP R/3 system. ----------------------------------------------------------------------------------------------8) What is meant by BADI? A) Business add-ins are enhancements to the standard version of the system. When the customer needs more functionality than the SAP standard Program(Functionality)then we can add extra functionality to standard SAP functionality through Badi. Badi can't distrub the orginial(standard)code. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software. We can differentiate between single-use and multiple use Business Add-Ins. The distinction is based on the procedure or event character of an enhancement. In the first case, the program waits for the enhancement to return something, usually a return code. A typical example could be a benefit calculation in HR. Depending on the implementation, alternative calculations can be executed. With multiple use add-ins, an event that may be of interest to other components is processed in program flow. Any number of components could use this event as a hook to hang their own additional actions on to. (OR) BADI IS USED TO ADD SOME ADDITIONAL FUNCTIONALITY TO THE STANDARD FUNCTIONALITY WITHOUT DISTURBING THE STANDARD FUNCTIONALITY. BADI stands for bussinesaddings and its for enhancements in the applicaion area .main use of it is reusabilty. When the customer needs more functionality than the SAP standard Program(Functionality)then we can add extra functionality to standard SAP functionality through Badi. Badi can't distrub the orginial(standard)code. Adding extra functionality to the standard is nothing but Add-in. Badi are not creted in the program itself. They are created and maintained seperately and called when we need the Badi. A Customer exit supports follows only procedure language. but BADI support Object oriented. That is why BADI is reusable component. BADI CONTAINS TWO SECTIONS: 1)BADI DEFINITION 2)BADI IMPLEMENTATION

You need to first define a BADI to enhance a SAP application program. The developer needs to create an interface for the BADI. An Adapter class is created from this that will implement the interface. Developers need to create an instance of the adaptor class in the SAP Application program and create method calls as required. ADAPTER CLASS IS TAKING CARE ABOUT THE VERSION CHANGE MANAGEMENT...OK SE18-----BADI DEFINITION SE19-----BADI IMPLEMENTATION ----------------------------------------------------------------------------------------------9) What is meant by BAPI? A) BAPI (Business Application Programming Interface) defined as an interface providing access to processes and data in business application systems such as R/3. BAPI is used to upload data into SAP system. It has a role as communication plattform for developing applications, e.g. booking material documents from flat files, see more in trx BAPI. For specific business tasks such as uploading transactional data, BAPIs are implemented and stored in the R/3 system as remote function call (RFC) modules. One of the big plusses for BAPIs is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot packs because the transaction can change (format, required inputs etc) which means you then need to update the call transaction. Some of the BAPIs are better documented and easier to use than others. You usually need to perform the BAPI that actually does the COMMIT after you call your BAPI. The Program coding for calling a BAPI is usually cleaner than setting up the screen flow etc for the Call Transaction. You don't need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that BAPIs probably have better performance since they don't do the screen flow processing. In general if the BAPI exists for the transaction you want to perform and you can figure out how to use it the BAPI is probably the best way to go. This is just from my experience working with both BAPI and Call Transaction. I have had some very good successes with BAPIs, but very occasionally found that I could not get the BAPI to perform the update I needed. The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.

----------------------------------------------------------------------------------------------10) What the difference between BDC and BAPI? What the exact situation where we can use BDC and BAPI? A) BDC is the good old method of moving legacy data to SAP. BAPI is the new enhanced Application Interface through which data can be uploaded into SAP System. BDC is transaction oriented. Meaning, the data is uploaded into SAP through standard transactions. All checks, validations,exits that are applicable to the transaction are active while loading data into SAP. Simply saying, BDC is continuous running of transaction repeatedly without human intervention, data being picked from text file for each run. It is just a bundling of multiple executions of the same transaction and execute at once like a macro. Whereas BAPI is an interfacing method, through which SAP data can be processed from within SAP or from other non-SAP applications. BAPI can be termed as SAP transaction without dialog. All the screens of particular transaction is converted in the form of a Code Module. We can establish on-line interface with SAP data from non-SAP applications through BAPI's if they are enabled for Remote Access. Generally BDC is preferred if the data from the legacy system is moved to SAP single time. For example, at the time of Go-Live the data required for SAP is either downloaded from other software or manually prepared in excel sheets and uploaded into SAP at once. After that data or SAP has nothing to do with other software. BAPI's are preferred, if data exchange is online or continuous between SAP transactions or SAP and non-SAP applications. BAPI's are preferred in view of performance also. Data loading through BAPI's are more robust and faster comparatively, if they are called correctly. ----------------------------------------------------------------------------------------------11) What is meant by EDI(Electronic Data Interchange)? A) EDI, stands for Electronic Data Interchange, is the electronic exchange of structured business data between different applications. They support the automatic processing of business transactions. Advantages of EDI process:* * * * * * * * * Reduced data Entry Errors Reduced Processing cycle time Availability of data electronic form Reduced Paper Work Reduced Cost Reduced Inventories and Better Planning Standard Means of Communicating Better Business Processes Competitive Advantage

----------------------------------------------------------------------------------------------12) What is LSMW? A) LSMW(Legacy System Migration Workbench) is a tool that supports the transfer of data from non-SAP systems (Legacy Systems) to SAP R/3 systems. This can be a one-time transfer as well as a periodic one. LSMW also supports conversion of data of the legacy system in numerous way. The data can then be imported into the SAP R/3 system via batch input, direct input, BAPIs or IDocs. Furthermore, the LSM Workbench provides a recording function that allows generating a data migration object to enable migration from any required transaction.Total of 26 processing steps are available in LSMW ,In case of data transfer using Batch Input only 14 steps are required. Steps to transfer data from LSMW system to SAP System: Enter Transaction LSMW in SAP ,to start the workbench. LSMW workbench shows the following information* Project : An ID with a maximum of 10 characters to name your data transfer project. If you want to transfer data from several legacy systems, you may create a project e.g. for every legacy system. * Subproject: An ID with a maximum of 10 characters that is used as a further structuring attribute. * Object : An ID with a maximum of 10 characters to name the business object. Enter Project ID , Subproject ID , Object ID. Click Execute. The next screen gives the STEPS in your LSMW data Migration. Enter the required data and import the data. ----------------------------------------------------------------------------------------------13) What is Smartforms? A) SMARTFORMS provide number of benefits over SAP-Script. It is a step by step guide which teaches various concepts about Smartforms like how to call them through ABAP, how to pass internal table, how to display data in tabular way in Smartforms. More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program. The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database. The SAP transaction code is 'LSMW' for SAP version 4.6x. For those with the older SAP version (4.7 and below), the data migration programs might not have been pre-loaded. You can download the LSMW at no cost from SAPNet under Services, SAP Methodology and Tools, category Tools.

14) What is SAP Adobe forms? A) This is another SAP tool designed to create your own forms. The transaction for this is SFP. How to use them: You can create a sales order form in adobe form and send to the sales reps. Sales reps can fill this form when they are not connected to internet / SAP system. Once they connect to SAP just send an e-mail to a specific user id in outlook. You got to customize and code how do you want to process once you receive this form. This enables you to create orders even when you are not connected to the system. Hence no data loss. This is not how i used though :-). ----------------------------------------------------------------------------------------------15) What is the difference between Adobe forms and Smart Forms / Smart Scripts? A) Smart forms / scripts are used to show the data in SAP. Most likely you will use these to print / display some kind of reciepts / forms. Many companies must be using this for hard copies / ALE / EDI or to transfer data from SAP to others. Adobe forms are used to post data into SAP from SAP too. So this has an additional feature compared to smartforms. Where do we use this: You can use for offline forms usage, and as like smartforms to print. What do i need to know to work on these? You just need to know ABAP. It is beneficiary if you know java script. But it hardly matters. If i can do without knowing Java script, you can do the same. Same with XML. Transaction for doing this is SFP and this runs on netweaver. Have fun with forms. It is very easy to design the forms in Adobe forms. It is as good as dragging and dropping. You can add list boxes, check boxes, radio-buttons. ----------------------------------------------------------------------------------------------16. What is AS-IS document? A) Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP. Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes. ----------------------------------------------------------------------------------------------17. What is To-Be document??

A) Parallely you map these processes to SAP. Processes that you are not sure of
as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you will also be made aware of the gaps between ASIS and TO-BE. Here decisons have to be made as to wether a ABAP

development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it. ----------------------------------------------------------------------------------------------18. What is Baseline Configuration in SAP? A) Base line and Final config is the third phase in ASAP methadology. The purpose of this phase is to implement all the business & process requirements based on business blue print. Base Line Configuration: This phase comprises the priority requirements of the enterprise, ensuring that they can be implemented quickly. This phase can be completed without programming or enhancements to SAP systems. In this phase you confirm that all your requirements are met in the R/3 system. Final configuration is a transportation process that expands that base line solution. ----------------------------------------------------------------------------------------------19) What is SDLC Life Cycle? What are the different phases of SDLC? A) Software Development Life Cycle or SDLC is a model of a detailed plan on how to create, develop, implement and eventually fold the software. Its a complete plan outlining how the software will be born, raised and eventually be retired from its function. Although some of the models dont explicitly say how the program will be folded, its already common knowledge that software will eventually have its ending in a never ending world of change web, software and programming technology. 1.REQUIREMENT: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs. 2.ANALYST: Analyze end-user information needs. 3.DESIGN: Software development team describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudo-code and other documentation. 4.CODING (or) Implementation: The real code is written here. 5.TESTING: Our team brings all the pieces together into a special testing and maintenance environment, then checks for errors, bugs and interoperability. 6.MAINTANENCE: changes, correction, additions, move to a different computing platform or say migration and porting and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.

20) What are the different models of SDLC? A) The different models of SDLC are *Waterfall or Linear-Sequential Model *Modified Waterfall Model *V-model *Incremental Model *Spiral Model *Prototype Model(Application developed without functionality) *Iterative model