SAP ABAP Data Element MOPUPZ_KK (Maximum Subitem Number for Creation of Table Lines)
Hierarchy
☛
FI-CA (Software Component) FI-CA
⤷
FI-CA (Application Component) Contract Accounts Receivable and Payable
⤷
FKKB (Package) Contract A/R & A/P: Central Objects
FI-CA (Software Component) FI-CA⤷
FI-CA (Application Component) Contract Accounts Receivable and Payable⤷
FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
| Data Element | MOPUPZ_KK |
| Short Description | Maximum Subitem Number for Creation of Table Lines |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR3 | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | 0 | |
| Long | 30 | Maximum Subitem Number |
| Heading | 3 | Max |
Documentation
Definition
If an item is recorded in the dunning history or in another history, the information about which subitems there are for this item at this event should be saved. Based on this information, you can later reconstruct - if new subitems result from the item split - whether these new subitems resulted from the items contained in the history.
Use
The field is required internally for technical purposes.
Dependencies
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 472 |
