Unable to Export Message Mapping to Spreadsheet via SAP NWDS

[shankul_saxena]

Hi All,

I am trying to export the message mapping to spreadsheet via SAP NWDS. NWDS is performing the task but doesn't create an xls file in the folder.

I have found two issues:-

• When the mapping is complex and have big xml file. Export to spreadsheet doesn't create the file. Even NWDS doesn't open it in mapping editor.
• When the mapping is a simple one. Export to spreadsheet completes the task and place the xls file in the given folder.

If possible, please redirect me to the correct team. Should I raise this issue with Basis Team or with SAP.

Regards,

Shankul

[former_member682709]

I think right now there is no solution.
It still doesn't work in NWDS 7.5 SP19. I cannot even open every mapping as soon as it hits a certain complexity.
I have a mapping where i map a XML structure into 6 IDOCs. Can be opened fine in the Swing tool, but not in NWDS, let alone exported to spreadsheet. I made a change in a smaller mapping in the NWDS, even transported it to the target system. Everything works fine, so i guess everything is ok, but when i open the exact same mapping in the Swing tool it shows me the old version of the mapping. Something fishy is going on here i guess.

[former_member651453]

Hi Shankul,

I'm having the same problem. Did you find a solution?

[shankul_saxena]

No I haven't found a solution of it till now.

[JaySchwendemann]

You should first check on having the most current patchlevel NWDS matching the SP of the PI / PO system, see engswee.yeoh 's excellent blog about the topic here: https://blogs.sap.com/2016/03/17/stop-using-the-wrong-nwds-version-have-a-smoother-eclipse-experienc...

That being said it could very well be a bug within the PI / PO component "SAP_XIESR".

If that's so you should find (or not because KB search on launchpad.support.sap is inferior) a matching note. However, then you will be stuck with a patching project. As different component tend to have SCA dependencies it might be wiser to go for a full SP upgrade than patching single components (my 2c)

To answer your questions straight:

• Make sure you use the most current NWDS for your SAP_XIESR component
• Search for existing notes about the error on launchpad
• If found, consider patching or SP upgrade
• If not found, raise incident at SAP
• Your SAP-Basis is probably not the right group to address this problem

Cheers

Jens