SDIMA: Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ

Hi Experts,
when checking condition records consistency between CRM and ERP via transacation SDIMA we get the following error for one of the conditon records: 'Values for field SUPP_EXIST in condition table CNCCRMPRCUS801 differ'. Can anybody explain to me where this message could come from? To my understanding field 'SUPP_EXIST' only exists in CRM condition tables for technical reason. So no way to compare this against an ERP condition table field, is there?
And related to this: I found that this error message is triggered from method CL_CND_DIMA_CRM->COMPARE_MBDOC. As the DIMA-Compare is triggered asynchronously and just setting a break-point is no option therefore, I was wondering if anybody knows a way of debugging this method in order to find out what the coding does in detail before the message is thrown.
Thanks a lot for your help!
Cheers,
Jens

Hi Brian and the other Experts,
thanks for your help. Unfortunately, I don't have a single record with this problem but a lot more. So it is not possible to correct this manually. Also, I would not know how to correct this anyhow as I don't understand what field in R/3 should map to field SUPP_EXIST in CRM condition tables. Let me explain:
From my understanding, in CRM (leave aside scales) we have two database tables for each condition table, a central and a supplemental table. A condition record always creates a data record in the central table and nothing is inserted in the supplemental table in case that the fields form the supplemental table are not needed. However, when there are less common condition features involved (e.g. uppler limits), then an additional data record will be created in the supplemental table with the relevant data. And this is when field SUPP_EXIST comes into play as it is an indicator for the system that a data record exists for that condition record also in the supplemental table.
The condition record data model in R/3 is completely different. For CRM condition table CNCCRMPRCUS801 the following tables in R/3 are involved: A801, KONH and KONP. And there is a data record for each of them for a given condition record. There is no concept of having a supplemental table as far as I understand it so where exactly would I find this SUPP_EXIST in R/3 so that I can make sure it does not deviate from the data in CRM?
Would be great if someone could give me another hint. What am I getting wrong?
Cheers,
Jens

Similar Messages

  • FLEET Table, Possible Values For Field IS SI UNIT

    Dear experts,
    While doing analysis on fleet data I realized that for field IS_SI_UNIT (PM: Vehicle Data in SI Unit (e.g. Dimensions)) in table FLEET in two separate systems we have vehicle records set with different entries for this field.
    In one system vehicles are stored with value F: DB Unit set individually (new) 
    and in other one with value Y: DB Unit set through (new)
    Systems are SAP ECC 6.0
    Does anyone know what does it mean and what influence this has? In both systems vehicles are created by end users using standard PM creation transaction and those indicators are set in background while equipment is saved so there is not influence by end user.
    I could not find much information on SAP support portal about meaning behind possible values for field IS_SI_UNIT in table FLEET so was wondering if anyone knows more here?
    Thanks,
    Ivo

    Dear,
    There will not be any impact.Finally system will consider only SI units for fleet equipment consumption calculation.
    Kindly read note:366733 - Equipment/fleet: SI units in table FLEET and  372736 - Equipmt/vehicle:rounding error because of SI units
    It may help you.
    But in my system i can view only "Y"
    Regards,
    Pardhu

  • Error  Enter a value for field BP_GUID

    I am using MDG  7.0
    When I create a  Request for "Create ERP Customer",
    I then enter data including the sales Area Data and Company Code data
    Then Submit
    at the following approval step , Sales Area data and CC data is missing.
    I get ERROR message  "Enter a value for Field BP_GUID"
    Please advise what Table or T-code am I missing values for .
    Thanks for your assistance,

    hi,
    See the attached screen shot.
    Regards,
    Tushar

  • UDF - Set Valid Values for Field

    I have a UDF created in Marketing Docs / row level called UOM_Ordered (alphanumeric, length 2) using Set Valid Values for Field.  Values are:
    CS
    IN
    DZ
    PC
    Above are CS abrev for Case, IN abrev for Inner, DZ abrev for Dozen .................
    If possible could I have say for example "IN" not to appear in the drop down if the value in OITM (UDF called U_Inner_Qty) is either NULL or a Zero?  It's would be a way to stop mistakes when orders are inputted.
    Any help on this would be appreciated.
    Thks - Scott

    Hello
    You could try the following:
    Insert a formatted search on the field, which contain conditions, ie whether the condition that the value is 0 or null, then bring the required data, while if it is not the case, applies the search formatted with the available data.
    On the other hand, leave the form with all the options for disabled users. The latter through additional authorizations for users
    I hope it will help
    Best regards,

  • In TXN CO03, extract value for field "To Confirm" under tab "Qty/Activity"

    Hi,
    Can anyone help to extract value for field "To Confirm" under tab "QTY/ACTIVITIES" in tansaction CO03 at operatin level. There are three Activiti (CC-Set-up,CC-Labor Time & CC-Var-OH) under table control Activities. I need value of the field "To Confirm" for CC-Labor Time.
    From where I can fetch this value,
    1. Is this field available in some table?
    2. Is there any FM with which the same can be extracted.
    3. Any other method?
    Regards,
    Bibhuti.
    Edited by: bibhuti kumar on Feb 20, 2008 6:16 AM

    Hi,
    pls use below table's and get detals you want
    AFKO - Order header details
    AFVC - Order operation details
    AFVV - Order operation value/date's/qty details
    the relation is below
    Step1: AFKO; AUFNR-->AFKO-AUFPL
    Step2: AFVC; AFKO-AUFPL = AFVC-AUFPL
    take filed to APLZL,VORNR
    Step3: AFVV;AFKO-AUFPL=AFVV-AUFPL, AFVC-AUFPL = AFVV-AUFPL
    take filed to MGVRG,LMNGA,XMNGA,VGW02
    Step4: (MGVRG - (LMNGA+XMNGA)) * VGW02
    hope this will solve your problem
    Regards,
    Sankaran

  • New field creation in Condition Table?

    Hi Gurus
    I want to know whether it is possible to add a new field in field catalogue whle creating a condition table. I want to add Chapter Id of the material.
    Thanks
    Rishi

    Hi Rishi,
    Follow below example-
    Add a Field To New Condition Table in Pricing
    Add a field to a new condition table in Pricing (Condition Technique):-
    I will explain you the process with below example...Please follow steps in below sequence-
    Try to add the filed from the field catalog.  In case the required combination field is not there, you can add the field through the following process to filed catalog and create the condition table.   It is most common that one or other time we need to use this function while configuring multi tasking & complex Pricing Architecture.
    Here I'm giving a simple guide to add fields to the Pricing Field Catalogues:
    For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
    When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
    Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
    Reason and Prerequisites: 
    For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
    Proceed as follows:
    1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
    2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
    Component Component type:
    ZZPSTYV ZZPSTYV
    Save, check and activate the change you made.
    3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
    4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'.
    Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
    5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
    6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
    MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
    In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
    Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.
    For header fields, use structure KOMKAZ instead of structure KOMPAZ and
    USEREXIT_PRICING_PREPARE_TKOMK instead of
    USEREXIT_PRICING_PREPARE_TKOMP.
    For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.
    Regds
    MM

  • Default values for fields in infotype 0017

    Is there any way to set default values for fields in infotype 0017? Maybe a
    feature? I'm thinking about defaulting values based on pay scale group.
    Thanks before.

    Hi
    You can implement what i suggested in my previous post.
    Or else, you can do what we did in one of our client requirement.
    We created a custom Ztable where we had defined which value of the the employee grouping to be placed for which record.
    We did that on the basis of the company code fields.
    For eg: IF BUKRS = 'TR01'
    then EE Grp Expense Type = '1'.
    ENDIF.
    Similarly for other fields.
    Hope this helps.
    Harsh

  • FRM-40212: Invalid value for Field SHIP_TO_ADDRESS1on forms OEXOETEL

    I want to customize a form "OEXOETEL". I want to copy some values from another order to a new order.When i navigate to a block LINE i receive this message: "FRM-40212: Invalid value for Field SHIP_TO_ADDRESS1".
    cursor c_order(p_header_id varchar2) is
    select o.sold_to,
    o.order_type,
    o.terms,
    o.ship_from,
    o.SHIP_to_org_id,
    o.ship_to_address1,
    o.ship_to_address5,
    o.customer_number,
    o.invoice_to_org_id,
    o.INVOICE_TO_LOCATION,
    o.SHIP_TO_LOCATION,
    o.invoice_to_address1,
    o.invoice_to_address5,
    o.sold_to_contact
    from oe_order_headers_v o,
    hz_parties hzp
    where hzp.party_name = o.sold_to
    and o.header_id = p_header_id;
    IF l_block_name IN ('ORDER') THEN
    IF p_event = 'WHEN-NEW-RECORD-INSTANCE' THEN
    open c_order(name_in('global.header_id'));
    loop
         fetch c_order into x_order_row;
    exit when c_order%notfound;
         copy(x_order_row.customer_number,'ORDER.CUSTOMER_NUMBER');
         copy(x_order_row.sold_to,'ORDER.SOLD_TO');
    copy(x_order_row.ship_to_org_id,'ORDER.SHIP_TO_ORG_ID');
    copy(x_order_row.SHIP_TO_LOCATION,'ORDER.SHIP_TO_LOCATION');
         copy(x_order_row.ship_to_address5,'ORDER.SHIP_TO_ADDRESS5');
    copy(x_order_row.ship_to_address1,'ORDER.SHIP_TO_ADDRESS1');
    copy(x_order_row.ship_to_address1,'ORDER.SHIP_TO_ADDRESS1_MIR2');
         copy(x_order_row.invoice_to_org_id,'ORDER.INVOICE_TO_ORG_ID');
         copy(x_order_row.invoice_TO_LOCATION,'ORDER.INVOICE_TO_LOCATION');
         copy(x_order_row.invoice_to_address5,'ORDER.INVOICE_TO_ADDRESS5');
    copy(x_order_row.invoice_to_address1,'ORDER.INVOICE_TO_ADDRESS1');
    copy(x_order_row.INVOICE_TO_LOCATION,'ADDRESSES.INVOICE_TO_LOCATION');
         copy(x_order_row.order_type,'ORDER.ORDER_TYPE');
         copy(x_order_row.sold_to_contact,'ORDER.SOLD_TO_CONTACT');
         copy(x_order_row.ship_from,'ORDER.SHIP_FROM');
    end loop;
    close c_order;
    end if;
    end if;

    Review Note: 302613.1 - OEXOEORD: Cannot select List of Values From The Ship To Address1 Field
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=302613.1

  • Selecting a document field for a field in a condition table/access

    Hello
    I created a pricing condition table using field WGHIE from the standard field catalog.
    Img/SD/Basic Functions/Pricing/Pricing Control/Define Access Seq
    I can assign the table to a access, but when I try to do the field assigment it give's me the message "<i>Select a document field for WGHIE</i>"  at the field assignment part.
    In the fields display the WGHIE field has nothing listed in the Doc Field and it's grayed out so you cant change it.   Also in the I/0 field its red lighted
    Any ideals as to how I can fix this.   
    Thanks

    Rudy,
    For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040
    REWARD IF U FINDS THIS AS USEFUL...
    Regds
    MM

  • Excise rates not reflecting in PO based on values entered in newly created condition table in TAXINN.

    Dear SAP Gurus,
    I have created a new condition table using t.code m/03 by taking a copy of existing standard condition table. I have assigned the newly created condition table to access sequence. After assignment of condition table i have entered the relevant excise rates in excise condition types using the newly created key combination through t.code FV12. When i enter the Tax Code in PO, excise duty rates are not reflecting in PO. When i am entering the excise rates in any other standard key combination, excise rates are reflecting in PO.
    Following are the fields in newly created key combination (Condition Table)
    1) Country
    2) Plant
    3) Control Code
    4) Tax Code
    Kindly help me in resolving the issue.
    Regards,
    Vinay

    HI,
    Check whether you have maintained the rates for the new tax code in FV11 also whether you have assigned the tax code to the company code ?
    Compare the tax code which is working in PO with the one which is not & find out if there is any difference.
    If you want to post the tax values to the new G/L in OB40 then maintain the same settings for the tax code which is working in PO.
    Thanks & Regards,

  • Update routine to populate value for field ZDOCCATG(Document category)

    Hi Experts,
       I need to populate  data for field ZDOCCATG(Document Category) based on the value of the below  two fields,
    1. 0deb_cre_lc(Debit / credit Amount)
    2. 0ac_doc_typ(Belegart)
    The logic is as follows:
    if 0deb_cre_lc > '0'.
         if 0ac_doc_typ == 'dz'.
          ZDOCCATG = Disputes.
         else
      ZDOCCATG = Invoices.
       end If.
    else
    if 0ac_doc_typ < '0'.
    ZDOCCATG = Credits.
    end if.
    I need to write the update routine to get the values assigned for Document category based on these two fields. When i open the routine for the field ZDOCCATG, i can see the below screen:
    PROGRAM UPDATE_ROUTINE.
    $$ begin of global - insert your declaration only below this line  -
    TABLES: ...
    DATA:   ...
    $$ end of global - insert your declaration only before this line   -
    FORM compute_data_field
      TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
      USING    COMM_STRUCTURE LIKE /BIC/CS80FIAR_O03 - (Communication structure)
               RECORD_NO LIKE SY-TABIX
               RECORD_ALL LIKE SY-TABIX
               SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
      CHANGING RESULT LIKE /BIC/AZOARFSCM00-/BIC/ZDOCCATG
               RETURNCODE LIKE SY-SUBRC "Do not use!
               ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
    $$ begin of routine - insert your code only below this line        -
    fill the internal table "MONITOR", to make monitor entries
    result value of the routine
      RESULT = .
    if abort is not equal zero, the update process will be canceled
      ABORT = 0.
    $$ end of routine - insert your code only before this line         -
    ENDFORM.
    Please let me know the code to be inserted (based on the logic mentioned above) in the above screen . Thanks
    Regards,
    Kavitha Jagannath

    Hi Kavitha,
          Supposing the technical name of fields is /bic/0deb_cre_lc and /bic/0ac_doc_typ use the code below at the marked position.
    PROGRAM UPDATE_ROUTINE.
    $$ begin of global - insert your declaration only below this line -
    TABLES: ...
    DATA: ...
    $$ end of global - insert your declaration only before this line -
    FORM compute_data_field
    TABLES MONITOR STRUCTURE RSMONITOR "user defined monitoring
    USING COMM_STRUCTURE LIKE /BIC/CS80FIAR_O03 - (Communication structure)
    RECORD_NO LIKE SY-TABIX
    RECORD_ALL LIKE SY-TABIX
    SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
    CHANGING RESULT LIKE /BIC/AZOARFSCM00-/BIC/ZDOCCATG
    RETURNCODE LIKE SY-SUBRC "Do not use!
    ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
    $$ begin of routine - insert your code only below this line -
    fill the internal table "MONITOR", to make monitor entries
    result value of the routine                 
    <----- Paste the code below as shown here --->
    if comm_structure-/bic/0deb_cre_lc > 0.
      if comm_structure-/bic/0ac_doc_typ == 'DZ'.
       result = 'DISPUTES'.
      else
       result = 'INVOICES'.
      endIf.
    elseif comm_structure-/bic/0deb_cre_lc < 0.
      result = 'CREDITS'.
    end if.
    <----
    >
    if abort is not equal zero, the update process will be canceled
    ABORT = 0.
    $$ end of routine - insert your code only before this line -
    ENDFORM.
    Regards:
    Jitendra
    Edited by: Jitendra Gupta on Oct 15, 2009 3:05 PM

  • Need to add new fields to the condition table

    Hello All,
    The requirement is to create the new condtion table for MM containing the following fields and maintain the entries in this table:
    - client
    - characteristic
    - class
    - internal characteristic.
    THe condition tables are created via tcode M/03 or through the customizing path
    Material Management > Purchasing > Conditions > Define Price Determination Process > Maintain Condition Table.
    The problem which i am facing is as follows :
    -SAP has the standard procedure for the generation of the condition tables . Selected fields are made available by SAP in the field catalog and we can select only from the those available fields. Once we select the required fields the condition table is automatically generated in the background.
    -As the requirement is, we need to have 4 fields in the generated condition table (client, characteristic, class and internal characteristic), but the problem is that none of these fields are available in the field catalog which is provided by SAP (in tcode M/03, M/04 and M/05).
    -Designing of the Z table wonu2019t be useful as we would not be able to use the Z table as the condition table.
    Can you please suggest how can we add the desired field to the existing field catalog in M/03 or is there any other alternate solution to this ?
    Thanks in advance for your help.

    >
    Rinkesh Doshi wrote:
    > Hello,
    >
    > The specific ABAP question which I have is :
    >
    > Is there any way in which we can enhance the existing field catalog in M/03 tcode to include the 4 new fields (client ,characteristic,class,internal characteristic) ?
    >
    > Thanks.
    Please post your code which you developped until now and show us where the problem is. I cant see any ABAP related question.

  • 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

  • Adding custom fields to the condition table in CRM

    Hi all,
    Our requirement is to download the sales conditions type from R3 to the CRM system. In one of the condition table we are trying to add shipping point( VSART ) and Special processing indicator (SDABW).
    For that we have added the fields in the structure CND_MAPT_ACS_REM_CUST (Comm. Structure Condition Exchange Customer Exit R/3 Fields) and we have added the fields in the field catelog in transaction ( /SAPCND/CTCT - Maintain Condition Tables). Then we have mapped these fields in the view V_CND_MAP_CNVFLD.
    Finally we run the adapter object of that particular table to download the details from R3, but the condition table in CRM is not getting activated, so the adapter object is giving the error.
    Please help in this.
    Thanks & Regards,
    Raghuram.

    Hello Raghuram,
    I feel that your issue is similar what i have faced, refer to my post:
    Link: [Issue in customer specific price;
    For solving this you can refer to detailed steps in,  Note 514952 - Download of customer-specific tables.
    Also additionaly you may need to run the report /sapcnd/rv12n001, as i also had to do so.
    If not solved then let me know the relevant message in SLG1
    Regards

  • Setting default values for field on screen.

    Hello,
    I am trying to set default value for one of the fields I have on screen when I execute the custom transaction.
    I am doing that in PBO as follows. But the default value is not set for Date field.
    PROCESS BEFORE OUTPUT.
    MODULE PBO_OUT.
    MODULE STATUS_5000.
    *&      Module  STATUS_5000  OUTPUT
          text
    MODULE STATUS_5000 OUTPUT.
      SET PF-STATUS 'NON_SAP_DOCUMENT'.
      SET TITLEBAR '001'.
    ENDMODULE.                 " STATUS_5000  OUTPUT
    *&      Module  PBO_OUT  OUTPUT
          text
    MODULE PBO_OUT OUTPUT.
      ERDAT = SY-DATUM.
    ENDMODULE.                 " PBO_OUT  OUTPUT
    Please help.
    Thanks.
    Regards,
    Rajesh.

    Works Now...

Maybe you are looking for