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

Similar Messages

BI Idoc type not same as the source system Idoc type

Hi Experts,
We have refreshed BI 7.0 from production to quality system and while restoring in source system in RSA1 we are getting error message " BI Idoc type ZSZD005 is not the same as source system Idoc type ZSAD008" with ID-RSAR371
Quick response would be really appreciated
Regards,
RaviChandra

Hope this will be helpful for you
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a04af5ab-5737-2b10-67aa-88e25e80b325

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

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

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

Which types of errors occured in "source system"?

hi
which types of errors occured in "source system"? how will correct it? send me data on it

Hi,
The common error will be RFC Connection .pls chk this links;
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a61e5e07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/bp_biv335/BI_EN/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
Hope this helps.
Regards
CSM Reddy

Is it Possible to import an IDoc type from R/3 into APO system

Hi Gurus ,
Could you please guide if we can import an IDoc type from R/3 system to APO system ?? If yes , can you please give the guidelines / step - by - step procedure for this.
Thanks in advance ,
Roseline

hi
yes u can export an idoc from r/3 to a legacy system.
the brief outline is as follows:
1. set up an rfc connection. it has to be 'T' type in t-code sm59
configure the saprfc.ini file if on windows based os. if on unix based os configure rfcexec.c to have the login details of apo system.
2.set up logical systems( at least 1 each for r/3 and apo) using T-code SALE.
3.assign clients to the logical sytems using T-code SALE..
4.create ports using tcode we20.
5. create idoc segments using we30 and release.
6. create idoc type using we31.
7. create message type using we81.
8. assign message to idoc using we82.
9.build a customer model using tcode bd64.
10. create an outbound process code usint tcode we41.
it will help if you specify your idoc that you want to use- for vendor, customer and material there are predefined distributions and idocs.
Thanks.

Active system source with IDoc type error

Hi all,
When I activate system source , it shows below message.
How can i solve this? Thanks.
"Diagnosis
     Incorrect IDoc type ZSBG021 in the ALE defintion of the source system.
System response
     Error when sending data to BW.
Procedure
     Enter IDoc type ZSBD031 ."

Hi,
I am facing the same problem,
Can any one answer on that.
I followed the following procedure
1. I recreated the connections in R3 and BW using transactions WE20 and WE21.
Do not know if these steps are necessary or not,but thats the way i followed earlier as told by my superior.
I also tried just deleting these connection, instead of recreate, both time, result was same.
It worked last time but now its giving the same error.
I check the connection and it give this error.
I tried to restore, it gave me error
Source system cannot use any of the proposed connection names
Message no. RSAR362
Diagnosis
Every connection to a source system is named using a unique two-digit identifier. Source system ZRQCLNT330 does not accept any of the proposed values.
The last proposed value was ZA.
Don't know how to proceed now.
Any suggestions?
Regards
Amit
Update on this issue.
We solved it by Restoring the source system
Steps
1. Check the rfc and rfc user in both system to coimmunicate.
2. Delete the partner profile in both system (We20/21). Please some one confirm about this.
3. Then Simply Restore the Source system. It will create the partner profiles in both system.
Message was edited by:
        Amit Chaturvedi

R/3 source system creation error(Idoc is missing)

Hi expert's.
i have created an r/3 source system in BI 7. but it's showing error when i am activating it.
error as follows.
1. Basic type ZSMA087 does not exist     EA     447
2. Incorrect IDoc type ZSDF085 in the ALE definition of the source system     RSAR     373
for the above error 1 i checked in the RSBASIDOC table. it showing the idoc type. when i am checked with the source system that is r/3 system in the partner profile for logical system. it's showing the incorrect idoc type in RSSEND outbound parameters for that logical system
when i am changed that idoc type it's showing error as follows.
"entry RSSEND zsma087 does not exit in edimsg.
after that i checked with this table edimsg. for the rssend outbound option it's won't have the idoc type zsma087. table edit is also not possible on that.
so please help me to solve the issue.
regards
Harikrishna N

Hi Hari,
                Are you using ECC6.0 system or Bw(bi7.0) & R/3 source system
Regards,
Vijay.

IDoc type could not be determined for the IDoc in F110

Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
Regards

If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

R3 to BW Extraction fails: Non-updated Idocs found in Source System

We load data from R3 to BW and this process has been successful for the past few days except last night. The error msg is listed below in between two dashed lines:
Non-updated Idocs found in Source System
Diagnosis
IDocs were found in the ALE inbox for Source System that are not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs manually using the Wizard or by selecting the IDocs with incorrect status and processing them manually.
I checked the system connection by right click the source system in the Source System page on BW and selecting "Check" and "Customizing for Extractors" from the context menu and find everything works fine.
Any idea about the IDOC thing?
Thanks

hi Subray/Bhanu,
With WE05, find some records with yellow status. How to find some missing data here?
With BD87, under BW system folder, there are two folders:
1. IDocs in outbound processing
2. IDoc in inbound processing
Under 1st folder, there is one yellow status folder called "IDoc ready for dispatch (ALE service)", continue to expand another folder called CREMAS under it, there is a blue information line which is "Receiver found , Data filtered , No conversion , No version change".
Under 2nd folder, there is one yellow status folder called "IDoc ready to be transferred to application", continue to expand other two folder under it called "BBPIV" and "RSRQST", find there is a red flash status line which is "No resources, immed. processing not possible: Too few free dialog work" under these two folders.
I need to go ahead to select these two red flash status lines and then press the Process button at the top bar?
Thanks
Message was edited by: Kevin Smith

Difference between message type and idoc type

Hi
difference between message type and idoc type
Regards
Rama

Hi,
Message Type:
A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
Diff. b/w IDOC type and IDOC
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
Example:
MATMAS is the message type and MATMAS05 is IDoc type for Material Master.
Thanks,
Shankar

Extraction failure and then picked up due to IDOC setting on source system

hi All,
Just give one master data Company Code load as an example. We run the data load every night around 12 though Process Chain. When we checked the monitor, find that it ran twice, 1st time, it ran at 12 which was supposed to run, but it failed with red error and the red error msg is:
"IDocs were found in the ALE inbox for Source System that are not updated. Processing is overdue."
then it ran again at 07:45:55 which was successful with green light. We guess this problem is caused by IDOC setting on the source system. Run WE02 on the source system, expend Inbound IDocs folder and then expend RSRQST folder, find status 64 which indicates the yellow status.
Can anyone explain here why the extraction failed 1st time around 12am due to IDOC setting on the source system, and then the run was picked up around 7am successfully?
Thanks in advance!

Hi Kevin,
this is really a strange behaviour. What I could imagine: it could be temporary network issue or performance issue or system unavailability on the r/3 source system side. maybe you could check if other processes/jobs on R/3 were canceled, or if there is any system log available at the time concerned.
Lilly

Incorrect Idoc Type in ALE Definition of Source System

Similar Messages

Maybe you are looking for