Details on idoc

Hi all,
Can anybody help me out what IDOC is and where do i found more information on IDOC.
Thankx in Adv

Hi Sanjay,
IDOC is a data container & it hold the data to transfer one system to other/many systems.
IDOC contains One control Record,N noof Data Records,N noof status records.
Control record gives the info, like sender,reciever,message type,IDOC type,Techincal info like partner system,port and IP address. And these data will be stored into EDIDC table.
Data records contains the actual data & stores in segments. Thes info. stored in table called EDID4.
Like the same way status record info. stored in table EDIDS. It contains the IDOC status.
For your info. You can view all the status in WE47 TCODE.
We02 is the TCODE to see the IDOC lists.
WE19---> To test the IDOC
BD87---> Reprocess the IDOC
Then you need to know about IDOC & Message type
Message type gives the meaning of the IDOC.
You can view all the Message/IDOC type in the table EDIMSG.
Still if u want more info. you can suit anything.
Thanks,
Eswar

Similar Messages

Cutom T-Code for seding customer details thru IDoc Debmas

Hi Experts,
I have a requirment where in.. I need to send customer details thru IDoc from a custom screen which has cutomer text box and a submit button. After entering cutomer and clicking on submit debmas06 Idoc has to be triggered.
I am not an ABAP expert... please help me with process on devloping the above reqirment.
This is a critical requirment please help ASAP.
Thanks,
Suma

Hi,
u have to use standalone program..iam giving one sample code..aong with u have define the RFC (SM59,WE21(Create port),WE20(create partner profile,BD64 distribute model view)...u have to do..
when u press on submit button,,,
*& Report ZZ_Program_To_Create_Idoc
report zz_program_to_create_idoc .
tables: ekko,ekpo.
selection-screen skip 3.
selection-screen begin of block b1 with frame title titl.
selection-screen skip.
select-options s_ebeln for ekko-ebeln.
selection-screen skip.
selection-screen end of block b1.
data: header_segment_name like edidd-segnam value 'Z1EKKO',
item_segment_name like edidd-segnam value 'Z1EKPO',
idoc_name like edidc-idoctp value 'Z19838IDOC1'.
data: header_segment_data like z1ekko,
item_segment_data like z1ekpo.
data: control_record like edidc.
data: messagetyp like edmsg-msgtyp value 'ZZ9838MESG1'.
data: i_communication like edidc occurs 0 with header line,
i_data like edidd occurs 0 with header line.
data: begin of i_ekko occurs 0,
ebeln like ekko-ebeln,
aedat like ekko-aedat,
bukrs like ekko-bukrs,
bsart like ekko-bsart,
lifnr like ekko-lifnr,
end of i_ekko.
data: begin of i_ekpo occurs 0,
ebelp like ekpo-ebelp,
matnr like ekpo-matnr,
menge like ekpo-menge,
meins like ekpo-meins,
netpr like ekpo-netpr,
end of i_ekpo.
start-of-selection.
select ebeln aedat bukrs bsart lifnr from ekko
into table i_ekko where ebeln in s_ebeln.
select ebelp
matnr
menge
meins
netpr
from ekpo
into table i_ekpo
where ebeln in s_ebeln.
control_record-mestyp = messagetyp.
control_record-rcvprt = 'LS'.
control_record-idoctp = idoc_name.
control_record-rcvprn = '0MART800'.
loop at i_ekko.
header_segment_data-ebeln = i_ekko-ebeln.
header_segment_data-aedat = i_ekko-aedat.
header_segment_data-bukrs = i_ekko-bukrs.
header_segment_data-bsart = i_ekko-bsart.
header_segment_data-lifnr = i_ekko-lifnr.
i_data-segnam = header_segment_name.
i_data-sdata = header_segment_data.
append i_data.
select ebelp
matnr
menge
meins
netpr
from ekpo
into table i_ekpo
where ebeln = i_ekko-ebeln.
loop at i_ekpo.
item_segment_data-ebelp = i_ekpo-ebelp.
item_segment_data-matnr = i_ekpo-matnr.
item_segment_data-menge = i_ekpo-menge.
item_segment_data-meins = i_ekpo-meins.
item_segment_data-netpr = i_ekpo-netpr.
i_data-segnam = item_segment_name.
i_data-sdata = item_segment_data.
append i_data.
endloop.
clear i_ekpo.
refresh i_ekpo.
endloop.
call function 'MASTER_IDOC_DISTRIBUTE'
exporting
master_idoc_control = control_record
OBJ_TYPE = ''
CHNUM = ''
tables
communication_idoc_control = i_communication
master_idoc_data = i_data
exceptions
error_in_idoc_control = 1
error_writing_idoc_status = 2
error_in_idoc_data = 3
sending_logical_system_unknown = 4
others = 5
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
else.
loop at i_communication.
write: 'IDOC GENERATED', i_communication-docnum.
endloop.
commit work.
endif.
initialization.
titl = 'ENTER THE PURCHASE ORDER NUMBER'.
Regards,
Nagaraj

Details about IDOC

Dear all,
           please give me detail about IDOC i IDES . I dont know about the IDOC.
Thanks& regards
                                                                  sourabh

Hi Sourabh,
IDoc refers to Intermediary Document.
I is primarely a Intermediary Document that is being used for data flow between SAP and other Third Party Tools.
When the user is using a Third Party tool to enter data instead of SAP, and this data has to be moved into SAP, then a I DOC is being created, where in we specify the matching fields between SAP and the fields in the Third Party.
This is used noth ways i.e for receiving data and also sending data to Third Party Tool.
Once the I DOc is being created, we provide the information to EDI consultant who would provide the required link between SAP and the Outside Tool.
Further we use T code WE19 for creating a I DOC and WE02 for viewing it
Hope I have provided enough information to you regarding I DOC.
Regards
Phani

How to populate address details in IDOC

HI,
I am creating customer master using OILDEB06 IDOC.
However I dont see the fields like SMTP_ADDR, SORT1, Street 5 etc in the idoc segments.
How do I pass all the address details along with my IDOC.
Do I need to use some BAPI or am I missing something inMapping.
Appreciate your help.
Thanks and regards

These are additional address fields which are part of 'Central Address Management'. Pasted below is the documentation associated with it. Basically, you need to add these separately.

Additional address fields:
There are additional address fields available due to linking the customer and vendor master and the respective contact persons to central address management. This additional address information is stored in central address management's own tables rather than being kept in the actual master tables (KNA1 for the customer master, LFA1 for the vendor master, KNVK for the contact persons).
A separate transfer run via the ALE interface is needed to transfer this additional address information. This run should be before the transfer run for master data.
See Transfer of address data.
If you use number ranges with internal number assignment when creating new customer and vendor masters, the number which is used to identify the master object in the system must be determined beforehand due to address information and master data being transferred separately.
You can determine the numbers using the following BAPIs:
BAPI_VENDOR_GETINTNUMBER (for the vendor master)
BAPI_CUSTOMER_GETINTNUMBER (for the customer master)
BAPI_PARTNEREMPLOYEE_GETINTNUM (for the contact persons)
Master data fields for which there is a counterpart in central address management (such as name, street, or telephone number) continue to be filled in the actual master tables. The formatting for these fields within central address management is different from the original formatting of the fields without the link to central address management. We therefore recommend that you only transfer the data for such fields when transferring central address management address information.
Here is the documentation on transferring address data.

Transfer address data
You can use the DX Workbench (transaction SXDA) to transfer address data.
Create a transfer project using the following object types:
BUS4001 for company and organization addresses (for example, customer address, vendor address, other office address of contact person)
BUS4002 for private addresses (of contact person)
BUS4003 for office addresses (composite work address of contact person).
The address data is entered by the SAVEREPLICA-BAPIs of these three object types.
For more information about these BAPIs and their interfaces, in particular the meaning of the key fields, see "Distributing addresses via ALE" by choosing Basis --> Basis Services/Communication Interface --> Business Address Services in the SAP Library.
You can create example files for the DX Workbench from existing address records in the system (for example, in a customer master record ) with the programs RSDXBUS4001, RSDXBUS4002 and RSDXBUS4003. These example files show the meaning of all fields in the Business Address Services BAPI interfaces.
The programs have the same input parameters as the SAVEREPLICA-BAPIs.
Please reward and close the post once answered.
Srinivas

Problem update IBAN bank details with IDOCs segment E1KNBKM

Hi all,
i use Idoc DEBMAS07 in which i use the segment E1KNBKM to create IBAN in customer bank details. If bank details do not exist, the IDOC is integrated, IBAN is created.
If i recreated the same Idoc, with same data (just change bank name) the Idoc is in error with the message : 'No batch input data for screen SAPMF02D 0130'.
In debugging, we see that the dynpro sequence is wrong. For vendors it's work. I can create and update IBAN.
i don't find SAP notes, or help forum on this problem.
Any ideas ?
Thanks
Edited by: ToraTora on Aug 17, 2011 11:16 AM

maybe you are the first who encountered this error, open a call at SAP yourself

Sending vendor details through IDOC

Hi all,
I want to transfer all vendor details for all vendor master table through IDOC.
is there any standard IDOC for this?
thanks.

Hi,
First of all do the ale settings using below steps.
Step1: Creation of Logical system u2013 Transaction BD54
Step 2: Assigning client to Logical System u2013 Transaction SCC4
Step 3: Creation of RFC destination u2013 Transaction SM59
Step 4: Port generation u2013 Transaction WE21 - Port is required for the outbound message type and hence port generation is required only at the sender.
Step 5: Creation of partner profile u2013 Transaction WE20
Both outbound and inbound partner profiles need to be created.
6: Creation of Distribution Model u2013 Transaction BD64 -
Then use transaction BD14 to send your vendor data.
Thanks,
Asit Purbey.

Populating bank details in Idoc basic type PEXR2002 message type PAYEXT

Hi,
I need to populate the bank details in E1IDBO2 I2. however, this segment appears on the idoc if i use RVND free form payment and release it.
This is not happening if i use FB60. i couldn't see the E1IDBO2 I2 segment at all.
Is there any setting in config to make this segment appear on the Idoc.
Any thoughts on this.
Thanks.

figured it out. Thanks.

Message type details of idoc

Hi ,
Is there any table where i can find message type details of an idoc like who created it , last changed by ??

I wanted creation date and last changed for a particluar message type and not the idoc ....
I think this concept is not there is SAP ...
Anyways thanks for the help ....

Passing only item level details through IDOC

Hi All,
I have a requirement whrerein I am using the standard ORDERS05 IDOC without any additional enhancement.
The current scenario is that whenever there is a change in any of the line items of a PO, the entire PO is passed through IDOC to XI.
Now, the requirement is such that if there is a change in any of the line items in the PO, then only the details of that line item should be passed through the IDOC instead of the whole PO.
Please let me know how can this be achieved.
Thanks,
Dawood.

Hi,
You have to find out the corresponding exit where Idoc segments are getting filled. In the exit, clear the other details from segment and populate the require data.
Regards,
Piyush

Vendor details. IDOC help.

We have two different SAP Systems. By using the message type ADRMAS we
are sending Vendor address details to another system ( Used ALE Cocept)
Now i want to block the updation of telephone number, email, fax in the receiving system.
the inbound idoc is being processed by IDOC_INPUT_ADRMAS.
I am unable to find user exit or BADI for the inbound idoc function module. Is there any way to block the updation
of vendor details on the receiving system.
Please help.

Hi,
1. Create a rule, by giving your Segment name(Give the segment where in your field exists).
2. Choose Maintain Rule(Select your rule which was created in above step).
3. Now all the fields which are avlbl in your segment will appear.
4. Double-click on the field for which conversion rule to be maintained.
5. Choose option (Convert sender fields) and Under Rule type give your SAP field name. Click on Conditions give the value to be maintained, if you want space to be populated then give slash (/) . Come back to main screen.
6. Now the last step,Assign message type for newly create rule. here you need to maintain the source and destination systems names along with segment type and conversion rule.

Posting of bank detail through IDOC from IBM Websphere

Hi
I am facing a problem during the seletion of the Basic IDOC type in the websphere .I trying to get the bankdetails of the business partner , for that I have selected the Basic Idoc type in the configaration of the IBM websphere BUPA_C_BANKDETAIL_ADD01.
But after the seletion when we try to connect its showing error like "Segment couldnot be read for the release 700"
I have checked with the release of the SAP also , it is 700 only .
Can anyone please help me out in this matter , its really urjent .
Thanks & Regards
Debasri Sarkar

Hi,
Have read the documentation for bapi BAPI_ACC_DOCUMENT_POST and check for documentation import parameter EXTENSIONIN 2
Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIO
Description
This enhancement structure can be used to transfer additional fields.
There are four fields available for each data record (VALUEPART1 - 4), which each contain 240 characters. A defined ABAP dictionary structure can be transferred in the field STRUCTURE, on the basis of which the field contents are read.
The accounting document can be supplemented and changed in an implemented BAdI ( ACC_DOCUMENT) before the active accounting component is called.
The class CL_EXM_IM_ACC_DOCUMENT is available as example implementation. Here, for each data record of the parameter that is transferred the ABAP dictionary structure is checked and the content of the fields VALUEPART1 to -4 is set in the structure. If the structure that is transferred contains a field POSNR, the associated lines of the accounting document are updated using the contents of the enhancement.
a®

Can anybody explain all the details about idoc like configuration settings etc..

Hi all can anybody explain the idoc configuration settings, communication channels sender and receiver settings

Hi,
Common steps in both Sender and Receiver:
Create logical system and assign to client
Create RFC Destinations in SM59
Create RFC Ports in WE21
Steps in Sender
Create table in SE11 and insert data
Create Segments in Tcode WE31.Define the table fields in segment
Create basic IDOC type in WE30.Specify the above created segment name,save and release the IDOC
Create message type in WE81
Assign message type to IDOC type in WE82 and release
Create partner profile in BD64,add the message type ,specify sender,receiver,message type and generate partner profile and execute.Distribute the model view
Check the partner profile in WE20
Develop a report in SE38 with code that transfers the data from source to destination
Execute the report and specify the fields to be transferred
Check the control records in WE02
Steps in Receiver:
Create an update function module in SE37
Assign the function module to logical message
Define input method in Tcode BD51
Create process code in WE42
Generate partner profile in BD64
After executing the report in sender system check in the destination system table wheather the fields are transferred
In this case a custom table has been created in sender and receiver with same structure.We can even transfer the standard table fields by using idocs
Thanks & Regards,
Sravanthi Polu

Please Send Details on IDOCS

Hi all,
Can u please Post me pdf's,sims.... on idocs.
My mail ID:[email protected]
I would like to understand the IDOC concept and How it is used in XI.
Thanks
Srinivasa

Hi,
see the below links also,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9913a954-0d01-0010-8391-8a3076440b6e
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
Regards
Chilla..

Open Sales orders through IDOC

Hi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any IDOC message type available for this in SAP R/3 4.7 version or is there a standard solution of sending these details through IDOC
Regards
Anandh

Hi
We are trying to send the list of open sales orders of a customer in an IDOC to the customer. For example, if the customer has got 15 sales order to be delivered to him , he needs the details of all these 15 orders in an single IDOC
Is there any IDOC message type available for this in SAP R/3 4.7 version or is there a standard solution of sending these details through IDOC
Regards
Anandh

Scenario IDoc-XI-FlatFile

Hi,
I am trying to Push Idoc from SAP R/34.7 to Flat File thru XI.Message Type is HRMD_ABA.The Idoc is forwarding successfully from SAP R/3,But I am not able see the details and Idoc in XI at all even though in sxmb_moni as well as at Message Display Tool.Earlier i have forwarded so many Idoc's like MATMAS01-04,CREMAS,Customized Idoc's etc to the Flat File Successfully and monitored at XI.This time i am not able to monitor even at XI.Ne messages are displaying.
Plz tell me how to resolve this issue..
Regards
Sridhar Raju Mahali

Hi
Go thru this Problem Analysis Guide on Sending an IDoc through XI Failedhttp://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Hope it helps
Regards
Arpit

Details on idoc

Similar Messages

Maybe you are looking for