PSM_S4C_FM_MD -
The following messages are stored in message class PSM_S4C_FM_MD: .
It is part of development package PSM_S4C_FM_MD in software component PSM-FM-MD. This development package consists of objects that can be grouped under "Funds Management Master data".
It is part of development package PSM_S4C_FM_MD in software component PSM-FM-MD. This development package consists of objects that can be grouped under "Funds Management Master data".
Message Nr ▲ | Message Text |
|---|---|
| 017 | Blank number range is not allowed. |
| 018 | Spaces and special characters are not allowed in the key field. |
| 019 | A blank authorization group is not allowed. |
| 020 | ----- Master Data Validator (Fund)---- |
| 021 | The end of validity must not be earlier than the start of validity. |
| 022 | Fund &1 already exists. |
| 023 | Postings exist for fund &1. |
| 024 | Validity cannot start on &2; this fund has postings from &1 on. |
| 025 | Validity cannot end on &2; this fund has postings up to &1. |
| 026 | Postings already exist for this fund between &1 and &2. |
| 027 | Fund &1 is assigned to work packages (WBS elements). |
| 028 | Fund &1 is an element in global hierarchies. |
| 029 | Fund &1 is assigned to cost center. |
| 030 | Plan data exists for fund &1. |
| 031 | ----- Master Data Validator (Budget Period) ---- |
| 032 | Budget period &1 already exists. |
| 033 | Postings exist for budget period &1. |
| 034 | Validity cannot start on &2; this budget period has postings from &1 on. |
| 035 | Validity cannot end on &2; this budget period has postings up to &1. |
| 036 | Postings already exist for this budget period between &1 and &2. |
| 037 | Plan data exists for budget period &1. |
| 040 | Field &1 is a required field. |
| 041 | Fund type &1 does not exist. |
| 042 | Fund &1 does not exist. |
| 043 | Expiration date must be between start and end of validity |
| 044 | Frequency &1 does not exist. |
| 045 | Start date or expiration date overlaps with other budget periods. |
| 046 | Frequency change not allowed. Postings exist for &1. |
| 047 | Authorization group &1 does not exist. |
| 048 | Budget period &1 is an element in global hierarchies. |
| 050 | |
| 057 | ---- Message for Attachment ---- |
| 058 | Error occurred saving the attachment, remove it to proceed. |
| 059 | Object not deleted, attachment deletion cannot be performed. |
| 060 | Object deleted, but attachment deletion cannot be performed. |
| 061 | ----- Master Data Validator(Functional Area) ---- |
| 062 | Functional area &1 already exists. |
| 063 | Postings exist for functional area &1. |
| 064 | Validity cannot start on &2; this functional area has postings from &1 on |
| 065 | Validity cannot end on &2; this functional area has postings up to &1. |
| 066 | Postings already exist for this functional area between &1 and &2. |
| 067 | Functional area &1 is assigned to WBS elements. |
| 068 | Functional area &1 is an element in global hierarchies. |
| 069 | Functional area &1 is assigned to cost centers. |
| 070 | Plan data exists for functional area &1. |
| 071 | Functional area &1 is assigned to fixed assets. |
| 072 | Enter a name for functional area &1 in language &2. |
| 073 | Enter a name for functional area &1. |
| 074 | Functional area &1 has been created. |
| 075 | You are not authorized for this operation related to attachments. |
| 080 | Budget period locked by &1. |
| 081 | System error occurred when locking budget period. |
| 093 | Functional area locked by &1. |
| 094 | System error occurred when locking functional area. |
| 100 | ----- Field Status ---- |
| 101 | Activity &1 does not exist |
| 129 | ---External Service--- |
| 130 | &1 is not valid master data in Funds Management |
| 131 | Unable to open database cursor. |
| 133 | Unable to count documents. |
| 150 | ---General PSM Master Data Messages--- |
| 153 | This activity is not supported. |
| 154 | No authorization to create the master data. |
| 155 | No authorization to edit the master data. |
| 156 | No authorization to display the master data. |
| 157 | No authorization to delete the master data. |
| 161 | Master data was not created correctly. |
| 162 | Master data was not updated correctly. |
| 163 | Master data was not read correctly. |
| 164 | Master data was not deleted correctly. |
| 170 | ---Master data in plan data during update--- |
| 171 | Validity cannot start on &1; this fund has plan data from &2 on. |
| 172 | Validity cannot end on &1; this fund has plan data up to &2. |
| 173 | Plan data already exists for this fund between &1 and &2. |
| 174 | |
| 175 | Validity cannot start on &1; this budget period has plan data from &2 on. |
| 176 | Validity cannot end on &1; this budget period has plan data up to &2. |
| 177 | Plan data already exists for this budget period between &1 and &2. |
| 179 | Validity cannot start on &1; this functional area has plan dat from &2 on |
| 180 | Validity cannot end on &1; this functional area has plan data up to &2. |
| 181 | Plan data already exists for this functional area between &1 and &2. |
| 182 | |
| 183 | ---Master data in the hierarchy during update--- |
| 184 | Validity cannot start on &1; this fund has hierarchies valid up to &2. |
| 185 | Validity cannot end on &1; this fund has hierarchies valid from &2 on. |
| 186 | Hierarchies already exist for this fund between &1 and &2. |
| 187 | |
| 188 | Validity cannot start on &1; budget period hierarchies valid up to &2. |
| 189 | Validity cannot end on &1; budget period hierarchies valid from &2 on. |
| 190 | Hierarchies already exist for this budget period between &1 and &2. |
| 191 | |
| 192 | Validity cannot start on &1; functional area hierarchies valid up to &2. |
| 193 | Validity cannot end on &1; functional area hierarchies valid from &2 on. |
| 194 | Hierarchies already exist for this functional area between &1 and &2. |
| 196 | ----- Master Data Validator (GRANT) ----- |
| 197 | Validity cannot start on &1; this grant has plan data from &2 on. |
| 198 | Validity cannot end on &1; this grant has plan data up to &2. |
| 199 | Plan data already exists for this grant between &1 and &2. |
| 200 | Plan data exists for grant &1. |
| 201 | A non-relevant grant already exists. |
| 202 | Grant locked by &1. |
| 203 | System error occurred when locking the grant. |
| 204 | Non-relevant grant must not be deleted. |
| 205 | Grant &1 already exists. |
| 206 | |
| 207 | Grant &1 is assigned to work packages (WBS elements). |
| 208 | Grant &1 is an element in global hierarchies. |
| 209 | Grant &1 is assigned to cost center. |
| 210 | Grant &1 is assigned to fixed assets. |
| 211 | Validity cannot start on &1; this grant has hierarchies valid up to &2. |
| 212 | Validity cannot end on &1; this grant has hierarchies valid from &2 on. |
| 213 | Hierarchies already exist for this grant between &1 and &2. |
| 214 | Validity cannot start on &1; this grant has a cost center valid up to &2. |
| 215 | Validity cannot end on &1; this grant has a cost center valid from &2 on. |
| 216 | Cost center already assigned for this grant between &1 and &2. |
| 217 | Validity cannot start on &1; this grant has WBS elements valid up to &2. |
| 218 | Validity cannot end on &1; this grant has WBS elements valid from &2 on. |
| 219 | WBS elements already assigned for this grant between &1 and &2. |
| 220 | Validity cannot start on &1; this grant has fixed assets valid up to &2. |
| 221 | Validity cannot end on &1; this grant has fixed assets valid from &2 on. |
| 222 | Fixed assets already assigned for this grant between &1 and &2. |
| 224 | Company code &1 does not exist. |
| 225 | Grant type &1 does not exist. |
| 226 | Authorization group &1 does not exist. |
| 227 | Validity cannot start on &2; this grant has postings from &1 on. |
| 228 | Validity cannot end on &2; this grant has postings up to &1. |
| 229 | Postings already exist for this grant between &1 and &2. |
| 230 | Postings exist for grant &1. |
| 231 | Postings exist, changes to the 'Expense/Revenue' settings not allowed. |
| 232 | A/R reconciliation account &1 must have budget consumption type '55'. |
| 233 | Postings exist, 'Posting Allowed' setting must not be removed. |
| 234 | Plan data exist, 'Budgeting Allowed' setting must not be removed. |
| 235 | Fiscal year closing entries already exist in the universal journal. |
| 236 | Fiscal year closing entries already exist in the universal journal. |
| 237 | A/P reconciliation account &1 must have budget consumption type '54' |
| 238 | Budget account &1 is not enabled as a carry forward account. |
| 239 | Account &1 is an A/P reconciliation account for down payments. |
| 240 | Account &1 is an A/R reconciliation account for down payments. |
| 241 | Account &1 is relevant to cash flow. |
| 242 | Cash accounts cannot have budget consumption types '95' or '99'. |
| 243 | Reconciliation account cannot have budget consumption type '95'. |
| 244 | Indicator 'Budgeting Allowed' is not allowed. |
| 245 | Indicator 'Use Budget Account as Carry Forward Acct' not allowed. |
| 246 | Indicator 'Posting Allowed' not allowed. |
| 247 | Account cannot be a revenue account. |
| 248 | Account cannot be an expense account. |
| 249 | Indicator 'Budget-Relevant' not allowed. |
| 250 | Budget consumption type &1 must not be a cash origin account. |
| 251 | G/L Account &1 does not exist. |
| 252 | Budget consumption type &1 must not be a budget account carry forward. |
| 253 | Reconciliation account &1 must not be a cash origin account. |
| 254 | Account &1 with 'Relevant to Cash Flow' cannot be a cash origin account. |
| 255 | Settings for account &1 with budget consumption type '61' not possible. |
| 256 | Assets and contracts accounts receivable not supported for account &1. |
| 257 | Settings for account &1 with budget consumption type '54' not possible. |
| 258 | Settings for account &1 with budget consumption type '55' not possible. |
| 259 | Settings for account &1 with budget consumption type '57' not possible. |
| 260 | Budget account &1 does not exist. |
| 261 | This G/L account &1 is not assigned to a PSM-activated company code. |
| 262 | Indicator 'Use Budget Account as Carry Forward Acct' cannot be removed. |
| 263 | Postings exist. The 'Budget-Relevant' setting must not be changed. |
| 264 | 'Budget-Relevant' setting does not support the AVC for revenue accounts. |
| 265 | Customer, vendor and contracts accounts receivable not supported for &1. |
| 266 | Sponsored class does not apply to account &1. |
| 267 | Grant fiscal year variant &1 does not exist. |
| 268 | Sponsor &1 does not exist. |
| 269 | &1 not allowed by interval &2. |
| 270 | Cost center &1 does not exist. |
| 271 | Validitiy of cost center &1 does not overlap with grant. |
| 272 | Cost center &1 does not exist in company code &2. |
| 273 | Sponsor role assignment is missing for business partner &1. |
| 274 | Time slice split rule &1 does not exist. |
| 275 | Cost sharing rule &1 does not exist. |
| 276 | Billing rule &1 does not exist. |
| 277 | Grant was reset because sponsor was changed. Cancel save to reverse this. |
| 278 | No currency assigned to company code &1. |
| 300 | ----- Master Data during Update (Cost Center) ----- |
| 301 | Validity cannot start on &1; this fund has cost centers valid up to &2. |
| 302 | Validity cannot end on &1; this fund has cost centers valid from &2 on. |
| 303 | Cost center is already assigned to this fund between &1 and &2. |
| 309 | Validity cannot start on &1; func. area has cost centers valid up to &2. |
| 310 | Validity cannot end on &1; func. area has cost centers valid from &2 on. |
| 311 | Cost center already assigned to this functional area between &1 and &2. |
| 320 | ----- Master Data during Update (WBS Element) ----- |
| 321 | Validity cannot start on &1; this fund has WBS elements valid up to &2. |
| 322 | Validity cannot end on &1; this fund has WBS elements valid from &2 on. |
| 323 | WBS elements already assigned to this fund between &1 and &2. |
| 326 | Validity cannot start on &1; func. area has WBS elements valid up to &2. |
| 327 | Validity cannot end on &1; func. area has WBS elements valid from &2 on. |
| 328 | WBS elements already assigned to this functional area between &1 and &2. |
| 340 | ----- Master Data During Update (Fixed Asset) ----- |
| 341 | Validity cannot start on &1; this fund has fixed assets valid up to &2. |
| 342 | Validity cannot end on &1; this fund has fixed assets valid from &2 on. |
| 343 | Fixed assets already assigned to this fund between &1 and &2. |
| 346 | Validity cannot start on &1; func. area has fixed assets valid up to &2. |
| 347 | Validity cannot end on &1; func. area has fixed assets valid from &2 on. |
| 348 | Fixed assets already assigned to this functional area between &1 and &2. |
| 360 | ----- Master Data during Delete (Fixed Asset) ----- |
| 361 | Fund &1 is assigned to fixed assets. |
| 398 | **** Master Data Sponsored Class |
| 399 | Enter a name for sponsored class &1 in language &2. |
| 400 | Enter a description for sponsored class &1 in language &2. |
| 401 | Enter a valid sponsored class type. |
| 402 | Enter a sponsored class description. |
| 403 | Enter a sponsored class name. |
| 404 | Enter a sponsored class. |
| 405 | Sponsored class locked by &1. |
| 406 | System error when locking the sponsored class. |
| 407 | Postings for sponsored class &1 exist. |
| 408 | Sponsored class &1 does not exist. |
| 409 | Sponsored class &1 has been created. |
| 410 | Sponsored class &1 has been deleted. |
| 411 | Sponsored class &1 already exists. |
| 412 | You cannot change the class type: Postings already exist. |
| 413 | You cannot delete sponsored class &1: Postings already exist. |
| 414 | Sponsored program &1 does not exist. |
| 415 | You cannot delete sponsored class &1: it is used by grants |
| 416 | Enter a description for sponsored class &1. |
| 417 | Enter a name for sponsored class &1. |
| 418 | Class type can be expense or revenue for a sponsored class &1. |
| 419 | |
| 421 | Enter a sponsored program description. |
| 422 | Enter a sponsored program name. |
| 423 | Enter a sponsored program. |
| 424 | Sponsored program locked by &1. |
| 425 | System error occurred when locking the sponsored program. |
| 426 | Postings for sponsored program &1 exist. |
| 427 | Sponsored program &1 has been created. |
| 428 | Sponsored program &1 has been deleted. |
| 429 | Sponsored program &1 already exists. |
| 430 | You cannot delete sponsored program &1: Postings already exist. |
| 431 | You cannot delete sponsored program &1: it is used by grants |
| 432 | Enter a description for sponsored program &1. |
| 433 | Enter a name for sponsored program &1. |
| 434 | Enter a name for sponsored program &1 in language &2. |
| 435 | Enter a description for sponsored program &1 in language &2. |
| 438 | ***Master Data Grant |
| 439 | Fiscal year variant &1 is not defined or maintained for date &2. |
| 440 | Correct the fiscal year variant &1 so it has 12 periods. |
| 441 | Unexpected life cycle status &1 is assigned to the grant. |
| 442 | Sponsored class &1 does not exist. |
| 443 | Number range object GRANT is missing. Contact your administrator. |
| 444 | Number range interval &1 must be internal. |
| 445 | Number range interval &1 must be external. |
| 446 | Number range interval &1 for grant type &2 does not exist. |
| 447 | Number assignment failed. Grant was not created. |
| 448 | Unspecified problem with number range &1. |
| 449 | &1 is not allowed by interval &2. |
| 450 | Budget is already assigned. Budget validity time slices cannot be reset. |
| 451 | Only continuous time slices are allowed, expected valid from date is &1. |
| 452 | Budget validity time slices do not cover the entire grant validity. |
| 453 | Grant type &1 must be assigned an internal or external number range. |
| 454 | Time slice &1 cannot be deleted after budget is assigned. |
| 455 | Time slice validity is outside the budget postings date &1 &2. |
| 456 | Valid from date &1 must not be later than grant validity start date &2. |
| 457 | Valid to date &1 must not be earlier than grant validity end date &2. |
| 458 | No controlling area has been assigned to company code &1. |
| 459 | Grant type &1 must be assigned an internal number range. |
| 460 | Grant type &1 must be assigned an external number range. |
| 461 | No FM area has been assigned to company code &1. |
| 462 | Fund &1 does not exist. |
| 463 | Grant validity cannot end on &1; Cost center &2 is valid from &3. |
| 464 | Grant validity cannot start on &1; Cost center &2 is valid till &3. |
| 465 | Add one timce slice at a time. |
| 466 | Time slice cannot be added between &1 and &2. |
| 467 | Cost sharing indicator can only be set for an internal fund. |
| 468 | Configure an initial lifecycle status for grant type &1. |
| 469 | Funds which have GM fund type as 'Internal' or 'External' can be added. |
| 470 | Authorization group &1 is assigned to the grant. |
| 471 | Grant type &1 is assigned to the grant. |
| 472 | Enter an internal number range when assignment type is 'Internal Only'. |
| 473 | Enter an external number range when assignment type is 'External Only'. |
| 474 | Enter both number ranges when assignment type is 'Internal or External'. |
| 475 | 'ExNumRg' must be empty when assignment type is 'Internal Only'. |
| 476 | 'InNumRg' must be empty when assignment type is 'External Only'. |
| 477 | Unable to create grant &1. |
| 478 | Enter a name for grant &1 in language &2. |
| 479 | Grant number is missing for external grant from grant type &1. |
| 480 | Plan data exists for time slice &1. |
| 481 | Grant &1 has been created. |
| 482 | Fund &1 assigned for cost sharing of grant &2 is not an internal fund. |
| 483 | Cost sharing is not enabled for fund &1 in grant &2. |
| 484 | Sponsored program &1 is not assigned to grant &2 for cost sharing. |
| 485 | Sponsored class &1 is not assigned to grant &2 for cost sharing. |
| 486 | Fund &1 is not assigned to grant &2 for cost sharing. |
| 487 | Valid from date &1 must not be earlier than budget validity start date &2 |
| 488 | Valid to date &1 must not be later than budget validity end date &2. |
| 489 | The expected 'From Date' is &3 for grant &1 with time slice &2. |
| 490 | Sponsored class &1 in 'Cost Sharing Details' is not 'Expense' type. |
| 491 | Sponsored class &1 in grant &2 does not exist. |
| 492 | Sponsored program &1 in grant &2 does not exist. |
| 493 | Grant type &1 has internal assignment type. Grant number must be empty. |
| 494 | IDC-relevant indicator can only be set for an expense sponsored class. |
| 495 | IDC recovery indicator can only be set for an internal fund. |
| 496 | Only one internal fund can have IDC recovery indicator checked. |
| 497 | Only one fund with grant fund type as external is allowed. |