DSXchange

Ah... sorry. Thought you missed it.

Or explain to us exactly how you are doing it... right now it's a little light on details.

eostic wrote:Without seeing the xsd it is hard to say

Scroll up.

Ah... thanks. Wasn't aware of that little nuance with the new stage.

That's fine... I guess I was hoping there was a little more detail in the error messages with regards to the nature of the issue. Something more than a "mapping error". Sorry that I don't have any concrete suggestions at the moment but I'm curious what "runs fine" in the 7.5.2 re...

The Img or "Image tags" are used to link images into posts. Find any of the many free file hosting / sharing sites out there and upload your screenshot then use the tags to link back to the URL they give you. Heck, most will build the image tags for you, ready to go.

You don't need to direct the attention of The Ray, The Ray is attentive to all.

First piece of advice for "combined operator" errors like that is to set the environment variable $APT_DISABLE_COMBINATION to true to determine in which stage the problem is occurring. However, it does seem to be an issue with your ABAP stage. Double-check your "DSSAP Logical Connecti...

Can you post a sample of the actual errors, please?

You should mark it as Resolved. Since it is your post you have that power - simply click the appropriate box at the top of the screen.

Then it's time to report it as a bug with whatever stage you are using (which you haven't mentioned) to your official support provider and see what they have to say.

I agree when I am trying to run with ./ it might fail Correction - it will fail. As you've seen. Why the need for "powershell"? Why not a simple batch file? ps. I haven't seen any evidence posted where you've used the syntax noted at the URL you posted. For example: The most common (defau...

Now you're mixing UNIX in your DOS command. It doesn't use the "dot slash" like that, remove those two characters and it should run more better.

Unless someone else chimes in who knows better, I'd suggest you contact your official support provider and see if that is expected behaviour in that situation. You may need to 'test' your source first and only run the loader job if there is actual data to load.

So... this is marked as Resolved with no resolution noted. Can you please add whatever secret sauce you were missing?