Show TOC

User Exits For Component Supply Processing

User Exits in Programm MV45AFZC

The following 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:

Extensions using transactions SMOD and CMOD

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

General

You can use this user exit to overwrite the standard method with which the system determines the recipient of messages (either at sales document level or in the customer master record). You can define a special recipient for an incoming document that has just been processed.

For delivery schedules

The system checks an incoming delivery schedule against the current/old delivery schedule to determine if there are any differences.
The user exit is called up at the end of this standard tolerance check at which time you can process or change data.
With this user exit, you can change the VBLB structure (sales document: delivery schedule data), before the system copies delivery schedule data to the corresponding internal table.

Planned delivery schedules

This user exit allows you to process schedule lines generated automatically in a planning delivery schedule.
This user exit allows you to modify the calendar used in a delivery schedule split.

For delivery orders (MAIS)

This user exit enables you to control how the system copies packing proposals into the outbound delivery order.

For workflow

These user exits allow you to change the workflow parameters for processing inbound EDI messages.

For the self-billing procedure

You can use these user exits for the
standard self-billing procedure .
You can use these user exits for the self-billing proceure with invoice creation.

Activities

1. To enhance a program according to your specific requirements, you can either use an exisiting project or create a new one.
Add to the coding in the standard system. We provide you with the necessary function modules with short texts, interfaces and documentation.
2. Activate the project.
This triggers the ABAP coding. If you do not activate the project the extension will not work.

Further Notes

Unlike modifications, extensions are suitable for all releases because you do not change SAP coding. Rather, you write coding in your own program.

For a more detailed description of how to create an extension, see the "Extension of SAP Transactions" documentation (choose Help --> Online help in the extension transaction).