Dispatch time

Hi,
For one of the output type I gave parameters for Dispatch time as '3' (Send with application own transaction).
Many Invoices created with NAST-VZTYP as '3'.  I want to change(around 200 invoices) from '3' to '1' (Send with periodically scheduled job) so they will be picked by program RSNAST00.
I know how to change them manually by going through each and every invoice. But I need a program or FM which will handle all 200 invoices in one shot.
Please give me some inputs to do mass changes.
Thanks

Anyone is having suggestions regarding the above question?

Similar Messages

  • Purchase Order going to Dump if Output Message has Dispatch Time 4

    Hi All,
    We are getting a Runtime Error while saving or changing any Purhase Order, if the Output Message has Dispatch Time maintained as 4 i.e. Send Immediately.
    For all other dispatch time there is no issue. We have maintained condition record for the Message Type with Print Medium as 1 and Dispatch Time as 4. Also, the printer is maintained in the communication tab.
    No printer is maintained as default in the User Profile. No Printer is assigned to purchasing group. Our requirement is to print on the printer specified in the Condition Records itself.
    We are using Smartform, not standard SAP script for printing.
    Please suggest how we can rectify this issue.
    Regards,
    Ankit

    Hi Jurgen,
    Sorry for missing out the Dump details earlier.Please find below an extract from the dump:
    Category               ABAP Programming Error
    Runtime Errors         POSTING_ILLEGAL_STATEMENT
    ABAP Program           FRMSCM0012
    Application Component  Not assigned
    Date and Time          10.06.2014 08:30:46
    Error analysis
         There is probably an error in the program
         "FRMSCM0012".
         This program is triggered in the update process. The following ABAP
         statements are illegal here:
         - CALL SCREEN
         - CALL DIALOG
         - CALL TRANSACTION
         - SET SCREEN
         - LEAVE TO LIST-PROCESSING
         - SUBMIT
         - LEAVE SCREEN
         - LEAVE LIST-PROCESSING
         - LEAVE PROGRAM
         - LEAVE TO TRANSACTION
         - MESSAGE I/W/E (if not handeld using EXCEPTIONS ERROR_MESSAGE)
         - MESSAGE A
    How to correct the error
         Probably the only way to eliminate the error is to correct the program.
    If the error occurs in a non-modfied SAP program, you might be able to
    find a solution in the SAP Notes system. If you have access to the SAP
    Notes system, check there first using the following keywords:
    "POSTING_ILLEGAL_STATEMENT"
    "FRMSCM0012" bzw. FRMSCM0012_SF
    "SFORM_PRINT_OUTPUT"
    Information on where terminated
        The termination occurred in ABAP program "FRMSCM0012", in
         "SFORM_PRINT_OUTPUT". The main program
        was "RSM13000 ".

  • Process the output with dispatch time 3

    Dear experts!
    Thank you for your attention!
    I ues output type BA00 to print order confirmation and set the dispatch time 3
    after i save the order, where can i process the output?
    as in delivery output, we can use VL71 to process outbound delivery.
    which t-code could i use to process the order output with dispatch time 3  ???
    Best regard!
    Tangdark

    is there anyone can help???
    please~~~

  • Output determination: Dispatch time for Outline Agreements

    Hi gurus,
    I have an issue, when I am creating an outline agreement, by defaul the output message type: NEU is showed, and, it is fine, but, the dispatch time is always = 1 - Send with periodically schedule job.
    In the customising of the output NEU, I have:
    General data:
    Access sequence = 0001
    Check box active = Access conditions
    Check box active = Multiple issuing
    Print parameter = Purchasing group
    In the fine-tuned control, the "Update Print-Related data" is not active.
    And, I do not have defined any message schema for this output.
    And, then, I customised the dispatch time for NEU with the value = 4 - Print immediately, but, still is appearing the dispatch time "1".
    Then, I created 1 condition record with POrg, Doctype and Vendor, but, still is appearing the dispatch time "1".
    Could you help me with this, please?
    Kind regards,
    Sandra PF

    Hi Biju,
    The point is that this output message type does not have a "Message schema determination", for that reason, if I am creating the condition record, it will be never updated. I was doing a testing and saw it.
    But, if my message type NEU does not have any schema and according to SAP, by default will define the message type NEU, why the dispatch time is still = 1 if in the customising of NEU I have defined the dispatch time = 4?
    More ideas?
    Kind regards,
    Sandra PF

  • PO Message - Dispatch Time

    Hi,
    I have created a new message type copying data from NEU. I create a condition for this message type with the dispatch time 3 (Send with application own transaction).
    It is working fine when I create a new PO. But when I change the PO and a new message is created (Change message) the dispatch time apperas automatically with value 4 (Send immediately (when saving the application)) . I expect the value 3 as per the condition message.
    Can anyone please explain me this behavier? Is it possible to custom it in order to the system get the value 3 even when the PO is changed?
    Edited by: Alex Santana Almeida on Jul 9, 2009 1:11 PM

    IMG > MM > purchasing > Messages > Output Control > Message Determination Schemas > Define Message Schema for Purchase Order
    in step Assign Schema to Purchase Order      is a field for dispatch time for changes.

  • Output Processing. Dispatch Time: 3 ( Application own Transaction)

    Hi,
    I have created output records for an output type with the dispath time =3 (Application Own Transaction) and Transmission Medium = 8 (Special Function) and provided a processing routine to output type.
    The output records are populated in sales orders in "Not Processed" Status. My question when will the output gets processed and changes its status to "Processed" when the Dispatch Time is 3 (Application Own Transaction).

    Hello,
    In transaction V/30 there is 'Dispatch Time' tab where one option is
    'Send with application own transaction', you could create your own
    transaction to fulfill your requirements.
    I hope you find this information very helpful and hopefully it will solve your problem.
    Regards,
    Martina McElwain
    SD - Forum Moderator

  • Difference between dispatch time in po and scheduled time in job

    Hi all ,
    can any one please explain me
    what is the exact difference between dispatch time maintained in po and time/date set for job schedule
    here my question is ,i maintained dispatch time as send job with periodically in PO and i had maintained date/time in job process steps with some period.
    when po message is triggered ,which time will be consider system.time specified in job schedule or dispatch time in Po.
    which one consider first?
    Thanks
    konidala

    Dispatch time that is set up as part of the message output condition records, drives at which event does the output be transmitted. Conversely, the date/time during the batch job set up is the time when the batch job must execute the program.
    For example, if you had selected the dispatch time for output NEU in the PO to be '1' and you had set up ME9F program as a background job running daily once at 1PM, when the PO is created and saved at 10AM, the output type NEU will be triggered and will be held in queue. At 1PM when ME9F program is run as part of the background job, it'll pick up this output type for execution and transmission.

  • Regarding the 'Dispatch time' settings for output type...

    Hi Experts,
    May i know what 'Send with application own transaction' means when we configuring output type in SPRO for 'Dispatch time'.
    Cause i knew if we set it as 'Send immediately', then this output type will be triggered upon saving the orders.
    But i dont know what that item for..Could you kindly help me on this...
    What it means if we set the dispatch time as 'Send with application own transaction' for delivery output..??
    Thank you very much.

    Hi,
    If you choose 'Send with application own transaction'  when maintaining condition record for output type,during order,delivery and invoice saving the output type signal is yellow,that means unless you select that output and trigerred for printing it will not goto the spool.i.e in simple words the output is for manual printing.......
    Let me know if you need any clarifications on this..
    Regards,
    Chandra

  • Message dispatch time status 3

    Hi
    When we use Message dispatch time status 3 (Application own transaction) in PO output.
    Regards
    Ram

    Hi ,
    When you want to process the o/p manually , you go for this option .
    Processed through ME9F.
    Regards
    Ramesh Ch

  • Working with dispatcher timer

    What is the best way for use DispatcherTimer I'm when I need time for my app add one per page and stop it when the page is out but now I thinking if I use one in the App class for each when I need it, is the  best way.
    And if the way what I'm doing don't affect the performance of the app?

    The dispatcher timer, as its name cleverly suggests, is attached to the CoreDispatcher object which maintains the thread's system message queue. Once you start one, it usually never stops even if you moved away to a different page. Why>? Because the UI
    stack looks like this
    Pages you make
    Frame
    Core Window
    STA Thread with Dispatcher.
    The same dispatcher object can be accessed from several places throughout your UI. Now, all dispatcher timers are attached to this object. If you actually need one for each page, you can make it a shared resource (make a public static DispatcherTimer in
    your App.xaml.cs file) and you can access it from there.
    Unless the timers are supposed to tick at different intervals, there is no point in using more than one. Shared timers will work best. Remember, the tick event is marshalled on the UI thread and if you do intensive stuff, you will block the UI

  • Controlling time of EDI dispatch in output type for invoice

    Hi Gurus,
    I am trying to change the setting for invoice dispatch through EDI
    Currently the system is set so that invoice is sent (EDI) upon saving - and the desire it to make a manual decision when to send invoice
    I have looked at output types in SPRO - but could not figure out how to change the setting - it is not allowing me to change. Am I missing something?
    Any tips / tircks / suggestions?
    Thanks. - this is urgent as YE closing nears

    Go to V/40 .
    select the output type that you are using for Invoicing.
    double click it.
    go to Default Values tab .
           Change the Dispatch time to 1. Send with periodically scheduled job. .
    Now the invoices will be posted only when you run the program RSNAS00.
    IF this doesn't work out, Change it at COndition record level.
    Regards,
    Ajai
    Don't forget to reward points if useful.

  • Output at a specific time

    Hi Gurus,
    I have a conditioin where the user intends to Print a out put for few billing types at 4: 0 Clock.
    After lot of analysis i have come up with a suitable solution that is
    1) In the  condition record VV31 mention dispatch time = 3, i.e through application specific program.
    And run VF31 as a periodic task.
    Can you please tell me how can i run a Transaction like VF31 as  a periodic task at 4:0 clock.
    Thanks
    Monti

    Hi,
    In VF31 enter necessary data, click on Program from menu and select execute in background.
    Enter output device,printer and press enter
    Click on date/time, maintain  date and time click on check to verify  and save.
    Background job will be scheduled for your program.
    To see the job details goto T.code SM37 enter *  in job name field and enter user name click on execute, system will give the job details.
    Regards,
    Chandrasekhar.S

  • Send an output with dispath time 3, from an external report.

    Hi,
    It would be very appreciated if someone could help us with the following question:
       We have an output message in a shipment which print a form.
       This output is defined with dispatch time 3 ‘Send with application own transaction’.
       Then we have the following doubt:
           We need to create a report which the user can use for:
             1. Re-send the output (we mean print the form again) if it was already
    sent    (Status = Successfully processed)
                   2. Send the output (we mean print the form first time) if it has not been sent yet (Status = Not processed)
         Then we had thought to do a submit to RSNAST00 program, with the ‘Send again’ checkbox marked for the case 1, and with this flag empty for the case 2.
         But we have seen that this program only works with output are defined with dispatch time 1 or 2. So we think that it  would not work in our case.
    Could you help us with this, please? Do you know other program or other way to do it?
    Thanks in advance.

    No one knows?

  • Automatic DOP take more time to execute query

    We upgraded database to oracle 11gR2. While testing Automatic DOP feature with our existing query it takes more time than with parallel.
    Note: No constrains or Index created on table to gain performance while loading data (5000records / sec)
    Os : Sun Solaris 64bit
    CPU = 8
    RAM = 7456M
    Default parameter settings:
    parallel_degree_policy               string      MANUAL
    parallel_degree_limit                string      CPU
    parallel_threads_per_cpu             integer     2
    arallel_degree_limit                 string      CPU
    cpu_count                            integer     8
    parallel_threads_per_cpu             integer     2
    resource_manager_cpu_allocation      integer     8
    Query:
    SELECT COUNT(*)
    from (
    SELECT
    /*+ FIRST_ROWS(50), PARALLEL */
    Query gets executed in 22minutes : execution plan
      COUNT(*)
          9600
    Elapsed: 00:22:10.71
    Execution Plan
    Plan hash value: 3765539975
    | Id  | Operation           | Name             | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
    |   0 | SELECT STATEMENT    |                  |     1 |    21 |  2164K  (1)| 07:12:52 |       |   |
    |   1 |  SORT AGGREGATE     |                  |     1 |    21 |            |          |       |   |
    |   2 |   PARTITION RANGE OR|                  | 89030 |  1825K|  2164K  (1)| 07:12:52 |KEY(OR)|KEY(OR)|
    |*  3 |    TABLE ACCESS FULL| SUBSCRIBER_EVENT | 89030 |  1825K|  2164K  (1)| 07:12:52 |KEY(OR)|KEY(OR)|Automatic DOP Query: parameters set
    alter session set PARALLEL_DEGREE_POLICY = limited;
    alter session force parallel query ;Query:
    SELECT COUNT(*)
    from (
    SELECT /*+ FIRST_ROWS(50), PARALLEL*/
    This query takes more than 2hrs to execute
    COUNT(*)
          9600
    Elapsed: 02:07:48.81
    Execution Plan
    Plan hash value: 127536830
    | Id  | Operation              | Name             | Rows  | Bytes | Cost (%CPU)| Time     | Pstart|Pstop |    TQ   |IN-OUT| PQ Distrib |
    |   0 | SELECT STATEMENT       |                  |     1 |    21 |   150K  (1)| 00:30:01 |       |      |         |      |            |
    |   1 |  SORT AGGREGATE        |                  |     1 |    21 |            |          |       |      |         |      |            |
    |   2 |   PX COORDINATOR       |                  |       |       |            |          |       |      |         |      |            |
    |   3 |    PX SEND QC (RANDOM) | :TQ10000         |     1 |    21 |            |          |       |      |  Q1,00  | P->S | QC (RAND)  |
    |   4 |     SORT AGGREGATE     |                  |     1 |    21 |            |          |       |      |  Q1,00  | PCWP |            |
    |   5 |      PX BLOCK ITERATOR |                  | 89030 |  1825K|   150K  (1)| 00:30:01 |KEY(OR)|KEY(OR)|  Q1,00 | PCWC |            |
    |*  6 |       TABLE ACCESS FULL| SUBSCRIBER_EVENT | 89030 |  1825K|   150K  (1)| 00:30:01 |KEY(OR)|KEY(OR)|  Q1,00 | PCWP |            |
    Note
    - automatic DOP: Computed Degree of Parallelism is 16 because of degree limitcan some one help us to find out where we did wrong or any pointer will really helpful to resolve an issue.
    Edited by: Sachin B on May 11, 2010 4:05 AM

    Generated AWR report for ADOP
    Foreground Wait Events                       DB/Inst: HDB/hdb  Snaps: 158-161
    -> s  - second, ms - millisecond -    1000th of a second
    -> Only events with Total Wait Time (s) >= .001 are shown
    -> ordered by wait time desc, waits desc (idle events last)
    -> %Timeouts: value of 0 indicates value was < .5%.  Value of null is truly 0
                                                                 Avg
                                            %Time Total Wait    wait    Waits   % DB
    Event                             Waits -outs   Time (s)    (ms)     /txn   time
    direct path read                522,173     0    125,051     239    628.4   99.3
    db file sequential read             663     0        156     235      0.8     .1
    log file sync                       165     0        117     712      0.2     .1
    Disk file operations I/O            267     0         63     236      0.3     .1
    db file scattered read              251     0         36     145      0.3     .0
    control file sequential re          217     0         32     149      0.3     .0
    library cache load lock               2     0         10    4797      0.0     .0
    cursor: pin S wait on X               3     0          9    3149      0.0     .0
    read by other session                 5     0          2     429      0.0     .0
    kfk: async disk IO              613,170     0          2       0    737.9     .0
    sort segment request                  1   100          1    1007      0.0     .0
    os thread startup                    16     0          1      43      0.0     .0
    direct path write temp                1     0          1     527      0.0     .0
    latch free                           51     0          0       2      0.1     .0
    kksfbc child completion               1   100          0      59      0.0     .0
    latch: cache buffers chain           19     0          0       2      0.0     .0
    latch: shared pool                   36     0          0       1      0.0     .0
    PX Deq: Slave Session Stat           21     0          0       1      0.0     .0
    library cache: mutex X               45     0          0       1      0.1     .0
    CSS initialization                    2     0          0       6      0.0     .0
    enq: KO - fast object chec            1     0          0      11      0.0     .0
    buffer busy waits                     3     0          0       1      0.0     .0
    cursor: pin S                         9     0          0       0      0.0     .0
    CSS operation: action                 2     0          0       1      0.0     .0
    direct path write                     1     0          0       2      0.0     .0
    jobq slave wait                  17,554   100      8,942     509     21.1
    PX Deq: Execute Reply             4,060    95      7,870    1938      4.9
    SQL*Net message from clien           96     0      5,756   59962      0.1
    PX Deq: Execution Msg               618    56        712    1152      0.7
    KSV master wait                      11     0          0       2      0.0
    PX Deq: Join ACK                     16     0          0       1      0.0
    PX Deq: Parse Reply                  14     0          0       1      0.0
    Background Wait Events                       DB/Inst: HDB/hdb  Snaps: 158-161
    -> ordered by wait time desc, waits desc (idle events last)
    -> Only events with Total Wait Time (s) >= .001 are shown
    -> %Timeouts: value of 0 indicates value was < .5%.  Value of null is truly 0
                                                                 Avg
                                            %Time Total Wait    wait    Waits   % bg
    Event                             Waits -outs   Time (s)    (ms)     /txn   time
    control file sequential re        6,249     0      2,375     380      7.5   55.6
    control file parallel writ        2,003     0        744     371      2.4   17.4
    db file parallel write            1,604     0        503     313      1.9   11.8
    log file parallel write             861     0        320     371      1.0    7.5
    db file sequential read             363     0        151     415      0.4    3.5
    db file scattered read              152     0         64     421      0.2    1.5
    Disk file operations I/O            276     0         21      77      0.3     .5
    os thread startup                   316     0         15      48      0.4     .4
    ADR block file read                  24     0         11     450      0.0     .3
    rdbms ipc reply                      17    12          7     403      0.0     .2
    Data file init write                  6     0          6    1016      0.0     .1
    direct path write                    21     0          6     287      0.0     .1
    log file sync                         7     0          6     796      0.0     .1
    ADR block file write                 10     0          4     414      0.0     .1
    enq: JS - queue lock                  1     0          3    2535      0.0     .1
    ASM file metadata operatio        1,801     0          2       1      2.2     .0
    db file parallel read                30     0          1      40      0.0     .0
    kfk: async disk IO                  955     0          1       1      1.1     .0
    db file single write                  1     0          0     415      0.0     .0
    reliable message                     10     0          0      23      0.0     .0
    latch: shared pool                   75     0          0       2      0.1     .0
    latch: call allocation               26     0          0       2      0.0     .0
    CSS initialization                    7     0          0       6      0.0     .0
    asynch descriptor resize            352   100          0       0      0.4     .0
    undo segment extension                2   100          0       5      0.0     .0
    CSS operation: action                 9     0          0       1      0.0     .0
    CSS operation: query                 42     0          0       0      0.1     .0
    latch: parallel query allo            4     0          0       0      0.0     .0
    rdbms ipc message                37,948    97    104,599    2756     45.7
    DIAG idle wait                   16,762   100     16,927    1010     20.2
    ASM background timer              1,724     0      8,467    4912      2.1
    shared server idle wait             282   100      8,465   30019      0.3
    pmon timer                        3,123    90      8,465    2711      3.8
    wait for unread message on        8,381   100      8,465    1010     10.1
    dispatcher timer                    141   100      8,463   60019      0.2
    Streams AQ: qmn coordinato          604    50      8,462   14010      0.7
    Streams AQ: qmn slave idle          304     0      8,462   27836      0.4
    smon timer                           35    71      8,382  239496      0.0
    Space Manager: slave idle         1,621    99      8,083    4986      2.0
    PX Idle Wait                      2,392    99      4,739    1981      2.9
    class slave wait                     46     0        623   13546      0.1
    KSV master wait                       2     0          0      27      0.0
    SQL*Net message from clien            7     0          0       1      0.0
    Wait Event Histogram                         DB/Inst: HDB/hdb  Snaps: 158-161
    -> Units for Total Waits column: K is 1000, M is 1000000, G is 1000000000
    -> % of Waits: value of .0 indicates value was <.05%; value of null is truly 0
    -> % of Waits: column heading of <=1s is truly <1024ms, >1s is truly >=1024ms
    -> Ordered by Event (idle events last)
                                                        % of Waits
                               Total
    Event                      Waits  <1ms  <2ms  <4ms  <8ms <16ms <32ms  <=1s   >1s
    ADR block file read           24                                     100.0
    ADR block file write          10                                     100.0
    ADR file lock                 12 100.0
    ASM file metadata operatio  1812  99.0    .3    .4                      .2    .1
    CSS initialization             9                   100.0
    CSS operation: action         11  90.9   9.1
    CSS operation: query          54 100.0
    Data file init write           6        16.7  16.7                    16.7  50.0
    Disk file operations I/O     533  88.7   2.6    .6               1.5    .2   6.4
    PX Deq: Signal ACK EXT         4 100.0
    PX Deq: Signal ACK RSG         2 100.0
    PX Deq: Slave Session Stat    21  42.9  28.6  28.6
    SQL*Net break/reset to cli     6 100.0
    SQL*Net message to client    102 100.0
    SQL*Net more data to clien     4 100.0
    asynch descriptor resize     527 100.0
    buffer busy waits              4  75.0        25.0
    control file parallel writ  2003   9.3    .5          .0    .1        90.0
    control file sequential re  6466  10.6    .0    .0    .0    .1    .2  89.0
    cursor: pin S                  9 100.0
    cursor: pin S wait on X        3                          33.3  33.3        33.3
    db file parallel read         30                           6.7  30.0  63.3
    db file parallel write      1604   7.4    .1                .6  16.5  75.5
    db file scattered read       403   3.7    .2   2.5  13.6  14.9   3.5  61.5
    db file sequential read     1017  12.3    .8   2.3   7.3   6.6   2.0  68.8
    db file single write           1                                     100.0
    direct path read           522.2   2.2   2.1    .1    .0   1.8  17.9  75.9
    direct path write             22         4.5                     4.5  90.9
    direct path write temp         1                                     100.0
    enq: JS - queue lock           1                                           100.0
    enq: KO - fast object chec     1                         100.0
    enq: PS - contention           1 100.0
    kfk: async disk IO         614.1 100.0                                  .0
    kksfbc child completion        1                                     100.0
    latch free                    58  46.6  27.6  15.5  10.3
    latch: cache buffers chain    19  36.8  10.5  52.6
    latch: call allocation        26  76.9  11.5         7.7         3.8
    latch: parallel query allo     4 100.0
    latch: shared pool           111  44.1  28.8  27.0
    library cache load lock        2                                           100.0
    library cache: mutex X        45  84.4   8.9   4.4   2.2
    log file parallel write      861  10.0          .1    .1              89.5    .2
    log file sync                172   6.4                                90.1   3.5
    os thread startup            332                                     100.0
    rdbms ipc reply               18  72.2                                11.1  16.7
    read by other session          5                                     100.0
    reliable message              11  81.8   9.1                           9.1
    sort segment request           1                                     100.0
    undo segment extension         2  50.0                    50.0
    ASM background timer        1724    .8    .6    .1                      .6  97.9
    DIAG idle wait             16.8K                                     100.0
    KSV master wait               13   7.7  23.1  61.5                     7.7
    PX Deq: Execute Reply       4060    .4          .0    .0          .1   3.4  96.0
    PX Deq: Execution Msg        617  34.7   1.5   2.4   1.5   1.5    .2    .8  57.5
    PX Deq: Join ACK              16  93.8                     6.3
    PX Deq: Parse Reply           14  71.4   7.1  14.3   7.1
    PX Idle Wait                2384    .0                                  .6  99.3
    SQL*Net message from clien   103  82.5         1.0   1.9               1.0  13.6
    Space Manager: slave idle   1621                                        .2  99.8
    Streams AQ: qmn coordinato   604  50.0                                      50.0
    Wait Event Histogram                         DB/Inst: HDB/hdb  Snaps: 158-161
    -> Units for Total Waits column: K is 1000, M is 1000000, G is 1000000000
    -> % of Waits: value of .0 indicates value was <.05%; value of null is truly 0
    -> % of Waits: column heading of <=1s is truly <1024ms, >1s is truly >=1024ms
    -> Ordered by Event (idle events last)Edited by: Sachin B on May 11, 2010 4:52 AM

  • Customer invoice n delivery note print together at time of Billing

    Hi,
    Customer want invoice and delivery note attach together.
    once billing document saved invoice and delivery note print together immediately.
    plse suggest
    Thanks in advance..

    HI
    In the Out put determination maintain Those 2 Output Types and assign to the Billing Type
    At the time of maintaining the Condition record through VV31 , maintain the Dispatch time " 4" and message Transaction Medium "1"
    After that select the Line and Click on Communication Give Output Device and Tick " Print Immediately Field
    Regards,
    Prasanna

Maybe you are looking for

  • Ldb_process and PNP

    Hi, could you give me a working example of using FM LDB_PROCESS with logical dabase PNP, please? Every example, which I found there dont work and I dont know why. Thanks in advance Krzysztof

  • Is it possible for me to extract a file from my ipad through a comoputer without having to put in my ipad password

    I have forgotten my ipad password and now i cannot get to the file i need, which is a play write that is due as a school assignment on 16/06/14 Need help urgently! Help would be much apreciated

  • SWX_GET_MANAGER vs. RH_GET_ACTORS

    Hi All, Since someone deleted my inquiry yesterday, I am posting a new one now. Basically my requirement is that I need to determine the manager of the wf_initiator so that they can be used as a recipient in the send mail step. The very kind Richard

  • Ibook clamshell indigo won't go into sleep

    When I close the lid of my ibook clamshell it wont go into sleep. I tried going into system preferences and looking at energy saver and display, but Icouldn't find out how to make it go into sleep when I close the lid. Any suggestions will be appreci

  • Mini DVD files

    I was recently contacted about getting the footage from a mini DVD camcorder into iMovie. I know these cameras aren't mac compatible and I told the guy that but, does anyone know what kind of files are made when it's put onto a PC? I thought there mi