BDC: Batch Data communications. What is the difference between batch input and call transaction in BDC?

Session method. 1) 2) 3) 4) 5) Synchronous processing. Can transfer large amount of data. Processing is slower. Error log is created data is not updated until session is processed.

Call transaction. 1) Asynchronous processing 2) can transfer small amount of data 3) processing is faster. 4) Errors need to be handled explicitly 5) data is updated automatically Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3. BDC is not a typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is not bi-directional. In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling. It can also be used for real-time interfaces and custom error handling & logging features. Whereas in Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too. Batch Input (BI) a program still use the classical BDC approach but doesnt require an ABAP program to be written to format the BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and invokes the transaction mentioned in the header record of the file. BAPI: - Business Application Programming interface. A BAPI is a point of entry to the R/3 System- that is, a point at which the R/3 System provides access to business data and processes. Each object in a BOR can have many methods, one or more of which can be implemented as BAPIs. BAPIs can have various functions: Create an object Retrieving the attributes of an object Changing the attributes of an object

BAPIs usually have an export parameter called RETURN. This can be structure or an internal table. The return parameter contains information on errors that occurred while the BAPI was being processed. There are no exceptions for BAPIs.

BAPI with standardized names contains standard methods. Three of the most important are listed: Get List: Returns the contents of the key fields for the object we have chosen. Get Detail: Returns detailed in formations for the required object. CreateFromData: Create a new object in the R/3 and returns information about it. BAPI: Exception Handling Every BAPI contains an interface parameter; RETURN which contains information about errors that occurs. This parameter is always of an ABAP Dictionary type. This means that we must SAP Internet Pricing and Configurator (SAP IPC) is used in numerous SAP applications to configure products through the Internet. SAP IPC belongs, technically speaking, to SAP Customer Relationship Management (SAP CRM), but it can also be installed separately on its own database ("standalone"). As of SAP CRM 5.0 the SAP IPC 7.0 is a component of the Application Platform (AP). Compared to the previous release that is SAP IPC 4.0, the technology has been switched to SAP Virtual Machine Container (VMC), which is part of the SAP Web Application Server (SAPWeb AS) and SAP NetWeaver 2004s. Installation of a separate database is not required as SAP IPC 7.0 is moved to the SAP Web AS. This was done in order to use VMC.

BAPI stands for Business Application Programming Interface. It is a library of functions that are released to the public as an interface into an existing SAP system from an external system. RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system. Functions can only be called via RFC, if they are tagged as RFC functions in the SAP development workbench. They are then called RFC function modules. BAPIs are complete sets of (BAPI) function modules that model a business application. When you are familiar with web developments: RFC can be compared to HTTP and BAPIs are CGI applications. In other words: A BAPI function is a function module that can be called remotely using the RFC technology.

List of BAPIS 4000 BAPIs using in Car

1. 2. 3. 4. 5. 6. 7. 8. 9.

For Adding roles to a business Partner Compliance check To create a standing order To change a standing order To get the dangerous goods list Create a shipping doc Change a shipping doc Release of Parked shipping documents. Converts IPC configuration table to BAPI configuration table.

10. List of Companies 11. List of business areas 12. Creating ZPOR orders.

BASE LINE and Final Configurations: Some months ago I discussed, the importance of business blueprintand correct configuration of SAP for a successful implementation. Today, lets take a look at the configuration of the SAP solution during the implementation phase. In any SAP implementation programme, the configuration consists of two sets of deliverables:

1. Baseline Configuration - Design and configure daily business transactions, master data, and organizational structure Establish Authorization Profiles - Complete remaining configuration to meet all any additional business scenarios that must be supported outside the normal daily transactions, Build upon the Baseline configuration FRICE - Develop FRICE (Reports, Interfaces, Conversions, Extensions, Forms) requirements and integrate into the business process configuration

2. Final Configuration Each of the above set of configuration deliverables need to be planned, implemented in SAP, tested and signed-off as a release. The baseline configuration ensures that the implementation team will configure and confirm settings from the baseline scope. Baseline scope normally includes pre-configured business processes. Best practices forming part of the solution configuration will need to be configured. This happens during the final configuration stage. The final configuration is even more refined with specifics on customizations and how business processes and procedures will be handled in the live production environment. It would be correct to say that the final configuration cycle tests the entire end to end business scenarios, to gain confidence that the developments and system configuration are correct and reflect the original plan layed out in the business blueprint Very SAP implementation project goes through pre-defined stages. Some of you might remember my post on the milestones in an ERP implementation project. Normally, the first stage in a SAP R/3 project is the Business Blueprint stage. Business blueprints help in guiding people through complex business processes. SAP R/3 business blueprint uses computer based graphic modeling methods in integrating technology and business processes. In a nutshell, Business Blueprints in SAP are a definitive description of R/3, providing a comprehensive view of the main business processes and business solutions available in the R/3 system. Some important points worth mentioning here are: 1. Business blueprints in SAP R/3 help business users understand complex business processes. In fact, the goal of the business blueprint is to streamline business processes. 2. Business blueprints are often the first step in business engineering. Blueprints help in speeding up SAP R/3 implementations facilitating communication among SAP customers and SAP R/3 consultants. 3. SAP R/3 business blueprint stresses on four key areas: - Events i.e. when should something be done - Tasks or Functions i.e. what should be done - Organization i.e. who should do what Communication i.e. what information is required to do the right task 4. To summarize what I just said above, SAP R3 business blueprint tells business process owners who must do what, when and how.

The result is the Business Blueprint, a detailed set of documents that list the results gathered during requirement workshops including process flows, list of business

processes, requirements, technical approach, and master list of custom FRICE (Forms, Reports, Interfaces, Conversions, and Enhancements) objects
WHAT is BADI: