on 09-19-2014 3:06 PM
Hello All,
I am trying to run the standard EXPORT_MD_TO_FILE Data Manager Package. I'm having an issue with any descriptions that have a comma. If the description has a comma, it splits it into another column in the export.
Thus, if I have:
ID Desc
45678 Pottery Austin, TX
My export will show: 45678,Pottery Austin, TX
I would think it should show: 45678,"Pottery Austin, TX"
(like any other csv file)
I have tried changing the OUTPUTDELIMITER field in the transformation file to a semi-colon (;), however the behavior does the following:
45678;Pottery Austin; TX
It seems like the behavior of the Export first makes the delimiter a comma, then does a find and replace of all commas with the OUTPUTDELIMITER value, thus even converting my text comma to a semi-colon.
Has anyone else experienced this and/or found a way around this?
Thanks,
Alex
(BPC NW 10.0)
Hi Alexander,
It's a known issue (there are some resent posts about the same). And I think you are 100% right about the bug logic. I can recommend to open a ticket in SAP support. You can't do a lot...
By the way, what is you core BPC SP?
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alex,
I am on CPMBPC 800 SP14, but I am unable to test the export now - I have to implement the note http://service.sap.com/sap/support/notes/2057437
Without it my export to file is not working at all
Vadim
Hi Alexander,
You can use the comma as separator, and output 45678,Pottery Austin, TX which is correct.
the question is what do you do with the file, if you import the file again then the , will separate pottery Austin and TX. so when you import with the file you need to use length to separate them. not ,
What you can try is use a conversion file to replace all the , to _ then use comma separator.
then you will get something like 45678,Pottery Austin_ TX
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Andy,
I already tried doing the conversion replace. The issue is that it seems the system first makes the separator a comma before it hits even the transformation file. It seems the logic goes:
Before Transformation: 45678,Pottery Austin, TX
Transformation using OUTPUTDELIMITER: 45678;Pottery Austin; TX
Conversion using JS to replace: does nothing because there is no comma
After the transformation, because it shows everything to the conversion file as a ";", it appears to the conversion file as another "column". Thus, it doesn't convert anything.
The issue is that before transformation, the system decides to make it a comma, thus forcing the transformation to convert every comma to ";", because it seems it just does a find-and-replace of comma to OUTPUTDELIMITER.
And yes, the goal is to be able to re-import the file back into the system, that is why the number of columns matters. (though, in almost every situation of using the data, it would be an issue.)
I used a city, state as an example, in reality, it's not that simple, sometimes it's a list such as "Black, Smooth, Faucet" or something of the like.
It seems it's just a fault in the logic of the Export I guess.
Alex
Hi Alexander,
Just tested master data export on the system with BPC 10 SP 14 (BW 730 SP 12) with the note installed:http://service.sap.com/sap/support/notes/2057437
Transformation file has the line: OUTPUTDELIMITER=;
Description of test member has comma inside.
Result:
TEST1;INC;Test, with comma;(...)
No issues with comma!
B.R. Vadim
User | Count |
---|---|
15 | |
4 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.