Requirement of archived sales order is showed in mdo4.

the sales order is archived ,but its
requirement is showed in mdo4 and the delivery document have been
archived .i donn't how to correct it .

run SDRQCR21

Similar Messages

  • Due to deleted Sales order line items and Archived Sales order is still showing as Incomplete in BW as Open Order reports because of Incorrect SAP R/3 Rejection Status("A") in VBUP table.

    In a archived saler Order user had deleted Line Item and completed overall sales order. Now this sales order is archived, but it is stll appearing in BW report as open order because of deleted item  with rejection Status is maintained as “A” (Not yet Processed).
    We want to change this status from "A" (Not yet Processed) to "C" as completed.
    I have tried to reload Archive data but due to some limitation I was not able to do it. Also I feel this will like this s not the proper way to do it.
    Could you please help me to correct way to do it???
    Thanks in advance....

    Hi Vaibhav,
    If you can get the list of Sales orders which has deleted line items and force completion status. You can manage them in BI via lookup  or navigation attribute.
    Just my views I am sharing .
    Thanks,
    KDJ

  • View requirements for delivered sales orders in MD4C.

    MD4C shows requirements for open sales orders and other related data but if a delivery has been created for the order which covers complete sales order item quantity it is excluded in the report.
    I want to view such requirements too. Is there a possibility of the same and how?
    Or any other transaction where this can be seen?
    Regards,
    Sonal Murbade

    Hi,
    When a delivery is completed (e.g. bu PGI). the requirement is not needed any more and it's deleterd in table VBBE or VBBS, so, you can not see it in requirement list any more.
    You sill can see the order in table VBAP(sales order) or table LIPS (delivery).
    BR

  • Tables for archived sales order data

    Hi,
    ABAP Gurus would like to know in which tables will I be able to see data of archived sales orders (it is not VBAK)
    Any help would be greatly appreciated.
    Thanks in advance.
    Mick

    Hi,
    If I am understanding correctly, your system has data archiving implemented.
    If that's the case then there is no table which will store archived sales order.
    For that you need to go to T.Code SARA.
    Choose object name SD_VBAK.
    Click on READ.
    This will show a screen giving a name of program and option to execute in background or foreground.
    This is how you can retrieve the info about archived Sales Order.
    Hope this helps
    Regards
    Nishant
    Message was edited by:
            Nishant Rustagi

  • How to retrieve the ARCHIVED Sales order data

    Hi All,
    When issuing the output for the delivery, it is giving an error saying 'Sales Order XXXX does not exist' due to which the prices in the output were displayed as '0'. Reason for this can be that 'the order might have been archived'.
    My requirement is,
    1. If Sales Order doesnu2019t exist in data base then need to check if Sales order exists in archive data base.
    2. If  yes, take needed data from archive data base tables to calculate price. The logic of price calculation should be the same as for not archived Sales Orders.
    Can anyone help me on this..?
    Please tell me how to check whether the Sales order exists in the Archived database. Please share the table names(sample logic if possible) sothat I can use them in the report logic.
    Please tell me how to pull the data from the archive database tables to calculate the price.
    Thank you in advance.
    Thanks & Regards,
    Paddu.
    Edited by: Paddu K on Feb 23, 2009 3:42 PM

    *&      Form  get_archive_data
    *       Fetch Archive Data
    FORM get_archive_data .
      CLEAR:    g_read_handle, g_commit_cnt,
                g_read_cnt, g_reload_cnt,it_rel_tab,it_bseg_a,it_bkpf_a,
                it_bset_a, gt_result.
      REFRESH: it_rel_tab[],it_bseg_a[],it_bkpf_a[],
               it_bset_a[], gt_result[].
    *Populating selection screen fields to field-symbols
      PERFORM build_fs_select_options.
    *Call FM as_api_read  FI Data
      CALL FUNCTION 'AS_API_READ'
        EXPORTING
          i_fieldcat                      = 'SAP_FI_DOC_002'
          i_selections                    = ft_selections[]
    *   I_OBLIGATORY_FIELDS             =
    *   I_MAXROWS                       =
       IMPORTING
         e_result                        = gt_result[]
    EXCEPTIONS
       parameters_invalid              = 1
       no_infostruc_found              = 2
       field_missing_in_fieldcat       = 3
       OTHERS                          = 4
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      IF NOT gt_result[] IS INITIAL.
    *Sorting by KEY and Offset
        SORT gt_result BY archivekey archiveofs.
    *To delete duplicates
        DELETE ADJACENT DUPLICATES FROM gt_result COMPARING archivekey
        archiveofs.
    *looping the internal table
        LOOP AT gt_result.
    *Get read handle for  object
          CALL FUNCTION 'ARCHIVE_READ_OBJECT'
            EXPORTING
              object         = 'FI_DOCUMNT'
              archivkey      = gt_result-archivekey
              offset         = gt_result-archiveofs
            IMPORTING
              archive_handle = g_read_handle
            EXCEPTIONS
              OTHERS         = 1.
          IF NOT sy-subrc IS INITIAL.
            MESSAGE ID sy-msgid TYPE 'I' NUMBER sy-msgno
                    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
            EXIT.
          ENDIF.
          IF sy-subrc = 0.
    *Get Acoounting Document details
            PERFORM object_read_opened
                      TABLES it_rel_tab
                             it_bseg_a
                             it_bkpf_a
    *                         it_bset_a
    *                         it_bsik_a
    *                         it_bsak_a
                             it_bsid_a
                             it_bsad_a
    *                         it_bsec_a
                      USING g_read_handle
                            l_archobj
                            g_commit_cnt
                            g_read_cnt
                            g_reload_cnt
          ENDIF.
    *close the file.
          CALL FUNCTION 'ARCHIVE_CLOSE_FILE'
            EXPORTING
              archive_handle          = g_read_handle
            EXCEPTIONS
              internal_error          = 1
              wrong_access_to_archive = 2
              OTHERS                  = 3.
          IF sy-subrc <> 0.
            MESSAGE i004." 'Unable to close archive session'.
            EXIT.
          ENDIF.
        ENDLOOP.
      ELSE.
        MESSAGE i000 WITH 'No data found for Archived data'(095).
        EXIT.
      ENDIF.
    *Start of Changes by GTHATIKONDA on 10/17/2008 #ECDK902204
      IF NOT it_bkpf_a[] IS INITIAL.
        SORT it_bkpf_a BY belnr.
        DELETE ADJACENT DUPLICATES FROM it_bkpf_a COMPARING belnr.
        DELETE it_bkpf_a WHERE budat GT p_budat. "#ECDK902206
      ENDIF.
    *Start of Changes by GTHATIKONDA on 10/17/2008 #ECDK902206
      IF it_bkpf_a[] IS INITIAL.
        MESSAGE i000 WITH 'No data found for Archived data'(095).
      ENDIF.
    *End of Changes by GTHATIKONDA on 10/17/2008 #ECDK902206
      IF NOT it_bseg_a[] IS INITIAL.
        SORT it_bseg_a BY belnr gjahr buzei.
        DELETE ADJACENT DUPLICATES FROM it_bseg_a COMPARING
                                              belnr gjahr buzei.
      ENDIF.
    *End of Changes by GTHATIKONDA on 10/17/2008 #ECDK902204
    ENDFORM.                    " get_archive_data
    *&      Form  build_fs_select_options
    FORM build_fs_select_options .
      REFRESH:  ft_selections.
    *Comapny code
      APPEND INITIAL LINE TO ft_selections ASSIGNING <fw_selections>.
      <fw_selections>-fieldname  = 'BUKRS'.
      APPEND INITIAL LINE TO <fw_selections>-selopt_t ASSIGNING <lw_selopt>.
      MOVE p_bukrs  TO <lw_selopt>-low.
      MOVE  'I' TO <lw_selopt>-sign.
      MOVE  'EQ' TO <lw_selopt>-option.
    *Customer
      APPEND INITIAL LINE TO ft_selections ASSIGNING <fw_selections>.
      <fw_selections>-fieldname  = 'KUNNR'.
      LOOP AT s_kunnr.
        APPEND INITIAL LINE TO <fw_selections>-selopt_t
               ASSIGNING <lw_selopt>.
        MOVE-CORRESPONDING  s_kunnr TO <lw_selopt>.
      ENDLOOP.
    *Start of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
    **Customer Group
    *  append initial line to ft_selections assigning <fw_selections>.
    *  <fw_selections>-fieldname  = 'KTOKD'.
    *  loop at s_ktokd.
    *    append initial line to <fw_selections>-selopt_t
    *           assigning <lw_selopt>.
    *    move-corresponding  s_ktokd to <lw_selopt>.
    *  endloop.
    *End of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
    *Profit Center
      APPEND INITIAL LINE TO ft_selections ASSIGNING <fw_selections>.
      <fw_selections>-fieldname  = 'PRCTR'.
      LOOP AT s_prctr.
        APPEND INITIAL LINE TO <fw_selections>-selopt_t
               ASSIGNING <lw_selopt>.
        MOVE-CORRESPONDING  s_prctr TO <lw_selopt>.
      ENDLOOP.
    *Commented #ECDK902210
    **Key Date
    *  append initial line to ft_selections assigning <fw_selections>.
    *  <fw_selections>-fieldname  = 'BUDAT'.
    *  append initial line to <fw_selections>-selopt_t assigning <lw_selopt>
    *  move p_budat  to <lw_selopt>-low.
    *  move  'I' to <lw_selopt>-sign.
    *  move  'EQ' to <lw_selopt>-option.
    *Aging Period1
      APPEND INITIAL LINE TO ft_selections ASSIGNING <fw_selections>.
      <fw_selections>-fieldname  = 'ANZTA'.
      APPEND INITIAL LINE TO <fw_selections>-selopt_t ASSIGNING <lw_selopt>.
      MOVE p_ag1  TO <lw_selopt>-low.
      MOVE  'I' TO <lw_selopt>-sign.
      MOVE  'EQ' TO <lw_selopt>-option.
    *Aging Period2
    *Start of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
    *  append initial line to ft_selections assigning <fw_selections>.
    *  <fw_selections>-fieldname  = 'ANZTA'.
    *End of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
      APPEND INITIAL LINE TO <fw_selections>-selopt_t ASSIGNING <lw_selopt>.
      MOVE p_ag2  TO <lw_selopt>-low.
      MOVE  'I' TO <lw_selopt>-sign.
      MOVE  'EQ' TO <lw_selopt>-option.
    *Aging Period3
    *Start of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
    *  append initial line to ft_selections assigning <fw_selections>.
    *  <fw_selections>-fieldname  = 'ANZTA'.
    *End of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
      APPEND INITIAL LINE TO <fw_selections>-selopt_t ASSIGNING <lw_selopt>.
      MOVE p_ag3  TO <lw_selopt>-low.
      MOVE  'I' TO <lw_selopt>-sign.
      MOVE  'EQ' TO <lw_selopt>-option.
    *Aging Period4
    *Start of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
    *  append initial line to ft_selections assigning <fw_selections>.
    *  <fw_selections>-fieldname  = 'ANZTA'.
    *End of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
      APPEND INITIAL LINE TO <fw_selections>-selopt_t ASSIGNING <lw_selopt>.
      MOVE p_ag4  TO <lw_selopt>-low.
      MOVE  'I' TO <lw_selopt>-sign.
      MOVE  'EQ' TO <lw_selopt>-option.
    *Aging Period5
    *Start of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
    *  append initial line to ft_selections assigning <fw_selections>.
    *  <fw_selections>-fieldname = 'ANZTA'.
    *End of changes by GTHATIKONDA on 16/10/2008 #ECDK902192
      APPEND INITIAL LINE TO <fw_selections>-selopt_t ASSIGNING <lw_selopt>.
      MOVE p_ag5  TO <lw_selopt>-low.
      MOVE  'I' TO <lw_selopt>-sign.
      MOVE  'EQ' TO <lw_selopt>-option.
    ENDFORM.                    " build_fs_select_options
    *&      Form  object_read_opened
    *       To Fetch Arichive Data
    FORM object_read_opened TABLES   it_rel_tab
                                      it_bseg_a
                                      it_bkpf_a
    *                                  it_bset_a
    *                                  it_bsik_a
    *                                  it_bsak_a
                                      it_bsid_a
                                      it_bsad_a
    *                                 it_bsec_a
                             USING value(g_read_handle) LIKE sy-tabix
                                   value(l_archobj) LIKE arch_def-object
                             value(g_commit_cnt) LIKE arch_usr-arch_comit
                               g_read_cnt TYPE i
                               g_reload_cnt TYPE i.
      DATA: BEGIN OF table_wa ,
               table LIKE arch_stat-tabname,
            END  OF table_wa.
      DATA: lit_data(2048) TYPE c OCCURS 1 WITH HEADER LINE.
      DATA:  l_structure LIKE arch_stat-tabname,
             l_lin TYPE i.
      CLEAR: it_table_org1,lit_struc,it_table_org2,table_wa,it_rel_tab.
      REFRESH: it_table_org1[],lit_struc[],it_table_org2[],it_rel_tab[].
      CLEAR: g_duprec,g_read_cnt,g_reload_cnt,g_object_cnt.
    *Read  data from the infostructure
      DO.
        ADD 1 TO g_object_cnt.
        CLEAR l_structure.
        CALL FUNCTION 'ARCHIVE_GET_NEXT_RECORD'
          EXPORTING
            archive_handle                = g_read_handle
         IMPORTING
           record                        = lit_data
    *   RECORD_CURSOR                 =
    *   RECORD_FLAGS                  =
           record_structure              = l_structure
    *   RECORD_LENGTH                 =
    *   RECORD_REF                    =
         EXCEPTIONS
           end_of_object                 = 1
           internal_error                = 2
           wrong_access_to_archive       = 3
           OTHERS                        = 4
        IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          EXIT.
        ENDIF.
        IF NOT l_structure IS INITIAL.
          table_wa-table = l_structure.
          APPEND table_wa TO it_rel_tab.
        ENDIF.
        APPEND lit_data.
        CLEAR l_lin.
        FIELD-SYMBOLS: <fs_struc> TYPE c.
        CASE l_structure.
    *BKPF data
          WHEN 'BKPF'.
            ASSIGN it_bkpf_a TO <fs_struc> CASTING.
            <fs_struc> = lit_data.
            APPEND it_bkpf_a.
    *BSID data
          WHEN  'BSID'.
            ASSIGN it_bsid_a TO <fs_struc> CASTING.
            <fs_struc> = lit_data.
            APPEND it_bsid_a.
    *BSAD data
          WHEN  'BSAD'.
            ASSIGN it_bsad_a TO <fs_struc> CASTING.
            <fs_struc> = lit_data.
            APPEND it_bsad_a.
    *BSEG data
          WHEN 'BSEG'.
            ASSIGN it_bseg_a TO <fs_struc> CASTING.
            <fs_struc> = lit_data.
            APPEND it_bseg_a.
        ENDCASE.
        REFRESH lit_data.
        CLEAR g_object_cnt.
      ENDDO.
    ENDFORM.                    " object_read_opened
    *&      Form  get_bsid_bsad_archive_data
    *If Exclude Spl. GL Trnasaction is initial get BSID BSAD Archive data  *
    FORM get_bsid_bsad_archive_data .
    *Work Area
      DATA: wa_bsid TYPE type_bsid.
    *Reading BSAD Archive internal table
    *      loop at it_bsad_a   where bukrs eq p_bukrs
    *Start of changes by GTHATIKONDA on 10/14/2008 #ECDK902180
    *Commented by GTHATIKONDA on 10/17/2008 #ECDK902204
      LOOP AT it_bkpf_a  WHERE  bukrs = p_bukrs AND
                                budat LE p_budat. "#ECDK902206
    *End of changes by GTHATIKONDA on 10/14/2008 #ECDK902180
        LOOP AT it_bseg_a   WHERE bukrs EQ p_bukrs AND
                                  belnr EQ it_bkpf_a-belnr AND
                                  gjahr EQ it_bkpf_a-gjahr AND
                                  augdt GT p_budat AND
    *                            koart eq 'D'     and
                                  kunnr IN s_kunnr AND
                                  prctr IN s_prctr.
    *Changes by GTHATIKONDA on 10/17/2008 #ECDK902204
    *    loop at it_bkpf_a  where budat le p_budat."#ECDK902206
    *Move corresponding fiels
          MOVE-CORRESPONDING it_bseg_a TO wa_bsid.
          wa_bsid-blart = it_bkpf_a-blart.
          wa_bsid-budat = it_bkpf_a-budat.
          wa_bsid-bldat = it_bkpf_a-bldat.
          APPEND wa_bsid TO i_bsad.
          CLEAR wa_bsid.
        ENDLOOP.
      ENDLOOP.
      IF NOT i_bsad[] IS INITIAL.
        APPEND LINES OF i_bsad TO i_bsid.
      ENDIF.
    *Start of Changes by GTHATIKONDA on 10/17/2008 #ECDK902206
      IF NOT i_bsid[] IS INITIAL.
        SORT i_bsid BY belnr.
    *Commenting this logic by GTATIKONDA on 10/31/2008 #ECDK902245
    *  delete adjacent duplicates from i_bsid comparing belnr.
      ENDIF.
    *End of Changes by GTHATIKONDA on 10/17/2008 #ECDK902206
    ENDFORM.                    " get_bsid_bsad_archive_data
    *Reading BSAD Archive internal table
    *      loop at it_bsad_a  where bukrs eq p_bukrs
    *Start of changes by GTHATIKONDA on 10/14/2008 #ECDK902180
    *Commented by GTHATIKONDA on 10/17/2008 #ECDK902204
      LOOP AT it_bkpf_a  WHERE bukrs = p_bukrs AND  "#ECDK902206
                               budat LE p_budat.
    *End of changes by GTHATIKONDA on 10/14/2008 #ECDK902180
        LOOP AT it_bseg_a  WHERE bukrs EQ p_bukrs AND
                                 belnr EQ it_bkpf_a-belnr AND
                                 gjahr EQ it_bkpf_a-gjahr AND
                                 kunnr IN s_kunnr AND
                                 umskz EQ space AND
                                 augdt GT p_budat AND
                                 prctr IN s_prctr.
    *Changes by GTHATIKONDA on 10/17/2008 #ECDK902204
    *    loop at it_bkpf_a  where budat le p_budat. "#ECDK902206
    *Move corresponding fiels
          MOVE-CORRESPONDING it_bseg_a TO wa_bsid.
          wa_bsid-blart = it_bkpf_a-blart.
          wa_bsid-budat = it_bkpf_a-budat.
          wa_bsid-bldat = it_bkpf_a-bldat.
          APPEND wa_bsid TO i_bsad.
          CLEAR wa_bsid.
        ENDLOOP.
      ENDLOOP.
      IF NOT i_bsad[] IS INITIAL.
        APPEND LINES OF i_bsad TO i_bsid.
      ENDIF.

  • Requirement type in sales order

    hi sap gurus,
    i want to know how requirement type is configured and how it conmtroll the scenario in MAKE TO ORDER scenario. previously i have seen that with requirement type in sales order Procurement tab, system determine the planning statergy and it determine the special stock type of material, e.g. E for sales order stock and Q is for project stock. but i want to know whether this is correct or not and how this is happenning i.e. what is the configuration and assignment.
    please help at earliest.
    biplab rout

    Hi,
    Check this thread
    Re: Requirement type
    Re: requirement type and requirement class
    Thanks,
    Raja

  • Sales Order Status showing  Being Processed

    Hi All ,
    I my client created sales order with 100000.700 ton and with 42 Piratical delivery document with different dates and 42 billing document and clear accounting documents
    But the problem is Sales order status showing as Being Processed
    I check all delivery documents if was showing total quantity delivers and i check copy controls OR to ZLF Updated document flow is there
    and i Item category TAN don't not having completion rule
    My question is it is mandatory to maintain Completion rule in item category
    The Problem With Only One sales order it showing Being Processed, rest of sales document Showing completed
    Do we need to Updated Status manually ?
    Can any one guide me what could be a Problem
    Thanks
    Rajesh

    Hi,
            GO TO VA02 THEN SELECT THE ITEM  THEN GO TO SCHEDULE LINE -> STATUS TAB-> GIVE THE REASON FOR REJECTION
    Regards,
    T.Murugu

  • Archiving sales orders

    Hi,
    Is it possible to archive only sales orders, or does archiving sales orders mean we have to seperately go and archive all related deliveries, billing, etc.
    Any idea??
    Thanks
    Keshi

    HI Kesineni,
    Sales order Archiving:
    In "SARA" transaction you can select the number of the sales orders that you want to archive.
    The archive procedure has two steps:
    First - you run the preparation to the archive (here the documents steel in database, is just a test to know if the documents are ready to be archive, that means, they are completed)
    Second - You run the archive process. Here, if you have a variant to eliminate the documents automatically, the documents disappear for the data base.
    SD archiving objects are:
    SD_VBAK sales orders
    RV_LIKP deliveries
    SD_VBRK billing documents
    Reward points pls.
    Regards,
    Govind.

  • Where we can see requirement type in sales order.

    Hi
    Where we can see requirement type in sales order ?
    Can we change the requirement type in sales order.
    Thanks,
    KP

    Hi
    1.You can see requirement type in sales order in the Procurement tab.
    2.Yes you can change the requirement type in sales order in the same field.
    Regards
    Vamsi

  • Need to make available the archived sales orders to view for end users.

    Hi All Exparts,
    I have one request to make available the archived sales orders to verify the goods issue for the end users.
    can you please guide me for the same with complete details steps. i will request for the all the steps serially.
    one more thing can i make it available with the help of the ABAP guys?
    Please guide me for the same.
    Thanks to all.
    Som.

    Hi Adithya,
    Thanks for ur kind reply. i entered in SARA and put the SD_VBAK also then in the below i can see in Action - preparation, archive, delete, Analyze, Management this things only...
    so please guide what to do next with the details.
    please also tell me through this can i make it available to the end users?
    pls let me know.
    Thanks again,
    Som.

  • Removing incoterms as a required field from sales order.

    hi,
    how can i set incoterms field as a not required on the sales order?

    Hi
    I have rechecked the whole thing
    May be at item level it should be asking now
    Check the procedure flowing at VOV7 for your sales order item category
    Go to OVA2 choose your sales  item
    Again the procedure of what is there in VOV7 and remove the incoterms at item level also
    Then completely come out of SAP and relog and do it after 2 mins
    I have Incoterms removed and tested it and it is working
    Incoterms completely removed in sales order the order gets saved without incoterms
    Both at header and item level  it has to be removed from the incompletion procedure
    Regards
    Raja

  • Can I use the customer requirement number as sales order in 'Goods issue MB

    Can I use the customer requirement number as sales order in 'Goods issue MB1A'?
    Thanks,
    Tiger

    Why I used the customer requirement in MB1A as the sales order, Update was terminated.
    Thanks,
    Tiger

  • After invoice completed the sales order is showing being processed

    Dear All,
    I have created one Sales Order.  Checked the incomplet procedure where it gives document is completed.
    I have created invoice with reference to this Sales Order.  Invoice is successfully created and Accounting document is also generated.
    Now if I check the document flow the Sales Order is showing as Being Process (not completed)
    Can anyone tell me the reason why this sales order is showing Being process in Document Flow though the invoice is completly processed.
    with regards
    Amjathpasha

    Hi,
    Please check the below link. All this is happening because of some inconsistency in the system, for which we do not have a clear reason, every time and every issue may be having a different reasons. It is advisable to go through the different solutions provided by others in the forum and analyze which is suitable for your scenario.
    Hope below link helps you...
    Re: Sales Order Status
    Venkat Cheedalla

  • Specific sales order not showing in VKM1

    I have this sales order that is not showing in VKM1 even the credit status in not approved just wondering because there is other sales order with the sames credit account and credit status which show in VKM1. So there are two sales order with credit status not approved with the same credit account and same credit control area but only 1 of the 2 sales orders shows in VKM1. What are the cause of this scenario?
    I check the 2 sales order in VKM4 the only difference is field OlIt (Status of credit check against oldest open items) the sales order that shows in VKM1 got status approved while the sales order that doesnt shows in VKM1 got status not approved. Is this a possible cause? Please help where I can find this status in the sales order header

    In VBUK you can check Header - Over all credit status
    In VBUP you can check the same at item level.
    VKM1 will show documents with over all credit stats = B Credit check not OK.
    The document which is not shwoing in VKM1, CHECK IN table VBUK for the over all credit status.
    Regards
    Sai

  • Retrive the archive sales order

    Hi gurus,
    Can we retrive the archived sales order?
    How?
    thanx in advance.
    rgds,
    Anand

    Hi,
    goto SE11 - give the table name CDHDR.
    you can find out your deleted sales orde number.
    regards,
    Sumith

Maybe you are looking for