Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
FI-LA (Application Component) Lease Accounting⤷
FI_LA_GF (Package) Lease Accounting General Functions
IMG Activity
| ID | 0FILA009S_1 | Specify Dates for Postings |
| Transaction Code | S_XB7_96000171 | (empty) |
| Created on | 20011004 | |
| Customizing Attributes | ||
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | VVTFILA_GF_009SA |
Use
The lease provides various dates for accounting (installation date, contract start date, contract end date, and so on). These dates are also used for other accounting processes.
In this Customizing activity, you specify how dates that are relevant for accounting (such as the posting date, asset value date, value date) are copied from the lease.
Standard settings
The system uses entries without a process as the default:
Process Company Code Group Target Field Source Field
G1 BLDAT LEASTARTDT
G1 BUDAT LEASTARTDT
G1 BZDAT LEASTARTDT
G1 DATE_FROM LEASTARTDT
G1 EFFDATE LEASTARTDT
G1 UBZDT LEASTARTDT
G1 VALITY_FROM CONTSTARTDT
G1 VALITY_TO CONTENDDT
If you want to use other settings than the standard settings, you have to configure the required dates for your process.
Activities
When you create a process, you must enter all the required dates. All the dates you require from the default (where no process is assigned) must be entered for each specific process.
Example:
Process Company Code Group Target Field Source Field
G1 BLDAT LEASTARTDT
G1 BUDAT LEASTARTDT
G1 BZDAT LEASTARTDT
G1 DATE_FROM LEASTARTDT
G1 EFFDATE LEASTARTDT
G1 UBZDT LEASTARTDT
G1 VALITY_FROM CONTSTARTDT
G1 VALITY_TO CONTENDDT
FLOR G1 BLDAT CONTSTARTDT
FLOR G1 BUDAT LEASTARTDT
FLOR G1 BZDAT LEASTARTDT
FLOR G1 DATE_FROM CONTSTARTDT
FLOR G1 EFFDATE LEASTARTDT
FLOR G1 UBZDT CONTSTARTDT
FLOR G1 VALITY_FROM CONTSTARTDT
FLOR G1 VALITY_TO CONTENDDT
Further notes
The assignment of a date from the lease to an accounting date can be the same for the company code groups, accounting principles, and classifications. In this case, you do not need to make any entries in these fields. If the assignment is different, then enter the corresponding company code group, accounting principle, and classification.
The date is transferred in the function module FILA_IDAT_FROM_ITEMS_FILL from the contract item to processing.
You can assign a date for the following fields:
- DATE_FROM (from-date for an entry)
- Activation of relevant payment schedule items
Function module used: FILA_PARM_ACTIVATE_REL_ENTRIES
The function module is used in the subprocess INCEPTION_SPLIT and activates all the relevant payment schedule items that lie before the DATE_FROM date.
If payment schedule items are marked as inactive, these are ignored in calculations unless explicitly requested. This behavior is implemented in the subprocess INCEPTION_SPLIT because this process generates a copy of the payments before the DATE_FROM date. For more information, see the documentation for the Customizing activity Define Payment Schedules. - Filling of accruals
Function module used: LAGF_ACE_CALL_PREPARE
The date is used to determine the start date for accruals and the posting date for the initial posting.
The date is saved in the tables ACEDSOH and ACEDSOI in the DATE_FROM field. This determines the time dependency of this entry. When you make an adjustment, such as FLOR (floating rate adjustment), the system generates a new entry.
- VALITY_FROM (start of term for an accrual subobject)
Function module used: LAGF_ACE_CALL_PREPARE
Selects the validity start date of accruals.
The date is saved in the tables ACEDSOH and ACEDSOI in the VALIDITY_FROM field. The VALIDITY_FROM date is the start date for calculating accruals. - VALITY_TO (end of term for an accrual subobject)
Function module used: LAGF_ACE_CALL_PREPARE
Selects the validity end date of accruals.
The date is saved in the tables ACEDSOH and ACEDSOI in the VALIDITY_TO field. The VALIDITY_TO date is the end date for calculating accruals. - EFFDATE (effective date of event)
Function modules used: LAAE_SCHEDULES_DEACTIVATE, LAAE_SCHEDULES_COPY, and LAAE_SCHEDULES_REACTIVATE.
Controls the posting date for changes made to the accruals. When you copy, deactivate, or reactivate accruals, the system generates a posting on this date. - BDOTP (posting date for one-time postings LAE)
Determines the postings date and document date for the one-time postings.
Function module used: LAGF_ONETIME_POSTINGS_PREPARE fills the effective date, which is copied in the function module CREATE_ONE_TIME_POSTING in the subprogram CREATE_BAPI_DOC and from there in the subprogram BUILD_FI_DOC_HEADER to the posting and document date.
If the BDOTP field is not filled, the system copies the value from the BUDAT field. - BUDAT (posting date in the document)
Determines the posting date for the asset in Asset Accounting.
The posting date is copied in the function module LAFA_POSTING_ON_ASSETS_PREPARE to Asset Accounting. - BLDAT (document date in the document)
Determines the document date in Asset Accounting.
The document date is copied in the function module LAFA_POSTING_ON_ASSETS_PREPARE to Asset Accounting. - WWERT (translation date)
Determines the translation date of the capitalization posting in Asset Accounting.
The translation date is copied in the function module LAFA_POSTING_ON_ASSETS_PREPARE to Asset Accounting.
If you need a different translation date for the scrap value, for example the original exchange rate is used in a change process, you must make this setting in the following Customizing activities. For more information, see the documentation for the following Customizing activities:
- Specify Depreciation Terms/Scrap Value
- Specify Depreciation Terms/Scrap Value for Process with Value Transfer
If the WWERT field is not filled, the system copies the value from the BUDAT field. - BZDAT (reference date)
Determines the reference date for the asset in Asset Accounting.
The reference date is copied in the function module LAFA_POSTING_ON_ASSETS_PREPARE to Asset Accounting. - UBZDT (original value date of transaction)
Determines the original value date of the asset in Asset Accounting. The original value date is copied in the function module LAFA_POSTING_ON_ASSETS_PREPARE to Asset Accounting.
If the original value date is entered, the system generates a post-capitalization in Asset Accounting. The function module LAFA_ASSET_CREATE is responsible for this and enters the UBZDT date in the capitalization date for the asset.
When the system checks the open posting periods (in the function module FILA_IDAT_DATES_ON_DELAY_GET) it deletes the UBZDT if the asset is to be created in the current fiscal year. - ADATU (valid-from date)
In Asset Accounting, controls the assignment to controlling objects according to time periods. There is not process in the Lease Accounting Engine that triggers this change in Asset Accounting.
You must define the following fields in the Customizing activity: Fill Structure for Processing Control from Value IDs - ZUONR (Assignment Number)
- XSTOP_FIAA (Indicator: Stop Periodic Postings to Asset Accounting)
- XSTOP_ACE (Indicator: Stop Periodic Accrual Postings (ACE))
- XANEU (Indicator: Transaction Based on New Acquisition)
Business Attributes
| ASAP Roadmap ID | ||
| Mandatory / Optional | ||
| Critical / Non-Critical | ||
| Country-Dependency |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20011019 |
| SAP Release Created in | 461 |
