Can we go with ALE configuration instead of receiver idoc adapter at target

Hi Experts,
Could you please provide me some idea when why don't we go with ALE configuration to exchange IDOC from PI to Target system instead of configuring receiver IDOC adapter at target side.

Hi Raj
Point 1:
When we send IDoc from SAP system to PI ,it used ALE connections nothing but using RFC destination and Port it establishes the connection IDoc will reach PI ABAP Stack.
Point 2:
When we send IDoc to ECC using PI IDoc adapter it uses the same mechanism(RFC destination/Port),but the only purpose of IDoc comm8unication channel is to call RFCDEstination and Port created in PI.
i.e: There is no difference in communication(Point 1 and Point 2) both uses TRFC calls.
Regards,
Raj

Similar Messages

Issue with ALE configuration for creating the idoc for Purchase orders

Hello,
I am trying to send the purchase order through message type configuration using ALE.
I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
I have done ALE distribution using BD64.
Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
In NAST table, the entry is there but on executing RSNAST00 nothing happens.
Please provide me the pointers to solve the given problem.
Regards,
Mayank

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

Problem with file content conversion in receiver file adapter

Hi All
I have a problem with file content conversion in receiver file adapter.
This is my recordset structure: Header_Record,1,Claim_Record,*,Check_Rec,1
These are the content conversion parameters:
Header_Record.fieldSeparator = ,
Header_Record.endSeparator = 'nl'
Claim_Record.fieldSeparator = ,
Claim_Record.endSeparator = 'nl'
Check_Rec.fieldSeparator = ,
Check_Rec.endSeparator = 'nl'
In SXMB_MONI, i can see that the data is correctly extracted from proxy, and correctly mapped to receiver message, and i see a checkered flag (success).
But, Adapter status is RED with the following error message:
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
In communication channel monitoring, i get the following error message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Channel has not been correctly initialized and cannot process messages
What is going wrong here? Can anyone please tell me?
Thanks
Chandra

Posted in Incorrect forum.
Posted again in Process Integration forum

Problem with an Receiver Idoc adapter

Hi.
We have just went from XI 3.0 to PI.7.10.
The Receiver idoc adapter is set up in the same way as it was in XI.
The problem is when two different interfaces runs at the same time I got data into the DC40-record which not belongs too this idoc but from an another interface/idoc.
The idocs are different messagetypes.
In this case the field MESCOD which belongs to one of the idocs also appered in the idoc where the field MESCOD not should be used.
Any idea whats wrong ?
/Per-Arne

Thanks.
Checked sxmb_moni as you said.
In the OutboundBinding-node I can see the right idocadapter is used
where 'Apply Control Record Values from Payload' is enabled.
<SAP:ChannelName>IDOC_INBOUND_U01_110</SAP:ChannelName>
In the IdocOutbound-node I can see the message code 'EXT' which should'nt be there.
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>001</SAP:MANDT>
<SAP:DOCREL>710</SAP:DOCREL>
<SAP:DOCNUM>0000000000033474</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>OILLDD01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>OILLDD</SAP:MESTYP>
<SAP:MESCOD>EXT</SAP:MESCOD>
Too be more specific about the interface.:
I got one file in from a file adapter and out of that file I produce two idocs into R3 whit
two different idocs-adapters.
I think you are right about that the configuration may be mixed up.
Any idea of what I can do?
It may be an PI 7.10 bug ?
Shall I delete all config objects and so set config up from scrach again ?
/Per-Arne

Configuration Of Receiver Idoc Adapter

Hi Experts,
for an interface,I need to desighn a receiver idoc adapter.Plese guide Me
regarding following matters:
1. how to configure receiver idoc adapter ?
2. how to get the control record for the receiving idoc?
3. what are the configuration we have to make?
4. receiving idoc's data i want to update in my SAP database,How to achieve that?(Any program I have to write?what i need to mention in there?)
Eagerly looking for valuable suggestions.
Regards,
Rasmiraj
Edited by: rasmiraj tripathy on Aug 29, 2011 1:32 PM

Hi RashmiRaj,
Configuration Scenario
1. Create the RFC Destination in SM59.
2.Create Port in IDX1.
3.Create Logical System in BD54
4.Create A Scenario
5. Select a Business System in Service with out Party
6.Create a Receiver Communication Channel.
7. Create a new Business Service
8. Create a new Communication Channel
9. Mention the logical Name in the Service->Adapter Specific Parameters of both the File Sender Service as well as the business system.
10. create sender agreement
11. Create Receiver Determination
12. Create Interface Determination
13. Create Receiver Agreement
Also check the link [File to IDOC|http://www.****************/Tutorials/XI/FileToIDoc/FiletoIDocScenario.htm]
and http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660?quicklink=index&overridelayout=true
Thanks and Regards,
Naveen
Edited by: chichilin on Aug 29, 2011 5:40 PM

ALE Configurations in File to IDOC Scenario

Hi All,
We are doing File to IDOC Scenario.
ALE Configurations done:
R/3 Side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to XI.
2. Created port in R/3(using automatically generated port name) and assigned the RFC dest created above.
3. Created partner profile and assigned the ports to the message types.
4. Created Logical system
XI side:
1. Created RFC dest, pointing to XI and tested the connection for remote login to r/3.
2. Created port using IDX1 transaction with port name starting with SAP<SID> and assigned the RFC dest created above. (SID of XI)
3. Unable to load metadata in XI.
Now we are unable to test the scenario as it provides an error message in MONI as "Error: Transaction IDX1: Port SAP<SID>, client , RFC destination contain errors".
Also Let me know whether the steps mentioned above are correct for the scenario.
Regards,
Nithiyanandam

Hello,
SAP 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 (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 SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP 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 #####+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.
In SLD System Landscape Directory
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.
With Regards,
Vidya.
*******Reward with Points if found useful

Configurations for Receiver IDoc adapter??

Hi,
I have a File-to-Idoc scenario. In the Reciever Idoc adapter configuraiton, we have to provide: 1) RFC destination and 2)Port. Where do we define the RFC destination and Port? Do we have to do any any configuration in R/3 in we20 and we21?
Any help is greatly appreciated.
Thanks,
Karma

1) RFC destination and 2)Port. Where do we define the RFC destination and Port?
>>These are defined on XI server in IDX1 tcode.
>>Port is SAP<XXX>, <XXX> = SID of R/3 receiver system
>>RFC destination is the one u mention in this port definition.
>>First define the RFC destination in SM59 of XI Server.
>>U need not do anything in IDX2.
Do we have to do any any configuration in R/3 in we20 and we21?
Yes.
In WE20 of R/3, u have define the partner profile for XI server with the IDoc as inbound parameter.
In WE21 port for connecting to XI server. Here also u have to mention the RFC destination, which has to be defined in SM59.
Good luck.
-Naveen.

Client issue with ALE Configurations

Hi Experts,
I am trying to connect to a different SAP System through ALE. I have defined logical systems. When i am trying to assign destination logical system to destination client, i am getting an error - "Entry already exists" as there is another system aready assigned with this same client number.
My Question is - Is there any way to connect to 2 Diff SAP systems having same client number? Otherwise, if there is a client (Say 400) that is already assigned to an SAP System, Then cannt we connect to another SAP system having the same client number( 400)?
Rgds,
SURYA.

No, SCC4 is only for defining the clients of current system (and the corresponding logical system, which must be unique throughout the landscape), it's not about communication at all (apart the logical system).
Use SM59 to define an RFC destination, you'll define the target host and client .
Use WE21 to create an RFC port, referring to the RFC destination above.
Use WE20 to assign this RFC port to the logical system.
By "distribute model", I don't know if you're talking about the "distribution model", in that case I recommend you to go though this thread where there are general information : Distribution model for Message control ?
Sandra

ALE Configuration to Download the IDOC to a FTP Location

Hello SDN,
I need to generate the IDOCs and save them in text format onto an FTP Location specified by the client.
I understand, I need to setup the an TCP/IP RFC Destination and Create a FIle Port Specifying the FTP directory path.
Please suggest the necessary setup/configuration for the same along with checkpoints.
Thanks,
Manu
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on Apr 7, 2011 9:49 AM

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

Dyanamic Configuration at receiver file adapter determine target directory

Hi Experts,
I have a requirement to determine the target directory during runtime.
From the source side one particular field determine the Target directory where you need to place file
ECC - PI - File adapter - this is the scenario
In target side 3 directories in the same server . but the directory should determine from source fields - werks
As I am new to PI Please describe the procedure in detail.
Thanks in advance.
Kevin

Hi Kevin,
Use the below UDF and map to the rootnode in the message mapping.
public String GetFileName(Container container){
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String ourSourceFileName = conf.get(key);
return ourSourceFileName;
In the Advanced tab of the File adapter, check the option Adapter Specific Message Attributes. Under that, check the Filename option.
This would get the fieldname in the target filename.
Check the below link:
/people/madanmohan.agrawal/blog/2009/05/20/combining-three-different-aspects-of-pi-asma-af-module-and-variable-substitution-in-one-shot
http://help.sap.com/saphelp_nw04/helpdata/en/43/0a7d1be4e622f3e10000000a1553f7/frameset.htm
/people/shabarish.vijayakumar/blog/2007/07/26/troubleshooting-the-file-adapter-last-updated-on-02-july10
Thanks,

Single Transaction code for ALE Configuration

Hi All,
I want to Know is there any Single Transaction code for the ALE Configuration instead of going through SALE, WEDI t-code or with defining logical systems assigning them to clients, creating RFC and Distribution Model, generate partner function and..so on.
Please let me know if there is any t-code through which i can do the ALE configuration in a single T-code.
Thanking you in advance,
Bhanu

hi ars
i got a task saying that message type is DESADV01 ,but u told that DESADV01
is basic type,can i know the difference.
regards
sagar

ALE Configuration HCM - Program read table idoc_structure error

Hello SCN community,
I have small problem with ALE Configuration of HRMD_A message type. I created extension named 'ZRMD_A06'.
When I'm trying to run t-code: bd21 (report RBDMIDOC)
I'm getting following error message:
At the beginning I thought there is problem with segment structure of Z1P2006 of extension 'ZRMD_A06'
I compared segment Z1P2006 with structure 'P2006' in se11 - and it is the same.
Next I checked the bd21 transaction in debug mode.
I figured out that there is error in FM 'RH_MASTER_IDOC_DISTRIBUTE_HRMD' in include 'LRHALF10'.
Could you please help me?

Hello,
Thank you all for your help.
I'm writing this post to provide solution for others like me.
To solve this problem you need to apply this sap note:
HR-CA-ALE: Segment Z1Pnnnn prevents distribution
for me:
As of Release 4.6: In the customer enhancement RHALE001, fill the function exit EXIT_SAPLRHA0_004 with the line
F_idoc_control-cimtyp = 'ZRMD_AXX'.
steps:
1. Go to SE37
2. Enter EXIT_SAPLRHA0_004
3. Double click on INCLUDE ZXHALU08 . (in my case)
4. Add to the code this line: F_idoc_control-cimtyp = 'ZRMD_A06'. (ZRMD_A06 - because I called so my custom extension)
5. and have a nice day because you solved this problem!

Can't Sync with MobileMe and I get this error.

Help me, I can't sync with MobileMe cuz I keep receiving this message. I can't understand what it means.

Well, that didn't work. I did reset--wanted to replace everything on my computer from the cloud, but I still got the same message..sigh..

Ale configurations for IDoc?

hi..
What are the ALE configurations need for an IDOC?
bye.

Hi,
Perform the following ALE configurations
SAP 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 (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 SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP 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 (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.
Also gothru this Blog <a href="/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi Configuration for Pushing IDOC's from SAP to XI</a> by Swaroopa Vishwanath
Regards
Santhosh
<a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
Use a Good Subject Line, One Question Per Posting - Award Points

Idoc Adapter Configuration Issues

Dear Collegues,
I have given up almost all hope on configuring my Idoc adapter as I have an error message that I am not sure of how to fix; I have read just about everything I can get my hands on....any help would be so much appreciated:
Scenario: Demonstrate a simple 'proof of concept' to send MATMAS from R3 ->XI -> R3
Sending system: [R3 4.6b] CL0510
Rec'g system: [R3 4.6b] EL0510
XI system 3.0: NXL220
Current error message in outbound RFC layer of CLO:
No service for system SAPCL0, client 510 in Integration Directory
Per the documentation I have done the following:
- RFC connections are all complete
- Port and Partner Profiles complete
- ALE model from sender for MATMAS
- IDX1 in nxl for ports
- IDX2 - matmas metadata
- Integration Builder [config]:
 *Technical and Biz systems set up
 *CL0510 is set up as 'services w/o party' and there is
 a generated idoc channel.
 *The Adapter Specific Identifier is the CL0510 log
 syst.
 *Receiver Determination is created w/
 idoc_inbound_asychronous as interface; not sure
 what "namespace" is so I threw the word Idoc in there
 *Interface Determination is created w/ above
 parameters except the receiver party and service have
 asterisks in them I can't seem to remove
 *Sender and Rec'r Agreements set up [again what goes
 in that namespace field?]
I think that identifies all of the configuration I have attempted to enter. I have been only able to read documentation and weblogs as XI training won't be happening for me and my collegues until another several weeks.
Thanks so much,
Jennifer Edmondson
Intel Corp, AZ

Hi Jennifer,
for the inbound to XI, e.g. CL0510 you don't have a sender agreement since when you setup up the WE21 trfc Port on CL0510 it points to the XI system as a regular type T SM59 connection. On the connection you can enable the TRACE flag and see in the trace what payload got sent and any errors. I had a problem with that as my user / password to the XI machine was wrong.
The other part I'm missing from your message is, did you do all the Repository stuff beforehand, e.g. import the IDOCs for each Software Components(defined in the SLD, Tech and Buiz System), then when you use the dropdown in the Directory the Namespaces will default as the urn:sap-com:document:sap:idoc:message. Again once you have done the repository there is no need to write namespaces by hand at all. Do not put an IDOC into a Message Interface, may be into an action if you like to put a scenario into the IR (not necessary).
On the Receiving IDOC Adapter you will specify all the RFC stuff for the EL0510 system and this one goes into an receiver agreement.
I'm sending MATMAS from R/3 to XI to File Adapter or SOAP and no issues at all.
On CLN510 in BD87 does the IDOC has a status of send? Does it look ok?
I hope this helps. I can make some screenshots of my config if that helps. Send me an e-mail to [email protected]
Cheers
Stefan

Can we go with ALE configuration instead of receiver idoc adapter at target

Similar Messages

Maybe you are looking for