Opening analyzer with transaction RRMX

Hello all.
I want to open the BEx Analyzer from the BW system by calling transaction RRMX.
I created a SAP Transaction iView that calls transaction RRMX.
I defined the "Start SAPGUI for Windows" as "auto" and the "Application Parameters" as "WBID=<workbook name>".
When I preview the iView I'm asked if I want to save or open a SAP GUI Shortcut file. When I open this file I get a login screen to the BW system with an error message "This system rejects all logons using SSO tickets".
I also tried transaction RRMXP and the same thing happened.
We use EP6 SP9 and no SSO is defined for our portal, we use user mapping at the moment. With other transactions in BW (for example SM50) I don't have any problems- the portal uses the user name and password defined in the user mapping.
Any ideas on how to solve this problem will be appreciated.
Regards,
Sagi Lefler

hi Sagi,
yes it did work with user mapping. check these steps out
1)select "r3 dedicated" from the template list of your systems and in connector option give your BW app host, port no, sys no, log name, client etc
2)in user mgt select UIDPW and admin,user
3)select sap transaction iview.in application parameters give WBID=85I8QK2OMOZLWLBQM2P831KLU (for example)
transaction code RRMXP and ur bw sysname.
4)go to personalize and enter ur userid and password for ur BW sys.
hope this helps
-Madhuri

Similar Messages

Hyperion Analyzer with Transactional Data

Has there been anyone out there that has used Analyzer to "drill through" to transactional data without the use of integration server and/or SQL drill through?

I have an early release of Analyzer 6.0.1. With this release I was able to successfully 'drill-through' to tables in an Oracle database. The setup was quite easy, and, as you stated, did not require EIS or SQL drill-through.

Problem with the transaction RRMX

Hi,
I install the sap gui 7.10 with business explorer but when I execute the transaction RRMX the excel screen oppened but the sistem close it very fast.
Someone have an idea?
I have BW 3.5
Thanks!

Hi,
I have this problem, I solved problem by updated with patch level 3 and used excell 2000 ,
a®

Launch of new NW2004s-BI Frontend from transaction rrmx

Hi,
my customer has upggraded to NW2004s. We are on Support Package 7. The NW2004s-BI Frontend is FEP701.
When I enter transaction <rrmx> the "old" BW 3.5 Bex Frontend launches.
Is there a way to have <rrmx> call the new NW2004s-BI frontend?
I have been toggling the "Launch Legacy Version from RRMX" flag on and off in the new NW2004s BI Frontend but nothing but the 3.5 Analyzer lauches?
Can you help with that issue?
Thanks
Christian

Hi Christian! in this reply you could find your solution.
 but attached file is available only by OSS!
If you think this helps, don't forget give me points!
see note 933768
Symptom
Error in Business Explorer Components like Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog
Other terms
Business Explorer, Frontend, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog, Selector, characteristic restriction, filter, filter value, variables
Reason and Prerequisites
You have installed NetWeaver 2004s BI Add-On Frontend Patch 700, and you need a hotfix (advance correction) for certain problems that are caused by the BI Add-On (frontend).
This note will be updated as solutions for newly detected problems are available. Hence you should check the actuality of this note, if you have already applied hotfixes for the patch level of your BI Add-On.
Solution
Attached to this note you will find frontend components (DLL files) that correct certain errors. You will find a list and descriptions of solved problems in the following. It is recommended to replace all respective DLLs in the setup directory of the BI Add-On with the attached DLLs. However, you can also selectively replace individual DLLs that are required for the solution of problems that you encountered. In the following it is described which DLLs are required to solve specific problems.
The Open/Save dialog and the Value Help dialog (selector) are components that are used by several SAP Business Explorer applications. Hence, if you encounter errors in one of those applications, please also check the dialogs sections below for a solution.
SAP Business Explorer Web Application Designer
SAP Business Explorer Analyzer and Variables Screen
New property to adjust the size of the Drop-down item added.
Known errors occuring, while entering the values in variable screen pop-up, have been corrected
SAP Business Explorer Query Designer
Corrected critical error at saving of reusable elements (especially evident with calculated key figures using variables). We strongly recommend to apply this hotfix.
If a presentation hierarchy is selected for a drilldown, it is not possible any more to restrict the characteristic to a hierarchy node from another hierarchy.
Refresh problem solved with repeated query execution in web browser.
Dimension preview is enabled again and allows scrolling.
Problems with query variable order presentation and editing are solved.
Structure member selections using calculated key figures display further calcuated key figure properties.
Error with characteristic value variables replaced by queries corrected.
Errors with structure member descriptions corrected.
There were too many characteristics offered as aggregation reference for formulas. Now only characteristics of the corresponding InfoProvider are listed.
Paste of multiple characteristics when restricting structure member selections is working again.
Error when creating structure member hierarchies with formulas is solved.
Copy and paste of a structure member without changing the focus was not possible. This is now enabled.
Variables could not be entered in the editors for conditions and exceptions. This is possible now. Also variables for key date can now be entered.
Error when adding attributes by drag and drop corrected.
Sorted display of query elements corrected.
Paste of a second reusable structure enabled again.
It is not allowed to restrict a structure member to a characteristic value if the other structure already contains a restriction of this characteristic. This check is now implemented.
Sometimes values for Zero Suppression were not correctly saved. This is corrected now (updated 04 May 2006)
Restricted and Calculated key figure folders did not display if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
It was not possible to delete a Characteristic from filter if a reusable filter contained this characteristic (updated 04 May 2006)
Paste of InfoObjects and reusable Elements was errorneously possible to Exception and Condition area. Is frobidden now. (updated 04 May 2006)
Text variables with repalcement path are now always not inputable (updated 04 May 2006)
Variables were not displayed correctly if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
There could be a runtime error (occasionally) in Anaylzer after user selected "Exit and use query" in Query Designer due to a still processed error check. (updated 04 May 2006)
There is now a check if a presentation hierarchy exists on server. If not, the user is informed by a warning (updated 04 May 2006)
New warning informs user about non existing presentation hierarchies (updated 15 May 2006)
Formula variables with replacement path "by attribute" offer now only numerical attributes. (updated 15 May 2006)
Empty formulas now cause an error message, not just a warning message, because queries with empty formulas are not executable. (updated 15 May 2006)
For compounded characteristics in InfoProvider tree the compound info was not displayed in all cases, this is corrected now (updated 15 May 2006)
Variables replaced by query result or by a replacement table can be just used in Filter. The user is informed by an error message if such variables are used anywhere else (updated 15 May 2006).
Queries with cell were sometimes saved with wrong coordinates for cells. Such queries are not executable. This is corrected now. Wrong queries are auto corrected, if they are loaded and saved with this corrected version (updated 15 May 2006).
Problem with "hanging" explorer during execution of a query in web solved (updated 15 May 2006).
Variable order setting is now also possible for new queries (updated 15 May 2006)
Empty structures cause now an error message, not just a warning message, because queries with empty structures are not executable. (updated 15 May 2006)
There were some cases where Text variables were not stred correctly and as a consequence not replaced. All known issues are now corrected. (updated 15 May 2006)
With this hotfix the Note 948374 should be also implemented in the backend system, it prevents some save prolems.
Small usability improvements in Varible-, Exception- and Condition editor (updated 23 May 2006)
Multiple keyfigures are not allowed in Filter, but it was possible to do this with copy and paste of multiselected keyfigures (updated 23 May 2006)
There were cases where users could create different components with same technical names, this is checked now (updated 23 May 2006)
Variables replaced by query result or by a replacement table reported an incorrect message if they were defined with "Input allowed = true", this is corrected (updated 23 May 2006)
SAP Exit variables were errorneously not allowed to be used in non content systems, this is corrected (updated 23 May 2006)
In variable editor for Formula variables replaced by attribute value there were not offered all possible numeric variables offered. This caused a runtime error if especially variables created with Query Designer 3.x were edited. This is corrected now (updated 23 May 2006)
Due to a program error any saved formula might have been saved incorrectly, if it is using any variables (formula or text variables). This is a critical error which might lead to not understandable error messages during query execution or missing text variable replacement for formulas. The error is corrected the was that any corrupt query can be loaded and after a save it is repaired. We strongly recommend to use this hotfix for all installations!
SAP Business Explorer Report Designer
Introduced Versioning and added Version checks. More recent versions of Report Designer are able to design reports with new features. If such a report is edited with an older version of Report Designer some design features might be lost in the report or loading the report might not be possible.
Images from Mime repository can be added to the report.
Sequence of Report Sections is saved and loaded in the right order.
Query Text Elements for more than one Dataprovider are correctly dsiplayed in the Report Item. Property Dialog shows the name of the Dataprovider of the selected Text Element.
Conditional Formatting for Hierarchy nodes enabled.
Open Dialog/Save Dialog
Value Help Dialog (Characteristics Restriction/Filter Selection)
Search can be performed by entering the search criteria in value help dialog and then by pressing the <Enter> keyboard button
or see note 929632
Symptom
There are errors in Business Explorer components such as Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog.
Other terms
Business Explorer, Front end, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog, selector, characteristic restriction, filter value, variables
Reason and Prerequisites
You have installed NetWeaver 2004s BI Add-On Front End Patch 02 and you require advance corrections for certain problems that are caused by the BI Add-On (front end).
Solution
You can find front end components (DLLs) that correct the errors described below attached to this note. We recommend that you replace all attached DLLs in the setup directory of the BI Add-On. However, you can also replace only those DLLs required to correct a problem that occurred in your system. The following sections describe which DLLs correct which problems.
The Open/Save dialog and the input help dialog are components that are used by several SAP Business Explorer applications. Therefore, check whether the correction of a problem that occurred in one of the applications is described there.
SAP Business Explorer Web Application Designer
 Up to now, there are no advance corrections.
SAP Business Explorer Analyzer and variable screen
 To correct the problems in the Analyzer and the variable screenthat are described here, the files BExApi.dll, BExAddin.dll, BExAnalyzer.xla, BExVariableScreen.dll, BExLocalFormulaParser.dll, BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
In the variable screen, the formats for the calendar year and calendar month characteristics have not been transferred correctly to the server. As a result, error messages occurred during the check.
When deleting an item in design mode, the system did not remove the displayed data of the item in analysis mode, rather it still displayed this data.
The display of the checkbox item and the radio button item has been corrected.
Errors occurred when you saved variants on the variable screen. All known errors have been corrected.
The security certificate for the Analyzer has expired and the advance corrections contain a new security certificate.
SAP Business Explorer Query Designer
 To correct the problems in the Query Designer that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
Executing in the Web no longer opens different browser windows, rather the system always uses the same one.
In certain cases, queries that contain attributes were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
In certain cases, queries that contain cells were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
If queries are saved incorrectly (for example with incorrect attributes or incorrect cells), the system issues messages for all cells that are incorrect and it refers to a possible solution. Currently, all text messages are in English and they will be translated in Support Package Stack 8.
You can now insert and resort attributes at any position. You can do this using drag and drop or cut and paste.
Formula variables with replacement path now also permit the setting of the dimension.
If you edited attributes for an object and you then saved your changes immediately without exiting the field, the system did not save the change in this field. This problem has now been corrected.
Texts of attributes are now displayed correctly after you load the query again (up to now, the system displayed only technical names).
Constant selection was not displayed correctly in the context menu of a selection. Now, the system displays a checkmark to indicate that constant selection is activated.
Attributes of display hierarchies are now displayed and saved correctly.
The system no longer displays operators twice in technical names in formulas. Up to now, [+] + was displayed.
The system no longer displays UIDs as technical names for structure items and cells in formulas.
Structures with hierarchical structure items: In certain cases, structure elements disappeared during the hierarchical setup. However, these were saved and they caused an endless loop on the server. This problem has been corrected. You can use the BEx Query Designer to open queries that were saved with these "vanished" structure elements and the "vanished" structure elements are displayed again.
Errors and terminations on the server now cause a message in the message window of the BEx Query Designer telling you to close and to restart the BEx Query Designer.
For variables with replacement path, the system displayed too many characteristics (some technical characteristics) for the replacement characteristic. This problem has been corrected.
Further consistency checks have been implemented and the corresponding messages are displayed in the message list. The system now checks not only queries but it also checks restricted and calculated key figures, variables, and cells.
If you change a reusable element, the system does not save it automatically. An information message is displayed telling the user that saving the element may affect other queries. You can save the element normally using a save function in the context menu. If the element is used in the query, it is always saved with the query.
When you exit the BEx Query Designer, the system checks which reusable elements have not yet been saved. The system displays a list containing all unsaved elements and it asks the user whether these elements should be saved.
There is a new menu function "Save All" that saves all changed reusable elements.
When you select text variables, the system now displays the correct variable type "Text variable" in the selection.
You were able to use cut and paste for conditions and exceptions, but this always caused a runtime error. The functions have been deactivated for the moment to avoid program terminations.
You can now define variables with a replacement from an attribute.
You can now also display only posted values in the value help (read mode D).
For text and formula variables with replacement path, you can no longer create on the technical characteristic 1TEXT or 1FORMULA. Any existing variables (that were created with earlier versions) are reported as incorrect and you should delete them.
For restricted or calculated key figures or for variables, if you made changes and you saved these changes online and confirmed with OK, the system sometimes issued message "Not saved - object is not changeable". This problem has been corrected.
When creating new reusable elements, the system only checked if the user was authorized to create new elements for this InfoProvider, but it did not check whether the user was authorized to create elements with the given technical name. This problem has been corrected.
You can now move and copy cells using cut and paste and copy and paste. Unfortunately, you still cannot use drag and drop.
In formulas, multiline headers of structure elements are correctly displayed in single lines and no longer in several lines.
In certain cases, hierarchy node variables were saved without a corresponding hierarchy assignment and you could not use them in the report that was being executed.
After each time you saved data, the context menu of the currently selected object was incorrect. This problem has been corrected.
You could not delete filter values directly in the BEx Query Designer, rather you had to do this in the filter dialog.
You could not change characteristics of attributes.
The system now issues a corresponding success message after each successful saving process.
SAP Business ExplorerReport Designer
 Up to now, there are no advance corrections.
Open dialog/Save dialog
 Up to now, there are no advance corrections.
Input help dialog (characteristic value restriction/filter selection)
 To correct the problems in the value help dialog that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
You can now edit variables in the value help for all variable types and not only for characteristic value variables.
You can now create variables in the value help for all variable types and not only for characteristic value variables.
When changing an offset, negative offsets are displayed as -5 and no longer as 5-. Variable offsets are displayed directly in the right area of the value help.
Variables as the to-value of intervals no longer cause terminations.
In the value range editor, the value you entered manually was not transferred if you directly chose the transfer arrow.
In the value help for reference characteristics, the system did not display the variables for basic characteristics and therefore there were usually fewer variables than in the BEx Query Designer.
When you select the hierarchy, the system now correctly displays the date and version variables and no longer hierarchy variables as was incorrectly the case before.
When you call the value help from the variable entry screen, the system sometimes displayed all master data values (read mode "M") even though it should only display posted values (read mode "D"). This problem has been corrected.

BEx Analyzer with GUI 720 and MS Office 2010 does not work

I have recently installed SAP GUI 720 with BEx addon (7 and 3.x) on a computer with Office 2010 and Windows 7.
All BEx components work fine except Analyzer 7.
When starting Analyzer 7 nothing happens.
I have tried instead starting transaction RRMX from a BI system but this generates a short dump.
Does anyone have an idea about what could be the problem?
<<text removed>>
Best regards,
Didrik
Edited by: Matt on Sep 22, 2010 8:17 AM

Hello Didrik von Essen,
guess its issue with Excel Addins. i rectified the same issue by enabling the excel addins.go to Application wizard. and change the please find the screenshot . let me know if it works

Cannot open analyzer???

Hi all,
I use Windows XP profesional, and office 2002.
I have installed business explorer, but I cannot open a report via Analyzer. I also tried enter the BI system, run transaction RRMX and when it open the XL (it is in Greek) the open folder button does not operate, does not open any folder to choose a report to open, and also it is displayed within Greek windows in German Language.
Any clues???
Thanks in advance

Is your question regarding SAP Business One? Please post it in the proper forum if it is not.
Thanks
Gordon

GR/IR: Open receipts with vendor name

Hello SAP Gurus-
I am not sure if we are doing something wrong but we are currently reconciling our GR/IR account and what we noticed is that when we added the vendor name to the report with the help of an OSS note, we noticed that it gives us all transactions that make up the balance however it isn't what we wanted exactly.
What we were looking for was once we execute MR11 and handle all differences, we want to see only open receipts with the Vendor name. How can we achieve this? Is there a report? Should the GR/IR account be set up as a clearing account?
Any help/ insight is greatly appreciated!

figured it out

Cleared items still shows as open items in transaction FBL3N

Dear All,
We have an issue with respect to cleared items still shows as open items in transaction FBL3N.
Few documents has been posted and cleared, but still those line items still shows as open items. We had this problem only for few line items.
For other line items this clearing process is working properly without any issue.
Issue:
1. Documnet has been posted on 15.08.2209 and the same document has been cleared on 12.03.2010, but this document still shows as open item only....
Looking forward your response / suggestions to resolve this issue.
Thanks in advance
Regards,
Prasad

Hi Prasad,
You have the following ways to find out the reason:-
1. Check your selection criteria in FBL3N, if you are selecting open items as on 15.08.2009, then they will still show open items..
2. Check in table BSIS and BSAS and check where the documents are appearing.If they are cleared, they all should be appearing in BSAS.
This is standard SAP and most probably it has got to do with dates...
Regards,
SAPFICO

FPBW: Extract Open Items with a posting date in the future

Dear all,
I'm are currently searching for possibilities to extract Open Items with a posting date in the future from SAP IS-U 4.72 into SAP BW 3.5.
Currently I'm using the Business Content extractor 0FC_OP_01 together with the mass transaction FPBW in IS-U.
The problem I'm facing is within the mass transaction FPBW. I've have set the key date at 01.11.2007, but this job already runs for 52.000 seconds on the same database select-statement.
Does anybody know a possible solution to improve the performance of the statement below? (I pasted it from the process overview)
================================
SELECT
/*+
INDEX("DFKKOP" "DFKKOP~1" "DFKKOP^1" "DFKKOP____1" "DFKKOP____1__X" "DFKKOP_1")
"BETRH" , "BETRW" , "BUDAT" , "BUKRS" , "FAEDN" , "GPART" , "GSBER" , "INKPS" , "SPART" , "VKONT" ,
"WAERS" , "MAHNV" , "ABWBL" , "APPLK" , "AUGBD" , "AUGBL" , "AUGBT" , "AUGDT" , "AUGRD" , "AUGST" ,
"AUGWA" , "BLART" , "BLDAT" , "EMGPA" , "GRKEY" , "HVORG" , "MANSP" , "MWSKZ" , "OPBEL" , "OPSTA" ,
"OPUPK" , "PERSL" , "PYMET" , "QSSHB" , "SBETW" , "SPZAH" , "STUDT" , "TVORG" , "VTREF" , "XBLNR" ,
"XMANL" , "HKONT" , "OPUPZ" , "OPUPW" , "STAKZ" , "WHGRP" , "AUGBS" , "XANZA" , "XRAGL" , "ABWTP" ,
"ASTKZ"
FROM
"DFKKOP"
WHERE
"MANDT" = :A0 AND "AUGST" = :A1 AND "GPART" BETWEEN :A2 AND :A3 AND ( "AUGDT" = :A4 OR "AUGDT" > :A5
AND ( "BUDAT" <= :A6 OR "AUGBD" <= :A7 ) OR "WHGRP" <> :A8 AND "OPUPW" = :A9 )
ORDER BY
"AUGST" , "GPART"#
=================================
I have already tried to create an index on the following fields (in the same order):
- MANDT Client
- AUGST Clearing status
- GPART Business Partner Number
- AUGDT Clearing date
- BUDAT Posting Date in the Document
Any help would be appreciated!
Thanks in advance,
Steven Groot

Hi Marcos,
When you have created the Restricted keyfigures for Open Items, You have to add the date characteristic on which you are looking open item and add the variable there.Here you have to use a variable of type Interval and select the operator "<" the date of the Variable.If you go through, there are standard variable for keydate, which you can use directly.
Hope you got the idea
Regards
Happy Tony

While trying to change a BOM with transaction CS02, a runtime error appears

While trying to change a BOM with transaction CS02, a runtime error appears.
In intial screen he entered material ,plant BOM usage and date valid from after executed then id displayed item list in that he wantu2019s delete one item, he has been deleted selected item after that when he was saving he is getting runtime error
Developer trace
ABAP Program SAPLKED1_WRITE_CE4_BPS1                 .
Source LKED1_WRITE_CE4_BPS1U01                  Line 30.
Error Code SAPSQL_ARRAY_INSERT_DUPREC.
Module $Id: //bas/640_REL/src/krn/runt/absapsql.c#17 $ SAP.
Function HandleRsqlErrors Line 775.
RABAX: level LEV_RX_STDERR completed.
RABAX: level LEV_RX_RFC_ERROR entered.
RABAX: level LEV_RX_RFC_ERROR completed.
RABAX: level LEV_RX_RFC_CLOSE entered.
RABAX: level LEV_RX_RFC_CLOSE completed.
RABAX: level LEV_RX_IMC_ERROR entered.
RABAX: level LEV_RX_IMC_ERROR completed.
RABAX: level LEV_RX_DATASET_CLOSE entered.
RABAX: level LEV_RX_DATASET_CLOSE completed.
RABAX: level LEV_RX_RESET_SHMLOCKS entered.
RABAX: level LEV_RX_RESET_SHMLOCKS completed.
RABAX: level LEV_RX_ERROR_SAVE entered.
RABAX: level LEV_RX_ERROR_SAVE completed.
RABAX: level LEV_RX_ERROR_TPDA entered.
RABAX: level LEV_RX_ERROR_TPDA completed.
RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
RABAX: level LEV_RX_END entered.
RABAX: level LEV_RX_END completed.
RABAX: end RX_RFC
In sm21
Perform rollback
Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
     Short dump "090618 110101 donalda 11557 " generated
Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
       Occurred on     18.06.2009 at   11:01:01
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLKED1_WRITE_CE4_BPS1" had to be terminated because
one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"RKE_WRITE_CE4__BPS1" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
The exception must either be prevented, caught within the procedure
"RKE_WRITE_CE4__BPS1"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
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,
use the following search criteria:
"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLKED1_WRITE_CE4_BPS1" or "LKED1_WRITE_CE4_BPS1U01"
"RKE_WRITE_CE4__BPS1"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.

Hi ,
you are getting beacuse u are trying to do mass update to database.
Please check that below note are applicable to your system.
Note 453313 - DBIF_RSQL_ERROR_INTERNAL for mass insert
Note 869534 - AFS MRP doesn't work properly with all BOM item categories
Thanks Rishi Abrol

Error in transaction RRMX

When I run transaction RRMX in SAP Netweaver ABAP Trail Version. I get an error saying "Please Install Excel as Viewer". Can you suggest what can I do?
Actually I wanted to create some BEx queries

Hi,
Checkout this posting
with suggested resolution.
Please Install Excel as Viewer
Thanks, AbyJacob

How to make a single payment for different open items with same due date

Hi,
I have created a payment method and selected "Payment per due day " option in payment method company code settings.
Even I have selected that option, Payment will not happen grouping for the items with same due date
for ex : I have two open items with one due date and another open item with another due date so when I am trying performing F110 system should make a single payment for the item with same due date and seperate payment for another item.
But system making single payment for all items
Could you please suggest anything how to make a seperate payment with due date.
Regards
VK GUPTA

Hi,
Please check Vendor Master data: FK02 ->company code data -> Payment transaction accounting: unflag 'individual payment'.
Make a test and let me know if it's okay.
regards

Why open items with dunning level 0 sometimes appear?

Hi All,
when I run the dun transaction (F150) sometimes in table MHND and MHNK open items with dunning level 0 appear. These are open items overdue, but not enough to level 1. Note that this problem appear only sometimes.
Do you know how to avoid this?
Many thanks

Check if deselcting the indicator for Always Dun? in dunning level configuration in FBMP ,solves your issue.
Thanks and regards
Kedar

Charge off difference whening clearing customer open item with bank receipt

Hi,
Our company users will use F-32 to clear customer open item with bank receipt, sometimes, our invoice is 100 RMB issue to customer, the customer finally pay 99.98, then in F-32, we use charge off difference to post 0.02 difference to a account.
The user then want to control this, saying for example, if the customer pay only 90, whening using charge off differnce, the system will pop up a error message.
Can this be done in SAP, or we need to use user exit, then which user exit?
Thanks.

Dear,
This is done through customer tolerance group using transaction OBA3. Here enter the maximum amount in Loss under the Permitted Payment Differences. you are able to hold tolerance for customer clearing.
Is this what you wanted?
Regards,
Chintan Joshi.

Open MM03 with a material number from CRM UI

I can launch MM03 from CRM UI. Please guide me how to open MM03 with a particular material (skiping first screen if possible) from the CRM_UI screen.

Hey,
Maybe this blogpost can help you.
[http://sapcrmweblog.blogspot.com/2011/01/extending-business-object-repository.html|http://sapcrmweblog.blogspot.com/2011/01/extending-business-object-repository.html]
Check the example method ZEXECUTE_WITH_PARAM. This allows you to move a parameter from the CRM system to the PID of a field in the transaction you called.
Furthermore, you will need to move the material number you want to use to the GDC (or if you can use GDC object CURRENTPRODUCT-PRODUCTID, I don't know where it is occupied, that would also be fine), and use that in the transaction launcher definition.
If the CURRENTPRODUCT is not bound when you call the transaction, I think the best way to go would be to add a paramater in IMG --> Customer Relationship Management --> UI Framework --> Technical Role Definition --> Define Global Data Context Parameters called ZPRODUCT type Product.
This GDC object can be occupied by implementing the following code somewhere in the code when you have the material you want to pass available in the BOL.
DATA: __gdc TYPE REF TO if_crm_ui_data_context.
__gdc ?= cl_crm_ui_data_context_srv=>get_instance( me ).
__gdc->set_entity( name = 'ZPRODUCT' value = <your bol-product> ).
Hope this helps.
Regards,
Pieter Rijlaarsdam

Opening analyzer with transaction RRMX

Similar Messages

Maybe you are looking for