Where to find a NetWeaver BW/BI 7.x Frontend Support Package
2009-12-03 11:19
381 查看
SAP NetWeaver BW/BI Frontend SPs/FEPs packages are self executable files. They can either directly installed in the client machines or in an installation server to be later distributed. These self executable files contain different binaries of type .dll, .exe, .ocx etc..
The Frontend SPs/FEPs are available in the SAP Service Marketplace with the following naming convention and the given location.
BI[XX]SP[YY]_[YY][ZZ]-GUID.exe
[XX] - Final Release number
[YY] - Support Package number
[ZZ] - Patch number
GUID - Globally Unique Identifier
E.g. you can see the Frontend SP 1000 as 'bi710sp10_1000-10004472.exe'. The GUID will be same for all the SPs/FEPs in one release planning. So all the patches under the SAP GUI 710 release, will have the same GUID.
Note 1231363 describes the 'Delivery Strategy' and the naming/numbering convention of BW/BI Frontend SPs and FEPs:
BW/BI Frontend SP: number ending with '00' (e.g. 1000)
-> for "Early Adopters" (fully tested)
BW/BI Frontend Patch: number ending with '01' (e.g. 1001)
-> recommended version (fully tested & additionally validated)
The Frontend SPs/FEPs are available in the SAP Service Marketplace with the following naming convention and the given location.
BI[XX]SP[YY]_[YY][ZZ]-GUID.exe
[XX] - Final Release number
[YY] - Support Package number
[ZZ] - Patch number
GUID - Globally Unique Identifier
E.g. you can see the Frontend SP 1000 as 'bi710sp10_1000-10004472.exe'. The GUID will be same for all the SPs/FEPs in one release planning. So all the patches under the SAP GUI 710 release, will have the same GUID.
Note 1231363 describes the 'Delivery Strategy' and the naming/numbering convention of BW/BI Frontend SPs and FEPs:
BW/BI Frontend SP: number ending with '00' (e.g. 1000)
-> for "Early Adopters" (fully tested)
BW/BI Frontend Patch: number ending with '01' (e.g. 1001)
-> recommended version (fully tested & additionally validated)
相关文章推荐
- Note 1049712 - Applying SPs / Patches for SAP NetWeaver BW/BI Frontend
- Test run failed: Unable to find instrumentation target package: android.support.v7.appcompat
- "Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.
- Preview of BI 2012 with Speaker Dan Kearnan: Expect SAP NetWeaver BW to Run Soon on SAP HANA
- Android Studio "Error:Failed to find: com.android.support:XXXX"错误解决办法
- android studio 报错"Failed to find: com.android.support:appcompat-v7:10.+"
- How To Find Where The Memory Is Growing For A Process (Doc ID 822527.1)
- End to End Sequence Labeling via Bi-directional LSTM CNNs CRF
- error: memcached support requires ZLIB. Use --with-zlib-dir=<DIR> to specify the prefix where ZLIB
- 解决 ECMall 错误 Call to a member function get() on a non-object in frontend.base.php
- Use Java reflection to find classes that implement an interface from a package
- xcrun: error: unable to find utility "PackageApplication", not a developer tool or in PATH
- Xcode脚本自动化打包问题:xcrun: error: unable to find utility "PackageApplication", not a developer tool or in PATH
- ros-indigo卸载不全,出现The package <package name> needs to be reinstalled, but I can’t find an archive for
- front-end:map ,jump to some area
- 8 Tips To Become A Better Front End Developer
- xcrun: error: unable to find utility "PackageApplication", not a developer tool or in PATH
- Error:Failed to find: com.android.support:appcompat-v7:21.+
- OPAM failed to install CIL because computer cannot find package Ocamlfind
- 解决Android Studio打开别人包时出现Failed to find: com.android.support:appcompat-v7:21.