My experience in the past with Oracle EBS and Peoplesoft there were always ways to control what is an allowed accounting string and what is not. An accounting string refers to the combination of segments and accounts that are tied to a transaction in the GL.
There was the concept of Combination Codes. This was a value that represented a particular combination of segments.
An example:
Subsidiary : Jockey
Business Unit : Underwear, Outerwear, Sleepwear, Corporate
Practice : Bras, Pantyhose, T-shirts, Socks, Underwear
Department : Admin, HR, Manufacturing, Advertising, Marketing, QA, Logistics
Using this the above a typical ComboCode might be:
- JUW-BR-MAN = Jockey.Undearwar.Bras.Manufacturing
- JOW-TS-ADV = Jockey.Outerwear.T-shirts.Advertising
When entering a transaction, the user would select the ComboCode from a list and the corresponding segments would be filled in.
Some combinations of segment do not make sense. An example would be Jockey.Outerwear.Bras.QA, because they do not make Bras to for outerwear.
There may be different ways to control this. By exclusive use of ComoCode, you only define ComboCodes that make sense.
There may be Accounting rules that reject invalid combinations. There may be programing mechanics that allow you to filter choices as others are selected.
Carrying this concept further it could also include the natural account (revenue, expense,…).
There certainly may be account that should not be associated with certain segments, an HR department never generates revenue.
The question is how this accomplished this in NetSuite.