MII transaction stops working if its content is formatted

[former_member1338085]

We are using MII 15.1 SP5 Patch 4 and during transport (I don't know how it happened, but) some transactions became formatted. Like if I executed under UNIX this:

cat originalTrans.trx | xmllint --format - > newTrans.trx

The newTrans.trx is not working. If I execute it from browser I receive this error:

Error type: DataStructure
Description: XML refers to not existing parent

We have to open it in workbench, save it and it seems that it's fine afterwards. But we have lot of transactions in our project. Is there any way to convert all of the transactions into original format?

In which phase of the import/export/transport became some of the transactions formatted?

[former_member1338085]

I found the reason why the transaction became formatted!

I had to add a new parameter to a certain transaction. Added it and saved it. Then right-click to the transaction in workbench and "Export". The exported file was formatted! And moreover after this operation any other transaction exported from workbench became formatted! (And that file was imported into another MII system)

If I went System Management -> Projects -> Project Selection -> Export then the output zipfile contained the transaction non-formatted.

So the conclusion: In MII 15.1 SP5 Patch 4 if I simply add a new parameter to a transaction then the export functionality in workbench gets crazy and starts to export files which are not functional afterwards.

[agentry_src]

Very odd behavior. I wonder if that was addressed in 15.2 or 15.3.

Thanks for sharing the details.

Cheers, Mike

[agentry_src]

Hi Tibor,

I know of no reason for the transaction to be converted to standard XML format, but I can confirm from testing as far back as 11.5, that if you open the actual code for a transaction and format it so it is easier to read, then it stops working if you save it. What I would recommend is only for the future. Save an export outside of SolMan or NWDI for recovery. But you should also be able to check the zip file to see which ones have different timestamps. See if you can find the ones with similar timestamps as the one you fixed already (or find another one which is broken without fixing it). I don't know if this will work, but I suspect that if the format changed, the file save timestamp would hopefully also have changed.

Good luck!

Mike

[former_member1338085]

Hi Mike,

okay, so can you please issue a ticket for this problem?

THx

[agentry_src]

Hi Tibor,

Tickets have to go to the SAP Help desk (Services Marketplace, I think). The SAP Community is strictly volunteers helping out. And as I am no longer employed by SAP, I couldn't do it on your behalf, even if I wanted to.

Cheers, Mike