Symptom You want to use SAPCAR functionality in Windows XP operating system. Login to SAP Service Marketplace. Go to Software Download >Search for Software Downloads.

Search for keyword “SAPCAR”. Choose any of the latest SAPCAR from the search result. Ensure, you are selecting and downloading SAPCAR.EXE with 32-bit functionality. Go to the directory of your downloaded SAPCAR location and execute the SAPCAR command. For easier execution, you can just put the SAPCAR.EXE and the SAR file into 1 folder location.

As in this example, both SAPCAR.EXE and TEST.SAR are in folder D: itsiti test. D: itsiti>cd test D: itsiti>SAPCAR.EXE -xvf TEST.SAR 4.

You are now successfully un-car the SAR file and you can check the files extracted.

Regards From: irfraz via sap-basis [mailto:sap-basis@Groups.ITtoolbox.com] Sent: 16 January 2009 17:27. Caddick Subject: RE: [sap-basis] Extract.sar with SAPCAR.exe. The difference between sar and car files are, for kernal upgrade you download.SAR files from SAPmarket and for patch, you download CAR files. Hana-client-chef-cookbook - A cookbook to install the SAP HANA client CLI onto a Windows instance.

Check Authorizations Check the required authorizations. Users who want to generate easy queries require the following authorizations. • Role S_RS_RDEMO contains all authorization objects for the BW system. • Role SAP_BC_SIW_DEV needs to have activity 06 for authorization object S_SIW_CFG added to it. The Service Integration Workbench (SIW) is needed for generation of the ABAP components in the easy query.

• You still need an SOA role for service configuration with SOA Manager (such as SAP_BC_WEBSERVICE_DEBUGGER, SAP_BC_WEBSERVICE_ADMIN_TEC or SAP_BC_WEBSERVICE_ADMIN_BIZ). For more information, see the documentation for SOA Manager under Roles and Authorizations. CASE 1: Foro Help: 1.- TO TAKE AND CARRY AN OBJECT OF A infoarea TO ANOTHER, THAT CREATES DUMP ERROR: ****************************************************** Note solution: 1859888 – Dump in RSA1 while displaying InfoArea Symptom: When launching transaction RSA1 and navigating to the info area say ‘XYZ’ leads to the below dump. “ASSERTION_FAILED” ” “CL_RSAWBN_TREE_MODEL==========CP” “CL_RSAWBN_TREE_MODEL==========CM002″ “GET_CHILDREN” Environment SAP NetWeaver BW Release Independent. Reproducing the Issue Launch the transaction RSA1. Goto Inforarea ‘XYZ’. Cause: If you change the order of components in the process chain tree, this seems to have no effect, the change is not displayed until the whole tree is refreshed.

So this is the reason for the dump to occur. Resolution Kindly follow the below steps this should solve the problem: Run the t-code RSA1OLD so the whole info Area tree will be Re-generated. Then try “drag and drop” the object again to recheck. ****************************************************** CASE 2: Foro help: Nota: 1664459 – Runtime Error when opening RSA1/RSPC *************************************************** Runtime Error ASSERTION_FAILED in ABAP Program CL_RSAWBN_TREE_VIEW Purpose. The purpose of this page is to provide a solution to the Runtime Error ASSERTION_FAILED in ABAP Program CL_RSAWBN_TREE_VIEW.

Overview This WIKI page contains a description of the ABAP dump and a possible solution. Issue A Runtime Error ASSERTION_FAILED in ABAP Program CL_RSAWBN_TREE_VIEW is generated when running either transaction RSA1 or RSPC. This is a screenshot of the error.

Reproducing the Issue Execute either transaction RSA1 or RSPC. Cause There are inconsistencies with an Application Component. Solution • Delete the contents of table RSCOMPTLOGO • Call the transaction again – the application components will be regenerated • Also implement Note 1585456 OR • Transport object RSDC with key RSPC to move the tree structure into your system • Also implement Note 1585456 Esta entrada fue publicada en el por. You have a BW 2.0B system with at least level SP3, or a higher system (BW 2.1C, BW 3.x ). (1) Run the SAP_INFOCUBE_INDEXES_REPAIR report. To do this, go to transaction SE38 and schedule this report as a background job.

(2) If you run this report and the indexes have still not been repaired, make sure during the checks in DB02 that the information can be refreshed by pressing the “Refresh” and “Perform Database Checks” buttons, then analyze the causes as follows: • Look at the log in transaction RSRV, for “Database”, “Indices of an InfoCube and its Aggregate”, “Execute” (F8) and then “results” (F6).This should provide you with information about the problem. • After the job (SAP_INFOCUBE_INDEXES_REPAIR) has run, look at the system log (transaction SM21).SQL errors are logged there, which provide information as to why an index was not created.

For more information on analyzing SQL errors, see note 495256. • Refer also to notes 337830 and 364650. Esta entrada fue publicada en el por. How many development clients are possible? How to work with target groups • 3. How to work with transport groups • 4.

Virtual systems • 5. Temporary inactive system flag in SMSY • 6. Changes in the logical components of a project where Charm is already activated • 7. Several Solution Managers in the landscape • 8. Completing a task list • 9. Completing inconsistent task lists (note 933705) • 10. Can I delete a project with Charm activated?

Scheduling of import job /TMWFLOW/SCMA_TRORDER_IMPORT hourly • 12. Import options • 13. Return codes and tp errors • 14. Urgent correction SDHF stays in the import buffer after the import • 15. Working with urgent corrections and normal corrections in the same task list –REALLY interesting case to know • 16.

Task list “logs” • 17. Error: “No maintenance cycle is opened for the current system” • 18. Dump ITAB_DUPLICATE_KEY • 19. Retrofit functionality • 20. System copy • 21. Missing authorizations for READ RFC connections • 22.

Registering transport requests in ChaRM • 23. Report CRM_SOCM_SERVICE_REPORT and email actions not processed • 24. What happens when the solman system is down?

Special considerations for non-ABAP landscapes in ChaRM • 26. In which situations a ChaRM project is locked? Several managed system with same SID • 28. Incorrect use of SM_*_LOGIN RFC connection. How many development clients are possible?

You should know that in SAP Solution Manager 7.1 ChaRM tracks will not use “SAP” transport layer, for more information please refer to SAP note. Per each development client that you need to manage via ChaRM: Logon to domain controller system client 000 ->Transaction STMS ->Transport Routes ->Go to Change mode ->Double click on the development system ->Go to tab Standard Transport Layer ->Insert row for client-specific settings ->Enter development client number and the transport layer which should be used in ChaRM ->Save and distribute the configuration change. Note: Notice that TMS will not allow you to enter two times the same development client with different transport layers. When systems in the logical component of the SMI project or TMS transport routes has been changed after the generation of the task list, tables /TMWFLOW/TTRCKHC and /TMWFLOW/TTRCKEC will be updated partly, the tables will be updated in that way that new entries will be created. The new entry in the header table /TMWFLOW/TTRCKHC will get the ‘active’ flag, and the old entry will remain, but get the ‘Completed’ flag. The task list will go on working with the old entries. But if you complete the task list and generate a new one, this will use the new entries.

In case that you are working with ChaRM project using cCTS functionality, if you need to change your transport landscape – maybe a new system is installed or an old one is removed. In this case, you also have to change the clusters that you created or add or delete a cluster. Roughly the following steps are required when changing the tracks: – Make sure that all projects in ChaRM and QGM using the respective cluster track are closed. – Make your changes at system or/and cluster level, distribute your configuration changes. – According to the dimension of the changes create new projects or create new task lists for the same project. 2) With variant SAP0, it is possible to create both normal corrections and urgent corrections under this maintenance cycle. And we have different import considerations: for normal correction we are using import project all, which means in this case all requests on the same CTS project will be imported all together (including those in urgent corrections); while for urgent correction we are using import subset, which means only those requests created under specific urgent corrections will be imported.

This is the case: MC in status Go-Live with several Normal corrections in status consolidated and two urgent corrections assigned to this MC, one urgent correction already in status Confirmed and the other in status “To be tested”. From the MC I schedule the import into production system: – the two transport orders of normal correction in status “Consolidated” were imported correctly – the urgent correction in status “confirmed” ( already imported into production) is imported again in production as we see in point 14, see the log of the transport order – the urgent correction in status “to be tested” is ALSO IMPORTED in production —– WHY????? I HAVE NOT EVEN TEST THIS URGENT CORRECTION!!! What I have described is the correct behavior; all TRs are imported, also when you do not want to import the second UC.

Every time a transport request is imported into QUA system, this transport request is entered into the import buffer of the production system. Note: The same happens when the transport request is released, the transport request is entered into the import buffer of the quality system. The process of an urgent correction includes the import into PRD, so we have to fill the import buffer of PRD, there we use standard SAP technique, when import into QAS the import buffer of the following system will be filled. The IMPORT into PRD made from ChaRM is a pour call of TMS functionality, so we can not manipulate the import queue.

RFC destination plays a very crucial and important role through the whole ChaRM processes. If you take a look in the ChaRM check result, you will see we are also checking a lot of RFCs just to ensure the project is consistent. If there are some errors for those RFCs, especially to your domain controller systems, then we will say the whole project might be in danger because the communication to remote systems might have been closed for a moment. Here we do not differentiate whether it is a READ RFC or TMW RFC, it is also very hard for us to decide the real root cause of the error. It might disappear after a few seconds; it might also be some network problems or even hardware issues which need a longer time to solve it. Therefore, to make sure the whole project is safe and consistent, I am afraid the best solution is just to lock it.

Link de ayuda: In this case the EXPORT_TOO_MUCH_DATA short dump is not related to a memory problem but it is related to reaching the level of maximum amount of data what can be stored in the memory. ABAP program “CL_SWNC_COLLECTOR_DB==========CP” The exception, which is assigned to class ‘CX_SY_COMPRESSION_ERROR’, was not caught in procedure “SAVE_AGGREGATE” “(METHOD)”, nor was it propagated by a RAISING clause. Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.

The reason for the exception is: The dataset stored under an EXPORT/IMPORT ID is restricted by 1. The maximum possible size of 2 GB 2. The length of a data record and the capacity of the sequence counter.This error occurs only if the capacity of the sequence counter does not go beyond 255. Termination occurred in the ABAP program “CL_SWNC_COLLECTOR_DB==========CP” -in “SAVE_AGGREGATE”.The main program was “SWNCTOTAL “. FRom the dump >>>>>EXPORT datatable FROM rfcserver_aggtable TO DATABASE swncmoni(wo) ID monikey. The short dump displays the profile that triggers the termination. When the short dump EXPORT_TOO_MUCH_DATA occurs in the report CL_SWNC_COLLECTOR_DB, the value of the variable is AGGTYPE: WO [WO] RFC client profile (refer to note: 1110822 and use the report SWNC_COLLECTOR_COMPRESSION ) Run SWNC_COLLECTOR_COMPRESSION from SE38, set check to WO, and select “Schedule Background Program” in the bottom of screen, then execute.

Or Technical name# Description in ST03N ACCOUNT, MANDT, USERID# Account, client, user PROG_NAME, RFC_CALLER# RFC program, RFC caller TARGET, LOCAL_DEST, REMOT_DEST (*)# RFC destination, local server, RFC destination ENTRY_ID, FUNC_NAME (*)# Report name, transaction name or name of the background job. Do the following: please call ST03, and navigate to: Collector and Performance DB ->Workload Collector ->TOTAL Collector ->Control On this screen You can exclude profile WO (RFC Client Profile) from being collected for TOTAL values. This means that You will not see details for these statistics under TOTAL in ST03 (only for RFC Client Profile statistics of course), but You can still see the values for the individual servers, so this can be calculated any time when needed. Access the transaction SE16 and check for each profile which ones have more than 20000 entries in the table. You can check all the W* profiles for this. The table name to be checked is SWNCMONI.

Use the below criteria Area W* (WL, WD, WF, WJ, WM, WO, etc items) Host / Instance TOTAL Period Type M For each profile (area) with more than 20000 entries, please run the SWNC_COLLECTOR_COMPRESSION report and activate a switch for this profile area. After this please run the report SWNC_COLLECTOR_RECOMPRESS one time and do the counting again. The only affected table is SWNCMONI.

See also 1578639 – Shortdumps “EXPORT_TOO_MUCH_DATA” in “SWNCTOTAL” Analyzing EXPORT_TOO_MUCH_DATA dumps in SAP_COLLECTOR_FOR_PERFMONITOR NOTA: Para el error que se nos presento, aplicamos la sgte Nota, la cual se adecuaba a la release 7.40 de nuestro cliente: 2108954 – OLAP cache query runtime error CX_SY_COMPRESSION_ERROR Esta entrada fue publicada en el por. Link: ITAB DUPLICATE KEY – A row with the same key already exists The Problem: It was for one of the training sessions, I was expected to conduct, I was preparing a data flow for showing the data load from flat file up to the cube, routing the flow through DSO. I was creating the flow on my company’s Training Server, which pointless to say is not very closely monitored and is connected to many source systems, which are added and removed frequently. So, I created the entire flow using a flat file data source and a standard DSO.

As it happens, on executing the info-package, the data got loaded into the PSA. From there, it was designed to load Data, on to the DSO through DTP, by manual execution solely for demonstration purpose. But whenever I executed the DTP, it gave me ITAB_DUPLICATE_KEY dump with a short text of “A row with the same key already exists” (See Figure-1 ABAP Dump). Parable Of The Patch And Wine Skins Bible.

Figure 1 -ABAP Dump All the settings were perfectly fine, it was for the very first time I was loading the data. Still, I checked and rechecked it, and after checking it for the umpteen times I was baffled and totally perplexed. I was under the assumption that there is a row in DSO table which already has the same key, which I was not able to find or locate. I went to the extent of manually checking all the activation queue, under New data, but nothing was there. The only thing that showed the way forward was the ISOSMAP table which was figuring in the dump and it led me to SAP Note 613449.

The Cause: Using a BW client, having many different source systems attached, which get added and removed on a frequent basis, is fraught with perils of unused objects getting left behind because of one reason or another, creating a duplicate entry in RSISOSMAP table and making system inconsistent. Normally they will have same transfer structure and same data source, but coming from two different source systems, hence creating duplicity and this is primarily responsible for the dump ITAB_DUPLICATE_KEY. Solution: Fortunately SAP has provided a solution in terms of a report Program RSAR_RSISOSMAP_REPAIR to amend and remove duplicity from table RSISOSMAP. So we go to ABAP Editor: Initial Screen and enter the program name as shown in the Figure 2 – ABAP Editor: Initial Screen and execute it. It immediately takes us to the next screen providing a selection for Repair Mode. We will select that option as shown in Figure-3 (Selection for Repair mode).

Once we execute it, after selecting the repair mode option, Figure 3 – Selection for Repair Mode it shows us the report with duplicate entries for same data source (under the heading OLTPSOURCE) but from different Source Systems (under the heading LOGSYS) having duplicate Transfer Structure (Under the heading TRANSTRU) as can be seen in the Fig-4 (Report RSISOMAP) Figure 4 – Report RSISOSMAP Now, all that we have to do is, remove the unwanted entry for the source system which we are not using, like in my case Source System BWPRD-800. So now, we go to Table RSISOSMAP by executing Tcode SE16. See Figure-5 Data Browser: Initial Screen and explore that particular table and (Ingresar la fuente de datos para buscar en la tabla) Figure 5 – Data Browser: Initial Screen On the selection screen for table RSISOSMAP we will enter the Data-source name which is occurring in duplicity as evident from the report and execute it. See Figure-6 (Borrar la fuente de datos del sistema fuente que NO SE UTILIZARA) Figure 6 – Selection screen for Table RSISOSMAP Now we will delete the entry for the source system that is redundant or not wanted and all our problems will be resolved. Figure 7 – Duplicate entries Table RSISOSMAP Foros de ayuda: *************************************************************************** • 18. Dump ITAB_DUPLICATE_KEY *************************************************************************** Notas relacionadas: Esta entrada fue publicada en, el por. Link: System copy configuration of SAP Business Warehouse (SAP BW) system landscape is highly complex due to the many connections between the involved application systems.

Typically such a system landscape contains SAP BW systems, BI Java systems and SAP BW source systems such as SAP ERP, SAP CRM and SAP SCM etc. The two main copy use cases are Initial Copy (creating a new system from a copy) or System Refresh (refreshing the data of an existing system from a copy). In either copy use case, one must pay special attention to both the various system connection details (ie: connections between SAP BW system and its source system such as SAP ERP, SAP CRM etc.) and system configuration settings (ABAP and Java basic configurations). Additionally, with each system copy, a series of post copy configuration activities are required to ensure success.

These activities are a part of every system copy including a migration to SAP HANA as well as regular system copies of your SAP BW landscape. To manage such challenges, all these post copy activities have been automated for SAP BW system landscape ( Post-Copy Automation or short: BW PCA). This automated solution makes the required post-copy activities much easier, more efficient and more robust. The manual guide for SAP BW system copy configuration described in (SMP logon required) becomes obsolete. BW PCA is offered as part of the SAP Landscape Virtualization Management product.

It can be executed in ABAP systems locally by using the ABAP task manager for lifecycle management automation or triggered by SAP Landscape Virtualization Management as part of an integrated solution. • Get an overview on to get familiar with the challenges and the automated solution and its coverage. • Check (Post-Copy Automation for SAP Business Warehouse System Landscapes (BW-PCA)), the BW PCA collective SAP Note for a list of all detailed information including installation and configuration guides (SMP logon required). • BW PCA supports an • Visit the page to get a broad picture of the whole automation offering of PCA provided for SAP systems by SAP Landscape Virtualization Management and other related information such as EKT Learning Map, Best Practices and FAQ etc.

Related topics: • • •. Esta entrada fue publicada en, el por. Link del TEMA: *** UPDATE 20th Oct 2014: Please look at: and OSS note 886102 for the automation and improvement updated by SAP *** It is not uncommon that once BW QA gets refreshed or system copy from BW Prod, the source system connectivity to ERP system breaks. This document shows the step-by-step to restore BW QA to ERP QA. ERP System: ERP Quality System (QAS) client 100 BW QA System: BW Quality System (Q11) client 100 Scenario: Source Systems QASCLNT100 is broken in txn RSA1 in BW QA (Q11) after it is refreshed from BW Production. This is a need to restore the connection for transport migration to work successfully.

Pre-requisite: 1. Open clients via txn SCC4, SE06 in ERP QA (QAS) and BW QA (Q11). If not, you will encounter dump DYNPRO_SEND_IN_BACKGROUND when trying to recreate the Source Systems in x11’s txn RSA1. (This step requires Basis authorization and should be done by Basis) • Logon to ERP QA (QAS), run txn SCC4 and open client for changes.

Repeat for BW QA (Q11). • In ERP QA (QAS) Run txn SE06, open namespaces so that there is no error when running FM RSAP_BIW_DISCONNECT later on. Repeat for BW QA (Q11). In BW QA (Q11), go to txn WE20, check for ERP QA (QASCLNT100). If it does not exist, create it.

If it exists, select the ERP QA’s Partner Profile QASCLNT100 and delete RSRQST from outbound and RSINFO and RSSEND from inbound. Save your partner profile. It should look like the screen below.

Obtain ALE user-id passwords for to logon to QAS client 100 (ERP) and Q11 client 100 (BW) later on. Step-by-Step Restore Procedure: 1. In BW QA (Q11), run txn SE11, table RSBASIDOC, narrow the results by putting in your ERP system id only e.g.

QAS* Result 2. In BW QA (Q11), run txn SE37, enter function module RSAP_BIW_DISCONNECT and client Test/Execute button. This step deletes obsolete BW connections. Repeat this step for all entries in table RSBASIDOC. Avs Video Editor Download For Windows 7. Enter the values accordingly and click Generate button. I_BIW_LOGSYS = BW QA system (Q11) I_OLTP_LOGSYS = ERP QA system (QAS) I_FORCE_DELETE = X Caution: DO NOT enter a value in the field “RFC target sys”. This would cause the function module to run in the system specified there!

In BW QA (Q11), run txn RSA1 and Create Source System QASCLNT100. With existing RFC destination and passwords, enter the fields like below: You will be prompt to logon to QAS client 100.

Click Continue button will do. Click Use button if you are confident that the RFC destination works perfectly. If not, you could click Check button to confirm. You might encounter a pop up message like this below. Click Delete will do.

If this happens, after delete, repeat step 3 again. With existing RFC destination and passwords, you should be able to create the Source System for ERP QA (QASCLNT100) without problem. Problems that I encountered along the way.

Problem 1: DYNPRO_SEND_IN_BACKGROUND when trying to generate Source System QASCLNTxxx in txn RSA1 Solution: Open clients in txn SE06 and SCC4 in both ERP QA and BW QA systems Problem 2: Entry in inbound table already exists Solution: • Go to WE20 and check whether Partner profile QASCLNT100 exist in LS type,if not just add Parnter profile with same and save. Partner profile Name: QASCLNT100 TYPE: LS Give: Ty: US User: User Name Lang: EN and Save. • Again re-click on Partner Profile: QASCLNT100 you will see,there will be some entries in Inbound & out Bound Tabs.

Delete the following from outbound: 1.RSRQST Delete the following from inbound. 1.RSINFO 2.RSSEND and save your partner profile. • Now execute txn RSA1, it will ask to active Workbench, activate it and it should work.

Lastly, this document is only possible from the two reference below and many other related threads that I had also come cross so I would also like to give credits to them. References: OSS Note 886102 – System Landscape Copy for SAP Netweaver BW (Phase 6) Transfer Structure Prefix error – ******************************************************************** ******************************************************************** COMMENTS: •. Hi Samuli, Yes, I agree with SAP recommendation, in fact by doing so, there are so many issues Basis could avoid. Unfortunately, sometimes due to complexity of landscape in global SAP environment and tight project deadlines for different regions, refreshing ERP QA is not always possible hence such a problem occurs and needs to deal with. Thanks for highlighting this, it does throw some lights to others who aren’t aware of the dependency and impact between ERP and BW ********************************************************** **********************************************************. Link de SDN: Introduction: TREX is a search engine in the integrated technology platform. The name “TREX” stands for Text Retrieval and information EXtraction.

When a customer uses SAP Solution Manager ITSM suite ( Incident Management of Change Management), there will be a lot of incidents and changes that will be created as part of the organization’s ticketing processes. TREX “full text search” predominantly helps in searching and filtering those incidents or changes based on the search criteria. When you get a support message in the Solution Manager Incident management; reporting an issue then you can search in your internal Knowledge Articles for problem solutions. Quick review of the installation process: Please check SMP for latest updates on versions/releases and install the latest files. Go to SMP and download the TREX files 2. Start SAPCAR to uncar the Files 3.

Installing TREX – a) Start SAPInst - 4. TREX SID Name Give a SID name.

Below is an example. Installation/ Initiation/Completion.