FINS_ONE_ALLOCATION -

The following messages are stored in message class FINS_ONE_ALLOCATION: .
It is part of development package FINS_ONE_ALLOCATION in software component FI-GL-GL. This development package consists of objects that can be grouped under "One Allocation".
Message Nr
Message Text
001Business transaction could not be determined for &, & and &.
002Ledger & could not be found.
003Plan Category & could not be found.
004Company Code & could not be found.
005Error occurred determining fiscal year variant.
006No currency type defined in Plan Category &1. 'P' is used.
007Primary/ secondary cost element & cannot be used in Profi Center Alloc.
008Master Data for field & is missing.
009No reference data.
010Error period.
011Error period acc.
012Invalid input.
013&1 field &2 (&3) of segment &4 is mandatory and contains no value
014&1 field &2 (&3) of cycle &4 is mandatory and contains no value
015The number of exec. periods and receiver data periods differs.
016Save template before setting mark flag.
017Select the markable column.
018Template already used in allocation; fields could not be changed.
019Default fields could not be changed.
020Search unsuccessful; no hits found for entered field.
021Invalid one allocation field category found; choose the valid value.
022Only account-based operating concern allowed.
023Specify values between 0 and 100 only.
024Please use the Fiori apps for universal allocations.
025& field & of segment & should not contain a value:
026Error during derivation.
027Some company codes are enabled for Public Sector and some not.
028The end date & of cycle & is prior to the start date &
029Determined input fields differ from the actual input fields
030PSM derivation with a fix value for field: & failed.
031A input value was overwritten by the derivation.
032Missing message for cost center has fixed PSM value assigned.
033WBS element & does not exist in company code & .
034The plan category &1 is used for &2 which is not allowed.
035Another user locks Actual Allocation for ledger &
036Another user locks Plan Allocation for ledger &
037Cycle & & cannot be started because run group & is locked.
038Derivation behavior modification for field &1 on &2 side is not supported
039Company codes of cycles are assigned to different operation concerns.
040The defined formula is not allowed
041Maintain custom key figure in detailed page before toggling the flag.
042Only numeric type custom field allowed.
043Invalid input; only custom field from universal journal entry allowed.
044Object type & is not allowed as Receiver Tracing Factor.
045Customer reference key figure data is incomplete.
046Value fields in customer reference key figure should be different.
047Master data field & is superfluous
048The field &1 (&2) is not fully configured and might be removed.
049Cycle &1 cannot be executed for ledger &2.
050Cycle &1 &2 uses the same name as cycle &3 &4.
051Validity range of Flexible Ledger Cycle &1 &2 overlaps with other cycles
052Validity range of cycle &1 &2 overlaps with other Flexible Ledger Cycles
053Cycle &1 &2 was already executed for a different ledger
054Receiver portions in segment &1 in cycle &2 &3 exceed the limit
055End date of cycle &1 &2 is before period &3 for which it was executed
056Cycle &1 &2 uses company code &3 which not assigned to ledger &4.
057Segm. &1 of Cycle &2 uses &3 which not defined in Ledger/Company Code &4
058Maintain additional reference key figure before saving template
059Field &1 cannot be set as distributed category
062A combination is invalid: &1 &2 &3 &4.
063Cycle &1 must be only defined for the leading ledger &2.
064Leading ledger is not configured correctly.
065No valid accounts from area &1 / &2 exist.
066Operating concern &1 must be defined exclusively for account-based CO-PA.
067Receivers in segment &1 of cycle &2 use different currency codes
068Company code &1 in segment &2 is not assigned to controlling area &3
069Error while retrieving clearing accounts for account &1
070Incorrectly defined interval for field &1 in segment &2 of cycle &3
071Group &1 in segment &2 of cycle &3 does not exist
072The group &1 used in cycle &2 is invalid
073Company code &1 in segment &2 of cycle &3 is not assigned to ledger &4
074No clearing account for overhead account &1 is defined.
075Company code &1 is used as sender and receiver in segment &2 of cycle &3
076Allocations from company code &1 to company code &2 is not allowed.
077Intercompany allocation cycle &1 can not use &2 as field group
078Intercompany allocation cycle &1 can not be defined as flex. ledger cycle
079Intercompany allocation cycle &1 can not allocate cross company code &2
080Provide Company Code to determine fields of the asgn. operating concern
081No operating concern could be determined for company code &1.
082Error for operating concern &1 which is assigned to the used company code
083Field &1 not assigned to operating concern &2 of used company code &3.
091Segment &1 of cycle &2 must not use an allocation structure.
092In segment &1, provide either an assessment acct or an alloc. structure.
093Allocation Structure &1 in segment &2 of cycle &3 doesn't exist.
094Alloc Structure &1 in segm &2 of cycle &3 cannot be used for allocations.
095Results of cycle &1 did not pass the checks.
107You must also reverse plan cycle &1 &2 from periods &3 to &4.
108Cost center &1 is blocked for actual primary postings.
109Cost center &1 is blocked for actual secondary postings.
110Cost center &1 is blocked for plan primary postings.
111Cost center &1 is blocked for plan secondary postings.
Privacy Policy