DSXchange

Ok, that means the error has occurred before that column. You will still need to put in some time and effort in locating the cause.

WMM_CROSS_RFRN_ACCT_NR is probably a COMP-3 field and the error means that your metadata doesn't match the data. There is no easy way to solve this, you need to match the metadata with the data column by column to find out where the difference occurs. Assume the OCCURS didn't work correctly as a sta...

Flatten all arrays. the OCCURS 2 times will be flattened.

Functionality is the same, performance might be a little slower. I don't like using lookup filesets because you cannot "view data" on them during the development phase. Once you have a functioning job you can convert datasets to lookup filesets so that you can take advantage of the prebuilt indices.

Flatten all would be best. Do you have arrays ("OCCURS" or "OCCURS DEPENDING ON") or just group level, i.e. "10 SUB-GROUP." with no pictures?

try

Does it ask you about flattening?

In PX you cannot take a reject from a transform stage, you need to do it from the Database passive stage. Draw a reject link and activate rejects in the stage details and then either use PEEK or write the errors to a target.

Unfortunately this often ends up being an iterative process. With big copybooks I will delete all but the first 20 columns or so, replacing it with a big VarChar filler field then check with "view data" to see if the columns are parsed correctly. When that is fixed, I will make a copy of the origina...

Your imported copybook metadata does not match that in the file. Did you get any warnings or error while importing the copybook? At the moment your metadata is longer than the actual data.

What are you using the "if" statement for? Is it the derivation of the unique primary key?

The error message is quite clear that you are loading duplicate keys. If you put in a reject link you will see which keys are incorrect and can proceed accordingly.

No, I haven't seen that specific error before, so it might not be one of the ones corrected by the major DS/IIS patch.

Have you contacted your support provider? There are a number of issues with QS8 importing rulesets. There is a wrap-up fix pack that solves many of them. Do you have that applied?

IsNull() won't work here (the 3rd time might be a charm)! Use as your constraint.

Craig - that is what I though as well ... the "shrug" part, I mean. Some performance degradation in all hashed files can be expected as well as growth in file sizes.