Help required in ALE configuration
Hello All,
I am working on SAP Demo version. I have created a logical system and saved it.
After defining logical system i tried to create a distribution model but i don't see any logical system in the distribution model? Can anyone help me in this issue.
Regards,
Lisa
<<Posting list of links is not permitted. Please do not do it again. Further violations can result in points being deducted, or your account being deleted>>
Hi,
Refer below links.
Re: tell me about ale configuration
reg:ALE Configuration
Re: ALE and Idocs configuration
Re: ALE Configuration
Regards
Md.MahaboobKhan
Edited by: Matt on Jan 19, 2009 7:38 PM
Similar Messages
-
Help required for MSS configurations on Portal
Hi Experts,
Can someone please send me Portal Configuration guide or some kind of document on how to configure MSS --> Overview and Organisation services. Do I need to pass any parameters or any other configurations required?
Please help me.
Earlier responses would be much appreciated.
Thanks
UdayHi uday,
Please find the below links
MSS Configuration within SAP Portal: Organization Structure
ESS/MSS configuration in Portal as a part of HCM
http://help.sap.com/erp2005_ehp_04/helpdata/EN/14/1a6493d09849448a0537ee6727e799/frameset.htm
Hope it helps...
Thanks,
Rahul. -
Urgent help required for network configuration
sir
i have a mixed scenario right now.
I have only three computer on home network.
1.vista accer travelmate 4720 laptop loaded with vista sp1 ultimate
2.normal pc : Core2 duo with XFX ATI REDION graphics card and this pc is loaded with OEL 5.3.x linux but this pc has 2 NICs(eth 0,eth 1) I have connected both with a switch and the switch is connected to a modem for internet.can I use one NIC as private and another NIC as public to access internet?
3. normal pc : P4 HT and its loaded with win xp sp2 having eth 0
how to set my network.
I have connected each NIC with a D-Link switch.And the D-Link switch is connected with DataOne Nokia Siemens network c2110 modem.
But problems are that
1) each time i can connect only one PC at a time.
2)OEL 5.3.x is not connected to the specified modem ever....by [adsl seup|http://forums.oracle.com/forums/thread.jspa?threadID=832112&tstart=0] command.should i configure it during installation?is there any easy shell scriot avilable to do this stuff?
please help as soon as you can.......
regards
Edited by: mango_boy on Sep 7, 2009 4:44 AMifconfig output:
eth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:243 (243.0 b) TX bytes:9406 (9.1 KiB)
Interrupt:16 Base address:0xec00
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:3779 errors:0 dropped:0 overruns:0 frame:0
TX packets:3779 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6124500 (5.8 MiB) TX bytes:6124500 (5.8 MiB)
virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:8360 (8.1 KiB)
xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)adsl-setup output
[root@localhost ~]# adsl-setup
Welcome to the ADSL client setup. First, I will run some checks on
your system to make sure the PPPoE client is installed properly...
LOGIN NAME
Enter your Login Name (default root): kris_9929
INTERFACE
Enter the Ethernet interface connected to the ADSL modem
For Solaris, this is likely to be something like /dev/hme0.
For Linux, it will be ethX, where 'X' is a number.
(default eth0): eth1
Do you want the link to come up on demand, or stay up continuously?
If you want it to come up on demand, enter the idle time in seconds
after which the link should be dropped. If you want the link to
stay up permanently, enter 'no' (two letters, lower-case.)
NOTE: Demand-activated links do not interact well with dynamic IP
addresses. You may have some problems with demand-activated links.
Enter the demand value (default no):
DNS
Please enter the IP address of your ISP's primary DNS server.
If your ISP claims that 'the server will provide dynamic DNS addresses',
enter 'server' (all lower-case) here.
If you just press enter, I will assume you know what you are
doing and not modify your DNS setup.
Enter the DNS information here: server
PASSWORD
Please enter your Password:
Please re-enter your Password:
USERCTRL
Please enter 'yes' (three letters, lower-case.) if you want to allow
normal user to start or stop DSL connection (default yes): yes
FIREWALLING
Please choose the firewall rules to use. Note that these rules are
very basic. You are strongly encouraged to use a more sophisticated
firewall setup; however, these will provide basic security. If you
are running any servers on your machine, you must choose 'NONE' and
set up firewalling yourself. Otherwise, the firewall rules will deny
access to all standard servers like Web, e-mail, ftp, etc. If you
are using SSH, the rules will block outgoing SSH connections which
allocate a privileged source port.
The firewall choices are:
0 - NONE: This script will not set any firewall rules. You are responsible
for ensuring the security of your machine. You are STRONGLY
recommended to use some kind of firewall rules.
1 - STANDALONE: Appropriate for a basic stand-alone web-surfing workstation
2 - MASQUERADE: Appropriate for a machine acting as an Internet gateway
for a LAN
Choose a type of firewall (0-2): 1
Start this connection at boot time
Do you want to start this connection at boot time?
Please enter no or yes (default no):no
** Summary of what you entered **
Ethernet Interface: eth1
User name: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Activate-on-demand: No
DNS addresses: Supplied by ISP's server
Firewalling: STANDALONE
User Control: yes
Accept these settings and adjust configuration files (y/n)? y
Adjusting /etc/sysconfig/network-scripts/ifcfg-ppp0
Adjusting /etc/ppp/chap-secrets and /etc/ppp/pap-secrets
(But first backing it up to /etc/ppp/chap-secrets.bak)
(But first backing it up to /etc/ppp/pap-secrets.bak)
Congratulations, it should be all set up!
Type '/sbin/ifup ppp0' to bring up your xDSL link and '/sbin/ifdown ppp0'
to bring it down.
Type '/sbin/adsl-status /etc/sysconfig/network-scripts/ifcfg-ppp0'
to see the link status.Edited by: mango_boy on Sep 7, 2009 9:02 AM
added adsl setup output
Edited by: mango_boy on Sep 7, 2009 9:15 AM -
Help required on ALE/IDocs
Hi,
I am facing an issues related to IDocs, where in an Idoc is being sent from the sender to receiver system.
However, when I see the Idoc on the receiver system, I find that some fields in some of the segments are set to '/'.
The data that I can see in these fields in the sender system and are visible here and are set to '/'.
Could any one help out here and suggest where this could be happening?
(I checked the filtering and coversion rules and there's nothing happening there on these fields)
Regards,
Sudeep
Moderator message: please use more descriptive subject lines from now on.
Edited by: Thomas Zloch on Nov 8, 2010 12:39 PMHI,
Check the FM called during idoc sending, wether any one hardcoded the fields with "/" while sending to thirdparty system.
BR,
Lokeswari. -
ALE Configuration Conceptual Questions
Hi Experts,
I need some help regarding the ALE configurations.
1. I know that we specify the RFC dest in the port and then specify the port in partner profile. What exactly is the significance of a port in case of outbound Scenario? we could have directly specified the RFC destination in the partner profile.
2. When we create the TCP/IP RFC destination it creates a TRFC Connection. However in the special options tab we have the option select QRFC version? What is the use of that?
3. Why does the port created is of TRFC for ALE? Is it that the RFC connection is of TCP/IP so we need a TRFC port?
4. Why do we need to create TCP/IP rfc destination for ALE, why not HTTP RFC destination?
5. Is distribution model is mandatory for all the ALE scenarios? If not then when its mandatory?
6. While creating process code we have option process with/without ALE service. What does that exactly means?
Thanks
Kumar
Moderator message: please search for available information/documentation, do not ask interview-type questions.
Edited by: Thomas Zloch on Apr 19, 2011 7:01 PMhi,
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
Regards,
S.Nehru -
Help required in Weblogic 6 - Creation & Configuration of Web Application
Forum Home > Enterprise JavaBeans[tm]
Topic: Help required in Weblogic 6 - Creation & Configuration of Web Application
Duke Dollars
2 Duke Dollars assigned to this topic. Reward the best responses to your question
using the icons below, or transfer additional Duke Dollars to this topic.
Welcome moinshariff!
Watching this topic.
Previous Topic Next Topic
This topic has 1 reply on 1 page (Most recent message: Jan 23, 2002 1:05 AM)
Author: moinshariff Jan 22, 2002 4:55 AM
Hi,
I am using Weblogic 6. I have created a new Web
Application called Web (I have not used the DefaultWebApp_myserver).
And I have the following settings:
Name : Web
URI : Web
and Path : C:\Web
and placed my JSP files under c:\Web\
I am able to access the first page, but after that I am not able to access the
second page.
I get "Error 404--Not Found" on the browser. Basically the class file is not getting
created under /Web-inf/_tmp_war_myserver_myserver_Web/jsp_servlet/ folder .
I tried a work around for this. I copied all my files under one more folder called
web and placed this under C:\Web
The it works. Now I have 2 copied off all the files, 1 copy under c:\web and another
copy under c:\web\web\.
If I have the files under DefaultWebApp_myserver and have the setting as
Name: DefaultWebApp_myserver
URI: DefaultWebApp_myserver
Path: .\config\mydomain\applications
everything works fine.
Can any one please let me know if there is any configuration which has to be done
so that I do not duplicate the code in 2 directories
Thanks in advance.
Regards,
MoinForum Home > Enterprise JavaBeans[tm]
Topic: Help required in Weblogic 6 - Creation & Configuration of Web Application
Duke Dollars
2 Duke Dollars assigned to this topic. Reward the best responses to your question
using the icons below, or transfer additional Duke Dollars to this topic.
Welcome moinshariff!
Watching this topic.
Previous Topic Next Topic
This topic has 1 reply on 1 page (Most recent message: Jan 23, 2002 1:05 AM)
Author: moinshariff Jan 22, 2002 4:55 AM
Hi,
I am using Weblogic 6. I have created a new Web
Application called Web (I have not used the DefaultWebApp_myserver).
And I have the following settings:
Name : Web
URI : Web
and Path : C:\Web
and placed my JSP files under c:\Web\
I am able to access the first page, but after that I am not able to access the
second page.
I get "Error 404--Not Found" on the browser. Basically the class file is not getting
created under /Web-inf/_tmp_war_myserver_myserver_Web/jsp_servlet/ folder .
I tried a work around for this. I copied all my files under one more folder called
web and placed this under C:\Web
The it works. Now I have 2 copied off all the files, 1 copy under c:\web and another
copy under c:\web\web\.
If I have the files under DefaultWebApp_myserver and have the setting as
Name: DefaultWebApp_myserver
URI: DefaultWebApp_myserver
Path: .\config\mydomain\applications
everything works fine.
Can any one please let me know if there is any configuration which has to be done
so that I do not duplicate the code in 2 directories
Thanks in advance.
Regards,
Moin -
ALE configuration for Outbound Idoc - Help me
Hi Experts,
I am newbee in SAP and XI. I was trying to send MATMAS Idoc from R3 and i was running into some issues. So i would appreciate if someone can help me.
I am using following link as reference. /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I did all the steps mentioned in the above link ( Creating Logical Systems, Assigning Client and RFC destnations, Creating distribution models ..... etc)
and then everything went well and i saw success messags in all the steps.
I used BD10 to send material and it went well. But when i check TRFC queue, i see some error messages; "<i><b>No service for system SAPRDI, client 800 in Integrion Directory</b></i>"
And all the messages are hanging in the TRFC queue.
Note: I havent configured anything in XI yet. I wanted to make sure IDoc gets to XI client first.
Thank you in advance. Pls help me its very urgent.
Thanks,
SuryaI created RFC destination (SM59) and Port (IDX1)
Then i sent another material (BD10) and checked tRFC queue. i found bunch of error in the Queue.
<b>1.connection to host 10.4.23.120, service sapgw00 timed out / CPI-C error C
No service for system SAPRDI, client 800 in Integration Directory
partner not reached (host 10.16.176.29, service sapgw00) / CPI-C error CM
connection to host 10.16.136.127, service sapgw58 timed out / CPI-C error</b>
Note: i have noticed entries for R3 in SLD as below
System Name: <b>RDI </b> ( not <b>SAPRDI</b> as mentioned in the error message)
System Home: r3ides
That might be reason. If so, how to change it in R3 box? Any suggestions?
Please send me if you guys have any links or docs to address this issue.
Thanks,
Surya -
Hi all,
I am doing <b>file to IDOC scenario</b>. can anyone tell me
what ALE Configuration is required to do in SAP R/3 and
and XI.
By which manner I hv to create ports and rfc
detaination and how to point them? and how to point them?
And Which RFC Destination and Port to be mentioned in
the Idoc receiver adaptor? (Whether it is created in SAP
or in XI?)
thx and regards,
Mukharji.
[email protected]Hi Mukharji..
these steps might be usefull in Configuration.
SAP XI
1) <b>RFC Destination (SM59)</b>
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.
2) <b> Create Port (IDX1)</b>
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 SAP R/3 towards other system.
e) Save
3) <b> Load Meta Data for IDOC (IDX2)</b>
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
<b>SAP R/3</b>
1) <b>RFC Destination (SM59)</b>
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.
<b>2) Create Port (We21)</b>
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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
<b>3) Create Partner Profile (WE20)</b>
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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
<b>In SLD System Landscape Directory</b>
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
<b>In Transaction SALE</b>
Define and Assign the logical system name.
cheers,
raghavesh -
Help required network configuration - Gateway route settings get erased on reboot.
Oracle Linux 7
Linux myhostname 3.8.13-35.3.1.el7uek.x86_64 #2 SMP Wed Jun 25 15:27:43 PDT 2014 x86_64 x86_64 x86_64 GNU/Linux
#cat /etc/sysconfig/network-scripts/ifcfg-eno16780032
TYPE="Ethernet"
BOOTPROTO="none"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_FAILURE_FATAL="no"
NAME="eno16780032"
UUID="2d1107e3-8bd9-49b1-b726-701c56dc368b"
ONBOOT="yes"
IPADDR0="34.36.140.86"
PREFIX0="22"
GATEWAY0="34.36.143.254"
DNS1="34.36.132.1"
DNS2="34.34.132.1"
DOMAIN="corp.halliburton.com"
HWADDR="00:50:56:AC:3F:F9"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
NM_CONTROLLED="no"
#route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 34.36.143.254 0.0.0.0 UG 0 0 0 eno16780032
34.36.140.0 0.0.0.0 255.255.252.0 U 0 0 0 eno16780032
169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eno16780032
When I reboot the machine, the first line in route table gets erased, I then run:
#route add default gw 34.36.143.254
After which network works fine.
Help required. I don't want to use NetworkManager.The following might be useful:
https://access.redhat.com/solutions/783533
"When transitioning from NetworkManager to using the network initscript, the default gateway parameter in the interface's ifcfg file will be depicted as 'GATEWAY0'. In order for the ifcfg file to be compatible with the network initscript, this parameter must be renamed to 'GATEWAY'. This limitation will be addressed in an upcoming release of RHEL7."
NetworkManager is now the default mechanism for RHEL 7. Personally I don't quite understand this, because as far as I can gather it is a program for systems to automatically detect and connect to known networks. I think such functionality can be useful when switching between wireless and wired networks, but for a server platform, I wonder. -
ALE CONFIGURATION WHAT ARE CHANGES REQUIRED WHILE MIGRATING TO UNIX
HELLO GUYS,
PLEASE LET ME KNOW WHAT ARE THE CHANGES REQURIED IN ALE CONFIGURATION WHILE WE ARE MIGRATING FROM WINDOW NT TO UNIX?
REGARDS
RAJESHHi Rajesh,
Could you briefly explain me the scenario in which you want to transfer the data ?
Upto my understanding:
If you want to transfer the data from SAP to legacy system, through ALE u need to have translation programs, u can use BAPI's for this.
Regards,
Kannaiah Kavuri -
Can anybody help out in ALE?
Hi friends,
Can anybody help me out by giving the navigation steps of configuring the ALE.......Please urgent
Useful Answers will be definetly rewarded points.hi,
1. INTRODUCTION TO ALE DEVELOPMENT
To develop a new custom ALE scenario, comprises 5 steps:
1. Design and develop the custom IDoc with its segments and a new message type
2. Configure the ALE environment with the new IDoc and message type (customer model, partner profiles and linking IDoc to message type)
3. Develop the outbound process which does the following:
Populates the custom IDoc with control info and functional data
Sends the IDoc to the ALE layer for distribution
Updates status and handles errors
4. Configure the ALE inbound side (partner profiles with inbound process code)
5. Develop the inbound process which does the following:
Reads the IDoc into a BDC table; selects other data that is required
Runs transaction using call transaction or BDC session
Updates status and handles errors
2.1. Create IDoc type (WE30) Client independent
The IDoc type refers to the IDoc structure that you will require for your development
To create the IDoc type, follow these next few steps:
Enter transaction WE30 (ALE -> Extensions -> IDoc types -> Maintain IDoc type)
Type in ZINVRV01 and click on Basic IDoc type, click the Create icon
Click on Create new (we are creating an IDoc from scratch but you may want to copy another IDoc if it is similar to your requirements) and enter a description, and press enter
Click on ZINVRV01 and then on the Create icon
Enter Z1INVRV as the segment type (must start with Z1), check mandatory if the segment must exist (in this case check it), enter 1 in minimum number and 1 as maximum number. (Make the maximum number 9999999999 if there are going to be many of these segments in each IDoc. IE. When line items are passed via IDocs), click on Segment editor
Enter a description for your segment type and create
Enter a description for your segment, enter each field required in your IDoc, in our case type LIFNR across for Field name, DE structure and DE documentation, repeat for XBLNR and press enter to validate.
Save and generate, press back
To release the segment choose Goto, Release from the menu
Check the box on the line of your new segment
Save, back and enter
Your IDoc type structure should be displayed with your new segment
Save and back
To release the IDoc type choose Extras, Release type from the menu and Yes
Your IDoc is now ready for use. If you need to add fields or segments to your IDoc type, you will need to cancel the release of the IDoc type as well as the segment release using a similar
procedure followed above (except now you uncheck the release box for the segment and you choose cancel release for the IDoc type).
2.2. Create message type (WE81) Client independent
To create a new message type, follow these next few steps:
Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
Choose Create logical message type by double clicking on it
Click on change icon to enter change mode
Click on New entries to add a new type
Enter the required message type, in our case it is ZINVRV and an appropriate description
Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) Client independent
To link the message type to the IDoc type follow these next few steps:
Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
Click on change icon to enter change mode
Click on New entries to create the link
Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
Type in your message type ZINVRV and press enter
Click on New entries
Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
Save and exit.
You have now created an object that well use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) Client dependent
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
Choose the receiving systems to which the sending system must forward message type ZINVRV to.
For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
Save the entries.
NOTES:
You cannot maintain a message type between the same sender and receiver in more than one customer distribution model.
Only the owner is authorised to modify the model.
To change the owner of a model, choose the 'Maintain ownership of customer distribution model' function. Make sure that all changes will be distributed to all systems that know the corresponding model. To do so, you can use the correction and transport system.
To transport the customer distribution model you should use the Distribute customer model function of the IMG as described below.
2.3.2. Distribute customer model (BD71) Client dependent
After the customer model has been created centrally, it must be distributed to the other remote systems. This entails first of all setting up the communication for the distributed systems and then sending the model.
2.3.2.1. Distribute Model (BD71) Client dependent
This task is performed on your ALE reference client. To distribute the customer distribution model, read the ALE configuration procedure and follow these steps:
Make the settings for the communication with the other decentral systems, you have not set them yet.
Define the RFC destination for R/3 connections whose names correspond to the name of the corresponding logical system.
Create the output partner profile.
Distribute the customer model
Specify the name of the customer model.
You must specify the target system to which you want to distribute the customer model.
You must repeat this function for every distributed logical system.
2.3.2.2. Maintain sending system partner profile (WE20) Client dependent
With this function, you define the partner profiles for all outbound and inbound messages on the basis of the customer distribution model.
After you have defined and distributed the customer model, you will have to maintain the partner profiles locally. To do this read the ALE configuration procedure.
Enter the output mode (background, immediately) and the package size for outbound processing.
Requirements
The customer model must be maintained.
RFC destinations must be maintained.
The customer model must be distributed.
To ensure that the appropriate persons in charge are informed if a processing error occurs, you must make settings in: Error processing Maintain organisational units.
2.4. Populate & distribute IDoc using ABAP
An IDoc consists of a control record with structure edidc and one or more data records with structure edidd. The control record contains the sender and recipient of the IDoc, as well as information on the type of message.
To be able to pass an IDoc to the ALE layer, you must set up a field string with structure edidc and an internal table with structure edidd. They are used to call function module master_idoc_distribute, which performs the save to the database and triggers the dispatch if necessary.
Hope this helps, Do reward. -
hi experts,
i want detailed information on ALE configuration.if we have to transfer some data to other system what we have to do.how can we configure ALE for this.explaine from scratch how to define ALE.i mean from creation of idoc,creation of segments ,what are outbound components, and inbound components.what are the process coades.
urgent please.
thanks in advance.Hi Refer this link:
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
For ALE -- IDoc's
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
ALE/ IDOC/EDI
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
<b>Sending System(Outbound ALE Process)</b>Tcode SALE:
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
<b>Receiving System(Inbound ALE )</b>
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
<b>Sending System(Outbound ALE Process)</b>
Tcode SALE : 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
<b>Receiving System(Inbound ALE )</b>
Tcode SALE ?3 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 !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
Raja T -
ALE Configurations for IDOC2IDOC scenario
Hi Experts,
Can anyone list down wht r the ALE configurations are required for IDOC2IDOC scenario?
1. Sender SAP ---> XI
2. XI ---> Reciever SAP
Please provide me the TCodes with the details that are needed for the above scenario?
Your help is higly appreciated
Rgds
Faisal....
Edited by: Abdul Faisal on Jul 28, 2008 11:49 AMHey,
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 partner profile.
Give the outbound or inbound message type based on the direction.
In your Sender R3:- outbound
In your Receiver R3:- Inbound.
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.
<removed by moderator>
regards,
Milan
Edited by: Mike Pokraka on Jul 28, 2008 5:04 PM -
Hi All,
Currently i'm working on the following requirements. we are using TIBCO system as a middleware tool and it will ceate an IDOC which needs to be directed to R/3 system. As we have already imported the IDOC to the TIBCO system and then it will fetch the data from non-SAP system and creates the IDOC and sends it to R/3 system? I've done the following ALE configurations but got the error message as 56..."Partner profile is not define".
I've done the following ALE configurations at R/3 side.
1. Created a logical system and RFC destination for TIBCO.
2. created a TRFC port.
3. Create a Partner profile and linked the TRFC port.
4. posted an IDOC from WE19.
but when i checked the status of IDOC in WE02 its displaying an warning message with status code 56 "Partner profile is not define". and i think no need to do any ALE Configuration at sender side since the sender system is TIBCO.
pls correct me if i'm wrong. as one of my colleage suugested me to create FIle port instead of TRFC port?
regards
FaisalHI
SAP R/3
R/3 to XI
1) RFC Destination (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.
2) Create Port (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)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (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.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
XI to R/3
1) RFC Destination (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.
2) Create Port (IDX1) ( Create port to get IDOC Meta data from sender system)
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 SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Refer the below links for further assistance
4.create partner profile using idx2
ALE configuration for pushing idocs from SAP to XI
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
IDOC testing using WE19
/people/sameer.shadab/blog/2005/07/25/reposting-idocs-instead-of-recreating--for-testing-purpose-xi
File To IDOC - Part1 (SLD and Design):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC&
File To IDOC - Part2 (Configuration):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part2+(Configuration)&
File To IDOC - Part3 (Steps required in XI and R3):
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/11/fileToIDOC-Part3(StepsrequiredinXIandR3)
cheers -
ALE Configuration Again !!!
Hi All,
I am trying to do ale configuration for idoc to file scenario. I created two RFC connection one for XI system and one for R3 system. Then I created ports for both the RFC. After that I created two Logical system having same name as the two RFC above. But as per the instruction , i should assign client to above logical system. But problem is that the client number ie 030 is already defined to R3 system. My XI system have same client id, so when i am trying to assign client 030 to XI logical system, it is giving as client number is already present. I don;t understand the logic of assigning client to LS.
what should i do here?
Second thing: Can we create more than one logical name for the same system. I asked this because in the RFC list of R3 system, i already have RFC for R3 system , logical name is also present. So can i create another logical system for R3 system?
Ranjeet Singh.An excerpt from SAP documentation on Logical System Names.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: <System-ID>CLNT<Client>. Refer to url
http://help.sap.com/saphelp_nw04/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
SCC4 should already have been set. So I assume that you are creating your logical systems in the IMG to then assign in WE20 (Partner Profiles). As the XI SystemID will be different to your R3 SystemID, CLNT should not be an issue.
If not then please clearly define the issue to include where you want to create the logical system and which way your IDOC will travel. We currently send IDOCs from CRM to XI and vica versa
Maybe you are looking for
-
Why is t not letting me download free apps on my iPad when it's asking for my security number and when I type it in my details on my iCloud account it's saying its been declined and asking for another payment card ? Can some1 help me pls!!
-
How can I back up mail boxes to an external drive (not using Time Machine)?
I recently lost all of my mailboxes when switching from Mavericks back to Mountain Lion; I still have all of my emails, just without the mailboxes I'd created over the past 6 years to organize these emails. The files that control organization inform
-
Javax.ejb.Inject not found
I'm working with jdeveloper 10.1.3 in S.O. XP build a proyect template JSP,EJB3,TOPLINK import javax.ejb.Inject; Error: Inject not found Tanks
-
Key column in an internal table?
Hi all, Can somebody tell me, if it is possible to create an internal table with a key-column? I think it is, but I do not know how? So, How can I make it? Does this keys work exactly like DB table keys? Thanks, MPM
-
PL/SQL : HTP Rowtype
Hi i wish to pass a rowtype as an input parameter to a procedure that shall display data from the rowtype . Simple data types are accepted by the procedure and displayed , but i am not sure how to do the same with a rowtype . Thanks.