Skip to Content
0
Former Member
Feb 25, 2009 at 09:43 PM

Updating commuication structure in VMC based Requirement User Exit

39 Views

Hi,

would anyone know what would be the right way to missuse the Requirement User Exits in the VMC based Pricing User Exits?

And now to clarify: In erp where the User Exits are written in good ol' ABAP there are at times situations where instead of returning a boolean value from the Requirements user exit there is instead just an update of the communication structure taking place and the User Exit always returns true.

In my humble opinion this is not quite what Requirements user exits are for, but can't change that so have to live with it 😊

In CRM when we use the new User Exit model (VMC based) our Requirements method signatures gives us access to classes which only allow us to read attributes from the communication structure through the nice abstraction layer (which I think is a good model if you want in the future to run the same user exits in both ERP and CRM).

My challenge: I can't, in the Requirements user exit update the attributes (communication structure).

My guess is that we have three ways how to update the communication structure:

1. In a BADI, which would happen I assume before the User Exits are invoked.

2. Updating the various objects we have access to in any given user exit (which obviously have logical names so at times a bit of a hit and miss when trying to find a value that matches the oh so complex ERP communication structure names).

3. Using the methods that update the attributes in the communication structure.

For this specific case I would like to change the distribution channel in the Requirements user exit.

Any (good) ideas?