Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
AP-MD-PRO (Application Component) Central Part of Product Master⤷
COM_PRODUCT_API (Package) Product: APIs for Processing General Products
Basic Data
| Data Element | COMT_OLTP_RFCDEST |
| Short Description | RFC Destination for OLTP System |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RFCDEST | |
| Data Type | CHAR | Character String |
| Length | 32 | |
| Decimal Places | 0 | |
| Output Length | 32 | |
| Value Table | RFCDES |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | CRM_DESTINATION | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 5 | Dest. |
| Medium | 11 | Destination |
| Long | 15 | RFC Destination |
| Heading | 15 | RFC Destination |
Documentation
Definition
The RFC destination is used for data exchange with the OLTP System. Each OLTP System has its own RFC destination. Once an RFC destination has been selected, the system knows to which OLTP System the product data should be transferred as material data.
Any functions called subsequently with RFC in the relevant OLTP System use this selected RFC destination. The RFC is used, for example, to check whether a material already exists in the OLTP System for a material number derived from a particular product ID. Or RFC may be used to read the valid possible entries for the input fields relevant to the upload (material type, material group, industry sector).
To avoid superfluous RFC calls in different OLTP Systems, the RFC destination should only be changed if data is to be transferred to an OLTP System other than the system normally used.
History
| Last changed by/on | SAP | 20100420 |
| SAP Release Created in | 20C |
