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

Similar Messages

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 ....

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 for STO using BAPI_OUTB_DELIVERY_CREATE_STO

Hi Experts,
Am Cretaing Delivery DOC for the STO (PO) as the reference document using the bapi BAPI_OUTB_DELIVERY_CREATE_STO.
my problem is, the bapi is not picking the stogare location(LGORT) from the STO doc storage location. Please help me to find way, if its possible to pass the storage location to Bapi or any Badi exists for the bapi to pass the storage location based on some condition.
Have found below BADI's for the BAPI in my initial investigation, but not sure to use which one, pls suggest
LE_SHP_PRICING
BADI_HU_MAIN
BADI_HU_PACKING_ALWD
BADI_HU_PACKING_QTY
BADI_HU_SAVE
BADI_HU_AUTOPACK
DELIVERY_PUBLISH
Pls find below code for reference.
WA_STOCK_TRANS_ITEMS-REF_DOC    = STO no
WA_STOCK_TRANS_ITEMS-REF_ITEM   = Item.
WA_STOCK_TRANS_ITEMS-DLV_QTY    = quantity.
WA_STOCK_TRANS_ITEMS-SALES_UNIT = 'EA'.
APPEND WA_STOCK_TRANS_ITEMS TO STOCK_TRANS_ITEMS.
CALL FUNCTION 'BAPI_OUTB_DELIVERY_CREATE_STO'
          IMPORTING
            DELIVERY          = DELIVERY
            NUM_DELIVERIES    = NUM_DELIVERIES
          TABLES
            STOCK_TRANS_ITEMS = STOCK_TRANS_ITEMS
            DELIVERIES        = DELIVERIES
            RETURN            = RETURN3.
thanks in advance.

Hi Venkat,
If you check the Function Module Documentation, there is a note which mentions:
Order (SALES_ORDER_ITEMS-REF_DOC)
Unless specified otherwise, the entire order is delivered. This means that it is not necessary to list all the order items. It is sufficient to specify the order number.
Please try this.
Regards,
Pranav.

Billng document creation using bdc

hi experts,
I've been using bapi for sales order and outbound delivery creation. But for billing document i'm using BDC. it's simpler. The creation of sales order and outbound delivery has no problem. The problem is upon creation of the billing document, it only creates the last entry in the item level. Example, if item has 10,20, and 30; it will only create item 30 in the billing document level. But no problem with the sales order and outdel. What could i be missing here?
Thank you in advance!

Hi,
Im actually not very particular on where in the bdc code the line items are being processed. the only variable that I see here is the outbound del number which is g_odnum. Here is the BDC code.
f_bdc_dynpro 'SAPMV60A' '0102'.
      f_bdc_field 'BDC_CURSOR' 'KOMFK-VBELN(01)'.
      f_bdc_field 'BDC_OKCODE' '/00'.
      f_bdc_field 'KOMFK-VBELN(01)' g_odnum.
      f_bdc_dynpro 'SAPMV60A' '0104'.
      f_bdc_field 'BDC_CURSOR' 'VBRK-FKART'.
      f_bdc_field 'BDC_OKCODE' '=SICH'.
      f_bdc_transaction 'VF01'.
Can you help me identify where it is in this BDC code?
Thanks for you help!

Sales document creation using bapi

Hi Experts ,
When i try create sales order using bapi " BAPI_SALESDOCU_CREATEFROMDATA'" , it says error like this , Please enter sold to party and ship to party, even though we are sending partner number it shows same error , if we pass values directly in se37 we get the correct result , but when we are calling it in program it says error.
Error on this field : partner Number
Thanks & Regards
Siva Krishna

Hi shiva,
           Please go through the documentation,
Sales document type is checked with sales and distribtion document type.
You must at least enter order header data (using the structure ORDER_HEADER_IN) and partner data (using the table ORDER_PARTNERS).
Furthermore, you must enter the business object for which the sales document is to be created:
               - BUS2030 for inquiries
               - BUS2031 for quotations
               - BUS2032 for sales orders
I think ur program,
does not pass business object , kindly check

Error: Sales BOM / delivery document creation via DI API

Running into an error from SAP when trying to post a Delivery Note document object via the DI API.
-5002 -You cannot add a document with a bill of materials that does not include all components
I have a Sales BOM on a Sales Order. All components have been included within the Delivery Note object. When calling the document Add() function, SAP is pushing back with the error above.
Does the fact that the components of the Sales BOM are also BOMs themselves make a difference in whether the DI API fails or succeeds in posting the Delivery Note?

Does the fact that the components of the Sales BOM are also BOMs themselves make a difference ?
I believe the answer is YES.
Thanks,
Gordon

XML document creation using reflection

Hi all,
I'm tyring to write a class which creates an XML document from objects passed in. For example, you call the add(Object) method and it takes your object, uses reflection, then outputs XML like this...
<fieldName>fieldValue<fieldName>
The only problem is that after looking through this forum I am a little concerned about the performance of my proposed solution (using reflection).
The class will be used in a batch process which processes millions of objects (to generate a whopping XML file that'll be sent on for further processing by a third party).
Is there a better way to do this than by using reflection?
This class is going to be used by multiple batch processes hence there will be lots of different object types passed (they'll also be new ones in the future that we don't even know about yet) hence my reflection choice.
Thanks,
Chris

The only problem is that after looking through this
forum I am a little concerned about the performance of
my proposed solution (using reflection).The only way that you'll know for sure is if you try it out. Write the code, test it, then run it in a profiler to find out where the performance problems (if any) are.
Is there a better way to do this than by using
reflection?Probably not, if you want to pass any arbitrary object to it.
One possible alternative is to have "XML aware" objects: define an interface WritesXML, that defines a method toXML(). You then check to see whether the given object implements this interface, and if it does you simply call the method, otherwise you use reflection.
Another alternative, assuming that your objects follow the Bean pattern, is to create "XML-ifiers" on the fly, similar to the way an app-server handles JSPs. First time you see an object you create a class that will write it to XML, then compile this class and invoke it for all subsequent objects. This will require that you have a JDK installed on the runtime machine, that the objects follow the Bean pattern, and that the number of instances of a given class are very high.
This class is going to be used by multiple batch
processes hence there will be lots of different object
types passed (they'll also be new ones in the future
that we don't even know about yet) hence my reflection
choice.Sounds like a good reason to use reflection.

Dynamic Drop Down creation using simple data types

Hi all,
I have got a requirement in which i have to create an iView which is going to have 6 drop down values and with in that 1 value is going to have sub values which needs to get displayed in the similar drop down fashion.
I have created a simple data type having enumeration of the 6 values and linked the same to iView with drop down by key which is working successfully. And for the purpose of sub values i have created a similar simple data type with two values and linked the same with a value attribute.
Well, can any one tell me the further process to proceed ?
Thanks in advance ...
Vipin

Vipin,
There are quite some steps to achieve what you need. Since you have both your DropDownByKey elements defined and bound to context elements, it may make sense to keep the Second DropDownByKey element invisible and make it visible only when user selects a specified key from first DropDownByKey. To achieve this, follow these steps.
1. Create an action with a parameter "key" of type string.
2. Bind this action with onSelect event of your First DropDownByKey UI Element.
3. Do mapping of parameter "key" in your wdDoModifyView with following code.
if (firstTime)
         final IWDDropDownByKey dk = (IWDDropDownByKey)view.getElement("DropDownByKey1");
           // Replace DropDownByKey1 with id of your DropDownByKey Element.
         dk.mappingOfOnSelect().addSourceMapping("key", "key");
4. Create a context attribute of type WDVisibility say "DDVisible" and bind to "visible" property of your second DropDownByKey.
5. Set DDVisible to NONE in wdInit().
wdContext.currentContextElement().setDDVisible(WDVisibility.NONE);
6. In onSelect action write this code to make second visible
if(key.equalsIgnoreCase("Two")){
     //Replace "Two" with your required value.
         wdContext.currentContextElement().setDDVisible(WDVisibility.VISIBLE);
       else{
            wdContext.currentContextElement().setDDVisible(WDVisibility.NONE);
This should give the desired results.
Hope this helps.
Vishwas.

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

Print Layout Designer:Due date in Delivery document

In print layout designer in 2005 version for Delivery document when they preview the document in document printing it compute an automatic due date but if the preview was done in the delivery document itself the due date is the same as posting date.
And as to delivery document in SAP no due date will be computed because due date will be determine upon invoice. But upon checking on their database, the same layout/template was used in the preview of the document in the delivery itself and in the document printing. The due date used in the layout was delivery due date.
They want to apply the scenario of having automatic computation of due date in Delivery document in the print layout designer in their 2007 version. All details created in the Print layout designer in 2005 version are defined already in their 2007 version but when the document was preview in document printing no computation of due date.
Is the layout used in the preview of delivery document itself was different when i used the document printing and select the same document and preview it? Is it possible to compute the due date in delivery document?
Can someone help me?

Hi Paul,
Yes, we already informed our customer that in delivery document no due date will be computed. But my question is it is possible that the print layout used in the preview of delivery document itself was different when the preview is done in the document printing window? To preview the document in document printing, select or highlight one transactions and click preview.
When we check the customer database and preview the delivery document itself the due date is
the same as posting date but when i preview the document in the document printing when you check the
field due date it was not the same as posting date.
We check the layout and the field is Database Delivery: Due date. The layout name was also the same when we preview
the transactions in delivery document itself and in the document printing.
Can someone tell me if the layout was different in the document printing window under Sales A/R module?
Thanks,
Janice

Regarding delivery creation using BAPI

Hi,
I am creating a delivery document number using BAPI_DELIVERYPROCESSING_EXEC.its working fine and giving delivery number also.but the problem is when i open the created delivery number in tc VL02N,the delivery and picking quatities are empty..what are the parameters i am missing ?so for me its not possible to issue PGI..
what's the solution for this..and is there any function module to pick the quantity....
Please reply soon..

HI shilpa,
Try to use below code
DATA : lv_file_name TYPE string.            "File name
lv_file_name = pv_file.
CALL METHOD cl_gui_frontend_services=>gui_upload
    EXPORTING
      filename                = lv_file_name
      filetype                = gc_asc
      has_field_separator     = gc_x
    CHANGING
      data_tab                = gt_upload[]
    EXCEPTIONS
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      not_supported_by_gui    = 17
      error_no_gui            = 18
      OTHERS                  = 19.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
               WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
Thanks,
Amol

Finding material doc given delivery no ( without using VBFA table )

Dear friends ,
I need to find out material document no given delivery document no, using data base tables . Using VBFA table is ruled out due to performance issues .
What is the way to do this ?
Regards
Mahesh.

As an ABAPer, I can assure you that you will get much better performance with VBFA than with any other table. In VBFA you'll be searching by the VBELV and POSNV, which are the primary key. This should work quite fast, as long as the SELECT statement has been programmed correctly. I bet the poor performance has been caused by an inefficient SELECT statement. If you post the code fragment here, I might be able to suggest some improvements.
In MKPF you'll have to search by LE_VBELN field, which is not part of the primary key or any standard indexes. This will be very inefficient and I would not recommend that.

DIAPI posting Delivery Document with Serial Numbers SP1

Release 2005A, SP1 PL4 seems to have broken code that worked with SP00. When trying to create a Delivery Document that contains Serial Numbers, an error is generated: Error -1, General Error. When adding a delievery document which does not contain serial numbers, the document adds successfully.
The following code loops through a recordset to create documents, add expenses and add serial numbers when appropriate. Is this a new 'feature' or can we make a coding change to eliminate this error?
Sample code:
    Try
      oSalesOrder = oCompany(piCompany).GetBusinessObject(SAPbobsCOM.BoObjectTypes.oOrders)
      RecSet = oCompany(piCompany).GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)
      RecSet2 = oCompany(piCompany).GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)
      RecSet3 = oCompany(piCompany).GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)
      RecSet4 = oCompany(piCompany).GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)
      RecSet5 = oCompany(piCompany).GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)
      RecSet6 = oCompany(piCompany).GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)
      '-- Select Documents to process and loop through recordset
      lsSQL = "SELECT DocEntry FROM DeliveryTable WHERE ProcessResult IS NULL Group by DocEntry"
      RecSet.DoQuery(lsSQL)
      While Not RecSet.EoF
        oSalesOrder.GetByKey(RecSet.Fields.Item(0).Value)
        If bDocuments(piCompany).DelDraft = False Then
          oDelivery = oCompany(piCompany).GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDeliveryNotes)
        Else
          oDelivery = oCompany(piCompany).GetBusinessObject(SAPbobsCOM.BoObjectTypes.oDrafts)
        End If
        oDelivery.CardCode = oSalesOrder.CardCode
        oDelivery.Comments = "Based On Sales Order " & oSalesOrder.DocNum & "."
        oDelivery.DocDate = Today
        oDelivery.ContactPersonCode = oSalesOrder.ContactPersonCode
        oDelivery.DocCurrency = oSalesOrder.DocCurrency
        oDelivery.DocDueDate = Today
        If bDocuments(piCompany).DelDraft = True Then
          oDelivery.DocObjectCode = SAPbobsCOM.BoObjectTypes.oDeliveryNotes
        End If
        '-- Handle Expenses for Document
        Dim ExpenseLoop As Integer
        Dim ExpenseCount As Integer = 0
        For ExpenseLoop = oSalesOrder.Expenses.Count - 1 To 0 Step -1
        ExpenseCount += 1
          '-- Create new Expense if needed
          If ExpenseCount > oDelivery.Expenses.Count Then
            oDelivery.Expenses.Add()
          End If
          oSalesOrder.Expenses.SetCurrentLine(ExpenseLoop)
          '-- Copy all non-readonly properties
          If oSalesOrder.Expenses.LineTotal > 0 Then
            oDelivery.Expenses.BaseDocEntry = oSalesOrder.Expenses.BaseDocEntry
            oDelivery.Expenses.BaseDocLine = oSalesOrder.Expenses.BaseDocLine
            oDelivery.Expenses.BaseDocType = oSalesOrder.Expenses.BaseDocType
            oDelivery.Expenses.DeductibleTaxSum = oSalesOrder.Expenses.DeductibleTaxSum
            oDelivery.Expenses.DistributionMethod = oSalesOrder.Expenses.DistributionMethod
            oDelivery.Expenses.ExpenseCode = oSalesOrder.Expenses.ExpenseCode
            oDelivery.Expenses.LineTotal = oSalesOrder.Expenses.LineTotal
            oDelivery.Expenses.Remarks = oSalesOrder.Expenses.Remarks
            oDelivery.Expenses.TaxCode = oSalesOrder.Expenses.TaxCode
            oDelivery.Expenses.VatGroup = oSalesOrder.Expenses.VatGroup
          End If
        Next ExpenseLoop
        Dim i As Integer = 0
        Dim liMinRef As Integer = -1
        For x = 0 To oSalesOrder.Lines.Count - 1
          lsSQL = "SELECT ISNULL(MIN(CAST(LineRef as int)),999999) as MinLineRef FROM DeliveryTable WHERE DocEntry = " & RecSet.Fields.Item(0).Value & " AND CAST(LineRef as int) > " & liMinRef
          RecSet5.DoQuery(lsSQL)
          If Not RecSet5.EoF Then
            '-- It's possible that the DeliveryTable has less records then the RDR1 table - if that's the case
            '-- we may be at the end, so set the liMinRef field to something out of range
            liMinRef = RecSet5.Fields.Item(0).Value
          End If
          '-- get line items for each document
          lsSQL = "Select * from DeliveryTable WHERE DocEntry = " & RecSet.Fields.Item(0).Value & " AND LineRef = " & x & " AND ProcessResult IS Null"
          RecSet2.DoQuery(lsSQL)
          RecSet2.MoveFirst()
          While Not RecSet2.EoF
            '-- We need to walk through the SO to find the item that we are receiving based on the LineNum
            Dim liCurrentLine As Integer = x
            Dim lbFound As Boolean = False
            While liCurrentLine <= (oSalesOrder.Lines.Count - 1)
              '-- We need to get the PO Line number (x is NOT the LineRef)
              oSalesOrder.Lines.SetCurrentLine(liCurrentLine)
              If oSalesOrder.Lines.LineNum = liMinRef Then
                lbFound = True
                Exit While
              End If
              liCurrentLine += 1
            End While
            If lbFound Then
              i += 1
              If i > oDelivery.Lines.Count Then
                oDelivery.Lines.Add()
              End If
              oDelivery.Lines.BaseEntry = oSalesOrder.DocEntry
              oDelivery.Lines.Quantity = RecSet2.Fields.Item(6).Value
              oDelivery.Lines.BaseType = SAPbobsCOM.BoObjectTypes.oOrders
              oDelivery.Lines.LineTotal = oSalesOrder.Lines.LineTotal * (oDelivery.Lines.Quantity / oSalesOrder.Lines.Quantity)
              oDelivery.Lines.UserFields.Fields.Item("U_WhseLoc").Value = RecSet2.Fields.Item(8).Value
              oDelivery.Lines.AccountCode = oSalesOrder.Lines.AccountCode
              oDelivery.Lines.Address = oSalesOrder.Lines.Address
              oDelivery.Lines.Currency = oSalesOrder.Lines.Currency
              oDelivery.Lines.ItemCode = oSalesOrder.Lines.ItemCode
              oDelivery.Lines.BaseLine = liMinRef
              oDelivery.Lines.ItemDescription = oSalesOrder.Lines.ItemDescription
              oDelivery.Lines.WarehouseCode = oSalesOrder.Lines.WarehouseCode
              lsUserID = RecSet2.Fields.Item("UserID").Value
              '-- manage serial numbers
              j = -1
              lsSQL = "Select * from DeliverySerial WHERE DocEntry = " & oDelivery.Lines.BaseEntry & " AND LineRef = " & liMinRef
              lsSQL += " AND WIPLineRef = " & RecSet2.Fields.Item("WIPLineRef").Value
              RecSet3.DoQuery(lsSQL)
              While Not RecSet3.EoF
                '-- get the next SystemSerialNumber for the Inventory Item
                lsSQL = "EXEC " & gsDB(piCompany) & "xspGetSysSerial " & sparm(oDelivery.Lines.ItemCode) & ", " & sparm(RecSet3.Fields.Item("LotNo").Value)
                lsSQL += ", " & sparm(RecSet3.Fields.Item("ManSerNo").Value) & ", " & sparm(RecSet3.Fields.Item("IntSerNo").Value)
                lsSQL += ", " & RecSet3.Fields.Item("QTY").Value & ", " & sparm(oDelivery.Lines.WarehouseCode) & ", " & sparm(RecSet2.Fields.Item(8).Value)
                RecSet4.DoQuery(lsSQL)
                  j += 1
                  If j + 1 > oDelivery.Lines.SerialNumbers.Count Then
                    oDelivery.Lines.SerialNumbers.Add()
                  End If
                  oDelivery.Lines.SerialNumbers.SetCurrentLine(j)
                  oDelivery.Lines.SerialNumbers.BatchID = RecSet3.Fields.Item("LotNo").Value
                  oDelivery.Lines.SerialNumbers.ManufacturerSerialNumber = RecSet3.Fields.Item("ManSerNo").Value
                  oDelivery.Lines.SerialNumbers.InternalSerialNumber = RecSet3.Fields.Item("IntSerNo").Value
                  oDelivery.Lines.SerialNumbers.SystemSerialNumber = RecSet4.Fields.Item(0).Value
                  oDelivery.Lines.SerialNumbers.BaseLineNumber = oDelivery.Lines.BaseLine
                RecSet3.MoveNext()
              End While
              '-- 'end manage serial numbers
            End If
            RecSet2.MoveNext()
          End While
        Next x
        '-- now add object to SAP
        If 0 <> oDelivery.Add() Then
          Dim liError As Long
          Dim lsError As String
          Call oCompany(piCompany).GetLastError(liError, lsError)
          '-- write error code to table - Delivery document creation was unsuccessful
          lsSQL = "Update DeliveryTable SET ProcessResult = " & liError & ", ProcessDate = GetDate() WHERE DocEntry = " & oSalesOrder.DocEntry & " AND ProcessResult Is Null"
          RecSet2.DoQuery(lsSQL)
          lsuWriteEvent("AR Delivery", bDocuments(piCompany).DelDraft, oSalesOrder.DocEntry, liError, lsError, piCompany)
        Else
          lsuWriteEvent("AR Delivery", bDocuments(piCompany).DelDraft, oSalesOrder.DocEntry, 0, "Success", piCompany)
        End If
        RecSet.MoveNext()
      End While
    Catch
      LogErrorMessage(Err.Description)
    Finally
      If Not RecSet Is Nothing Then
        System.Runtime.InteropServices.Marshal.ReleaseComObject(RecSet)
      End If
      If Not RecSet2 Is Nothing Then
        System.Runtime.InteropServices.Marshal.ReleaseComObject(RecSet2)
      End If
      If Not RecSet3 Is Nothing Then
        System.Runtime.InteropServices.Marshal.ReleaseComObject(RecSet3)
      End If
      If Not RecSet4 Is Nothing Then
        System.Runtime.InteropServices.Marshal.ReleaseComObject(RecSet4)
      End If
      If Not RecSet5 Is Nothing Then
        System.Runtime.InteropServices.Marshal.ReleaseComObject(RecSet5)
      End If
      If Not RecSet6 Is Nothing Then
        System.Runtime.InteropServices.Marshal.ReleaseComObject(RecSet6)
      End If
      If Not oSalesOrder Is Nothing Then
        System.Runtime.InteropServices.Marshal.ReleaseComObject(oSalesOrder)
      End If
      If Not oDelivery Is Nothing Then
        System.Runtime.InteropServices.Marshal.ReleaseComObject(oDelivery)
      End If
      GC.WaitForPendingFinalizers()
    End Try

We have narrowed down the issue to this:
If you are just adding a delivery document with serial numbers, the DIAPI works OK. If you are adding a delivery document which is based upon a sales order and add the 3 lines that reference it:
oDelivery.Lines.BaseEntry = oSalesOrder.DocEntry
oDelivery.Lines.BaseType = SAPbobsCOM.BoObjectTypes.oOrders
oDelivery.Lines.BaseLine = liMinRef
then you receive a error of -1, General error. This is functionality that did work in 2004 and 2005 SP00. I believe this is a bug.

Picked quantity in delivery docuement

Hi, experts,
I have created the sales order and try to create the delivery. However, in the delivery document and in its picking tab the column "picked quantity" allows no changes(default 0) with color blue instead of white.
Only when I save it and the delivery document nr is generated and I get into the this delivery document again using VL02N, I am allowed to change the picked quantity and post goods issue.
Is this normal?
Best regards,
Fan

Hi
in-img-enterprise structure -assignment-under logistics execution there is a setting maintained for warehouse/plant and storage location combination and remove your entry remove the warehouse maintained for your plant and storage location combination there and try
If warehouse is assigned to to your plant and storage location combination then manual picking is not possible
In this case you need to do picking thro a additional process called Transfer order in t code LT03
(this is a big subject by itself)
Not to allow manual picking system has greyed out the picked qty in the picking tab in delivery If warehouse is assigned
Regards
Raja
Edited by: ramanathan raja on Aug 27, 2009 5:57 PM
Edited by: ramanathan raja on Aug 27, 2009 6:01 PM

Delivery Document creation using buffered data?

Similar Messages

Maybe you are looking for