SAP ABAP Data Element L_ADRNRD (Location: Address, dynamically determined fr.ship.pnt, etc.)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM-BF (Application Component) Basic Functions
     ⤷ VTR (Package) SD R/3 transport processing
Basic Data
Data Element L_ADRNRD
Short Description Location: Address, dynamically determined fr.ship.pnt, etc.  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type ADRNR    
Data Type CHAR   Character String 
Length 10    
Decimal Places 0    
Output Length 10    
Value Table ADRC    
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Address 
Medium 15 Address 
Long 20 Address 
Heading 10 Address 
Documentation

Definition

Address providing more detailed information on a location. The address is identified by a unique key in the SAP system.

Use

This field will be filled with the address number of the shipping point, the plant, and so on.

It contains the address number dynamically determined during runtime and has to be distinguished from the address manually created in the (current or previous) document.

In this case, the origin indicator of the address is set to 'A'.

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 by/on SAP  20110901 
SAP Release Created in