Message Number list used by SAP ABAP Class CL_PRS_PROJECTERPUPDRC_IMPL (ProjectERPUpdateRequestConfirmation_In)
SAP ABAP Class
CL_PRS_PROJECTERPUPDRC_IMPL (ProjectERPUpdateRequestConfirmation_In) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | PLM_SE_PRS_MESSAGES - 042 | Error in creating the network relationship. | ||
| 2 | PLM_SE_PRS_MESSAGES - 027 | No InternalID-TechnicalID correspondence found. | ||
| 3 | PLM_SE_PRS_MESSAGES - 028 | Material component already assigned to the activity. | ||
| 4 | PLM_SE_PRS_MESSAGES - 029 | Not assigned material component. | ||
| 5 | PLM_SE_PRS_MESSAGES - 030 | Relationship already exists. | ||
| 6 | PLM_SE_PRS_MESSAGES - 031 | Nonexistent relationship. | ||
| 7 | PLM_SE_PRS_MESSAGES - 032 | Enter either SuccessorNetworkID or SuccessorNetworkSenderTechnicalID. | ||
| 8 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 9 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 10 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 11 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 12 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 13 | PLM_SE_PRS_MESSAGES - 036 | The action on milestone &1 could not be performed. | ||
| 14 | PLM_SE_PRS_MESSAGES - 036 | The action on milestone &1 could not be performed. | ||
| 15 | PLM_SE_PRS_MESSAGES - 036 | The action on milestone &1 could not be performed. | ||
| 16 | PLM_SE_PRS_MESSAGES - 036 | The action on milestone &1 could not be performed. | ||
| 17 | PLM_SE_PRS_MESSAGES - 026 | Activity &1 does not exist. | ||
| 18 | PLM_SE_PRS_MESSAGES - 044 | Error in deleting the network relationship. | ||
| 19 | PLM_SE_PRS_MESSAGES - 046 | Enter Completion Percent below 100. | ||
| 20 | PLM_SE_PRS_MESSAGES - 046 | Enter Completion Percent below 100. | ||
| 21 | PLM_SE_PRS_MESSAGES - 048 | Project Definition &1 changed successfully. | ||
| 22 | PLM_SE_PRS_MESSAGES - 063 | &1 has to be the same as &2. | ||
| 23 | PLM_SE_PRS_MESSAGES - 066 | Project &1 does not exist. | ||
| 24 | PLM_SE_PRS_MESSAGES - 067 | &1 should be provided using unit &2. | ||
| 25 | PLM_SE_PRS_MESSAGES - 069 | There is a loop in the network hierarchy. | ||
| 26 | PLM_SE_PRS_MESSAGES - 081 | WBS element ID &1 may not be used. | ||
| 27 | PLM_SE_PRS_MESSAGES - 085 | Insufficient authorization on milestone &1 | ||
| 28 | PLM_SE_PRS_MESSAGES - 085 | Insufficient authorization on milestone &1 | ||
| 29 | PLM_SE_PRS_MESSAGES - 085 | Insufficient authorization on milestone &1 | ||
| 30 | PLM_SE_PRS_MESSAGES - 087 | Insufficient authorization to create milestone | ||
| 31 | PLM_SE_PRS_MESSAGES - 087 | Insufficient authorization to create milestone | ||
| 32 | PLM_SE_PRS_MESSAGES - 088 | System status &2 is active (WBS &1), Milestone cannot be &3 | ||
| 33 | PLM_SE_PRS_MESSAGES - 008 | The required network ID is missing. | ||
| 34 | PLM_SE_PRS_MESSAGES - 001 | No update possible, data has been changed since last read | ||
| 35 | PLM_SE_PRS_MESSAGES - 001 | No update possible, data has been changed since last read | ||
| 36 | PLM_SE_PRS_MESSAGES - 002 | Mandatory field &1 not provided. | ||
| 37 | PLM_SE_PRS_MESSAGES - 002 | Mandatory field &1 not provided. | ||
| 38 | PLM_SE_PRS_MESSAGES - 002 | Mandatory field &1 not provided. | ||
| 39 | PLM_SE_PRS_MESSAGES - 002 | Mandatory field &1 not provided. | ||
| 40 | PLM_SE_PRS_MESSAGES - 002 | Mandatory field &1 not provided. | ||
| 41 | PLM_SE_PRS_MESSAGES - 003 | Field &1 not found in table &2. | ||
| 42 | PLM_SE_PRS_MESSAGES - 004 | Value &1 not found in table &2. | ||
| 43 | PLM_SE_PRS_MESSAGES - 005 | &1 party ID is missing. | ||
| 44 | PLM_SE_PRS_MESSAGES - 005 | &1 party ID is missing. | ||
| 45 | PLM_SE_PRS_MESSAGES - 005 | &1 party ID is missing. | ||
| 46 | PLM_SE_PRS_MESSAGES - 005 | &1 party ID is missing. | ||
| 47 | PLM_SE_PRS_MESSAGES - 006 | The partner with ID &1 and role code &2 could not be read. | ||
| 48 | PLM_SE_PRS_MESSAGES - 007 | Invalid action code for party. | ||
| 49 | PLM_SE_PRS_MESSAGES - 000 | ChangeStateID could not be determined. | ||
| 50 | PLM_SE_PRS_MESSAGES - 009 | Provide only one ID as network parent! | ||
| 51 | PLM_SE_PRS_MESSAGES - 010 | Exactly one of ID or SenderTechnicalID has to be provided for activity &1 | ||
| 52 | PLM_SE_PRS_MESSAGES - 011 | The unit of measure for Free/Total Float Duration must be DAY! | ||
| 53 | PLM_SE_PRS_MESSAGES - 013 | Invalid domain value: &1 in &2. | ||
| 54 | PLM_SE_PRS_MESSAGES - 015 | The partner &1 already exists. | ||
| 55 | PLM_SE_PRS_MESSAGES - 016 | The partner &1 is not assigned to this project. | ||
| 56 | PLM_SE_PRS_MESSAGES - 017 | WBS &1 already exists. | ||
| 57 | PLM_SE_PRS_MESSAGES - 018 | WBS &1 does not exist. | ||
| 58 | PLM_SE_PRS_MESSAGES - 019 | Milestone &1 already exists. | ||
| 59 | PLM_SE_PRS_MESSAGES - 020 | Milestone &1 does not exist. | ||
| 60 | PLM_SE_PRS_MESSAGES - 021 | Network &1 already exists. | ||
| 61 | PLM_SE_PRS_MESSAGES - 022 | Network &1 does not exist. | ||
| 62 | PLM_SE_PRS_MESSAGES - 023 | Only Customer/Vendor code values are permitted for Product Recipient. | ||
| 63 | PLM_SE_PRS_MESSAGES - 025 | Activity &1 already exists. |