July 30, 2009 at 10:20 am
Symptom
You are trying to upload a new PDF/Image file to the MDM PDF/Image Table using the MDM Portal iViews but receiving a “com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter” error.
Other terms
MDM, Portal, iView, PDF, Image
Reason and Prerequisites
When uploading a PDF/Image file to the PDF/Image Table using the MDM Portal iViews, the PDF/Image is uploaded without a thumbnail while the MDM Server is expecting to get it with a thumbnail.
Solution
Make sure that the repository in question has “Allow invalid PDFs” property set to “Yes”.
To do that please perform the following steps:
1. Log on to the MDM Console.
2. Connect to the repository which the MDM iViews are connected to.
3. Right-Click on the repository and select “Properties”.
4. Make sure that the property “Allow invalid PDFs” is set to “Yes”, and for [...]
July 20, 2009 at 6:43 pm
Symptom
Formatting of MDM Real, Measurement or Currency field types with 1 or more digits after the decimal point appear to be different when comparing these fields in Item Details Edit mode to Item Details View mode.
Other terms
MDM, Portal, iViews, Item Details, MDM 5.5, Real, Measurement, Currency
Reason and Prerequisites
You have created a MDM Standard Item Details iView and that includes either a Real, Measurement or Currency field. Field formatting in view mode is done according to the MDM Console settings (e.g. Decimal places, Dimension etc.) using the MDM Java API, while for edit mode, formatting is handled by generic portal formatting infrastructure.
Solution
Since the underlining MDM repository data is not affected by the formatting discrepancies, there is no risk of unintentional data modification. [...]
July 20, 2009 at 6:42 pm
Symptom
Date and numbers format do not match the user regional setting
Other terms
Date, Currency, Real, MDM, Portal, iView
Reason and Prerequisites
MDM Standard Portal iViews formatting of dates and numbers are determined at runtime according to the portal users language property. (If this property is empty, the setting will be set according to the Browser Language Preferences settings).
Note that adjustments to this property also impact the MDM data and MDM metadata language.
Solution
To modify this property in the portal, go to Personalize -> User Profile. In the General Information tab, select the Language property value according to which all formatting will be applied (e.g. If you set the language property to ‘English[US]‘ then the date format will be displayed as 5/27/2008, while if set to ‘German[DE]‘ [...]
July 15, 2009 at 2:11 am
Symptom
When trying to edit a record via MDM Portal Item Details iView you see a message that “Record is protected, record is checked out” and you can not edit it. Trying to edit the same record with the Data Manager is possible without the protected-error.
Other terms
Protected, check out, MDM, Portal, iView
Reason and Prerequisites
When you first select the record in the Portal (before you check it
out), the selected recordID is of the Original record.
Once you log to the Data Manager and check-out the same record, a new checked-out record is created (you can see this by selecting “All versions” in the Data Manager). Now, when you return to the Portal and try to work on the Original record, you get a message saying “record is [...]
July 15, 2009 at 2:05 am
Symptom
When working in MDM iViews, MDM table and field privileges enforced policy is stricter then the one in Data Manager
Other terms
Roles, Permissions, Privileges, iViews
Reason and Prerequisites
In MDM iViews, an MDM role’s field and table privileges (Read, Write) are determined as follows: If in the MDM Console, under Admin -> Role -> Tables and Fields tab, the Read-Only property is enabled for the MDM table (e.g. Products) Access column, then ALL fields located under the table node are assumed to be Read-Only, regardless if any of these fields has a Read/Write setting.
In the Data Manager, a field privileges are determined only based on the field access property, regardless of the table access property setting.
This result in the iView enforcing a stricter policy compared to [...]
July 15, 2009 at 2:00 am
Symptom
There are 3 possible symptoms to this issue:
1. MDM Portal iViews image fields are not displaying image. Instead of the linked image, a red “X” is displayed. In addition, Portal DefaultTrace file will contain the following entry:
Access denied (Object:com.sap.portal.system/security/com.sap.pct.mdm.appl.masteriviews/low_safety).
2. When trying to open any Pop-up window in the MDM Item Details iView you get a “Portal Running environment error”. In the Portal DefaultTrace file you see the following entry:
com.sapportals.portal.prt.runtime.PortalRuntimeException: Access is
denied: com.sap.pct.mdm.appl.masteriviews.QualifierRowPopupViewer -
user:
com.sapportals.portal.prt.deployment.DeploymentManager.checkPermissions
Caused by: com.sapportals.portal.pcd.gl.PermissionControlException:
Access denied (Object(s): com.sap.portal.system/security/com.sap.pct.mdm.appl.masteriviews/low_safety).
3. When attempting to open a Pop-up, the Popup window opens up with a generic exception error message: “Portal runtime error. An exception occurred while processing your request……Refer to the log file for details about this exception”. The Default Trace log has no additional information”.
Other terms
MDM, [...]
July 15, 2009 at 2:00 am
Symptom
When using MDM 7.1 SP00/SP01, after making changes to the tuple field for a specific
record, The permanent ids within the change history table are populated
inconsistently. This results in the tuple changes not being found when searching utilizing the
main table record permanent id. This also occurs when working with the MDM Change tracker in the Portal in conjunction with a
Result Set iView, i.e. The change tracking log entries for the selected record will not display the tuples that changed
Other terms
Change tracker, MDM, Portal, iView, Web UI
Reason and Prerequisites
The issue occurred due to a limitation of how tuple changes were
recorded in the change tracking table (it did not save the change with
the Main table record permanent ID).
Solution
Changes to tuple values and tuple member fields may only be found by [...]