Error in ALE customization.

Hi,
when I use PRRW transaction to transfer all data from HR system to FI.
I am getting error :
"In your system an error occurred that can probably be corrected by making changes in ALE customizing. "
I have checked RFC connection from HR to FI is in place.

Have you checked RFC destinations defined to your logical system?
Use transaction BD97,check the assignment to RFC destination for your logical system, also insue that you are using correct(standard BAPI Destination or Special method destination)as per your system customization.
Hope this will help you.

Similar Messages

Ale customization through executable programs

i have followed the following steps to customize ale for message type MATMAS
create logical systems EP800, EP810
assign logical systems to clients
create modelview --> save
add message type --> save
generate partner profiles --> execute
here iam getting an error saying that
   Port could not be created
   RFC destination EP810 not specified for system EP810
Enter the RFC destination and restart the generation
to solve this i have manually created port in we21.
but still uam getting the same error.
how to procede now

Hai Lavanya
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
        save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
   select all what ever you want and delete remaining fields.
   save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
   it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
   give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
Regards
Sreeni

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<b> Error in ALE Service, Entry in outbound table not found</b>.
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

Status 51 Error in ALE IDOC

Hi,
Iam trying to send a MATMAS Idoc from one client to another client , which is in the same R/3. The outbound staus is 03 and the inbound is 51.
I just created a material (Material details are attached below for reference) and send tht material to the other client using BD10.
can you please tell me the Inbound function module name which i should use to post it again.
Material Name:KRMATERIAL
Industry sector : Mechanical Engineering
Material Type : Finished Products.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
Thanks
-Karthik

Hi Karthik,
Just follow the procedure, this is for MATMAS
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
<b>Reward Points if this helps,</b>
Satish

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.

Idoc error 29 - Error in ALE service

Hi All,
I have this error 29 - Error in ALE service when the idoc is created (No global company code is assigned to the company code).
This message comes after 01 - IDoc created
Any idea why this is happening? I have created conversion rule to convert the company code.
Help needed uegently.
Thanks!

Hi,
Status 29 generally occurs when the Partner Profile has not been configured.
Check if the Message type is configured on the outbound side.
Thanks
Krithika

Error in ALE customization.

Similar Messages

Maybe you are looking for