tfdir-fmode
_____________
R = Remote-Enabled
K = Remote-Enabled JAVA Module
X / @ = Remote-Enabled + BasXML supported
J = JAVA Module Callable from ABAP
tfdir-utask
_____________
Update module: Yes
1 = Start update immediately (start immed)
2 = Start of update delayed (Start Delayed)
3 = Update is started immediately, no restart possible (Immediate start, No restart)
4 = Start update immediately (start immed)
5 = Update triggered by collector (Coll run)
6 = Start update immediately (start immed)
Start update immediately
The function module is processed immediately in the update task.
Update is started immediately, no restart possible
The function module will be edited in the update task. It cannot be updated subsequently.
Start of update delayed
The function module is processed in the update task as a low priority item. You use delayed update primarily for database changes that are not time-critical (e.g. statistical updates).
Update triggered by collector
A number of similar function modules that previously used to run individually in the V2 update process can be grouped together and run collectively.
The reasons for processing them collectively are as follows:
the data of all the calls are read and processed internally
database updates are not made until the internal processing is complete
For further information, refer to the ABAP/4 documentation under IMPORT FROM LOGFILE and UPDATE.
BasXML Log
By setting the indicator “basXML Protocol”, you can switch from the classic RFC protocol to the basXML protocol for RFC-enabled function modules for RFC communication.
When this indicator is set, the developer of the function module shows that the function module for the classic RFC protocol and the basXML protocol behaves in the same way, from a semantic point of view. Semantic differerences result from the conceptional differences between the two protocols. The classic RFC protocol uses a positioning logic, while the basXML protocol uses a name identification.
Example
A field in a structure has exactly the same position and length in the sender system as in the receiver system, but has a different name in the two systems. With the classic RFC protocol, this difference is not recognized and the data is displayed correctly at the receiver end because of the same structure. The data is also available in the application. In the case of the basXML protocol, the name of the field is checked. Due to the different field names, no assignment takes place and therefore the value of the field is missing on the receiver side.
Use
The basXML protocol is used if the following conditions are met:
1. The sender system and the receiver system must be based on SAP NetWeaver 2007 or highter.
2. For the RFC destination, the basXML application is allowed on the map “Special Options”.
3. The function module call takes place synchronously or asynchronously.
Note: The basXML protocol is not used for all RFC call variants that record on the database. These include tRFC, qRFC, and bgRFC.
4. The indicator basXML protocol is set for the function module.
Note: The protocol is chosen within a communication link for each individual function module, based on the previous four conditions. Therefore, the system switches between both protocol variants according to requirements.
