ALE settings in xi
1) what are the ALE settings i have to maintain in R/3 system and XI in Idoc 2 file scenario?(I know little bit RFC Destination, Port, Partner profile in R/3 system. is it required to maintain the port in XI also? )
2) what is use of Meta data ( IDX2 )? can we import it every time explicitly ?
3) what are the ALE settings i have to maintain in R/3 system and XI in File 2 Idoc scenario?
4) should i create ports in both R/3 and XI systems?( idoc 2 file / file 2 idoc)
Hey,
Steps for ALE settings:-
Steps for XI
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the R3 system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto IDX1.
Create a new port.
Give the port name.
Give the client number for the R3 system.
Select the created Rfc Destination.
Step 3)
Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Steps for R3.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the XI system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto WE21.
Create a port under transactional RFC.(R3->XI)
Designate the RFC destination created in prev step.
Step 3)
Goto SALE.
Basic settings->Logical Systems->Define logical system.
Create two logical systems(one for XI and the other for R3)
Basic settings->Logical Systems->Assign logical system.
Assign the R3 logical system to respective client.
Step 4)
Goto WE20.
Partner type LS.
Create two partner profile(one for XI the other for R3).
Give the outbound or inbound message type based on the direction.
Step 5)
Goto WE19
Give the basic type and execute.
fill in the required fields.
Goto IDOC->edit control records.
Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
Click outbound processing.
Step 6)
Go to SM58
if there are any messages then there is some error in execution.
Goto WE02.
Check the status of the IDOC.
Goto WE47.
TO decode the status code.
Step 7)
Not mandatory.
Goto BD64.
Click on Create model view.
Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
reward points if useful.
regards,
Milan
Similar Messages
-
Doubt regarding ALE SETTINGS in IDOC scenario.
Hi Friends,
I have some doubts regarding ALE settings for IDOC scenarios, can anyone please clarify my doubts.
For exmaple take IDOC to FILE scenario
The knowledge i got from SDN is --
One need to do at the R3 side is --- RFC DESTINATION (SM59) for the XI system.
--- TRFC PORT for sending IDOC to the XI system
--- CREATING LOGICAL SYSTEM
--- CREATING PARTNER PROFILE
at the XI side is --- RFC Destination ( For SAP sender system)
--- CREATING PORT for receiving IDOC from the SAP sending system(IDX1).
1. Do we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself or in XI system or in both systems we create these logical systems? Is this a mandatory step in doing ALE configurations?
In IDOC to IDOC scenario-------
2. Do we craete two RFC destinations in XI system? One RFC DESTINATION for the Sender R3 system and another RFC DESTINATION for the Receiver R3 System? and do we create RFC DESTINATION for the XI system in receiver R3 system? If not.....y we don't create like this........Please give me some clarity on this.............
3. If we use IDOC adapter ,since IDOC adapter resides on the ABAP STACK ,we don't need sender communication channel ,for the similar reason----
y we r creating receiver communication channel in the case of FILE to IDOC scenario?
4. Can any one please provide me the ALE settings for IDOC to FILE scenario,
FILE to IDOC scenario,
IDOC to IDOC scenario individually.
Thanks in advance.
Regards,
Ramana.hi,
1. Yes, we create two logical systems for both Sender ( R3 system ) and Receiver( XI system ) in R3 system itself and
it is a mandatory step in doing ALE configurations
2. We create 1 RFC destination each in R3 and XI.
R3 RFC destination points to Xi and
XI RFC destination points to R3
3 We need to create Communication Channel for Idoc receiver as the receiver channel is always required but sender may not be necessary
4. ALE settings for all IDOC scenarios are same as follows....
Steps for ALE settings:-
Steps for XI
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the R3 system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto IDX1.
Create a new port.
Give the port name.
Give the client number for the R3 system.
Select the created Rfc Destination.
Step 3)
Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Steps for R3.
Step 1)
Goto SM59.
Create new RFC destination of type 3(Abap connection).
Give a suitable name and description.
Give the Ip address of the XI system.
Give the system number.
Give the gateway host name and gateway service (3300 + system number).
Go to the logon security tab.
Give the lang, client, username and password.
Test connection and remote logon.
Step 2)
Goto WE21.
Create a port under transactional RFC.(R3->XI)
Designate the RFC destination created in prev step.
Step 3)
Goto SALE.
Basic settings->Logical Systems->Define logical system.
Create two logical systems(one for XI and the other for R3)
Basic settings->Logical Systems->Assign logical system.
Assign the R3 logical system to respective client.
Step 4)
Goto WE20.
Partner type LS.
Create two partner profile(one for XI the other for R3).
Give the outbound or inbound message type based on the direction.
Step 5)
Goto WE19
Give the basic type and execute.
fill in the required fields.
Goto IDOC->edit control records.
Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
Click outbound processing.
Step 6)
Go to SM58
if there are any messages then there is some error in execution.
Goto WE02.
Check the status of the IDOC.
Goto WE47.
TO decode the status code.
Step 7)
Not mandatory.
Goto BD64.
Click on Create model view.
Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful
Prashant -
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 ,
Its a Migration Project and we have to Transfer all the Inspection Plans from the Old System to a New System.
We are tryin to go by the Idocs Approcach.
But i donnt know the MASS SEND Prog. for the same eg. BD10(RBDSEMAT) for Material , also i am stuck in the ALE Settings too ...
In Outbound Side Distribution Model i have added the following BAPI :
Object name InspectionPlan
Method name Create
Object type BUS1191
Method CREATE
Description Create inspection plan
and in the Outbound Partner Profile :
Message Type INSPECTIONPLAN_CREATE
Basic type INSPECTIONPLAN_CREATE02
I am also not able to Find the Inbound Process Code for the message type INSPECTIONPLAN_CREATE.
Although i guess the Inbound Function Module is IDOC_INPUT_INSPECTIONPLAN_CREA .
Please help me with the issue.
regards
Vikas.Thanks... but i am still in need of a mass send program ... or can i send the inspection plans via change pointers ?
while creating the entries in BD52 (Change Document Items for Message Type) i am not sure what should be added for this message type (INSPECTIONPLAN_CREATE)? -
Idocs are not prosessing even after ALE settings in SAP XI and ECC
Hi Experts!,
<b>I have a system which has SAP ECC and SAP XI 3.0 installed with 2 instances on the same operating system. ( In MMC you can see ECC and XI under the same SAP console tree ).
I have made many times all possible ALE settings between ECC and XI and I was unable to deliver the IDOC [ Idoc scenario- unable to get the IDOC in the receiver side (R3)]
Could any one please let me know how to solve this issue.
Useful answers will be rewarded.
</b>
Thanks in advance!,
SunilHi Martens,
I appreciate your kind reply, error : Unable to convert ALE logical system.., this is the error message I am getting, while I do File to IDOC scenario. So what may be the wrong thing in this configuration, Have done ALE settings ( Log sys, assign log sys, partner profile, port and RFC connection from R3 to XI).
So could you please let me know the solution.
regards,
Sunil -
ALE settings in sapR3 system logical system
Hi People
IN IDoc to File scenario
How to create Logical system(ALE settings) in SAP R3 system, i know little bit idea about that, we have to 1st create LS name (for R3 sys & PI sys), after that we have to assign that name's how to assign that, PLS can u provide me to with screen shots (if possible) r any links
Regards
shekarHi,
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 -
ALE settings...
Hi Gurus,
I have few issues with the ALE settings in the SRM config.
1.What is the function of the Partner profile we create in EBP and R/3.
2. What is the function of the doc. types.
3. Do we define Ports also in ALE settings.
4. What is the function of the transaction type(BUS2121)
5.How we structure the info as we do in R/3.Is there any std IDOC type with header and item segment.
6. As i know in ALE/Idocs, info. travells through Ports.Where we can see the ports.Do we define ports.
Please give some light on the above.
Thanks in Adv.
IS1.What is the function of the Partner profile we create in EBP and R/3.
It is bridge between EBP and R/3 .You must distribute the partner profile to r/3 after you create in ebp Once you create a modelview .it must be deployed to back end to transfer your information to r/3 eg. good recipet anfd invoice.
2. What is the function of the doc. types.
Document type are represents the business object like PO, PR and reservation. In R/3 it is called document type and SRM it is called as a transaction type.
3. Do we define Ports also in ALE settings.
Ports will be created automatically when you genrate apartner profile or you can define ports also with help of technical consultant.
4. What is the function of the transaction type(BUS2121)
It represents Shopping card. Every business object has BUS id .
5.How we structure the info as we do in R/3.Is there any std IDOC type with header and item segment.
check it up in we02 for more info . on message BBPIV and MBGMCR
6. As i know in ALE/Idocs, info. travells through Ports.Where we can see the ports.Do we define ports.
You can define a port in we20 if you want.
BR
Muthu -
ALE Settings for IDOC Processing
Hi,
Can anybody tell me what all the ALE settings I have to look for any IDOC.
Thanks,
bsv.Hi,
Please check this link for ALE setup for inbound and outbound processes.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
Regards,
Ferry Lianto -
ALE Settings error: Outbound: LS to KU
Hi Guys,
Requirement: send idoc to customer 1000358 (KU) when user execute a report in R/3
when user execute report we have written the code for idoc generation using function module
MASTER_IDOC_DISTRIBUTE. the idoc number is geeting genarated successfully with sy-subrc 0
although its giving an error in WE02 that:
IDoc: 0000000003560240 Status 29: Error in ALE service
Could not determine recipients for message type ZNACPRLST
its not picking the recepient information of the customer from ALE settings.
I have added that recepient info forcefully in debug before function module MASTER_IDOC_DISTRIBUTE.
But again the idoc number is geeting genarated successfully although its giving
another error in we02 that:
IDoc: 0000000003560258 Status 37: IDoc added incorrectly
Entry in outbound table EDP13 not found. please check the partner profile.
Although i have checked tht the entry exist in above table in se11.
ALE Settings:OUTBOUND:
Sender: LS- SP5CLNT210
Receiver: KU - 1000358
idoc type: ZPRLST01
message type:ZNACPRLST
WE82 assign idoc type with message type.
Receiver port: SAPOUT (File type & Transfer idoc immediately, RFC destination also there)
Partner profile: partner no: 1000358
partner type: KU
outbound params: message type - ZNACPRLST
But nothing i did in message control for outbound process code becoz we are
generating the idoc in the report itself by coding.
Distribution model: i can not create any distribution model. Because recipient system is KU.
and therefore no logical system name of recepient. therefore system will
not allow to create distribution model unless we have a logical sys name
of recipient. And i think as the recipient sys is KU (not LS) therefore
no need of distribution model?
I dont have any configuration for inbound till now. And i believe that doesnt matter
for outbound trigger.
Please can anybody tell me what could be the error in ALE settings that sytem is showing?
Will appriciate any help....
Thanks,
Biswajit.Hi,
thanks for your reply.....
i did exactly in WE20 that i wrote before...
The file port for EDI system is also perfect otherwise it woudnt work for other standard idocs...right?
i m tried to retest the same in We19 as well....
but it is giving the same below error:
IDoc: 0000000003560240 Status 29: Error in ALE service
Could not determine recipients for message type ZNACPRLST
its not picking the recepient information of the customer from ALE settings.
If I added that recepient info forcefully in iwe19 and retest it again the idoc number is geeting genarated successfully although its giving another error in we02 that:
IDoc: 0000000003560258 Status 37: IDoc added incorrectly
Entry in outbound table EDP13 not found. please check the partner profile.
Although i have checked tht the entry exist in above table in se11.
Your comments pls...
Thanks,
Biswajit. -
Hi
Am able to send idoc successfully from ecc 6.0 but i can see them in target system dont know where am mistaking in Ale settings or where pls help me out its bit urgent requirment.
Regards
MeetaHi,
did u check what i suggested.....sender side it seems fine..but u hava also set settings in reciver side also..Please check the below things
1>WE20(Partner profile) in reciver side..
here u will specify the partner as sender partner,and in the inbound paramters u have to give the messagetype and process code...see if u have done these settings in inbound side....
Regards,
Nagaraj -
ALE Settings For File-IDOC Scenario
Hi All,
While Doing IDOC-File Scenario we have to do the Following Settings
In XI
1) Create RFC Destination towards R/3
2) Create Port
3) Load Meta data
In R/3
1) Create RFC Destination towards XI
2) Create Port
3) Create PF
Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
Clarify me these Confusions
Regards
BopannaHI,
for IDOC TO FILE
We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
i.e for FILE-IDOC
1) No need to Distribute the modal view
2) For partner profile Specify the INBOUND PARAMETERS
FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
PLZ REFER THE LINK BELOW.
PLZ REWARDS THE POINTS
VIKAS JAIN
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
Edited by: vikas jain on Jan 22, 2008 11:49 AM -
ALE settings error "Too many recipients found for message type" urgent
Hi all ,
please help me to solve this issue !!!!!!!!
i done with ale settings .
in the bd64 , orders message type is used in 2 different model view for 2 different systems
when i create po it is giving error in output "Too many recipients found for message type ORDERS in the ALE model"
how can i rectify this error.
ThanksHi,
Try to redefine your distribution model to have both receivers of your message type ORDERS in one "model view".
Regards,
Jakub -
Reg: ALE settings in SAP R3 system
Hai
I am Kiran. I want to know complete details about ALE settings.
Can any one send necessary documents regarding these settings.
Thanks
KiranEnter tcode WEDI and you will be able to see all the transaction codes that corresponds to ALE/Idocs.
Please follow the links,
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/whitepapers/ale.htm
http://www.sapgenie.com/ale/index.htm
http://www.sappoint.com/abap.html
http://www.sapbrain.com/TUTORIALS/TECHNICAL/ALE_tutorial.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEHR/CABFAALEHR_ALE_QS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/ECPCA/ECPCA_ALE_154.pdf
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
Check this link:
ALE
and this :
http://www.erpgenie.com/sap/ale/whitepaper.htm -
Hi People
In IDoc to File Scenario
I need some info about R3 sys configurations step by step i know what is the procsess
1st we have to create LS (Tcode : SALE)
2nd we have to create RFC destination (TC : sm59)
3rd we have to create PORT (TC : we21)
4th we have to create PP (TC : we20)
5th we have to create DISTRIBUTION MODEL (TC : bd64)
i know this steps But i want step by step in that what we have ti give in LS , RFCDS, PORT, PP, DM
and how it process internally, what details we have to give in all configurations in that above transactions
regards
shekarHi,
Follow below steps to create custom IDOC.
1.Create segments through transaction WE31.
2.Create IDoc Type through transaction WE30 by attaching created segments.
3.Message type through transaction WE81.
4.Link Idoc and message type in WE82 transaction.
Check the transaction WEDI for ALE settings
Check these links for more details on IDoc's:
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
Thanks
Swarup -
ALE settings for IDOC2FILE Scenario
Hi All,
I have the requirement to work on IDOC2FILE scenario. i am not able to do the ALE settings well in both R/3 side and XI side. Anybody have the full documentation with step-by-step analysis, please send me ASAP. Please help me in this regarding.
I am very thankful to you all in advance.
Regards,
Nag.Hi Nagarjuna kumar ,
The following websites give u step-by-step solution for ALE settings for IDOC2FILE Scenario:
A Step-by-Step Guide on IDoc-to-File Using Business Service in the XI Integration Directory
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Introduction to IDoc-XI-File scenario and complete walk through for starters.
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
IDOCs (Multiple Types) Collection in BPM
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
cheers!
gyanaraj
****Pls reward points if u find this helpful
Maybe you are looking for
-
I'm trying to restore my iPhone, but get an error message 'the iPhone cannot be restored, the device cannot be found. How can I resolve this?
-
Please let me know how to display alternate colors in ALV? how to display end of list and top of list in a seperate colour? Thanks
-
Office 365 & Microsoft Account directory merge
The Azure account is managed and run by a Microsoft Account user. The same user has a Office 365 subscription so it has an work/organization account as well. Because the Microsoft sign-in pages are confused and messed up if a user needs to use differ
-
Hi, I need to build a page that will do the following and I'm hoping for some guidance.. remote client open URL http://domain.com/getdata.cfm remote client check that the port is open then send xml string the page needs to process the xml string exam
-
Bridge failed to restart...
Hi all, I'm using OpenMQ (the version provide with glassfish 3.0.1 Here, the output of the version I run : ================================================================================ Open Message Queue 4.4 Oracle Version: 4.4 Update 2 (Build 5-a