SAP ABAP Message Class PLM_SE_PRS_MESSAGES (Message class for PS services)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
PS (Application Component) Project System
⤷
PLM_SE_PRS_XI_PROXY (Package) Proxy implementations for Project System
⤷
⤷
Attributes
| Message class | PLM_SE_PRS_MESSAGES | |
| Short Description | Message class for PS services | |
| Changed On | 20100310 | |
| Last Changed At | 182855 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | ChangeStateID could not be determined. | The short text describes the object sufficiently | ||
| 2 | No update possible, data has been changed since last read | The short text describes the object sufficiently | ||
| 3 | Mandatory field &1 not provided. | The short text describes the object sufficiently | ||
| 4 | Field &1 not found in table &2. | The short text describes the object sufficiently | ||
| 5 | Value &1 not found in table &2. | The short text describes the object sufficiently | ||
| 6 | &1 party ID is missing. | The short text describes the object sufficiently | ||
| 7 | The partner with ID &1 and role code &2 could not be read. | The short text describes the object sufficiently | ||
| 8 | Invalid action code for party. | The short text describes the object sufficiently | ||
| 9 | The required network ID is missing. | The short text describes the object sufficiently | ||
| 10 | Provide only one ID as network parent! | The short text describes the object sufficiently | ||
| 11 | Exactly one of ID or SenderTechnicalID has to be provided for activity &1 | The short text describes the object sufficiently | ||
| 12 | The unit of measure for Free/Total Float Duration must be DAY! | The short text describes the object sufficiently | ||
| 13 | The content of &1 exceeds the field length of the target field. | The short text describes the object sufficiently | ||
| 14 | Invalid domain value: &1 in &2. | The short text describes the object sufficiently | ||
| 15 | Exactly one duration unit allowed. | The short text describes the object sufficiently | ||
| 16 | The partner &1 already exists. | The short text describes the object sufficiently | ||
| 17 | The partner &1 is not assigned to this project. | The short text describes the object sufficiently | ||
| 18 | WBS &1 already exists. | The short text describes the object sufficiently | ||
| 19 | WBS &1 does not exist. | The short text describes the object sufficiently | ||
| 20 | Milestone &1 already exists. | The short text describes the object sufficiently | ||
| 21 | Milestone &1 does not exist. | The short text describes the object sufficiently | ||
| 22 | Network &1 already exists. | The short text describes the object sufficiently | ||
| 23 | Network &1 does not exist. | The short text describes the object sufficiently | ||
| 24 | Only Customer/Vendor code values are permitted for Product Recipient. | The short text describes the object sufficiently | ||
| 25 | For action &1 the mandatory fields are missing. | The short text describes the object sufficiently | ||
| 26 | Activity &1 already exists. | The short text describes the object sufficiently | ||
| 27 | Activity &1 does not exist. | The short text describes the object sufficiently | ||
| 28 | No InternalID-TechnicalID correspondence found. | The short text describes the object sufficiently | ||
| 29 | Material component already assigned to the activity. | The short text describes the object sufficiently | ||
| 30 | Not assigned material component. | The short text describes the object sufficiently | ||
| 31 | Relationship already exists. | The short text describes the object sufficiently | ||
| 32 | Nonexistent relationship. | The short text describes the object sufficiently | ||
| 33 | Enter either SuccessorNetworkID or SuccessorNetworkSenderTechnicalID. | The short text describes the object sufficiently | ||
| 34 | Invalid value &1 for &2. | The short text describes the object sufficiently | ||
| 35 | NetworkRelationship: Predecessor network must be the parent network. | The short text describes the object sufficiently | ||
| 36 | NetworkRelationship: Predecessor activity must be the parent activity. | The short text describes the object sufficiently | ||
| 37 | The action on milestone &1 could not be performed. | The short text describes the object sufficiently | ||
| 38 | Exactly-once request cannot be locked: &1 (error code: &2). | The short text describes the object sufficiently | ||
| 39 | Exactly-once request timed out (message UUID &1). | The short text describes the object sufficiently | ||
| 40 | Internal error in exactly-once processing (message UUID &1). | The short text describes the object sufficiently | ||
| 41 | UUID &1 for element &2 does not comply to required pattern. | The short text describes the object sufficiently | ||
| 42 | Internal error storing response for request message UUID &1. | The short text describes the object sufficiently | ||
| 43 | Error in creating the network relationship. | The short text describes the object sufficiently | ||
| 44 | Error in changing the network relationship. | The short text describes the object sufficiently | ||
| 45 | Error in deleting the network relationship. | The short text describes the object sufficiently | ||
| 46 | Progress of WBS element &1 could be determined | The short text describes the object sufficiently | ||
| 47 | Enter Completion Percent below 100. | The short text describes the object sufficiently | ||
| 48 | Project Definition &1 could be changed successfully | The short text describes the object sufficiently | ||
| 49 | Project Definition &1 changed successfully. | The short text describes the object sufficiently | ||
| 50 | Progress of WBS element &1 could not be determined | The short text describes the object sufficiently | ||
| 51 | ISO code of system language could not be determined. | The short text describes the object sufficiently | ||
| 52 | Object number of project &1 could not be determined. | The short text describes the object sufficiently | ||
| 53 | Object number of wbs element &1 could not be determined. | The short text describes the object sufficiently | ||
| 54 | Object number of network &1 could not be determined. | The short text describes the object sufficiently | ||
| 55 | Object number of activity &1 &2 could not be determined. | The short text describes the object sufficiently | ||
| 56 | Object number of material component &1 could not be determined. | The short text describes the object sufficiently | ||
| 57 | Name for &1 &2 could not be determined. | The short text describes the object sufficiently | ||
| 58 | Field &1 is required. | The short text describes the object sufficiently | ||
| 59 | External unit of measurement &1 is not unique for language &2. | The short text describes the object sufficiently | ||
| 60 | Unit of measurement ISO code &1 is not supported. | The short text describes the object sufficiently | ||
| 61 | &1 conversion failed: No external code exists for internal code &2. | The short text describes the object sufficiently | ||
| 62 | Entry &1 in &2 does not exist in table &3. | The short text describes the object sufficiently | ||
| 63 | Value &1 in &2 is larger than &3. | The short text describes the object sufficiently | ||
| 64 | &1 has to be the same as &2. | The short text describes the object sufficiently | ||
| 65 | Individual measure units have to be the same as &1. | The short text describes the object sufficiently | ||
| 66 | Only customer and vendor are accepted in &1. | The short text describes the object sufficiently | ||
| 67 | Project &1 does not exist. | The short text describes the object sufficiently | ||
| 68 | &1 should be provided using unit &2. | The short text describes the object sufficiently | ||
| 69 | Creating the partner failed. | The short text describes the object sufficiently | ||
| 70 | There is a loop in the network hierarchy. | The short text describes the object sufficiently | ||
| 71 | &1 has to uniquely identify a WBS element. | The short text describes the object sufficiently | ||
| 72 | &1 has to uniquely identify a network. | The short text describes the object sufficiently | ||
| 73 | &1 has to uniquely identify an activity in a given network. | The short text describes the object sufficiently | ||
| 74 | Parent WBS element has to be the same for a network and its subnetworks. | The short text describes the object sufficiently | ||
| 75 | Parent WBS element has to be the same for an acty and its parent ntwk. | The short text describes the object sufficiently | ||
| 76 | Activity hierarchy can be at most one level deep. | The short text describes the object sufficiently | ||
| 77 | Parent WBS element has to be the same for an acty and its acty element. | The short text describes the object sufficiently | ||
| 78 | Parent network has to be the same for an acty and its acty element. | The short text describes the object sufficiently | ||
| 79 | &1 | The short text describes the object sufficiently | ||
| 80 | &1 has to be between &2 and &3. | The short text describes the object sufficiently | ||
| 81 | Project ID &1 may not be used. | The short text describes the object sufficiently | ||
| 82 | WBS element ID &1 may not be used. | The short text describes the object sufficiently | ||
| 83 | Acty elements cannot have ntwk relations or milestones. | The short text describes the object sufficiently | ||
| 84 | A network cannot be its own parent. | The short text describes the object sufficiently | ||
| 85 | The ID of an acty elmnt must be different from the ID of its parent acty. | The short text describes the object sufficiently | ||
| 86 | Insufficient authorization on milestone &1 | The short text describes the object sufficiently | ||
| 87 | For action &1 the mandatory fields &2 or &3 are missing. | The short text describes the object sufficiently | ||
| 88 | Insufficient authorization to create milestone | The short text describes the object sufficiently | ||
| 89 | System status &2 is active (WBS &1), Milestone cannot be &3 | The short text describes the object sufficiently | ||
| 90 | Progress of Activity &1 could be determined | The short text describes the object sufficiently | ||
| 91 | Progress of Activity &1 could not be determined | The short text describes the object sufficiently |
History
| Last changed on/by | 20100310 | SAP | |
| SAP Release Created in | 605 |