Hierarchy
⤷
⤷
Basic Data
| Data Element | RSDSWSFUNCNAME |
| Short Description | DataSource Push Function Module |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FUNCNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | TFDIR |
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 | FM |
| Medium | 15 | Function Module |
| Long | 30 | Function Module |
| Heading | 33 | DataSource Push Function Module |
Documentation
Definition
This RFC-enabled function module and the function group of the same name are generated when you activate a DataSource that is located in a Web service source system.
The function module receives data and writes it to the PSA that belongs to the DataSource. If the data is not written successfully, the exception "INTERNAL_ERROR" is raised.
Since the function module (and the function type) is generated, it has to occupy a valid generation namespace provided by the system.
Use
If a fixed service name has been defined, you can define fixed object names. Fixed object names are retained after the DataSource is transported to the target system.
Dependencies
A prerequisite to updating data to the PSA is that an InfoPackage for real-time acquisition is assigned to the DataSource. The related parameters are maintained in this InfoPackage (package size, and so on).
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 710 |