FINS_FI_MASS_DATA - Mass Data Handling
The following messages are stored in message class FINS_FI_MASS_DATA: Mass Data Handling.
It is part of development package FINS_FI_MASS_DATA in software component FIN-MIG. This development package consists of objects that can be grouped under "Financial Accounting (SAP_FIN): Mass Data Handling".
It is part of development package FINS_FI_MASS_DATA in software component FIN-MIG. This development package consists of objects that can be grouped under "Financial Accounting (SAP_FIN): Mass Data Handling".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | 50% of available work processes are selected by default |
| 002 | Number of batch jobs set to &1% of available jobs. SAP Note 3036450 |
| 003 | Number of batch jobs set to as per customizing. SAP Note 3036450 |
| 100 | --- Mass Data Handling -------------------------------------------------- |
| 101 | &2 job &1 scheduled for immediate execution |
| 102 | Cannot lock table &1; &2 is already running (user &3) |
| 103 | &2 is complete in client &1 |
| 104 | &3 step &2 completed in client &1 |
| 105 | Preparation for step &1 failed |
| 106 | Cannot create background job &1 |
| 107 | Report can run as batch job only |
| 108 | Completed &1 &2 work packages |
| 109 | No background work processes available |
| 110 | &3 step &1 failed for work package &2; try again |
| 111 | &3 step &1 for work package &2 was completed successfully |
| 112 | Program must be started from a transaction |
| 113 | No log available |
| 114 | Cannot display job log; insufficient authorization |
| 115 | Cannot display application log for client &1 |
| 116 | &2 is not necessary in client &1; no data available |
| 117 | No data needs to be processed in step &2 in client &1 |
| 118 | &2 was not yet started in client &1 |
| 120 | &1 does not support repeated runs |
| 122 | New run not allowed. Predecessor job &1 (&2) exists |
| 124 | Reset method not implemented for set id &1, step id &2 |
| 125 | Reset not allowed in Near-Zero-Downtime mode |
| 126 | Analysis of Transactional Data not allowed in Near-Zero-Downtime mode |
| 127 | Trigger tables can only be filled in Near-Zero-Downtime mode |
| 128 | &1 jobs scheduled for immediate execution |
| 129 | Cannot display overview log for client &1 |
| 130 | No error or warning messages in the selected packages |
| 131 | Some logs no longer exist; Overview is incomplete |
| 132 | Too many messages found. Cannot show complete overview |
| 133 | Error processing for &1 in client &4 is locked by user &2 |
| 134 | Run &3 still active for &1. Try again later |
| 135 | Upgrade still running. Function is currently not available |
| 136 | Process stopped for load balancing reasons |
| 137 | Reset run is only possible with a previous run |
| 138 | Process stopped because lock could not be set |
| 139 | Start of run not allowed currently (see long text) |
| 140 | Previous run &1 was already reset |
| 141 | No run allowed before the reset run &1 is finished |
| 142 | Reset activity &1 in simulation mode |
| 143 | Reset activity &1 in update mode |
| 144 | No of packages selected for reset: &1 |
| 145 | Reset data for step &1, package key &2 |
| 146 | Resetting potential leftovers for step &1 |
| 147 | Selection criteria for &1: '&2' |
| 148 | Reset run only possible for all steps, not for single step &1 |
| 149 | Cannot perform activity &1 currently |
| 150 | Cannot reset activity &1 currently |
| 151 | &3 step &1 for work package &2 was reset successfully |
| 152 | Resetting &3 step &1 failed for work package &2; try again |
| 153 | Previous runs contain no packages to reset |
| 154 | Mark a line for which to show the single messages |
| 155 | You can only accept errors in completed work packages |
| 156 | Action was only partially executed |
| 157 | Set ID &1 is invalid |
| 158 | Application class &1 does not exist (Set ID &2 / Step ID &3) |
| 159 | Cannot re-run activity &1 currently |
| 160 | Unit Test: Project &1 is processed |
| 161 | Unit Test: Set ID &1, Step ID &2, Package &3 is processed |
| 162 | Unit Test: Some Error Message |
| 163 | Unit Test: Package &1 sucessfully processed in &2 seconds |
| 164 | Unit Test: Package &1 sucessfully reset |
| 165 | Unit Test: Remaining Data of Set ID &1 / Step ID &2 reset |
| 166 | Re-run of run &1 with type &2 not possible (project &3) |
| 167 | No error overview available (select node on lower level) |
| 170 | Creation of new packages is only allowed if final package exists |
| 171 | Server group &1 is invalid |
| 172 | Enter a positive number |
| 301 | Running in client &1 |
| 302 | Processing key &1 |
| 303 | &1 entries deleted from shadow table FINS_ACCEPT_TRA |
| 304 | &1 entries read from message table FINS_ACCEPT_MSG |
| 305 | &1 entries inserted into shadow table FINS_ACCEPT_TRA |
| 306 | &1 entries read from shadow table FINS_ACCEPT_TRA |
| 307 | Entries for accepted errors updated in message table FINS_ACCEPT_MSG |
| 308 | Running in client &1 (target client "&2", upgrade="&3") |
| 309 | Export conflicts with import of request &1 |
| 310 | Transport &1 marked as processed |
| 311 | Analysis of workpackages and logs for activity &1 &2 successful |
| 401 | ABAP class &1 for mass data activity &2 does not exist |
| 402 | ABAP class &1 does not implement mandatory interface &2 |
| 403 | Enter an ABAP class. &1 is an interface |
| 404 | Mass data activity &1 is still used in tables; For example: &2 |
| 405 | &1: Names starting with U are reserved for test automates |
| 406 | &1: Names starting with &2 or &3 are reserved for Central Finance |
| 407 | No versions exist for mass data activity &1 |
| 408 | General text with name &1 does not exist |