Central Finance Cockpit for Support Tools
source link: https://blogs.sap.com/2023/12/14/central-finance-cockpit-for-support-tools/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Central Finance Cockpit for Support Tools
Introduction
The Central Finance Cockpit application serves as an organized framework for all the important transactions, tables, and reports that can be used by SAP team and Experienced Consultants to operate Central Finance.
Within the application, commonly used reports and transactions are thoughtfully grouped by topic or process, facilitating easy navigation for users.
Delivery
It is delivered via SAP note 3358225 for Central Finance System. Once this note is implemented (Or a relevant Support Pack or Release is upgraded where it is delivered) you can access this functionality via Transaction code: FINS_CFIN_COCKPIT
The below screen shot provides the overview of the delivered content (which could differ based on your system release,e.g : SAP S/4 HANA 1709,1809 …).
The tool features an auto-generated ALV tree functionality, where each node represents topic-wise transactions, reports, and tables.
Additionally, the tool offer flexibility by enabling users to extend the current framework, allowing them to maintain their node hierarchy according to their specific requirements.
Some of the examples are:
- FINS_CFIN_CO_SIMULATE – The report will help for simulate the both CO object mapping and CO document replication.
- RFINS_CFIN_MDG_MAPPING_TEST– Using this program users can directly check mapping entry by passing source value along with the logical system name, it is like a quick search.
- FINS_CFIN_DFA – (Data Flow Analyzer), It is a new transaction which has been delivered in the note 3152812 (https://me.sap.com/notes/3152812) the transaction is used to compare the document flow between source and target system, you can pass either source document or target document and you will get complete list of all the documents which links to it.
- RFINS_CFIN_REOPN_TECH_CLRD_DOC – The program used to re-open the technically cleared items in the target system.
- CFIN RFINS_CFIN_CORR_MISSING_CLRITM – The program used to extract the missing clearing items to the target system using AIF reset GUID which stuck with the error message FINS_CFIN_AC_DOC 056.
Tables Name | Purpose |
CFIN_EX_AIF_IDX | The table store the AIF GUID which comes from External interface AC_EX_DOC |
CFIN_AIF_PREREQ | The tables store the AIF serialization data |
CFIN_AIF_IDX_MUL | |
CFIN_AIF_IDX_TBL | Stores the AIF GUIDs from AC_DOC and AC_DOC_CHG interface |
Technical Details of the Framework
The cockpit is built on mainly two tables: FINS_CFIN_NODETX and FINS_CFIN_COKPIT.
These tables store the node information displayed during the Cockpit execution.
The FINS_CFIN_COKPIT table acts as the Hierarchy table, playing a vital role in building a tree structure in the report.
The FINS_CFIN_NODETX table serves as the Text table for Nodes in the ALV tree.
This tool has pre-delivered content, and you may add more entries for your own needs.
Before creating an entry in the FINS_CFIN_COKPIT table, a corresponding entry in the FINS_CFIN_NODETX table is required.
Both tables have a maintenance view, allowing users to maintain entries via the SM30 transaction, empowering them to create their own custom hierarchy.
Extensibility:
To Create a custom hierarchy
Step 1:
Create a node name in the FINS_CFIN_NODETX table.
Example: SPRAS = ‘EN’, NODE_NAME = ‘CUST_TOOLS’, and NODE_DESC = ‘Custom Tools’.
Step 2:
Update the FINS_CFIN_COKPIT table.
Select the group checkbox without the ‘Node Name’, ‘Object Type’, ‘Object Name’, and ‘Parent Node’ to create a main node.
Example: NODE_NAME = ‘CUST_TOOLS’ and NODE_GROUP = X.
Create an entry with ‘Node Name’, ‘Parent Node’, and Node Group = ‘X’ for sub-nodes.
Example: NODE_NAME = ‘CUST_TCODE’, PARENT_NODE = ‘CUST_TOOLS’, and NODE_GROUP = X.
2.3. Assign the elements to the nodes with fields ‘Node Name’, ‘Object Type’, and ‘Object Name’.
Example: NODE_NAME = ‘CUST_TCODE’, OBJECT_TYPE = ‘TRAN’, and OBJECT_NAME = ‘ ZCFIN_FIND_SPEC_AUTH ‘.
Result:
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK