BP Relationship Save IDOC

Dear Friends,
When I change, Insert, Delete telephone data, Fax data or SMTP data in the BP Relationship screen, I'm not getting any values for TASK field which is under
E101XIF_PARTNER_REL_COMPLEX/E101BURS_EI_RELATION_DATA/E101BURS_EI_ADDRESS/E101BURS_EI_REL_ADDRESS/
E101BURS_EI_ADDRESS_DATA/E101BUS_EI_COMMUNICATION/E101BUS_EI_TEL_DATA/E101BUS_EI_BUPA_TELEPHONE/
E101S_EI_BUPA_TELEPHONE_CON/ *TASK*
I'm not getting any value for it. Each time what ever actions I perform the IDOC is not coming with that parameter. I want this parameter to be sent to the target system. Becuase they have to determine what kind of operation the CRM has performed, like INSERT, CHANGE or DELETE.
I'm new to this one, if anyone can shed some lights I would really appreciate it.
Thanks!

Closed.

Similar Messages

Save Idoc to file

Hi, are there any ways to save a Idoc to a file in a simple way?
Thanks

Hi Rune,
When u save the IDOC, save it as a local file in "unconverted format".
You can upload this file in WE19 directly.
Hope this helps you!!
cheers,
Prashanth

How to save IDOC number in BPM to use in ALEAUD

Hi Experts,
I am doing IDOC - BPM - sync SOAP scenario, i am using async to sync bridge in BPM, how can i get original IDOC number so that i can use it in webservice response message to ALEAUD mapping??

hi
you have to use Configurable Parameters in the ccBPM. in runtimeyou assign the IDOCNUM field value to the parameter and then use it in the response mapping (WSDL-ALEAUD). you have to define the parameter in the Message Mapping under the Signature Tab.
Also you have to bind the parameter in the Operation Mapping. to do this,define a new parameter in the Operation mapping and then bind it with the parameter defined in the message mapping.
see this blog to know how:
SAP PI 7.1 Mapping Enhancements Series: Parameterized Message Mappings
rgds
RP
Edited by: Rodrigo Alejandro Pertierra on Nov 3, 2011 3:49 PM

Idoc creation when sales order is saved

Hi all,
I have a requirement of Idoc creation in CRM 7.0 server. Whenever Sales order will be created , upon SAVE , idoc should be created and will be passed to XI server. This is a scenario of Idoc to XML conversion .
I am new to CRM server . Kindly guide me how to tigger idoc when Sales Order created (Kindly name the transactions).
Thanks & Regards,
Madhura Nadgauda

Hello All,
Link given below describes scenario on similar lines.
[https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f]
Issue resolved.
Thanks.

Idoc flatfile to IDOC xml issue with new PI7.11 module SAP_XI_IDOC/IDOCFlat

Hi,
I am trying to develop a scenario as mentioned in the blog using the new module available in PI7.1,but I am getting this error
"Error: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ORDERS05" is unavailable."
I have made every configuration correct and IDOC meta data available in both SAP R3 and PI,but it is still complaning about the meta data does not exist.
Blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13743%3Fpage%3Dlast%26x-order%3Ddate
did anybody face issue with the new module available "SAP_XI_IDOC/IDOCFlatToXmlConvertor",please help me or give me mre information why I am getting this meta data error.
Thank you,
Sri

Hi Sri,
To Convert IDOC Flat file into IDOC xml from the given blog, the IDOC flat file should be present in standard format like:
E2EDK01005                    0000047110815000000000001.........
E2EDKA1003                    0000047110815000000000002.........
E2EDKA1003                    0000047110815000000000003..........
E2EDKA1003                    0000047110815000000000004........
The Flat file have relationship as IDOC Number "000004711081500000" and segment sequence "0000001".
If your flat file is not in this formate so i don't think that module is able to convert into IDOC xml. and if your file is already in this format then it may be issue with destinations which are created in NWA.
Thanks
Harish

Trigger Vendor master idoc automatically

Hi Experts,
When i save idoc vendor master (CREMAS05) , how can i trigger the idoc and send it to XI system automatically ?
I tried running the report RSEOUT00 with the idoc details but message displayed is 'no idoc ready for processing'.
Regards,
Syed.

Hi
First you test the scenario by generating the IDoc with Tr. code WE19 and execute Standard Outbound processing.
Have u checked whether that Idoc is generated or not?
Go to WE02 and check the status of the Idoc.
Regards
Sridhar Goli
Edited by: Sridhar Goli on Sep 30, 2008 1:47 PM

Can i get IDOC to File scenario Step-by-Step Procedure?

can i get IDOC to File scenario Step-by-Step Procedure?
please provide me the step-by-step and hole procedure..please.
Tks

Hi,
Check this blog-
IDOC - File scenario
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
configuring IDOCS
/people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii
IDOC scenarios
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
Idoc related setting
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Save Idoc to file
https://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
see the below links
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
Also
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
regards
Aashish Sinha
PS : reward points if helpful

IDOC to FIle, Proxy to file not working

Dear Experts,
I am new with XI configuration scenarios, that to i am facing problem
while i was doing with idoc to file and proxy to file not connecting .
i think what r the prerequisites to scuceed these things.
I think this would be administration configuration.
After installation of XI what r the steps have to follow for achiving this.
Please help me.
Thaks and Regards
Ram.

Hi,
This will help you
Client Proxy - /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Server Proxy - /people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies - Activate Proxy
/people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap
/people/prateek.shah/blog/2005/06/14/file-to-r3-via-abap-proxy - ABAP Proxy
IDOC to file
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Save Idoc to file
Regards
Agasthuri Doss

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 or RFC

Dear Guys
Will some body explain the relationship between IDOC BAPIS and RFCs. I have developed a interface between SAP 4.6C and ASP.NET using .NET Connectors. When I am getting data by just using RFC then why should I go for IDOCs.
My same is question is related to BAPIs when RFCs Function using BAPI are providing me data through BAPIs then why is IDOC technology there.
When I have to use RFC and when we can use IDOC or RFCs.
Basically I am trying to develop an ASP application by using which our customer can crreate Sale Order on SAP.

hi,
>>>How does it work in real life scenarios? Will there be a batch job to trigger the IDOCS to XI?
yes but you can set IDOC creation from PO
in a few minutes (in standard) and you
have to do a lot a development to send
them with RFC... so not few minutes
+ you can archive idocs and delete them
just like any message in the XI
>>>>2) How can i create an IDOC?
you have to maintain the partner profile and
set the output type and that's all...
5 minutes in standard
3) What is the RFC involved to get the purchase orders?
none you have to fill the RFC yourself...
you can use BAPI for PO creation as a template
but you still have to fill it youself
Regards,
michal

Idoc Testing! Need help!

Hi!
 (Please give answers specific to my question & pls read below)
 i want to test idoc outbound as well as inbound.
First Consider inbound,
 I ve read previous posted threads it was mentioned goto>we19> give idoc no
I want to know what is idoc no how we get idoc no for the idoc.

Then i know the steps...
Now Outbound,
How to test outbound idoc -- i want to know how my posting program has correctly generated idoc to ale layer.
I want this in complete detail.
 Thanks!
 Rahul.

Hi Rahul,
idoc structure
http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/idoc/SAP_IDOC_structure_introduction.html
What is Idoc?
I give overview of IDoc terminology and how IDocs work in an enterprise will clarify the process
SAPs presence in the IT world is justified by a central premise: It turns a companys many individual systems into one, big supersystem. More than a linking together of applications, SAPs implementation causes a redirection of the flow of information through a company and its partner companies that enhances the potential of its business functions.
This flow of information is enabled by a core element in SAP technology: the Intermediate Document, or IDoc. Technically, the IDoc is an example of Electronic Data Interchange (EDI). Unlike conventional EDI, IDocs are not based on a descriptive language.
The IDoc concept borrows the best features of EDI and combines them with the best features of conventional transaction file formats. The result is a lean data transport mechanism that is the engine of SAP data flow, tying together applications, databases, companies, and networks. Here is a look at the makeup of IDocs within the application architecture.
Form and content: IDoc terminology
As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
A message refers to the contents of a specific implementation of an IDoc; its a logical reference. This differs from a reference to the IDoc itself, which specifies the messages physical representation. Think of it this way: If youre watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayors limousine (which is specific to the mayor) is the IDoc. Youre building a logical object, and the IDoc is both its container and the vehicle that moves it.
The IDoc control record
Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDocs functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI (see Figure A).
Figure A
IDOC number Sender Receiver Port Message type IDoc type
1234567890 R3NYC R3LA FILE INVOICES INVOICE01
This cover slip format informs the receiving system of the IDocs purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
Data records
The data records following the control record are structured alike, including two sections: a segment information section and a data section.
In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner companys Oracle system, which has no such data dictionary.
The second part of the record is the data itself, a storage area of 1,000 characters.
Status records
If youve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, youre familiar with the list of stops and transfer points through which a package passes on its way to you.
This collection of records is exactly what youll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records (see Figure B) are used to record these errors and the date/time of their occurrence.
Figure B
(Display Status Record)
IDoc number 0000000000123456
Direction 1 Outbound
Status information
 38 IDoc archived
(additional descriptive text)
Log time
 Date 6-30-02
 Time 14:35:21
Portion of IDoc status display
IDoc Base
IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
This IDoc Base gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
Multiple messages
One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, its no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system (see Figure C).
Figure C
CONTROL RECORD
DATA RECORD - CUST PROFILE LOC #1
DATA RECORD - CUST PROFILE LOC #2
DATA RECORD - CUST PROFILE LOC #3
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #1
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #2
DATA RECORD - CUST DISCOUNT STRUCTURE LOC #3
STATUS RECORD
STATUS RECORD
STATUS RECORD
Records in a multiple-message IDoc
Final thought
There is no mastering SAP without mastering its workhorse, the IDoc. ERP environments utilizing SAP and similar platforms are made necessary in the first place by the increasing demands of ever more integrated business relationships. IDoc technology addresses this trend with a simple but powerful design philosophy: Data is no longer something to be stored; its something to be moved.
And
These links give u complete details abt idocs testing
Test Tool
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b80f643d711d1893e0000e8323c4f/content.htm
Status Monitor for ALE Messages
http://help.sap.com/saphelp_nw04/helpdata/en/d4/0d67e4d85511d2a6080060087832f8/content.htm
Regards ,
Kumar.

Re-send incoming IDOC

Hi,
we created own IDOC type and input function module to create Sales orders from interface data: Incoming file data are converted to IDOCS, IDOC_INBOUND_SINGLE saves IDOCS.
Is there a way to re-route IDOCs to outbound?
The background is that we have one system to receive interface data. They have to be converted to 'order' idocs. But the IDOCS have to be processed in different systems. Will an IDOC saved with FM IDOC_INBOUND_SINGLE be an outbound one if we fill the control structure pi_idoc_control_rec_40 accordingly with destination system?
Thanks for any hints!
C.

I had an other similar thread answering the question

LSMW use Idoc DOCMAS

Hello,
I would like to change data carrier and original for documents .
For that , I use a lsmw with Idoc Docmas DOCMAS04 . The drawback is that lot of fields are reset ( description , object links , application ...)
is it a way to use DOCMAS only for changing some field without resetting the others ?
Thanks , Philippe

Thx Liam,
But i dont find a basic type entitled "ORDERS01" and i wanna ask how to create the segment of the same type??
May be i point out the steps of what i am doing.
1.Maintain Object Attributes
    I select the IDoc radio button and define the
    Message type as "SALESORDER_CREATEFROMDAT2" and
    Basic type as "SALESORDER_CREATEFROMDAT202"
2.Maintain Source Structures
    I define a header and a item structures for mapping
3.Maintain Source Fields
   I define the fields in header and item structures
   created from previous step.
4.Maintain Structure Relations
   I assign header structure to link a relationship with
   IDOC structure "E1BPSDHD1" etc...
5.Maintain Field Mapping and Conversion Rules
   I successfully mapped some field
   eg. E1BPSDHD1-SALES_ORG = '1000'.
Most of field i have mapped except the sold-to-party or ship-to-party. I cannot find a field in E1BPSDHD1 for mapping customer no.
Refer to Liam's reply, which step could i create the segment of same type? thx...

Message Listener Not Working

Hi,
We are using MII 12.0.2 (88). We have connected with SAP ECC and we are receivng iDoc mesg from SAP and processing thru message listener and processing rule editors.
This connection was successful and we are able to recive all iDoc but suddenly on this is not working as only one type of iDoc are getting. But in SAP all are showing as Successful in WE02 tranx. We have checked in SM58 and other queues also. But in MII we didnt receive any iDoc except particular iDoc.
We are seeing this error in log "Could not save IDoc messages to the database"
and location as "com.sap.xmii.databuffer.server.JCoIDOCServer".
What is the problem and how to solve it.
Regards,
Senthil
Edited by: senthil kumar on Jun 7, 2011 5:08 PM

Hi Senthil,
Did you mean that you were receiving a variety of IDocs before and now you only receive one type?
Or did you just try a new type and fail?
Check to make sure the Partner Profile's Outbound Parameters and the Distribution Model both are set properly for the IDoc types.
Regards,
Mike

Display Intercompany Account Payable Posting document

Hi Friends,
We have a query related to Intercompany account payable posting document. In Intercompany process, we are posting the intercompany account posting in receiving company by using standard SAP EDI functionality. It mean once the AR is realized, we post the AP using Outbound & Inbound IDOC. Now when we like to display the account payable document, there are two ways -
1. Go to Account Receivable document, Environment->Document Environment->Relationship Browser-> IDOC->AP Document
2. Change view of billing document, Services for Objests->Display Relationshis->IDOC Number->AP document
Here we have a requirement to display the AP document directly without going to all the above ways, could you please whether any transaction/approach to display the AP document from AR document.
Thanks in advance
Best Regards,
Goutham

Please take the Invoice Number put "0" in Prefix go to FB03>Document List> remove all the values given in the screen if there is any, enter the Invoice Number with ZERO Prefix in reference Number Field.
This will give you two documents one will by IC-AR and Other will be IC-AP.
Hope this helps.
Regards,
Vivek

BP Relationship Save IDOC

Similar Messages

Maybe you are looking for