SAP ABAP Message Class /AIN/IF (/AIN/IF)
Basic Data
Hierarchy
☛
AIN (Software Component) AIN 710: Add-On Installation
⤷ AIE-AII (Application Component) Infrastructure
⤷ /AIN/IF (Package) Auto-ID Interfaces
⤷ AIE-AII (Application Component) Infrastructure
⤷ /AIN/IF (Package) Auto-ID Interfaces
Attributes
Message class | /AIN/IF | |
Short Description | ||
Changed On | 20141109 | |
Last Changed At | 140722 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 002 | Error in deleting document assignment | The short text describes the object sufficiently | |
3 | 003 | System Error - Message stored in tRFC queue, TID &1. See Application Log. | Space: object requires documentation | |
4 | 004 | Message mapping type is not defined. Define the mapping type in the IMG. | Space: object requires documentation | |
5 | 005 | Processing finished at &1 (&2) | The short text describes the object sufficiently | |
6 | 006 | Message accepted and queued for processing | The short text describes the object sufficiently | |
7 | 007 | &1 message picked from queue | The short text describes the object sufficiently | |
8 | 008 | Message cannot be serialized, due to mapping error, stored in tRFC queue. | The short text describes the object sufficiently | |
9 | 009 | Received HTTP packet has no payload or does not have expected payload | Space: object requires documentation | |
10 | 010 | XI communication failed; error: &1 | The short text describes the object sufficiently | |
11 | 011 | System Error - Message stored in qRFC, Queue Name &1. | The short text describes the object sufficiently | |
12 | 012 | HTTP listener sent response with response code: &1(&2) | The short text describes the object sufficiently | |
13 | 013 | Creating HTTP client object failed; destination not found | Space: object requires documentation | |
14 | 014 | Creating HTTP client object failed: no authorization to use HTTP dest. | The short text describes the object sufficiently | |
15 | 015 | Creating HTTP client object failed:HTTP/HTTPS communication not available | The short text describes the object sufficiently | |
16 | 016 | Creating HTTP client object failed | The short text describes the object sufficiently | |
17 | 017 | Failed by message code page conversion; error: &1 | The short text describes the object sufficiently | |
18 | 018 | Failed during HTTP communication; error: &1 | The short text describes the object sufficiently | |
19 | 020 | HTTP listener got response with response code: &1(&2) | The short text describes the object sufficiently | |
20 | 021 | Location not found for device &1 | The short text describes the object sufficiently | |
21 | 022 | Message command &1 not supported by mapping | The short text describes the object sufficiently | |
22 | 023 | Device &1 not found. | The short text describes the object sufficiently | |
23 | 024 | Message mapping failed | The short text describes the object sufficiently | |
24 | 025 | Location not found for device group &1 | The short text describes the object sufficiently | |
25 | 026 | Message was mapped into &1 internal message(s) | The short text describes the object sufficiently | |
26 | 027 | Call rule processor with internal message number &1 for location &2 | Space: object requires documentation | |
27 | 028 | Rule processor finished with return code: &1 | The short text describes the object sufficiently | |
28 | 029 | RFC destination & not found. | The short text describes the object sufficiently | |
29 | 030 | Rule processor finished with return code REPROCESS - execute again later | The short text describes the object sufficiently | |
30 | 031 | HTTP message correctly received: &1 | The short text describes the object sufficiently | |
31 | 032 | TCP/IP comm. to destination &1 failed. Received error message &2 | Space: object requires documentation | |
32 | 033 | CCMS update failed in NotifyError from source &1 | The short text describes the object sufficiently | |
33 | 034 | CCMS update succeeded in NotifyError from source &1 | The short text describes the object sufficiently | |
34 | 035 | Number range request successfully completed | The short text describes the object sufficiently | |
35 | 036 | Notify Extension successfully received | The short text describes the object sufficiently | |
36 | 037 | Status Ping successfully received | The short text describes the object sufficiently | |
37 | 038 | Status Ping successfully sent to DC: &1 - Return status is: &2 | The short text describes the object sufficiently | |
38 | 039 | Status Ping report failed for DC: &1 - Cause: &2 | Space: object requires documentation | |
39 | 040 | BatchIssueTag command successfully sent | The short text describes the object sufficiently | |
40 | 041 | BatchIssueTag command could not be sent: &1 | The short text describes the object sufficiently | |
41 | 042 | WriteData command successfully sent | The short text describes the object sufficiently | |
42 | 043 | WriteData command could not be sent: &1 | The short text describes the object sufficiently | |
43 | 044 | Extension command successfully sent | The short text describes the object sufficiently | |
44 | 045 | Extension command could not be sent: &1 | The short text describes the object sufficiently | |
45 | 046 | Status Ping command could not be sent: &1 | The short text describes the object sufficiently | |
46 | 047 | Registration failed: &1 | The short text describes the object sufficiently | |
47 | 048 | Registration failed for device: &1 - See log for details | The short text describes the object sufficiently | |
48 | 049 | Registration succeeded for device controller: &1 | The short text describes the object sufficiently | |
49 | 050 | Registration failed for subscription: &1 - See log for details | The short text describes the object sufficiently | |
50 | 051 | Registration succeeded for subscription: &1 | The short text describes the object sufficiently | |
51 | 052 | Deregistration failed for subscription: &1 - See log for details | The short text describes the object sufficiently | |
52 | 053 | Deregistration succeeded for subscription: &1 | The short text describes the object sufficiently | |
53 | 054 | Deregistration failed, but registration succeeded for subscription &1 | The short text describes the object sufficiently | |
54 | 055 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
55 | 056 | Logical port not found for proxy class &1 | The short text describes the object sufficiently | |
56 | 057 | Deregistration failed: &1 | The short text describes the object sufficiently | |
57 | 058 | Deregistration failed, subs. &1 not on ALE server - See log for details | The short text describes the object sufficiently | |
58 | 060 | Insufficient input data provided | The short text describes the object sufficiently | |
59 | 061 | An open SQL exception occurred | The short text describes the object sufficiently | |
60 | 062 | Database record already exists | The short text describes the object sufficiently | |
61 | 063 | Database update failed | The short text describes the object sufficiently | |
62 | 064 | Unknown error occurred | The short text describes the object sufficiently | |
63 | 065 | No test messages found in the database | The short text describes the object sufficiently | |
64 | 067 | No device found for device group ID &1 | The short text describes the object sufficiently | |
65 | 068 | Device group &1 not found | The short text describes the object sufficiently | |
66 | 069 | Observation time &1 could not be converted | The short text describes the object sufficiently | |
67 | 070 | Registering subscription: &1 | The short text describes the object sufficiently | |
68 | 071 | Unregistering subscription: &1 | The short text describes the object sufficiently | |
69 | 072 | Parameter name: &1 - Parameter value: &2 | The short text describes the object sufficiently | |
70 | 080 | Duplicate ECSpec name exception: &1 | The short text describes the object sufficiently | |
71 | 081 | ECSpec validation exception | The short text describes the object sufficiently | |
72 | 082 | No such name exception: &1 | The short text describes the object sufficiently | |
73 | 083 | Invalid URI exception: &1 | The short text describes the object sufficiently | |
74 | 084 | Duplicate subscription exception: &1 | The short text describes the object sufficiently | |
75 | 085 | Security exception | The short text describes the object sufficiently | |
76 | 086 | Implementation exception | The short text describes the object sufficiently | |
77 | 087 | No such subscriber exception: &1 | The short text describes the object sufficiently | |
78 | 088 | Subscribe events exception: &1 | The short text describes the object sufficiently | |
79 | 089 | Both device group and document must be specified for UI message storage | The short text describes the object sufficiently | |
80 | 090 | An open SQL error occured while saving UI messages | The short text describes the object sufficiently | |
81 | 091 | Error in adding external observation links | The short text describes the object sufficiently | |
82 | 092 | There are no internal observations (action) created | The short text describes the object sufficiently | |
83 | 093 | Parent location not found for location &1 | The short text describes the object sufficiently | |
84 | 100 | Internal error during message mapping (CONVERT_TO_INTMSG) &1 &2 &3 | The short text describes the object sufficiently | |
85 | 600 | --------Error messages for number range distribution AII<->AII---------- | The short text describes the object sufficiently | |
86 | 601 | Error during creation of a number range request on local instance | Space: object requires documentation | |
87 | 602 | Own logical system could not be determined | The short text describes the object sufficiently | |
88 | 603 | Number range request for &1 &2 was confirmed completely | The short text describes the object sufficiently | |
89 | 604 | Number range request for &1 &2 was confirmed partially | The short text describes the object sufficiently | |
90 | 605 | Number range request for &1 &2 was rejected | The short text describes the object sufficiently | |
91 | 606 | Error during processing of a number range request on central instance | Space: object requires documentation | |
92 | 607 | Error during processing of a number range response on local instance | Space: object requires documentation | |
93 | 608 | Number range request was sent for &1 &2 (size: &3) | The short text describes the object sufficiently | |
94 | 609 | Number range response was sent for &1 &2, number from &3, number to &4 | The short text describes the object sufficiently | |
95 | 610 | Error while trying to send a number range response on central instance | Space: object requires documentation | |
96 | 611 | Number range interval created (&1 &2) | The short text describes the object sufficiently | |
97 | 612 | Number range interval updated (&1 &2) | The short text describes the object sufficiently | |
98 | 613 | Response received for an interval which does not yet exist | The short text describes the object sufficiently | |
99 | 614 | No overal interval defined on central instance for &1 &2 | The short text describes the object sufficiently | |
100 | 615 | Size of numbers requested for &1 is greater than 9999999999 | The short text describes the object sufficiently | |
101 | 616 | Number range request for &1 &2 was rejected | The short text describes the object sufficiently |
History
Last changed on/by | 20141109 | SAP | |
SAP Release Created in | 200 |