SAP ABAP Message Class /AIN/PUB_POBJ (Messages for BO Physical Object)
Basic Data
Hierarchy
☛
AIN (Software Component) AIN 710: Add-On Installation
⤷ AIE-AII (Application Component) Infrastructure
⤷ /AIN/PUBLIC_SERVICES (Package) Auto-ID Released Services
⤷ AIE-AII (Application Component) Infrastructure
⤷ /AIN/PUBLIC_SERVICES (Package) Auto-ID Released Services
Attributes
Message class | /AIN/PUB_POBJ | |
Short Description | Messages for BO Physical Object | |
Changed On | 20141109 | |
Last Changed At | 140335 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Physical object ID must be provided | The short text describes the object sufficiently | |
2 | 001 | Physical object internal ID must be provided | The short text describes the object sufficiently | |
3 | 002 | Location internal ID must be provided | The short text describes the object sufficiently | |
4 | 003 | Proper inventory status must be provided | The short text describes the object sufficiently | |
5 | 004 | Physical object does not exist | The short text describes the object sufficiently | |
6 | 005 | Physical object already existed | The short text describes the object sufficiently | |
7 | 006 | Physical object attribute '&1' is not registered within element set '&2' | The short text describes the object sufficiently | |
8 | 007 | Physical objects belong to different bundles | The short text describes the object sufficiently | |
9 | 008 | Update time and user must be provided | The short text describes the object sufficiently | |
10 | 009 | Enter correct parent and top physical object relation | The short text describes the object sufficiently | |
11 | 010 | Physical object has to be a standalone object | The short text describes the object sufficiently | |
12 | 011 | Enter correct object and inventory status | The short text describes the object sufficiently | |
13 | 012 | Parent-child relation of physical object must be provided | The short text describes the object sufficiently | |
14 | 013 | Physical objects must belong to same location | The short text describes the object sufficiently | |
15 | 014 | Only objects in stock can be added to physical object hierarchy | The short text describes the object sufficiently | |
16 | 015 | Physical object '&1&2' currently belongs to another object hierarchy | Space: object requires documentation | |
17 | 016 | Update time must be provided | The short text describes the object sufficiently | |
18 | 017 | Update user must be provided | The short text describes the object sufficiently | |
19 | 018 | Physical object currently does not belong to other object hierarchy | The short text describes the object sufficiently | |
20 | 019 | More than one ID is provided | The short text describes the object sufficiently | |
21 | 020 | Untagged physical object must be assigned to a tagged parent object | The short text describes the object sufficiently | |
22 | 021 | ID version shall be provided | The short text describes the object sufficiently | |
23 | 022 | Parent physical object must not be an untagged object | The short text describes the object sufficiently | |
24 | 023 | Untagged physical object can not be added to a bundle | The short text describes the object sufficiently | |
25 | 024 | Physical object IDs provided are duplicated | The short text describes the object sufficiently | |
26 | 025 | Physical object &1 currently is locked by another process | The short text describes the object sufficiently | |
27 | 026 | Both product internal ID and UoM must be provided | The short text describes the object sufficiently | |
28 | 027 | Physical object to be decommissioned must be a tagged object | The short text describes the object sufficiently | |
29 | 028 | Physical objects do not belong to a bundle | The short text describes the object sufficiently | |
30 | 029 | Physical object with ID '&1&2' is new | The short text describes the object sufficiently | |
31 | 030 | Physical object internal ID, ID, and its ID version must be provided | The short text describes the object sufficiently | |
32 | 031 | Physical object with ID '&1&2' (version: &3) already exists | The short text describes the object sufficiently | |
33 | 032 | ID '&1&2' (version: &3) is not a valid ID | The short text describes the object sufficiently | |
34 | 033 | Physical object ID components must be provided | The short text describes the object sufficiently | |
35 | 034 | Physical object with ID '&1&2' does not yet exist | The short text describes the object sufficiently | |
36 | 035 | Physical object category determination parameters shall be provided | The short text describes the object sufficiently | |
37 | 036 | Physical object ID and ID version must be provided | The short text describes the object sufficiently | |
38 | 037 | Physical object ID '&1&2' does not exist | The short text describes the object sufficiently | |
39 | 038 | Physical object with an ID can only have a quantity with the value ONE | The short text describes the object sufficiently | |
40 | 039 | Physical object is already a top object | The short text describes the object sufficiently | |
41 | 040 | Physical object with internal ID '&1' does not exist | The short text describes the object sufficiently | |
42 | 041 | A partial hierarchy can not be moved | The short text describes the object sufficiently | |
43 | 042 | Physical object ID can not be created without an object header | The short text describes the object sufficiently | |
44 | 043 | Other attributes can not be created without an object header | The short text describes the object sufficiently | |
45 | 044 | A tag can not be decommissioned more than once | The short text describes the object sufficiently | |
46 | 045 | The top object has to be provided for setting status to out of stock | The short text describes the object sufficiently | |
47 | 046 | No authorization to display Object (Auth obj &1, ACT &2) | The short text describes the object sufficiently | |
48 | 047 | No authorization to create/change Object (Auth obj &1, ACT &2) | The short text describes the object sufficiently | |
49 | 048 | No authorization to delete Object (Auth obj &1, ACT &2) | The short text describes the object sufficiently | |
50 | 049 | Physical object with ID '&1&2' is decommissioned | The short text describes the object sufficiently | |
51 | 050 | Physical object '&1&2' cannot be added to own sub hierarchy (pack cycle) | The short text describes the object sufficiently | |
52 | 051 | Physical object with status '&1' cannot be set 'in stock' | The short text describes the object sufficiently |
History
Last changed on/by | 20141109 | SAP | |
SAP Release Created in | 400 |