Master Data not updating

We have found that are master data text isn't updating in APO from BW.  I can see that the data is in the APO PSA but doesn't reflect in the master data object.  We tried deleting the master data but the application advises that you cannot delete master data that's being referenced.
Are these problems related?
Why will the master data descriptions not update?
Please suggest a solution.

We have are pulling the description text from BW into APO via a master text load.  I am loading the data into the PSA and then into the maste data object.  The PSA shows the correct description.  When I view the master data, the description is empty.  We are updating 0LANGU, QSMATNR, and 0TXTLG.  When I look at the info object table /BIC/TQSMATNR, there are no table entries.

Similar Messages

  • Asset Master Data not updated

    Quantity purchased via PO is not updating the master data of the newly created fixed assets.
    When created and inserted into any number, the amount is updated with the purchase.
    What do you make the purchase of newly created assets are properly updated in the asset master data?
    GLippmann

    The SAP Notes instrctions solved the problem.
    Thank you mvery much.
    Best Regards...
    GLippmann

  • ADF master-detail master selection not updating detail tables properly

    Hi All,
    I am using JDev version : 11.1.2.0.0
    I created new Fusion Web Application Module. In that module I created a master-detail data model and added them to a page fragment with a query panel. When I run it as a separate module, It works perfectly and Master selection correctly updates detail tables.
    But when I integrate that module to another Fusion Application(Add application jar file to the Master Application libraries), Master-details master selection not updating detail tables properly. This problem occurred sequentially.
    The problem is that.
    After the page load, first selection of the Master Table works correctly and detail tables update correctly.
    But second selection doesn't work, means detail table doesn't get update according to the Master table.
    And again in the third selection works correctly.
    This happens in a sequential manner. I monitor the behavior using Firebug. Observations are as follows,
    When running correctly, Response of the Post Definition is
    <?xml version="1.0" ?> <partial-response><changes><update id="pt1:t1"><![CDATA[<div tabindex="0" id="pt1:t1" class="xpa xpi" _leafColClientIds="['pt1:t1:c1','pt1:t1:c2','pt1:t1:c3','pt1:t1:c4','pt1:t1:c5','pt1:t1:c6','pt1:t1:c7','pt1:t1:c8','pt1:t1:c9','pt1:t1:c10','pt1:t1:c11','pt1:t1:c12','pt1:t1:c13']"><div id="pt1:t1::ch" style="overflow:hidden;position:relative;width:1365px;" _afrColCount="13" class="xz4"><table class="xz6" summary="This table contains column headers corresponding to the data body table below" id="pt1:t1::ch::t" style="position:relative;table-layout:fixed;width:1365px" cellspacing="0"><tr><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th></tr><tr><th id="pt1:t1:c1" _d_index="0" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c1::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DateFormat</div></th><th id="pt1:t1:c2" _d_index="1" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c2::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DefinisionId</div></th><th id="pt1:t1:c3" _d_index="2" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c3::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldId</div></th><th id="pt1:t1:c4" _d_index="3" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c4::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLabel</div></th><th id="pt1:t1:c5" _d_index="4" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c5::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLength</div></th><th id="pt1:t1:c6" _d_index="5" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c6::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOffset</div></th><th id="pt1:t1:c7" _d_index="6" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c7::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOrder</div></th><th id="pt1:t1:c8" _d_index="7" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c8::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldStatus</div></th><th id="pt1:t1:c9" _d_index="8" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c9::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldType</div></th><th id="pt1:t1:c10" _d_index="9" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c10::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldTypeLen</div></th><th id="pt1:t1:c11" _d_index="10" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c11::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IgnoreField</div></th><th id="pt1:t1:c12" _d_index="11" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c12::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IsMandatory</div></th><th id="pt1:t1:c13" _d_index="12" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c13::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">RecordType</div></th></tr></table></div><div id="pt1:t1::db" class="xyx" style="position:relative;width:100%;overflow:hidden" _afrColCount="13"></div><div id="pt1:t1::sm" class="xzt" style="position:absolute;display:none"></div><div id="pt1:t1::ri" class="xyz" style="position:absolute;display:none;overflow:hidden"></div><div id="pt1:t1::dataW" style="display:none"></div></div>]]></update><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="d1::iconC"><![CDATA[<span id="d1::iconC" style="display:none"><span id="af_table::disclosed-icon"></span><span id="af_table::undisclosed-icon"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval><![CDATA[AdfPage.PAGE.sendStreamingRequest("pt1:t1");]]></eval><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/dnd-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/nav-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/menu-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/table-SHERMAN-1147.js</extension><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){   self.location = "mcsd.html";   }</eval><eval><![CDATA[AdfDhtmlLookAndFeel.addSkinProperties({"af|table-tr-column-scroll-animation-duration":"300","af|table-tr-column-reorder-animation-duration":"600","af|table-tr-hover-highlight-row":"true"});AdfPage.PAGE.addComponents(new AdfRichTable('pt1:t1',{'rowSelection':'single','rowBandingInterval':0,'editingMode':'none','afrSelListener':true}),new AdfRichColumn('pt1:t1:c1',{'sortProperty':'DateFormat','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c2',{'sortProperty':'DefinisionId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c3',{'sortProperty':'FieldId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c4',{'sortProperty':'FieldLabel','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c5',{'sortProperty':'FieldLength','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c6',{'sortProperty':'FieldOffset','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c7',{'sortProperty':'FieldOrder','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c8',{'sortProperty':'FieldStatus','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c9',{'sortProperty':'FieldType','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c10',{'sortProperty':'FieldTypeLen','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c11',{'sortProperty':'IgnoreField','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c12',{'sortProperty':'IsMandatory','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c13',{'sortProperty':'RecordType','sortable':true,'minimumWidth':12,'rowHeader':false}));AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
    When not running correctly, Response of the Post Definition is
    <?xml version="1.0" ?> <partial-response><changes><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){   self.location = "mcsd.html";   }</eval><eval><![CDATA[AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
    I could not figure out what went wrong when integrating to another module.
    Can you please help me to rectify this problem.
    Thanks
    dk

    Hi,
    sound to be an implementation specific issue that is hard to comment on without knowing how to reproduce it. If you have a rerooducible test case based on the Oracle HR schema using JDeveloper 11.1.1.6, zip it up, rename the "zip "extension to "unzip" and sent it to the mail address you find in my OTN profile. If you don't have that test case, explain how this can be reproduced
    Frank

  • Access master data in update rules

    Hi,
    I try to calculate a weight in my update rules. Therefore I need the product weight and the number of peaces. I try to read the product weight from master data. The problem is, that it always calculates zero as the result. Is it possible to read master data in update rules?
    If I try to calculate the weight in the transfer rules, I get the message in the monitor, that the transfer rules don't finish. Do you have an idea what to do?
    Regards,
    Gabi

    Hi Robert,
    here is my code in the update rule.
    fill the internal table "MONITOR", to make monitor entries
      DATA: l_s_errorlog TYPE RSMONITOR.
      data: temp_prod_weight type /BIC/PZL2_P_ID.
    general values
      RESULT = COMM_STRUCTURE-/BIC/ZL2_POTMW.   "weight
      UNIT = COMM_STRUCTURE-UNIT_OF_WT.
      RETURNCODE = 0.
      ABORT = 0.
    calculate weight from master data, if it is zero
      IF COMM_STRUCTURE-/BIC/ZL2_POTMW = 0
      or COMM_STRUCTURE-/BIC/ZL2_POTMW = '0'
      or COMM_STRUCTURE-/BIC/ZL2_POTMW is initial.
        select single /BIC/ZL2_NETW UNIT_OF_WT
        from /BIC/PZL2_P_ID
        into corresponding fields of temp_prod_weight
        where /BIC/ZL2_P_ID = COMM_STRUCTURE-/BIC/ZL2_P_ID
        and objvers = 'A'.
        if sy-subrc <> 0.
          l_s_errorlog-MSGTY = 'I'.
          append l_s_errorlog to MONITOR.
          RESULT = 0.
    abort, if calculation is not possible
          ABORT = 1.
        else.
          RESULT = temp_prod_weight-/BIC/ZL2_NETW
    COMM_STRUCTURE-/BIC/ZL2_POTMQ.
          UNIT = temp_prod_weight-UNIT_OF_WT.
        endif.
    ENDIF.
    convert unit
      CALL FUNCTION 'UNIT_CONVERSION_SIMPLE'
        EXPORTING
          INPUT                      = RESULT
        NO_TYPE_CHECK              = 'X'
        ROUND_SIGN                 = ' '
          UNIT_IN                    = COMM_STRUCTURE-UNIT_OF_WT
          UNIT_OUT                   = 'KG'
        IMPORTING
        ADD_CONST                  =
        DECIMALS                   =
        DENOMINATOR                =
        NUMERATOR                  =
          OUTPUT                     = RESULT
        EXCEPTIONS
          CONVERSION_NOT_FOUND       = 1
          DIVISION_BY_ZERO           = 2
          INPUT_INVALID              = 3
          OUTPUT_INVALID             = 4
          OVERFLOW                   = 5
          TYPE_INVALID               = 6
          UNITS_MISSING              = 7
          UNIT_IN_NOT_FOUND          = 8
          UNIT_OUT_NOT_FOUND         = 9
          OTHERS                     = 10
      IF SY-SUBRC <> 0.
        l_s_errorlog-MSGTY = 'I'.
        append l_s_errorlog to MONITOR.
        UNIT = COMM_STRUCTURE-UNIT_OF_WT.
        RESULT = COMM_STRUCTURE-/BIC/ZL2_POTMW.
      ELSE.
        UNIT = 'KG'.
      ENDIF.
    I'm loading via PSA, but I have problems to debug the code. If I set a break point in my code (command break-point), I can't stop at it.
    Thanks,
    Gabi

  • How to look up master data in update rule

    Hi Friends,
    I want to Fill a characteristic of an info cube using the attribute value in a master data in Update rule.
    Eg: I want to fill a field in cube 0PM_C01 that is got from Master data 0PM_ORDER. I have to do this in upate rule. Can anyone help me.
    Joe

    Eugene, Atlaj
    Your answers were very useful.
    Eugene as you said,
    I read the link you mentioned and I can use code
    like this
    DATA: mat LIKE /BI0/PMATERIAL-MATERIAL.
    SELECT SINGLE MATERIAL FROM /BI0/PMATERIAL INTO mat
    WHERE EANUPC = COMM_STRUCTURE-EANUPC AND OBJVERS = 'A'.
    IF SY-SUBRC = 0.
    RESULT = mat.
    RETURNCODE = 0.
    ELSE.
    RETURNCODE = 8.
    ENDIF.
    But for each record of comm structure the selection quer y will touch the Data base. As Atlaj said, can I fill the internal table in the start routine and look it up in the update rules. I think the performance willbe increased. Could you give me code sample or link?
    Thanks in ADV
    Joe

  • FM for master data creation/update

    Hello all,
    I would like to ask you for a FM for master data creation/update.
    Thanks all for your help.

    The answer is API_SEMBPS_CHA_VALUES_UPDATE.

  • All Master data not displaying

    Hi all;
    I am tring to create Hierarchy for some values for one master data object.
    Here is the issue:
    If I go to the RSD1 > 0costcenter > maintain master data > If I execute with maxm hits I get let's say 200 records for that master data But If I enter some value which is there in the master data instead of the execution it's not displaying anything.
    Same thing I am trying to create Hier for those cost centers but in the hier maintaince window when I enter that costcenter it does not display anything...and I check in Maintain Master data for 0costcenter those value are there when i execute all but don't see again if I give that particular value and execute.
    Any reason...
    Thanks.

    Hi simon;
    I checked that table and all the entries are version 'A' and I also saw there the ones that are not coming while creating hier are active as well. I also checked tcode RSATTR and there is nothing left for change run., this is production env,. and we do change run every night after the process chain.
    Thank you for you reply do you think anything else because those some master data not populating...on selection?

  • Data not Updated in Custom Screen fields-Vendor Master

    Hello,
    I have created a custom screen in vendor master transaction and also implemented the two BADI's below.
    Business Add-In: Processing Master Data Enhancements
    (CUSTOMER_ADD_DATA/VENDOR_ADD_DATA)
    Passed the Custom Program and Screen No in the method GET_TAXI_SCREEN
    Business Add-In: Customer Subscreens
    (CUSTOMER_ADD_DATA_CS/VENDOR_ADD_DATA_CS)
    activate it with the BADI Processing Master Data Enhancements with method CHECK_ADD_ON_ACTIVE.
    I also created a new screen and used few fields from LFA1 (Append structure fields) such that the fields on the screen are : LFA1-ZZFIELD1 etc...
    Now the issue is the screen is displayed, but the data entered on the screen is not updated on the table LFA1 or data from the table is not displayed on the custom screen.
    Am i missing something?
    Regards,
    Shiva

    Solved this problem.
    I built the query against InfoCube and not the characteristic itself. That's why I can't see the update.
    Thanks.

  • Master data delta update to data souce not possible

    Hi,
    0material_att data source delta update failed for a few days from the process chain and when I tried to manually run the delta infopackage, I got this message:
    Last delta update is not yet completed
    Therefore, no new delta update is possible.
    You can start the request again
    if the last delta request is red or green in the monitor (QM activity)
    I did "manage" for this data source but none of the failed delta run showed in there. I also looked for cancelled jobs in sm37 but nothing came up either. So I ran a full upload without deleting the data as my user is waiting for this fix to be shown in the report. What can I do now to enable the delta run again without deleting the data?
    sharon

    Hi Sharon,
    chk in RSMO for that master data 0material_attr, if there are any red/yellow req. If so change the QM status to RED again and goto IP and trigger the load again (it wil say that earlier delta has failed and if u want to Repeat ;ast delta,) in that give OK and exe the load again.
    In some cases, the datasource will not support repeat deltas, in that case do a re-init for the master data load. (no need to delete any datas.)
    Hope this helps. If you have any queries please ask.
    Thanks!
    Dharini

  • Extraction of certain master data not working

    Hi, we are on BI7 and some of the BC masterdata extractions are not working correctly.  Some masterdata working fine, consequently communication between systems working, but some master data fields e.g. 0co_area, 0chrt_accts and more are not working fine.  Get this on 3.x and new datasources.
    The data does get pulled through but the upload just never goes green, and keeps running.  If one look at the batch jobs (SM37) in the appropriate source system, it keeps on going until it is manually stopped. 
    I am only experiencing this problem with data pulled through from the production system - I am pulling it through to my testing and production box, but fails in both, where all other ECC systems are fine.
    In the monitor there is a warning and the following is the details of the monitor: 
    Overall status: Missing Messages or warnings
       Requests (messages):  Everything OK  (green)       Data request arranged  (green)
           Confirmed with:  OK (green)
       Extraction (messages): Missing messages (yellow)
           Data request received (green)
           Data selection scheduled (green)
           Missing message:  Number of sent records (yellow)
           Missing message: Selection completed (yellow)
       Transfer (IDocs and TRFC): Missing messages or warnings (yellow)
           Request IDoc: Application document posted (green)
           Info IDoc 1 : Application document posted (green)
           Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n (yellow)
           Info IDoc 2 : Application document posted (green)
       Processing (data packet) : Everyting OK (green)
           Inboun Processing (32 records) : No errors (green)
           Update PSA (32 records posted) : No errors (green)
           Processing end : No errors (green)

    Thanks, for the responses.  The appropriate Idocs work fine with transaction BD87. I looked in SM58 earlier during the course of the day and there was no error, just checked again (8PM) and found some entries with error texts for BW background user - 6 errors within 10 seconds.  Something to do with 'ERROR REQU... PG# IN 1' - do not have authorisation at this moment to check the specific requests, but not sure if the master data extractions would have caused these.
    In the job log for the problematic jobs, only 1 IDoc get created, unlike the other succesful ones that have 3 IDocs (not sure if this means anything)

  • Data Not updated in BDC

    hi alll
    1.   i have written below coding for vendor master update. i have two records in text file, in that first record not updated. while updating its shows error. but second record updated. how can i solve. plse help me
    2.  I want to show the error message or i want to print how can i do it
    REPORT  ZVENTESTBDC.
    data : begin of it_xk01 occurs 0,
             LIFNR(10) type c,
             BUKRS(4) type c,
             EKORG(4) type c,
             KTOKK(4) type c,
             NAME1(30) type c,
             SORT1(10) type c,
             LAND1(3) type c,
             AKONT(10) type c,
             FDGRV(10) type c,
             WAERS(3) type c,
          end of it_xk01.
    DATA : IT_BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE,
           IT_BDCMSGCOLL LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
    CALL FUNCTION 'GUI_UPLOAD'
      EXPORTING
       FILENAME                      = 'C:\Documents and Settings\entegall\Desktop\vendor.txt'
       FILETYPE                      = 'ASC'
       HAS_FIELD_SEPARATOR           = 'X'
      HEADER_LENGTH                 = 0
      READ_BY_LINE                  = 'X'
      DAT_MODE                      = ' '
      CODEPAGE                      = ' '
      IGNORE_CERR                   = ABAP_TRUE
      REPLACEMENT                   = '#'
      CHECK_BOM                     = ' '
      VIRUS_SCAN_PROFILE            =
      NO_AUTH_CHECK                 = ' '
    IMPORTING
      FILELENGTH                    =
      HEADER                        =
      TABLES
        DATA_TAB                      = it_xk01.
    loop at it_xk01.
       refresh it_bdcdata.
      perform open_group.
    perform bdc_dynpro      using 'SAPMF02K' '0100'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'RF02K-REF_LIFNR'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'RF02K-LIFNR'
                                   it_xk01-lifnr.
    perform bdc_field       using 'RF02K-BUKRS'
                                  IT_XK01-BUKRS.
    perform bdc_field       using 'RF02K-EKORG'
                                  IT_XK01-EKORG.
    perform bdc_field       using 'RF02K-KTOKK'
                                  IT_XK01-KTOKK.
    perform bdc_dynpro      using 'SAPMF02K' '0110'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'LFA1-LAND1'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'LFA1-NAME1'
                                  IT_XK01-NAME1.
    perform bdc_field       using 'LFA1-SORTL'
                                   IT_XK01-SORT1.
    perform bdc_field       using 'LFA1-NAME2'
    perform bdc_field       using 'LFA1-LAND1'
                                  IT_XK01-LAND1.
    perform bdc_dynpro      using 'SAPMF02K' '0120'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'LFA1-KUNNR'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_dynpro      using 'SAPMF02K' '0130'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'LFBK-BANKS(01)'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=ENTR'.
    perform bdc_dynpro      using 'SAPMF02K' '0210'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'LFB1-FDGRV'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'LFB1-AKONT'
                                  IT_XK01-AKONT.
    perform bdc_field       using 'LFB1-FDGRV'
                                  IT_XK01-FDGRV.
    perform bdc_dynpro      using 'SAPMF02K' '0215'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'LFB1-ZTERM'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_dynpro      using 'SAPMF02K' '0220'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'LFB5-MAHNA'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_dynpro      using 'SAPMF02K' '0310'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'LFM1-WAERS'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'LFM1-WAERS'
                                  IT_XK01-WAERS.
    perform bdc_dynpro      using 'SAPMF02K' '0320'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'RF02K-LIFNR'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '=UPDA'.
    *perform bdc_transaction using 'XK01' using IT_BDCDATA mode 'A' UPDATE 'S'
    CALL TRANSACTION 'XK01' USING IT_BDCDATA
                            MODE  'A'
                           UPDATE 'S' MESSAGES INTO IT_BDCMSGCOLL.
    *perform close_group.
    endloop.
    FORM BDC_DYNPRO USING PROG SCR.
      CLEAR IT_BDCDATA.
      IT_BDCDATA-PROGRAM = PROG.
      IT_BDCDATA-DYNPRO  = SCR.
      IT_BDCDATA-DYNBEGIN = 'X'.
      APPEND IT_BDCDATA.
    ENDFORM.
    FORM BDC_FIELD USING FNAM FVAL.
      CLEAR IT_BDCDATA.
      IT_BDCDATA-FNAM = FNAM.
      IT_BDCDATA-FVAL  = FVAL.
      APPEND IT_BDCDATA.
    ENDFORM.

    go through this porgarm u will get the clear picture about down loading the error msg.
    PROGRAM ID     : ZSD_CONDREC_DISCOUNT_ZSWD
    DESCRIPTION    : BDC PROGRAM TO UPLOAD CONDITION RECORDS FOR Discount
    TRANSACTION    : VK11
    CONDITION TYPE : ZSWD(Key combination 3)
    VERSION        : 1.0
    Text Elements
    001  :  Select Options
    002  :  C:\SD\Error\Discount-ZSWD
    003  :  Error Download Path
    004  :  C:\SD\Error\Discount-ZSWD - DDMMYYYY HH:MM:SS.txt
    REPORT ZSD_CONDREC_DISCOUNT_ZSWD
           MESSAGE-ID 00.
    *include bdcrecx1.
    TABLES : t100.
           Internal table declaration                                    *
    DATA : BEGIN OF it_price OCCURS 0,
                  index(4),      "Index
                  kschl(4),      "Condition type
                  vkorg(4),      "Sales organization
                  vtweg(2),      "distribution channel
                  spart(2),      "Division
                  matnr(18),     "Material no
                  kbetr(11),     "Rate
                  konwa(5),      "Rate unit (currency or percentage)
                  kmein(3),      "Condition unit
                  krech(1),      "Calculation type for condition
                  datab(10),     "Validity start date
                  datbi(10),     "Validity end date
                  er_message(100),
           END OF it_price.
    Internal table to get the error data                                 *
    DATA : it_error LIKE it_price OCCURS 0 WITH HEADER LINE.
    DATA : bdcdata LIKE bdcdata OCCURS 0 WITH HEADER LINE.
    DATA : i_msgtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
    Internal table to find the error from the legacy data                *
    DATA : BEGIN OF it_erfind OCCURS 0,
                  index(4),      "Index
                  er_message(100),  "For Error Message
           END OF it_erfind.
    Variables declaration                                                *
    DATA : g_message(200),
           time(10),
           date(10)  ,
           v_error_filename LIKE rlgrap-filename.
    date      = sy-datum.
    time      = sy-uzeit.
           Initialization
    INITIALIZATION.
    Generating Error file name with date and time.
      PERFORM make_file_name.
           Selection Screen                                              *
      SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
      PARAMETER: p_file LIKE ibipparms-path OBLIGATORY.
      SELECTION-SCREEN SKIP.
      SELECTION-SCREEN BEGIN OF LINE.
      SELECTION-SCREEN COMMENT 1(30)  text-003.
      SELECTION-SCREEN COMMENT 33(79) text-004.
      SELECTION-SCREEN END OF LINE.
      SELECTION-SCREEN:END OF BLOCK b1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file .
      PERFORM get_filename.
    Start of selection
    START-OF-SELECTION.
      PERFORM upload_data.
      PERFORM fill_data.
    END-OF-SELECTION.
    *&      Form  fill_data
          text
    FORM fill_data.
      LOOP AT it_price.
    *Start of Screen 1
        PERFORM bdc_dynpro      USING 'SAPMV13A' '0100'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RV13A-KSCHL'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ANTA'.
        PERFORM bdc_field       USING 'RV13A-KSCHL'
                                      it_price-kschl.
    Key Combination: Sales org / Dist. channel / Division / Material
        PERFORM bdc_dynpro      USING 'SAPLV14A' '0100'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RV130-SELKZ(03)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=WEIT'.
        PERFORM bdc_field       USING 'RV130-SELKZ(03)'
                                      'X'.
    *Start of Screen 2
        PERFORM bdc_dynpro      USING 'SAPMV13A' '1800'.
        PERFORM bdc_field       USING 'KOMG-VKORG'
                                      it_price-vkorg.
        PERFORM bdc_field       USING 'KOMG-VTWEG'
                                      it_price-vtweg.
        PERFORM bdc_field       USING 'KOMG-SPART'
                                      it_price-spart.
        PERFORM bdc_field       USING 'KOMG-MATNR(01)'
                                      it_price-matnr.
        PERFORM bdc_field       USING 'KONP-KBETR(01)'
                                      it_price-kbetr.
        PERFORM bdc_field       USING 'KONP-KONWA(01)'
                                      it_price-konwa.
        PERFORM bdc_field       USING 'KONP-KMEIN(01)'
                                      it_price-kmein.
        PERFORM bdc_field       USING 'RV13A-KRECH(01)'
                                      it_price-krech.
        PERFORM bdc_field       USING 'RV13A-DATAB(01)'
                                      it_price-datab.
        PERFORM bdc_field       USING 'RV13A-DATBI(01)'
                                      it_price-datbi.
               perform bdc_dynpro      using 'SAPMV13A' '1821'.
               perform bdc_field       using 'BDC_CURSOR'
                                             'KOMG-MATNR'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=SICH'.                    "Save the entry
        PERFORM bdc_transaction TABLES i_msgtab USING 'VK11' 'N' 'L'.
    *To fetch the error message from the standard error table
        SELECT  SINGLE * FROM t100 WHERE sprsl = 'E'
                                   AND arbgb = sy-msgid
                                   AND msgnr = sy-msgno.
        g_message = t100-text.
    *subroutine to change the error message for every document number
        PERFORM replace_parameters  USING sy-msgv1
                                          sy-msgv2
                                          sy-msgv3
                                          sy-msgv4
                                CHANGING  g_message.
        WRITE: / 'System variables:'.
        SKIP.
        WRITE: / '        Sy-msgty:', sy-msgty.
        WRITE: / '        Sy-msgid:', sy-msgid.
        WRITE: / '        Sy-msgno:', sy-msgno.
        WRITE: / '        Sy-msgv1:', sy-msgv1.
        WRITE: / '        Sy-msgv2:', sy-msgv2.
        WRITE: / '        Sy-msgv3:', sy-msgv3.
        WRITE: / '        Sy-msgv4:', sy-msgv4.
        SKIP.
        WRITE: / 'Message:'.
        SKIP.
        WRITE: / sy-msgty, g_message.
    *To find out the error in the legacy data if there is anything and pass
    *the document no with error message to the seperate internal table
    *called it_erfind
        IF sy-msgty = 'E'.
          it_erfind-index = it_price-index.
          it_erfind-er_message = g_message.
          APPEND it_erfind.
        ENDIF.
    *Finally we are segregating the error and downloading the error data.
        AT LAST.
    *To segregate the error
          PERFORM segregate_error.
    *To download the error from it_error internal table with err mesg
          PERFORM error_download.
          PERFORM display_message.
        ENDAT.
      ENDLOOP.
               perform close_group.
      CLEAR it_price.
    ENDFORM.                    "fill_data
    *Subrotine to replace the parameters
    FORM replace_parameters USING p_par_1 p_par_2 p_par_3
                                  p_par_4 CHANGING p_message.
    erst mal pruefen, ob numerierte Parameter verwendet wurden
      DO.
        REPLACE '&1' WITH p_par_1 INTO p_message.
        IF sy-subrc <> 0.
          EXIT.
        ENDIF.
      ENDDO.
      DO.
        REPLACE '&2' WITH p_par_2 INTO p_message.
        IF sy-subrc <> 0.
          EXIT.
        ENDIF.
      ENDDO.
      DO.
        REPLACE '&3' WITH p_par_3 INTO p_message.
        IF sy-subrc <> 0.
          EXIT.
        ENDIF.
      ENDDO.
      DO.
        REPLACE '&4' WITH p_par_4 INTO p_message.
        IF sy-subrc <> 0.
          EXIT.
        ENDIF.
      ENDDO.
    falls keine numerierten Parameter vorh., ersetzen wie gehabt
      REPLACE '&' WITH p_par_1 INTO p_message.
      CONDENSE p_message.
      IF sy-subrc EQ 0.
        REPLACE '&' WITH p_par_2 INTO p_message.
        CONDENSE p_message.
        IF sy-subrc EQ 0.
          REPLACE '&' WITH p_par_3 INTO p_message.
          CONDENSE p_message.
          IF sy-subrc EQ 0.
            REPLACE '&' WITH p_par_4 INTO p_message.
            CONDENSE p_message.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDFORM.                    "REPLACE_PARAMETERS
    *Subroutine to segregate the error data from the legacy data
    FORM segregate_error.
      LOOP AT it_erfind.
        LOOP AT it_price WHERE index = it_erfind-index.
          MOVE-CORRESPONDING it_price TO it_error.
          it_error-er_message = it_erfind-er_message.
          APPEND it_error.
        ENDLOOP.
      ENDLOOP.
    ENDFORM.                    "segregate_error
    *Subroutine to download the error data from the it_error table.
    FORM error_download.
      IF it_error[] IS NOT INITIAL.
        CALL FUNCTION 'WS_DOWNLOAD'
          EXPORTING
            codepage = 'IBM'
            filename = v_error_filename
            filetype = 'DAT'
          TABLES
            data_tab = it_error.
      ENDIF.
    ENDFORM.                    "error_download
           Start new screen                                              *
    FORM bdc_dynpro USING program dynpro.
      CLEAR bdcdata.
      bdcdata-program  = program.
      bdcdata-dynpro   = dynpro.
      bdcdata-dynbegin = 'X'.
      APPEND bdcdata.
    ENDFORM.                    "BDC_DYNPRO
           Insert field                                                  *
    FORM bdc_field USING fnam fval.
             IF FVAL <> NODATA.
      CLEAR bdcdata.
      bdcdata-fnam = fnam.
      bdcdata-fval = fval.
      APPEND bdcdata.
             ENDIF.
    ENDFORM.                    "BDC_FIELD
    *&      Form  bdc_transaction
          text
         -->MESSTAB    text
         -->TCODE      text
         -->CTUMODE    text
         -->CUPDATE    text
    FORM bdc_transaction TABLES messtab USING  tcode ctumode cupdate .
      CALL TRANSACTION tcode USING bdcdata
                            MODE   ctumode
                            UPDATE cupdate
                            MESSAGES INTO messtab.
      REFRESH bdcdata.
      CLEAR   bdcdata.
    ENDFORM.                    " bdc_transaction
    Uploading data file to internal table.                           *
    FORM upload_data.
      CALL FUNCTION 'WS_UPLOAD'
          EXPORTING
             filename                      = p_file
                        CODEPAGE                      = 'IBM '
             filetype                      = 'DAT'
          TABLES
              data_tab                      = it_price
          EXCEPTIONS
             conversion_error              = 1
             invalid_table_width           = 2
             invalid_type                  = 3
             no_batch                      = 4
             unknown_error                 = 5
             gui_refuse_filetransfer       = 6
             OTHERS                        = 7.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
        WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
    ENDFORM.                    "upload_data
    *&      Form  display_message
    FORM display_message .
      IF it_error[] IS INITIAL.
        MESSAGE i019(zmsg).   "Success
      ELSE.
        MESSAGE e020(zmsg).   "Failed
      ENDIF.
    ENDFORM.                    " display_message
    *&      Form  get_filename
          text
    -->  p1        text
    <--  p2        text
    FORM get_filename .
      CALL FUNCTION 'F4_FILENAME'
       EXPORTING
         program_name        = syst-cprog
         dynpro_number       = syst-dynnr
          FIELD_NAME          = p_file
       IMPORTING
         file_name           = p_file .
      IF sy-subrc NE 0  .
        WRITE : / 'Enter File Name'.
      ENDIF.
    ENDFORM.                    " get_filename
    *&      Form  make_file_name
    FORM make_file_name .
      WRITE sy-datum TO date  MM/DD/YYYY.
      WRITE sy-uzeit TO time  USING EDIT MASK ' __ __ __'.
      CONCATENATE text-002 date time '.txt'
             INTO v_error_filename.
    ENDFORM.                    " make_file_name
    regards
    prabhu

  • Data not updating for raw materials only in cube level

    HI all gurus,
    we have flow like ods1->ods2->cube1,cube2 and cube3.
    In ods1 we mapped ZMATERIAL WITH OMATERIAL.
    In ods2 we mapped zmaterial with zmaterial directly.
    In cube we mapped zmaterial with zmaterial only but also we added 0mat_type in update rules of cube. i.e.we mapped in update rules  0mat_type is master data attribute of zmaterial.
    But the problem is ods2 is mapped to cube1,cub2 and cube3 parllelly.
    But the data is not populating to cube2 and cube3 only for rawmaterials i.e 0mat_type is having 15 material types(finished ,semi finishe and rawmaterials) only 4 raw materials are not showing any data for these two cubes but for one cube1 it is showing data for all 15 material types. (including raw materials)
    what could be the problem.
    I checked the Attribute change run.
    I checked the data in masterdata also zmaterial and 0material.(data is available upto date).
    Please help and i will definitely assingn the points.
    It's very urgent becauz total my development work is stopped.
    Thanks & regards,
    Kumar.

    Hi,
    Check the material values in cube2 and cube 3 for records not having 0mat_type and then using that material check the material master data table to confirm whether mat_type is present for those materials or not.
    Also, if you have written any start routine in update rules for cube 2 and 3 then check that too.
    PB

  • Need more Info about "Load transactional data when master data not loaded"

    Hi,
    Can you please explain me this option in the infopackage " Load transactional data when master data is not loaded"....
    Say i load a transactional data record which has a material no. AAAXX.
    In the fact table, the material no. is replaced with the corresp. DIM ID.
    Now, assume that there is no entry for this Material no.
    AAAXX in the master data table...so no DIM ID for it..
    How is it then stored in the fact table ?
    Hope i have managed to explain the scenario..
    Thanks in advance,
    Punkuj

    Hello Punkuj K,
    How r u ?
    No, if the entry for that Material Number "AAAXX" is not there in the Master Data then it will create a SIDs & DIMs ID for that & Transaction Data will be loaded.
    Use
    Choose this indicator if you want to always update the data, even if no master data for the navigation attributes of the loaded records exists. The master data is generated from the loaded transaction data. The system draws SIDs. You can subsequently load the master data.
    Dependencies
    The texts, attributes, and hierarchies are not recognized by the system. Load the texts / attributes / hierarchies for the corresponding InfoObjects separately.
    This function corresponds to the update. Possible errors when reading the master data into the update rules are not associated with this indicator.
    Recommendation
    We recommended loading the master data into the productive systems in advance. Select this indicator especially in test systems.
    Best Regards....
    Sankar Kumar
    +91 98403 47141

  • Master Data - Flexible update

    We have C1 master data, Different attributes under this.
          the source for this char is coming from different info pkgs.
          also Transactional data.
      We r loading master data from r/3 into char1 using flexible update mode.
      When looked at the master table using Se11, can view all the data correctly.
    But when view the contents of the C1 master data from RSA1 (Maintain master data ), observed that one of the attribute is not loaded.
    Any idea what could be the reason. 
    any way how to identify how this data is loaded, either master load or transaction data.
    Also how to correct this data.

    look into the transfer rules of the master data infoobject, check where the attribute is getting loaded, else check in the transfer rules of the transaction data infosource if it is marked to get loaded from there.
    proceed accordingly. if u dont find it in both the rules, then it needs to be configured again taking data from available data source.
    **revert on doubts. reward if helpful**

  • Master Data Full Update

    Hi All,
    If I load Master Data everyday (Full Update), does the data overwrites the previous day data or adds the new data to the existing one?

    Hi S.D
      How are you? Yes, its master data always overwrites the data for which the keys match. So you need not worry about any duplicates. Infact, even when we do a delta load for our master data, we do a full load once a week to ensure that we did not lose any data with deltas.

Maybe you are looking for