Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-ICF (Application Component) Internet Communication Framework⤷
SHTTP (Package) Development Class for HTTP Communication
Basic Data
| Data Element | ATRA_SINGLEREC |
| Short Description | ICF: Stateful Comm. Single Record Processing for ATRA |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ATRA_SINGLEREC | |
| 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 | 0 | |
| Medium | 15 | Single Display |
| Long | 0 | |
| Heading | 0 |
Documentation
Definition
For stateful communication, this flag controls whether all entries are written to a single file or whether an extra file is created for each entry.
Use
o Selection: Single record
- User-specific settings
For stateful communication, one entry is written for each request for the runtime analysis.
You can find these entries under the appropriate user.
No entries are written for the logon.
- Non-user-specific setting
For stateful communication, one entry is written for each request for the runtime analysis.
Entries are also written for the logon. You can find these entries under the
User: "SAPSYS".
All other entries are made under the user for which the logon was processed.
Comment: If the "GUI Link" option is activated, and the request is processed in the kernel, then this setting is ignored.
o Selection: Composite entries:
- The entries are grouped together in a single file.
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 700 |
