SAP ABAP Message Class BORVII (Automotive Messages VII)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
LO-SPM-INB (Application Component) Goods Receipt Process
⤷
LE_BOR (Package) Goods Receipt Processing for Inbound Delivery
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-SPM-INB (Application Component) Goods Receipt Process⤷
LE_BOR (Package) Goods Receipt Processing for Inbound Delivery 
Attributes
| Message class |  |
BORVII |
| Short Description |  |
Automotive Messages VII |
| Changed On |  |
20041209 |
| Last Changed At |  |
143915 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
& & & & | Space: object requires documentation | |
| 2 | 001 |
Inbound delivery &1 &2 does not exist; reference is saved | Space: object requires documentation | |
| 3 | 002 |
Vendor (&1) or delivery note (&2) missing; reference not saved | Space: object requires documentation | |
| 4 | 003 |
There are references to missing vendor; status cannot be set | Space: object requires documentation | |
| 5 | 004 |
There are still references to missing vendor; status should still be '0' | Space: object requires documentation | |
| 6 | 100 |
Delivery & cannot be assigned to any internal notification | The short text describes the object sufficiently | |
| 7 | 101 |
Delivery &: Item & is not uniquely assigned to an internal item | The short text describes the object sufficiently | |
| 8 | 102 |
Posting reset due to error in another IDoc in mass processing | The short text describes the object sufficiently | |
| 9 | 103 |
Changes to shipping notifications are not possible at present | The short text describes the object sufficiently | |
| 10 | 104 |
Unknown qualifier in segment & | The short text describes the object sufficiently | |
| 11 | 105 |
Delivery &: Assignment to regular shipment is not unique | The short text describes the object sufficiently | |
| 12 | 106 |
Delivery &1: Corresponding regular shipment &2 not found | The short text describes the object sufficiently | |
| 13 | 107 |
Int. shipping notification &1: Time deviation shipment -> delivery | Space: object requires documentation | |
| 14 | 108 |
Creation of shipping notifications in shipment is not possible at present | Space: object requires documentation | |
| 15 | 109 |
Delivery &: Shipment type does not correspond to the delivery type | Space: object requires documentation | |
| 16 | 110 |
Partner identification is not filled in segment & (no. &) | The short text describes the object sufficiently | |
| 17 | 111 |
Delivery &: No route schedule found | The short text describes the object sufficiently | |
| 18 | 112 |
Delivery &: Route schedule could not be uniquely identified | The short text describes the object sufficiently | |
| 19 | 113 |
Int. notification &: Route schedule in notification and shipment differ | The short text describes the object sufficiently | |
| 20 | 114 |
Shipping notifications & - & created with warnings | The short text describes the object sufficiently | |
| 21 | 115 |
Shippping notifications & - & created, & included in shipment | The short text describes the object sufficiently | |
| 22 | 116 |
Shpg notifications &-& created with warnings, & included in shipment | The short text describes the object sufficiently | |
| 23 | 117 |
IDoc &: No external identification in field & | The short text describes the object sufficiently | |
| 24 | 118 |
IDOC &: Entry in field & is not unique (see shipment &) | The short text describes the object sufficiently | |
| 25 | 119 |
IDoc &, Segment &:Dely qty is not equal to the total from summ. JIT calls | The short text describes the object sufficiently | |
| 26 | 120 |
Segment &: Inconsistency in assignment of summarized JIT calls | The short text describes the object sufficiently |
History
| Last changed on/by | |
20041209 | SAP |
| SAP Release Created in | 471 |
