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
Basic Data
| Data Element | DATASET_KK |
| Short Description | Additional Output to Dataset |
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 | 7 | Dataset |
| Medium | 13 | Outp. Dataset |
| Long | 28 | Additional Output to Dataset |
| Heading | 0 |
Documentation
Definition
Controls whether additional key date-related open items are to be output in a dataset. This enables you to subject the dataset to additional evaluations.
The line items are output in accordance with the structure FKKOP_COPY. Only those fields that the report needs to prepare the list are filled:
- Report RFKKOP03 (FPO1 and FPO1P) exports:
- All fields that appear in the list
- Selected fields required to evaluate the items
- COPY field, that is always set if the item of a simulated business partner item corresponds to a clearing document
- Report RFKKOP04 (FPO4) exports all fields of the layout used as well as some fields required to evaluate the items.
The layout fields where the origin structure is not FKKOP (for example, local currency) are not exported.
File name
In reports RFKKOP03 (FPO1) and RFKKOP04 (FPO4), the file name is defined by the logical file name FI-CA-OPEN-ITEMS, whereby <PARAM_1> corresponds to the report name, and <PARAM_2> to the user name.
In the mass activity, the file name is defined by the logical file name FI-CA-OPEN-ITEMS-MASS, whereby <PARAM_1> corresponds to the run date and run ID of the mass activity, and <PARAM_2> to the interval number. A separate file is created for each interval - always on the application server where the interval was processed.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
