Mapping SAP data to JPK_KR_PD and JPK_ST_KR
Preparing the SAP system for reporting JPK_KR_PD and JPK_ST_KR starts much earlier than generating the XML file. The key stage is proper data preparation and determining how the information recorded in the system will be assigned to fields required by the Ministry of Finance's logical structures.
This process is what we call data mapping.
In practice, mapping involves analyzing information recorded in the SAP system, determining its source, and assigning it to appropriate elements of the JPK report. Properly prepared mapping allows automating reporting and reducing the need for manual corrections during subsequent reporting periods.
Scope of data covered by mapping in SAP
The scope of mapping depends on the JPK structure and the way records are kept in the enterprise. In the case of JPK CIT, it includes both financial-accounting data and fixed asset information (two separate files).
The following areas are most often analyzed:
| Area | Data scope |
| General Ledger | Accounting entries, account balances, financial documents |
| Fixed assets | Registry data, values, depreciation, change history |
| Chart of accounts | Accounting accounts used during reporting |
| Contractor data | Contractor identification data |
| Organizational data | Business units, companies, activity areas |
| Dictionaries | Values used during reporting |
Each of these areas should be analyzed before starting solution development and testing.
Data sources used during mapping
One of the most important project stages is determining where the system will retrieve data used to create JPK CIT XML files.
From the SAP user perspective, information most often used is available in the following system areas:
| Place in SAP | Example data |
| General Ledger | Accounting entries and account balances |
| Fixed asset card file | Basic fixed asset data |
| Fixed asset explorer | Fixed asset values and depreciation |
| Fixed asset history report | Value and amortization change history |
| Basic contractor data | Identification data used in reporting |
| Chart of accounts | Accounting account structure |
Analyzing this data allows determining whether all information required by JPK structures is available in SAP or needs supplementation.
Preparing data mapping
The mapping process should start with business analysis, not solution configuration. It usually includes the following stages:
| Stage | Purpose |
| JPK requirements analysis | Identification of data required by JPK structures |
| SAP data analysis | Determining data sources |
| Developing mapping rules | Assigning SAP data to JPK fields |
| Testing | Verification of the accuracy of reported data |
| Validation | Checking compliance with the Ministry of Finance's dictionary requirements |
It is good practice to prepare complete mapping documentation before starting integration tests.
Common issues during data mapping in SAP
Most problems do not stem from the SAP solution itself, but from the quality of data collected in the system and the method of record-keeping.
The most common are:
incomplete master data,
lack of required information in fixed assets records,
different record-keeping rules in individual companies,
structure preventing 1:1 mapping of accounts to JPK CIT codes,
custom classification dictionaries used by the enterprise,
data inconsistency between SAP modules,
lack of documentation of previous changes.
The earlier such problems are detected, the easier it will be to prepare correct reporting.
Best practices for preparing mapping
Organizations implementing JPK CIT projects most often apply several proven principles.
The most important include:
starting data analysis early,
preparing and agreeing on mapping documentation,
organizing accounts and dictionaries used in SAP,
making a copy of production data before starting tests,
involving business users, accounting, and SAP consultants.
This approach significantly reduces the number of errors during implementation.
Checklist before generating JPK CIT
Before starting reporting, it is worth ensuring that all key elements have been verified.
| To check | Status |
| Master data is complete | ☐ |
| Chart of accounts has been verified | ☐ |
| Fixed assets data is up to date | ☐ |
| Dictionaries have been prepared | ☐ |
| Mapping rules have been developed | ☐ |
| Reporting tests have been conducted | ☐ |
| Data has been checked before submission | ☐ |
Such a checklist facilitates the organization's preparation for mandatory reporting and helps reduce the risk of errors.
Preparing mapping as part of the JPK CIT project
Data mapping is not a one-time task performed only during implementation. It should be treated as part of solution maintenance and data quality management in the SAP system.
Any change in the chart of accounts, fixed assets records, organizational structure, or Ministry of Finance requirements may require updating previously prepared mapping rules. Therefore, it is worth regularly reviewing project documentation and verifying whether the data used still meets current requirements.
Preparing SAP for JPK CIT reporting?
Proper data mapping is one of the most important elements of implementation JPK_KR_PD and JPK_ST_KR. The quality of this process determines the correctness of reporting and the ability to automatically generate files compliant with Ministry of Finance requirements.
Haergi supports enterprises in implementations JPK CIT in environments SAP ECC and SAP S/4HANA. We help analyze data, prepare mapping rules, conduct tests, and verify system readiness for reporting.
Contact our experts and find out how to prepare SAP for JPK CIT reporting.
JPK · JPK