Psa information
hi gurus,
In processing option of InfoPackage we have the fallowing options.
1:PSA and then into DataTargets (package by package)
2:PSA and DataTargets (package by package)
what is the technical difference between these two.Give me the technical reason about which one is best.
regards
balaji.p
Hi
First Option:
In PSA and then at once in InfoCube or InfoObject
Use
Select this field if you want to update data first to the PSA and then want to post it to InfoCubes or the master data table of an InfoObject.
If there is an error while posting to the InfoCubes or the master data table of an InfoObject, the data is in the PSA and you can post the data again from there.
second Option
Select this field if you want to update data to the PSA and post it to the InfoCubes or master data table of the InfoObject in parallel.
When you post data to the PSA and InfoCubes or the master data table of an InfoObject in parallel, a second parallel process is started to post data to the InfoCubes or the master data table of an InfoObject, as long as there are sufficient free dialog processes.
If there is an error while posting to the InfoCube or master data table of an InfoObject, you can post the data from the PSA again.
Hope it helps
Thanks
Teja
Similar Messages
-
Need table containing specific PSA information
I'm hoping this is an easy one, that I'm just missing somehow.
What SAP table contains the field where I can check if a PSA request has been loaded above the PSA level. Basically I need the first column in the list (Request Updated) when you manage on a datasource and see the list of PSAs. It seems like Iu2019ve found nearly every table that contains PSA information, but the right one. ThanksRSTSODSREQUESTPG
RSTSODSPART
RSTSODSREQUEST
try all these ...
rgds, -
How to delete the OLD PSA table altogether?
Hi,
I am in BI for NW04S and CRM4.0 sp6.0.
I created a custom data source in the source system and replicated and used transfer rule/Update rule to load an Data store object in the BI system.
However today , I needed to change some fields of the same data source, and replicated and regenerated the transfer rule, Update rule etc.
Checked the RSA3 in the source system and the data source is working fine.
However When I look into the PSA after an attempted data load, I still fine the old PSA table (/BIC/B0000893000) getting populated and not the new one ( /BIC/B0000893001).
when I look into the show data flow on the ODS i can see the PSA table name, and when I serached in SE11 for that table name I have found both these new and old table.
Although the data source is replicated in to BW system properly for some reason the OLD PSA table is still being used.
How can I correct the situation?
Thanks, will reward the points is the problem is solved.
ArunDear Arun,
Please check in the table (SE16) RSTSODS.
This table stores the PSA information for all the datasouces.
Enter the datasource in question followed by * in the field 'ODSNAME' (for eg. 2LIS_02_SCL*).
This will show you all PSA tables for that Datasource.
The fields DATETO and DATEFROM will tell you, which PSA table is currently in use.
By the way, a new PSA table should be generated only if there is a change in Transfer Structure.
Hope it helps.
thanks,
amol -
Data retention limit for infoproviders??
Hello experts
Can any budy tell me how to find out data retention limit for all infoproviders??
Thanks
Sudeepwhen you mean data retention - there can be multiple data retentions possible :
1. PSA information - this would be the typical PSA data retention that you follow in the process chains
2. Request Information - this would depend if you are using request information archiving which is avaiilable from 7.0 onwards
3. Information in the infoprovider : This would depend if you have used archiving etc ...
typically the data retentions would be
same as in R/3 for ODS which stored detailed information
for cubes - it would typically be about 5 years or so - this would depend on the amount of data available in the infoprovider and how frequently the data is being used... -
Information in PSA for 0IMFA_1 is missing in infocube
Hello everyone,
I've loaded all the necessary data for 0IMFA_1 through all the nessesary infosources via PSA's, also i've preloaded the 0im_fa_ip_8, 0im_fa_ip_9, and 0im_fa_iq_9 (0im_fa_ip_7 is not required).
Information that i see coming for Budget- for mesures, in this case WBS's is present in the PSA but not in the cube itself. Specifically i miss the resolution of 0VTDETAIL
which enables me to seperate the line for original budget to supplments or returns.
As a result of this the amounts <b>aggregate</b> for every line for different approval years.
I suspect start routine which exist in the update rules of the infosource.
has anybody encountered this?
Thanks in advance for your answershi again Adi
check if applicable oss note 723601-0IMFA_1: 0VTDETAIL is not updated correctly.
hope this helps.
Symptom
When you update the 0IMFA_1 InfoCube from the 0CO_OM_OPA_2 and 0CO_OM_WBS_2 InfoSources, the 0VTDETAIL characteristic is not updated.
Other terms
Update rule
Reason and Prerequisites
This is due to an error in the update rules.
Solution
The problem is solved with the following Support Packages:
BW Release 2.1C as of Support Package 29
BW Release 3.0B as of Support Package 21
BW Release 3.20 as of Support Package 13
BW Release 3.30 as of Support Package 6
After you import the relevant Support Package, transfer the affected update rules again from the Content delivered by SAP. -
How to find information abt PSA?
Hi All,
I need to find the PSA's which are not deleted for long time.
Let me know the process.
Thanks
JagadeeshHi Jagadeesh,
Go to Table RSTSODSPART.
Display the records with deletion indicator as blank ( put selection condition = space ie blank)
It will display you the list of PSA table whose PSA requests are not yet deleted.
Using the Technical name of ODS (which is PSA table name in RSTSODSPART) you can find out the datasource name in table RSTSODS.
You can verify this by going to the Manage of that Datasource and checking the requests available there.
Hope this helps you in easily finding out the PSA tables with large PSA requests pending for deletion.
Regards,
Pratap Sone -
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 -
How can i delete data in psa and how can i partation psa?
hi friends,
can i delete data from psa and how can i partation psa?
Thanking u
suneel.hi Suneel,
http://help.sap.com/saphelp_nw70/helpdata/en/7d/724d3caa70ea6fe10000000a114084/frameset.htm
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 <b>Implementation Guide with SAP NetWeaver > Business Intelligence > Connections to Other Systems > Maintain Control Parameters for Data Transfer</b> 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.
transaction SPRO to go implementation guide
at database level
http://help.sap.com/saphelp_nw70/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/frameset.htm
If you are using this database you can also partition PSA tables. You first have to activate this function using RSADMIN parameter DB4_PSA_PARTITIONING = 'X'. SAP Note 815186 includes more comprehensive information on this.
hope this helps. -
Dear Experts,
I have enhanced the extract structure of 2lis_13_vdkon in R/3 with 5 fields which are exist in transfer structure.
I have replicated the data source in BI but unfortunately i have not deleted the data in the PSA.
After replication when i try to activate the data source the system is giving Dump and im not able to see the PSA also.
Please help me out.
When i manage on the data source to c PSA, its giving error like this
Invalid DataStore object name 2LIS_13_VDKON_BB: Reason: No valid entry in table RSTS
The Dump when activating the data source is :
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Exception CX_SY_OPEN_SQL_DB
Date and Time 03.06.2009 09:46:55
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
"CL_RSAR_PSA===================CP" or "CL_RSAR_PSA===================CM006"
"_UPDATE_DIRECTORY_TABLES"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
Regards
venuHi Venu,
The issue I think is the PSA was not deleted cleanly. If you try and activate the PSA you will get the dump again.
..Probably if you go through the ABAP dump you will notice it is pointing to the following code;-
75 * Put the fields of PSA to database without check, otherwise error by
76 * activation of table
77
78 IF p_psa_exists EQ rs_c_false OR
79 i_new_version EQ rs_c_true.
>>>>> INSERT rstsodsfield FROM TABLE l_t_odsfield.
81 ELSE.
82 DELETE FROM rstsodsfield
83 WHERE odsname = l_s_odsfield-odsname
84 AND version = l_s_odsfield-version.
85 MODIFY rstsodsfield FROM TABLE l_t_odsfield.
Put a breakpoint in the code in line 78. and activate the DS..the program should stop in 78...change the value of variable rc_c_false so that line 82 gets executed. This will clean up the PSA entries in table rstsodsfield. Now activate the DS and delete the PSA entries in the PSA table.
We faced the same issue and resolved it this way.
Thanks
-Saif -
Not able to see PSA for the data souce 2lis_13_vdkon after enhaning
Dear Experts,
I have enhanced the extract structure of 2lis_13_vdkon in R/3 with 5 fields which are exist in transfer structure.
I have replicated the data source in BI but unfortunately i have not deleted the data in the PSA.
After replication when i try to activate the data source the system is giving Dump and im not able to see the PSA also.
Please help me out.
When i manage on the data source to c PSA, its giving error like this
Invalid DataStore object name 2LIS_13_VDKON_BB: Reason: No valid entry in table RSTS
The Dump when activating the data source is :
Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC
Exception CX_SY_OPEN_SQL_DB
Date and Time 03.06.2009 09:46:55
How to correct the error
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
"CL_RSAR_PSA===================CP" or "CL_RSAR_PSA===================CM006"
"_UPDATE_DIRECTORY_TABLES"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
Regards
venuHi Venu,
The issue I think is the PSA was not deleted cleanly. If you try and activate the PSA you will get the dump again.
..Probably if you go through the ABAP dump you will notice it is pointing to the following code;-
75 * Put the fields of PSA to database without check, otherwise error by
76 * activation of table
77
78 IF p_psa_exists EQ rs_c_false OR
79 i_new_version EQ rs_c_true.
>>>>> INSERT rstsodsfield FROM TABLE l_t_odsfield.
81 ELSE.
82 DELETE FROM rstsodsfield
83 WHERE odsname = l_s_odsfield-odsname
84 AND version = l_s_odsfield-version.
85 MODIFY rstsodsfield FROM TABLE l_t_odsfield.
Put a breakpoint in the code in line 78. and activate the DS..the program should stop in 78...change the value of variable rc_c_false so that line 82 gets executed. This will clean up the PSA entries in table rstsodsfield. Now activate the DS and delete the PSA entries in the PSA table.
We faced the same issue and resolved it this way.
Thanks
-Saif -
Load fails while running a Process Chain even before loading to the PSA.
Hi Experts,
We are working on BI 7.0 and ECC 6.0 on an IS-U Project.
We are loading Transaction Data using Process Chains. Data load is failing even before loading to the PSA and the error message is as below:
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Inbound Processing
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box, and look at the long text for further information.
Follow the instructions in the message.
Had anyone come across this type of error, if so, what could be the reason of failure and probable solution.
Your time is very much appreciated.
Thanks in Advance.
Best Regards,
Chandu.Hi,
It might be a network connection between the source system and BW? Can you get your Basis colleague to look into the connection?
Hope this helps.
Cheers,
Gimmo -
Error While loading the data into PSA
Hi Experts,
I have already loaded the data into my cube. But it doesn't have values for some fields. So again i modified the data in the flat file and tried to load them into PSA. But while starting the Info Package, I got an error saying that,
"Check Load from InfoSource
Created YOKYY on 20.02.2008 12:44:33
Check Load from InfoSource , Packet IP_DS_C11
Please execute the mail for additional information.
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Pls help me in this......
With Regards,
Yokesh.Hi,
After editing the file did you save the file and close it.
This error may come if your file was open at the time of request.
Also did you check the file path settings.
If everything is correct try saving the infopackage once and loading again.
Thanks,
JituK -
ERROR DURING LOADING DATA FROM PSA TO DSO IN "PRUEFMBKT"
Respected all
I am trying to load data through an r/3 field( pruefmbkt, char-40length) to infoobject. the data is coming correctly to psa but when i am loading it in to dso or infocube request is turning red giving following error message--
Value '010/12.05-112.15/hold on not operate' (hex.
'3031302F31322E30352D3131322E31352F686F6C64206F6E20') of characteristic
PRU_LSIL contains invalid characters
Message no. BRAIN060
Diagnosis
Only the following standard characters are valid in characteristic
values by default:
!"%&''()*,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ.+
Furthermore, characteristic values that only consist of the character #
or that begin with ! are not valid.
You are trying to load the invalid characteristic value 1. (hexidecimal
representation 3031302F31322E30352D3131322E31352F686F6C64206F6E20).
Procedure for System Administration
Try to change the invalid characters to valid characters.
If you want values that contain invalid characters to be admitted into
the system, make the appropriate setting in BW Customizing. Refer to the
documentation describing the requirements for special characters and the
possible consequences.
For more information on the problems involved with valid and invalid
characters, click here.
kindly give me the solution how to deal with this problem.
thanks
abhayHI Abhay,
please check if the infoobject corresponding to field PRU_LSIL in BW system has lower case checkbox enabled in the infoobject properties, as the value '010/12.05-112.15/hold on not operate' coming from R/3 has lower case alphabets.
Hope this helps.
Regards,
Umesh. -
Hi All,
We are trying to delete the PSA requests by manually but when we go to few PSA tables there we are not able to delete the requests from the Data Source.
The PSA Table name is also like this /BIC/B0000535001.
When I try to delete the one request from the PSA its throwing error as RSDU_TABLE_DROP_PARTITION_MSS Error while creating the clone table /BIC/B0000535001
Can we know what the clone table and How to solve this issue ASAP.
Thanks
SravaniHi Sravani,
Please try the below things, hope this may solve ur problm.
There are two main steps you must perform:
(1) fix the reason why the table drop fails and then
(2) remove the shadow tables so processing can continue.
To determine why the partition drop failed, we recommend checking:
1. The SQL Server Error Log - this will tell you if the transaction log ran out of space. The log can be seen via SQL Server tools or transactions ST04/DBACOCKPIT.
2. The Blocking Lock Monitor - as long as you have the monitor job active, this transaction will show if there is blocking occurring. This monitor is in transactions ST04/DBACOCKPIT.
3. The Deadlock Monitor - will show if there was a deadlock at the time of the partition drop. This monitor is in transactions ST04/DBACOCKPIT.
After you have determined the root cause, you must correct it before removing the shadow tables. If the log ran out of space then you must move it to a drive with enough space or add another log file on a different drive with enough space. If the root cause is blocking or deadlocks then first search SAP Notes for known solutions or, secondly, open a customer message in BC-SYS-DB-MSS if you need help. In all other cases, open a BC-SYS-DB-MSS customer message so the development support team can assist you in finding the cause.
After you have corrected the root cause, you must remove the shadow tables. You can do this with the latest version of the SAP ABAP program RSDD_MSSQL_CUBEANALYZE (install the latest version which is attached to SAP Note 991014). After the program is installed, execute it with SE38 and choose Settings -> Expert Mode. Acknowledge the warning, press the Detail button under the Determine All Shadow Objects item and press Start Check. Then select each shadow table and press Delete Clone Table.
For more information regarding SAP BW's use of SQL Server table partitioning, read the white paper titled "Table Partitioning in SAP BI on Microsoft® SQL Server# 2005/2008". The paper is currently available for download at:
http://www.microsoft.com/isv/sap/technology/interop/bi.aspx
Regards
KP -
Dump while Executing DTP - PSA To ODS
While executing DTP, I am getting the following ABAP Dump: "MESSAGE_TYPE_X".
"MESSAGE_TYPE_X" " "
"SAPLRSSTATMAN" or "LRSSTATMA
"RSSTATMAN_GET_PARTTAB_PSA"
I was facing some selection issue in the Info Package (generic Data source), then I have deleted all the entries in the table u201CRSSELDONEu201D against that Data source. After that I was able to load the data from R/3 server to PSA smoothly.
Now I am facing the issue while loading data from PSA to ODS through DTP. I already activated all the objects again (Data Source, ODS, & DTP).
Please guide me.
Thanks in Advance u2026u2026
KiruthikaI tried with Error DTP, I am getting same Dump. When I click Execute button with debug option directly it's going to Dump.
I am getting the following Error message
Runtime Errors MESSAGE_TYPE_X
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSSTATMAN" or "LRSSTATMA
"RSSTATMAN_GET_PARTTAB_PSA"
Information on where terminated
Termination occurred in the ABAP program "SAPLRSSTATMAN" - in
"RSSTATMAN_GET_PARTTAB_PSA".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 1165
of the (Include) program "LRSSTATMANU10".
I have deleted all the entries in the table u201CRSSELDONEu201D against that Data source. After that I was able to load the data from R/3 server to PSA smoothly. As per my understanding table u201CRSSELDONEu201D is used for info package selection.
If there any problem related to this, please guide me.
Regards,
Kiruthika
Edited by: kiruthika marappan on Sep 4, 2009 2:16 PM
Maybe you are looking for
-
I can not uninstall Office 2013 from command line
Hi, I have been stuck for a while trying to uninstall Office 2013 via command line. Installation file was downloaded from Volume Licensing Service Center, Uninstall.xml file for silent uninstallation looks like this: <Configuration Product="ProPlus">
-
Logical standby database to physical standby database
I already start my logical standby database and I want to return it again to physical standby database. So what should I do?
-
I dropped my ipod touch 4g(black) on the floor at chipotles(concrete) freaking out!!
ok so i dropped my ipod on concrete and now there is a dent beside the screen on the lower sound button when i use my ipod it has this huge black speckly blob by the dent and everything is extremely white it is possible to use it but very annoying an
-
Videora must be in the SP profile setting!!!!
As I'm browsing the board I see that people keep getting frustrated with the best piece of Windows based iPod software out there. Here's the solution: The "One Click Profile" under the settings must be as follows: SP/320x240/768Kbps Stereo/128Kbps Fo
-
Hi!! In the code below I try to read a number and a String to a file. But the number can't be extracted when reading from the file again! Why can that be?...;/ kR\\j* import java.io.* ; import java.util.* ; public class TestaNu public static voi