idoc for outbound delivery

[Former Member]

Hi,

I have added extra zfields for each line item of the delivery in VL02N. Once this delivery saved, these details will be saved in one ztable with reference to that delivery no. Now which idoc is going to trigger for VL02N, so that i can add these zfields as extension for that IDoc & in which userexit i have write the coding so that these ztable values will be taken to the main IDoc?

Ex:

Header:

Delivery No. & Date

Line items:

ItemNo. -- MaterialNo. -- qty -- units -- ZField1

00010 -- mat1 -- 5 -- gms -- 1

-

---

2

-

---

3

-

---

4

00020 -- mat2 -- 7 -- gms -- 1

-

---

2

-

---

3

Is there any way to know what idocs are available for the particular t.code. (T.code wise IDoc list).

rgds,

balu

[Former Member]

Use the Idoc DELVRY05.

Reagrds,

Kiran Bobbala

[Former Member]

Use DESADV message type.

Use DELVRY05 IDoc type.Process COde: DELV.

Regards

Kannaiah

[Former Member]

Hi,

thanks for the reply...

i've added in both o/b & i/b in the partner No. in WE20. I have saved in VL02N & done PGI. No idocs generated.

How to trigger the idoc DELVRY05 for the VL02N Outbound Delivery.

rgds,

balu

[Former Member]

For the partner number, add the outbound parameter only.Remove the configs done in inbound parameters.

For the Outbound parameter, what you have added in the Message control. Whats the process code you are using.

Regards

Kannaiah

[Former Member]

Hi,

For the Outbound parameter, i have not added any details in the Message control tab. What to enter there...

Application:

Message Type:

Process Code:

Change message:

& what is the effect...

also i don't have any output type for this.

rgds,

balu

[Former Member]

Hi,

with reference to this link,

http://help.sap.com/saphelp_di471/helpdata/EN/04/8ccd25d7fe0e429fb7196e7617cca3/content.htm

I have updated the Outbound parameters-->Message Control tab... for the partner in WE20.

Message type: DESADV

IDoc type: DELVRY05

Still idoc not created after VL02N-Change Outbound Delivery, save & PGI.

Any other settings to do, otherthan WE21, WE20, BD64 etc...

Can anyone share hw to send the VL02N outbound delivery details through an idoc.

responses will be appreciated...

rgds,

balu

[Former Member]

In order to trigger the IDoc DELVRY05 for changes to outbound delivery (VL02N), the following needs to be done:

1. In Transaction NACE, create a new Z output type for Application (think it is V2 (Shipping)) Then assign the Processing Routine to enable the ALE. Set the Program as 'RSNASTED' and processing routine as 'ALE_PROCESSING'.

2. Then go to the outbound parameters in WE20 for this Message Type / Basic Type and add the details in 'Message Control' tab - Application ,Message Type and Process Code.

In order to make change to the IDoc segments and add your own custom data - you can make changes in the user exit EXIT_SAPLV56K_001 and EXIT_SAPLV56K_002.

Reward Points if helpful.

[Former Member]

Hi,

Thanks for the reply.

I have added the code in the userexit: V56K0001 , in the component, EXIT_SAPLV56K_002, the following code:

*Segment Delivery Item

DATA: I_E1EDL24 LIKE E1EDL24,

*Segment added under E1EDL24

I_ZPBSEG2 LIKE ZPBSEG2.

*EDIDD-Data record (IDoc)

DATA: BEGIN OF S_IDOC_DATA OCCURS 0.

INCLUDE STRUCTURE EDIDD.

DATA: END OF S_IDOC_DATA.

*Constants

CONSTANTS: lc_E1EDL24 LIKE edidd-segnam VALUE 'E1EDL24',

lc_ZPBSEG2 like edidd-segnam value 'ZPBSEG2'.

********************************************************************************************************************************************

check segment_name = 'E1EDL24'.

CASE SEGMENT_NAME.

WHEN 'E1EDL24'.

IF control_record_out-cimtyp = 'DESADV'. " Message type

I_E1EDL24 = IDOC_DATA-SDATA.

*Description field(MAKTX) population.

*Assign ZPBSEG2 Segment to IDOC_DATA-SEGMENT.

IDOC_DATA-SEGNAM = lc_ZPBSEG2.

*W_MATNR = I_E1AFKOL-MATNR.

*

*CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'

*EXPORTING

*INPUT = W_MATNR

*IMPORTING

*OUTPUT = W_MATNR

*EXCEPTIONS

*OTHERS = 1.

SELECT SINGLE * FROM ZSOHEADERS.

IF SY-SUBRC EQ 0.

I_ZPBSEG2-VBELN = ZSOHEADERS-VBELN.

I_ZPBSEG2-KUNNR = ZSOHEADERS-KUNNR.

ENDIF.

*Finally assign all the data to S_IDOC_DATA-sdata and Append to idoc_data.

S_IDOC_DATA-sdata = I_ZPBSEG2.

S_IDOC_DATA-segnam = lc_ZPBSEG2.

Append S_IDOC_DATA to idoc_data.

Clear S_IDOC_DATA.

Endif.

ENDCASE.

but the break-point is not going there, when i run VL02N, to create idoc. But idoc DELVRY05 is generated. Also in that it is not showing any extended idoc, created by me.

Let me know hw & where, which exit to proceed...

rgds,

balu

[Former Member]

Have you attached the Extended idoc type to Message type: Check WE82.

Have you attached the extended idoc type & Message type to FM: Check WE57.

Check that if you have released the extended idoc type & new segment.

Regards

Kannaiah

[Former Member]

In order to debug the code while the IDoc is being generated, you need to do the following

1. Put a break point in the user exit code

2. Open the delivery in VL02N. Goto Extras -> Delivery Output -> Header. Enter the output type and print medium (6(EDI) or A( ALE))

3.Click on Further data and select->select send with periodically scheduled job and save it.

4. Now go to SE38 and execute program RSNAST00.

5. Enter the Application (V2) and Object Key (Delivery No); Output Type etc. and execute. The processing will stop at the break point.

I hope by this you can check whether your logic is working.

[Former Member]

Hi,

I have released, segment, extended idoc, & in WE82 attached this ext.idoc to msgtype & basis type for that release. In WE57, used this function exit & attached msgtype, idoc, ext.idoc, Direction: outbound & saved.

assigned the o/ptype in VL02N as suggested & saved... executed the RSNAST00 in se38 ... it is showing the msg as:

0 outputs were processed in total (0 successfully, 0 incorrectly)

but not going to debug mode. In WE05, idoc is created as std. only.(without showing any ext.idoc&zfields).

As it is not hitting the debug mode, i think that is not the right userexit or func.exit. Which is the suitable to hit that...

The Enhancement: V56K0001 docu. is showing like this:

You can use this enhancement to make individual adjustments to the creation of IDocs that are based on IDoc type SHPMNTnn.

pls guide on this...

rgds,

balu

[Former Member]

The Outbound Process Code 'DELV' is attached to the function module IDOC_OUTPUT_DELVRY. So you have only those two user exits available with you.

Try running RSNAST00 with only the outbound delivery number and also give a breakpoint in the IDOC_OUTPUT_DELVRY code to check if this processing FM is called or not when the IDoc is getting populated.