Replacing SAP BC by SAP XI

Hi All,
we try to replace a SAP Business Connector installation by a SAP XI 2.0 installation.
We currently exchange IDOCs via SAP BC over http(s) with our suppliers. If we substitute SAP BC by SAP XI we don't want our suppliers to be affected. So the http(s) post from XI should be identical to the SAP BC http post.
Unfortunately the two posts differ on header fields and parameter passing like the following example shows.
SAP BC post:
 POST /LieferantB HTTP/1.0
User-Agent: Mozilla/4.0 [en] (WinNT; I)
Accept: image/gif, /
Host: fs6509.hannover.is-energy.de:8891
Content-type: application/x-sap.idoc
X-tid: 0A108469607640D99CD00535
Content-Length: 14248
SAP XI post:
 POST /LieferantB?msgguid=40D77B9EF194003602000000C0A8BD3F&bs=ISE_BS_Auftraggeber_ise&namespace=urn%3ais-energy%2ede%2fbestellwesen&interface=ORDERS%2eORDERS02&qos=EO HTTP/1.0
content-type: application/x-sap.idoc
content-length: 4743
connection: close
accept: /
user-agent: SAP Web Application Server (1.0;620)
host: fs6509.hannover.is-energy.de:8891
accept-encoding: gzip
So how may I get rid of the ?msguid=...?bs=... stuff?
And what's about the X-tid of the SAP BC post?
Any hints even links to documentation are welcome!
Regards
Marc

Hi,
>>>>Can i use SAP BC adapter in my XI and use everything that is being used in SAP Business connector
Answer is no. But for BC to XI migration there is lots of documents available. I also posted some of them in your earlier posts for same issues.
Can you please close that thread and opn only one thread for one subject.Also mark that thread answered.
Please refer your unanswered link.
Re: Migration from SAP BC To SAP P.I?
Regards
Aashish Sinha
PS : reward points if helpful

Similar Messages

Data (Master Data Changes and Transaction Data) from SAP BW to SAP BPC 5.1

Hi guys
I have seen posts on this forum describing data transfers from SAP R/3 to SAP BPC. I assume the procedure for data transfers from SAP BW to SAP BPC 5.1 should be the same i.e. using SSIS packages.
However I have some unique requirements -
1. DATA AT DIFFERENT AGGREGATED LEVELS - I need data from SAP BW at different levels - Some data comes at Product level while other at Customer level and some at Project Level. The current procedure takes BW queries output in excel sheets (6 files) and then use the data manager package to load the data in SAP BPC 5.1 using appropriate transformation and conversion files. This procedure is highly manual and I am looking at using SSIS package to do this. However, because of having data at different levels, it becomes a little tricky. How can we achieve this using SSIS?
2. UPDATING MASTER DATA - I need to update the master data (dimension members) in SAP BPC 5.1 at the start of every month. The current procedure compares (in MS ACCESS) the data from the queries mentioned in 1 to the dimension members in SAP BPC 5.1 and spits a file with the new entries which needs to be manually updated in the appropriate dimensions using Admin Console. I am looking at automating this task. I cannot just replace all the contents of a dimension with the members coming from SAP BW since the dimension members contains some dummy members which are used for planning.
3. HIERARCHY CHANGES - What is the best way to capture the hierarchy changes in SAP BW into SAP BPC 5.1?
Please advise.
Thanks,
Ameya Kulkarni

Hi Ameya,
how did you solve the described problems? Can you give some hints about uploading master data and updating the hierarchy?
BR, André

Technical differences between SAP Enterprise and SAP ECC 6.0

Hi,
Can anyone plz tell me what will change technically after the upgrade from SAP Enterprise to SAP ECC 6.0, in respect to reports, module pool programming and other technical logics?
Thx,
KK

Difference b/t ABAP4.7 and ECC6.0.
Difference between R/3 4.7, ECC5 & ECC6 anyone?
http://help.sap.com/saphelp_nw2004s/helpdata/en/5b/8c3842bb58f83ae10000000a1550b0/frameset.htm
http://service.sap.com/releasenotes
/people/thomas.jung3/blog/2005/05/15/abap-46c-to-640-delta-training
Re: R/3 Enterprise v mySAP ERP 2003 v ECC 5.0 v mySAP ERP 2004
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000497320&_SCENARIO=01100035870000000112&_OBJECT=011000358700000810532004E
http://help.sap.com/saphelp_nw2004s/helpdata/en/5b/8c3842bb58f83ae10000000a1550b0/frameset.htm
http://service.sap.com/releasenotes
See this weblog:
/people/thomas.jung3/blog/2005/05/15/abap-46c-to-640-delta-training
Re: R/3 Enterprise v mySAP ERP 2003 v ECC 5.0 v mySAP ERP 2004
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000497320&_SCENARIO=01100035870000000112&_OBJECT=011000358700000810532004E
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
A similar post
/message/1783778#1783778 [original link is broken]
You can go through the Release Notes for each of the versions after 4.6B (4.6C, 4.7 , ECC 5.0 & ECC 6.0)
http://help.sap.com/saphelp_erp2005/helpdata/en/43/688055b88f297ee10000000a422035/content.htm
For 4.7 SAP R/3 http://help.sap.com/saphelp_47x200/helpdata/en/12/9d78d6d8f74043a32e82be87e433b7/content.htm
Release Notes on SAP Web Application Server 6.30
http://help.sap.com/saphelp_47x200/helpdata/en/2b/64fc3e9d3b6927e10000000a114084/content.htm
http://solutionbrowser.erp.sap.fmpmedia.com/
http://solutionbrowser.erp.sap.fmpmedia.com/
http://service.sap.com/instguides
http://service.sap.com/erp
http://www.stonewayinc.com/clients/sap/bestoftour/presentations/SAP_BOT_2_Furlan_IBM.ppt
From the ABAP perspective, few differences are.
The WS_* function modules used in 4.6c has become obsolete from 4.7C. All the WS_* FMs have been replaced by GUI_* FMs.
(ii) Concept of Unicode is introduced.
(iii) Few tables have been modified in ECC6.0.
Tables TVARV & TTREX have been replaced by TVARVC & TTREXN respectively.
(iv) we have enhancement points and enhancement sections along with enhancemnts and BADI'S . and we can write the part of code in those points.
For functional differences please check out the following link:
http://solutionbrowser.erp.sap.fmpmedia.com/
ECC->enterprise central component.ECC 6.0 is the advanced version.if we consider in technical point of view then i can give u one example.
In the new version we have enhancement points and enhancement sections along with enhancemnts and BADI'S.SAP has provided these ,so that without going for access keys we can write our code in the enhancement points along with Standard SAP code.So now SAP has provided more user friendly environment.Also a new DEBUGGER also arrived with the new version.Now we can see more things in the new er version of DEBUGGER.
Reward points for useful Answers
Thanks
Murali Poli

Migration from SAP BC To SAP P.I

HI Experts ,
I am required to do migration from SAP BC to SAP P.I. I would require the following Info/Help from you as i have not worked on such scenario before this!
1) What kind of challenges can be faced during migration from BC to XI?
2) What is the best practise for doing the same?
3) Can you share some scenario from where i can have some idea how to do migration?
4) Generally how much time it takes in migration activity if ther are not much interfaces involved in it?
Would appreciate your valuable inputs on the same!
I have read How to guide docs on how to do migration from BC to XI but not convinced with the content
Regards
Saras Jain

Hi Saras,
I am giving you an example senario and a how to do all the steps and why it needed. if you need more information just mail me i'll give you the concerned PDF.
Scenario
SAP Business Connector enables data exchange between an SAP system and
external systems using HTTP and e-mail. SAP Exchange Infrastructure (SAP XI)
replaces SAP Business Connector (SAP BC).
We distinguish between standard scenarios (that do not contain customer-specific
development) and individual scenarios (that do contain services or mappings created
by the customer). The following sections describe how to migrate both types of
scenarios to SAP XI.
Scenario 1 (IDoc HTTP, HTTP IDoc)
An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
XML. It is sent to an external business partner by using HTTP.
An external business partner sends an XML document by using HTTP to SAP BC or
to SAP XI. The document is converted to an IDoc and sent to a connected SAP
system in the internal system landscape.
Scenario 2 (IDoc Mail, Mail IDoc)
An SAP system sends an IDoc to SAP BC or to SAP XI. The IDoc is converted to
XML. It is sent to an external business partner as an e-mail.
An external business partner sends an e-mail to SAP BC or to SAP XI. The
document is converted to an IDoc and sent to a connected SAP system in the
internal system landscape.
Flow Services
Flow services are services that are written in the proprietary graphical-based flow
language of SAP BC.
Java Services
Java services are services that are written in the Java language.
There are several platforms that support Java, including SAP XI. However, the data
model used in the Java services in SAP BC is proprietary.
Stylesheet Transformations
Stylesheet transformations are often used for mapping purposes. They take an XML
document as input, convert it according to rules defined in the stylesheet, which is
also an XML document, and produce an XML document as output.
The XML Stylesheet Transformation Language (XSLT) was defined by W3C (World
Wide Web Consortium), the consortium that defines most of the common standards in modern internet communication, such as HTML and SOAP.
SAP NetWeaver is the open integration and application platform from SAP. With
NetWeaver 04, there is a significant overlap between the functions of SAP
NetWeaver and SAP BC. Many functions provided by SAP BC are offered by SAP XI
as part of SAP NetWeaver, for example, conversion of an IDoc to an XML message,
mapping, routing, and adapters to connect to a large number of third-party back-end
systems. SAP BC is therefore no longer needed. New or updated SAP solutions are
based on SAP NetWeaver. Customers looking for a strategic integration solution for
the complete application landscape should therefore now favor SAP NetWeaver.
The last version of SAP BC was SAP BC 4.7, which was released in June 2003. SAP
BC has not been developed further since this release. SAP BC is not released for
any further platforms (such as Windows 2003) and does not support any further JDK
versions, including the current version (Version 1.4).
For information about the supported SAP BC versions, JDKs, and operating systems,
see SAP Note 309834. For information about the support and maintenance strategy
for SAP BC, see SAP Note 571530. Customers who still use SAP BC need to be
aware of the following:
A solution based on SAP BC cannot be a strategic, long-term solution.
A solution based on SAP BC is based on technology that was implemented in
2003 and that is no longer further developed.
SAP BC is supported on limited platforms and for limited JDKs only. Vendor
support for some of these platforms and JDK versions will soon be
discontinued.
SAP BC and SAP NetWeaver are based on different technologies: SAP BC is based
on webMethods proprietary Integration Server, whereas SAP NetWeaver is based
on open standards, such as BPEL4WS (business process execution language for
web services). Therefore, only parts of an SAP BC implementation, such as XSLT
mappings, can be migrated to a solution based on SAP NetWeaver. Any custom
programming based on SAP BC, such as SAP BC flow language, is unlikely to be
reusable in the SAP NetWeaver context.
Purpose of this Migration Guide
The purpose of this migration guide is to provide scenario-based descriptions of the
migration from a companys system landscape that uses SAP BC to exchange
documents with business partners, to a system landscape that uses SAP XI instead.
This migration guide outlines, for certain scenarios, the individual steps a company
has to take to replace an existing SAP BC implementation with SAP XI.
The basic steps in the back-end systems are:
Defining the logical systems
Maintaining the ALE distribution model
Maintaining partner profiles and EDI ports
Maintaining RFC destinations
The basic steps in the SAP XI system are:
Maintaining the System Landscape Directory
Configuring the IDoc adapter
Maintaining the receiver determinations, interface determinations, and
interface agreements
Maintaining the communication channels
The type of scenario to migrate typically has an impact on the communication channels only.
Scenario 1 IDoc/HTTP
IDoc HTTP Using SAP BC
Within the system landscape of a company, an SAP system sends an IDoc
asynchronously to SAP BC. SAP BC converts the IDoc into a standard IDoc XML
document. The fields of the IDoc are not modified, that is, the conversion does not
involve any mapping of source fields to target fields. After conversion, SAP BC uses
HTTP to send the XML document synchronously to an external URL of a business
partner.
System Landscape
An SAP system and SAP BC are installed within the same system landscape
of a company.
The following information is defined in the SAP system to allow data
exchange between the SAP system and SAP BC:
o An RFC destination and a logical system for SAP BC
o The distribution model is maintained, if necessary
The following information is defined in SAP BC:
o An SAP server with an alias is defined. For this SAP server, the
information that the SAP BC requires to connect to the SAP system is
specified.
o A listener is configured to listen to requests from the SAP system.
o A routing rule with the transport type XML is configured for the
specific sender, receiver, and message type. The routing rule
determines how a message is to be routed and where it is to be routed
to. The scenario described does not use an ACL, (Access Control List
to restrict execution permissions for this routing rule) or pre-processing
or post-processing SAP BC services.
4.2 IDoc HTTP Using SAP XI
Check the prerequisites described above under Prerequisites for Standard
Scenarios.
The IDoc adapter is used to receive an IDoc from an SAP back-end system and
convert it to XML.
The adapter used to post this XML to an external destination is the plain HTTP
adapter.
To set up the communication channel, perform the following steps:
1. Locate the routing rule in SAP
Business Connector.
In the Administration View, choose
Adapters Routing to navigate to
Routing Rules.
2. Select the details of the relevant routing rule.
To display the details, choose the green triangle (Edit).
Transport is typically set to XML and a URL is specified. You can use this
URL in your SAP XI settings.In some cases, Transport is set to
B2B Service and the parameters Server Alias, Folder and Service
exist. This is the same as when Transport is set to XML and has the
URL http://<serverhost>:<port>/invoke/<folder>/<service>.
You can find <serverhost> and<port> in the definition of the
remote server under Settings >Remote Server in the Administration
View.
3. Set up the communication channel in the Integration Directory using the parameters from the SAP BC routing rule.
Use the following settings:
Adapter Type: HTTP Receiver
Transport Protocol: HTTP 1.0
Message Protocol: XI Payload in HTTP Body
Adapter Engine: Integration Server
Addressing Type: URL Address
Target Host, Service Number,and Path need to be set in accordance with the SAP BC routing rule. HTTP Proxy Host and HTTP Proxy
Port can be set if required.All other parameters have no corresponding values in SAP BC and should be set to their default values.
regards
Aashish Sinha
P : Reward points if helpful

Sap bc or sap xi

Are there any documents out there that can help in decide why should one replace SAP BC with SAP XI?
Also any doc on BC vs XI?
Thanks,
Bhaskar

Bhaskar
If you go through the below given video presentation you can understand why you should replace your Business Connector to XI.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/f834c3ad-0701-0010-9f92-92c60207fd6a
---Satish

Differnce between SAP-XI and SAP PI

hi can any body tell me what is the differnce between SAP-XI and SAP-PI

Hi vijay,
u can get lot of information regarding PI and XI in sdn.There already exists a no. of thread.just search with keyword "XI 3.0 and PI 7.0" u can get a lot.
XI 3.0
1. J2Se adapter engine was replaced with J2EE Adapter Engine.
2. BPM was available from XI 3.0
3. Part of Netweaver 2004
PI 7.0
1XI renames as Process Integration
2.. Part of Netweaver 2004s.
3. Has all features of XI 3.0 and every SP of Pi 7.0 has a corresponding release for XI 3.0.
4. Runs on WAS 7.0 and has same features as XI 3,0
From functional point, there is no difference between XI3.0 and PI7.0. There are changes only wrt SP. For every SP release on PI7.0 a corresponding SP for XI3.0 is also released.
A comparision of the service packs in 2004 and 2004s;
in 2004 - in 2004s
SP12 & < - SP04
SP13 + 14 - SP05
SP15 - SP06
SP16 - SP07
SP17 - SP08
SP18 - SP09
For release notes
ref:http://help.sap.com/saphelp_nw04/helpdata/en/cf/9844428e9cbe30e10000000a155106/frameset.htm
There is no f'nal difference between XI 3.0 and PI 7.0. In order to bring all netweaver releases on par with each other , SAP released / renamed XI as PI and it is a part of NW04s
For every release of PI 7.0, there is a parallel Support Pack on XI.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/706005a3-3bd6-2910-91ae-a2016239bdcf">SAP NetWeaver Process Integration 7.1 Overview of New Capabilities</a>
Also check these threads.
Difference between NetWeaver 2004 and NetWeaver 7.0 or 7.1
All the diff between XI 3.0 and PI 7.0
differences between xi 3.0 and pi 7.0
Difference/ changes from XI 3.0 to PI 7.0
regards
Bill

SAP BEx + SAP BO or SAP AA + SAP BO

Hi Everyone
I have gone through a lot many articles on Advanced Analysis available on the Internet but the doubt still remains:
-Is SAP Advanced Analysis capable of replacing SAP BEx Analyzer and BEx Query Designer?
-Is there a separate license fee for SAP Advanced Analysis?
We need to zero-in on the selection of the best tool for the reporting and hence very confused between the selection from SAP BEx + SAP BO or SAP AA(Advanced Analysis) + SAPBO?
SAP AA and SAP BO
- All the complex logic can be processed using SAP Advanced Analysis and user interface will be Business Objects Layer
- Ability to talk to disparate systems in single report
- Add-in available for Microsoft PowerPoint 2007 too
- It is a new product and hence it will take time for people to understand and implement it
- Skill set is scarce
- No successful Case Studies verifying the potential of the tool
- It features into the future roadmap of SAP and hence SAP support will be available for the long term
On the other hand
SAP BEx and SAP BO
- No additional license for SAP BEx as it comes with NetWeaver Stack
- All the complex logic can be processed using Business Explorer and user interface will be Business Objects Layer
- SAP BEx has matured over years and the likelihood of show stopper bugs is less
- Skill set is easily available
- Successful Case Studies verifying the potential of the tool
- The support from SAP will continue for next few years
- It no more appears into the future roadmap of SAP
Please suggest !!
Regards
Gajendra

We still have to use both tools - BEx analyzer and Advanced Analysis.
Some of our users need the same query fed into the excel file many times, but with different years.
Ex. (profit for 2005, 2006, 2007, etc...)
I could not achieve this with AA - however, it works well with Analyzer.
I beleive performance is better with Analyzer, but Advanced analysis is more user friendly/intuitive.
Our strategy is to use both tools on a case by case basis.
Thanks,
Matt

Open HUB ( SAP BW ) to SAP HANA through DB Connection data loading , Delete data from table option is not working Please help any one from this forum

Issue:
I have SAP BW system and SAP HANA System
SAP BW to SAP HANA connecting through a DB Connection (named HANA)
Whenever I created any Open Hub as Destination like DB Table with the help of DB Connection, table will be created at HANA Schema level ( L_F50800_D )
Executed the Open Hub service without checking DELETING Data from table option
Data loaded with 16 Records from BW to HANA same
Second time again executed from BW to HANA now 32 records came ( it is going to append )
Executed the Open Hub service with checking DELETING Data from table option
Now am getting short Dump DBIF_RSQL_TABLE_KNOWN getting
If checking in SAP BW system tio SAP BW system it is working fine ..
will this option supports through DB Connection or not ?
Please follow the attachemnet along with this discussion and help me to resolve how ?
From
Santhosh Kumar

Hi Ramanjaneyulu ,
First of all thanks for the reply ,
Here the issue is At OH level ( Definition Level - DESTINATION TAB and FIELD DEFINITION )
in that there is check box i have selected already that is what my issue even though selected also
not performing the deletion from target level .
SAP BW - to SAP HANA via DBC connection
1. first time from BW suppose 16 records - Dtp Executed -loaded up to HANA - 16 same
2. second time again executed from BW - now hana side appaended means 16+16 = 32
3. so that i used to select the check box at OH level like Deleting data from table
4. Now excuted the DTP it throws an Short Dump - DBIF_RSQL_TABLE_KNOWN
Now please tell me how to resolve this ? will this option is applicable for HANA mean to say like , deleting data from table option ...
Thanks
Santhosh Kumar

Log On problem via webgui. sap/bc/gui/sap/its/webgui

Hello, would you be so kind to help me in my problem.
I have sap web as 7.00, and i have published a service for using "sap gui for html" via browser from the Remote Place.
http://........./sap/bc/gui/sap/its/webgui
icm/server_port_0 i made 80 in the profile
(icm/server_port_0 = PROT=HTTP,PORT=80).
But there is such a problem.
When u try to connect using this url it gives u the log on screen to enter your user/password (u can even change it!!)
but when you try to log on it just refreshes the screen and nothing actually happens.
The same time when you are doing it licaly in the office everything works fine.
Does anybody know what can be the solution of this problem?
Dmitry.

Hi! Привет.
Well i have tried to use this transaction (SIAC_PUBLISH_ALL_INTERNAL) and it published a lot of services, but still i can't log on from home, for example, to the system in our office where ICM and ITS are running.
I found an interesting link
/people/durairaj.athavanraja/blog/2005/08/21/running-your-first-its-webgui-application-in-sap-netweaver-04-abap-edition--nsp
And i tried mannually to publish "SYSTEM" and "SHUFFLER" services. The same time "WEBGUI" service works fine in the office. Those two i also can publish, but i can't start them in SE80.
It is written that
sap/bc/gui/sap/its/system/ call was terminated because the corresponding service is not available. And i can't find such a service following that link... Still it shows that it has been published.
May be it is so because i can't test the service
/default_host/sap/public/bc/its/mimes
The error is
The URL http://.../sap/public/bc/its/mimes was not called due to an error.
Note
The following error text was processed in the system S01 : Illegal access to a string (offset too large)
The error occurred on the application server s00-5000_S01_01 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: SPLIT_PATH_GIVE_ROOT of program CL_IAC_HELPER=================CP
Method: SPLIT_PATH_GIVE_SERVICE of program CL_IAC_HELPER=================CP
Method: GIVE_MIME_CONTENT_USING_PATH of program CL_IAC_HELPER=================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_ITS_MIMES=========CP
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP

Is this possible: SNC connection from SAP GUI to SAP Router, and ...

Hi,
I have (stupid perhaps) question.
Is this scenario possible:
SNC connection from SAP GUI to SAP Router, and non-SNC connection from SAP Router to SAP System.
I know how to set up scenario like this:
SAP System --- (non-SNC conn) --- saprouter1 --- (SNC conn) --- saprouter2 --- (non-SNC conn) --- SAP GUI.
Best regards,
Marek Majchrowski

Wolfgang,
To be sure myself and Marek understand, can you confirm the different scenarios supported:
Scenario 1:
SAP GUI --- (non SNC conn) --- saprouter1 --- (SNC conn) --- saprouter2 --- (non-SNC conn) --- SAP System
With this scenario, it would be possible for a user to logon using SAP GUI onto the SAP System, but without SAP GUI SNC.
Scenario 2:
SAP GUI --- (SNC conn) --- saprouter1 --- (non SNC conn) --- saprouter2 --- (SNC conn) --- SAP System
With this scenario it would be possible to logon to the SAP System using SAP GUI, and using SNC authentication.
Also, with this scenario the SAP GUI software and SAP System software would consider this to be similar to:
SAP GUI -- (SNC conn) -- SAP System
Scenario 3:
This is the scenario mentioned by Marek in his initial question:
SAP GUI -- (SNC conn) -- saprouter1 -- (non SNC conn) -- SAP System
With this scenario it will not be possible to logon to SAP System using SNC, and only possible if the SAP GUI is configured to not use SNC. In other words the SNC connection between SAP GUI and saprouter1 is available, but cannot be used.
Thanks,
Tim
Edited by: Tim Alsop on Feb 25, 2008 5:24 PM

Com.sap.portal.appintegrator.sap doesn't work

Hi all,
I needed to change the file 'WinGuiRenderLayer.properties'
I found the par under 3 locations:
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp
I changed the file in those locations (I removed the bak extension and restarted the server).
Also, I made sure that the pars/directory contains the jar files.
After I restarted the server the application integrator iviews doesn't work (Web Dynpro, Transaction...).
Before I did the changes, I backed up the original pars/directory.
Copying the original pars didn't help.
How can I solve this?
Portal is EP6.16
Attched exception details:
Date : 10/25/2007
Time : 13:56:51:765
Message : [PortalNode.fireEventOnNode.toEventListener] event=onNodeReadyEvent, target=com.company.Orders, operation failed
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
 at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
 at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
 at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
 at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
 at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
 at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
 at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
 ... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
 not registered!
Resources:
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:219)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
 ... 45 more
Severity : Warning
Category : /System/Server
Location : com.sap.portal.portal
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_27
Datasource : 6397450:D:\usr\sap\SPD\JC00\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 000E7F3049DE005C0000002100001C4000043D4FEE02FB46
Source Name : com.sap.portal.portal
Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
 at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
 at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
 at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
 at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
 at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
 at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
 at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
 ... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
 not registered!
Resources:
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:219)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
 ... 45 more
Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
 at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
 at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
 at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
 at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
 at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
 at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
 at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
 at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
 at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
 at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
 at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
 at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
 at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
 at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
 ... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
 not registered!
Resources:
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
 D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:219)
 at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
 ... 45 more
Dsr Component : <Server Name>
Dsr Transaction : 5a4c6ec082f111dccf17000e7f3049de
Dsr User : <User>
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 44
Source : com.sap.portal.portal
ThreadObject : SAPEngine_Application_Thread[impl:3]_27
Transaction :
User : <User>
Thanks,
Omri

Solved it.
This is what I did:
1) Took par from my production environment (same SP level)
2) Clear the par (by using 'Archive Remover')
3) Clear the pcd cache
4) Upload the par (redploy)\
5) Restart the portal
Thanks,
Omri

What is difference between SAP R3 And SAP IS Mills Product

HI Friends
What is difference between SAP R3 And SAP IS Mills Product
What are the futures are availables in IS MIlls
Regards

Hi,
SAP R/3 is the central enterprise version. It is not specifically designed for any inducstry sectors and it can cater many of the industry types.
Is is developed for specific industries an for SMB's (small and medium business). It will have components specifically for the industry.
The SAP Mill Products component adds sector-specific functionality to an ERP system to satisfy the complex requirements of mill industries (e.g. metal, wood, paper, textiles, construction materials, and cable sectors).
These industry segments differ from others primarily in that the materials used have a large number of characteristics and variants. The materials in the segments listed above are also predominantly area-based (e.g. paper, textiles, plastic film) or length-based (e.g. cables, piping). Account must be taken of these material characteristics throughout the entire supply chain.
To cater for the particularities of these industry segments, SAP Mill Products features processes and functions that cover the entire supply-chain cycle from product design and configuration, through planning, order processing, capacity planning and production, to final delivery. Additional functions are available in costing and inventory management. SAP Mill Products are also integrated into Quality Management, Financial Accounting, and Controlling.
Prase

Can We send data from SAP to non SAP using ALE !

In this case what will be the receiver side configuaration !
What will be our receiver client !

Hi,
We can send SAP to Non-SAP system using ALE technology.
Ex:-
Business Connector, VB.NET system can be integrated using ALE technology over TCP/IP connection.
Regards
Vijayanand Poreddy

Is it possiblle to integrate non-sap to non-sap using XI?

hi,
is it possible to integrate non-sap to non-sap system using SAP XI?
ex. File to JDBC scenario
regards
Ruban

Ruban,
Yes you can do it.
In ur same example u know we have File adapter and JDBC adapter, then what else we need :-).
-raj.

How do we Integratet SAP to Non-SAP Using Business Connector

Hi Experts,
I am new to SAP Business Connector !!
and what are the Forms ? for SAP Business Connector Related Postings ??
!! I have a requirement to integrate sap to non-sap with Business Connector !!
We need to Generate the SAP Data In xml Format ? and the Non-sap System can Understand Only XML Formated data.
Is there any way Business Connector Box can Pull the XML file from R/3 Application Server and store the file in the Business Connector Server. from that How do we Sent XML file to Non-sap. How do we Integrate ??
what transaction code will trigger this event ? I mean is ther any SAP Transaction Code to Integrate Business Connector?
For Eg. like in R/3 SD to FICO and MM Integration.
Please Give your Valuable Suggests..
Thanks .
Upender.

Hi,
It is not an issue, It will be a separate project :-).
The right forums for this,
Expert Forums » SAP NetWeaver » Process Integration
www.wmusers.com
Also go through the following links:
http://www.sapgenie.com/interfaces/businessconnector.htm
http://www.sapgenie.com/mysap/bus_connector.htm
/people/bla.suranyi/blog/2006/07/10/xi--sap-business-connector-integration-using-the-http-adapter
http://help.sap.com/saphelp_nw04/helpdata/en/6a/3f93404f673028e10000000a1550b0/frameset.htm
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
https://websmp104.sap-ag.de/connectors
Thanks and Regards,
Chandra Madapati

Replacing SAP BC by SAP XI

Similar Messages

Maybe you are looking for