SAP ABAP Data Element LFDN2_KK (Access sequence)
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 (Application Component) Contract Accounts Receivable and Payable
⤷ FKKB (Package) Contract A/R & A/P: Central Objects
Basic Data
Data Element | LFDN2_KK |
Short Description | Access sequence |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | NUMC3 | |
Data Type | NUMC | Character string with only digits |
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 | 0 | |
Heading | 3 | Seq |
Documentation
Use
The system uses Schlüsselfeldwerten to determine G/L accounts in automatic account determination You can, for example, create a tax account in Customizing dependent from posting area, chart of accounts, company code, tax codes and transaction keys. The tax account is imparted automatically when a document is posted.
The system first attempts to impart an entry with recourse to all used key fields. If this does not work, the last key field excluded at the next attempt. At the last attempt, only the first key field value is used.
You can change this standard procedure with user-defined access sequences. To do this, you define:
- which of the possible key fields are relevant for the determination of the G/L account
- in which order the system uses your key field definitions for the determination of the G/L accounts
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |