PI_BASIS 2006_1_640 for SAPKW35018

I was Applying the Patch for BW 350 its SAPKW35018 ;
its shows me Error_stop.I was looking at service.sap.com/notes it says we need to have PI_BASIS,2006_1_640 as requirement .But its not available at service.sap.com/pathces .
Please help me .....

There are two separate kinds of prerequisite to apply SP SAPKW35014.
The first one is to apply PI_BASIS 2006_1_640, which is not released
at the moment. The second possibility is AOP SAPKIPYJ64
(PI_BASIS 2005_1_640: patch 0004). This package is available.
For your reference notes:
836439 SAPBWNews BW Support Package 14 NW'04 Stack 14 RIN
821148 Installing/upgrading Basis Plug-in (PI_BASIS) 2005.

Similar Messages

Can't find KINBC8A.SAR file for PI_BASIS 2006_1_640

Hello, I'm trying to upgrade to PI_BASIS 2006.1.640.
As per note 1007796 I need to unpack archive KINBC8A.SAR but the file is not available for downloading with 51032427.zip file from the SAP Software Distribution Service.
Do you know where can I get this file?
Many thanks,
Diego

If I look into the file content I can see "KINBC8A.SAR" under
DELT_640\DATA\KINBC8A.SAR
Markus

PI_BASIS 2007_1_640 Addon

Hi Gurus,
As iam Upgrading my system i need a to apply an Addon PI_BASIS 2007_1_640 i could'nt find that in the Service Market Place , Can any one suggest how can i search the addon PI_BASIS 2007_1_640,
Waiting for Your Response.
Thanks and Regards,
Naresh.

Hi Naresh,
You can't find PI_BASIS 2007_1_640 as it is not released. you can use PI_BASIS 2006_1_640 if your Kernel release is 640 or you can use PI_BASIS 2006_1_700 if your kernel release is 700.
you can get the addon in: service.sap.com/swdc->Download->Installation and Upgrades ->Entry by application group->Plug-in's->SAP Plug in.
Hope it resolves your issue.
Thanks
Kishore

SRM SERVER 5.0: which is the max length possible for attachment ?

When I add file to a Shopping Cart in "Documents and Attachments" area , which is the maximum size permitted ? 1MB, 2MB, 3 MB?
Thank you in advance.
Best regards.
Claudia.

I was able to attach a file of 31,8 MB and I 've not problem.
These are the informations you requested to me:
SRM 5.00
SAP_ABA     640     SAPKA64022
SAP_BASIS     640     SAPKB64022
PI_BASIS     2006_1_640     SAPKIPYL06
ST-PI     2005_1_640     SAPKITLQH5
SAP_BW     350     SAPKW35022
CCM     100     SAPK-10006INCCM
SRM_SERVER     SAPKIBKS14
ST-A/PI     01I_BCO640 -
BR
CLA.

MIDDLEWARE ( R/3 Plugin support pack details)

Hi Experts,
We have to integrate CRM5.0 with R/3 4.7. Can anybody tell me the version of the PI( plug-in) support package, which has to be installed at R/3.
Points will be rewarded.
Thanks in advance
Nadh.

Hi Eric,
Thanks for your support.
I have gone through the SAP note 672651 - OCS: Known problems with Support Packages in Basis Rel.6.40 and did a analysis of steps to install BW 3.5 support packs
1.Logon to client 000 with superuser having full authorisaton (i.e SAP_ALL and SAP_NEW)
2.Update SPAM/SAINT Version
3.Install PI_Basis 2005_1_640 with SAINT tcode
4.Install SAP_BASIS support packs with SPAM
SAPKB64013---SAPKB64014
SAPKB64015---SAPKB64018
SAPKB64019---SAPKB64021
5.Install SAP_ABA support packs with SPAM
SAPKA64013---SAPKA64014
SAPKA64015---SAPKA64018
SAPKA64019---SAPKA64021
6.Install PI_Basis 2006_1_640 with SAINT
7.Install SAP_BW Support packs
SAPKW35013---SAPKW35014
SAPKW35015---SAPKW35018
SAPKW35019---SAPKW35021
Our BW 3.5 system is having SAP_Basis SAPKB64012 as current level and SAP_BW SAPKW35012
as current level.
Please let me know is the queue defined for Basis,ABAP and BW Supports packs is ok.
Regards,
Anil.

DYNPRO_SEND_IN_BACKGROUND ERROR

Hi Guru's,
We are facing a problem with our system and need some expert opinion on it .The client opens a bex query in the browser and it is working fine . But when they click on save view button and try to save it it throws an HTTP 500 - internal server error . The note says screen output without connection to user .
Termination type was : RABAX_STATE
The ABAP call stack was :
SYSTEM-EXIT of program SAPLSTRD
function TRINT_POPUP_EDIT_CANCEL_O_SHOW of program SAPLSTRD
RAISE_ERROR of program SAPLSTRD
TR_EDIT_CHECK_OBJECTS_KEYS of program SAPLSTRD
in ST22
it says
During background processing, the system attempted to send a                    screen to a user.
Current screen: "SAPLSTRD " 0351.
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
DYNPRO_SEND_IN_BACKGROUND C
SAPLSTRD or " "
SYSTEM-EXIT
We tried looking for OSS notes but dont seem to find the right fit .
We are on BW 3.5 version and the system status is as follows
COMPONENT RELEASE
SAP_ABA     640     0016     SAPKA64016
SAP_BASIS      640     0016     SAPKB64016
PI_BASIS        2006_1_640     0001     SAPKIPYL01
ST-PI                    2005_1_640     0007     SAPKITLQH7
SAP_BW               350     0016     SAPKW35016
BI_CONT                 353     0008     SAPKIBIFP8
SAP_WPDRMD   640     0001     SAPKQDRB01
ST-A/PI     01J_BCO 640     0000          -
Can this issue be solved by installing some support pack ?
Any pointers will be highly appreciated
Thank you all in Advance
Warm Regards
Ankush
PS : Points wil be rewarded

Hi Ankush,
Which system is the user trying to save a View? Dev? Prod?
The reason for the error is that the Objects the User is trying to create is locked in a transport. When the User tries to SAVE, the System attempts to popup a screen with "Edit" or "Display" or "Show".
the FM TRINT_POPUP_EDIT_CANCEL_O_SHOW does this.
DYNPRO_SEND_IN_BACKGROUND happens when a Batch job tries to Call a Screen. Not sure why this error appears when the User tries to click the SAVE button.
Can you paste the code the short dump details? Did you try replicating the issue using your login? do you get the same error?
Cheers,
Praveen.

XI JDBC Connectivity Problems

Hi All,
We are using the J2EE Engine of our XI box for connectivity to an external DB for BI UD Connect.
We keep getting on an intermittent basis the following error message :-
BIRuntimeException: Null is not a supported value for Connection Property: url
But the URL property is not blank and works fine but if we resave the configuration when we get this message it works again without us doing anything!!!
Is there something we can do or should do to stop this?
SAP_ABA              640     0020     SAPKA64020     Cross-Application Component
SAP_BASIS     640     0020     SAPKB64020     SAP Basis Component
PI_BASIS        2006_1_640     0001     SAPKIPYL01     Basis Plug-In (PI_BASIS) 2006_1_640
ST-PI                   2005_1_640     0007     SAPKITLQH7     SAP Solution Tools Plug-In
SAP_BW              350    0020     SAPKW35020     Business Information Warehouse
Any help appreciated.
Thanks
Craig

Hi,
Check some links they may help u out.
                          To install oracle drive in XI server, just check these links,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html
http://msdn2.microsoft.com/en-us/library/ms177523.aspx
/people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
                          JDBC Receiver with Oracle Stored Procedures
configuring jdbc adapter with multiple tables
RFC -> XI -> JDBC Scenario Updating Multiple Tables
/people/alessandro.berta/blog/2005/10/04/save-time-with-generalized-jdbc-datatypes
JDBC Adapter multiple Selects
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=jdbc%20with%20multiple%20tables&cat=sdn_all
Regards,
Phani

Upgrade from R/3 4.6C to ECC 6.00 : languages

Hi,
We're trying to upgrade from SAP R/3 4.6C to ECC 6.00 under NT environment, having Oracle as database. During the preparation phase, we got the following error, and in our current SAP system R/3 we have 2 additional languages NL and FR (EN and DE are already in), can you please explain why this phase is blocking in this step, and if I continue I've to do a full language import, thanks in advance.
The following language(s) could not be updated yet:
- French       for component EA-APPL
- French       for component EA-DFPS
- French       for component EA-FINSERV
- French       for component EA-GLTRADE
- French       for component EA-HR
- French       for component EA-IPPE
- French       for component EA-PS
- French       for component EA-RETAIL
- French       for component ECC-DIMP
- French       for component ERECRUIT
- French       for component FI-CA
- French       for component FI-CAX
- French       for component FINBASIS
- French       for component INSURANCE
- French       for component IS-CWM
- French       for component IS-H
- French       for component IS-M
- French       for component IS-OIL
- French       for component IS-PS-CA
- French       for component IS-UT
- French       for component LSOFE
- French       for component PI_BASIS
- French       for component SAP_ABA
- French       for component SAP_AP
- French       for component SAP_APPL
- French       for component SAP_BASIS
- French       for component SAP_BW
- French       for component SAP_HR
- French       for component SEM-BW
- French       for component ST-PI
- Dutch        for component EA-APPL
- Dutch        for component EA-DFPS
- Dutch        for component EA-FINSERV
- Dutch        for component EA-GLTRADE
- Dutch        for component EA-HR
- Dutch        for component EA-IPPE
- Dutch        for component EA-PS
- Dutch        for component EA-RETAIL
- Dutch        for component ECC-DIMP
- Dutch        for component ERECRUIT
- Dutch        for component FI-CA
- Dutch        for component FI-CAX
- Dutch        for component FINBASIS
- Dutch        for component INSURANCE
- Dutch        for component IS-CWM
- Dutch        for component IS-H
- Dutch        for component IS-M
- Dutch        for component IS-OIL
- Dutch        for component IS-PS-CA
- Dutch        for component IS-UT
- Dutch        for component LSOFE
- Dutch        for component PI_BASIS
- Dutch        for component SAP_ABA
- Dutch        for component SAP_AP
- Dutch        for component SAP_APPL
- Dutch        for component SAP_BASIS
- Dutch        for component SAP_BW
- Dutch        for component SAP_HR
- Dutch        for component SEM-BW
- Dutch        for component ST-PI
Please mount another Language Disk for these language(s).
If you do not have further Language Disk(s), you may
continue, but the languages mentioned above will be lost
after the upgrade. A full language import has to be
performed after the upgrade to reinstall the language(s).
? continue
? cancel

Hi Markus,
I've introduce the following information:
> MOUNT POINT 07 = S:\export\Data\CDLAN2
> MOUNT POINT 01 = S:\export\Data\KN_WINDOWS_X86_64_AUPG
> MOUNT POINT 06 = S:\export\Data\CDLAN1
> MOUNT POINT 05 = S:\export\Data\CD3
> MOUNT POINT 03 = S:\export\Data\CD1
> MOUNT POINT 08 = S:\export\Data\UMN_WINDOWS_X86_64
> MOUNT POINT 02 = S:\export\Data\KN_WINDOWS_X86_64
> MOUNT POINT 04 = S:\export\Data\CD2
And in mount point 06/07 we have the languages.
The content of the trace file is:
here's the complete trace:
2007/07/05 16:35:01 *****************************
2007/07/05 16:35:01 Checking directories ...
2007/07/05 16:35:01 Searching for Data Carrier labeled AOXUPGR
Adding path: S:\export\Data\KN_WINDOWS_X86_64_AUPG
2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64_AUPG ... no matching label
Adding path: S:\export\Data\KN_WINDOWS_X86_64
2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64 ... no matching label
Adding path: S:\export\Data\CD1
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD1
Adding path: S:\export\Data\CD1\UPG1
Adding path: S:\export\Data\CD1\UPG2
Adding path: S:\export\Data\CD1\UPG3
Adding path: S:\export\Data\CD1\UPG4
Adding path: S:\export\Data\CD1\UPG5
Adding path: S:\export\Data\CD1\UPG6
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD1 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG4 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG5 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG6 ... no matching label
Adding path: S:\export\Data\CD2
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD2
Adding path: S:\export\Data\CD2\UPG7
Adding path: S:\export\Data\CD2\UPG8
Adding path: S:\export\Data\CD2\UPG9
Adding path: S:\export\Data\CD2\UPG10
Adding path: S:\export\Data\CD2\UPG11
Adding path: S:\export\Data\CD2\UPG12
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD2 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG7 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG8 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG9 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG10 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG11 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG12 ... no matching label
Adding path: S:\export\Data\CD3
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD3
Adding path: S:\export\Data\CD3\UPG13
Adding path: S:\export\Data\CD3\UPG14
Adding path: S:\export\Data\CD3\UPG15
Adding path: S:\export\Data\CD3\UPG16
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD3 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG13 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG14 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG15 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG16 ... no matching label
Adding path: S:\export\Data\CDLAN1
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN1
Adding path: S:\export\Data\CDLAN1\LANG1
Adding path: S:\export\Data\CDLAN1\LANG2
Adding path: S:\export\Data\CDLAN1\LANG3
Adding path: S:\export\Data\CDLAN1\LANG4
2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN1 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG4 ... no matching label
Adding path: S:\export\Data\CDLAN2
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN2
Adding path: S:\export\Data\CDLAN2\LANG5
Adding path: S:\export\Data\CDLAN2\LANG6
2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN2 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG5 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG6 ... no matching label
Adding path: S:\export\Data\UMN_WINDOWS_X86_64
2007/07/05 16:35:01 Working on S:\export\Data\UMN_WINDOWS_X86_64 ... no matching label
Regards,
A.Kamel

SAP BW upgrade problem in phase lang_select

Hello everybody,
during our upgrade from SAP BW 3.0B to 3.5 a problem occurred in the phase lang_select running PREPARE. Unfortunately we did not find any up-to-date SAP note on this, except in the note (212481), where the symptom is descried quite well, but the solution does not fit. By the way, the folder-names are already in upper-case (a different note told to do so). So I would be glad if anybody who does have any experience with upgrading from 3.0B could take a look at our problem as described below.
First of all our system information:
SAP Kernel 640 PL 115
OS: IBM AIX 5.2.0
DB: DB2 V8 FP 10
actual release of SAP BW: 3.0B
target release of SAP BW: 3.5 SR1
R3trans: 6.13 (release 640)
Tp: 340.16.12 (release 640)
Problem: PREPARE, phase lang_select
>> 08:56:19 PREPARE: START OF PHASE LANG_SELECT
working on /software/51030722/LANG1 ...
working on /software/51030722/LANG2 ...
working on /software/51030722/LANG3 ...
The following language(s) could not be updated yet:
- German for component PI_BASIS
- German for component SAP_ABA
- German for component SAP_BASIS
- German for component SAP_BW
- English for component PI_BASIS
- English for component SAP_ABA
- English for component SAP_BASIS
- English for component SAP_BW
Please mount another Language Disk for these language(s).
You need at least CDs which satisfy the vector "DE"
(standard languages) for all components.
It is not allowed to omit this update.
What we did until the message comes up:
- all by SAP recommended preparations on the OS, the DB and SAP BW 3.0B have been successfully implemented (as described in Component Upgrade Guide SAP BW 3.5 SR1)
- we copied all the data from CD/DVD into directories on the server
- we copied the fix FIX_WEBAS640SR1.SAR into /usr/sap/put/, which is required by PREPARE later on (SAP note 663240)
- start of PREPARE on the command-line (the directory /usr/sap/put/ is now filled with files and subdirectories are created)
- overwriting R3trans and Tp with the newest versions (as mentioned at the beginning)
- executing UaServer on the AIX, accessing the tool via web browser from a client
- in the applet we start PREPARE
- making entries for PREPARE
- lang_select
We did also examine the logs, here is what they say:
R3upchk.log
UPGRADEPHASE LANG_SELECT
...started at 20060308085619
Phase log file: 'LANGSEL.LOG'
Condition #if 1 >= 0
is evaluated as a TRUE expression, total status is TRUE, stack level 1
...begin dialogue at 20060308085623
Langsel.log
1 ETQ201XEntering upgrade-phase "LANG_SELECT" ("20060308085619")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '10', GwService = 'sapgw10'
4 ETQ399 Environment variables:
4 ETQ399 dbs_db6_schema=SAP1
4 ETQ399 auth_shadow_upgrade=0
4 ETQ380 computing toolpath for request "TP_LANG_SELECT"
4 ETQ381 request "TP_LANG_SELECT" means "create cofile in phase TP_LANG_SELECT"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETG880 Language data requested for "" (without standard languages "DE")
4 ETQ359 RFC Login to: System="1", Nr="10", GwHost="sap1", GwService="sapgw10"
4 ETQ232 RFC Login succeeded
cdtrace.log
2006/03/08 08:56:19 Searching for Data Carrier labeled LANGUAGE
 Adding path: /software/51030783
2006/03/08 08:56:19 Resolving directory structure below /software/51030783
 Adding path: /software/51030783/UM1
 Adding path: /software/51030783/UM2
2006/03/08 08:56:19 Directory structure below /software/51030783 resolved
2006/03/08 08:56:19 Working on /software/51030783 ... no matching label
2006/03/08 08:56:19 Working on /software/51030783/UM1 ... no matching label
2006/03/08 08:56:19 Working on /software/51030783/UM2 ... no matching label
 Adding path: /software/51030777
2006/03/08 08:56:19 Resolving directory structure below /software/51030777
 Adding path: /software/51030777/UPG1
 Adding path: /software/51030777/UPG2
 Adding path: /software/51030777/UPG3
2006/03/08 08:56:19 Directory structure below /software/51030777 resolved
2006/03/08 08:56:19 Working on /software/51030777 ... no matching label
2006/03/08 08:56:19 Working on /software/51030777/UPG1 ... no matching label
2006/03/08 08:56:19 Working on /software/51030777/UPG2 ... no matching label
2006/03/08 08:56:19 Working on /software/51030777/UPG3 ... no matching label
 Adding path: /software/51030630
2006/03/08 08:56:19 Working on /software/51030630 ... no matching label
 Adding path: /software/51030722
2006/03/08 08:56:19 Resolving directory structure below /software/51030722
 Adding path: /software/51030722/LANG1
 Adding path: /software/51030722/LANG2
 Adding path: /software/51030722/LANG3
2006/03/08 08:56:19 Directory structure below /software/51030722 resolved
2006/03/08 08:56:19 Working on /software/51030722 ... no matching label
2006/03/08 08:56:19 Working on /software/51030722/LANG1 ... matches -> added to result list.
2006/03/08 08:56:19 Working on /software/51030722/LANG2 ... matches -> added to result list.
2006/03/08 08:56:19 Working on /software/51030722/LANG3 ... matches -> added to result list.
 Adding path: /software/51030769
2006/03/08 08:56:19 Resolving directory structure below /software/51030769
 Adding path: /software/51030769/K01
 Adding path: /software/51030769/K02
 Adding path: /software/51030769/K03
 Adding path: /software/51030769/K04
 Adding path: /software/51030769/K05
 Adding path: /software/51030769/K06
 Adding path: /software/51030769/K07
 Adding path: /software/51030769/K08
2006/03/08 08:56:19 Directory structure below /software/51030769 resolved
2006/03/08 08:56:19 Working on /software/51030769 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K01 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K02 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K03 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K04 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K05 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K06 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K07 ... no matching label
2006/03/08 08:56:19 Working on /software/51030769/K08 ... no matching label
 Adding path: /software/51030865
2006/03/08 08:56:19 Working on /software/51030865 ... no matching label
Well, we actually do not know what the problem is. It seems to us that the program is not able to identify the language source files. The point is why did the source-paths for the other data work, as we copied the CD/DVD-data into folders? What is different with the language-CD?
Thanks a lot for your help,
Peter

I had the same problem but for upgrading SAP SOLUTION MANAGER 3.2 to 4.0 in the PREPARE PHASE "LANG_SELECT"
In the PEVALLAN.<SAPSID> ,I realized that the path for the required DVD I entered was too long !!
My real path was "C:\SAP_CDS\Upgrade_SOL4\51031485\51031485_1\SAP_CRM_LNG"
and the PEVALLAN FILE in the IV_LANGDIR parameter it was
""C:\SAP_CDS\Upgrade_SOL4\51031485\51031485_1\SAP_CR"
I've just shortened the path and it works now.
This surprised me because from the beginning of the PREPARE phase, I had no problems with that kind of thing.

Not Getting SAPKINBC9A upgrade patch for PI_BASIS

Hi All,
I am implementing SPS 12 in my ECC 6.0 System. System is on oracle and linux. My PI_BASIS patch is on 2005_1_700 level and i need to upgrade the same on 2006-1_700. So i cannnot import any of 2006 patch before this component
I am not getting the support pack SAPKINBC9A on OSS. Am i searching right patch or do i need to implement some other patch for this.
Thanks in Advance
Thanks,
Bhanu Pratap Singh

I got the patch. And i have implemented the same with SAINT.

EHP1 installation problem "No matching SAINT package for 'PI_BASIS' found"

Hi everybody,
i want update an Netweaver 2007 (SP14), BI, Dual Stack system to EHP1 (SP 5).
I use this manual during this installation:
(Update to NetWeaver EhP1)
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/808c3535-e378-2c10-83b4-cff07abef8e3&overridelayout=true
I've get all necessary support packages and the xml-file, put it into EPS-INBOX (Page 18 and Page 21) but i get the message "No matching SAINT package for 'PI_BASIS' found".
I know this was an issue, if you have SPAM 0036 (Note 1387523), but i've updated allready to 0037.
Have somone an idea?
Thanks a lot.

Hi,
please compare the SCA files for PI_BASIS are located in EPS/in
-rw-rr 1 c2badm sapsys 192917 Nov 9 18:05 K-70101INPIBASIS.SAR
-rw-rr 1 c2badm sapsys 353557 Nov 9 18:05 K-70102INPIBASIS.SAR
-rw-rr 1 c2badm sapsys 508062 Nov 9 18:05 K-70103INPIBASIS.SAR
-rw-rr 1 c2badm sapsys 393073 Nov 9 18:05 K-70104INPIBASIS.SAR
-rw-rr 1 c2badm sapsys 1222228 Nov 9 18:05 K-70105INPIBASIS.SAR
-rw-rr 1 c2badm sapsys 54524280 Nov 9 18:07 K-701DHINPIBASIS.SAR
with the entries in your .xml file like this:
<caption>PI_BASIS 7.01</caption>
 <ppms-number>01200615320200010570</ppms-number>
 <runtime-type>ABAP</runtime-type>
 <name>PI_BASIS</name>
 <version>701</version>
 <vendor>sap.com</vendor>
 <support-package>
 <caption>PI_BASIS Support Package 01 for 7.01</caption>
 <name>SAPK-70101INPIBASIS</name>
 <vendor>sap.com</vendor>
 <ppms-number>01200615321100046953</ppms-number>
 <sp-level>000001</sp-level>
 <patch-level>0</patch-level>
 <archives>
 <archive-name>K-70101INPIBASIS.SAR</archive-name>
 </archives>
 </support-package>
 <support-package>
 <caption>PI_BASIS Support Package 02 for 7.01</caption>
 <name>SAPK-70102INPIBASIS</name>
 <vendor>sap.com</vendor>
 <ppms-number>01200314691100043507</ppms-number>
 <sp-level>000002</sp-level>
 <patch-level>0</patch-level>
 <archives>
 <archive-name>K-70102INPIBASIS.SAR</archive-name>
 </archives>
 </support-package>
and so on ...until SAPK-70105INPIBASIS
finally the AddOn Package:
<support-package>
 <caption>PI_BASIS 701 Upgrade</caption>
 <name>SAPK-701DHINPIBASIS</name>
 <vendor>sap.com</vendor>
 <ppms-number>01200314691100040643</ppms-number>
 <sp-level>0000</sp-level>
 <patch-level>0</patch-level>
 <archives>
 <archive-name>K-701DHINPIBASIS.SAR</archive-name>
 </archives>
 </support-package>
 </software-component>
Gerd

XML configuration file does not show entry for PI_BASIS for PREPARE

Hello SAP Gurus,
We are doing ECC 6.0 SR3 upgrade including EHP3 SP3
We generated XML configuration file for EHP3 from MOPZ
But during XML file does not contains any information for PI_BASIS target level or source level
current level is 2006_1_620
We tried that XML file in PREPARE during EHP_INCURSION phase
but failed all time.
Let me know what we have to generate XML file with proper information including PI_BASIS
Even PI_BASIS not appearing in MOPZ list for selection, its surprising for us.
Any idea/direction would be highly appreciated.
Thanks,
Amit Lal

Hi,
I forwarded my query to AGS Dev support, They verified Solution manager and found no problem since it was up to date SPS15 ST400
Problem was in SAPup, they provide the lastest sapup tool that was again released for this specific problem. See notes for SAPup with keyword EHP
thanks,
Amit

Need the note for 632429 in sap basis

my friend working in sap bw server got an error where to see the sap note this number please reply

Hi,
You need to look in service.sap.com.
You'll need to have userid & pwd for this. Check with your basis consultant to provide one for you.
Check the note details for now.
Summary
Symptom
This note concerns additions to the system switch or component upgrade, and an ADD-ON component that existed before the upgrade.
It also refers to errors in the guide or problems during the upgrade that only occurred after the guide was created.
Other terms
Add-On, ADD_ON, ADDON, ADDON_INFO, PREPARE
R/3 Enterprise
Reason and Prerequisites
You want to perform a system switch or component upgrade and have already installed an add-on component in your system.
The ADDON_INFO PREPARE phase (in the 'initialization' PREPARE module) recognized this prerequisite and this composite SAP note was created as a result.
Use the list below to check if one or more of the add-ons in the list are installed in your system.
The attached note contains other important information you require for the system switch or component upgrade.
If your system contains an add-on of an SAP software partner, the upgrade will always refer you to this note. Contact the vendor of the partner add-ons to receive additional information about the upgrade, if necessary.
Solution
This note is updated on a regular basis;
obtain the latest version before you start the upgrade.
History (LIFO) 24.04.2007 AOFTOOLS 400_710
08.12.2006 AUTOID_INT
03.11.2006 DBM 600, DBMC 100
10.10.2006 RCX 600, FCX 600, DDS 600
27.09.2006 DMIS
04.08.2006 IS-M/AMC 200
14.07.2006 NRX 306_600, 305_500
12.07.2006 OSEM 500, RCXEM 500
05.07.2006 REBK01 250, REBKXL 100, REBKXL 470
30.06.2006 FINBASIS, SEM-BW
12.04.2006 AOFTOOLS 351, 400
13.03.2006 BANK-ALYZE
06.03.2006 EA-IPPE
02.03.2006 KJCHM 601
24.02.2006 BI_CONT 353, 702, 703
06.02.2006 OSEM 410, RCXEM 410
24.11.2005 IS-PS-XT 600
04.10.2005 ISREA 510
12.01.2005 SLL_PI, ST-PI 003C, ST-PI 2005_1
15.12.2004 ECC-DIMP 500, P3A V500
20.10.2004 C-CEE, HR-CEE
28.09.2004 SLL-LEG
24.06.2004 WP-PI, PI_BASIS
04.06.2004 LSOFE, ERECRUIT, WFMCORE
03.03.2004 ECC 500
16.07.2003 CSC-ABPL, HR-KR+CN
16.06.2003 BANK/CFM 463_20
16.06.2003 Release note
SAP ERP Central Component 600 (ECC 600) ADD-ON RELEASE NOTE
NRX 306_600 954621
IS-PS-XT 600 890090
KJCHM 601 921295
EA-IPPE 400 914554
REBK01 250 960415
RCX 600 973274
FCX 600 973273
DDS 600 973272
DBM 600 983872
DBMC 100 983872
SAP ERP Central Component 500 (ECC 500)
Note 700778 contains a constantly updated list of all add-ons that are integrated in ECC 500 - this note contains references to the add-on specific information for the upgrade.
ADD-ON RELEASE NOTE
NRX 305_500 924462
ISREA 510 882097
SCM_BASIS 410 753272, Section I
WP-PI 723189, 789554
C-CEE 105_500 574102
HR-CEE 105_500 776578
ECC-DIMP 500 717818
P3A V500 778122
SLL_PI 700779
ST-PI 003C 606041
ST-PI 2005_1 769519
MRSS 500 889961
EA-IPPE 300 914554
AUTOID_INT 884658, 738424
You use SCM 5.0.
ADD-ON RELEASE NOTE
OSEM 500 952165
RCXEM 500 952166
You use SCM 4.1.
ADD-ON RELEASE NOTE
OSEM 410 919794
RCXEM 410 922117
EA-IPPE 300 914554
Solution Manager 4.0
ADD-ON RELEASE NOTE
ST 310 892412
ST 320 892412
ST-SUP 310 892412
ST-SUP 320 892412
ST-SER 892412
TMWFLOW 320 892412
CPROJECTS 310_620 892412
ST-ICO 892412
Web Application Server 620
ADD-ON RELEASE NOTE
DMIS 2006_1_620 970534
DMIS_CNT 2006_1_620 970539
NetWeaver 2004
ADD-ON RELEASE NOTE
AOFTOOLS 351 736572
BI_CONT 353 774933
ERECRUIT 300 717803
DMIS 2006_1_640 970534
DMIS_CNT 2006_1_640 970539
LSOFE 300 718625
WFMCORE 110_640 718627
WP-PI 723189, 789554
SLL-LEG 300_640 754698
ST-PI 003C 606041
ST-PI 2005_1 769519
FINBASIS 300 718455
SEM-BW 400 718455
NetWeaver 2004s
ADD-ON RELEASE NOTE
AOFTOOLS 400 921103
BI_CONT 702 847019
BI_CONT 703 916834
BANK-ALYZE 50 920370
DMIS 2006_1_700 970534
DMIS_CNT 2006_1_700 970539
FINBASIS 600 852448
MDM_TECH 555_700 1024362
SEM-BW 600 852448
SLL-LEG 700 853060
SLL-LEG 710 970465
IS-M/AMC 200 965483
SAP NetWeaver 7.1 (AS ABAP)
ADD-ON RELEASE NOTE
AOFTOOLS 400 921103
R/3 Enterprise Extension Set 2.0 (R/3 47x200)
Note 625318 contains a constantly updated list of all add-ons contained in R/3 Enterprise 47x200 - this note contains references to the add-on-specific information for the upgrade.
ADD-ON RELEASE NOTE
BANK/CFM 463_20 352072, section II(8)
CSC-ABPL 606860, 159979, 640520
HR-KR+CN 159979, 549368, 535649, 351062
RBD see Note 625318
ST-PI 003C 606041
ST-PI 2005_1 769519
EA-IPPE 200 914554
Regards, Siva

How to add pictures in CCM for items in SRM_EXTRAXTED_CATLG

Hi guys (and girls of course),
Best wishes for 2007 for all of you.
I've got following issue I've been struggling with: I'm trying to add a picture to items in CCM, but for items coming from R3 (replicated to SRM). I want to use the standard PICTURE/URL field for this ('complex' data type)
(procedure for uploading R/3-materials is currently already working)
I've been checking out following BADI's:
/CCM/IF_EX_CTLG_ENRICHMENT~ENRICH_ITEM
I have found an example for implementing this in another thread and this seems to work for 'simple' characteristics, eg /CCM/CONTRACT_ID as mentioned in the example)
IF_EX_BBP_CCM_CHAR_MAINT~VALUATE_PRODUCT
for additional customer-characteristics this works fine, also for simple standard characteristics (eg /CCM/MPN) this works fine.
But in both cases i seem to be unable to fill the complex characteristic /CCM/PICTURE (subfield /CCM/URL). I tried to use the same syntax as in the CSV-load file (ie /CCM/PICTURE#/CCM/URL) but it's not working as i expect.
When i add this info manually to the field, the picture shows as expected. (But adding this info manually is not an option of course.)
Any thoughts or hints would be greatly appreciated.
Some additional information
SAP_ABA 700 0009 SAPKA70009
SAP_BASIS 700 0009 SAPKB70009
PI_BASIS 2005_1_700 0009 SAPKIPYJ79
ST-PI 2005_1_700 0001 SAPKITLQI1
SAP_BW 700 0009 SAPKW70009
SAP_AP 700 0006 SAPKNA7006
CCM 200_700 0005 SAPK-27005INCCM
SRM_PLUS 550 0006 SAPKIBK006
SRM_SERVER 550 0006 SAPKIBKT06

Hi ,
I was not active on SDN for some time hence did not see yr thread.
We had used SRM_EXTRACTED_CATALOG in our earlier project and managed to get pictures for all the items in shopping.
The path we took:
with the report BBP_CCM_TRANSFER_CATALOG get the SRM_EXTRACTED_CATALOG in CAT
map the relevant categories in SRM_EXTARCTED_CATALOG to /CCM/MASTER_CATALOG.
import all the picture JPEG files for all the items in the MIME of server
SE80->MIME repository -> drill down to BSP/SAP/BC/CCM (sorry i don't remember the exact path and I don' t have the system now) -> create yr own folder-> import all the JPEG files to this folder.
now derive a URL for each item in a format: http:
server name.domain name\services (sap\bc\bsp\cat\yr folder name\file name)
validate this URL in IE
it should derive the picture from the MIME of yr server and show you on screen
now go to mastrer catalog ->open the chara "image" for each item -> paste this url and type (JPEG) -> and save the item
this should give picture of each item when you are shopping in EBP as preview and in detail also
it's somewhat cubersome to paster those URLs but it's one time activity.
Helpful?
BR
Dinesh
reward if helps

Download of ABAP Support Packages for SAP Netweaver PI 7.1

Hello all,
I'm just working on upgrade SAP Netweaver PI 7.0 to PI 7.1 and we have no functional connection to SAP OSS and therefore I'm not able to aprove some Support Packages via Solution Manager.
PLEASE - Can somebody download the following Support Packages and copy it via ftp:
BW Support Package 06 for 7.10 - SAPKW71006
BW Support Package 05 for 7.10 - SAPKW71005
Basis Support Package 06 for 7.10 - SAPKB71006
Basis Support Package 05 for 7.10 - SAPKB71005
ABA Support Package 06 for 7.10 - SAPKA71006
ABA Support Package 05 for 7.10 - SAPKA71005
PI_BASIS 2006_1_710: patch 0006 - SAPKIPYN06
PI_BASIS 2006_1_710: patch 0005 - SAPKIPYN05
FTP data:
server: ftp.vse.sk
username: sap
password: Supp0rtpack
Thanks for your time and help.
Best regards,
Slavomir Kysel.

Solved by SAP Walldorf.

PI_BASIS 2006_1_640 for SAPKW35018

Similar Messages

Maybe you are looking for