Error FF753 Tax code 01 not appear in any G/L account item with FM Active

Question

Hi
We have fund management configured for one of the company code, while creating billing document through VF01/VF02 we are  getting the Error FF753 Tax code 01 not appear in any G/L account item.
This error however does not appear when posting directly from FI with the same tax code.
I have tried to change the message control in which case i am getting a dump pointing to PSM-FM.
Please advise.
Regards
Sandeep

Answer 1

Hi:
          If you could please refer to the contents of  OSS Note 112609 - How are tax codes transferred to conditions ?
"Symptom
If a billing document is transferred to accounting the system displays error messages. Transferring tax codes from tax conditions into the pricing conditions and discounts does not function as expected.
Other terms
FF805, FF747, FF753, MWSKZ, MWSK1, tax code
Reason and Prerequisites
The tax condition in the SD pricing procedure contains incorrect reference steps, there are several tax conditions in the pricing procedure of which the tax codes overwrite each other or a program error exists.
Solution
In the accounting document for a billing document, the different G/L account line items are provided with a tax code. The tax code of the G/L accounts is transferred from the tax condition(s) of the billing document. How are the tax codes of the tax conditions transferred into the other conditions of a billing document ?
Basically:
The conditions of a billing document are read from top to bottom. As soon as an active tax (inactive = ' ') is read, the system transfers the tax code of this tax into the non-tax conditions as follows:
    1. The reference steps (From-step, To-step) are read (the reference steps are defined in the pricing procedure).
    2. The tax code is transferred into all conditions, for which
    the step number of the condition lies in the pricing procedure between "From-step" and "To-step",
    the condition is not inactive (exactly: the inactive flag is not equal to A (Condition exclusion), M (Inactive due to manual entry), or X (Incorrect)),
    the condition is not statistical (if it is no invoice list condition),
    the condition is no tax condition.
After the transfer of the tax code the system searches for the next active tax. If further taxes are found, their tax code is again transferred according to the above procedure. If the reference steps of different taxes overlap, tax codes that have already been transferred are overwritten. To all non-tax conditions which in the pricing procedure stand after the last tax condition the tax code of the last active tax condition is transferred if they are not statistical.
Special features:
    1. If the "From-step" of a tax condition refers to a subtotal of the pricing procedure, the tax code of the tax is not only transferred into the conditions with step number between From-step and To-step but into all non-tax conditions for which
    the step number of the condition in the pricing procedure is lower than the "To-step" of the tax condition.
    the condition is not statistical (if it is no invoice list condition).
    the condition is not a tax condition.
    2. If the "To-step" of the tax condition is smaller than the "From-step", then the system sets "To-step = From-step".
Notes:
    1. As of Release 4.0 the tax code is no longer transferred in pricing but only when the billing document is released to accounting.
    2. If you use several taxes and tax codes and Customizing is incorrect for the release of billing documents to accounting, among others the system may display error message FF747.
    3. If there are several taxes in the pricing procedure refer to Notes 72173 and 82091 for Releases 3.0D - 3.1G. For Release 3.1H, only note 82091 is relevant.
    4. For conditions which are transferred into accounting (thus not statistical, not inactive conditions) and do not contain a tax code, the system searches for a default tax code which in Accounting Customizing can be set depending on the company code (tax code for non-taxable transactions). This applies to releases up to and including Release 4.5B. For Release 4.6, refer to Note 385127."
Regards