Delivery Document in FBL3N

Hi gurus,
i have a requirement of adding a delivery document number in FBL3N.please suggest me is it possible , if so please can you send me the details on that.
Thanks and regards,
Rajeshwar

Hi,
In FBL3N report, after generating the Report, Go to Settings - Special fields and add the required field. If the field required by you exists in the list of special fields-Table then it will allow you to display the field.
Note- this is a cross client change
hope this helps
regards,
radhika

Similar Messages

Adding Delivery Document in FBL3N

Hi gurus,
i have a requirement of adding a delivery document number in FBL3N.please suggest me is it possible , if so please can you send me the details on that.
Thanks and regards,
Rajeshwar

Hi Rajeshwar ,
try to add field Reference it will have Delivery No in it.
but u need to know every document will have ref in it , but based on the Document type u can find out which one is DO or SO......
regards
prabhu
Edited by: Prabhu Peram on Oct 8, 2008 4:41 PM

Report of cancelled Delivery Document, Billing Document & Shipment Document

Hi,
How can I get list of cancelled Delivery Document, Billing Document & Shipment Document.
Regards,
VK

Hi,
Good Day,
Cancelled Delivery will available in Table CDPOS
Pass below parameter
OBJECTCLAS    LIEFERUNG
OBJECTID       Delivery Number
TABNAME       LIKP
CHNGIND       D
Cancelled Invoice available in Table VBRK Pass Below Parameter
FKSTO = 'X'
Shipment Document Once you delete i don't thinks will get the details.
May we can use Userexist and maintain customized table to track the deleted shipment number.
Best Regards,
KSK

Unable to capture condition type in delivery document

There are deliveries in production server, for the same destination zone, in which, for some deliveries, the condition Z52L is not determined and for some other deliveries, the condition Z52L is determined although the condition record for its plant with its corresponding destination zone is maintained in VK13.
For example, if we take 2 documents with the same Ship-To-Party, same Plant, and same Destination Zone:
1 delivery document, condition Z52L is properly determined while the other
delivery document, condition Z52L is not determined.
Another good representative example if we take 2 delivery documents with the same Ship-To-Party, same Plant and same destination zone:
1 delivery document, condition Z52L is properly determined while the other
delivery document, condition Z52L is not determined.
But in the analysis pricing of the delivery document, there is no destination zone found but still it captures the condition Z52L by just referring to the transportation zone of the ship to party while the other delivery document cannot able to capture it since there is no maintained condition record for those with blank destination zone in VK13.
Another point that we want to clarify is even the user update the pricing in the delivery document, still the condition was not yet updated even it is already maintained in VK13.
Please help and explain this issue to us.
Thank you in advance. Hoping for your assistance on this matter.
Reyna Agustin

hi,
for the first errot check if you have maintained the item level copy control (from sales order to del). if yes check the settings against the field 'pos/- qty'. put a + here. for the second issue check in the item level copy ctrl from sales order to billing maintain 'd' in the price type.
saurabh

Regarding- Packing Line Item Not Displayed in the Delivery Document.

Hi,
I have 2 queries
1) Have created separate Material Type Packaging for my packing material and the item category group used is VERP, my Orginal Material is getting packed in the Delivery Document, however the packed item is not coming as a separate line item in the Delivery document, I have maintained the item category settings for the Delivery Packing Material and also the packing Material contains stock,
2) The Plant and Storage Location for my handling unit need to get defaulted autmatically in the delivery document what settings should I configure for the same.
Kind Regards
Atul Keshav

Hi,
Find the below threads, which is explained in context with returnable packaging, same will be useful for you.
[Re: returnable packaging]
[Returnable packaging process;
Regards,
Reazuddin MD

Item number in billing document not matching with delivery document-reg

Hi All,
In the billing document the item number is coming from Shipment document. ie., there are three deliveries in a shipment. Each delivery has got one line item, ie., 10. These three deliveries are assigned to a shipment, the order in which the deliveries are attached if we take as 10 for first delivery, 20 for th esecond and 30 for the third, In billing document the billing from first delivery is getting the item number as 10, the second delivery's billing document is getting the item number as 20 and the third as 30.
Can someone please reply where and how this is configured?
Thanks and regards,
Tajudeen S.

Hi,
first look at IMG/Sales and Distribution/ Billing / Maintain Copying Control For Billing Documents / Copying control: Delivery document to billing document
There is a field "Copy item number from reference"
Maybe it helps.
regards
Wojciech

Open Sales order, Delivery docuement, Billing document, Item

Hi Gurus,
Kindly help to view the following items for a particular customer.
1) Open sales order value
2) Open Delivery docuement value
3) Open Billing document value
4) Open item.
I presume for viewing open sales order VA05N and to view Open item FBL5N would suffice. Please correct me if i am wrong and let me know about points 2 and 3.
This is required because, my client is facing some figure mismatch while executing F.35 tcode. I am trying to analyze the differnce of figures while doing a Static and dynamic credit check.
Thanking you in advance
ficoguy.

Dear ficoguy,
1) Open sales order value
Tcode: VA05 (select OPEN SALES ORDERS)
optional method: SE11/ TABLE VBAK/ INPUT customer code as KUNNR, fetch the list.
Input the VBELN in VBUK and filter with RFSTK='A'
2) Open Delivery document value
Tcode: VF04 (OUTPUT DATA FOR BATCH PROCESSING-->CHECK LIST DISPLAY)
DOCUMENT TO BE SELECTED = DELIVERY RELATED
optional method:(same as above except the FIRST TABLE)
SE11/ TABLE LIKP/ INPUT customer code as KUNNR, fetch the list.
Input the VBELN in VBUK and filter with RFSTK='A'
3) Open Billing document value
TCode: VF05
Selection criteria : OPEN BILLING DOCUMENTS
4) Open item.
Tcode : FBL5N
Check and revert back.
Thanks & Regards,
Hegal K Charles

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 is still open even already invoiced

Good day! Could anyone help me on this?
Here is the scenario:
A new delivery document was created based in sales order. The delivery undergoes to approval procedure and then approved.
Upon posting of the delivery doc and after past few days, sales return was requested. So, sales return was processed and successfully posted based in that delivery doc, but later that day another sales return was requested and did same procedure (successful).
Two sales return was created based in that delivery doc and both SR were 'closed' while the delivery doc is still open, now to close that DR an invoice doc is required. Invoice was made base again in that DR and successfully posted. Expectedly, the DR should close but apparently it doesn't close. Why is that? Or did I miss something that would close that DR?
Thanks in advance!

Hi Nagesh,
Yes your right, all marketing docs undergone with approval procedure are all saved as Draft until it was approved by the approver and then posted by the originator and that is the only time DR or any marketing docs should be called as official/posted transaction.
Going back to my scenario, what I mentioned was approved and posted meaning the transaction was officially saved and undergone with the normal module flow SO->DR->SR->SI.
And my concern was focused on why DR is still open even already invoiced.
Correct me if I'm wrong, DR will still remain 'Open' only if the item total qty was not yet invoiced. For example:
DR1              QTY            Amount
Item 1             10              100
SI
Item 1              8                80
Thanks,
Rhod

Sap standard report for delivery document block.

Hi,
We want to block delivery document for further processing that picking and PGI.
For that we are looking for sap standard report if available so we could provide it to client.
so we need
SAP standard report for blocked delivery document.

Hi,
As far as my understanding there is no such report but you can try with report MATERIAL WHERE USED LIST
Please find t-code for this as due to system unavailable i am not mentioning t-code for same
kapil

Delivery Document for Services

Hello Experts,
I have a scenario which I am looking for an SAP solution. My client provides consultancy services and bills customers for it. At the beginning of the contract, customer gives a letter of intent (LOI) which authorised commencement of work. After work is completed, the customers signs a job completion form/service entry sheet, which is the basis on which the client can invoice the customer for the hours/days spent. Thinking along OTC, it looks to me that the LOI could represent a sales order, but I am looking for a document to represent the job completion form/service entry sheet. Can we have a delivery document for services? Is there any other document that can perform the same function as delivery in this scenario? I think there has to be another document after the sales order that will represent the actual hours/days spent on the job which the invoice can reference in billing the client.
Thanks for your prompt help.
Luqman

Its part of Customer Service. And widely know as After Market.
Is very much integrated with SD as well as PS.
DP90 csan be used by PS & SD both.
Whereas, if your refer DP90, its purely based on Sales Document.
Refer following SAP Help link for reference/understanding:
- [ Resource-Related Billing |http://help.sap.com/saphelp_dimp50/helpdata/en/59/54fc37004d0a1ee10000009b38f8cf/content.htm|also CS billing process]
Also refer, SAP Note 301117 - Enhanced documentation for dynamic item processor (DIP).
As DIP profile(TCode ODP1) is the critical part of RRB configuration.
Regards
JP

Delivery document available in VKDFS table. How to remove that?

Hi,
The scenario goes like this. I create purchase order,goods receipt and invoice. followed by which i create a return delivery for one line item . Now this return delivery gets added in VKDFS table. The reason is because billingtype is IV(Intercompany billing).
Item category of delivery is RLLN(Relevant for proforma). generally item category relevant for proforma doesnt get added in VKDFS. But since this is intercompany billing it is added in VKDFS.
Now my doubt is how or where do we give the billing type for delivery document.I mean where do we assign Intercompany billing to delivery document.....

Hello,
please run transaction 0VLK to dsiplay the involved delivery type.
Notice the field 'Default ord.ty' TVLK-DAART.
Run transaction VOV8 to display the order type in TVLK-DAART.
Here you can see the 'Intercomp.bill.type'
Best regards,
Ivano.

Delivery Document not getting closed

Hi Experts,
I am using 2007 B PL 08. I want to close the delivery document through SDK against which no Invoice or return is booked. it gives me error 'Internal error -5002 occured' when I try to close this document with following code.
Dim fd As SAPbobsCOM.Documents
fd = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDeliveryNotes)
         If fd.GetByKey(93) = True Then
                DelClose = fd.Close
                If DelClose <> 0 Then
                    oCompany.GetLastError(FErrCode, FErrMsg)
                    MsgBox(FErrMsg)
                End If
          End If
i even try following code to loop through the lines collection and close lines instead of closing header.
it gives me "you can not close rows in this type of document" error:
Dim fd As SAPbobsCOM.Documents
            fd = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDeliveryNotes)
            If fd.GetByKey(93) = True Then
                For i = 0 To fd.Lines.Count - 1
                    fd.Lines.SetCurrentLine(i)
                    If fd.Lines.LineStatus <> SAPbobsCOM.BoStatus.bost_Close Then
                        fd.Lines.LineStatus = SAPbobsCOM.BoStatus.bost_Close
                    End If
                Next
                DelClose = fd.Update
                If DelClose <> 0 Then
                    oCompany.GetLastError(FErrCode, FErrMsg)
                    MsgBox(FErrMsg)
                End If
            End If
this used to work with 2005 B. Am I doing anything wrong?
Thanks in advance,
Binita

Hi Binita,
Closing the delivery at the header level works in the DI API in SBO 2007A (though it's not good practice as the correct method, as you know, would be to add a return linked to the delivery to return the goods to stock and update the GL). I can also do this via the SBO client (it warns me that there is no target document but I can choose to continue).
If you can close the delivery via the SBO client in 2007B then it sounds like a bug in the DI API.
Kind Regards,
Owen

Delivery document not getting updated

Dear Experts,
Till date our client was using VL04 for creating DA for only domestic sales, now they
are asking to provide facility to created DA for export shipment in VL04 and we have done customization for the same.
Now there are two separate (delivery document number) number ranges generated for
domestic and export sales.
Now my problem is : delivery document number generated for export sales is not getting
updated in database table VTRDI
Have any idea ??
Please advice
R.Karthik
Edited by: Karthik R on Sep 30, 2009 5:31 PM
Edited by: Karthik R on Sep 30, 2009 6:39 PM

Hi Lakshmipathi ,
Thank you so much.....for ur valuable advice !!
I have checked the table LIKP and LIPS ...and the export delivery number is getting saved
in these two tables...
But my problem is with creating shipment in VT01...as delivery number generated for export is not
getting picked in VT01 but for normal domestic orders it is getting picked.
I could not figure out where I went wrong??
could you please guide me on this issue.
R.Karthik
Edited by: Karthik R on Oct 5, 2009 8:46 AM

Delivery document is in UOM bags but should be invoiced in kilos

Hi Experts!
Please help me on this matter.
My client's situation is that a delivery document was created wherein the sales UOM is in bags and the unit price was in bags. However, when the time of the invoicing came, the client's customer wants to be billed in kilos and the price in kilos. The reason behind this is that sometimes, when the item is delivered, it is not the exact number of bags received by the client's customer and so they allow this for their customer.
What document should I create and how should I account for the price difference?
Note: Inventory UOM is in kilos. Sales UOM is in bags
Hoping for your prompt response.
Regards,
Jen

Already solved my problem. I could use the Base Units column so that I can used the Inventory UOM when I create a delivery document.
Unfortunately, I have to create a new AR invoice.
Thank you for all your inputs
Edited by: Jennifer Tinagan on Jun 25, 2009 1:40 PM
Edited by: Jennifer Tinagan on Jun 25, 2009 1:48 PM

Delivery Document in FBL3N

Similar Messages

Maybe you are looking for