Академический Документы
Профессиональный Документы
Культура Документы
Examine why field status errors occur for Materials Management (MM) transactions. Understand >> Key Concept
the relationship between MM and Financial Accounting field status. Discover the steps required to A Materials Management (MM)
correct field status group errors and the special considerations for configuring field status groups. movement type and a general ledger
(G/L) account both have field selec-
When you post Materials Management differs for Profit Center (042). Note 042 tion strings. Field selection strings
(MM) transactions that have a Financial indicates the profit center fields are con- need to be consistent between
Accounting (FI) impact, you may receive trolled by the forty-second position in the Financial Accounting and MM. For
the error message M7 093 Different field raw data display of field T156B-FAUSN. example, it is inconsistent for an
selection for movement type 501/account MM movement type to suppress a
What should your next step as an analyst
400020 differs from Profit Center 042 or profit center, but for the G/L account
be? To resolve this message you need to
F5 808 Field Cost Center is a required to require a profit center.
know the field selection for a movement
field for G/L account 3000 792000. These
type. First Ill explain what MM field
error messages are caused by an inconsis- entry per special stock indicator is active
status is and how it interacts with FI field
tency in the field status group for the MM for each movement type. Double-click on
status. Then Ill show you how to quickly
movement type and the FI G/L account to the appropriate entry to see the field status
identify and correct any inconsistencies.
which you are posting. Common MM group overview (Figure 2).
transactions such as MB01, MB1A,
MB1B, MB1C, and VL01 and SAP Enjoy MM Field Status The field status groups break the individual
transactions such as MIGO and MIRO When you post an MM document certain fields in the MM document into logically
can trigger these messages. information is required to process the related groups. Double-click on a group to
transaction, such as plant, storage loca- see the full field details (Figure 3). If the
When configuring a movement type using tion, and material. Additional information field status group name is in blue it means
transaction OMJJ to set the field status can be required of an MM transaction at least one field in the group is optional or
group, you miss the similar field status (e.g., movement type 201 requires a cost required; if it is black then all fields are
group for the G/L account configured center). The field status group controls suppressed. The text (FI only) refers to
using transaction OBC4. To help resolve what information is required to complete fields that are only used in FI, but you may
these issues, SAP provides standard report an MM transaction. need to update these settings if you run into
RM07CUFA to help analyze the inconsis- the error messages I have discussed.
tencies. Ill show you how to use this To configure MM field status, use transac-
report to update field selections, and also tion OMJJ and select the sub-dialog Field The field status group detail shows the
explain in greater detail the considerations selection (from 201)/Batch search proce- settings for individual fields such as
you need to take into account when dure (Figure 1). The text (from 201) Profit Center. The options Suppress,
adjusting the configuration. means it applies to movement types from Req. Entry, and Opt. Entry control the
201 to 999 only, not to the purchasing field status during MM document entry
Consider the following scenario: The Finan- goods receipt transactions 101 to 199. One for the specific movement type. You can
cial Accounting (FI) General Ledger (G/L)
team has decided that profit center should
be a compulsory account for material con-
sumption accounts. When a user performs a
goods receipt using movement type 501,
goods issue (GI) receipt without purchase
order (PO), they receive error message Fld
Figure 1 Transaction OMJJ for movement type field selection update
selectn for mvmt type 501/acct 400020
use the page up and page down keys to Sometimes a single row in the field status FI Configuration
navigate between pages. group can refer to more than one field in
Now that I have discussed the configura-
the MM document (e.g., the Sales order
tion for MM field status group, you know
option controls the sales order document
the error messages occur due to an incon-
and sales order item fields). Use the Field
sistency between MM and FI field status
check button in Figure 3 to see which
groups. FI has two field status groups, one
fields a single setting controls.
for the G/L account and one for the
The settings in the OMJJ sub-dialog Field posting key (Table 1).
selection (from 201)/Batch search proce-
dure do not apply to SAP Enjoy transaction
OBC4: G/L Account Field Status Group
MIGO (goods receipt with a purchase
order). Instead you need to enter the field Each G/L account is assigned a field status
for which you want to change the status in group. You can display the field status
the sub-dialog Field selection (Enjoy) group assignment with transaction FS03
shown in Figure 4. Note the SAP Enjoy (Figure 5 on the next page).
logic applies to all movement types from
Figure 2 Transaction OMJJ detail after An FI field status group is not unique. You
101 to 999. It has no special text, as
you double-click on the move- need to know its field status variant. Click
ment type opposed to Figure 1, which says from 201.
on the drop-down arrow next to Field
status group G003 or press F4 for help.
Then the field status variant 1000 is dis-
played at the top of the selection list
(Figure 6 on the next page).
Figure 6 Find the field status variant for a field status group
Invalid Combinations
I have discussed the configuration for MM
field status group and error messages that
occur due to an inconsistency between MM
and FI field status groups. Table 4 shows
the logic SAP applies to the comparison of
the MM movement type and FI G/L
account field status group settings. Table 5
provides additional detail on the four com- Figure 7 Transaction OBC4 field status group overview
binations that cause errors. Analyze your
own business scenarios before proceeding
with the possible corrections suggested.
Error Report
Now I will introduce a report to quickly
identify and correct any inconsistencies. You Figure 8 Transaction OB41 configures FI posting keys
can use report RM07CUFA (Field Selection
Comparison: Movement Type G/L Account) Configuration
to identify the field selection string errors. Configuration object Table Table description
transaction
See SAP Note 9281for more information. MM movement type OMJJ T156B Movement types: screen selection
Enter the data from the error message Fld
FI G/L field status group OBC4 T004F Field status definition groups
selectn for mvmt type 501/acct 400020
differs for Profit Center (042) into the FI posting key OB41 TBSL Posting key
selection screen of RM07CUFA. Table 2 List of configuration tables where field status group settings are stored
Figure 9 Raw data display of field Space Display entry Rarely used
To change the field status group with trans-
selection string Table 3 Field status symbols
action OMJJ or OBC4, click on the
appropriate symbol for the row in error. The Click on the error log icon of the main group. This was done by clicking on the -
left symbol with the header MvT is the report output to take you to a summary list symbol for Profit Center in Figure 10,
MM field status and the hotspot links to of all errors (Figure 11). This is useful as going to the Field Status Overview,
transaction OMJJ. The symbol on the right the report has a long list of field status double clicking on the Additional account
hand with header A/c is the FI G/L field groups you have to scroll through. assignments group, and then setting the
status and the hotspot links to transaction required entry option for Profit Center.
OBC4. In both cases, a screen similar to the In this case the error is resolved by mak-
MM Maintain Field Status Group: Over- ing profit center a required field in the
view screen appears as shown in Figure 2. MM movement type 501 field status
Issues with RM07CUFA
Report RM07CUFA is very useful but you
MM cannot resolve all issues directly form this
Suppressed () Required (+) Optional (.) report. There is no link to OMJJ sub-
Suppressed () OK Error Error dialog Field selection (Enjoy), so you
need to enter OMJJ directly to update
FI Required (+) Error OK Error
configuration for SAP Enjoy transactions.
Optional (.) OK OK OK
Table 4 Matrix showing intersection of MM and FI field status group settings The report does not compare settings for
FI posting keys. Usually this is not an
MM T156B FI T004F Description Issue Possible correction issue as the MM relevant posting keys 80
Required Suppressed Required The field is populated in Make field status to 99 have default settings with nearly all
(+) (-) in MM, but MM, but the data cannot optional in FI or sup- fields optional, which allows all field data
suppressed be transferred to the FI press in MM
to pass through. If there is an issue with
in FI posting, resulting in loss of
data in the FI document the posting key field status group you see
Suppressed Required Suppressed The field cannot be popu- Make field status
the error message Rules for posting key
(-) (+) in MM, but lated in MM resulting in an required in MM or 91 and acct 400020 set incorrectly for
required error in the FI posting for optional in FI or sup- PRCTR field. n
in FI the required field pressed in FI
Optional Required Optional in The field may not be popu- Make field status
Rohana Gunawardena is the
(.) (+) MM, but lated in MM resulting in an required in MM or
required error in the FI posting for optional in FI SAP practice director of
in FI the required field Quality Systems & Soft-
Optional Suppressed Optional in The field maybe populated Make field status ware, a specialist SAP
(.) (-) MM, but in MM, but the data cannot optional in FI or sup- consulting firm. Rohana has
suppressed be transferred to the FI press in MM been working with SAP
in FI posting, resulting in loss of
since 1992, focusing on the order-to-cash
data in the FI document
process with emphasis on global rollouts,
Table 5 Field status group settings that cause errors
business segment reporting, cross-module
integration, and the financial impact of
SCM transactions. Plus, he has helped
multiple clients on detailed system correc-
tion projects (e.g., correcting inventory
balances, retrospectively activating group
currency, and cleaning up intercompany
accounting transactions). Rohana has
spoken at many SAP conferences and has
Figure 10 Field status group error found for profit center field
published more than 20 articles on various
aspects of SAP. He is a Fellow of the Insti-
tute of Chartered Accountants in England
& Wales. You may contact Rohana via
email at Rohana@QSandS.com.
Figure 11 Error log for report RM07CUFA