Hierarchy
⤷
⤷
Basic Data
| Data Element | IDOCLOGIC_KK |
| Short Description | Interface Logic for Creation of G/L Item |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | IDOCLOGIC_KK | |
| Data Type | NUMC | Character string with only digits |
| 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 | 10 | G/L ItmLog |
| Medium | 20 | G/L Item Logic |
| Long | 26 | G/L Item Logic |
| Heading | 8 | G/L Log. |
Documentation
Definition
0 - Logic with CO-PA
1 - Logic without CO-PA
Use
You can use this setting to influence the logic of the interface for creating general ledger items.
Use logic 0 wherever the CO-PA function of the interface is to be used. In this case, you have to create a G/L item for tax and revenues for each E1FKK_EBS_TOI_ITEM segment, since the CO-PA characteristics are saved in the revenue items. Here you have to run the tax determination and creation of revenue items for each segment of type E1FKK_EBS_TOI_ITEM.
If you do not use the CO-PA update, you can use logic 1. The logic of the tax and revenue item creation is run only once for all segments of type E1FKK_EBS_TOI_ITEM. This results in improved performance, in particular if you are using tax jurisdiction codes.
Dependencies
Example
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 471 |