SAP for Public Sector Discussions
Foster conversations about citizen engagement, resource optimization, and service delivery improvements in the public sector using SAP.
Showing results for 
Search instead for 
Did you mean: 

Using Value Type to limit posting in FMIR - but problems with POs

0 Kudos

We are testing using FMIR value types to lock users out of certain processes at year end. We have tested Purchase Requisitions, Travel Commitments, Funds Reservations and Purchase Orders and all seem to be working fine except POs. In the first three, the user gets a hard stop message that  Period 012/Fiscal Year 2013 for payment budget not open for FM posting in value type XX. This is what we want and expect.

However, for POs no message is received. The PO processes as ordered in SRM and replicates to "some" tables in ECC (we are using extended classic scenario). The MM tables (EKPO, EKKO, EKKN, etc) are updated with the PO. However FMIOI is not updated so no commitment is reflected. So the system is allowing the document to post but not updated the FM tables.

When the FMIR Value Type control for POs is removed, the transaction posts correctly by updating both the MM tables and the FM tables, so the problem is specific to adding this.

Any suggestions or advice is appreciated - thanks.



Active Contributor
0 Kudos


Please, check out OSS note 1112484.



0 Kudos

Thanks Eli but this note pertains to deletion of items or other modifications that result in the creation of FM value for the related shopping cart in closed periods. I am having the problem at the creation of a new PO - I have FMIR set to not allow value type 51 to post in FY13, but the system is still allowing the SRM document to be ordered and all ECC MM tables to be updated, it is just not posting the FM value. It should throw an error that no postings are allowed and not allow the PO to be created - just like it works in travel, purchase reqs, etc.

Former Member
0 Kudos

Hello Robyn,

Check the Financial Transaction value in the commitment item master data being used.

The Commitment item with financial transaction 50 do not update in FM.

So correct the financial transaction and use the appropriate value in case it is presently updated as 50.



0 Kudos

Value type 50s are purchase requistions, which do update FM for us. Purchase Order post with value type 51.