SURDP_PLM - Messages for PLM to RDP data replication
The following messages are stored in message class SURDP_PLM: Messages for PLM to RDP data replication.
It is part of development package INTEGRATION_SUS_RDP_PLM_RPLCTN in software component SUS-RDP-INT. This development package consists of objects that can be grouped under "Replication of PLM Specification Data".
It is part of development package INTEGRATION_SUS_RDP_PLM_RPLCTN in software component SUS-RDP-INT. This development package consists of objects that can be grouped under "Replication of PLM Specification Data".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No filter criteria are defined for the selection. Do you want to proceed? |
| 001 | Execution completed with "&1" |
| 002 | Missing BAdI implementation BADI_SURDP_UPH_CUSTOM |
| 003 | Enter at least one valid "Specification Type" |
| 004 | Enter at least one valid "Specification" |
| 006 | The group entity does not exist. Choose valid group entry for "Hit List" |
| 007 | Enter a group entry for "Hit List" |
| 008 | Enter "Specification Valid From Date" |
| 009 | You do not have authorization to execute transaction &1 |
| 010 | Data package &1 of &2 processed |
| 014 | Report for data transfer for &3 load started on &1 at &2 |
| 015 | Report for data transfer for &3 load started in test mode on &1 at &2 |
| 016 | Report for data transfer for &3 load completed on &1 at &2 |
| 017 | Report for data transfer for &3 load completed in test mode on &1 at &2 |
| 018 | Delta load is only possible if an initial load was successfully completed |
| 019 | &1 specifications selected for processing |
| 020 | Transfer to API failed; response code: &1 (&2) |
| 021 | Failed to create API client &1 |
| 022 | Failed to create OAuth client &1 |
| 023 | OAuth client in RFC destination &1 is not configured |
| 024 | Error: &1&2&3&4 |
| 025 | Error detail: &1&2&3&4 |
| 026 | &1 entities (&2) transferred |
| 027 | Enter "Source ID" |
| 028 | &1 entities (&3) extracted out of &2 specifications |
| 029 | Enter "Recipe Valid From Date" |
| 030 | Enter at least one valid "Recipe Type" |
| 031 | Enter at least one valid "Recipe ID" |
| 032 | Enter "RFC Destination" |
| 033 | Enter at least one valid "Recipe Status" |
| 034 | &1 recipes selected for processing |
| 035 | &1 entities (&3) extracted out of &2 recipes |