More XI 3.0-- IDoc-- R/3 - Trouble

hi,
i was trying to set up a scenario in which an idoc matmas04 is sent via XI to the receiver-R/3 instead of pure ALE/IDoc transfer.
I get the corresponding Error in the XI-Monitoring:
translated to English it says something like: Receiver Service can't be acknowledged as ALE Logical System.
As Outbound and Inbound Interfaces I use the imported MATMAS04-Idoc - I followed all the required steps in the configuration. I use Services without partner where both R/3s appear as corresponding business-services (which I set up in the SLD). Both services are labelled "receiver". The sender uses communication channel: idoc, which seems to be alright, and the receiver uses GeneratedReceiverChannel_IDoc.
on the XI in transaction idx2 the idoc-type shows up, in idx1 i declared a port for the receiving system, which is pointless i guess...
in SXMB_ADM I set the entry in configuration integration server, configuration data-idoc to XML_CONVERSION value 2...
any further ideas welcome - thanx in advance,
matthias

Hi Matthias,
I have a similar error situation like yours. Here is the snapshot of the Error ID: ATTRIBUTE_INV_RCV_SERV
Details:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_RCV_SERV</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Receiver service cannot be converted into an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any clues to fix it are appreciated.
Thanks,
Raghu

Similar Messages

Error : Document contains same order item more than once in IDOC

We have Intercompany IDOCs getting created in our system. The
trigger for this is the Billing Document in the same system in
differenct company code. The MEssage type being used is INVOIC and the
basic type is INVOIC01.
The IDOC is in the status of 51 with the error message
Document contains same order item more than once
Message No : M8 321.
Can anyone tell me why raise this error and how to resolve it?
Thanks.

What I have recently learned is that in 6.0 SAP allows the same line item to be on an idoc multiple times. However, the item has to be GR-based-IV and there has to be a unique entry in the delivery note of the GR.   I have successfully tested this in my development system.
What I can't get to work is if the GRs have the same delivery note value.   What I think is happening is these GRs are not unique so SAP cannot match a GR with an IR so it fails with this error.
Here are the examples:
Works
GR# A           deliverynote/BOL    "abcd"
GR# B           deliverynote/BOL     "efgh"
Invoice idoc
e1edp02    qualifier 016          abcd
e1edp02    qualifier 016          efgh
Doesn't work:
GR# A           deliverynote/BOL    "abcd"
GR# B           deliverynote/BOL     "abcd"
Invoice idoc
e1edp02    qualifier 016          abcd
e1edp02    qualifier 016          abcd
If anyone knows of a way to make the second scenario work, I'd like to hear your solution.
Thanks
Sandra

Send/Receive IDOCs (XML) from/to SAP R/3 with XI-SOAP without XI!

Dear SAP specialists,
(BACKGROUND) We are using the Microsoft BizTalk Adapter for SAP 1.0, developed on top of the SAP DCOM Connector (we are using the version 6.20 Patch Nr. 177), with Microsoft BizTalk Server 2002 SP1 in order to send and receive IDOC via the tRFC transport protocol. We are using the Microsoft BizTalk Adapter for SAP 1.0 since February 2002, and today we are exchanging more than 25,000 IDOC/day with this architecture.
When we migrate our SAP R/3 system to the version 4.7 with WAS 6.20, I was very enthusiastic about the possibility of sending the IDOC in XML via the standard HTTP transport protocol, because it would considerably simplify my architecture, i.e. no need of any (expensive) adapter any more! But, I had to realise that the quality of service exactly once will not be there anymore with HTTP as it exists with tRFC. Then, we carry on using the tRFC transport protocol with the adapter.
(QUESTION) But recently, I followed the SAP Course TBIT40 XI Foundations and I learn that:
1. On one hand, the XI-SOAP protocol supports the quality of service exactly once by the usage of a message GUID within the XI-SOAP envelope;
2. On the other hand, all mySAP solutions using WAS 6.20 (or higher) carry a small Integration Engine (with XI-SOAP as the native transport protocol).
Then, my question is: << Is it possible to exchange IDOC (XML) directly with an SAP R/3 4.7 (WAS 6.20) via the XI-SOAP transport protocol using the small Integration Engine embedded into it, with the quality of service exactly once? >>
Many thanks in advance and best regards,
Patrice Krakow

Hello Patrice
We have same issue. Is it possible to use IDoc (XML) directly with SAP 5.0 with SOAP (HTTP) without XI?
Since your que is three years old, I'm sure you must have found some method for this.
We'll highly appreciate your help.
Regards: Gaurave

IDOC not created in R/3

Hi,
I am sending IDOC from XI to R/3 using IDOC Adapter.
When I send around 2000 documents(2000 idoc are created in R/3)it works fine and I can see Idoc created in WE02.
But When I send more then 6000 documents,IDOCS are not created in R/3.But I can see in idx5 in XI 6000 outbound idocs.
Thanks in advance.
Rekha.

Have you checked whether the tRFC queue is full and creating with time delay ?
Try to increase remote user login parameter in the instance profile.
regards
Shravan

IDoc status 53 in employee replication from SAP HR

Hi experts,
We are having some problems in CRM BP creation with role employee.
We are using CRM 5.0 and SAP ECC 6.0 and we are trying to replicate employees information to CRM from HR.
After read the notes 934372, 615896, 550055, 363187, 312090 we made the next configuration steps in our systems:
R/3:
- Creation of connection port (trans. WE21)
- Creation of logical system (trans. WE20) and assignment of outbound message HRMD_ABA
- Creation of distribution model (trans. BD64) with all filters indicated in note 312090
CRM
- Creation of logical system (trans. WE20) and assignment of inbound message HRMD_ABA
- Creation of conversion between basic types HRMD_A05 and HRMD_ABA01 (trans. WE70) as described in note 312090
- Creation of conversion between message types HRMD_A and HRMD_ABA (trans. WE73) as described in note 312090
- Creation of external number range ZE from HR01200001 to HR01299999 (using PA04 in R3 we found the number range between 01200001 and 01299999)
- Creation of BP Grouping with the same name of number range (ZE) checked to be external too
- Update of table T77S0 (using SM30):
HRALX HRAC X
HRALX PBPON OFF
HRALX PBPHR ON
HRALX PBPON ON
HRALX PNUMB 3
HRALX PPROL BUP003
HRALX PSUBG ZE
PLOGI PLOGI MV
We know we should have the same value in R3 and CRM for PLOGI/PLOGI, so we created in CRM MV because that is the plan version used in R3. To create it, we just manually add a new row in table T778P and then selected it in table T77S0. Is this the correct way to create a plan version?
After these steps, in R3 we execute program RHALEINI with parameters:
- Plan version = MV
- Object type = P
- Object ID = an active employee
- Reporting period = all
- Transfer mode = Insert
- Receiving system:
Receiving partner No = DCRCLNT300 (logical system created in WE20)
Message type = HRMD_ABA
And everything looks fine in R3.
In CRM, using trans. WE05, we can see that the iDoc is created, apparently without problems with status 53 - "Applicaton document posted" but the business partner is never created.
Did we miss some configuration steps?
Should we do something more after see the iDoc in CRM to create BP?
Thanks in advance.
Alda

hi pratk bhai,
ya i have done the same setting what Ada has mentioned eariler,
and as of your suggestion to maintatin the mandatory infotype, i have even done tht,
after running RHALEINI in R3, the status is all green here.
when i run the tcode BD87 to check the Idoc status its showing fine (Error free).
now, through tcode se38 the report CRMHRALE_CENTRAL_PERSON shows all the employees as status green,,
but the partner number is not getting generated. ( i have used HRALX-PNUMB= 3 (Prefeexing the number range coming from R3)).
kindly advice me what should be done in order to generate a BP number for the replicated HR Employee.
best regards,
Madhup

File to IDOC:how do i relate inbound idoc with generated idoc in the R/3

hi experts;
can any body tell me how can i relate the IDOC number genrated in the PI with the generated IDoc number in the SAP R/3 system for file to IDOC scenario?
in SAP PI for tcade idx5, idoc no is:12002
but in SAP R/3 in tcode WE05, idoc no is:846915
how can i know a particular message (in SAP PI) created a particular idoc in the backend SAP R/3 System.
thanks in advance,
kumar

Hi Kumar
at the time of testing you have to note down a time at what ur file got picked up ok
then go to we05
-> give the date on CREATED ON field.
-> then in BASIC TYPE field select your particular IDOC CREMAS05 or whatever, see the TIME field that you have noted down at the time of testing, if that is matching means that is ur latest IDOC you have tested.
-> one more thing, tha last IDOC showing in the list means that is your latest IDOC you have tested.
Hope i have helped you, points plz
Warm Regards
Dheeraj Kumar

URGENT- IDoc Packaging - Que- Michal blog

Hi,
I was following Micahl's blog - for idoc packaging -
/people/michal.krawczyk2/blog/2007/12/02/xipi-sender-idoc-adapter-packaging
But there is another blog, which also by Michal.
/people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change ,
which is also mentioned in OSS note: Note 814393 - Multiple IDoc instances in an XI message.
Do I need to do both of them to achieve the Idoc Packaging.
I also noticed that in the first blog, it is about pushing Idocs out of R/3 system and in the second blog it is the other way round.
Can any one please clarify.
reg

with the first blog, how does sxmb_moni screen looks like - R3 system, XI. On XI it should not make any diff as XI is still splitting the packages.
Yes you are right...On R3 system, if packaging is done, then you will find all IDOCs as single message. As you said on XI it will not make any difference.
With the 2nd blog, XI would show single message for each package, but with more instances of the Idoc payload. (As shown in the first blog - look at the 2nd pic). Which means that you saving the queues but the payload size is more here in this case.
Yes..It show single message with more instance of IDOCs. You are right about saving the queues and payload size is also more

IDoc related doubt .......Please see..

Hi all,
What is message in Idoc? Please tell in layman terms. Is it part of the data records? Please point me to related files or threads.
Thanks,
Charles.

Hi,
The Message type are mornally assign to SAP document type (IDOC). A message type represents a business function ( Purchase order data, Invoivce data etc). The technical structure of the message type is the IDoc type.
An IDoc type can be implemented for various "logical" messages; one message can also be assigned to different IDoc types (m:n relationship).
The message is defined by the values for message type (required), message code (optional) and message function (optional). These three fields belong to the key fields in the partner profiles, which are used, for example, to determine inbound processing. If the 'Message type' field is not maintained (e.g. in the case of a control record from Release 2.1, in which MESTYP did not exist), the IDoc Interface uses the value from STDMES (EDI message type).
Example
The message ORDERS (= message type) identifies purchase orders (outbound) and sales orders (inbound).
Check transaction WE81, for Message type in SAP.
Also, follow this link for more infomation related to IDOC processing
http://help.sap.com/saphelp_46c/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm
Check this lin for information about "Distribution Using Message Types".
http://help.sap.com/saphelp_46c/helpdata/en/78/2174a351ce11d189570000e829fbbd/frameset.htm
Let me know if you need any other information.
Regards,
RS

Bundling ORDERS05 IDOC

Hi all,
We have a problem with bundling the IDOCS in Message Mapping. We have a requirement to convert more than one ORDERS05 IDOCS to one flat XML file.
When the IDOC has the following data, the mapping works well:
Input IDOC:
IDOC 1:
ORDERS05
- E1EDP01
--- POSEX 0010
- E1EDP01
--- POSEX     0020
- E1CUCFG
--- POSEX     0010
E1CUVAL     10-1
E1CUVAL     10-2
- E1CUCFG
--- POSEX     0020
E1CUVAL     20-1
E1CUVAL     20-2
IDOC 2:
ORDERS05
- E1EDP01
--- POSEX     0010
- E1EDP01
--- POSEX     0020
- E1CUCFG
--- POSEX     0010
E1CUVAL     10-1
E1CUVAL     10-2
- E1CUCFG
--- POSEX     0020
E1CUVAL     20-1
E1CUVAL     20-2
Output Message:
IDOC 1:----
IDOC 2:
Position number:      0010----
Position number:      0010
Configuration1:     10-1----
Configuration1:     10-1
Configuration2:     10-2----
Configuration2:     10-2
Position number:      0020----
Position number:      0020
Configuration1:     20-1----
Configuration1:     20-1
Configuration2:     20-2----
Configuration2:     20-2
However when you miss one E1CUCFG node, you will get a confusing result:
Input IDOC:
IDOC 1:
ORDERS05
- E1EDP01
--- POSEX     0010
- E1EDP01
--- POSEX     0020
- E1CUCFG
--- POSEX     0020
E1CUVAL     20-1
E1CUVAL     20-2
IDOC 2:
ORDERS05
- E1EDP01
--- POSEX     0010
- E1EDP01
--- POSEX     0020
- E1CUCFG
--- POSEX     0010
E1CUVAL     10-1
E1CUVAL     10-2
- E1CUCFG
--- POSEX     0020
E1CUVAL     20-1
E1CUVAL     20-2
Output Message:
IDOC 1:----
IDOC 2:
Position number:      0010----
Position number:      0010
Configuration1:     20-1----
Configuration1:     20-1
Configuration2:     20-2----
Configuration2:     20-2
Position number:      0020----
Position number:      0020
Configuration1:     10-1----
Configuration1:     10-1
Configuration2:     10-2----
Configuration2:     10-2
We have tried standard functions like: useOneAsMany, CreateIf, if, ifWithoutElse, collapseContext, etc. in the graphical mapping tool but it doesnt work.
Could you please take a look at this problem?
Appreciate any help on this,
Kind regards
Kamran Vakili

Ive solved this problem

What is the difference beween idoc package and idoc collection

Hi friends,
    i am unable to understand difference betwen Idoc package and Idoc cillection.
    Please give me clear clarification.
Thanks and regards
Bhanu

Hi Bhanu,
Apart from the replies above, in case you're looking for an answer from ECC perspective, here are some inputs: (ECC is considered as sender here)
1. IDoc Collection:
   This will collect the IDocs and will not immediately send it to the target system after they are created. Program RSEOUT00 can be later scheduled for these collected IDocs to deliver them to the target. You can treat this as a park and process approach which proves useful in several business scenarios.
This standard link gives more insight:
SAP Library - IDoc Interface/ALE
2. IDoc Packaging:
    This defines the number of IDocs to be packed and sent in 1 RFC call (tRFC). If you set is as 20, then 20 IDocs will be sent in 1 tRFC request. This doesn't connote whether the IDocs will be triggered immediately or later, this just talks about the bundling of IDocs per RFC call.
Hope this helps.
Regards,
Abhishek

CRMXIF_ORDER_SAVE_M02 Idoc status 53, but no transaction created in CRM

Hi,
Via transaction WE19, I have filled idoc CRMXIF_ORDER_SAVE_M02.
When I click on "standard inbound", the idoc is generated and get the status 53 which seems to be OK, but no Transaction is created in CRM.
Any idea ?
I've tried to fill more fields of the idoc structure but nothing changed.
Is there a step I am missing ?
What's the use of these fields in the idoc structure ?
APPL_SNAME
DATAX
Thanks for any help !
Aussie

Hi Aussie,
In transaction WE19 for the Idoc CRMXIF_ORDER_SAVE_M02.
It has no problem with data instead check the receiver Port, sender port, Partner No,
Partner type, role . If these didnot match then the data will not be reflected in CRM.
regarding APPL_SNAME: it is not relevant with the problem, its a structure of teh description.
Please see the ports.
have a nice day!!
receiver Port , sender port, Partner No, type, role Partner profile not maintained
Name of structure for the technical description
With regards,
Lakshmi Narayana

Question about inbound PEXR2002 IDOC

Hi,
How would you handle multiple deductions (2 different deductions with different reason codes) for the same invoice? What are the segments that are going to be used for this purpose?
Thanks,
Nile.

Hi ,
check this link...it gives more info
file to idoc scenario
sekhar

Delivery order by IDOC

Hi Experts,
I'm trying to make a delivery order by IDOC type DELORD (ORDERS05). Does any one process with this type of massage?
I create several orders, but I still have a problem with orders. They look almost the same but still not working.
Could some one write me requirements for this massage? For example links between Idoc segments and fields from Schedule agreements.
Any help will be appreciated.
Edited by: Michal Jesionek on May 31, 2008 4:15 PM

HI ,
Please find the info as follows.
E1EDP20 : IDoc schedule lines
Segment definition E2EDP20001 Released since Release 46C , Segment length: 0061
WMENG : Scheduled quantity
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 001, Offset : 0063. external length : 000015
AMENG : Previous scheduled quantity
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 002, Offset : 0078. external length : 000015
EDATU : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 003, Offset : 0093. external length : 000008
EZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 004, Offset : 0101. external length : 000006
EDATU_OLD : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 005, Offset : 0107. external length : 000008
EZEIT_OLD : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 006, Offset : 0115. external length : 000006
ACTION : Action code for the item
internal data type : CHAR
Internal length : 000003 characters
For more information use the idoc type see the structure in we60.
Thanks,
Pramod

Debugging customized function module when Idoc is triggered via ALE

Hi,
Whenever we save the billing document, an outbound idoc is triggered via ALE. The logic for the data to be included in the idoc is written in a customized function module.
However we are making some changes and would like to include some more data in the idoc. But we find that when we put a breakpoint in the function module, on saving the billing document, the flow does not stop at the break point. We are 100% sure that the code in the function module gets executed based on the data in the idoc.
How do we get into debug mode and break the flow in the function module so that we can debug in the function module?
Any help would be greatly appreciated.
Thanks in advance,
Mick

Hi Mick, this might be of some help 4 u.
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view
Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 - Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Create Model View
Tcode BD82 - Generate partner Profiles & Create Ports
Tcode BD64 - Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE - for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 - Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 - Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 - Send Material Data
Tcode WE05 - Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
cheers,
Hema.

IDOC STUDY MATERIAL

i'm new to idoc. i have knowledge of ABAP and want to know how to create IDOC. i could not follow the materials from sapbrain....

Hi,
see the following steps
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/
IDOC Type : Defines the Structure(Hierarchy of Segments) based on which the IDOC(Data records) will be generated.
IDOC Type Can be
1. Basic Type : These are IDOC types delivered by SAP like MATMAS03
Customers can also create Basic idoc types
2. IDOC Extension: These are Created only by customers to Extend the Existing IDOC Types by adding Additional Segments.
For more information about ALE / IDOC check these links
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
Regards,
Satish

More XI 3.0-- IDoc-- R/3 - Trouble

Similar Messages

Maybe you are looking for