Tcode for Sales Order Output(collective processing)

Hi
What is the tcode or program to print sales orders collectively, similar to VL71 for deliveries & VF31 for invoices.
Regards
Uma

Hi Uma
There is no such T code for sales order print.
You can use SE38-> run RSNAST00 program for sales order output (collective processing).
try and revert.

Similar Messages

  • Table for Sales Order - Output Type - Processing Check

    Hi all,
    We have around 300 Sales Order, where we need to check weather Sales Order Acknowledgement (Custom) Output Type is processed or not?
    With the help of condition record setup we beleive all the Sales Order have got the output type assigned, but we need to know, is there any way from any SAP table, we can check the output is processed or not.
    Also, let me know is there any way some table can we check, all the sales order have got the output type assigned?
    <Text removed by Moderator. Priority normalized.> Please help.
    Thanks
    RS

    You can use Table NAST.
    Field
    Field Desc
    Reference
    KAPPL
    Application
    Application type
    V1 - Sales
    V2 - Shipping
    V3 - Billing
    OBJKY
    Object key
    Sales Order - Header Output
    Sales Order + Item - Item Output
    KSCHL
    Message type
    Output Type
    PARNR
    Partner
    Customer Number
    PARVW
    Partner Role
    Partner Function - SP
    NACHA
    Transm. Medium
    MANUE
    Msg. manually
    DATVR
    Processing date
    UHRVR
    Processing time
    USNAM
    User name
    VSTAT
    Processing status
    LDEST
    Output Device
    TCODE
    Communication strategy
    OBJTYPE
    Object type
    BUS2032 - Sales Order
    LIKP\LIPS - Delivery-Header\Item
    VBRK\VBRP - Billing-Header\Item
    Thanks, JP

  • Tcodes for Sales order confirmation, Adv  shipping notification, del note?

    i wanna  know   where  do  we create  sales  docs  like shipping notification, delivery schedule, invoice or billing document, po confirmation , sales order confirmation etc etc.  which   are  not the  regular    sales  documents like  the sales  order(va01), delivery (vl01n), billing (vf01)  which   have their  regular  Tcodes.  so i wanna   are  there   tcodes  which  can create  the above   documents . i guess not. so  how  do  we create these  and  send  them to  our  customers
    thanks
    n. bhardwaj
    SD

    Hi Neha,
    Just look in table TSTC and TSTCT for the transactions. In these tables you can search based on the description.
    Regards,
    Atish

  • Re: Sales Order OUtput( V**) v/s Billing Output ( VF31)

    Hello Friends,
    In Standard SAP, we have VF31 - Output from Billing , where we can choose the Invoice we would like to print.
    I would like to have the same functionality for Sales Order Output.
    In Standard SAP , there is no such functionality where we can choose the Sales orders which we want to print.
    Pl. let me know what type of enhancement would be required to achieve the above mentioned functionality.
    Thanks a lot in advance,
    Julie.

    Hi,
    There are two options for you.
    1.Using the standard program "RSNAST0D".
    Goto SE38,Enter the Program name as "RSNAST0D".
    Execute or press F8.
    In the selection screen,Enter the Application as "V1".Selection type as "2(for repeated processing)".
    Execute.
    You can make this one as a T.Code also by using the transaction SE93.Ask your ABAPer for this.
    You can use the program "RSNAST0F" for monitoring the incorrectly processed output".
    2.For VF31,it uses a standard program "SD70AV3A".
    Make a copy of this one and change the necessary tables etc. for this so that the screen is also similar to our VF31.For this ask your ABAPer to develop a Z program.
    Regards,
    Krishna.

  • How to print one sales order output from two printers using single command.

    Dear all,
    Our requirement is to print single sales order from two different printers, where as one printout for sales order output and another for sales order cash receipt.
    We developed two smartforms for both outputs.
    But we are struggling to assign the smartforms to single document type, which has to result two printouts after saving the sales order.
    Please help us to solve the issue.
    Your suggestions will be highly appreciated.
    Best regards
    Raghu ram

    Hi,
    You should define two different output type for your requests, one is for SO output, the other is for SO cash receipt. That's okay!
    Good luck
    Z.T

  • Processing of Sales order output type BA00 processes another Z output type for acknowledgement.

    Hi Friends,
    I am facing below mentioned issue and request your suggestion to solve it
    Via processing of sales order output type BA00 another Z output type is processed and acknowledgment is sent to SAP inbox( sost).
    This is working incase of manual addition of BA00 output type and via standard program " sd70av1a", but this functionality is not working when i am calling this standard program in a Z report via batch job.     
    with the below code-
    DATA: name TYPE tbtcjob-jobname.
             DATA: number  TYPE tbtcjob-jobcount.
             DATA: print_parameters TYPE pri_params.
             name = 'ORDER_PRINTING'.
             CLEAR: range1.
    *REFRESH: range.
             range1-sign = 'I'.
             range1-option = 'EQ'.
             range1-low = 'BA00'.
    *        range1-high = 'ZBA1'.
             APPEND range1 TO range.
             CALL FUNCTION 'JOB_OPEN'
               EXPORTING
                 jobname          = name
               IMPORTING
                 jobcount         = number
               EXCEPTIONS
                 cant_create_job  = 1
                 invalid_job_data = 2
                 jobname_missing  = 3
                 OTHERS           = 4.
             IF sy-subrc = 0.
               SUBMIT sd70av1a WITH  rg_kschl IN range
                               WITH  rg_vbeln IN order_tab
                               TO SAP-SPOOL
                               SPOOL PARAMETERS print_parameters
                               WITHOUT SPOOL DYNPRO
                               VIA JOB name NUMBER number
                               AND RETURN.
               IF sy-subrc = 0.
                 CALL FUNCTION 'JOB_CLOSE'
                   EXPORTING
                     jobcount             = number
                     jobname              = name
                     strtimmed            = 'X'
                   EXCEPTIONS
                     cant_start_immediate = 1
                     invalid_startdate    = 2
                     jobname_missing      = 3
                     job_close_failed     = 4
                     job_nosteps          = 5
                     job_notex            = 6
                     lock_failed          = 7
                     OTHERS               = 8.
                 IF sy-subrc <> 0.
                 ENDIF.
               ENDIF.
             ENDIF.
           ENDIF.
    In this case only BA00 is getting processed but Z output type created for sending acknowledgment is not triggered.
    Please suggest how can i achieve the required functionality.
    Thanks,
    Surya

    Solved myself..
    Thanks.
    Br,
    Surya

  • Collective Outputs for sales orders

    hi,
    Please can anybody help me to find out the outputs collectively for Sales Order.

    Hi I asked a similiar question and this was the answer i received from PJ and it worked for me
    Hi Paul,
    SAP has provided a Standard Program,SD70AV1A for Mass printing of Sales Orders. Give the same to your ABAP team and ask them to assign a T-Code to this program.

  • Archiving Process for Sales Order

    Hi,
    We have this new client. Archiving was previously working & has suddenly stopped. Logs are also unavailable as they have been erased.
    We just have a list of Batch Jobs which contain the following Programs.
    1. RSARDISP - The Scheduling Job
    2. S3VBAKWRS - Archiving Program (Input or output error in archive file /oracle/STP/ixos/exchange/RSD04210.220142.BATCHBA)
    3. RSARCH_STORE_FILE
    We need to run these batch jobs, in order to find out where the error is occurring.
    We can see the old already archived documents, by ckicking on Enviorment -> Display Originals on VA02 screen
    Questions:
    1 What is the sequence in which we need to run these programs?
    2.Is this the entire list of steps in order to enable archiving for Sales Orders
    3.I am not sure if SARA is being used to schedule, or is it just these Batch Jobs with the programs. How can I know the exact process that was employed previously
    Any assistance is Appreciated
    Thanks

    Hi
    If you don't have any documentation, I suppose that you are using the object SD_VBAK, and your client is using SARA. Check these points:
    - The settings for the auth.objects are in tcode AOBJ. See the reports for preprocessing, archiving and deletion. You must mantain selection variants to call them with SARA.
    - See mantain networks graphic. You must archive and delete all documents in the flow before to archive SO.
    - See the settings in tcode VORA (customizing tcodes) where you do the settings for residence time (Number of days which must elapse in order to archive the sales document).
    I hope this helps you
    Regards
    Eduardo

  • What are the User Exits for Sales Order creation process?

    Hi,
    what are the User Exits for Sales Order creation process? how can I find them?
    thanks in advance,
    will reward,
    Mindaugas

    Please check this info:
    User Exits In Sales Document Processing
    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
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    Regards
    Eswar

  • Default Output Type for Sales Order Header

    Hi Guru
    I created 2 output types for hardcopy printout and for mail.
    I want both should be selected as default when a sales order is created. (using NACE)
    Output will be manually from VA02 -> issue output to. Here I must get 2 output types.
    As of now, this is manual process. 
    Please help.
    sunil Kolambkar.

    Hi Sunil,
    For this you need to maintain condition record for output type. for the sales order type, [V V11].
    Do the output determination in the same way as Pricing procedure determination.
    OUTPUT DETERMINATION:
    SPRO- IMG- Basic Functions- Output Control- Output Determination- Output Det using Cond Tech- Output Det for Sales Documents & output det for billing documents.
    Create Condition Table: select the field Sales Doc Type from field catalog & Save
    Maintain Access Sequence: 4-digits code & description.
    Assign condition table to access sequence. Select Accesses line item and Go To Fields. Fields will display the fields we have selected in the condition table i.e. sales doc type.
    Maintain Output Types:
    AF00: Inquiry
    AN00: Quotation
    BA00: Order Confirmation
    LD00: Delivery
    Select BA00 & Copy & Rename. Give the same 4-digit code as given to acc seq.
    You Can Maintain:
    Languages of Output
    Partners (to whom we want to send output)
    Print Program- print specification
    Sap Script- layout
    Assign Output Types to Partner Functions: go to new entries & assign your output type to partner functions.
    Maintain Output Determination Procedure: V10000 (Standard Procedure). Go to new entries & create your own 6-digit code with descp. Select the procedure & go to Control Data. Here mention the output type i.e. cond type & leave requirement and manual only columns as blank.
    Determination Rule: link the 6-digit procedure code to doc types.
    Create Condition Records: VV11. Select document type and click on Communication. Mention partner function, medium, time. Output device: LP01, Spool request Name: SD_003, Suffix 2: order_confir & flag on print immediately.
    Once you press enter you will come across 2 key combinations:
    Sales organisation/ Customer Number: fill SO, Customer No, Partner Function Abbreviation, Partner to whom the output should be sent, time, medium, language. {It contains: Sales Orgn, Customer, Partner Function (The abbreviated form of the name that identifies the Partner) (During output determination, the system determines the recipient of the output from the master record for the specified partner function. In this field, you can explicitly specify a recipient that will override the standard partner. There must also be a master record for the partner that is specified explicitly.), Medium, Time & Language.}
    Order Type: Document Type, Partner Function (abbreviation), Partner, Medium, Time & Language.
    Hope this would be helpful.
    Regds,
    Rupali

  • T-Code for Sales order mass output

    Hi Friends,
    I have 150 SOs. In which I need to process the output again. Checked the MASS trx for this but could not find any option?
    Is there any otherway we can process the output at one shot?
    Regards,
    Ram

    Hi,
    Just like we have the T.Code "VF31" for billing documents,we don't have any such T.Code here for "Sales orders".But there is a procedure.
    That is:
    Goto the T.Code "SE38".
    Enter the program name as "RANAST00".
    Execute.
    Enter the application as "V1".
    Enter the output type also.
    Check the tick box "send again".
    Execute.
    Regards,
    Krishna.

  • T Code for doing mass output for Sales order like VL71 for Delivery

    Hi
    Can anyone let me know what is the t code for the sales orders for which despatch time was set as "3- using own transaction"
    Muthu

    Hi,
    Though there is a program, there is no output for sales order similar to VL71 for delivery. Sales order is the only transaction for which there is no tcode for this purpose.
    You can do the following.
    Go to SE38 give program name SD70AV1A and execute
    Now give ur selection criteria and save this as a variant.
    Now you can schedule a job at regular intervals using this variant.
    This will enable that if you maintain the output record as 3(using own transaction), the output will be created in mass for multiple sales orders.

  • Down Payment processing for Sales orders using Milestone Billing Plan

    Hi,
    The business scenario is as follows.
    The delivery for the sales orders are to be created only after the pre payment( a percentage of the total sales order value) is made by the customer.
    Hence the sales orders while creation are blocked for delivery creation using credit block by means of a userexit.
    The credit manager checks the blocked sales orders using VKM1 transaction and verify if there are any payments made by the customer to cover this pre payment to be made.
    If it is enough to cover then he releases the sales order manually for delivery creation.This is a complex process since there are too many sales orders and the payments made by the customer may not match the amount to be paid(it can be greater or lesser).The customer just pays a huge amount which is to be distributed among the sales orders for pre payments.
    Later, when the invoice is created, the customer account is cleared manually using F-32 transaction for the oldest open invoices.
    Here again there is a huge manual effort involved since he need to distribute the amount against the invoices using oldest open item principle.
    As a solution we are planning to implement "Down Payment processing for Sales orders using Milestone Billing Plan".
    Is this the right solution?
    Can you please give the steps in detail to implement this functionality for above scenario?
    We are using SAP 4.7 version without Project Systems.
    Thanks in advance.
    Regards,
    Ragesh

    Hi Ragesh
    Check the links where you will get the entire down-payment configuration
    [https://forums.sdn.sap.com/post!replydownpayments ]
    Regards
    Srinath

  • Output type attchment not displaying for sales orders

    Hi,
    Output type attachment is not showing form some orders NACE is perfectly configured 10 out of 100 not showing in
    output type as attachement rest of ordrs showing attafchemtns.
    How to do where to find out.

    Hi..
    Check Transaction " V/43" whether sales order output type and procedure are defined or not for a particular order type.
    Regards,
    Lokeswari.

  • Auto Replishmnet process for Sales Orders

    Hi,
    Can any body suggest, how we can follow "Auto Replishmnet process for Sales Orders" for Particular customers with for required articles.
    Please suggest replishment process for sales orders.
    Regards
    Kiran kovi

    Hi,
    This process is available in SAP Retail. Help says you can use it for manufacturing as well.
    You can read up more about VMI: Customer replenishment here:
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/86/37e622f09b11d18ca1080009d10d9a/content.htm
    Hope that helps!
    Regards,
    Naveen

Maybe you are looking for