Objectives
A SAPscript form is allocated to the SAP Utilities application form. In the SAPscript form, you determine the layout of the application form (for example, paragraphs, windows, page windows).
Standard SAP texts can be allocated to the individual hierarchy levels. Literals and variables are stored in these standard texts.
The SAP Utilities application form is used to generate an executable print program, which is called from the application.
The document level (DOC_HEADER) and item level (DOC_ITEM) are the two most important levels in the bill form. Fields such as customer ID, bill number, and due date are available at this level. The item level is run once per billing line item (loop).
In addition to the above-mentioned levels, there are 1:1 levels. These contain additional information such as contract account data or contract data.
One or more text elements can be assigned to each level. These text elements contain user-defined texts (text literals) or fields (variables) that are filled with actual data at runtime.
The billing form can be displayed in various ways:
Consumption and amount determination are split up
Presented without groups
Bill line items sorted according to divisions and contract number
Bill line items are sorted according to meter number
With a cover page, detailed description on the following slides
The print workbench can model any of these requirements. The next few slides will describe how to sort bill line items according to certain criteria.
The print documents created in invoicing are then processed using a print report. The output of the print report are the printed bills.
Shipping control allows you to define options for sending correspondence. For example, you can specify that two copies of a document are to be printed, or that one copy is to be printed and another copy is to be sent by e-mail.
The payment form number is an internally assigned, unique number that can be allocated to a payment form and that cash payer can use to pay the bill.
The payment form number is allocated regardless of whether a payment form is created during bill printout.
It is saved in the field NRZAS in the print document header.
The payment form number determines which open items are paid with the payment form.
You can select these open items using the payment form number, for example in the cash desk.
Invoicing allocates payment scheme numbers only for cash payers and for bill requests.
You make the Customizing settings for the payment medium in Financial Accounting (FI). You will find the relevant activities under Financial Accounting Global Settings à Correspondence à Attached Payment Media.
You can define a FORM ID for each country. The system also specifies a function module that formats the payment medium for a specific country (for example, for DE = PAYMENT_MEDIUM_DE_BANKTRANSFER).
In a further activity, you must specify an SAPscript form for the company code and FORM ID that will be used to print the attached payment medium.
For IS-U invoicing, you must assign the FORM ID you want to use to the company code in posting area R401. Invoicing then includes the FORM ID in documents when the following conditions are met:
A FORM ID is defined in the relevant company code
The contract account to be invoiced is a cash payment account
The invoice relates to an outstanding receivable
When these conditions have been fulfilled, the FORM ID field is inserted in the print document and invoice printing generates a payment medium in addition to the invoice.
A payment form number is also generated for the payment medium. This number can also be specified on the note to payee. The number range must be defined.
Sort all billing line items according to presort key (ascending).
Sort according to VAT code within a presort group (ascending).
Call each sort module in order to create blocks, for example, according to contract.
Calculation of subtotal (SUBTOTAL) according to Customizing settings.
All billing line items (cross-document) are sorted according to presort key (ERCHZ line sort) and divided into groups with the same presort key.
Within these groups, items are sorted again based on VAT codes (ERCHZ-MWSKZ). The resulting groups are then transferred to the separate sort modules. Items are then further sorted within the sort module according to contract, company code or customer-specific, for example.
Depending to the Customizing settings, a sub total line item (SUBT) is also generated in the sort module.
In the previous example, two electricity contracts are assigned to a contract account. In the billing schema, presort key 0001 is assigned to the info lines. Presort key 0002 is assigned to the invoice lines that are relevant for posting.
In Customizing for the presort keys, the function module ISU_BILL_TYPE_CONTRACT is assigned to both key 0001 and key 0002. This function module sorts the invoice lines according to the contract number.
In the first step, the invoice lines are sorted according to the presort key. This means that invoice lines with presort key 0001 come before invoice lines with presort key 0002.
The user cannot change this sorting. It can only be influenced by the definition of the applicable presort keys
In the second step, the invoice lines are sorted according to the logic in the function module. In this case, the invoice lines are sorted according to contract number. This sorting is done by the function module ISU_BILL_TYPE_CONTRACT.
In the third step, subtotals are added. Customizing for presort key 0002 specifies that a subtotal is generated. The system recognizes a control break for the contract and inserts special subtotal rows in the print document.
For each billing schema, there must be at least one invoice line with a presort key that generates a subtotal.
The aim of the presort keys is to ensure that the invoice lines appear in the print document in the exact order in which they are to be printed. Resorting at a later stage in invoice printing is time- consuming and could even result in errors (for example, when creating several subtotals in invoice printing).