Complete Enhancement List of Sales

Document Pricing
Thursday, October 13, 2016
10:22 AM

This is the completed of enhancement list of sales document, enhancement for

sales document have been split into following part : Standard Processing,
Material Determination, Partner Determination, Pricing, Product Selection, Text
Determination, Variant Configuration, Availability Check, Product Allocation etc.

This post will give you complete list of enhancement sales document
pricing.

1.MV45AFZZ Exit Name USEREXIT_PRICING_PREPARE_TKOMK

Note : Move additional fields into the pricing communication table (header).

2.MV45AFZZ Exit Name USEREXIT_PRICING_PREPARE_TKOMP

Note : Move additional fields into the pricing communication table (time)

3.SAPMV61A Exit Name USEREXIT_FIELD_MODIFICATION

Note : Modify the attributes of condition screen fields.

4. SAPMV61A Exit Name USEREXIT_FIELD_MODIFIC_KZWI

Note : Modify subtotal attributes of condition screen fields.

5.SAPMV61A Exit Name USEREXIT_FIELD_MODIFIC_KOPF

Note : Modify the header totals attributes of condition screen fields.

6. SAPMV61A Exit Name USEREXIT_FIELD_MODIFIC_LEER

Note : Modify the blank lines condition screen fields.

7. SAPMV61A Exit Name USEREXIT_PRICING_CHECK.

Note : Check pricing maintenance in the document

8.SAPMV61A Exit Name USEREXIT_CHANGE_PRICING_RULE

Note : Change the pricing rule

9.RV61AFZB Exit Name USEREXIT_XKOMV_BEWERTEN_INIT

Note : Initialize before loop for the pricing procedure start.

10.RV61AFZB Exit Name USEREXIT_XKOMV_BEWERTEN_END

Note : Transfer values into the pricing communication structure during pricing.

11.RV61AFZB Exit Name USEREXIT_XKOMV_ERGAENZEN

Note : Change the dynamic part of the condition records.

12.RV61AFZB Exit Name USEREXIT_XKOMV_ERGAENZEN_MANU

Note : Change the ready for input fields of the manually entered condition
records to the condition screen

13.RV61AFZB Exit Name USEREXIT_XKOMV_FUELLEN

Note : Change the work fields of the condition line ( with condition )

14.RV61AFZB Exit Name USEREXIT_XKOMV_FUELLEN_O_KONP

Note : Change the work fields of the condition line ( without condition )

15.RV61AFZB Exit Name USEREXIT_PRICING_COPY

Note : Change the KONV fields for copied price components.

BAdI Sales Document Pricing

1. SD_COND_ACCESS_A Method FILL_ACCESS_PRESTEP_ACCESS

Note : Access in Pricing for replacement.
http://www.abapgurus.com/complete-enhancement-list-sales-document/

User Exits In Sales Document Processing

This IMG step describes additional installation-specific processing in sales document processing. In
particular, the required INCLUDES and user exits are described.

Involved program components

System modifications for sales document processing affect different areas. Depending on the
modification, you make the changes in the program components provided:

MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".

MV45AOZZ

For entering additional installation-specific modules for sales document processing which are called
up by the screen and run under PBO (Process Before Output) prior to output of the screen. The
modules must start with "ZZ".

MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called
up by the screen and run under PAI (Process After Input) after data input (for example, data
validation). The modules must start with "ZZ".

MV45AFZZ and MV45EFZ1

For entering installation-specific FORM routines and for using user exits, which may be required and
can be used if necessary. These program components are called up by the modules in MV45AOZZ or
MV45AIZZ.

User exits in the program MV45AFZZ

The user exits which you can use for modifications in sales document processing are listed below.

USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales
document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during
order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the
routine BELEG_SICHERN.

USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited
together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:

Modification group 1: Automatic modification with transaction MFAW

Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed
information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you
must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.

See the Screen Painter manual for further information on structuring the interface.

USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the
section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.

USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the
section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.

USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.

USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is
described in the section "Copy customer master fields into sales document" .
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.

USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending
on the required fields. For example, if you want to define the number range depending on the sales
organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.

USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the
communication structure KOMK taken as a basis for pricing.

USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the
communication structure KOMP taken as a basis for pricing.

USEREXIT_READ_DOCUMENT

You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.

USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at
the beginning of the safety routine. This is why this indicator must also be set during the maintenance
of user-specific tables that are also to be saved.

USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the
last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.

User exits in the program MV45AFZA

USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication
structure KOMKD taken as a basis for the material determination. This is described in detail in the
section "New fields for material determination" .

USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure
KOMPD taken as a basis for the material determination. This is described in detail in the section "New
fields for material determination ".

USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure
KOMKG taken as a basis for material determination and material listing. This is described in detail in
the section "New fields for listing/exclusion".

USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure
KOMPG taken as a basis for material determination and material listung. This is described in detail in
the section "New fields for listing/exclusion".

USEREXIT_REFRESH_DOCUMENT

With this user exit, you can reset certain customer-specific fields as soon as processing of a sales
document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it
must be reset again before processing the next document so that the credit limit is not used for the
sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with
F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.

User-Exits in program MV45AFZB

USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is
not deleted (unlike in the standard system).

USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the
schedule line is not deleted (unlike in the standard system).

USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header.
The system could, for example, check whether certain shipping conditions are allowed for a particular
customer group.

USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.

USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in
the order.

USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line.
During BOM explosion, for example, you may want certain fields to be copied from the main item to
the sub-items (as for billing block in the standard system).

USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.

USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional

criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike
in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.

USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can
include new fields for text determination or fill fields that already exist with a new value.

USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include
new fields for text determination or fill fields that already exist with a new value.

User-Exits for product allocation:

The following user exits all apply to structure COBL, in which the data for account determination is
copied to item level.

USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.

USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.

USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.

USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a
certain field in the account assignment block (see also MV45AFZB).

USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)

USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard
system, the delivering plant is copied from the customer master or the customer-material info record. If
you want to use a different rule, then you must enter it in this user exit.

USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:

EBAN (purchase requisition)

EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM
can be processed and then returned to the order.

USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find
notes on the user exit in MV45AFZB.

User-Exits for first data transfer:

The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.

USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the
sales document header)

USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a
sales item)

USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a
sales document schedule line)

USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change
status).

USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).

USEREXIT_MOVE_FIELD_TO_KOMPH

You can use this user exit to include new fields for batch determination (document item).

USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g.
with a customer hierarchy)

USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item
field could be used as the precondition for pricing to be carried out again). Further information in
MV45AFZB.

USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or
price group could be set as the preconditions for the system to carry out pricing again). Further
information in MV45AFZB.

User-Exits in Program MV45AFZD

USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which
data should be used to explode the BOM (explosion with required delivery date, for example).

User exits in the program FV45EFZ1

USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line
is changed automatically if a purchase requisition is allocated, and it or the sales document is
changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in
order to protect your sales orders from being changed automatically. Use this user exit for this
purpose. Decide at this point whether the schedule lines are to be changed.

User-Exits in Program RV45PFZA

USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status).
Reserve field UVK01 could, for example, be used for an additional order status (as for rejections
status, etc.).
The following workareas are available for this user exit:

VBUK (header status)

FXVBUP (item status)

FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:

FXVBAP (Item data)

FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.

User exits in the screens

Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A
0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be
included on the Include screens for maintaining. If an application-specific check module is needed for
the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing
logic of the Include screens.
For field transports, you do not have to make changes or adjustments.

Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with
the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made
to the processing logic.

User Exits in Program MV45AFZ4

USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure KOMK- for free goods determination. For more information, see the New Fields for Free Goods
Determination IMG activity.

USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP
for free goods determination. For more information see the New Fields for Free Goods
Determination IMG activity.

User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs

EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability
segment for cross-company code sales, or whether the data comes from external billing (external
customer, sales data from the selling company code.

From
<http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/content.ht
m>

SD User exits
Skip to end of metadata

Created by Yathish K, last modified by Jyoti Prakash on Feb 11, 2013

Go to start of metadata

Purpose
This wiki page would discuss about various Userexits relevant for SAP Sales and Distribution module.

Introduction
A user exit is a place in a software program where a customer can arrange for their own tailor-made
program to be called. In R/3, some user exits use Include statements to include customer program
enhancements that are called from the program. Other user exits use tables that are accessed through
customization.
Warning
Documentation below is copied from SPRO activities documentation and SAP library :

SAP Help - User Exits in Sales Document

SAP Help - User Exits for Billing
SAP Help - Transferring new SD fields to Accounting
SAP Help - User Exits in Transportation
SAP Help - User Exits for Billing Plan

Relevant Information

CMOD

Customer Exits

Include

It is reserved for customers, for which you need a

Routines

modification key

Sales Related Exits

Customer Exits

Enhancement

Description

Code

SDAPO001

Activating Sourcing Subitem Quantity

Propagation

SDTRM001

Reschedule schedule lines without a new ATP

check

V45A0001

Determine alternative materials for product

selection

V45A0002

Predefine sold-to party in sales document

V45A0003

Collector for customer function modulpool

MV45A

V45A0004

Copy packing proposal

V45E0001

Update the purchase order from the sales order

V45E0002

Data transfer in procurement elements (PRreq.,

assembly)

V45L0001

SD component supplier processing (customer

enhancements)

V45P0001

SD customer function for cross-company code

sales

V45S0001

Update sales document from configuration

V45S0003

MRP-relevance for incomplete configuration

V45S0004

Effectivity type in sales order

V45W0001

SD Service Management: Forward Contract Data

to Item

V46H0001

SD Customer functions for resource-related

billing

V60F0001

SD Billing plan (customer enhancement) diff. to

billing plan

Include Routines

Include

Description

MV45ATZ

For entering metadata for sales document processing

MV45AO

For entering additional installation-specific modules for sales

ZZ

document processing
which are called up by the screen and run under PBO (Process
Before Output) prior
to output of the screen.

MV45AIZ

For entering additional installation-specific modules for sales

document processing.
These are called up by the screen and run under PAI (Process
After Input) after data
input (for example, data validation).

MV45AFZ

For entering installation-specific FORM routines and for using user

exits, which may

and

be required and can be used if necessary.

MV45EFZ
1

For more details see Help link above.

Billing Related Exits

Customer Exits

Enhancement

Description

code

SDVFX001

User exit header line in delivery to accounting

SDVFX002

User exit for A/R line in transfer to accounting

SDVFX003

User exit cash clearing in transfer to accounting

SDVFX004

User exit G/L line in transfer to accounting

SDVFX005

User exit reserves in transfer to accounting

SDVFX006

User exit tax line in transfer to accounting

SDVFX007

User exit: Billing plan during transfer to

Accounting

SDVFX008

User exit: Processing of transfer structures SDFI

SDVFX009

Billing doc. processing KIDONO (payment

reference number)

SDVFX010

User exit item table for the customer lines

SDVFX011

Userexit for the komkcv- and kompcv-structures

V05I0001

User exits for billing index

V05N0001

User Exits for Printing Billing Docs. using POR

Procedure

V60A0001

Customer functions in the billing document

V60P0001

Data provision for additional fields for display in

lists

V61A0001

Customer enhancement: Pricing

Delivery related exits

Customer Exits

Enhancement

Description

Code

V50PSTAT

Delivery: Item Status Calculation

V50Q0001

Delivery Monitor: User Exits for Filling Display

Fields

V50R0001

Collective processing for delivery creation

V50R0002

Collective processing for delivery creation

V50R0004

Calculation of Stock for POs for Shipping Due

Date List

V50S0001

User Exits for Delivery Processing

V53C0001

Rough workload calculation in time per item

V53C0002

W&S: RWE enhancement - shipping material

type/time slot

V53W0001

User exits for creating picking waves

VMDE0001

Shipping Interface: Error Handling - Inbound

IDoc

VMDE0002

Shipping Interface: Message PICKSD (Picking,

Outbound)

VMDE0003

Shipping Interface: Message SDPICK (Picking,

Inbound)

VMDE0004

Shipping Interface: Message SDPACK (Packing,

Inbound)

V02V0001

Sales area determination for stock transport

order

V02V0002

User exit for storage location determination

V02V0003

User exit for gate + matl staging area

determination (headr)

V02V0004

User Exit for Staging Area Determination

(Item)

Include Routines

Include

Description

MV50AF

User Exits for Delivery Processing

Z1

MV50AF

User Exit for Batch Quantity Allocation

Z2

MV50AF

LIPS-KOQUI (Picking is subject to confirmation) determination

Z3

MV50AF

The user exits in this include can be used to fill the condition tables for

ZK

material
listing and material exclusion (KOMKG and KOMPG) and product
selection (KOMKD
and KOMPD) with own data.

MV50AF

In delivery creation process for sales orders there is the possibility to

ZL

restrict the delivery

creation to some order items. If these order items are member of a
delivery group, but not
all items of this delivery group are includes in the restriction range of the
order item nubers,
you can specify in this routine what to do.

MV50AF

This user exit can be used to modify change mode of pricing screens in

ZP

delivery processing.

MV50AF

Users Exit for Batch Determination; LIPS-LGORT determination

ZZ

User Exits for Transportation

Include Routines

Include

Description

MV56AO

You can include your own modules in this program, to be processed in

ZZ

shipment processing
screens during PBO.

MV56AIZ

You can include your own modules in this program, to be processed in

shipment processing
screens during PAI.

MV56AFZ

You can include your own FORM routines in this program. They can

contain your own

adjustments for shipment processsing.

MV56AFZ

This program contains pre-defined FORM routines, in which you can

carry out your own

adjustments for transportation processing.

For additional information, see SAP Help link above.

User Exits for Price Determination

Routine

Module Pool

Include

Description

RV60AFZZ

This user exit allows you to copy additiona

or
Function
Group

USEREXIT_PRICING_PREPARE_TKOMK

SAPLV60A

pricing in the TKOMK

communication structure (header fields),
been provided in

the standard SAP system. These fields can

pricing in the

billing document. This user exit is describe

"New fields in
pricing" section.

USEREXIT_PRICING_PREPARE_TKOMP

SAPLV60A

RV60AFZZ

This user exit allows you to copy additiona

pricing in the TKOMP

communication structure (item fields), wh

been provided in the

standard SAP system. These fields can als

pricing. This user

exit is described in detail in the "New field

section.

USEREXIT_FIELD_MODIFICATION

SAPMV61A

MV61AFZA

You can use this user exit to adjust the dis

individual lines in the condition

screen by changing the display attributes

fields. This does not

include the display of subtotals. This user

in order processing.

USEREXIT_FIELD_MODIFIC_KZWI

SAPMV61A

MV61AFZB

You can change the display of subtotals in

screen by changing

the display attributes of the screen fields.

This user exit is also used in order process

USEREXIT_FIELD_MODIFIC_KOPF

SAPMV61A

MV61AFZB

You can adjust the display of subtotals in t

screen to your requirements

by changing the display attributes of the s

This user exit is also used in order process

USEREXIT_FIELD_MODIFIC_LEER

SAPMV61A

MV61AFZB

You can adjust the display of blank lines in

screen to your requirements

by changing the display attributes of the s

This user exit is also used in order process

USEREXIT_PRICING_CHECK

SAPMV61

MV61AFZA

You can install additional checks to the sta

condition lines (e.g.
maximum/minimum value).

USEREXIT_PRICING_RULE

SAPLV61A

RV61AFZA

In the standard SAP system, it is predefine

condition categories and classes
can be copied or recalculated per pricing
change the predefined standard
procedure for each pricing type.

USEREXIT_CHANGE_PRICING_RULE

SAPMV61A

MV61AFZA

You can use this user exit to change the p

has been predefined in the
copying control table in billing.

USEREXIT_XKOMV_BEWERTEN_INIT

SAPLV61A

RV61AFZB

This field is used in the formulas and there

before the loop for the pricing
procedure starts.

USEREXIT_XKOMV_BEWERTEN_END

SAPLV61A

RV61AFZB

Within a loop for the price components du

specific values can be transferred

into the communication structures in prici

processed.

USEREXIT_XKOMV_ERGAENZEN

SAPLV61A

RV61AFZB

In change mode, you can change the dyna

condition record (KONVD) that

is always redetermined (i.e. it is not stored

table KONV).

USEREXIT_XKOMV_ERGAENZEN_MANU

SAPLV61A

RV61AFZB

You can use this user exit to change the re

fields of the manually entered

condition record in add mode in the condi

USEREXIT_XKOMV_FUELLEN

SAPLV61A

RV61AFZB

This user exit is always called up during a

of all or individual price

components. You can change the work fie

condition line. However, this only

applies to conditions that have been dete

condition record.

USEREXIT_XKOMV_FUELLEN_O_KONP

SAPLV61A

RV61AFZB

This user exit is always called up during a

of all or individual price components.

You can change the work fields of the con

However, this only applies to conditions

that have been determined via a condition

may include subtotals, manually entered

conditions or conditions that have been ca

formula.

USEREXIT_PRICING_COPY

SAPLV61A

RV61AFZA

You can change the KONV fields for copied

components.

Note: as of Release 4.6A, the display of the condition screen (screen 6201) has been converted from a
full screen to a subscreen. The full screen is included in the SAPMV61A module pool, the subscreen,
however, in program SAPLV69A. Therefore, instead of MV61AFZA and MV61AFZB, the user exits
in LV69AFZZ should be used. For reference, see OSS note 313569.

User Exits for Partner Determination

Partner determination contains the following user exits for your use

User Exit

Description

EXIT_SAPLV09A

You can use this user exit to control whether an address that was entered

_001

manually
and has already been used in other documents (referenced), should be
referenced
again if it changes or whether a new address shold be created
(duplicated).

EXIT_SAPLV09A

Call up this user exit if a customer has not been maintained in the current

_002

sales area.

EXIT_SAPLV09A

Use this user exit to control the origin of partners in the partner

_003

determination procedure
(origin X, Y or Z). If X, Y, or Z has been entered in the Origin field, this
user exit is automatically
called up during partner determination.

EXIT_SAPLV09A

Use this user exit to integrate your own check in a program, that runs

_004

before the partner

is saved in the document.

For more detailed information, see the program documentation for each ofthe user exits.

User Exits For Credit Checks

If you want to carry out your own individual credit checks, that differ from those in the standard system,
you must define them in the following user exits:

User Exit LVKMPTZZ

LVKMPF

USER_CREDIT_CH

Z1

ECK1

LVKMPF

USER_CREDIT_CH

Z2

ECK2

LVKMPF

USER_CREDIT_CH

Z3

ECK3

User Exit for availability check

User exit

Include

Description

USEREXIT_AVAIL_CHECK_

MV45AFZ This user exit allows you to determine whether the system

CREDIT

should or should not

carry out an availability check after a blocked document has
been released or after
a new credit check.

User Exit for Risk Management for Receivables

User exit

Description

RVKMPU

Using this user exit, you can define new forms of

S2

payment guarantee.

User Exits for Billing Plan

User exit

Include

RV60FUS1

SAPLV60F

Description

Billing Plan: Distribute Difference

BILLING_SCHEDULE_DELTA

For milestone billing a percentage value is fully invoiced for each billing deadlin

the original item value and any later changes, you can use the user exit to dete

RV60FUS2

SAPLV60F

be stored in the final invoice or sent to the next deadline.

USEREXIT_MOVE_FIELD_TO_FPLT : This user exit allows yo

USEREXIT_MOVE_FIELD_TO_FPLA : This user exit allows yo

Billing plan: Prepare pricing

USEREXIT_PRICING_PREPARE_TKOMX

This user exit is used to copy or create an additional field in the definitive comm

The user exit is also often used to change the duration of a billing plan deadline

the following fields:

RV60FUS3

SAPLV60F

tkomp-anz_tage (Number of days in a deadline)

tkomp-anz_monate (Number of months in a deadline)
tkomp-anz_jahre(Number of years in a deadline)
tkomp-anz_wochen (Number of weeks in a deadline)

Bill. Plan: Deadline Proposal From Source

USEREXIT_DATE_PROPOSAL
In the standard release deadlines are set according to a template in the billing

for each day but you can adjust the template with the user exit so that the grid
pattern instead.
Modification report for billing plan SDFPLA02

This report enables you to update the header data for a billing plan with the res
and set in the billing plan.
In this way you can, for example, set the goods issue date as the starting date

Additions to billing plan with transaction SMOD

User exit SDVAX001

In the standard release the billing plan type is determined from the item catego

You can also use the user exit to determine the billing plan type dependent on d
User exit V60F0001
This user exit is for changing the deviating billing date (FPLT-AFDAT).

RV60FUS4

SAPLV60F

field preparation field selection for screen

RV60FUS5

This userexit can be used to split date lines TKOMK for Header fields

RV60FUST

User Part for Billing Plan - Data Definition

Additional User Exits in Billing Document

User exit

Include

Description

USEREXIT_FILL_VBRK_VBRP

RV60AFZ

Fill in the fields in VBRK/VBRP tables

USEREXIT_NUMBER_RANGE_I

RV60AFZ

Determine the number range for internal

NV_DATE

document number

RV61AFZ

User exits for printing

User Exits For Product Allocation Processing*

User exit

Include

Description

SDQUX00

Function module exit for enhanced check in SD

01

product allocation

User Exits For Availability Check

User exit

Include

Description

USEREXIT_PLANT_SELECTION

RV03VFZ

The user exits named here are planned for projects that are to be

carried out in agreement

with SAP development as they may only be used in consultation
with SAP. SAP provides no
guarantee if they are used without our advice in program is an
exception to this rule

USEREXIT_ADD_FIELD_TO_HEA

FV45VFZ

DER

USEREXIT_ADD_FIELD_TO_LINE

USEREXIT_DELIVERY_GROUPS

FV45VFZ

USEREXIT_MVERF_INIT

USEREXIT_QUOTA_KEY_VALUE

USEREXIT_AVAILABILITY_IN

RV03VFZ

This user exit is used to adjust the flow during plant transfer. A list

of permitted plants, where

USEREXIT_AVAILABILITY_OUT
this material is created, is determined and checked in the standard
USEREXIT_DARA_REFRESH

R/3 delivery. A dialog box

USEREXIT_PLANT_SELECTION

appears where you can select the plants. The user exits allow you to
modify the plant table
so that plant selection takes place in advance for every flagged
selection and a dialog box
becomes unnecessary.

User Exits For Component Supply Processing

User exit

Include

Description

USEREXIT_CHECK_VBLB-

MV45AFZ

These user exits are available for checking customer reserve fields

USR01

from VBLB-USR01 to

USEREXIT_CHECK_VBLB-

VBLB-USR05. The reserve fields are used in the component supplier

USR02

industry. The system

USEREXIT_CHECK_VBLB-

calls them in the screen flow logic for header data in forecast and

USR03

JIT delivery schedules

USEREXIT_CHECK_VBLBUSR04
USEREXIT_CHECK_VBLBUSR05

Function module V450001 is available as an SAP extension for the component supplier industry. It
contains the following user exits:

EXIT_SAPLVED4_004

General - You can use this user exit to overwrite the standard method with which the

document level or in the customer master record). You can define a special recipient f

EXIT_SAPLV45L_001

For delivery schedules - The system checks an incoming delivery schedule against
differences.

EXIT_SAPLV45L_002

For delivery schedules - With this user exit, you can change the VBLB structure (sa
delivery schedule data to the corresponding internal table.

EXIT_SAPMV45L_001

Planned delivery schedules - This user exit allows you to process schedule lines ge

EXIT_SAPMV45L_002

Planned delivery schedules - This user exit allows you to modify the calendar used

EXIT_SAPMV45A_005

For delivery orders (MAIS) - This user exit enables you to control how the system c

EXIT_SAPLVED4_001

For delivery orders (MAIS) - These user exits allow you to change the workflow par

EXIT_SAPLVED4_002
EXIT_SAPLVED4_003
EXIT_SAPLVED4_005
EXIT_SAPLVED4_006

EXIT_SAPLVED4_001

For the self-billing procedure - You can use these user exits for the standard self-b

EXIT_SAPLVED4_005
EXIT_SAPLVED4_006

EXIT_SAPLVED5_002

For the self-billing procedure -You can use these user exits for the self-billing proce

EXIT_SAPLVED5_003
EXIT_SAPLVED5_004

User Exits For Resource-Related Billing

You can use the following user exits for resource-related billing before Release 4.5A:

RV45HFZZ enhancement
USEREXIT_INV_REQ_ITEM
USEREXIT_INV_REQ_ITEM_PARTNER
You can use the following user exits for resource-related billing as of Release 4.5A:

V46H0001 enhancement
EXIT_SAPLV46H_001
EXIT_SAPLV46H_002User Exits For Billing
USEREXIT_NUMBER_RANGE (Module pool SAPLV60A, program RV60AFZZ)
The internal number range used in the standard system is specified in the billing type table and can be
changed in this user exit. This user exit is only called when the billing documents is created.

USEREXIT_ACCOUNT_PREP_KOMKCV (Module pool SAPLV60A, program RV60AFZZ)

In this user exit additional fields for account determination that are not provided in the standard system
are copied into communication structure KOMKCV (header fields).

USEREXIT_ACCOUNT_PREP_KOMPCV (Module pool SAPLV60A)

In this user exit additional fields for account determination that are not provided in the standard system
are copied into communication structure KOMPCV (item fields).

USEREXIT_NUMBER_RANGE_INV_DATE (Module pool SAPLV60A, program RV60AFZC)

Depending on the number range, table TVFKD is used to set the billing date (country-specific requirments
in Italy). USEREXIT_NUMBER_RANGE is automatically deactivated when this user exit is being applied.

USEREXIT_FILL_VBRK_VBRP (Module pool SAPLV60A, program RV60AFZC)

This user exit is only called when the billing document is created. It is used to provide the header and the
item of the new billing document with deviating or additional data.

USEREXIT_PRINT_ITEM (Module pool SAPLV61A, program RV61AFZB)

Printing the item line of a billing document can be supplemented or changed.

USEREXIT_PRINT_HEAD (Modulpool SAPLV61A, Programm RV61AFZB)

Printing the header line of a billing document can be supplemented or changed.

User exits in program RV60AFZD

Short descriptions of the user exits are contained in the program:

USEREXIT_RELI_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAK_AVBPAK
USEREXIT_NEWROLE_XVBPAP_AVBPAK
The following user exits are available in report SAPLV60B for transfer to accounting (function group
V60B):

EXIT_SAPLV60B_001: Change the header data in the structure acchd

You can use this exit to influence the header information of the accounting document. For example, you
can change the business transaction, "created on" date and time, the name of the person who created it

or the transaction with which the document was created.

EXIT_SAPLV60B_002: Change the customer line ACCIT
You can use this exit to change the customer line in the accounting document. This exit is processed once

the ACCIT structure is filled in with data from document header VBRK.
EXIT_SAPLV60B_003: Change the customer line in costing

The customer line is filled in differently for costing. You can use exit 003 to influence the ACCIT structure.
EXIT_SAPLV60B_004: Change a GL account item ACCIT You can add information to a GL

account item (such as quantity specifications) with this exit.

EXIT_SAPLV60B_005: User exit for accruals
Once all relevant data for accruals was entered in the GL account item, you can add to this data with this

exit.
EXIT_SAPLV60B_006: Change the control line ACCIT
You can use exit 006 to add information to the control line.
EXIT_SAPLV60B_007: Change the installment plan
You can use exit 007 to add information to the installment plan

parameters in the GL account item.

EXIT_SAPLV60B_008: Change the transfer structure ACCCR, ACCIT and ACCHD
After the accounting document is filled in with data, you can use exit 008 to change the document once

again.
EXIT_SAPLV60B_010: Item table for customer lines
You can use exit 10 to influence the contents of customer lines before they are created.
EXIT_SAPLV60B_0011: Change the parameter for cash account determination or
reconciliation account determination
You can use this exit to change inbound parameters in order to influence account determination. User

Exits For General Billing Interface

USEREXIT_AVBPAK_CPD (in Include RV60AFZB)

With this user exit for the general billing interface, deviating address data for different partner functions
can be copied from the interface.

USEREXIT_AVBPAK_ADD (in Include RV60AFZA)

With this user exit for the general billing interface, new partner functions can be copied from the
interface.

USEREXIT_XVBAPF_KEY (in Include RV60AFZA)

With this user exit for the general billing interface, a key field can be added in the aggregrated flow.

USEREXIT_XVBAPF_KEY_CANC (in Include RV60AFZA)

Special user exit for the general billing interface with which a key field can be added in the aggregrated
flow.
User Exits For Sales Support
In Sales Support, you can use the following SAP enhancements:

MCV2001 - Expand LIS fields for sales activities/sales promotions. This enhancement
contains the following user exit:
EXIT_SAPLMCV2_001
V43MLIS - Expand LIS fields for address lists. This enhancement contains the following user
exit:
EXIT_SAPLV43M_007
V43K0001 - Enhancement for linking to calendar. This enhancement contains the following
user exit:
EXIT_SAPLV43K_001
V43ADATA - Change sales activity data in dialog. This enhancement contains the following
user exit:
EXIT_SAPMV43A_007
User Exits For Lists

User Exits in Program RVKPR002 (Customer Expected Price)

RVKPRFZ

This allows the list structure of individual fields to be filled on

header and item levels.

RVKPRFZ

This allows the sort sequence for the first issue of the list to be

defined.

RVKPRFZ

This allows you to deposit your own user codes.

RVKPRFZ

This allows you to create your own list headings.

There are two additional user exits for listing sales documents, which influence the way in which the
communication structure is filled. These user exits do not affect the structure of the list but the way in
which the data is transferred and how the new additional fields are filled.

CUSTOMER_FILL_1
CUSTOMER_FILL_2

User Exits for Payment Cards

Include MV45AFZH contains the user exit AUTHORIZATION_VALUE_SPLIT.
You can use this user exit to initiate the system to create several authorizations in the sales order at the
same time. This might be appropriate when different shipping points are assigned to the items and
therefore several shipments will be created for a sales order.

More information can be found here:

From <https://wiki.scn.sap.com/wiki/display/ERPLO/SD+User+exits>