Clarification on the E1EDPA1 Segment in IDOCS

Hello Team,
I have this doubt,
For an inbound IDOC (orders05) , I just got to know that segment E1EDPA1 relates to partner information at the item level,
I am trying to loop the internal table IDOC_DATA for segment E1EDPA1 and extract the partner details (partn,parvw) for each segment.
But i'm just confused about this..
If we mean that the E1EDPA1 segment relates to the partner information at the item level, does that Imply that we will have the same number of E1EDPA1 segments as the number of line items in the IDOC?
In other words, lets say the Inbound IDOC contains 3 line items, would that mean we have 3 E1EDPA1 segments in the IDOC, where each segment correspond to a single line item?
Any help would be highly appreciated..

when you dbl-click, it will ask you to create this include and will also warn you, once it warns, you go ahead by pressing enter key.
and you end up within this include where you can write your own code.
Regards.

Similar Messages

Chanding the content in an IDOC segment at runtime

Hi Experts,
I have funny issue with modification of the data in an IDOC segment. Below is the description of the issue:
     I am using the IDoc type FIDCC2.FIDCCP02. I have to populate the value for field 'KTOSL' of the
     segment E1FISEG. I wrote the logic in user exit EXIT_SAPLF050_006. It is getting triggered and the
     logic is updating the values in the IDOC_DATA internal table properly.
     When the IDoc is generated, I observed that the value for this field is not updated in IDoc Segment.
Could you please suggest where I went wrong.
Ramana

Hi Neha,
Thank you for the responce.
We need not to fill all the 21 fields before the field KTOSL. Because I was using the work area to modify the internal table based on the index.
One thing I can conclude is that we cannot change the values in the standard segments of a stanrd Idoc type. By the time you enter in the processing Functinal Module, the Idoc number would have been generated. So the modification we carry out are just updating the internal table which of no effect. The right way is that find the place where the values getting updated to the data base and change values as required. These changed values can be founf in the data base but not in the IDoc generated.
Neha one more query for the clarification,could you ever delt with the down payment requests through IDocs. If so please share the details.
Ramana

Populating the Conditions segment in PORDCR102-PO create IDOC

Hi Gurus,
Iam populating some fields in the E1BPMEPOCONDHEADER segment of the IDOC PORDCR102. But the condition record is not getting generated in the PO.
Kindly can anyone throw some light on the mandatory fields that needs to be populated in this segment and is there any necessity to populate some other linked segments along with this segment inorder to get the condition record created.
I am populating some fields below :
E1BPMEPOCONDHEADER-COND_TYPE = 'ZA00'.
E1BPMEPOCONDHEADER-COND_VALUE = '12'.
E1BPMEPOCONDHEADER-CURRENCY = 'USD'.
E1BPMEPOCONDHEADER-CURRENCY_ISO = 'USD'.
E1BPMEPOCONDHEADER-COND_UNIT = 'EA'.
E1BPMEPOCONDHEADER-COND_P_UNT = '1'.
E1BPMEPOCONDHEADER-APPLICATIO = 'EF'.
Please help
Thanks
Venkatesh P

you need to pass
CONDITION_NO
ITM_NUMBER
in 1BPMEPOCONDHEADER and 1BPMEPOCONDHEADERX also..

Populating the Conditions segment in PORDCR101-PO create IDOC

Hi ,
Iam populating some fields in the E1BPMEPOCONDITION segment of the IDOC PORDCR101. But the condition record is not getting generated in the transaction ME22N.Kindly can anyone throw some light on the mandatory fields that needs to be populated in this segment and is there any necessity to populate some other linked segments along with this segment inorder to get the condition record created.
Iam passing the below given fields.
E1BPMEPOCOND-ITM_NUMBER
E1BPMEPOCOND-COND_VALUE
E1BPMEPOCOND-CURRENCY
E1BPMEPOCOND-CURRENCY_ISO
E1BPMEPOCOND-COND_UNIT
E1BPMEPOCOND-COND_P_UNT
E1BPMEPOCOND-CHANGE_ID .
Thanks,
Kittu.

hi,
I am having the same requirement i.e file-xi-r3 create po, can any one tell me the necessary steps needed for this. i am new to all this and still learning things, so please help me.
thank you
email [email protected]

Populating the custom segments for the Basic type attached to HRMD_A (IDOC)

Hi,
I've enhanced a few infotypes and want the new fields to be available in an IDOC created through the program RHALEINI.
Here are the steps I followed.
Step 1 :(we31)
We created new segment Z1IT023 , containing all the fields from infotype 0023 along with the custom fields added.
Step 2 :(we30)
We created an extension of IDOC type HRMD_A07 by name HRMD_EX to include this segement.
Step 3 :
We added an entry in table EDIMSG against message type HRMD_A , with base type : HRMD_A07 , extension : HRMD_EX , version : 700
Step4 :(we20)
Now , we made changes to partner profile by adding entry for message type HRMD_A with base IDOC type as HRMD_A07 and extension as HRMD_EX
Step5:
We changed the entry in table T777D and specified the IDOC segment as Z1IT023.
Step6.
We then tried to execute the report RHALEINI to generate the IDOC. The IDOC got created, but it didn't have the data for the segment Z1IT023.
In fact, there is a different solution to this... by adding the custom segment(containing nly the new infotype fields) as a child of the original segment E1P0023 and then writting code in the user-exit to populate the segment, but our intension is to have a single segment with all the infotype 0023 data. Besides, I believe in HR, making an entry in T777D should free us from writing any code for populating the IDOC segments.
Can anybody please suggest me, where am I going wrong. How can the new segments be populated automatically.
Thanks in advance.
Sujit.
Responses will be suitably rewarded.

Hi,
Did u get any exit to populate the custom segment?
Thanks,
San

Idoc to jdbc :On the basis of field WERKS, the child segments should get re

We are working on IDOC to JDBC scenario.
In my IDOC INFREC.INFRECMASS01 has one segment E1E1NAM( parent segment), inside this parent segment we have one child segment E1E1NEM containing two lines. On the basis of one field WERKS, the child segments should get repeated in the target but in the target side we are getting only one of the values of WERKS .
We have used SPLIT BY VALUE(each value) on WERKS but still only one of the values are coming on the target side .
pl help
rgds
arun

ahi arvind ,
i sent the source /target every thing in ur rediffmail id , we tried to change the context of WERKS TO E1EINAM ,removed split by value , but got an error
Cannot produce target element /ns0:MT_IB_VENDORISL/STATEMENTNAME[2]/si_sku_vendor_link/ACCESS. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
pl suggest ...
rgds
arun

IDOC : navigation to the errored segment ...IMPORTANT

Hello all...
In transaction BD87 ...if a user selects a particular errored out IDOC (with status 51) with some error ina segment ( lets say segment 3) and clicks on it..
I need to take him directly to the errored SEGMENT 3 screen(<b>Display data record</b> <b>for IDOC screen</b>) ...
i need to skip all the screens in between,which he has to navigate to reach the segment...
how can i do it?
I had to copied RBDMON00 program( BD87) into my z program...now i need to find out the way to go to errored segment directly based on segment number displayed skipping the navigation screens in between....
Hope u got my question...
Thanks...

Hi Aday,
Please check this FM EDI_DOCUMENT_TREE_DISPLAY.
I am afraid there is no standard FM available to get the error segment of an IDoc. Perhaps you may want to write your own codes to go to table EDID4 to get the corresponding segment.
Regards,
Ferry Lianto
Message was edited by:
Ferry Lianto

How can i check the segment in idoc.

hi gurus,
how can i check the segment in idoc.please help me as

Hi Rohit,
In WE02/05 U can view the IDocs.
Since u r having the IDoc with u, Double click the Idoc no. and it will take you to screen where it will show you all the segments of IDoc. Here you can check which segment is giving error.
Go to WE60/63 which shows the detailed documentation in the MySAP environments if u have been using the old 4.6c systems. In 6.10 since the documentation is not available ,modify your personal settings to show the documentation by default; In 6.10 in transactions WE60 and WE63, documentation is no longer generated by default for the segment fields when the documentation is generated. To activate the generation of the documentation from the corresponding data elements, proceed as follows: WE60/WE63. > Goto > User settings. Here you must set the indicator for 'Display of the documentation' under 'Display attributes for IDOC types' and then save the change. Now the documentation is also displayed for the segment fields when WE60/WE63 is executed.
**Reward points if u find this useful.
Thanks & Regards,
gyanaraj

Limit the no of segments per IDOC to less than the current default value

Hi friends,
please help me in the following issue.
The possibility to limit the number
of segments per IDOC to less than the current default value.
Purpose is to limit the traffic of IDOCs between systems.
How to solve this issue to avoid traffic
Thanks in advance.
Regards
Sandeep

Hi Kiran,
Actually we are using standard ones at that time we are getting prolems. When using custom developed ALE's
we are putting segment size is less.To decrease segment size is there any filtering at the sender side? To change segment size may be nedd to take help form SAP.
But if have filtering at any level from sender side need to confirm before consult SAP.
Regards
Sandeep

How to cancel the release of the current segment definition-WE31-IDOC?

Hi Experts,
Am trying to add a new field to a existing custom segment type/defination. This segment type is already using in the system.
So, went to WE31 and pressed the PENCIL button for changing/adding my new field, but am geting the below message,
(1)pls let me know that does it mean CANCEL the release (Menu>Edit>Cancel Release)? if so, Can I go ahead and use this CANCEL the release? do I need to take any pre-requisites as this segment is already relased?
(2)But, you know there is another option saying 'ADD VERSION-Shift+F5', if I choose this option, its also taking me to a screen where in I can add new fields so which is correct option for me is it either (1) or (2)?
Current segment definition Z_segment_defination can no longer be changed
Message no. EA666
Diagnosis
The current segment definition Z_segment_defination of segment type Zsegment_type is already released.
System Response
The segment definition cannot be changed.
Procedure
You can either add a new segment definition or cancel the release of the current segment definition.
Thank you

so i tried to CANCEL the release by goiong menu pathEdit-->Cancel the release, but am getting the below error, How to fix it to add my new field?
Error while resetting release of segment
Thank you

Specific segment in idoc ORDERS05

Hi,
In purchase order, we have idocs in type ORDERS05. Someone has added specific segment under standard segment E1EDPA1.
In scheduling agreement release we have also idocs in type ORDERS05 but not the specific segment added.
Do you know in which user exit or else, there can be condition in the system which add specific segment in OREDERS05 when it is purchase order, and do not add specific segment when it is scheduling agreement release... Because I want to modifiy it to add also specific segment in scheduling agreement releases..
Thank you for your help.
Regards,
Peggy Delvincourt

Hello Madhu
The specific segment already exist (old team has create it to put others data) in the idoc type ORDERS05.
But and I do not understand why this specific segement appears only for purchase order but not in scheduling agreement release, as theses 2 types of documents are the same idoc type ORDERS05.
I think a specific code is wriiten to put "if purchase order create specific segment in ORDERS05, if not purchase order do not create specific segment in ORDERS05".
And I can't find where this condition might be, in any user exit?
Because I need to correct that and make the system create the specific segment also for scheduling agreement release...
Hope I'm clear..
Thank for your help.
Peggy.

Dates fields issue in the sales orders through IDOC

Hi all,
I'm trying to create a sales order through Inbound IDOC using IDOC_INPUT_ORDERS.
I have 2 custom fields in the sales order which are date fields.
I'm populating them from the IDOC segments(using E1EDKT1-tdid, E1EDKT2-tdline) in the user-exit just before the call trasacation statement. These dates are not coming for a few orders... but are getting populated normally for few of them.
But the tricky part is that... if I process the same IDOC for the second time.. the order created is having the dates.
My issue is that.. i need all the orders to be populated with the dates which IDOC have.
Could anyone please help me with this issue.
All the answers/replies are highly appreciated!!
Thanks for you help!

hi,
the following may be of help
There are 2 major exceptions to the batch input internal table. All text data from the segments E1EDKT1/2 and E1EDPT1/2 are not part of the batch input session. Text elements from these segments are posted directly to the data base AFTER the sales order has been created (please note: in order that item texts are posted correctly to the sales order the field POSEX from segment E1EDP01 MUST be transmitted). Also, configurable material information from the IDOC is exported to a global memory and therefore will not be part of the batch input session. Configurable material data is performed in Form CHECK_CONFIGURATION and the data is exported to global memory in the following code:
Exportiert IDOC Daten ins globale Memory
export IDOC data to global memory
call function 'CUXC_IDOC_TO_MEMORY'
       tables
            cfg_instref = xe1curef
            cfg_ref     = xe1cucfg
            inst        = xe1cuins
            part_of     = xe1cuprt
            value       = xe1cuval
       exceptions
            error       = 1
            others      = 2.
One extra piece of useful infomartion if you wish to debug the process is to set your breakpoints at the following points
for Function module IDOC_INPUT_ORDERS
include LVEDAF0F..
CALL TRANSACTION 'VA01' USING bdcdata
                            MODE input_method
                            UPDATE 'S'
                            MESSAGES INTO xbdcmsgcoll.
Now input_method is A foreground process and N for background processing but try changing it to P (pass through mode)
If you have breakpoints in va01, e.g. MV45AF0B_BELEG_SICHERN,(the part where the sales document is saved)
they will be hit, e.g
perform userexit_save_document_prepare.
perform userexit_save_document.
Lastly, don't forget using program SDJEDI , see note 380603 for more information on this
Hope this is useful
Paul Quinn

How to generate a new segment in IDoc for multiple occurance of Control Num

Hi Experts,
In my scenario, i need to generate a new segment in IDoc(Target Structure) based on Control Number Field in the Source Structure.
The segment need to be created for multiple occurance of the Control Number.
Ex:
Control Number - 100 appears 5 times in Source Structure.This control Number is mapped to one of the Field in the Segment of IDoc.
Now my requirement is to generate the Segment 5 times with respective to this Control Number.
please help me out to resolve this issue.
Thanks,
Kish.

Hi,
Here is the XML Structure of my Source:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:GoodsReceipt_MT xmlns:ns0="urn:WOL-com:XI:data:HJ:10">
   <row>
      <CONTROL_NUMBER>111</CONTROL_NUMBER>
      <LINE_NUMBER>1111</LINE_NUMBER>
      <CONTROL_NUMBER_2/>
      <OUTSIDE_ID/>
      <WH_ID>111111</WH_ID>
      <LOCATION_ID/>
      <HU_ID>11111</HU_ID>
      <NUM_ITEMS/>
      <ITEM_NUMBER>111111</ITEM_NUMBER>
      <CONTROL_NUMBER_3>LR</CONTROL_NUMBER_3>
      <LOT_NUMBER>11111</LOT_NUMBER>
      <UOM>11111</UOM>
   </row>
   <row>
      <CONTROL_NUMBER>111</CONTROL_NUMBER>
      <LINE_NUMBER>12222</LINE_NUMBER>
      <CONTROL_NUMBER_2/>
      <OUTSIDE_ID/>
      <WH_ID>12222</WH_ID>
      <LOCATION_ID/>
      <HU_ID>1222</HU_ID>
      <NUM_ITEMS/>
      <ITEM_NUMBER>112222</ITEM_NUMBER>
      <TRAN_QTY>112222</TRAN_QTY>
      <CONTROL_NUMBER_3>LR</CONTROL_NUMBER_3>
      <LOT_NUMBER>12222</LOT_NUMBER>
      <UOM>1122222</UOM>
   </row>
   <row>
      <CONTROL_NUMBER>222</CONTROL_NUMBER>
      <LINE_NUMBER>2222</LINE_NUMBER>
      <CONTROL_NUMBER_2/>
      <OUTSIDE_ID/>
      <WH_ID>22222</WH_ID>
      <LOCATION_ID/>
      <HU_ID>222222</HU_ID>
      <NUM_ITEMS/>
      <ITEM_NUMBER>2222222</ITEM_NUMBER>
      <TRAN_QTY>22222222</TRAN_QTY>
      <LOCATION_ID_2>33333333</LOCATION_ID_2>
      <CONTROL_NUMBER_3>LR</CONTROL_NUMBER_3>
      <LOT_NUMBER>22222</LOT_NUMBER>
      <UOM>22222</UOM>
   </row>
   <row>
      <CONTROL_NUMBER>333</CONTROL_NUMBER>
      <LINE_NUMBER>3333</LINE_NUMBER>
      <CONTROL_NUMBER_2/>
      <OUTSIDE_ID/>
      <WH_ID>33333</WH_ID>
      <LOCATION_ID/>
      <HU_ID>33333</HU_ID>
      <NUM_ITEMS/>
      <ITEM_NUMBER>333333</ITEM_NUMBER>
      <TRAN_QTY>33333333</TRAN_QTY>
      <CONTROL_NUMBER_3>LR</CONTROL_NUMBER_3>
      <LOT_NUMBER>33333</LOT_NUMBER>
      <UOM>333333</UOM>
   </row>
</ns0:GoodsReceipt_MT>
Now Control_Number 111 occurs 2 times, 222 & 333 occurs 1 time.
Now one IDoc for 111,222 & 333 should be generated.
But Control_number 111 appears 2 times.
Now the data in the 2 rows should be passed to Single IDoc by repeating the segments inside the IDoc.
As u said i changed the Occurance of IDoc to 0...unbound and imported as External Definition. I have done upto Generating IDoc for each unique Control_Number.
I stuck up at repeating the Segments in the IDoc.
So please help me out.
Thanks,
Kish.

Regarding new segment in Idoc

Hi,
    I have created a new segment ZDH_HAZMAT for hazardous materials for the idoc type ZDH_ORDERS and released it for purchase order. Actually modifying the segment data for already existing Idoc segments (E1EDP01) is possible and i have done it using user exit MM06E001. When a new segment (ZDH_HAZMAT) is added, it's showing a syntax error . Waiting for earliest reply.
                                                        Thank you.

Hello,
You must keep a an IF condition like this in selection program's user exit.
     if Segmetn-Name eq <New segmetn>
         break <user name>
    end.
It must stop other wise the enhancing the standard Idoc type is wrong. And so you need to check whether it is activate / released the new segment properly.
All the very best for you.
- Mohan Vamsi

What is the internal processing for idocs

Dear friends this is subbu working as a abap consultant.
can any body explain the how idocs are transfered (inbound process and outbound process)

1.Here out bound means sender.Inbound mens --receiver.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
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
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
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
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Please check this link for more information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Reward points..

Clarification on the E1EDPA1 Segment in IDOCS

Similar Messages

Maybe you are looking for