SAP Business One 9.3 PL06 Overview - SAP Support

Important Corrections Delivered in Patches SAP Business One 9.3 This presentation provides an overview of the most important corrections, also known as Top ReSolutions, which are delivered in patches. A selection of the corrections is presented in more detail. 

- For a complete overview of the corrections delivered in a specific patch, refer to the overview note.

- For all enhancements in SAP Business One 9.3, please review the Highlights document.

- For all changes made in the DI API interface between patches of SAP Business One version 9.3, refer to SAP Note 2584704.

- For Troubleshooting and Compatibility Information, refer to the following SAP Notes:

•  SAP Business One Sales Mobile App for iOS and Android - SAP Note 2267084.
•  SAP Business One Service for iOS - SAP Note 2639956.

- For SAP Business One Patch Delivery Schedule please refer to SAP Note 2267770.

Sensitive Personal Data – Bank Accounts of Natural Persons

Feature

• Control by log/record of any access to a special category of personal data – sensitive personal data – now includes bank account data
• In the core SAP Business One application the following three fields are affected:
  • Business Partner Bank Account No. ▪ Business Partner IBAN No.
  • Employee Bank Account 
  • Bank Account values in master data and transactions (payments, check register, bill of exchange, OPEX table, deposits, etc.) encrypted in the database
• Values hidden/masked by default on User Interface – NOTE: manual change required when upgrading from 9.3 PL04 or 9.3 PL05
• Access and decryption via DI API supported

Benefit

• Selected authorized users can view hidden sensitive personal data values

Bank Accounts and IBAN Encryption and Impact on Payment Wizard

Important Rules

• When updating OPEX table with the payment run data, the bank account no. and IBAN of business partner who is determined as natural, are taken into the OPEX as encrypted data.

• When generating the bank file in payment wizard, the encrypted data is decrypted before taken into the bank file.
• The decryption of this data when the bank file is of type EFM format, is supported only when the selected payment methods in the payment wizard run are all related to EFM format. When the wizard run involves payment methods which relate to both EFM and DLL formats and the wizard includes business partners which are determined as natural persons, the bank account and IBAN will not be decrypted before taken into the EFM bank file. A pop-up message is raised to warn users about the combination of two different bank file categories.

• The decryption of the data when the bank file is of type .DLL format is handled by DI service (SAP Note 2633811). This service is called by the payment addon. The payment add-on identifies the fields to be decrypted by the setup in Personal Data Management.
• Once the bank file is generated with decrypted data, users need to ensure it is stored in a secure and protected location.