/STTPEC/INT_MSG - Messages for Integration
The following messages are stored in message class /STTPEC/INT_MSG: Messages for Integration.
It is part of development package /STTPEC/INT in software component LO-GEN-ATT. This development package consists of objects that can be grouped under "Advanced Track & Trace: Integration".
It is part of development package /STTPEC/INT in software component LO-GEN-ATT. This development package consists of objects that can be grouped under "Advanced Track & Trace: Integration".
Message Nr ▲ | Message Text |
|---|---|
| 000 | === DO NOT USE === |
| 001 | An error occured. Please check application log |
| 002 | An unknown error occured. Please contact SAP support |
| 003 | A technical error occured. Please contact your basis team |
| 004 | BAdI /STTPEC/MM_SELECTION is triggered |
| 005 | Sequential Processing |
| 006 | Processing package #&1 |
| 007 | BAdI /STTPEC/MM_BEFORE_SEND is triggered |
| 008 | No workload to send |
| 009 | Parallel Processing |
| 010 | Package &1 processed: Duration &2 (s) |
| 011 | Integration Process Started on &1 at &2 |
| 012 | Integration Process Ended on &1 at &2 |
| 013 | Error during initializing server Group &1 |
| 014 | No Destination Data found |
| 015 | RFC Resource Failure |
| 016 | <=============== Package Runtimes =================> |
| 017 | No free sessions available for parallel process |
| 018 | Maximum number of attempts has been reached. Timeout expired |
| 019 | Communication failure: Integration not possible. |
| 020 | Can not initializing server Group &1. Sequential process will be used. |
| 021 | Material Integration Result Log |
| 023 | Current function module is obsolete. Use the following: &1 |
| 024 | Interface of function module &1 is not available |
| 025 | Dynamic Interface Mapping for SAP ATTP functions |
| 026 | RFC Interface Mismatch. Check notes. |
| 099 | Processing for &1: &2 seconds |
| 101 | Enter valid number of tasks |
| 102 | Enter valid server group |
| 103 | Server group &1 is invalid |
| 104 | Server group initialization failed (&1) |
| 105 | Enter valid package size |
| 106 | Enter valid maximum retry attempts |
| 107 | Enter valid waiting time between retries |
| 108 | Enter valid server group |
| 109 | Enter valid document type |
| 110 | Business Document type &1 integration |
| 200 | =============BP Integration messages=============== |
| 201 | &1 Business Partners were sent to SAP ATTP system &2 |
| 202 | Allowed account groups have not been found |
| 203 | Account group &1 has been already assigned to business partner type &2 &3 |
| 204 | No BP Found |
| 205 | SAP ATTP BP Type Configuration is not maintained |
| 206 | Allowed Vendor Account Groups are not maintained |
| 207 | No BP for Integration found |
| 208 | No Address data available for BP&1 |
| 209 | Assigned Business partners were not fully provided |
| 210 | GLN for Vendor &1 is not maintained |
| 211 | GLN for Customer &1 is not maintained |
| 212 | GLN not found |
| 213 | Accout Group cannot be empty |
| 214 | Customer &1 filtered out from integration as it has no GLN assigned |
| 215 | Vendor &1 filtered out from integration as it has no GLN assigned |
| 216 | &1 BPs filtered out from integration as they have no GLN assigned |
| 300 | ============Location Integration messages========== |
| 301 | No BP assignment found for Plant &1 Storage location &2 |
| 302 | GLN Data cannot be determined: Unable to find assigned BP |
| 303 | Plant value is empty |
| 304 | Vendor data not found. Check Account Group Assignment. |
| 305 | Customer data not found. Check Account Group Assignment. |
| 306 | No Plants for Integration found |
| 307 | No Storage locations for Integration found |
| 308 | &1 Plants were sent to repository instance system &2 |
| 309 | &1 Storage locations were sent to repository instance system &2 |
| 310 | Address data for Storage Locations not found |
| 311 | Storage Loc &1 was filtered out due to the errors during Plant Int. |
| 312 | Storage location integration is excluded. |
| 313 | Plant &1 filtered out from integration as it has no GLN assigned |
| 314 | &1 Plants filtered out from integration as they have no GLN assigned |
| 315 | &1 Storage loc. filtered out as their plants have no GLN assigned |
| 316 | Storage Loc &1 filtered out as its plant has no GLN assigned |
| 317 | GLN for location not found |
| 400 | ============Product Integration messages========== |
| 401 | No relevant alternative UoMs found |
| 402 | No relevant storage location data for material found |
| 403 | No relevant plant data for material found |
| 404 | Error during selection of text descriptions for material |
| 405 | No materials to be updated after integration to SAP ATTP |
| 406 | No materials UoM to be updated after integration to SAP ATTP |
| 407 | Error occured during MARM update |
| 408 | Material &1 will be integrated in Package &2 |
| 409 | &1 materials to be integrated to repository instance. |
| 410 | Serialization type cannot be "Not serialized" |
| 411 | &1 Materials were sent to repository instance system &2 |
| 412 | No materials were found. |
| 413 | Serialization date valid only from tomorrow. |
| 414 | Customer-relevant fields for product integration not found |
| 415 | Date "Valid from" already effective and cannot be changed |
| 416 | No relevant additional country/reg. assignment for alternative UoMs found |
| 417 | You are not authorized to maintain material &1 |
| 418 | Material &1 is currently locked by user &2 |
| 419 | Material number &1 cannot be converted |
| 420 | No additional attributes for products found |
| 421 | Profile Relevant Country &1 is invalid |
| 450 | === Material Integration Messages (CIF ONLY) ==== |
| 451 | Synchronizing EAN11 with GTIN for Track and Trace in EWM |
| 500 | =============Batch Integration messages=========== |
| 501 | Batch Characteristic &1 is invalid |
| 502 | Batch Field &1 is invalid |
| 503 | Invalid Field Type |
| 504 | Invalid Batch Field |
| 505 | Invalid Batch Characteristic |
| 506 | Data not found for batch integration |
| 507 | Read point is empty in batch itegration message |
| 508 | Business step is empty in batch integration message |
| 509 | Objectlist and Quantitylist are empty in batch integration message |
| 600 | === NEW INTEGRATION LOGIC TRN === |
| 605 | Update Processing for &1 ... |
| 610 | Checking for relevance ... |
| 611 | Document type '&1' is not relevant for integration. |
| 612 | Batch '&1' is not serialized. |
| 613 | Material &1 UOM &2 is not serialized. |
| 614 | Material &1 is not integrated. |
| 615 | Order Item &1 is not relevant based on ser. settings. |
| 616 | Order &1 is not relevant based on settings. |
| 617 | Order &1 is not relevant based on status. |
| 618 | New values for document &1 are not relevant. Method 'delete' was set up. |
| 619 | Item &1 of Document &2 was excluded from integration |
| 620 | Transforming data... |
| 621 | Processing document &1 ... |
| 622 | Document header cannot be encoded due to missing attributes |
| 623 | Document &2 was excluded from integration |
| 624 | ERP Document Types relevant for integration not found |
| 898 | &1&2&3&4 |
| 899 | &1 &2 &3 &4 |