SAP ABAP Data Element AEXTS (Transaction Call in an External System)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ PP-MRP-BD (Application Component) Master Data
⤷ MD0C (Package) Customizing R/3 Material Requirements Planning
⤷ PP-MRP-BD (Application Component) Master Data
⤷ MD0C (Package) Customizing R/3 Material Requirements Planning
Basic Data
Data Element | AEXTS |
Short Description | Transaction Call in an External System |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
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 | ExtSys |
Medium | 15 | In Ext. System |
Long | 30 | Carry Out in External System |
Heading | 1 | E |
Documentation
Definition
Determines whether the transaction is to be invoked in SAP Advanced Planning and Optimization (SAP APO).
Use
If this indicator is set, the transaction is executed in one of the connected SAP APO systems in which the material for which the stock/requirements list was invoked is integrated.
If this indicator is not set, the transaction is executed in the local system.
Dependencies
If the transaction is to be executed in the local system, the system checks whether the specified transaction code is available.
To be able to invoke the transaction in external systems, it is necessary to assign the RFC destinations to the different application cases for all logical systems in which materials are integrated.
Assign RFC Destinations to Different Application Cases
Example
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in | 700 |