Address error in delivery document

Hi Sapients,
While i am delivering from a particular plant normal sales process its allowing me for delivery process.
If i do the same with STO process while doing delivery PGI its giving Address does not exist.
Suggest me as early as possible.
Regards,
ram

Dear Ram,
Means System is asking about the SHiptoparty of this STO(Receiving plant).
While creating the Cuatomer under supplying plant and Check the Assignment in Plant to Customer in MM-Purchasing-STO.
Regards
raj.

Similar Messages

Report to Monitor the change of delivery address on the delivery document

Is there a report that can show me when a user had changed the delivery address in a sales document or delivery document. The ship to # would stay the same but the address can be changed within the sales document which does not effect Master Data records.
We are trying to moitor this to find where users have modified the address when shipping a delivery.
Thanks

Grant,
I was unable to find a solution to your problem. I think it is unlikely that this change
when a user had changed the delivery address
is explicitly recorded by SAP. In the systems I looked at today, address changes in Sales docs are not among those that are automatically recorded.
You can, however, look in table VBPA. If an address has been entered manually (vs the normal automatic determination via customer master tables), then VBPA-ADRA is changed to 'E'. Unfortunately, I can't find any place where this event is time-stamped, or the user responsible is recorded. You might be able to intuit the user using other means.
Regards,
DB49

Error in delivery document flow

Hi guru ,
i am facing one issue , i have save the delivery document but this is open delivery document the system showing open delivery and goods issue in document flow what happing in the process , can you plz tell me
regads,
bhaskar.k

Hi
Try to correct it running report RVDELSTA. See SAP Note 506510 - Correction report: Status in the delivery and related notes (depending your release) for further information.
I hope this helps you
Regards
Eduardo

Run time error in delivery document

          I am doing standard Order To Cash process i will get an run time error in PGI time

Runtime Errors MESSAGE_TYPE_X
Date and Time 18.07.2014 22:41:23
Short dump has not been completely stored (too big)
Short text
     The current application triggered a termination with a short dump.
What happened?
     The current application program detected a situation which really
     should not occur. Therefore, a termination with a short dump was
     triggered on purpose by the key word MESSAGE (type X).
Error analysis
     Short text of error message:
     No RFC destination is defined for SAP Global Trade Services
     Long text of error message:
     Technical information about the message:
     Message class....... "/SAPSLL/PLUGINR3"
Number.............. 002
Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
Trigger Location of Runtime Error
    Program                                 SAPLMBWL
    Include                                 LMBWLU21
    Row                                     59
    Module type                             (FUNCTION)
    Module Name MB_POST_GOODS_MOVEMENT
Source Code Extract
Line SourceCde
Source Code Extract
Line SourceCde
   29 *    when a goods movement for an inbound or outbound delivery is posted
   30 *    directly from VL31N/ VL01N, XBLNR is not yet known when we call
   31 *    CKMV_AC_DOCUMENT_CREATE, but the number is supposed to be stored in
   32 *    BKPF as well. There is no other way to forward XBLNR to FI as not
   33 *    every document is posted by MB_CREATE -> a new function module in
   34 *    MBWL for transferring the information, called by FI, meant to load
   35 *    the complete function group for all MBxx postings when this isn't
   36 *    required (Performance). Would be the better way to transport the
   37 *    information after switching off MBxx in later release.
   38 *    corresponding IMPORT ... FROM MEMORY ... can be found in
   39 *    AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
   40      l_mem_id = 'MKPF-XBLNR'.                                   " 641365
   41      EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
   42    ENDIF.
   43    IF xmkpf-xabln IS INITIAL.                               "note 434093
   44        CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
   45    ENDIF. "note 434093
46
47 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51         EXCEPTIONS
52 error_message = 4.
53 * As soon as we have started to put things into UPDATE TASK, we must
54 * ensure that errors definitely terminate the transaction.
55 * MESSAGE A is not sufficient because it can be catched from
56 * external callers which COMMIT WORK afterwards, resulting in
57 * incomplete updates. Read note 385830 for the full story.
58    IF NOT sy-subrc IS INITIAL.
>>       MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
60 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61 *     MESSAGE A263.
62    ENDIF.
63 * Optische Archivierung
64 * Spaete Erfassung mit Barcode
65 * Redesign of barcode handling -> note 780365
66   PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67 xmkpf-mjahr
68                                          barcode.
69
70 MOVE-CORRESPONDING xmkpf TO emkpf.
71   CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72     EXCEPTIONS
73       error_message = 4.
74 MOVE-CORRESPONDING xmkpf TO emkpf.
75    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76         EXCEPTIONS
77           error_message = 4.
78    IF NOT sy-subrc IS INITIAL.

Posting Period error in delivery document

Following data in OMSY Screen
Co Cd     Company     Year   Pe     Fyr     LM     Fyr     LM
9001     L                   2007   3     2007     2     2006     12
Following data in MMRV Screen
Company Code    9001   L
Current period                03 2007
Previous period              02 2007
Last period in prev.year 12 2006
Please let me know if we can post goods in month of June as this is 3rd month in Fiscal Year.
I am getting following error message.
Posting only possible in periods 2007/03 and 2007/02 in company code 9001
Please let me know what year format it is following & how to follow financial year method.
Regards,
GHS.

According to the data you have provided u are using V3 - fiscal year i.e. Apr - Mar.
Followed by India and some other countries.
As far as your error solving is concerned, please check the date for which you are posting. May be it is in the future 4th month (i.e. july for V3) probably. That is why the system is giving in the error. If you change the date to june then the problem will be solved.
Hope the answer help you.
Regards
AK
Please reward points if helpful

Error during the replication of inbound delivery document to GTS

Hi
While trying to transfer an inbound delivery from the feeder system to the GTS system, I am getting the following error, eventhough the customs document type TRLOIM is assigned to the Feeder sys doc type EL, at application level MM0B in customs management. The inbound delivery document has been maintained with the Prev Doc Type T1 & Prem Doc No in the Foreign trade Data
Customs document type cannot be determined for external document type
Message no. /SAPSLL/API_INBOUND020
Thanks & Regards
Ram

Hi Ram,
Please use OSS note1238850 to fix the issue, this error comes as your doc type EL is not getting transferred when you are sending I/B delivery.
Hope this helps.
Kind Regards,
Sameer

Ssrs sharepoint 2013 error: "A delivery error has occurred ...not a sharepoint document library..."

Greetings SSRS/SharePoint experts,
SharePoint 2013 with SSRS - Creating a subscription to a report that is in SharePoint
I'm trying to create a subscription to publish a report to a sharepoint document library.
I've configured all the settings and on clicking OK get the following error:
"A delivery error has occurred. ---> Microsoft.ReportingSerives.Diagnostics.Utilities.DeliveryErrorException: A delivery error has occurred. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidExtensionParameter: One of the extension
parameters is not valid for the following reason: The delivery path is either not a SharePoint Document Library Folder or does not exist in the Share Point farm."
SQL Server Developer Edition 2012 SP1
SharePoint 2013 Standard
Just wondering if anyone has a solution.
I've tried changing the proxy settings as per this post
http://social.technet.microsoft.com/Forums/en-US/19817dc7-6725-40d8-befa-1b94099a71bd/sql-server-2012-reporting-services-in-sharepoint-2013-integrated-mode-dilivery-extension
Workaround is to not use a sharepoint document library but write the report to a windows file share (this works but is not optimal).
Hoping someone at Microsoft or an expert will come back with something.
Kind regards
Gio

Hi,
Can you check the SharePoint ULS log located at : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS, and look at the log there when the error occurs?
You can also check the Application Event Log on the SQL Server to see if there are any additional errors.
Tracy Cai
TechNet Community Support

Web Services,Delivery Document Adding Error Could not commit Transaction

Dear All,
I am working with SAP Business One Web Services, While adding Delivery Document it's giving error "Could not commit transaction" Please Give your Suggestion It's urget.
Thanks,
Madhu
9701155577

Hi,
Do you mean there is no journal entry created orthat the link is missing?
If this really is a delivery for stock/inventory items there should be a journal entry, else it sounds like an error in SAP.
Are there still changes in the stored procedure? Also have a look at the TansactionNotice. It is possible the roll back does not work correctly.
Again sounds like an error.
Doe sit happen all the time?
Only for certain items?
Are the stored procedures now clean?
What Version are you using?
Kind Regards,
Friederike

Error when reverse delivery document

Hi Gurus
Basically we are pipe coating company (Service based)
We are using serial number management for pipes .GRN for pipe has been done and serial number assigned to it.
While doing dispatch the one serial number has been taken by two different delivery doc.(which we have seen from them serial number history)
For Some reason we cancelled all the delivery for the sales order in vl09.
Since the one delivery doc is reversed the serial number is taken by that document.
When we do for other delivery document we are not able to reverse we are getting the following error,
System status ESTO is active (EQU 62784)
Message no. BS013
Diagnosis
Object EQU 62784 has system status ESTO (In the warehouse). According to this status, transaction 'Goods receipts' is not allowed.

Hi KK,
Please post it in the correct functional forum so that your issue will be resolved at the earliest.
This forum is for performance tuning.
Please close this thread and open it in the correct forum.
Cheers,
Raja.D

Collective Billing doc./online stops if a delivery document saves with error

Dear Gurus
We will save the billing documents using VF04 (Maintain Billing Due list) by selecting all the delivery documents and will click on "Collective Billing Doc. /Online'. Sometimes, if a single delivery documents was incomplete or saved with error, system stops the execution at the error delivery document. Again we will exclude the error delivery document and tries to select the remaining documents. We will repeat it till all documents cleared (except the error Document).
Is there any option, where we can successfully execute all the documents with excluding the error delivery documents. That means, system should save all the billing documents without stopping at the error document. This will helps us to minimize our time. Suggest us a solution.
Regards
Maheshwar Rao Gudepu

Normally, for any reason, if billing documents cannot be generated, it could be due to incompletion log exists in sale order and not in delivery. So in all probabilities, wherever system has stopped generation of billing document, if you check the corresponding sale order, it would have been saved with incompletion log. So before executing VF04, user has to educate to check this. On the other hand, if you want to automate this process, you can try with USEREXIT_FILL_VBRK_VBRP in program RV60AFZC
G. Lakshmipathi

Error when creating document flow for delivery

Hi,
I would like to post the GR for Inbound delivery. I receive an error the TO is not confirmed. I have tried to confirm the tranfer order and I receive the "error when creating document flow for delivery . In order to avoid inconsistencies the goods movement posting was cancelled." It seems like the document already exist.
How can I do to confirm the TO and post the GR.
Thanks
Dede

In Inbound delivery after GR only a TO is created and confirmed.
So please check the PO history and see a GR is there or not .
Once a GR is found create a TO and do the confirmation

Error message KI248 on delivery document when posting goods issue

Hi,
On the delivery document, when posting goods issue I get the following message:
"Account 60700000 requires an assignment to a CO object
Message no. KI248
Diagnosis
All given account assignment objects (order, project) are defined as statistical.
System Response
Statistical orders or projects are ignored when FI and CO are reconciled. You must enter a cost center, order, project, or cost object to which the costs are posted for CO postings.
Procedure
Enter a cost center, an order, a project, or a cost object that is not statistical. The posting row affected is 000 and the account is 60700000."
On the sales order I have a statistical order.
CO-PA is active, cost element 607 is included in PA transfer structure.
I also tried with cost center allocation in OKB9.
60700000 is defined as a cost element (category 1).
Any suggestion could be helpfull.
Thanks,
Lavinia

Hi,
Thank for your answer.
I tested with element cost category 12, it's working, but not the way I need: I don't have any value on the cost center.
When I don't have statistical order in sales order, the sistem it's working exactly how I need: the costs are posted on cost center and the VPRS condition is transfered to CO-PA on profitability segment.
Anyway, I finaly make it work with a cost center substitution.
Lavinia

Error in creating delivery document from stock transport order

hi sd gurus plz help i m nt able to create delivery in vl10b from stock transport order me21n after giving shipping point and po number also. can u help me out and can u tell me how to maintain copy control from stock tarnsport to delivery docu.

Hi Debesh,
The settings for Delivery type for STO is maintained using the following path:
Materials Management>Purchasing>Purchase Order>Set up Stock Transport Order>Assign Delivery Type and Checking Rule . Here you assign the Delivery type to Stock Transport order (with reference of Suplying Plant)
For creation of STO for delivery creation use T-code- VL04. Enter the Relevant Shipping Point and the Delivery Creation Date. Also tick mark the option Purchase order. If you already have a Purchase order enter the no.
System will show the details of the STO here by using the Main Menu > Delivery> Create Deliveries you can create the Delivery against the STO. Then by using the VL02n option you can do the Picking / PGI for the Delivery.
Hope the above helps you.
REWARD if it helps you!!
Regards,
Ajinkya

Error facing in delivery document entry

Hi,
I am facing one problem in entering of delivery document in sale module so please give me solution.
Problem: Dump problem please contact to SAP service support person; Problem distribute location...
SAP/SAP business one/SAP Business One_20100813114543.dmp
Please give me the solutions ASAP
Thanks,
Surendra.

Dear GordonDu
Apologize for yesterday's my reply.... (some problem in internet side that's reason i was not posted proper message to you)
Issue: I was facing this problem in all clients and all users. Please give the salutation as soon as possible.
And one thing, How to send any attachments to you for this issue (like dmp file or some screen shots for the problem)?
Thanks,
Surendra

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.

Address error in delivery document

Similar Messages

Maybe you are looking for