Creating ALE
HI,
I AM CREATING ALE, BUT WHEN IN BD64 I AM SAYING GENERATE PARTNER PROFILE AND EXECUTE.
IT IS GIVING ME FOLLOWING MESSAGE-
' NO MESSAGE HAVE BEEN DEFINED FOR THE SELECTION CONDITIONS IN MODEL'.
ANYBODY PLZZZ HELP ME.
THANKS.
Hi Siddiqui,
I think you haven't saved the model view before genering the partner profile. Please save it after assigning the message type to model view and then generate partner profile.
Check this link for same:
ALE configuration for pushing idocs from SAP to XI
step name : Create a Distribution Model by selecting u2018Create Model Viewu2019:
Regards,
Sachin
Similar Messages
-
Hello,
Could you give me step by step procedure to create ALE.
Thank youHi,
IDOC
http://msdn2.microsoft.com/en-us/library/ms942196.aspx
Idoc configuration Required~
in R/3
1) RFC destination pointing to XI
2) WE20 Partner Profile entries
in XI
1) RFC destination pointing to R/3
Go thru this -
configuration steps for receiving idoc in xi from r/3
Go thru these for Idoc to XI scenarios-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani -
Create AlE Relationship between two company code F210 to FN21 (UHP To UPI)
Hi,
I want to know how to create ALE realtion ship between two company code ( F210 to FN21(Server name UHP to UPI ) and how to process it?
Please reply ASAP.
Regards,
AchinHi Sathish,
Thanks for reply!..
But My question I want to Add ALE relationship between two company code F210 to FN21 (UHP(Production server) To UPI(Third Party System)).
Regards!
Achin -
Urgent: Creating ALE IDOC for SALES ORDER
hi
please tell me <b>step by step procedure to create ALE IDOC for SALES ORDER?</b>
reward for sure
regards
ravishHi,
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 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V 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
Regards -
Hello, I am trying to send contracts from SRM to R/3 backend system.
I know that I have to create a profile in WE20 transaction but where I have to put inbound parameters BLAORD and COND_A?
My SRM system is SEDCLNT110 and R/3 backend is ECDCLNT101. For which system I have to put these inbound parameters?
Thanks in advance
Rosa RodríguezRosa,
Put them as Inbound parameters for your SRM Logical System(SEDCLNT110 ) in ECC.
SG
Edited by: SRMUSER123 on May 5, 2010 9:41 AM -
Need of ALE settings to connect 4.7 to 5.0 to send IDOc
Hi
I have two servers 4.7 and 5.0 .
Now I want to send Idoc from 4.7 client 800 to 5.0 client 800.
Can anybody provide me the steps to create ALE settings and to send IDOC.
creating logical systems in source and destination and creating RFC and partner profile and port.
Thanks in AdvanceHi,
For ALE senerion for sending the material from one system there are three methods are there
1) Executable program only for Master Data
2) Message type Master As well as Transcation Data
2) Change Pointers Master As well as Transcation Data
1) SCC4 Create the Logical systems.
ALG800 for 800
ALG810 for 810
2) Assign the Logical systems to the Client using SCC4> selecting the Client and Double click> maintain the logical system name which you had created in the step 1
3) Main RFC destination SM59---> use the same Logical system name as the Logical system name
log on to 800 and goto SM59 --> create
ALG810 --> provide the 810 logon details and save
test with remote logon...it will open the client 810..
logon to client 810 goto--> sm59 --> create
ALG800 --> provide the 800 logon details and save
test with remote logon...it will open the client 800..
logon to 800 goto BD64 maintain CDM-->change
create CDM
ZCDM01 CDM
ALG800 sender
ALG810 Reciever
MATMAS Message type
ZCDM01 CDM
ALG810 sender
ALG800 Reciever
MATMAS Message type
save
Environment ---> Generate partner porfile.
edit --> distribute CDM
Logon to 810
goto BD64---> select CDM ZCDM01 ---> Environment ---> Generate Pratner Profile.
Edit --> distribute.
ALE Setting are compleated.
Logon to sender system 800.
create material in MM01
Material 10001
Industry sector mechanical engee
Material Type finished
enter
Base Unit of Measure KG
Weight unit KG
Gross Weight 100
Net Weight 100
save
Execute BD10 in client 800
Check the Idoc in WE05.
Log on to Client 810
Execute BD11
check the IDOC status in WE05
goto MM03 provide the material numer enter...
Thansk,
Nelson -
Hi, I am new for ALE/IDOC.
I am trying to create ALE/IDOC between two r/3.
Can you please tell me in detail how to set up RFC connection between these two systems?
Should I have to login in to clint 100 first and set up the rfc destination and then login to clnt 200 and set rfc destination again?
I am not clear how to do it. Please help me with the steps.
Ramyahi,
RFC connection mainly needs between two different server's example: r/3 to bw or non-sap to bw, if u r working in the same client that's dont need. if u wan to create
rfc connection go for SALE T-CODE.
regards
harikrishna.N -
Step by Step procedure for ALE
Dear Friends,
Can anyone please post the step by step procedure of creating ALE with an example.
Regards
SNHi,
Follow the below steps outbound side for IDoc transfer.
1. Create logical system (t-code BD54)
2. Assign client to logical system (t-code SCC4)
3. Create Ports (t-code WE21)
4. Create Partner Profile (t-code WE20)
5. Create Distribution model (t-code BD64)
At the inbound side,
1. Create logical system (t-code BD54)
2. Assign client to logical system (t-code SCC4)
3. Create Partner Profile (t-code WE20)
4. At the outbound side, once you create the distribution model, select the model, and from the menu bar, select, Edit->Model view->distribute.... this will create the model view at the receiver.
Now use the respective transactions to send the respective customer or vendor or....of ur need.
~ Bineah -
ALE problem when delete GL Account
Dear Expert,
I have create ALE with 2 client in my system. When I try to create GL account in sender system, that GL account also created in receiver system.
When I tried to delete it from sender system, that GL account still exist in receiver system but have flag "mark for deletion".
I use message type GLMAST.
Regards,
MALHi MAL,
AELE does not move the deletion. You need to delete the GL Accounts manually in all the received systems. One thing you can do before deletion is to block the the account for posting, ALE it and then delete.
Regards.
Ruchit. -
Hi All,
I need steps for ,how to create ALE,
I have one work on that,please.
Can u send steps with screen shots please.
Regards,
Kalidas.Thi
good
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Look at 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
Just follow the procedure
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 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 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
-System Name : ERP000
-Description : Sending System
-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
STEP 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
STEP 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)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
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
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
thanks
mrutyun^ -
Urgent: Application Object Type for ALE IDoc
Hi All,
I am struggling with ALE IDoc, I just wanted to know that is it mandatory to create Application Object Type when i have created my own message type, Idoc type, segment type and Function Module. I am Getting an error while excuting transaction we42( Maintaining Process code)
Error: Application Object Type is not planned.
Please Help with this. i don't have any requirement of filtering or serialisation, so still do i need to create these application objects.
Useful ans will be rewarded.
ThanxHi,
Yes u need to have the assignment of Object type as ur extending the IDOC.
Check the steps below:
TCode- BD95.
Create ALE object type Z... with table name EKKO and Field name -BSART
Step2:
Tcode- BD59 Assignment of Object type to Message
Give the message type ORDERS.
Assign the object type Z........ to segment type E1EDK01 with field BSART.
Regards
Kannaiah -
What is the process of ale creation?
Hi,
Here I have created ALE but when i am creating model view and after execute it then it showing me no message has been defined for the model even after added messages in model view, this message i am getting in /nbd82.
well any body give details of ale means idoc creation, inbound process, outbound process and ale cofiguring.
From
Mohammed Moid AhmedHi
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
ALE
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Reward points if useful
Regards
Anji -
Transport ALE Configuration from Development to Production System
Hello All,
We have created ALE-IDOC scenario in the development system and its working fine. Now we want to transport it to the Production / Quality system. How can we transport the settings like logical systems, port definition, partner profiles, distribution model , RFC destinations from one system to another system??
Because the client numbers are different for development , quality and production systems.. Do we need to transport the logical system and client assignment using STMS or create directly in the target system??
Thanx in advance...The issue with transporting the ALE distribution model is that the source and target logical system names change between the dev, test and prod environments.
Assume an ECC6 and PI landscape with dev/test/prod called E6D/E6T/E6P and PID/PIT/PIP with all systems using client 100. By default (SAP recommendation) the logical system name for E6D client 100 is E6DCLNT100 and its PI partner in the dev landscape will be PID client 100 with logical system name PIDCLNT100. In test the logical system names will be E6TCLNT100 and PITCLNT100 and in prod E6PCLNT100/PIPCLNT100.
So, when a distribution model is set up in dev with a source system of E6DCLNT100 sending messages to a target system PIDCLNT100 everything works nicely. This assumes that the PIDCLNT100 logical system partner in WE20/WE21 is mapped to a port which maps to an RFC destination pointing to client 100 of PID.
When this model is transported to the test system it won't work because the logical system names are wrong.
It is possible to create a logical system name called PISERVER in SALE and then map that, via WE20/WE21 to point to the corresponding PI instance. Thus in E6D, WE21 would map logical system PISERVER to the RFC destination for PIDCLNT100 but in E6T the mapping would link to RFC destination PITCLNT100 and in E6P to PIPCLNT100. In this way any ABAP programming trying to use the ALE distribution model would send messages to PISERVER and would be transportable.
However, setting up the source system in the same way appears to be impossible. When attempting to generate partner profiles, transaction BD82 stubbornly insists that the source system for which it will build profiles MUST be the logical system name defined for the execution client in SCC4. Theoretically, mapping similar to that for PISERVER could be performed for ECC6SERVER and the ALE distribution model could be built to send messages from ECC6SERVER to PISERVER but BD82 won't honour this source system.
This appears to make it impossible to transport an ALE Distribution Model. Can anybody provide a process to overcome this apparent architectural limitation? -
Hi gurus,
While creating ALE partner profiles from R/3 , I am getting the following error.
Port could not be created
RFC destination SRMCLNT100 not specified for system SRMCLNT100
Enter the RFC destination and restart the generation
I have created the RFC destination from R/3 as wellas from SRMclinet 100 and could be able to remote logon to the respective systems. I am able to create partner profiles from SRMclient 100 but I could not do it from R/3.
Pl give your advice.
SSHello,
We defining ALE Distribution models, we add message types between 2 logical systems.
When generating the partner profile from this view, the system tries to use an RFC destination with exactly the same name as the logical system.
In your case, it does not find the RFC destination SRMCLNT100 in R/3.
A workaround is to maintain the partner profiles manually :
WE20 to maintain partner profile
WE21 to maintain ports
Rgds
Christophe -
Ale/idoc configuration Guide
Hi,
Hi i am trying to create ale/idoc scenario between my two clients. Can any one tell me steps by steps configuration of that.
Regards,
Gurprit BhatiaHi,
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
with regards,
sowjanya.gosala.
Maybe you are looking for
-
Posting lines Val gr code AGC val class A/ C dt A/C Cr Gain/loss from revaluation 1000 e 3030 4032020 4032020 Inventory posting 1000
-
I changed my Apple ID now I cant access icloud emails. What do I do?
I have changed my Apple ID. Now I cant access my emails. Any suggestions?
-
Hi there , Can any one please tell me that how do we work with BC sets & how can we use that to migrate the data from one system to other system.... Regards Kaushik
-
Help using dynamic XML with Tree Menu
Can some one please help me? I don't know what I'm doing wrong. I'd simply like to be able to load an XML file of data and use this data to populate a Flex tree component. The XML file needs to reside on the server and will change from time to time,
-
Just a quick question. I have some test results. From a cluster I am creating a CSV file... But how do I make it to get the results in excel sheet, shaped as shown in the attached excel sheet. Please note that those are different tests (test1 to tes