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 doesn’t 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

Similar Messages

  • 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?

  • 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:<b>error in ale service layer</b>

    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 .

  • 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

  • Status 29: Error in ALE service : Entry in outbound table not found

    IDoc: 0000000003560240 Status 29: Error in ALE service
    Entry in outbound table not found
    No partner profile (outbound parameter) could be found using the following key:
    /0000000000/LS//YHROT_XXM_IN////
    This refers to the key fields in table EDP13:
    RCVPRN  Partner number
    RCVPRT  Partner type
    RCVPFC  Partner function
    MESTYP  Logical message
    MESTYP  Message code
    MESCOD  Message function
    TEST    Test indicator
    Procedure
    Please check the EDI partner profiles.
    But The IDOC befor this and after this is successfully run.
    And even after reprocessing also it is giving same error.
    After checking Contorl record, we found that there is no data in receipant Info in Partner Tab.
    What would be the issue.
    Please suggest. 
    Thanks & Regards,
    Monika

    Hi ,
    Thanks for your reply.
    We are using one custom message type.
    I would like to give you example of exact scenario.
    Suppose my IDOC has large amount of segments then ,
    It is dividing as
    1st IDOC : Control record ....header and data segments
    2nd IDOC : only data segment
    3rd IDOc : only data segment
    4th IDOC : data segment and Trailer.
    In this way, I am getting all my 4 IDOCs in error.
    What should be d reason?
    your help will be grateful.
    Hi Everyone,
    any update?
    Edited by: Monika.Dhumal on Feb 14, 2012 11:49 AM

  • 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

  • 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.

  • 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 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

  • 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

  • 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

  • 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

  • Status 51:No status record was passed to ALE by the application

    Hi All,
    my scenario is file->XI->IDOC.
    data is reaching r/3 system, but i see below error in WE02
    status 51: Application document not posted
    No status record was passed to ALE by the application
    registering the function module, linking FM with basic type with direction equal to 2, assigning FM to process code and inbound parameters of partner profiles are configured well.
    Plz let me know if i missed any steps.
    Thanks,
    Goutham

    use similar thread
    Inbound IDOC
    In WE19, Give the IDOC number & execute ... then put the cursor on the idoc control record . then click on the Standard Inbound push button on the application tool bar.it will show show all the details like partner no,type , message type , process code & function module name ...
    now put a break point in the function module .. & debug .
    if u r using customised inbound function module , then click on inbound function module .. there u will get a pop screen with FM name & debugging option in both background & foreground mode...
    Edited by: Dharamveer Gaur on Sep 19, 2008 2:17 PM

  • No status record was passed to ALE by the application

    Hi Experts,
    My requirement is something like this: The middleware (XI) is triggering an IDOC which is Inbound to SAP-ECC. This IDOC is used for posting of Financial documents (Invoice and Credit memos).
    I am processing the IDOC by writing a FM. Inside the FM I am reading data from IDOC and using a BAPI to post the documents. Then I am updating the status of the IDOC based on successful or unsuccessful posting.
    Issue: When XI triggers the IDOC, the IDOC is resulting in status "No status record was passed to ALE by the application". This is not the status that I am populating inside my FM. This means that the control is not entering the FM at all (please correct if I am wrong).
    My findings: When I re-process the same IDOC which resulted in error previously using WE19, the control goes inside my FM (obviously as I give my FM name in WE19 ) and the status gets populated according to my code.
    Problem that I am facing is only when I am trying to do an Intergration testing.
    I have searched SDN for same issue and found out that I need to clear/refresh all the necessary variables. I am doing that (and double checked it too).
    Please help me with this problem as I am running out of ways to find the solution (and time also ).
    Many thanks,
    Daljeet.

    Hi Daljeet,
    Please check SM58 logs.
    Thanks,
    Best regards,
    Prashant

Maybe you are looking for