Skip to Content
avatar image
Former Member

Regarding Value Exception while Importing the Vendors from ECC using MDIS

Hi All,

I am trying to Import an XML file through Import Server but the issue is some of the records(Vendors) were successfully uploaded into the system while some of the records went into Value Exception. I have tried posting them many a times but all the time i am getting the same output.

1. Can anyone tell that how could i know for which value/field this Exception is coming?

2. Is there any way out to Import the remaining records through Import Manager and which file should be used for that? The one which went into Exception Folder or the one which went into Archive folder?

Please suggest as i am not able to understand the error even from the error message.

The exception what i am getting is:

Partial Set failure with RC error code = <0x84020020> for record number 0 through 189

1

Import Failed!

[MDS=R3-ZM2MDA Repos=EVO_VENDOR ClientSystem=ECC_System Port=EVOVendorOut]: xImporter: Thread ordered to stop: RC = 0xfffffffa

[MDS=R3-ZM2MDA Repos=EVO_VENDOR ClientSystem=ECC_System Port=EVOVendorOut]: xImporter: Thread finished; Start -> End: 0.000000000 seconds.

[&&&_VENDOR]Import Task Finished. Chunk size[50000], No. parallel chunks[5]

Edited by: Gaurav Arora on Jul 7, 2009 4:13 PM

Edited by: Gaurav Arora on Jul 7, 2009 4:25 PM

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Jul 08, 2009 at 06:32 AM

    Hi Gaurav,

    1. The Records that have the Value Exception can be found in the below location

    .../Repository/Inbound/Remote System/Port/Exception/ValueX

    2. The commnon reason for Value Exceptions are usually IMproper Date formats(dd/mm/yyyy Vs mm/dd/yyyy), Improper Currencies, Leading Zeros Required etc

    3. Look at your data and fix the data issue and load the file again.

    4. To answer your question if you have to reprocess the same file as it is then which file to pick: Then you should pick the file from the Archive Directory (Not from Exception).

    5. Other Exceptions can be fixed using the Import Manager: This can be done as follows: Login to the Import Manager > Specify Type = "PORT", Remote System = <Name of Remote System>, Port = <Name of port where you have the exception>. After you are into the Import Manager open the Map used for importing data. Look into the Map and look at the Mapping. This map when opened will also throw an error if it finds any error.

    Hope this helps.

    Thanks,

    SA

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 08, 2009 at 09:03 AM

    MDIS processes import files in three stages:

    ● Structural Transformation Stage - Source tables are impoted following the rules of the import map.

    ● Value Transformation Stage - Source values are converted according to the rules of the import map.

    ● Import Stage - Transformed records are imported into the MDM repository.

    If MDIS encounters a problem at value transformation stage, it sets aside the records containing the error in "ValueX" folder of MDIS Port. Here you can check the records which went wrong during MDIS import.

    So, you need to process all the records from "ValueX" MANUALLY to fix the problems usually a date/Currency/Quantity format mismatches.

    Manually Procedure To Import ValueX records

    1. Open the Import Manager and connect to the MDM repository containing the port where the Value exception was found.

    2. When the Connect to Source dialog appears, choose the source type Port and select the appropriate remote system from the drop-down list.

    3. In the Port drop-down list, select PortName [Exception] where PortName is the name of the port containing the exception.

    The Import Manager loads the first exception file waiting on the port. Because ours is value exception, the value extended record containing the exception opens.

    4. Fix the exception according to the Action Items section of the Import Status tab and save the corrected map.

    5. To fix any other exceptions waiting on the port, choose File -> Get Next Source File from the main menu

    for Further reference refer the below link

    http://help.sap.com/saphelp_mdm550/helpdata/en/43/12036df94c3e92e10000000a1553f6/frameset.htm

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 08, 2009 at 11:42 AM

    HI Gaurav,

    Check the import map . There should be some problem in the import map.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 08, 2009 at 11:48 AM

    Hi gaurav

    You can check for the records ID which failed to import in the MDIS log files. For reimporting we manually connect to the ValueX folder in Exception directory and pick the files and use interactive import manager capability for knowing which fields or value mappings are failing.

    regards

    Ravi

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Have anyone had the error "Source file does not conform to XML schema. Element <TEXT> not found in the xml schema" when trying to open the ValueX exception in the Import Manager type Port?

      What I noticed is the ValueX xml file structure is different than that of the standard output xml schema. Anyone else facing this issue? We're currently unable to open ValueX exceptions through the Import Manager type Port.

      We're running MDM 7.1