Kontakt

Ansicht
Dokumentation

APO_TPVS_FLDCT - Define Field Catalog

APO_TPVS_FLDCT - Define Field Catalog

BAL_S_LOG - Application Log: Log header data   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you define the TP/VS field catalog. You define fields (in other words, object characteristics, such as means of transport or transshipment location) in the TP/VS field catalog that you use to do the following:

  • Define compatibility types for compatibilities
  • Define conditions

You can define fields for the following object types:

  • Order/freight unit
  • Order item
  • Transshipment location
  • Vehicle (this object type also includes trailers)
  • Shipment
  • Compartment
  • Means-of-transport combination

You can create the TP/VS field catalog in two ways:

  • Using an upgrade report. If you want to upgrade from a 3.0, 3.1, or 4.0 system to a higher system, we recommend that you execute the upgrade report to fill the field catalog with standard fields. The following standard fields are filled, amongst others:
  • Means of transport (only used for compatibilities and not for conditions)

  • Transshipment location (only used for compatibilities and not for conditions)

  • Source/destination location

  • Source/destination transportation zone

  • Shipping data (for example, shipping point, Incoterms)

  • Product data (product number, transportation group)

  • Order data (order number, requested delivery date, material availability date)

  • Volume/weight group

You can also define additional user-specific fields.
  • Manually if you do not need all the standard fields

The entry in the Field Name field should agree with the field name of the corresponding field in the object structure to enable standard processing (except for transshipment location (= HUB_LOCNO)):

  • Order/freight unit/order item: /SAPAPO/VSR_G_FUNIT
  • Vehicle: /SAPAPO/VSR_G_RESOURCE
  • Shipment: /SAPAPO/VSR_G_SHIPMENT

In the Description field, enter a description for the field.

You can optionally use Table Name (DDIC) and Field Name (DDIC) to specify the DDIC table that contains the required values for the input help (for example, for defining conditions and compatibilities).

You should enter values for fields that are not contained in the object structure by using the following enhancements in the standard system:

  • Order/freight unit/order item: BAdI /SAPAPO/VS_FUNIT (method GET_FIELD_VALUE, interface /SAPAPO/IF_EX_VS_FUNIT)
  • Vehicle: user exit 004 in function group /SAPAPO/VS_VSGUI
  • Shipment: user exit 003 in function group /SAPAPO/VS_VSGUI

Orders with certain Incoterms are not to be shipped together.

The window for the delivery might depend on the delivery priority and the shipping conditions. Possible values for shipping conditions are stored in customer table Z_SHIP_COND, field SHIP_COND.

To make it possible to define compatibilities and conditions, the TP/VS field catalog must contain at least three fields (filled in the standard system):

Field Name Description Table Name (DDIC) Field Name (DDIC)
INCO1 Incoterms Part 1
LPRIO Deliver Priority
VSBED Shipping Conditions Z_SHIP_COND SHIP_COND

Z_SHIP_COND

For more information about compatibilities and conditions, see the SAP Library under SAP Advanced Planning and Optimization (SAP APO) -> Transportation Management -> Transportation Planning/Vehicle Scheduling (TP/VS).






Addresses (Business Address Services)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 5199 Date: 20240524 Time: 004741     sap01-206 ( 58 ms )