/SCTM/BO
53 messages in this application area
Each row lists the SAP message number and the English message text as provided in the source extract. Use anchors (e.g. #msg-123) to deep-link to a specific message on this page.
| Message | Message text |
|---|---|
| 1 | Error accessing number range (shipment type &1/freight document type &2) |
| 2 | Document &1 was not found |
| 3 | Incorrect category &1 |
| 4 | A general error has occurred |
| 5 | Error calling the postprocessing framework |
| 6 | Function was called with incorrect input data |
| 7 | Creation of the business object failed |
| 8 | Deletion of the business object failed |
| 9 | Generation of administration class for business objects failed |
| 10 | No authorization for activity &1 |
| 11 | SAPscript read error |
| 12 | SAPscript save error |
| 13 | SAPscript deletion error |
| 14 | SAPscript error; check Customizing |
| 15 | Source location/business partner in document &1 does not exist |
| 16 | Destination location/business partner in document &1 does not exist |
| 17 | Assigning the document has failed |
| 18 | Deletion of the document assignment has failed |
| 19 | Operation &2 is not possible for document &1 |
| 20 | Reading document &1 has failed (&2 &3 &4) |
| 21 | Document &1 &2 does not exist |
| 22 | Error in status management |
| 23 | No Customizing exists for document category &1 |
| 24 | No authorization for transportation status activity & |
| 25 | No authorization for requested activity |
| 26 | Saving was not successful |
| 27 | Internal call error: invalid structure for document (&1 &2 &3 &4) |
| 28 | Processing stops has failed |
| 29 | Inbound message processing was terminated due to errors |
| 30 | Document &3 &1 (&4) is locked by user &2 |
| 31 | Location &1 not found |
| 32 | Business partner &1 not found |
| 33 | Error when determining the address |
| 34 | Alternative address number &1 does not exist for location &2/partner &3 |
| 35 | Location &1 does not exist in the master data |
| 36 | Business partner &1 does not exist in the master data |
| 37 | Assignment of document &1 to document &2 not possible: &3 not found |
| 38 | Transport. planning point determ: sender in shipment &1 does not exist |
| 39 | Transport. planning point determ: sender in frgt doc &1 does not exist |
| 40 | Status management: operation &1 is not possible |
| 41 | You cannot delete freight document &1: document assignments exist |
| 42 | You cannot delete bill of lading &1: document assignments exist |
| 43 | You cannot change freight document &1: status &2 is set |
| 44 | Document &1 was deleted |
| 45 | You cannot change document &1; changes were not saved |
| 46 | Document &1 is locked; changes were not saved |
| 47 | Document &1 was changed since being selected; changes were not saved |
| 48 | Location for business partner &1 does not exist |
| 49 | Document &1 that is assigned to item &2 of document &3 was not found |
| 50 | Stops cannot be determined for document &1 |
| 51 | Error when converting weight from &1 to &2 |
| 52 | Document &1 was saved |
| 53 | Processing was terminated on purpose; debugging parameter is active |
Message texts are shown for technical reference in consulting and education contexts. SAP, SAP TM, SAP EWM, SAP GTS, SAP S/4HANA and other SAP product and service names are trademarks or registered trademarks of SAP SE in Germany and other countries.