Credit management -ve open delivery values

Hello Masters,
In S077 there are -ve open delivery values. Why -ve values are updated into FD33.
I know how to correct them with RVKRED77,RVKRED88,RVKRED07progrms. My issue is why those are updating?
I saw other forum answers about activating credit checks for return items...etc.
That's not the issue here.
Can any body help me in this issue.
Thanks in Advance

Hi
See these notes to check different points:
SAP Note 396338 - Problems in credit management - analysis help
SAP Note 400311 - RVKRED77: Reorganization credit data, new documentation
SAP Note 425483 - Consulting note collection: Credit checks
SAP Note 18613 - Checklist for Credit Management
I hope this helps you
Regards
Eduardo

Similar Messages

  • Open Delivery value update error in credit management

    Hi
    We have credit management active at delivery level. The value of open deliveries is not getting updated correctly for items with material substitution (material determination). For all other items, its getting updated correctly.
    E.g Let say the credit limit set in FD32 is 10000 and the credit limit used % is 98 and the credit exposure value is 9800.
    Now when I create an order with qty 10 for mat A, it creates a sub item B due to material determination and the value of the item is Rs.1200. In our system, the sub item with TAPS item category is relevant for pricing.
    Then I create a delivery in VL01N and save it.
    Now if i check in FD33, the credit limit used should be 101% and the credit exposure value should be 11000, but its not updating the open delivery value correctly. Its not considering the value of the new delivery.
    However, If I add a normal item (TAN) in the same sales order and create a delivery for that item and save it, its updating the credit exposure based on the value of the normal item in the delivery correctly.
    How to make the system update the open delivery values correctly by taking the items with material determination also into account.??
    Please advise if any specific settings need to be done.
    Regards
    Madhu

    Hi,
    the system updates open values for credit management. These are:
    Open sales order credit value (S066-OEIKW)
    Open delivery credit value (S067-OLIKW)
    Open billing document credit value (S067-OFAKW)
    The system updates the open values in standard SIS structures S066 and S067. Technically, the structures are transparent tables. You can display the contents using transaction SE16 or using table maintenance.
    The S067-OLIKW will give the open delivery credit values credit.Check in you system whether this table is updated with the delivery values for the credit account(customer number)
    RVKRED77 u2013 Reorganize SD credit data
    When updating errors occur, it enables you to reorganize the open credit, delivery and billing document values.
    If the table is not updated run this report in background.
    Regards,
    Saju.S

  • Sales value showing 3000Rs in credit management FD33 as open delivery value

    Sales value showing 3000Rs in credit management FD33 as open delivery value, I want to get the delivery document numbers.

    Hi Friend,
    open delivery value in credit management will updated in SO67 AND this is  information structure.
    Please find the below link to which is similar to your issue
    Open Delivery Value - Credit Mgt
    Thanks
    Dasaradha

  • Open Delivery Value - Credit Mgt

    Hi,
    Is there any way or report to find out what makes up of the open delivery value for a credit acct as seen in FD33 -> Extra -> Sales Value
    thanks!

    hi
    goto V/c2 and specify the customer number here u can get open deliveries,open sales orders.
    open delivery values are those which are delivered but not billed
    it is vc/2
    regards
    prashanth
    Message was edited by:
            prashanth goud<b></b><u></u><u></u><u></u><b></b>
    Message was edited by:
            prashanth goud

  • Open delivery values in S067 table showing as -ve

    Hi All
    Open delivery values in S067 table showing as -ve.
    Could u please explain , what are the reasons!
    Regards
    Raj

    You can check the data in S067 by running the SAP report RVKRED88, this re-evaluates the credit data after update errors. If you find differences between S067 and the result of RVKRED88, you can correct S067 using SAP report RVKRED77. But note as this requires a table lock on various SD tables, you may have to run this report when users are out of the system.

  • Open Delivery value in F.35

    Hi,
    In Credit Master Sheet (F.35), there is a field "Open Delivery value" against which I am getting some value.
    Can somebody give me Idea regarding how to get the delivery document numbers for those deliveries for which this value is coming?
    I have tried VL06O, but no use.
    Thanks in advance,
    Anup

    Hi Anupam,
    I see this question is answered ,could you please explain me what was the solution.I have a similar issue.Quick response would be highly appreciated and rewarded.
    My question "identify on the F.35 screen "how" SAP or "where" SAP extracts the value for "open delivery value" on this screen".
    Kind Regards

  • Open Delivery Value

    Hi,
      Is there any report or table where the Open delivery value is getting stored ( Delivery Number wise )
    My client want a report on Open delivery value , they want to know at the end of the day , how many deliveries are pending and what is the value of that .
    Regards
    Rajesh

    Hi,
    Try VA05, this is the list of sale orders which will give you the delivery status and the order value.
    Regards
    Rasheed

  • Retrive open order and open delivery value x custome

    Hi,
    how can i obtain a list of open order value and open delivery value per customer?
    10x
    bye

    Check the following code which give details of pending orders & values and it can be modified as per ur requirement.
    REPORT  ZPEND_ORDER no standard page heading line-size 255.
    *& Purpose : Details of Sale order having pending deliveries           *
    *&           ( For Rake order handling )                               *
    tables : vbak, vbap, likp, lips, kna1, vbuk, vbpa, vepvg, vbfa, vbup.
    data : pend_qty like  vbap-kwmeng,
           dlv_qty like  vbap-kwmeng,
           ord_qty like vbap-kwmeng.
    data: begin of itab_vbak occurs 0,
          vbeln like vbak-vbeln,           "sales order no
          audat like vbak-audat,           " created date
          auart like vbak-auart,           " Sales Document Type
          vkorg like vbak-vkorg,           "Sales Organization
          vtweg like vbak-vtweg,           " distribution channel
          spart like vbak-spart,           " Division
          vkgrp like vbak-vkgrp,           " Sales group
          vkbur like vbak-vkbur,           " Sales office
          kunnr like vbak-kunnr,           " sold to party
          kunag like vbak-kunnr,           " ship to party
          cust like vbak-kunnr,            " sold to party
          ship like kna1-name1,            " ship to party
          city like kna1-ort01,            " ship to party location
          deliv like likp-vbeln,           " delivery
          matnr like vbap-matnr,
          arktx like vbap-arktx,           " mat description
          kwmeng like vbap-kwmeng,
          kbmeng like vbap-kbmeng,
          fkrel like vbap-matnr,
          vstel like vbap-vstel,
          route like vbap-route,
          chln_no like likp-xabln,
          grn_no like likp-bolnr,
          truck_no like likp-traid,
          dlv_dt like vbfa-erdat,           "dlvy date
          ord_qty like vbap-kwmeng,
          dlvd_qty like vbap-kwmeng,
          pend_qty like vbap-kwmeng,
          kzwi5 like vbap-kzwi5,
          posnr like vbap-posnr,
    end of itab_vbak.
    data  posnr like vbap-posnr.
    *FOR ALV DISPLAY
    type-pools: slis.
    constants: formname_top_of_page type slis_formname value 'TOP_OF_PAGE'.
    *Data Decelararion for alv display
    data: i_fieldtab type slis_t_fieldcat_alv,
          i_heading  type slis_t_listheader,
          i_layout   type slis_layout_alv,
          i_sort     type slis_t_sortinfo_alv,
          i_print    type slis_print_alv,
          i_events   type slis_t_event,
          i_repname  like sy-repid,
          f2code   like sy-ucomm value  '&ETA',
          i_save(1) type c,
          i_exit(1) type c,
          i_variant like disvariant,
          h_text(50).
    start-of-selection.
      selection-screen skip 1.
      selection-screen begin of block v1 with frame title text-001.
      selection-screen skip 1.
      select-options:
                     ord_no for vepvg-vbeln,
                     audat for vbak-audat obligatory,
                     matnr for vbap-matnr,
                     spart for vbap-spart obligatory,
                     vstel for vepvg-vstel obligatory,
                     sale_org for vbak-vkorg obligatory,
                     sale_off for vbak-vkbur.
      selection-screen skip 1.
    check box for ALV display
      parameters p_alv as checkbox.
      selection-screen end of block v1.
      selection-screen skip 1.
      data:   ftab(72) occurs 5 with header line.
      refresh ftab.
      ftab = 'VBELN'. append ftab.
      refresh itab_vbak.
    initialization.
      i_repname = sy-repid.
    start-of-selection.
      select vbeln audat vkorg vtweg spart vkbur kunnr from vbak
           into
           (itab_vbak-vbeln, itab_vbak-audat,
            vbak-vkorg, vbak-vtweg, vbak-spart,
            itab_vbak-vkbur, itab_vbak-kunnr)
           where vbeln in ord_no
           and audat in audat
           and vbtyp = 'C'
           and vkorg in sale_org
           and spart in spart
           and vkbur in sale_off.
        if sy-subrc = 0.
          select posnr kwmeng kbmeng matnr arktx  "added for mat description
                   fkrel vstel route kzwi5 spart
                   from vbap into corresponding fields of itab_vbak
                   where vbeln = itab_vbak-vbeln .
            check ( itab_vbak-fkrel = 'A' or  "Delivery-related billing document
                    itab_vbak-fkrel = 'D' )   "Relevant for pro forma
              and itab_vbak-vstel in vstel
              and itab_vbak-matnr in matnr
              and itab_vbak-spart in spart.
            select single * from vbup where vbeln = itab_vbak-vbeln
                                        and posnr = itab_vbak-posnr.
            check vbup-gbsta ne 'C'.
            dlv_qty = 0.
            select single kunnr from vbpa into itab_vbak-kunnr
                   where vbeln = itab_vbak-vbeln
                   and parvw = 'WE'.
            select single name1 ort01 from kna1 into
                   (itab_vbak-cust, itab_vbak-city)
                    where kunnr = itab_vbak-kunnr.
          in case of partially processed sale order get delivery details
            clear : dlv_qty, itab_vbak-dlv_dt, itab_vbak-dlvd_qty, itab_vbak-chln_no,
                    itab_vbak-grn_no, itab_vbak-truck_no.
            if vbup-gbsta eq 'B'. "partially processed
              dlv_qty = 0.
            get details from delivery
              select vbfavbeln vbfarfmng vbfavbtyp_n vbfaerdat
                 into (vbfa-vbeln, vbfa-rfmng, vbfa-vbtyp_n, vbfa-erdat)
                 from vbfa
                 where vbelv = itab_vbak-vbeln
                   and posnv = itab_vbak-posnr.
                check vbfa-vbtyp_n = 'J'.
                clear : dlv_qty, itab_vbak-dlv_dt, itab_vbak-dlvd_qty, itab_vbak-chln_no,
                        itab_vbak-grn_no, itab_vbak-truck_no.
                select single erdat xabln bolnr traid kunag
                   into (itab_vbak-dlv_dt, itab_vbak-chln_no, itab_vbak-grn_no,
                         itab_vbak-truck_no, itab_vbak-kunag)
                   from likp
                   where vbeln = vbfa-vbeln.
                if sy-subrc = 0.
                  dlv_qty = dlv_qty + vbfa-rfmng.
                  itab_vbak-dlv_dt = vbfa-erdat.
                  itab_vbak-dlvd_qty = dlv_qty.
                  itab_vbak-deliv = vbfa-vbeln.
                endif.
                append itab_vbak.
              endselect.
            elseif vbup-gbsta eq 'A'.
            for unprocessed sale order
            ship to party details
              itab_vbak-kunag = itab_vbak-kunnr.
              itab_vbak-ship = itab_vbak-cust.
              append itab_vbak.
            endif.
          endselect.
        endif.
        clear itab_vbak.
      endselect.
      loop at itab_vbak.
      clear with change in document / item no
        on change of itab_vbak-vbeln or itab_vbak-posnr.
          clear: dlv_qty,ord_qty,pend_qty.
        endon.
        at new posnr.
        In case full qty not delivered
          if itab_vbak-kwmeng > itab_vbak-dlvd_qty.
            select single vbpa~kunnr into vbpa-kunnr
               from vbpa
               where vbeln = itab_vbak-vbeln
                and  posnr = itab_vbak-posnr
                and  parvw = 'WE'.
            if sy-subrc eq 0.
              itab_vbak-kunag = vbpa-kunnr.
              select single name1 ort01 from kna1 into
                    (itab_vbak-ship, itab_vbak-city)
                     where kunnr = itab_vbak-kunag.
              if sy-subrc ne 0.
                select single vbpa~kunnr into vbpa-kunnr
                   from vbpa
                   where vbeln = itab_vbak-vbeln
                   and parvw = 'WE'.
                itab_vbak-kunag = vbpa-kunnr.
                if sy-subrc ne 0 and p_alv ne 'X'.
                  write :/ 'vbpadetls' , itab_vbak-vbeln, itab_vbak-posnr, itab_vbak-vbeln.
                endif.
              endif.
            endif.
          endif.
          itab_vbak-ord_qty = itab_vbak-kwmeng.
        Delivered Qty & Pending qty
          dlv_qty = dlv_qty + itab_vbak-dlvd_qty.
          itab_vbak-pend_qty = itab_vbak-kwmeng - dlv_qty.
          modify itab_vbak transporting kunag ship city dlvd_qty ord_qty pend_qty .
        endat.
      endloop.
    end-of-selection.
      sort itab_vbak by vbeln posnr audat kunnr matnr.
      if p_alv ne 'X'.
        loop at itab_vbak.
          select single kna1name1 kna1ort01
                 into
                 (kna1-name1, kna1-ort01)
                 from kna1
                 where kunnr = itab_vbak-kunnr.
          pend_qty = itab_vbak-ord_qty - itab_vbak-dlvd_qty.
          format color col_normal.
          write : /01(10) itab_vbak-vbeln,
                  12(10)  itab_vbak-audat,
                  24(8)  itab_vbak-kunag no-zero,
                  34(6)  itab_vbak-posnr no-zero,
                  42(10) itab_vbak-matnr no-zero,
                  54(15) itab_vbak-arktx,
                  72(25) itab_vbak-ship,
                  100(15) itab_vbak-city,
                  118(8)  itab_vbak-ord_qty,
                  128(10) itab_vbak-route,
                  140(10) itab_vbak-dlv_dt,
                  152(10) itab_vbak-dlvd_qty,
                  164(10)  itab_vbak-chln_no,
                  176(10)  itab_vbak-grn_no,
                  188(10)  itab_vbak-truck_no,
                  200(10) itab_vbak-pend_qty,
                  218(15) itab_vbak-kzwi5 left-justified.
          format reset.
          at end of audat.
            sum.
            pend_qty = itab_vbak-ord_qty - itab_vbak-dlvd_qty.
            format color col_background.
            write: /118(8) itab_vbak-ord_qty,
                   152(10) itab_vbak-dlvd_qty,
                   200(10) pend_qty,
                   218 itab_vbak-kzwi5 left-justified.
            format reset.
          endat.
          at last.
            sum.
            pend_qty = itab_vbak-ord_qty - itab_vbak-dlvd_qty.
            format color col_total.
            write : /5 'Grand Total : '.
            write: /118(8) itab_vbak-ord_qty,
                  152(10) itab_vbak-dlvd_qty,
                  200(10) pend_qty,
                  218 itab_vbak-kzwi5 left-justified.
            format reset.
          endat.
        endloop.
      else.
      for ALV Display
        i_repname = sy-repid.
        perform fieldcat using i_fieldtab[].
        perform eventtab using i_events[].
        perform comment using i_heading[].
        perform call_alv.
        perform build_layout using i_layout.
      endif.
    top-of-page.
      if p_alv ne 'X'.
        format color col_heading.
        write: /01 'Ord No',
                12 'Ord Date',
                24 'Sold to Party',
                34 'Item No',
                42 'Mat No',
                54 'Mat Descp',
                72 'Ship to Party',
                100 'City',
                118 'Qty',
                128 'Route',
                140 'Dlv Date',
                152 'Dlv Qty',
                164 'Challan No',
                176 'GRN No',
                188 'Truck No',
                200 'Pend Qty',
                218 'Total Value'.
        format reset.
      endif.
    *&      Form  fieldcat
          text
         -->P_I_FIELDTAB[]  text
    form fieldcat using p_fieldtab type slis_t_fieldcat_alv.
      data: l_fieldcat type slis_fieldcat_alv.
      clear l_fieldcat.
      l_fieldcat-tabname    = 'ITAB_VBAK'.
      l_fieldcat-fix_column = 'X'.
      l_fieldcat-no_out     = ' '.
      l_fieldcat-fieldname  = 'VKBUR'.
      l_fieldcat-outputlen  = 6.
      l_fieldcat-seltext_l  = 'Sales Office'.
      l_fieldcat-no_zero = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'VSTEL'.
      l_fieldcat-outputlen  = 5.
      l_fieldcat-seltext_l  = 'Shipping Point'.
      l_fieldcat-no_zero = ' '.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'VBELN'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Order No.'.
      l_fieldcat-no_zero = 'X'.
      l_fieldcat-hotspot = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'AUDAT'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Doc Date'.
      l_fieldcat-hotspot = ''.
      l_fieldcat-no_zero = ' '.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'POSNR'.
      l_fieldcat-outputlen  = 5.
      l_fieldcat-seltext_l  = 'Item'.
      l_fieldcat-no_zero = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'MATNR'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Material No'.
      l_fieldcat-no_zero = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'ARKTX'.
      l_fieldcat-outputlen  = 15.
      l_fieldcat-seltext_l  = 'Mat. Description'.
      l_fieldcat-no_zero = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'KUNNR'.
      l_fieldcat-outputlen  = 8.
      l_fieldcat-seltext_l  = 'Sold to Party'.
      l_fieldcat-no_zero = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'CUST'.
      l_fieldcat-outputlen  = 15.
      l_fieldcat-seltext_l  = 'Sold to Party Descp.'.
      l_fieldcat-no_zero = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'KUNAG'.
      l_fieldcat-outputlen  = 8.
      l_fieldcat-seltext_l  = 'Ship to Party'.
      l_fieldcat-no_zero = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'SHIP'.
      l_fieldcat-outputlen  = 15.
      l_fieldcat-seltext_l  = 'Ship to Party Descp'.
      l_fieldcat-no_zero = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'CITY'.
      l_fieldcat-outputlen  = 13.
      l_fieldcat-seltext_l  = 'City'.
      l_fieldcat-no_zero = ' '.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'DELIV'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Delivery No.'.
      l_fieldcat-no_zero = 'X'.
      l_fieldcat-hotspot = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'ORD_QTY'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Qty'.
      l_fieldcat-no_zero = ' '.
      l_fieldcat-hotspot = ' '.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'ROUTE'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Route'.
      l_fieldcat-no_zero = 'X'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'DLV_DT'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Delivered date'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'DLVD_QTY'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Delivered Qty'.
      l_fieldcat-no_zero = ' '.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'CHLN_NO'.
      l_fieldcat-outputlen  = 15.
      l_fieldcat-seltext_l  = 'Challan No'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'GRN_NO'.
      l_fieldcat-outputlen  = 15.
      l_fieldcat-seltext_l  = 'GR Number'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'TRUCK_NO'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Truck No'.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'PEND_QTY'.
      l_fieldcat-outputlen  = 10.
      l_fieldcat-seltext_l  = 'Pending Qty'.
      l_fieldcat-no_zero = ' '.
      append l_fieldcat to p_fieldtab.
      l_fieldcat-fieldname  = 'KZWI5'.
      l_fieldcat-outputlen  = 13.
      l_fieldcat-seltext_l  = 'Value'.
      append l_fieldcat to p_fieldtab.
      clear l_fieldcat.
    endform.                    " FIELDCAT
    *&      Form  EVENTTAB
          text
         -->P_I_EVENTS[]  text
    form eventtab using p_events type slis_t_event.
      data: ls_event type slis_alv_event.
      call function 'REUSE_ALV_EVENTS_GET'
        exporting
          i_list_type = 0
        importing
          et_events   = p_events.
      read table p_events with key name = slis_ev_top_of_page
                               into ls_event.
      if sy-subrc = 0.
        move formname_top_of_page to ls_event-form.
        append ls_event to p_events.
      endif.
    endform.                    " EVENTTAB
    *&      Form  BUILD_LAYOUT
          text
         -->P_LAYOUT   text
    form build_layout using p_layout type slis_layout_alv.
      p_layout-f2code       = f2code.
      p_layout-zebra        = 'X'.
      p_layout-detail_popup = 'X'.
    endform.                    " BUILD_LAYOUT
    *&      Form  COMMENT
          text
         -->P_I_HEADING[]  text
    form comment  using    p_i_heading type slis_t_listheader.
      data: hline type slis_listheader,
            text(60) type c,
            sep(20) type c.
      clear: hline, text.
      hline-typ  = 'H'.
      write : 'Pending Sale Order Details' to hline-info.
      append hline to i_heading.
    endform.                    " COMMENT
    *&      Form  TOP_OF_PAGE
          text
    form top_of_page.
      call function 'REUSE_ALV_COMMENTARY_WRITE'
        exporting
          it_list_commentary = i_heading
          i_logo             = 'ALV_REPORT'.
    endform.                    " TOP_OF_PAGE
    *&      Form  call_alv
          text
    -->  p1        text
    <--  p2        text
    form call_alv .
      call function 'REUSE_ALV_GRID_DISPLAY'
        exporting
          i_interface_check        = ' '
          i_buffer_active          = ' '
          i_callback_program       = i_repname
          i_callback_pf_status_set = ' '
          i_callback_user_command  = 'FRM_ALV_USER_COMMAND'
          i_structure_name         = 'ITAB_VBAK'
          i_background_id          = ' '
          is_layout                = i_layout
          it_fieldcat              = i_fieldtab
          it_sort                  = i_sort[]
          i_default                = 'X'
          i_save                   = 'A'
          is_variant               = i_variant
          it_events                = i_events[]
          is_print                 = i_print
        tables
          t_outtab                 = itab_vbak.
      if sy-subrc <> 0.
        write: 'SY-SUBRC: ', sy-subrc, 'REUSE_ALV_LIST_DISPLAY'.
      endif.
    endform.                    " call_alv
    *&      Form  frm_alv_user_command
          text
         -->UCOMM      text
         -->SELFIELD   text
    form frm_alv_user_command using ucomm like sy-ucomm
                  selfield type slis_selfield.
      case ucomm.
        when '&IC1'.
          if selfield-tabname = 'ITAB_VBAK'.
            if selfield-fieldname = 'VBELN'.
              read table itab_vbak index selfield-tabindex.
              if sy-subrc = 0.
                set parameter id 'AUN' field itab_vbak-vbeln.
                call transaction 'VA03' and skip first screen.
              endif.
            elseif selfield-fieldname = 'DELIV'.
              read table itab_vbak index selfield-tabindex.
              if sy-subrc = 0.
                set parameter id 'VL' field itab_vbak-deliv.
                call transaction 'VL03N' and skip first screen.
              endif.
            endif.
          endif.
      endcase.
    endform.                    "frm_alv_user_command

  • Clear unwanted open delivery value FD33

    Hi
    I have an issue issue in FD33. It is showing open delivery value but VC/2 is showing no open deliveries. Please advise me how to update this open delivery value.
    Is there any program to get it updated and also let me know what would be the reason for not updated this value.
    Thanks in Advance
    Regards,
    Gali

    hi,
    please check the document created date.
    if it is under the moths given then we can consider your problem and system has to calculate that documents also.
    so please check the dates of document.
    regards,
    balajia

  • Open Delivery value in FD33

    In FD33 for one of our customers, it is showing a big amount in 'Sales Value' and when drilling down to it, it shows the amount as 'Open Delivery'.  According to users, we do not have any open delivery for this customer.
    Is there a report that will show the detail of that Open Delivery amount, e.g. Sales Order number?  
    Thank you,

    Hello Ruslim
    Sometimes there an inconsistancy in credit value updation, like the case you mentioned -  there is no open delivery but still some value is appearing in the open delivery.
    You can execute program RVKRED88 (simulation- reorganisatio of SD credit data) & check the correct value.
    once you execute above program against the credit account & credit control area, you will get the detail of the correct values.
    once you are sure that there is a inconsistancy, you can run program RVKRED77 to update the value correctly in FD33.
    To summerise - RVKRED88 is for simulation & RVKRED77 for updating.
    thank you
    Anirudh

  • Credit management Authorization Based on Value.

    Hi All,
    Can help me out to find whether we can implement Credit management based on different level of Values or not.As i know we can do authorization based on % like 100%, 110% etc.
    But i want to activate release authorization based on the Amount like
    level 1              Rs 1 lakh( Can release upto 1 lakh) when it reaches to above of 1 lakh
    level2               Rs  2 lakh ( it will release upto 2 lakh)
    like wise.As what i understand whatever the standard roles are given relevant to % basis only.

    hello, friend.
    yes, you can do this in a few ways...
    1.  try 'Document Class' - a document class is assigned a certain value, which is assigned to a user (the link to credit management is indirect)
    2.  the traditional way is to use 'Risk Category', and you can set specific values (e.g. maximum document values) when doing OVA8. 
    i seem to recall there may also be a way to assign values to risk category, but i will check on this.
    regards.

  • Credit Management - Release for delivery

    Dear all,
    Any body kindly explain for me about Release function in VKM3, pls?
    If a sales order is blocked for delivery with Credit limit check, and now, i want to deliver that order without remove Credit limit check by go to va02 and change that order. So, How to do?
    Thank you,

    Hi Quang...
    VKM3 is used to view the orders blocked for delivery.
    As you said.. if an order is blocked for delivery, you can release the block by getting into VA02. Under the General Header data of Sales in the field delivery block you could see the reason for blocking that particular sales order for delivery.
    In that you may have to remove the block to blank.(i.e the delivery block column should be blank...) Hence you can remove the block for that particular delivery....
    Sometimes if releasing the sales order block is not in your eligibility and if you have to reassign that responsibility to your manager (say the Regional sales manager) then you have to reassign the task to him. For that we are having reassign button.
    Sometimes.. if you want to reject that sales order as a whole , as you are thinking that sales need not happen for that particular sales order... you can reject the sales order. If you reject the sales order it wouldn't be possible for your other users to process that under any circumstance of time..
    Hope I have answered all your queries..
    Thanks,
    Safeer Rahman

  • To exclude Open Order Value in Credit exposure for Delivery credit Block

    Dear All,
    I have assigned the credit Limit block at the Delivery Level.
    For the credit Exposure, i have removed the ticked for Open Sales Orders.
    But when i created sales Order, that open order value get added to the exposure. I want to have only the Open Delivery values and other pending Invoices.
    Is there any option for me to avoid the open sales Order value get updated in the Credit Exposure.
    Thank U,
    Uwanthi

    Hi,
    Remove Sales document type from 'Assign Sales Documents and Delivery Documents' node and assign only delivery credit group.
    Check configuration in OVA8 for both the credit groups.
    In FD32 if sales value is already added as open items and exposure is updated, try using a new customer to test your requirement or reset the customer.
    Regards,
    Amit

  • Regarding open items in credit management

    Dear friends
    My query is that is it possible to restrict credit management for credit and debit open items? See i am using oldest open item blocking in my scenario. Now credit and debit amounts are both considered as open item for credit management. I want only invoice (Debit entry) for consideration and not his payment(credit entry).
    Please advise is it possible or not and if possible where to define that???
    With regards
    Inder

    Hi,
    All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria. You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
    SM30 - Table/View
    V_TVTW – Define Distribution Channel
    V_TVTA_KKB – Assign sales area to credit control area
    V_T014 – FI - Define Credit Control Area
    T001CM - FI – Assign Permitted Credit Control Area to company code
    OVXG - Set up Sales Areas
    e.g. Sales Organization
    Distribution Channel Division Distribution Channel Division
    FD32 - Customer Credit Management
    OVAK - Define credit limit check by sales document type
    Check Credit
    A – Credit limit check and warning message
    B – Credit limit check and error message (no sales order can be created)
    C – Credit limit check and delivery block (block delivery if hit credit limit)
    Options B and C -> used for checking open order values (when you create/change the sales order)
    D – Automatic credit control with open order values
    More control in transaction OVA8 - Automatic credit control
    You check for open orders and deliveries, or just open deliveries.
    or open order values with other options
    Credit group
    Allows you to combine different sales document types for the credit limit check
    VKM1 - Blocked SD Documents – Finance have to released the delivery block
    OVAD - Define credit limit check by delivery order
    whether the automatic credit check occurs at the time of delivery creation and/or goods issue
    OVA7 - Define credit limit check by item category
    Set whether to include/exclude item category for credit limit check
    OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
    You enter the credit groups when you configure the sales document types for credit management and define the (D – automatic credit check).
    SAP default credit groups
    01 – credit group for sales order
    02 – credit group for delivery
    03 – credit group for goods issue
    OVA8 - Automatic credit control – Double click on the line items
    You can have the followings credit limit check :-
    Static
    Depends on the customer total value of open orders, deliveries, billing documents and open items.
    Open items
    No of days open
    Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
    Max open items %
    The customer balance must not exceed a certain percentage.
    Oldest open items
    If you don’t want to deliver to the customer at all when even only 1 invoice is overdue.
    Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
    Days oldest item
    No of days allowed for overdue or payment terms.
    Use of the credit check Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
    that was previously blocked, it would be reblocked again by the system. The system only reblocks the sales document if the new order quantity is above a certain % amount.
    Released documents are still unchecked
    The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
    Next Review Date
    If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document day is in April then the credit limit is zero.
    You can use the “NextReview date” and “Number of days” fields and combined it with the “Last int.review” field in customer credit master “Status” view (FD32).
    VOKR - Display of work list for credit management (configure the display variant)
    regards,
    Siddharth.

  • Credit management-sales value

    Hi
    Sales value showing incorrect value in credit management(FD32-Transaction code)
    Sales value is determined based on following formula
    Sales value = Open delivery/invoice - Open order
    Open Delivery/Invoice: 162,812.52 (go to environment>sales and distribution doc > Open delivery/Invoice
    I would like to know that what are the Open delivery number. Because by checking open delivery status the value is not matching with above Open delivery value = 162,812.52
    Kindly let us know how to get delivery no/Invoice no to identify and match sales value.
    Regards
    Pinal

    Hi Pinal,
    Please check the T code VF04 which shows all the Open Deliveries which have PGIed between a particular date range.
    Sum of all these open deliveries will give the Open Deliveries value.
    Regards,
    MP

Maybe you are looking for

  • Time Capsule won't connect to BT Home Hub3

    I was using the TC in Dubai and all was well and I am now back living in the UK. I now have a BT Home Hub 3 but I can't get the TC to connect to the network. Do I need to set the TC up as the primary network? If so, how do I do this? Or do I set the

  • Sec 10 Exemptions and form 16 summary  are not showing in payslip..

    Hi Experts, After configuration of all nodes i am unable to see Form 16 summary and Sec 10 exemptions In payslip.Please help me to resolve the problem.Thanks in advance. Regards, Sai.

  • How to get in IPhoto chosen top photo of album presented in iOS

    On Mac a photo can be chosen as top photo. In Photos on iOS a random? photo is presented.

  • Calibration error message in WCS(MSE)

    I get a calibration error message in WCS when I try to add data points in the RF calibrate models section.  Here is the error message: Error in Calibration. MessageMEDIATION-5, WcCalibration!x.x.x.x!xx:xx:xx:xx:xx:xx,row Status,No access The first se

  • Simple Maze Game (Pac Man Style) Best Practice

    Hi I wanting to create a really basic pac man style maze game, its actually for some marketing materials and it will be really used as means of navigation rather than as a game, I want pac mac to eat certain words and when that happens it will tell t