Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-TOO-FUB (Application Component) Function Builder⤷
SFUNC (Package) Function Builder
Basic Data
| Data Element | RS38L_BXML |
| Short Description | BasXML Log |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | BasXML |
| Medium | 15 | BasXML |
| Long | 20 | BasXML Log |
| Heading | 10 | BasXML |
Documentation
Definition
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 position 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.
History
| Last changed by/on | SAP | 20100420 |
| SAP Release Created in | 710 |
