Data error handling documents

Dear Freinds,
can any one send error handling documents for data loads.
Regards,
Pavan

Pavan,
<b>load failed .
fullload-- masterdata or transcational data-- data in PSA--- directly update from PSA by deleting request in data target.</b>
Yea you can update the data from the PSA if the data is correct.
<b>full load -- master data or transcation data-- no PSA- schedule the infopackage again.</b>
Yes when you have no data backup in BW (PSA) you need to extract data from the source system. In case of delta if the load fails you can repeat the delta load which extracts data from source system.
<b>delta load- master data or transactional data data in PSA-- directly update from PSA by deleting request in data target.</b>
<b>delta laod-- master data or transactional data- no psa- schedule the IP again.</b>
If the delta load fails you can repeat delta even if the data is present in the PSA or not
<b>also when we go for repair full request and repeat delta?</b>
You can go for repair full request only when you have data in PSA.

Similar Messages

  • Date Error in the billing

    Hi Experts
    I have senario here where the Invoice was created in four times and cancelled and the date of creation and t he cancellation was on 16.03.2010  and the fourth one invoice created on 16.03.2010 and cancelled on 18.03.2010 and agin when trying to create with refering the same delivery used in all the cases Error says Date error. Document date 16.03.2010 older than last assigned date 18.03.2010"
    Please advise
    thanks in advance

    Hi
    Kindly check the belwo:
    1.Can you check the number ranges maintained for the J_1AOFFDOC
    2.Last assigned date for the relevant combination of company code, subsidiary, document class in the table OFNUM_TW_2 .
    Means the date assigned in the above table is different from the PGI date so check the date and assign the same date in vf01
    Regards'
    Damu

  • Can't delete file after renaming due to Word file handle still present. Error staes document is still in use but it's really not. Worked fine in 2007 but not in 2010.

    I have some code associated with a Word Template. The template is opened, filled out and saved via a routing in vba. This all works fine in older 2007 version (which is version it was originally created in). Once this file is saved, the user can change the
    date in a text box and re-save document. The code saves using the new date for part of new file name and then deletes that older file from the server. It fails at the delete function because the newer version of word is not dropping the file handle from the
    first named file when user saves it to the new filename. In older version (2007) this handle was released as soon as file was saved to a different name. I can't seem to figure out how to release the old document filename so the old document file can be deleted.
    I hope I explained this well enough.
    Here's the code that woeked in version 2007 but fails in version 2010.
    Option Explicit
    Dim CAPEX01 As MSForms.ComboBox
    Dim CAPEX02 As MSForms.ComboBox
    Dim LocalPath As String
    Dim NetPath As String
    Dim OldPath As String
    Dim OldPathNet As String
    Dim DocName01 As String
    Dim DocName02 As String
    Dim DocName03 As String
    Dim DocName04 As String
    Dim DocName As String
    Dim DocNameold As String
    Dim TestDocName As String
    Dim filesys
    Dim newfolder
    Sub AutoOpen()
    ActiveDocument.ActiveWindow.View.Type = wdPrintView
    TestDocName = ActiveDocument.TextBox2
    OldPathNet = "\\yourPath\" & TestDocName & "\"
    End Sub
    Sub AutoNew()
    TestDocName = ActiveDocument.TextBox2
    OldPathNet = "\\yourPath\" & TestDocName & "\"
     ComboBox1.Locked = False
     ComboBox1.Enabled = True
     FillList1
     FillList2
     End Sub
    Sub DeleteOldDoc()
    OldPathNet = "\\yourPath\" & TestDocName ' & "\"
    DocNameold = OldPathNet & TestDocName & "-" & DocName02 & "-" & DocName03 & "-" & DocName04 & ".doc"
        If Not TestDocName = DocName01 Then
            Set filesys = CreateObject("Scripting.FileSystemObject")
        If filesys.FileExists(DocNameold) Then
            filesys.DeleteFile (DocNameold), True      
     'I get file permission error here
        End If
        End If
    If DocName01 <> "" Then
    If Not TestDocName = DocName01 Then
    If Not TestDocName = "" Then
        MsgBox "Project Proposal Has Been Moved From Year " & TestDocName & " To " & DocName01 & ""
    End If
    End If
    End If
    TestDocName = DocName01
    End Sub
    '''''''Document path functions''''''
    Sub chkpath()
    Set filesys = CreateObject("Scripting.FileSystemObject")
    If Not filesys.FolderExists("\\yourPath\") Then
       newfolder = filesys.CreateFolder("\\yourPath\")
    End If
    If Not filesys.FolderExists("\\yourPath\" & DocName01 & "\") Then
        newfolder = filesys.CreateFolder("\\yourPath\" & DocName01 & "\")
    End If
    End Sub
    ''''''Save Function''''''
    Private Sub CommandButton1_Click()
    DocName01 = ActiveDocument.TextBox2
    DocName02 = ActiveDocument.TextBox4
    DocName03 = ActiveDocument.TextBox1
    DocName04 = ActiveDocument.ComboBox1.Value
    chkpath
    NetPath = "\\yourPath\" & DocName01 & "\"
    DocName = NetPath & DocName01 & "-" & DocName02 & "-" & DocName03 & "-" & DocName04
    ActiveDocument.SaveAs2 FileName:=DocName, FileFormat:=wdFormatDocument
     ComboBox1.Locked = True
     ComboBox1.Enabled = False
     ComboBox2.Locked = True
     ComboBox2.Enabled = False
     TextBox1.Locked = True
     TextBox1.Enabled = False
     TextBox3.Locked = True
     TextBox3.Enabled = False
     TextBox4.Locked = True
     TextBox4.Enabled = False
     DeleteOldDoc
    End Sub
    Sub FillList1()
    Set CAPEX02 = ActiveDocument.ComboBox2
      With CAPEX02
          .AddItem "CASTING", 0
          .AddItem "HOT ROLLING", 1
          .AddItem "COLD ROLLING", 2
          .AddItem "FINISHING", 3
          .AddItem "PLANT GENERAL", 4
          .AddItem "MOBILE EQUIPMENT", 5
      End With
    End Sub
     Sub FillList2()
     Set CAPEX01 = ActiveDocument.ComboBox1
      With CAPEX01
          .AddItem "A Name", 0
          .AddItem "Another Name", 1
      End With
    End Sub
    Private Sub CommandButton2_Click()
        UserForm1.Show
    End Sub

    mogulman52 and Don,
    I went back and looked at my code and had already updated it to SaveAs in the new docx format. It still holds the lock handle in place until Word closes, unlike earlier versions which released the lock handle when you did a SaveAs.
    As a note, all my Word and Excel macro-enabled (dotm & xltm) templates are read only and are never filled in, prompting the user for a file name on any close event or if they run the code gets auto-named. I do the SaveAs and concatenate the file name
    from data on the document (or sheet) that has been filled in. During the SaveAs the docx gets saved to a network folder and also on a local folder. The lock gets renamed to the filename and remains until Word is closed.
    So my code still fails at the point noted below while trying to delete an old filename version after the file has been saved as a new filename in a new folder. So....
    The code is looking in the last folder where the docx file was saved for the older filename so it can be deleted. The newest docx version has already been saved in a different folder and has a new lock handle of its own. That lock is not my problem, it's
    the older file lock which really exists in the same folder as the first filename that the docx was saved to. It does not release that lock until I exit Word. My work around has been to instruct all users to manually delete the older version file.
    The other odd thing is this only happens when I run it from code, if you manually go through these steps with the SaveAs menu drop-downs in Word it will release the lock handle???
    Hope this isn't to confusing and thanks for all your suggestions and help.
    Sub DeleteOldDoc()
    OldPathNet = "\\yourPath\" & TestDocName ' & "\"
    DocNameold = OldPathNet & TestDocName & "-" & DocName02 & "-" & DocName03 & "-" & DocName04 & ".doc"
    If Not TestDocName = DocName01 Then
    Set filesys = CreateObject("Scripting.FileSystemObject")
    If filesys.FileExists(DocNameold) Then
    filesys.DeleteFile (DocNameold), True 'I get file permission error here- lock handle is still present from last SaveAs command in last folder where previous version of file was saved.
    End If
    End If
    If DocName01 <> "" Then
    If Not TestDocName = DocName01 Then
    If Not TestDocName = "" Then
    MsgBox "Project Proposal Has Been Moved From Year " & TestDocName & " To " & DocName01 & ""
    End If
    End If
    End If
    TestDocName = DocName01
    End Sub
    Glenn

  • Step by Step documents for Process Chain Error Handling with Screen Shots

    Hi
    Is anybody having Step By Step Documents for Process Chain Error Handling with Screen Shots ?. Please forward it to me to my e-mail [email protected] .  I will reward points to u immediately.
    bye
    Aamira Khan

    Hi,
    You can find lots of topic related to process chain issues in SDN.Please make a search in SDN.
    https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_library&query=process+chain&adv=true&sdn_author_name=&sdn_updated_on_comparator=ge&sdn_updated_on=&sortby=cm_rnd_rankvalue
    Regards.

  • Error handling for master data with direct update

    Hi guys,
    For master data with flexible update, error handling can be defined in InfoPackege, and if the load is performed via PSA there are several options - clear so far. But what about direct update...
    But my specific question is: If an erroneous record (e.g invalid characters) occur in a master data load using direct update, this will set the request to red. But what does this mean in terms of what happens to the other records of the request (which are correct) are they written to the master data tables, so that they can be present once the masterdata is activated, or are nothing written to masterdata tables if a single record is erroneous???
    Many thanks,
    / Christian

    Hi Christian -
    Difference between flexible upload & Direct upload is that direct upload does not have Update Rules, direct upload will have PSA as usual & you can do testing in PSA.
    second part when you load master data - if error occurs all the records for that request no will be status error so activation will not have any impact on it i.e. no new records from failed load will be available.
    hope it helps
    regards
    Vikash

  • Persisting the post data while handling errors in STRUTS

    hi,
    Let me explain my situation.
    I have an updation form.On click of the update button I am doing some validations in my Action class.In case of any error it will redirect back to the input page.
    Now comes my problem.As I have told you,my form is an updation form.So it contains field already set with some values,a bean.When the error ,redirects control back to the input page,the newly enterd data,which has errors is not displayed and instead the old bean contents are resetted.
    How to persist the newly entered data?
    Any suggestions will be helpful,
    thanks,
    vysh

    Hi David, could you help me to write this kind of routine? (Like ON-ERROR Oracle Forms)
    I have tryed to follow a lot of examples published in this forum, but none of then are working properly.
    In the URLs bellow you will see that a lot of people are looking for the same solution.
    Re: Catching ORA errors in Validations
    Error Trapping
    Error Handling
    Handling Oracle error messages
    Re: Catching Unique constraint error.??
    Re: how to get custom error mwssage
    Re: showing oracle error ID
    Thanks
    Nilton
    Message was edited by:
    Nilton Maganha

  • IDCS3   error message "Cannot add data to unknown document"

    I am using a Mac and last week I opened an ID document from my flash drive, worked on it, saved it back to my flash drive and reopened it just to make sure it saved right. Now when I try to open it, it says "Cannot add data to unknown document". All the permissions look fine. Is it a file problem? Is there anything I can do to recover it?

    That is a very dangerous workflow. NEVER work off of removable media.
    Always copy to your harddrive and work there.
    That said, try copying the file to your harddrive now and working on that.
    Bob

  • Error handling in process chain-doubts

    Hi ,
    I have some doubts in error handling of process chains.
    1) I have  aprocess load infopackeage and subsequent process is update fromPSA.
    process load infopackage got failed  , so i loaded  the IP manually and repeated the next i.e process update from PSA .
    How to correct the process chain from now?
    2) I have  aprocess load infopackeage and subsequent process is Delete request in infocube .process load infopackage got failed  , so i loaded  the IP manually and repeated the next process i.e Delete request in infocube. Chain continued by deleting the right request . How this is possible ?
    Plz  help me  as this is urgent and daily i have to deal with this  issues. If any documents on error handling is greatly appreciated.
    My mail id is [email protected]
    Regards,
    Pavan

    Hi Pavan,
    Hope the following links will give u a clear idea about process chains and clear ur doubts.
    Business Intelligence Old Forum (Read Only Archive)
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    Errors in monitoring of process chains can be categorized into 4 different sections...
    Master data - Full Update
    Master data - Delta Update
    Transaction data - Full Update
    Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
    Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
    There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
    In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
    For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
    U can even look into these links:
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    For common data load errors check this link:
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    ****Assign Points if Helpful****
    Regards,
    Ravikanth.

  • (ID 30101 Details: Data error (cyclic redundancy check) (0x80070017)) _More information

    Hi,
    Can anyone please help with this?  Our Tape Drive died and we got a new one from our Maintenance Company. Since then large backups to tape are failing.  When the jobs are small they seem to go through OK but when the job is greater than around
    200GB then it fails with the error below.
    I tried updating the tape drive driver but Windows said that the drive wasn't functioning properly any more.
    The only difference between the old faulty drive and the new drive is the firmware.  We used to have A422 in the old drive.  The new drive has  D8D5.  Can someone please help as it's driving me crazy.
    "Affected area:
    IBM TotalStorage 3573 Tape Library
    Occurred since: 03/03/2015 10:19:37
    Description: Library drive IBM ULTRIUM 5 HH 3580 TAPE DRIVE (1068006186) in IBM TotalStorage 3573 Tape Library is not functioning and library jobs may fail until the drive is repaired.
     The drive is not functioning for the following reason:
     (ID 3303)
    DPM encountered a critical error while performing an I/O operation on the tape Physical Servers-LT-MonthlyBackup-00000235 (000086L4) (Barcode - 000086L4) in Drive IBM ULTRIUM 5 HH 3580 TAPE DRIVE (1068006186).
    (ID 30101 Details: Data error (cyclic redundancy check) (0x80070017))
    More information
    Recommended action:
    Retry the operation. If the problem persists, contact your hardware vendor.
    No action required
    Resolution: To dismiss the alert, click below
    Inactivate"
    Regards
    Willie

    Hi,
    It sounds like another faulty drive - You can try to reproduce the problem outside of DPM using some external utilities.   If you get an error before the tape fills you can use net helpmsg errorcode to see what the error was.
    Download the DPMerasetape.zip file from the following link and extract to c:\temp folder.
    https://onedrive.live.com/?cid=b03306b628ab886f&id=B03306B628AB886F%21524&sc=documents
    The utilities are not that user friendly, but here are the basics.
    Always Stop DPMLA Service prior to running MCT.EXE Commands.
      NET STOP DPMLA
    C:\> mct-x64.exe -p
    Opening changer \\.\Changer0
         ********** Changer Parameters **********
             Number of Transport Elements : 1
             Number of Storage Elements : 50
             Number of Cleaner Slots : 0
             Number of of IE Elements : 0
             Number of NumberDataTransferElements : 6
             Number of Doors : 0
             First Slot Number : 0
             First Drive Number : 0
             First Transport Number : 0
             First IEPort number : 0
             First Cleaner Slot Address : 0
             Magazine Size : 0
             Drive Clean Timeout : 600
      Flags set for the changer :
             CHANGER_BAR_CODE_SCANNER_INSTALLED
             CHANGER_POSITION_TO_ELEMENT
             CHANGER_STORAGE_DRIVE
             CHANGER_STORAGE_SLOT
             CHANGER_DRIVE_CLEANING_REQUIRED
             CHANGER_VOLUME_IDENTIFICATION
             CHANGER_VOLUME_SEARCH
             CHANGER_SERIAL_NUMBER_VALID
     Changer can move from Slot to :
                     Slot
                     Drive
     Changer can move from Drive to :
                     Slot
                     Drive
     Changer is Capable of positioning transport to Slot.
     Changer is Capable of positioning transport to Drive.
    C:\> mct-x64.exe -d
    Opening changer \\.\Changer0
    Product Data for Medium Changer device :
      Vendor Id    : STK
      Product Id   : L180
      Revision     : 030
      SerialNumber : 3077520000
    For MCT utility we have the  -m [MOVE] command to move media around inside the library.
    -m [ElemType-T] Transport# [ElemType-Source] S_lot#/D_rive# [ElemType-Destination] S_lot#/D_rive#
    Get / view command syntax for –m (move) command for changer 0
    C:\>mct-x64 0 -m
    Opening changer \\.\Changer0
    MoveMedium : mct -m t N s\d N s\d N   [Where s/d means Slot or Drive and N is ZERO based].
    Some Examples:
    mct-x64 -m t 0 s 0 d 0    (Using transport-0, move media from slot-0  to drive-0)
    mct-x64 -m t 0 d 0 s 0    (Using transport-0, move media from drive-0 to slot-0)
    mct-x64 -m t 0 s 0 s 100  (Using transport-0, move media from slot-0  to slot-100)
    mct-x64 -m t 0 d 0 d 1    (Using transport-0, move media from drive-0 to drive-1)
    mct-x64 -m t 0 s 0 ie 0   (Using transport-0, move media from slot-0  to IEPort 0)
    Once you move a tape into a drive, use mytape commands Loadtape, taperewind, locktape, Disable hardware compression, Set block size to 65536 (64K), writeforspanning.
    You need the symbolic name for the tape drive you loaded media into - look in the DPM console by clicking the tape drive and look at the details for
    \\.\tape########.  use that in the following command.
    Mytape.exe \\.\Tape2147483638
    Status: Getting the handle for \\.\Tape2147483638...Success
    TapeConsole_1.0>taperewind">\\.\Tape2147483638>TapeConsole_1.0>taperewind
    Status: Rewinding Tape ...Success
    TapeConsole_1.0>setdriveinfo">\\.\Tape2147483638>TapeConsole_1.0>setdriveinfo
    Hardware error correction  [y]-Enable / [n] Disable : y
    Hardware data compression  [y]-Enable / [n] Disable : N   (BE SURE TO DISABLE)
    Data padding  [y]-Enable / [n] Disable : n
    Setmark reporting   [y]-Enable / [n] Disable : n
    Number of bytes between the end-of-tape warning and the physical end of the tape: 0
    Status: Setting Drive Information...Success
    TapeConsole_1.0>writeforspanning">\\.\Tape2147483638>TapeConsole_1.0>writeforspanning
    Status: Writing onto tape...Failed !!!
    Error_ID reported: 1100                 (net helpmsg 1100
    = The physical end of the tape has been reached.
    Number of bytes written: 983040     (Ignore bytes written, we'll get physical tape position later)
    Giving up
    Time taken: 15788ms
    TapeConsole_1.0>taperewind">\\.\Tape2147483638>TapeConsole_1.0>taperewind
    Status: Rewinding Tape ...Success
    REPEAT
    TapeConsole_1.0>erasetape">\\.\Tape2147483638>TapeConsole_1.0>erasetape s
    Short erase / Long Erase [s/l]:Status: Erasing the tape...Success
    \\.\Tape2147483646...Success
    c:\>mct-x64.exe -m t 0 d 0 s 0
    Opening changer \\.\Changer0
    Source is a Drive
    Destination is a Slot
    Move : Transport - 0, Src - 0, Dest - 0
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • For IDOC monitoring, analysis and error handling in  ALE & idoc

    Hello...experts..can u please tell me about idoc monitoring,analysis and error handling..and can u please tell as per interview  point of view in this area..if availble can u send material about this...
    thx
    Message was edited by:
            durga kottapalli

    Hi,
    Reprocessing IDocs with errors
    Outbound (BD88)
    Once the error has been determined and corrected it is not necessary to resend the IDoc again. You simply resend the IDocs that have already been generated.
    Using the IDoc overview screen you need to take note of the following for each IDoc that was not processed:
    Error number: 2, 4, 5, 25, 29
    Error number: 30 (Execute Check IDoc dispatch to process)
    IDoc number
    Using the Error number, the IDoc number and the transaction BD88 , with the required message type you can resend the IDoc. Match the error number with this transaction and execute the function for the IDocs incorrectly processed.
    Just check the below link, u will get all IDOC related Interview questions
    http://www.allsaplinks.com/idoc_sample.html
    http://www.allsaplinks.com/
    http://www.sappoint.com/abap.html
    http://www.sap-img.com/
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    http://www.sappoint.com/abap.html
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sap-img.com/
    http://www.allsaplinks.com/
    Regards,
    Suresh.
    Message was edited by:
            SureshKumar Ramamoorthy

  • Effective error handling in Adapter Module

    eX(i)perts..
    Can anybody share the effective error handling strategies inside adapter modules?
    Specifically looking for
    1. Module parameters configuration related error handling
    2. Business logic failure owing to incorrect data.
    -- Amol

    Hi,
    Please see the following PDF documents to develop the Module processor programs.
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/02706f11-0d01-0010-e5ae-ac25e74c4c81
    http://help.sap.com/saphelp_nw04/helpdata/en/0d/00453c91f37151e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/02706f11-0d01-0010-e5ae-ac25e74c4c81
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e21106cc-0c01-0010-db95-dbfc0ffd83b3
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9913a954-0d01-0010-8391-8a3076440b6e
    help : http://ifr.sap.com
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6f83d790-0201-0010-629d-ab5bf10c94e4
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7bf6e190-0201-0010-83b7-cc557eb76abe
    Some weblogs for JAVA mapping for IDoc mapping
    /people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-i
    /people/prasad.ulagappan2/blog/2005/06/29/java-mapping-part-ii
    Difference in using java,xslt,message mapping
    Regards
    Chilla..

  • Error Handling for BAPI MB_COUNT_POST_WITHOUT_INV_DOC for MI10 Transaction

    Hi,
    Can any one suggest me, how to handle the errors for the BAPI MB_COUNT_POST_WITHOUT_INV_DOC, because this bapi does not have any return table for errors handling? And also suggest any other BAPI which fits for MI10 transaction.
    <removed by moderator>
    Thanks&Regards,
    Damuan.
    Edited by: Thomas Zloch on Feb 2, 2012

    Hi Dear,
    Your answer is very helpful, thanks..!!
    But when  i am testing with the EIKPF structure, neither error is populating in EIKPF  nor the records are  posting in MI10. Could you please guess what would be the problem?
    Below are the fields that i am passing through this BAPI
    1)Document date 2)count date 3)plant 4)storage location 5)item number 6)material code 7) entry quantity
    Thanks&Regards,
    Damuan.

  • ESB error handling and notification features

    Hello everyone,
    I am newbie to oracle SOA ESB. I am an oracle apps guy.
    This being my first post to this forum, I have a lot of questions. :-)
    For a small intergration requirement, we are looking for a good integration tool
    Some requirements are:
    1) Flat files will be generated by concurrent programs on oracle apps which need to be transferred to legacy systems.
    2) Pick the data from apps tables and insert them into another database. Not much translation required.
    After some research, found ESB to be a good fit.
    Before actually start using it, we wanted to do a couple of POCs.
    So far we are using shell scripts for ftp process. We opted for an integration tool to have DB to DB transmission. Apart from this we need better error handling and error notification mechanism.
    Some error conditions:
    1) Unavailability of ftp server or Database server.
    2) Permission issues. Say some files may not have read, write, deletion permissions. They need to be caught and notified.
    3) Mandatory field missing while inserting data which is read from a flat file into a DB table etc..
    My initial thoughts on error handling are:
    Connection error: To retry for connection errors. If the retry fails send notification via email and also write the failed connection details into an error log file(apart from the server log file).
    Data mismatch: NOtification to be sent with the error details.
    I would like to know What happens to the file if the destination ftp server is unavailable while ESB is trying to FTP the file. Will ESB retain the file with itself and FTP the file once the ftp server is up?
    In BPEL I could see try catch blocks which can be used to handle the errors and thus send notifications.
    ESB documents introduced terms like error hospital related to error handling but I was not able to figure out a way of implementing them. As I am not well versed with XML and WSDL I am probably unable to use the fault tab which is in the routing service. I feel Oracle could have given some samples that explain about ESB error handling.
    Also to my dismay, adapter docs say that there is a limitation of 7MB size for ftping. Although our file sizes often fall below this size, I would want to know if there is any workaround to over come this size constraint.
    I think I put a lot of stuff in a single post and may be in the most haphazard way. Please bear with me.
    Please suggest me of some documents if any related to my questions.
    Would be really great if you can give me a straight forward solution to all the above problems
    Hope this forum would be a great help to me.
    Cheers,
    Robert.

    I have worked on a few SOA Apps implementations. Some successful and some not so. It really comes down to the type of integrations.
    But I would say the majority of your integration will be batch as this is what eBus is all about. If this is the case then I would recommend Oracle Data Integrator. If you go Oracle Data Integrator Suite it includes Service Bus and BPEL. ODI has an eBusiness Suite adapter as well.
    The good thing about ODI is that you can use it for data conversion, that conversion can then be reused once live, so the conversion is not throw away.
    In SOA 10.1.3.4 the limit of 7MB has been resolved but you must be using the file / FTP adapter for input and out, from the sounds of it you want to call concurrent programs so this probably wouldn't work.
    cheers
    James

  • Error handling in bdc Fb01along with erros in Idoc.

    Hi,
    Can any one send me the sample code for the error handling in bdc Fb01along with erros in Idoc. Actually, mail should be sent
    Thanks
    Avi.

    Hi,
    This may help you.
    <b>FORM send_mail USING   receiver.
      CLEAR: w_lines,tbl_packing_list,tbl_object_header,
                 tbl_contents_txt, tbl_receivers.
      REFRESH:tbl_packing_list, tbl_object_header,
               tbl_contents_txt,tbl_receivers.
      SORT tbl_err.
      DELETE ADJACENT DUPLICATES FROM tbl_err COMPARING ALL FIELDS.
      IF NOT tbl_err[] IS INITIAL.
    Preparing the email.
        PERFORM prepare_email.
      ELSE.
       If sy-subrc NE 0.
          MOVE sy-subrc TO w_code.
       ENDIF.
        EXIT.
      ENDIF.
    Get  the content of header e-mail document data
      PERFORM document_data.
    Get details of the error file attached (like type of file and format)
      PERFORM packing_list.
    Get receiver mail id's
      tbl_receivers-receiver = receiver.
      tbl_receivers-rec_type = 'C'.
      tbl_receivers-express  = c_flag.
      tbl_receivers-sap_body = c_flag.
      APPEND tbl_receivers.
    Call FM to send E-mails to receivers
      CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
           EXPORTING
                document_data              = st_document_data
                put_in_outbox              = 'X'
           TABLES
                packing_list               = tbl_packing_list
                object_header              = tbl_object_header
                contents_txt               = tbl_contents_txt
                receivers                  = tbl_receivers[]
           EXCEPTIONS
                too_many_receivers         = 1
                document_not_sent          = 2
                document_type_not_exist    = 3
                operation_no_authorization = 4
                parameter_error            = 5
                x_error                    = 6
                enqueue_error              = 7
                OTHERS                     = 8.
    ENDFORM.                    " send_mail
    *&      Form  prepare_email
          text
    -->  p1        text
    <--  p2        text
    FORM prepare_email.
    E-Mail body content
      IF NOT w_lifnr IS INITIAL.
        CONCATENATE text-015 w_docnum text-016
               INTO tbl_contents_txt-line
          SEPARATED BY space.
      ENDIF.
      APPEND tbl_contents_txt.
      CLEAR tbl_contents_txt.
    E-mail error file attachment header
      CONCATENATE text-063 text-064
                   text-065 text-066 c_comma
             INTO tbl_contents_txt-line
        SEPARATED BY c_comma.
      APPEND tbl_contents_txt.
      CLEAR tbl_contents_txt.
    E-mail error file attachment content
      LOOP AT tbl_err.
        CONCATENATE w_docnum tbl_err-v_segnum
                    tbl_err-msg tbl_err-type
          INTO tbl_contents_txt-line
          SEPARATED BY c_comma.
        CONCATENATE c_linefeed tbl_contents_txt-line c_comma
               INTO tbl_contents_txt-line.
        APPEND tbl_contents_txt.
        CLEAR tbl_contents_txt.
      ENDLOOP.
    ENDFORM.                    " prepare_email
    *&      Form  document_data
          text
    -->  p1        text
    <--  p2        text
    FORM document_data.
      CLEAR w_line.
      IF NOT w_lifnr IS INITIAL.
        CONCATENATE text-075 text-027 sy-datum sy-uzeit INTO w_line
        SEPARATED BY c_uscore.
      ENDIF.
      st_document_data-obj_name  = w_line.
      st_document_data-obj_descr = w_line.
      st_document_data-priority  = 1.
      st_document_data-obj_prio  = 1.
    ENDFORM.                    " document_data
    *&      Form  packing_list
          text
    -->  p1        text
    <--  p2        text
    FORM packing_list.
      CLEAR w_lines.
      DESCRIBE TABLE tbl_err LINES w_lines.
      READ TABLE tbl_contents_txt INDEX w_lines.
      tbl_packing_list-head_start = 1.
      tbl_packing_list-head_num   = 1.
      tbl_packing_list-body_start = 1.
      tbl_packing_list-body_num   = 1.
      tbl_packing_list-doc_type   = 'RAW'.
      APPEND tbl_packing_list.
      tbl_packing_list-head_start = 1.
      tbl_packing_list-head_num   = 0.
      tbl_packing_list-body_start = 2.
      tbl_packing_list-body_num   = w_lines + 1.
      tbl_packing_list-doc_type   = 'CSV'.
      tbl_packing_list-obj_descr  = 'Error_Attachment'(060).
      IF NOT w_lifnr IS INITIAL.
        tbl_packing_list-obj_name   = 'Idoc Number is'(072).
      ENDIF.
      tbl_packing_list-doc_size   = 255 * ( w_lines + 1 ).
      APPEND tbl_packing_list.
    ENDFORM.                    " packing_list
    </b>
    Thanks
    Manju.

  • How to edit inbound idoc with data errors in multiple segments and reproces

    Hi friends,
    i have a requirement for error handling of inbound sales order(ORDERS04) without using WORKFLOW and WE19.
    i have seen some function modules like edic_* ..
    but my doubt is how to edit the error data(how can i identify the particular error fileds in the segments)and how to reprocess the same idoc.
    Please help me...
    Thanks in advance

    Hi Narasimh,
    Please find the following steps to edit IDOC segment after you find the error using WE02.
    The example codes can be found in website 
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    STEP 1 - Open document to edit
    CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
           EXPORTING
                document_number               = t_docnum
           IMPORTING
                idoc_control                  = itab_edidc
           TABLES
                idoc_data                     = itab_edidd
           EXCEPTIONS
                document_foreign_lock         = 1
                document_not_exist            = 2
                document_not_open             = 3
                status_is_unable_for_changing = 4
                OTHERS                        = 5.
    STEP 2 - Loop at itab_edidd and change data
    LOOP AT itab_edidd WHERE segnam = 'E1EDKA1'.
      e1edka1 = itab_edidd-sdata.
      IF e1edka1-parvw = 'LF'.
        e1edka1-partn = t_eikto.
        itab_edidd-sdata = e1edka1.
        MODIFY itab_edidd.
        EXIT.
      ENDIF.
    ENDLOOP.
    STEP 3 - Change data segments
    CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
               TABLES
                    idoc_changed_data_range = itab_edidd
               EXCEPTIONS
                    idoc_not_open           = 1
                    data_record_not_exist   = 2
                     OTHERS                  = 3.
    STEP 3a - Change control record
    CALL FUNCTION 'EDI_CHANGE_CONTROL_RECORD'
           EXPORTING
                idoc_changed_control         = itab_edidc
           EXCEPTIONS
                idoc_not_open                = 1
                direction_change_not_allowed = 2
                OTHERS                       = 3.
    STEP 4 - Close Idoc
    Update IDoc status
    CLEAR t_itab_edids40.
      t_itab_edids40-docnum      = t_docnum.
      t_itab_edids40-status      = '51'.
      t_itab_edids40-repid       = sy-repid.
      t_itab_edids40-tabnam      = 'EDI_DS'.
      t_itab_edids40-mandt       = sy-mandt.
      t_itab_edids40-stamqu      = 'SAP'.
      t_itab_edids40-stamid      = 'B1'.
      t_itab_edids40-stamno      = '999'.
      t_itab_edids40-stapa1      = 'Sold to changed to '.
      t_itab_edids40-stapa2      = t_new_kunnr.
      t_itab_edids40-logdat      = sy-datum.
      t_itab_edids40-logtim      = sy-uzeit.
      APPEND t_itab_edids40.
      CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
           EXPORTING
                document_number  = t_docnum
                do_commit        = 'X'
                do_update        = 'X'
                write_all_status = 'X'
           TABLES
                status_records   = t_itab_edids40
           EXCEPTIONS
                idoc_not_open    = 1
                db_error         = 2
                OTHERS           = 3.
    Hope this will help.
    Regards,
    Ferry Lianto

Maybe you are looking for