Ansicht
Dokumentation
FINS_SIS_PREP_INFO - Information: Preparatory Phase
ABAP Short Reference CPI1466 during BackupThis documentation is copyright by SAP AG.
The project, Subsequent Implementation of Document Splitting,includes several phases:
- The Blueprint / Concept Phase
- The Configuration Phase
- The Test Phase
- The Go-Live Phase
The Preparatory Phase for the Subsequent Implementation of Document Splitting includes the necessary settings, activities, and tests that you need to carry out before you can enrich posting data in the production system.
You must run the Customizing activities forDocument Splitting before the Customizing activities within the Preparatory Phase for the Subsequent Implementation of Document Splitting can be run. You can make changes to the document splitting Customizing only if document splitting hasn't been activated.
To activate document splitting, you must first Create a Project for the Subsequent Implementation of Document and specify an activation date within the project definition.
In the project cockpit, you set the Activate Document Splitting status to activate data enrichment in the Execution Phase. Journal entries will be split if the posting date of the document is later than the document splitting activation date, and if the Activate Document Splitting status has been set. Afterward, you can no longer make changes to the document splitting Customizing because this will lead to inconsistent posting data.
The Preparatory Phase of the Subsequent Implementation of Document Splitting includes the following activities:
When you create a project, you specify the document splitting activation date. The project is used to gather together all company codes for which document splitting should be activated.
Within the Preparatory Phase, you can run the activities for company codes assigned to this project. When you assign company codes to this project, please be sure that all company codes with cross-company-code postings are assigned to one project.
If you assign several company codes to a project and if some of these company codes have different fiscal years, the document splitting activation for some company codes might occur for periods of less than one year. For these company codes, in this fiscal year, it isn't possible to report on the level of document splitting characteristics.
Therefore, the activation date that you specify, should be the first day of the fiscal year that is used by most of the company codes.
The Preparatory Phase also includes helpful analysis tools. You can use these tools to check the document splitting Customizing in combination with journal entries that have already been posted. To ensure that these checks produce a meaningful result, you should choose a test environment that is based on the most current production system.
The analysis tools include the following Customizing activities:
With help from these tools, you can determine whether the document splitting Customizing is complete and correct. In addition, you can decide whether the posted journal entries already have the necessary data quality and contain all information relevant for document splitting.
During the Preparatory Phase, you need to consider both the enrichment of open items and of the balance carryforward. You need to implement the available BAdIs with the relevant enrichment logic.
In the Execution Phase of the project, the following BAdIs for data enrichment are available:
The first two BAdIs, Generate Document Splitting Information for Open Items and Generate Balance Carryforward Distribution, are implemented during the data conversion of the Execution Phase.
The BAdis Enrich Reversal Posting with Account Assignment and Enrich Period End Postings, enable further modifications to postings, without assigned accounts, during Document Splitting.
The Preparatory Phase is closed with the Customizing activity Complete Preparations. After you have set the project's preparation status to completed, the system performs multiple checks to ensure data consistency. It creates a snapshot (copy) of the current Customizing settings and compares them with the Customizing settings that are active during each future project status change.
In the activities, which follow in the Execution Phase, this copy is used to check whether any Customizing changes were made between the Preparatory Phase and the Execution Phase.
CPI1466 during Backup BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 7535 Date: 20240523 Time: 202854 sap01-206 ( 115 ms )
