 |
|
|
|
|
|
|
|
|
|
|
 |
|
|||||||||
 |
 |
 |
 |
 |
|
|||||
 |
|
|||||||||
 |
 |
 |
 |
|
||||||
|
||||||||||
 |
 |
Guideline to integrate Remedy ARS and SAPARSXLink provides an intelligent and smooth way to integrate Remedy ARS and SAP. For this guideline the focus lays on a BAPI/RFC integration.
This guideline is addressed to System Architects and Remedy ARS skilled persons. 
Precondition:
The integration points must be clearly known and defined. In case of a typical standard ARS/SAP integration System Architects or SAP/Remedy skilled persons have to investigate the business processes and find out where are the integration points and what kind of data has to be exchanged. As result a number of transactions can be documented, each transaction describes an integration task (business case) and the conditions like when should be this integration executed, what is the trigger, what kind of data needs to be exchanged and what are the dependencies between other transactions/integrations (sequential processing, data plausibility check, etc).
Standard BAPI
The SAP system contains thousands of BAPI/RFC’s but not every function module is a remote function call (RFC) to access from outside. Especially in customized SAP systems there a numbers of new fields which there are untouched by standard BAPI’s. The challenge is to find the right BAPI which provides the functionality to implement this integration task. Best practice is to consult a person who is specialized on the SAP module which is involved in that integration. By using the BAPI explorer (SAP transaction BAPI, se37) the function module documentation will give good information for what this BAPI can be used and describes which data is required and will be exchanged. The BAPI should be tested on SAP side to demonstrate that it fulfill the requirements. The BAPI explorer has a built-in functionality to test BAPI/RFC’s. By using a BAPI in different scenarios for each scenario an own test-case should be executed. In a test-case the input parameter can be checked and transfered to the BAPI; after processing the BAPI the export parameter can be reviewed. Export parameter can be simple data or system messages like error messages, numbers or warnings. Does the BAPI provides tables these tables can be used as import and export parameter (e.g. to create a selection criteria or to retrieve a key-list of material numbers as output).
Customized BAPI?
Is there no BAPI available ARSXLink supports also to combine several BAPI’s in one adapter to split the task on different BAPI’s. In 99% of all cases standard out-of-the-box BAPI’s is all what we need. At times there is no chance to avoid using a customized BAPI. Under some circumstances, especially in very customized SAP systems it can be necessary to develop own written (customized, Z-Bapi’s) BAPI’s. This can take place by copying a standard BAPI or write a new one from scratch. This work will be normally done by the SAP interface skilled persons.
Data mapping
Each transaction has an own data mapping. This mapping document describes in detail each field that should be exchanged, the domain of that field in both System and eventually the re-mapping of the values between systems.
Test case
A numerous test case for each kind of this integration should be provided from the responsible person of each system. E.g. to create an Asset in SAP the SAP responsible person should provide information (test data) how to create Asset Type A, Asset Type B1 and Asset Type B). |
 |
|
||||||
 |
|
|||||||||
 |
 |
|
||||||||
 |
|
|||||||||