Triggering output type(Bringing it to unprocessed state )

Hi All,
I have one output type. I want to trigger that output type and then bring it to an unprocessed state.
Please let me know how can I achieve the same.
My requirement is that, after the output type is triggered, I have to process the output type and get the PDF.
This part can be done. All I want is ,,,to bring the output type to unprocessed state.
Please  suggest the needful.
Regards
Rudra

set nast-vstat = 0

Similar Messages

  • 'Send Aplication with Own transaction ' for triggering Output Type

    Hi All,
    Can anyone let me  know how the option 'Send Applicaion with own transaction'  for triggering output type works?
    Thanks in Advance,
    Savitha

    just F1 on the Dropdown list box, you get some help from there.

  • Triggering output type when sales order is saved

    Hello all,
                I have a small question. Whenever I create a drop ship sales order it triggers a custom output type and prints the form by default even though this output type hasnt been saved in the sales order messages. Similarly from a drop ship PO when it is created with reference to the drop ship order and a requisition it tries to call this cusotm output type and prints the form.
    Please advice how to find the settings and make it not print this form.
    Thanks in advance.

    Hello,
             There are few other custom output types configured for a sales order. I wonder why it picks this particular output type and prints the form.
             If I uncheck 'Print Immediately' then would it stop from just printing or even calling the form too.
              Please advice if there might be any other config which tells to call this particular form whenever a drop ship sales order is created.

  • Triggering output type from VL02N

    Hi,
    I need to attach some kind of routine to VL02n.
    The requirement is that in VL02N, on goods issue, an output type is supposed to be triggered.
    Please suggest me as to how to trigger this output type on goods issue.
    The functionality is like this.......on triggering the output type, idocs are generated. SO i need to write a routine sort of from where i can trigger and then write the idoc related code

    Hi,
    just follow this link..it might be useful...
    [Automatic Output Type from VL01|http://wiki.sdn.sap.com/wiki/x/BY-jBw]
    Regards
    Kiran

  • Creating/Triggering Output Type from program

    Hi,
    When I am creating Inbound Delivery using VL31N tcode, an Output type associated with it triggers automatically.  But my problem is that I have stopped the triggering of Output type automatically while saving Inbound delivery. and want to create mannually through program.
    Is there any FM or any other way to do through program.
    best regards
    bobby

    Hi
    Below link is for your reference
    [create output type reference|http://www.interfax.net/en/help/sap_sd_mm_module.html]
    hope it will help you.
    Regards
    Natasha Garg
    Edited by: Natasha Garg on Feb 5, 2009 7:25 AM

  • Triggering output type using ABAP code

    Dear Friends,
    I am trying to trigger an output type by submitting RSNAST00 with all the required input in one of my ABAP program and I am getting error messages. See the code which I have written below and help me to resolve this issue. Also, suggest me if we have any alternate methods to do it:
          ranges: range_kappl for nast-kappl,
                  range_objky for nast-objky,
                  range_kschl for nase-kschl,
                  range_nacha for nast-nacha.
          move: 'I'         to  range_objky-sign,
                'EQ'        to  range_objky-option,
                vttk-tknum  to  range_objky-low.
          append range_objky.
          move: 'I'         to  range_kappl-sign,
                'EQ'        to  range_kappl-option,
                'V7'        to  range_kappl-low.
          append range_kappl.
          move: 'I'         to  range_kschl-sign,
                'EQ'        to  range_kschl-option,
                'ZNM7'      to  range_kschl-low.
          append range_kschl.
          move: 'I'         to  range_nacha-sign,
                'EQ'        to  range_nacha-option,
                '2'         to  range_nacha-low.
          append range_nacha.
          submit rsnast00
            with s_kappl in range_kappl
            with s_objky in range_objky
            with s_kschl in range_kschl
            with s_nacha in range_nacha
            and return.
    Thanks & regards,
    Mallikarjuna M

    Use below subroutine.
    Fill nast structure with whatever data you have.
           PERFORM einzelnachricht_dialog(rsnast00) USING lv_rcode.
    Advantages of using this are
    1. If Output already exists and it waiting it will not submit new one.
    2. You can control user name,date,time in nast entries.

  • Triggering Output Type

    Hi,
           I have a report program which displays all the delivery. If select a delivery and press a print button (customized one), then the delivery has to be printed.
    I am using BAPI_LIKP_PROCESS_MSG_DIRECT to print the delivery.
    Now the problem is, only when i goto the delivery (VL02N) ->Extras--> delivery output->header and press save, I am able to print the delivery. Else i am getting Error message <b>'No messages for initial processing exist'</b>. I think i need to trigger the output type from the report and then print the delivery using BAPI.
    Can any one tell me how to trigger the output type from the report? Is any FM or BAPI available ?
    Regards,
    Niyaz

    Hi Niyaz...
    For this req:
    You have to
    1. Maintain the Condition records in NACE.
    2. call the Standard report RSNAST00 from ur Report with all the Required selection criteria.
    Eg: Submit RSNAST00 with ...............
    <b>reward if Helpful.</b>

  • One question on triggering output type....

    Hi Experts,
    If we configure the output type with option u2013 4 (SPRO)u20184 Send immediately (When saving the application)u2019 and then in the condition record (NACE) we maintain option u2013 3.
    So finally which one will be taken in the document??
    Thank you very much.

    Hi there,
    As per the system logic, anything maintained in condition technique, system will default the values from the condition records. So in your condition records in NACE, change the transmission medium inthe condition records.
    One thumb rule. , whatever the settings are there in the condition type, maintain the same in condition records sothat system doesnot behave in a peculiar way.
    Regards,
    Sivanand

  • Error while triggering program through output type while saving invoice

    Hi,
    I have a scenario where in my Z program needs to be triggered when saving a invoice.
    For that we have attached out Z program to output type which gets picked while saving invoice.
    In the Z program we have written the entire code in Form Entry subroutine.
    In the Z program we have called a FM "SD_SALESDOCUMENT_CREATE", to create a sales order.
    After sales order is created we have used a Commit statement.
    If I run the Z program individually, Salesorder gets created perfectly.
    How ever as per scenario when trying to save the invoice, output type gets picked. But program doesn't get called.
    and when I go to the saved the invoice I get the following error immediately:
    "Error document - Update was terminated"
    I have found that the problem is with COMMIT statement through transaction SM13.
    Can anybody help me with this. I cannot save the sales order without COMMIT, so I have to use it.
    Thanks in Advance,
    Rohan.

    Hi Rohan,
    I have worked on almost similar kind of requirement as you. 
    "Error document - Update was terminated" is because saving of invoice is done in u201CUpdate Tasku201D. Again in that work process, FM also calls for update task, which is not allowed and give short dump.
    Here are two different approaches to cope up in this scenario.
    1.Call FM in NEW TASK.
    Calling Function module in new task will assign new work process and will use different update task.
    Use:
    CALL FUNCTION 'SD_SALESDOCUMENT_CREATE' STARTING NEW TASK 'task'
    This will not give update termination error.
    Call of FM in this way will work, but as this will be asynchronies call you will be not able to get status/message out of the FM call result.
    If capturing return message is mandatory, use below approach
    2, Process output type via Job
    Set output type, dispatch time u201CSend with periodically scheduled jobu201D in u201CDefault valueu201D tab.
    Run batch job for program u201CRSNAST00u201D with appropriate variant.
    Please let me know if you need any further details.
    Best Regards,
    Nisarg

  • Output type is not getting triggered for ship to party in shippment output

    Hi,
    we have maintained output determination procedure for shipments. It was working fine.
    We have just added new condition table to access sequence, and maintained the condition records also for condition type ZABC. I have checked in NACE, Application V7, I am able to find the condition type. checked in VV73, condition records displayed. But in VT02N/VT03N, we are unable to get print for  the output type.
    Why this is happening? we are able to see the procedure, condition type, access sequence, condition records in place ...why condition type ZABC is not getting triggered in the shipment output.
    Please advise and let me know if you need more details....thanks in advance.
    Thanks,
    SS

    Hi Noel,
    Thanks for your time and reply.
    We have output determination procedure for shipments, condition type ZABC, Access sequence ZABC, Condition tables 550,600,650,700 already maintained. output is working fine.we have a new requirement and created new condition table 700 with the fields" Ship to party and transportation planing point "(Condition table 700 ). we assigned the condition table 700 to access sequence ZABC. Condition type  ZABC already placed in Output determination procedure.
    We test the output, new condition record is not triggering in the output, even in output determination analysis also, we are unable to see the record 700 for the condition type ZABC. we are not sure what is the reason for the condition table that  is not picking up ? Why condition type ZABC with condition record 700 not visible in output determination analysis.
    I have checked condition records, output determination procedure. Please advise and let me know you need more details.
    Thanks,
    SS

  • Delivery Output type newly created not triggering

    Hi,
    I have created 2 new output types i;e 1 for returns Order and one when we save the Delivery order. This i have copied the standard output type (BA00 & LD00).
    so now in returns order the output type i want to trigger automatically and print. But it is not happening. In VV11 i have defined for this condition as Print immediately and in customizing also i have maintained for sales organisation. But it is NOT triggering automatically when i save the return order. If i manually go and add this output then its working. So can you please tell me what needs to be done to trigger automatically.
    Secondly for Delivery i have 2 output i;e when i save the delivery without picking and all in VL01N, it should trigger 1 output and second is when i do the picking and PGI in VL02N. Both should trigger automatically.Now both my output is triggered only when i do PGI in VL02n i;e VL01N output is not triggered.
    Please help how can i do that.

    Hi,
    Go to T-code NACE
    Application area : V2-Shipping
    Now select the condition records and select your new output types.
    Take the key combination defined by you Viz. Sales org/Delivery Type (for example
    Enter Medium as '1'
            Date/Time as '4'
    Press the communication Tab and Tick Print immediatley and release after output Check Box.
    Also maintain the output device as LOCL
    I hope this will help you
    Br,
    Tushar

  • Debugging the program that will get triggered for a particular output type

    Hi all,
             I have one program,which will get triggered when a Sales order of type 'VOR' is created.Whenever 'VOR' order is created it will trigger the 'ZALT' output type.And this output type 'ZALT'has been configured to my program.This output type configuration has been set up by my functional consultant.
    My problem is I created Sales order of type 'VOR'.But I want to debug my program,which has to be triggered because of that 'VOR' sales order type,which in turn triggers 'ZALT' output type and in turn triggers my program.
    My problem is I created Sales order of type 'VOR' by keeping debugging point in my program.But it is not going to my program and simply displaying sales order has been saved.
    So is the outtype has been configured properly?.Do I need to go to my functional consultant?Could anyone explain in this regard?
    Rgds,
    Balaji

    Hi Balaji,
    If possible, try to repeat the output in the output type messages screen of VA02 and change its dipatch time to '1'(Through further data). Now put the break point in the program assigned to output tye 'ZALT'(You can see this in the TNAPR table) and run the program RSNAST00 through SE38. The program will stop at the break point.
    If its not possible to repeat the output and if you want to check it the first time the output type is processed, ask the functional consultant to change the dispatch time in the condition record that is being retrieved for proposing the output type to '1'. Now run RSNAST00. The program will stop at the breakpoint.
    Thanks,
    Vinay

  • Output type maintained but not getting triggered

    I have created a Z output type for scheduling agreement(application EV) which  triggers an idoc and maintained it in NACE but it is not getting triggered automatically with the conditions.Is there any more settings that has to be done??
    Edited by: nevinphilip on May 17, 2010 10:35 AM

    Dear,
    Maintain condition record to your combination in t.code MN07
    Regards,
    Gopala.S

  • Output type Requirement triggering

    Hi,
    In my project I have a requirement to stop triggering of an output type if all the items in the sales order have reason for rejection set.
    I have done the condition check in a output requirement routine and if the condition fails then I set SY-SUBRC = 4.
    Problem 1:
    But when I am creating the sales order, the komkbv1 structure does not have the sales order no. (it has other fields) and kompbv1structure is not filled. Then how do I check if all the items have Reason for rejection set or not.
    Problem 2:
    For an existing sales order, I trigger the output type in Header-->Output... , this code is getting executed and sy-subrc is set to 4. But still the output is triggered.
    Please let me know how do I proceed.
    Code:
    w_vbeln = komkbv1-vbeln.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        INPUT         = w_vbeln
    IMPORTING
       OUTPUT        = w_vbeln .
    Atleast one item of the Sales Order does not have
    reason for rejection set.
    select single * from VBAP
    where vbeln = w_vbeln and
          ABGRU eq space.
    if sy-subrc ne 0.
       sy-subrc = 4.
       EXIT.
    endif.
    Thanks in advance,
    Vishnu Priya

    Hi,
    For the first problem,
      Check the standard structures available, but not sure.
    For the Second one,
      You routine include should be included in the standard include RV61BNNN
    for it to get triggered.
    Your routine will not get executed if your routine is not included in this standard include.
    Hope this helps.

  • Invoice output type getting triggered after setting SY-SUBRC = 4 in routine

    Dear Friends,
    When ever invoice document is generated, if the invoice document is completed and if its accounting document is generated successfully, we need to trigger an output type for invoice ZRD0
    For this purpose, we have created a routine 902 in our system. If the required condition, mentioned above, fails then SY-SUBRC set as 4 else set as 0 to trigger the output type.
    Currently we are facing a problem, even after setting SY-SUBRC as 4 in routine 902, output type ZRD0 getting triggered.
    Please help me to fix this bug.
    Thanks a lot.
    Best regards,
    Amol Chaudhari.

    Hello Aditya,
    I have maintained same code in both routines 'kobed_902' and 'kobev_902'.
    Required code maintained in the routine,
    sy-subrc = 4.                          " Do not trigger output type
    * If the posting document is created or Billing document canceled    *
    * and if invoice document is Completely processed then the output    *
    * type ZRD0 is Triggered.                                            *
      IF komkbv3-uvall CA gc_c.   "Invoice document is complete or not
        IF komkbv3-rfbsk CA gc_ce.   "For VF01 and VF11
          sy-subrc = 0.
        ENDIF.
      ENDIF.
    We are getting this problem on production client and not able to generate the scenario on quality.
    The output type is actually an EDI output type which is generating an IDOC for the invoice.
    Thank you.
    Best regards,
    Amol Chaudhari.

Maybe you are looking for