topic Re: User exits in Application Development and Automation Discussions

User exits

Former Member — Thu, 06 Oct 2005 02:43:01 GMT

Hello ABAPers,

So far I had not worked in user exits and I just wanted to know how the FORM routines like USEREXIT_SAVE_DOCUMENT_PREPARE (Include MV50AFZ1) etc are used and their purpose.

1. How to identify in which FORM routine should we include our custom code for some requirement.

2. How are X* and Y* tables used. How are those tables filled at runtime. And how are those used for updating the standard tables...for example I have used XVBAP once for updating VBAP.

Please suggest.

Re: User exits

Former Member — Thu, 06 Oct 2005 02:54:33 GMT

Hi Naren,

Check OSS 178328 It will answer all your queries.

Cheers.

( Dont forget to reward if answers were helpful) .

Re: User exits

Former Member — Thu, 06 Oct 2005 03:13:58 GMT

Thanks Sanjay...going thru that note. Appears informative. Points are awarded. Will get back to you if I get any doubts.

Thanks,

Naren

Re: User exits

Former Member — Thu, 06 Oct 2005 03:27:52 GMT

Hi Naren,

Specifically for MV50AFZ1 there is another consulting note 415716 which may be of help to you.

Cheers

Re: User exits

Former Member — Thu, 06 Oct 2005 04:23:13 GMT

Sanjay,

The notes have helped me a lot. But I have a question for you.

As per the notes, it is good to read index tables first and then the document tables for better performance.

For example for sales order items for material number (vbap-matnr)

Correct

select vbeln from vapma where kunde = 'xx'.

select matnr from vbap where vbeln = vapma-vebeln

and posnr = vapma-posnr.

Incorrect

select matnr from vbap where vbeln = 'xxx' and posnr = 'yy'.

What difference does those make. And how the select's using index tables are superior compared to direct select's on the document tables. Please explain.

Thanks,

Re: User exits

Former Member — Thu, 06 Oct 2005 04:52:27 GMT

Hi Naren,

I am not sure which note you are referring to .

In these exits you already have the data in YVBAP ( current database state ), XVBAP ( screen changed values in current transaction ). There is no need to fire a query to database .

Now to you question if you have the full key of VBAP ( VBELN & POSNR ) then there is no need to goto index table . But say you have the material number / sold to party only , then you can get the sales order numbers / item number from VAPMA and then do a selct from VBAP , rather than doing a select from VBAP just using MATNR.

VAPMA has no filed like KUNDE .

Cheers.

Re: User exits

Former Member — Thu, 06 Oct 2005 04:58:34 GMT

Sanjay,

Sorry for the confusion. My earlier post got some error.

Here is the note desc...I forgot the note number.

'Performance - Customer developments in SD'.

I am pasting the text below.

Symptom

Customer-specific programs and program enhancements ("User Exits") have a bad performance. The bad performance is noticed during accesses to the following SAP SD tables: VBAK, VBAP, VMVA, LIKP, LIPS, VBRK, VBRP, VBFA

Additional key words

Cause and prerequisites

The R/3 System contains no secondary indexes to the most important SD transaction data tables in the delivery. Instead, the R/3 System has proprietary index tables (sales document indexes, for example the tables VAKPA and VAPMA, matchcode tables for example M_VMVAB, M_VMVAC or matchcode views for example M_VMVAA, M_VMVAE), which allow an efficient access.

In order to use these efficiently a certain basic knowledge of the SAP data model is required. For this this note lists the most important errors which are made and it offers alternatives.

However note the following WARNINGS:

„X Before you use the listed alternatives productively, you must check your program closely for functional accuracy.

„X The sales document indexes must be maintained correctly in your system. This is usually automatically the case, however, there can be inconsistencies. Carefully read and follow Notes 128947 and 178328.

Consider the following NOTES:

In the following examples, there are often accesses to several tables, for example:

SELECT FROM vakpa WHERE kunde = ...

SELECT FROM vbak WHERE vbeln = vakpa-vbeln.

It can increase the performance, to define a selection view on the corresponding tables (here: VAKPA and VBAK) in order to combine the accesses to the two tables in one access.

Solution

1. Accesses to sales orders (tables VBAK, VBAP)

a) Search orders for customer number (field VBAK-KUNNR):

Incorrect:

SELECT FROM vbak WHERE kunnr = ...

Correct:

SELECT FROM vakpa WHERE kunde = ...

SELECT FROM vbak WHERE vbeln = vakpa-vbeln.

a) Search order items for material number (field VBAP-MATNR):

Incorrect:

SELECT FROM vbap WHERE matnr = ...

Correct:

SELECT FROM vapma WHERE matnr = ...

SELECT FROM vbap WHERE vbeln = vapma-vbeln

AND posnr = vapma-posnr

a) Other search helps for sales orders offer the matchcode tables and views M_VMVAx, x. = A, B, C, ... M; for example search for purchase order number of the customer, description and so on

Re: User exits

Former Member — Thu, 06 Oct 2005 05:16:31 GMT

Hi Naren,

This text is from note 185530 . What exactly is your problem . Do you have a performance problem.

This note actually says that if you have the customer number only and you want to select all orders for this customer , directly doing a select from VBAK where kunnr = <CUS_NUM> will take long time ( as customer is not a key here ) . Instead you can find the Sales order numbers from VAKPA using KUNDE = <CUS_NUM> ( and then selct from VBAK to get further details of sales order ) . This will be very fast as VAKPA has Customer number as first key . Similarly to read sales order items for a material first get order num / item num from VAPMA.

Hope this solves your issue.

Cheers .

Re: User exits

Former Member — Thu, 06 Oct 2005 05:44:27 GMT

Hi Naren,

USEREXIT_SAVE_DOCUMENT_PREPARE is just called before saving the documents. You can verify your business rules by calling a form written in a different include.

Usually at this point of time there will be no value updated in the tables like VBAK, VBAP..............

XV*** structure will hold the current values of the Sales Order.

YV*** structure will hold the previous values of the Sales Order.

For Example,

Sales Order is created with two line items say 10 and 20.

During the sales order change an item is added say 30.

XVBAP holds all the three line items(10, 20 and 30).

YVBAP holds only 10 and 20.

All the values in XV*** will be updated to the tables V*** repectively during COMMIT.

Using XV*** and YV*** you can determine the changes made for the sales order while change is processed.

Regards,

Baburaj

Re: User exits

Former Member — Thu, 06 Oct 2005 14:32:13 GMT

Hello Sanjay,

Thanks for the solution. You solution answers my question perfectly even though you are not familiar with my problem

Since I was not infront of my system at the time of posting the post...I couldnt figure out what kunde field is and why they are using that index table for pulling the vbeln's from vbak instead of direct select on vbak.

Thanks once again.

Re: User exits

Former Member — Tue, 20 Feb 2007 13:49:07 GMT

hi sanjay,

i m new to user exit n i have been assigned an object on enhancement.

i m sending you the requirement,if u have idea on that do help.

the requirement is.....

i have to use the include MV45AFZZ - User Exit --userexit_save_document or userexit_save_docuemnt_prepare. i need to do is to create an algorithm to create ALPHA number range . Also i need to check for exceptions from a cutom table which conatins some prohibitary words.

in more detail,The User Exit for this should be at document ‘Save’ to prevent creating numbers that do not become Sales Orders.

The field VBKD-IHREZ should be Display Only for the PM( philip morris) Document Types, only changed by the generation program update. This will be controlled through configuration of Transaction Code SHD0 - Field Display Characteristics> Configure Application Transaction Fields.

and also to have a unique 5-character alpha order number generated and retained with the sales order

thanx in advance.

Vishal.