on 2018 Jan 22 5:18 PM
Hi,
After implement BPC 10.1 NW and use it during one year, our customer require to change the way of entering data: reveneu in positive and expensive in negative.
This involves to change ACCTYPE property to EXP in all members of account type Dimensions. It affects all calculations (input template with cell formulas, scriptlogic, BADIs,...). In addition, traceability with historical data will be lost.
Should I considerer something else?
Why not to make all accounts INC? Then at least on database level the sign will be correct and your previous data will be ok:
INC: Positive -> DB Negative, Negative -> DB positive!
Effect: default.lgf/journal.lgf calculations will be affected:
Please read: https://blogs.sap.com/2014/06/09/how-to-write-defaultlgf/
Search for: "SIGN and ACCTYPE in EXPRESSION calculations"
DM package scripts will not be affected!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For income statement, I believe it'd be fine to define all accounts as EXP as this type will keep the signage you entered, in the presentation and DB layer.
The only thing is that, if you go this path, all accounts on your hierarchy (P&L) should be EXP. The user will then be responsible if the amount being entered is a credit or a debit - by entering the signage.
For historical data, you can then run an one-off script logic to revert the signage off "former" INC accounts.
Recommend a copy of the current environment to test this change.
Not sure around the BS accounts and I would recommend the keeping the acc. types. or at least testing it through to be sure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In case of INC the DB representation of figures will be standard - nothing to change in data upload from ERP...
The standard setup assumes that:
Data entry: INC - positive, EXP - positive
Data storage: INC - negative, EXP - positive (accounting standard)
What do you want to store?
Anyway, looks like strange idea!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vadim,
The main issue is how the user enter and view the data at the template. How its show the data at the data base is not relevant for us, but i believe that define all accountypes like EXP is the best option. I want something like this:
My question is about possible derived problems because of this change after go live project.
Thanks.
User | Count |
---|---|
6 | |
5 | |
4 | |
2 | |
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.