Release notes for Journal Entry 9.5-9.3
Journal Entry 9.5
Released February 2017
New features and improvements
- The BAPI template now supports using a list of values (LOV) for the DOCUMENTHEADER-USERNAME field.
This allows template creators to scope the field's value to the current user's SAP ID or Windows ID, or to another defined value.
Known issues
If the document exceeds the maximum document length, Journal Entry returns a warning message. After you click OK, the results vary, depending on the mapping:
- Cell-based mapping: The document is run up to the maximum number of rows; the rest of the document is not processed.
- Column-based mapping: The entire document is run, even though it exceeds the document length. Any rows that exceed the SAP limit will not be posted. To avoid posting a document that exceeds the maximum length, split the document.
Journal Entry 9.4
Released September 2016
New features and improvements
- Support added for the following transaction codes: F-22, F-43, F-65, FBV1.
- The following templates added:
Single company
FBV1 Park document F-65 Park document F-43 Post vendor invoice Column-based F-43 Post vendor invoice Cell-based F-22 Post customer invoice Column-based F-22 Post customer invoice Cell-based Multi Company post
F-43 Post vendor invoice Column-based F-43 Post vendor invoice Cell-based F-22 Post customer invoice Column-based F-22 Post customer invoiced Cell-based - Support added for Windows 10 and Microsoft Office 2016.
- Support added for SAP GUI 740.
To use SAP GUI 740, you must update the AppOptions.xml file with the following:
<SAPLogonConfigPath>[path to the SAPUILandscape.xml file]</SAPLogonConfigPath>
The AppOptions.xml file is located at C:\Users\<user name>\AppData\Roaming\Winshuttle\JournalEntry.
- Support added for column-based BAPI templates.
- Single installer installs the correct version, 32-bit or 64-bit, based on the version of Microsoft Office.
- An error message confirms that simulation is not supported for scripts that contain multiple loops.
- Documents can now be attached as an external URL (this requires Winshuttle Function Module 11.1).
Bugs fixed
- Full transaction code descriptions for templates are now shown and have been corrected where appropriate.
- Header items created when the document is split retain the cell formatting of the original header item.
- The Auto-attachment setting that is set by script developers is now enforced for script runners.
- Central only: Runners can now attach supporting documents.
Known issues
If the document exceeds the maximum document length, Journal Entry returns a warning message. After you click OK, the results vary, depending on the mapping:
- Cell-based mapping: The document is run up to the maximum number of rows; the rest of the document is not processed.
- Column-based mapping: The entire document is run, even though it exceeds the document length. Any rows that exceed the SAP limit will not be posted. To avoid posting a document that exceeds the maximum length, split the document.
Journal Entry 9.3
Released March 2, 2016
New features and improvements
- Support added for the following transaction codes: F-05, FV50, FV50L.
- New templates that support split documents for FB01, F-02, FB60, FB65, FB70, FB75, FBS1.
- Support for splitting documents in custom templates that were recorded with complex posting. The header amount is in the first line item.
- Split document is disabled for templates that have an amount in the header.
- When splitting a document, the default selection is not auto balance.
- Column-based and cell-based templates for FB60, FB65, FB70, FB75.
- Fields that are required by a default template are locked, and the Required Field check box cannot be unchecked.
- When importing scripts, header fields and line item fields appear on separate screens.
- When importing scripts, multiple debit/credit indicators can be defined (using comma-separated values).
- Custom templates that include IF conditions must use the mapping type that was used in the Transaction script.
- Default mapping has no overlap issues.
- Better experience when deleting scripts.
- The cell-protection prompt can be turned off in the AppOptions.xml file.
- Support information can be generated and provided to the Support team.
- Updated authorization check.
- Support for Winshuttle Function Module 11.
- Log header details are now available for column-based and cell-based mapping. They can be turned on or off in the AppOptions.xml file.
- Support for returning extended logs during validation.
- The Add Custom Script wizard is now localized in French, German, and Spanish.
- For Connect users, more relevant feature tracking in the logs.
- For Connect users, the fiscal year can be controlled in the Options.
If it is not defined in the Options, Journal Entry queries SAP to get the fiscal year. - For Central users, fiscal year can now be controlled on the Central site or in the Options.
If it is not defined in the Options, Journal Entry queries SAP to get the fiscal year.
Because these templates contain IF conditions, they cannot switch back and forth between column-based and cell-based mapping.
Bugs fixed
- Custom LOVs now work for multiple debit/credit indicator fields in a script.
- For multiple-template workbooks, the validation message now specifies the sheet for which the message is displayed.
- The Enter key now works when entering constants in the Mapper.
- An error is now returned when attempting to Park or Save as Completed an FB01L template that includes the Ledger Group field.
- Log header details are now available for column-based and cell-based mapping. They can be turned on or off in the AppOptions.xml file.
- Single line item simulation no longer gives an exception.
- Simulating an FB65 template no longer returns an AutoFill method of Range class failed error.