SD Docs Bapis Badis & User Exits

Activating Sourcing Subitem Quantity Propagation

Reschedule schedule lines without a new ATP check

Determine alternative materials for product selection

Predefine sold-to party in sales document

Collector for customer function modulpool MV45A

Copy packing proposal

Update the purchase order from the sales order

Data transfer in procurement elements (PRreq., assembly)

SD component supplier processing (customer enhancements)

SD customer function for cross-company code sales

Update sales document from configuration

MRP-relevance for incomplete configuration

Effectivity type in sales order

SD Service Management: Forward Contract Data to Item

SD Customer functions for resource-related billing

SD Billing plan (customer enhancement) diff. to billing plan

For entering metadata for sales document processing

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.

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).

For entering installation-specific FORM routines and for using user exits, which may 
be required and can be used if necessary.

User exit header line in delivery to accounting

User exit for A/R line in transfer to accounting

User exit cash clearing in transfer to accounting

User exit G/L line in transfer to accounting

User exit reserves in transfer to accounting

User exit tax line in transfer to accounting

User exit: Billing plan during transfer to Accounting

User exit: Processing of transfer structures SD-FI

Billing doc. processing KIDONO (payment reference number)

User exit item table for the customer lines

Userexit for the komkcv- and kompcv-structures

User exits for billing index

User Exits for Printing Billing Docs. using POR Procedure

Customer functions in the billing document

Data provision for additional fields for display in lists

Customer enhancement: Pricing

Delivery: Item Status Calculation

Delivery Monitor: User Exits for Filling Display Fields

Collective processing for delivery creation

Collective processing for delivery creation

Calculation of Stock for POs for Shipping Due Date List

User Exits for Delivery Processing

Rough workload calculation in time per item

W&S: RWE enhancement - shipping material type/time slot

User exits for creating picking waves

Shipping Interface: Error Handling - Inbound IDoc

Shipping Interface: Message PICKSD (Picking, Outbound)

Shipping Interface: Message SDPICK (Picking, Inbound)

Shipping Interface: Message SDPACK (Packing, Inbound)

Sales area determination for stock transport order

User exit for storage location determination

User exit for gate + matl staging area determination (headr)

User Exit for Staging Area Determination (Item)

User Exits for Delivery Processing

User Exit for Batch Quantity Allocation

LIPS-KOQUI (Picking is subject to confirmation) determination

The user exits in this include can be used to fill the condition tables for material 
listing and material exclusion (KOMKG and KOMPG) and product selection (KOMKD 
and KOMPD) with own data.

In delivery creation process for sales orders there is the possibility to 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.

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

Users Exit for Batch Determination; LIPS-LGORT determination

You can include your own modules in this program, to be processed in shipment processing 
screens during PBO.

You can include your own modules in this program, to be processed in shipment processing 
screens during PAI.

You can include your own FORM routines in this program. They can contain your own 
adjustments for shipment processsing.

This program contains pre-defined FORM routines, in which you can carry out your own 
adjustments for transportation processing.

USEREXIT_PRICING_PREPARE_TKOMK

RV60AFZZ

This user exit allows you to copy additional fields for pricing in the TKOMK 
communication structure (header fields), which have not been provided in 
the standard SAP system. These fields can also be used for pricing in the 
billing document. This user exit is described in detail in the "New fields in 
pricing" section.

USEREXIT_PRICING_PREPARE_TKOMP

RV60AFZZ

This user exit allows you to copy additional fields for pricing in the TKOMP 
communication structure (item fields), which have not been provided in the 
standard SAP system. These fields can also be used for pricing. This user 
exit is described in detail in the "New fields in pricing" section.

USEREXIT_FIELD_MODIFICATION

MV61AFZA

You can use this user exit to adjust the display of individual lines in the condition 
screen by changing the display attributes of the screen fields. This does not 
include the display of subtotals. This user exit is also used in order processing.

USEREXIT_FIELD_MODIFIC_KZWI

MV61AFZB

You can change the display of subtotals in the condition screen by changing 
the display attributes of the screen fields. 
This user exit is also used in order processing.

USEREXIT_FIELD_MODIFIC_KOPF

MV61AFZB

You can adjust the display of subtotals in the condition screen to your requirements 
by changing the display attributes of the screen fields. 
This user exit is also used in order processing.

USEREXIT_FIELD_MODIFIC_LEER

MV61AFZB

You can adjust the display of blank lines in the condition screen to your requirements 
by changing the display attributes of the screen fields. 
This user exit is also used in order processing.

USEREXIT_PRICING_CHECK

MV61AFZA

You can install additional checks to the standard checks of condition lines (e.g. 
maximum/minimum value).

USEREXIT_PRICING_RULE

RV61AFZA

In the standard SAP system, it is predefined which condition categories and classes 
can be copied or recalculated per pricing type. You can change the predefined standard 
procedure for each pricing type.

USEREXIT_CHANGE_PRICING_RULE

MV61AFZA

You can use this user exit to change the pricing type that has been predefined in the 
copying control table in billing.

USEREXIT_XKOMV_BEWERTEN_INIT

RV61AFZB

This field is used in the formulas and therefore initialized before the loop for the pricing 
procedure starts.

USEREXIT_XKOMV_BEWERTEN_END

RV61AFZB

Within a loop for the price components during pricing, specific values can be transferred 
into the communication structures in pricing to be further processed.

USEREXIT_XKOMV_ERGAENZEN

RV61AFZB

In change mode, you can change the dynamic part of the condition record (KONVD) that 
is always redetermined (i.e. it is not stored in database table KONV).

USEREXIT_XKOMV_ERGAENZEN_MANU

RV61AFZB

You can use this user exit to change the ready-for-input fields of the manually entered 
condition record in add mode in the condition screen.

USEREXIT_XKOMV_FUELLEN

RV61AFZB

This user exit is always called up during a redetermination of all or individual price 
components. You can change the work fields of the condition line. However, this only 
applies to conditions that have been determined via a condition record.

USEREXIT_XKOMV_FUELLEN_O_KONP

RV61AFZB

This user exit is always called up during a redetermination of all or individual price components. 
You can change the work fields of the condition line. However, this only applies to conditions 
that have been determined via a condition record. This may include subtotals, manually entered 
conditions or conditions that have been calculated with a formula.

USEREXIT_PRICING_COPY

RV61AFZA

You can change the KONV fields for copied price components.

You can use this user exit to control whether an address that was entered 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).

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

Use this user exit to control the origin of partners in the partner 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.

Use this user exit to integrate your own check in a program, that runs before the partner 
is saved in the document.

USER_CREDIT_CHECK1

USER_CREDIT_CHECK2

USER_CREDIT_CHECK3

USEREXIT_AVAIL_CHECK_CREDIT

This user exit allows you to determine whether the system should or should not 
carry out an availability check after a blocked document has been released or after 
a new credit check.

Using this user exit, you can define new forms of payment guarantee.

SAPLV60F

Billing Plan: Distribute Difference 

• BILLING_SCHEDULE_DELTA 
  For milestone billing a percentage value is fully invoiced for each billing deadline. In the case of deviations between 
  the original item value and any later changes, you can use the user exit to determine whether the difference should 
  be stored in the final invoice or sent to the next deadline.
• USEREXIT_MOVE_FIELD_TO_FPLT : This user exit allows you to create your own fields in table FPLT.
• USEREXIT_MOVE_FIELD_TO_FPLA : This user exit allows you to create your own fields in table FPLA.

SAPLV60F

Billing plan: Prepare pricing 

• USEREXIT_PRICING_PREPARE_TKOMX 
  This user exit is used to copy or create an additional field in the definitive communication structure for pricing. 
  The user exit is also often used to change the duration of a billing plan deadline. You can do this by overwriting 
  the following fields: 
  
  • 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)

SAPLV60F

Bill. Plan: Deadline Proposal From Source 

• USEREXIT_DATE_PROPOSAL 
  In the standard release deadlines are set according to a template in the billing plan. This grid entry list sets the deadlines 
  for each day but you can adjust the template with the user exit so that the grid entry list could, for example, follow a monthly 
  pattern instead. 
  Modification report for billing plan SDFPLA02 
  This report enables you to update the header data for a billing plan with the result that new billing plan deadlines are determined 
  and set in the billing plan. 
  In this way you can, for example, set the goods issue date as the starting date for the billing plan. 
  Additions to billing plan with transaction SMOD
• User exit SDVAX001 
  In the standard release the billing plan type is determined from the item category of the sales document and set in the billing plan. 
  You can also use the user exit to determine the billing plan type dependent on data from the order header, order item, etc.
• User exit V60F0001 
  This user exit is for changing the deviating billing date (FPLT-AFDAT).

SAPLV60F

field preparation field selection for screen

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

User Part for Billing Plan - Data Definition

USEREXIT_FILL_VBRK_VBRP

Fill in the fields in VBRK/VBRP tables

USEREXIT_NUMBER_RANGE_INV_DATE

Determine the number range for internal document number 
User exits for printing

SDQUX0001

Function module exit for enhanced check in SD product allocation

USEREXIT_PLANT_SELECTION

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_HEADER 
USEREXIT_ADD_FIELD_TO_LINE

USEREXIT_DELIVERY_GROUPS 
USEREXIT_MVERF_INIT 
USEREXIT_QUOTA_KEY_VALUE

USEREXIT_AVAILABILITY_IN 
USEREXIT_AVAILABILITY_OUT 
USEREXIT_DARA_REFRESH 
USEREXIT_PLANT_SELECTION

This user exit is used to adjust the flow during plant transfer. A list of permitted plants, where 
this material is created, is determined and checked in the standard R/3 delivery. A dialog box 
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.

USEREXIT_CHECK_VBLB-USR01 
USEREXIT_CHECK_VBLB-USR02 
USEREXIT_CHECK_VBLB-USR03 
USEREXIT_CHECK_VBLB-USR04 
USEREXIT_CHECK_VBLB-USR05

These user exits are available for checking customer reserve fields from VBLB-USR01 to 
VBLB-USR05. The reserve fields are used in the component supplier industry. The system 
calls them in the screen flow logic for header data in forecast and JIT delivery schedules