Skip to Content
avatar image
Former Member

Validation with data file failed...

We are on BPC10.0NWSP10

I am loading master data attributes from BW InfoObject and have written a start routine in the BADI UJD_ROUTINE as suggested by the HTG on this topic to filter certain values.

When I include the line STARTROUTINE = ZUJ_START_ROUTINE_EX_IMP under the *OPTIONS, upon "Validate & Process Transformation File" with the BW InfoObject MD, I am getting the following error:

[Start validating transformation file] Validating transformation file format Validating options... Validation of options was successful. Validating mappings... Validation of mappings was successful. Validating conversions... Validation of the conversion was successful Creating the transformation xml file. Please wait... Transformation xml file has been saved successfully. Begin validate transformation file with data file... [Start test transformation file] Validate has successfully completed Validation with data file failed

My transformation file looks like as follows:



Not sure what might be causing this error.

If I remove the last line (STARTROUTINE = ZUJ_START_ROUTINE_EX_IMP) the transformation file validates and processes successfully and MD loads, albeit incorrectly(since it does not call STARTROUTINE to do what we have implemented in the BADI).

Any thoughts?


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Dec 23, 2014 at 07:13 PM

    Hi Coomar,

    Then the error is in the badi code...


    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 24, 2014 at 07:53 AM

    Hi Coomar,

    Try run the package, and see any short dumps in ST22.

    You don't have to validate with real data to save the transformation file.

    Or just debug and step through your code if no short dumps from the BADI.


    Add comment
    10|10000 characters needed characters exceeded

  • Dec 23, 2014 at 08:40 PM

    If you've written a BADI you probably know how to debug it๐Ÿ˜Š.

    First of all, why do you need a BADI for filtering? There is a UI package that provides a wide range of filtering options.

    Second, if your filtering rules are so complex that only BADI can handle them, why START BADI and not END BADI? In START BADI data comes in delimited format and you have to parse it to get to individual element. In END BADI data is already parsed and each element is in a certain field of internal table.

    If you still want to have that START BADI just put a break-point at the end and check what data you returning in the table.

    Add comment
    10|10000 characters needed characters exceeded