SAP ABAP Data Element PXNINTFPATT (Interface Pattern)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DWB-PRX (Application Component) Proxy Generation
⤷ SAI_PROXY_GENTIME_MDR (Package) Proxy Generation Meta Data Repository
⤷ BC-DWB-PRX (Application Component) Proxy Generation
⤷ SAI_PROXY_GENTIME_MDR (Package) Proxy Generation Meta Data Repository
Basic Data
Data Element | PXNINTFPATT |
Short Description | Interface Pattern |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PXNINTFPATT | |
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 | 7 | IntfPat |
Medium | 17 | Interface Pattern |
Long | 17 | Interface Pattern |
Heading | 17 | Interface Pattern |
Documentation
Interfaces and their operations have communication patterns and security levels which are relevant for configuration (transaction Soamanager).
There are several interdependencies:
-The possible security levels depend on the chosen interface communication patterns.
-The operation patterns depend on the chosen interface communication patterns (eg for a TUCC pattern all necessary operation patterns must exist)
Further details about the implications and details of communication patterns and security levels see also Tab 'Configuration' and application help in transaction Soamanager.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 72L |