|
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.
For debit and credit indicators, use the default "S" and "H" or click the List of Values button and type in the labels you want.
Note: You can add tax information on the Basic tab or the Tax tab. However, fields on the tax tab cannot be included in a loop.
Notes:
If your template is column-based, add the Company Code on the last screen before you click Publish. You can select the column that is mapped to the Company Code, or you can type a fixed value.
In Journal Entry 9.1, you can choose to show the field's technical name instead of its description. Check the Show Technical Name box.
Select and map the fields for the header and the log fields, add any lists of values that you want people to use. If you want to use the same value for a field every time, change it to Fixed. See the sections below for more details.
Then click Next, and select and map the fields for the line items, add LOVs and set any values that need to be fixed.
After you select the mode, t-code, sheet, and mapping and click Customize New Template, check the Selection box for each field that you want people to use.
If a field must contain data, check both Selection box and the Required Field box.
To map fields, you need to assign a column or cell to the headers on the first page of the Customization pane and the line-item fields on the second page of the Customization pane.
Tip: Take note of the row or column where your header and log fields end so that you can avoid overlapping when you map the line items.
To manually map headers, enter a cell name or column name in the Mapping column.
To automatically map headers (if you have many cells to map), check the Auto map settings box, choose the settings that you want, and then click the AutoMap button .
Auto map settings:
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.
If you later want to change the LOV, click the LOV button in the Mapper to open the list.
If you do not check the box, SAP will convert the custom values to the default values that are listed in the Custom Debit Credit Indicators box.
Note: In version 9.2, the Preserve Excel Posting Key Values box is checked by default.
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.
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, which allows the runner to override the LOVs and enter a value that is not in the existing LOVs.
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.
Note: When you finish creating fixed values for headers or line item fields, the Data Review pane will show only the fields that are marked as Runtime. Fixed items will not appear in this list.
The Fixed value for dialog box appears.
Tip: If you need to find the value you want to use, click SAP F4, log on to SAP if necessary, click the value that you want to use, and then click the green check mark.
You will notice that the row containing the field name and description is now blue and that the cell in the Mapping 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 pin in the List of Values column, enter the new value, and click OK.
After you map the line-item fields, click Next.
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.
Enter the loop information:
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.
Important: Journal Entry cannot split a column-based document that contains multiple loops at the same level.
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.
Also in this section System requirements for Central |