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.

Similar Messages

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

Restoring the source system connection in BW

Hi all,
Ive been trying to upload data for 2 of my infocubes, and the extractions are bouncing. The message in R/3 is told me to check the connection. The RFC are fine. But when I tried to restore the source system connection (RSA1 in BW), it sent me the following error messages:
1.- Basic type ZS 118 does not exist.
2.- The following error in the source system:
3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
The description in each error is:
Error #1:
Diagnosis
    IDoc type ZS 118 could not be found.
System response
Procedure
   Please enter an IDoc type that exists.
Error #3:
Diagnosis
    Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
System response
    Error when sending data to BW.
Procedure
    Enter IDoc type ZS 118 .
They told me this IDocs are created automatically by the connection. Is that true?
How can I fix this, so that I can restore my connection and do the data extraction?
Thanks a lot
Regards,
Vic

Hi Victor Tostado
1.- Basic type ZS 118 does not exist.
Type Transaction WE30. Check iDoc types Obj. Name : RSSEND -> press F7
a.) Enter 'RSSEND' in the Obj. Name field. You will see an entry similar to the one below:
          RSSEND                          Data transfer from the source system (template)
                [-] E1RSSH               Data transfer IDoc: Header information
                         [+] E1RSHIE    Data transfer Idoc: Hierarchy header information
                                E1RSTXT   Data transfer IDoc: Texts
     b.) Enter RSREQUST in the Obj. Name field. You will see an entry similar to the one below:
            RSREQUST                    Data request to the source system
                 [-] E1RSRH               Data request IDoc: Header segment
                         [+] E1RSRHI     Data request IDoc: Hierarchy
                         [+] E1RSRTX    Data request IDoc: Texts
                         [+] E1RSRMD   Data request IDoc: Master data
                         [+] E1RSRIS      Data request IDoc: InfoSource
     c.) Enter RSINFO in the Obj. Name field. You will see an entry similar to the one below:
            RSINFO                         Info IDoc
                [-] E1RSHIN             InfoIDoc: Status segment
                        E1RSPIN            InfoIDoc: Data packet segment
                        E1RSEIN            InfoIDoc: Error segment
d.) If any of the above do not exist, contact your BASIS Team.
2.- The following error in the source system:
Type Transaction SM59. Maintain RFC destinations
a.)     Open the RFC Destinations. b.) Find your Source System and double click on it. c.) Technical setting should contain information regarding your source system d.) Logon Information should contain source system client and name & password for you remote logon.
3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system
Type Transaction WE21. iDoc Processing Ports.
receivers port is not available go to WE21 -> create port
a.) Select 'Ports' and then 'Transactional RFC'. b.) Click on the Port # for you source system. c.) Verify description & SAP R/3 versiond. RFC Destination should be one created in SM59. If non-existent then create one.
I) Type Transaction SE16. Data browser (for R/3 -> BW Connections)
Enter RSBASIDOC Print out copy of all entries in table.
II) Type Transaction SM30. Msg Types & Assignment to iDocs
Enter 'EDIMSG' in the Table/View field. Click on the 'Enter Conditions' option for Restrict Data Range. Click 'Maintain'. Select Message Type. Then enter 'RSSEND' in "From' field. Verify that the Basic Type matches what is in your RSBASIDOC table for each of your connections. If any are missing any entries you must create them as follows: Create another session and type Transaction WE30. Enter IDoc Type (ZSBAXXX) in Obj. Name field (Suggestion: Start new type with 'ZS' + Transfer Structure Prefix + (3)#'s) Select Create. Select "Create from Copy'. Enter 'RSSEND" in 'Copy From' field Enter Description (i.e. IDoc Type for BW Development) Execute (Green Check). Repeat for other missing entries.
Regards
Sangram Sutar

RFC Error:The BW IDoc type ZSBA011 is not the same as the source system

Hi Experts,
RSA1Source System (Context Menu) Check
I am getting the below error
<b>The BW IDoc type ZSBA011 is not the same as the source system IDoc type ZSBD012               </b>
What might happened wrong.When i checked with my Basis Consultant who is new to job,Replied every this is ok with regeards to RFC.
Where should i check to correct the error
Thanks

Hi,
Did you do a system copy for BW ?
Try a restore (rightclick on your source system) in most cases this will solve the problem.
If not check the notes below:
184322 Procedure after DB copy of BW source systems
886102      System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
325470      Activities after client copy in BW source systems
325525      Copying and renaming systems in a BW environment
184754      Procedure after BW database copy
184447      Building a BW-system landscape
184971      Notes on BW source system connections
140276      Error in source system assignment
524554      Storing destinations in the BW environment
538052 Maintenance of Myself destination in BW
Regards, Patrick Rieken
Message was edited by:
        Patrick Rieken - BI-Formance B.V.

FRM-10056: Incorrect module type stored in the file

Currently, we have been tasked with moving from windows to a red Hat Linux environment using OFM. We are currentlly using forms 11g. I have been operating totally in a windows environment and I got Linux compile code off the internet. When I try to compile the menu, I get the following:
I got the forms to compile but I cannot get the menu file to compile when I use the following:
for FILE in `ls $FORMS_PATH/*.mmb`; do
OUTPUT=${FILE/mmb/mmx}
echo "$FILE -> $OUTPUT"
frmcmp_batch.sh $FILE userid=userid/password@database Module_Type=MENU batch=yes output_file=$OUTPUT compile_all=special
done
I get the following results:
/public/server/apps2/code/test/forms/testmenu.mmb -> /public/server/apps2/code/test/forms/testmenu.mmx
Forms 11 (Form Compiler) Version 11.1.2.1.0 (Production)
Copyright (c) 1982, 2012, Oracle and/or its affiliates. All rights reserved.
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
PL/SQL Version 11.1.0.7.0 (Production)
Oracle Procedure Builder V11.1.2.1.0 - Production
Oracle Virtual Graphics System Version 11.1.2.1.0 (Production)
Oracle Multimedia Version 11.1.2.1.0 (Production)
Oracle Tools Integration Version 11.1.2.1.0 (Production)
Oracle Tools Common Area Version 11.1.2.1.0
Oracle CORE 11.1.0.7.0 Production
FRM-10056: Incorrect module type stored in the file
Form not created
I can not seem to find any info on resolving that error. Any suggestions?

Here is the content of our frmcmp.sh script.
#!/bin/sh
# frmcmp.sh - executable Bourne shell script to run the Forms Compiler
#             (Generator) after setting up the required environment
# NOTES
# 1/ The Forms installation process should replace
#    <percent>FORMS_ORACLE_HOME<percent> with the correct ORACLE_HOME
#    setting. Please make these changes manually if not.
# 2/ Some of the variables below may need to be changed to suite your needs.
#    Please refer to the Forms documentation for details.
# Set ORACLE_HOME if not set in the calling environment:
ORACLE_HOME=/app/oracle/product/Middleware/Oracle_FRHome1
## Change this to match where your FMw product is installed.
export ORACLE_HOME
PATH=$ORACLE_HOME/bin:$PATH
export PATH
DISPLAY=<DNS Name or IP address here and the port used.>
## For Example: Your_Domain_name.com:0.0
export DISPLAY
# Search path for Forms applications (.fmb &.fmx files, PL/SQL libraries)
# If you need to include more than one directory, they should be colon
# separated (e.g. /private/dir1:/private/dir2)
# Note: the current directory is always searched by default
FORMS_PATH=<INCLUDE all directories where Forms objects are found (Lib's, Memu's, etc)>
export FORMS_PATH
# You may need to set one or more of TNS_ADMIN, TWO_TASK or ORACLE_SID
# to connect to database
TNS_ADMIN=<DIRectory where your TNSADMIN.ora files exists>
export TNS_ADMIN
ORACLE_SID=<YOUR DB SID>
export ORACLE_SID
# System settings
# You should not normally need to modify these settings.
if [ `uname -s` = 'SunOS' ]; then
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/jdk/jre/lib/sparcv9/server:$ORACLE_HOME/jdk/jre/lib/sparcv9/native_threads:$ORACLE_HOME/jdk/jre/lib/sparcv9:$LD_LIBRARY_PATH
    export LD_LIBRARY_PATH
elif [ `uname -s` = 'HP-UX' ] && [ `uname -m` = 'ia64' ]; then
     LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/jdk/jre/lib/IA64W:$ORACLE_HOME/jdk/jre/lib/IA64W/server:$LD_LIBRARY_PATH
      export LD_LIBRARY_PATH
elif [ `uname -s` = 'HP-UX' ]; then
    SHLIB_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/jdk/jre/lib/PA_RISC2.0W:$ORACLE_HOME/jdk/jre/lib/PA_RISC2.0W/server:$ORACLE_HOME/jdk/jre/lib/PA_RISC2.0W/native_threads:$SHLIB_PATH
      export SHLIB_PATH
elif [ `uname -s` = 'AIX' ]; then
    LIBPATH=$ORACLE_HOME/lib:$ORACLE_HOME/jdk/jre/bin:$ORACLE_HOME/jdk/jre/bin/classic:$LIBPATH
    export LIBPATH
elif [ `uname -s` = 'Linux' ] && [ `uname -m` = 'ia64' ]; then
    LD_LIBRARY_PATH=$ORACLE_HOME/jdk/jre/lib/ia64/jrockit:$ORACLE_HOME/jdk/jre/lib/ia64/native_threads:$ORACLE_HOME/jdk/jre/lib/ia64:$ORACLE_HOME/lib ; export LD_LIBRARY_PATH
    export LD_LIBRARY_PATH
elif [ `uname -s` = 'Linux' ] && [ `uname -m` = 'x86_64' ]; then
    LD_LIBRARY_PATH=$ORACLE_HOME/jdk/jre/lib/amd64/native_threads:$ORACLE_HOME/jdk/jre/lib/amd64/server:$ORACLE_HOME/jdk/jre/lib/amd64:$ORACLE_HOME/lib ; export LD_LIBRARY_PATH
    export LD_LIBRARY_PATH
elif [ `uname -s` = 'Linux' ]; then
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/jdk/jre/lib/i386/server:$ORACLE_HOME/jdk/jre/lib/i386/native_threads:$ORACLE_HOME/jdk/jre/lib/i386
    export LD_LIBRARY_PATH
    # Set LD_ASSUME_KERNEL for RedHat 3.x
    if [ -f "/etc/redhat-release" ]
    then
      RHVER=`/bin/rpm -qf /etc/redhat-release --qf "%{VERSION}\n" 2>/dev/null`
      case $RHVER in
      3*AS | 3*ES)
        export LD_ASSUME_KERNEL=2.4.19
      esac
    fi
else
    LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/jdk/jre/lib/sparc:$ORACLE_HOME/jdk/jre/lib/sparc/native_threads:$LD_LIBRARY_PATH
      export LD_LIBRARY_PATH
fi This file gets sourced in our compile.sh script that all developers use to compile their Forms Objects (.fmb, .pll, .mmb, etc).
Here is a very simplified version of our compile.sh...
#!/bin/ksh
## Source the frmcmp.sh
. /<path to file>/frmcmp.sh
frmcmp module=$filename userid=user_id/pw@databasev module_type=form compile_all=yesHope this helps.
Craig...

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

Inbound idoc error in the source system

HI,experts
I manually configurate the idoc type ,message type ,etc between the BW system and r/3 source system when the automatic program encouters errors. And the communication between BW and source sysyem seems ok since the source system is activated successfully in BW side.
But when I check the inbound the idoc in source system after i triggerred a full load for the datasource 0FI_GL_4,an error occurs in the inbound process in R/3. There is no control information in the idoc which message type is RSRQST.
how can i figure this issue out ?could anyone help me ?

HI,ALL
Thanks for your replies and documents.
Now I find the problems lies in the error connection between R/3 and BW. IF the autoconfiguration is completelly correct , the table RSBASIDOC in both system should be added one record.But now when the source system is activated successfully ,the table in R/3 side has no entry while the BW side has one entry .juding from this ,there is no BW system connected to the R/3 ,which is proved when I fill the setup table for LO datasource an error message shows that there's no BW system is connected to the OLTP system.
How can i figure this issue out ?If I want to do an automatic configuration ,what shall I do ?

R/3 connection to BIW - No Idocs arrived from the source system

Question,
Hi Team,
I have issues during loading attribute data from R/3 source system to BI,
I go to the path
Data Warehousing Workbench - Modeling window. In the DataSources view, my application component Group ##. On my DataSource i Create Info Package and save it,
Later I select the following options
Full Update = select
On the Processing tab page, select only PSA.
On the Schedule tab page, choose Start Data Load Immediately and start the data load.
Till here everything is in active version and saved, and connection to the source system is active and working fine.
However when I do loading I received following messages, what I observed in Monitor window,
Data was requested OK
Request still running
Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
No Idocs arrived from the source system.
When I go to detail tab, under transfer section, I receive the following message
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
But when I actually go to PSA maintain section and select data and no of records, I can see the that data is loaded into PSA section,
But when I chose to run the transformation I donu2019t get data here,
Kindly help me to resolve this issue,
Regards,
BluSKy

Hi,
the BIW i am using , its compact BIW, which is in EXI, and i execute transaction /nrsa1 to go biw development workbench,
i am not sure about transactions settings about r/3 side,
could you plz throw some light on this issue,
regards
blusky

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.

Idoc not found in the receiving system

Hi Experts,
In the sending system idoc status is 03 (Data passed to port OK), but in the receiving system the idoc is not there. How to rectify this error?
Thanks & Regards,
Soumya.

Hi Soumya,
Check the RFC connections, becoz in the sending system once the IDOC is sent the status becomes 03 it does not check whether the IDOC has sent to the received system, if there are any errors before sending the IDOC it will not send and the status will be 01, so check the RFC connections at sending and receiving systems.......
Reward points if this helps............
Regards,
Ravi G

No Idocs arrived from the source system.

Dear All,
Please read this issue carefully.
Error Message is that
"No Idocs arrived from the source system."
In the Details Tab:
Trasnfer( IDOCS &TRFC):Missing Messages or warinings.
Request IDOC:Application Documnet posted from BW side and it is green..There is a request BW IDOC number sent to R3.
Where as an InfoIdocs 1:Sent not arrived :Data passes to the Port is ok.
Here i can see there is one idoc frm OLTP R3 side ansd no incomming idoc for BW side
I went to r3 side bd87 and found that idoc is posted well with status 53.
This is happing in Bw for each iinfopcakage is running?

Hi,
go through this link...
[https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=noidocsarrivedfromsource+system&adv=false&sortby=cm_rnd_rankvalue]
System.-> Check RFC connection and clear/process stuck IDOCs.
Idocs Missing or No Idocs arrived from source
For this check the TRFC que(SM58).If any Idocs r strucked up there execute them manually.checkin sm58 transactions, you can check the status of your Idocs using BD87 in R/3. Idocs may not be processed because of load on system. You can process them manually from context menu.
And go to BD87 to process the idoc's ..
check which idoc has to process...select the idoc and click process ..Then It will push the data into the data targtes,
Hope it will help you;
regards,
NR

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

Similar Messages

Maybe you are looking for