Aleksander,
the business case behind your example is not clear to me.
Usage of SQL rules is advised to be limited as SQL rules have to be tested manually and don’t leave a clear audit trail like other rules. Consider using other options depending on your business case:
- If you need a simple one-time check, use a report with cell formulas.
- If you need to do a pre-consolidation check for packages sent by subsidiaries, define a control (in Category Builder).
- If you need some accounts to be automatically populated, create a formula (in Category Builder).
- If you need an automatic rule for preconsolidation or consolidation phase, create a corresponding automatic rule. For your example you will have 2 steps: first fill AC3 with amounts of AC1 and AC2; then clear all negative amounts on AC3.
- If nothing else works for you, write an SQL rule. SQL rule uses SQL syntax specific to your database with system variables (that can be found by clicking on button ‘Variables’ on ’SQL’ tab of SQL rule creation window). Some information on it is provided in BOF230 (former FM212) training. You can also find some info and SQL rule code examples for MS, HANA and Oracle databases in FC 10 Windows User Guide http://help.sap.com/businessobject/product_guides/bofc10/en/fc_10_win_user_en.pdf Since SQL rules are rarely used I have yet to find better tutorials.