DYNPRO_SEND_IN_BACKGROUND In VL09

Dear all ,
  While canceling the Reverse Goods movements , am getting Pop-UP  Updated Was Terminated ,
How to Solve this Issues.
I checked the error. Its Showing
Screen output without connection to user.
What happened?
Error in ABAP application program.
The current ABAP program "SAPMV50A" had to be terminated because on
statements could not be executed.
This is probably due to an error in the ABAP program.
During background processing, the s
screen to a user.
Current screen: "SAPMV50A " 4004.
If the error occurred in one of your own programs or in an SAP prog
that you modified, try to correct it yourself.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yours
use the following search criteria:
"DYNPRO_SEND_IN_BACKGROUND" C
"SAPMV50A" or " "
"SYSTEM-EXIT"
Kindly through some lights .
Thanks & Regards ,
Shankar GJ
Edited by: Shankar GJ on Aug 14, 2009 7:43 AM

Hi,
The problem seems to be that you are trying to perform a foreground action in a background process. As stated by Raymond check all your active user exits and wherever necessay suppress the dialog(s) by using system variable SY-BINPT .
   Meaning whenever there is a background process running do not call any dialog screens ,which requires user action.
    Ex- Calling FM "popup_to_confirm" in user exits - requires some user action .
Hope this helps.
- Krishnan

Similar Messages

  • Error while posting a cancelling a delivery through VL09 in WM

    Hi Guru's,
    We have WM set up i have created a return sales order and the return deliivery to the customer and i have made a trnasfer and the stock is place in the permanent from the interim bins (904) and then PGR.
    Now i want to cancel that material document and the delivery, while doing VL09 reversal of material document i am getting an error "Storage bin 101 904 5190000000 does not exist.
    But for the reversal movement type 652 i have set it has a dynamic bin creation means it should take delivery number 5190000000 has the dynamic bin but it is not creating.
    Can any one help me in this

    you just have a big problem.
    I think the only way you have is to create the quant with zero quantity in this interim bin with IT options: direct table maintenance. 
    Then you do a LT01 to move the stock from permanent bin to the interim bin.
    For this table maintenance you have to be very carefull as you need to create the LQUA entry with exact the content that is stored as WM data in LIPS table to your delivery.

  • How to reverse PGI @ VL09 for delivery with subsequent invoice

    Greetings
    Our business process sometimes requires billing to happen prior to PGI.
    Hence, we have modified copy control settings to allow billing based off delivery creation (rather than PGI delivery).
    No modifications to the item categories and we are using standard movement types 601/602
    My issue is at VL09.
    VL09 will not allow me to reverse without cancelling the billing document.
    I get a message No data available for these selection criteria
    I have checked OMJJ movement type settings and I dont see anything here.
    Can anyone point me in the right direction to customize such a setting if it exists?
    We are using ECC 6.0
    thank you
    Ken

    hi
    your issue as standard behavior , when delivery document  billing status completed ,  you can not do the PGI , when you cancel the billing document then only system will accept PGI ,
    when you cancel the billing document , delivery document billing status will change , so accept PGI
    this status comes based on billing document types , like final billing (f2) delivery billing status comes complete, proforma invoice completed then delivery billing status comes not yet proceed
    this is the why system not accept the PGI for final billing document done
    check proforma billing document delivery PGI
    Regards
    sankar

  • Excise Duty Group not being populated during VL09 in MSEG-ROITAXGRPtable

    Hi,
    When we do the PGI (601 movement type), the data gets updated in MKPF & MSEG tables.During this process the details pertaining to ED group(field ROITAXGRP) are not updated in MSEG.
    The above factor has the following connection to 602.
    Subseqently when we do VL09 - the data pertaining to PGI (601) is imported from MSEG & hence ED group does not get populated as the system takes the material document of 601 to reverse the delivery document
    We need to know the following things.
    1. When we are doing delivery (Movt type 601) ,excise duty group gets updated in which field and table?
    2. When we are reversing the document why in the MSEG table ROITAXGRP field (Excsie Duty Group) not getting updated.
    3. Is there any User Exit which can be usd to populate this . We are using version 4.6c (IS-OIL) version ?
    regards,

    Thanks,
    K.Kiran

  • DYNPRO_SEND_IN_BACKGROUND when submitting a background job, when creating a

    Hi.
    We create sales orders via EDI.   When certain sales orders are created, we execute user exists on the Sales Order save.  During the User Exit, we submit/create (job_open_adk function, the submit command, and the job_close_adk function) a background job. 
    The background, is created and executed successfully, but we get 2
    short dumps everytime.
    The short dump is:
    DYNPRO_SEND_IN_BACKGROUND
    The description is:
    Screen output without connection to user.
    The short dump is for the user WF-BATCH.
    I've used DEBUG and the shortdump occurs on the submit command.
    submit zsd
    to sap-spool
    destination 'null'
    immediately ''
    keep in spool 'X'
    without spool dynpro
    and return
    user l_user via job tbtcjob-jobname
    number tbtcjob-jobcount
    with p_vbeln = l_order
    with p_ebeln = l_po
    with p_uname = l_user.
    Nothing should be displayed on the screen.
    I used 'without spool dynpro' to prevent the 'Print Screen List' window
    from appearing.
    I've put this code into a TEST program. I ran the test program
    myself. (under my ID) The program run perfectly. No
    shortdump.
    Similar code is used in other programs and it works perfectly - no shortdumps.
    The short dump occurs when we use ALE/EDI to create a sales order.
    The short dump has the ID WF-BATCH on it.
    I'm guessing the problem is with the WF-BATCH ID. Are printer setting
    missing on a Work Flow ID?
    Any ideas why the 'without spool dynpro' parameter doesn't work for the
    WF-BATCH ID?
    I've tried searching OSS and I looked at the on-line help/documentation
    on Submit. I saw a recommentation to use the
    fuction 'GET_PRINT_PARAMETERS' to set all of the print parameters. I
    tried this, but still got the short dumps.
    Any suggestion on how I can run the Submit command and not get a short dump?
    thanks,
    Michelle

    Hi,
    Try this notes:
    0100915 RSBDCREO: System hangs or parameters not effective
    0377038 HR-CA-ALE: DYNPRO_SEND_IN_BACKGROUND for HR doc. d
    0105165 Dump "DYNPRO_SEND_IN_BACKGROUND" in prog.SAPMSSY0
    0169303 Warning messages displayed for settlement mass pro
    0428489 VL10: Dump 'DYNPRO_SEND_IN_BACKGROUND' with backgr
    [[http://forums.sdn.sap.com/thread.jspa?threadID=14875|http://forums.sdn.sap.com/thread.jspa?threadID=14875]]
    Regards
    HM

  • Taking Long Time To cancel any document on vl09

    Hi,
       In vl09 PGI/Delivery cancellation(when i cancel any document),Taking very long time.can i have to check any coding on program.guide me for the same.
    Thanku

    You can do an SQL trace via ST05 and analize to see what statements are taking that long... you can give this to your ABAPer to amend any faults on the coding or indexes.
    regards
    Juan

  • Error  Screen output without connection to user  DYNPRO_SEND_IN_BACKGROUND

    Hi Experts
    I am  trying to debbug a BADI (for shc)  in SRM 7.0 with external debugger.
    I placed a breakpoint in the BADI, and logged into the portal screen,it is  independent portal.
    when i start to create the shc i get the error:     Screen output without connection to user
    if i delete the breakpoint it work well.
    the user i work with, has a developer key and SAP_ALL.
    Runtime Errors      DYNPRO_SEND_IN_BACKGROUND
    Exception              CX_SY_SEND_DYNPRO_NO_RECEIVER
    Thanks
    Almog
    Edited by: almog126 on Jul 14, 2010 3:00 PM
    Edited by: almog126 on Jul 14, 2010 3:00 PM

    did you solve this?
    We have now the same problem with any external debugging (WebServices/WebDynpro).

  • DYNPRO_SEND_IN_BACKGROUND  SAPLSPO1 or LSPO1U06   POPUP_TO_CONFIRM

    Hi
    Request you all to go through the dump,
    |What happened?                                                                               
    |
    |
    Error in the ABAP Application Program                                                    
    |
    |                                                                                             
    |
    |
    The current ABAP program "SAPLSPO1" had to be terminated because it has                  
    |
    |
    come across a statement that unfortunately cannot be executed.                           
    |
    |What can you do?                                                                             
    |
    |
    Note down which actions and inputs caused the error.                                     
    |
    |                                                                                             
    |
    |                                                                                             
    |
    |
    To process the problem further, contact you SAP system                                   
    |
    |
    administrator.                                                                           
    |
    |                                                                                             
    |
    |
    Using Transaction ST22 for ABAP Dump Analysis, you can look                              
    |
    |
    at and manage termination messages, and you can also                                     
    |
    |
    keep them for a long time.                                                               
    |
    |Error analysis                                                                               
    |
    |
    During background processing, the system attempted to send a screen to a                 
    |
    |
    user.                                                                                   
    |
    |                                                                                             
    |
    |
    Current screen: "SAPLSPO1 " 0500.                                                        
    |
    |                                                                                             
    |
    |
    Additional system information:                                                           
    |
    |
    "currently running as cpic server"                                                       
    |
    |                                                                                             
    |
    |How to correct the error                                                                     
    |
    |
    If the error occurred in your own ABAP program or in an SAP                              
    |
    |
    program you modified, try to remove the error.                                           
    |
    |                                                                                             
    |
    |                                                                                             
    |
    |
    If the error occures in a non-modified SAP program, you may be able to                   
    |
    |
    find an interim solution in an SAP Note.                                                 
    |
    |
    If you have access to SAP Notes, carry out a search with the following                   
    |
    |
    keywords:                                                                                
    |
    |                                                                                             
    |
    |
    "DYNPRO_SEND_IN_BACKGROUND" " "                                                          
    |
    |
    "SAPLSPO1" or "LSPO1U06"                                                                 
    |
    |
    "POPUP_TO_CONFIRM"                                                                       
    |
    |                                                                                             
    |
    |
    If you cannot solve the problem yourself and want to send an error                       
    |
    |
    notification to SAP, include the following information:                                  
    |
    |                                                                                             
    |
    |
    1. The description of the current problem (short dump)                                   
    |
    |                                                                                             
    |
    |  
    To save the description, choose "System->List->Save->Local File                       
    |
    |
    (Unconverted)".                                                                          
    |
    |                                                                                             
    |
    |
    2. Corresponding system log                                                              
    |
    |                                                                                             
    |
    |  
    Display the system log by calling transaction SM21.                                   
    |
    |  
    Restrict the time interval to 10 minutes before and five minutes                      
    |
    |
    after the short dump. Then choose "System->List->Save->Local File                        
    |
    |
    (Unconverted)".                                                                          
    |
    |                                                                                             
    |
    |
    3. If the problem occurs in a problem of your own or a modified SAP                      
    |
    |
    program: The source code of the program                                                  
    |
    |  
    In the editor, choose "Utilities->More                                                
    |
    |
    Utilities->Upload/Download->Download".                                                   
    |
    |                                                                                             
    |
    |
    4. Details about the conditions under which the error occurred or which                  
    |
    |
    actions and input led to the error.                                                      
    |
    |                                                                                             
    |
    |System environment                                                                           
    |
    |
    SAP Release..... 731                                                                     
    |
    |
    SAP Basis Level. 0005                                                                    
    |
    |                                                                                             
    |
    |
    Application server... "lecc-prd-10"                                                      
    |
    |
    Network address...... "172.18.218.141"                                                   
    |
    |
    Operating system..... "Linux"                                                            
    |
    |
    Release.............. "2.6.32-220.2.1.el6.x"                                             
    |
    |
    Hardware type........ "x86_64"                                                           
    |
    |
    Character length.... 16 Bits                                                             
    |
    |
    Pointer length....... 64 Bits                                                            
    |
    |
    Work process number.. 8                                                                  
    |
    |
    Shortdump setting.... "full"                                                             
    |
    |                                                                                             
    |
    |
    Database server... "lsdb-prd-2"                                                          
    |
    |
    Database type..... "ORACLE"                                                              
    |
    |
    Database name..... "EP1"                                                                 
    |
    |
    Database user ID.. "SAPSR3"                                                              
    |
    |                                                                                             
    |
    |
    Terminal.......... " "                                                                   
    |
    |                                                                                             
    |
    |
    Char.set.... "C"                                                                         
    |
    |                                                                                             
    |
    |
    SAP kernel....... 720                                                                    
    |
    |
    created (date)... "Jan 15 2013 18:18:58"                                                 
    |
    |
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr121116"                        
    |
    |
    Database version. "OCI_112, 11.2.0.3.0, V1, default"                                     
    |
    |                                                                                             
    |
    |
    Patch level. 401                                                                         
    |
    |
    Patch text.. " "                                                                         
    |
    |                                                                                             
    |
    |
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"          
    |
    |
    SAP database version. 720                                                                
    |
    |
    Operating system..... "Linux 2.6, Linux 3"                                               
    |
    |                                                                                             
    |
    |
    Memory consumption                                                                       
    |
    |
    Roll.... 0                                                                               
    |
    |
    EM...... 12569424                                                                        
    |
    |
    Heap.... 0                                                                               
    |
    |
    Page.... 16384                                                                           
    |
    |
    MM Used. 10030984                                                                        
    |
    |
    MM Free. 2535400                                                                         
    |
    |User and Transaction                                                                         
    |
    |
    Client.............. 100                                                                 
    |
    |
    User................ "EWMONECC"                                                          
    |
    |
    Language key........ "E"                                                                 
    |
    |
    Transaction......... " "                                                                 
    |
    |
    Transaction ID...... "530F7949A5601689E1000000AC12DA41"                                  
    |
    |                                                                                             
    |
    |
    EPP Whole Context ID.... "005056B976AF1ED3A8902D8CE1BD4303"                              
    |
    |
    EPP Connection ID....... "53109D4E863D7FBCE1000000AC12DA42"                              
    |
    |
    EPP Caller Counter...... 1                                                               
    |
    |                                                                                             
    |
    |
    Program............. "SAPLSPO1"                                                          
    |
    |
    Screen.............. "SAPMSSY1 3004"                                                     
    |
    |
    Screen Line......... 2                                                                   
    |
    |
    Debugger Active..... "none"                                                              
    |
    |Server-Side Connection Information                                                           
    |
    |
    Information on caller of Remote Function Call (RFC):                                     
    |
    |
    System.............. "EP1"                                                               
    |
    |
    Installation Number. 0020694200                                                          
    |
    |
    Database Release.... 731                                                                 
    |
    |
    Kernel Release...... 720                                                                 
    |
    |
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)                       
    |
    |
    Call Type........... "synchronous and transactional type Q (emode 0, imode 0)"           
    |
    |
    Inbound TID.........."AC12DA8A728B531098C05738"                                          
    |
    |
    Inbound Queue Name..."DLWSWP1CLNT1008000001383"                                          
    |
    |
    Outbound TID........." "                                                                 
    |
    |
    Outbound Queue Name.." "                                                                 
    |
    |                                                                                             
    |
    |
    Client.............. 100                                                                 
    |
    |
    User................ "EWMONECC"                                                          
    |
    |
    Transaction......... " "                                                                 
    |
    |
    Call Program........."SAPLIRFC"                                                          
    |
    |
    Function Module..... "TRFC_QIN_DEST_SHIP"                                                
    |
    |
    Call Destination.... "lecc-prd-10_EP1_00"                                                
    |
    |
    Source Server....... "lecc-prd-10_EP1_00"                                                
    |
    |
    Source IP Address... "172.18.218.141"                                                    
    |
    |                                                                                             
    |
    |
    Additional information on RFC logon:                                                     
    |
    |
    Trusted Relationship " "                                                                 
    |
    |
    Logon Return Code... 0                                                                   
    |
    |
    Trusted Return Code. 0                                                                   
    |
    |                                                                                             
    |
    |
    Note:                                                                                    
    |
    |
    - For Releases < 4.0, information on the RFC caller not available.                       
    |
    |
    - The installation number is available from caller Release > 700                         
    |
    |                                                                                             
    |
    |
    Additional information on RFC logon:                                                     
    |
    |
    Trusted Relationship " "                                                                 
    |
    |
    Logon Return Code... 0                                                                   
    |
    |
    Trusted Return Code. 0                                                                   
    |
    |                                                                                             
    |
    |
    Note: For releases < 4.0, information on the RFC caller are often                        
    |
    |
    only partially available.                                                                
    |
    |Information on where terminated                                                              
    |
    |
    Termination occurred in the ABAP program "SAPLSPO1" - in "POPUP_TO_CONFIRM".             
    |
    |
    The main program was "SAPMSSY1 ".                                                        
    |
    |                                                                                             
    |
    |
    In the source code you have the termination point in line 248                            
    |
    |
    of the (Include) program "LSPO1U06".                                                     
    |
    |Source Code Extract                                                                          
    |
    |Line |SourceCde                                                                              
    |
    |  218|
    PERFORM append_icon_to_button                                                      
    |
    |  219|       
    USING
    icon_button_4                                                     
    |
    |  220|                
    l_quickinfo_button_4             
    "*048i                      
    |
    |  221|       
    CHANGING button_4.                                                         
    |
    |  222|  ENDIF.                                              
    "974439  <<                 
    |
    |  223|                                                                                       
    |
    |  224|                                                                                       
    |
    |  225|* Aufbereitung des Fragetextes und Berechnung der Dynprogröße                          
    |
    |  226|  PERFORM format_text TABLES text_tab1                                                 
    |
    |  227|                 
    USING fragetext.                                                 
    |
    |  228|                                                                                       
    |
    |  229|  PERFORM calculate_screen_size                                                        
    |
    |  230|         
    USING                                                                    
    |
    |  231|            
    textlength                                                            
    |
    |  232|            
    start_spalte                                                          
    |
    |  233|            
    start_zeile                                                           
    |
    |  234|         
    CHANGING                                                                 
    |
    |  235|            
    tab_len1                                                              
    |
    |  236|            
    tab_len2                                                              
    |
    |  237|            
    end_spalte                                                            
    |
    |  238|            
    end_zeile                                                             
    |
    |  239|            
    dynpro_nummer.                                                        
    |
    |  240|                                                                                       
    |
    |  241|                                                                                       
    |
    |  242|* Aufruf der Dialog-Dynpros                                                            
    |
    |  243|                                                                                       
    |
    |  244|  CALL SCREEN dynpro_nummer STARTING AT start_spalte start_zeile                       
    |
    |  245|                       
    ENDING   AT end_spalte   end_zeile.                        
    |
    |  246|                                                                                       
    |
    |  247|                                                                                       
    |
    |>>>>>|  answer = antwort.                                                                    
    |
    |  249|ENDFUNCTION.                                                                           
    |

    Hi Madan,
    I'm suggesting you for SAP Note  1265724 - BAPI technically close PO: Dump DYNPRO_SEND_IN_BACKGROUND
    1739959 - DYNPRO_SEND_IN_BACKGROUND
    Try to update kernel patch with the latest one available.
    Need more info regarding which program or report you are executing .
    Thanks,
    Gaurav

  • During cancellation of delivery document using VL09

    Hi,
    I want to cancel only 3 items out of 5 items from the delivery document at the time of cancellation by using VL09..
    How can i do that??
    Rgds,
    Pavan.

    No. Not other way out. The method suggested above is the best possible method.
    As PGI is done for whole Delivery Document, Cancel / reverse of PGI is also done for the whole Delivery Document. You cannot cancel / Reverse partial Line items in Delivery.
    Hope this clarifies,
    Thanks,
    Jignesh Mehta

  • Error while reversing goods issue using VL09

    Hi All ,
      user is getting the error " 4902546971document does not contain any selectable items "  when reverse the GI using  VL09.
    Please find the below document flow.
    Free of Charge 70475917 / 10
    . Purchase order 9900099037 / 10
    . Delivery Standard 80721176 / 10
    .. Shipment 199662 / 1
    .. WMS transfer order 12862453 / 1
    .. Pro Forma Invoice 90070497 / 10
    .. GD goods issue:delvy 4902546971 / 1
    Regards,
    Amar

    Hi,
    Try to reverse the gods issue, with VL09, for document "Delivery Standard" with number 80721176
    Free of Charge 70475917 / 10
    . Purchase order 9900099037 / 10
    . Delivery Standard 80721176 / 10
    .. Shipment 199662 / 1
    .. WMS transfer order 12862453 / 1
    .. Pro Forma Invoice 90070497 / 10
    .. GD goods issue:delvy 4902546971 / 1
    Regards,
    Amar

  • PGI reversal VL09 not happening

    hi
    user has done following cycle
    1.ME21N-PO document type UB and Item cat I.
    2.VL10B- Outbound delivery
    3.VL06G-goods issue using automatic MVT 647 and 101)
    4.VF01-Performa Invoice(billing Type JEX)
    5.J1IIN- Excise invoice.
    In billing base price is missing because of that all duties and net price zero.now user wants to cancel entire cycle. he has done excise cancellation using J1IH. we are not able to reverse billing using VF11, we are not able to PGI reversal using Vl09. it giving error "No dat available for your selection".
    Note: is it problem of JEX because we have not assigned cancell billing type and doc pric procedure to JEX?
    any solution for the above issue.

    Hi rising sun.,
                               VF11 is not for reversal of the billing doccument it is fo cansellation & when you want to cansel the billing doccument first the accounting doccument for t hat billing doccument should be canselled,after you cansel the billing doccument reverse the goods issue in VL09and reject in VL02n,then VA02 reject the doccument
    As you are saying that no data available then go to VF04 and see whether your delivery doccument is there & VF05  to see t he Billing doccument
    If you are ablr to see the doccuments you can cansel them
    J1IH is to cansel the excise doccument
    REWARD if helpfull
    Thanks & Regards
    Narayana

  • PGI reversal not happening in vl09

    hi
    user has done following cycle
    1.ME21N-PO document type UB and Item cat I.
    2.VL10B- Outbound delivery
    3.VL06G-goods issue using automatic MVT 647 and 101)
    4.VF01-Performa Invoice(billing Type JEX)
    5.J1IIN- Excise invoice.
    In billing base price is missing because of that all duties and net price zero.now user wants to cancel entire cycle. he has done excise cancellation using J1IH. we are not able to reverse billing using VF11, we are not able to PGI reversal using Vl09. it giving error "No dat available for your selection".
    Note: is it problem of JEX because we have not assigned cancell billing type and doc pric procedure to JEX?
    any solution for the above issue.

    Proforma Invoice cannot be reversed. But also it will not stop you from reversing PGI. Check the document flow & ensure that the correct number is being used to cancel the PGI.
    Once PGI is cancelled, you can futher cancel the Delivery.
    Regards,
    Rajesh Banka

  • STO Post goods issue reversal using vl09 not happening.

    hi
    user has done following cycle
    1.ME21N-PO document type UB and Item cat I.
    2.VL10B- Outbound delivery
    3.VL06G-goods issue using automatic MVT 647 and 101)
    4.VF01-Performa Invoice(billing Type JEX)
    5.J1IIN- Excise invoice.
    In billing base price is missing because of that all duties and net price zero.now user wants to cancel entire cycle. he has done excise cancellation using J1IH. we are not able to reverse billing using VF11, we are not able to PGI reversal using Vl09. it giving error "No dat available for your selection".
    Note: is it problem of JEX because we have not assigned cancell billing type and doc pric procedure to JEX?
    any solution for the above issue.

    the optional solution can be as following steps:
    1) create the bin manually with ls01n: storage type 904, bin name is the delivery number,
    2) reverse with vl09 and a material doc will be created.
    3) check the bin stock with ls24, you will see negative stock in 904.
    4) create TO to offset this negative qty with lt06 with above mentioned material doc. this TO's source bin is just the one in regular storage type.
    5) confirm TO
    6) don't forget to delete the bin created in step 1,  this is because it is created manually but not dynamic bin that will dissapear automatically.
    pls reward if helpful.

  • Reverse PGI of delivery using VL09

    Hi ,
    My query is while reversing the delivery using VL09 it has check invoice has cancelled or not . For pro forma invoices we have put the code in MV50AFZ1 to check billing document cancelled(completed) or not . It is working fine and  showing the error message what we have given but in background it is reversal happening.
    When we check in MKPF table for material document (MBLNR) the reversal data updated.
    can you please explain .

    Hi,
    i quess Userexit in MV50AFZ1 is working for VL09? did you check if the userexit is also called (and working correctly) when calling the programm in background?
    regards
    Stefan Seeburger

  • Unable to reverse goods ..using vl09

    Hi Experts,
    we have created order , bill and delivery in production and we made one small mistake and cancelled the bill when we try to cancel the delivery using vl09 - goods movement reverse i am getting the message  no data available when i check the  billing status it says C-completed and also movement status aslo C.  how can i  reverse the goods its there any other way ....
    Thank you for your help in advacne....
    Regards,
    Venki

    Hi
    one small mistake and cancelled the bill
    If you are sure that  your first bill is cancelled there will be another bill having the cancelleation number
    Are you seeing that in document flow
    If that has happened the original invoice will have a posting status as E and not C as per your thread
    when i check the billing status it says C-completed
    I feel that your cancellation process has not been done properly
    Once this is cancelled properly the delivery status will be set to BEING PROCESSED from COMPLETED
    Then you can reverse it in VL09
    Make sure that you have executed cancellation properly
    Regards
    Raja

Maybe you are looking for

  • ITunes 7.5 messes up audio configuration

    I'm kind of stuck in a hole here. With the previous iTunes version, I could not access the iTunes store for some reason. I upgraded my iTunes to 7.5, but now, every time I try and open it, it says it has detected a problem with my audio configuration

  • How to accept changes in Vendor master record as an accounting clerk?

    I made some changes in vendor master records and they are yet to be confirmed by accounting clerk!! so , how can I do that in my development system?

  • Classpath error in webdynpro application

    Hi All, Currently I am using NWDS7.0.16, and I created webdypro application which connect to BI System by make use of BI-  XMLA connector. for that I added all required jar file in JavaBuild path. but when i try to build the application I am getting 

  • Not enough comp memory

    I have a 30 gb ipod, but not that much space on my laptop. is there a way I can load music on to my ipod, delete it from my laptop, then load different music on to my ipod, and still keep all of it from deleting from my ipod?

  • Director 11 and SW 11

    I have published a movie which compresses a sound. It works great in my ".dir" but when published as a ".dcr" or ".htm", the compression does not work. The publisher of the audioXtra said that shockwave may not be using the correct information from t