The SAP transactions are configured in a separate XML file that can be imported or exported using the runppmconfig command line program (see PPM Operation Guide). The language-specific descriptions (description XML elements) must be specified at least in the default language.
The XML configuration contains information on the pop-up menu, connection data for the available SAP systems and the transaction configurations (optional entries in italics):
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE r3transactionconf SYSTEM
"mysaptransaction.dtd">
<r3transactionconf>
<submenu>
<description language="..." name="..."/>
</submenu>
<logoutMenuEntry>
<description language="..." name="..."/>
</logoutMenuEntry>
<r3system systemid="..." client="...">
<description language="..." name="...">
Description of the SAP system
</description>
<locales>
<defaultlocale value="..."/>
<locale value="..."/>
</locales>
<applicationserver appserver="..."
systemnumber="..."/>
</r3system>
<transaction systemid="..." transactionid="..."
transactioncode="..." skipfirstscreen="..."
proctypegroup="..." mode="..." update="...">
<description language="..." name="..."/>
<batchinputline ... />
...
<batchinputlist ... />
...
</transaction>
<transaction ...>
...
</transaction>
...
</r3transactionconf>
For more detailed information on configuring system access, refer to the PPM Process Extractors Technical Reference.
For a transaction call to work, you need to configure not only connection data, but also at least one transaction (transaction XML element).
Use the SAP transaction recorder to create transaction configurations and record a corresponding transaction in the ABAP batch input. Please refer to the SAP documentation for more information on how the recorder works and on the ABAP batch input script syntax.
Warning
The following instructions on how to create configurations do not replace the SAP documentation, especially not in terms of resolving script errors. Basic knowledge about batch input scripts is a necessary requirement for creating transaction configurations.
In principle, two types of transaction calls can be configured: