PSA no deletion SAP BW on HANA Rev 61

Hi,
PSAs are not getting deleted for some of the datasources due to error loads and multiple runs. System is SAP BW on HANA Rev 61.
The previous job failure was not corrected and the subsequent job was started based on the process chain schedule and that one as well failed. This has happened 2 times. Now the PSA table says it has duplicate entries and it is not dropping when we try to delete manually or through program.
Whenever we try to delete the PSA, the SAPLSDB2 program runs and is stuck in SM51. St22 error log says
SQL error "-10807" while accessing table "/BIC/B0000674001".
65 l_s_data TYPE /BIC/B0000674001.
66 *---1363526 Increasing the security to check the number of records inserted in PSA table
67 *---is actually equal to data in l_t_data or p_t_data.
68 DATA: l_rollback TYPE rs_bool,
69 l_count TYPE i.
70 l_rollback = RS_C_FALSE.
71 *---1363526
72
73 APPEND LINES OF p_t_data TO l_t_data.
74
75 CLEAR: l_s_data.
76 l_s_data-partno = p_partno.
77
78 MODIFY l_t_data
79 FROM l_s_data
80 TRANSPORTING partno
81 WHERE request = p_requestid.
82
83
>>> INSERT /BIC/B0000674001
85 FROM TABLE l_t_data
86 ACCEPTING DUPLICATE KEYS.
87 *---1363526
88 DESCRIBE TABLE l_t_data LINES l_count.
89 IF l_count NE sy-dbcnt.
90 l_rollback = RS_C_TRUE.
91 ENDIF.
92 *---1363526
Category ABAP Server Resource Shortage
Runtime Errors DBIF_RSQL_SQL_ERROR
Except. CX_SY_OPEN_SQL_DB
Date and Time 10.08.2014 11:28:01
|Short text |
| SQL error "-10807" while accessing table "/BIC/B0000674001". |
|What happened? |
| Database error text: "System call 'recv' failed, rc=145:Connection timed out" |
|What can you do? |
| Please make a note of the actions and input which caused the error. |
| - |
| |
| To resolve the problem, contact your |
| SAP system administrator. |
| |
| Using transaction ST22 for ABAP dump analysis you can see and |
| administrate termination messages and retain them for longer periods. |
| Please make a note of the actions and input which caused the error. |
| - |
| |
| To resolve the problem, contact your |
| SAP system administrator. |
| |
| Using transaction ST22 for ABAP dump analysis you can see and |
| administrate termination messages and retain them for longer periods. |
|Error analysis |
| An exception occurred that is explained in detail below. |
| The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught |
| in |
| procedure "INSERT_ODS" "(FORM)", 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: |
| Database error text: "System call 'recv' failed, rc=145:Connection timed out" |
|How to correct the error |
| Internal call code.........: "[RSQL/INSR//BIC/B0000674001 ]" |
| Please check the entries in the system log (Transaction SM21). |
| 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, |
| please use the following search criteria: |
| |
| "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB" |
| "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C" |
| "INSERT_ODS" |
| If you cannot solve the problem yourself, please send the |
| following documents to SAP: |
| |
| 1. A hard copy print describing the problem (short dump). |
| To obtain this, select "System->List->Save->Local File (unconverted)" |
| on the current screen. |
| |
| 2. A suitable hardcopy printout of the system log. |
| To obtain this, call the system log with Transaction SM21 |
| and set the time interval to 10 minutes before and 5 minutes after |
| the short dump. In the display choose "System->List->Save-> |
| Local File (unconverted)" |
| |
| 3. If the programs are your own programs or modified SAP programs, |
| supply the source code. |
| To do this, choose "More Utilities->Upload/Download->Download" in the |
| Editor. |
| |
| 4. Details regarding the conditions under which the error occurred |
| or which actions and input led to the error. |
| 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, |
| please use the following search criteria: |
| |
| "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB" |
| "GP4PWAW7JG4VX23SSK75NF4776C" bzw. "GP4PWAW7JG4VX23SSK75NF4776C" |
| "INSERT_ODS" |
| If you cannot solve the problem yourself, please send the |
| following documents to SAP: |
| |
| 1. A hard copy print describing the problem (short dump). |
| To obtain this, select "System->List->Save->Local File (unconverted)" |
| on the current screen. |
| |
| 2. A suitable hardcopy printout of the system log. |
| To obtain this, call the system log with Transaction SM21 |
| and set the time interval to 10 minutes before and 5 minutes after |
| the short dump. In the display choose "System->List->Save-> |
| Local File (unconverted)" |
| |
| 3. If the programs are your own programs or modified SAP programs, |
| supply the source code. |
| To do this, choose "More Utilities->Upload/Download->Download" in the |
| Editor. |
| |
| 4. Details regarding the conditions under which the error occurred |
| or which actions and input led to the error. |
| The exception must either be prevented, caught within proedure |
| "INSERT_ODS" "(FORM)", or its possible occurrence must be declared in the |
| RAISING clause of the procedure. |
| To prevent the exception, note the following: |
|System environment |
| SAP Release..... 730 |
| SAP Basis Level. 0006 |
| |
| Application server... "pkghnp" |
| Network address...... "10.83.240.20" |
| Operating system..... "SunOS" |
| Release.............. "5.10" |
| Hardware type........ "sun4u" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 4 |
| Shortdump setting.... "full" |
| |
| Database server... "vsyexhann01" |
| Database type..... "HDB" |
| Database name..... "HNP" |
| Database user ID.. "SAPHNP" |
| |
| Terminal.......... " " |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 720 |
| created (date)... "Mar 21 2012 09:58:29" |
| create on........ "SunOS 5.10 Generic_141444-09 sun4us" |
| Database version. "SQLDBC 1.00.61.0380109 " |
| |
| Patch level. 201 |
| Patch text.. " " |
| |
| Database............. "HDB 1.0" |
| SAP database version. 720 |
| Operating system..... "SunOS 5.10, SunOS 5.11" |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 100555392 |
| Heap.... 0 |
| Page.... 0 |
| MM Used. 75424248 |
| MM Free. 25123904 |
|User and Transaction |
| Client.............. 330 |
| User................ "BIREMOTE" |
| Language key........ "E" |
| Transaction......... " " |
| Transaction ID...... "53E66CC9405502F9E10000000A53F03E" |
| |
| EPP Whole Context ID.... "CEED21FC7C3EC04FA3C0D0912FE05A37" |
| EPP Connection ID....... 00000000000000000000000000000000 |
| EPP Caller Counter...... 0 |
| |
| Program............. "GP4PWAW7JG4VX23SSK75NF4776C" |
| Screen.............. "SAPMSSY1 3004" |
| Screen Line......... 2 |
| Debugger Active..... "none" |
|Server-Side Connection Information |
| Information on caller of Remote Function Call (RFC): |
| System.............. "SP1" |
| Installation number " " |
| Database release... 620 |
| Kernel release...... 640 |
| Connection type 3 (2=R/2, 3=ABAP system, E=external, R=reg. external) |
| Call type.......... "synchronous and transactional type T (emode 0, imode 0)" |
| Inbound TID.........." " |
| Inbound queue name..." " |
| Outbound TID........."0A53F03E141153E6C6641A65" |
| Outbound queue name.." " |
| |
| Client#............. 330 |
| User................."BIWREMOTE" |
| Transaction......... " " |
| Call program........."SAPLERFC" |
| Function module "ARFC_DEST_SHIP" |
| Call destination.. "HNP330" |
| Source server....... "pkgapp2_SP1_03" |
| Source IP address "10.83.240.59" |
| |
| Additional information on RFC logon: |
| Trusted relationship." " |
| Logon return code....0 |
| Trusted teturn code..0 |
| |
| Note: |
| - For Releases < 4.0, information on the RFC caller is not available. |
| - The installation number is provided from Release > 700 |
| Transaction......... " " |
| Call Program........."SAPLERFC" |
| Function Module..... "ARFC_DEST_SHIP" |
| Call Destination.... "HNP330" |
| Source Server....... "pkgapp2_SP1_03" |
| Source IP Address... "10.83.240.59" |
| |
| Additional information on RFC logon: |
| Trusted Relationship " " |
| Logon Return Code... 0 |
| Trusted Return Code. 0 |
| |
| Note: |
| - For Releases < 4.0, information on the RFC caller not available. |
| - The installation number is available from caller Release > 700 |
|Information on where terminated |
| Termination occurred in the ABAP program "GP4PWAW7JG4VX23SSK75NF4776C" - in |
| "INSERT_ODS". |
| The main program was "SAPMSSY1 ". |
| |
| In the source code you have the termination point in line 84 |
| of the (Include) program "GP4PWAW7JG4VX23SSK75NF4776C". |
| The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in |
| procedure "INSERT_ODS" "(FORM)", but it was neither handled locally nor |
| declared |
| in the RAISING clause of its signature. |
| |
| The procedure is in program "GP4PWAW7JG4VX23SSK75NF4776C "; its source code |
| begins in line |
| 23 of the (Include program "GP4PWAW7JG4VX23SSK75NF4776C ". |
|Source Code Extract |
|Line |SourceCde |
| 54|* leave further processing because data is not consistent |
| 55| |
| 56| IF l_inconsistency_found = rs_c_true. |
| 57| p_subrc = 77. |
| 58| EXIT. |
| 59| ENDIF. |
| 60| |
| 61| |
| 62| |
| 63| |
| 64| DATA: l_t_data TYPE ty_t_data, |
| 65| l_s_data TYPE /BIC/B0000674001. |
| 66|*---1363526 Increasing the security to check the number of records inserted in PSA table |
| 67|*---is actually equal to data in l_t_data or p_t_data. |
| 68| DATA: l_rollback TYPE rs_bool, |
| 69| l_count TYPE i. |
| 70| l_rollback = RS_C_FALSE. |
| 71|*---1363526 |
| 72| |
| 73| APPEND LINES OF p_t_data TO l_t_data. |
| 74| |
| 75| CLEAR: l_s_data. |
| 76| l_s_data-partno = p_partno. |
| 77| |
| 78| MODIFY l_t_data |
| 79| FROM l_s_data |
| 80| TRANSPORTING partno |
| 81| WHERE request = p_requestid. |
| 82| |
| 83| |
|>>>>>| INSERT /BIC/B0000674001 |
| 85| FROM TABLE l_t_data |
| 86| ACCEPTING DUPLICATE KEYS. |
| 87|*---1363526 |
| 88| DESCRIBE TABLE l_t_data LINES l_count. |
| 89| IF l_count NE sy-dbcnt. |
| 90| l_rollback = RS_C_TRUE. |
| 91| ENDIF. |
| 92|*---1363526 |
| 93| |
| 94| |
| 95|*---1363526 |
| 96| IF sy-subrc NE 0 OR l_rollback = RS_C_TRUE. |
| 97|* Insert not successful - rollback changes |
| 98| CALL FUNCTION 'DB_ROLLBACK'. |
| 99|*---1363526 |
| 100| p_subrc = 13. |
| 101| ENDIF. |
| 102| |
| 103|ENDFORM. "INSERT_ODS |
| isShmLockId = 0 |
| isUsed = 1 |
| isCtfyAble = 1 |
| hasScndKeys = 0 |
| hasRowId = 0 |
| scndKeysOutdated = 0 |
| scndUniKeysOutdated = 0 |
| ----- Shareable Table Header Data ----- |
| tabi = 0xFFFFFFF1DD5E8E58 |
| pgHook = 0x0000000000000000 |
| idxPtr = 0x0000000000000000 |
| id = 11 (0x0000000B) |
| shmTabhSet = 0x0000000000000000 |
| refCount = 0 (0x00000000) |
| tstRefCount = 0 (0x00000000) |
| lineAdmin = 4 (0x00000004) |
| lineAlloc = 4 (0x00000004) |
| shmVersId = 0 (0x00000000) |
| shmRefCount = 1 (0x00000001) |
| rowId = 18446744073709551615 |
| scndKeyAdmin = 0x0000000000000000 |
| 0A53F03E141153E6C6641A65HNP330 00000001SENDED RSAR_TRFC_DATA_RECEIVE|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 3433433433333343433334334453332222222222222222222222222233333333544444225545555445445455444454|
| 0153603514115356366411658E0330000000000000000000000000000000000135E454002312F4263F4141F2535965|
| 0030004100350033004600300033004500310034003100310035003300450036004300360036003400310041003600|
|PROG |
| SAPLERFC |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 5454454422222222222222222222222222222222 |
| 310C526300000000000000000000000000000000 |
| 005300410050004C004500520046004300200020002000200020002000200020002000200020002000200020002000|
|%_DUMMY$$ |
| |
| 0000 |
| 0000 |
| 2222 |
| 0000 |
| 0020002000200020 |
|NUMBER_OF_FUNCTION_MODULES |
| 1 |
| 0000 |
| 0001 |
| 00000001 |
|SUPPORTABILITY_INFO-DEBUG_CONTEXT_ID |
| |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| 2222222222222222222222222222222222222222 |
| 0000000000000000000000000000000000000000 |
| 0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
|SPACE |
| |
| 0 |
| 0 |
| 2 |
| 0 |
| 0020 |
|SCREEN |
| |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222|
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000|
| 0020002000200020002000200020002000200020002000200020002000200020002000200020002000200020002000|
|No. 4 Ty. FUNCTION |
|Name ARFC_DEST_SHIP |
|SENDER_ID |
| pkgapp2_SP1_03 |
| 00000000000000000000000000000000 |
| 00000000000000000000000000000000 |
| 76667735553533222222222222222222 |
| 0B71002F301F03000000000000000000 |
| 0070006B00670061007000700032005F005300500031005F0030003300200020002000200020002000200020002000|
|SUPPORTABILITY_INFO |
| ######## ## # |
| 000000000000000000000000000000000000000000000000000000 |
| 000000000000000000000000000000000000000000000000000000 |
| 000000002222222222222222222222222222222222222222002220 |
| 000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000200020002000200020002000200020002000200020002000200020002000|
|UNIT_ID |
| ################

Hi Siddartha,
That option is not working.
Thanks

Similar Messages

PSA Data Deletion in SAP BW running on Oracle

Hi,
I deleted 2 failed requests (10000000 Records) from PSA Tables because of the disk space issue for our BW System.
RSA1PSA DELETE PSA DATA
The requests are deleted from the PSA, In BW in can see that there not requests in that particular PSA.
But Basis/Database team raised an issue that the data has been added to the Database
What is this mean and how can I proceed with this
Thanks

This is probably not an Oracle issue.
refer to your other topic at PSA Data Deletion in SAP BW running on Oracle

No SQL (hdbsql / HANA Studio) Connection to SAP HANA Rev. 69 (all services GREEN, running)

Hi all,
after starting HANA instance (locally installed on Linux Laptop) via sapcontrol [1], checking with sapcontrol's GetProcessList as well as HANA Studio Admin Console Diagnosis Mode Shows all Services GREEN, running.
However, when I try to open "Default Administration" in HANA Studio, it "Refreshing Overview" and is busy till infinity.
Trying to connect via \c command of HDBSQL eventually works, but any commands like \ds (list schemas) will run till infinity without returning anything.
SAP Business One for HANA SLD shows the Server but not the Company DBs / schemas.
I attached sapstart.log and statisticsserver_alert_sid.trc.
Any advice is highly appreciated.
Thanks & Kind Regards
Stephan
[1] I start HANA executing: /usr/sap/<SID>/SYS/exe/hdb/sapcontrol -prot NI_HTTP -nr 00 -function StartWait 270 2 OR /usr/sap/<SID>/SYS/exe/hdb/sapcontrol -nr 00 -function Start with user sidadm
[2] The issue occurs since the upgrade from Rev. 53 to HANA Rev. 69 (in the context of upgrading from Business One for HANA PL02 to PL09)

Yes Aleksandr
I think you are right.
After doing many installation of HANA Server in differrent AWS instances it didn't work for me.
But when I installed the HANA Studio on another machine with more RAM it worked.
I think we have to install HANA Studio on another AWS instance with 16 GB RAM to make it run smoothly.
Thanks & Regards
Manu

SAP HANA rev 82 update using hdblcmgui or LCM in studio?

Hi All,
I am updating sap hana to revision 82 from revisoin 81. SAP has suggested to use hdblcmgui for update and LCM in studio is depricated from SPS8.
Using hdblcmgui I dont see an option to upgrade.
SAP displays a note on LCM, suggesting hdblcm, but the update is option is not disabled.
Can I continue to update using LCM or how to upgrade using hdblcmgui?
Please suggest
Regards,
Raj

Hi Stanimir,
Yes the IP associated in AWS console was still the same.Now I've terminated the instance since it was halting our development activity.We are using the trail version of HANA rev 72, at any point of time we can't bring in more than one instance through CAL so we have terminated the corrupted instance and recreated a new instance to proceed further.
But this is really strange behaviour and curious to know, if some else has faced this problem. Unfortunately i couldn't hold the corrupted instance to debug further.
Thanks.
Siva.

PSA tables in SAP BW

Hi experts,
I'm having trouble with creating PSA tables in SAP BW. Can somebody please explain the different ways to create PSA tables.
Thank You Very Much
My Regards...

Hi..
After it is extracted from source systems, data is transferred to the entry layer the data
warehouse, the persistent staging area (PSA). In this layer, data is stored in the same form as
in the source system. The way in which data is transferred from here to the next layerincorporates quality-assuring measures and the transformations and clean up required for a
uniform, integrated view of the data.
When you activate the DataSource, BI generates a PSA table and a transfer program.
The data in the DataSource (R3TR RSDS) is transferred to the PSA.
When you transport the restored 3.x DataSource into the target system, the DataSource
(R3TR RSDS) is deleted in the after image. The PSA and InfoPackages are retained. If a
transfer structure (R3TR ISTS) is transported with the restore process, the system tries to
transfer the PSA for this transfer structure. This is not possible if no transfer structure exists
when you restore the 3.x DataSource or if IDoc is specified as the transfer method for the 3.x
DataSource. The PSA is retained in the target system but is not assigned to a DataSource/3.x DataSource or to a transfer structure.
The PSA table to which the data is written is created when the transfer structure is activated.
A transparent PSA table is created for every DataSource that is activated.
The PSA tables each have the same structure as their respective DataSource. They are also flagged with key
fields for the request ID, the data package number, and the data record number.
InfoPackages load the data from the source into the PSA. The data from the PSA is processed with data transfer processes.
With the context menu entry Manage for a DataSource in the Data Warehousing Workbench
you can go to the PSA maintenance for data records of a request or delete request data from the PSA table of this DataSource. You can also go to the PSA maintenance from the monitor for requests of the load process.
Using partitioning, you can separate the dataset of a PSA table into several smaller, physically independent, and redundancy-free units. This separation can mean improved performance when you update data from the PSA.
In the Implementation Guide with SAP
NetWeaver → Business Intelligence → Connections to Other Systems → Maintain Control
Parameters for Data Transfer you define the number of data records needed to create a new
partition. Only data records from a complete request are stored in a partition. The specified value is a threshold value.
The number of fields is limited to a maximum of 255 when using TRFCs to transfer data. The length of the data record is limited to 1962 bytes when you use TRFCs.
PSA Table
For PSA tables, you access the database storage parameter maintenance by choosing Goto → Technical Attributes in DataSource maintenance. In dataflow 3.x, you access this setting in transfer rule maintenance in the Extras menu.
You can also assign storage parameters for a PSA table already in the system. However, this has no effect on the existing table. If the system generates a new PSA version (a new PSA table) due to changes to the DataSource, this is created in the data area for the current storage parameters.
Define PSA Part. size using transaction RSCUSTV6
Minimum no. of records in a PSA partition
Use program SAP_PSA_PARTITION_COMPRESS for existing PSA
PSA
RSTSODS Directory of all PSA Tables
with regards,
hari kv
Message was edited by:
hari k

Benefits of using SAP CAR compared to SAP BW on HANA

Hi
I' like to understand the benefits of using SAP Customer Activity Repository. How is it better than SAP BW on HANA? What extra functions does the customer get?

Hi Waldemar (wow, I remember E.A.Poe...)
take a look to this document...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ad0a4b07-0301-0010-5095-ef7615676fc0
Hope it helps !
Bye,
Roberto

SAP GUI 7.10 rev 1 for OSX and WIN XP with transaction MIGO

Hello,
When I start transaction MIGO and MIGO_GR, with SAP GUI 7.10 rev 1, I only get a blank screen.
I've tried it in OSX 10.4.9, OSX 10.5.1 and Windows XP, all with the same result.
SAP GUI 7.10 gives the correct screen.
Do you have a solution for this ?

Hi John,
I can reproduce what you are describing. Looks like this problem has been introduced as a side effect of a change for solving another issue
We are going to look into that. In case you want to be able to track the process and get a notification when the fix is available, please create a [support message|https://service.sap.com/message] on component BC-FES-JAV with the description you have posted here.
Best regards
Rolf-Martin

SAP BW on HANA DB Migration - Technical & Functional Assessment Check List Required

Hello Experts,
Typically, Before we start SAP BW on HANA DB migration, we would certainly need Technical & Functional Assessment Check List. As per knowledge, to execute BW on HANA DB migration, we would need HANA Admin and Developer, BASIS and BW consultants.
Can some one share me what exactly these people does in Technical & Functional Assessment ?.
What could be the duration ?.
Does this people require to login into the system's physically and perform any activities ?
Please share me details.
Thanks,
HA

Hi,
with the perferred (and recommeded) database migration option (DMO) as part of the SUM the need of these Functional Assessment Check List might obsolete, as a lot of manual tasks are integrated into the automated process, which were only available as lists in the past.
For an Overview, see - Migration BW on HANA - Update 2014 | SCN
For a detailed step by step, see - SAP First Guidance - Migration BW on HANA using the DMO option in SUM
Best Regards Roland

How to copy the bookmarks which are created in SAP BW 7.3 to New SAP BW on Hana System?

Hi,
We have requirement of moving the Bookmarks from SAP BW 7.3 system to New SAP BW on Hana System.
Please let me know if it is possible? If possible how to do it.?
Thanks,
tms

Hi TMS,
Are you talking about Web template bookmark or QueryDesigner bookmark?
If yes then in both the cases its is stored in your client machine as a browser favourite.This has nothing to do with HANA or BW system.So you can transfer browser favourite file from one system to other.
If you are talking about in anyother context please be precise and more elaborate .
Thanks & Regards
A.Dinesh

SAP S/4 HANA for Oil and Gas

Hi All,
When SAP is announcing its road map for SAP S/4 HANA for Oil and Gas strategy. Which functionalities they are keeping from R/3, which they are dropping and which they are adding. How they are planning to simplify this area!!
Cheers

Dear Phillip,
Cloud enabled software can be easily deployed on-premises but not vice versa.
this could probably be the deciding factory, for every customer : - )
no one would want to block their future...
so even for on-premise, its better to start with cloud and go for hybrid model and i believe
if this lock is there.....
then every on-premise solutions will have a cloud solution.....
want to see your argument on, any one thinking, i want only on-premise, and i will not be needing
cloud solutions in near future..... also for hybrid customers, cloud first and then on-premise would be pain area.

Deleting SAP System in STMS

Hi there,
I want to delete a SAP system in TMS but Im unable to do so because the Delete Option is disabled. My navigation is as follows: STMS -> Overview -> Systems -> < choose the system I want to delete> -> SAP Systems -> Delete. I thought that Im in a Display Mode but I cant find any Display/Change Button here. Has anybody encountered this one? Im logged on as SAP* in client 000.
Thanks in advance

Hi Sohel,
Thank you for the response. Anyway, I did it by doing the following:
1. Log on to this SAP System.
2. Enter Transaction STMS.
3. Choose Overview  Systems. The system overview appears.
4. Choose Extras  Delete TMS configuration.
Thank you very much. This problem is solved now

Connectivity between SAP BW on HANA to ECC & BO

Dear Experts,
Kindly help me for below requirement for SAP BW 7.4 on HANA implementation.
ECC Side:
1.     BW 7.4 SP05 or SP07 required patch level for ECC system (SP and EHP level)?
2.     What are the Configuration needs to be activated to support extraction?
3.     Any other important & technical step to be activated or required?
4.     Pre-req for connectivity
5.     Is there any CTC wizard for Connectivity to ECC (Source system)?
SAP BW on HANA 7.4
What are the pre-req/services/configuration steps on SAP BW 7.4 on HANA side to established for BO & ECC connectivity?
SAP BO 4.0
1.     What are the steps required on BO side to established connectivity?
2.     What is 4.0 SP level require?
Thanks in Advance.
Regards,
Sri

Hi Mahish,
I see this post is from March. I understand you have got some solution to it already.
If yes, could you please share the solution.
Thanks and regards,
Aaloka

Data Provisioning in SAP BW on HANA by DXC step by step guide ?

Hi to all,
I required step by step guide for DXC Data Provisioning for SAP BW on HANA.
Please can any one let me know the URL or PF for same.
Regards
Pavneet Rana

Hi,
Refer the link below
Using the Direct Extractor Connection (DXC) | SAP HANA

How will SAP BW and HANA merge/melt over time?

Though SAP swears HANA would not replace BW but there are good reasons to believe the in-memory analytics platform(HANA) will eventually absorb BW. So, I think it is more accurate to say that SAP BW and HANA are begin to merge.
Any expert in this, can throw some light and educate us if it's so and how?
Thank you.

There are plenty discussion on this topic, but I'll recognize the information might be pretty scattered over very specific ones. Here is my POV in a few bullets:
BW disappearing as a separate box doesn't necessarily mean BW disappearing as a modeling paradigm. In S4, where most operational reporting and analytics are performed on the fly on top of the transactional data, several scenarios are implemented as BW artifacts on top of Virtual Info Providers.
In the long run, you'll have the option to have fully managed modeling (BW LSA++ modeling paradigm) and the fully open SQL based modeling paradigm (based on HANA catalog artifacts & Information views). Both are interchangeable and you could have one single reporting model going through different objects of both modeling paradigms.
There will still be cases where you might need a consolidated centralized DW (e.g. consolidating data from several different sources). In such cases, you won't need to physically replicate data from any HANA source, you will simply virtualize the data from the other HANA Boxes (SDA).
With HANA SPS09 and even more with SPS10+, there will be native DW features in HANA that will help more and more the construction of the native HANA DW scenario. BW will also leverage those features. Look for HANA Data Warehousing Foundation, which include several services such as DDO and DLM.

PSA data deletions

There are scheduled loads to a data target via a meta chain.
I want to include deletion of PSA data as part of the scheduled loads. Just wanted to check the following:
1. There are Process chain process to delete PSA tables
2. It is better to collectively delete the PSA tables
3. Should I include the PSA deletion as the last step for each individual process chain or as a new process in the meta chain
Thanks

Hi,
If you put all PSA tables deletion in one process, then system will delete one by one PSA & process will take more time.
So group PSA tables like Master data PSA, transaction data PSA, PSA in between source system & BI , PSA tables with in BI etc....
Then do analysis on data volume on each PSA. If any table will recieve more volume, then better to keep it alone in single process type where as smaller ones can be grouped. Again it depends on your server work processors available, regular PC design & data volume.
Hope you might get an direction.
Regards,
Arun Thangaraj.

PSA no deletion SAP BW on HANA Rev 61

Similar Messages

Maybe you are looking for