extended idoc not populating(urgent)

[Former Member]

hi guys

i have extended the basic idoc type delvry03 and created an extension delvrtext for it.however when i trigger the idoc from an output type the extended segments are not populated.is there a way you can put a break point in the code.if that is possible it will help me a lot.i am using the FM idoc_output_delvry to create this.i tried putting break points in rsnasted as well as the above FM but it doesnt stop and the idoc gets created.please tell me how do i make sure my code for populating the extended segments is running properly.

please reply as soon as possible.thanks for your time and help.

[Former Member]

Hi Sanket,

may be put a breakpoint in master_idoc_distribute... see the call stack to see what FMs are actually being called to create the idoc and put a break point appropriately.

PS: Reward points for useful answers.

Prabhu.

[Former Member]

Did you assign the extension to the application object? Your message type, IDoc type, extension should be tied to IDOC_OUTPUT_DELVRY for the outbound direction.

Next to check this in debugging, you need to create the output with the option 'Process in batch' instead of 'Process immediately'. That way an entry will be created in NAST table. Then you can run RSNAST00 for your output type, object(internal format of delivery number), etc. Now your the execution will stop at the breakpoints you set in IDOC_OUTPUT_DELVRY.

Let us know how it goes.

Srinivas

[Former Member]

hi guys.

thanks for the reply first of all.srinivas what do u mean by assign the extension to application object?i have done the configuration in we82 where i have attached the basic idoc type and extension to message type desadv. the function module is attached to the process code which is used in partner profiles for the idoc processing.can u explain me in detail.the idoc standard idoc is getting created but not the extended segments.also there is this weird message when i run a check on the partner profiles as follows

Entry XIDCLNT300/LS/LS/DESADV /

Message Control entry exists for this entry

Port exists

Basic type exists

Extension exists

<b><u> Combination of basic type and extension is not possible</u></b>

Link exists between logical message and IDoc type

what does this mean any idea?

once this check is done probably i can go and do the breakpoints.i just have a feeling that i am missing some small thing here.

please let me know

thanks

[Former Member]

Please ignore the assignment part of it. You seems to have done everything correctly. In your partner profile, try it by removing the extension. Your extended segments will not automatically be filled(or created) unless you fill them up and include them in the IDoc. IDoc display shows only the segments that are filled.

To fill the segments, choose an appropriate user exit and fill it.

Srinivas

[Former Member]

Sanket,

Within the standard, outbound FM for this application (most likely IDOC_OUTPUT_DELVRY), you will find a subroutine called "CUSTOMER_FUNCTION_002". This routine links to a user exit ZXTRKU02 which you need to created and use to populate your extension whenever the idoc is processing the extended segment name

(i.e.

IF SEGNAM = ZE1EDL26.

move: 'XYX123' to ZE1EDL26-POSNR.

ENDIF.

)

Does this make sense?

[Former Member]

Sanket, please reward and close this post if answered. It is not encouraging for people who try to help you, if you keep the post hanging in there without any resolution or a 'thank you'. If it is not answered, let the forum know about it or if you solved it yourself, close the thread.

Srinivas

[Former Member]

hi guys

i am still not done with the issue but yes without your help i wouldnt have reached here.i assigned points to you guys for your help.how do i close the post?is there a link for that or is it just me saying that its done..

please let me know.

thanks

[Former Member]

Hi Sanket,

If your issue is still not solved, you don't need to close. What I requested you was to continue the dialog until it is resolved. Are you still not able to fill the cutom segment fields? Did you try all the suggestions given here?

Please let us know where you are at with this issue. If you want to close this, there should be a button next to your original post that says 'Solved by me' or something like that. If someone in the forum helped you to resolve it, then you can select the 'Solved Problem' button next to the response that helped you.

Hope it helps

Srinivas

[Former Member]

oh ok i got it.

i am stuck at this silly thing.yes what i was looking for with the idoc,i am able to populate the segments now but this one small thing will solve it completely.can someone tell me where to get the delivery number in the user exit from?my whole logic uses the delivery number and i tested it by hardcoding.now i want to know where i can find that delivery number when my program flow comes to the user exit.there is this complex structure 'data' in the import parameters.earlier i had thought that i will use one of the standard segments to get the delivery number like E1EDL20-VBELN.but that doesnt work.do i am looking to find where the delivery number comes from in the user exit.for reference here are the details

FM idoc_output_delvry

Exit : EXIT_SAPLV56K_002

Thanks a lot

Sanket

[Former Member]

hi guys

got it to work.

thanks a lot for your time help and patience.please let me know if the points are not showing up on your wherever you check your points at and sorry for any mishaps.

take care

[Former Member]

Hi Sanket

I have exactly the same issue with you, only I want to populate a different field. I'm having problems making the user exit. Can you pass me the code you put in ZXTRKU02

I'd appreciate it

Lukas Karambelas

LKARAMBE@ATH.FORTHNET.GR

[Former Member]

Hi Sanket

I have exactly the same issue with you, only I want to populate a different field. I'm having problems making the user exit. Can you pass me the code you put in ZXTRKU02

It will very helpful for me.

Waiting for your reply.

Thanks in advance

my id : abap4india@gmail.com