Introduction to Winshuttle Journal Entry
Introduction to Winshuttle Journal Entry
Winshuttle Journal Entry is a data entry and upload tool that presents an easy-to-use front end for SAP FICO transactions. Journal Entry is available in two licensing modes:
- Winshuttle Connect to manage licensing of Winshuttle products.
- Winshuttle Central to manage licensing, and use of scripts, queries, and user access to SAP.
Release notes for Journal Entry 9.2
Released July 20, 2015
New features and improvements
- Transaction codes FBB1 for adjustment postings is supported.
- Transaction code FB01L, which is required as an additional transaction code for adding custom scripts, is supported.
- The Multithread Simulation feature allows large sets of data to be split into chunks and processed at the same time.
- LOV values for custom fields are now available in the Mapper.
- LOVs can now be defined for fields that are dependent on another field's value. Journal Entry prompts the script developer for the required value.
- Multi-company posting in Batch mode is supported for cell-based scripts.
Bugs fixed
- An error message is now returned when the debit or credit indicators are invalid.
- Custom posting keys are now preserved by default.
- Custom LOV fields and mandatory fields have separate error messages.
- Users are no longer prompted to save the workbook before customizing it.
- Apostrophes are now displayed correctly in email messages that are processed through Winshuttle Connect.
Known issues
- If a worksheet that has protected cells is run with the Multithread Simulation feature, the runner will receive multiple warning messages about the protected cells. Journal Entry will return one warning message for each thread.
Release notes for Journal Entry 9.1
Released May 29, 2015
New features and improvements
Bugs fixed
- Multiple loops at the same level are now supported in column-based templates.
- Validation now checks only the mapped columns.
- The Customize New Template and Re-Customize commands no longer cause Excel to raise an exception error and stop responding.
- Runners can no longer re-customize production-status files. They can view customizations.
- Fiscal Year now retains the user-entered value.
- French version: Hyperlinks are now created for column-based templates.
Known issues
- Excel worksheets that contain protected cells have the following limitations:
- The Document Split feature is not supported for cell-based or column-based templates.
- The Clear All command is not supported.
- The Clear Data command might not remove line-item data.
- If the Simulate Log header is protected, no simulation logs will be written.
- The ability to show field descriptions instead of field names is available for Validate only; it is not available for Post, Park, Save as Completed or Simulate.
- The Document split feature is not available for scripts that have multiple loops.
- If the Simulate or Validate header cells have fill effects applied, running Simulate or Validate might change the cell color to black.
Release notes for Journal Entry 9.0
Released January 28, 2015
New features and improvements
- Journal Entry now supports custom Transaction scripts that were recorded in Batch Input mode.
- For new custom templates, the t-code is displayed in the Template Info box.
- For new custom templates that are created by importing a Transaction script, the script file name is displayed in the Template Info box.
- With Central, multiple templates can now be published and run in a single workbook. After posting the data on one sheet, the runner can click the next sheet and post the data that is on it.
- Custom posting keys are now supported. When the Preserve Excel Posting Key Values option is checked, the custom values are posted to SAP, instead of being converted to default SAP posting key values.
- Document attachments now support macro-enabled files (.xlsm). Support has also been added for .rtf, .htm, and .pptx document attachments.
- Log columns that have custom headers now keep the header text and formatting instead of being overwritten with the default headers.
- Runners can now work with password-protected workbooks and worksheets by providing the passwords.
- Templates have been added for FBD1 (for both cell-based mapping and column-based mapping).
- Custom scripts can be added for FB01 and F-02 no longer require the amount field in the document header. The amount field can be in a line item or in both the header and a line item.
- Support has been added for SAP F4 lookup in custom fields. To get the required Winshuttle Function Module patch, contact Winshuttle Support. (Updated in Journal Entry 9.1)
- Company code header is now displayed for when you load the FB01-MC template.
- Logoff from SAP is automatic when you log off from Connect.
- With Central, multiple templates can now be published and run in a single workbook. After posting the data on one sheet, the runner can click the next sheet and post the data that is on it.
- Data File Management can now be controlled by the Central site administrator.
- The Fiscal Year setting can now be controlled by the Central site administrator.
- Journal Entry logs are now available on the Central site's Client Log Viewer page.
Bugs fixed
- Journal Entry 9.0 supports re-customizing templates that were created in Journal Entry 7.0 and Journal Entry 8.0.
- Loop information is now visible in the Mapper, as well as in the Loop Details box, when using Journal Entry 9.0 with Microsoft Excel 2010.
- The Delete Custom Script command label text is now visible when using Journal Entry 8.0 with Microsoft Excel 2010.
- In templates that have multiple loops that are at the same level, Journal Entry creates a document link for only the first posted document.
Known issues
- The Document Amount column must be formatted as Number.
- Multiple loops at the same level are supported only for long text. Multiple loops for other fields are not supported. (Fixed for column-based templates in Journal Entry 9.1)
- Different formatting applied to text in the same Log cell is not supported.
- When you customize or re-customize a column-based template, you must specify the Company Code on the last screen before you can publish the template.
Get started with Journal Entry
Select the documentation that is appropriate to the type of Winshuttle licensing that is used in your organization.