DSXchange

Sed is good. You can also do the same with grep and make it work more efficient.

Before others answer it, can you let us know what your answer is with the reason why.

Did you try in a different client PC?

When your executable job has commands that cannot be performed or variables not initialised, you may have phantom errors.

You may also have phantom errors which are serious to cause failure of the whole process.

A different invocation id than the one that is already running.

I do not think loading a null into a non-null ora col will raise this error. If it is done, it may return a warning for that record.

You cannot use a home editon. You need pro.

Even though you can create your own VOC entries to point to your new universe, it is advisable, as Ken said, to leave it blank and let it reside in the 'present working project'.

This assists in migration of code across projects.

Access Violation may imply permission problems.

Negative symbol may not always be represented by 'D'. The derivation of this char is by combination of the sign and the data.

You can reduce it saying

grep '^$' filename | wc -l

But make sure that an 'empty line' is a line 'with no value including blank spaces'. Otherwise your grep pattern will be different.

ABAP must be faster.

Look for DSExecute.

Use loop stage in DS v> 7.5.

A condition stage to perform the check of date.

ABAP is simple and straight-forward.

BAPI involves SAP side knowledge and development.