Skip to main content
Question

IFS Cloud 24R2 - posting errror : Posting type M1 is missing in Posting Control for company FR01 and code part Locaccount.

  • May 12, 2025
  • 4 replies
  • 64 views

Sophie Lesur
Do Gooder (Partner)
Forum|alt.badge.img+4

Hello, 

A code string completion is define between “Plan B - Group account” and “Plan A - Local account” to automatically calculate Plan A.

 

In posting control, the rules are defined on “Plan B - Group account” .

 

There is an error message, when we post an inventory transactions:

I launch : “ Run code string completion” , but the system does’nt calculate nor “Group account”, nor “Local account”. 

Why? 

Thanks for your help.

4 replies

Furkan Zengin
Ultimate Hero (Partner)
Forum|alt.badge.img+21
  • Ultimate Hero (Partner)
  • 765 replies
  • May 12, 2025

Hello,

Change override value to Allowed and rerun erroneous postings.

 

 

Hope this helps

Furkan


Sophie Lesur
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • 5 replies
  • May 16, 2025

Hi,

I finally can change the settings, as suggested.

 

 

I create new inventory transactions. But it doesn't work.


Do you have another solution?


Forum|alt.badge.img+16
  • Hero (Customer)
  • 735 replies
  • May 19, 2025

Hello, ​@Sophie Lesur 

Is this setup works for other posting controls, eg. supplier invoices?
I can see you have codestring completion one way, i.e. posting controls defines code part B  and from code part B system should tell code A. 
Problem is that all system requirements (account type, requirements, tax flag etc.) are defined on code A, not B. In case of inventory transactions I think system is not reaching codestring completion step before raising the posting error. 
Using double chart of accounts (local/group) I am normally require 1=1 mapping between the two, posting controls defining code A and codestring completion from A to B. In your case it is set up in opposite way. 
What you can try to do, is to set up M1 posting control for code A using AC1 (fixed value) control type with Overwrite Allowed enabled, and set the account to dummy value. This dummy value should have code B mandatory. You can make this value not allowed in combination control or try to invalidate it by validity date. 
This way system should reach codestring completion step without error and override dummy value with completion value. 



 


Sophie Lesur
Do Gooder (Partner)
Forum|alt.badge.img+4
  • Author
  • Do Gooder (Partner)
  • 5 replies
  • May 21, 2025

Hello, 

 

thanks for your response.

 

This set up is OK for supplier invoices, instant invoices, bank transactions… for financial transactions.

 

But it’s KO for inventory transactions … I will duplicate the posting rules.