PSM_S4C_POSTINGS -

The following messages are stored in message class PSM_S4C_POSTINGS: .
It is part of development package PSM_S4C_POSTINGS in software component PSM-FM-UP. This development package consists of objects that can be grouped under "Public Sector Management - FI Postings".
Message Nr
Message Text
000
001&1 &2 &3 &4
002Blank values are not allowed. Specify FM area and object type
003Please enter a value in all account assignment fields
004Object type must be '07' or '08'
010Posting with account &1 requires an assigned fund
011Fund &1 is not valid for the consumption date &2
012Posting with account &1 requires an assigned budget period
013Budget period &1 is not valid for the consumption date &2
014Posting with account &1 requires an assigned functional area
015Functional area &1 is not valid for the consumption date &2
016Posting with account &1 requires an assigned grant
017Grant &1 does not exist.
018Posting with account &1 requires an assigned budget account.
019Budget account &1 is not valid for the consumption date &2.
020Posting with account &1 requires an assigned cost center.
021Cost center &1 is not valid for the consumption date &2.
022Fund &1 does not exist for company code &2.
023Cost center &1 does not exist.
024Budget period &1 does not exist.
025Functional area &1 does not exist.
026No posting authorization for fund &1 in authorization group &2.
027No posting authorization in budget account &1.
028Account &1 maintained as budget account does not exist.
029Line item &2: Budget Account &1 does not allow postings
030Access the Customizing activity using the reference IMG.
031'Budget-Relevant' cannot be defined for budget consumption type &1.
032Line &1: The fund &2 does not have the same frequency as budget period &3
033Budget account settings are required for budget consumption type &1.
034Budget account &1 cannot be used as a carryforward account.
035Account &1 cannot be used. Leave blank or change to a suitable account.
036Line item &2 requires an assigned fund.
037Line item &2 requires an assigned budget period.
038Line item &2 requires an assigned functional area.
039Line item &2 requires an assigned cost center.
040Line item &2 requires a budget account for G/L account &1.
041Budget account needs to be maintained for G/L account &1.
042Line item &2: Account &1 maintained as a budget account does not exist.
043Account assignment element "Fund" must contain a value.
044Account assignment element "Grant" must contain a value.
045Enter a value for the budget period.
046Enter a value for the functional area.
047Postings cannot be made to budget account &1.
049Data in field &1 different to fixed master data value for WBS element &2
050Value in field &1 differs to fixed master data value for cost center &2
051Line item &2: Budget period &1 does not exist
052Line item &3: Fund &1 does not exist for company code &2
053Line item &2: Cost center &1 does not exist
054Line item &2: Functional area &1 does not exist
055Unable to retrieve master data for cost center &1.
056Unable to retrieve master data for WBS element &1.
057Settlement receiver of type &1 is not supported by PSM.
058Unable to retrieve data for order &1.
060Cost center &1 requires a fund.
061Cost center &1 requires a budget period.
062Cost center &1 requires a grant.
063Cost center &1 requires a functional area.
064Cost center &2 requires a budget account for G/L account &1.
065Cost center &2: Account &1 maintained as a budget account does not exist.
066Cost center &2: Budget account &1 does not allow postings.
067Cost center &2: Budget period &1 does not exist.
068Cost center &2: Functional area &1 does not exist.
069Cost center &3: Fund &1 does not exist for company code &2.
070Budget consumption type is blank for line &.
071Budget consumption date is blank for line &.
072Budget consumption period is blank for line &.
073Budget consumption year is blank for line &.
074Budget consumption amount type is blank for line &.
075There is a missing revenue/expense account in line &.
076Missing company code assignment for revenue/expense account in line &.
077Inconsistency between G/L account and revenue/expense account in line &.
078Missing company code assignment for budget account in line &.
100Update definition not found for chart of accounts &1 and G/L account &2
101Line item &1 without G/L account. PSM cannot classify the line item.
102Missing G/L account. PSM cannot classify.
103Enter a valid company code.
200Purchase order item & that contains a condition type entry not processed.
201Item &1 cannot be increased beyond its original value of &2 &3.
202The account assignment for item &1 cannot be changed.
211Upward adjustment for item &1 cannot be posted to an asset.
212Upward adjustment for item &1 cannot be posted to a service entry sheet.
301Posting to cash-relevant accounts uses incorrect document types.
302Posting to a not budget-relevant account not possible.
310*** Integration with Travel ***
311At the moment travel scenarios are not allowed in PSM postings.
400*** Integration with CO ***
402Allocation with personnel number is not allowed in PSM. Clear value &1
403Allocation with plant is not allowed in PSM. Clear value &1.
404Allocation with procurement process not allowed in PSM. Clear value &1.
405Allocation with product is not allowed in PSM. Clear value &1.
406Allocation with recv. activity type is not allowed in PSM. Clear value &1
407Allocation with recv. order is not allowed in PSM. Clear value &1.
408Allocation with sales document is not allowed in PSM. Clear value &1.
409Allocation with work item ID is not allowed in PSM. Clear value &1.
410Personnel number is not allowed in PSM. Clear value &1.
411Receiver order is not allowed in PSM. Clear value &1.
412Receiver sales document is not allowed in PSM. Clear value &1.
413Receiver service document is not allowed in PSM. Clear value &1.
414Receiver service doc. type is not allowed in PSM. Clear value &1.
415Activity type is not allowed in PSM. Clear value &1.
416Allocation with sales document item is not allowed in PSM. Clear value &2
417Receiver sales document item is not allowed in PSM. Clear value &2.
418Receiver service document item is not allowed in PSM. Clear value &2.
420Entering statistical key figures is not supported for PSM using KB31N.
421Costs and revenues cannot be reassigned for PSM using the SAP GUI.
500*** Closing Operations ***
501Manual scheduling of this application job is not allowed.
502Unable to determine the next budget period for &1.
503Item &1 is locked by another process.
504Processing item: &1
505No items that match your selection criteria were found.
506Select at least one document type.
507Test Run
508'Payroll Agency Fund' constant not found. Check your configuration.
600*** Grantee Management ***
601Fund &2 with fund type &1 not classified for a relevant grant.
602Fund &1 as external/auxiliary fund not allowed for a non-relevant grant.
603Grant &1 requires a budget validity number.
604Grant &1 is not valid for the consumption date &2.
605Grant &1 is not valid for company code &2.
606Sponsored program &1 does not exist.
607Sponsored class &1 does not exist.
608Posting to grant &1 requires a sponsored class.
609Posting to sponsored class &1 not allowed with grant &2.
610Posting to grant &1 requires a sponsored program.
611Posting to sponsored program &1 not allowed with grant &2.
612Empty sponsored program is not allowed.
613Empty sponsored class is not allowed.
614Posting to budget validity number &1 not allowed with grant &2.
615Posting to grant &1 must be found in the 'Award' lifecycle phase.
616Fund &2 is not defined in grant &1.
617Sponsored program &2 not defined in grant &1.
618Sponsored class &2 not defined in grant &1.
619You have no authorization posting to grant &1.
620Posting to grant &1 and G/L account &2 requires a sponsored class.
625********Earmarked Funds closing***
626Source doc no. &1 with document item &2 was successfully closed.
627Source doc no. &1 with document item &2 assigned with budget period &3.
628********END Earmarked Funds closing***
700*** Custom Substitution / Validation ***
701The custom value &4 in field &1 was overwritten automatically using &3.
702The custom value &2 in field &1 was overwritten automatically using &3.
703The PSM rule &1 is executed for the target field '&2'.
704-> The new value '&2' was derived (old value '&3') for &1.
705Executing PSM derivation for line type '&1'.
706-> As source, '&1' will be used (value '&2').
707-> Executing PSM ruleset '&1'.
709The custom value &2 in field &1 was cleared automatically.
710The custom value &4 in field &1 was overwritten automatically using &3.
Privacy Policy