Feedback on Account ID format when source GL accounts that contain dashes
Summary:
Feedback on Account ID format when source GL accounts that contain dashes
Content (please ensure you mask any confidential information):
We're currently undergoing a project to transition from Blackline to Oracle ARCS. One of the issues we encountered revolves around our Account ID setup. We're using two segments: Entity and Account. No issues with Entity, however for account - our GL account strings follow a format such as "100-10-100-0000" which is considered invalid to be input into one subsegment due to containing dashes.
For others who were in a similar situation, I'm curious to see how you went about solving for it. Each part of the string doesn't have a particular meaning so didn't want to add 4 profile segments for each piece. For now, we're converting them all to the format of "100_10_100_0000" which I don't particularly love but seems to be the best option. And potentially adding a profile attribute with the original format to help make lookups a bit easier.