Skip to main content

Billing Document Type Controls

Number Range: 

Internal Number Assignment :

Number ranges will be maintained in the T.Code VN01 and assign the Number range interval over here .

SAP allows only internal number range assignments for billing document
types.

SD Document Category : Billing documents will be differentiated based on the sales document category


Posting Block If you select this check box, the billing document is blocked from
posting to accounting.

Business user need to go to VFX3 and release the document manually.


Transaction Group This field is used for document control in SAP. For billing
documents, the transaction group is 7. For pro-forma invoices, it is 8.

Document Type You can specify an accounting document type that will be
linked to this billing type.

Ideally accounting document ‘RV’ will be maintained over here.

Negative Posting This field is used to control whether negative values are permitted
in the document.

Branch/Head Office This field allows you to control which partner function is
forwarded to accounting, if the payer and sold-to party are different in the sales
order. The default setting passes the payer to financial accounting.

Invoice List Type If this billing type is going to be used in invoice lists, you can
specify the type of invoice list document that can be created.

Rebate Settlement If this billing type is going to be used for settlement of
rebates, you have to specify the type of settlement in this field.


 Relevant For Rebate :

Activation of rebate can be done at sales organization level , Billing type level and Customer master data level.

 If you flag the Rel. For Rebate check box, the billing document is considered relevant for rebates.

This will be activated for regular invoices (such as F1 and F2) whereas pro-forma documents (such as F5 and F8) are not.

Comments

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...