/SCMB/DOCFLOW
58 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 |
|---|---|
| 0 | Unknown error &1 occurred |
| 1 | Attributes transferred in incorrect parameter |
| 2 | Attribute error |
| 3 | Attribute error (detail) |
| 4 | Source client must be different from current client |
| 10 | Attribute &1 not allowed |
| 11 | Attribute &1 could not be updated (link category &2) |
| 12 | Attribute &1 for link category &2 not supported |
| 21 | Persistent class of attribute &1 not completely implemented |
| 22 | Table &3 of attribute &1 does not exist |
| 30 | &3: Table &1 contains entries for client &2; see long text |
| 31 | &1: Customizing updated in client &2; table &3 created |
| 32 | &2: Table &1 created |
| 33 | Table could not be created |
| 34 | &1 does not exist; check name |
| 35 | Table &1 could not be activated; see long text |
| 36 | No entry exists for category &1 in /SCMB/DF_D_TYPEG in client &2 |
| 37 | Table for category &1 in client &2 must be generated again |
| 38 | Processing in client &1: |
| 39 | Errors or warnings were triggered during processing; see application log |
| 40 | Copying of data from table &1 into &2 failed due to duplicate key |
| 41 | Target table &1 does not exist or is inactive. Copying of data failed |
| 42 | Source table &1 and target table &2 are not compatible. Copying failed |
| 43 | &1: Number of records successfully exported from table &2: &3 |
| 44 | &1: Number of records successfully imported into table &2: &3 |
| 45 | &1: Customizing updated in client &2. Table name: &3 |
| 46 | &1: Structure name is deleted but table &2 is not empty |
| 50 | Error in network administration |
| 51 | Link category of link &2 missing (network ID &1) |
| 52 | No network ID (or link ID) transferred |
| 53 | No network ID exists for link &1 |
| 60 | Network ID not supported |
| 61 | Network ID not supported for link category &1 |
| 70 | Assignment of network ID &1 does not match structure of links |
| 71 | &2 network IDs used for links of network &1 |
| 72 | Network ID &1 used for several (&2) separate networks |
| 73 | Network of link &1 not read correctly (&2 networks) |
| 100 | Link error |
| 101 | Transfer both a maximum chain and a list of links |
| 102 | Link not specified |
| 110 | Link invalid |
| 120 | Maximum chain &1 invalid |
| 121 | Category of start document not specified |
| 122 | Maximum chain &1 not defined |
| 130 | Link category &1 not allowed |
| 131 | No link or link ID specified |
| 132 | Link ID &2 (link category &1) does not exist |
| 140 | Link category &1 not defined |
| 141 | Table &2 of link category &1 cannot be used |
| 200 | Document error |
| 201 | Documents involved not completely specified |
| 202 | Document with index &1 not transferred |
| 203 | Criteria transferred not sufficient to select documents |
| 210 | Document error |
| 221 | Document specified not found |
| 230 | Error in document administration |
| 231 | Structure &2 with characteristics of document category &1 invalid |
| 232 | Document category &1 does not exist |
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.