Availability quantity after changing sales order -

Hi experts,
where is the settings for availability quanity for assembly order..
problem is..
after creating sales order when we wanted to do change ..that time i am not getting availability quantity..
Thanksin Advance,
Anthyodaya...

Hello,
I hope you  are using the  Standard Assembly  to  Order strategy,in ATO if any changes in Sale order like  Delivery date, Quantity  will pass to  production Order directly,vice Versa any changes in production Order will be passed back to  Sale Order.
  Generally in ATO availability check will be carried out at component level, Based on the availability date of component , the delivery  date get adjusted.  
  Now explain me , what changes you have done in sale order, either date  or quantity, what message you are  getting  during  your availability  check.
Regards
Pradeep

Similar Messages

  • User exit for changing Sales order lines.

    Hello experts ,
    I want to delete the field "ROUTE" from all of the orders lines in sales orders, I have been using "USEREXIT_SAVE_DOCUMENT_PREPARE"  but it does not seems to do the job.
    What is the name of  user exit that i have to use for this task and which structure should be used,  is it xvbap ? is it vbap ?
    Thanks for the help.
    Avi.

    Hi,
    find the user exit u required.
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    Best regards,
    venkatawamy.y

  • Auto po creation after save sales order.

    Hi, Experts,
    A s per  my business requirement, We have mapped configuratin for auto PR creation at a time of order if stock not available, But system not create automatic PO after save sales order. I want to crate Automatic PO after save sales order, it is possible i know , But for that which type for configuration require i don't know, can anybody give me solution for this issue.
    Thankls a lot in advance,
    Regards:
    Happy

    Hi,
    It's possible to create PO automatically after sales order is saved.
    1. Set up back-to-back, i.e. PR can be automatically created after the SO is saved.
    2. Item category - make sure 'Create PO automatically' checkbox  is ticked.
    3. Enterprise Structure --> Sales Organization - ensure that PO type, purchasing group etc. is maintained.
    4. Transaction code SWETYPV - Ensure that both checkboxes are ticked for BO (object category), BUS2032 (object type), ALECREATEE/CHANGED and ERRORCHANGINGPURORD/ERRORCREATINGPURORD.
    5. Optional: You could execute BD86 to check for consistencies (note that you can still get it work even if BD86 shows errors)
    Regards,
    HweeLing

  • Propose order quantity in return sales order

    Hello Experts,
    I have a requirement where while creating return sales order with reference system should propose total delivered quantity instead of quantity in original sales order.
    I tried to copy routine 151 in VOFM but after the changes proposed quantity in return sales order is appearing as addition of original sales order quantity and total delivered quantity.
    example:
    Original sales order is having quantity = 100
    total delivered quantity = 45.
    default proposed return sales order(with reference) quantity = 100 (here system should propose 45 not 100)
    In copy routine if I change VBAP-KWMENG to 45 then in return sales order system is proposing 45 + 100 = 145 but I need system should only propose 45.
    I had searched the community but no where I found the solution.
    Please help. 

    Hi,
    The problem is we can not go with the process i.e. to create return sales order with reference to billing document as there are many other customizations already developed on existing process of creating return sales order with reference to sales order.
    So we need the solution in which return order(RE) should be created which should propose quantity as the total delivered quantity with reference to sales order.
    For the reference order only delivery document is posted in the system.

  • Every time system create new production order after releasing sales order c

    Hi Guru,
    FG material strategy: 82 (sales order creates production order).
    After creating the sales order it goes in to credit block. Whenever we release sales order from credit block through VKM1, system has created production order. We confirmed this production order and delivered.
    But after this sales person change the sales order value, because of which again sales order goes into the credit block and after releasing sales order from credit block system create new production order even if one production order already confirmed and delivered against the same sales order.
    *Every time system create new production order after releasing sales order credit block.
    Thanx & regards
    pnu

    PNU,
    So, to restate:
    In MD04, you have Unrestricted Sales order Stock ('E' Stock) on hand.
    In the same MRP segment, and against the same Storage Location as the stock, you have a Sales Order requirement that was recently blocked and unblocked.
    During the unblocking event, the system produced a new production order.
    This is not normal.  If the above accurately depicts your situation, I would look for an altered Strategy 82, or a userexit.  SAP ATP (the beginning event of the Strat 82 process) will normally first check for the availability of stock.  Only if the stock is not available, then it will create the new production order.
    Best Regards,
    DB49

  • ATP check partial Quantity allocation to Sales Orders

    Hi,
    Our client has three different sales order types for processing sales differently for the same materials.
    While doing ATP check they have a order of priority i.e ZOR1 -> ZOR2 -> ZOR3 with ZOR1 highest priority.
    For sales order type ZOR2 currently they donot have partial quantity allocation to sales orders.i.e if two orders, Order 1 created with 100 Qty and other Order 2 with 50 Qty and if ATP is 50 Qty.
    System is allocating material to Order 2 which has order quantity 50 ( Which equals ATP Qty )
    Now the client requirement is to configure system such that it does partial allocation to Order 1 ( order qty 100, where as ATP Qty is 50 ) i.e system should allocate even partial quantity to sales orders, that too in FIFO ( system should allocate ATP qty to order created first then next and so on )
    Please let me know what changes i need to do to achieve the above functionality in SAP system.
    Thanks
    Venkata Rama Reddy.K

    Dear Venkat,
    Please check the customer master for the customer which you have maintained in the 1st order. If the customer allows partial delivery, them the system will allocate the stock to the order which is created at first.
    At the time of ATP check(In Availability Screen), you do need to choose, One-time or System proposal, which will allocate the stocks partially to the 1st order as you don't have enough stock.
    Check out the settings in the customer master (for the customer in the 1st sale order) under Shipping Tab.
    Partial delivery per item  D/A/B
    Max. partial deliveries    >0
    (And more thing, you mentioned that sales document type is having priority. As of I know - there won't be any setting which will set particular sales document type with high priority. If you are really doing that kind of setting - update the same in this forum - it may help others..)
    Hope it may help you.
    (Venkat: Has your issue solved? Kindly update in the forum - if your question is answered)
    Thanks,
    Venkatesh.S.P.

  • Getting error in while changing sales order which is created using BAPI

    Hi All,
       I have created the sales order using BAPI ( BAPI_SALESORDER_CREATEFROMDAT1 ) and i am successfully creating sales order using this BAPI. But while i want to change sales order iam changing Shipping Conditions in Header Data of sales order .its giving an error .can any know any thing about this.
    Error mesage :    No status object is available for SDI 300082407/10    (Order Number/Item Number)
    In Header i  am passing these values ...
         wa_order_header_in-doc_type = vbak-auart.
        wa_order_header_in-sales_org = vbak-vkorg.
        wa_order_header_in-distr_chan = vbak-vtweg.
        wa_order_header_in-division = vbak-spart.
    Do i required to pass the below values ? in Header structure ( BAPISDHEAD1 ).
    REFOBJECTTYPE
    REFOBJECTKEY
    REFDOCTYPE
    Regards,
    Sudhakar Reddy A

    rectified

  • Problem in updating Billing plan while changing Sales order

    Hi All,
            I am using the BAPI 'BAPI_SALESORDER_CHANGE' to change a Prepaid Sale order.After calling this BAPI ,I am calling the function module <b>'BILLING_SCHEDULE_SAVE'</b> to update the Billing plan of the changed Sale order(Billing plan dates for Billing type ZF1 are changed).
         The updated date values are getting reflected in the screen when I view through the transaction VA02 and the values are also updated in FPLT table but the values are not getting reflected in the table VKDFS.
       Since the values are not getting reflectedin the table VKDFS the billing date is not correct while we view in the transaction VF04.
       Please provide your valuable suggestions for updating the Billing date in VKDFS table.
        Thanks in advance for your help.
    Thanks and regards,
    Siva

    Hi,
    I had the same problem. Here is an example code to resolve it:
    REPORT  ytestfg.
    DATA: i_bsid LIKE bsid OCCURS 0,
          i_bsid2 LIKE bsid OCCURS 0.
    TABLES: bsid.
    DATA: doc     LIKE     vbak-vbeln,
          pos(6) TYPE n.
    DATA e_fpla     LIKE     fpla.
    DATA e_fplt     LIKE     fpltvb OCCURS 0 .
    DATA: zfpla     LIKE     fplavb OCCURS 0,
    zfplt     LIKE     fpltvb OCCURS 0.
    DATA zfplt2     LIKE     fpltvb OCCURS 0 WITH HEADER LINE.
    doc = 'G03060619'.
    pos = '000010'.
    CALL FUNCTION 'SD_SALES_DOCUMENT_READ'
      EXPORTING
        document_number = doc.
    CALL FUNCTION 'SD_SALES_BILLINGPLAN_READ'
      EXPORTING
        i_vbeln                = doc
        i_posnr                = pos
      IMPORTING
        e_fpla                 = e_fpla
      TABLES
        e_fplt                 = e_fplt
      EXCEPTIONS
        no_billingplan_allowed = 1
        no_billingplan_found   = 2
        OTHERS                 = 3.
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Read the billing plan
    CALL FUNCTION 'BILLING_SCHEDULE_READ'
      EXPORTING
        fplnr          = e_fpla-fplnr
      I_VFKDAT       =
      I_BFKDAT       =
      TABLES
       zfpla          = zfpla
        zfplt          = zfplt
    Upddate the ZFPLT2 table with the new values
    MOVE zfplt[] TO zfplt2[].
    READ TABLE zfplt2 INDEX 1.
    zfplt2-afdat = '20080927'.
    Very important to set field updkz = 'U' ***
    zfplt2-updkz = 'U'. "--> UPDATE!!
    MODIFY zfplt2 INDEX 1.
    CALL FUNCTION 'BILLING_SCHEDULE_SAVE'
      TABLES
        fpla_new = zfpla
        fpla_old = zfpla
        fplt_new = zfplt2 " --> NEW
        fplt_old = zfplt.
    CALL FUNCTION 'SD_SALES_DOCUMENT_SAVE'.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    Regards,
    Edited by: PHO_BA on Mar 9, 2009 5:28 PM

  • How to change pricing Conditions in Sales order in change sales order bapi

    Hi Experts,
    How to change pricing Conditions in Sales order in change sales order bapi.
    I have used the 2 function modules bapi-changesalesorder and sd salesdocument change, But it is creating the new record , instead of changing the existing one, Could please assist regarding the same
    Thanks in Advance .
    NLN

    HI NLN
      I have just tried on my system and managed to overwrite the existing price by passing the following parameters.
      <b>Import Paramters:</b>
         SALESDOCUMENT - Sales Document Number
         ORDER_HEADER_INX - UPDATEFLAG as <b>'U'</b>.
         LOGIC_SWITCH - Import Structure - Pass 'X' to LOGIC_SWITCH-COND_HANDL.
      <b>Tables:</b>
         CONDITIONS_IN - ITM_NUMBER,
                         COND_COUNT, -> Condition counter same as KONV-ZAEHK generally it is <b>'01'</b>
                         COND_TYPE,
                         COND_VALUE,
                         CURRENCY.
         CONDITIONS_INX - ITM_NUMBER,
                          COND_COUNT,
                          COND_TYPE,
                          UPDATEFLAG as <b>'U'</b>,
                          CURRENCY.
       Hope i have clarified your query.
    Kind Regards
    Eswar

  • End User Transaction for Mass Change Sales Orders

    Hello,
    Transaction MASS can be used to change sales orders using object type BUS2032, however, end users are not allowed access to MASS.
    In most other cases, the object types can be accessed by individual transactions, for example, MEMASSPO for BUS2012 and XD99 for KNA1.
    But I cannot seem to find a similar transaction for object type BUS2032, does anyone know whether one exists or how to create such a shortcut.
    Thanks,
    Jake.

    Hi
    See SAP Note 483303 - BUS2032: Only sales orders of category VBAK-VBTYP = 'C'
    Regards
    Eduardo

  • How To Get The Total Delivered Quantity of a Sales Order

    Hello All,
    I have a requirement of getting the total delivery quantity of the sales order .I have checked it in LIps table but I am getting partially delivered quantity for a schedule line item.Can any one tell me how to get the total delivered quantity.
    Regards,
    Pavani.

    Hi
    Check the Table:
    VBEP  - Sales Document: Schedule Line Data.
    Inside the table check the Quantity Fields.
    Regards,
    Sreeram

  • Confirmed quantity in the sales order coming as 3.5 ea

    Hi Gurus
    The confirmed quantity in the sales order coming as 3.5 ea where the order quantity was 10ea.I checked CUIN for EA the decimal places is given as 0 which is very much correct moreover I checked the material master in additional data I have not find anything abnormal.The order was created by a batch job.Please help.

    Hai,
    The system has concluded that 3.5 EA for the confirmed quantity means the remaining part of the stock are already allocated to some other sales orders.Out of 10 EA only 3.5 EA are  in the stock.
    You can view through the MD04 and then enter the plant ,material and then check the quantity that are allocated to the various orders.
    Please revert for any.
    Kalyan

  • Need logic for calculate the balance quantity in open sales order

    hi all
    i need logic to calcuclate the balance quantity in open sales order ,
    where i am using VBAK header and VBAP item , and VBFA for document flow tables
    i need to have the balance quantity , for the open sales order
    especially taking with respect to  VBFA-VBTYP_N = M for invoice creation and N for canellation
    any one please help me

    thank you but i am clear abt it
    will you please anyother way to calucaluate the logic ,
    and i need to populate in bukets also for the terms of 5 years
    Edited by: sridhar loganathan on Nov 25, 2008 6:43 AM

  • Changing Sales Order PARTNER from 'MASS' transaction

    Hi,
    I have a requirement to change partner details (e.g. SHIP TO party  from SH1  to  SH2) for sales order. I need to use tcode 'MASS' (Mass maintainance)  for BUS2032.  But it does not have the option to change partner details.
    Can anybody let me any approach to achieve this. If we can do it through a config or may be creating a custom business object etc...
    I could found out the thread below talking about the same issue, but there is no solution to that. I want to build the solution around SAP standard and not interested for BDC/LSMW/CATT  etc.
    Mass changes Sales order partners
    Thanks,
    Madhu
    Edited by: Madhu K on Nov 1, 2011 11:58 PM

    Alan
    I am ok to create a custom tcode for MASS.  Do I need to copy the BUS2032  or the whole TCODE?
    My major concern is,  how to get the VBPA structure to the selection screen so that it ll show me  the I/P fields to enter Old  Ship to  and  New ship to..
    Can You please give me some idea on this.
    Thanks
    Madhu

  • Manual quantity allocation per sales order

    Hi All,
    The requirement is as follows.
    My client want users to allocate quantity for sales order manually so that they can control quantity allocation for sales orders when there is shortage of stock.
    We do not want to use product allocation for this, So can anyone suggest if there is any other way to allocate the stock manually for sales order.
    Thanks in advance,
    JM

    Hi,
    This can be acheived by enhancement.
    You can use userexit MV45AFZB -userexit_source_determination for this.
    You need to maintain the Z-table for all the bottleneck material with confirmation quatity column.
    So everytime when you create a sale order for bottleneck material, system will check this table & irrespective of any order quantity, it will confirm the quantities mentioned in the table.
    This way you can maintain the logic & fullfil the above requirement
    thank you

Maybe you are looking for