Alter the main tables of materialized views

Hi
I want to add a new column to the main table of a materialized view.Can anyone let me know,what are the steps I need to take care on materialized views,In addition to recompiling dependent objects?

PER_SPECIAL_INFO_TYPES: This table holds the definitions of SITs that are available to each Business Group. Each special information type is a user defined structure for the personal analysis key flexfield. The name of the special information type is the same as the name of the corresponding key flexfield structure.
PER_SPECIAL_INFO_TYPES_V : This table has the Employee's SIT info. A supplementary view used to simplify forms coding
PER_SPECIAL_INFO_TYPES_V2 : A supplementary view used to simplify forms coding.

Similar Messages

How do I figure where is the data in a materialized view coming from

Hi: when I run select NAME, OWNER from dba_mview_refresh_times, I see a number of materialized views. How do I find more details about this view i.e where is the data coming from and which fields. The source table that is in another database changed. But the view on my database where the materialized view exist has not changed. I want to confirm from where is data coming in this view
TIA
Ravi

SQL> select * from dict where table_name like 'ALL%MVIEW%'
TABLE_NAME                     COMMENTS
ALL_BASE_TABLE_MVIEWS          All materialized views with log(s) in the database that the user can s
                               ee
ALL_MVIEWS                     All materialized views in the database
ALL_MVIEW_AGGREGATES           Description of the materialized view aggregates accessible to the user
ALL_MVIEW_ANALYSIS             Description of the materialized views accessible to the user
ALL_MVIEW_COMMENTS             Comments on materialized views accessible to the user
ALL_MVIEW_DETAIL_PARTITION     Freshness information of all PCT materialized views in the database
ALL_MVIEW_DETAIL_RELATIONS     Description of the materialized view detail tables accessible to the u
                               ser
ALL_MVIEW_DETAIL_SUBPARTITION Freshness information of all PCT materialized views in the database
ALL_MVIEW_JOINS                Description of a join between two columns in the
                               WHERE clause of a materialized view accessible to the user
ALL_MVIEW_KEYS                 Description of the columns that appear in the GROUP BY
                               list of a materialized view accessible to the user
ALL_MVIEW_LOGS                 All materialized view logs in the database that the user can see
ALL_MVIEW_REFRESH_TIMES        Materialized views and their last refresh times for each master table
                                that the user can look at
ALL_REGISTERED_MVIEWS          Remote materialized views of local tables that the user can see
13 rows selected.

Table and Materialized View in different namespaces?

I've just faced something completly new for me. It appears that there are two objects with the same name and owner. Table and Materialized View have the same names and when I look into system dictionary I can se sth. like that:
OWNER OBJECT_NAME OBJECT_ID DATA_OBJECT_ID OBJECT_TYPE NAMESPACE
USER_A USER_TABLE 159381 159381 TABLE 1
USER_A USER_TABLE 159382 MATERIALIZED VIEW 19
(I couldn't find how to write above with const length font).
Two object in different namespace? I thought that Tables and Materialized Vievs have the same namespace.
Can you please tell me how can I create objects to achieve above result? I would also be grateful if you tell me where to find that topic in documentation.

Perfectly normal.
SQL> select object_name, object_type from user_objects where object_name = 'TEST_MV';
no rows selected
SQL>
SQL> create materialized view test_mv
2 as
3 select sysdate from dual;
Materialized view created.
SQL>
SQL> select object_name, object_type from user_objects where object_name = 'TEST_MV';
OBJECT_NAME                                        OBJECT_TYPE
TEST_MV                                            TABLE
TEST_MV                                            MATERIALIZED VIEW
SQL>
SQL> drop materialized view test_mv;
Materialized view dropped.
SQL>
SQL> select object_name, object_type from user_objects where object_name = 'TEST_MV';
no rows selected
SQL>

Display many fields of a lookup table in the main table

Hello Experts,
In MDM, I have a "Suppliers" table which is a lookup table. This table has 4 fields :
- Supplier Name (Display Field)
- Supplier Code
- Email
- Phone number
In the main table, a field "Supplier" uses the "Suppliers" lookup table. This fields displays the "Supplier Name" of the "Suppliers" lookup table.
Now I also want to display the "Email" and the "Phone Number" of the supplier. If I set these fields as Display Fields in the "Suppliers" lookup table, they appear concatenated in the main table, which I don't want.
The only way I found to display those fields is to set 2 new fields in the main table as calculated fields, eg: IF(TRUE, Supplier.Email).
Is there any way to display those fields w/o using calculated fields?
Thanks for your help

Hi Christian,
Thanks for your help. Actually I am working on the SRM part of MDM, so I do not use portal to display data but the SRM-MDM UI on which I can not manage iViews.
The need is to have, for each Material displayed, the name and the contact data of the Supplier. If I concatenate those data the display is not very clear for the user. Eg:
Supplier data: TOTO, contact_at_toto.com, 1234567890
I would rather have :
Supplier: TOTO
EMail: contact_at_toto.com
Phone Number: 1234567890
As you said, the non automatic update of calculated fields is an issue in my case. So I am currently looking at assignments, which seems to be schedulable via a workflow but I don't know if it's a good mean?
Best regards,
Patrick

How to populate the main table and the lookup's at the same time

Hi ,
What I have with me is the XML files which contain the data from the material master and the excel sheet which talks about the mapping . it basically tells me which field of the main table maps to which field of which segment in the IDOC and also the name of the table and the field in the R3 system .
I wish to use this info to populate the data in the material repository .
- How can I populate the data in the lookup table at the same time when I am populating the main table ? I have only the XML's that correspond to the main table . I don't have seperate data for the lookup tables .
- Can I use the standard maps available for import in the business content of material repository in MDM ?
- If the answer to the second question is NO then I think i can create the maps and save them for future use .
Regards
Deepak Singh

Hi, Deepak
>>> - How can I populate the data in the lookup table at the same time when I am populating the main table ? I have only the XML's that correspond to the main table . I don't have seperate data for the lookup tables .
I don't think you can populate both main table and all fields of lookup tables at the same time, i.e. using same map. You can consider 2 options to upload all information you have:
1) If your XML file contains data you would like to upload to lookup tables, you can upload it to MDM lookup tables with several maps using same XML and choosing different sections of that XML corresponding to different MDM lookup tables.
2) Also you can upload main table simultaneously with lookup table entries (using same map), but in this case new lookup table entries will only contain display field values that you mapped. To do this you should use 'Add' value mapping functionality for fields that you mapped to lookup tables.
>>>- Can I use the standard maps available for import in the business content of material repository in MDM ?
1) In case you have material master repository delivered by SAP and you use XML files which structure corresponds to SAP predelivered XSD schemas then you can use these maps undoubtedly.
2) If your repository is based on SAP predelivered, but you changed it ,you should adjust these maps due to differences in repository structure and XML files structure.
3) If you created your repository from scratch you should consider option of making your own import maps.
Regards,
Vadim Kalabin

Can't find the topics from the main table of contents

I need urgent help. I am still running RH 8 for Word (2007). I published the entire project. When testing the main table of contents, the books and topics appear as expected, but when I try to go to any of the topics I get the message:
The topic does not exist. Contact your application vendor....
From the individual projects I can see the topics. When I publish them and view the contents all seem to work fine, but it does not when viewing the entire project from the main table of contents.
The main project looks as follows:

Tried that and still have the problem. The RH help lists the following workaround for the error
message :
To workaround this WinHelp viewer limitation, you can either manually insert the Help filename statement on every page of the external CNT file or allow RoboHelp to automatically do it for you:
1 Open the Help file containing the included external CNT file.
2 From RoboHelp Explorer’s File menu, select Project Settings.
3 Select the Contents tab.
4 Select the Include Help filename with pages option. When you save the TOC file, this option automatically places the "@helpfilename.hlp" inside the CNT file on every page.
5 Click OK.
6 Save the external CNT file.
7 Recompile the Help project
I went to the main index project which contains the external cnt file and tried to select the contents tab (no such tab in the project settings). Then I went to the actual project, and again, selected Project Settings there is no Contents Tab. Is there any other way to get that contents tab?
This is how my screen looks like:
eangel

Truncate table and materialized view log

I user oracle 10 R2
I have a table and on that table a materialized view log.
I execute in a pl/sql procedure:
1) execute immediate('drop materialized view log on tab1');
then:
2) execute immediate('truncate table tab1');
3) Now I insert a lot of records in tab1
4) execute immediate('create materialized view log on tab1 WITH rowid INCLUDING NEW VALUES');
When I create the materialized view log I recieved this message:
ora32321: refresh fast on tab2 unsupported after detail table truncate
Why?

Refresh fast after truncate operation on container table is not supported, regardless the container table is or is not partitioned.
Perform a refresh complete.
ORA-32321 :
Cause:     A detail table has been truncated and no materialized view
     supports fast refersh after a detail table has been truncated
Action:     Use REFRESH COMPLETE. Note: you can determine why your
     materialized view does not support fast refresh after TRUNCATE
     using the DBMS_MVIEW.EXPLAIN_MV() API.

Oracle equals_path condition NOT working with table and materialized view

The user i am using is xdb with dba role.
1.When i try to use the statement
SELECT PATH FROM xdb.path_VIEW
WHERE
EQUALS_PATH(res, '/home/OE/PurchaseOrders/2002')=1
the result is
/home/OE/PurchaseOrders/2002
2. When i drop the path_view and recreated it like materialized view with statement
create MATERIALIZED view path_view as
select /*+ ORDERED */ t2.path path, t.res res,
xmltype.createxml(xdb.xdb_link_type(NULL, r2.xmldata.dispname, t.name,
h.name, h.flags, h.parent_oid, h.child_oid),
'http://xmlns.oracle.com/xdb/XDBStandard.xsd', 'LINK') link,
t.resid
from ( select xdb.all_path(9999) paths, value(p) res, p.sys_nc_oid$ resid,
p.xmldata.dispname name
from xdb.xdb$resource p
where xdb.under_path(value(p), '/', 9999)=1 ) t,
TABLE( cast (t.paths as xdb.path_array) ) t2,
xdb.xdb$h_link h, xdb.xdb$resource r2
where t2.parent_oid = h.parent_oid and t2.childname = h.name and
t2.parent_oid = r2.sys_nc_oid$
then the equals_path condition STOP working !!!
3. The same experiment, but i recreate it like table
create table path_view as .... using the rest of the statement ...
Can someone help me to understand why equals_path is NOT working on table and materialized view !

Thanks Jonah. I was under the impression that I already had it but seems like it has to be a direct priv - thru a role doesn't work.
I granted the reqd privs and then it worked fine. Thx for your help!

What are the main tables of SITs?

Hi
What are the main tables of SITs? How can I find out the tables related to SITs?
Regards
Rahman

PER_SPECIAL_INFO_TYPES: This table holds the definitions of SITs that are available to each Business Group. Each special information type is a user defined structure for the personal analysis key flexfield. The name of the special information type is the same as the name of the corresponding key flexfield structure.
PER_SPECIAL_INFO_TYPES_V : This table has the Employee's SIT info. A supplementary view used to simplify forms coding
PER_SPECIAL_INFO_TYPES_V2 : A supplementary view used to simplify forms coding.

Dropping base table of materialized view

HI please let me know what happens if i drop the base table of a materialized view? does the MV remain valid with data?

Hi,
Well, it's easy to test yourself.
SQL> select count(*) from t1;
COUNT(*)
       100
SQL> desc t1
Name                                      Null?    Type
ID                                                 NUMBER(10)
SQL> create materialized view t1_mv as select * from t1;
Materialized view created.
SQL> select count(*) from t1_mv;
COUNT(*)
       100
SQL> drop table t1 purge;
Table dropped.
SQL> select count(*) from t1_mv;
COUNT(*)
       100
SQL> desc t1_mv
Name                                      Null?    Type
ID                                                 NUMBER(10)
SQL> select object_type, status from user_objects where object_name = 'T1_MV';
OBJECT_TYPE         STATUS
TABLE               VALID
MATERIALIZED VIEW   INVALID
SQL> select * from t1_mv where rownum < 5;
        ID
         1
         2
         3
         4
SQL>I think the answer is very clear.
Asif Momen
http://momendba.blogspot.com

Can anybody tell me about SD Functionality and the main tables used in SD

Hi,
Can anybody tell me about SD Functionality and the main tables used in SD.
Thanks,
bsv.

Hi
SD FLOW
SD Flow Cycle:
INQUIRY ( VA11)
|
QUOTATION (VA21)
|
PURCHASE ORDER (ME21)
|
ORDER CONFIRMATION (VA01)
|
PICKING LIST (VL36)
|
PACKING LIST - (VL02, VL01)
|
SHIPPING (VT01)
|
INVOICE (VF21, VF01)
|
AR
Enquiry - Customer enquires about the Products services that were sold by a company - VA11
Quotation - Company Gives a Quotation for the products and Services to a Customer
Sales Order - Customer gives a Purchase order to the company agaionst which a Sales order will be raised to Customer in SAP.
VBAK: Sales Document(Header Data) (VBELN)
VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)
      Enquiry, Quotation, Sales Order are differentiated based on Doc.
      Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,
      for Quotation 'B' & for Order it is 'C'.)
Delivery(Picking, Packing, Post Goods Issue and Shipment)->
Company sends the material after picking it from Godown and Packing it in a Handling Unit(box) and Issues the goods
LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)
LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)
      (LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)
Billing - Also company bills to the customer for those deliveries
And in FI against this billing Accounting doc is created.
VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)
VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)
      (VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)
      Apart from these tables there are lot of other tables which starts with
      V, but we use the following tables frequently.
other tables and imp fields
VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)
      VBTYP= C(Sales Order) VBTYP=J(Delivery) VBTYP=M(Invoice)
VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)
VBEP: Sales Doc. Schedule Lines Data(VBELN,POSNR,EDATU,WMENG)
VBKD: To get sales related Business data like Payment terms etc.(VBELN,ZTERM)
VBFA: sales document flow data(VBELV,VBELN,POSNV,VBTYP)
VBPA: Partner functions Data(VBELN,PARVW,KUNNR,LIFNR)
VEDA: Contract Data(VBELN,VPOSN)
VEDAPO: Contract Data(VBELN,VPOSN)
KONA: Rebate Agreements (KNUMA,VKORG,VTWEG,SPART)
VBRL: SD Document: Invoice List(VBELN,POSNR,VBELN_VF,NETWR,KUNAG)
VKDFS: SD Index: Billing Indicator(FKTYP,VBELN,FKART,VKORG)
VBSK: Collective Processing for a Sales Document Header(SAMMG,SMART)
VBSS: Collective Processing: Sales Documents(SAMMG,VBELN,SORTF)
VRKPA: Sales Index: Bills by Partner Functions(VBELN,BELNR,KUNDE,PARVW)
VRPMA: SD Index: Billing Items per Material(MATNR,VBELN,BELNR,KUNNR)
TVLKT: Delivery Type: Texts(LFART,VTEXT)
KNA1: Customer Master-General(KUNNR,NAME1,LAND1)
KNB1: Customer Master(Company Code)(KUNNR,BUKRS,PERNR)
KNC1: Customer Master Data (Transaction Figures)(KUNNR,BUKRS,GJAHR)
KNVK: Customer Master Contact Partner(PARNR,KUNNR,NAME1)
KNVV: Customer Master sales data(KUNNR,VKORG,VTWEG,KDGRP)
KNBK: Customer Bank Details(KUNNR,BANKS,BANKL,BANKN)
KNVH: Customer Hierarchy (HITYP,KUNNR,VKORG,VTWEG,SPART)
KNVP: Customer Master Partner Functions(KUNNR,PARVW,KUNN2)
KNVS: Customer Shipment data(KUNNR,VSTEL,TRANS)
KNVI: Customer Tax data(KUNNR,ALAND,TATYP)
LFA1: Vendor Master-General (LIFNR,NAME1,ORT01)
LFB1: Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)
LFC1: Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)
MARA: Material Master-General (MATNR,MTART,MATKL)
MARC: Material Master-Plant data(MATNR,WERKS,EKGRP)
MARD: Material Master- St.Location Data(MATNR,WERKS,LGORT,LABST)
EBEW: Sales Order Stock Valuation(MATNR,VBELN,BWKEY,BWTAR)
TVKO: Sales Organizations(VKORG)
TVTW: Distribution Channel(VTWEG)
TSPA: Divisions(SPART)
TVKOV: Distribution Channels for S.Orgn(VKORG,VTWEG)
TVKOS: Divisions for S.Orgn(VKORG,SPART)
TVTA: Sales Areas(VKORG,VTWEG,SPART)
TVBUR: Sales Offices(VKBUR,ADRNR)
TVKBT: Sales Office Texts(VKBUR,SPRAS,BEZEI)
TVKBZ: Sales Office Assign.to Sales Area(VKORG,VTWEG,VKBUR)
TVKGR: Sales Group(VKGRP)
TVGRT: Sales Group Texts(VKGRP,SPRAS,BEZEI)
TVBVK: Sales Group to Sales office(VKBUR,VKGRP)
TVKWZ: Plants Assign.to S.Orgn(WERKS,VKORG)
T171T: Sales District Texts(BZIRK,BZTXT,SPRAS)
TVLA: Loading Points(LSTEL)
TVST: Shipping Points (VSTEL)
TVSWZ: Shipping Point to Plant(VSTEL,WERKS)
TVPT: Item Categories (PSTYV)
TINC: Customer Incoterms(INCO1)
T077D: Customer Account Group (KTOKD)
T001W: Plants (WERKS)
T001L: Storage Locations (LGORT)
T499S: Locations(WERKS,STAND,KTEXT)
TWLAD: To get address of Storage Location and Plant(LGORT,ADRNR)
TVAK: Sales Document (Order) Types (AUART)
TVAU: Sales Documents: Order Reasons (AUGRU)
TVFK: Billing Document Types (FKART)
TVLK: Delivery Types(LFART)
TVSB: Shipping Conditions (VSBED)
TTDS: Transportation Points(TPLST)
TVKT: Account Assignment Groups (KTGRD)
KONV: Condition Types pricing)(KNUMV,KSCHL,KWETR)
ADRC: To get Addresses of Partners(ADDRNUMBER,NAME1)
VBBE: Sales Requirements: Individual records(VBELN,POSNR,MATNR)
VBBS: Sales Requirement totals Record(MATNR,WERKS,LGORT,CHARG)
VBKA: Sales Activities Data(VBELN,KTAAR)
VBPV: Sales Document Product Proposal(VTWEG,MATNR,KUNNR,CHARG)
T682: Access Sequences (KOZGF)
T682T: Access Sequence Texts (KOZGF,VTXTM)
T683: Pricing Procedures (KALSM)
T683T: Pricing Procedures Texts(KALSM,KAPPL,SPRAS,VTEXT)
T685: Pricing Condition Types (KSCHL)
T685T: Condition Type Texts(KSCHL,SPRAS,KAPPL,VTEXT)
KONH: Conditions (Header)(KNUMH,KAPPL,KSCHL)
KONP: Conditions (Item)(KNUMH,KOPOS,KAPPL,KSCHL)
KONV: Conditions (Transaction Data)(KNUMV,KSCHL,KBERT,KWERT)
KOND: Conditions (KNUMD,ZUSKO,KSCHL)
for sd go through the links
http://www.sapgenie.com/abap/tables_sd.htm
Please check this SD online documents.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CAARCSD/CAARCSD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_SD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSD/BCBMTWFMSD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOLISPLN/LOLISPLN.pdf
Also please check this SD links as well.
http://help.sap.com/saphelp_47x200/helpdata/en/92/df293581dc1f79e10000009b38f889/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/dd/55f33e545a11d1a7020000e829fd11/frameset.htm
http://www.sap-basis-abap.com/sapsd.htm
http://www.sap-img.com/sap-sd.htm
http://www.sapgenie.com/abap/tables_sd.htm
http://searchsap.techtarget.com/featuredTopic/0,290042,sid21_gci961718,00.html
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/SD_tutorial.html
All help ebooks are in PDF format here
http://www.easymarketplace.de/online-pdfs.php
Reward points if useful
Regards
Anji

What are the main tables using in vendor performance report.

what are the main tables using in vendor performance report.
how many select statements are in ABAP reports.

Refer the links -
vendor performance report !!!
vendor performance report
vendor performance report
I need standard vendor performance report
Regards,
Amit
Reward all helpful replies.

Can we create materialized view on the top of another materialized view.

Hi ,
can we create materialized view on the top of another materialized view.
Thanks
Naveen

Welcome , Just remember is not good apporch to do that since performance when MV refresh
Please mark this thread as answered .

How can I change the name of a Materialized View?

How can I change the name of a Materialized View?

Oracle permitted renaming the snapshot in the earlier versions of 8i. However, it does not permit renaming the materialized view in 9i or 10g.
SQL> rename mymatview to mymatview2;
rename mymatview to mymatview2
ERROR at line 1:
ORA-32318: cannot rename a materialized view
SQL> disconnect
Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP and Data Mining options
SQL> rename mymatview to mymatview2;
rename mymatview to mymatview2
ERROR at line 1:
ORA-32318: cannot rename a materialized view
SQL> disconnect
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.3.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.3.0 - Production

Error while inserting value Qualified field in the main table

Hello,
I am trying to populate Qualified field in the main table when a new record is inserted in the Products Repository.
The field is Reference Price and its a qualified lookup field. I am using the below code to create qualified lookup value and create qualified link values.
QualifiedLookupValue qlvRefPrice = new QualifiedLookupValue();
TableId qltabid = repSchema.getTableId("ReferencePrices");
FieldId qlfieldid = repSchema.getFieldId("ReferencePrices","RP_ReferncePrices");
RecordId rdRefPrice = getRecordId(connPool,session,"RP",qlfieldid,qltabid);
HashMap map = new HashMap();
map.put(repSchema.getFieldId("ReferencePrices","StartDate_ReferencePrice"),new DateTimeValue(cal));
map.put(repSchema.getFieldId("ReferencePrices","EndDate_ReferencePrice"),new DateTimeValue(cal));
map.put(repSchema.getFieldId("ReferencePrices","ListPrice"),new FloatValue(Float.parseFloat("123.3")));
map.put(repSchema.getFieldId("ReferencePrices","Currency"),new LookupValue(getLookupRecordId(connPool,session,"Currencies","Currency_Currencies","EUR")));
QualifiedLinkValue qlvLinkValue = MdmValueFactory.createQualifiedLinkValue(rdRefPrice,map);
qlvRefPrice.addValue(qlvLinkValue);
emptyRecord.setFieldValue(fieldIdRefPriceHistory,qlvRefPrice);
However when the createrecord command is executed I get the following error.
java.lang.RuntimeException: No matching validation Id 97. at com.sap.mdm.internal.validation.ValidationInfoHelper.retrieveValidations(ValidationInfoHelper.java:71) at com.sap.mdm.data.commands.CreateRecordCommand.execute(CreateRecordCommand.java:246) at com.alcatel_lucent.productdetail.ProductItemDetail_Comp.createProduct(ProductItemDetail_Comp.java:2927) at com.alcatel_lucent.productdetail.wdp.InternalProductItemDetail_Comp.createProduct(InternalProductItemDetail_Comp.java:656) at com.alcatel_lucent.productdetail.ProductItemAddView.onActionSave(ProductItemAddView.java:971) at com.alcatel_lucent.productdetail.wdp.InternalProductItemAddView.wdInvokeEventHandler(InternalProductItemAddView.java:662) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869) at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1356) at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327) at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:332) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
I spoke to my MDM team and they say there is no validation which they have put for Reference Price field. I have tried inserting values in another field of type qualified lookup in the same main table and that works without any issue.
The code is as below:
QualifiedLookupValue qlvRating = new QualifiedLookupValue();
TableId qlvtable = repSchema.getTableId("ProductRatings");
FieldId qlvratinglink = repSchema.getFieldId("ProductRatings","RatingLink");
RecordId rdidPR = getRecordId(connPool,session,"CI",qlvratinglink,qlvtable);
wdComponentAPI.getMessageManager().reportSuccess("rdidPR "+rdidPR);
HashMap mapPR = new HashMap();
mapPR.put(repSchema.getFieldId("ProductRatings","AvailRating"),new LookupValue(getLookupRecordId(connPool,session,"AvailabilityRatings","AvailabilityRating_AvailabilityRatings","CI")));
mapPR.put(repSchema.getFieldId("ProductRatings","EffectiveDate"),new DateTimeValue(cal));
mapPR.put(repSchema.getFieldId("ProductRatings","FERAIndic"),new LookupValue(getLookupRecordId(connPool,session,"ReplacementIndicators","Code","FE")));
mapPR.put(repSchema.getFieldId("ProductRatings","FERAOrdItem"),new LookupValue(getLookupRecordId(connPool,session,"ReplProducts","ProdID","100008200")));
QualifiedLinkValue qlvLink = MdmValueFactory.createQualifiedLinkValue(rdidPR,mapPR);
qlvRating.addValue(qlvLink);
emptyRecord.setFieldValue(fieldIdRatingHistory,qlvRating);
I would really appreciate if someone can help in solving the issue.
Thanks in advance,
Aamod

Hi Aamod,
Sees that some validation/assignments are getting triggered as soon as you make changes to the record in MDM. Please check once after removing validations/workflow that you may have. This way you may debug the issue.
Hope this helps!!
Cheers,
Arafat

Alter the main tables of materialized views

Similar Messages

Maybe you are looking for