SAP ABAP Message Class FAGL_SWITCH_LEAD_LDG (Technical Changeover of Leading View in General Ledger (New))
Basic Data
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷
FI-GL-FL (Application Component) Flexible Structures
⤷
FAGL_SWITCH_LEADING_LEDGER (Package) Technical Changeover of Leading View in General Ledger (New)
⤷
⤷
Attributes
| Message class | FAGL_SWITCH_LEAD_LDG | |
| Short Description | Technical Changeover of Leading View in General Ledger (New) | |
| Changed On | 20131127 | |
| Last Changed At | 180703 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Multiple active switch projects exist | The short text describes the object sufficiently | ||
| 2 | You do not have authorization for activity &2 in plan &1 | The short text describes the object sufficiently | ||
| 3 | Ledger &2 is defined as leading ledger (&1 is invalid) | Space: object requires documentation | ||
| 4 | Ledger &1 is not defined for application &2 &3 | The short text describes the object sufficiently | ||
| 5 | Ledger &1 is not defined as new leading ledger | Space: object requires documentation | ||
| 6 | Business function FIN_GL_CHNG_LEAD_VAL is not active | Space: object requires documentation | ||
| 7 | A switch project is still active: &1 | The short text describes the object sufficiently | ||
| 8 | Switch project is active and therefore cannot be deleted | The short text describes the object sufficiently | ||
| 9 | Internal error | The short text describes the object sufficiently | ||
| 10 | Check was run for: previous leading ledger &1 | The short text describes the object sufficiently | ||
| 11 | Check was run for: future leading ledger &1 | The short text describes the object sufficiently | ||
| 12 | Check was run for: date of switch &1 | The short text describes the object sufficiently | ||
| 13 | Choose a non-leading ledger | The short text describes the object sufficiently | ||
| 14 | Posting with ledger group &1 in year &2 is not possible | Space: object requires documentation | ||
| 15 | Switch project from year &1 is still active; check this project | Space: object requires documentation | ||
| 16 | Internal error: Activity &1 is not modeled | The short text describes the object sufficiently | ||
| 17 | Switch project could not be activated | Space: object requires documentation | ||
| 18 | &1 is not a permitted transaction for this program | Space: object requires documentation | ||
| 19 | Prerequisites for switching leading ledger have not been met | Space: object requires documentation | ||
| 20 | This message does not have a long text | The short text describes the object sufficiently | ||
| 21 | Switch project cannot be stopped; postings already exist | Space: object requires documentation | ||
| 22 | Switch project is active and cannot be changed | Space: object requires documentation | ||
| 23 | Execution | The short text describes the object sufficiently | ||
| 24 | The requested exception &1 is not permitted | Space: object requires documentation | ||
| 25 | A switch project does not exist | The short text describes the object sufficiently | ||
| 26 | Switch project &1 has an undefined status | The short text describes the object sufficiently | ||
| 27 | Check on company code assignment | The short text describes the object sufficiently | ||
| 28 | Ledger &1 is activated in all company codes | The short text describes the object sufficiently | ||
| 29 | Ledger &1 is not activated in all company codes | Space: object requires documentation | ||
| 30 | Check on company codes | The short text describes the object sufficiently | ||
| 31 | Check for company code &1 | The short text describes the object sufficiently | ||
| 32 | Ledger &1 is not implemented in company code &2 | Space: object requires documentation | ||
| 33 | Documents exist in company code &1 as of fiscal year &2 | Space: object requires documentation | ||
| 34 | No documents exist in company code &1 as of fiscal year &2 | The short text describes the object sufficiently | ||
| 35 | Local crcy type &1 inconsistent: old leadg ldgr: &2, new leadg ldgr: &3 | Space: object requires documentation | ||
| 36 | Matching fiscal year variant &1 in fiscal year &2 | The short text describes the object sufficiently | ||
| 37 | Fiscal year start &1 is inconsistent: &2 &3 | Space: object requires documentation | ||
| 38 | Fiscal year end &1 is inconsistent: &2 &3 | Space: object requires documentation | ||
| 39 | Ledger-specific documents exist for Treasury/Loans components | Space: object requires documentation | ||
| 40 | Scenario &1 is not assigned to ledger &2 | Space: object requires documentation | ||
| 41 | Cannot change leading ledger; FI-AA (new) not active | Space: object requires documentation | ||
| 42 | Activity was not completed successfully | The short text describes the object sufficiently | ||
| 43 | Date &1 is not start of fiscal year in company code &2 | Space: object requires documentation | ||
| 44 | No fiscal year variant is defined for company code &1 | The short text describes the object sufficiently | ||
| 45 | Leading ledger was reset to &1 | Space: object requires documentation | ||
| 46 | Period start &1 in variant &2 differs from &3 variant &4 | Space: object requires documentation | ||
| 47 | Period end &1 in variant &2 differs from &3 variant &4 | Space: object requires documentation | ||
| 48 | Identical fiscal year start for variant &1 &2 in year &3 | The short text describes the object sufficiently | ||
| 49 | Identical fiscal year end for variant &1 &2 in year &3 | The short text describes the object sufficiently | ||
| 50 | Update of classic G/L accounting (GLT0) is no longer possible | Space: object requires documentation | ||
| 51 | Checking ledger-specific documents | The short text describes the object sufficiently | ||
| 52 | Ledger-specific documents already exist in &2 in company code &1 | Space: object requires documentation | ||
| 53 | Ledger-specific documents in company code &1 checked successfully | The short text describes the object sufficiently | ||
| 54 | Ledger-specific documents excluded from checks: | The short text describes the object sufficiently | ||
| 55 | Exception defined for project start: Document &1 &2 &3 | The short text describes the object sufficiently | ||
| 56 | Check scenarios | The short text describes the object sufficiently | ||
| 57 | Ledger group check | The short text describes the object sufficiently | ||
| 58 | Ledger group &1 changed by switch project | Space: object requires documentation | ||
| 59 | Ledger-specific documents excluded from checks: | The short text describes the object sufficiently | ||
| 60 | Exception defined for project start: Document &1 &2 &3 | The short text describes the object sufficiently | ||
| 61 | Switch project does not have the required status for this step | Space: object requires documentation | ||
| 62 | Activity was completed successfully | The short text describes the object sufficiently | ||
| 63 | Activity was not performed successfully; see message log | The short text describes the object sufficiently | ||
| 64 | This step is not required in the current status | Space: object requires documentation | ||
| 65 | Project status was changed; new status: &2 | Space: object requires documentation | ||
| 66 | &1: Lock is activated | Space: object requires documentation | ||
| 67 | &1: Lock is deactivated | Space: object requires documentation | ||
| 68 | &1: possible | Space: object requires documentation | ||
| 69 | &1: not possible | Space: object requires documentation | ||
| 70 | You have not confirmed | The short text describes the object sufficiently | ||
| 71 | Leading ledger was switched from &1 to &2 | The short text describes the object sufficiently | ||
| 72 | &1 is already the leading ledger | The short text describes the object sufficiently | ||
| 73 | Ledger group &1: Representative ledger switched from &2 to &3 | The short text describes the object sufficiently |
History
| Last changed on/by | 20131127 | SAP | |
| SAP Release Created in | 607 |