ICR: how do assignments work in detail?

Question

Dear all,
maybe somebody can help on how the setup of ICR assignment rules works in detail:
1. question on customized rules:
We have a couple of rules in place, but rules being more complicated than just one condition or a combination of "="-conditions of fields always populated sometimes produce unexpected results.
E.g. it seems that condition "orgunit field X = partner field X" is false for empty fields as long as this is the only condition in a rule, but becomes true for empty fields as soon as there is a 2nd condition (since support package 60306, before implementing it this condition apparently was always false for empty records).
And it seems that condition "orgunit field X = partner field Y" (with Y <> X and not being the only condition) is false when comparing records in different companies, but gets true when comparing records within the same company.
Furthermore it seems that the behaviour of conditions with operator <> has also changed since support package 60306.
Is there any documentation of the ICR assigment logic which is such detailed? The one in OSS note 1164059 is not.
2. question on rules implemented in BAdi FB_RC_ASSIGNMENT:
Can anyone provide an example implemetation assigning records?
Thanks a lot in advance!
Best regards,
Claus

Answer 1

Hello Claus,
Re #1: I think it would be helpful if you could provide an example. Basically matches on initial values only are ignored (otherwise all documents where no reference number is posted will be assigned to each other - which would not make any sense). But if your rule has more than one condition and the other fields are not initial and are a match then the assignment is made.
Re #2: If you want to create assignments you simply have to move the corresponding data records from CT_ORGUNIT_UNASSIGN and CT_PARTNER_UNASSIGN to CT_ASSIGN_DIFF or CT_ASSIGN_NODIFF. Also, you have to populate the field GRREF (hint: look at the call of FM NUMBER_GET_NEXT in LFBRC_CENTRAL_FUNCSF05).
Best regards,
Ralph