Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR

Hi Experts,
Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR 373 error is coming .
Some one suggested note no 886102 but i went inside i did not find correction or code for implementing please any body suggeste for rectifying this error.
Please tell correct aproach for solving the issue.

Hi,
there is some problem with your RFC connection
just go to WE20 T code and expand partner type LS
here search your r/3 system and click on that here you can find the details of idoc
if you are not able to correct yourself you can contact basis team for that.
just go to RSA1--> using the conxt menu doa check of Source system you will get the error message
just send the screen shot of the same to Basis team they will take care of the same.
Br
santosh

Similar Messages

Incorrect IDoc type ZSBC052 in the ALE definition of the source system

hi guyz,
i am getting the following error while checking the source system in bi.
Incorrect IDoc type ZSBC052 in the ALE definition of the source system RSAR 373
please guide through your expertise.
regards,
raps.

Hi,
Check the below given thread,
[Source System Check Problem;
[Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR;
Regards,
Durgesh.

Incorrect Idoc Type in ALE Definition of Source System

hi,
I have defined a R/3 Source System in BW client. This source system points to another R/3 Server in our system landscape. When I right click on the source system and click on the "check" option, getting the following error - "Incorrect Idoc type ZSKB013 in the ALE definition of the source system".
Where can I change this setting and will this be done on BW side or R/3?
regards,
SK

Hi,
there is some problem with your RFC connection
just go to WE20 T code and expand partner type LS
here search your r/3 system and click on that here you can find the details of idoc
if you are not able to correct yourself you can contact basis team for that.
just go to RSA1--> using the conxt menu doa check of Source system you will get the error message
just send the screen shot of the same to Basis team they will take care of the same.
Br
santosh

Incorrect IDoc type ZSBG014

Hello,
I have with source system.
When I chose: RSA1->Source System -> right clik check I got this message:
Incorrect IDoc type ZSBG014 in the ALE definition of the source system.
And I have problem with loading data to ODS. What should I do ?
Thx for help.
Ania Baranowska

Hi Ania,
please try to restore the source system connection in RSA1 of the BW system.
RSA1 -> Source System -> select "restore" from context menu
The "Restore" procedure will help to delete the partner profiles in R3
and BI, then do a restore on the source system in BI & it should recreate
them automatically.
Rgds,
Colum

Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.

Hi !
When I triggering the load from BW it is giving me an error Incorrect IDoc type ZSWA003 in the ALE defintion of the source system.
When I am checking the connection in source system with R3 system , it is giving me this error and asked me to Enter IDoc type ZSWA011 .
Please tell me how to do this.

Hi,
I assume that the source system has been copied fom production onto quality-system (or somothin likely).
To solve that, plase refer to the oss-note 886102.
https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=886102
https://service.sap.com/sap/support/notes/886102
Hope that helps.
cheers
Sven
Edited by: Sven Muntermann on Mar 26, 2009 6:21 PM

Incorrect IDoc type ZSBB010 in the ALE defintion of the source system.

Hi,
We have done client copy of BW production system into BW test system.
I am getting following error while checking Test R/3 system in BW Administrator workbench.
Diagnosis
Incorrect IDoc type ZSBB010 in the ALE defintion of the source system.
System response
Error when sending data to BW.
Procedure
Enter IDoc type ZSBB017 .
Ring any bell.. Thank you for Ur time..
Cheers
Senthil

Hello Senthil,
Please check WE20 transaction and look for idoc type there.Most likely you need to make some corrections in there. Also check BD64.
Regards.
Ruchit.

ALE inbox of BI is identical to the ALE outbox of the source system

Hi experts
We have BW 7 on ERP (ECC) 6. We have BW and ERP TOGETHER on the same developing system. BW is designed on developing client 100 (it is future productive client on the future productive system). It is of course default "myBI" source system. Upload is correct.
But because data is only inside clinet 200 (in the same system) I must create SAP source system client 200. It is correct, RFC destination is corect, source system clnt200 is correct and active. But data I cannot upload from this source system clnt200 - IDOCs are not correct, BW monitor is yellow and message:
ALE inbox of BI is identical to the ALE outbox of the source system
Is mistake in situation "the same system - various clients and sourcesystems"? Do you have any experiences with BW on the same system with ERP 6 and client enviroment?
Thanks
Ales

Hi Ales,
The problem can often be caused due to missing authorizations with the background user used to receive the data in BW or
the background user in the source system that sends the data to BW. Please check the authorizations as per the note
150315 , sometimes SAP_ALL profile does not have the required authorizations so please check that the background users
have the profiles mentioned in the note 150315:
As per the note:
Reason and Prerequisites
a) In the BW there exist two user:
   i) a human administrator, using S_RS_ALL
   ii) a user called BWREMOTE (or similar), used to receive the data
       from the OLTP, using S_BI-WHM_RFC
b) In the OLTP there exist also two user:
   i) a human administrator, needing authorizations to create users
       and RFC-destinations.
   ii) a user called ALEREMOTE (or similar), used to ...
       1) ... connect the OLTP to the BW
       2) ... extract the data
       3) ... send the data to the BW
       4) ... show monitoring dialogs
       for tasks 1 to 4, the profile S_BI-WX_RFC is used (however does
       not suffice on some points since some authorizations are
       missing in the delivered profile)
       5) ... make customizing of OLTP extractors
       for this, additionally the authorizations to execute
       IMG-functionality, to execute Transaction SBIW and
       to maintain the applications, which shall be customized, must
       be given during the customizing functionality is used.
I hope that this helps.
Regards,
Des.

ALE Change Pointers in source system not active

Hi All,
I am trying to load 0COSTELMNT using deltas. The initial load is OK and then i use a delta and it fails and i get the error:
"ALE Change Pointers in source system not active"
I have carried out the following steps in an attempt to resolve the problem - but it didnt. Anyone have any advice??
(1) Checked BD61 to confirm whether the change pointers are active
(2) Checked BDCP to confirm the number range is maintained
(3) Checked SALE (Activate change pointers for message types) to confirm whether the change pointer has been activated for the type we need:
COCOKA Control segment CO object/cost element
COELEM Cost element master data
(4) In transaction snum, Selected number ranges and confirmed the intervals are setup
No. 01
FROM: 0000000001
TO: 0000009999
(5) Activate transfer structure
(6) Replicate Datasources
Thanks,

If you are transferring master data from source system, the BD61 setting on the source system should be checked.
Why it has been unchecked - not sure (likely someone did it by mistake).
It shouldn't have any effect on txnl delta. What will be effected though is that you will have lost delta of the ALE based data sources for the period this setting was unchecked.

When we are able to see the data in Tcode RSA3(Source system)

Hi,
Please help me!
In enhancement after doing the R/3 stuff, when we are able to see the data in Tcode RSA3 in R/3 only?
Give the detail for all types of data source and for all types of loads.
eg: Std data source for deltaload, Generic data source for full load.....etc...
Regards,
Shiva.

Sure...
I am doing enhancement for datasource '2LIS_05_QVUDN'.
I complited the R/3 stuff and check the data for enhanced fields in RSA3...it's giving run timeout run time error.
Then I just ignore that error and I complited BW stuff successfully....after compliting BW stuff I am able to see the data in RSA3 in R/3.
So my question is, What is the root cause for this....?
When we are able to see the data in RSA3 in source system.?
please give me details for all types of datasource and all types of loads so that it will helps a lot for me in future.

Cloning use the different gcc version between source system and target sys

Hi All,
Our system is: Application tier and Database tier is split to two servers.
We should run a cloning, but I found the different gcc version on application tier on source system and target system.
The source application tier server is RedHat Linux ES3, gcc version is 3.2.3
The target application tier server is RedHat Linux ES3, gcc version is 2.9.6
There is the same gcc version on database tier on source system and target system, they are gcc 2.9.6.
My question: Can I use the different gcc version between source system and target system when I run an erp cloning?
Thanks & Regards
Owen

Not necessarily, you might get some errors if the version is higher and it is not supported by the OS. An example is Note: 392311.1 - usr/lib/gcc/i386-redhat-linux/3.4.5/libgcc_s.so: undefined reference to 'dl_iterate_phdr@GLIBC_2.2.4'
To be on the safe side, make sure you have the same version (unless you want to give it a try).

IDOC type to send OPEN ITEMS per INVOICE to external system?

Dear EDI Experts,
we want to send OPEN ITEMS of a customer per document via EDI to an XML file.
We checked on idoc type CRESTA01 but this idoc type provides "only" the total OPEN ITEMS of a customer but NOT e.g the invoice document numbers.
Is there any way to generate an IDOC or XML file with the invoice numbers and its OPEN ITEM amounts?
We want to transfer that data to an HH device in order to show customer which invoices yet to be paid.
Any idea?
Many, many thanks
Regards
JW

Hello,
many thanks for the quick answer to my question.
We want ONE credit idoc per one customer showing all OPEN ITEMS with the document number.
That info is sent to the Handheld in order to provide customer exact info which invoice he has not paid yet.
We do not need ONE idoc per ONE document.
But it seems no standard idoc provides such info and we have to call a FM to provide that info to a Z-Segement of CRESTA01. Is that correct?
Port definition XML in we21 for idoc type is understood.
Thanks a lot
Regards
JW

Which idoc type allows to send plant/sloc info to external system?LOISM001?

Dear EDI Experts,
we are looking for a solution for the following issue:
An external system (Mobile solution) shall get plant/stock info from SAP ERP.
Process:
1.Plant/Slocation is NOT empty, e.g. Material 1100 -> 100 PC
2. Stock is posted to Pant/Sloc, e.g. Material 1110 -> 50 PC + Mat. 1200 -> 80 PC
For the stock movement idocs can be generated BUT we need ALL stock of Plant/Sloc in idoc
-> 100 PC of 1100
-> 50 PC of 1110
-> 80 PC of 1200
As far as I know NO standard IDOC type exists which offers to transfer such info.
I came across the LOISM001 (to be triggered via transaction POIT) idoc which may meet the requirments. BUT it creates an idoc per material.
Questions:
1. LOISM001: Is there any chance to combine all materials of a plant/storage location to ONE idoc?
2. Any other idoc type suitable and how to trigger automatically?
Many thanks
Regards
JW
Edited by: Jens Wolf on Jul 1, 2008 3:34 PM

Hi !
You may check out the PROACT01.
It's designed to transmit stock data.
Hope that helped a bit.
Rainer

BHOLD Modelgenerator / Modelloader: missing application name in permission in the Role definition of the exportflie.

I have 2 applications (SAP-T and SAP-R) stored in BHOLD Core with same permission: Administrator.
I have 2 roles (Koos Test1 and Koos Test2) stored in BHOLD Core. "Koos Test1" role has been connected to
permission Administrator belonging to application SAP-R and the "Koos Test2" role has been connected to permission Administrator belonging to application SAP-T.
When I make an export with BHOLD Model Generator, these permissions have correctly been stored:
<application name="SAP-T" module="" parameter="0" protocol="DCOM">
<Permission name="Administrator" description="Administrator" />
</application> <application name="SAP-R" module="" parameter="0" protocol="DCOM">
<Permission name="Administrator" description="Administrator" />
</application>
But the 2 roles are not correctly been stored in the export file:
<role name="Koos Test1">
<task name="Administrator" description="Administrator" />
</role> <role name="Koos Test2">
<task name="Administrator" description="Administrator" />
</role>
The missing link is the definition of the application to which the permission belongs.
This means that the role model is not correct when I import this generated export file into another BHOLD environment
with Modelloader.

Koos,
I just went through this and I definitely see unexpected behavior but not quite like yours........When I do this, the roles are added fine and the applications are added fine. However, it only makes one 'Administrator' permission to me and links it to both
roles. Not sure if this is related to using same name for permissions with different apps or what. My version of BHOLD I am testing this with is 5.0.2724.......this is the pertinent contents of my export file:

<application name="SAP-T" module="" parameter="SAP-T" protocol="DCOM">
    <Permission name="Administrator" description="Administrator" />
</application>
<application name="SAP-R" module="" parameter="SAP-R" protocol="DCOM">
    <Permission name="Administrator" description="Administrator" />
</application>

<role name="Koos Test 1">
    <task name="Administrator" description="Administrator" />
</role>
<role name="Koos Test 2">
    <task name="Administrator" description="Administrator" />
</role>

One thing..........I used 'Administrator' as both permission name and description. Perhaps if the descriptions are different but the names are the same, it would show the expected results.......I will have to test this later......

Error in the Data Selection - Errors in Source System RSM 340

Hey Everyone,
I'm having an issue with loading a Delta for 0MAT_PLANT_ATTR. This is the second night it has happened, where I get the error "Error in the Data Selection". This error happens in the EXTRACTION part of the Monitor. And, we cannot run another Delta to see if it'll work, we have to delete the old Delta Init, and run a new one. The other error is "Errors in Source System - RSM340". That's as much it gives.
Could anyone suggest why this would be happening? I checked RSA3 in R/3, and no errors on the extraction. I also checked sm37 against the job that loads that data, and it completed successfully. I honestly don't think there's an issue with the data. We cannot have this happen often, and I just need to know if this is something that can be corrected.
Thanks,
John

There is nothing wrong with the TID's or anything like that. There is also no selection criteria in the infopackage.
When the Delta fails, the error occurs under EXTRACTION in the monitor. It seems to be successful under TRANSFER and PROCESSING in the monitor, which I find strange. Also, I run a new Delta Init with Data Transfer, and that works just fine.
So, I'm not sure what it could be?

SLT Replication for the same table from Multiple Source Systems

Hello,
With HANA 1.0 SP03, it is now possible to connect multiple source systems to the same SLT Replication server and from there on to the same schema in SAP HANA - does this mean same table as well? Or will it be different tables?
My doubt:
Consider i am replicating the information from KNA1 from 2 Source Systems - say SourceA and SourceB.
If I have different records in SourceA.KNA1 and SourceB.KNA1, i believe the records will be added during the replication and as a result, the final table has 2 different records.
Now, if the same record appears in the KNA1 tables from both the sources, the final table should hold only 1 record.
Also, if the same Customer's record is posted in both the systems with different values, it should add the records.
How does HANA have a check in this situation?
Please throw some light on this.

Hi Vishal,
i suggest you to take a look to SAP HANA SPS03 Master Guide. There is a comparison table for the three replication technologies available (see page 25).
For Multi-System Support, there are these values:
- Trigger-Based Replication (SLT Replication): Multiple source systems to multiple SAP HANA instances (one source system can be connected to one SAP HANA schema only)
So i think that in your case you should consider BO Data Services (losing real-time analytics capabilities of course).
Regards
Leopoldo Capasso

Incorrect Idoc type ZSPA065 in the ALE definition of the source system RSAR

Similar Messages

Maybe you are looking for