...
No. (No.)
The user chooses the name of the template
Invoice Interface Code
The user selects the invoice interface code for which the template is being set up
Business Type
The system will set up according to the billing interface. In the case of processing a fuel data record, the Purchase is
Source Code
The system will set up according to the billing interface.
Document Type
User selects Invoice
Buy-from Vendor No.
The user can select the fuel card vendor
If the "Purchase from vendor" field is blank on the template. The system will take suppliers from the Invoicing Interface
Reason Code
The user selects the reason code
Standard Purchase Code
The user sets up the method of posting the purchase invoice line, which the system will use for posting a non-card transaction that does not go to TK transactions, but goes to a purchase invoice. For fuel card transactions, the setting is set to Template mapping, and there the user must enter "sales" anyway
Do not set to the post-group template, because then they would take precedence over the settings on the vendor and on the standard purchase code.
Insert Dimension 2 – NO YES (Insert Dimension 2)
If checked, the system creates dimension 2=contract if it has not found it in the table of dimension values. E.g. after migration, not all contracts were in the table, the system does not crash by error, but adds. The danger of weeding with bad data that doesn't belong there
If unchecked and the stack row contains a contract number that is not in the dimension values, an error will be reported. It's stricter, but it doesn't weed out the Dimension Values.
...