Prevent creation of a delivery document

Hi,
We are making a delivery through project( Trx CNS0)
A reservation is created for a material in project 1 and project 2 for plant stock and a storage location is specified.
The material in question is available for 100 pc in the storage location.
When we create delivery for project 1 ( 100 pc) , system allows the creation of delivery document.
It also allows the creation of delivery for project 2 ( 100 pc) , eventhough the total stock is only 100 pc.
However , after PGI has been done for project 1 , system issues an error message " deficit stock" for project 2 at PGI.
We have maintained 01-daily requirements in MRP3 view.
We want to prevent creating a delivery document when there is no sufficient stock and do not want to wait until PGI is done.
Please suggest how can we achieve this .
Thanks,
Manohar

Thanks for your reply.
We are making delivery through project ( using Trx CNS0).
The sales order is for , say, supply of 1 no of building.
The parts are delivered to site , in knocked down condition or in various assemblies. For this , we use Trx CNS0 and pick the project stock / plant stock items and then create outbound delivery documents.
To answer your questions :
1) Is the requirements check box ticked in your schedule line category (VOV6) -. Not ticked for Category LP.
2) In availability check control whether include sales requirements check box is ticked (OVZ9).
There are many entries under 01-daily requirements. How does the system pick for deliveries through project ? is not clear to me. We have not created any new checking rules.
3) In delivery item category availability check off is not X (0VLP). Relevant for picking is flagged.
Expecting further replies,
Thanks,
Manohar

Similar Messages

Help Rgd. BAPI for Creation of Inbound delivery Document

Hi all,
I need a Bapi to create inbound delivery document without using PO reference. I have seen the below BAPIs. i) BAPI_IBDLV_CREATE_FROM_OBDLV,
ii) BAPI_GOODSMVT_CREATE. I am not sure whether they are for creating inbound delivery document without using PO reference.
It will be of great use if anyone can give me the BAPI for the purpose and the mandatory parameters or sample test data for the BAPI.
Thanks in Advance,
Rakesh.

If you create the inbound delivery->check the purchase order in the tabstrip "Confirmations" on item level. There are three fields: "Confirmation control key", "Order acknowl." and "acknowl. required".
Ckeck if there is a value in "confirmation control key".
You should get the same error if you try to create VL31N in dialog mode, not only by using the bapi.
Rgds,
JP

BAPI for Creation of Inbound delivery Document

Hi
I have found a BAPI for Creating Inbound delivery Document, BBP_INB_DELIVERY_CREATE. I filled the below parameters and executed it.
IS_INB_DELIVERY_HEADER
    DELIV_DATE                     11.04.2007
IT_INB_DELIVERY_DETAIL
            MATERIAL                       1096
            VEND_MAT
            MATL_DESC                      SHARP CAMERA111
            DELIV_QTY                               795,000
            UNIT                           KG
            PO_NUMBER                      4500000011
            PO_ITEM                        00010
I recieve a error 'This function is only possible for items with confirmation key'.
I dont know whether the error is with the data. Is there any other fields to be filled.
It will be of great help if anyone provide me with any input. ;>)
Thanks in Advance
Rakesh

If you create the inbound delivery->check the purchase order in the tabstrip "Confirmations" on item level. There are three fields: "Confirmation control key", "Order acknowl." and "acknowl. required".
Ckeck if there is a value in "confirmation control key".
You should get the same error if you try to create VL31N in dialog mode, not only by using the bapi.
Rgds,
JP

Preventing manual entry in delivery document.

Hi ,
Is there any solution regarding how the manual entry can be stopped in delivery document?
Thanks & regards,
Rupam.

Hi Rupam,
If you solved the problem, close your thread.
Thanks,
Gordon

Delivery document archieved

For a stock transfer invoice, dellivery document cancelled without cancelling the excise invoice. Is there any solution to prevent from cancelling the delivery document without cancelling the excise invoice

Hi,
I think you can still cancel the excise document.
However, if you need a check here, you need to put the same through a user exit at Delivery change/delete level. Take help of an ABAPer for the same.
Regards,
Peeyoosh.

Outbound delivery document from Sales order

Hi ,
While creating the outbound delivery document from Sales order, all the line items of the Sales order are populated in the Delivery document. The line items where stock is not available, the line is still populated in the delivery document with zero quantity.
Pls suggest the way in config, so that at the time creation of the delivery document system to populate only the lines with the available stock.
Thnx

Hello Soumya
I could not able to find any std transaction or config via you could restrict it. However you also no till 'Picking' not completed user is not able to make postings... so i couldnt see any issue in this.
Still you need to restrict this, you to configure User Exit via you can restrich the lin items to come in delivery for no stock item.
Amol

Cancellation of Delivery Document

Hi everyone,
I would like to ask if there is a way to correct a posted Delivery document without having to re-create the reference Sales Order document. Here's the scenario: Upon creation of a Delivery document, the user has forgot to change the delivery quantity before posting it. (human error)
Example:
Sales Order Qty = 10
Delivery Qty = 8 (Partial Delivery)
The Delivery Document has been posted in B1 with 10 as the quantity. If we try to create a Return Document for the 2 quantity which was not served, we cannot anymore create a new Delivery Document for the remaining 2 because the reference Sales Order document is already closed. Is there a way we can serve the remaining 2 without having to create a new Sales Order and just used the same Sales Order? Any suggestions will be appreaciated (either thru SDK or thru a workaround)
Thanks in advance.
Malu

Hi Malu,
There is no workaround either you make a return of 2 and again delivered 2 directly or return 10 and create a new sales order of 10 quantity a better option will be to return 10 and create new sales order.
I hope SAP will come up with solution on this as these is a commen scenerio required.
Thanks
Kamlesh

Delivery Document creation using buffered data?

We're using BAPIs to create an STO with estimated volumes/dates.
But, when the Actual information comes in, we first update the STO with actual volume, then create a delivery document. The problem is that the delivery document is using the estimated volume even though we've committed the volume change and can pull up the STO to see it prior to Delivery create.
For STO, we're using:
BAPI_PO_CREATE1 and
BAPI_PO_CHANGE
For Delivery creation, we're using:
BAPI_OUTB_DELIVERY_CREATE_STO
It seems that the Delivery is reading buffered information rather than what's actually been committed to the DB. Is there a way to bypass the buffer when calling this BAPI?
thanks,
Robert

Found a note that has addressed the issue
2008537 - Short dump while changing a replenishment delivery multiple times in one transaction

Delivery document creation after Posting of Goods through Purchase Order

Dear All,
Could you please help me out by letting me know how to create a delivery document flow i.e. entry in VBFA table after Posting of Goods through PO, I have Inbound delivery document that I know & also a succssfull Material document that is created and can be viewed through Purchase order history BY USING ME23N transaction code.
so please let me know is there any way to create a delivery by inputing delivery no., Material Doc & Material Doc year
Thanks,
Sanjay

Additonally:
At the time of GR the inbound delivery ican be updated in MIGO also if you set the suitable indicator in:
SPRO > LE > Shipping > Basic Shipping Functions > Configure Global Shipping Data (V_TVSHP-SPE_INB_VL_MM)
(see OSS note 1050944)
Even though you implement this change or w/o this change post the GR in VL32N, you won't get the document flow in table VBFA.
You can use table EKBE to get the necessary information.
Regards,
Csaba

Delivery document creation using vl01n

Hi,
I want to create a delivery document using VL01n.i need to create the doc for a particular selected item if there are many items for the order.i want to delete the remaining documents.
how to handle this in BDC.

just mention along with order ...
from item
as well as
to item fields ....

Creation of inbound delivery without reference to a PO

Dear gurus,
Let's say that a normal inbound flow is something like this:
PO > Create inbound delivery with reference to PO > inbound shipment > Transfer Order > Confirm Transfer Order > Post Goods Receipt > Putaway
Issue:
My client does not want to create the PO because the PO serves no purpose to them. They want the process to start from inbound delivery.
Question:
1. Can a standalone inbound delivery be created WITHOUT reference to a PO ? If yes, please tell me the configuration and transaction code involved in order to create this standalone inbound delivery.
2. Based on standard configuration, can an inbound delivery be created automatically with reference to a material document (for eg MIGO Mvt Type 501). Once again, for this scenario, no PO should be involved. If yes, please tell me the configuration and transaction code involved in order to trigger the creation of this inbound delivery (I'm not looking for the answer of an inbound delivery creation BAPI to being triggered directly after the creation of the Material Document).
3. Based on standard configuration, can an inbound delivery be created manually with reference to a material document (for eg MIGO Mvt Type 501). Once again, for this scenario, no PO should be involved. If yes, please tell me the configuration and transaction code involved in order to create this inbound delivery.
Thanks.

Hi Peter,
Actually, my intention is not really to create an inbound delivery based on a goods receipt. Since my client is not keen on the idea of creating a PO, I'm actually trying to provide alternatives and workarounds. From what I have gathered, I already know this much
-> An inbound delivery must be created with reference to PO unless Handling Unit Management is activated. If Handling Unit Management is activated, the creation of a Material Document will trigger the creation of an inbound delivery (I havent tested this out yet). Therefore, a PO will not be necessary in this case.
I was kind of expecting answers along this line, unless of course, something better pops up. Maybe someone out there may know something more.
As for Handling Units, I'm not familiar with it. Hopefully somebody can give me a good configuration guideline on what to do in order to activate it so that I can simulate the scenario of a Material Document triggering the creation of an inbound delivery (I'm not looking for the kind of answers which simply cuts and pastes the SAP HELP URL, 4.6C Handling Unit PDF, Best Practice Document and etc). Hopefully somebody out there can really give me a good guideline on how to do this.
Thanks..

How 2 creat report for displaying the details of a Delivery Document using

how to create report for displaying the details of a Delivery Document using the tables LIKP, LIPS
thank you
regards,
jagrut bharatkumar shukla
points will be rewarded

HI
I AM GIVING YOU MY DELIVERY DOCUMENT CODE...MODIFY IT ACCORDING TO YOUR REQUIREMENT
*& Report ZDELIVERY                                *
report zdelivery message-id z9bhu          .
types: begin of t_likp,
           vbeln type likp-vbeln,      "Delivery
           erdat type likp-erdat,      "Date for rec creation
*           LFDAT TYPE LIKP-LFDAT,      "Delevery Date
*           WAERK TYPE LIKP-WAERK,      "Currency
           kunnr type likp-kunnr,      "Ship-To Party
           kunag type likp-kunag,      "Sold-to party
           traty type likp-traty,      "Means-of-Transport
       end of t_likp.
types: begin of t_lips,
           vbeln type lips-vbeln,      "Delivery
           posnr type lips-posnr,      "Delivery item
           matnr type lips-matnr,      "Material Number
           arktx type lips-arktx,      "Short Text for Sales Order Item
           lfimg type lips-lfimg,      "Actual quantity delivered
           netpr type lips-netpr,
*           MEINS TYPE LIPS-MEINS,      "Base Unit of Measure
           vgbel type lips-vgbel,      "Doc no of the reference document
        end of t_lips.
types: begin of t_vbpa,
           vbeln type vbpa-vbeln,      "SD DocumenT Number
           posnr type vbpa-posnr,      "Item number
           parvw type vbpa-parvw,      "Partner function
           kunnrb type vbpa-kunnr,      "Customer Number 1
       end of t_vbpa.
types: begin of t_kna1,
           kunnr type kna1-kunnr,      "Customer Number 1
           name1 type kna1-name1,      "Name 1
           ort01 type kna1-ort01,      "City
           adrnr type kna1-adrnr,      "Address
       end of t_kna1.
types: begin of t_li_vbpa,
           vbeln type likp-vbeln,      "Delivery
           erdat type likp-erdat,      "Date for rec creation
*           LFDAT TYPE LIKP-LFDAT,      "Delevery Date
*           WAERK TYPE LIKP-WAERK,      "Currency
           kunnr type likp-kunnr,      "Ship-To Party
           kunag type likp-kunag,      "Sold-to party
           traty type likp-traty,      "Means-of-Transport
           vbeln1 type lips-vbeln,      "Delivery
           posnr type lips-posnr,      "Delivery item
           matnr type lips-matnr,      "Material Number
           arktx type lips-arktx,      "Short Text for Sales Order Item
           lfimg type lips-lfimg,      "Actual quantity delivered
           netpr type lips-netpr,      "Net Price
*           MEINS TYPE LIPS-MEINS,      "Base Unit of Measure
           vgbel type lips-vgbel,      "Doc no of the reference document
           vbeln3 type vbpa-vbeln,     "SD DocumenT Number
           parvw type vbpa-parvw,      "Partner function
           kunnrb type vbpa-kunnr,      "Customer Number 1
       end of t_li_vbpa.
types: begin of t_final,
           vbeln type likp-vbeln,      "Delivery
           erdat type likp-erdat,      "Date for rec creation
           kunnr type likp-kunnr,      "Ship-To Party
           kunag type likp-kunag,      "Sold-to party
           traty type likp-traty,      "Means-of-Transport
           vbeln1 type lips-vbeln,      "Delivery
           posnr type lips-posnr,      "Delivery item
           matnr type lips-matnr,      "Material Number
           arktx type lips-arktx,      "Short Text for Sales Order Item
           lfimg type lips-lfimg,      "Actual quantity delivered
           netpr type lips-netpr,      "Net Price
           vgbel type lips-vgbel,      "Doc no of the reference document
           vbeln3 type vbpa-vbeln,     "SD DocumenT Number
           parvw type vbpa-parvw,      "Partner function
           kunnrb type vbpa-kunnr,     "Customer Number 1
           name1 type kna1-name1,      "Name 1
           ort01 type kna1-ort01,      "City
           adrnr1 type kna1-adrnr,     "Address
           name2 type kna1-name1,      "Name 1
           ort02 type kna1-ort01,      "City
           adrnr2 type kna1-adrnr,     "Address
           name3 type kna1-name1,      "Name 1
           ort03 type kna1-ort01,      "City
           adrnr3 type kna1-adrnr,     "Address
       end of t_final.
*            D A T A D E C L A R A T I O N
*&*********Internal Table Declaration****************&*
data: it_likp type standard table of t_likp.
data: it_lips type standard table of t_lips.
data: it_vbpa type standard table of t_vbpa.
data: it_kna1 type standard table of t_kna1.
data: it_li_vbpa type standard table of t_li_vbpa.
data: it_li_vbpa_temp type standard table of t_li_vbpa.
data: it_final type standard table of t_final.
*&*********Work Area Declaration********************&*
data: wa_likp type t_likp.
data: wa_lips type t_lips.
data: wa_vbpa type t_vbpa.
data: wa_kna1 type t_kna1.
data: wa_li_vbpa type t_li_vbpa.
data: wa_li_vbpa_temp type t_li_vbpa.
data: wa_final type t_final.
*&*********Data Declaration************************&*
data: d_vbeln type likp-vbeln.
data: flag type i value 0.
*           S E L E C T I O N S C R E E N   D E C L A R A T I O N
selection-screen begin of block block2 with frame title text-001.
select-options: s_vbeln for d_vbeln obligatory.    "Delivery no
selection-screen end of block block2.
*            A T S E L E C T I O N - S C R E E N   E V E N T S
*AT SELECTION-SCREEN.
*PERFORM VALIDATE_DATA.
*            S T A R T   O F S E L E C T I O N     E V E N T S
start-of-selection.
perform fetch_data.
perform merge_data_kna1.
*INCLUDE Z9BT_SH_***4_FORMS.
call function 'OPEN_FORM'
exporting
*   APPLICATION                       = 'TX'
*   ARCHIVE_INDEX                     =
*   ARCHIVE_PARAMS                    =
    device                            = 'PRINTER'
*   DIALOG                            = 'X'
*   FORM                              = ' '
   language                          = sy-langu
*   OPTIONS                           =
*   MAIL_SENDER                       =
*   MAIL_RECIPIENT                    =
*   MAIL_APPL_OBJECT                  =
*   RAW_DATA_INTERFACE                = '*'
*   SPONUMIV                          =
* IMPORTING
*   LANGUAGE                          =
*   NEW_ARCHIVE_PARAMS                =
*   RESULT                            =
exceptions
   canceled                          = 1
   device                            = 2
   form                              = 3
   options                           = 4
   unclosed                          = 5
   mail_options                      = 6
   archive_error                     = 7
   invalid_fax_number                = 8
   more_params_needed_in_batch       = 9
   spool_error                       = 10
   codepage                          = 11
   others                            = 12
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
sort it_final by vbeln.
loop at it_final into wa_final.
call function 'START_FORM'
exporting
*   ARCHIVE_INDEX          =
   form                   = 'Z9BT_DELIVERY'
   language               = sy-langu
*   STARTPAGE              = ' '
*   PROGRAM                = ' '
*   MAIL_APPL_OBJECT       =
* IMPORTING
*   LANGUAGE               =
exceptions
   form                   = 1
   format                 = 2
   unended                = 3
   unopened               = 4
   unused                 = 5
   spool_error            = 6
   codepage               = 7
   others                 = 8
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function 'WRITE_FORM'
exporting
   element                        = 'ITEM_LIST'
   function                       = 'SET'
   type                           = 'BODY'
   window                         = 'MAIN'
* IMPORTING
*   PENDING_LINES                  =
* EXCEPTIONS
*   ELEMENT                        = 1
*   FUNCTION                       = 2
*   TYPE                           = 3
*   UNOPENED                       = 4
*   UNSTARTED                      = 5
*   WINDOW                         = 6
*   BAD_PAGEFORMAT_FOR_PRINT       = 7
*   SPOOL_ERROR                    = 8
*   CODEPAGE                       = 9
*   OTHERS                         = 10
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function 'END_FORM'
* IMPORTING
*   RESULT                         =
exceptions
   unopened                       = 1
   bad_pageformat_for_print       = 2
   spool_error                    = 3
   codepage                       = 4
   others                         = 5
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
endloop.
call function 'CLOSE_FORM'
* IMPORTING
*   RESULT                         =
*   RDI_RESULT                     =
* TABLES
*   OTFDATA                        =
exceptions
   unopened                       = 1
   bad_pageformat_for_print       = 2
   send_error                     = 3
   spool_error                    = 4
   codepage                       = 5
   others                         = 6
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
*&      Form VALIDATE_DATA
*       text
* --> p1        text
* <-- p2        text
form validate_data .
select single vbeln into wa_likp-vbeln
                    from likp where vbeln in s_vbeln.
append wa_likp to it_likp.
if sy-subrc <> 0.
flag = 1.
endif.
endform.                    " VALIDATE_DATA
*&      Form FETCH_DATA
*       text
* --> p1        text
* <-- p2        text
form fetch_data .
select a~vbeln
       a~erdat
       a~kunnr
       a~kunag
       a~traty
       b~vbeln
       b~posnr
       b~matnr
       b~arktx
       b~lfimg
       b~netpr
       b~vgbel
       c~vbeln
       c~parvw
       c~kunnr
         into table it_li_vbpa
                from likp as a
                left outer join lips as b on a~vbeln = b~vbeln
                inner join vbpa as c on b~vgbel = c~vbeln
                where a~vbeln in s_vbeln and
                c~parvw = 'RE'.
endform.                    " FETCH_DATA
*&      Form MERGE_DATA_KNA1
*       text
* --> p1        text
* <-- p2        text
form merge_data_kna1 .
if it_li_vbpa[] is not initial.
it_li_vbpa_temp[] = it_li_vbpa[].
sort it_li_vbpa_temp by kunnr.
delete adjacent duplicates from it_li_vbpa_temp comparing kunnr.
loop at it_li_vbpa into wa_li_vbpa.
read table it_li_vbpa_temp into wa_li_vbpa_temp with key kunnr =
wa_li_vbpa-kunag.
if sy-subrc <> 0.
wa_li_vbpa_temp = wa_li_vbpa.
append wa_li_vbpa_temp to it_li_vbpa_temp.
endif.
read table it_li_vbpa_temp into wa_li_vbpa_temp with key kunnr =
wa_li_vbpa-kunnrb.
if sy-subrc <> 0.
wa_li_vbpa_temp = wa_li_vbpa.
append wa_li_vbpa_temp to it_li_vbpa_temp.
endif.
endloop.
endif.
if it_li_vbpa_temp[] is not initial.
select kunnr
        name1
        ort01
        adrnr into table it_kna1 from kna1
                    for all entries in it_li_vbpa_temp
                    where kunnr = it_li_vbpa_temp-kunnr.
endif.
loop at it_li_vbpa into wa_li_vbpa .
wa_final-vbeln = wa_li_vbpa-vbeln.
wa_final-erdat = wa_li_vbpa-erdat.
*it_final-LFART = it_li_vbpa-LFART.
wa_final-kunnr = wa_li_vbpa-kunnr.
wa_final-kunag = wa_li_vbpa-kunag.
*it_final-VSTEL = it_li_vbpa-VSTEL.
wa_final-traty = wa_li_vbpa-traty.
wa_final-vbeln1 = wa_li_vbpa-vbeln.
wa_final-posnr = wa_li_vbpa-posnr.
wa_final-matnr = wa_li_vbpa-matnr.
wa_final-arktx = wa_li_vbpa-arktx.
wa_final-lfimg = wa_li_vbpa-lfimg.
wa_final-netpr = wa_li_vbpa-netpr.
*wa_final-GEWEI = it_li_vbpa-GEWEI.
*it_final-VOLUM = it_li_vbpa-VOLUM.
*it_final-VOLEH = it_li_vbpa-VOLEH.
wa_final-vgbel = wa_li_vbpa-vgbel.
wa_final-vbeln3 = wa_li_vbpa-vbeln.
*wa_final-PARVW = wa_li_vbpa-PARVW.
wa_final-kunnrb = wa_li_vbpa-kunnrb.
read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunnr.
if sy-subrc = 0.
wa_final-name1 = wa_kna1-name1.
wa_final-ort01 = wa_kna1-ort01.
wa_final-adrnr1 = wa_kna1-adrnr.
endif.
read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunag.
if sy-subrc = 0.
wa_final-name2 = wa_kna1-name1.
wa_final-ort02 = wa_kna1-ort01.
wa_final-adrnr2 = wa_kna1-adrnr.
endif.
read table it_kna1 into wa_kna1 with key kunnr = wa_li_vbpa-kunnrb.
if sy-subrc = 0.
wa_final-name3 = wa_kna1-name1.
wa_final-ort03 = wa_kna1-ort01.
wa_final-adrnr3 = wa_kna1-adrnr.
endif.
append wa_final to it_final.
clear wa_final.
endloop.
endform.

Delivery document not being picked while creating shipment document

Dear All,
Issue is regarding creation of shipment document.
As i am creating shipment document in VT01N, am unable to get the delivery doc . ie., delivery document is not picked in shipment creation.
I have created a sales order, picking is completed n saved, PGI not yet been done.
Am unable to create a shipment document due to delivery document not being picked.
i/p's will be of great help.
with regards,
Vijayashree

Dear all,
The issue is solved.
As the Route was not picking in Sales Order so the delivery was not picked in shipment creation.
Route determination setting was not correct.
Regards,
Vijayashree

Cancellation of multiorder delivery document.

Hi Experts,
I have generated one delivery document from ten sales orders by using the collective processing ( VL10A ).
Now when I am going to cancel the delivery document from the T-code- 'VL09', system is not allowing me to do it.
Can any one please suggest how can I cancell this delivery document.
Thanks & regards,
Rupam.
Edited by: RUPAM KR SEN on Jul 29, 2010 1:42 PM

Hi Rupam,
I checked this scenario.
After invoice creation, I cancelled the invoice in VF11, then did PGI reversal in VL09 and then deleted the delivery in VL02N.
When I deleted the Delivery, it gave a warning saying that the invoice number exists, but it allowed me to delete the delivery.
Consequently, the sales order now has the Open status.
The invoice has the delivery document number in the document flow, however the delivery number is not available in the system.
This will be the same case for you also if you try this scenario. I dont see any problem in this. If you are ok with this process, you can execute this for the problamatic sales orders.
Hope this helps

How to create excise invoice with reference delivery document

hi all sd guru
please guide me how to create excise invoice by taking reference of delivery no.
thankx in advance
san

HI
FACTORY SALES
IN CASE OF FACTORY sales you have to create a billing document either Proforma or Commercial.
Then you can reference the billing doc i9n J1IIN for creation
DEPOT SALES
In case of depot sales you can create a excise invoice with reference to delivery document.
For this after creation of delivery goto J1IJ and slect the rg23d from menu
you can create an excise invoice with delivery in depot sales.
In factory it is not possible to create a excise invoice with delivery doc.
regards
Prashanth

Prevent creation of a delivery document

Similar Messages

Maybe you are looking for