JPK Basic Package - Release Notes
Posted: Fri Feb 10, 2017 10:01 am
30.12.2019 – JPK version 3.2 (000)
Changes
1. New .XML scheme has beed prepared for JPK_FA structure. New scheme is XF03.
2. New validation rules and customizing set up for JPK_FA.
3. New selection screen for JPK_FA.
4. New validation rules for all date fields (equal to MoF validations).
Version 3.2 requires version 3.0 and contains all notes to version 3.1. If SAF-T version is below 3.0 please import 3.0 first and then 3.2.
Transports order is described in the instruction attached to the e-mail.
06.06.2019 – JPK version 3.1 (001)
Changes
If the date of creating the JPK file was not completed then no scheme was selected by the program. Note fill this date by current day in case it will be left empty.
Transport order:
1. Workbench: BE6K947322
30.05.2019 – JPK version 3.1 (000)
Changes
1. New .XML scheme has beed prepared for JPK_FA strucutre. New scheme is XF02.
2. New validation rules and customizing set up.
3. New selection screen for JPK_FA.
4. In case of using temporary tables (optimalization purposes) then program couses problems with log overload in JPK_MAG, in JPK_KR parameter on selection screen "remove balance 0" has stopped working.
5. JPK Merge for JPK_VAT has been improved.
Update to JPK 3.1 require at least version 3.0 (without notes, notes 1-7 have been combined to version 3.1 but without default values).
Transports order for ECC:
1. Workbench: BE6K947308
2. Customizing: BE6K947310
04.04.2019 – JPK version 3.0 (007) - note 7
1. JPKM optimization
New functionality allows to move data during merging process to hashed tables. Thanks to this conversion both duplicates are removed and all other checks are much faster.
2. Correction to parameter JPK008
JPK008 allows to add class witch will handle button OK_CODE, some buttons might not responding.
3. General optimization - Asynchronous insert to temporary tables – too large transaction log error
New functionality which allows to insert data to temporary tables(activated with *100 parameters) in asynchronous task. Data to SAF-T temporary tables were inserted in single task. For larger data volume and if database processes are logged there might be errors of too large size of transaction log. Activating parameter will split inserts to smaller tasks.
4. SAF-T - General Ledger
Added functionality will connect documents using journal number field. Additionally activating parameter will change default value of journal number from <BELNR> to <GJHAR>/<BELNR> in order to create unique number.
5. SAF-T - General Ledger
In default /BCC/JPK standard mapping XML field DATA DOWODU is filled from /BCC/JPK_ST_KR_DZKG-CPUDT which is acquired from accounting document creation date BKPF-CPUDT. There was no separate field which would represent this date in XML file. Note 7 adds possibility to adding field /BCC/JPK_ST_KR_DZKG-DATA_DOW which will be copied to DATA DOWODU.
6. SAF-T - Bank Statements
GET IBAN from table TIBAN
7. Exclude non tax positions basing on transaction type <BSET-KTOSL>.
8. If there’s no customer/vendor in document then fill partner data with Company Code data.
9. Reading invoice number while creating XML file.
Transports order:
1. Workbench: BE6K946706
2. Workbench: BE6K947172
3. Customizing: BE6K947178
07.01.2019 – JPK version 3.0 (006) - note 6
Change in /BCC/JPK_CL_XML_SLIT type T_SIZE
Number of decimal places in T_SIZE type has been increased. It will ensure proper package number calutaion for large files.
Transports order:
1. Workbench: BE6K946803
10.12.2018 – JPK version 3.0 (005) - notes 4-5
Note 4:
Adding default values in XML file for advance invoice (0 value if no tax).
Transports order:
1. Workbench: BE6R946616
2. Customizing: BE6K946614
Note 5:
1. Correction of dynamic WHERE during XML generation when temporary tabeles are active in JPK FA.
2. Correction of XML split.
3. Changes of log object loading algorithm in JPKM (new feature)
4. Disabling of duplicate validation in JPKM (new feature)
Transports order:
1. Wrokbench: BE6K946718 SNP:JPK:W10 JPK v 3.0.0.5 Nota 5 - JPK fixes – 201811210
2. Customizing: BE6K946720 SNP:JPK:C04 JPK v 3.0.0.5 Nota 5 - JPK fix - config 20181210
26.10.2018 – JPK version 3.0 (003) - notes 1-3
Note 1:
Correction for file division regarding document's currency.
Change in method /BCC/JPK_CL_FA->SAVE_FILL_DIRECT
Transports order:
1. Workbench: BE6K946559
Note 2:
Corrected issues for JPK KR:
1. Removed duplicate entries for ALV header strucutre in new general ledger
2. Fixed issue: accounts without balance in selected period were always omited independently of selected options. This issue occured only in new general ledger.
Transports order:
1. Workbench: BE6K946584
Note 3:
Fix for transactions in foreign currencies. Values were omitted on Credit side.
Changes in class: /BCC/JPK_CL_KR method: FILL_XML_ADD_ITEM
Transports order:
1. Workbench: BE6K946588
2. Customizing: BEK946590
17.10.2018 – JPK version 3.0 (001)
Transports:
1. Workbench: BE6K946535 SNP:JPK:W:01 Rozwiązanie JPK v 3.0.0.2 – 20181012
2. Customizing BE6K946530 SNP:JPK:C:01 - rozwiązanie JPK v.3.0.0.2 20181012
Improvments:
1 In order to reduce memory usage, JPK structures can be saved without interim database structures. Client’s enhancements written in READ_DOC_AFT place will not work automatically.
2 Big XML files can be cut into smaller packages to enable exporting files from the system.
3 Configuration transaction JPKC is changes to group parameters by the type of the structure.
4 JPK reports configuration is moved to separate transaction JPKRC. More complicated reports may be created based on JPK data in JPKR transaction.
5 JPK_FA: Foreign VAT registration numbers can be removed by selection option on selection screen.
6 Company code’s VAT number is displayed correctly when maintaining in company code data with PL prefix.
7 Corrected and added English translations.
8 JPK_VAT: Program suggests to select JPK correction when XML was already sent (when using JPK Transfer).
9 JPK_VAT: Selection of vendors and customers from selection screen is working correctly.
10 JPK reports button is added to main JPK transaction screen.
11 Data address log analysis is working correctly.
12 JPK_KR: for new GL, journal values were shown as 0. Issue is solved.
13 New option to hide unused tabs in JPK selection screen.
14 Option to change numbering of files created in transaction from two digits to alphanumeric values (more files can be created). Feature will not be delivered in standard.
15 File merge transaction JPKM is working better.
16 File merge transaction JPKM – description of newly created file can be changed.
17 JPK_VAT: option to change source fields for documents values, e.g when plants abroad function is used.
18 Authorizations to JPK files were not checked in every transaction.
19 JPK_KR: GL account description source field was different in JPK transaction than in XML file.
20 Reading from archive – function was redesigned and enhanced.
21 JPK_FA: Reference from FI document to SD document is checked for document type (if SD reference).
22 Error when company name contained “&” – can be eliminated by parameter.
23 JPK_MAG: Added default mapping for RW and MM goods release date from material document posting date.
24 Option to block JPK file creation date field for edition in JPK transactions.
25 File merge transaction JPKM – sorting in file choosing window corrected.
26 New configuration parameters in JPKC transaction.
27 Option to divide data base files in smaller packages to optimize memory usage.
01.10.2017 – JPK version 2.9 (= JPK version 2.8 + notes)
1. This version comprises compilation of version 2.8 + 8 notes released separately, if you have implemented all the notes from BCC you do not have to upgrade (please wait for version 3.0 that will contain new JPK_VAT xml format).
Notes:
Note 1 – changed transaction JPKZ for collective/background processing
Note 2 – eliminated “Load of program” error and improved JPKZ transaction
Note 3 – wrong values for gross invoices
Note 4 - eliminated archiving error
Note 5 – unified application information
Note 6 – change sign for tax code
Note 7 – omission of Vat ID prefixes
Note 8 – WNT customer name for output tax
07.02.2017 – Note 00 valid for JPK version 2.8
Transports:
1. BE6K910439 BCC:JPK:VAT:06 Usunięcie błędu walidacji dla zaokrągleń
Update introduced correct validation of rounding position in purchase section (JPK_VAT).
23.01.2017 - Release notes for JPK ver. 2.8
Transports:
1. BE6K910375 BCC:JPK:W:01 JPK v.2.8.
2. BE6K910377 BCC:JPK:C:01 JPK 2.8 (konfig)
A. General improvements:
1. New functionality that allows to combine JPK files: Invoices, Warehouse and VAT
• /BCC/JPKM - transaction that allows to combine JPK files
• /BCC/JPK – new button has been added that allows to join other JPK files
• Parameter JPK004 – define which JPK files can be combined (Inv/WH/VAT)
2. New parameters have been added that allows to define package size of data read from SAP tables:
• KR0003 - KR - Package size read from SAP Tables - for FI docs. (class/BCC/JPK_CL_KR_BP)
• KR0004 – KR - Package size read from SAP Tables - for FI docs. (class/BCC/JPK_CL_KR_NGL)
• KR0005 – KR - Package size read from SAP Tables - for FI docs. (class/BCC/JPK_CL_KR_PP)
• WB0003 – WB - Package size read from SAP Tables
• MAG004 – MAG - Package size read from SAP Tables
• VAT002 – VAT - Package size read from SAP Tables
• FA0004 – Invoice - Package size read from SAP tables
3. Customizable buttons have been added.
Note: Please use buttons: BT_ZX1, BT_ZX2, BT_ZX3, BT_ZX4, BT_ZX5 for individual extensions on Client systems. Buttons can be activated by filling structures: BT_ZX1, BT_ZX2, BT_ZX3, BT_ZX4, BT_ZX5 or by appropriate JPKC configuration. Parameters for JPKC:
1 – Information
2 – Code icon
3 – Text button
B. VAT:
1. New parameter VAT003 has been added – activates “VAT date” on selection screen
2. XML errors has been removed - For JPK VAT version applicable since 1 Jan,2017
C. Invoices:
1. New parameter FA0006 has been added – activates “Posting date” on selection screen
D. Book of accounts:
1. New parameter KR0006 has been added - change in extracting algorithm - Read is data from insights BSIS/BSAS/BSID/BSAD/BSIK/BSAK and BKPR table.
23.11.2016 – Note 01 valid for version 2.7
Transports:
1. BE6K910058
2. BE6K910060
1. Method for calculating the cumulative turnover (DT/CT): In JPK configuration (/n/BCC/JPK) we implemented new parameter “KR0001”. Filling parameter with value “X” will cause that cumulative turnover will include Opening Balance, remain parameter empty will cause that cumulative turnover will not include Opening Balance.
2. Parameter “KR0002” – filling parameter with value “X” will cause that opening balance turnover will be calculated as DT minus CT, that calculated amount (standard OB) will be allocated to cumulative turnover. Remain parameter empty will cause that OB will not be calculated and separately DT turnover of PY will be allocated to DT cumulative turnover and CT turnover of PY will be allocated to CT cumulative turnover.
3. For G/L account balances: In case of non-declaring which ledger should be used, it will be filled with value “0”. Parameter I_RRCTY has been implemented with default value of “0”.
4. For ledger entries, description of transaction has been resumed.
04.11.2016 – JPK Update to version 2.7
Transports:
1. BE6K909990 BCC:JPK:W:01 Rozwiązanie JPK v.2.7
2. BE6K909992 BCC:JPK:C:01 Rozwiązanie JPK v.2.7 (konfig)
3. BE6K910025 BCC:JPK:02 JPK v.2.7 – walidacja
A. General improvements:
• Transaction /BCC/JPKZ – running program in background will create a list of performed activities (transaction SM36).
• Transaction /BCC/JPKZ – new functionality which allows to create separate JPK files for each day of selected period (set as default) or for any number of days.
• We eliminated removal of activity logs (removed by SAP) and in case of removal, JPK will create new object to save performed activities.
• New transaction /BCC/JPKF – create default directory for saving JPK files.
B. Account books:
• Extract data from new general ledger (parallel books and sub-ledgers).
• Improved functionality of extracting credit notes.
• Opening balance selection – user may choose whether to present OB of the selected period or financial year. Only one OB will be transferred to JPK file.
C. Warehouse:
• Version 2.7 introduce the possibility to identify each material document specifying only movement type. So far both fields (document type and movement type were required). Nevertheless filling document type can still be used due to fact that may improve selecting process.
• Possibility to generate JPK files for each document type separately (PZ,RW,MM,WZ) by selecting checkboxes for each type.
• Possibility to extract data directly form material document (customer/supplier data).
D. Invoices:
• Version 2.7 introduce rounding’s to ensure the compliance between items on invoice with total value of invoice and also new functionality to verify “-/+” of each item on invoice.
• In case of non standard implementation of tax accounts, JPK standard may not correctly present net, tax and gross values. We implemented possibility to manually indicate tax (VAT) accounts in configuration.
E. Bank Statements:
• New field with bank account number, which will be transferred to appropriate fields in the XML file.
• New functionality that allows to change signs (“-/+”) for each BS item and balances. It may be activated through configuration.
Changes
1. New .XML scheme has beed prepared for JPK_FA structure. New scheme is XF03.
2. New validation rules and customizing set up for JPK_FA.
3. New selection screen for JPK_FA.
4. New validation rules for all date fields (equal to MoF validations).
Version 3.2 requires version 3.0 and contains all notes to version 3.1. If SAF-T version is below 3.0 please import 3.0 first and then 3.2.
Transports order is described in the instruction attached to the e-mail.
06.06.2019 – JPK version 3.1 (001)
Changes
If the date of creating the JPK file was not completed then no scheme was selected by the program. Note fill this date by current day in case it will be left empty.
Transport order:
1. Workbench: BE6K947322
30.05.2019 – JPK version 3.1 (000)
Changes
1. New .XML scheme has beed prepared for JPK_FA strucutre. New scheme is XF02.
2. New validation rules and customizing set up.
3. New selection screen for JPK_FA.
4. In case of using temporary tables (optimalization purposes) then program couses problems with log overload in JPK_MAG, in JPK_KR parameter on selection screen "remove balance 0" has stopped working.
5. JPK Merge for JPK_VAT has been improved.
Update to JPK 3.1 require at least version 3.0 (without notes, notes 1-7 have been combined to version 3.1 but without default values).
Transports order for ECC:
1. Workbench: BE6K947308
2. Customizing: BE6K947310
04.04.2019 – JPK version 3.0 (007) - note 7
1. JPKM optimization
New functionality allows to move data during merging process to hashed tables. Thanks to this conversion both duplicates are removed and all other checks are much faster.
2. Correction to parameter JPK008
JPK008 allows to add class witch will handle button OK_CODE, some buttons might not responding.
3. General optimization - Asynchronous insert to temporary tables – too large transaction log error
New functionality which allows to insert data to temporary tables(activated with *100 parameters) in asynchronous task. Data to SAF-T temporary tables were inserted in single task. For larger data volume and if database processes are logged there might be errors of too large size of transaction log. Activating parameter will split inserts to smaller tasks.
4. SAF-T - General Ledger
Added functionality will connect documents using journal number field. Additionally activating parameter will change default value of journal number from <BELNR> to <GJHAR>/<BELNR> in order to create unique number.
5. SAF-T - General Ledger
In default /BCC/JPK standard mapping XML field DATA DOWODU is filled from /BCC/JPK_ST_KR_DZKG-CPUDT which is acquired from accounting document creation date BKPF-CPUDT. There was no separate field which would represent this date in XML file. Note 7 adds possibility to adding field /BCC/JPK_ST_KR_DZKG-DATA_DOW which will be copied to DATA DOWODU.
6. SAF-T - Bank Statements
GET IBAN from table TIBAN
7. Exclude non tax positions basing on transaction type <BSET-KTOSL>.
8. If there’s no customer/vendor in document then fill partner data with Company Code data.
9. Reading invoice number while creating XML file.
Transports order:
1. Workbench: BE6K946706
2. Workbench: BE6K947172
3. Customizing: BE6K947178
07.01.2019 – JPK version 3.0 (006) - note 6
Change in /BCC/JPK_CL_XML_SLIT type T_SIZE
Number of decimal places in T_SIZE type has been increased. It will ensure proper package number calutaion for large files.
Transports order:
1. Workbench: BE6K946803
10.12.2018 – JPK version 3.0 (005) - notes 4-5
Note 4:
Adding default values in XML file for advance invoice (0 value if no tax).
Transports order:
1. Workbench: BE6R946616
2. Customizing: BE6K946614
Note 5:
1. Correction of dynamic WHERE during XML generation when temporary tabeles are active in JPK FA.
2. Correction of XML split.
3. Changes of log object loading algorithm in JPKM (new feature)
4. Disabling of duplicate validation in JPKM (new feature)
Transports order:
1. Wrokbench: BE6K946718 SNP:JPK:W10 JPK v 3.0.0.5 Nota 5 - JPK fixes – 201811210
2. Customizing: BE6K946720 SNP:JPK:C04 JPK v 3.0.0.5 Nota 5 - JPK fix - config 20181210
26.10.2018 – JPK version 3.0 (003) - notes 1-3
Note 1:
Correction for file division regarding document's currency.
Change in method /BCC/JPK_CL_FA->SAVE_FILL_DIRECT
Transports order:
1. Workbench: BE6K946559
Note 2:
Corrected issues for JPK KR:
1. Removed duplicate entries for ALV header strucutre in new general ledger
2. Fixed issue: accounts without balance in selected period were always omited independently of selected options. This issue occured only in new general ledger.
Transports order:
1. Workbench: BE6K946584
Note 3:
Fix for transactions in foreign currencies. Values were omitted on Credit side.
Changes in class: /BCC/JPK_CL_KR method: FILL_XML_ADD_ITEM
Transports order:
1. Workbench: BE6K946588
2. Customizing: BEK946590
17.10.2018 – JPK version 3.0 (001)
Transports:
1. Workbench: BE6K946535 SNP:JPK:W:01 Rozwiązanie JPK v 3.0.0.2 – 20181012
2. Customizing BE6K946530 SNP:JPK:C:01 - rozwiązanie JPK v.3.0.0.2 20181012
Improvments:
1 In order to reduce memory usage, JPK structures can be saved without interim database structures. Client’s enhancements written in READ_DOC_AFT place will not work automatically.
2 Big XML files can be cut into smaller packages to enable exporting files from the system.
3 Configuration transaction JPKC is changes to group parameters by the type of the structure.
4 JPK reports configuration is moved to separate transaction JPKRC. More complicated reports may be created based on JPK data in JPKR transaction.
5 JPK_FA: Foreign VAT registration numbers can be removed by selection option on selection screen.
6 Company code’s VAT number is displayed correctly when maintaining in company code data with PL prefix.
7 Corrected and added English translations.
8 JPK_VAT: Program suggests to select JPK correction when XML was already sent (when using JPK Transfer).
9 JPK_VAT: Selection of vendors and customers from selection screen is working correctly.
10 JPK reports button is added to main JPK transaction screen.
11 Data address log analysis is working correctly.
12 JPK_KR: for new GL, journal values were shown as 0. Issue is solved.
13 New option to hide unused tabs in JPK selection screen.
14 Option to change numbering of files created in transaction from two digits to alphanumeric values (more files can be created). Feature will not be delivered in standard.
15 File merge transaction JPKM is working better.
16 File merge transaction JPKM – description of newly created file can be changed.
17 JPK_VAT: option to change source fields for documents values, e.g when plants abroad function is used.
18 Authorizations to JPK files were not checked in every transaction.
19 JPK_KR: GL account description source field was different in JPK transaction than in XML file.
20 Reading from archive – function was redesigned and enhanced.
21 JPK_FA: Reference from FI document to SD document is checked for document type (if SD reference).
22 Error when company name contained “&” – can be eliminated by parameter.
23 JPK_MAG: Added default mapping for RW and MM goods release date from material document posting date.
24 Option to block JPK file creation date field for edition in JPK transactions.
25 File merge transaction JPKM – sorting in file choosing window corrected.
26 New configuration parameters in JPKC transaction.
27 Option to divide data base files in smaller packages to optimize memory usage.
01.10.2017 – JPK version 2.9 (= JPK version 2.8 + notes)
1. This version comprises compilation of version 2.8 + 8 notes released separately, if you have implemented all the notes from BCC you do not have to upgrade (please wait for version 3.0 that will contain new JPK_VAT xml format).
Notes:
Note 1 – changed transaction JPKZ for collective/background processing
Note 2 – eliminated “Load of program” error and improved JPKZ transaction
Note 3 – wrong values for gross invoices
Note 4 - eliminated archiving error
Note 5 – unified application information
Note 6 – change sign for tax code
Note 7 – omission of Vat ID prefixes
Note 8 – WNT customer name for output tax
07.02.2017 – Note 00 valid for JPK version 2.8
Transports:
1. BE6K910439 BCC:JPK:VAT:06 Usunięcie błędu walidacji dla zaokrągleń
Update introduced correct validation of rounding position in purchase section (JPK_VAT).
23.01.2017 - Release notes for JPK ver. 2.8
Transports:
1. BE6K910375 BCC:JPK:W:01 JPK v.2.8.
2. BE6K910377 BCC:JPK:C:01 JPK 2.8 (konfig)
A. General improvements:
1. New functionality that allows to combine JPK files: Invoices, Warehouse and VAT
• /BCC/JPKM - transaction that allows to combine JPK files
• /BCC/JPK – new button has been added that allows to join other JPK files
• Parameter JPK004 – define which JPK files can be combined (Inv/WH/VAT)
2. New parameters have been added that allows to define package size of data read from SAP tables:
• KR0003 - KR - Package size read from SAP Tables - for FI docs. (class/BCC/JPK_CL_KR_BP)
• KR0004 – KR - Package size read from SAP Tables - for FI docs. (class/BCC/JPK_CL_KR_NGL)
• KR0005 – KR - Package size read from SAP Tables - for FI docs. (class/BCC/JPK_CL_KR_PP)
• WB0003 – WB - Package size read from SAP Tables
• MAG004 – MAG - Package size read from SAP Tables
• VAT002 – VAT - Package size read from SAP Tables
• FA0004 – Invoice - Package size read from SAP tables
3. Customizable buttons have been added.
Note: Please use buttons: BT_ZX1, BT_ZX2, BT_ZX3, BT_ZX4, BT_ZX5 for individual extensions on Client systems. Buttons can be activated by filling structures: BT_ZX1, BT_ZX2, BT_ZX3, BT_ZX4, BT_ZX5 or by appropriate JPKC configuration. Parameters for JPKC:
1 – Information
2 – Code icon
3 – Text button
B. VAT:
1. New parameter VAT003 has been added – activates “VAT date” on selection screen
2. XML errors has been removed - For JPK VAT version applicable since 1 Jan,2017
C. Invoices:
1. New parameter FA0006 has been added – activates “Posting date” on selection screen
D. Book of accounts:
1. New parameter KR0006 has been added - change in extracting algorithm - Read is data from insights BSIS/BSAS/BSID/BSAD/BSIK/BSAK and BKPR table.
23.11.2016 – Note 01 valid for version 2.7
Transports:
1. BE6K910058
2. BE6K910060
1. Method for calculating the cumulative turnover (DT/CT): In JPK configuration (/n/BCC/JPK) we implemented new parameter “KR0001”. Filling parameter with value “X” will cause that cumulative turnover will include Opening Balance, remain parameter empty will cause that cumulative turnover will not include Opening Balance.
2. Parameter “KR0002” – filling parameter with value “X” will cause that opening balance turnover will be calculated as DT minus CT, that calculated amount (standard OB) will be allocated to cumulative turnover. Remain parameter empty will cause that OB will not be calculated and separately DT turnover of PY will be allocated to DT cumulative turnover and CT turnover of PY will be allocated to CT cumulative turnover.
3. For G/L account balances: In case of non-declaring which ledger should be used, it will be filled with value “0”. Parameter I_RRCTY has been implemented with default value of “0”.
4. For ledger entries, description of transaction has been resumed.
04.11.2016 – JPK Update to version 2.7
Transports:
1. BE6K909990 BCC:JPK:W:01 Rozwiązanie JPK v.2.7
2. BE6K909992 BCC:JPK:C:01 Rozwiązanie JPK v.2.7 (konfig)
3. BE6K910025 BCC:JPK:02 JPK v.2.7 – walidacja
A. General improvements:
• Transaction /BCC/JPKZ – running program in background will create a list of performed activities (transaction SM36).
• Transaction /BCC/JPKZ – new functionality which allows to create separate JPK files for each day of selected period (set as default) or for any number of days.
• We eliminated removal of activity logs (removed by SAP) and in case of removal, JPK will create new object to save performed activities.
• New transaction /BCC/JPKF – create default directory for saving JPK files.
B. Account books:
• Extract data from new general ledger (parallel books and sub-ledgers).
• Improved functionality of extracting credit notes.
• Opening balance selection – user may choose whether to present OB of the selected period or financial year. Only one OB will be transferred to JPK file.
C. Warehouse:
• Version 2.7 introduce the possibility to identify each material document specifying only movement type. So far both fields (document type and movement type were required). Nevertheless filling document type can still be used due to fact that may improve selecting process.
• Possibility to generate JPK files for each document type separately (PZ,RW,MM,WZ) by selecting checkboxes for each type.
• Possibility to extract data directly form material document (customer/supplier data).
D. Invoices:
• Version 2.7 introduce rounding’s to ensure the compliance between items on invoice with total value of invoice and also new functionality to verify “-/+” of each item on invoice.
• In case of non standard implementation of tax accounts, JPK standard may not correctly present net, tax and gross values. We implemented possibility to manually indicate tax (VAT) accounts in configuration.
E. Bank Statements:
• New field with bank account number, which will be transferred to appropriate fields in the XML file.
• New functionality that allows to change signs (“-/+”) for each BS item and balances. It may be activated through configuration.