BWA Support strategy from SAP

Hi,
With SAP pushing everyone towards HANA, does anyone know what the support strategy/timelines are that SAP has for BWA? I.e. until when will SAP support BIA?
Thanks
Werner

Hi Werner,
Got this info from SAP Support Portal .Looks like till 31/12/2020 SAP will support BWA.
-Arun.M.D

Similar Messages

How to post message from SAP to solution manager

Dear Friends,
We have configured solution manager service desk and the users were able to send messages so that we can view it in solman ITSM.
Now we want to bifurcate the messages from different people, hence we woule like to use of Problems in incident management of solman.
How a end user can create a message so that it comes and fall in problems folder of incident management,
Normally create support message from SAP will make the message to be visible in incidents of solman ITSM, but we want the message to fall in problems section of ITSM in solman.
Please help.
Thanks
Suresh

Hi,
In 7.1 we do have dedicated services as Problem management, with the transaction type SMPR. you can create ZMPR and proceed similar to SMIN ( incident) in ITSM.
also refer here Problem Management in SAP Solution Manager 7.1 - Part 2
Thanks
Jansi

OutlookSoft 4.2 - SAP Support Strategy

Hello All,
I want to know the SAP's support strategy for OutlookSoft/BPC. Specifically, when the support for 4.2 is ending?
Our Client is on 4.2 SP3. What is the recommended support pack for OutlookSoft 4.2?
Also, are there any maintenance fees for OutlookSoft 4.2 in order to be supported by SAP for extended period of time?
Regards,
Prabhu
Edited by: Prabhu Chinnakonda on Aug 29, 2008 7:45 PM

Hi,
I think, it is better to upgrade to BPC 5.X /7.X from OutlookSoft 4.2-SP3, so that your organization will be on par with latest SAP BPC tools. From BPC 9.X ( should be released around late 2009), this will be all together new tool, with complete changes & total integration with BI/IP/SEM in it.. By that time OutlookSoft 4.2, will be all most uotdated. Neverthless you can upgrade to OutlookSoft 4.2-SP4/SP5, but again in future you need to upgrade to BPC 5.X/7.X.
For upgardations & support , please contact SAP Support, where you will get complete details & dates.
Regards
CSM Reddy

SAP BW 3.5 Support from SAP

Hi All,
My customer is requesting for the below things, Please help me where i can check the details.
1) SAP BW 3.5 product support from SAP till what period (years).
2) where i can check the license expiry date of my product.
I have Customer S-user ID for my Project, Please guide where i can get the above details in service market place.
Regards,
Vara Prasad.

Hello Prasad,
For SAP BW3.5 ([click for details|https://websmp105.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200314690900000192])
End of mainstream maintenance 31.03.2010
End of extended maintenance 31.03.2013
Please see the following links for more details from service market place,
[SAP Maintenance Strategy|https://websmp105.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000611452&_SCENARIO=01100035870000000202]
[Customer-Specific Maintenance |https://websmp105.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000611452&_SCENARIO=01100035870000000202]
Also see [Product Availability Matrix |https://websmp105.sap-ag.de/pam]
Thanks
Chandran

Official Support from SAP on Support package levels

I have NW7 Dual stack system. Currently at SP10
Looking for an "official Policy" on supported SP levels from SAP, if it exists already. Please help me by providing a link that information or a document if it exists.
We are working on an ongoing infrastructure support policy for this installation.
Thanks in advance.
Vasu

You can run a certain level of support packages as long as you can live with the "deficiencies" resulting out of that. You can run on the initial installed level if you can deal with the fact, that you will need to apply a LOT of notes in case you run into an error (because of dependent notes because of the low support package level).
There may also be cases where it´s impossible to provide a correction by note (e. g. table changes) and where corrections can only be delivered by support packages.
Last but not least the law may force you to install a certain level (e. g. fiscal year change) to get the newest (and correct) data out of the system for all kinds of changes that may be necessary to comply the law.
Basically you can leave your system on a certain support package as long as you wish but it may become difficult or even impossible to give you a solution if more than an ABAP code correction is necessary.
This is especially true on dual stack systems where a change in the portal may force you to upgrade your complete backend to a certain level because there the ABAP + Java stack must be in sync --> one of the reasons why we totally avoid dual stack installations.
Markus

SAP Support from SAP

Hello,
I have SAP Solution Manager with working SAPOSS and SAP Router connection (to SAPSERV3) and need support from SAP.
Therefore I created the SAP Message, opened the system and created the appropriated user
Unfortunately it is not possible to log in to the SAP system.
My question:
How can the SAP R/3 Support connection could be established and tested?
Thank you very much!
regards,
Thom

Hi
For more information tryout these links you would be able to understand:
http://service.sap.com/upgrade
http://service.sap.com/upgradeservices

Send Support message to SAP from solman

Hi
Where can we find the document to connect solution manager to sap market place ,so that we can send the support messages to Sap from Solution manager directly with out logging into Service market place.
Thanks
Nanda

Hi Kishore,
Hope below URL Helps.
/people/kamran.ellahi2/blog/2006/01/13/setting-up-sap-service-desk-123-and-go
/people/federico.babelis2/blog/2006/04/14/service-desk-configuration-guide-for-dummies
Cheers
Deeepanshu

SAP BW 3.5 - Upgrade support package from 18 to 21

Hi All,
We are planning to apply the SP 21 for SAP BW 3.5 system.
Currently we are on SP 18.
We had created a Customer message to SAP regarding the Pre-Preparatory Steps before applying and Post upgrade steps . But the reply we got is quite confusing.
In one of the steps they had asked us to delete the Delta queue and delete the Set up tables. But looks like they have got confused with the SAP R/3 Upgrade.
Previously, when we upgraded from SAP BW 3.1 to 3.5 we never touched anything concerned with the Source systems ( SAP R/3).
Could anyone guide me regarding this issue. Also it would be great help if anyone give the Pre-Preparatory Steps before applying and Post upgrade steps.
Regards,
Satish

Hi,
Just go apply for from SP18 to SP21 directly. Before applying for this better check with BW consultants and also check with ABAPers team.
http://service.sap.com/bi
http://service.sap.com/sp-stacks for BW 3..5 not for BI 7.0 (EhPs)
Regards,
Srini Nookala

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

BWA-Support-Toolkit

Hi BWA specialists,
I just want to inform you about the BWA-Support-Toolkit which was released some month ago. I read the note (1517326) at the end of the last year but I had no time to implement it. By luck I found the note again and implement it. I think it is a real useful tool for those who can´t use the python standalone tool. I don´t want to lose too many words about it, please read the docu by yourself (attachment to the note 1517326) and let me know some how you can use it in your company.
In a few month the toolkit will be implemented in the SAP standard in a new version of the ST-A/PI component.
Looking forward to some new features of the tool. May be some of you find some functions which should be implemented and can be addressed to SAP directly
Regards,
Jens

hi Jay,
according Michael Wu from SAP America this tool was originally supposed to be used only by SAP as internal tool. So might be that they decided to take it out from users.
You may contact Michael directly with regards this matter. Please keep us posted about the results. Thanks, martin

HTTPs connection from SAP WebAS

Hello,
I have to establish a connection from SAP WebAS to an iSaSiLk server via HTTPS.
The iSaSiLk authentication is based on client certificates.
I've created a SSL client PSE, generated the Certificate Request, imported the certificate response and the chain of certificates associated with no errors. When testing the connection we're getting the following error message:
SAP icm log:
[Thr 1087400256] ->> SapSSLSessionInit(&sssl_hdl=0x2aaaba679980, role=1 (CLIENT), auth_type=3 (USE_CLIENT_CERT))
[Thr 1087400256] <<- SapSSLSessionInit()==SAP_O_K
[Thr 1087400256]      in: args = "role=1 (CLIENT), auth_type=3 (USE_CLIENT_CERT)"
[Thr 1087400256]     out: sssl_hdl = 0x1a3310c0
[Thr 1087400256] ->> SapSSLSetNiHdl(sssl_hdl=0x1a3310c0, ni_hdl=22)
[Thr 1087400256] NiIBlockMode: set blockmode for hdl 22 TRUE
[Thr 1087400256] <<- SapSSLSetNiHdl(sssl_hdl=0x1a3310c0, ni_hdl=22)==SAP_O_K
[Thr 1087400256] ->> SapSSLSetSessionCredential(sssl_hdl=0x1a3310c0, &cred_name=0x1a49e4e0)
[Thr 1087400256]   SapISSLComposeFilename(): Filename = "/usr/sap/XID/DVEBMGS00/sec/SAPSSLSPHTID.pse"
[Thr 1087400256] <<- SapSSLSetSessionCredential(sssl_hdl=0x1a3310c0)==SAP_O_K
[Thr 1087400256]      in: cred_name = "/usr/sap/XID/DVEBMGS00/sec/SAPSSLSPHTID.pse"
[Thr 1087400256] ->> SapSSLSetTargetHostname(sssl_hdl=0x1a3310c0, &hostname=0x1a4a09e0)
[Thr 1087400256] <<- SapSSLSetTargetHostname(sssl_hdl=0x1a3310c0)==SAP_O_K
[Thr 1087400256]      in: hostname = "<remoteServer_to_be_accessed>"
[Thr 1087400256] ->> SapSSLSessionStart(sssl_hdl=0x1a3310c0)
[Thr 1087400256]   SapISSLUseSessionCache(): Creating NEW session (0 cached)
[Thr 1087400256] Tue Jan 13 10:10:22 2009
*[Thr 1087400256] *** ERROR during SecudeSSL_SessionStart() from SSL_connect()==SSL_ERROR_SSL*
[Thr 1087400256]    session uses PSE file "/usr/sap/XID/DVEBMGS00/sec/SAPSSLSPHTID.pse"
[Thr 1087400256] SecudeSSL_SessionStart: SSL_connect() failed
secude_error 536871693 (0x2000030d) = "none of the PSEs registered with hSsl can suffice the negotiated SSL cipher suite"
[Thr 1087400256] >>            Begin of Secude-SSL Errorstack            >>
[Thr 1087400256] ERROR in ssl3_get_certificate_request: (536871693/0x2000030d) none of the PSEs registered with hSsl can suffice
[Thr 1087400256] <<            End of Secude-SSL Errorstack
[Thr 1087400256]   SSL_get_state() returned 0x00002150 "SSLv3 read server certificate request A"
[Thr 1087400256]   No certificate request received from Server
[Thr 1087400256] <<- ERROR: SapSSLSessionStart(sssl_hdl=0x1a3310c0)==SSSLERR_SSL_CONNECT
[Thr 1087400256] ->> SapSSLErrorName(rc=-57)
[Thr 1087400256] <<- SapSSLErrorName()==SSSLERR_SSL_CONNECT
[Thr 1087400256] *** ERROR => IcmConnInitClientSSL: SapSSLSessionStart failed (-57): SSSLERR_SSL_CONNECT [icxxconn_mt
On the iSaSiLk server we're getting:
ssl_debug(2): Starting handshake (iSaSiLk 3.06)...
ssl_debug(2): Received v3 client_hello handshake message.
ssl_debug(2): Client requested SSL version 3.0, selecting version 3.0.
ssl_debug(2): Creating new session 11:5F:04:C9:0D:32:15:B9...
ssl_debug(2): CipherSuites supported by the client:
ssl_debug(2): SSL_RSA_WITH_RC4_128_SHA
ssl_debug(2): SSL_RSA_WITH_RC4_128_MD5
ssl_debug(2): SSL_RSA_WITH_3DES_EDE_CBC_SHA
ssl_debug(2): SSL_RSA_WITH_DES_CBC_SHA
ssl_debug(2): SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
ssl_debug(2): SSL_RSA_EXPORT_WITH_RC2_CBC_40_MD5
ssl_debug(2): SSL_RSA_EXPORT_WITH_RC4_40_MD5
ssl_debug(2): CompressionMethods supported by the client:
ssl_debug(2): NULL
ssl_debug(2): Sending server_hello handshake message.
ssl_debug(2): Selecting CipherSuite: SSL_RSA_WITH_RC4_128_SHA
ssl_debug(2): Selecting CompressionMethod: NULL
ssl_debug(2): Sending certificate handshake message with server certificate...
ssl_debug(2): Sending certificate_request handshake message...
ssl_debug(2): Sending server_hello_done handshake message...
ssl_debug(2): IOException while handshaking: Connection closed by remote host.
ssl_debug(2): Sending alert: Alert Fatal: handshake failure
ssl_debug(2): Shutting down SSL layer...
ssl_debug(2): Closing transport...
From the iSaSiLk everything seems to be OK, but on the SAP WebAS the error "none of the PSEs registered with hSsl can suffice the negotiated SSL cipher suite" is really unclear, since the cipher chosen by the iSaSiLk is one of the ciphers sent by SAP WebAS...
Can anyone give me any suggestion?

Hello Olivier,
Thanks for your answer.
I've implemented note 800240 which facilitates the PSE analysis by implementing the report ZSSF_TEST_PSE. With this report I'm able to check all the PSE content, which are:
Filename            SAPSSLSPHTID.pse
PIN                 <no>
Signature           X
Encryption          X
Profile Parameter
DIR_INSTANCE                   /usr/sap/XID/DVEBMGS00                       /usr/sap/XID/D00
sec/dsakeylengthdefault                                                     1024
sec/libsapsecu                 /usr/sap/XID/SYS/exe/run/libsapcrypto.so
sec/rsakeylengthdefault                                                     1024
ssf/name                       SAPSECULIB
ssf/ssf_md_alg                                                              SHA1
ssf/ssf_symencr_alg                                                         DES-CBC
ssf/ssfapi_lib                 /usr/sap/XID/SYS/exe/run/libsapcrypto.so
ssf2/name
ssf2/ssf_md_alg                                                             SHA1
ssf2/ssf_symencr_alg                                                        DES-CBC
ssf2/ssfapi_lib
ssf3/name
ssf3/ssf_md_alg                                                             SHA1
ssf3/ssf_symencr_alg                                                        DES-CBC
ssf3/ssfapi_lib
Environment variables
USER                xidadm
SECUDIR             /usr/sap/XID/DVEBMGS00/sec
PSE
Validity            18.12.2008 19:47:04   18.12.2009 19:47:04
Algorithm           RSA (OID 1.2.840.113549.1.1.1)
Test signature
Signature OK
Verification OK
Test encryption
Encryption OK
Decryption OK
As you can see, the cipher algorithm used is RSA. Any suggestion... ?
An iSaSiLk server "is a Java programming language implementation of the SSLv2 (client-side), SSLv3, TLS 1.0 and TLS 1.1 protocols. It supports all defined cipher suites (except for Fortezza), including all AES and PSK cipher suites. iSaSiLk implements all standard TLS extensions, comes with an easy to use API and operates on top of the IAIK-JCE Javau2122 Cryptography Extension. iSaSiLk is highly configurable and will work with any alternative JCE implementation supported by a proper provider for supplying the required cryptographic algorithms".
Once again thanks for your answer.

I need the Log Report for the Data which i am uploading from SAP R/3.

Hi All,
I am BI 7.0 Platform with Support Patch 20.
I need the Log Report for the Data which i am uploading from SAP R/3.
I extract the DATA from R/3 into BI 7.0 DSO where I am mapping the GL Accounts with the FS Item. In the Transformation i have return a routine on the FS Item InfObject . I am checking the Gl code into Z table for the FS Item .
I capture the FS item from the Z table then update this FS item to Infobject FS item.
Now i need to stop the Data upload if i do not find the GL code in the Z table, and generate report for all GL code for which the FS item is not maintained in the Z table.
Please suggest.
Regards
nilesh

Hi.
Add a field that you will use to identify if the GL account of the record was found in the Z table or not. Fx, create ZFOUND with length 1 and no text.
In your routine, when you do the lookup, populate ZFOUND with X when you found a match (sy-subrc = 0) and leave it blank if you don't find a match. Now create a report filtering on ZFOUND = <blank> and output the GL accounts. Those will be the ones not existing in the Z table, but coming in from your transactions.
Regards
Jacob

Unable to import idoc into PI 7.0 system from SAP r/3 system

Hi Experts,
    I am getting an error while importing an Idoc structure from SAP r/3 system. The error says "unable to read Idoc segments". The Idoc has recently undergone changes. When We are looking at the struture of idoc through IDOCSYN table it is showing updated structure in SAP R/3 system but import to SAP XI is failing.
Can you suggest some way to tackle this kind of problem.
regards
Anupam

Hi Francis,
   This was indeed an authorization issue. Thank you so much for your valuable suggestion. The user lacked proper authorization to import the idocs.
Hi All,
    Thank you for all your support.
Regards
Anupam

SAP DB Connection from SAP BI on HP UNIX to MS SQL External Database

Dear All,
Greetings!
I have a scenario to configure a SAP DB Connection from SAP BI System on HP UNIX 11i to the external legacy system MS SQL 2000 Enterprise for data upload. I am interested in connecting the SQL server as a Source System to the BI System.
I read through documents mentioning about installation of a Client driver in the SAP BI System, I also downloaded the JDBC client software and tried installing the same, but the steps as mentioned Setting the CLASSPATH or connecting to the server did not work.
Please help me in connecting the SQL Server as Source System, I would like to know in detail about the same - so kindly help me with the links to documents and guides about the same.
Thank you
Regards,
Vineeth Damodar

Short answer: this does not work.
Long answer: To connect directly to the database you need
- a database client for the source system
- a database interface library for the source system
Both of them are not available for HP-UX if the target database is SQL server --> doesn't work.
What you can do is: add a Windows application server to your BI system (heterogeneous installations work and are supported) and add there the database client and the database interface library.
Markus

Error during upgrade from sap R3 4.7 ext 110 to ERP6 EHP4

Dear all
we doing an upgrade in test server to ERP6 with EHP4,source release is sap Entreprise 4.7 110.We have copied all the required DVDs to the server .During the configuration phase while giving the EHP package we got the error.
EHP_INCLUSION.log details
4 ETQ233 Calling function module "SPDA_PREPARE_PATCH" by RFC
4 ETQ234 Call of function module "SPDA_PREPARE_PATCH" by RFC succeeded
4 ETQ239 Logging off from SAP system
4 ETQ010 Date & Time: 20100915210509
2 ETQ732 Package descriptions uploaded successfully
4 ETQ399 Looking for SAINT package for 'SAP_APPL' ...
4 ETQ399 R3upReadNewPackages:
4 ETQ399   patchType='U', langVect='DE'
4 ETQ359 RFC Login to: System="MBD", Nr="00", GwHost="saptest", GwService="sapgw00"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "spda_read_new_packages" by RFC
4 ETQ399   ismovesVersion='0'
4 ETQ399 R3upReadNewPackages: exit: rc=0
4 ETQ399      Found: name = 'SAP_BS_FND', release = '701', package = 'SAPK-701GGINSAPBSFND', type = 'AOX'
4 ETQ399             (not usable, different component
4 ETQ399 ... No matching package found.
Is this related to the current SAP_APPL support pack version ?.currently we have
SAPKH47031 SP 31 for SAP_APPL 4.70
Regards
Shahnas.S

> i have few questions regarding above
(Almost) all of your questions are answered in the note:
> 2.Do wee need to apply the above note for non-unicode upgrade
<...>
Even on non-Unicode system you should replace all matchcodes that are still required by search helps.
<...>
> 3.Note 1330256 recomends to apply support pack or to apply the Note 1330256 ,but we can do it only at upgraded version.
Yes - it avoids dumping with the dump mentioned in the note
> 4.How to identify the matchcodes
<...>
You can use the program TWTOOL01 to determine the existence of matchcodes.
<...>
> 5.How to delete them
<...>
You can then use the function module DD_MCOB_DEL to delete matchcode objects, and the function module DD_OBJ_DEL to delete matchcode IDs.
<...>
> 6.Impact of deleteing matchcodes
None since they were replaces by search helps.
Markus

BWA Support strategy from SAP

Similar Messages

Maybe you are looking for