Field not getting updated in BDC while running in background

Hi Friends,
I'm executing a BDC transaction to update the Alternate Tax Classification (VBAK_TAXK1) field in Sales Order. I'm passing value 1 to the field and then saving it directly. While running the BDC in background, the field is not getting updated. On the other hand i checked it running in foreground, the field got updated without any error message.
Can anybody help me advicing why the field is not getting updated in background?
Thanks,
Bestin

Hi ,
Check the the log if you are using a session method and if call transaction then capture the messages for the same,
Because in the foreground the BDC will update the records even if there is a warning message nut in background it will not update. So check the data which you are inserting and try avoid the warning messages also so that it can run smoothly in backfround.
Thanks & Regards
Jyo

Similar Messages

  • Custom fields not getting updated in Mass Maintenance-MM17

    Hi,
    I have created a custom field in MARC table and the data is getting updated to the MARC table through MM01/MM02 but it is not getting updated by MM17.  I have checked the notes 44410, 576160, 414020 and 116311.  I have done the following changes as per the sap notes.
    1. Created a custom segment ZE1MARCM by copying the standard segment E1MARCM and added the custom field in that  
        segment.
    2. I have extended the IDOC 'MATMAS03' and added the custom segment ZE1MARCM to E1MARAM.
    3. Created a new entry in we82 and provided the extension type 'ZMATMAS03' and release '701'.
    4. Adjusted the partner profile in we20 for matmas with port and providing the extension idoc type.
    5. Added the custom field in the table MASSFLDLST.
    6. Implemented the code in BADI 'MG_MASS_NEWSEG' and exits 'EXIT_SAPLMV01_002' , 'EXIT_SAPLMV02_002' as per the 
        sap notes.
    The custom field is not getting updated through mass maintenance.  Please let me know if i have missed anything?
    Thanks,
    Geeta

    I had this same question several years ago. Please check my answer at Initialize MARC Custom Fields Using MM17 Does Not Work

  • Quantity field not getting update in PCA document for Goods Receipt

    We have the Purchase Account activated for our company code.
    For movement type 101 (Goods Receipt), I am getting the quantity field updated for GR/IR account and Stock Account (B/S item).
    But the quantity field is not getting updated for the "Purchase Account" and the "other offsetting PL A/C).
    Please advice whether I am missing something.
    Regards
    B.Mohanty

    Hi Aravind,
    Check SAP notes  1063198 and 1117587.
    FAGLL03 display quantity which is updated in FAGLFLEXA, BSEG is not
    relevant in this case. This is clearly explained in the note 1063198.
    The quantity posts through to FI on the 'goods receipt' items, but not on the
    'invoice receipt' items.
    In the FI normally the Quantity is not a 'real' important field, as it
    is more related to the MM area.
    But in the old 'Profit Center Accounting' and the old' Special Ledger'
    the field has been important.
    As the same logic of these areas to 'store' the Quantity is also used
    in the NewG/L the field get only filled in the line, where it make
    'sense' from our point of view, because only in the 'goods receipt'
    lines a 'real' Quantity is posted to the system.
    So as before in the PCA and SL, now also in the NewG/L the Quantity is
    filled in the correct and important lines and postings.
    In the BSEG ('old document segment table') the field is filled 'just'
    as it is send to the FI, but this is not completely correct from the
    business point of view.
    This can also lead to issues with the reporting and summation to this
    field. So with creating the new logic in the NewG/L the 'correct'
    standard of the 'writing' for the Quantity has also been taken over.
    So in the end, the update and display is correct according  SAP standard behavior.
    Actually,Quantities within G/L are never reliable,
    because the purpose of FI is a view on the data according to amount
    but not according to quantity.
    In the FI normally the Quantity is not a 'real' important field, as it
    is more related to the MM area.
    I hope I could be of assistance.
    Regards,
    Fernando

  • REGUP Table Withholding tax field not getting updated

    hi friends,
                  from a specifc date with holdiing tax is not getting updated in REGUP-QBSHH field, so in payment advice its not getting displayed. can any one help me wat could be the problem for this
    thanks
    nagaraj

    hi amir,
            i dont have test case for that. till 28th of the last month the field has been updated and after that till now all the entries in that field is showing zero. but when we check in FB03. i can see the with holding tax amount. can u tell me how this table is getting updated
    thanks

  • Fields not getting updated in FBL3N and FBL5N

    Hi
    I have introduced new fields like material number, quantity sales document number, etc in through FBL3N --> Settings --> List special fields.
    Also i added one more field in 'sort key' as sales document number. I updated sort key in customer master and GL master (i.e. reconcliation account of customer A/c)
    But inspite of doing this, i can see those fields after change layout. But these fields are still empty. I do not know why its empty.
    When i changed sort key to sales document number, sales delivery number is coming instead of sales document number in assignment field.
    Please help

    Dear Meenakshi,
    Even though there are various fields available in FBL5N or FBL3N, all the fields are not updated for all the transactions. Based on transaction to transaction, fields get updated and mostly these are SAP standards. If you want certain fields, you need to develop Z reports accordingly.
    For example when GR is posted, system does not update PO number in Purchase order field. But alternatively it is updated in REFKEY1 field. Similarly when billing is done, it does not update material code in FI tables so it does not appear in FBL5N.
    Regarding Sort key, check with your SD consultant, what copy control it is used. In finance, assignment field is updated based on copy control used in SD.
    Regards,
    Niraj

  • BAPI_MATERIAL_SAVEDATA-Tax fields not getting updated.

    Hi Everyone,
        I'm trying to create material through this BAPI -"BAPI_MATERIAL_SAVEDATA"
    I'm also passing the tax information related to it in the TAXCLASSIFICATIONS table.I'm populating the fields in the format as I have shown below in the code.Everything is working fine ,material is getting created except the tax information in the material not being affected against what I'm passing.I'm not sure though what does the tax_ind field does in the TAXCLASSIFICATIONS  table.
    Specifically,The country CA has different type codes mentioned as CATX1,CATX2,CATX3.But the values are getting updated only for the CATX1 category code.So after the creation, All the countries have their taxes classified except and CATX2 and CATX3 remain blank-no entry at all.
    Kindly let me know if you have a clue regarding this.
    FUNCTION Z_CREATE_MATERIAL.
    *"*"Local Interface:
    *"  IMPORTING
    *"     VALUE(MATERIAL) TYPE  MARA-MATNR OPTIONAL
    *"     VALUE(MATDESC) TYPE  MAKT-MAKTX OPTIONAL
    *"     VALUE(KBETR) TYPE  BDCDATA-FVAL OPTIONAL
    *"     VALUE(MATCOST) TYPE  STPRS_BAPI OPTIONAL
    *"  EXPORTING
    *"     VALUE(MESSAGE) TYPE  STRING
      DATA: BAPI_HEAD   LIKE BAPIMATHEAD,
            BAPI_MAKT   LIKE BAPI_MAKT,    "Material Description
            BAPI_MARA1  LIKE BAPI_MARA,    "Client Data
            BAPI_MARAX  LIKE BAPI_MARAX,
            BAPI_MARC1  LIKE BAPI_MARC,    "Plant View
            BAPI_MARCX  LIKE BAPI_MARCX,
            BAPI_MBEW1  LIKE BAPI_MBEW,    "Accounting View
            BAPI_MBEWX  LIKE BAPI_MBEWX,
            BAPI_RETURN LIKE BAPIRET2,
            bapi_sales like BAPI_MVKE,
            bapi_salesx like BAPI_MVKEX,
            bapi_mard like BAPI_mard,
            bapi_mardx like BAPI_mardx.
      DATA: BEGIN OF INT_MAKT OCCURS 100.
              INCLUDE STRUCTURE BAPI_MAKT.
      DATA: END OF INT_MAKT.
      DATA: BEGIN OF L_T_MARM OCCURS 100.
              INCLUDE STRUCTURE   BAPI_MARM.
      DATA: END OF L_T_MARM.
      DATA: BEGIN OF L_T_MARMx OCCURS 100.
              INCLUDE STRUCTURE   BAPI_MARMx.
      DATA: END OF L_T_MARMx.
      DATA: BEGIN OF L_T_tax OCCURS 100.
              INCLUDE STRUCTURE   BAPI_MLAN.
      DATA: END OF L_T_tax.
    *for plant 3800
    * Header
      BAPI_HEAD-MATERIAL        = MATERIAL.
      BAPI_HEAD-IND_SECTOR      = '1'.
      BAPI_HEAD-MATL_TYPE       = 'HAWA'.
      BAPI_HEAD-BASIC_VIEW      = 'X'.
      bapi_head-SALES_VIEW = 'X'.
      bapi_head-PURCHASE_VIEW = 'X'.
      BAPI_HEAD-ACCOUNT_VIEW    = 'X'.
      bapi_head-cost_view = 'X'.
      bapi_head-mrp_view = 'X'.
    * Client Data - Basic
      BAPI_MARA1-BASE_UOM       = 'EA'.
      BAPI_MARA1-UNIT_OF_WT     = 'LB'.
      BAPI_MARA1-ALLWD_VOL = '10'.
      BAPI_MARA1-PACK_VO_UN = 'CCM'.
      bapi_marax-ALLWD_VOL = 'X'.
      bapi_marax-PACK_VO_UN = 'X'.
      BAPI_MARA1-DIVISION       = '00'.
      BAPI_MARA1-NET_WEIGHT     = '1'.
      BAPI_MARA1-MATL_GROUP = '002'.
      BAPI_MARa1-TRANS_GRP = '0001'.
      bapi_mara1-prod_hier = '001700010000000110'.
      BAPI_MARAX-trans_grp    = 'X'.
      bapi_marax-prod_hier = 'X'.
      BAPI_MARAX-BASE_UOM   = 'X'.
      BAPI_MARAX-UNIT_OF_WT   = 'X'.
      BAPI_MARAX-DIVISION    = 'X'.
      BAPI_MARAX-MATL_GROUP    = 'X'.
      BAPI_MARAX-NET_WEIGHT    = 'X'.
      bapi_mara1-ITEM_CAT = 'NORM'.
      BAPI_MARAX-item_cat    = 'X'.
    *Units of measure - Gross weight populate
      L_T_MARM-ALT_UNIT = 'EA'.
      L_T_MARM-ALT_UNIT_ISO = 'EA'.
      L_T_MARM-GROSS_WT = '1'.
      L_T_MARM-UNIT_OF_WT = 'LB'.
      L_T_MARM-VOLUME = '100'.
      L_T_MARM-VOLUMEUNIT = 'CCM'.
      L_T_MARMX-VOLUME = 'X'.
      L_T_MARMX-VOLUMEUNIT = 'X'.
      APPEND L_T_MARM.
      L_T_MARMX-UNIT_OF_WT = 'X'.
      L_T_MARMX-GROSS_WT = 'X'.
      L_T_MARMX-ALT_UNIT = 'EA'.
      L_T_MARMX-ALT_UNIT_ISO = 'EA'.
      APPEND L_T_MARMX.
    *Tax Classification
      L_T_tax-DEPCOUNTRY = 'US'.
      L_T_tax-DEPCOUNTRY_ISO = 'US'.
      L_T_tax-TAX_TYPE_1 = 'UTXJ'.
      L_T_tax-TAXCLASS_1 = '1'.
       append l_t_tax.
      L_T_tax-DEPCOUNTRY = 'DE'.
      L_T_tax-DEPCOUNTRY_ISO = 'DE'.
      L_T_tax-TAX_TYPE_1 = 'MWST'.
      L_T_tax-TAXCLASS_1 = '1'.
      append l_t_tax.
      L_T_tax-DEPCOUNTRY = 'CA'.
      L_T_tax-DEPCOUNTRY_ISO = 'CA'.
      L_T_tax-TAX_TYPE_1 = 'CTX1'.
      L_T_tax-TAXCLASS_1 = '0'.
      append l_t_tax.
      L_T_tax-DEPCOUNTRY = 'CA'.
      L_T_tax-DEPCOUNTRY_ISO = 'CA'.
      L_T_tax-TAX_TYPE_1 = 'CTX2'.
      L_T_tax-TAXCLASS_1 = '0'.
       append l_t_tax.
      L_T_tax-DEPCOUNTRY = 'CA'.
      L_T_tax-DEPCOUNTRY_ISO = 'CA'.
      L_T_tax-TAX_TYPE_1 = 'CTX3'.
      L_T_tax-TAXCLASS_1 = '0'.
        append l_t_tax.
      L_T_tax-DEPCOUNTRY = 'AU'.
      L_T_tax-DEPCOUNTRY_ISO = 'AU'.
      L_T_tax-TAX_TYPE_1 = 'ATX1'.
      L_T_tax-TAXCLASS_1 = '0'.
       append l_t_tax.
      L_T_tax-DEPCOUNTRY = 'NZ'.
      L_T_tax-DEPCOUNTRY_ISO = 'NZ'.
      L_T_tax-TAX_TYPE_1 = 'NZTX'.
      L_T_tax-TAXCLASS_1 = '0'.
       append l_t_tax.
    * Material Description
      REFRESH INT_MAKT.
      INT_MAKT-LANGU           = 'EN'.
      INT_MAKT-MATL_DESC       = MATDESC.
      APPEND INT_MAKT.
    * Plant - Purchasing
      BAPI_MARC1-PLANT      = '3800'.
      BAPI_MARC1-PUR_GROUP  = '100'.
      BAPI_MARCX-PLANT      = '3800'.
      BAPI_MARC1-ISS_ST_LOC = '0001'.
      BAPI_MARC1-SLOC_EXPRC = '0001'.
      BAPI_MARCx-PUR_GROUP      = 'X'.
      BAPI_MARCX-ISS_ST_LOC = 'X'.
      BAPI_MARCX-SLOC_EXPRC = 'X'.
      BAPI_MARC1-LOADINGGRP = '0002'.
      BAPI_MARCx-LOADINGGRP = 'X'.
      BAPI_MARC1-PLND_DELRY = '1'.
      BAPI_MARC1-MRP_TYPE = 'PD'.
      BAPI_MARC1-MRP_CTRLER = '001'.
      BAPI_MARC1-SM_KEY = '001'.
      BAPI_MARC1-LOTSIZEKEY = 'TB'.
      BAPI_MARC1-PROC_TYPE = 'F'.
      BAPI_MARCx-PLND_DELRY      = 'X'.
      BAPI_MARCx-MRP_TYPE      = 'X'.
      BAPI_MARCx-MRP_CTRLER      = 'X'.
      BAPI_MARCx-SM_KEY      = 'X'.
      BAPI_MARCx-LOTSIZEKEY      = 'X'.
      BAPI_MARCx-proc_type = 'X'.
      BAPI_MARC1-MRP_GROUP = '0030'.
      BAPI_MARCx-MRP_GROUP = 'X'.
    *Sales View
      bapi_sales-SALES_ORG = '3020'.
      bapi_sales-DISTR_CHAN = '14'.
      bapi_sales-DELYG_PLNT =  '3800'.
      BAPI_SALES-ITEM_CAT = 'NORM'.
      bapi_salesx-ITEM_CAT = 'X'.
      bapi_salesx-Delyg_plnt = 'X'.
      bapi_salesx-sales_org = '3020'.
      bapi_salesx-DISTR_CHAN = '14'.
      bapi_sales-MATL_STATS = '1'.
    bapi_salesx-MATL_STATS = 'X'.
    * Accounting
      BAPI_MBEW1-VAL_AREA   = '3800'.
      BAPI_MBEW1-VAL_CLASS   = '3100'.
      BAPI_MBEW1-STD_PRICE  = matcost.
      BAPI_MBEW1-PRICE_CTRL = 'V'.
      bapi_mbew1-PRICE_UNIT = '1'.
      BAPI_MBEWX-VAL_AREA   = '3800'.
      BAPI_MBEWX-PRICE_CTRL = 'X'.
      BAPI_MBEWx-STD_PRICE  = 'X'.
      BAPI_MBEWX-VAL_CLASS   = 'X'.
      bapi_mbewx-price_unit = 'X'.
      bapi_mard-plant = '3800'.
      bapi_mard-stge_loc = '0001'.
      bapi_mardx-plant = '3800'.
      bapi_mardx-stge_loc = '0001'.
      CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
        EXPORTING
          HEADDATA                   = BAPI_HEAD
         CLIENTDATA                 = BAPI_MARA1
         CLIENTDATAX                = BAPI_MARAX
         PLANTDATA                  = BAPI_MARC1
         PLANTDATAX                 = BAPI_MARCX
    *   FORECASTPARAMETERS         =
    *   FORECASTPARAMETERSX        =
    *   PLANNINGDATA               =
    *   PLANNINGDATAX              =
       STORAGELOCATIONDATA        = bapi_mard
       STORAGELOCATIONDATAX       = bapi_mardx
         VALUATIONDATA              = BAPI_MBEW1
         VALUATIONDATAX             = BAPI_MBEWX
    *   WAREHOUSENUMBERDATA        =
    *   WAREHOUSENUMBERDATAX       =
         SALESDATA                  = bapi_sales
         SALESDATAX                 = bapi_salesx
    *   STORAGETYPEDATA            =
    *   STORAGETYPEDATAX           =
    *   FLAG_ONLINE                = ' '
    *   FLAG_CAD_CALL              = ' '
    *   NO_DEQUEUE                 = ' '
    *   NO_ROLLBACK_WORK           = ' '
       IMPORTING
         RETURN                     = BAPI_RETURN
       TABLES
         MATERIALDESCRIPTION        = INT_MAKT
       UNITSOFMEASURE             = L_T_MARM
       UNITSOFMEASUREX            = L_T_MARMX
    *   INTERNATIONALARTNOS        =
    *   MATERIALLONGTEXT           =
       TAXCLASSIFICATIONS         = l_t_tax
    *   RETURNMESSAGES             =
    *   PRTDATA                    =
    *   PRTDATAX                   =
    *   EXTENSIONIN                =
    *   EXTENSIONINX               =
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    Any suggestions on this one would really mean a lott of help to me.
    Thanks a lot,
    Archies!!

    Hi James ,
    I' m not sure but could you please try like this
    L_T_tax-DEPCOUNTRY = 'CA'.
      L_T_tax-DEPCOUNTRY_ISO = 'CA'.
      L_T_tax-TAX_TYPE_1 = 'CTX1'.
      L_T_tax-TAXCLASS_1 = '0'.
       L_T_tax-TAX_TYPE_2 = 'CTX2'.
      L_T_tax-TAXCLASS_2 = '0'.
      append l_t_tax.
    Hope this helps
    Caglar

  • Fields not getting updated in the database through BAPI enhancement

    Hi Experts,
    I have added 4 custom fields in the transaction FB60. The fields are getting displayed in vendor line item.
    I have to fill these fields from an inbound idoc which uses the BAPI_ACC_DOCUMENT_POST bapi. I have implemented the BADI BADI_ACC_DOCUMENT to pass my custom fields to the bapi and it is processing correctly by adding the custom field values to the extension table that is getting passed to the standard program of the BAPI from the BADI.
    But I think, I have missed to append my fields in one of the standard structures. I have added the fields in BSEG, CI_COBL( which is getting called in BAPICOBL_CI, ACCIT).
    Can anybody tell me which other standard structure I should add my custom fields so that it functions properly and gets added to the BSEG table.
    Regards,
    Sangeeta.

    Solved on own.

  • Screen Fields Not getting Updated with DYNP_VALUES_UPDATE

    Hi All,
    I am using FM DYNP_VALUES_READ to read the screen field values and then modifying those values and passing the modified table to DYNP_VALUES_UPDATE. But the problem is screen fields are not populated with these values . The values I wish to populate are footer values . I am using OO ALV for this wherein I am handling an event for filter of records and accordingly I need to modify my footer. Any Suggestions??
    *&      Form  footer
          Caslculate Total items, number of hits/Miss and percent MSP
    -->  p1        text
    <--  p2        text
    FORM footer .
      CLEAR : io_totitems,
              io_tothit,
              io_totmiss,
              io_permiss.
    IF NOT l_flag EQ 1.
    Get total items
      DESCRIBE TABLE i_outdata LINES io_totitems.
      LOOP AT i_outdata INTO wa_outdata.
      calculate number of hits
        IF wa_outdata-hit_miss  = 'HIT'.
          io_tothit = io_tothit + 1.
        ENDIF.
      calculate number of Miss
        IF wa_outdata-hit_miss  = 'MISS'.
          io_totmiss = io_totmiss + 1.
        ENDIF.
        CLEAR wa_outdata.
      ENDLOOP.
    calculate percent MSP
      io_permiss = ( ( io_totitems - io_totmiss ) / io_totitems ) * 100 .
      IF l_flag EQ 1.
        wa_dynpread-fieldname = 'IO_TOTITEMS'.
        APPEND wa_dynpread TO t_dynpread.
        wa_dynpread-fieldname = 'IO_TOTHIT'.
        APPEND wa_dynpread TO t_dynpread.
        wa_dynpread-fieldname = 'IO_TOTMISS'.
        APPEND wa_dynpread TO t_dynpread.
        wa_dynpread-fieldname = 'IO_PERMISS'.
        APPEND wa_dynpread TO t_dynpread.
        CLEAR wa_dynpread.
        d020s-prog = sy-repid.
        d020s-dnum = sy-dynnr.
        CALL FUNCTION 'DYNP_VALUES_READ'
                EXPORTING
                   dyname               = d020s-prog
                   dynumb               = d020s-dnum
                   translate_to_upper   = 'X'
              REQUEST              = ' '
                TABLES
                   dynpfields           = t_dynpread.
        MOVE io_totitems TO io_totitem.
        CONDENSE io_totitem NO-GAPS.
        MOVE io_tothit TO io_tothits.
        CONDENSE io_tothits NO-GAPS.
        MOVE io_totmiss TO io_totmis.
        CONDENSE io_totmis NO-GAPS.
        MOVE io_permiss TO io_permis.
        CONDENSE io_permis NO-GAPS.
        LOOP AT t_dynpread INTO wa_dynpread.
          CASE: wa_dynpread-fieldname.
            WHEN 'IO_TOTITEMS'.
              wa_dynpread-fieldvalue = io_totitem .
              MODIFY t_dynpread FROM wa_dynpread.
            WHEN 'IO_TOTHIT'.
              wa_dynpread-fieldvalue = io_tothits.
              MODIFY t_dynpread FROM wa_dynpread.
            WHEN 'IO_TOTMISS'.
              wa_dynpread-fieldvalue = io_totmis.
              MODIFY t_dynpread FROM wa_dynpread.
            WHEN 'IO_PERMISS'.
              wa_dynpread-fieldvalue =  io_permis .
              MODIFY t_dynpread FROM wa_dynpread.
          ENDCASE.
          CLEAR wa_dynpread.
        ENDLOOP.
        CALL FUNCTION 'DYNP_VALUES_UPDATE'
          EXPORTING
            dyname               = d020s-prog
            dynumb               = d020s-dnum
          TABLES
            dynpfields           = t_dynpread
          EXCEPTIONS
            invalid_abapworkarea = 1
            invalid_dynprofield  = 2
            invalid_dynproname   = 3
            invalid_dynpronummer = 4
            invalid_request      = 5
            no_fielddescription  = 6
            undefind_error       = 7
            OTHERS               = 8.
        IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        ENDIF.
      ENDIF.
    Get all fotter details in a internal table
    this is used to download footer in Excel
      wa_footer-fldname = 'Total Items '.
      wa_footer-value = io_totitems.
      APPEND wa_footer TO i_footer.
      wa_footer-fldname = 'Number of HIT'.
      wa_footer-value = io_tothit.
      APPEND wa_footer TO i_footer.
      wa_footer-fldname = 'Number of MISS'.
      wa_footer-value = io_totmiss.
      APPEND wa_footer TO i_footer.
      wa_footer-fldname = 'Percentage MISS '.
      wa_footer-value = io_permiss.
      APPEND wa_footer TO i_footer.
      CLEAR wa_footer.
    ENDFORM.                    " footer

    data: t_dynfields1 type table of dynpread with header line.
    CALL FUNCTION 'DYNP_VALUES_READ'
    EXPORTING
    dyname = d020s-prog
    dynumb = d020s-dnum
    translate_to_upper = 'X'
    REQUEST = ' '
    TABLES
    dynpfields =  t_dynfields1.
    <b>read table t_dynfields1 index 1</b> “ I hope this is missing
    I will be selecting from a list .
    Because once the value is read we need to update the screen field with that value .
    Here the selected value will be in the first place
    Now
    Your operation is to populate the fields with some variables .
    In the same when I do this there is only one value then
    Im expecting only one entry here …
    LOOP AT t_dynpread INTO wa_dynpread.
    CASE: wa_dynpread-fieldname.
    WHEN 'IO_TOTITEMS'.
    wa_dynpread-fieldvalue = io_totitem .
    MODIFY t_dynpread FROM wa_dynpread.
    WHEN 'IO_TOTHIT'.
    wa_dynpread-fieldvalue = io_tothits.
    MODIFY t_dynpread FROM wa_dynpread.
    WHEN 'IO_TOTMISS'.
    wa_dynpread-fieldvalue = io_totmis.
    MODIFY t_dynpread FROM wa_dynpread.
    WHEN 'IO_PERMISS'.
    wa_dynpread-fieldvalue = io_permis .
    MODIFY t_dynpread FROM wa_dynpread.
    ENDCASE.
    CLEAR wa_dynpread.
    ENDLOOP. */
    Comment this for a while and
    Change the code as
    t_dynfields1-fieldname = ' '. "<--- header name
    t_dynfields1-fieldvalue = ' '."<----val  
    append t_dynfields1.
    t_dynfields1-fieldname = ' '.
    t_dynfields1-fieldvalue = ' '.
    append t_dynfields1.
    t_dynfields1-fieldname = ' '.
    t_dynfields1-fieldvalue = ' '.
    append t_dynfields1.
    And check .
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
    EXPORTING
    dyname = d020s-prog
    dynumb = d020s-dnum
    TABLES
    dynpfields = t_dynfields1.
    regards,
    vijay

  • Addtional tab CI field not getting updated in table

    Hi all,
    I am using cProjects 4.0 system.
    I had implemented addtional custom tab to display project custom include fields. In CI include of dpr_project table i added custom fields.
    Then created new webdynpro component and in implemented interface tab in had implemented DPR_CUST_EXT_INTF.  In view i displayed the 2 custom fields i added. In cProjects SPRO, i had given my component name for addtional tab. When I run the application it is showing those fields i added in addtional tab. While saving it is not updating custom field. Please let me know what needs to be done.
    Thanks & Regards,
    Karthick S

    Hi,
    For adding custom fields from CI_* includes, I advise you to use available feature in SAP standard 'field groups for customer fields' under : SPRO -> Collaboration Projects -> Global Enhancements to Project Elements.
    This is the easiest way to add custom tabs & fields without webdynpro development. All standard functions are supported: field control, save, BADI...
    BR
    Matthias

  • Cost center field not getting updated to the second level dso

    Hi Experts,
    Data is going from one DSO to other high level DSO where in the source DSO there is cost center filled for a Purchase order but it is not in the target DSO. Target DSO fetches data from 5 DSO's and this is one of them.
    Please suggest.
    Thanks
    Sudha

    Hi Sudha,
    As you say that the load from source DSO to Target DSO is the final load, so question of overwrite does not come into picture.The only point which I feel is that the data might be getting resticted somewhere...
    Is there any routine in the transformation for that field available which will be restricting the load from the source DSO to the target DSO. Is there any start routine available..Please check all these things...
    Hope it Helps,
    Thanks,
    Amit Kr.

  • Fields not getting updated in VA01.

    I am writting code in exit EXIT_SAPLVEDA_001.I am passing billing block as ZM from the IDOC,according to the following condition
    Edited by: smriti singh on Apr 30, 2008 11:28 AM

    After that you have to append are insert it

  • Matlab workspace not getting updated while labview mex file is running

    Hi,
    Let me start from the overview of the system for better understanding.
    The system is to acquire data from a DAQ6070e using labview 7.1 . this data is then to be used in matlab for processing. All this needs to happen in real time hence the data is to be acquired from labview and outputted into matlab in real time.
    in order to do this we generated the labview and the matlab codes seperately. After days of hard work we managed to import the labview vi into matlab using a math interface toolkit, but now have run into another interesting problem.
    the workspace in matlab is not getting updated during the time the labview vi is running inside matlab. it only updates after the vi has run . for example if i need to monitor the system for 300 seconds then ideally the labview vi should output the samples for each acquisition and output it to matlab, what actually is happening is that the labview keeps running for 300 seconds without outputting any data during those 300 seconds and only outputs the last set of acquisition values at the end of the 300 seconds. Which beats the purpose of the whole program.
    Kindly help
    Regards
    Manuj

    Thanks Mate,
    What you said about "MEX file will not be able to "store" data between runs" ,i realised in the morning. as a result i dont think your suggestion of for loop will also be effective as labview mex file will not acquire data during matalb code execution and vice versa.
    Hence i have decided to do it the other way...we will now try to run the matlab code in labview.
    this leads to other problem
    As this is a real time operation i need to find out a way of storing the data into computer memory and then reading from it(when i say memory i do not mean writing it to a file and readin from it as that is slow) becasue i think the buffer i am specifying in my AI config is not big enough.
    I was thinking maybe i should use a RT FIFO queue but then i have not been able to find out the difference between buffer memory and fifo memory. ie is buffer memory supposed to be the ram memory or is it the hard disk memory?
    I am posting the vi here for easy understanding
    All help is very much appreciated
    Attachments:
    RT-loop2ver21.vi ‏231 KB

  • Product ID is not getting updated in SC Goods /Service field

    Hi Gurus,
    While creating shopping carts in EBP, we are able to find the Product ID from the Good/Service find option, but when we select the Product ID in the search, it's not getting updated in the SC Goods/Service field.Also when we try to find the Cost center / WBS using find button it's not going to the search area after software upgrade.
    Could you please suggest us why system is behaving like this.
    Thanks
    Sada

    Hi Gurus,
    Any Idea on this.
    Also few of the Product ID's are getting updated from the search help to Goods /Service field of the SC and some are not getting updated. while debug the SC , we are geeting the error message as BBP_SC006, Its relavant to catlog. But we are not transfering the Product from catlog to SC item.
    The error mesage as: Good/Service & does not exist.
    Thanks & regards
    Sada

  • TDS amount not getting updated in the table under the field QBSHB

    Dear Friends,
    The TDS amount entered while booking the vendor invoices through MIRO T-cde, is not getting updated in the table BSEG under the field QBSHB. 
    Kindly let me know the reason for the same and guide me to correct it
    TIA.
    Regards,
    Vincent

    HI Vincent,
    Bseg-QBSHB field is relavent for classic WT.
    I hope you are using the EWT.
    Hence if you post a document through MIRO it will not update
    (but if you post document FB60 it will update but wrongly).
    Reason is Miro document is posted through interface.
    Hence SAP is suggested to not refer the Bseg-QBSHB and etc., fields.
    refer only with_item table.
    Please refer the below replay from SAP
       Please refer the below note .363309
    Please review attached note 363309 for detailed explanation
    BSEG-QBSHB is designed to fill for the classic withholding tax. And
    extended withholding tax information is stored exclusive in table
    WITH_ITEM.
    You can check in table BSEG for the fields and will find that system
    do NOT update field BSEG-QBSHB.
    In your line layout,you define a field BSEG-QBSHB. But actully the field
    of vendor/customer line item is filled with zero from FI. Thus,it shows
    zero in line item display.
    And as note 363309 says,
    "Remove the field which contains the withholding tax information
    from your display variant.
    If you want to display the withholding tax information, double-click on
    the document number and subsequently choose 'Withholding tax' button."
    (BSEG-QSSKZ, BSEG-QSSHB, BSEG-QBSHB) field is not relavent for
    Extended withholding tax and not suppose to use in report FBL1N.
    It basically does not make any sense to use the withholding tax fields
    of the document line items (BSEG-QSSKZ, BSEG-QSSHB, BSEG-QBSHB) with the
    activated extended withholding tax.
    regards
    Madhu M
    Edited by: M Madhu on Jan 31, 2011 1:19 PM

  • Open Sales Order values not getting updated after run RVKRED77 & RVKRED88

    Hiiii,
    In Production Server. We run the reports RVKRED77 & RVKRED88. Credit info structure and and Open Sales Order values not getting updated. In FD32, Status - Sales value it showing '0". At the time of creating Sales Order Dynamic Credit check not happening coz of Tables S066 not updating. Please provide me Solution.
    Best Regards,
    Sridhar . P

    Dear Heagal,
    I followed your suggestions and implemented in the Development and moved the changes in to Quality Server. I tested it thoroughly by creating New Customer and maintained Credit Limit. I come to know that Problem is in all Servers. I made 3 changes.
    1. In Pricing Procedure Sub Total A it was not maintained against Net value. I placed it.
    2. Removed Credit groups for Delivery Type.
    3. In OVA8 i maintained Max. Doc Value :99,999,999.00 before it was with 1.00
    I checked the OMO1 Settings it was Asynchronous. As SAP Notes Suggesting to use Synchronous but here it's a client setting. So, It's Can't possible to change. Changes will affect other Company Codes.
    Tested both in DVP and QTY Dynamic Credit Check is working Perfectly and Status in FD33 Sales Value field getting update.
    If i move these changes in to Production, Will i need to run the reports again or not? How it will affect on Old Cusomer Billing and  Credit Limit data. For few of the Customers the Credit Limit data it was exceeded. Please provide me advice. The issue need to be Solved immediately.
    Best Regards,
    Sridhar

Maybe you are looking for

  • Problem with image MBP "15

    Hi guys, Lately, after being connected with my MBP 15" many hours and with the following open programs, such as Illustrator, Photoshop, Safari, iTunes .. Sometimes it goes without so much.. I get the image of the screen as follows: http://i4.minus.co

  • Mac Pro WiFi broken.

    I am fixing my Dad's Mac Pro with broken WiFi. I have a Gigabyte WB-300D WiFi adapter left over from when I built my PC in 2012. When I slot it in, it doesn't show up as an AirPort card. What can I do to get my WiFi working? I don't really want to bu

  • Help with connecting amplitube Irig

    I cannot get any signal from my Irig...any help??  Im on a macbook pro from 2011

  • Service interface with 2 operations

    I have a service interface with 2 operations... so i have 2 operation mappipngs.. but when i create the interface determaination....it shows only one mapping... should i create 2 interface determaitions????one for each opeartion?? if yes what should

  • Vista Support Question

    Hi! Does DW CS4 support Vista 64-bit. Reason I ask is that it only says certified for Vista in DW system requirements and when I was also looking at PhotoShop system requirements, it stated certified for Vista 32-bit AND 64-bit. I would imagine DW CS