Special Features for Self-Billing (SAP Library - Scheduling Agreements for Component Suppliers (SD-SLS-OA))

Special Features for Self-Billing

There is a variety of billing methods which your customer can use to settle business transactions. With the special self-billing features, you can make settings to run specific checks on incoming self-billing documents sent to you by EDI by a particular customer.

These billing features are similar to those for standard delivery schedules. They allow you to define how self-billing documents are to be processed for each sold-to party or combination of sold-to party/unloading point. You can:

Activate test runs for incoming EDI self-billing documents

Make settings for self-billing

This includes:

Defining sales document types for credit and debit memo requests that the system creates when it receives a self-billing document from the customer requiring a credit or debit to the customer's account.

In the standard system, sales document type G2 is for credit memo requests and L2 for debit memo requests.

Activating a special rule for an automobile manufacturer

You can use this field to refer to any of the various user exits that you program for EDI processing. The system will then take the user exits into account when processing billing documents for the automobile manufacturer that you designate.

Specifying whether an employee should be notified if general texts are sent in a billing document

Make settings for self-billing with invoice creation

This includes:

Defining billing document types for invoices, and credit memos sent in by the customer to correct quantity differences
Defining retro-billing document types for credit and debit memos sent in by the customer to correct prices
Specifying whether an invoice is to be created for every external invoice sent in by the customer

The system normally creates an invoice in the R/3 System exactly as it is received from the customer. This may not always be possible, for example when there are items not relevant for billing, or when the document requires an invoice split. In these cases, the system does not create an invoice.

By setting this indicator, you can create invoices for testing purposes even in those circumstances when the system normally would not.

Specifying the default values of an invoice in case the system cannot determine this information from the delivery, or other internal referenced document, referred to in the intermediate document (IDoc)

Assign external conditions to internal conditions

For only those conditions that you enter here, the system compares the value of the internal condition with that of the external condition sent in the external invoice.

You can specify that the system should take these differences into account by setting the related indicator. If there are differences in these values, the system updates the IDoc status records and sends a mail to inform you. It continues processing the IDoc and, if no serious errors occur, creates the invoice anyway. This function is only available for the self-billing procedure with invoice creation.

With user exit EXIT_SAPLVED5_003, you can design your own tolerance checks.

Define tolerance levels for differences between external and internal conditions

In the standard self-billing procedure, the system compares the values in the credit advice with those in the existing internal invoice. If the system finds any differences in these values, it terminates processing.

With this function you can define differences that the system tolerates. In this case, even if the system determines differences in the external and internal condition values, it ignores them and continues processing the IDoc.