ADS2KIPUPL_API_AL - Message Class for SPEC 2000 IP Upload API
The following messages are stored in message class ADS2KIPUPL_API_AL: Message Class for SPEC 2000 IP Upload API.
It is part of development package ADS2KIPUPL_API_AL in software component IS-AD-SPC. This development package consists of objects that can be grouped under "SPEC2000 Initial Provisioning Upload: API Layer".
It is part of development package ADS2KIPUPL_API_AL in software component IS-AD-SPC. This development package consists of objects that can be grouped under "SPEC2000 Initial Provisioning Upload: API Layer".
Message Nr ▲ | Message Text |
|---|---|
| 000 | *******<Messages for API Development>******* |
| 001 | Transmission Sequence Number &1 not next in sequence |
| 002 | Transmission File rejected - Sequence Number is blank |
| 003 | Serial Number exceeded permitted range - &1 |
| 004 | Transmission File rejected - RTC value is not &1 for file type &2 |
| 005 | Transmission File rejected as technical checks failed |
| 006 | Transmission Sequence Number &1 should be greater than &2 present in DB |
| 007 | Messages raised out of Customer Extensions. File Rejected |
| 071 | All Price Break: Quantity and Amount are rejected |
| 072 | All Other Charges: Code and Amount are rejected |
| 074 | All Used On Assemblies (UOA) are rejected |
| 075 | Inconsistency encountered for Replacing/Replaced Part type: Part type &1 |
| 076 | All the Replacing/Replaced Parts are rejected |
| 078 | Duplicate Suppliers found for a particular Spare Part &1 |
| 090 | When &1 is given, &2 should not be blank |
| 091 | Status Object creation failed |
| 092 | Status of the part does not allow it to be deleted |
| 093 | Status of the part does not allow it to be revised |
| 094 | End Item Parts cannot have effectivities |
| 095 | Part rejected - Sequence Number is blank |
| 096 | Part marked for revision is rejected as it was already deleted |
| 097 | Part marked for deletion is rejected as it was already deleted |
| 098 | IS_SPCIPPDR-UPDATEFLAG is invalid (API Call: API_S2K_IP_PART_UPDATE) |
| 099 | Part marked as new is a deleted part in DB. Existing part is revised |
| 100 | Part marked as new is rejected as it already exists in DB |
| 101 | Part marked for deletion is rejected as it does not exist in DB |
| 102 | Part marked for revision does not exist in DB. It is treated as new part |
| 103 | Part marked for revision is rejected as it does not exist in DB |
| 104 | All Suppliers are rejected |
| 105 | All Locations are rejected |
| 106 | All APN/MCP/OPTs are rejected |
| 107 | T_SPCIPPARTS: PARTTYP is invalid. Values (&1 &2:&3) |
| 108 | APN &2:&1 repeated in transmission - Element rejected |
| 109 | MCP &2:&1 repeated in transmission - Element rejected |
| 110 | OPT &2:&1 repeated in transmission - Element rejected |
| 111 | Single APN &2:&1 cannot be revised - Element rejected |
| 112 | Single MCP &2:&1 cannot be revised - Element rejected |
| 113 | Single OPT &2:&1 cannot be revised - Element rejected |
| 114 | UPDATEFLAG ignored for APN &2:&1 as 'Revision as set' is opted. |
| 115 | UPDATEFLAG ignored for MCP &2:&1 as 'Revision as set' is opted. |
| 116 | UPDATEFLAG ignored for OPT &2:&1 as 'Revision as set' is opted. |
| 117 | APN &2:&1 already exists in DB, but marked as new in transmission |
| 118 | MCP &2:&1 already exists in DB, but marked as new in transmission |
| 119 | OPT &2:&1 already exists in DB, but marked as new in transmission |
| 120 | APN &2:&1 does not exist in DB, but marked for deletion in transmission |
| 121 | MCP &2:&1 does not exist in DB, but marked for deletion in transmission |
| 122 | OPT &2:&1 does not exist in DB, but marked for deletion in transmission |
| 123 | Part Rejected as technical check failed for keys |
| 124 | Invalid UPDATEFLAG for APN &1 - &3:&2 |
| 125 | Invalid UPDATEFLAG for MCP &1 - &3:&2 |
| 126 | Invalid UPDATEFLAG for OPT &1 - &3:&2 |
| 127 | APN &2:&1 marked for deletion is rejected as it was already deleted |
| 128 | MCP &2:&1 marked for deletion is rejected as it was already deleted |
| 129 | OPT &2:&1 marked for deletion is rejected as it was already deleted |
| 130 | T_SPCIPSPLX: Entry missing for supplier &1 |
| 131 | Supplier record is repeated in transmission - Record rejected |
| 132 | Supplier record is rejected as technical check failed for SPL |
| 133 | Supplier record marked as new is rejected as it already exists in DB |
| 134 | Supplier record marked for deletion is rejected as it doesn't exist in DB |
| 135 | Supplier record marked for revision does not exist in DB. Treated as new |
| 136 | Supplier record marked for revision is rejected as it doesn't exist in DB |
| 137 | T_SPCIPOSDS: ODCDSTTP is invalid. Values (&1/&2) |
| 138 | All Optional Suppliers/Distributors are rejected |
| 139 | OSC &1 repeated in input - rejected |
| 140 | DST &1 repeated in input - rejected |
| 141 | Single OSC &1 cannot be revised |
| 142 | Single DST &1 cannot be revised |
| 143 | UPDATEFLAG ignored for OSC &1 as 'Revision as set' is opted |
| 144 | UPDATEFLAG ignored for DST &1 as 'Revision as set' is opted |
| 145 | OSC &1 already exists in DB, but marked as new in transmission |
| 146 | DST &1 already exists in DB, but marked as new in transmission |
| 147 | OSC &1 does not exist in DB, but marked for deletion in transmission |
| 148 | DST &1 does not exist in DB, but marked for deletion in transmission |
| 149 | Invalid UPDATEFLAG for OSC (&1 - &2) |
| 150 | Invalid UPDATEFLAG for DST (&1 - &2) |
| 151 | Supplier record marked for revision is rejected as it was already deleted |
| 152 | Supplier record marked for deletion is rejected as it was already deleted |
| 153 | T_SPCIPSPL-UPDATEFLAG is invalid (API Call: API_S2K_IP_PART_UPDATE) |
| 154 | Supplier record marked as new was already deleted in DB. Being revised. |
| 155 | OSC &1 marked for deletion is rejected as it was already deleted |
| 156 | DST &1 marked for deletion is rejected as it was already deleted |
| 157 | All Other Charge Codes(OCH) are rejected |
| 158 | PBQ &1 repeated in input - rejected |
| 159 | Single PBQ &1 cannot be revised |
| 160 | UPDATEFLAG ignored for PBQ &1 as 'Revision as set' is opted |
| 161 | PBQ &1 already exists in DB, but marked as new in transmission |
| 162 | PBQ &1 does not exist in DB, but marked for deletion in transmission |
| 163 | Invalid UPDATEFLAG for PBQ (&1 - &2) |
| 164 | PBQ &1 marked for deletion is rejected as it was already deleted |
| 165 | PQA &1 does not exist in DB, but marked for revision in transmission |
| 166 | Status of the supplier does not allow it to be deleted |
| 167 | Status of the supplier does not allow it to be revised |
| 170 | T_SPCIPCSNX: Entry missing for location &1 |
| 171 | Location record is repeated in transmission - Record rejected |
| 172 | Location record is rejected as tech check failed for CSN |
| 173 | Location record marked as new is rejected as it already exists in DB |
| 174 | Location record marked for deletion is rejected as it doesn't exist in DB |
| 175 | Location record marked for revision does not exist in DB. Treated as new |
| 176 | Location record marked for revision is rejected as it doesn't exist in DB |
| 177 | All the Effectivity Range Codes are rejected |
| 178 | Effectivity Range Code (EFF) &1 repeated in input - rejected |
| 179 | Single Effectivity Range Code (EFF) &1 cannot be revised |
| 180 | UPDATEFLAG ignored for EFF &1 as revision as set is opted |
| 181 | EFF &1 already exists in DB, but marked as new in transmission |
| 182 | EFF &1 does not exist in DB, but marked for deletion in transmission |
| 183 | Invalid UPDATEFLAG for EFF (&1 - &2) |
| 184 | All the Used On Assemblies (UOA) are rejected |
| 185 | Used On Assembly (UOA) &2:&1 repeated in input - rejected |
| 186 | Single Used On Assembly (UOA) &2:&1 cannot be revised |
| 187 | UPDATEFLAG ignored for UOA &2:&1 as 'Revision as set' is opted |
| 188 | UOA &2:&1 already exists in DB, but marked as new in transmission |
| 189 | UOA &2:&1 does not exist in DB, but marked for deletion in transmission |
| 190 | Invalid UPDATEFLAG for UOA (&1 - &3:&2) |
| 191 | Location record marked for revision is rejected as it was already deleted |
| 192 | Location record marked for deletion is rejected as it was already deleted |
| 193 | T_SPCIPCSN-UPDATEFLAG is invalid (API Call: API_S2K_IP_PART_UPDATE) |
| 194 | Location record marked as new was already deleted in DB. Being revised. |
| 195 | EFF &1 marked for deletion is rejected as it was already deleted |
| 196 | UOA &2:&1 marked for deletion is rejected as it was already deleted |
| 197 | Overlapping Price Break Range; All Price Break Quantities rejected |
| 198 | PQA_END &1 greater than PQA &2; All Price Break Quantities rejected |
| 199 | All Price Break Quantities are rejected |
| 200 | Status of the location does not allow it to be deleted |
| 201 | Status of the location does not allow it to be revised |
| 205 | OCH &1 repeated in input - rejected |
| 206 | Single OCH &1 cannot be revised |
| 207 | UPDATEFLAG ignored for OCH &1 as 'Revision as set' is opted |
| 208 | OCH &1 already exists in DB, but marked as new in transmission |
| 209 | OCH &1 does not exist in DB, but marked for deletion in transmission |
| 210 | Invalid updateflag for OCH (&1 - &2) |
| 211 | OCH &1 marked for deletion is rejected as it was already deleted |
| 212 | OCH &1 does not exist in DB, but marked for revision in transmission |
| 213 | All Other Charge Codes (OCH) are rejected |
| 216 | All Replacing (RPD) / Replaced (RPE) Parts are rejected |
| 217 | Replacing Part (RPD) &2:&1 repeated in input - Element rejected |
| 218 | Replaced Part (RPE) &2:&1 repeated in input - Element rejected |
| 219 | Single Replacing Part (RPD) &2:&1 cannot be revised - Element rejected |
| 220 | Single Replaced Part (RPE) &2:&1 cannot be revised - Element rejected |
| 221 | UPDATEFLAG ignored for RPD &2:&1 as 'revision as set' is opted |
| 222 | UPDATEFLAG ignored for RPE &2:&1 as 'revision as set' is opted |
| 223 | RPD &2:&1 already exists in DB, but marked as new in transmission |
| 224 | RPE &2:&1 already exists in DB, but marked as new in transmission |
| 225 | RPD &2:&1 does not exist in DB, but marked for deletion in transmission |
| 226 | RPE &2:&1 does not exist in DB, but marked for deletion in transmission |
| 227 | Invalid UPDATEFLAG for RPD &1 - &3:&2 |
| 228 | Invalid UPDATEFLAG for RPE &1 - &3:&2 |
| 229 | RPD &2:&1 marked for deletion is rejected as it was already deleted |
| 230 | RPE &2:&1 marked for deletion is rejected as it was already deleted |
| 300 | ******************Messages for Database Update*************************** |
| 301 | Insert failed for table &1 |
| 302 | Update failed for table &1 |