the part II of the package). 2.

After you have the two parts downloaded, log into the OS level and uncar the 2 parts in separate directories. Copy the part I in a new folder, and copy the p art II into the same folder (there are cases that files may need to be replaced. replace them, don't worry). 3. If on Windows, disable Windows service SAP_[SID]_##. 4. Stop SAP, the database, SAPOSCOL, sapccm* and saprouter (if they exist)). 5. Backup the old kernel. Usually it is located in: </usr/sap/SID/SYS/exe/<uc or nuc>/<system>. it might also be located in /usr/sap/SID/SYS/exe/run The default kernel location is: /sapmnt/SID/exe . When the SAP instance is start ing up by startsap command, the kernel from /sapmnt/SID/exe is overwriting the k ernel in /usr/sap/SID/SYS/exe/run . So always is better to upgrade kernel in /sa pmnt/SID/exe directory. 6. Delete the old original kernel, and copy the new kernel there. (keep backup ! ) 8. if on Unix as user root : saproot.sh [SID] 9. if on Windows, enable Windows service SAP_[SID]_##. 10. if on Windows Start the services related 11. start SAP. 12.Now just confirm the new kernel version in SAP with this command: disp+work | more SAP-BODS Integration using BAPI By Praveen Addanki, HCL-AXON 1. Introduction: We can call SAP ERP or R/3 Remote Function Call (RFC) enabled functions, includi ng Business Application Programming Interface (BAPI) functions, from queries ins ide data flows. A Remote Function Call is really what the word suggests: You cal l a function but it is remote rather than part of your code. This is the standar d way how 3rd party s tools access SAP, both for read and write. All RFCs meant to be used for business reasons, their function name starts with the text BAPI_XXX X like BAPI_ABSENCE_CREATE or BAPI_ABSENCE_GETDETAIL, both meant to create or di splay employee s absence records in HR. If you design data flows with BAPI calls against one version of SAP ERP or R/3, then change data stores to a later version of SAP ERP or R/3. Data Services allo ws this without the need to re-import the BAPI. Any new parameters added to the function call, including additional columns in table parameters, are added autom atically to the call and filled with NULL values. Thus Data Services allows you to design jobs that are portable between SAP ERP or R/3 systems. After you impor t the metadata for an SAP ERP or R/3 function, the function is listed in the Fun ctions category of the ERP or R/3 data store. You will also see the function in the function wizard, listed under the data store name. Data Services supports tables as input and output parameters for SAP ERP or R/3 RFC and BAPI functions. The function import process automatically includes the m etadata for tables included as function parameters. 2. BAPI Call: After you import the metadata for an SAP ERP or R/3 function, the function is li sted in the Functions category of the ERP or R/3 datastore. You will also see th e function in the function wizard, listed under the datastore name. To call a BA

PI depends on the requirement; here in this document we have considered an examp le of creating a CONTRACT using BAPI_CONTRACT_CREATEFROMDATA . For this BAPI, we ne ed to send mandatory input and Tables parameters to create a CONTRACT. To specify a table as an input parameter to a function, the table must be an inp ut to a query, either as a top-level input or nested under the top-level. The ta ble must also be available in the FROM clause of the context where you call the function. Data Services maps columns in the input schema by name to the columns in the table used as the function input parameter. You need only supply the colu mns that are required by the function. At validation, if Data Services encounter s type mismatches between supplied columns and the function signature, it attemp ts to convert the given type to the expected type. For type mismatches that it c annot resolve, Data Services produces validation errors.