Ale Service Layer error 29

Hi All,
Plz help me in this issue, I had made the Ale connection to transfer Data, once I had done it successfully, after that I had deleted and made again, this time I am able to transfer the data, in both the clients it is showing traffic light green, however in the target client after two seconds it is converted in Red with "error in ALE service layer 29, unable to find recipient "MATFET", last time I had given MATMAS, since I am getting this error I had added MATFET also, still I am getting this error.
In Patner profile : Inbound client( Sender): MATMAS, SYNCH
In Patner profile : Outbound client( Reciver): SYNCH
In Patner profile : Inbound client( Reciver): MATMAS
Every thing is in green, no errors, in profiles and distribution model, everything is successfully created except this Traffic light and error in the receiving client.

Hi All,
According to the suggestion I drilled down the issue in BD87 and found this information.
Could not determine recipients for message type &
Message no. B1003
Diagnosis
An IDoc of message type MATFET was passed to the ALE layer, but the three receiver fields in the header record were not filled. In this case the ALE layer tries to determine the receivers from the entries in the distribution model. There are no entries available in the distribution model for the above message type.
Procedure
Define the receivers in your distribution model for this message type or deactivate distribution for these message types.
One more thing In BD87 if I go to sender client then there is node for sender system and in the receiving client there is node for receiving system, is this correct ? or both the systems should be reflected in both the systems?

Similar Messages

Status 29:error in ale service layer

i have written a stand-alone program in ale to transfer materials to inbound system.idoc got genereated but i am getting staus record as 29...
what to do if i get an status 29:error in ale service layer

Hi Pavan ,
Goto to transaction WE05 put the Idoc Number generated or enter the message type .Under the Status 29 there would be error description .
Check that out .

ALE service layer

Hi,
Can any boby tell me what the ALE service layer do in ALE.

Hi,
This layer provides ALE with an interface to R/3 to originate or receive messages containing data to or from external (or other R/3) systems.
Processing in the ALE layer consists of the following steps.
Receiver determination. If the receivers are not known, they are determined from the customer distribution model. If a receiver is not found, processing ends. For each receiver identified in this step,
the following steps are executed.
1)IDoc filtering. If an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not
meet the filter criteria, it is dropped.
2)Segment filtering. For each sender and receiver combination, a set of segments that are not required can be filtered out.
3)Field conversion. Field values in data records are converted by using the conversion rules specified for the segment. Values can be converted to global values or converted to specific values for the receiver. For example, storage location 0001 can correspond to storage location 1000 in the receiving system. The rules specified here are also available in the EIS (Executive Information System) module.
4)Version change for segments. Segments are version−controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Thus, the segment can communicate with a back−level system by blanking out the new fields. Read
the version specified in the Seg. Release in IDoc Type field of the partner profile to determine the version of the segment to be generated.
5)Version change for IDocs. IDocs, like the segments, are also version−controlled. A new version of an IDoc always contains segments of the preceding version and segments added in the new version. Thus, the IDoc can communicate with a back−level system by deleting segments that do not exist in the version specified. The version is determined from the Basic Type field of the partner profile.
6)Communication IDocs generated. The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have
multiple communication IDocs, depending on the number of receivers identified and the filter operations performed. Communication IDocs are saved in the SAP database. At this point, a tangible IDoc that can be viewed by using monitoring tools has been created in the system.
The IDoc gets a status record with a status code of 01 (IDoc Created).
7)Syntax check performed. The IDoc goes through a syntax check and data integrity validation. If errors are found, the IDoc gets a status code of 26 (Error during Syntax Check
of IDocOutbound); if no errors are found, the IDoc gets a status code of 30 (IDoc Ready for DispatchALE Service).
8)IDocs dispatched to the communication layer. In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not wait for data to be received or processed on the destination system. You read the setting in the Output
Mode field of the partner profile to determine the timing of the dispatch. If the mode is set to Transfer IDoc Immed., IDocs are immediately transferred to the communication layer; if not,
they are buffered until the next run of dispatch program RSEOUT00. After IDocs have been transferred to the communication layer, they get a status code of 03 (Data Passed to Port OK). This status does not necessarily mean that IDocs have been dispatched to the destination
system.

Need Answer on ALE Service Layer

In my cusomized outbound program i am using a function module MASTER_IDOC_DISTRUBUTE to generate the IDOCS. I am passing the both sender and reciever values to the function module MASTER_IDOC_DISTRUBUTE then distribution model in BD64 is not required. if we are not passing the both sernder and reciever to the MASTER_IDOC_DISTRUBUTE, the MASTER_IDOC_DISTRUBUTE will pick both the sender and reciever from the ALE Distribution model (ALE Service Layer) . What my doubt if i pass both sender and reciver need it won't execute distribution model in the BD64. In this situation If i need a filters and converstion for the recievers then i should use the diribution model. In this situaion if i pass both sender and reciever to the MASTER_IDOC_DISTRUBUTE does the ALE Service Layer ( Conversions & Filtters ) will execue?

Hi,
>>>>But I don't know how to achieve this. I guess using Distribute Model,
yes of course
>>>> If so, a client for edi subsystem(non-sap system) need be defined in SAP R3 system. I doubt about this.
yes a logical system for example
>>>>Another problem is how to define a client for non-sap system in SAP R3 sytem.
logical system
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Error in ALE Service While Creation of Vendor Master

hi,
I am using a scenario where a third party system is sending vendor master data to a R/3 system The file is picked up by the file adapter(sender) and mapped to IDOC format, using Idoc adapter (receiver). A Vendor is then created by posting the CREMAS03 IDOC into the R/3 system.
Everything goes fine till the Idoc comes into the R/3 system. There in BD87(Idoc Status Monitor), getting the "Error in ALE Service" error. When expanded further the specific error is that of "Cross-system company code xxxx does not exist". What is generally the cause of this error and how would I resolve it?
For those of you who have attended TBIT 40, this scenario is Example 1 - Creation of Vendor Master Data.
Any help would be appreciated?
regards,
SK

one more thing
if you want to be sure that you're using the right data
try to set your system to send the vendor data out
first - send it from BD14
and then you'll know which fields do you need
if you do that take a look at segment E1LFB1M
and check for BURKS
Regards,
michal

Status record 65 error in ale service

HI Experts,
               I have an issue when I tried to send a cost center idoc from one system to another. The company code for the record is 0093 in the sender system; however when the idoc gets created, in the idoc the value of the company code becomes SAH001. I dont know why this happens.
This is the record to in the corresponing table table- which is to be sent from sender to Receiver. The company code ie company code field value is 0093 .
The RFC/LS connections have been done and checked. I am able to send the cost center group data correctly. While sending the cost center I am encountering the following error:-
For an example
Content of created Idoc in sender
Company code field |   SAH001
The company code info is now SAH001. I wonder why ?
So when we send the idoc to recceiver, we get the same company code and I get an error that company code doesnt exist.
Content of idoc in receiver
Company code field |   SAH001
I want to display 0093.
Please tel me what is error and how to rectify?
Thanks & regards
Mathi

hI,
Testing inbound idoc :
Once you configured everything then goto WE19 Transaction :
Give message type or idoc type and execute .
now here you need to fill the Mandatory data in each segment,once you done then
idoc->edit control record -> here you need to fill sender and receiver details.
now you should get green color ,if you get red color then config issue.
now click on start inbound -> now you will get idoc number.
if you want to debug then click on inbound function module -> enter FM -> select call in debug mode and enter.
now cursor will go debug mode
http://www.photographybykevin.net/sap/idoc_overview.pdf
Testing Outbound idoc :
Once you done all configuration ..
Let me say example like invoice ,you need to send invoice from SAP R/3 to other system.
create invoice at VF01 -> Here customer should configure in Parter profile ,once you create invoice ,it creates the idoc.
debugging Outbound IDOC :
keep the break point in form routine above as i said
Create invoice or invoice list
when you maintain output type in invoice or invoice list -
Now click on Further data ->select peridoc scheduling-> back and save it.
Run RSNAST00 Program
Output application : V3
Object key : Invoice or invoice list number
Output type : RD00 or LR00
Medium = 6(EDI) ,A (ALE)
when you execute the program and it will goto debugging.
See the below status codes :
See table TEDS1 for all status codes via SE16 in SAP. Outbound ALE Status Codes
Successful Transmission:
03 - Successful outbound transmission
12 - Dispatch OK
IDoc being processed:
01 - IDoc created
30 - IDoc ready for dispatch (ALE service) (Program RSEOUT00 needs to be executed)
ALE Error Messages:
02 - Error passing data to port
04 - Error within control information on EDI subsystem
05 - Error during translation
25 - Processing despite syntax errors (outbound)
29 - Error in ALE service
32 - Resubmit edited intermediate document (DO NOT USE)
Syntax Error Messages:
26 - Error during syntax check of IDoc (outbound) Inbound ALE Status Codes
IDoc Processed Successfully:
50 - IDoc added
53 - Successful posting
IDoc ready for processing:
64 - IDoc ready to be passed to application. The IDoc will be passed to the application by program RBDAPP01.
Errors in IDoc Processing:
51 - Error - application document not posted
56 - IDoc with errors added (You should never see this error code)
60 - Error during syntax check of IDoc (inbound)
61 - Processing despite syntax error (inbound)
63 - Error passing IDoc to application
65 - Error in ALE service - indicates partner profiles are incorrect
69 - IDoc was edited
Regards,
Nagaraj

IDOC: Error in ALE Service

Hi All,
I have created a new outbound idoc type ZSLSRPT and assigned it to a partner profile with type LI in we20. I tried running my customized program for idoc outbound and the status shows Error in ALE Service, Entry in outbound table not found.
Am I missing something with the partner definition? Do I need to configure the vendor output type in NACE? Please help.
Thanks,
Kenny

Hi Kenny,
Have you setup the distribution model (BD64) for the corresponding message type?
Also check this link for your reference.
http://help.sap.com/saphelp_nw04/helpdata/en/52/16adef543311d1891c0000e8322f96/content.htm
Regards,
Ferry Lianto

IDocStatus:Error in ALE service Cross-system company code does not exist

HI All,
I am sending CREMAS04 IDOC from XI to one R/3 system,and in R/3 a vendor should get created in master table.
My IDOC is getting posted successfully but in R/3 system I am getting error that
IDoc: 0000000000705816 Status: Error in ALE service
T100 Text: Cross-system company code XXX does not exist
I have created partner profiles in receiver system and in partner profiles I have set the process code as CRE1.
Please help me to resolve this problem.

Hi Shweta
Have you checked with the data i.e. company code .
May the company code which you are passing is not there in ur receiver system.
Just check it out.
Regards
-Mitesh

MM SUS Vendor Replication Error: Error in ALE Service

Dear Experts,
We are implementing MM SUS (SRM 5.0). As a part of this we need to replicate vendors from ECC to SUS system via XI. We have created a Reduced Message Type Z_CREMAS_SUSMM and had set up the partner profile in WE20 with SUS logical system as destination and specifing the Message Type, and port of the XI system
We executed the transaction BD14 for replication, it is resulting in error 29 : Error in ALE Service : Entry in Outbound table not found.
Please provide inputs to overcome this problem
Thank you,
Regards,
Ravi

Hi Ahmed,
Thanks for your reply. We have configured as per SAP configuration guide(plan driven procurement). As per this we had set up partner profile for SUS logical system and define the outbound parameters with receiver port of XI system.
If you feel one more partner profile need to be setup for XI system then please advise us for necessary configuration.
Thanks
Ravi

STPPOD Idoc creation status : Error in ALE Service

Experts,
I am trying to send GR from MM to SUS in MM-SUS Classic Scenario on ECC 6.0 Server. I have also configured Goods REceipt Notifications Functionality to sending GR from MM to SUS.
When i am trying to send GR Idoc is generated (STDPOD) but i am getting the Error whose status - 29 in WE02 t-code :
Status Message for Selected IDoc
Status Text:   IDoc: 0000000000211243 Status: Error in ALE service
T100 Text:     Entry in outbound table not found
While i have properly configured Partner Profile for Message Type STPPOD :
Partner Role          Basic Type     Receiver Port           Application     Output Mode
LS        DELVRY03      A000000018 (XI port)           GRN               Transfer Idoc Immediately
When i try WE19 t-code for this idoc, i found the error "Port '' does not exist in the table of port descriptions"
while i have already defined port (A000000018)in WE21 t-code and this port also working fine for other messages.
Please suggest.
Thanks.
Regards,
Pawan Keshwani

Nikhil,
Issue is resolved it was the wiered error. As i removed LS from the field Partner Role in STPPOD message at partner profile(WE20) for SUS Client in ECC. Now the message STPPOD outbound message working fine.
Thanks.
Regards,
Pawan Keshwani

Error in ALE Service

hi
using the t.code BD13, i got the Customer Master Record in to the system
WE02 / WE05
IDoc:207013 Status: Error in ALE Service
Could not determine recipents for message type DEBFET
then i did in t.code WE19-- Function module IDOC_INPUT_DEBFET (in background)
Pop-up window
No Object for request IDoc selected for sending
Pop-up window
IDoc 207014 was saved and processed by function IDOC_INPUT_DEBFET
I cheked the status in WE02
IDoc:207014 Status: Application document not Posted
No Object for requested IDoc selected for sending
56 - EDI : Partner profile inbound not available.
please give me the solution, where i have to correct the issue
and i am not getting the function IDOC_INPUT_DEBITOR_MDM
Babu rao

in WE20, can yoy pls check if you have the partner profile maintained. If not pls maintain the same and the issue should be resolved.
Hope this helps.
rgds

Error in ALE service 29 Could not determine recipients for message type MAT

Hi Experts,
While transferring the material using ALE am getting error 29 ie 'Error in ALE service' and message is 'Could not determine recipients for message type MATFET'.
Also i ve recieved the materials with the proper status al the end am getting the above error.
Kindly help me out.
Thanks in advance.

Hi ,
Status 29 means " partner profile not found " . Please check if the recieving partner is configured properly in WE20 in sender system.
Also make sure that the Port and RFC definations are also completed. If the IDoc is manually triggered then please make sure that control record parameters of the idoc are properly filled - if we miss the details ( like wrong port given , wrong basic type for message type - or extended message type ) then also the idoc will fail in status 29 even though the partner profile is properly configured .
Since your idoc is getting generated i think no issues with BD64 since already interested recipeints were populated in control record of idoc.
Regards
Vikas Chaudhary

Error in ALE service status 29

EXPERTS.
i have configurged all the ale settings.
1)logical systems   SALE
sender - 800 client
receiver-810 client
2) SM59 R/3 connections
   Receiver , here i checked the remote login , it is working , i mean i am able to login to 810 client
3)WE21 TRfc
generated port ie A000000038.
and given RFC destination as RECEIVER ---this is the logical system name of receiver
4)Done BD64
5)WE20 outbound partner profile
here in outbound parametes eneterd message type as cosmas
and in this given receiver port as A000000038.
and basic type as cosmas01.
6)Now i activated all the settings for changes pointers.
7)I changed cost centre in KS02 and saved
8)Executed BD21 ie idoc generation for change pointers
Got a pop up saying 1 master copy idoc generated , 1 communication idoc generated.
9)WE02.
Now status is 29 Error in ALE service
I clicked on control record.
In partner following information is there.
Receiver Informatiion
Port    : A0000000038
partner number : RECEIVER
partn type : LS
Sender Infornation
Port : SAPSHS
Partner number : SENDER
partn type : LS
In sender info port is comming as SAPSHS i dont know from where it is comming.
So please tell me , where went wrong.

Hi thanks for the reply
I executed WE19 as you said.
In the input screen given the idoc num 5234746
and in the menu option -> IDoc ->Test outbound idoc ->executed.
Now pop up came Idoc sent to R/3 sytem or external program.
Then we02.
one new idoc is generated ie 5234747.
And it is green ie status 3 data pased to port ok.
1) Why now it came to status 3? Even i checked the earlier failed idocs they also turened to status 3? Why so
2)So when ever we execute we19 , will it generate new idoc?
3)When we are doing in our company servers is it suggestable to execute we19 rather than BD87 , since WE19 geneates new idoc?Will business accepts it?

Vendor Master Replication Error from ECC to SUS : Error in ALE Service

Dear Experts,
We are implementing MM SUS (SRM 5.0). As a part of this we need to replicate vendors from ECC to SUS system via XI. We have created a Reduced Message Type Z_CREMAS_SUSMM and had set up the partner profile in WE20 with SUS logical system as destination and specifing the Message Type, and port of the XI system
We executed the transaction BD14 for replication, it is resulting in error 29 : Error in ALE Service : Entry in Outbound table not found.
Please provide inputs to overcome this problem
Thank you,
Regards,
Ravi

Hi,
Check
Re: Idoc Error Status "Entry in outbound table not found "
Looks like some issue with the partner profile set up for the sender or receiver of the EDI message in WE20.
Set up them again and When these have been set up try reprocessing your IDocs from BD87

5 IDOC with status 29 Error in ALE service

hi there,
im looking at this similar problem with less information on me the only info i got is this can anyone help me out pls
IDOC Status Outbox:
IDOC failure between 13/07/2008 to 14/07/2009
1 IDOC with status 02 Error passing data to port
5 IDOC with status 29 Error in ALE service
IDOC Status InBox:
88 IDOC with status 51 Application document not posted
regards
raju

Hi,
Check this thread.
DB13-DBCHECK by saving log-throwing DUMP:TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
Regards.

Ale Service Layer error 29

Similar Messages

Maybe you are looking for