User exits for sales document line item

[Former Member]

Hi,

While creating the contract in the line item one field product hierarchy is a mandatory field.In our project we maintain upto 3rd level but if user main upto first level only in the sales consystem is not throwing an error while saving the contract.Now through user exit we want to throw an error message if product hierarchy field is not maintained upto 3rd level.

Anybody please tell which user exit shall i use or in which user exit VBAP table hits?

I gone through IMG documenation in SD--User exit but not getting clarity.

Regards,

SATYA

[Former Member]

raise it to abap general

[Former Member]

You may use the following user exit

ProgramID: MV45AFZZ

FORM USEREXIT_MOVE_FIELD_TO_VBAP.

I use it like this:

FORM USEREXIT_MOVE_FIELD_TO_VBAP.

if VBAP-ARKTX is initial.

VBAP-ARKTX = 'General Item'.

endif.

ENDFORM.

*So if there is no description for the material, the text 'General Item' will be given.

Let me know whether this can solve your problem.

Ken

[Former Member]

Hi Ken,

Thanks for your reply.

But, it does not solve my problem.

Since this is a standard Program I am unable to make changes into it.

If you can please suggest How you were able to make changes into it?

Or, if there is some other relevant User Exit for this which refers to a Contract Line Item

i.e. for the table VBAP.

Regards

Satya

[former_member204513]

Dear Satya,

Take help of ABAPer to identify the usefull user exit.

Try with these User exits which are belongs to the Contract processing.

User Exits For Contract Processing

The following SAP enhancement is available in sales processing:

o V45W0001 Function module exit for copying sales header data into

items.

This enhancement contains the user exit:

- EXIT_SAPLV45W_001

Activities

1. Create your enhancement, using a project. You can either use an

existing one or create a new one.

Supplement the coding delivered by SAP. SAP provides you with the

necessary function modules with short texts, interface and

documentation.

2. Activate the project.

The ABAP coding will only run once the project has been activated.

Until then the enhancements will not take effect.

Further notes

In contrast to modifications, enhancements can be used in any release.

This is because they are defined in your own system and not in the SAP

original system. You can find the documentation about the enhancement by

activating the "SAP docu" key in the enhancement transaction.

I hope this will help you,

Regards,

Murali.

[Former Member]

We already checked that user exit but it is solving our problem.That user exit takes us to VEDA table but we want a user exit which goes to VBAP.

Thanks for the response.

Regards,

SATYA