SAP ABAP Data Element EDI_COMCNT (Commit counter for IDoc inbound processing from file)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
⤷ BC-MID-ALE (Application Component) ALE Integration Technology
⤷ SED (Package) IDoc Interface (Processing, Administration, Definition)
Basic Data
Data Element | EDI_COMCNT |
Short Description | Commit counter for IDoc inbound processing from file |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | EDI_NUMC8 | |
Data Type | NUMC | Character string with only digits |
Length | 8 | |
Decimal Places | 0 | |
Output Length | 8 | |
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 | C-counter |
Medium | 15 | Commit Counter |
Long | 40 | CommitCounterForIDocInb.ProcgFromFile |
Heading | 40 | CommitCounterForIDocInb.ProcgFromFile |
Documentation
Use
During inbound processing from a file, many IDocs are normally held in internal tables before they are saved in the database via COMMIT WORK and further inbound processing including transfer to the application is started. In the standard system (that is, if the field is empty) a COMMIT WORK is transmitted, as soon as more than ten thousand data records are imported with the last IDoc.
- Large values
If a lot of free memory is available, you can increase the standard value 10000 and therefore possibly increase performance. 10000 data records require at least 10 MB of memory per internal table!
- Small values
If there is a large memory requirement, a reduction in the value can also improve performance.
History
Last changed by/on | SAP | 20010130 |
SAP Release Created in |