topic Re: Mapping problem for IDOC Type DESADV in Application Development and Automation Discussions

Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 05:59:00 GMT

Dear all

I need to change Segment E1EDP07 in the message type DESADV.

I should concatenate VBELN and VGPOS into BSTNK.

I tried to do this with BD79 (Rules for Data Converting). This seems not to work as I can get only 1 sender Field.

So I tried to use the userexit EXIT_SAPLBD11_001, but it seems that this is not used. I have set a break-point for debugging and treated the IDOC with RSNAT00 without any stop.

Do you have any ideas how I can do this?

Herbert

Re: Mapping problem for IDOC Type DESADV

alex_m — Thu, 06 Aug 2009 06:11:34 GMT

Why do you want to concatenate that since you have all the values in the segment?

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 06:26:48 GMT

I also have to get some additional data and put into BSTNK so that's the receiver can use the IDOC as it's sent

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 06:49:59 GMT

Try Enhancement: V56K0001 and exit :EXIT_SAPLV56K_002.

Regards,

Mayank

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 06:52:37 GMT

ok, that stops in there. Problem only is that idoc_data is empty.... how comes?

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 07:02:27 GMT

I dont think IDOC_DATA should be empty.

please let us know how you are triggering this IDOC.

Also as you have mentioned RSNAT00 ,what is that??

I asssume you are triggering using message control..if so did you give application type and condition type to trigger it in partner profile?

Edited by: mayank verdia on Aug 6, 2009 9:03 AM

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 07:24:37 GMT

Sorry, i typed wrong. I mean report RSNAST00. I trigger my IDOC using messages.

I identified the problem now as following:

When I use in WE20 Process Code DELV, it does not step into your mentionned user exit.

When I use Process Code SD05, it steps into, but IDOC_DATA is empty and no IDOC is finally created.

Do you have any idea why?

Re: Mapping problem for IDOC Type DESADV

Jay71 — Thu, 06 Aug 2009 07:27:39 GMT

Hi,

In partner profile settings do you have an outbound process code associated with your IDOC. if yes why not create an enhancement in that process code so that you can modify the data before the idoc is distributed to the destination.

Regards,

Jayaram

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 07:27:43 GMT

Hi,

What is the function module associated with it. Which can be found from WE57 tcode.

Thanks

kamath

Edited by: Ramachandra Kamath on Aug 6, 2009 9:27 AM

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 07:29:31 GMT

hi Herbert ,

<<Copy paste from http://sap.ittoolbox.com/documents/extending-a-basic-idoc-type-18138 deleted. Points removed. Do NOT copy and paste from other sources>>

Regards

Saurabh Goel

Edited by: Matt on Aug 6, 2009 3:58 PM

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 07:34:43 GMT

Hi,

In DELVProcess code are you giving you application as V2?

try using Process code SHPM and Application as V7...

Regards,

Mayank

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 07:40:45 GMT

Yes, I have V2 for DELV.

I do not have a transport but only a shipping. That's why I think your other proposal will not work

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 07:43:26 GMT

I have 2 entries for my DWSADV01

1 with FM IDOC_INPUT_DESADV and the other with IDOC_INPUT_DESADV1

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 08:05:14 GMT


> I have 2 entries for my DWSADV01
> 
> 1 with FM IDOC_INPUT_DESADV and the other with IDOC_INPUT_DESADV1

With the first one, you cannot do much, as there is no user exit in it. But in the second one, there is a user exit when the idoc data is parsed the exit name is EXIT_SAPLV55K_004 and is called in the subroutine DESADV_IDOC_PARSE in the function.

But please note that the function IDOC_INPUT_DESADV1 is used with process code DELS for message type DESADV and Idoc type DELVRY01 and IDOC_INPUT_DESADV is used with process code DESA and message type DESADV with IDoc type DESADV01. So you might be using IDOC_INPUT_DESADV function and unfortunately there are no user exits to handle your requirement.

My advice would be to check with the source system or the middleware to define the mapping of these fields according to your requirement. But if that is not possible, then you need to first check which message type and IDoc type you are receiving and proceed accordingly

KR,

Advait

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 13:43:35 GMT

Hi,

R u able to solve the issue?

If yes,Please let community know what went wrong and why idoc_data was not coming?

Regards,

Mayank

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 13:55:13 GMT

Unfortunatly not yet, i'm still investigating

Re: Mapping problem for IDOC Type DESADV

Former Member — Thu, 06 Aug 2009 18:51:07 GMT

Hi,

Hv you tried creating a new Delivery and put a break point in the exit instead of triggering from nace transaction.

Is there any condition type for which data will be populated ?

I am not sure but assuming ,i too encounter this issue in SHPMNT05 O/B idoc.

Regards,

Mayank