Migration for Release 2

Changes to BOPF Model of Yard Orders/Yard Requests Correction Report

In SAP Yard Logistics 1.0, two activity categories were used for the yard order business object - Yard Order and Yard Request. In SAP Yard Logistics 2.0, only one standard activity category is used - ROOT.

You use the report /SAPYL/YO_NODE_CAT_MIGRATION to set the activity category for all yard orders for a specific yard (specified as select-option) in the database table /SAPYL/YO_HDR to the ROOT activity category.

This report shall only run once using transaction SA38 during migration and it should run for all your yard numbers.

Customizing Activity "Define Yard Numbers"

Before Release 2, you can define yard number properties in Customizing activity Define Yard Numbers by choosing your central EWM business system and EWM warehouse number. Now, in Release 2, this can be defined per Yard Order Item individually, that is, multiple warehouses per Yard Order. Also, the field TU Mapping Type is removed, as this mapping is now based on the field External Document ID (which is filled with the SAP TM's freight order, if the source system is an SAP TM system). Therefore, these fields have been removed from this screen. The Dangerous Goods field is still available but moved down to the additional fields for defining the Dangerous Goods Check and the Dangerous Goods Source from where the system reads the Dangerous Goods data.

Customizing Activity "Map TM Freight Order Types"

In Release 2, in this Customizing activity, a new flag to determine the mapping between the items for the freight order from SAP TM and the items to the Yard Request can be defined:
  • When the mapping type is 1 – Duplicate external hierarchy, no additional logic is needed. The system copies one to one the item hierarchy from TM.

  • When the mapping type is 2 – Consider TU Loading Hierarchy, the items will be loaded on the parent item, only when the TU Loading Hierarchy already maintained in SAP Yard Logistics allows this. If the loading hierarchy does not allow it, the item is placed on the same level as its corresponding parent item.

Customizing Activity "Map TM Relevant TU Types for Yard Request"

In this Customizing activity, an additional column for Equipment /Vehicle Type is added, that is, now the TU types can be determined more granular by using the equipment plus the means of transport from SAP TM.

Customizing Activity "Define Default Activity Types"

In this Customizing activity, the time points for the default activities are changed. The time point for 1=During Yard Request Release is deleted. Now only the time points 0=During Yard Request Creation or 2=During Yard Order Creation are possible.

Customizing Activity "Define Whether to Activate Yard Task of Yard Order Automatically"

In the previous release, the system triggered the automatic activation of the first yard task and the follow up tasks using the SAP Post Processing Framework. As this implies some technical drawbacks, these PPF actions were removed and this new Customizing activity is implemented.