SAP ERP, add-on for Polish SAF-T regulatory requirements 1

Configuration Guide

Document Version: 1.16 Released to Customer

Date: February 26, 2021

CUSTOMER

SAP ERP, add-on for Polish SAF-T regulatory

requirements 1.0

Configuration Guide CUSTOMER

SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0

Configuration Guide – Version: 1.16– Released to Customer

February 26, 2021

© 2021 SAP SE or an SAP affiliate company. All rights reserved. 2

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, table names, and key concepts of a programming language when they are

surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,

names of variables and parameters, source text, and names of installation, upgrade and

database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they

appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with

appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .




February 26, 2021


Document History

Version Status Date Change

1.0 Released to Customer Aug 2, 2016 Initial version

1.1 Released to Customer Aug 24, 2016 Desktop application eTransfer included

1.2 Released to Customer Sep 21, 2016 Minor revisions throughout the entire document

1.3 Released to Customer Oct 14, 2016 Desktop application eTransfer:

- Configuration is now possible via graphical interface

(sections 4.5.1, 4.5.2)

- A new feature for testing the connection to the Ministry

of Finance was introduced (section 4.6.1)

1.4 Released to Customer

Nov 18, 2016 Desktop application eTransfer:

- New configuration properties are introduced that allow to

configure the XML schemas for the XML validation

(section 4.5.2)

ERP add-on PLVAT:

- Update with the release of PLVAT 100 SP01

Description of new functionalities:

- Tax audit Document Number Range

- Excluded Codes of VAT

- Standard Authorization Objects

Added a list of figures.

1.5 Released to Customer Jan 20, 2017 ERP add-on PLVAT:

- Update with release of PLVAT 100 SP02, especially on

new XML versions

Minor revisions throughout the entire document

1.6 Released to Customer Jun 23, 2017 ERP add-on PLVAT:

- Update with release of PLVAT 100 SP03

- New IMG path for configuration

- New functionality for Tax ID no (NIP) validation





February 26, 2021



1.7 Released to Customer Dec 11, 2017 ERP add-on PLVAT:

- Update with release of PLVAT 100 SP04, especially on

new XML versions

- Customizing for Non-Taxable Tax Codes

- Data Protection & Privacy Report

- New functionality for deleting tax audit document

1.8 Released to Customer Jan 02, 2018 Desktop application eTransfer:

- Update with the release of PLVAT_DESKTOP 100 SP00

Patch 5

1.9 Released to Customer May 17, 2018 Expanded and updated DP&P section and moved it to the

Security section

1.10 Released to Customer Jul 15, 2018 Update with information about supported SAP ERP

modules

1.11 Released to Customer Sep 14, 2018 Desktop application eTransfer:

- Modernized user interface

- Improved accessibility

ERP add-on PLVAT:


- Customizing for Special Ledger

- SAF-T Additional Parameters

1.12 Released to Customer May 13, 2019 ERP add-on PLVAT:

- Update with release of JPK FA (2)

- Company code address data

- SAF-T Additional Parameter for downpayment accounts


1.13 Released to Customer Nov 4, 2019 ERP add-on PLVAT:

- Update with release of JPK FA RR

- SAF-T Additional Parameter for Local Currency

1.14 Released to Customer Jan 27, 2020 Desktop application eTransfer:

- Update with the release of PLVAT_DESKTOP 100

SP01 Patch 3

ERP add-on PLVAT:


- New structure JPK FA (3)

- New structure JPK VAT (4)

1.15 Released to Customer July 9, 2020 Desktop application eTransfer:

- Update with the release of PLVAT_DESKTOP 100

SP01 Patch 4




February 26, 2021



1.16 Released to Customer Feb 26, 2021 ERP add-on PLVAT:


- Report from archive

- Definition of additional reports




February 26, 2021


Table of Contents

1 About This Document ........................................................................................... 10 1.1 Purpose and Scope ........................................................................................................................ 10 1.2 Target Audience ............................................................................................................................. 10 1.3 Glossary ......................................................................................................................................... 10 1.4 Important SAP Notes ...................................................................................................................... 11

2 Solution Overview ................................................................................................. 12 2.1 Scope of Solution ........................................................................................................................... 12

3 Configuration Information for ERP Add-on PLVAT ............................................... 13 3.1 Configuration with Business Configuration Sets ............................................................................. 13 3.2 Manual configuration of application ................................................................................................ 13

General Parameters ....................................................................................................... 14 Accounting Books ........................................................................................................... 36 Warehouse ..................................................................................................................... 38 Value-Added Tax (VAT) Register ................................................................................... 39 Invoices........................................................................................................................... 51

3.3 Additional configuration for DP&P functionality............................................................................... 54

4 Installation and Configuration Information for Desktop Application eTransfer . 57 4.1 Workstation Preparation ................................................................................................................. 57 4.2 Workstation Installation .................................................................................................................. 57 4.3 Network Installation ........................................................................................................................ 58 4.4 Starting the Application ................................................................................................................... 58 4.5 Application Configuration ................................................................................................................ 58

Configuration in Application ............................................................................................ 58 Configuration Parameters ............................................................................................... 59 Electronic Signature Configuration ................................................................................. 62

4.6 Testing ............................................................................................................................................ 62 Testing Connection ......................................................................................................... 62 Starting Application in Test Mode ................................................................................... 63

4.7 Languages ...................................................................................................................................... 63

5 Security Information ............................................................................................. 65 5.1 Authorization Concept .................................................................................................................... 65

Roles .............................................................................................................................. 65 Authorization Objects ...................................................................................................... 65 Standard Authorization Objects ...................................................................................... 67

5.2 Preparation and Sending of SAF-T Data (Java) ............................................................................. 68 Preparation of SAF-T Documents ................................................................................... 68 Encryption of SAF-T Data ............................................................................................... 68 Encryption of Encryption Key .......................................................................................... 69 Preparation of Authentication Metadata .......................................................................... 69 Host Interface Documents SAF-T for Clients .................................................................. 69




February 26, 2021


InitUploadSigned Method................................................................................................ 69 Put Blob Method ............................................................................................................. 70 FinishUpload Method ...................................................................................................... 70 Status ............................................................................................................................. 70

5.3 Ports ............................................................................................................................................... 70 5.4 Data Protection & Privacy ............................................................................................................... 70

Glossary.......................................................................................................................... 71 Read Access Logging ..................................................................................................... 72 Information Retrieval ....................................................................................................... 73 Deletion of Personal Data ............................................................................................... 73 Change Log .................................................................................................................... 75

6 Operations Information ......................................................................................... 76 6.1 Monitoring ....................................................................................................................................... 76 6.2 Administration and Management .................................................................................................... 76

Technical Configuration .................................................................................................. 76

7 Appendix ............................................................................................................... 77 7.1 Using SCPR20 transaction to upload and activate BCSets ............................................................ 77 7.2 Rebuild info structure ...................................................................................................................... 79




February 26, 2021


Table of Figures

Figure 1: JPK Configuration Parameters ..................................................................................................................... 14

Figure 2: Company Code Configuration ....................................................................................................................... 14

Figure 3: Basic Parameters ......................................................................................................................................... 17

Figure 4: Company Code Address Data ...................................................................................................................... 18

Figure 5: Plant Abroad Address Data .......................................................................................................................... 18

Figure 5: Company Identification and Address ............................................................................................................ 19

Figure 6: National Address .......................................................................................................................................... 19

Figure 7: Foreign Address ........................................................................................................................................... 20

Figure 8: Table /PLVAT/JPKSPF ................................................................................................................................. 21

Figure 9: Table /PLVAT/JPKPARV .............................................................................................................................. 22

Figure 10: Table /PLVAT/JPKMSG .............................................................................................................................. 23

Figure 11: Table with all supported versions ................................................................................................................ 23

Figure 12: Table of Tax Offices .................................................................................................................................... 24

Figure 13: Table with XML Attributes ........................................................................................................................... 25

Figure 14: Table /PLVAT/JPKSRC .............................................................................................................................. 26

Figure 15: Definition of KR version 1 for Source Type – ERP data .............................................................................. 26

Figure 16: Definition of KR version 1 for Source Type – Flat file.................................................................................. 27

Figure 18: Archive Objects Configuration .................................................................................................................... 29

Figure 19: Additional parameters maintenance view ................................................................................................... 30

Figure 20: Maintenance of additional reports ............................................................................................................... 35

Figure 21: Report name translation .............................................................................................................................. 35

Figure 22: Position of new reports in the toolbar .......................................................................................................... 35

Figure 23: Accounting Books ....................................................................................................................................... 36

Figure 24: Table /PLVAT/JPKKKZ ............................................................................................................................... 37

Figure 25: Table /PLVAT/JPKKKK ............................................................................................................................... 37

Figure 26: Table /PLVAT/JPKKKP ............................................................................................................................... 38

Figure 27: VAT Register .............................................................................................................................................. 39

Figure 28: VAT Purchase Classifiers ........................................................................................................................... 40

Figure 29: VAT Sales Classifiers ................................................................................................................................. 41

Figure 30: Table /PLVAT/JPKTYD ............................................................................................................................... 42

Figure 31: Table /PLVAT/JPKGRM .............................................................................................................................. 42

Figure 32: Determination Methods ............................................................................................................................... 43

Figure 33: VAT Versions .............................................................................................................................................. 45

Figure 34: Table /PLVAT/JPKVVERV4 ........................................................................................................................ 46

Figure 35: Table /PLVAT/JPKVZKK ............................................................................................................................. 46

Figure 36: Table /PLVAT/JPKVSKK ............................................................................................................................ 47




February 26, 2021


Figure 37: Table /PLVAT/JPKVEXCL .......................................................................................................................... 47

Figure 38: Mapping document types ............................................................................................................................ 48

Figure 39: Mapping groups using materials ................................................................................................................. 48

Figure 40: Numbering for repeated combination .......................................................................................................... 49

Figure 41: Mapping groups using document types and tax codes ............................................................................... 49

Figure 42: VAT Declaration Definition .......................................................................................................................... 50

Figure 43: Invoice Parameters ..................................................................................................................................... 51

Figure 44: Table /PLVAT/JPKVTEC ............................................................................................................................ 52

Figure 45: Table /PLVAT/JPKVRST ............................................................................................................................ 53

Figure 46: Table /PLVAT/JPKV_ST ............................................................................................................................. 54

Figure 47: Transaction SM30 ....................................................................................................................................... 54

Figure 48: Maintenance View PLVT ............................................................................................................................. 55

Figure 49: View V_DPP_MASK_RSTRC ..................................................................................................................... 55

Figure 50: Configuration Parameters ........................................................................................................................... 59

Figure 51: eTransfer Test Mode................................................................................................................................... 63

Figure 52: eTransfer Languages .................................................................................................................................. 64




February 26, 2021


1 About This Document

1.1 Purpose and Scope

This Configuration Guide provides a central starting point for the technical implementation and configuration of SAP

ERP, add-on for Polish SAF-T regulatory requirements 1.0. It contains all activities necessary for configuring the

application.

1.2 Target Audience

This document is intended for the following target audiences:

• Consultants

• Partners

• Customers

1.3 Glossary

Abbreviation Term Definition

CN Combined Nomenclature Goods nomenclature established to meet the

requirements of both the Common Customs Tariff and

of the external trade statistics of the European Union.

DPP Data Protection & Privacy Protection from unauthorized processing (storing,

transmitting, changing, deleting) of personal data

DPP Report Data Protection & Privacy Report Report with function to display personal data and

function to display activities performed on personal data

collected in tax audit documents

FA Invoices Sales VAT invoices

JPK Jednolity Plik Kontrolny Polish name for Standard Audit File for Tax

KR Financial books ZOIS Trial balance and documents journal

MAG Warehouse Documents Documents based on material movements

MF Ministry of Finance Polish Ministry of Finance

PKWiU Polska Klasyfikacja Wyrobów i

Usług

Polish Classification of Goods and Services




February 26, 2021


Abbreviation Term Definition

SAF-T Standard Audit File for Tax An international standard for electronic exchange of

reliable accounting data from organizations to a

national tax authority or external auditors

SAP

NetWeaver

ILM

SAP NetWeaver Information

Lifecycle Management

Business function that enhances the SAP standard

delivery with the ability to manage the lifecycle of live

and archived data, based on rules. SAP NetWeaver

ILM provides the functions that support the simplified

blocking and deletion of personal data

SP Support Package Official SAP Support Package for the solution

UPO Urzędowe Poświadczenie Odbioru Document confirming that JPK files were loaded on MF

Portal

VAT Value-added tax register VAT register

WB Bank statements Bank statements

1.4 Important SAP Notes

Notes for ERP add-on PLVAT 100:

• 2351241: SAF-T Poland: Release strategy for "SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0"

• 2345524: SAF-T Poland - PLVAT 100: Release note PLVAT 100

• 2392769: SAF-T Poland - PLVAT 100: Release note PLVAT 100 SP01








Notes for desktop application eTransfer:

• 2357171: SAF-T Poland - PLVAT_DESKTOP 100: Release note PLVAT_DESKTOP 100

• 2688783: SAF-T Poland - PLVAT_DESKTOP 100: Release note PLVAT_DESKTOP 100 SP01

• 2848285: SAF-T Poland - PLVAT_DESKTOP 100: Release note PLVAT_DESKTOP 100 SP01 Patch 2






February 26, 2021


2 Solution Overview

This configuration guide describes the configuration steps for two main areas: general parameters and Jednolity Plik

Kontrolny (JPK) types.

This document also provides information on how SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0

supports Data Protection & Privacy compliance.

The general parameters area contains general settings that are not directly related to any individual JPK type:

• Company code configuration

• SAF-T information types

• Tax office codes

• Number range for tax audit document

• XML active versions

• XML default values

• SAF-T data sources

• SAF-T data processing

• Archive infosystem structure assignment

• SAF-T parameters list

• Definition of additional reports

Configuration of JPK types covers:

• Accounting books

• Warehouse

• VAT Register

• Invoices

The following sections of the document describe in detail the process of setting up all the configuration parameters.

2.1 Scope of Solution

SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0 comprises data extraction from the following SAP

ERP modules:

• SAP Fl

• SAP MM

• SAP SD

Requirements and functionalities described below are not included in "PLVAT 100" solution:

• data extraction from FI-CA, FI-TV, RE-FX

• data extraction from dedicated industry solutions (SRM, SAP Sourcing, IS-U, CFM, HER, ...).




February 26, 2021


3 Configuration Information for ERP Add-

on PLVAT

3.1 Configuration with Business Configuration Sets

Note

When new implementation begins, it is mandatory to start configuration of PLVAT tool with the upload of initial

configuration. The initial configuration is installed automatically during implementation of the PLVAT package but is

available only on client 000. In order to easily get this initial configuration, we have prepared Business Configuration

Set aka BCSet. This will deliver all new configuration records for future functionalities. Upload and activation of BCSet

should be executed with transaction SCPR20. Instructions on how to use SCPR20 can be found in the appendix 1

Using SCPR20 transaction to upload and activate BCSets.

The current valid version of the initial configuration depends on the system support package level and is available in

the note 2376385 - SAF-T Poland - PLVAT 100: BC set for starting the configuration as a ZIP file attachment. This

note cannot be implemented with the SNOTE transaction.

Please pay attention to keeping the right sequence of uploading and activating BCSets and transporting configuration

requests with BCSets and manual entries. Due to a change of legal requirements, you may receive new partial

BCSets via notes.

3.2 Manual configuration of application

Access to the IMG tree

Launch the PLVAT configuration in Customizing (tr.SPRO) under Financial Accounting (New) → Financial Accounting

Global Settings (New) →Tax on Sales/Purchases →Basic Settings → SAF-T PLVAT Poland Configuration.

The initial screen of the SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0 configuration appears.

Alternatively, you can also start transaction code /N/PLVAT/JPK0 in the command field; this will display the relevant

PLVAT IMG tree only.

Note

When you use the command field, you must enter the prefix /N before transaction code /PLVAT/JPK0. You

can add the transaction code /PLVAT/JPK0 to your Favorites folder. In this case, don't enter the prefix /N.

Customizing areas

• General parameters

• Accounting Books

• Warehouse

• VAT Register

• Invoices

https://launchpad.support.sap.com/#/notes/2376385




February 26, 2021


General Parameters

This IMG tree area parameters mostly refer to the basic configuration elements of the program. They are crucial for

the whole application but also contain some data needed for the selected JPK type. Parameters of XML files are

subject of change due to new legal requirements. Some parameters are delivered with BCSets and should not be

modified by the user. The following sections will discuss the parameters that should be modified and those that the

user should not change.

Figure 1: JPK Configuration Parameters

3.2.1.1 Company Code Configuration

Access this screen area by using transaction SPRO under Financial Accounting (New) →Financial Accounting Global

Settings (New) →Tax on Sales/Purchases →Basic Settings → SAF-T PLVAT Poland Configuration→ General

Parameters→ Company Code configuration.

This screen area contains settings that are related to individual Company codes. In order to modify company-code

related parameters, please select the desired company code in the left panel.

Figure 2: Company Code Configuration




February 26, 2021


3.2.1.1.1 Basic parameters

This part of the configuration contains some basic parameters related to general functionalities. Data is stored in the

/PLVAT/JPK0 table:

• You can create tax audit documents, but only for those company codes for which you have selected the CC

active.

• The Read from archive active checkbox activates the reading from the archive for the selected company code. If

activated, it will then be possible to retrieve the data not only from the database but also from the archive for the

chosen JPK type and selection parameters specified on the JPK Data Source Parameters screen.

• This switch allows you to enable reading from the archive for selected data sources. This means the option to

read from archive will be available for end users; otherwise, the option in the definition of the data source is

disabled.

• If you select the Payment Ref. checkbox, the system reads the vendor invoice numbers from the Payment

reference field [BSEG-KIDNO] on vendor items. If field is not populated, the value from the [BKPF-XBLNR] field

will be taken. This field is used by some companies if the vendor invoice number length exceeds 16 characters.

• The Alt.ChartOfAcc. field is used for assigning an alternative chart of accounts for GL account classification in

JPK KR in the node ZOIS (Trial balance). This switch doesn’t change the presentation of the accounts, and

accounts from operational chart of accounts will be used.

• If you check the Settlm.Document checkbox, this causes settlement documents to be visible in the documents

journal. Settlement documents do not have items, only headers.

• If you select the Tax Base Amnt. Ded. checkbox, the system displays the tax base value only in the part that is

the basis for calculating the amount of deductible VAT.

• If you select the Loc.Curr.Inst.Domes. checkbox, the system reads the net and VAT values in the JPK VAT from

the country currency instead of the local currency. If you select this checkbox, the system reads the values from

the fields LWBAS and LWSTE instead of the HWBAS and HWSTE (table BSET).

• If you check the Val. Movem w/o Val. checkbox, the system calculates and displays values for movements

without valuation in the JPK MAG Warehouse.

• The Date format field defines the date format expected in text fields. If you don't make any settings in this field,

the default format is DD.MM.YYYY. This is parameter is used to read VATDATE in case when date is stored in

[BKPF-BKTXT] field.

• In the Destin. folder field, you specify the place where XML files should be saved on the application server or

assign the logical name of the folder (if the parameter ‘Logical Name’ is set). Logical folder should be

maintained in transaction AL11.

• If you select the Logical Name checkbox, the logical folder name is maintained. The use of logical folder names

allows you to use the same name for different systems and assign different physical paths.

• Use the Special Ledger field to assign the Special Purpose Ledger from which data is retrieved to the JPK KR

structure. If the field is filled in the SAF-T configuration, the system automatically takes the Special Purpose

Ledger to the data source, and the ledger cannot be changed in the data source parameters.

• Enabling the Inv. NIP Validation option causes the system to validate VAT ID numbers (NIP) in JPK FA

Invoices. You can choose between the Check Only mode and the Check and delete if error mode. Polish NIP

number must have 10 digits and a valid checksum; otherwise they are reported as wrong.

• Enabling the VR NIP Validation option causes the system to validate VAT ID numbers (NIP) in JPK VAT

Register. You can choose between the Check Only mode and the Check and delete if error mode. Polish NIP

numbers must have 10 digits and valid checksum; otherwise they are reported as wrong.




February 26, 2021


• Enabling the Alt. Proc. Vat Reg. option causes the system to use the alternative procedure for tax data

collecting.

• The System name field is an obligatory field for the header of JPK VAT structure. This field should be completed

by name of the system from which the data originates.

• Enabling the Event Logging option causes the system to save changes made in tax audit document in the

Activity Log.

• Enabling Std.Spl.Paym.Method causes the system to mark invoices as split-payment-relevant in the JPK FA (3)

structure and JPK VAT (4) structure based on the following criteria:

o Conditions in a standard SAP solution for Poland Split Payment - PLVAT 100 checks the

"GLO_MATCODE_PL_V" view for PKWiU codes that users classified as split-payment-relevant and

analyses the gross amount of the invoice. For more details about the "GLO_MATCODE_PL_V" view and

Poland Split Payment, please refer to the notes “2834977 - Split Payment becomes obligatory for certain

types of Goods and Services” and “2845577 - Poland Split Payment: Logistics Note DDIC Object

Changes”. In standard PLVAT, if the gross amount of the invoice is equal to or greater than 15.000, - PLN

and the PKWiU code is split-payment-relevant, the system recognizes the document as a split-payment-

relevant. The gross amount analyzed by the system could be changed from 15.000, - PLN to another

value, by using the parameter JPK_SPL_OBLIG_VALUE in PLVAT configuration. For more details about

the parameters please refer to chapter 3.2.1.9.

o Business process indicator stored in the FI/SD documents - PLVAT 100 checks, if the MPP business

process indicator is stored in the FI document and based on that marks the invoice as split-payment-

relevant. Indicators can be read from SD billing documents, by using the parameter

JPK_COMMGR_BUSPR_FROM_SD in PLVAT configuration, described in the chapter 3.2.1.9.

For more details about the business process indicators and commodity group indicators stored in the

FI/SD documents, please refer to the note “2903258 - Poland JPK VAT Sales Process Enhancement -

Collective Note”.

• If you select the Payment Form Met checkbox, the system marks invoices as split-payment-relevant in the JPK

FA (3) structure and JPK VAT (4) structure based on the payment method used in the Financial document and

configured in PLVAT customizing in area Split-payment-relevant payment forms.

Enabling FI Doc Tax Code Mth causes the system to mark invoices as split-payment-relevant in the JPK FA (3)

structure and JPK VAT (4) structure based on the financial document type and tax code configured in PLVAT

customizing in area Split-payment-relevant FI documents and tax codes.

• If you select the User Routine SplMth checkbox, the system allows you to use a custom method to mark

invoices as split-payment-relevant in the JPK FA (3) structure and JPK VAT (4) structure. Custom methods can

be implemented in a dedicated enhancement point:

enhancement-point /plvat/jpk05_spl_payment spots /plvat/jpk05_process.




February 26, 2021


Figure 3: Basic Parameters

3.2.1.1.2 Address Data

The PLVAT solution offers two methods of determining the address needed for presentation in XML files. The first is

based on standard functionality, and the data is downloaded directly from the definition of the business unit. The

second method is to enter data regarding the address of the business unit directly in the PLVAT configuration.

Configuration of Address Data in SAP standard

XML structures require additional address data of the Company Code (for example district, community).

In order to complete this data, launch Company Code customizing under Financial Accounting (New) → Financial

Accounting Global Settings (New) → Global Parameters for Company Code → Enter Global Parameters.

Choose the Address tab and complete the highlighted fields with the data corresponding to the company code:




February 26, 2021


Figure 4: Company Code Address Data

Configuration of Address Data in SAP standard in case of Plants Abroad

In case of Plants Abroad where legal entity address data is not related to Company Code address data, needed

address records will be collected from the definition of the plant. Go to Financial Accounting (New) → Financial

Accounting Global Settings (New) → Tax on Sales/Purchase → Basic Settings → Plants Abroad → Enter Vat

Registration Number for Plants Abroad. Enter address data and VAT ID for country PL as follows:

Figure 5: Plant Abroad Address Data

Configuration of Address Data in PLVAT 100

To maintain Company Code address data, launch SAF-T PLVAT Poland Configuration→ General Parameters→

Company code configuration→ Company Identification and Address Configuration. To activate address data from

PLVAT customizing, select checkbox Repl.CC Address (Replace Company Code Address).

Company Identification and Address Configuration

This area contains information about Company Code VAT Registration Number, National Business Registry Number,

Company Name, Contact E-Mail Address (displayed in XML for VAT (3) and VAT (4) structure), and address.




February 26, 2021


Figure 6: Company Identification and Address

If you select the PltAbroadAddr checkbox, the program takes the address data to XML from the plant abroad data

instead of the company code data.

To activate the address data from PLVAT customizing instead of SAP standard, select checkbox Repl.CC Address.

Option Address for XML allows you to configure which address data is presented in the header part of XML files.

Option Address for Doc. allows you to configure which address data is presented in the field seller address (P_3D) in

JPK FA structure.

National address

This area allows you to configure the Voivodeship, District, Community, Street, House Number, Apartment Number,

City, Postal Code, and Post Office for Company Code National Address.

Figure 7: National Address

Foreign Address

This area allows you to configure the Country, Street, House Number, Apartment Number, City, Postal Code for

Company Code Foreign Address.




February 26, 2021


Figure 8: Foreign Address

Note

Option available only for the JPK FA (3) structure.

3.2.1.1.3 Split-payment-relevant payment forms

This area allows you to configure payment methods that are split-payment-relevant. If the configured method is used

in the financial document, the system marks this document as split-payment-relevant in the JPK FA (3) structure and

JPK VAT (4) structure.

Note

Option is activated if Payment Form Met checkbox was selected in the Basic parameters for Company code.

3.2.1.1.4 Split-payment-relevant FI documents and tax

codes

This area allows you to configure split-payment-relevant financial document types, tax codes, or a combination of

both. The system marks invoices as split-payment-relevant in the JPK FA (3) structure and JPK VAT (4) structure

based on the financial document type and tax code configured in /PLVAT/JPKSPF table. It is possible to use any

combination of document type and tax code or single values for both as filter conditions.




February 26, 2021


Figure 9: Table /PLVAT/JPKSPF

Note

Option is activated if FI Doc Tax Code Mth checkbox was selected in the Basic parameters for Company

code.

3.2.1.1.5 Additional parameters Values

This part of configuration allows you to change the logic of the program, enabling parameters and assigning values to

them. A parameter’s value is assigned on the Company Code level. You can use any parameter defined in the global

part of the configuration; for details refer to the SAF-T Parameters List. Note that you can use each parameter only

ones for a single Company Code. The values are populated without apostrophes. Simple example of parameter

values appears on the screen below.




February 26, 2021


Figure 10: Table /PLVAT/JPKPARV

Note

For characteristics of the SAF-T parameters refer to chapter 3.2.1.9.

3.2.1.1.6 Message Configuration

This area allows you to configure the target type for the system messages displayed in SAP ERP, add-on for Polish

SAF-T regulatory requirements 1.0. Message display configuration is available on the Company Code level. You can

determine whether a message should be displayed and what type the message should have by selecting message

class, message number, and one of following final types:

• E Error

• I Information

• N Don’t Display

• W Warning

Please be very careful, especially when setting option – Don’t Display. Some important message can be missed!




February 26, 2021


Figure 11: Table /PLVAT/JPKMSG

3.2.1.2 SAF-T Information Types

The /PLVAT/JPKSTY table contains the definition of the codes of JPK along with names, used in SAP ERP, add-on

for Polish SAF-T regulatory requirements 1.0. JPK information types are XML-version-dependent. This table is

delivered with content, see Configuration with Business Configuration Sets. The following JPK information types

exist:

Figure 12: Table with all supported versions

Note

Do not change the contents of this table.

3.2.1.3 Tax Office Codes

The /PLVAT/JPKKUS table contains a list of the codes of tax offices together with their names used in SAP ERP,

add-on for Polish SAF-T regulatory requirements 1.0. These codes are assigned to the company codes in the table

/PLVAT/JPK0 (Company code configuration). This table is delivered with the following content, see Configuration

with Business Configuration Sets.




February 26, 2021


Figure 13: Table of Tax Offices

3.2.1.4 Number range for tax audit document

You access the maintenance of number range objects using the SNRO transaction. Choose Change intervals to make

an entry as follows:

1. Enter a number range with the number 01.

The maximum extension length is six characters. This range is used for automatic numbering of tax audit

documents.

2. Enter /PLVAT/JPK as object number name.




February 26, 2021


3.2.1.5 XML Active Versions

The /PLVAT/JPKXJPK table contains the definitions of the headers of active XML versions and namespace

definitions for the different types of JPK. This table is delivered with the following content, see Configuration with

Business Configuration Sets:

Figure 14: Table with XML Attributes

Note

Do not change the entries provided in the order.

3.2.1.6 XML Default Values

In this Customizing activity, you can enter default and fixed values for JPK XML elements. Default values are used if

the element is obligatory and no value was assigned. Fixed values are always used to fill elements regardless of the

data in the current document. These values will overwrite the obligatory and non-obligatory elements in the XML file.

Default and fixed values are used during the XML creation process.

Note

The entered values must be of the required type.

3.2.1.7 JPK Data Sources

The /PLVAT/JPKSRC table contains the definition of the types of data sources, which consists of the assignment to

the source type, full and abbreviated name. This table is delivered with the following content; see Configuration with

Business Configuration Sets. Default configuration contains two types, but the user can define a separate type. This

can be used to add a separate extractor where the source for data is different from the default. It is possible to build a

separate interface to a third-party application in order to collect external data.




February 26, 2021


Figure 15: Table /PLVAT/JPKSRC

Note

Do not remove the types of data sources 1 and 2.

3.2.1.8 JPK Data Processing

The /PLVAT/JPK1 table contains the configuration of the processing modules for the different types of JPK.

Specialized ABAP classes are assigned to the various types of sources for each type of JPK. Each line contains the

definition of two classes:

• Main class – data manager

• Data class – data extractor

The combination of these two classes needs to be assigned to the single source type, JPK type, and JPK version. It

is also possible to assign different classes to the selected Company Code, in which case these classes will be used

when the document is related to the Company Code. If Company Code field is empty, it means it is valid for all other

Company Codes. If the user decides to define a separate data source type, see JPK Data Sources, the data

manager and data extractor classes need to be assigned for each JPK type and JPK version. An example of class

assignment appears below.

This table is delivered with the content; see Configuration with Business Configuration Sets. It contains assignments

of classes for all supported versions

Figure 16: Definition of KR version 1 for Source Type – ERP data




February 26, 2021


Figure 17: Definition of KR version 1 for Source Type – Flat file

3.2.1.9 Archive Infosystem Structure Assignment

3.2.1.9.1 General overview

Since Support Package 08, PLVAT supports reading data from archive. Data Archiving – a service provided by SAP

NetWeaver – removes mass data that the system no longer needs online but which must still be accessible at a later

date, if required, from the database. Data in the database can only be archived using archiving objects, which

describe the data structure and context. There are both technical and legal reasons for archiving application data.

Data Archiving:

• Resolves memory space and performance problems caused by large volumes of transaction data

• Ensures that data growth remains moderate so that the database remains manageable in the long term

• Ensures that companies can meet the legal requirements for data storage in a cost-efficient manner

• Ensures that data can be reused later, for example, in new product development

The PLVAT addon supports reading from an archive based on the archiving objects of the Archive Development Kit

(ADK). Other types of archiving are not supported. The addon supports reading of archived transaction data and

archived master data. ADK is delivered with SAP NetWeaver and is the technical framework and basis for SAP’s data

archiving solution. ADK is a development environment and an application interface between SAP applications, the

database, and the archive files where your data is stored. ADK ensures that data archiving is independent of

hardware and release changes. More details can be found under the link:

• https://help.sap.com/doc/saphelp_nw70/7.0.31/en-US/2a/fa0391493111d182b70000e829fbfe/frameset.htm

You can determine which archiving objects to use based on your business needs. You can opt to archive only

selected transactional data, selected master data, or both. It is possible that some objects will not be archived while

others can be processed several times within the same period. If this happens, it is impossible to know which data

should be read from archive in general. If we want to be sure to collect all needed data, we should always perform

data reading from operational tables and archive in the same run for tables containing operational data. The

customer can disable archive reading; this functionality is realized by new configuration. It is possible to disable

reading from the archive for all objects or for selected tables.

https://help.sap.com/doc/saphelp_nw70/7.0.31/en-US/2a/fa0391493111d182b70000e829fbfe/frameset.htm




February 26, 2021


One of the most important elements of the ADK is the concept of the info structure. Each archive object can contain

data from multiple tables. Depending on the structure of the archiving object, different info structures can be defined.

Each archive object can have more than one info structure. Each of the info structures is built on a catalogue of fields

that can be modified by users at the stage of creating or modifying the info structure. The key fields of archive object

are obligatory for the info structure, while other fields are optional. It is also worth adding that info structures can be

created at the document header level or at the item level. The latter difference may affect whether the requested

document can be found using a specific info structure. For example, if a financial document has a header and items,

it can be read using both types of info structure, while if the document has only a header, it will not be possible to

read it using an item-based info structure. It should also be added that info structure should contain at least the most

important fields for a given object in the field catalogue. In the SAP system it is possible to add new fields to the

existing info structures, or to create new ones based on modified catalogs. The approximate procedure for rebuilding

info structure is attached in appendix 2 Rebuild of infostructure. The same procedure can be used to modify any

other info structure.

Note

An extremely important role in the PLVAT addon is the archiving object for FI documents, by default

FI_DOCUMNT. The definition of the info structure provided with the standard system does not include the

VATDATE field, which is extremely important for the VAT structure. The recommended action is to modify

the info structure to add this field to the field catalog. If modification is not possible, then it will be necessary

to specify the restriction using the posting date in the definition of the data source.

3.2.1.9.2 How system reads data from archive

The logic of reading data from archive refers to the PLVAT archive objects configuration table :

1. Find archive object for current query.

2. If not found, raise an error message and go to point 12. (Complete the configuration and restart data extraction.)

3. If current query is excluded from archive reading, “Do Not Read” checked, go to point 12.

4. If configuration contains info structure, go to point 8.

5. If info structure is not provided, start search procedure.

6. Find all active info structures for given archive object.

7. Try to determine best info structure that fits current query.

8. If there is no active info structure or none of them fit query, raise error message and go to point 12 (this situation

means that it is necessary to check the configuration of info structures).

9. Check if selected info structure fits current query.

10. If result is negative, raise error message and go to point 12 (this situation means that it is necessary to check the

configuration of info structures or check PLVAT configuration of archiving object).

11. Read data from archive with selected info structure.

12. End of processing archived data.




February 26, 2021


3.2.1.9.3 PLVAT archive objects configuration table

The picture below shows a part of the configuration for archive objects. This table is delivered with content; see

Configuration with Business Configuration Sets. When the user selects the “Read from archive” option in the

definition of the data source, the system uses this configuration to get archived data. If the option is not selected, then

this configuration has no impact on data extraction.

Figure 18: Archive Objects Configuration

What do the following columns mean in the configuration shown?

1. Table name – table which is subject of query

1. Business process – same table can be part of different archiving objects; this field can be set as:

2. General – option default when table is assigned to only one archiving object

3. Delivery – used to read data related to delivery documents – for example, table VBFA

4. Billing – process is set if billing data are needed, e.g. table VBFA

2. Sale – used to read sale data – for example, VBFA

3. Archive object – name of archive object which contains needed data

4. Active info structure – By default this field is empty; this means the system will be search for active info

structures that fit the current query. It is possible to set this field manually if you wish to use only the selected

one.

5. Do Not Read – This checkbox is used to disable reading form archive for current table. You will need to disable

some tables from archive reading if the data for selected object is not archived there. For example, in the user

system, only transactional data is archived, so all tables containing master data should be disabled.

3.2.1.10 SAF-T Parameters List

Parameters can be applied to single or multiple modules. The name of a parameter starts with the module name

where it was used. If a name of parameter starts with “JPK_” it means the parameter is used in more than one

module. Parameters are used to change the logic of data extractors. This allows to get greater flexibility of the tool to

match the needs of the client's business. The list of parameters is common for all Company Codes, but the user can




February 26, 2021


assign different values and not use at all at the Company Code level. The user can define separate parameters with

names starting with letter Z or Y.

The /PLVAT/JPKPARD table contains the list of standard parameters that have been implemented in the "PLVAT

100" solution. This table is delivered with the following content, see also Configuration with Business Configuration

Sets:

Figure 19: Additional parameters maintenance view

Note

You can also add user-specific parameters and implement them in the enhancements.

Parameters can be read with method /PLVAT/CL_JPK_SYSTEM=>GET_PARAMETER.

No Parameter Name Description of Parameter

1. FA_DOWNPAYMENT_ACCOUNTS Allows you to specify down payment clearing accounts,

used to identify transactions related to the down payment

process. See SAP Note 818079 - PL: Down Payment

Invoice for Poland. Up to three GL accounts separated by

semicolons can be specified. Enter accounts with leading

zeros. The parameter has been used in the FA module

since version 2.






February 26, 2021



2. FA_USE_LOCAL_CURRENCY Company codes can define one or two additional local

currencies that are stored per company code parallel to the

first local currency. This parameter is intended for

company codes where the second or third local currency is

used for legal reporting purposes in PLN. If this parameter

is activated, the system displays values in the second or

third local currency in JPK FA structure. To activate

reading values for FA from the second or third local

currency, the new parameter must be set respectively 2 or

3

3. JPK_SPL_OBLIG_VALUE For the purpose of marking split-payment-relevant

invoices, the system checks the gross value of the invoice.

The default value that makes split payment mandatory is

greater than 15.000, PLN. The value could be changed by

activating this parameter. The parameter allows you to

specify the minimum gross value of the invoice from which

the split payment is applicable. If not specified, the default

value 15 000.01 PLN is used. This parameter is used in

the FA and VAT modules.

4. KR_LOCAL_CURRENCY Company codes can define one or two additional local






third local currency in JPK KR structure. Activate reading

of second or third local currency for selected GL. The

accepted value can be 2 or 3 respectively. If not set.

values are read from selected ledger according to the

switch in section Basic Parameters. Also, if the selected

second or third local currency is not PLN, this parameter

will be ignored.

5. KR_PACKAGE_SIZE This parameter restricts the number of records in a single

SQL query since some databases have restrictions

regarding available capacities. With this parameter the size

of selection from database package during extraction

phase, integer value (default 100).

6. VAT_GROUP_SEPARATOR For the purpose of deriving Supply Procedures and

Services Groups in the JPK VAT (4) structure, the system

searches for a supply or group symbol accompanied by a

one-character start and end delimiter. The default delimiter

is #. This delimiter can be changed by activating this

parameter. The value of the parameter can contain a

single character.




February 26, 2021



7. VAT_SD_EXCLUDE_ITEM_TYPES This parameter causes the system to recognize which

delivery of goods and provision of services group (GTU)

should be marked on the correction invoices based of the

sales document item categories (VBRP-PSTYV) assigned

in parameter configuration. Default category provided with

the standard configuration is G2N. To activate parameter,

enter a list of sales document item categories (VBRP-

PSTYV) used in the system to indicate “Before correction"

items. Selected SD item categories should be separated

with comma.

8. VAT_USE_LOCAL_CURRENCY Company codes can define one or two additional local






third local currency in JPK VAT structure. To activate

reading values for VAT from the second or third local

currency, the new parameter must be set respectively to 2

or 3.

9. FA_DELDATE_FROM_DELIVERY The delivery date is read from VAT date by default. If you

need to determine the delivery date from the delivery

document, activate this parameter. It causes the system to

derive the delivery date in the JPK FA structure from field

LIKP-WADAT_IST or VBRP-FBUDA (for many deliveries

or credit memos)

10. FA_ENTER_GROSS_VALUES When this parameter is set to X, fields P_9B and P_11A of

XML element ("FakturaWiersz") are populated with gross

values, price, and item total value respectively. WARNING!

Fields are populated only if the gross pricing procedure is

used to calculate invoice items.

11. FA_WARNING_AFTER_NIP_DELETE If option Inv. NIP Validation is activated with Check and

delete if error mode, the system validates the VAT ID

numbers (NIP) and displays an error if the VAT ID is

incorrect. This parameter changes the message type from

error to warning.




February 26, 2021



12. JPK_COMMGR_BUSPR_FROM_SD If the user decides to implement enhancement for Poland

delivered with the note 2903258 - Poland JPK VAT Sales

Process Enhancement - Collective Note, commodity

groups and business processes are elements of source

SD/FI invoices. Those elements are available in the sale,

billing, and financial document. The PLVAT addon can

collect that data when the Standard SD/FI/MM

determination method is enabled on the Company Code

level (see Supply Procedures and Services Groups

Determination). The addon default setting is to read data

from the FI document for all kinds of invoices; this

parameter causes the system to read the commodity

groups and business processes from SD billing documents

instead of FI documents. This parameter has no impact on

FI invoices.

The parameter JPK_COMMGR_BUSPR_FROM_SD is

relevant for VAT and FA (split payment area) structures.

13. KR_ALTERNATIVE_ACCOUNT This parameter switches the system to display the account

number and account description from the Alternative Chart

of Accounts, customized in the SAF-T Company Code

configuration, see Basic parameters

14. MAG_WZ_DELIV_REF_OVERWRIGHT Activating this parameter changes the way the delivery

reference number is read. With the parameter disabled,

the system reads data from the MKPF-XBLNR field; with

the parameter enabled, the system reads the data from the

MSEG-VBELN_IM field.

15. VAT_DELDATE_FROM_DELIVERY The VAT structure’s field “delivery date” is populated with

BKPF-VATDATE by default. This parameter switches the

logic to derive the delivery date from delivery document in

SD module, field LIKP-WADAT_IST. Alternatively, it reads

VBRP-FBUDA in case of many deliveries or credit memos.

16. VAT_DOCTYPE_CONVERT The PLVAT addon presents document types as IDs from

internal configuration; see Document types for categorizing

invoices. This parameter switches the system to display

the name of document type from XML element values (MK,

VAT_RR,WEW, RO, FP) instead of document type ID (1,

2, 3, 11, 12, 13) in the collected data of JPK VAT (4)

structure. If the user decides to use this functionality, If you

decide to use this functionality and you would like to export

data to Excel, make sure to maintain the same format in

order to be able to import it again.






February 26, 2021



17. VAT_DOCTYPE_FROM_REF The default setting in the PLVAT addon doesn’t allow you

to collect document types from reference fields; only

determination on tax code/FI document type combination

is possible. See Mapping Document Types. This

parameter causes the system to assign the document type

in the VAT structure by using the reference fields (one of

the determination method BSEG-XREF1, BSEG-XREF2,

BSEG-XREF3, BKPF-BKTXT have to be activated for

company code). Each document type ID (always two

digits) must be entered with a start delimiter, letter “D”, and

end delimiter (for example #D01#; #D11#, #D03#).

18. VAT_MPP_FROM_REF_CHECK For VAT structure it is possible to mark a split-payment-

relevant invoice with special code using reference fields.

The PLVAT addon doesn’t validate manual entries by

default. This parameter enables the validation of value

15.000, - PLN for split payment invoices recognized with

reference determination methods (BSEG-XREF1, BSEG-

XREF2, BSEG-XREF3, BKPF-BKTXT) in VAT structure

19. VAT_RENUMBER_ITEMS_TO_XML During XML creation, the system sorts all data from

different data sources. This can change the sequence

number of invoices. In case of any error, the program

creates an entry in the log with the new sequence number.

This means the sequence number from XML doesn’t

correspond to the sequence number presented when

displaying data source. This parameter causes the system

to renumber the items so that the order of invoices in the

data set is the same as the XML generated in real mode.

20. VAT_RENUMBER_ITEMS_TO_XML_TEST This parameter has the same functionality as per real

mode, but when it is set items will also be updated also

test runs. See the explanation for

VAT_RENUMBER_ITEMS_TO_XML.

21. WB_SORT_BY_STATMENT_DATE Activating the parameter changes the way the bank

statements are sorted in JPK WB. With this parameter

enabled, the system sorts bank statement and checks its

balances based on the statement date.

3.2.1.11 Definition of additional reports

The functionality of additional-user reports is a mechanism allows you to build separate blocks to manage collected

data. The reports are function modules that are built based on one fixed interface. The user can develop separate

function modules and run them from PLVAT cockpit transaction /PLVAT/JPK. Please use template function module

/PLVAT/JPK_REP_TEMPLATE to start separate developments. This function module should be copied to a new one

in the customer namespace. Two standard function modules:




February 26, 2021


• /PLVAT/JPK_REP_DISP_MULTI – display data from multiple data sources

• /PLVAT/JPK_REP_DISP_VTOTALS – display multiple totals from VAT structure

can be treated as examples of how you can prepare own function modules. Please remember to use authorizations

checks to keep data safe. Reports are available in the “Display mode” and “Data mode”; the current mode is passed

to the function module through its interface. The information about selected data sources is available through function

module interface. The following screen shows how to create a configuration entry.

Figure 20: Maintenance of additional reports

For new entries, remember to enter the translation of the report name into the Polish language. The next screen

shows how to enter a new translation. Please save the new entry before you start translation.

Figure 21: Report name translation

The report name will be visible in the menu on the toolbar of main screen of transaction /PLVAT/JPK.

Figure 22: Position of new reports in the toolbar




February 26, 2021


Accounting Books

Access this screen area using transaction SPRO under Financial Accounting (New) → Financial Accounting Global

Settings (New) → Tax on Sales/Purchases → Basic Settings → SAF-T PLVAT Poland Configuration → Accounting

books.

This screen area contains settings that are directly related to ‘JPK KR’ Accounting books.

Figure 23: Accounting Books

3.2.2.1 Off-Balance Sheet Accounts

With the operational chart of accounts, enter an account group that contains the off-balance-sheet accounts by

choosing Off-balance sheet account group. If your company doesn't use the whole off-balance-sheet group, enter

either the single off-balance-sheet account or the range of the off-balance-sheet accounts by choosing Off-balance

sheet accounts. Those accounts are assigned neither to the balance sheet nor to the income statement. On this

basis, the entry pozabilansowe is outputted in the JPK KR Accounting books in the section of ZOIS Trial balance in

the TypKonta field.

3.2.2.2 Account Group

3.2.2.2.1 Account Group Codes

The /PLVAT/JPKKKZ table is used for account group codes together with names for JPK KR Accounting books. An

account group code can have more than one character, but do not enter insignificant zeroes. The length of the

account in the chart of accounts is determined based on the entry in the table T004 field SAKLN Significant length of

the G/L account number. If the G/L account number contains digits only, the initial, insignificant part of the account

number is removed. In the next step, in the accounts qualification process, the code of the account group is selected

from the /PLVAT/JPKKKZ table so that it covers most of the initial characters of the G/L account (after removing the

insignificant digits). The entries contained in this table are transferred to and displayed in the JPK KR in the section of

the ZOIS Trial balance, in the KodZespolu Account group code and OpisZespołu Account group name fields.




February 26, 2021


Figure 24: Table /PLVAT/JPKKKZ

Note

The introduction of the entries in this table is mandatory. Each account of the chart of accounts must have

the account group code to which it can be assigned.

3.2.2.2.2 Account Categories

The /PLVAT/JPKKKK table is used for account category codes together with the names, within the individual account

groups defined in the previous step (in table /PLVAT/JPKKKZ). Category code can have more than one character.

The entries contained in this table are transferred to and displayed in the JPK KR, in the section of the ZOIS Trial

balance, in the KodKategorii Category code and OpisKategorii Category name fields. In the accounts qualification

process, the code of the category is selected from the table /PLVAT/JPKKKK, so that it covers most of the initial

characters of the account remaining after the removal of digits covered by the account group code.

Figure 25: Table /PLVAT/JPKKKK




February 26, 2021


Note

The introduction of the entries in this table is mandatory. Each account of the chart of accounts must have

the category code, to which it can be assigned.

3.2.2.2.3 Account Subcategories

The /PLVAT/JPKKKP table is used to introduce codes of subcategories of accounts along with the names, within the

individual account categories defined in the previous step (in table /PLVAT/JPKKKK). Subcategory code can have

more than one character. The entries contained in this table are transferred to and displayed in the JPK KR in the

section of the ZOIS Trial balance, in the KodPodkategorii Subcategory code and OpisPodkategorii Subcategory

name fields. In the accounts qualification process, the code of the subcategory is selected from the table

/PLVAT/JPKKKP, so that it covers most of the initial characters of the account remaining after the removal of digits

covered by the account category code.

Figure 26: Table /PLVAT/JPKKKP

Note

The introduction of the entries in this table is optional.

Warehouse

You access this screen area by using transaction SPRO under Financial Accounting (New) →Financial Accounting

Global Settings (New) →Tax on Sales/Purchases →Basic Settings → SAF-T PLVAT Poland Configuration →

Warehouse.

This screen area contains settings that are directly related to ‘JPK MAG’ Warehouse.




February 26, 2021


3.2.3.1 Types of Material Movement Documents

The /PLVAT/JPKMTYR table is delivered with content, which must be verified and completed with specific settings of

your system. Assign the types of material movement documents, which are required in JPK MAG Warehouse, to the

combination of the following parameters:

• Movement type

• Movement indicator

• Special stock Indicator

• Receipt indicator

• Consumption posting

• Item created automatically

• Item category in purchasing document

• Type of warehouse

Each item of the material movement document is qualified as PZ (external good receipts), WZ (external good

issues), RW (internal good issues) or MM (warehouse movements), depending on the assignment read from this

table.

Note

If the entry in the configuration table should apply to all possible values for some of the parameters

mentioned above, leave this field empty. The system reads the value of the given parameter from the

material document item (MSEG table) and then tries to find the entry with this value in the configuration

table. If the system doesn't find this entry, it continues the search for a line without an entry for this

parameter. If the system doesn't find the row in the configuration table, an error message is sent to the

extraction log.

Value-Added Tax (VAT) Register


Global Settings (New) →Tax on Sales/Purchases →Basic Settings → SAF-T PLVAT Poland Configuration → VAT

Register.

This screen area contains settings that are directly related to JPK VAT – Value-Added Tax Register.

Figure 27: VAT Register




February 26, 2021


3.2.4.1 VAT Purchase Classifiers

The /PLVAT/JPKVZK table is delivered with content. This table includes the classifiers corresponding to various

types of purchase and input tax.

VAT Purchase Classifiers are XML version dependent.

Figure 28: VAT Purchase Classifiers

Note

As of version 4, the following configuration for classifiers has been added:

• Reference Tax Classifier, which allows you to assign a tax code only for one classifier (base

amount) and calculate the tax amount based on this classifier (for example, if the tax code is

assigned to the K_40 classifier, and K_40 is the reference classifier for K_41, the system calculates

the value for K_41 automatically based on the configuration for K_40);

• Type of Classifier Amount, where you choose between the Base amount or Tax Amount;

• Change Sign of the Amount, where you choose whether the sign of the amount collected for a

specified classifier is to be changed or left unchanged.

The above configuration has no effect in versions 1 to 3 of the JPK VAT; for these versions' classifier properties

are embedded in the program and are non-configurable.

3.2.4.2 VAT Sales Classifiers

The /PLVAT/JPKVSK table is delivered with content. The table includes the classifiers corresponding to various

types of sales and appropriate tax rates. The names of the classifiers are taken from the Polish VAT Act (“Ustawa z

dnia 11 marca 2004 r. o podatku od towarów i usług Dz.U. 2004 nr 54 poz. 535 z późniejszymi zmianami) and

contain references to specific clauses in the Act.




February 26, 2021


VAT Sales Classifiers are XML version dependent.

Figure 29: VAT Sales Classifiers

Note

As of version 4, the following configuration for classifiers has been added:

• Reference Tax Classifier, which allows you to assign a tax code only for one classifier (base

amount) and calculate the tax amount based on this classifier (for example, if the tax code is

assigned to the K_40 classifier, and K_40 is the reference classifier for K_41, the system calculates

the value for K_41 automatically based on the configuration for K_40);

• Type of Classifier Amount, where you choose between the Base amount or Tax Amount;

• Change Sign of the Amount, where you choose whether the sign of the amount collected for a

specified classifier is to be changed or left unchanged.

The above configuration has no effect in versions 1 to 3 of the JPK VAT, for these versions classifier properties are

embedded in the program and are non-configurable.

3.2.4.3 Document types for categorizing invoices

The /PLVAT/JPKTYD table is delivered with content. This table includes the document types for categorization of

sales and purchase invoices. Each document type has a unique ID in the system connected with designation in the

XSD schema. This ID is used in configuration (refer to chapter 3.2.4.6.4).

Document types are XML version dependent.




February 26, 2021


Figure 30: Table /PLVAT/JPKTYD

Note


3.2.4.4 Supply and services groups for categorizing

invoices

The /PLVAT/JPKGRM table is delivered with content. This table includes supply procedures and services groups,

which allow you to categorize documents connected with the output tax in the JPK VAT structure. Each group has a

unique ID in the system connected with the designation in the XSD schema. This ID is used in configuration (refer to

chapter 3.2.4.6.5 and 3.2.4.6.6).

Supply procedures and services groups are XML-version-dependent.

Figure 31: Table /PLVAT/JPKGRM




February 26, 2021


Note


3.2.4.5 Supply Procedures and Services Groups

Determination


Global Settings (New) →Tax on Sales/Purchases →Basic Settings → SAF-T PLVAT Poland Configuration→ VAT

Register→ Supply Procedures and Services Groups Determination

You can also enter the transaction code /N/PLVAT/JPK0 in the command field.

This area allows you to configure methods used by the system to determine supply procedures and services group

related to an individual Company code.

Figure 32: Determination Methods

Multiple selection from the following methods is possible:

• Material numbers – when this method is activated, if the material number indicated in the configuration is found

in a document (reported in the JPK VAT (4) structure), the system marks this document as related to the

specified Supply Procedures and Services Group. For details about assigning material numbers to groups refer

to chapter 3.2.4.6.5.

• CN codes – when this method is activated, if the material with CN code indicated in the configuration is found in

a document (reported in the JPK VAT (4) structure), the system marks this document as related to the specified

Supply Procedures and Services Group. For details about assigning CN codes to groups refer to chapter

3.2.4.6.5.




February 26, 2021


• Material groups – when this method is activated, if the material with material group indicated in the configuration

is found in a document (reported in the JPK VAT (4) structure), the system marks this document as related to

the specified Supply Procedures and Services Group. For details about assigning Material groups to groups

refer to chapter 3.2.4.6.5.

• PKWiU codes – when this method is activated, if the material with PKWiU code indicated in the configuration is

found in a document (reported in the JPK VAT (4) structure), the system marks this document as related to the

specified Supply Procedures and Services Group. For details about assigning PKWiU codes to groups refer to

chapter 3.2.4.6.5.

• SD and/or FI document type and/or tax code – when this method is activated, the system marks documents as

related to the specified Supply Procedures and Services Group in JPK VAT (4) structure based on the billing

type, financial document type, tax code or combination of these indicators. For details about assigning

document types and tax codes to groups, refer to chapter 3.2.4.6.6.

• Split payment method determination – when this method is activated, the system marks documents as split-

payment-relevant in JPK VAT (4) structure based on the customizing in Basic Parameters. For details refer to

chapter 3.2.1.1.1.

• Read codes from BSEG-XREF1 – when this method is activated, if the document includes the Supply

Procedures and Services Group IDs in the field BSEG-XREF1, the system marks this document as related to

the specified Supply Procedures and Services Group in the JPK VAT (4) structure. Each Supply Procedures

and Services Group ID must be entered with a start and end delimiter (for example #11##23##52#). The default

delimiter is #. This delimiter can be changed by activating VAT_GROUP_SEPARATOR parameter. For more

details about the parameters, please refer to chapter 3.2.1.9.




and Services Group ID must be entered with a start and end delimiter (for example #11##23##52#). The default






and Services Group IDs must be entered with a start and end delimiter (for example #11##23##52#). The

default delimiter is #. This delimiter can be changed by activating VAT_GROUP_SEPARATOR parameter. For

more details about the parameters, please refer to chapter 3.2.1.9.

• Read codes from BKPF-BKTXT – when this method is activated, if the document includes the Supply

Procedures and Services Group IDs in the field BKPF-BKTXT, the system marks this document as related to the

specified Supply Procedures and Services Group in the JPK VAT (4) structure. Each Supply Procedures and

Services Group IDs must be entered with a start and end delimiter (for example #11##23##52#). The default



• Trading partner – when this method is activated, if the document includes the Trading partner in the field BSEG-

VBUND, the system marks this document as related to the “TP” procedure (Existing relation between the

purchaser and the provider of goods or services, referred to in Article 32 Section 2 point 1 of the Act) in the JPK

VAT (4) structure.

• Standard SD/FI/MM – when this method is activated, the system marks documents as related to the specified

Supply Procedures and Services Group in JPK VAT (4) structure based on the business process

(procedural/transaction types) and commodity groups (delivery of goods and provision of services groups)

indicators and indicators stored in FI/SD documents. For more details about the business process indicators and




February 26, 2021


commodity group indicators stored in the FI/SD documents, please refer to the note “2903258 - Poland JPK

VAT Sales Process Enhancement - Collective Note”.

• User routine – when this method is activated, the system will allow to use custom method to mark documents as

related to the specified Supply Procedures and Services Group in the JPK VAT (4) structure. Custom method

can be implemented in dedicated enhancement point:

enhancement-point /plvat/jpk04_spsgroups spots /plvat/jpk04_grp

3.2.4.6 VAT register configuration of parameters

depending on the XML version


Global Settings (New) →Tax on Sales/Purchases →Basic Settings → SAF-T PLVAT Poland Configuration→ VAT

Register→ VAT register configuration of parameters depending on the XML version

You can also enter the transaction code /N/PLVAT/JPK0 in the command field. This area allows you to assign the

tax codes to VAT classifiers, exclude tax codes, configure the mapping of document types and Supply Procedures

and Services Groups related to an individual Company code for specified XML version.

Figure 33: VAT Versions

Caution

You can copy the assignment of classifiers from VAT version 3 to VAT version 4.

But please be careful as the numbering of the classifiers have been changed in VAT version 4 (for example,

classifier K_36 in version 3 changed into K_33 in version 4).




February 26, 2021


3.2.4.6.1 VAT Purchases - Assignment of VAT Classifiers

To assign VAT classifiers to tax codes, select the XML version.

Figure 34: Table /PLVAT/JPKVVERV4

Next choose the catalog VAT Purchases –Assignment of VAT codes, enter the tax procedure and assign VAT

classifiers for the combination of tax code and document type in the /PLVAT/JPKVZKK table:

Figure 35: Table /PLVAT/JPKVZKK

Note

Net and VAT amounts are accumulated within the individual accounting documents according to the VAT

type (input/output), and the VAT classifier is read from this table based on the combination of tax code and

document type. If the combination is not found, the system repeats the search for the line with the VAT code

but with no document type.

3.2.4.6.2 VAT Sales - Assignment of VAT Classifiers





February 26, 2021


Then choose the catalog VAT Sales –Assignment of VAT codes, enter the tax procedure and assign VAT classifiers

for the combination of tax code and document type in the /PLVAT/JPKVSKK table:

Figure 36: Table /PLVAT/JPKVSKK

Note

Net and VAT amounts are accumulated within the individual accounting documents according to the VAT

type (input / output) and the VAT classifier is read from this table based on the combination of tax code and

document type. If the combination is not found, the system repeats the search for the line with the VAT code

but with no document type.

3.2.4.6.3 Excluded VAT codes


Then choose the Excluded VAT Codes catalog, enter the tax procedure, and specify the tax code in the

/PLVAT/JPKVEXCL table:

Figure 37: Table /PLVAT/JPKVEXCL

Items posted with VAT codes contained in the /PLVAT/JPKVEXCL table are excluded from JPK VAT even if the tax

codes are assigned to VAT classifiers. Items posted with tax codes not assigned to any VAT classifier are reported as




February 26, 2021


errors only if they are not contained in this table. Enter tax codes for input and output tax in this table. You can limit

the exclusion to the sales or purchase part of the JPK structure. Enter a tax code into the table and select the

checkbox to switch off the exclusion for the specified part of the JPK structure (sales or purchase side).

3.2.4.6.4 Mapping Document Types

To configure the mapping for document types, select the XML version and choose the Mapping document Types

catalog.

Then enter Company code, select invoice type (Sale or Purchase), and assign the document type ID to the financial

document type, tax code or combination of both.

For list of document type ID refer to chapter 3.2.4.3.

Figure 38: Mapping document types

3.2.4.6.5 Supply procedures and services mapping using

materials

To configure the mapping for Supply procedures and services groups based on Material numbers, CN codes,

Material Groups, and PKWiU codes, select the XML version and choose the Supply procedures and services

mapping using materials catalog. Then enter a company code, select invoice type (Sale or Purchase), select

procedure (determination method), and assign the Supply procedures and services groups ID to the selected values.

In addition, you can specify the validity dates for this assignment by filling the fields From date and To date (two dates

are always are required).

For list of Supply procedures and services group IDs refer to chapter 3.2.4.4. You can select or exclude specified

values (SIGN column) and choose from many available operators likelike, for example, equal, between, greater than

(Option column).

Figure 39: Mapping groups using materials




February 26, 2021


If the combination of Company code, Invoice type, Supply procedures and services groups ID and Procedure has to

be used more than once, the numbering for a line with repeating combination must be maintained. The consecutive

number should be entered in the Number column.

Figure 40: Numbering for repeated combination

3.2.4.6.6 Supply procedures and services with document

types and tax codes

To configure the mapping for Supply procedures and services groups based on the billing type, financial document

type, tax code, select the XML version and choose the Supply procedures and services with document types and tax

codes catalog. Then enter Company code, select invoice type (Sale or Purchase), and assign the Supply procedures

and services groups ID to the billing type, financial document type, tax code or combination of these indicators. In

addition, you can specify the validity dates for this assignment by filling the fields From date and To date (two dates

are always required).

For list of Supply procedures and services group IDs refer to chapter 3.2.4.4.

Figure 41: Mapping groups using document types and tax codes

If the combination of Company code, Invoice type, Supply procedures and services groups ID has to be used more

than once, the numbering for a line with repeating combination must be maintained. The consecutive number should

be entered in the Number column.




February 26, 2021


3.2.4.7 VAT Declaration Definition

The /PLVAT/JPKVDEK table is delivered with content. This table includes the definition, properties, calculation

formula, and validation formula for every field in the VAT-7 declaration (part of a JPK VAT (4) structure).

VAT declaration definition is XML version dependent.

Figure 42: VAT Declaration Definition

3.2.4.7.1 Creation of formula

You can use values from declaration (P_01…P_68) and values of classifiers from data sources. When crating

calculation formula or validation formula, value of needed parameter must be enclosed in square brackets. In case of

classifiers single parameter always represents total value from all data sources.

• Example: [P_01] + [P_02] means sum of declaration values P_01 and P_02

• Example: [K_10] means the system will evaluate total value of K_10 classifier from all records

Single field for formula can contain multiple expressions separated by ‘|’ sign and result from previous expression can

be use in the following one. Previous result is represented by {RES} expression.

The following are permitted:

• arithmetic formulas

• logical formulas (with result TRUE or FALSE)

• conditions of the form IF <logical expression> THEN <arithmetic formula>ELSE<arithmetic formula>

• expressions with fields of structure SY

Operators

• AND logical AND

• OR logical OR




February 26, 2021


• = equals

• <>, >< not equal to

• < less than

• > greater than

• <=, =< less than or equal to

• =>, >= greater than or equal to

• + positive value (of an expression)

• - negative value (of an expression)

• + addition

• - subtraction

• * multiplication

• / division

• ** exponential

• ABS absolute value

• NOT negation (of a logical expression)

Note

Changes to the contents of this table are not recommended. In exceptional cases, if it is necessary to

change the properties of a field from Read-Only to Normal, please remember to delete the calculation

formula for this field.

Invoices


Global Settings (New) →Tax on Sales/Purchases →Basic Settings → SAF-T PLVAT Poland Configuration →

Invoices.

This screen area contains settings that are directly related to JPK FA Invoices.

Figure 43: Invoice Parameters




February 26, 2021


3.2.5.1 Excluded Document Types and Tax Codes

In the /PLVAT/JPKVTEC table, enter the VAT codes for output tax. The documents from the JPK FA structure can be

disabled by configuring a document type, VAT tax code, or a combination of both. If all the items of the document

include only the VAT codes contained in this table or do not have any VAT code, the document doesn't appear in the

JPK FA Invoices.

Figure 44: Table /PLVAT/JPKVTEC

3.2.5.2 EU VAT Tax Codes

In the /PLVAT/JPKVUE table, enter the VAT codes for output tax. If the document includes items posted with the

VAT codes contained in this table, the fields ‘P_4A’ (VAT EU code (prefix) of taxpayer) and ‘P_5A’ (VAT EU code

(prefix) of purchaser), contained the JPK FA Invoices in the section 'Faktura’ (Invoice), are filled in.

Note

Entries in this table also influence the JPK VAT structure, because the tax codes contained in the table are

used for determining the correct VAT ID number (NIP) in the JPK VAT XML file.

3.2.5.3 Exempt VAT Codes

In the /PLVAT/JPKVZW table, enter the VAT codes for output tax. Items posted with VAT codes contained in this

table are shown in the 'Faktura’ (Invoice) section of the JPK FA Invoices, with value in the field 'P_13_7' 'Total value

of sales exempt'.




February 26, 2021


3.2.5.4 Reverse Charge VAT Tax Codes

In the /PLVAT/JPKVOO table, enter the VAT codes for output tax. Documents posted with VAT codes contained in

this table are shown in the Faktura (Invoice) section of the JPK FA Invoices with the attribute 'true' in the 'P_18' field

and the values in the fields 'P_13_4” and “P_14_4”. Such invoices refer to the supply of goods or services, for which

the purchaser has the tax obligation.

3.2.5.5 Non-Taxable VAT Tax Codes

In the /PLVAT/JPKVNT table, enter the VAT codes for output tax. Documents posted with VAT codes contained in

this table are shown in the Faktura (Invoice) section of the JPK FA Invoices, with the values in the fields 'P_13_5” and

“P_14_5”. Such invoices refer to the non-taxable transactions.

3.2.5.6 VAT Tax Reporting Codes

The /PLVAT/JPKVRST table is delivered with the following content:

Figure 45: Table /PLVAT/JPKVRST

There are five VAT tax reporting codes provided in the structure of the JPK FA Invoices, the last of which is a reserve

code. So, this table contains four tax reporting codes only. If another reduced rate is introduced by tax authority, add

an appropriate entry into this table.

3.2.5.7 VAT Tax Rates Values and Validity

The /PLVAT/JPKV_ST table is delivered with the following content. This table contains the values for different types

of VAT tax reporting codes. Entries here are time dependent. If the value of the individual VAT tax reporting code

changes, limit the validity of the existing entries and enter the new, valid-from date corresponding to the date of the

beginning of validity of new values.




February 26, 2021


Figure 46: Table /PLVAT/JPKV_ST

3.3 Additional configuration for DP&P functionality

The following additional configuration is required in order to support Data Protection and Privacy functionality. For

more information on DP&P requirements, see 5.4 Data Protection & Privacy.

Note

Configuration is valid only on the system where the function for simplified deletion of personal data of SAP

NetWeaver Information Lifecycle Management is activated and customized. This option is available from SAP

ERP 6.0 EHP7 support package 5.

a. Start SM30 transaction and enter the V_APPL_CODE_MASK view.

Figure 47: Transaction SM30




February 26, 2021


b. Add code PLVT.

Figure 48: Maintenance View PLVT

c. Enter view V_DPP_MASK_RSTRC.

Figure 49: View V_DPP_MASK_RSTRC

d. Add entries.

Table/Structure Field

Name

Data Element Appl.

Code /PLVAT/JPKDTAREP ADDRESS /PLVAT/JPK_ADR PLVT

/PLVAT/JPKDTAREP NAME /PLVAT/JPK_NAME PLVT

/PLVAT/JPKFFA P_3A /PLVAT/JPK_P3A PLVT

/PLVAT/JPKFFA P_3B /PLVAT/JPK_P3B PLVT

/PLVAT/JPKFFA P_5B /PLVAT/JPK_P5B PLVT

/PLVAT/JPKVS ADRNAB /PLVAT/JPK_ADRNAB PLVT

/PLVAT/JPKVS NAZNAB /PLVAT/JPK_NAZNAB PLVT

/PLVAT/JPKVZ ADRWYS /PLVAT/JPK_ADRWYS PLVT

/PLVAT/JPKVZ NAZWYS /PLVAT/JPK_NAZWYS PLVT




February 26, 2021


/PLVAT/JPKFRR P_1A /PLVAT/JPK_R1A PLVT

/PLVAT/JPKFRR P_1B /PLVAT/JPK_R1B PLVT

/PLVAT/JPKFRR P_1C /PLVAT/JPK_R1C PLVT

/PLVAT/JPKFRR P_1D /PLVAT/JPK_R1D PLVT

/PLVAT/JPKFRR P_2A /PLVAT/JPK_R2A PLVT

/PLVAT/JPKFRR P_2B /PLVAT/JPK_R2B PLVT

/PLVAT/JPKFRRD P_1A2 /PLVAT/JPK_R1A PLVT

/PLVAT/JPKFRRD P_1B2 /PLVAT/JPK_R1B PLVT

/PLVAT/JPKFRRD P_1C2 /PLVAT/JPK_R1C PLVT

/PLVAT/JPKFRRD P_1D2 /PLVAT/JPK_R1D PLVT

/PLVAT/JPKFRRD P_2A2 /PLVAT/JPK_R2A PLVT

/PLVAT/JPKFRRD P_2B2 /PLVAT/JPK_R2B PLVT




February 26, 2021


4 Installation and Configuration

Information for Desktop Application

eTransfer

4.1 Workstation Preparation

Basic preparation of the environment requires administrative authorizations on the workstation.

Before installing the dispatch application, install Java Runtime Environment version 8 on the workstation (available on

http://java.oracle.com).

Note

Please pay attention to the version number. Java Runtime Environment version 9 or newer may not work

correctly due to major changes in specification.

Make sure that your corporate network allows Internet connectivity for dispatch application. It is common practice to

block applications for security reasons. In that case contact your network administrator.

Note

To use the software, you need a certified card reader (for example, from Unizeto or CryptoTech) and a card

with a qualified certificate (for example, Certum or SigillumSign). Register the certificate in the system of the

Ministry of Finance using UPL‑1 form, according to the instructions of the Ministry of Finance.

4.2 Workstation Installation

Before you create a local installation, create a destination folder (for example, C:\Program Files\eTransfer), and give

full permissions to the folder and subfolders of the dispatch application to the users. The permissions for creating,

changing, and deleting files are required to run the application.

During the installation, unpack the delivered archive file eTransfer.zip to the destination folder (for example,

C:\Program Files\eTransfer).

Note

New version of the application provides native Windows launchers for running application in normal or test

mode. New executable files are named respectively: etransfer.exe and test-etransfer.exe

http://java.oracle.com/




February 26, 2021


4.3 Network Installation

If a network path was selected for the installation (accessible through a mapped drive letter, for example,

X:\Path\eTransfer, or a UNC path, for example, \\SERVER\path\eTransfer), create a network folder and give full

permissions to that folder and subfolders (creating, modifying, deleting files) to all end-users of the dispatch

application.

Note

The application can be run only once at the same time. If more workstations are set for dispatching, we

recommend to install a separate local installation on each of them.

4.4 Starting the Application

Launch the application using the etransfer.exe file.

4.5 Application Configuration

Configuration in Application

The application allows you to configure parameters from a graphical interface. To go to the configuration interface, on

the main eTransfer screen, choose Configuration. The following window with all configuration parameters appears:




February 26, 2021


Figure 50: Configuration Parameters

For each parameter, a tooltip is available. For more information about the parameters, see also chapter 4.5.2. You

can leave parameter fields empty. If you leave a configuration parameter empty, the application uses the default

value for that parameter. After changing the parameters, choose Ok to enter your values in the application.

Configuration Parameters

The standard configuration of the electronic dispatch module is done via the application configuration GUI (see

chapter 4.5.1). You can also change parameters in the configuration.properties file located in the installation folder.

By default, the application saves all data under the root folder of the installation. You can change the default path and

set it to a custom path pointing to a directory of your choice inside the application. Configure access to the Internet if

you use a proxy server.

Note

You can check this in the browser settings, or you can ask your IT department).

The format of the file with the application settings (default configuration.properties) requires the use of the "\"

(backslash) before any special character (for example, "\\", "\:" "\|").




February 26, 2021


Application

Parameter

Default Value Explanation

ask_for_pin false Parameter specifying whether the application should ask for a

PIN (usually true in DLL mode and false in Windows mode)

crl_url <empty by default> URL for checking whether certificate was revoked – if this is

empty, the application tries to find the URL in the certificate.

crl_check false Turns a qualified certificate validation on or off

proxy_host <empty by default> Host name or IP number of the proxy server if the internet

connection is not direct

proxy_port <empty by default> Proxy server port number

proxy_domain <empty by default> Domain name of the proxy server if the internet connection is

not direct

If a domain is defined, on the application logon screen, the

User field should be filled only with the user name, without the

domain name – for example <user_name> (user1234) is

correct, but <domain_name>/<user_name>

(domena1234/user1234) is incorrect.

proxy_logon false Parameter specifying whether the proxy server must be

authenticated (true or false)

dll_mode false The certificate can either be stored on a card or installed locally

in the operating system. When the dll_mode parameter is set

to false, it is assumed that the certificate is stored on a card,

and the card reader is used to read it. When the dll_mode

parameter is set to true, the application can use any certificate

installed in the operating system (the certificate must be

installed correctly, and the user must have the required

permissions to access it).

archive_files false Parameter specifying whether the declarations should be

archived locally

collection_mod

e

false Sets application dispatch mode: collection_mode=true sets

collection mode (all JPK files are send in single session),

collection_mode=false sets single mode (each JPK file is send

in single session)

web_jpk_servi

ce

https\://e-

dokumenty.mf.gov.pl

URL address of the web service of the productive eTransfer of

the Ministry of Finance

test_web_jpk_

service

https\://test-e-

dokumenty.mf.gov.pl

URL address of the web service of the test eTransfer of the

Ministry of Finance

log_file_path <path_to_application>\\etra

nsfer.log

Path to the system file containing the error log

archive_jpk_dir

ectory

<path_to_application>\\jpk

_xml_archive

Archive folder (local) of sent declarations




February 26, 2021


Application

Parameter


upo_archive_

dir

<path_to_application>\\upo

_archive

Archive folder (local) of UPO confirmations

synch_director

y

<path_to_application>\\sap

_synch

Default synchronization folder (this parameter saves the last

path, used during synchronization)

publickey_path

_prod

<path_to_application>\\enc

rypt\\public.pem

Path to public key that is used for encrypting the secret key for

production dispatching SAF-T files (in production mode)

publickey_path

_test

<path_to_application>\\enc

rypt\\public_test.pem

Path to public key that is used for encrypting secret key for

testing dispatching SAF-T files (in test mode)

smart_card_lib c\:\\windows\\system32\\cry

ptoCertum3PKCS.dll

Certificate driver path if DLL mode is active (in case of using

two different certificates)

xml_jpk_direct

ory

<path_to_application>\\jpk

_xml

The default folder of the declarations to be sent (this parameter

saves the last path, mentioned during dispatch)

url_schema_va

t

https://www.gov.pl/docume

nts/2034621/2182793/Sch

emat_JPK_VAT(3)_v1-

1.xsd

Default base URL for XSD schema JPK_VAT

url_schema_v7

m

https://www.gov.pl/attachm

ent/d21ef656-8faa-4384-

a960-a11895ce4a2a

Default base URL for XSD schema JPK_V7M

url_schema_kr http://www.mf.gov.pl/docu

ments/764034/5134536/Sc

hemat_JPK_KR(1)_v1-

0.xsd

Default base URL for XSD schema JPK_KR

url_schema_w

b

http://www.mf.gov.pl/docu

ments/764034/5134536/Sc

hemat_JPK_WB(1)_v1-

0.xsd

Default base URL for XSD schema JPK_WB

url_schema_m

ag


ments/764034/5134536/Sc

hemat_JPK_MAG(1)_v1-

0.xsd

Default base URL for XSD schema JPK_MAG

url_schema_fa https://www.gov.pl/attachm

ent/1abeab45-4e71-4616-

b8d5-6b71699e86f8

Default base URL for XSD schema JPK_FA

url_schema_pk

pir


ments/764034/5134536/Sc

hemat_JPK_PKPIR(2)_v1-

0.xsd

Default base URL for XSD schema JPK_PKPIR




February 26, 2021


Application

Parameter


url_schema_e

wp


ments/764034/5134536/Sc

hemat_JPK_EWP_v1-

0.xsd

Default base URL for XSD schema JPK_EWP

url_schema_fa

_rr

https://www.gov.pl/attachm

ent/07315f76-eb8d-4273-

8256-738ed0a1f223

Default base URL for XSD schema JPK_FA_RR

language <empty by default> Language of application GUI (en or pl)

check_web_se

rvice_certificat

e

true Checking validity of the certificate

trusted_authori

ty

true Verify that the certificate has been issued by a trusted

certification authority

Electronic Signature Configuration

To enable the application to sign the XML request using a certificate, register it in the Windows repository. For this

purpose, the software included with your certified signature card is provided.

To check whether the certificate has been successfully registered, in Microsoft Internet Explorer, choose Tools ->

Internet Options. On the Content tab page, choose Certificates.

In case of problems with the electronic certificate in Windows mode dll_mode=false (for example, no sufficient local

system rights), you can configure application in the direct driver (DLL) mode (dll_mode=true). In this case, configure

the path to the driver library file (DLL).

4.6 Testing

Testing Connection

Before shipping the JPK application, you can test the connection, checking the availability of the Ministry of Finance

servers or detect potential problems with internet connections. You can test connections by choosing Test

Connection on the main screen. After conducting the test, the system displays a success or error message.

Note

It may happen that the connection test is successful but no files are sent. In that case contact your network

administrator to check network configuration, proxy settings, firewall, and antivirus software settings.




February 26, 2021


Starting Application in Test Mode

When you start the application using the test-etransfer.exe file, you can test the dispatch with the use of the

eTransfer test web service of the Ministry of Finance (available under https://test-e-dokumenty.mf.gov.pl). The

application starts in test mode, which you can see by the window title eTransfer – TEST MODE (eTransfer – TRYB

TESTOWY).

Figure 51: eTransfer Test Mode

In test mode, there is no risk that the dispatched files reach the Tax Office. The test web service returns the UPO

files, for each properly sent SAF-T files. SAF-T files receive the status 200 if they are properly encrypted and sent

and the request XML (opens sending session and contains detailed information about the files that are sent) was

properly signed. Otherwise, the web service returns another status (from 401 to 415).

4.7 Languages

The application is available in the English and Polish languages.

When you run the application for the first time or if you have never switched the language manually, the language is

determined based on the language of your Windows installation:

• If you run Windows in Polish, the application automatically starts in Polish.

• If you run Windows in any other, the application automatically starts in English.

https://test-e-dokumenty.mf.gov.pl/




February 26, 2021


To switch the language, you may use the Change Language button located in the main window of the application.

Clicking it opens a dialog window with language selection.

Figure 52: eTransfer Languages




February 26, 2021


5 Security Information

For information about specific security-related topics, see the following resources on SAP Service Marketplace or

SDN:

Topic Quick Link on SAP Service Marketplace or SDN

Security http://service.sap.com/security

http://sdn.sap.com/irj/sdn/security

Platforms http://service.sap.com/platforms

Infrastructure http://service.sap.com/securityguide

→ Infrastructure Security

Related SAP Notes http://service.sap.com/notes

http://service.sap.com/securitynotes

SAP NetWeaver http://sdn.sap.com/irj/sdn/netweaver

For a complete list of available SAP Security Guides, see SAP Service Marketplace at

http://service.sap.com/securityguide.

5.1 Authorization Concept

Roles

In SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0, there are no predefined roles.

Authorization Objects

The following table lists the security-relevant authorization objects that are used by SAP ERP, add-on for Polish SAF-

T regulatory requirements 1.0.

Authorization Object Field Value Description

/PLVAT/J0 (JPK

configuration authority)

ACTVT 23 - Maintain Maintain JPK

configuration

http://service.sap.com/security

http://sdn.sap.com/irj/sdn/security

http://service.sap.com/platforms

http://service.sap.com/securityguide

http://service.sap.com/notes

http://service.sap.com/securitynotes

http://sdn.sap.com/irj/sdn/netweaver

http://service.sap.com/securityguides




February 26, 2021



/PLVAT/J1 (JPK access

to transaction modes)

BUKRS - Company

Code

Company Code Activity authorizations

/PLVAT/J1 ACTVT - Activity 01

02

03

06

07

24

V3

A5

O5

01 - Create, add

02 - Change

03 - Display

06 - Delete

07 - Activate, generate

24 - Archive

V3 - Display version

A5 – Display reports

O5 – Display DPP rep.


/PLVAT/J2 (JPK types

authorization)

BUKRS - Company

Code

Company Code Permissions for the

types of JPK

/PLVAT/J2 /PLVAT/JP - JPK type 01

02

03

04

05

01 - KR

02 - WB

03 - MM

04 - VAT

05 - FA

/PLVAT/J2 ACTVT - Activity 40

41

12

43

48

A5

A9

74

83

40 - Creating in the

database

41 - Removing from the

database

12 - Data modification

and creation of change

documents

43 - Release data to

send (approve)

48 - Simulation

A5 - Displaying data in

test mode

A9 - Sending XML file

74 – Cancel approval

83 – Upload

confirmation




February 26, 2021


Standard Authorization Objects


S_BTCH_ADM (Manage

background processing)

BTCADMIN Y Y - Running jobs in

background

S_GUI (Activities with

reference to GUI

objects)

ACTVT - Activity 02

04

60

61

02 - Change

04 - Print

60 - Upload - load data

into the system

61 - Export - save lists

displayed on the screen

in local files

S_DATASET (Accessing

files from ABAP/4

programs)

ACTVT - Activity 01

03

01 - Create/add XML

files

03 - Display XML files

S_DATASET(Accessing

files from ABAP/4

programs)

OBJTYPE DEBUG DEBUG - Debugging

S_APPL_LOG

(Application log*)

ALG_OBJECT /PLVAT/JPK Object name

S_APPL_LOG

(Application log*)

ALG_SUBOBJ DATA01

DATA02

DATA03

DATA04

DATA05

DATA01 - KR

DATA02 - WB

DATA03 - MM

DATA04 - VAT

DATA05 - FA

S_APPL_LOG

(Application log*)

ACTVT - Activity 03 03 - Display

S_ALV_LAYO (Global

default layouts of the

ALV*)

ACTVT - Activity 23 23 - Maintain

S_NUMBER (Number

range management)

ACTVT - Activity 02

03

11

02 - Change

03 - Display

11 - Change the status

of a range of numbers

S_TCODE (Check

authorizations for

starting the transactions)

TCD /PLVAT/JPK

/PLVAT/JPK0

/PLVAT/JPK - Kreator

JPK

/PLVAT/JPK0 - Kreator

JPK configuration




February 26, 2021


Note

Authorization objects marked with an asterisk (*) are required for all users.

5.2 Preparation and Sending of SAF-T Data (Java)

SAF-T data are prepared on the client side (for example, ERP system) in the form of XML files conforming to the XSD

schema published by the Ministry of Finance on https://www.podatki.gov.pl/jednolity-plik-kontrolny/ in the Structures

of SAF-T block. Each of the documents described wiring diagram is to be a separate XML file. The generated XML

file must be encoded in UTF-8.

Preparation of SAF-T Documents

SAF-T generated documents are compressed files in ZIP format and binary divided into pieces so the size does not

exceed 60 MB. You should expect a high compression ratio so the scenario that there is more than one part is

relatively rare.

The required compression method is ZIP file format using the DEFLATE algorithm, without the option of sharing (split

/ multipart). As a result of compression, create one ZIP file containing a single document SAF-T. If the size of the

resulting ZIP file exceeds 60MB, divide the binary number into the corresponding parts of the size of 60MB each, and

the last part with a size no larger than 60MB.

This approach, on the one hand provides the use of known and commonly used tools, and ease of implementation on

different platforms, the other - the efficiency, in particular the compressive operation and simplicity of the API for

these operations.

Encryption of SAF-T Data

Compressed files are encrypted. Encrypted files use the AES256 algorithm with the key generated on the client side.

The implementation of encryption uses the following specifications of AES:

Key Size 256 bits / 32 bytes

Cipher Mode CBC (Chain Block Chaining)

Padding PKCS#7

Block Size 16 bytes

The algorithm encryption process is as follows:

• The client generates a random 256-bit key.

• The generated encrypted keys are all part of the compressed archive (in accordance with paragraph. 1.1) -

AES256 encryption algorithm is.




February 26, 2021


• The encryption key is encrypted using the asymmetric RSA algorithm, using the public key certificate provided

by the Ministry of Finance (encryption key is delivered with program in folder /encrypti/public.pem. You can also

download it from Ministry of Finance web page)

• The encrypted key is appended to the file metadata. For more information, see the following chapter.

Encryption of Encryption Key

The encryption algorithm for the encryption key performs the asymmetric RSA using a public key certificate provided

by the Ministry of Finance. The implementation of encryption uses the following specifications of the RSA algorithm:

Key Size 256 bits / 32 bytes

Cipher Mode CBC (Chain Block Chaining)

Padding PKCS#7

Block Size B16 bytes

Preparation of Authentication Metadata

To send data, you must prepare the credentials in form of an appropriate XML uploads method InitUploadSigned

after you have prepared the essential documents in line with the schedule of the SAF-T.

Host Interface Documents SAF-T for Clients

The mechanism for receiving documents is based on REST services operating based on the HTTPS protocol. This

approach ensures the effectiveness and efficiency of the interface (for example, even compared, SOAP interfaces

type), and an easy integration with the ERP and others written in different technologies.

InitUploadSigned Method

The InitUploadSigned method is used to initiate a client session. Its call is a necessary condition for the data transfer

method Put Blob Azure service.




February 26, 2021


Put Blob Method

The Put Blob method is used to send essential documents SAF-T. This method is implemented directly by the service

storage space Azure (Azure Storage).

FinishUpload Method

The FinishUpload method is used to end the session. Its call is a prerequisite for the proper completion of the

procedure for sending documents. It checks the required files using the name and MD5 values declared in the

InitUploadSigned method. If this method is not invoked at the end of the session it means that the whole session is

invalid or was interrupted.

Status

The Status method returns an official receipt confirmation of sent documents. This method is part of the clients API,

available from the same service as the other methods.

5.3 Ports

For the communication with the server of the Ministry of Finance, the application uses the HTTPS protocol (port 443).

5.4 Data Protection & Privacy

The SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0 is able to process data (for example, personal

data) that might be subject to the data protection laws applicable in specific countries as described in SAP Note

1825544.

Data protection is associated with numerous legal requirements and privacy concerns. In addition to compliance with

general data protection and privacy acts, it is necessary to consider compliance with industry-specific legislation in

different countries. SAP provides specific features and functions to support compliance with regard to relevant legal

requirements, including data protection. SAP does not give any advice on whether these features and functions are

the best method to support company, industry, regional, or country-specific requirements. Furthermore, this

information should not be taken as advice or a recommendation regarding additional features that would be required

in specific IT environments. Decisions related to data protection must be made on a case-by-case basis, taking into

consideration the given system landscape and the applicable legal requirements.

In some scenarios, personal data also includes referenced data such as customer, vendor or business partner data.

SAP simplifies existing deletion functionality to cover data objects that are personal data by default. For this purpose,

SAP uses SAP Information Lifecycle Management (ILM). This function supports the simplified blocking and deletion

of personal data and has impact on data collected in SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0.

https://service.sap.com/sap/support/notes/

https://service.sap.com/sap/support/notes/




February 26, 2021


Detailed information about partner blocking can be found in the ILM documentation. To learn more about how to do

this, please visit Blocking and Unblocking Customer Master Data

For end users without special authorizations (authorization object /PLVAT/J1 ACTVT=05), personal data of

customers and vendors blocked in SAP ILM cannot be accessed. Further information on ILM blocking and related

authorizations can be found in SAP Notes 1825544 and 2007926.

Note: SAP does not provide legal advice in any form. SAP software supports data protection compliance by

providing security features and specific data protection-relevant functions, such as simplified blocking and

deletion of personal data. In many cases, compliance with applicable data protection and privacy laws will not

be covered by a product feature. Definitions and other terms used in this document are not taken from a

particular legal source.

Caution: Generic Fields

The customer needs to make sure that no personal data enters the system in an uncontrolled or non-purpose-

related way – for example, in free-text fields, through APIs, or customer extensions.

Glossary

The following terms are general to SAP products. Not all terms may be relevant for this SAP product.

Term Definition

Blocking

A method of restricting access to data for which the primary business purpose has

ended.

Consent

The action of the data subject confirming that the usage of his or her personal data

shall be allowed for a given purpose. A consent functionality allows the storage of a

consent record in relation to a specific purpose and shows if a data subject has

granted, withdrawn, or denied consent.

Data subject

An identified or identifiable natural person. An identifiable natural person is one who

can be identified, directly or indirectly, in particular by reference to an identifier such

as a name, an identification number, location data, an online identifier or to one or

more factors specific to the physical, physiological, genetic, mental, economic,

cultural, or social identity of that natural person.

Deletion Deletion of personal data so that the data is no longer available.

End of business

Date where the business with a data subject ends, for example, the order is

completed, the subscription is canceled, or the last bill is settled.

End of purpose (EoP)

End of purpose and start of blocking period. The point in time when the primary

processing purpose ends, for example, a contract is fulfilled.

End of purpose (EoP)

check

A method of identifying the point in time for a data set when the processing of

personal data is no longer required for the primary business purpose. After the EoP

has been reached, the data is blocked and can only be accessed by users with

special authorization, for example, tax auditors.

Personal data

Any information relating to an identified or identifiable natural person (a data

subject).

https://help.sap.com/doc/af87585335d90150e10000000a44176d/1511%20000/en-US/f5c25853b2dc7425e10000000a44176d.html

https://service.sap.com/sap/support/notes/1825544





February 26, 2021


Term Definition

Purpose The information that specifies the reason and the goal for the processing of a

specific set of personal data. As a rule, the purpose references the relevant legal

basis for the processing of personal data.

Residence period

The period of time between the end of business and the end of purpose (EoP) for a

data set during which the data remains in the database and can be used in case of

subsequent processes related to the original purpose. At the end of the longest

configured residence period, the data is blocked or deleted. The residence period is

part of the overall retention period.

Retention period

The period of time between the end of the last business activity involving a specific

object (for example, a business partner) and the deletion of the corresponding data,

subject to applicable laws. The retention period is a combination of the residence

period and the blocking period.

Sensitive personal data

A category of personal data that usually includes the following type of information:

1. Special categories of personal data, such as data revealing racial or ethnic

origin, political opinions, religious or philosophical beliefs, trade union

membership, genetic data, biometric data, data concerning health or sex life or

sexual orientation.

2. Personal data subject to professional secrecy

3. Personal data relating to criminal or administrative offenses

4. Personal data concerning insurances and bank or credit card accounts

Where-used check (WUC)

A process designed to ensure data integrity in the case of potential blocking of

business partner data. An application's where-used check (WUC) determines if

there is any dependent data for a certain business partner in the database. If

dependent data exists, this means the data is still required for business activities.

Therefore, the blocking of business partners referenced in the data is prevented.

Read Access Logging

Read access logging is used to monitor and log read access to sensitive data. Data may be categorized as sensitive

by law, by external company policy, or by internal company policy. Read access logging enables you to answer

questions about who accessed particular data within a specified time frame. Here are some examples of such

questions:

1. Who accessed the data of a given business entity, for example a bank account?

2. Who accessed personal data, for example of a business partner?

From a technical point of view, this means that all remote APIs and UI infrastructures (that access the data) are

logged.

For more information on the log functionality, see the Application Help for SAP ERP, Add-on for Polish SAF-T

Regulatory Requirements 1.0, chapter 1.18.1 DPP Report.




February 26, 2021


Information Retrieval

Data subjects have the right to receive information regarding their personal data that is being processed. The

information retrieval feature supports you in complying with the relevant legal requirements for data protection by

allowing you to search for and retrieve all personal data for a specified data subject.

The display report will only show the personal data (no other related business data which are not considered as

personal data) about the data subject. According to the type of data, a selection screen and a result screen will be

offered. Execution of this report will require special authorization.

Deletion of Personal Data

5.4.4.1 Simplified Blocking and Deletion

When considering compliance with data protection regulations, it is also necessary to consider compliance with

industry-specific legislation in different countries. A typical potential scenario in certain countries is that personal data

shall be deleted after the specified, explicit, and legitimate purpose for the processing of personal data has ended,

but only as long as no other retention periods are defined in legislation, for example, retention periods for financial

documents. Legal requirements in certain scenarios or countries also often require blocking of data in cases where

the specified, explicit, and legitimate purposes for the processing of this data have ended, however, the data still has

to be retained in the database due to other legally mandated retention periods. In some scenarios, personal data also

includes referenced data. Therefore, the challenge for deletion and blocking is first to handle referenced data and

finally other data, such as business partner data.

5.4.4.2 Deletion of Personal Data

The processing of personal data is subject to applicable laws related to the deletion of this data when the specified,

explicit, and legitimate purpose for processing this personal data has expired. If there is no longer a legitimate

purpose that requires the retention and use of personal data, it must be deleted. When deleting data in a data set, all

referenced objects related to that data set must be deleted as well. Industry-specific legislation in different countries

also needs to be taken into consideration in addition to general data protection laws. After the expiration of the

longest retention period, the data must be deleted.

This SAP product might process data (personal data) that is subject to the data protection laws applicable in specific

countries as described in SAP Note 1825544.

Deletion

To enable even complex scenarios, SAP simplifies existing deletion functionalities to cover data objects that are

personal data by default. For this purpose, SAP uses SAP Information Lifecycle Management (ILM) to help you set

up a compliant information lifecycle management process in an efficient and flexible manner. For the SAF-T Poland





February 26, 2021


solution, the SAP ILM is relevant only for the Business Partner as well as for ERP Customer and Vendor data. The

ILM component supports the entire software lifecycle including storage, retention, blocking, and deletion of data.

This SAP product depends on SAP ILM configuration for Business Partner and ERP Customer and Vendor data to

support masking of blocked data.

End-of-Purpose Check

An end of purpose (EoP) check determines whether data is still relevant for business activities based on the retention

period defined for the data. The retention period is part of the overall lifecycle of personal data which consists of the

following phases:

1. Business activity: The relevant data is used in ongoing business, for example contract creation, delivery or

payment.

2. Residence period: The relevant data remains in the database and can be used in case of subsequent processes

related to the original purpose, for example reporting obligations.

3. Blocking period: The relevant data needs to be retained for legal reasons. During the blocking period, business

users of SAP applications are prevented from displaying and using this data; it can only be processed in case of

mandatory legal provisions.

4. Deletion: The data is deleted and no longer exists in the database.

Since the goal of SAF-T Poland is to report business transactions, SAF-T itself does not provide an End of Purpose

Check (EoP Check). Instead, it relies on the EoP Check of the applications it reports.

Beside that, an EoP check is introduced for the data files created by SAF-T solution: For all kinds of XML files,

additional “Retention Period” parameter should be configured. It will allow automatically control which data should be

deleted.

For more information on the end-of-purpose check, see the Application Help for SAP ERP, Add-on for Polish SAF-T

Regulatory Requirements 1.0, chapter 1.18.3 Deleting tax audit document.

Blocking

Blocking of data can impact system behavior in the following ways:

1. Display: The system does not display blocked data.




February 26, 2021


2. Change: It is not possible to change a data set that contains blocked data.

3. Create: It is possible to create a data set that contains blocked data

4. Copy/Follow-Up: It is not possible to copy a data set or perform follow-up activities for a business object that

contains blocked data.

5. Search: It is possible to search for blocked data or to search for a data set using blocked data in the search

criteria, but result is displayed in masked form.

It is possible to display blocked data if a user has special authorization. If a user doesn’t have this authorization, data

sets of blocked data are masked and XML files containing blocked data can’t be displayed. (For reporting purposes to

the Polish authorities, the data within the XML file is not masked to ensure compliant transmission to the data to the

authorities.)

For more information on blocking, see the Application Help for SAP ERP, Add-on for Polish SAF-T Regulatory

Requirements 1.0, chapter 1.18.2 Personal data masking.

Change Log

Personal data is subject to frequent changes. Therefore, for review purposes or as a result of legal regulations, it may

be necessary to track the changes made to this data. When these changes are logged, you should be able to check

which employee made which change, the date and time, the previous value, and the current value, depending on the

configuration. It is also possible to analyze errors in this way.

Defining Fields to be Logged

Before creation of the XML file, users can change data collected by SAF-T Poland framework. These data changes

will only affect the data collected and stored within the tables of SAF-T Poland framework, but not the data in the

original tables of the different ERP modules. This kind of changes can also be done for personal data which logs of

the following information:

• the user who is changing the data

• the date and time of change

• the data sets' identifying keys and their values

• the heading name for the attribute that has been changed

The change functionality is limited to the ABAP part of the solution only.

For more information on the change log functionality, see the Application Help for SAP ERP, Add-on for Polish SAF-T

Regulatory Requirements 1.0, chapter 1.8 Changing data extracted from SAP ERP.




February 26, 2021


6 Operations Information

Designing, implementing, and running your SAP applications at peak performance 24 hours a day is vital for your

business success. This chapter contains important information on how to smoothly operate SAP ERP, add-on for

Polish SAF-T regulatory requirements 1.0.

This add-on is based on SAP ERP 6.0. Therefore, the general operations information that is covered in the related

operations guides also applies to SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0.

For more information about related guides, see the following resources on SAP Service Marketplace:

Resource Quick Link on SAP Service Marketplace

Documentation on maintaining an SAP ERP 6.0

http://service.sap.com/instguides

→ SAP Business Suite Applications → SAP ERP 6.0

→ Operations

For a complete list of available SAP Operations Guides, see SAP Service Marketplace at

http://service.sap.com/instguides.

6.1 Monitoring

There is no application log for SAP ERP, add-on for Polish SAF-T regulatory requirements 1.0.

Error logs are provided for each individual tax audit documents. These logs do not contain information about system

errors.

6.2 Administration and Management

Technical Configuration

During the configuration data of the company code, provide the default location for saving XML files.

Note

For more information, see chapter 3.2.1.1.

Create the paths you define in the configuration on the application server first.

In addition, each application server must have permission to read and write files in this folder.

http://service.sap.com/instguides




February 26, 2021


7 Appendix

7.1 Using SCPR20 transaction to upload and activate

BCSets

1. Start transaction SCPR20.

2. Upload BC Set file.

Select provided file: <file_name>.bcs.




February 26, 2021


3. Confirm BC Set.

If system asks about package, you can choose a local object. This file should not be transported, only

configuration, see next steps

4. Run activation process.

5. Provide new configuration request.




February 26, 2021


6. Confirm default activation options

7.2 Rebuild info structure

1. This procedure must be repeated on each system separately.

2. Start SARI transaction.

3. Start customizing mode.




February 26, 2021


4. Enter archive infostructure /PLVAT/JPK_001.

5. Deactivate structure.

6. Delete index table.




February 26, 2021


7. Confirm deletion if popup appears. The table’s name depends on the system.

8. Check and modify field list if needed.

9. If you need to add any additional fields, modify the field catalog, then go back to step 8 and apply changes. You

must move fields to the info structure from optional fields.




February 26, 2021


10. Activate the info structure.

11. Choose Retention Warehouse or Retention Management according to your ILM scenario, if the popup appears.

- If no tax audit documents have been archived, this is the end of procedure.

- If any tax audit documents were archived, fill the structure with data separately on every client.

12. Mark all items and use button Fill Structures.

13. This is the end of procedure when structures will be refilled.

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.