Each configuration project starts with the creation of Company Code.
Well, not exactly. You need to have much more done before starting Company Code creation. Like a Chart of Accounts (at least its name), Controlling Area, Posting period variant etc. But these are objects which are most likely unique across the implementation project. And they are not much used by end-users. I’ll talk about them separately.
But this is the Company Code which users talk about and key in most often. That’s why it is very important to get proper coding structure for your Company Code number.
SAP allows you to have up to 4 characters in this number. How should you use it? It depends on many parameters, and some of them are not so obvious.
Let me give you some ideas before you start.
1. Small numbers. How many legal entities are in the project’s scope now and in the future? If there are only 1-2 companies, why not simply code them as 1 and 2. Yes, that easy. Just Company Code = “1” and “2”. You will laugh, but I have seen this numbering structure on one project. And this is not a small company. This is huge plant, but they have only 2 legal entities. Of course, having Company Code number = 1 is easy for users. They don’t need to make many strokes on the keyboard.
But let’s be honest. Most SAP projects work in environments where there are more than one or two legal entities. The companies have complex structures of daughter/mother companies, different branches, representative offices across different countries.
I can suggest to you 3 more strategies for a numbering convention.
2. Flat structure. Wherever your company is, whatever is its relationship with other companies in the group, each Company Code simply gets the sequential number. Yes, that can mean more effort for users later to work out the relationships between the companies. But in a very heterogeneous environment, especially where ownership of the companies can change from time to time, this is the useful approach. Which number to start with? It’s up to you. Start with 1, 1000, A, AAAA, whatever you feel like.
3. Hierarchy structure. You have main companies which have branches and representative offices. Branches in their turn can also have representative offices. In this case it would be better to stick to assigning a specific position in the Company Code number to a specific hierarchy level. Say, the first 2 characters are for the main companies, third is for branches and the fourth is for the representative office. In this case – 1500 – main company (number 15), 1510 – branch #1 of that company, 1505 – representative office #5 of main company, 1513 – representative office #3 of branch #1. Of course, this structure does not allow you to specify the geographical location of each Company Code. But is that so important?
4. Geographical structure. Do you have companies in different countries across the globe? In this case you may set a country code in the Company Code. This can be a simple 2-character ISO country code (US, GB, AU etc). Or you can make ranges for regions and then number companies within the area. Say 1xxx – companies in Europe, 2xxx – companies in Americas, 3xxx – companies in Asia.
Of course, I don’t mean to tell you that you can only stick to these 4 rules. You’re the consultant at the project. You can propose different strategies to your management or key users, so they can approve one or another approach, or give you some other ideas. And, of course, mix&match strategies are still possible. How about mixing numbers 3 and 4?
And finally, some rules of thumb.
What was your experience in proposing Company Code numbers to your projects? How many options did you propose? Were they different from what I mentioned above? Please share your ideas in comments.
Image: Ali Samieivafa