|
Back to |
To author templates in Journal Entry, you must have the Transaction Developer role in Central.
Winshuttle Journal Entry provides several default templates, organized under headings of General Ledger, Accounts Payable, Accounts Receivable, or Accrual/Deferral. Depending on the type of template that you selected, you can further customize the templates for Simple post, Multiple Company post, or COPA post and, depending on the template, by t-code.
In Journal Entry for Winshuttle Central, you must store the template in Central. For more information on configuring Central, see the Winshuttle Central Admin Guide.
Journal Entry adds efficiency by allowing multiple templates or data sheets to be added to one workbook. The entire workbook is submitted to Central, which triggers one workflow for all templates.
Note: Column mapping is not supported for BAPIs.
You are notified that your template and any supporting documents have been submitted to the Central site.
Whether you are creating a sheet from a template or creating an original template, the Journal Entry customization capabilities give you control over the mapping and naming of cells (similar to the functionality in Transaction) and over the layout of objects in the workbook.
In Journal Entry, you can customize a template from the default BAPI by clicking the Customize button. The default BAPI covers document post and is available in single post or multicompany post modes.
By using the Add More Fields button in the Customization wizard, you can include headers and line items that were not included when the BAPI script, the .txr file, was created. You can search for fields, and map fields as for any other template in Journal Entry.
By default, the field return-message v2 is included among the journal line items to display the document number after post. When the sheet is posted, the field return-message v2 also returns the document number, company code and fiscal year to the post results cell and provides the document number link.
Journal Entry templates from BAPIs also may requiring splitting to simulate because BAPI processes simulations by chunks. The chunk size is specified through the split document settings that you added when you created the template. If the data exceeds the chunk size, the user is asked to split the document.
When adding data to a Journal Entry sheet, the amount must be entered as a plus or a minus because no debit or credit indicators are available. For example, a debit of $50 would be entered as "-50".
Only "Post" is available for the current implementation of BAPI in Journal Entry. "Park" is not available.
After the document number is returned, you can attach documents as for other templates in Journal Entry.
To map cells, you must map the headers on the first page of the Customization pane to the data cells on the second page of the Customization pane. There are two ways to do this:
To automatically map log and output cell headers, click Log Cells and then click the AutoMap button.
You can assign a list of values (LOV) to a cell by selecting to display entire SAP windows, include a text file, include an Excel file, or to include select SAP fields from an F4 lookup. Where a list of values appears, the value selected by the user during data entry is validated when the sheet is validated.
-or-
Although SAP descriptions are not loaded, you can customize your own descriptions. In addition, you can limit the values available. Click Delete to remove a value from the list.
For all header and line item fields, you can create a run-time value.
Note: If Journal Entry prompts you that line items will overlap with existing log and out cells, do one of the following: increase the Start Row, uncheck the Write headers for Journal Entry Header Items box, or change the mapping for header items or logs.
For all header and line item fields, you can create a fixed value--that is, a permanent value that cannot be changed. The runner will not be able to edit this value during execution.
The Fixed value for dialog box appears.
You will notice that the row containing the field name and description is now blue and that the cell in the Mapped to cell column is now gray. This is because fixed values are not mapped to a particular cell in Excel.
Note: To change a current fixed value, click the red arrow in the List of Values column, enter the new value, and click OK.
Note: If Journal Entry prompts you that line items will overlap with existing log and out cells, do one of the following: increase the Start Row, uncheck the Write headers for Journal Entry Header Items box, or change the mapping for header items or logs.
Template authors can define a custom length of between 0 and 998 line items for a document. If a runner tries to post a document that exceeds the maximum item length, a message prompts the runner to split the document. Document chunks from a split cannot be longer than the maximum length for that template.
Important: Journal Entry cannot split a column-based document that contains multiple loops at the same level.
When you finish creating fixed values for headers or line item fields, you will see a data review pane which includes all fields that were marked as "Runtime." Fixed items will not appear in this list.
Note: If you choose Runtime for a field, you can either give LOV values for that field or you can leave as it is. However, if you give the LOV values for that field, the runner will have to choose a value from the LOVs that you specified unless and until you select the Allow user to override Custom List of Values check box. This is because, at the time of execution, the runner can override the LOVs and enter a value that does not exist in the existing LOVs.
For large uploads, instead of using multiple workbooks, you can split your document. You need to know the name or number of an SAP reconciliation or offset account so that all the documents that result from a split can be balanced.
Also in this section |