IDOC Tables

Dear Friends,
Please tell me where / how can I find all the tables related to IDOC (material, PO number, Doc type)
Regards,
Dhananjay

>
Dhananjay. wrote:
> Please tell me where / how can I find all the tables related to IDOC (material, PO number, Doc type)
There is no transaction that would list all tables related to an IDoc (and why do you even need all tables?).
You'll need to have an understanding of what the specific IDoc does. In fact, some IDocs, like ORDERS05, for example, may be used for completely different purposes - to create purchase orders and sales orders. When you know what kind of document an IDoc is creating/changing, you can simply look up the related tables in any of the widely available resources. For example here:
http://www.erpgenie.com/sap/abap/tables.htm
Use WE60 transaction to read the IDoc documentation, then compare the field names and descriptions to the fields in the tables.

Similar Messages

IDOC Tables with Errors Post System Refresh

Hi Everyone,
Is there any Report or other way through which one can get List of IDOC Tables with Errors Post System Refresh.
Thanks,
Regards,
- Ishan

Hi,
While selecting the Infopackage to run the INIT load, it is taking me to the ECC login screen. Once i enter my credentials, its showing a dump with the message:
Short text of error message:
No RFC authorization for user XXXXX ( RSA8 ).
Long text of error message:
Technical information about the message:
Message class....... "RSAR"
Number.............. 051
Variable 1.......... "No RFC authorization for user XXXXX ( RSA8 )."
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Please advice.
Regards
sneha

What is the name of the IDoc table

Can anyone tell me what the name of the IDoc table is

Janice,
Go to WE16 transaction and give the table name. If you dont know the table name just search out for it with all.
---Satish

IDOC: table relating

Hi!
Does anyone know how which table/structure gives me a relation between a message from a SD-delivery (that creates an IDOC) and the IDOC number created?
In an SD-delivery a message is determined. The message creates an IDOC. I need a table/structure that gives me the relation between delivery number and IDOC created.
Thanks in advance,
F

Hi..
This program will server ur Req: Slight changes may be needed...
REPORT ZSELIDOCS                                                   .
tables:edid4,edidc,likp.
*likp
types:begin of ty_likp,
vbeln type VBELN_VL,
end of ty_likp.
data:it_likp type table of ty_likp,
wa_likp type ty_likp.
*edid4
types:begin of ty_edid4,
DOCNUM type EDI_DOCNUM,
SEGNAM type EDI_SEGNAM,
sdata type EDI_SDATA,
end of ty_edid4.
data:it_edid4 type table of ty_edid4,
wa_edid4 type ty_edid4.
*edidc
types:begin of ty_edidc,
DOCNUM type EDI_DOCNUM,
MESTYP type EDI_MESTYP,
IDOCTP type EDI_IDOCTP,
end of ty_edidc.
data:it_edidc type table of ty_edidc,
wa_edidc type ty_edidc.
*final
types:begin of ty_final,
vbeln type vbeln_va,
docnum type edi_docnum,
sdata(10) Type C,
MESTYP type EDI_MESTYP,
IDOCTP type EDI_IDOCTP,
end of ty_final.
data:it_final type table of ty_final,
wa_final type ty_final.
parameters:s_vbeln like likp-vbeln.
start-of-selection.
select vbeln from likp into table it_likp where vbeln = s_vbeln.
if sy-subrc = 0.
select DOCNUM
mestyp
idoctp
from
edidc into table it_edidc
where mestyp = 'DESADV'
AND IDOCTP = 'DELVRY03'.
if not it_edidc is initial.
SELECT DOCNUM SEGNAM sdata from edid4 into table it_edid4 for all
entries in it_edidc where docnum = it_edidc-docnum
                                  AND SEGNAM = 'E1EDL20'.
endif.
endif.
clear it_final.
loop at it_likp into wa_likp.
read table it_edid4 into wa_edid4 with key sdata+0(10) = wa_likp-vbeln.
IF SY-SUBRC = 0.
move: wa_edid4-sdata+0(10) to wa_final-sdata,
wa_edid4-docnum to wa_final-docnum.
move wa_likp-vbeln to wa_final-vbeln.
   append wa_final to it_final.
   CLEAR WA_FINAL.
ENDIF.
endloop.
loop at it_final into wa_final.
write:/ wa_final-vbeln,
wa_final-docnum,'|',
wa_final-sdata.
endloop.
<b>Reward if Helpful</b>

Idoc Tables for Message segments

Dear Experts,
I was find SAP table for Idoc Message Type for WPUBON for report of Sales Auditor
Plz help
Regards,
Richa Grover

HelloRicha,
Message Type        Msg
                               Code Msg
                               Fn Inbound Event Code                     Function
WPUBON                 WPUB                                               IDOC_INPUT_POS_SALES_DOCUMENTS

Looking for idoc tables.

Hello,
I am looking for a list of tables where idoc details are stored.
I know about tables EDIDC and EDID4. But they have header data and segment name data.
There should be few other tables that store the data that's in the segments fields.
say for ex. Material number or other material attributes in Matmas idocs.
Which table holds those detais?
Would appreciate anyones help pl.?
Best Regards,
Shiv.

Hi
The Data is stored in the table EDID4 under application data. YOu can see that only when you increase the width of output to 1000. The Application data is stored as a cluster rather than single fields
The data is stored only in structures of segments at filed level. But this may not be retreivable.
Reward points if useful
Thansk & Regards
Kishore

Extracting data from iDoc tables

Hi,
I need to extract data from idoc segments from the database tables EDIDC and EDID4 for which the idoc status is 51 and to save all this data in an external file.
For example, I need to check all the iDocs with WPUBON01 base type and if the status is 51 then I have to query the ARTNR field from E1WPB02 segment and to save idoc number and ARTNR in an excel file.
Can anybody help me or give me some example?
Thank you in advance.
Ioan

See Below Example code :
TYPE-POOLS: slis.
tables : edid4 , edidc ,edids ,lfa1,teds2.
DATA: t_fieldcatalog TYPE slis_t_fieldcat_alv.
DATA: s_fieldcatalog TYPE slis_fieldcat_alv.
DATA: s_layout TYPE slis_layout_alv.
DATA: text11 LIKE E1EDP02.
DATA: text111 LIKE E1MBXYI.
DATA: s_keyinfo TYPE slis_keyinfo_alv.
DATA: v_repid TYPE syrepid.
DATA: V_MSGNO LIKE T100-MSGNR.
*DATA: V_TEXT(90).
DATA : WA_EDIDS TYPE EDIDS.
data : begin of itab_edids occurs 0,
   user like edids-UNAME,
   date like edids-CREDAT,
   time like edids-cretim,
   idoc like edids-docnum,
MESSAGETYPE like edidc-MESTYP,
VENDOR LIKE EDIDC-SNDPRN,
name like lfa1-name1,
icon(1),
   EXPAND TYPE C,
end of itab_edids.
data : itab type edid4.
data : begin of itab_edidc occurs 0,
     doc_num like edidc-docnum,
     MESSAGETYPE like edidc-MESTYP,
   IDOCTYPE like edidc-DOCTYP,
   PARTNERNUMBER like edidc-RCVPRN,
   PARTNERTYPE like edidc-RCVPRT,
MESSAGECODE like edidc-MESCOD,
VENDOR LIKE EDIDC-SNDPRN,
data like edidc-credat,
*include structure edidc.
end of itab_edidc.
data : begin of itab_status occurs 0,
idoc like edids-docnum,
date_stauus like edids-logdat,
status_counter like edids-countr,
staTus like edids-status,
*descrp like teds2-descrp,
DESCRP(70),
ponumber like ekpo-ebeln,
MESS LIKE edidc-MESTYP,
*appdoc like edids-stapa1,
end of itab_status.
data : text like edid4-sdata.
DATA: text1 LIKE E1EDK01.
data : begin of itab_teds1 occurs 0.
        include structure teds1.
data end of itab_teds1.
*selection-screen begin of block sb with frame title text-001.
*select-options:
   s_rsdat for edidc-CREDAT.
*selection-screen end of block sb.
DATA: f_fieldcatalog TYPE slis_fieldcat_alv.
selection-screen begin of block sb with frame title text-001.
parameters:
       p_su radiobutton group gp1,
       p_re radiobutton group gp1,
       p_al radiobutton group gp1.
select-options:
    s_rsdat for edids-creDAT,
    s_user for edids-uname.
selection-screen end of block sb.
initialization.
PERFORM INITIALIZATION.
start-of-selection.
PERFORM DATA_RETRIVAL.
PERFORM DATA_BASED_SELECTION.
PERFORM PASSING_ALV.
*select docnum mestyp doctyp rcvprn rcvprt mescod credat into
*table itab_edidc from edidc
*where credat in s_rsdat.
*CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
*EXPORTING
*i_program_name = v_repid
*I_INTERNAL_TABNAME = 'ITAB_STATUS'
*CHANGING
*ct_fieldcat = t_fieldcatalog.
*CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
*EXPORTING
*i_program_name = v_repid
*I_INTERNAL_TABNAME = 'ITAB_EDIDS'
*CHANGING
*ct_fieldcat = t_fieldcatalog.
s_LAYOUT-ZEBRA = 'X'.
*s_LAYOUT-SUBTOTALS_TEXT = 'SUBTOTAL'.
*s_LAYOUT-TOTALS_TEXT = 'TOTAL'.
*&      Form INITIALIZATION
      text
--> p1        text
<-- p2        text
FORM INITIALIZATION.
V_REPID = SY-REPID.
s_keyinfo-header01 = 'IDOC'.
s_keyinfo-item01 = 'IDOC'.
*s_layout-subtotals_text = 'SUBTOTAL TEXT'.
*s_layout-key_hotspot = 'X'.
*s_layout-expand_fieldname = 'EXPAND'.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
       EXPORTING
            i_program_name         = V_REPID
            I_INTERNAL_TABNAME     = 'ITAB_STATUS'
            I_INCLNAME = V_repid
       CHANGING
            ct_fieldcat            = T_fieldcatalog
       EXCEPTIONS
            INCONSISTENT_INTERFACE = 1
            PROGRAM_ERROR          = 2
            OTHERS                 = 3.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
       EXPORTING
            i_program_name         = V_REPID
            I_INTERNAL_TABNAME     = 'ITAB_EDIDS'
            I_INCLNAME = V_repid
       CHANGING
            ct_fieldcat            = T_fieldcatalog
       EXCEPTIONS
            INCONSISTENT_INTERFACE = 1
            PROGRAM_ERROR          = 2
            OTHERS                 = 3.
f_fieldcatalog-just = 'L'.
MODIFY t_fieldcatalog FROM f_fieldcatalog
TRANSPORTING just
WHERE ( fieldname = 'IDOC' OR FIELDNAME = 'STATUS_COUNTER' ).
f_fieldcatalog-SELTEXT_L = 'Status Message'.
MODIFY t_fieldcatalog FROM f_fieldcatalog
TRANSPORTING SELTEXT_L
WHERE fieldname = 'DESCRP'.
f_fieldcatalog-TECH = 'X'.
MODIFY t_fieldcatalog FROM f_fieldcatalog
TRANSPORTING TECH
WHERE fieldname = 'EXPAND'.
f_fieldcatalog-REPTEXT_DDIC = 'Vendor Name'.
MODIFY t_fieldcatalog FROM f_fieldcatalog
TRANSPORTING REPTEXT_DDIC
WHERE fieldname = 'NAME'.
*f_fieldcatalog-REPTEXT_DDIC = 'V Code 32122'.
*MODIFY t_fieldcatalog FROM f_fieldcatalog
*TRANSPORTING REPTEXT_DDIC
*WHERE fieldname = 'VENDOR'.
ENDFORM.                    " INITIALIZATION
*&      Form DATA_RETRIVAL
      text
--> p1        text
<-- p2        text
FORM DATA_RETRIVAL.
select uname credat cretim docnum into table
itab_edids from edids
               where credat in s_rsdat and
                      uname in s_user and
                      countr = ' '.
select uname credat cretim docnum from edids
*APPENDING CORRESPONDING FIELDS OF TABLE itab_edids
              where logdat in s_rsdat and
                     uname in s_user.
                     SELECT budat hkont belnr shkzg wrbtr FROM bsas
*APPENDING CORRESPONDING FIELDS OF TABLE it_temp WHERE hkont = w_glacct
*"wa_cb-gl_account
*AND bukrs IN (so_bukrs-low)
*AND budat < so_date-low.
delete adjacent duplicates from itab_edids.
if not itab_edids[] is initial.
     select docnum mestyp doctyp rcvprn rcvprt mescod SNDPRN credat into
    table itab_edidc from edidc for all entries in itab_edids
    where docnum = itab_edids-idoc.
endif.
LOOP AT ITAB_edids.
   READ TABLE ITAB_EDIDC WITH KEY DOC_NUM = ITAB_EDIDS-IDOC.
   itab_edids-messagetype = ITAB_EDIDC-MESSAGETYPE.
   itab_edids-VENDOR = ITAB_EDIDC-VENDOR.
   MODIFY ITAB_EDIDS.
   CLEAR ITAB_EDIDS.
   ENDLOOP.
DELETE ITAB_EDIDC WHERE MESSAGETYPE = 'ORDERS'.
loop at itab_edids.
read table itab_edidc with key doc_num = itab_edids-idoc.
if sy-subrc ne 0.
delete itab_edids.
endif.
endloop.
select docnum logdat countr status into table itab_status from edids for
   all entries in itab_edidc where docnum = itab_edidc-doc_num.
   LOOP AT ITAB_STATUS.
   READ TABLE ITAB_EDIDC WITH KEY DOC_NUM = ITAB_STATUS-IDOC.
   ITAB_STATUS-MESS = ITAB_EDIDC-MESSAGETYPE.
   MODIFY ITAB_STATUS.
   CLEAR ITAB_STATUS.
   ENDLOOP.
loop at itab_status.
    clear : text ,text1 , text11, text111, itab.
   select single descrp from teds2 into itab_status-descrp
                          where status = itab_status-STATUS AND
                               LANGUA = 'E'.
   select single sdata into text from edid4 where
     DOCNUM = itab_status-idoc and
     segnam = 'E1EDK01'.
*MOVE: text        TO text1,
     text1-BELNR TO itab_status-ponumber.
      itab_status-ponumber = text1-belnr.
   move text+83(30) to itab_status-ponumber.
   MODIFY ITAB_STATUS.
   clear itab_status.
IF itab_status-MESS = 'WMMBXY'.
   select single * from edid4 INTO ITAB where segnam = 'E1MBXYI' AND
                 HLEVEL = '02' AND DOCNUM = itab_status-idoc.
MOVE : ITAB-SDATA TO TEXT111 ,
text111-EBELN TO itab_status-ponumber.
**text1-BELNR TO ponumber.
ELSE.
select single * from edid4 INTO ITAB where segnam = 'E1EDP02' AND
                 HLEVEL = '03' AND DOCNUM = itab_status-idoc.
MOVE : ITAB-SDATA TO TEXT11 ,
*text1-EBELN TO ponumber.
text11-BELNR TO itab_status-ponumber.
endif.
    MODIFY ITAB_STATUS.
    clear itab_status.
endloop.
ENDFORM.                    " DATA_RETRIVAL
*&      Form PASSING_ALV
      text
--> p1        text
<-- p2        text
FORM PASSING_ALV.
s_LAYOUT-EXPAND_FIELDNAME = 'EXPAND'.
DATA: t_events TYPE slis_t_event.
DATA: s_events LIKE LINE OF t_events.
s_events-form = 'TOP_OF_PAGE'.
s_events-name = 'TOP_OF_PAGE'.
APPEND s_events TO t_events.
s_layout-lights_fieldname = 'ICON'.
sort itab_status by status_counter descending. " -
mod3
CALL FUNCTION 'REUSE_ALV_HIERSEQ_LIST_DISPLAY'
       EXPORTING
            i_callback_program = v_repid
            is_layout          = s_layout
            it_fieldcat        = t_fieldcatalog
            i_callback_user_command = 'USER_COMMAND'
            i_tabname_header   = 'ITAB_EDIDS'
            i_tabname_item     = 'ITAB_STATUS'
            IT_EVENTS          = t_events
            is_keyinfo         = s_keyinfo
       TABLES
            t_outtab_header    = itab_EDIDS
            t_outtab_item      = itab_STATUS
       EXCEPTIONS
            program_error      = 1
            OTHERS             = 2.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " PASSING_ALV
*&      Form DATA_BASED_SELECTION
      text
--> p1        text
<-- p2        text
FORM DATA_BASED_SELECTION.
if p_su eq 'X'.
*loop at itab_status where status = '53'.
*select single stapa1 from edids into itab_status-appdoc
where docnum = itab_status-idoc and status = '53'.
*delete itab_status where status ne '53'.
*modify itab_status.
*endloop.
delete itab_status where status ne '53'.
loop at itab_edids.
read table itab_status with key idoc = itab_edids-idoc binary search.
if sy-subrc ne 0.
delete itab_edids.
ELSE.
*SHIFT ITAB_EDIDS-IDOC LEFT DELETING LEADING '0'.
MODIFY ITAB_EDIDS.
endif.
endloop.
LOOP AT ITAB_STATUS WHERE MESS NE 'WMMBXY'.
SELECT SINGLE * FROM EDIDS INTO WA_EDIDS WHERE DOCNUM = ITAB_STATUS-IDOC
AND COUNTR = ITAB_STATUS-STATUS_COUNTER.
IF WA_EDIDS-STATXT CA '&'.
V_MSGNO = WA_EDIDS-STAMNO.
IF V_MSGNO NE '000'. "----mod3
CALL FUNCTION 'MESSAGE_PREPARE'
EXPORTING
msg_id = WA_EDIDS-STAMID
msg_no = V_MSGNO
MSG_VAR1 = wa_edids-stapa1
MSG_VAR2 = WA_EDIDS-STAPA2
MSG_VAR3 = WA_EDIDS-STAPA3
MSG_VAR4 = WA_EDIDS-STAPA4
IMPORTING
MSG_TEXT = itab_status-descrp.
CONDENSE ITAB_STATUS-DESCRP.
ENDIF."---- mod3
ELSE .
ITAB_STATUS-DESCRP = WA_EDIDS-STATXT.
ENDIF.
*SHIFT ITAB_STATUS-IDOC LEFT DELETING LEADING '0'.
*SHIFT ITAB_STATUS-STATUS_COUNTER LEFT DELETING LEADING '0'.
MODIFY ITAB_STATUS.
ENDLOOP.
LOOP AT ITAB_STATUS WHERE MESS EQ 'WMMBXY'.
SHIFT ITAB_STATUS-IDOC LEFT DELETING LEADING '0'.
SHIFT ITAB_STATUS-STATUS_COUNTER LEFT DELETING LEADING '0'.
ITAB_STATUS-DESCRP = 'APPLICATION DOCUMENT POSTED'.
MODIFY ITAB_STATUS.
ENDLOOP.
delete adjacent duplicates from itab_edids comparing idoc.
elseif p_re eq 'X'.
loop at itab_status where status = '53'.
delete itab_edids where idoc = itab_status-idoc.
endloop.
loop at itab_status.
read table itab_edids with key idoc = itab_status-idoc binary search.
if sy-subrc ne 0.
delete itab_status.
endif.
endloop.
LOOP AT ITAB_STATUS.
SELECT SINGLE * FROM EDIDS INTO WA_EDIDS WHERE DOCNUM = ITAB_STATUS-IDOC
AND COUNTR = ITAB_STATUS-STATUS_COUNTER.
IF WA_EDIDS-STATXT CA '&'.
V_MSGNO = WA_EDIDS-STAMNO.
IF V_MSGNO NE '000'. "----mod3
CALL FUNCTION 'MESSAGE_PREPARE'
EXPORTING
msg_id = WA_EDIDS-STAMID
msg_no = V_MSGNO
MSG_VAR1 = WA_EDIDS-STAPA1
MSG_VAR2 = WA_EDIDS-STAPA2
MSG_VAR3 = WA_EDIDS-STAPA3
MSG_VAR4 = WA_EDIDS-STAPA4
IMPORTING
MSG_TEXT = itab_status-descrp.
CONDENSE ITAB_STATUS-DESCRP.
endif. "-----mod3
ELSE .
ITAB_STATUS-DESCRP = WA_EDIDS-STATXT.
ENDIF.
SHIFT ITAB_STATUS-IDOC LEFT DELETING LEADING '0'.
SHIFT ITAB_STATUS-STATUS_COUNTER LEFT DELETING LEADING '0'.
MODIFY ITAB_STATUS.
ENDLOOP.
LOOP AT ITAB_EDIDS.
SHIFT ITAB_EDIDS-IDOC LEFT DELETING LEADING '0'.
MODIFY ITAB_EDIDS.
ENDLOOP.
delete adjacent duplicates from itab_edids comparing idoc.
elseif p_al eq 'X'.
delete adjacent duplicates from itab_edids comparing idoc.
LOOP AT ITAB_STATUS." WHERE MESS NE 'WMMBXY'.
SELECT SINGLE * FROM EDIDS INTO WA_EDIDS WHERE DOCNUM = ITAB_STATUS-IDOC
AND COUNTR = ITAB_STATUS-STATUS_COUNTER.
IF WA_EDIDS-STATXT CA '&'.
V_MSGNO = WA_EDIDS-STAMNO.
IF V_MSGNO NE '000'. "----mod3
CALL FUNCTION 'MESSAGE_PREPARE'
EXPORTING
msg_id = WA_EDIDS-STAMID
msg_no = V_MSGNO
MSG_VAR1 = WA_EDIDS-STAPA1
MSG_VAR2 = WA_EDIDS-STAPA2
MSG_VAR3 = WA_EDIDS-STAPA3
MSG_VAR4 = WA_EDIDS-STAPA4
IMPORTING
MSG_TEXT = itab_status-descrp.
CONDENSE ITAB_STATUS-DESCRP.
endif. "----mod3
ELSE .
ITAB_STATUS-DESCRP = WA_EDIDS-STATXT.
ENDIF.
*SHIFT ITAB_STATUS-IDOC LEFT DELETING LEADING '0'.
*SHIFT ITAB_STATUS-STATUS_COUNTER LEFT DELETING LEADING '0'.
MODIFY ITAB_STATUS.
ENDLOOP.
endif.
LOOP AT ITAB_EDIDS.
if p_su EQ 'X'.
itab_edids-icon = '3'.
elseif p_re eq 'X'.
   itab_edids-icon = '1'.
   ELSE.
   read table itab_sTATUS with key idoc = itab_EDIDS-idoc
                               STATUS = '53' ."binary search.
   IF SY-SUBRC EQ 0.
    itab_edids-icon = '3'.
   ELSE.
   itab_edids-icon = '1'.
   ENDIF.
   ENDIF.
select single name1 from lfa1 into itab_edids-name where
            lifnr = itab_edids-vendor.
SHIFT ITAB_EDIDS-IDOC LEFT DELETING LEADING '0'.
MODIFY ITAB_EDIDS.
clear itab_edids.
ENDLOOP.
loop at itab_status.
SHIFT ITAB_STATUS-IDOC LEFT DELETING LEADING '0'.
SHIFT ITAB_STATUS-STATUS_COUNTER LEFT DELETING LEADING '0'.
if itab_status-descrp is initial.
select single descrp from teds2 into itab_status-descrp
                           where status = itab_status-STATUS AND
                                LANGUA = 'E'.
endif.
MODIFY ITAB_STATUS.
clear itab_status.
endloop.
sort itab_status by idoc.
sort itab_edids by idoc.
ENDFORM.                    " DATA_BASED_SELECTION
*& Form TOP_OF_PAGE
text
FORM TOP_OF_PAGE.
SKIP.
ULINE.
IF P_SU EQ 'X'.
WRITE : / 'TITLE : SUCCESSFULLY POSTED IDOC', 50 'DATE :', SY-DATUM..
ELSEIF P_RE EQ 'X'.
WRITE : / 'TITLE : REJECTED IDOCS' ,50 'DATE :', SY-DATUM.
ELSEIF P_AL EQ 'X'.
WRITE : / 'TITLE : ALL IDOCS' ,50 'DATE :', SY-DATUM.
ENDIF.
WRITE :/9 'Successful-Green light Unsuccessful-Red Light'.
format color COL_TOTAL intensified on.
WRITE : / 'NOTE : DOUBLE CLICK TO SEE CORREPONDING IDOC AND PO'.
WRITE :/9 'DOUBLE CLICK IDOC NO ON HEADER LIST'.
WRITE : 'AND PO NUMBER ON DETAIL LIST'.
format color off.
ULINE.
SKIP.
ENDFORM. "TOP_OF_PAGE
FORM user_command *
--> UCOMM *
--> SELFIELD *
FORM user_command USING ucomm LIKE sy-ucomm
selfield TYPE slis_selfield.
DATA: WA_IDOC9 LIKE EDIDC-DOCNUM.
DATA: SELTAB     TYPE TABLE OF RSPARAMS,
      SELTAB_WA LIKE LINE OF SELTAB.
RANGES : R_DATE FOR EDIDC-CREDAT." SY-DATUM.
IF ucomm = '&IC1'.
if SELFIELD-SEL_TAB_FIELD = 'ITAB_EDIDS-IDOC'.
READ TABLE itab_edids INDEX selfield-tabindex.
IF sy-subrc = 0.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = ITAB_edids-IDOC
IMPORTING
OUTPUT = WA_IDOC9.
*r_date-low = itab_edids-date.
*r_date-high = itab_edids-date.
*r_date-SIGN = 'I'.
*r_date-OPTION = 'BT'.
*append r_date.
SUBMIT RSEIDOC2 WITH DOCNUM = wa_idoc9
WITH CREDAT in R_DATE[] AND RETURN.
ENDIF.
ELSEIF SELFIELD-SEL_TAB_FIELD = 'ITAB_STATUS-PONUMBER'.
READ TABLE itab_STATUS INDEX selfield-tabindex.
IF sy-subrc = 0.
SET PARAMETER ID 'BES' FIELD itab_sTATUS-PONUMBER.
CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
ENDIF.
ENDIF.
ENDIF.
ENDFORM..

Idoc Hit ratio and Idoc Table

Hi
We would like to monitor the idoc hit ratio (No of idocs posted successfully in the first instance/Total No of Idocs) to see the success rate of our interfaces.
What is the best way to get this data?
Is there any table which gives all the statuses of the idocs. For eg If a idoc had initially failed (status 51) and then it was reprocessed and was successfully posted (status 53), is there any table which gives us this data?
Thanks in advance.
Mick

Thanks Sergey.
I checked one idoc, which was created on 29.01.2010 (29th January 2010). However when I use table EDIDS, with field CREDAT as 10.02.2010 (10th Feb, 2010), it shows me 2 entries for the above mentioned idoc. This is because it was reprocessed on 10th of Feb.
Is there any way to get the idocs created on say for eg 0n the 1st of Feb, 2010 along with the entire history of statuses on the 1st of Feb (all the statuses that the idoc went through on the 1st of Feb)?
Mick

Idoc tables/segment structure

hi gurus,
how i write sthructure of an idoc segment.
how i define internal table for header and item level data.
please guid me with an example.
please provide me some programme or threads where programme is wriiten for saving the data through idoc into db.
thanks and regards.

Hi,
Make sure you have this..Marked in bold..
*" IMPORTING
*" VALUE(MESSAGE_TYPE) LIKE TBDME-MESTYP
*" VALUE(IDOC_TYPE) LIKE EDIDC-IDOCTP
*" VALUE(SEGMENT_NAME) LIKE EDIDD-SEGNAM
*" EXPORTING
*" VALUE(IDOC_CIMTYPE) LIKE EDIDC-CIMTYP
*" TABLES
*" IDOC_DATA STRUCTURE EDIDD
INCLUDE Z123.
<b>ENDFUNCTION.
FORM ...
ENDFORM.</b>
Thanks,
Naren

IDOC Table

HI All
My user has given a list of say 50 customers. He wants to know what is the message type these customers are using for Inboound and outbound I doc processing. Is there any table , where we can put these customer number and get the massage type details . Also advice any alternate procedure .
Regards
SAM

HI,
Table - TCEDP21.
thanks,
vrajesh

Idoc data in transparent tables

Hi,
There is a existing program which picks up data from Idoc and creates the output files for further processing.
My requirement is I need to pick up data with using Idoc tables, is there any SAP transparent tables which stores the data? Is it possible or is there any method available to select the data?
Regards,
Kumar.

Hi,
Use the table EDID4 to read the IDOC data.
You can also use the FM IDOC_READ_COMPLETELY
Thanks,
Naren

Idoc-segment Table

HI guys,
In a Idoc we have a segment called E1EDP01 contains several records for name PO no#( unique identifier) and some other text fields.
In which Idoc table contents of this segments will be stored.I am sure its not EDIDC.. where i can find only segment but not the contents in it.
SE16 E1EDP01 shows it as structure then how to find Idocs sepcific to these segment values.
Pl advise.
Reg
shan1242

If you go to tcode WE09 then you can do a search on Business Content.
If you are for instance looking for an Idoc containing a PO number then you fill:
E1EDK02 in the 'Search in Segment',
BELNR in the 'Search in field'
and the PO number itself in the 'for Value' filed.
Make sure you have the correct date range and execute.
If an Idoc was created then that Idoc number will be returned in the result
Hope this is what you were looking for.
Rgs, Alice

Tables for IDOC's

Some time ago I created a job which deletes all idocs older than 1 year.
I am asked now to check what is the benefit in term of space(tables, database..)
I wander in which tables idocs are stored(if tables are different for different idocs could you let me know tables for most commonly used)
. However I am afraid (having oracle database) I can not see the benefits as segments/database just grows regardless of empty space.

Jan,
Check below links for idoc tables
What is the name of the IDoc table
Re: IDOC Table
Idoc table
Re: idoc
To reduce the Oracle DB size check below link
Re: How to reduce oracle DB's size?
Re: degradated indexes of the table D0101INC
Hope it helps
Thanks
Sushil

We have to upgrade from SAP 4.0 version to ECC6.0(only EDI/IDOC effects)

Hi All,
We have to upgrde a system from SAP 4.0 version to ERP6.0, is there any difference in EDI and IDOC
tables or their types in ERP6.0 from the 4.0 version, which we have to also consider or not.
but if differences are there but SAP itself is taking care for that, then how the sap is taking care of that ..?
Regards,
Rohit Sharma
Edited by: rohit sharma on Jun 19, 2008 1:26 PM

I´m not sure what you mean by "old table to new table".
The general table structure is not changed, VBAK + VBAP are still there. They may have been extended by additional fields, depending on how your system is implemented. It´s also possible, that if you activate any business function after the upgrade, that tables will get appends.
The old IDOC structures working before the upgrade should work after the upgrade the same way since those structures are not touched.
Markus

Mapping and Interfacing files into R/3 as IDOCs using XI

We are trying to send an IDOC into R/3 thru XI. We generated one from R/3 into XI - it worked fine, however the reverse direction is not working well.
We are using XI 2.0 with R/3 4.6C.
We ran into two problems:
when we tried DEBMAS/DEBMAS06, we were getting a message in SXMB_MONI / IDX5 that the entry DEBMAS06 is not found (in table IDOCSYN) on XI. On our XI server we found that there were only 65 IDOC message types defined (I dont know why .. but none of the popular IDOC messages like DEBMAS, CREMAS, MATMAS, ORDERS, etc are in XI). We thought may be that is the reason. But we do not know thru config, how to add IDOC messages into XI - this is not the same as importing IDOC type .. we have already done that. Just importing an IDOC structure does not put an entry in tables like IDOCSYN, and others...
Then we tried using an IDOC message that was in XI IDOC tables - FLIGHT_SAVEREPLICA. This ones gets past the error we got with DEBMAS. However, we still do not see the IDOC in R/3. When we check IDX5 or SXMB_MONI, it says that the message is processed successfully and does not show any errors. We are not understanding why it does not reach R/3.
Has anyone mapped files into IDOCs and sent to R/3 thru XI. If you did, CAN YOU PLEASE HELP US OUT....
It looks like we are missing small config step .. somewhere ..
We created partner profiles, set up ports and RFC destinations. IN SLD we did define the logical systems. On the surface, from the config everything seems fine.
OSS note 669669 is already in.
Any help will be greatly appreciated ...

> We are trying to send an IDOC into R/3 thru XI. We
> generated one from R/3 into XI - it worked fine,
> however the reverse direction is not working well.
> We are using XI 2.0 with R/3 4.6C.
>
> We ran into two problems:
> when we tried DEBMAS/DEBMAS06, we were getting a
> message in SXMB_MONI / IDX5 that the entry DEBMAS06
> is not found (in table IDOCSYN) on XI. On our XI
> server we found that there were only 65 IDOC message
> types defined (I dont know why .. but none of the
> popular IDOC messages like DEBMAS, CREMAS, MATMAS,
> ORDERS, etc are in XI). We thought may be that is the
> reason. But we do not know thru config, how to add
> IDOC messages into XI - this is not the same as
> importing IDOC type .. we have already done that.
> Just importing an IDOC structure does not put an
> entry in tables like IDOCSYN, and others...
You need to change the outbound version to a lower version. ie send debmas03 not 06.
This is an ALE to ALE issue. Not XI related.
> Then we tried using an IDOC message that was in XI
> IDOC tables - FLIGHT_SAVEREPLICA. This ones gets past
> the error we got with DEBMAS. However, we still do
> not see the IDOC in R/3. When we check IDX5 or
> SXMB_MONI, it says that the message is processed
> successfully and does not show any errors. We are not
> understanding why it does not reach R/3.
>
Trace time....
> Has anyone mapped files into IDOCs and sent to R/3
> thru XI. If you did, CAN YOU PLEASE HELP US OUT....
>
> It looks like we are missing small config step ..
> somewhere ..
>
> We created partner profiles, set up ports and RFC
> destinations. IN SLD we did define the logical
> systems. On the surface, from the config everything
> seems fine.
> OSS note 669669 is already in.
>
> Any help will be greatly appreciated ...
Use SXI_SUPPORT and follow it in debug...
Cant tell what else is wrong.

IDOC Tables

Similar Messages

Maybe you are looking for