Ansicht
Dokumentation

Enhancements in the Location Master Data ( RELNAPO_30A_SP1_MD_LO )

Enhancements in the Location Master Data ( RELNAPO_30A_SP1_MD_LO )

ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Enhancements in the Location Master Data

Use

New Structure of APO Initial Menu

The path to the master data has changed due to the conversion of APO menu. You have previously chosen Navigation Master Data Location in the SAP Easy Access Menu. As of APO Release 3.0A (First Customer Shipment and Support Package 1), you choose Master Data Location directly in the SAP Easy Access Menu.

In addition to APO master data, you can now maintain master data for the various applications included in APO under Master Data. This restructuring means that master data maintenance is no longer possible within the individual submenus of the APO applications.

Restructuring of the Interface

Up to now, there was an initial screen in the location master where you could enter a location key. This enabled you to branch to a second screen for the purposes of data maintenance. However, major changes have been made to the maintenance of the location master for APO Release 3.0A (FCS + SP1:

  • Maintain or choose a location in the screen Location Master. If you maintain a location type when creating a location, the system displays the location type you have maintained for the location when you change or display the location. You branch to the screen Change, Maintain, or Display Location.
  • In contrast to 2.0A where it consisted of several input fields, the subsequent screen contains several tabs as of Release 3.0A (FCS + SP1) where you can maintain the corresponding data.

The following tabs and input fields are new as of APO Release 3.0A (FCS + SP1):

Location Master Initial Screen

Location type: The location types that the system proposes by means of the input help are default values, and are assigned to a location. There are two special features:

  • Location type 1007 (MRP area): Opens the fields MRP and Sublocation on the tab General that can be transferred from the R/3 System or created in the APO System.
  • Location type 1010 (Customer): Contains the tab VMI customer that only appears for this location type in the location master.

Location Maintenance

Plan version: The plan version is displayed in this screen as of Release 3.0A (FCS + SP1). You can set a certain plan version in the screen Location Master: Initial Screen using the button Set plan version, in other words, version-dependent fields are filled for this version. If you have not set a certain plan version, the system automatically sets plan version 000.

Tab General

  • External location: Part of an external location description
  • Business system group: Part of the an external location description
  • Created: Specification of the user who first created the data
  • Changed: Specification of the person who last changed the data
  • Business event: Field used in the area of ATP Backorder processing/Product availability
  • Planning plant: Field that only appears on the tab for a location with location type 1007 (MRP area)
  • Sublocation: Field that only appears on the tab for a location with location type 1007 (MRP area)
  • Network design location profile: Field that belongs to the cost profile of the network design
  • New location: Field that belongs to the cost profile of the network design

Tab Address

All fields on this tab are new, and the tab is used for general address specifications.

Tab Calendar

Contains the calendar for Production, Warehouse, and Shipping that was already available in the location master prior to Release 3.0A (FCS + SP1).

Tab TP/VS

  • All fields are new. This tab contains data for the application component Transportation Planning and Vehicle Scheduling (TP/VS).
  • Incompatible/Compatible Vehicles: Here you define the compatibility or incompatibility of a vehicle with a location
  • Customer delivery: Only customers are supplied with these shipments
  • Picking lead time
  • Transportation creation lead time

Tab Resources

The handling resources (not warehouse resources) maintained on this tab can only be maintained on a version-independent basis. However, consumption of these resources is version-dependent.

  • Selection buttons:
  1. Loading/Unloading resource maintained You maintain the corresponding resources.
  2. Opening times: You maintain opening times for the location.
  3. None: Neither resources nor opening times are maintained.
  • Loading/Unloading resource (Inbound): Maintain a resource for the inbound delivery process.
  • Loading/Unloading resource (Outbound): Maintain a resource for the outbound delivery process.
  • Consumption: Specifies the consumption of the maintained inbound or outbound resource.
  • Inbound resource
  • Outbound resource

Tab SNP

  • Category group for stocks
  • Push not allowed

Tab VMI customer

All fields are new, and the tab is only available for location type 1010 (customer).

  • Location for sold-to party
  • External location description
  • Sales organization
  • Distribution channel
  • Divisions

Tab Extras

Tab that contains text fields for maintaining additional information.

Effects on Data Transfer

Transferral of the Vendor from the OLTP System to the APO System

You must maintain the table CIFVENTYPE when transferring a vendor from the OLTP System to the APO System: In the APO System, the vendor is a supplier. The vendor is not of such significance in the R/3 System. In order to ensure correct transfer to the APO System therefore, the vendor in the R/3 System must be transferred together with the attribute Forwarding agent that is represented by a certain account number. Because you can maintain the data on an application-specific basis, you must maintain the above-mentioned table in order to guarantee the integration of data with the APO System. This table ensures that the vendor is recognized as a forwarding agent and transferred as such.

Effects on Customizing

Automatic Assignment Customer Transportation Zone

If you have maintained a transportation zone in APO Customizing under Transportation Planning and Vehicle Scheduling (TP/VS) Basic Settings Maintain Transportation-relevant Hierarchy, the system automatically assigns the customers already assigned to a transportation zone in the R/3 System to a transportation zone when transferring customer data from the R/3 System to the APO System. This occurs during the maintenance of the above Customizing activity. In the case of a transportation zone, this refers to a location.

Further Information

Release information APO TP/VS: New Application Component Transportation Planning and Vehicle Scheduling (TP/VS)






ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 8080 Date: 20240329 Time: 105839     sap01-206 ( 120 ms )