‎2007 Dec 12 6:35 PM
Hi everybody!
I need to change the IDOC_INPUT_ORDERS standard behavior, so I've copied
the VEDA function group to a new group and created the new ZIDOC_INPUT_ORDERS function module (with no changes made yet!).
However there is a problem when my new function module is executed: it does not call the exit EXIT_SAPLVEDA_001 from within, while if I run the standard one it calls!
(tested with inbound idoc processing)
Do I have to make any additional steps (activation or other) to force the standard exit to be called from my new z function module? Or is this an ABAP bug?
My version is SAP 4.7.
Thanks all!
Manuel Dias
‎2007 Dec 13 10:40 AM
hi manuel,
i have seen your question, in that you specified that IDOC_INPUT_ORDERS standard behaviour is copied to ZIDOC_INPUT_ORDERS, and while copying you have to copy all the include programs and exits like EXIT_SAPLVEDA_001 TO ZEXIT_SAPLVEDA_001, and so you cant call the exit EXIT_SAPLVEDA_001. hope this could work and let me know it doesn't work
Reward if useful
‎2007 Dec 12 7:56 PM
where r u attaching this FM in ur ALE settings??
u need to attach ur FM in
ALE conf.s check it whether do u have access to ALE setting?
‎2007 Dec 13 10:18 AM
I've already configured all the ALE setting, including a new inbound process code,
function module activation in BD51, etc.
When I test an inbound idoc in WE19, it works correctly: it calls my
ZIDOC_INPUT_ORDERS. The only problem is that if I specify the standard IDOC_INPUT_ORDERS to process the IDOC it call correctly the user exit but if I call
my custom ZIDOC_INPUT_ORDERS function module, the exit is not executed (during
debug it just skips the CALL CUSTOMER-FUNCTION '001' ).
Is this standard in ABAP? I mean: is it possible that each SAP exit is associated
internally with a specific and standard function module or report?
Regards,
Manuel Dias
‎2007 Dec 13 10:40 AM
hi manuel,
i have seen your question, in that you specified that IDOC_INPUT_ORDERS standard behaviour is copied to ZIDOC_INPUT_ORDERS, and while copying you have to copy all the include programs and exits like EXIT_SAPLVEDA_001 TO ZEXIT_SAPLVEDA_001, and so you cant call the exit EXIT_SAPLVEDA_001. hope this could work and let me know it doesn't work
Reward if useful
‎2007 Dec 13 12:27 PM
Hi Manikantha,
Thats one of the possibilities, however the standard exit defined in EXIT_SAPLVEDA_001
is quite extensive because it is changed by several different partners.
I could copy it to another function module, but then I will have to maintain manually both
function modules. A better solution I have is to change the CUSTOMER_FUNCTION_IDOC
form from CALL CUSTOMER-FUNCTION '001' to
CALL FUNCTION 'EXIT_SAPLVEDA_001' directly.
The issue is: both are not a very good solution because I can't use standard exits management procedure (activation, deactivation, etc) and I was wondering if this is normal when copying standard ABAP code with exit calling inside? (if it is, I will reward you)
Regards,
Manuel Dias
‎2007 Dec 13 12:45 PM
Hi Manuel,
IDOC_INPUT_ORDERS is in function group VEDA. By copying it to Z... it now resides in another function group, let me call it ZCUS as example.
that means that the user exits EXIT_SAPLVEDA_001 in enhancement VEDA0001 are no longer connected to CALL CUSTOMER-FUNCTION 001 in your code.
if I remember correctly, you need to copy function EXIT_SAPLVEDA_001 to EXIT_SAPLZCUS_001, then make this new function known in transaction SMOD, enhancement VEDA0001. Then you can activate this new user exit in transaction CMOD. I did that a few years ago and it worked, so it might point you in the right direction.
Cheers
Thomas
‎2007 Dec 13 10:28 PM
Hello Thomas,
I didn't know I could create a new enhancement for the new exit type and associate it with a new function module.
Strangely, I cannot do it in SAP 4.7 version (???) but tried in another SAP version (4.6)
and it allow me to do so.
Thanks,
Manuel Dias
‎2007 Dec 14 8:43 AM
Hi again,
it was indeed 4.6C where I did that, so it is strange that 4.7 would not allow that, I will have a look.
Thanks
Thomas