How to check how many sales orders are pending

Dear experts,
I would like to know in Sap what is the process to chech how many orders are still pending. I know some std tcodes for it I am little confused. Kindly help me how to find out.

Hi,
Goto the T.Code "VA05".
Give the date range and also enter the sold-to-party.
Tick the check box "Open Sales orders".
Enter.I will gives you the list of orders that are open means pending.
You can also use the T.Code "VA05n".
Here also tick the check box "Open orders".
Enter the document type etc...
Execute.Here also you will get the open orders.
Regards,
Krishna.

Similar Messages

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.

Many Sales Order one Production Order

Respected Members,
I have a small requirement.
Our Functional consultants make a scenario that many sales order club to give one production order depending on some parameter.
Problem is that at table level ,i am not able to see that how many sales order are clubbed to a specific production order.
I had seen pegged requirements report (tcode MD09) ,in this mrp element no is nothing but sales order no only but this records can be only seen upto u have not done the confirmation.
Once the confirmation has done it will show no records.
So please tell me in which tables i can see that how many sales orders are clubbed to a specific production order even the confirmation is also over.This is needed to built one report.
Thanks a Lot.
Manish

Hi,
If you are in MTO environment there should be direct connection between your SO and PrdOrd.
But it seems there's a N:1 relation (or N:M relation) between your SOs and PrdOrds. It means that you are in MTS environment...I'm not sure you can create such report - but it's only my opinion...
BR
Csaba

How to check ,how many users are logged in and logged out in oracle ebs 11i/R12.

Hi Experts,
Kindly let me know
how to check ,how many users are logged in and logged out in oracle ebs 11i/R12.
Also, in the database level too ,Do we need to write any trigger for this?
Thanks in advance.

Hi,
How to check ,how many users are logged in and logged out in oracle ebs 11i/R12.
Please check the following links:
Oracle EBS - Number of Users logged into EBS / Oracle Applications currently
List all users currently logged in on Oracle EBS
Also see forum Search:
Forum Search: Logged In EBS User
Also, in the database level too
Please see:
https://forums.oracle.com/message/9225094#9225094
Do we need to write any trigger for this?
Yes you may, But I personally suggest you not to do so as it may affect performance.
Thanks &
Best Regards,

How to check how many source systems are connected to my BW system?

Hi friends
how to check how many source systems are connected to my BW system?
Regards
BN

Hi All,
Thanks a lot for your help. its resolved now with your help.
Regards
BN

How PIR's are consumed by the customer requirements even though the sales orders are blocked?

Dear experts,
I am using strategy 40 for material A with Backward/Forward consumption of 60 days backward and 60 days forward.
My PIR is as follows :-
Material Month #1 Month #2 Month #3 Month #4 Month #5 ....
material A 100 100 100 100 100 ....
I created a Sales Order for material A with the quantity of 600 in Day 4 of Month #1.
After MRP run, planned order conversion and production order has been completed.
Month #1, Month #2 and Month #3 PIR's are consumed even though we made the setting in Such a way that the sales orders should just display but not planned . and the sales orders are into the blocked requirements list in the result of /n/afs/MD02.
1)but why it is consuming the PIRS?
2)is there any affect of backward and forward consumption on this?
Thanks in advance.
Regards
Bhargavi Desai

Hi,
Normally it is recommended that, not to delete PIR's one by one or remove quantity from previous periods/ requirement manually. If the PIR's of previous month is not consumed it is normally a feedback to sales people to do a analysis at their end.
In PP point of view, normally a re-organization run is carried out by MD74, MD75 or MD76. The same can be done by scheduling batch job to run on month ends basis w.r.t. period you specify.
Regards,
Narresh

How to configure rescheduling for sale order quantities

kindly explain how to configure rescheduling for sale order quantities that are created last month. kindly explain. i am in urgent.
regards,
g.v.shivakkumar

Hi,
Short text
Rescheduling sales and stock transfer documents: by material
Description
The 'Rescheduling' program (SDV03V02) processes sales document items that are contained in the item directory for the material. It takes into consideration open items and schedule lines from stock transfer items, stock transfer scheduling agreements and purchase order requests (items only), referred to hereafter as stock transfer documents, for the materials.
All sales documents for the material that are still open are selected. This means that the material index must be activated for at least all sales document types, whose items may have requirements. All stock transfer documents or items for the material that are still open are also selected. Open in this case means for example, that there is no deletion indicator, that the item from a stock transfer purchase order request cannot be labeled as completed or that the quantity delivered and posted to goods issue for the item in a stock transfer purchase order is the same as the amount ordered. An availability check can only be carried out if a checking rule is assigned to the document type - if this is not the case, the document or document item is not checked.
Checking rule 'A' is used as a basis for rescheduling sales orders (exceptions to this are rush orders they use checking rule B, and orders with individual customer stock; they use checking rule AE). Stock transfer documents use the checking rule that is assigned in Customizing for Purchasing. It is important that the scope of checks is consistent for both the stock transfer documents and the sales documents and that they do not exclude each other, as this can lead to incorrect test results. An example of an incorrect setting would be: The scope of check for checking rule 'A' checks delivery schedules for stock transfer purchase orders and stock transfer purchase requests, however the scope of check for the checking rule for the stock transport scheduling agreement does not.
The items and schedule lines found in the selection are sorted according to 'Priorities' - document category, delivery priority, creation date of the item or schedule line (for stock transfer purchase orders and delivery plans) entered on the selection screen or according to the schedule line date of the earliest schedule line with order quantity, document number and item number and then transferred to the availability check. Priority 1 is highest priority and priority 5 the lowest. Stock transfer purchase order requests are sorted after stock transfer purchase orders and scheduling agreements, as they are less binding. This means that when you have identical sort criteria such as delivery dates, the stock transfer purchase order item is checked first and then the item from the stock transfer purchase order request.
The preset option 'Unconfirmed documents required' only carries out rescheduling for materials for which there is at least one unconfirmed transaction.
You can use the parameters 'Sorting criteria delivery date' to define whether sorting is carried out with the order quantity after the creation date of the item or the delivery date of the earliest schedule line.
If you mark the 'Simulation' field, the checked documents are not saved. Instead a results list is generated and saved. However, the availability check for the corresponding documents continues as if saving has taken place already, that is, that the simulated list corresponds to the actual one.
Under 'Options' on the selection screen, specify whether sales documents and/or stock transfer documents should be processed. For stock transfer documents you can enter whether stock transfer purchase orders and scheduling agreements should be processed at item or schedule line level:
Processing at item level:
All open schedule lines for the item are read and collected, then transferred to the availability check. To sort and prioritize documents, you do not need each individual schedule line. It is sufficient to have the item or data from the first schedule line. All open schedule lines for the item are processed and checked.
Example of processing at item level:
Sorting: Date (Delivery date first schedule line) - Document number - Document item
Doc. cat. Doc. number Doc. item Doc. schedule line Delivery date PO        4500000012      10               0001              26.01. PO        4500000012      10               0002              26.02. PO        4500000025      20               0001              28.01. PO        4500000025      20               0002              02.02.
You can see that the second schedule line for document 4500000025/20 from 02.02 was processed after the second schedule line for document 4500000012/10 from 26.02. This is because all open schedule lines for an item are read and processed. The first schedule line from 4500000012/10 has the earliest delivery date, therefore it has priority.
Processing at schedule line level:
Each open schedule line for an item is entered in document sorting in accordance with the values entered under 'Priorities'. The availability check is carried out for each individual schedule line.
Example for processing at schedule line level:
Sorting: Date (delivery date first schedule line) - document number -document item
Doc. cat.    Doc. number Doc. item Doc. sched. line Del. date PO           4500000012    10             0001           26.01. PO           4500000025    20             0001           28.01. PO           4500000025    20             0002           02.02. PO           4500000012    10             0002           26.02.
Here you can see that each schedule line was sorted according to its delivery date. Note that this type of processing requires more runtime due to the individual checks and more frequent saving.
The results of rescheduling are saved, as long as the program was not started in simulation mode. When calling up from the 'Sales' area menu or when directly starting via the development environment, the iniator is informed via a dialog box that he has just started a process that changes data. He can then decide whether or not he wants to continue.
Checking procedure for stock transfer documents:
An availability check of stock transfer documents in rescheduling is carried out in accordance with the check carried out when manually creating a document. If, however, the required quantity for a schedule line is not available on a particular date and will not be ready until later, new schedule lines are created for the stock transfer purchase orders and scheduling agreements, containing the relevant data. New items are created in this case for stock transfer purchase order requirements. The total sum of schedule line quantities for a processed schedule line corresponds to the schedule line quantity of the original schedule line.
First example: Using a stock transfer purchase order item with a schedule line:
a) Status of item before rescheduling run:
Del. date PO quantity   Confirmed quant Confirmed del. date 23.07.      50 items       0 items              -
==> This now affects the stock/requirement situation:
    - Goods issue is posted for the material in the delivering plant on the 23.07.
    - A purchase order of 10 items was created for the material in the delivering plant. Delivery is expected on the 29.07.
b) Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity   Confirmed quant   Confirmed del. date 23.07.     40 items      40 items            23.07. 29.07.     10 items      10 items            29.07.
==> The first schedule line was changed in accordance with the results of the rescheduling availability check. Only 40 of the 50 original items could be delivered on the 23.07. Therefore, a new schedule line is created for the rest on the 29.07. for 10 confirmed items.
Second example: Same output situation as the above example.
==> There is now a change in the requirement/stock situation:
A purchase order for 10 items is created for the material in the delivering plant. Delivery is expected on the 29.07. A further purchase shows another 40 planned items on the 30.07.
   Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity Confirmed quant Confirmed del. date 29.07.     10 items       10 items          29.07. 30.07.     40 items       40 items          30.07.
==> The first schedule line was changed in accordance with the result of the availability check for rescheduling. The original delivery date is set to the date confirmed in the ATP check. A new schedule line is created for the remaining 40 items, that are available on the 30.07.
Note:
Any set fixed delivery date and quantity indicators and creation indicators for schedule lines or items are 'inherited' by newly created schedule lines. Assuming that the original schedule line was fixed in the above example (since it is created manually), this indicator is also set for the newly created schedule line.
If shipping scheduling is activated for a stock transfer document type, this is also implemented for newly created schedule lines, with the exception of route schedule determination. This means that in the current version of the program no route schedule has been determined for a schedule line containing a route schedule for which new schedule lines may need to be created.
The results of the run are issued in the form of a list, which is also saved, so that the results can be controlled at a later date. This is done using the function 'Evaluate rescheduling', but it is only a good idea to do this after the first rescheduling has taken place. You can restrict selection requirements but these can however affect the runtime. You can use this function to analyze the saved list until the next rescheduling run, which writes over the result. If you start rescheduling in the background, a spool file with the result list referred to will be created in the corresponding setting. You can see this in spool management.
Output
A list of changed documents, a list of documents in which an error occurred during processing and as a result were not changed, can be called up via the menu 'Edit - Error log'. If in a subsequent evaluation a restricted selection is carried out, a note appears at the end of the list to say that not all document items are displayed.
You can set the scope of the list under the menu option 'List' in the list display. You can view improvements, deteriorations and the whole list. Before the documents can be included in one or either of the restricted lists, the date or quantity has to have changed so that the item can be contained in both the list of improved or deteriorated documents.
You can use the interface for changing transactions and the order list to navigate. Use 'Back' to exit the list and 'New selection' to return to the selection screen.
Recommendation
You should only start this program occasionally and use very restricted selectin criteria during working hours as it requires enormous system resources.
Note
The columns for 'New date' and 'New confirmed qty' only contain entries if the dates or quantities have changed.
As the system only runs the change check (dates/quantities) per line in the original list, an item whose backlog has increased in the list of improvements. This occurs, for example, if the whole quantity can be delivered at once but at a later date. In this situation, the system determines an increase for the line when it compares quantities.
Regards,
Amrish Purohit

How to implement authorization at sales order/projects level?

If we open a sales order in VA02 and then try to open the same sales order in another session in VA02, there will be a message that the sales order is being processed.
I wish to implement similar functionality in my application which consists of editable report.
I tried to debug the situation in VA02 case mentioned above, to know something more about it, but could not understand anything!
I know that lock objects can be helpful in this, but in my case there can a be range of sales orders (and projects within a range of profit centers).
How to implement such a functionality?
Edited by: Ankit Modi on Dec 30, 2009 10:54 AM
Edited by: Ankit Modi on Dec 30, 2009 10:55 AM

@ Max -
Yes Max, but the problem is that I want the lock on many sales orders at a time. Its like, there is a report in which many rows (for sales orders) are editable. I want all those to be locked at a time. This will not work by Lock object, I believe...
@ Soumya -
Yes Soumya, but, as I explained above, I want a range of sales orders rather than a sales order in particular. That will not work by lock object. Right?

How can I create multiple sales orders with reference to one contract?

Hello Gurus,
Can you please how can I create multiple sales orders with reference to one contract?
thanks!
Rakesh

hi
Lets consider example
In your contract for line item 1 you have entered qty 100
You careated sales order with 70 quantity, and now you want to creat another sales order for 30
For this first you need to check what is your item category in contract (VA42)
Goto VOV7
SPRO - IMG - Sales and distribution - Sales - Sales document item - Define item categories - Go to change mode
Make the completion rule = B Item is completed after full quantity has been referenced

How to find number of sales ordered for customers made

Dear All,
Is there a standard way in SAP to know, how many Sales Orders of a particular type did customers ordered in a certain time period.
I wanted to know ? Which customer orders most orders and who ordered least.
Thanks & Regards
Venkat

Hi Venkat,
Go to [SE16]. Enter the table name as VBAK. Enter the Sales Document Type and time period in the selection screen and execute the query. Save the output into a excel sheet using System -> List -> Save -> Local File.
In excel, you can sort and group the data as per your requiremet.
Regards
Nadarajah Pratheb

How to create IDoc once Sales Order Invoice (Billing) has been created

Hi,
How to create IDoc once Sales Order Invoice (Billing) has been created ?
I.e Once you click on save button of Invoice , IDoc Should genrate Automatically.
Thanks.

Hi,
We need to do custom configuration for this scenario such that an output type will be attached when ever an INVOICE is created.
Refer to application V3 in NACE. The Output type should contain an entry with transmission medium: Distribution (ALE).
for example check the customization done for an output type in NACE.
Goto NACE ---> Select an application V3 ---> Click on processing routines ---> select the output type (Eg: RD00) ---> Click on Details button (CNTRL + SHFT + F2) which gives the configuration info.
For example we can generate the IDOC based on the settings in partner profiles for the customer (Sold To)
With Regards,
Dwaraka.S
Edited by: Dwarakanath Sankarayogi on Jan 29, 2009 8:16 AM

How to Change Division On sales order

Hii Guy,
How to change Division on sales order after been save ?
my user wrongly enter division code while creating sales order. the SO already have PGI and not yet been invoice.

Best Practice is to go PGR and then cancel Delivery.Then Go to VA02 and change the Division.
You can customize the Division at Sales Docuement Type by De-Selecting the Check Box of Item Division.It means the division will be copied from the Header Level of Customer Master Data.
Best Regards,
Ankur

How to find who deletes sales order?

Dear All:
how to find who deleltes sales order ?and When ?
Anyhelp will be appreciated!
CynthiaYu
20081221
Edited by: yu Cynthia on Dec 21, 2008 4:19 AM

Hi Cynthia
        Check in VA05 or VA05N list of sales orders also where you can see the status of the sales document
       Apart from the above this standard report will help you to some extent
        VEXP -Expiring SD Documents
    Regards
    Srinath
Edited by: sri nath on Dec 21, 2008 11:34 AM

How to find out the Sales order no based on spool no

Hi Experts,
Anyone tell me how to find out the Sales order no based on Spool no.
Thanks and regards,
Amjad

Hello Mohammed,
Please check the following SAP Spool tables for your spool request.
You will find your required document number as an Object key in these tables.
TSCMSTAT --> Field OBJNO
SOOS --> Field APPLKEY (Document number will be a part of this key)
If your document is getting printed by SAP Script, then dont forget to take SCR value in the OBJTP field while searching for your record.
Thanks and Best Regards,
Vikas Bittera.
***Points for Usefull answers ***

How to count number of sales orders generated in a month in SAP SD

Hi SD Gurus,
I have a very strange query from client. I have to count the number of sales order created in a month for a z report. For example 30 in Jan, 25 in Feb etc. Could anyone suggest me How to count number of sales orders generated in a month in SAP SD.
Regards
Vinod Kumar

Hi,
Goto the T.Code "SE16" or "SE16n" or "SE11".
Enter the table name as VBAK
Enter the created on date as the starting date of the period and to date as the end date.
Enter.
Click on "Number of Entries".It will tell you the number of entries created in a particular period.
If you want a report,goto the T.Code "VA05n".
Regards,
Krishna.

How to check how many sales orders are pending

Similar Messages

Maybe you are looking for