SAP ABAP Message Class VW Message Number 305 (& Location specification insufficient)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-BF (Application Component) Basic Functions
⤷
VTR (Package) SD R/3 transport processing

⤷

⤷

Attribute
Message class | ![]() |
VW | |
Short Description | ![]() |
Shipment Processing Output | |
Message Number | ![]() |
305 | |
Documentation status | ![]() |
||
Authorization check Error Message | |||
Changed On | ![]() |
20100310 |
Message Text
& Location specification insufficient
Help Document
Diagnosis
Your entries are not sufficient to define the location.
System Response
Procedure
Rules for the definition of a location in stage processing of the shipment document
Locations can, for example, emerge as shipping point or destination in the stage of a shipment document.
These shipping points and destinations can be defined with a reference to an existing object in the SAP system or as completely free addresses. Here are the rules governing this
- The location definition must be unique. I.e., from the fields
- GFT Connection point
- Shipping point
- Customer
- Plant
- Vendor
only one may be filled. - An exception exists if the GFT connection point itself references a shipping point, a customer, a plant, a vendor, etc. In this case, the connection point and e.g., shipping point can be filled. Up to the connection point itself, all other fields are not ready for input but are only displayed.
- Some fields are optional and do not have to be maintained. They may be maintained under certain circumstances:
- Loading point: Shipping point must be maintained
- Storage location: Plant must be maintained
- Unloading point: Custmer must be maintained
- Warehouse: Shipping point or plant must be maintained
- Door: Warehouse must be maintained
- Additional info: Can always be maintained
- The addresses can always be maintained:
- As completely newly defined, stand-alone address, without another field being filled. Example: Inbound delivery to a construction site
- As an alternate address for one object, e.g., an alternate address for the customer.
History
Last changed on/by | ![]() |
20100310 | SAP |
SAP Release Created in |