i.) Does anybody use multiple accouting schemas (using
different Account Elements) in production ?
- If yes, how does it work for you ? Everything smooth
?
- If no, what are the problems ( no demand ?, does not
work ? , ...)
ii.) Setup of multiple Accouting Schemas and Multiple
COA (Account Elements)
Is there any possibility to create a second accouting
schema incl. "Account Schema Elements" and Default
Accounts automatically from an csv like it is done
when the Client is created ?
I have not found any option for this. Setting all the
default accounts manually for the second schema can
not be the idea.
I managed to load a second AccountElement (COA).
As well we created a second AccoutingSchema (Schema)
and used the newly created AccountElement as "Account
Schema Element".
Next step would be to create the default accounts.
Are we basically doing the right things ?
Maybe we could reuse the create client code for this ?
iii.) A more general question on setting/changing
default accounts.
If I try to change or set a default account the value
looks: "*-AccountNo-...." (The first * for all Orgs)
If I try to set or change the value of the default
account, I never managed to set the Org value to
"*-Account-"
The system forces me to set an existing org. "*" is
not an option.
Any ideas ?
iv.) I will create second AccountElement (COA) with specific
org (not "*") for example "STORE-AccountNo-...." but fail.
how to set parameter to import account with specific
org (not "*")?
Thanks a lot for any feedback
Kind regards
/sul