IDOC Listener for 12.1 to ECC 6.0 is now available

[IDoc Listener|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a02bc706-15f2-2c10-1aab-a1927ada11f0]
The ECC 6.0 side is virtually unchanged, but there were significant changes in NW and MII.
Enjoy! Or let me know if there are any areas that need improvement or clarification.
Thanks,
Mike

Hi,
There are no standard timeliness for the upgrade project. It depends upon number of factors like number of background processes, no of R3trans processes defined in configuration phase, Memory parameters etc. So, it is really difficult to give you an estimate for this. Best option is do the test upgrade, so that you will get an idea how much time it will take.
Also, If you want to migrate your existing system to new hardware then I would suggest you to install your system as unicode system on new hardware as a result you can save a lot of time because of unicode conversion in CUUC.
Thanks
Sunny

Similar Messages

IDOC type for interface between SAP ECC and SAP F&R

Hi Experts,
I need SAP standatd IDOC type for interfacing between SAP ECC and SAP F&R [SAP Forecasting and Replenishment] using message type u201CFRE_LOC_SITEu201D.
Please help me in finding the idoc type?
Regards,
Krishan

Hi Denish,
You have 2 ways of loading data from R/3 to APO.
1. R/3 to BW cube to APO-BW cube to APO planning area
or
2. R/3 to APO-BW cube to APO planning area
BW can be a enterprise BW system ( independent) or you can use the BW inbuilt in APO also referred to as APO-BW.
The only difference between the 2 BW systems is APO-BW can not take the load of reporting where as the enterprise BW can.
Unless your company policy requires the enterprie BW system, I suggest using 2nd way.
You can load the data from R/3 to APO-BW cube using extractors either generic or standard depending on your data. You need to have a RFC connection setup between APO-BW and R/3. ( This is not CIF).
When you load the data into the APO-BW cube, you just have to load the data from the cube to APO planning area using the transaction /sapapo/tscube.
Refer to [DP Data Mart|http://help.sap.com/saphelp_scm50/helpdata/en/13/5ada58309111d398250000e8a49608/frameset.htm] for more information about the data transfer between APO-BW and APO.

Crystal Reports for Eclipse 2.0 - Service Pack 1 - is Now Available!

Service Pack 1 for Crystal Reports for Eclipse 2.0 is now available!
Readme file listing the fixes is here:
[http://downloads.businessobjects.com/akdlm/crystalreportsforeclipse/2_0/cr4ev2_readme.pdf]
Kirby Leong in another post listed the download URLs, which I'll copy here:
CR4E Runtime Package
[http://downloads.businessobjects.com/akdlm/crystalreportsforeclipse/2_0/crjava-runtime_12.2.202.zip]
CR4E Manual Install Package
[http://downloads.businessobjects.com/akdlm/crystalreportsforeclipse/2_0/cr4e_2.0.1.zip]
CR4E All-In-One Package
[http://downloads.businessobjects.com/akdlm/crystalreportsforeclipse/2_0/cr4e-all-in-one-win_2.0.1.zip]
CR4E Language Packs
[http://downloads.businessobjects.com/akdlm/crystalreportsforeclipse/2_0/cr4e.nls1_2.0.1.zip]
[http://downloads.businessobjects.com/akdlm/crystalreportsforeclipse/2_0/cr4e.nls2_2.0.1.zip]
If you wish to use the Eclipse IDE Software Updater:
1. Start Eclipse 3.4.1 (Gemini) IDE.
2. Select Help -> Software Updates...
3. Select the "Available Software" tab.
4. Click the "Manage Sites..." button.
5. If you do not see the following URL listed:
http://downloads.businessobjects.com/akdlm/crystalreportsforeclipse/2_0/update_site/
    then click "Add..." and add it.
6. Select the above URL in the "Available Software Sites", then click "OK".
7. The Available Software should now list the above URL. Open the node, and you should see "Crystal Reports for Eclipse".
8. Check all checkboxes for "Crystal Reports for Eclipse", and "Install..."
After successful update, you'll see version 2.0.1 listed in Help -> About Eclipse SDK and clicking on the "Crystal Reports for Eclipse" icon (blue swoosh with green diamond).
If you don't see that version listed, here's some troubleshooting tips:
Open a web browser, and Go to the following URL:
http://downloads.businessobjects.com/akdlm/crystalreportsforeclipse/2_0/update_site/site.xml
You should get back a XML file listed the current CR4E plugin and language packs versions. If you get an error instead, it may be because (1) you're in a locked down environment that won't let you access that site, or (2) the CR4E Update Site may be down for maintenance.   If the former, you'll have to download the updates by some other means and upgrade manually.

hello ....
my report is ''crystal report 11'' => "OLE DB" => "Add Command(select * from table) " .
code(JRC) : eclipse + crystal report for eclipse version 2 => "cr4e-all-in-one-win_2.0.1.zip"
<%@ page contentType="text/html; charset=UTF-8"
import="
com.crystaldecisions.report.web.viewer.CrystalReportViewer,
com.crystaldecisions.reports.sdk.ReportClientDocument,
com.crystaldecisions.sdk.occa.report.lib.ReportSDKExceptionBase,
java.sql.Connection,
java.sql.DriverManager,
java.sql.ResultSet,
java.sql.SQLException,
java.sql.Statement" %>
<%
try {
     String reportName = "report.rpt";
     ReportClientDocument clientDoc = new ReportClientDocument();
     clientDoc.open(reportName, 0);
     String tableAlias = "Command";
     clientDoc.getDatabaseController().setDataSource(
               myResult("SELECT * FROM table"),
               tableAlias,"resultsetTable");
     CrystalReportViewer crystalReportPageViewer = new CrystalReportViewer();
     crystalReportPageViewer.setReportSource(clientDoc.getReportSource());
     crystalReportPageViewer.processHttpRequest(
               request,
               response,
               application,
               null);
} catch (ReportSDKExceptionBase e) {
     e.printStackTrace();
    out.println(e);
%>
I simplified the code, *myResult("SELECT * FROM table") * is absolutely no problem ,
and this code is absolutely no problem in the "crystal report for eclipse "version 1
but in version 2 run error:
com.crystaldecisions.sdk.occa.report.lib.ReportSDKException: 無法預期的資料庫連線器錯誤---- Error code:-2147467259 Error code name:failed
Please help me and tell me why....

Configuring IDOC Listener on MII 12.1

Hi,
I had a basic question around the configuration.
This is from 12.1 help:
"The SAP Java Resource Adapter (SAP JRA) server is used to connect to SAP ERP Central Component (SAP ECC) to receive remote function calls (RFC) and IDocs. You can use the asynchronous HTTP interface to post data to SAP MII for asynchronous transaction processing."
In this regard is it mandatory to first configure SAP JRA on NW and then proceed with the IDOC specific config both on the R/3 as well as NW side?
The reason I ask this is that we are currently struggling with this config on 12.1.8 (build 30) where the BASIS folks are observing that the system hangs when they try to add enteries to the XMIIIDOC component . Before going through with the IDOC config they made sure that the JRA is configured and followed the steps as mentioned in the 12.1 installation guide under "Configuring JRA for JRA Actions" & "Cloning the default JRA Config" sections.They are simultaneously also following up in the NW forums to find a solution.
Additionally I had another question (this one's specifically for MIke Appleby ). Would one have to follow similar config steps as IDOC when configuring the RFC listener , atleast from the NW CE perspective? We are trying to download Control Recipes from R/3.
Thanks
Udayan

Hi Udayan,
Yes, the configuration for the RFC Listener is essentially the same as the IDoc Listener, except the binding is different (do not change either type from the default values and you should be fine).
The differences between the two Listener types are really on the ECC side. The installation instructions for Batch Manufacturing included the RFC Listener setup. Keep meaning to write a separate document for RFC Listeners, but haven't yet.
One general note of caution for all readers:
Do not reuse ProgIDs from an IDoc Listener in an RFC Listener and vice versa. Only use a unique ProgID once (and deleting them from one Listener or MII server to use them elsewhere is generally not advisable).
Roughly 90% of the tickets entered for IDoc Listeners with MII are because of ProgIDs used in more than one place.
Regards,
Mike

Updated IDoc Listener document

Hi All,
There is a new document for building an IDoc listener using MII 12.0 and ECC 6.0. This will hopefully reduce confusion for those using the documents meant for use with xMII 11.5 and ERP R/3. Please let me or Diana Hoppe know your comments and suggestions.
Since there are so many different ALE configurations possible, we know that we can't address them all. Nor was that our intention. We wanted to provide a template and reasonable starting point for building a simple Listener. If our simple model does not work, you may need to bring an ALE expert into the picture. We hope that it proves useful to some of you out there.
[New IDoc Listener Instructions|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
Thanks,
Mike & Diana

Thanks.

BCExeption: The IDOC metadata for null is not available in SID

<h3>Hello Guys,</h3>
we need some information about the error message:
com.wm.pkg.sap.BCExeption: The IDOC metadata for null is not available in <SID>
We use a Business Connector 4.8 and the backend is an ECC 6.0, we have an inbound xml scenario with FTP.
We pick up the ORDRSP from the vendors ftp-server and we would like to drop it to our backend system.
We can read the xml file into a string, but not send to the backend system, we use following steps:
- bytesToString
- stringToDocument
- documentToRecord
- recordToIDOC
- lockSession
- createTID
so far works perfekt
- sendIDoc
- releaseSession
On the step "sendIDoc" we see the described error message, but what is the message from the message?
Any Ideas?
Thank you and regards,
Michael

Hello Michal,
thank you for your quick answer!
In my opinion, i don't need any input for this service, because we pick up all data from the vendors ftp - server in a definied time interval.
All needed fields are available in the xml file. In the result tab is the IDocList filled correct, but no sending to the backend system because the error is displayed.
Is it a problem with my concept?
Regards,
Michael

RSAR2318 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Error RSAR238 : IDoc type for source system T90CLNT090 is not available
I have already checked trx & dtps, but could not find resolution.
Kindly help me with this error.
Thanks and regards,
MS

M Sharma wrote:
But how exactly can I create when T90CLNT is not active? Help please.
Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

RSAR238 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Kindly help me with this error.
Thanks and regards,
Dhanapal

Hi,
Check the same in SDN..
Object ZDUMMY could not be activatedMessage no. R7I028
Re: DSO Activation problem
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
Thanks
Reddy

IDOC structure for HRMD_A07

Dear All,
We want to create IDOC HRMD_A07 through SAP PI in ECC to create employee.
Please guide how we can get the output structure like
e1plogi
e1pityp
e1p0000
e1pityp
e1p0001
e1pityp
e1p0002
Whereas the standard IDOC structure is like as follows:
e1plogi
e1pityp
e1p0000
e1p0001
e1p0002
Reg,
NJ

Well, u can still create IDoc with the required structure. Thre is a test tool (tcode WE19) where u can create and populte the segments as u want for testing. Use the 'Create' button and place it in proper hierarchy.

IDOC Listener not calling BLS Transaction

All,
I am running xmii 11.5.4. I have a single IDOC Listener configured with a Routing Rule for Message Type = "PROCESS_MESS_DOWNLOAD". The Routing Rule is defined to trigger a BLS called "TEST_BLS". The Listener is configured with the BLS Input Parameter.
The Listener processes the incoming message by writing the XML file to the defined Path with no problems.
The issue is the BLS Transaction will not trigger. The Transaction has a single Transaction Property of data type XML with no default value defined.
I have tried using a simple Transaction with nothing but an Event Logger or XML Trace actions to verify the Transaction is being executed. But nothing occurs.
I have viewed the General Log and see no errors or warnings or fatal log entries.
The Transaction works fine manually from inside Logic Editor and even runs from a URL invokation.
Any ideas of what to look for or try would be greatly appreciated.
Thanks,
Chuck

Udayan,
The Transaction consists of only an Event Logger Action and an XML Tracer Action. Neither of these are apparently executing. No event is logged and no entry is made to the XML Tracer file. The Transaction has a Transaction Property defined as stated in my first post.
I have noticed through trial and error that the IDOC Listener only works with the asterick message type. The actual message type of the IDOC is evidently not being read by the Listener. The IDOC being created is coming from a PPPI Process Message. The first few lines are:
<?xml version="1.0" encoding="UTF-8"?>
<PROCESS_MESS_DOWNLOAD>
<INPUT>
<CLIENT>200</CLIENT>
</INPUT>
<TABLES>
<MSEL>
<item>
<MSID>100000000000000537</MSID>
Thanks,
Chuck

Where can I find IDOC Listener (xMII 12.05) .It is not in DataServices.

Hi all,
I can not find IDOC Listener in Data Services in xMII version 12.05.
Where can I find the IDOC Listener? Must I set up it first? Or must I do some configurations for IDOC Listener?
Thanks.

Cemil,
in MII 12.0.x you will find the Listener under Message Services -> Message Listener.
If you need to run a transaction after receiving a IDOC, than you need also to configure
a Rule under Message Services -> Processing Rule Editor.
Under the link below you will find the Documentation for Message Services:
http://wbhelp.sap.com/manufacturing/xmii_120/en/45/aa5d17b8f52e78e10000000a155369/frameset.htm
Regards
Pedro

Remotely shutting down the idoc listener

This is onorthodox, and the reason for it is too long to type here. But is there a way to turn off an idoc listener through a URL that I could run in BLS?
Doesn't matter if its recommended or supported. I'm just curioius. I'll do it at my own risk

No there is no service type URL available for this. The only option is via the Message Listener screen currently. That said....
You could attempt to post directly to the admin page handler, simulating a call from the JSP page. That would be your only option. I really don't recommend it since it could be broken by any service pack.

Idoc number from sales order in ECC

Hi,
Sales order is created by processing an Idoc. Now i want to trace back the idoc number for the sales order created.
Please let me how we can do this in ECC. I saw couple of posts stating ICON SERVICE FOR OBJECTS...i couldn't really identify that icon. In someother post i saw this can found under Environment.
Please let me know whether there are any prerequisites for this, and how i can i achieve this in ECC?
Thank You in Advacne
Thank You
Challa

Hi Challa,
To find which idoc created the sales order, you can do the following,
Check for the customer PO no in the sales order.
Then go to any other inbound idoc which is bound to create a sales order, and see in which segment is the PO number.
Then go to WE09 and put the dates etc and then go to " Criteria for search in Data Records"
Put the segement no in Search in segement field.
Put the idoc field in which you see the PO number
and put the PO no in the " for Value" field and execute.
You will get the idoc which created the sales order.
Let us know.
Regards,
SB

MII 12.1 and IDoc listener

Hi.
I have been trying to setup an idoc listener in MII 12.1, but can not figure out where in NWA to do this an how.
Have anyone tried that? The help file might not be updated on this point.
BR
Poul.

Hi.
Thanks, I have found this location but could not se anything happening. To start with i missed the parameter setting MaxReaderThreadCount and needed to restart the listener.
Now I get something in the log but my username and password is not working..
Thanks a lot for this
BR.
Poul.

1 request Idocs created for message type MATMAS

Hi Experts
I have done necessary config.
I have attempted BD10 and BD11.
I have got message that "1 request Idocs created for message type MATMAS"
But iam unable to find the material in target system.
Please suggest what need to be done.
regards
ramSiva

Marias,
And in PI, after having changed the password (why not), have you unlock this user account ? in SU01 of PI, you have a lock button.
if you did it, and changed also the password, as explained, you have perhaps another (or several) program like a RFC destination which uses another password, and so after some exchanges... with a bad/old password, you have your message "too many...", and then the user is again locked...
If you change the password in PI, you should change it in all application which uses this user. I hope you have not the same user from ECC to PI, than from a third-party to PI...
that's why: the use of such technical users have to be referenced in a doc. By this way, if password has to modifiy, we know where we have to update it (mainly in different RFC destination).
Mickael
Edited by: Mickael Huchet on Dec 5, 2011 5:33 PM

IDOC Listener for 12.1 to ECC 6.0 is now available

Similar Messages

Maybe you are looking for