Message Number list used by SAP ABAP Class CL_PRS_PROJECTERPCRTRC1_IMPL (ProjectERPCreateRequestConfirmation_In_V1)
SAP ABAP Class
CL_PRS_PROJECTERPCRTRC1_IMPL (ProjectERPCreateRequestConfirmation_In_V1) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | PLM_SE_PRS_MESSAGES - 070 | &1 has to uniquely identify a WBS element. | ||
| 2 | PLM_SE_PRS_MESSAGES - 087 | Insufficient authorization to create milestone | ||
| 3 | PLM_SE_PRS_MESSAGES - 084 | The ID of an acty elmnt must be different from the ID of its parent acty. | ||
| 4 | PLM_SE_PRS_MESSAGES - 083 | A network cannot be its own parent. | ||
| 5 | PLM_SE_PRS_MESSAGES - 082 | Acty elements cannot have ntwk relations or milestones. | ||
| 6 | PLM_SE_PRS_MESSAGES - 081 | WBS element ID &1 may not be used. | ||
| 7 | PLM_SE_PRS_MESSAGES - 081 | WBS element ID &1 may not be used. | ||
| 8 | PLM_SE_PRS_MESSAGES - 080 | Project ID &1 may not be used. | ||
| 9 | PLM_SE_PRS_MESSAGES - 079 | &1 has to be between &2 and &3. | ||
| 10 | PLM_SE_PRS_MESSAGES - 079 | &1 has to be between &2 and &3. | ||
| 11 | PLM_SE_PRS_MESSAGES - 076 | Parent WBS element has to be the same for an acty and its acty element. | ||
| 12 | PLM_SE_PRS_MESSAGES - 075 | Activity hierarchy can be at most one level deep. | ||
| 13 | PLM_SE_PRS_MESSAGES - 074 | Parent WBS element has to be the same for an acty and its parent ntwk. | ||
| 14 | PLM_SE_PRS_MESSAGES - 073 | Parent WBS element has to be the same for a network and its subnetworks. | ||
| 15 | PLM_SE_PRS_MESSAGES - 072 | &1 has to uniquely identify an activity in a given network. | ||
| 16 | PLM_SE_PRS_MESSAGES - 071 | &1 has to uniquely identify a network. | ||
| 17 | PLM_SE_PRS_MESSAGES - 003 | Field &1 not found in table &2. | ||
| 18 | PLM_SE_PRS_MESSAGES - 069 | There is a loop in the network hierarchy. | ||
| 19 | PLM_SE_PRS_MESSAGES - 068 | Creating the partner failed. | ||
| 20 | PLM_SE_PRS_MESSAGES - 067 | &1 should be provided using unit &2. | ||
| 21 | PLM_SE_PRS_MESSAGES - 063 | &1 has to be the same as &2. | ||
| 22 | PLM_SE_PRS_MESSAGES - 061 | Entry &1 in &2 does not exist in table &3. | ||
| 23 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 24 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 25 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 26 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 27 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 28 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 29 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 30 | PLM_SE_PRS_MESSAGES - 033 | Invalid value &1 for &2. | ||
| 31 | PLM_SE_PRS_MESSAGES - 012 | The content of &1 exceeds the field length of the target field. |