/SPE/INSPRES - Inspection Outcome Messages for Complaints & Returns SPM
The following messages are stored in message class /SPE/INSPRES: Inspection Outcome Messages for Complaints & Returns SPM.
It is part of development package /SPE/RET_INSPECTIONS in software component LO-SPM-RET. This development package consists of objects that can be grouped under "".
It is part of development package /SPE/RET_INSPECTIONS in software component LO-SPM-RET. This development package consists of objects that can be grouped under "".
Message Nr ▲ | Message Text |
|---|---|
| 000 | You are not authorized to &1 inspection outcomes |
| 001 | Input parameters for publishing inspection outcomes are inconsistent |
| 002 | Field &1 value &2 is not valid for &3 |
| 003 | Cannot create inspection outcomes for RMA &1 delivery &2 and HU &3 |
| 004 | Inspection outcomes created successfully for RMA &1 delivery &2 and HU&3 |
| 005 | Method executed successfully |
| 006 | No inspection outcomes selected for given criteria |
| 007 | Cannot perform database updates |
| 008 | No record exists in database for RMA &1 delivery &2 and HU &3 |
| 009 | Inspection outcome changed successfully for RMA &1 delivery &2 and HU &3 |
| 010 | Item records supplied without header for business key &1 |
| 011 | Status prevents deletion of inspection outcome for RMA &1 delivery &2 |
| 012 | No input data is supplied to method |
| 013 | Publish destinations given are inconsistent |
| 014 | No publish destination is given as parameter |
| 015 | Entries are locked for Inspection outcome RMA &1 delivery &2 by user &3 |
| 016 | Technical locking error for RMA &1 delivery &2 |
| 017 | No follow up activity allowed for returns delivery &1 and RMA &2 |
| 018 | Inconsistent parameter combination is passed to function module |
| 019 | Inspection outcome for RMA &1 delivery &2 and HU &3 is already confirmed |
| 020 | Reference to delivery is missing in inspection outcome |
| 021 | Inspection outcomes for RMA &1 delivery &2 and HU &3 deleted |
| 022 | Inspection outcomes not yet maintained for RMA &1 delivery &2 and HU &3 |
| 023 | Destination CRM system could not be found |
| 024 | No queue could be set for CRM communication |
| 025 | No destination EWM system found in distribution model |
| 026 | No queue could be set for EWM communication |
| 027 | Inspection outcome for RMA &1 delivery &2 is not assigned to a warehouse |
| 028 | No inspection outcome sent to CRM |
| 029 | Combination of catalog &1, code group &2 and code &3 not valid |
| 030 | No default catalog profile defined |
| 031 | Codes must be defined by combination of catalog, code group and code. |
| 032 | Number range failure during creation of inspection outcome for RMA &1 |
| 033 | Follow-up activity is mandatory for returns delivery &1 RMA &2 |
| 034 | No codes defined for follow-up activity 'Putaway' in Customizing |
| 035 | Stock Type &1 of Goods Movement (Primary Posting) not supported |
| 036 | Default follow-up activity for returns delivery &1 must not be initial |
| 037 | Handling unit &1 contains uninspected parts and cannot be confirmed |
| 038 | Inspection outcomes for RMA &1 delivery &2 not published to EWM. |
| 039 | Handling unit &1 item &2 has uninspected parts |
| 040 | Inspection outcome for RMA &1 not sent to CRM due to its status |
| 041 | Inspection outcome not sent to CRM due to technical issue |
| 042 | Inspection outcomes not yet maintained for RMA &1 and delivery &2 |
| 043 | Inspection outcome for RMA &1 and delivery &2 is already confirmed |
| 044 | Inspection outcome changed successfully for RMA &1 and delivery &2 |
| 045 | No record exists in database for RMA &1 and delivery &2 |
| 046 | Cannot create inspection outcomes for RMA &1 and delivery &2 |
| 047 | Inspection outcomes for RMA &1 and delivery &2 deleted |
| 048 | Inspection outcomes created successfully for RMA &1 and delivery &2 |
| 049 | Inspection outcome for HU &1 item &2 added to publish request to CRM |
| 050 | Inspection outcomes deletion not successful. |
| 051 | Inspection Outcome for RMA &1 Delivery &2 published to &3 |
| 052 | Inspection data from buffers is empty |