propagation

[former_member193027]

Hi,

Can someone explain me the difference between standard and enhanced propagation.

also under which conditions the standard and enhanced propagation does not work.

Thirdly is there any way we can understand that propagation has worked or why it has not worked

[MarcoFreischlag]

Propagation Mode for Execution Information

Controls how execution information is propagated between different related
freight documents.

Use

The following options are available:

• Standard Propagation

Select this option if the attributes DATACS and DATAID of the execution
information are not used in your scenario.

• Enhanced Propagation

Select this option if the attributes DATACS and DATAID are used to
distinguish between several expected events of a freight document in SAP EM that
are all related to the same expected event of its successor document.

Dependencies

If you have not selected the checkbox Propagate
Execution Info in the Customizing activities for defining freight order

types, freight booking types, and transportation unit types, this setting is not

taken into account regarding the propagation of execution events to predecessor

documents. We recommend that you set the propagation mode to the same value for

all freight documents that are related to each other regarding the execution

tracking.

Example

One freight unit with several containers is assigned to an ocean freight

booking. The behaviour regarding the propagation mode can be the following:

Standard Propagation

The freight unit and the freight booking both have exactly one expected
event Loading End at the port of loading. If the event is reported for
the freight unit, it will be propagated to the freight booking immediately and
vice versa.

Enhanced Propagation

• Using the attributes DATACS and DATAID SAP EM can be set up to have one expected event Loading End per container that has to be loaded at the port of loading. If these events are reported for the single containers on the freight unit, only the last one that indicates that all the containers are loaded, will be propagated to the freight booking. If the event is reported for the freight booking, the enhanced propagation mode will automatically report the event Loading End for all containers of the freight unit.

[Former Member]

Hi Marco,

Firstly I Thank you for explaining this in such a great detail.

I have a question in mind, though exactly not similar to this scenario you have explained. This infact is related to the propagation from a successor document to the predecessor document.

I have a scenario where there are two freight units in a freight order going to the same location. In the case of a multi-pick scenario where the load (FU) is picked up from two different plants/ Shipping locations but going to the same customer location as a consolidated load. in this case when tracking is done at the shipment level, for example, a POD is reported at the customer location for the shipment (FOR) then the propagation will lead to updating both the Freight units with the same date/time stamp even if customer rejects one of the Freight units.

So is there a way to handle this case in EM?

Best Regards,

Pramod