- updated that allows sending and validation of new JPK_FA(3), please be informed that new scheme should be saved in Engine folder
- updated that allows sending and validation of new JPK_FA(2), please be informed that new scheme should be saved in Engine folder
- small fix for module /BCC/JPT_OTH_CHECK_ROLL_VAL (SAF-T file name recognition)
- other small fixes and S/4 HANA compatibility
- adjusted to JPK Typ domain change in base JPK solution (domain /BCC/JPW_DD_TYP), which caused imposible to add JPK file manually
- fixed problem with sending status changed by checking TAX ID (NIP Checker integration) to the one from the moment of the beginning of the checking
- added displaying "Cel złożenia" field (JPK Base solution integration)
- updated certificates to support both JPK Transfer and NIP Checker
- added proxy to JPK Transfer connection option
- added compatibility with JPK_VAT (3) XML format (required form 01.01.2018)
- updated "About Product" button window (e.g. to check directly availbility of update)
- RFC user’s password encryption (new files: install.bat, install.sh)
- updated with NIP Checker 1.00 007 version
- added JCO_SAPROUTER parameter to jpk.properties file
- small adjustment to better work with NIP Checker 1.0 006 (NIP checker ID dependent on company code)
- better icon positioning - new status icons for each sending step (1/2/3/4)
- fixed error with hanging on processing
- NIP Checker compatibility
- better icon positioning
- starting signature tool icon visible by default
- improved tooltips for statuses
- New TOSIGN_S_COPY_LOCAL parameter forcing JPK transfer to copy files for signing to local workstation folder. Can be used when end users do not have access to JPK XML folders.
- additional ONLY_TEST_MODE parameter to be set on SAP test systems. Prevents files from being sent from test systems.
- better AUTO_COPY_SIGNED/AUTOCOPY functionality - possible to specify the path + mask (before only mask). The path designates the folder where signed files are put by the signing program. This allows to use AUTOCOPY with proCertum SmartSign which does not change extensions of the files after signature (making it difficult to distinguish signed and unsigned files)
- additional special command line parameters can be passed to signing tool (path to the folder where signed files should be put to)
- better AUTO_COPY_SIGNED functionality when application server access used (removed filename limit to 40 characters, empty AUTOCOPY does not clear AUTO_COPY_SIGNED anymore, special AUTOCOPY value NO clears AUTO_COPY_SIGNED)
- more special command line parameters can be passed to signing tool (File with path, Company Code, JPK Type, File without path, Path)
- added status "in process - signature"
- making parameter PATH_XML_SAP dependent on Company Code and JPK Type.
- better compatibility with ECC 6.0 older systems
- fix to SAVE_SENT_XML functionality when using local paths for file access (SAP Folder not checked)
- fix to AUTO_START_SIGN_TOOL when using server paths for file access (SAP Folder checked)
- minor fixes to error handling
- added PATH_TOSIGN_S parameter – it defines the path to TOSIGN folder used by the signature tool (when AUTO_START_SIGN_TOOL parameter is used). Parameter PATH_TOSIGN_S should be used ONLY if the TOSIGN folder cannot be derived from PATH_XML parameter (default behavior, when PATH_TOSIGN_S is not given or empty). This configuration parameter can be given on general level (CompCode = “*” and SAF-T(JPK) type = “*”) or on detailed level (for any Company Code/ SAF-T type). The path has to end with \TOSIGN or /TOSIGN depending on operating system.
- additional messages were added when XML directories cannot be read (do not exist or the user is not authorized)
- added PATH_XML_E parameter – Path to the default directory with JPK files visible from JPK Engine. This parameter should be used ONLY when JPK Transfer Engine must access JPK XML files from different path then the one visible by the SAP system (e.g. access via application SAP server on Linux and JPK Transfer engine located on Windows)!
- enhanced handling of external files - F4 help for file attributes (Company Code, JPK Type, Date from, Date to, Version), new parameters to automatically retrieve attributes from filename (EXT_FILE_MASK, EXT_FILE_MASK_AUTO), new parameter to force, that attributes were unique (EXT_FILE_DISTINCT).
- fixed error with date to on the selection screen.
- enhanced functionality of archiving correctly sent XML files (SAVE_SENT_XML parameter). Now it is possible to use this function also when using local folders (no SAP Folder is checked).
- added the possibility to shut JPK Transfer Engine down from the SAP system (via transaction /BCC/JPT_SHUTDOWN or via parameter AUTO_SHUT_ENGINE_LC automatically when exiting JPK Transfer Monitor transaction)
- changed external operating system command called when parameter AUTO_START_ENGINE_AS is used from ZJPT_ENGINE_START to ZJPT_ENGINE_ST_XXX (where XXX is the SAP client number).
- the connection information icon if everything is OK is now hidden.
- when in status Signed, then the string "+ Signed" added to the detailed status message
- fixed problem with last 11 truncated characters on PDF UPO in field "Skrót złożonego dokumentu"
- minor translation corrections
- added possibility to start the signing tool directly from JPK Transfer Monitor transaction (new global parameter AUTO_START_SIGN_TOOL),
- added possibility to start JPK Transfer Engine on SAP appliaction serwer when the user used JPK Transfer Monitor transaction and the engine was not started (additional global parameter AUTO_START_ENGINE_AS),
- changed the default threshold for using new XSD files to SAP server date (was start date of the data being sent). Can be changed in future backwards with global configuration parameter,
- added administor transactions /BCC/JPT_STP (configuration of user's signing tools), /BCC/JPT_SHUTDOWN (forcing shutdown of the JPK Transfer Engine - will work from wersion 1.3).
- changed customizing to adjust to Ministry of Finance requirement to send corrections to old files (from the year 2016) in new format (VAT 01.01.2017)
- added transaction /BCC/JPT_CUST, /BCC/JPT_XSD, /BCC/JPT_LEP to access customizing tables (no need to give access to SM30 anymore),
- added customizing parameter AUTO_START_ENGINE_LC, allowing to start engine locally (on user workstation) when user starts JPK Transfer transaction.
JPK Transfer 1.2/006 - 2016-01-16
New SAF-T Transfer note has been released on January, 21st 2017 to our customers - JPK Transfer 1.2 (005). New version is only slightly different from the previous one 1.2 (002). The translations has been updated, the button informing about release version was added on the selection screen and the administration manual was updated. Additionally the new version has smaller authorization requirements (does not require administration authorizations S_CTS_ADMI i S_CTS_SADM).
As this new version brings only slight interface changes it does not have to be installed when previous version 1.2 (002 or higher) was already implemented. Updated installation files are placed in the same FTP location as previously released version 1.2 (002). If you want to update from version 1.2 (002) or higher, to the version 1.2 (005) please import the transport request 910383 into your SAP system. Other installation files were not changed.
JPK Transfer 1.2/002 - 2016-12-23
1. Better sending status presentation – 3 fields added to the ALV grid:
- general sending status icon
- last operation execution icon
- last operation description
2. Possibility to display detailed error information longer than 100 characters (double click on the detailed status field opens the popup window with longer description, if available).
3. Possibility to show on the ALV grid, the records for the files already sent with success to the Ministry of Finance, for which the files were removed from the XML folder (additional selection parameter ”Show sent and removed records”).
4. New optional configuration parameters put into /BCC/JPT_DB_TCU table:
• PATH_XML_SAP – default „SAP Folder” checkbox value. Important! This configuration parameter can be given only on general level (Company Code = “*” and SAF-T(JPK) type = “*”).
• PATH_XML_MANUAL – if any value (usually X) for this key was introduced, than user can enter the XML path on it’s own. The path provided by user owerwrites the parch read from configuration table. Important! This configuration parameter can be given on general level (Company Code = “*” and SAF-T(JPK) type = “*”) or on detailed level (for a given Company Code / SAF-T type).
• AUTHORIZATION_CHECK – if any value (usually X) for this key was introduced, than authorization object /BCC/JPK01 is checked for the Company Code/ SAF-T Type. Important! This configuration parameter can be given only on general level (Company Code = “*” and SAF-T(JPK) type = “*”).
• SAVE_SENT_XML – if any value (usually X) for this key was introduced, than, when UPO confirmation is read, the XML will be compressed and saved to the index database table /bcc/jpt_db_indx. It can be later downloaded from SAP via „Download archived XML” button. Important! The button appears on the ALV screen only if archived data for selected SAF-T files exist. Important! This configuration parameter can be given on general level (Company Code = “*” and SAF-T(JPK) type = “*”) or on detailed level (for a given Company Code / SAF-T type).
• AUTO_COPY_SIGNED – Parameter that facilitates signing of the xml file, if the signing program does not have the functionality to copy the signature file to another folder (SIGN). If this paramterer has value X, then the solution before sending the file, checks if the .xades signature file is in folders SIGN and TOSING. If the system finds the respective file in the folder TOSIGN and the file is missing in SIGN folder, than the system copies the signature file to „SIGN” folder. Important! When other signature file extensions are used or in unix systems in which upper cases matter, one can put filter value for signature as AUTO_COPY_SIGNED parameter value e.g.: ”*. XAdES”, instead of ”X” value.
5. Possibility to save (archive) the successfully sent XML file in SAP table (/bcc/jpt_db_indx) in compressed form for later retrieval (see new configuration parameter SAVE_SENT_XML).
6. Possibility to set the path to XML files manually if configuration allows it (see configuration parameter PATH_XML_MANUAL)
7. Possibility to set the default value of the parameter „SAP Folder” (see configuration parameter PATH_XML_SAP).
7. Possibility automatically copy signature file from TOSIGN to SIGN folder (facilitates file signing, parameter AUTO_COPY_SIGNED).
9. Easier configuration (values for configuration keys in table /BCC/JPT_DB_TCU)
10. Hiding the button ”Set production run” in the production run”.
11. Prepared to handle XML versions (for second and subsequent versions of XSD files – e.g. JPK_VAT from 01.01.2017)
12. Documentation update and other small improvements
JPK Transfer 1.1 - 2016-07-01
- Updated version 1.0 (first official version)