FICAX - Difference between lock fields INV_REASON and FICA_INV_REASON

[Former Member]

Hello,

In FICAx, the contract account has two similiar fields for Invoice Locks. One is name INV_REASON and the other is named FICA_INV_REASON. The first one is filled when:

Lock Category = 06 (Partner specific Account Data)

Process = 05 (Invoicing)

The second:

Lock Category = 06 (Partner specific Account Data)

Process = 12 (Invoice (FI-CA) )

Does anyone know the difference between these two fields or how they should be used?

Thanks

Marco

[AmlanBanerjee · Accepted solution]

Hi Marco,

The field INV_REASON is the SAP standard field for lnvoice locks which you will find when you activate any industry Business Function Set (BFS), say IS-T (Telecommunications) or IS-U (Utilities) etc.

So, if you are performing the invoicing through the standard process (T.code-EASIBI), and you want to block the invoicing then you have to populate the field INV_REASON.

Now as of EHP 2.0, SAP has given a functionality called "Invoicing in Contract Accounts Receivable and Payable" that allows you to create convergent invoices. For this, you have to activate the BFS FICAX-FI-CA extended.

This functionality processes the billing information from SAP billing systems and billing systems from other providers into customer invoices.You can integrate billing from component Sales and Distribution (SD) directly into Invoicing in Contract Accounts Receivable and Payable.

For more inforamtion on this functionality, refer to the attached link-

http://help.sap.com/erp2005_ehp_02/helpdata/en/43/5f38b7e7f21de5e10000000a422035/frameset.htm

So in here , if you are performing the invoicing through this functionality (T.code-FKKINV_MA), and you want to block the invoicing then you have to populate the field FICA_INV_REASON.

Hope it helps..

Thanks,

Amlan

[Former Member]

Hello Amlan,

Thank you very much for the information,

I come from an IS-U background and only knew about INV_REASON. Now working with FI-CAx and what you said makes sense, since in our tests, setting a block in INV_REASON didn't affect invoicing in anyway, while setting a lock in FICA_INV_REASON worked just fine.

Once again, thanks!

Marco