SP14 for BW

Hi,
We have SP10 for SAP_BW and we want to upgrade to SP14 , which dependency exist with other components, if we upgrade to SP14 for SAP_BW , we must upgrade other components like SAP_ABA , SAP_BASIS and other components?
Wich time take to upgrade SAP_BW from SP10 to SP14?
Best regards
Zied

Hello Zied ,
Select the Support Pack for example in my case I am planning to apply SAPKW70017 .
In download menu you will found the header:
File Type | Download Object | Title | Info File | File Size | Released On
Select the option info , you will found the details ( Package Attribute ).
Check the ( Package Import Conditions ) you will found the Condition , where you can list pre-requisite of SAPKW70017.
Regards,
Santosh

Similar Messages

Error while applying J2EE SP14 for 640 system

Hi,
I am facing issue while applying J2EE SP14 for 640 system. The current level is SP9. Below is the error. Can you recommand any resolution for the same.
ERROR 2005-03-04 14:23:47
CJS-20076 Error while retrieving the mode of the J2EE Engine. See output of logfile C:\Program Files\sapinst_instdir\PATCH\MSS/getEngineMode.log: 'Error while loading BatchConfig C:\Program Files\sapinst_instdir\PATCH\MSS/getSafeMode.xml definition file.
java.lang.Exception: Unknown Task information
     at com.sap.engine.configtool.batch.descriptor.BatchConfigDescriptorDocument.readDescriptorFromDocument(BatchConfigDescriptorDocument.java:121)
     at com.sap.engine.configtool.batch.descriptor.BatchConfigDescriptorDocument.readDescriptorFromDocument(BatchConfigDescriptorDocument.java:94)
     at com.sap.engine.configtool.batch.descriptor.BatchConfigDescriptor.loadFromFile(BatchConfigDescriptor.java:66)
     at com.sap.engine.configtool.batch.BatchConfig.main(BatchConfig.java:74)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:78)
WARNING 2005-03-04 14:23:47
The step checkIfSafeModeIsEnabled with step key ApplySupportPackage|ind|ind|ind|J2EE_Engine|6.30|0|PatchJ2eeEngine|ind|ind|ind|J2EE_Engine|6.30|0|checkIfSafeModeIsEnabled was executed with status ERROR.

hi Atul,
Welcome to SDN!
This problem occurs due to unexpectedly high CPU usage. Check the SAP OSS Notes (from Service Market Place) <a href="https://websmp203.sap-ag.de/form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200000309362004">743207</a> and <a href="https://websmp203.sap-ag.de/form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200000300342004">742395</a>
They will help you to solve the problem.
Regards
ak

Prepare EP for ESS(MSS)

Hi, guru!
I'm prepare Portal for ESS(MSS)/EP <-> HR/ECC configuration.
HR:
ECC 6.0 sp14
all packages 600 sp14
EA-HR up to 603 sp10
EP:
nw7.0 sp14
for ess/mss deployed in additional:
SAPPCCUI_GP 600
SAP ESS 600
SAP MSS 600
BPERP5ESS14
BPERP5MSS14
BPERP5***14
BPERP5HRA14
BPERP5COM14
q: SAPPCCUI_GP 600 SAP ESS 600 SAP MSS 600 - ok? or up to 603?
Best Regards,
Vlad

if backend is on EHP4 then frontend should be on EHP4 as well
ie EA Hr 604 then sap _ess 603
check these
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=31476
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES

What is the table for query name

Hi All,
I need an urgent requirement for removing duplicate technical query names from the production. Since there are few issues with the SAP given program I am customizing the SAP Program. Can any one tell me what is the table where the QUERY NAME and it's technical name can be found?
Thanks,
Alex.

hi Alex,
try RSRREPDIR, RSZCOMPDIR.
there is one oss note all the tables.
Table containing Work Book and query relation
Query Detailes
oss 792779
Symptom
Report ANALYZE_RSZ_TABLES is designed as a check-tool for detecting and solving different types of inconsistencies in the main query definition database tables.
The program is recommended for BW system administrators.
Other terms
Query definition, query, reusable, component, variable, missing elements, missing records, missing UID, INCONSISTENCY, RSZELTDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZCALC, RSZSELECT, RSRREPDIR.
Reason and Prerequisites
ATTENTION: the described version of the program is delivered with the following Support Packages:
SP27 for release BW 3.0B
SP21 for release BW 3.1C
SP13 for release BW 3.5
All versions of this report available in systems before those Support Packages are test versions which can be used only for information purposes.
Check prerequisites
Checks are possible only for elements in object version 'A' (active) and 'D' (delivered).
Checks for query elements in 'D' version are possible only in the systems which are set as content.
Checks description
Report performs checks in the tables containing the parts of the definitions of queries and query components: RSRREPDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZELTDIR and RSZELTXREF.
1. Table RSRREPDIR
The table RSRREPDIR is a header table of the generated reports. Consistency of query definition in this table allows to select a query in the Open Dialogs of fronted application and to call report generated for this particular query using transaction RSRT.
The following errors can be found:
- queries with missing definition;
- queries with missing GENUNIID;
- queries with technical names different than in RSZCOMPDIR;
- non-queries in the table.
1.1 Queries with missing definition
The queries are available only in the table RSRREPDIR and not found in the table RSZELTDIR in the corresponding object version. Such queries (in active version) can be accessed only from RSRT transaction. An attempt to execute such query will return the short dump 'Exception condition INCONSISTENCY'. The error also happens during query generation in RSRT or during mass regeneration of the queries using RSR_GEN_DIRECT_ALL_QUERIES report or application menu of transaction RSRT. The inconsistent queries can not be repaired because of missing query definitions. The recommended solution is to delete those records in order to avoid the possible system dumps.
1.2 Queries with missing GENUNIID
Queries having empty GENUNIID field in the table RSRREPDIR. Such queries may be available in the frontend and in RSRT transaction. An attempt to execute such query will return the message'GENUNIID not found'. Situation requires additional investigation at SAP. Create an OSS message for BW-BEX-ET-QDEF.
1.3 Queries with technical names different than in RSZCOMPDIR
The check outputs the queries which have different technical names in the RSRREPDIR and RSZCOMPDIR tables. Execution of a query using the technical name given in Query Designer and stored in the table RSZCOMPDIR will return the error message 'GENUNIID not found'. The system tries to find the corresponding GENUNIID for the wrong COMPID which does not exist in the system or which belong to another query. The recommended solution is to correct the wrong COMPID in the table RSRREPDIR via corresponding procedure.
1.4 Non-queries in the table
The table RSRREPDIR normally contains only reports. Query elements of other types should not exist in this table and can be deleted. In case, when such records exist in the table an attempt to access them in RSRT returns the error message 'GENUNIID not found'. The recommended solution is to delete those records from the table using the corresponding procedure.
2. Table RSZCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for queries and other reusable query components (STR, RKF and CKF).
The following errors can be found:
- local elements in RSZCOMPIC;
- components with inconsistent definition;
- components based on non-existing InfoProviders;
- components based on non-active InfoProviders.
2.1 Local elements in RZSCOMPIC
The table RSZCOMPIC contains an InfoProvider assignment for the reusable components. The local elements and also variables have no InfoProvider assignment and should not exist in this table. Those elements can be deleted via corresponding procedure.
2.2 Components with inconsistent definition
The reusable queries or query components existing in the table RSZCOMPIC, but not found in the table RSZELTDIR. Those reusable components may return 'Exception condition INCONSISTENCY' dump during accessing/execution. The situation may have different outcomes and has to be investigated at SAP. Create an OSS message for BW-BEX-ET-QDEF.
2.3 Components based on non-existing InfoProviders
Queries or query components are assigned to the InfoProviders which do not exist anymore in the system. Queries without InfoProvider are not available in Open Dialogs of frontend applications, but can be executed in RSRT. The execution will return the error message'InfoProvider not found'. The recommended solution is to delete the unnecessary components. Deletion of these queries or query components can be done directly from the list using corresponding procedure similar to RSZDELETE transaction.
2.4 Components based on non-active InfoProviders
Queries or query components which are assigned to the InfoProviders which do not exist in the system in the active version. Queries without active InfoProvider are not available in Open Dialogs of frontend applications. In case, an affected query is technically consistent, an attempt to execute it in transaction RSRT will return the message 'Activate the XXX InfoCube / InfoProvider again. Message #BRAIN 056'. Quite often this error is combined with other errors like missing GENUNIID in the RSRREPDIR or other inconsistencies. Each case has to be investigated in order to get the current status of this object. If the affected query is useless, it can be deleted from the system using transaction RSZDELETE.
The check is available only for the query elements in object version 'A' (active).
3. Table RSZCOMPDIR
The table RSZCOMPDIR is the directory table containing the main properties of all reusable components.
The following errors can be found:
- duplicated technical names (COMPID);
- components with inconsistent definition;
- components without InfoProvider assignment;
- components with missing OWNER.
3.1 Duplicated technical names (COMPID)
The check outputs queries or other reusable query components which have duplicated technical names (COMPID).
The error does not cause any dumps in ABAP or terminations in Query Designer, but may cause several symptoms in different reporting areas:
different queries are available in BEX Analyzer and RSRT under the same name;
wrong query is used as Data Source for Web Template (Web Reporting, Reporting Agent, Broadcasting, MDX);
replacement of variables does not work... etc.
The recommended solution is to provide a new technical name for the duplicated component using corresponding procedure.
ATTENTION: in case when there are only 2 components with the duplicated technical name, only one of those 2 components can be renamed using the corresponding procedure.
The alternative solution for renaming the duplicated technical names is to use the ABAP report RENAME_DUPLICATE_ELEMENTS.
3.2 Components with inconsistent definition
Reusable query components which are not found in the element directory table RSZELTDIR are displayed. This situation may cause the short dump 'Exception condition INCONSISTENCY' during accessing the affected component in Query Designer or execution the affected query in RSRT. Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.3 Components without InfoProvider assignment
All reusable query component (except variables) should be assigned to a particular InfoProvider. This assignment is located in the table RSZCOMPIC. When the record is not found in this table, the affected component may become not available in Query Designer in the corresponding InfoProvider. In some cases the error message "Component XXX.. (version A) has no InfoCube assignment". Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
3.4 Components with empty ONWER field
Reusable components which have empty OWNER field in the table RSZCOMPDIR are accessible by users having $USER setting in the authorization object S_RS_COMP1 (users which are authorized to their own queries or query components). This leads to authorization concept violation.
For error solution the field OWNER in the RSZCOMPDIR should be filled with any value. Execute the corresponding edit mode in order to fill the empty field with user 'SAP'. This will prevent the potential authorization violation for users with $USER setting and will take no effect on the users without this setting.
4. Table RSZELTXREF
The table RSZELTXREF contains all links and dependencies between the query elements within a query or query component.
The following errors can be found:
- missing elements (INCONSISTENCY dump);
- not supported relations between query elements;
- extended RSZELTXREF check.
4.1 Missing elements
Missing elements are those query elements which exist as the dependant objects (field TELTUID) in the table RSZELTXREF, but not available in the element directory table RSZELTDIR in corresponding object version. In case, when such elements are used in any query or other query components (STR, CKF or RKF), this may lead to ABAP short dump with 'Exception condition INCONSISTENCY' error message in query run-time or design-time. Other known symptoms of this error is, that structures, calculated key figures or restricted key figures are not available in an Info Provider in Query Designer during design-time.
The missing elements which are in use in other queries or query components, can not be automatically repaired or deleted without components where those elements are used. In most cases the manual repair operations directly in the DB tables are required. Create an OSS message for SAP component BW-BEX-ET-QDEF for further investigations and creation of a repair plan.
The missing elements which are not in use in any query or query components, can be deleted from the system via corresponding delete procedure. This deletion will not affect any existing query or query component.
ATTENTION: if missing element is variable, it can be repaired in some cases automatically using the corresponding repair procedure. See table RSZGLOBV check 5.1. 'Variables with inconsistent definition' for details.
4.2 Not supported relations between query elements
Some relations between query elements which are not supported and can cause dumps in ABAP or terminations in Query Designer (for example link STR <--> VAR). Such cases have to be additionally investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
4.3 Extended RSZELTXREF check
The extended RSZELTXREF check outputs 2 situations which, in combination with other conditions in the system, may be responsible for slow performance of all operations which involve select from the table RSZELTXREF and resolving the relations between query elements (query load, query generation, expanding of a variable list for corresponding InfoObject, expanding of a list of reusable components in Query Designer,... etc.):
- records with empty INFOCUBE field
- records which are not used in any query or query component
Records with empty INFOCUBE field
The current algorithm of resolving of relations between the query elements uses an optimization which allows to reduce the amount of data selected from the table RSZELTXREF during such operations are query load, query generate, expand a list of reusable components (STR, CKF, RKF) and so on. All relations between query elements within one reusable component based on one InfoProvider 'N' are also located within the same InfoProvider. The system has to select only records where the INFOCUBE field contain the same InfoProvider 'N' and in addition to this all other records where the INFOCUBE field is empty. This is necessary, because in all BW releases below 3.x the INFOCUBE field was not in the RSZELTXREF table and all components created before 3.x release have this field empty. Selection of records with empty INFOCUBE is required in order to ensure the consistency of processed query.
When the number of records with empty INFOCUBE is quite large (50.000 - 1 mln records), any simple operation which require resolving of the relations may take a long time, because those records are always being selected, loaded to Query Designer and processed in the design-time.
Records which are not used in any query or query component
The program makes a virtual attempt to reconstruct the table RSZELTXREF via resolving the relations between all reusable components existing in the system. All records which are not used in any query or query components are considered as non-used records. Usually these are fragments of old queries or other components which are not deleted due to former errors in the query delete algorithm.
The current version of the program contain only information about those 2 issues. See the OSS note 823804 for additional information.
ATTENTION: the extended RSZELTXREF check is recommended when all critical problems with reusable components are resolved and the system clean-up is done (no useless records in the tables, no useless non-executable queries or other affected query component available).
Starting from SP28 for BW 30B, SP22 for BW 31C and SP14 for BW 3.5 the Extended RSZELTXREF check detects and fixes the following situations:
records used in existing queries or query components with empty INFOCUBE field;
records used in existing queries or query components with wrong INFOCUBE assignment;
records with or without INFOCUBE assignment which are not used in any query or query component.
For further check details read the OSS note 859086.
5. Table RSZGLOBV
The table RSZGLOBV contains the definitions and technical properties of the variables.
The following errors can be found:
- variables with inconsistent definition;
- variables with missing or incorrect properties;
5.1 Variables with inconsistent definition. Variable not found in RSZELTDIR/RSZCOMPDIR tables.
The variable existing in the table RSZGLOBV, but not existing in the tables RSZELTDIR or RSZCOMPDIR have inconsistent definition. These situation may return 2 different error messages. When a variable is missing in RSZELTDIR table (or in both together), an attempt to expand a list of variable under a corresponding InfoProvider or a list of text/formula variables will return a message 'Inconsistency in loading...'. All variables which are created for corresponding InfoProvider, text/formula variable are not available. When a variable is missing in the RSZCOMPDIR table only the error message is 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded' in Query Designer.
In both cases the variables can be repaired via the corresponding procedure provided in the program under the technical name (COMPID) corresponding to the name in VNAM field in the table RSZGLOBV with the text 'REPAIRED BY SAP'.
As an alternative solution, when the affected variables which are not used in any query or query component can be deleted directly from the RSZGLOBV table. Both solutions will fix the reported symptoms.
ATTENTION: it is recommended to open a repaired variable in Variable Wizard of Query Designer and to adjust the definition of this variable, when it is necessary.
ATTENTION: deletion of the affected variables missing in the table RSZCOMPDIR is not possible using transaction RSZDELETE. An attempt to delete such variable will return the error message 'Component not found'.
5.2 Variables with missing or incorrect properties
Several errors can be found within this check. The variables of different type have their own sets of properties. Missing or incorrect properties may cause different error message during execution of a query where such variables are in use. In the case of the affect variables with processing type 'replacement' , the replacement may not work because of the problem.
Each case has to be investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
6. Table RSZELTDIR
The table RSZELTDIR is the main directory table containing all query elements available in the system.
ATTENTION: the RSZELTDIR check may take a long running time depending upon the table size.
The following errors can be found:
- local elements not in use;
- reusable elements not in RSZCOMPDIR table;
- reusable elements not in RSZCOMPIC table;
- structure (STR) without structure members;
- selections or RKF without definition in RSZSELECT table;
- formulas or CKF without definition in RSZCALC table;
- variables (VAR) without definition in RSZGLOBV table;
- queries (REP) without entries in RSRREPDIR table.
6.1 Local elements not in use
Local elements (field REUSABLE = false) which are not used as dependant objects in the table RSZELTXREF. These elements are useless and not accessible from Query Designer. Usually these are fragments of the definitions of old queries accumulated in system because of different problems with save/delete procedures which are not accessible by the end users. The recommended solution is to delete those elements using the corresponding delete procedure.
6.2 Reusable elements not in RSZCOMPDIR table
Reusable elements (field REUSABLE = true) must have a corresponding entry in the table RSZCOMPDIR which contains the definition and properties of this reusable component. An attempt to load such component in Query Designer may cause the error message 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded'. Additional investigations are requires at SAP. Create an OSS message for BW-BEX-ET-QDEF.
ATTENTION: Deletion of such affected components is also not possible using transaction RSZDELETE. An attempt to delete will return the message 'Component not found'.
6.3 Reusable elements not in RSZCOMPIC table
Reusable elements (field REUSABLE = true), except variables (DEFTP = 'VAR'), must have a corresponding entry in the table RSZCOMPIC which contains an InfoProvider assignment for reusable components. When a reusable component has no InfoProvider assignment it may be not available in Query Designer during design-time. Additional investigations are required at SAP. Create an OSS message for BW-BEX-ET-QDEF. In case the affected component is useless, it can be also deleted from the system using transaction RSZDELETE.
6.4 Structures (STR) without structure members
Reusable and non-reusable structures (DEFTP = 'STR') should have dependant elements (structure members). When these structure members are not found a query containing this structure returns the error message 'Element structure not correct' during generation or execution in RSRT or BEx analyzer. The program outputs a query technical name where such structures are used or the technical name of an InfoProvider if the affected structure is reusable and not used in any query. In this case it can be accessed from any query created in the same InfoProvider in Query Designer. The solution is to open the affected structure in using the latest available version of Query Designer and to create the required structure members in order to avoid the error message.
In case, when the affecter structure is local (non-reusable) and is not used in any query, this structure is not accessible by frontend users and can be deleted from the system by corresponding procedure provided in the program.
6.5 Local selection of RKFs without records in RSZSELECT table
Local selections and reusable Restricted Key Figure (DEFTP = 'SEL') usually should have the corresponding records in the DB table RSZSELECT. The program outputs all selections found in the system which have no corresponding records in the RSZSELECT table.
Usually this issue has no impact on the existing queries and produces no error messages. There are 3 possible types of selections within a query:
Normal selection - this selection represents a characteristic in Row, Columns or Free Characteristics area, Conditions or Exceptions. This situation produces no error messages, but the selection is not taken into account by OLAP.
Dummy structure member - structure member type selection can be defined using Query Designer. Such structure member produces no selection and can be used only as place holder within a query. This situation produces no error messages during generation/execution of a query containing a structure with those dummy structure members.
Cell selection - this type of selection is usually used as Cell selection and can be defined using Cell Editor in Query Designer. This situation produces no error messages, but the selection is not taken into account by OLAP.
If it is necessary, the selection definition can adjusted using the latest available version of Query Designer. The affected local selections can be accessed from the queries presented in the WHERE-USED (INFOCUBE/QUERY). The Restricted Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local selection is not used in any query or query components the recommended solution is to delete this selection using the corresponding delete procedure.
6.6 Local formulas of CKFs without records in RSZCALC table
Local formulas (DEFTP = 'FML') or Calculated Key Figures (DEFTP = 'CKF') should contain definition of the calculations in the table RSZCALC. When such definition is not found in the table RSZCALC the queries or query components which include those affected objects can not be generated or executed by OLAP. An attempt to generate such query returns the error message 'The (sub) formula XXX... is not available'.
The definitions of the affected formulas or Calculated Key Figures can be adjusted using the latest available version of Query Designer. The adjustment of a local formula is possible from the corresponding query listed presented in the program. The Calculated Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
In case, when a local formula is not used in any query or query components the recommended solution is to delete this formula using the corresponding delete procedure.
6.7 Variables without records in RSZGLOBV table
Variables (DEFTP = 'VAR') should exist in the table RSZGLOBV. The table RSZGLOBV contains all processing properties and definition of the variables. Query where such variables are used can not be executed without problems.
The repair procedure is not possible, because of missing definition. In case, when such variable is not used in any query, the recommended solution is to delete it from the system in order to avoid potential problems. If the affected variable is already used in other queries or query components, create an OSS message for SAP component BW-BEX-ET-QDEF. Further investigations and possible repair plan have to be created at SAP.
6.8 Queries without records in RSRREPDIR table
Queries (DEFTP = 'REP') should exist in the table RSRREPDIR. The table RSRREPDIR is a header table of generated reports and also a part of the database view V_REP_JOIN which provides data for the BEx Open/Save Dialogs.
A query which does not exist in the table RSRREPDIR is not accessible via RSRT transaction (error message 'GENUNIID not found') and not displayed in the Open/Save Dialogs of fronted applications.
The recommended solution is to delete such queries using the corresponding procedure provided in the program and similar to RSZDELETE.
In some cases the repair procedure is also possible. The success of the repair procedure depends upon the consistency of the affected query, the existence of a valid InfoProvider for this query and some other factors. For repair attempt create an OSS message for the SAP component BW-BEX-ET-QDEF.
hope this helps.

Problem with creating links with the WPC (SP14)

Hi,
I have a problem creating links with the WPC (SP14): When I want to create internal links (Browse and select the target item) via the right button (choosing a website as a reference link). If I do so I encounter the problems either that the linked site (outside the WPC) shows a blue background and/ or has no navigation frame (on the left side & no breadcrumb-navigation on top).
If I create links with the left button in the WPC via URLs I have the problem with the inserted URL, because sometimes (I don't know why und when) some parts of the code in the URL changes, so that the linked Website is empty (besides the navigation fram - the content isn't displayed anymore). To me it looks like as if the originally website cannot be "found" anymore.
Does anyone has the same problems and is eventually able to help me? This would be really great. Thanks!

Hi,
you have also to deploy the following file from Service Marketplace:
Patch for SP14 for KMC WEB PAGE COMPOSER 7.00
Than it will works. The best way is you deploy WPC SP 15.
If you want i can send you this file via email.
regards,
Sharam
Edited by: Seed mopo on Apr 28, 2008 11:45 AM

Web Service on ECC 6.0 SP14

Hi everybody,
I have a message interface on PI 7.0.
I need to generate, from this interface, an asyncronous Web Service on ECC 6.0 SP14 for a direct connection without PI.
How can I do that?
hank you

Hi
if you want to create the web service using the function module do the following steps.
the main requirement for creting the web service using the function module is the function should be RFC enabled.
1. To create web service of this Function Module
Go to Utilities ->More utilities->create a web service->from function module
2. A new wizard will be open to create the web service and click on continue.
3. Enter the web service name (any name that you want to give) and give the short description, select the Endpoint type as Fuinction Module and click on continue.
4. Select the Function Module name that you are using.
5. select the profile as Basic Authentication: SOAP Pro.
6. Press continue to release the web service. The web service is now created
To check the web service Go to the transaction WSADMIN and select the node
SOAP Application for RFC-Complaint FMs and expand the node and select your web service that you have created and expand the web service node up to the last .
Now to test the web service select the last node and click on the web service home page button and it will open the home page.
from this page u will get the wsdl file as well as you can testthe web service.
Thanks
Rinku

Read Time Out Exception while generating PDF Document

Hi,
We are working on Netweaver 04,Patch SP 16 and trying to generate a Non Interactive PDF on ADS Version SP 14 for printing purpose (Eg.Invoice). This extracts data using EJBs. We used Interactive Form UI element which has various sub elements like static image, etc.
We are using Acrobat Reader 7.0 for generating PDF.
The form fetches the records and prints perfectly in the Development System, While creates a 'java.net.SocketTimeoutException: Read timed
out ' Exception in Production.
Time Out period for web service container is set to 180 sec in both Dev and Prod.
Default trace in the production is continously throwing following error."com.adobe.document.XMLFormService#com.adobe/AdobeDocumentServices#com.adobe.document.XMLFormService
Thread[XMLForm.exe Error Reader,5,SAPEngine_Application_Thread[impl:3]
_Group]##0#0#Error##Plain###Service XMLFormService: Native process
(PID=0) /usr/sap/NWP/JC00/j2ee/os_libs/adssap/XMLFormService/bin/XMLForm.exe terminated abnormally with error code 127# "
We are running following services in both Prod and Dev for using ADS.
1. IIOP Provider
2. Data Manager Service
3. Data Font Manager Service
4. XML Module
5. Document Services Configuration
6. Document Services License Support Service
Could some one please let us know what could be the problem?
Thanks And Regards,
Apeksha.

Hi Markus,
Thanks for the prompt reply. However, SAP notes 867502
and 811342 speak about PDF manipulation services, which we are not using in our application. We need to create non interactive form which simply reads the data from the DB and displays it to the users for printing.
The other 2 notes-826419 and 849851 talk about SP 10,11 and 12, while we are using SP14 for Adobe Services and SP 16 for Netweaver Java Stack.
The application works perfectly on the Development Server, but not on Production Server. Though all the configurations are same on both the servers, still can you suggest what all things need to be considered ?
Thanks and Regards,
Apeksha

Error in adapter specific message attributes

Hi guys,
I'm trying to dynamically assign a destination directory name by using the code..
DynamicConfiguration conf = (DynamicConfiguration) container
    .getTransformationParameters()
    .get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create(
    http:/"+"/sap.com/xi/XI/System/File,
    Directory);
String valueNew = "MyDirectory";
    conf.put(key, valueNew);
I'm getting a null pointer exception when i test this. When i tried to debug i found that my DynamicConfiguration object conf is null...
Can anyone tell me why is this happening???

Hi,
1. did you use the code from this blog:
/people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
2. you do have SP14 for XI 3.0 right ?
Regards,
michal

Regarding File name schema in Receiver com. Channel

Hello,
I have gone thru the blog
The specified item was not found.
"The same filename from a sender to a receiver file adapter - SP14 for Dynamic configuration" by Michal Krawczyk....And here in this Scenario in ID (in Reeiver communiation channel)what should we give as file name.(or) can we leave it blank.
If my client wants the name ,then instead of assigning it to the root can I consider a element and assign the udf...In this case how it will effect the Receiver file name schema in Rec Communication channel in ID

Hi,
Pass it as %FileName% which will come from dynamic configuration.
SAP note may give some hints- 746393 and also this thread has got the answer
Module Processor : Module exception java.lang.ClassCastException
Thanks
Swarup
Edited by: Swarup Sawant on Aug 22, 2008 11:19 AM

Content Management in KM

Dear Sir,
We use EP6 SP14, for the KM portal. May I know what is the date modifiaction of each folder defined?? because I found on my Portal server, the date in Modification of every folders are the same. When will update to the latest date?
Please kinly help.
Thnak you and best regards,
Vimol

Dear Sir,
Because there are a lot of folder, the top folder , modificated date was not changed. We have updated a lot of report , but it does not work.
Best regards,
Vimol

Backing up KM Folders via Portal Drive

Hi Experts,
We've implemented Netweaver Portal 7.0 with SP14 for a local company. Company migrated all shared folders from filesystem into KM via Portal Drive.
Portal is running on a VMWARE machine with Linux OS.
Followings are common questions, when we implement a Document Management SYstem on KM. I'm writing my answers but need help in Q2 esp.
Q1: How to backup files in KM?
A1: KM repostory is default DBFS mode ad all files within KM are stored in DB. So backing up DB means backing up KM thus all files.
Q2: How to backup/restore single/multiple files in KM in case of accidental deletion?
A2: In case of accidental deletion, with SP14 "Deleted Items" functionality given to KM and you can view and restore files deleted.
In case of permanent deletion, there is no option for KM file backup/restore other than DB.
Here we tried to simulate something following to backup files and restore in case of problem just like FileSystem document management:
On Backup Server, we installed Portal Drive and mapped the Portal KM Folders.
Then created a FileSystem backup on this mounted FS. But unable to backup in specific cases.
Not sure what is causing the problem, may be backup software, may be VMWARE architecture or may be linux or SAP portal for the last.
Here is the error code we get when we tried to backup KM Folders on a 32-bit windows 2003 server with Netbackup.
6/4/2008 2:14:53 PM - granted resource MediaID=@aaaae;Path=Z:\bck;MediaServer=bkcompany
6/4/2008 2:14:53 PM - granted resource test_disk
6/4/2008 2:14:53 PM - estimated 16 kbytes needed
6/4/2008 2:14:54 PM - started process bpbrm (88520)
6/4/2008 2:14:54 PM - connecting
6/4/2008 2:14:54 PM - connected; connect time: 00:00:00
6/4/2008 2:14:58 PM - begin writing
6/4/2008 2:15:05 PM - Error bpbrm(pid=88520) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
6/4/2008 2:15:10 PM - Error bpbrm(pid=88520) could not send server status message
6/4/2008 2:15:10 PM - end writing; write time: 00:00:12
file read failed(13)
also the event log entry:
Faulting application bpbkar32.exe, version 6.5.2007.1115, faulting module bpbkar32.exe, version 6.5.2007.1115, fault address 0x00067581.
May be this specific case is encountered by any of you
Does anyone have any solution or sample implementation like above.

Hi
Have you tried ICE Offline scenario?
[How to distribute KM Content using ICE Protocol|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/802c1739-d270-2910-ad9f-f369de07c1bf]
Check the Offline scenario, not Online.
Regards
Aparnna

Error Handling in JDBC Adaptor - Without BPM

Hi friends,
My problem is like this. Scenario is File -> Xi -> JDBC.
here i didn't used BPM at all.
My interface is working fine.
right now i am not doing any error handling for 'Primary key violation, refrential intigrity etc.. '.
if this type errors encountered i going to adapter monitoring and looking out the issue.
Now the client requirment is
whenever this type of errors occured Client should be notified Via email along with error description.
Is there anyway to do this ?

Hi Suresh,
You can setup the Alerting framework of XI to trigger alerts. Alert rules can be set to raise alerts in case of JDBC Adapter Errors.
Check these links....
http://help.sap.com/saphelp_nw04/helpdata/en/3f/81023cfa699508e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
Thanks & Regards,
Renjith
An addition to what i just said...You have to be on SP14 for this...
Message was edited by: Renjith Andrews

What is the correct CIM model and CR content version to import into SLD?

Hi All,
I just met a difficulty that I can not find the correct import version of CIM model and CR content.
Could anyone share some valuable suggestions?
Situations now:
I installed ECC6 SR3 with ABAP+ Java stacks, after installation successfully, I logged onto SLD through http://xxx:50000/sld
since my CIM model and CR content version is too low, so I want to upgrade it.
The currect version is as below:
Model Version (sld/new):     1.5.24
SAP CR Content Version (sld/new):     SAP_CR 2.0 (produced 03/17/2005)
Namespace     Model Version     Classes     Instances     Associations     Total Objects
sld/active      1.5.24               908     36381     60183             97472
I have read note 669669 carefully and downloaded all the relevant versions before updating, the the results are not correct. something like "Unknow status -1" "import anyway" appears.
So, could anyone tell me the correct update file and sequence?
Thank you very much in advance.
Best regards,
Nick

Hi Raghu,
Thanks for your quick reply.
I have downloaded 5 files:
cimsap51506_0-20005942.zip     SP06 for SAP CR CONTENT UP TO 2009
CRDelta1418_0-10003379.ZIP     SP18 for SAP CR CONTENT 2.0
CRDelta1511_0-10004549.ZIP     SP11 for SAP CR CONTENT UP TO 2007
CRDelta41514_0-10006428.ZIP     SP14 for SAP CR CONTENT UP TO 2008
CRDelta51506_0-20005942.ZIP     SP06 for SAP CR CONTENT UP TO 2009
and the update sequence are the same as above, that is to say, first I update CIM model version successfully from 1.5.24 to 1.5.45, and then, I upload CRDelta1418_0-10003379.ZIP which gave me an error message "Unknown status -1", even how many times I click "Import anyway", it's useless.
after then, I tried to upload CRDelta1511_0-10004549.ZIP directly, but it also refused. warning message is "The selected aggregate import is not applicable to the current content version SAP_CR 2.0 of the target namespace.", I clicked button "Import anyway", but it's useless since there contains 0 objects, I don't know why, the message shows "The import will upgrade the content of export line SAP_CR from the current version 2.0 to version 4.0.
Contains 0 objects."
The file CRDelta1511_0-10004549.ZIP is under SAP CR CONTENT UP TO 2007, why its version is 4.0? is it because I need to firstly update to 3.0? and where can I find version 3.0?
I really appreciate your kind help.
Best regards,
Nick

XI Adapter framework core 3.0 download

Hi to all,
can anyone give me the exact url to download the XI Adapter Framework core 3.0? I need of libraries, as aii_af_lid.sda, containe into it.
Thanks!

As you have not specified you patch version, you will need to go into http://service.sap.com/swdc
Support Packages and Patches > SAP NetWeaver > SAP NETWEAVER > SAP NETWEAVER 04 > Entry by Component > Process Integration (PI/XI)
XI ADAPTER FRAMEWORK 3.0
#OS independent
Then take you pick from this lot:
File Type Download Object Title Patch Level Info File File Size [kb] Last Changed
SCA SAPXIAF01_0-20000273.SCA SP1 for XI ADAPTER FRAMEWORK 3.0 0 Info 2904 31.03.2004
SCA SAPXIAF02_0-20000273.SCA SP2 for XI ADAPTER FRAMEWORK 3.0 0 Info 2860 04.05.2004
SCA SAPXIAF03_0-20000273.SCA SP3 for XI ADAPTER FRAMEWORK 3.0 0 Info 2861 09.06.2004
SCA SAPXIAF04_0-20000273.SCA SP4 for XI ADAPTER FRAMEWORK 3.0 0 Info 3791 05.08.2004
SCA SAPXIAF05P_2-20000273.SCA Patch for XI ADAPTER FRAMEWORK 3.0 SP5 2 Info 3862 18.10.2004
SCA SAPXIAF09P_3-20000273.sca Patch for XI ADAPTER FRAMEWORK 3.0 SP09 3 Info 4061 02.12.2004
SCA SAPXIAF10_0-20000273.sca SP10 for XI ADAPTER FRAMEWORK 3.0 0 Info 4140 07.01.2005
SCA SAPXIAF10P_2-20000273.sca Patch for SP10 for XI ADAPTER FRAMEWORK 3.0 2 Info 4155 02.02.2005
SCA SAPXIAF11_0-20000273.sca SP11 for XI ADAPTER FRAMEWORK 3.0 0 Info 4267 04.03.2005
SCA SAPXIAF11P_2-20000273.sca Patch for SP11 for XI ADAPTER FRAMEWORK 3.0 2 Info 4256 03.06.2005
SCA SAPXIAF12_0-20000273.sca SP12 for XI ADAPTER FRAMEWORK 3.0 0 Info 1946 18.05.2005
SCA SAPXIAF12P_7-20000273.sca Patch for SP12 for XI ADAPTER FRAMEWORK 3.0 7 Info 1949 03.11.2005
SCA SAPXIAF13_0-20000273.sca SP13 for XI ADAPTER FRAMEWORK 3.0 0 Info 3625 28.07.2005
SCA SAPXIAF13P_7-20000273.sca Patch for SP13 for XI ADAPTER FRAMEWORK 3.0 7 Info 2014 03.11.2005
SCA SAPXIAF14_0-20000273.sca SP14 for XI ADAPTER FRAMEWORK 3.0 0 Info 2137 30.09.2005
SCA SAPXIAF14P_2-20000273.sca Patch for SP14 for XI ADAPTER FRAMEWORK 3.0 2 Info 2134 15.12.2005
SCA SAPXIAF15_0-20000273.sca SP15 for XI ADAPTER FRAMEWORK 3.0 0 Info 2555 16.12.2005
SCA SAPXIAF15P_5-20000273.sca Patch for SP15 for XI ADAPTER FRAMEWORK 3.0 5 Info 2526 07.07.2006
SCA SAPXIAF16_0-20000273.sca SP16 for XI ADAPTER FRAMEWORK 3.0 0 Info 2640 28.02.2006
SCA SAPXIAF16P_7-20000273.sca Patch for SP16 for XI ADAPTER FRAMEWORK 3.0 7 Info 2654 13.10.2006
SCA SAPXIAF17_0-20000273.sca SP17 for XI ADAPTER FRAMEWORK 3.0 0 Info 2950 23.05.2006
SCA SAPXIAF17P_8-20000273.SCA SAPXIAF17P 8 Info 2925 01.02.2007
SCA SAPXIAF18_0-20000273.sca SP18 for XI ADAPTER FRAMEWORK 3.0 0 Info 3121 28.07.2006
SCA SAPXIAF18P_5-20000273.SCA Patch for SP 18 for XI ADAPTER FRAMEWORK 3.0 5 Info 3090 28.05.2007
SCA SAPXIAF19_0-20000273.sca SP19 for XI ADAPTER FRAMEWORK 3.0 0 Info 3371 13.11.2006
SCA SAPXIAF19P_8-20000273.SCA Patch for SP19 for XI ADAPTER FRAMEWORK 3.0 8 Info 3336 23.05.2007
SCA SAPXIAF20_0-20000273.SCA SP20 for XI ADAPTER FRAMEWORK 3.0 0 Info 3865 23.03.2007
SCA SAPXIAF20P_5-20000273.SCA Patch for SP20 for XI ADAPTER FRAMEWORK 3.0 5 Info 3874 17.07.2007
Also, there is
XI ADAPTER FRAMEWORK CORE 3.0
#OS independent
File Type Download Object Title Patch Level Info File File Size [kb] Last Changed
SCA SAPXIAFC01_0-20000272.SCA SP1 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 3919 31.03.2004
SCA SAPXIAFC02_0-20000272.SCA SP2 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 3962 04.05.2004
SCA SAPXIAFC03P_4-20000272.SCA Patch for XI ADAPTER FRAMEWORK CORE 3.0 SP3 4 Info 3973 09.08.2004
SCA SAPXIAFC04P_2-20000272.SCA Patch for SP4 for XI ADAPTER FRAMEWORK CORE 3.0 2 Info 4701 09.09.2004
SCA SAPXIAFC05P_5-20000272.SCA Patch for SP5 for XI ADAPTER FRAMEWORK CORE 3.0 5 Info 4797 19.10.2004
SCA SAPXIAFC09P_12-20000272.sca Patch for SP09 for XI ADAPTER FRAMEWORK CORE 3.0 12 Info 4847 07.01.2005
SCA SAPXIAFC10_0-20000272.sca SP10 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 5057 07.01.2005
SCA SAPXIAFC10P_7-20000272.sca Patch for SP10 for XI ADAPTER FRAMEWORK CORE 3.0 7 Info 5068 29.03.2005
SCA SAPXIAFC11_0-20000272.sca SP11 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 5133 04.03.2005
SCA SAPXIAFC11P_14-20000272.sca Patch for SP11 for XI ADAPTER FRAMEWORK CORE 3.0 14 Info 5145 27.03.2006
SCA SAPXIAFC12_0-20000272.sca SP12 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 6651 18.05.2005
SCA SAPXIAFC12P_17-20000272.sca Patch for SP12 for XI ADAPTER FRAMEWORK CORE 3.0 17 Info 6647 29.03.2006
SCA SAPXIAFC13_0-20000272.sca SP13 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 7457 28.07.2005
SCA SAPXIAFC13P_20-20000272.sca Patch for SP13 for XI ADAPTER FRAMEWORK CORE 3.0 20 Info 7461 04.04.2006
SCA SAPXIAFC14_0-20000272.sca SP14 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 8295 30.09.2005
SCA SAPXIAFC14P_25-20000272.SCA Patch for SP14 for XI ADAPTER FRAMEWORK CORE 3.0 25 Info 8265 19.07.2007
SCA SAPXIAFC15_0-20000272.sca SP15 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 8501 16.12.2005
SCA SAPXIAFC15P_19-20000272.SCA Patch for SP15 for XI ADAPTER FRAMEWORK CORE 3.0 19 Info 8481 11.05.2007
SCA SAPXIAFC16_0-20000272.sca SP16 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 8591 28.02.2006
SCA SAPXIAFC16P_19-20000272.SCA Patch for SP16 for XI ADAPTER FRAMEWORK CORE 3.0 19 Info 8474 28.06.2007
SCA SAPXIAFC17_0-20000272.sca SP17 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 8706 23.05.2006
SCA SAPXIAFC17P_21-20000272.SCA SAPXIAFC17P 21 Info 8601 28.06.2007
SCA SAPXIAFC18_0-20000272.sca SP18 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 8916 28.07.2006
SCA SAPXIAFC18P_22-20000272.SCA SAPXIAFC18P 22 Info 8827 19.07.2007
SCA SAPXIAFC19_0-20000272.sca SP19 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 9110 13.11.2006
SCA SAPXIAFC19P_16-20000272.SCA Patch for SP19 for XI ADAPTER FRAMEWORK CORE 3.0 16 Info 9010 05.07.2007
SCA SAPXIAFC20_0-20000272.SCA SP20 for XI ADAPTER FRAMEWORK CORE 3.0 0 Info 10110 23.03.2007
SCA SAPXIAFC20P_6-20000272.SCA Patch for SP20 for XI ADAPTER FRAMEWORK CORE 3.0 6 Info 10118 24.07.2007

BPC not working in Excel 2013

Dear Team,
Currently we are using BPC10 version in SAP.
Version 10.0 SP12Patch 8 .NET4
Excel version is 2010 . whereas we have upgraded our Excel Version to 2013 BPC is not supporting.
BPC10 is not supporting for Microsoft Excel 2013.
Please guide how to solve the issue and make it compactable for Excel 2013.
Thanks in advance.
Regards,
AJAY.

Hi Yasser,
I tried but its not working.
I have tried to install the Patch
EPMEXCLCLNT14P_3-10011004.ZIP Patch for SBOP EPM ADD-IN BIG VOL. 10.0 SP14
for .NET 4 or .NET3.5 I got the below error.
for .NET3.5 I am getting the below error.
and for .NET4 I have attached the error in above threat.
Dear Experts please advise how to over come the issue.
Regards,
Ajay

SP14 for BW

Similar Messages

Maybe you are looking for