Validation for Account Assignment Combinations

[Former Member]

Hi gurus,

Instead of using classic validation rule in SAP FI, I want to activate the tool "Validation for Account Assignment Combinations":

For the Validation option, the G/L accounts are controlled by the system even if they are not in the valid account assignment combination range. This implies that the creation of documents containing G/L accounts out of the ranges is not possible or that all accounts should be listed in the ranges (even the accounts for which no control is required...)!

I think that it is a sytem issue, but I cannot find many OSS note on this topic nor documentation.

Is there any expert who can share his point of view on that issue and share some detailed documenation about this SAP recent solution?

Thank you in advance for your help,

Best regards,

Pascal Morizur

[Former Member]

Hi, could you clarify your issue?If possible post an example.

It's not new solution, if I'm correct this option is available starting from EHP4

[Former Member]

Hi Aleksey,

The requirement is simple and could be summarized as follows: I want to validate the combination of Accounts and Profit centers (and other combination of standard dimensions).

Example:

Range definition:

- HKONT from 12100000 to 12300000

- PRTCTR = from BRA900  to BRA9999

I want the system to check that for any account contained in the range above, the profit center is also contained in the range, if not a message should block the posting.

It is working well for this set of account.

My issue is that when I use an account not belonging to this range, the same control is applied meaning that I should customize all possible combinations of account and Profit centres...

The sytem should not check the accounts that are not contained in the account range, otherwise I will be obliged to list all possible combinations and the maintenance will be very heavy...

This SAP solution avaialble from EHP4 or 5 is very interesting and is a great complement of basic SAP FI validation rules, but it should not work like that...

Thank you in advance for your help

Regards

Pascal

[Former Member]

Hi, this tool has a little bit different logic then ob28, this is logically, because why create new the same tool.

Several words how it works.

You need choose Valid, Not valid.

In you example Valid.

If this derivation strategy is active, then FM  FAGL_VALIDATE_COMBINATION, which set value Not valid by default. if you create derivation rule with HKONT 1 PC 1, then this combination will be the only for posting(means VALID indicator set to 'X' if combination is founda). that's why you need to put all relevant combination.

Invalid strategy works in contrary:by default set indicator Invalid='blank' and if system find combination then put as Non valid.

[Former Member]

Thank you for your reply Aleksey!

Even if different, I think that the technical logic is really not the best one...

My ideas before coming back to traditional OB28:

- define a limited number of accounts in the Validation step using the "condition" as a selection criteria. But it does not work (the selection seems to be applied the the declared intervals)...

- define the step 1 as an enhacement using the BADI "FAGL_VAL_CUST_EXIT_BADI" to default VALID indicator set to 'X' for the accounts not contained in the interval...but I fear that I will be obliged to declare all accounts in a set or specific table...

Do you have any other idea for me?

Best regards

Pascal

[Former Member]

If you want use OB28, then put accounts range in prerequisites and PCs range in Check.

If you want to use FAGL_VALIDATE then create 3 ranges

1)

12100000 - 12300000 and BRA900 - BRA9999

1 - 1209999 and PC = *

12300001 -9999999 and PC *

I don't think that you should use BADi for such simple logic.

Also you could create Invalid derivation type.

In derivation step put HKONT as a sourse and maintain range, and in Condition put PC(3)(3 first numbers)<>BRC. 

[Former Member]

Thank you but my example was very basic and I have many combinations of Accounts and Profit centers to define, so there are some limit to your solutions:

• Solution 1: I will need to list all possible account ranges for the full chart of accounts...This is exaclty what I want to avoid to optimize the maintenance of my solution.
• Solution 2: I will have to maintain many invalid ranges in the conditions as I have a lot of Profit centers intervals to exclude...This is neither the ideal solution.

It would be very easy to say to the program: if account is not belonging to the range, then VALID indicator ='X', if not proceed with the standard...logic. Technically I don't see how to apply such simple logic, if you have any idea I would be happy to share...

Best regards,

Pascal