Scribd
Upload
516 views8 pages

Idoc Extension

This document outlines 7 steps to configure and test IDoc processing for customer and vendor data in SAP. The steps include: 1) Configuring append structures and message types; 2) Setting release and checking for errors; 3) Writing enhancement code; 4) Configuring projects; 5) Writing code to extract and map data for outbound IDocs; 6) Executing transaction codes to process data; 7) Executing IDocs and verifying in transaction WE05.

Uploaded by

Vishnu Vardhan Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
516 views8 pages

Idoc Extension

This document outlines 7 steps to configure and test IDoc processing for customer and vendor data in SAP. The steps include: 1) Configuring append structures and message types; 2) Setting release and checking for errors; 3) Writing enhancement code; 4) Configuring projects; 5) Writing code to extract and map data for outbound IDocs; 6) Executing transaction codes to process data; 7) Executing IDocs and verifying in transaction WE05.

Uploaded by

Vishnu Vardhan Reddy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

STEP1: GO TO THE RESPECTIVE TABLE AND APPEND THE FIELDS IN APPEND

STRUCTURE

STEP1: GO TO WE30

AND THEN PROVIDE THE DETAILS BASIC TYPE AND DESCRIPTION


STEP2:
GO TO TCODE WE31

SAVE IT AND GO TO MENU EDIT AND SET RELEASE

STEP3
NOW GOTO WE82
CLICK ON NEW ENTRIES AND ASSIGN THE BELOW MESSAGE TYPES

SAVE IT .
STEP4.
NOW GO TO WE30 AND SET RELEASE AND CHECK THE INCONSISTENCIES IT
SHOULD BE WITH NO ERRORS AND WARNINGS

STEP5.
NOW WE HAVE TO CHECK THE APPRIOPIATE EXITS AND WRITE THE CODE.

NOW GO TO SMOD AND CHECK THE ENCHANCEMENTS


NOW CREATE A PROJECT ON CMOD
FOR CUSTOMER RELATED we used DEBMAS07 Type

DATA: kna1m LIKE e1kna1m,


kna11 LIKE e1kna11,
z1kna11 LIKE z1kna11,
w_kna1 LIKE kna1,
w_adrc LIKE adrc.

CHECK message_type EQ 'DEBMAS'.


CHECK segment_name EQ 'E1KNA1M'.

LOOP AT idoc_data.
CASE idoc_data-segnam.
WHEN 'E1KNA1M'.
MOVE idoc_data-sdata TO kna1m.
WHEN 'E1KNA11'.
MOVE idoc_data-sdata TO kna11.
ENDCASE.
ENDLOOP.

SELECT SINGLE * FROM kna1


INTO w_kna1
WHERE kunnr = kna1m-kunnr.
IF sy-subrc EQ 0.

SELECT SINGLE * FROM adrc


INTO w_adrc
WHERE addrnumber = w_kna1-adrnr.

idoc_cimtype = 'ZDEBMASEXT'.
CLEAR :z1kna11.
* MOVE-CORRESPONDING w_kna1 TO z1kna11.
* MOVE-CORRESPONDING w_adrc TO z1kna11.
w_kna1-zsort2 = w_adrc-sort2.
z1kna11-zsort2 = w_kna1-zsort2.
CONDENSE: z1kna11-zsort2.
MOVE 'Z1KNA11' TO idoc_data-segnam. " administrative section
MOVE z1kna11 TO idoc_data-sdata. " data section
APPEND idoc_data.
ENDIF.

For Vendor CREMAS06 we used


DATA: lfa1m LIKE e1lfa1m,
lfa11 LIKE e1lfa1a,
z1lfa11 LIKE z1lfa11,
w_lfa1 LIKE lfa1,
w_adrc like adrc.

CHECK message_type EQ 'CREMAS'.


CHECK segment_name EQ 'E1LFA1M'.

LOOP AT idoc_data.
CASE idoc_data-segnam.
WHEN 'E1LFA1M'.
MOVE idoc_data-sdata TO lfa1m.
WHEN 'E1LFA1A'.
MOVE idoc_data-sdata TO lfa11.
ENDCASE.
ENDLOOP.

SELECT SINGLE * FROM lfa1


INTO w_lfa1
WHERE lifnr = lfa1m-lifnr.
IF sy-subrc EQ 0.
select single * from adrc
into w_adrc where ADDRNUMBER = w_lfa1-adrnr.

idoc_cimtype = 'ZCREMASEXT'.
CLEAR z1lfa11.

* MOVE-CORRESPONDING w_lfa1 TO z1lfa11.


w_lfa1-zsort2 = w_adrc-sort2.
z1lfa11-zsort2 = w_lfa1-zsort2.
CONDENSE: z1lfa11-zsort2.
MOVE 'Z1LFA11' TO idoc_data-segnam. " administrative section
MOVE z1lfa11 TO idoc_data-sdata. " data section
APPEND idoc_data.
ENDIF.

STEP6.

NOW GO TO RESPCTIVE TCODE AND EXECUTE IT

EX: BD12 FOR CUSTOMER

BD14 FOR VENDOR

STEP7.

NOW GOTO WE05 AND EXECUTE AND CHECK IT.


Check in WE20

You might also like