Ansicht
Dokumentation

FINS_MPROJ_COCKPI_06 - Cockpit: Implement Document Splitting

ABAP Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.

The project cockpit handles all mass data activities that are relevant for the Subsequent Implementation of Document Splitting.

In the project cockpit, the following reconciliation and data enrichment activities are carried out:

• Reconcile Journal Entries (SIS_RC_UJE)

• Generate Splitting Information (SIS_SPL)

• Reconcile Splitting Information (SIS_RC_SPL)

• Activate Document Splitting (SIS_MAN_SP)

• Confirm Fiscal Year Closure (SIS_MAN_GJ)

• Enrich Journal Entries (SIS_ENR)

• Reconcile Opening Balances (SIS_RC_BL1)

• Enrich Opening Balances (SIS_BAL)

• Reconcile Enriched Opening Balances (SIS_RC_BL2)

• Confirm Data Enrichment (SIS_MAN_DT)

The following activities must be run to activate document splitting in a production system. You need to run these activities before you can post a document with a posting date that is on or later than the document splitting activation date. Furthermore, these activities need to be run in one step, for all company codes that are assigned to the project.

• Reconcile Journal Entries (SIS_RC_UJE)

• Generate Splitting Information (SIS_SPL)

• Reconcile Splitting Information (SIS_RC_SPL)

• Activate Document Splitting (SIS_MAN_SP)

Important:

The manual activity Activate Document Splitting is a status change and completion of this activity is mandatory to implement document splitting. If you don't set this status, document splitting will not be activated on the activation date you have specified in the project.

If you don’t set this status, you can still post without document splitting logic. Therefore, if you want to stop the implementation of document splitting in your production system, you can still do this only if the Activate Document Splitting status hasn't been set.

The activities that follow Activate Document Splitting, in the project cockpit, are run after the fiscal year is completely closed.

Because the fiscal year close can be completed at different points in time, for the assigned company codes or ledgers, these activities can be started per company code, per ledger, or per fiscal year variant. You need to ensure that the sequence of activities is followed for the company codes and ledgers.

If you posted several documents in the previous fiscal year after the running the balance carryforward, which resulted in several automatic balance carryforward postings, we recommend that you rerun the balance carryforward. To delete the existing entries and to calculate a minimal number of entries, you can run the balance carryforward again with the option Reset Balance Carryforward. This step reduces the number of entries that need to be enriched during in the activity Enrich Opening Balances.

The activity Confirm Data Enrichment completes the mandatory steps for the enrichment of data in the Subsequent Implementation of Document Splitting.

You have confirmed that all preparation activities have been completed before you can perform the activities in the project cockpit.

Running an activity

• To start a specific activity, in the pre-defined sequence, you can click Start Activity on top of the activity overview or you can select Start Activity from the context menu.

• The system creates and starts work packages, for data enrichment or reconciliation activities, and then displays them as sub-items of a Run ID.

• You can view the progress of the activities and any corresponding errors when you click Refresh.

• You can use the context menu for the message column of each individual package to navigate to the log display. The log provides you with detailed information about all messages that appeared while the package was processing.

Resetting an activity

• If there are any data enrichment or reconciliation errors, you might need to reset an activity. You can do this by clicking Reset Activity or by selecting Reset Activity from the context menu.

• RESET of data enrichment, in production systems, is only allowed for the following activities:

• Reconcile Journal Entries (SIS_RC_UJE)

• Generate Splitting Information (SIS_SPL)

• Reconcile Splitting Information (SIS_RC_SPL)

After the status Activate Document Splitting has been set in the production system, you can no longer reset activities in the production system.

In test systems, you can reset all activities. However, please note that this can lead to inconsistent data and you might need to delete test data to see a green status light in the project cockpit for Document Splitting.

You haven't completed the project. If you created any follow-up postings to the balance carryforward (FBCB), you must first reverse these documents. To do this, click Reset Activity for each activity, starting from the last activity in the project cockpit and proceed to the top activity of the project cockpit.

The reset functionality deletes any entries that were created in the tables FAGL_SPLINFO, FAGL_SPLINFO_VAL, and ACDOCA.

The project cockpit lists activities, in the correct sequence, that are relevant data enrichment steps within the project for the Subsequent Implementation of Document Splitting.

After you start an activity, you can see the technical processing of the activity, Run or ResetRun, below the activity. Below Run, you can see the entities (packages), such as company code or ledger, which must be processed.

In the columns of the project cockpit layout, you can view the different activity status types, such as the overall Status, the Processing Status, the Number of Errors/Warnings per run, and the runtime Duration.

The column, Status, shows the overall status and completeness of the activity for the project. If a run has been performed successfully, a green status appears only if ALL entities within the activity have been processed.

The column, Processing Status, shows which entities (packages) have been processed and which entities haven't been processed. You can identify the different types of processing in this processing status column.

The Legend button on top of the project cockpit provides you with detailed information regarding the icons used in the status columns.

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 8887 Date: 20240523 Time: 195713     sap01-206 ( 143 ms )