a

The SAP alias.

b

RFC name.

c

(optional) Name of the map containing the input parameters. Default: default. See subsection Filling of Parameter Map c Before Call.

d

(optional) Time in seconds the function waits for a response for the request. A time lower than three seconds will be ignored. Default: 60

e

(optional) Comma-separated list of field and table names and optional indexes the result should be restricted to. Default: No output filtering. See subsections Output Value Restriction with Parameter e (you can also output ABAP exceptions and the entire response in the SAPXML format).

f

(optional) This parameter allows you to additionally write the response values into a Named List or an XML object. If the parameter remains empty, neither is done.

To additionally write into a list, simply enter its name here. The list is automatically created (or emptied, if it already exists). The response values are then inserted into the list. Filter e is also applied. The return values of the function and the contents of the list are therefore the same.

To additionally write into an XML object, please use the prefix :xml: (written exactly like this and without spaces between prefix and name). The XML object is created automatically and will contain the entire response of the RFC. Filter e is not applied! You can evaluate the RFC response in the XML object using the functions select nodes from XML/DOM to List( a, b, c, d, e ) and get value from XML( a, b, c, d ). Note: The XML structure in the XML object is identical to the XML structure of the debug file *_debug_RfcOut.xml, which can be written as a local debug file using parameter g.

g

(optional) true if a trace files of the request should be generated. Default: false . The names of the created trace files will be logged into Lobster_data's log. File name format: <Job number>_<Timestamp>_debug_<RFC name>_<In|Out>.xml , where for a mapping test the value T is used instead of the job number . The files are written into folder ./debug/sap . Important note: Even if the parameter is set to true, the trace files are only written in a mapping test or if tracing has been activated for phase 3 of the profile (or system-wide). If you always want to write the debug files (e.g. in the test phase as proof for the SAP team), i.e. also in a normal job run and without the tracing in phase 3 activated (with its corresponding overhead), you can also specify the value always . Warning: These files are not automatically deleted, so it is the user's responsibility to monitor this folder and delete files manually to prevent a disk overflow. Please also note that a high number of files in this folder can affect performance.

h

(optional) Semicolon-separated list of ABAP exceptions to be ignored.

i

(optional) Return value if an ignored ABAP exception (see parameter h) occurred.

j

(optional) The RFC queue to be used. If the parameter is left empty, the default queue is used.

Warning: If a JCoContext is used (see parameter k), a defined queue is ignored!

k

(optional) Create JCoContext (true/false). Default: <empty>. Limitation: The JCoContext can only be created for connections with JCo version 3. For aliases with JCo version 2.x, the function terminates with an error occurs if k=true.

If a call is made with k=true, a JCoContext is created for alias a, which exists until the end of phase 3 of this profile job (or until a termination with error). Only with an explicit parameter value k=false, you can remove a subsequent call from an existing JCoContext (an empty parameter k does not close the context!). Such a context is required for (stateful) BAPI calls (Business Objects in SAP). All BAPI calls must take place in the same JCoContext because they are contiguous. All calls together are then committed at the end (BAPI_TRANSACTION_COMMIT). If no commit is executed by the end of the JCoContext, the BAPI data transferred to the SAP system within this JCoContext is discarded.

Normal RFC calls do not have to be committed, so the JCoContext has no meaning there and should only be created for sequential BAPI calls, since it is very resource-intensive. But you can also call normal RFCs in an existing JCoContext. Note, however, that these are not rolled back if a commit is not made, because they will work without it!

Warning: When the JCoContext is created, any queue defined in parameter j is ignored!

Note: In the first function call, the value true can also be written in capital letters (TRUE). In that case, the JCoDestination for this job is cloned and an RFC_PING is executed at the beginning to test the connection.