Running BW on ERP

Hello experts!
Are there any information or experiences of running a SAP BW system on a productiv SAP ERP/ECC system?
Normally I wouldn't recommend this, because I think database and parameters have some different requirements on these both systems. But we have a case were we would try to run a BW on ERP with a small implementation and small amount of data.
Therefore I ask
a) for information or recommendations from SAP to do this
b) for experiences from having this scenario
Thanks in advance,
Peter

Hi Peter, seems you are referring to technology called Multiple Components in One Database (MCOD):
https://service.sap.com/MCOD -> SDN
If so, especially see document [MCOD : Operational areas, Advantages & Limitations|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c00ed7f9-d311-2a10-cdaa-e124e955909c]

Similar Messages

How to get LIS Extraction run on SD/ERP

Hi,
what steps to take to get LIS Extraction run on SD/ERP
for 2LIS_11_VAITM, 2LIS_11_VAHDR, 2LIS_11_VASTI, 2LIS_11_VAKON, 2LIS_11_VASTH ?
ThanXs
Martin

Hi,
take a look at
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50326ace-bac2-2b10-76bb-bd1a20ed2b57

Run a SAP ERP transaction from a BPF

Hi Experts:
We would need to run a SAP ERP transaction from our BPF. Would it be directly possible?
I guess it would be possible by programming a BADI, wouldn't it? Would it be the best option?
Thanks in advance for your help.
Kind regards
Jose

Hi Jose -
You can execute an ERP transaction from a Drill Through command if your EPR system has an ITS (Internet Transaction Server)installed. Please see the following "How To" guide for details:
[How To..Configure Drill Through Functionality |http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10a56b21-04b9-2d10-a6b7-e0f8732b4142]
You cannot directly access the Drill Through from a BPF, you would need to link a report into the BPF then link the Drill Through from the report.
Regards,
Sheldon

Can ESS 2004 with XSS 500 run in an ERP 2005 ladscape with NW2004s

We are trying to plan our upgrade. We are running ERP 2004 ESS. If we upgrade our ERP system to 2005 with Netweaver 2004s J2EE, will the ERP 2004 ESS components still work?

Stephen,
Suggest you have a look at note 1007341 - <i>SAP ERP 2004/2005 supported ESS/MSS system landscapes</i>.
This note gives you all the combinations that are supported by SAP.
Regards,
John

Companies running on SAP (ERP) in India

Can anyone provide me the list of those companies in India.....
Who has already implemented SAP (ERP)
(ii) Who is going to implement SAP soon
Regards,
Surajit Pramanick
Kolkata, West Bengal
XXXXXXXXXXXXXX
Moderator: Thread has been locked due to violation of Rules of Engagement

Hi Everyone ,
Please go through the below URL's to understand the basic overview of SAP GTS module and it's application areas .
SAP GTS Training Day 1 Part 1 by G.V.Rao ( VENKAT ) - YouTube
SAP GTS Training Day 1 Part 2 by G.V.Rao ( VENKAT) - YouTube
SAP GTS Training Day 2 by G.V.Rao ( VENKAT ) - YouTube
If you need any documents in this regard , please let me know I can help you in this regard .
Sri Krishna

SAP E-Commerce for mySAP ERP. Runtime Error on order check-out.

Hi,
Currently I'm running a webshop on ERP commerce (isa). And an error occurs on order check-out when you actually try to create your order online. I've checked my XCM settings several time and configurations are default and active.
In the ECC back-end this process al goes wel with a user and transaction code va01.
(Date formats from the users are consistent).
Any help would be very welcome!? I've seen more trhreads but never a suitable answer for my issue.
Kr,
Jelmer Oenema
The error looks like follows when doing a log and trace:
Full Message Text
A runtime exception occurred on the highest level
[EXCEPTION]
java.lang.NullPointerException
at com.sap.isa.backend.r3.salesdocument.rfc.ReadStrategyR3.setLatestDateFromItemExtensionToAttribute(ReadStrategyR3.java:2601)
at com.sap.isa.backend.r3.salesdocument.rfc.CreateStrategyR3.simulateDocument(CreateStrategyR3.java:359)
at com.sap.isa.backend.r3.salesdocument.OrderR3.simulateInBackend(OrderR3.java:500)
at com.sap.isa.businessobject.order.Order.simulate(Order.java:251)
at com.sap.isa.isacore.action.b2c.order.MaintainBasketB2CBaseAction.createOrder(MaintainBasketB2CBaseAction.java:568)
at com.sap.isa.isacore.action.b2c.order.MaintainBasketB2COrderAction.basketPerform(MaintainBasketB2COrderAction.java:66)
at com.sap.isa.isacore.action.b2c.order.MaintainBasketB2CBaseAction.isaPerform(MaintainBasketB2CBaseAction.java:180)
at com.sap.isa.isacore.action.IsaCoreBaseAction.ecomPerform(IsaCoreBaseAction.java:343)
at com.sap.isa.isacore.action.EComBaseAction.doPerform(EComBaseAction.java:353)
at com.sap.isa.core.BaseAction.execute(BaseAction.java:211)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at com.sap.isa.core.RequestProcessor.processActionPerform(RequestProcessor.java:674)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:427)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:427)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:358)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1069)
at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:455)
at com.sap.isa.core.RequestProcessor.processForwardConfig(RequestProcessor.java:267)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:279)
at com.sap.isa.core.RequestProcessor.process(RequestProcessor.java:391)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at com.sap.isa.core.ActionServlet.process(ActionServlet.java:243)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
at com.tealeaf.capture.LiteFilter.doFilter(Unknown Source)
at com.sap.isa.isacore.TealeafFilter.doFilter(TealeafFilter.java:61)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:174)
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)

Hello Jelmer,
Waht release ans SP of ECO are you running and what ERP backend ? . If you create a session log do you get any further information?
Have you checked note [1040092|http://service.sap.com/notes/1040092] this looks like the solution to your issue, bue dependent on your release.
regards
Mark

Vendor replication in One client ERP, with SRM 5.0 version

Hi Guys,
Can anyone suggest me how to do the vendor replication in the One client ERP i.e SRM is being on the same stack of the SAP R/3 system. which is set as a one of the node in the SAP R/3 SPRO path. this is in Version 5.0.
Please suggest how to do the Vendor replication in this, whether are there any prerquisties for doing this replication?
The VenMap Table is not getting updated with entries.
Please help me soon.
Regards
Srujan K

Hi
no ranges you need to take care of this if you want to transfer same no range as ECC no range.
slg1 - you can see logs
bucf - no range for vendors
+SAP Implementation Guide
++Cross-application components
+++SAP Business Partner
++++Business Partner
+++++Basic Settings
++++++Number Ranges and Groupings
+++++++Define Number Ranges
+++++++Define Groupings and Assign Number Ranges
sorry. do you want Suggestion ECC as well as SRM in one client?
Master Data Synchronization in mySAP ERP
Purpose
In order for the Supplier Relationship Management (SRM) application to run as add-on in a mySAP ERP environment, it is necessary to synchronize master data objects within this platform, that are similar from a business point of view, yet technically different.
Master data objects on ERP and SRM side that need to be synchronized
ERP (SAP ECC*)
Corresponding object in SRM
Vendor
Business partner
Material/service
Product
Material type/service type
Product category
ECC: Enterprise Core Component
Integration
Master data synchronization in ERP is carried out centrally.
For more information, see: Master Data Synchronization
Once you have set up master data synchronization for your objects using the Synchronization Cockpit, and after initial data synchronization and key mapping has been completed, delta reports that run in the background ensure that master data is always matched.
The individual configuration steps are described in the IMG:
Supplier Relationship Management ® SRM Server ® Master Data ® Master Data Synchronization in mySAP ERP (One Client)
Features
This function ensures that changes (create, change, delete) that are made to objects on one side cause immediate (bidirectional) update to the same objects on the other side. In this way, SRM and ECC data is permanently synchronized.
·         Purchasing organizations are not included in the automatic bidirectional master data synchronization and, as is also the case with mySAP SRM, have to be matched manually or via an update report (ECC -> SRM).
Replication (and the updates) from plant (MM) to business partner location (SRM) only occurs in one direction with the report BBP_LOCATIONS_GET_FROM_SYSTEM that is executed manually.
·         Where SAP Supplier Self-Services (SUS) runs together with mySAP SRM on one ERP platform, master data synchronization occurs as described above. If SUS runs separately of ERP, SAP NetWeaver XI is used to synchronize master data with SRM.
Master Data Synchronization
Purpose
Master data synchronization synchronizes master data objects in an SAP system that are similar from a business, but not from a technical, point of view, and in this way allows you to integrate different SAP applications seamlessly in your business processes.
You can use master data synchronization, for example, to set up integration of the SAP Business Partner with the customer master. This allows you to integrate SAP applications that make technical use of the Business Partner in their user interface, and use the customer master as a technical basis in subsequent business processes.
Implementation Considerations
In order to be able to use master data synchronization, you must have defined and activated Synchronization Control as well as Customer/Vendor Integration and/or Material/Service Integration in Customizing of the Cross-Application Components under Master Data Synchronization.
Pay attention to the following note on master data synchronization terminology:
The paired terms, customer/debtor and supplier/creditor/vendor, are used with the same meaning in master data synchronization, and one term can be substituted synonymously when the documentation is read.
Integration
Master data synchronization is based in particular on the two master data objects SAP Business Partner and SAP Product, and makes it possible for the following synchronization processes, among others, to be carried out:
·        Synchronization of the business partner with the customer/debtor master
·        Synchronization of the business partner with the supplier/creditor master
·        Synchronization of the product with the material master
·        Synchronization of the product with the service master
For a complete list of all synchronization processes that are defined and active in an SAP system, see the synchronization cockpit under Synchronization Processes.
Master data synchronization replaces the current technical solutions for Customer/Vendor Integration and complements some business processes that are based on integration between the product master and the material or service master (Material/Service Integration).
Master data synchronization also has an effect on the archiving processes of the master data objects business partner/customer master /vendor master and product/material master /service master.
For more information on activating/deactivating synchronization processes, see the IMG of the Cross-Application Components under Master Data Synchronization ® Synchronization Control.
Features
Synchronization Directions
A synchronization process is always defined as a one-way synchronization between a source object type and a target object type, meaning that the synchronization is only ever active in one direction, from the source object type to the target object type. If the data of an object instance of the source object type is changed, the corresponding data in the corresponding object instance of the target object type is changed at the same time. Both synchronization directions must be activated in the SAP system in order to allow the undirected synchronization of two master data object types.
Synchronization Scenarios
There are two synchronization scenarios in master data synchronization:
·        Synchronization from the master data maintenance
When you create and save new master data, the system carries out initial synchronization with the master data object types for which synchronization processes have been activated in the SAP system, and creates the corresponding master data.
If you change existing master data that has already been synchronized, the system locks this master data, and all the corresponding master data of the source object type and the target object type during maintenance. When you save the changed master data, the system generally carries out a delta synchronization with the master data object types for which synchronization processes have been activated in the SAP system, and changes the corresponding master data. In some cases, changing existing master data can lead to a delta synchronization having to be carried out.
·        Synchronization using the synchronization cockpit
You use the synchronization cockpit to prepare, perform and check the initial synchronization of master data objects in an SAP system.
Constraints
Master data synchronization can neither synchronize master data objects across systems, nor can it transfer master data objects from external or legacy systems. You can use the SAP external data transfer to transfer legacy or external data.
Synchronization Cockpit
Definition
User interface for master data synchronization in an SAP system.
Use
Using the synchronization cockpit, you can carry out all the steps for master data synchronization in an SAP system These are as follows:
·        Customizing synchronization
·        Selection, preparation and starting of synchronization runs.
·        Monitoring of synchronization runs
·        Postprocessingof synchronization errors
·        You can start the synchronization cockpit in Customizing of the Cross-Application Components under Master Data Synchronization ® Synchronization of Mass Data ® Execute Synchronization Cockpit.
Before you can work with the synchronization cockpit, the following prerequisites must be fulfilled:
·        There are data records for at least one source object in the SAP system.
·        You are authorized to carry out synchronization.
·        You are authorized to start the Postprocessing Office (PPO).
·        You have carried out the Customizing of the master data synchronization.
·        You have carried out the general Customizing for the PPO.
For more information, see the Implementation Guide (IMG) of the Cross Application Components under General Application Functions ® Postprocessing Office.
·        You have activated the writing of PPO orders for the master data objects in Customizing of the master data synchronization.
For more information see the Implementation Guide (IMG) of the Cross-Application Components under Master Data Synchronization ® Synchronization Control ® Activate PPO Orders for Platform Objects in the Dialog.
Structure
The synchronization cockpit is divided into three work areas:
·        Synchronization processes work area
This work area contains a list of the synchronization processes. The list displays only the active synchronization processes, or all the synchronization processes. You can change between the two views at any time.
·        Customizing synchronization work area
This work area contains an overview of all the reports that you can use for the Customizing synchronization.
·        Synchronization work area
This work area contains the tab pages Processing and Monitor, which you can use to prepare or monitor synchronization runs.
Integration
The Postprocessing Office (PPO) is integrated in the synchronization cockpit, so that it can be used to postprocess synchronization errors. If the PPO has not been activated, the synchronization cockpit does not start synchronization in the case of an error, and issues the relevant error message.
br
Muthu

Distributed WMS with ERP on IBM mainframe?

I am working a dWMS opportunity. The propsect is running a homegrown ERP system on an IBM mainframe. I'm looking for information about the technical architecture between the ERP system and dWMS. I understand from metalink doc #821294.1 we use ODI.
Thanks in advance.

Hi Arthur,
Thanks for your reply, yeah, OLE DB Provider is the old fashtion way to do it but ADO.NET data provider
is latest way to do it, I believe both of them could works on it, please check following screenshot I made from HIS 2013 realease notes, and the point is it's not worth to buy a HIS 2010/2013 in order to get ADO.NET
data/OLE DB Provider, do I have to buy a dirver from a 3rd part company? Could I download
ADO.NET data/OLE
DB Provider from somewhere for free?
Johnny Wang

Can I set up a Mac Pro as a server using OSX Server for my current Windows-based office?

I have a small business, and our office currently has a Windows-based network. I love my Mac and it's ease of use, and for now I have to use Remote Desktop to log on to my server, and then run my MRP/ERP business software from that. Is there an Apple solution (Mac Pro?) for my server, where other users could run parallels to access the MRP/ERP software? Thanks!

It is possible - even quite easy - to turn almost any current or recent model of Mac into a server by installing OS X Server. It is less clear, however, that this will do what you want.
What are the hardware and software requirements of your MRP/ERP software? If it will only run under Windows or any OS other than Mac OS X, then it will not work, and installing OS X Server will not change that.
You may be able to get the MRP/ERP software to run under Windows run on a Mac using Parallels or VMWare Fusion, but it would still be running under the Windows OS, just virtualized so that it runs inside the Mac OS. Thus it will not be any easier to use than your current system, and in fact may be harder, and might not work at all.
You could also run Windows under BootCamp, but again, while the Windows OS would be running natively, you lose any ease of use of the Mac OS.
Best of luck.

SPROXY not working in application system

Hello all,
I have been trying to make SPROXY work in my QAS ERP 2004 SPS23 system
for a few days now but I can not make it. I have
configured SPROXY in the past for my sandbox and DEV system with
success but I do not seem to have any luck in QAS.
My PI landscape consists of sandbox, developement, qa and production
systems. The version is PI 7.0 SPS21
My ERP landscape consists of the same 4 systems but in version 6.40 -
ERP 2004 SPS23
All non production systems use a central SLD that runs in the PI development
box (PID)
The error message I get is as follows:
When I run SPROXY in ERP QAS client 330, I get : "No connection to Integration
Builder (only local data visible)"
When I do Goto --> Integration Builder, I get the message "Integration
Builder address not maintained"
However, when I do Goto --> Connection Test, from the 4 reports I have
to run, two work and two do not work:
=>Check/maintain with report SPROX_CHECK_IFR_ADDRESS works and shows the correct address for Integration repository
=>Check with report SPROX_CHECK_HTTP_COMMUNICATION works
The other two reports
=>Check with report SPROX_CHECK_IFR_RESPONSE
==>Check with report SPROX_CHECK_IFR_CONNECTION
return: Integration builder data not undestood.
SLDCHECK runs fine: All green and invokes correct IE session with the correct SLD URL (central SLD)
SLDAPICUST shows the correct SLD (central)
SXMB_ADM --> Integration Engine Configuration shows the destination RFC
SAPIS_PIQ
which is defined in SM59 as type H and works fine
TCP RFCs LCRSAPRFC and SAPSLDAPI work
The corresponding JCos in Visual Administration look ok
I have registered the queues in SXMB_ADM and they registered ok .
The /sap/xi/engine service is active in both the application system and the PI system (QAs and PIQ)
Finally the exchange profile settings in PIQ are fine as well
com.sap.aii.connect.repository.name : piqas.finance.local
com.sap.aii.connect.repository.httpport : 50000
com.sap.aii.connect.repository.contextRoot :rep
com.sap.aii.connect.integrationbuilder.startpage.url : rep/start/index.jsp
com.sap.aii.applicationsystem.serviceuser.name: PIAPPLUSER
and the password is set.
PIAPPLUSER is service user and is not locked.
I have tested SLDCHECK in PIQ and SLDAPICUST and they look ok as well.
Any other clues? Any way I can investigate further via checking logs
and traces to find out what is wrong?
The "Data not understood" message is not helping me much in determining
what is wrong
Many thanks
Andreas

Hi Andreas,
Please go through the below blog which explains you step by step in proxy connectivity.
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
Regards,
Naveen.

Alert box:No more free items available, please create new one

Hi,
We are running a SAP ERP Ecommerce, we get a strange alert box message "no more free items available, please create a new one". This alert window pops up only when you have created one order in a session and you are trying to create another order. Has anyone come across this issue?
Steps to recreated this issue
1. Create an order with any product - quantity is rounded to next possible value.
2. Order created, close the order.
3. Trying to create new order. (Product field is not a text box anymore)
4. Try to transfer product from catalog by hitting shopping basket icon.
5. Error message -> "No more free items available, please create new one".
Thanks,
-Tarun

Hi,
We are running a SAP ERP Ecommerce, we get a strange alert box message "no more free items available, please create a new one". This alert window pops up only when you have created one order in a session and you are trying to create another order. Has anyone come across this issue?
Steps to recreated this issue
1. Create an order with any product - quantity is rounded to next possible value.
2. Order created, close the order.
3. Trying to create new order. (Product field is not a text box anymore)
4. Try to transfer product from catalog by hitting shopping basket icon.
5. Error message -> "No more free items available, please create new one".
Thanks,
-Tarun

Exporting to PDF fails for a report

Hi,
One of my reports no longer exports to PDF. When run through our ERP system it looks as if it's exporting but the progress popup window quickly dissappears. When we go to the location where the exported file should be nothing is there.
I tried opening up the report in the Crystal 11 and exporting from there. I get the following two error messages:
Failed to export the report.
Not supported
This was working yesterday. The only thing I did was to add the u2lbar.dll to the bin folder and copy over the barcode font so that we could display barcodes on this report. However, even if I comment the line to do the barcode I still get the same problem.
Thanks,
Jon

The font you are using probably doesn't have embedding permissions.
hth,
- Ido

Mapping Logical Systems -

Hi,
i want to connect to 2 backends to test ESS BP functionality.
The background is that i want to test functions for ERP 6.0 EhP3 and need to keep the old Webdynpro functionality.
The old java webdynpro (ESS) is running on the portal side, the new ABAP webdynpro is running on the ERP system.
I configured new JCODestinations as described in http://help.sap.com/saphelp_nw70/helpdata/EN/af/84a34098022a54e10000000a1550b0/frameset.htm
I could connect now to iviews like life events with the correct parameters.
The issue is now that i also need to switch the XSS Overview (XssMenu) pages.
So far i am always connected to the old system. I tried all properties of that iview and also created a new one.
Is it possible to connect to the old system?
Thanks,
Kai

Hi Christian,
We are also looking into this functionality but have not gotten it to work yet.
Our issue is that our DEV/QA users need to test with different backend clients.
So we want to be able to specify a different JCO as part of the WebDynpro URL that we issue.
For testing, we have created two new JCOs (one data and one metadata). The names of the new JCOs are the same as the old but with 3 unique characters appended to the name (e.g. "ABC"). Those new JCOs point to a different client.
Then when we call the URL for the WebDynpro, we append
?sap-wd-arfc-useSys=SAP_R3_HumanResources:ABC&sap_wd_afrc-useSys=SAP_R3_HumanResources_Metadata:ABC
to the end of the URL.
However, after authenticating, this URL fails with NullPointerException
Any idea about what the problem might be?
TIA ... Bart

1099 Report for OTV - Classic Withholding Tax

Hello Members,
We run on SAP ERP 6.0 EHP6 and use the classic withholding tax functionality.
Wondering what the rest of the world with classic setup is using for 1099-MISC reporting for one time vendors ?
Currently we follow a cumbersome process of pulling FBL1N report (which doesn't have otv address information), and then FCHN to get vendor address details. With this we change a vendor and update the master data and payment document withholding information in QAS to print the paper form from QAS.
I read a few of the forums and the idea I get is, if the vendor is to be 1099 reported, it should be a standard vendor.
Questions:
1) Any standard functionality available within classic setup for 1099 MISC reporting of OTV ?
2) Does using extended functionality make OTV reporting any better
3) Any best practices that you are following which you think is better than ours ?
Regards,
Ani

Hi,
See SAP Note-802033
Raj

SAP ECC 6.0 Maintenance phase

Dear Experts,
We got notification from our EWA report that our SAP ERP 6.0 maintenance ended on 31.03.2013 as follows:
0.0.1 SAP Application Release: Maintenance Phases
SAP Product
SAP Product Version
End of Mainstream Maintenance
End of Extended Maintenance
SAP ERP
6.0
31.03.2013
31.03.2016
Your system P01 is running on SAP ERP 6.0. Mainstream maintenance for SAP ERP 6.0 ended on 31.03.2013.
Recommendation:
We recommend that you upgrade your system. For more information, see SAP Service Marketplace at service.sap.com/upgrade.
If you decide to continue using the current release, SAP offers extended maintenance for SAP ERP 6.0 from 01.04.2013 to 31.03.2016.
while SAP note 1648480 - Maintenance for SAP Business Suite 7 Software tells that the maintenance is extended to 2020, please also refer to link: SAP AU & NZ - SAP extends mainstream maintenance for SAP ERP 6.0 and Business Suite 7.0 until 2020
Please advise.
Regards,
Rudi

Dear Experts,
We got notification from our EWA report that our SAP ERP 6.0 maintenance ended on 31.03.2013 as follows:
0.0.1 SAP Application Release: Maintenance Phases
SAP Product
SAP Product Version
End of Mainstream Maintenance
End of Extended Maintenance
SAP ERP
6.0
31.03.2013
31.03.2016
Your system P01 is running on SAP ERP 6.0. Mainstream maintenance for SAP ERP 6.0 ended on 31.03.2013.
Recommendation:
We recommend that you upgrade your system. For more information, see SAP Service Marketplace at service.sap.com/upgrade.
If you decide to continue using the current release, SAP offers extended maintenance for SAP ERP 6.0 from 01.04.2013 to 31.03.2016.
while SAP note 1648480 - Maintenance for SAP Business Suite 7 Software tells that the maintenance is extended to 2020, please also refer to link: SAP AU & NZ - SAP extends mainstream maintenance for SAP ERP 6.0 and Business Suite 7.0 until 2020
Please advise.
Regards,
Rudi

Running BW on ERP

Similar Messages

Maybe you are looking for