Self Billing Procedure in SD is the counter part of MM Invoicing through ERS (Evaluated Receipts Settlement)
When the customer receives a delivery from you, they price the materials based on:
- Prices from the customer’s purchasing department
- Differences between the delivery note and goods receipt
- Differences due to the quality of the material, for example
- Retroactive price adjustments
The customer uses materials and prices to prepare an invoice on your behalf that they send to you by Electronic Data Interchange (EDI). The system receives and converts this invoice into intermediate document (IDoc) GSVERF. It then forwards it to function module IDOC_INPUT_SBINV, which determines the reference delivery and items based on the internal delivery number, or external delivery number, sent in the external invoice.
In this self-billing procedure, you cannot create an invoice for the delivery: no original invoice exists. However, the system simulates invoice creation to determine internal prices and their conditions.
Once the system has determined the reference delivery, and simulated an invoice, it compares condition values in these documents to those in the external invoice (in IDoc form). The system compares only those conditions specified in the IDoc and entered in Customizing.
If the values in the external invoice match the values in the simulated invoice, and the delivery, the system creates an invoice in the R/3 System exactly as the customer has prepared it. Note that the system does not use the standard billing transaction here, but rather a special billing interface (GN_INVOICE_CREATE). The external invoice number, in the External number field, is used in the settlement process.
If the system finds any differences in the values, it updates the IDoc status records, and sends a mail to the employee responsible. It continues processing the IDoc and, if no serious errors occur, creates the document anyway. The employee then informs the customer to send one of the following correction or retro-billing documents:
- Credit memos for quantity corrections
- Credit and debit memos for price corrections in retroactive billing
- Cancellation documents
The system determines the invoices for these documents, along with the related deliveries, credit and debit memos, and cancellation documents.
If the values in the external credit memo (quantity correction) match the values in the invoice, and delivery, the system automatically creates a credit memo exactly as the customer has prepared it.
Credit or debit memo requests based on return deliveries, are treated just as credit memo requests for quantity corrections, except that the system carries out pricing only for those materials that are returned. Also, instead of comparing each condition value, the system determines an overall difference per item and compares it to the overall correction value.
In the case of retro-billing, the system reprices all documents in the transaction before comparing the condition values of the items. It calculates the difference between the old and new prices in the invoice and delivery, and enters it into condition PDIF to use in the pricing procedure. The difference calculated by the customer in the credit or debit memo is entered in the internal condition that you have assigned in Customizing. If these values match, the system automatically creates the credit or debit memo.
If these values do not match, the system sends a mail to the employee responsible, but creates the document anyway. If you do not want this, make the appropriate settings in Customizing for the sales document type.
Self Billing procedure through EDI has process if the customer sends the vendor self-billing documents per EDI, they can be read and processed automatically by the vendor system. EDI processing enables a high level of automation and a low error count.
As a rule, the SAP system controls exchange of messages with other systems by means of logical messages. The message type for transmission of self-billing documents is SBWAP (Self Billing With Automatic Postings). The process code for this transaction is SBAP. This process code must be assigned to the partner profile. A partner profile is required for each partner involved in the process.
Some of important Notes on this topic are: