Hierarchy
EA-FIN (Software Component) EA-FIN⤷
FI-GL-GL-AAC (Application Component) Manual Accruals⤷
FI_GL_ACAC (Package) Manual Accruals
Basic Data
| Data Element | ACAC_FIDOC_GJAHR |
| Short Description | Fiscal Year (of FI Document Selected) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | GJAHR | |
| Data Type | NUMC | Character string with only digits |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | GJR | |
| Default Component name | FISC_YEAR | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Fisc. Year |
| Medium | 15 | Fiscal Year |
| Long | 20 | Fiscal Year |
| Heading | 4 | Year |
Documentation
Definition
Supplementary Documentation - ACAC_FIDOC_GJAHR0001
Use
On the basis of the fiscal year and the periods defined in the planning parameters, the system determines the planning period. The system checks whether valid master data exists for the planning period.
Dependencies
Depending on the planning area, the fiscal year is dependent on other input fields.
Within primary cost planning, there are direct dependencies to the fields:
- Controlling area
- Version
- Plan parameter
Since, among other things, the fiscal year determines the planning period, there are also dependencies to the fields:
- Cost center and group
- Cost element and group
The SAP system checks whether the master data is valid in the whole planning period. With regard to orders, there are no dependencies since this master data is not time-dependent.
For the first fields mentioned above, the following are validated:
- Fiscal year-specific area data
- Fiscal year-specific version data
- Currency-specific fields of the plan parameters
against the indicator : Update All Currencies? (Fiscal year-specific area data).
Supplementary Documentation - ACAC_FIDOC_GJAHR0003
Use
Fiscal year in which the accounting document is posted.
Dependencies
The fiscal year is determined from the posting date you entered and the posting period defined for the company code.
Supplementary Documentation - ACAC_FIDOC_GJAHR0005
Use
This is the fiscal year in which the physical inventory document was posted.
Dependencies
The fiscal year of the inventory document is determined from the planned payment date and together with the document number, forms the key that is used to access an inventory document.
Supplementary Documentation - ACAC_FIDOC_GJAHR0006
Use
Fiscal year for the accounting document
Procedure
Examples
Dependencies
Supplementary Documentation - ACAC_FIDOC_GJAHR0007
Use
Here the fiscal year defines the start of the validity period of the tax code. The setting that you have selected is valid until you enter a new year.
Examples
You have maintained tax codes for 1994, 1997, and 2003. This results in the following validity periods:
Tax code for year Validity period
- 1994 1994 - 1996
- 1997 1997 - 2002
- 2003 2003 - ...
Dependencies
Supplementary Documentation - ACAC_FIDOC_GJAHR0010
Use
Used to select customer accounts with open items in which no transactions have been posted since the fiscal year that you entered (old receivables).
Supplementary Documentation - ACAC_FIDOC_GJAHR0011
Use
Used to restrict the fiscal year of sales/purchases
Supplementary Documentation - ACAC_FIDOC_GJAHR0012
Use
Used to select vendor accounts with open items in which no transactions have been posted since the fiscal year that you entered (old payables).
Supplementary Documentation - ACAC_FIDOC_GJAHR0013
Use
Enables you to restrict the fiscal years
Supplementary Documentation - ACAC_FIDOC_GJAHR0016
Use
As the same goods receipt document can occur in more than one year, the goods receipt document cannot be identified uniquely without specification of the year.
Procedure
Enter the calendar year in which the goods receipt document was posted.
Examples
Dependencies
History
| Last changed by/on | SAP | 20030326 |
| SAP Release Created in | 200 |
