FI313 – “No funds center

entered/derived in item &.”

Applies to:
This article is release-independent.

Summary
You are using FM account assignments within one of the following components/modules: Plant Maintenance
(PM), Sales Order (SD), Asset Accounting (FI-AA) or Materials Management (MM) and you receive the error
message FI313: No funds center entered/derived in item &.
Author: Vanessa Barth
Company: SAP
Created on: 09 December 2008

Author Bio
Vanessa Barth is a Senior Support Consultant in SAP Financials Team. She has been
working in the Funds Management Area (PSM-FM) for the past ten years, most of the time as
a Consultant in partner companies and now as a member of SAP Support Team.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2008 SAP AG 1
 FI313 – “No funds center entered/derived in item &.”

Table of Contents
Reason and Prerequisites for FI 313..................................................................................................................3
1. The error message is received within a Sales Order (SD) process............................................................3
a) SD customizing settings for FM objects. ..................................................................................................................3
b) The integration of PSM-FM and Sales Order is not required to your business process...........................................3
2. The error message is received within a Plant Maintenance (PM) process.................................................3
a) A missing or incorrect integration between Plant Maintenance (PM) and Funds Management (PSM-FM)..............3
b) A missing derivation rule in FMDERIVE...................................................................................................................3
c) Field Status definition for Account Assignments ......................................................................................................4
d) Changing account assignment data on Location Tab. .............................................................................................4
3. The error message is received within an Asset (FI-AA) process................................................................4
4. The error message is received within a Materials Management (MM).......................................................4
5. The cause of FI313 can also be a missing or incorrect derivation rule in FMDERIVE...............................5
Related Content..................................................................................................................................................6
Copyright.............................................................................................................................................................7

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2008 SAP AG 2
 FI313 – “No funds center entered/derived in item &.”

Reason and Prerequisites for FI 313

You have activated Funds Management functionality (Enterprise Extension EA-PS is activated in transaction
code SFW5 and flags "Account Assignment Derivation" and/or "Activate Update in Funds Management" are
activated in customizing path PSM -> Funds Management Government -> Actual and Commitment
Update/Integration -> Activate/Deactivate Funds Management").
If you are on release ECC 600 and your EA-PS is higher or equal to SAPKGPPD08, this note can help you
to avoid FI313.
If you are on a lower release, there are some correction notes that you can find in the Service Marketplace
according to your package. The following information can also be useful to avoid FI313 even in lower
releases.
The cause of FI313 can be one of the following, depending on which module you have received this error
(SD, MM, FI-AA, PM).

1. The error message is received within a Sales Order (SD) process

In this case, check the following:

a) SD customizing settings for FM objects.

You can set "fund center" as an optional entry in SD customizing settings for field status. This can be
checked in the IMG path:
SPRO -> Public Sector Management -> Funds Management Government-> Actual and Commitment
Update/Integration -> Integration -> Maintain Field Status for Assigning FM Account Assignments
You should have a record with Object type = '04' (sales order).
It is not necessary to have the field as required (unless you want to insert it in the origin process) due
to the fact that this can avoid the account assignment derivation between CO objects and FM objects.
For more information, check note 572729.

b) The integration of PSM-FM and Sales Order is not required to your business process
If you do not want to integrate sales order process within PSM-FM, you should consider deactivating
this integration in customizing transaction OFUP. In release EA-PS 1.10 and 2.00 modification note
591573 is available.

2. The error message is received within a Plant Maintenance (PM) process.

a) A missing or incorrect integration between Plant Maintenance (PM) and Funds Management (PSM-FM).
This can be checked in the IMG path:
IMG -> Public Sector Management -> Funds Management Government -> Actual and Commitment
Update/Integration -> Integration -> Maintain Field Status for Assigning FM Account Assignments
You should have a record there with Object type = '03' (plant maintenance) in such a way that the
fields are displayed and ready for input in the Funds Management dialog box of the order.
Doing this, you integrate the plant maintenance processes with Funds Management. To this end, you
stipulate that the commitment item, funds center, and fund for an FM area and for object type 03 will
accept input. When you create a maintenance order, you can enter the FM account assignments by
choosing Extras -> Assignments -> Funds Management.

b) A missing derivation rule in FMDERIVE

You should consider having a derivation rule in your FMDERIVE with function module
FMDT_READ_ORDER_PM_FROM_FMZUOB. This function reads the account assignment that was
entered or derived within Plant Maintenance orders.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2008 SAP AG 3
 FI313 – “No funds center entered/derived in item &.”

c) Field Status definition for Account Assignments

If you set your system in such a way that FM data is derived from the reference object (functional
location or equipment), the system response depends on how you defined the fields of the FM dialog
box using Customizing activity 'Maintain Field Status for Assigning FM Account Assignments':
• the fields of the FM dialog box are defined as ready for input ('Opt. entry' or 'Req. entry') in
Customizing:
If you change the reference object in the order, the system does not re-derive FM data automatically.
For that, you must navigate to the FM dialog box and, by choosing icon 'Redetermine account (F5)',
trigger the derivation manually.
• The fields of the FM dialog box are defined as not changeable ('Display') in Customizing:
If the reference object is changed in the order, FM data is redetermined automatically.
• The fields of the FM dialog box are defined as not displayable ('Hide') in Customizing:
FM data is not determined.
Set the field status to optional to permit the user to enter the FM objects and still benefit from the
possibility to automatically derive the FM objects from a CO object.

d) Changing account assignment data on Location Tab.

If you want to change account assignment data on the 'Location' tab page and redetermine FM data on
the basis of changed data, you can use enhancement SAPFMPM with user-exit
EXIT_SAPLFRC4_001.

3. The error message is received within an Asset (FI-AA) process.

a) Please consider to have a derivation rule in FMDERIVE with the function module
FMDT_READ_MD_ASSET. This function module reads the asset master data (for example the cost
center) so that they can be used as source fields in your derivation strategy.
b) Check in your FI-AA customizing if you have activated the account assignment element "funds
center" but you have not specified an account assignment type for account assignment object "funds
center" for APC balance sheet postings (see note 684659 for details).

4. The error message is received within a Materials Management (MM).

a) MM customizing settings for FM objects. You can set funds center as an optional entry in MM
customizing settings for field status. For more information, check note 572729.
b) You are creating a PO/PR related to a PM order. Kindly check item 2 of this note.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2008 SAP AG 4
 FI313 – “No funds center entered/derived in item &.”

5. The cause of FI313 can also be a missing or incorrect derivation rule in FMDERIVE.
Be aware that derivation rules are usually classified as consulting issues. To make sure it is a bug, you
can activate the trace according to the instructions in consulting note 666322.
If you check the trace log and the 'value before' is blank, this means that the system is not able to find
this assignment and you should consider creating a derivation rule. If you check the trace log and the
'value after' is not correct or blank, you should check/adjust your existing derivation rule.
The FM derivation tool can only be used for deriving Funds Management account assignments.
Additional information is available in note 881202.

Note: Bear in mind that customizing, correcting or changing the derivation rules is your own responsibility, so if you need
assistance in this respect you will need to contact your responsible consultant as per SAP note 83020.

If the issue persists, use the fmderive trace tool as per note 666322 in order to check where the system fails.
If you are still not able to find the solution to FI313, create a support message with all the information
regarding which steps above were done, including the changes made and the FMDERIVE trace log (values
after and before) attached to your message.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2008 SAP AG 5
 FI313 – “No funds center entered/derived in item &.”

Related Content
For additional information, please check the following web pages.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/f0/ca5716260211d28a430000e829fbbd/frameset.htm
For more information, visit the Enterprise Resource Planning homepage.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2008 SAP AG 6
 FI313 – “No funds center entered/derived in item &.”

Copyright
© 2008 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,
zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere,
Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of
IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of
Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All
other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves
informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the
express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied
warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may
result from the use of these materials.
SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these
materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and
does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.
Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be
used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of
certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors
or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com

© 2008 SAP AG 7