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).

Type of Integrations

RFC architecture of ARSXLink

Which integration type do I need?

As shown in the graphic  ARSXLink provides three different type of integration modules. Depends on your business need you may select the right type.

• Get / scheduled data transfer to replicate data from SAP to Remedy ARS / time scheduled
• Online Query / Queries data life from the SAP system, transparency for the user / event driven
• Put / Creates end to end processes in SAP, interactive / event driven

Online Query or Get replication?

Some factors have to be considered before you can choose the best integration method.

If the data changes very often in the SAP system a direct access to the SAP system is the best way. The users can query exactly the data they need on time, the data will pulled directly from SAP and this integration is absolutely transparent for the User. They don’t know that they have queried SAP.

For static data the most common way is to replicate the data with the Get method. This can be done in a complete or incremental way, as well as to one or more forms at a time.

At the end it’s your decision what is the best way to fit to your needs.

The Online Query integration method can be fully integrated in your Remedy Workflow with standard workflow methods you already known.

Process outsourcing to SAP?

With the Put integration method ARSXLink provides a great opportunity to call processes outside your Remedy ARS. It doesn’t matter how complex theses transactions are (e.g. to create/update Purchase Order). This integration type is fully transparency for the User and works interactively. By executing the integration the user will promptly informed what was the result of the SAP transaction and all BAPI dependent return information can be provided.

This integration method can be fully integrated in your Remedy Workflow with standard workflow methods you already known.

How does it work?

This is the first milestone in such a project, all requirements will be met and the integration points are verified.

First time we get in touch with the ARSXLink application on our Remedy AR System. After the basic configuration where we configure our partner system which represents the SAP system and the connections to Remedy ARS and SAP the defined transactions must be defined and configured.

By creating the transaction the integration type must be set and this cannot be changed anymore.

 

ARSXLink Adapter Generator

 

Integration – Step by Step

1. On the properties of the transaction there is a generation tab on display. First step is to create the workspace, this can be a “Makefile” for the Unix Systems or a whole MS Studio Workspace. This will be used to compile and link the adapters.
2. Second step is to generate the Adapter Code. After query and selecting the in this integration used BAPI’s the adapter code will be generated. As result of this generation the Adapter Generator create a full compilable C-program which contains all necessary functions and methods. Individual changes can be made to manipulate fields, analyze and process return messages, etc.
   • Concatenating of SAP Text tables to one text field in Remedy ARS
   • Building User defined keys
   • Formating of Return Messages to user requirements
   • Trailing Zeros
   • etc
3. For Put and Online Query integration we need a vendor form to access it via Remedy workflow. By creating the vendor form the adapter code will be parsed and all touched field in that Adapter will be added in the vendor form. This makes sure that all fields we need in this transaction can easily selected by building the workflow.
4. For Get integration type instead of the vendor form we need to generate a menu to select the SAP field later at the mapping. A generator toll parse the source code of the adapter and create the menu entires.
5. Building your individual workflow to integrate with Put and Online Query methods.
6. For Get integration an individual mapping has to be created. You can define vendor queries to create selection parameters to replicate only the data you want from SAP. Each SAP field can mapped to a Remedy ARS field or default values can be defined. For each record coming from SAP can be configured to create and/or update record in ARS. n-m relationships can be built easily.
7. Test your Integration

Get integration method requires only Step 1,2,4,6 – Put and Online Query integration method requires only Step 1,2,3,5

 

Mapping Get Adapter

Special Cases

Each Remedy ARS / SAP integration is a individual integration because each customer has own defined business processes and requirements.

Sequential BAPI’s/RFC’s calls - With your individual adapter you can call several BAPI’s/RFC’s in one adapter. All combinations are possible.

SAP Updates - Using the Get adapter as easy update solution trigger by SAP. E.g. Service Notification has changed in SAP and the changed data can be passed to Remedy ARS.

Easy Data manipulations - SAP stores large text fields in individual table with restricted length; Remedy stores text fields in one field. The adapter can be changed to change format and map internal values.

More information’s? Please contact us.

[contact-form]