Hi,
Our process chain got failed today showing an errors of invalid charcters. I maintained in RSKC transactio for those invalid charcters. But still my request in DSO is in red status only. When I try to delete from DSO, I could not delete the request. I am able to delete from PSA and reload agin. But iam unable to delete from DSO. I really don't understand the reason behind this........
Can anyone help me...........?
Suman
SAP BW 7.0
I am writing a SAP variable via a customer user exit for the characteristic 0FISCPER (Fiscal Year Period). I would like to generalize the code for these user exit and that is why I need the value of the restriction of the characteristic 0FISCVARNT (Fiscal Year Variant) in the concerning query. In my query definition the characteristic 0FISCVARNT is restricted to the value "[K4] Calendar Year, 4 spec . periods", but I would like to read this value in my user exit in stead of hardcoding it.
Does anybody know i can read in my user exit the values of the characteristic restrictions (filter values) of the concerning query.
Does anybody knows if this is possible and how this can be implemented? I have already checked all the posts in sdn on de the subject "SAP variable user exit".
Kr, Guy Verschueren
Hi All,
We are planning to upgrade BW 3.5 to 7.3 ( technical upgrade only).
If any one has done this can you please share issues with us.
We know that we have to have migrate teh securites from 3.5 to new 7.3 authorizations. IS this migration too complex?
We use lots of Woorkbooks, will that also be impacted if yes probable correcting steps?
Your thoughts on current data loads and Info-source impacts will also be appreciated.
You inputs will really help me.
Thanks in Advance to you all
Mukesh
Hi Gurus,
We are getting a dump called ASSERTION_FAILED in our BI 7 system.We have implemented the support packs upto the level 20.We have implemented the note 1282485.But still no luck.
Short text
The ASSERT condition was violated.
What happened?
In the running application program, the ASSERT statement recognized a
situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the
activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort"
for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following checkpoint group was used: "No checkpoint group specified"
If in the ASSERT statement the addition FIELDS was used, you can find
the content of the first 8 specified fields in the following overview:
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
-
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:
"ASSERTION_FAILED" " "
"CL_RSTRAN_GEN_GROUP===========CP" or "CL_RSTRAN_GEN_GROUP===========CM00M"
"SET_ATTRIBUTS_BY_RULE_"
Termination occurred in the ABAP program "CL_RSTRAN_GEN_GROUP===========CP" -
in "SET_ATTRIBUTS_BY_RULE_".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 57
of the (Include) program "CL_RSTRAN_GEN_GROUP===========CM00M".
Please help.
Thanks,
Jagadish
To get the list of PSA table names we have a SAP Standard table RSSTATMANPSA. Can you please tell me what is the SAP standard table for Change Log table names ??
Please search the forum before posting a thread
Edited by: Pravender on Feb 12, 2012 1:51 PM
Hi,
When I transport a transformation from Dev environment to Q environment, the transformation stays inactive in the QA environment.
The Scenario:
Datasource - db connect. Added a few new fields to the datasource. The change are made in the SAP BW system and data load to the DSO is successful. When the data elements - Datasource, DSO, Transformation and DTP were transported to the Q system, the transformation in the Q system was inactive.
First time when all the elements were transported in the same request, the request got failed with a message that the transformation was inactive.
Later when the transformation was transported to Q system, the transport request was successful. But the transformation was still inactive. When we analyzed the transport logs, the routines associated with the transformation was successful, but there was no mention about the transformation in the logs.
System details : SAP BW 7.3 SP 5
Alternatives tried:
1. Activated the transformation through the program - RSDG_TRFN_ACTIVATE. The transformation was activate. But the new fields mapping was missing.
2. The Logical system mapping was missing. So added that through Tools --> Conversion Logical system names.......
3. Transported the data elements individually --> Datasource and DSO first in one request and then Transformation in a separate request.
4. Deleted the transformation in the Dev system and assigned it to a Transport request and transported it to the Q system. The transformation in the Q system got deleted. Re-created the transformation in the Dev system and transported it to the Q system. Only the T-version of the transformation was available in the RSTRAN table. A-version of the object was not present in the RSTRAN table.
I guess this must be a SAP system issue.
I searched in the internet for any OSS notes related to this, but was not able to find anything till now.
If any of you have come across this kind of situation, please share your experience.
Thanks and Regards
Premnath
9980894400
I need to prepare a spec for all the fields from an infocube. Please tell me an easy way to document the fields from an infocube. I mean there should be some table in sap bi where we can export the fields to excel and there on copy it to a word doc. Please tell me the infocube table name where we have all the iobj field names. Hope you got my requirement.
thanks,
Daniel
Hi All,
We were trying to install BW Admin Cockpit in SAP Netweaver BW 7.3 Version.
However, we are facing below runtime error & it gives Dump everytime -
"ASSERTION_FAILED"
Terminated Program "CL_RSSH_DTP_PROXY============CP"
Same Error is being faced even by entering T Code RSA1 as well....
Kindly let me know if anybody has solution for this Issue.
Thanks
Swapnil
SAP BW 7.0
I am writing a SAP variable via a customer user exit for the characteristic 0FISCPER (Fiscal Year Period). I would like to generalize the code for these user exit and that is why I need the value of the restriction of the characteristic 0FISCVARNT (Fiscal Year Variant) in the concerning query. In my query definition the characteristic 0FISCVARNT is restricted to the value "[K4] Calendar Year, 4 spec . periods", but I would like to read this value in my user exit in stead of hardcoding it.
Does anybody know i can read in my user exit the values of the characteristic restrictions (filter values) of the concerning query.
Does anybody knows if this is possible and how this can be implemented? I have already checked all the posts in sdn on de the subject "SAP variable user exit".
Kr, Guy Verschueren
Hi,
When I attempt to release my transport containing TRFN and DTP coming from Source 2LIS_12_VDITM to a DSO I get the following error before release:
Message no. RSO657
I am thinking this is because I have noticed from previous developers the DataSource 2LIS_13_VDITM in BWQ and BWP has the package $TMP.
I am concerned that if I add the BW DataSource to my Transport as is suggested by the error that this will break my Deltas when transported to BWQ or BWP.
Anyone have any suggestions or words of encouragement???
Thank You,
Hi Guru's/Experts,
I am Getting a Short dump when iam loading the data from DTP to Cube. I know its long query to post- but no choice left.
1) Error message as below.
Runtime Errors MESSAGE_TYPE_X
2) Error analysis
Short text of error message:
Internal error: invalid call - Contact SAP
Long text of error message:
Technical information about the message:
Message class....... "RSTRAN"
Number.............. 000
Variable 1.......... "invalid call"
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
3) How to correct the error
"MESSAGE_TYPE_X" " "
"GP_MET_RSTRAN_SECTION_GEN" or "GP_MET_RSTRAN_SECTION_GEN"
I can understand this error is throwing from SAP program which is not able to generate the Perform Class in Code.
When i compaired the code from Dev to Quality there the missing code i found the below Message
$*$ end of global - insert your declaration only before this line *-*
METHODS
new_record__end_routine
IMPORTING
source_segid type rstran_segid
source_record type sytabix
EXPORTING
record_new type sytabix.
My question is does this METHOD will create a short Dump. If not please gimme the alternate solution.
Your Help is highly appreciated
Thanks in Advance
Hi,
When I transport a transformation from Dev environment to Q environment, the transformation stays inactive in the QA environment.
The Scenario:
Datasource - db connect. Added a few new fields to the datasource. The change are made in the SAP BW system and data load to the DSO is successful. When the data elements - Datasource, DSO, Transformation and DTP were transported to the Q system, the transformation in the Q system was inactive.
First time when all the elements were transported in the same request, the request got failed with a message that the transformation was inactive.
Later when the transformation was transported to Q system, the transport request was successful. But the transformation was still inactive. When we analyzed the transport logs, the routines associated with the transformation was successful, but there was no mention about the transformation in the logs.
System details : SAP BW 7.3 SP 5
Alternatives tried:
1. Activated the transformation through the program - RSDG_TRFN_ACTIVATE. The transformation was activate. But the new fields mapping was missing.
2. The Logical system mapping was missing. So added that through Tools --> Conversion Logical system names.......
3. Transported the data elements individually --> Datasource and DSO first in one request and then Transformation in a separate request.
4. Deleted the transformation in the Dev system and assigned it to a Transport request and transported it to the Q system. The transformation in the Q system got deleted. Re-created the transformation in the Dev system and transported it to the Q system. Only the T-version of the transformation was available in the RSTRAN table. A-version of the object was not present in the RSTRAN table.
I guess this must be a SAP system issue.
I searched in the internet for any OSS notes related to this, but was not able to find anything till now.
If any of you have come across this kind of situation, please share your experience.
Thanks and Regards
Premnath
9980894400
Hi Guru's/Experts,
I am Getting a Short dump when iam loading the data from DTP to Cube. I know its long query to post- but no choice left.
1) Error message as below.
Runtime Errors MESSAGE_TYPE_X
2) Error analysis
Short text of error message:
Internal error: invalid call - Contact SAP
Long text of error message:
Technical information about the message:
Message class....... "RSTRAN"
Number.............. 000
Variable 1.......... "invalid call"
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
3) How to correct the error
"MESSAGE_TYPE_X" " "
"GP_MET_RSTRAN_SECTION_GEN" or "GP_MET_RSTRAN_SECTION_GEN"
I can understand this error is throwing from SAP program which is not able to generate the Perform Class in Code.
When i compaired the code from Dev to Quality there the missing code i found the below Message
$*$ end of global - insert your declaration only before this line *-*
METHODS
new_record__end_routine
IMPORTING
source_segid type rstran_segid
source_record type sytabix
EXPORTING
record_new type sytabix.
My question is does this METHOD will create a short Dump. If not please gimme the alternate solution.
Your Help is highly appreciated
Thanks in Advance
Hi,
Our client is upgrading BW server from SAP Netweaver 7.0 to Netweaver 7.3 and they want us to carry out pre and post upgrade testing.
Kindly share your thoughts on the areas where we need to focus on post upgrade testing. What are the changes that are going to be made available in SAP Netweaver 7.3 for BW. If there is any set of questionairre/checklist kindly share.
Thanks!!
Hi,
Our process chain got failed today showing an errors of invalid charcters. I maintained in RSKC transactio for those invalid charcters. But still my request in DSO is in red status only. When I try to delete from DSO, I could not delete the request. I am able to delete from PSA and reload agin. But iam unable to delete from DSO. I really don't understand the reason behind this........
Can anyone help me...........?
Suman
To get the list of PSA table names we have a SAP Standard table RSSTATMANPSA. Can you please tell me what is the SAP standard table for Change Log table names ??
Please search the forum before posting a thread
Edited by: Pravender on Feb 12, 2012 1:51 PM
Hi All,
We were trying to install BW Admin Cockpit in SAP Netweaver BW 7.3 Version.
However, we are facing below runtime error & it gives Dump everytime -
"ASSERTION_FAILED"
Terminated Program "CL_RSSH_DTP_PROXY============CP"
Same Error is being faced even by entering T Code RSA1 as well....
Kindly let me know if anybody has solution for this Issue.
Thanks
Swapnil
Experts,
I need to populate 0CALWEEK, 0CALMONTH, 0CALQUARTER & 0CALYEAR in the cube from 0CALDAY in DSO. I wrote the below code in the expert routine. 0CALMONTH & 0CALYEAR are populating perfect, but 0CALWEEK is coming in wrongly (displays 201308 for 8/12/2013) and 0CALQUARTER is throwing an error at the time of DTP load.
I have been successful in the past with regular transformations where in a one to one mapping between 0CALDAY & 0CALWEEK/0CALQUARTER etc, but this is my first time doing this in an Expert Routine. Please share your solutions. Thanks.
..............................................................................
LOOP AT SOURCE_PACKAGE into source_pkg.
Clear result_pkg.
Move-corresponding source_pkg to result_pkg.
result_pkg-CALMONTH = source_pkg-CALDAY.
result_pkg-CALQUARTER = source_pkg-CALDAY.
result_pkg-CALWEEK = source_pkg-CALDAY.
result_pkg-CALYEAR = source_pkg-CALDAY.
Hi All,
After a system copy from production to dev all our transfer rules and infopackages are missing.
Whats is the best way to get these back??
I have read a few post on the forum but need some clarification on the exact approach.
Thanks.
Nick.
Hi Gurus,
We are getting a dump called ASSERTION_FAILED in our BI 7 system.We have implemented the support packs upto the level 20.We have implemented the note 1282485.But still no luck.
Short text
The ASSERT condition was violated.
What happened?
In the running application program, the ASSERT statement recognized a
situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the
activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort"
for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following checkpoint group was used: "No checkpoint group specified"
If in the ASSERT statement the addition FIELDS was used, you can find
the content of the first 8 specified fields in the following overview:
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
" (not used) "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
-
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:
"ASSERTION_FAILED" " "
"CL_RSTRAN_GEN_GROUP===========CP" or "CL_RSTRAN_GEN_GROUP===========CM00M"
"SET_ATTRIBUTS_BY_RULE_"
Termination occurred in the ABAP program "CL_RSTRAN_GEN_GROUP===========CP" -
in "SET_ATTRIBUTS_BY_RULE_".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 57
of the (Include) program "CL_RSTRAN_GEN_GROUP===========CM00M".
Please help.
Thanks,
Jagadish