PPC1PR - Abarbeitung der ERP-Prozesse
The following messages are stored in message class PPC1PR: Abarbeitung der ERP-Prozesse.
It is part of development package PPC1 in software component IS-A-PPC. This development package consists of objects that can be grouped under "Backflushing in PP".
It is part of development package PPC1 in software component IS-A-PPC. This development package consists of objects that can be grouped under "Backflushing in PP".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Argument &1 not contained in table &2 |
| 002 | Assign storage location &1 for two-step backflush to an MRP area |
| 003 | Material &1 must be excluded from MRP planning for MRP area &2 |
| 008 | Processes were processed successfully |
| 009 | Processes could not be processed |
| 010 | All processes were processed |
| 011 | Too many application errors: processing terminated |
| 012 | System error: processing terminated |
| 013 | Communication error: processing terminated |
| 014 | No process reversal: processing terminated |
| 015 | No free resource: processing terminated |
| 016 | Not all started processes reversed |
| 017 | Processing finished: log & written |
| 020 | Backflush processing is currently locked by & |
| 021 | When accessing in asynchronous mode, enter the selection type |
| 022 | No backflushes found for the specified selection criteria |
| 023 | Inventory management: Insufficient quantities of material &1 in plant &2 |
| 024 | Batch determination: Insufficient quantities of material &1 in plant &2 |
| 030 | Error updating the log |
| 031 | Application error occurred |
| 050 | Not possible to write postprocessing records for activities |
| 051 | Too many postprocessing records for activities exist |
| 100 | Inconsistency of postprocessing records ( 'RSNUM' = &, 'RSPOS' = & ) |
| 101 | User &1 locking postprocessing records for assemblies &2 &3 |
| 102 | Post processing records for material & ('RSNUM'= &) are locked by user & |
| 200 | Synchronous postings of material were successful |
| 201 | Asynchronous postings of material were successful |
| 202 | Synchronous postings of material were not successful |
| 203 | Asynchronous postings of material were not successful |
| 204 | Activity postings were successful |
| 205 | Activity postings were not executed |
| 206 | General processing error: processing not possible |
| 207 | Account assignment object: &1, plant: &2, date: &3 |
| 208 | Activity postings could only be completed partially |
| 209 | No movement type exists for backflush profile &1 |
| 210 | Error when deleting |
| 211 | No details found for account assignment object &1 |
| 212 | No order number found for account assignment object &1 |
| 213 | No backflush system for account assignment object &1 |
| 214 | ... &1 seconds for procesing &2 components (&3, &4) |
| 215 | Activity postings were not executed |
| 216 | Too many material document items were required for assemblies &1 and &2 |
| 300 | Select at least one time of creation |
| 301 | &1 logs selected: display of &2 most recent logs |
| 302 | Make at least one entry for error selection |
| 400 | Plant: &1, Date: &2 |
| 503 | Server group &1 does not exist |
| 504 | System error. To analyze the error, check the system log |
| 505 | There are no resources available for server group &1 |
| 512 | Communication error for &1 &2 with &3 |
| 513 | System error for &1 &2 with &3 |
| 514 | Time exceeded for &1 with &2 |
| 515 | Time exceeded for &1 (maximum number of free processes) |
| 516 | Time exceeded for &1 (waiting for confirmation of all processes) |
| 517 | Error in posting request; no documents were created |