cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

TM-EM Integration - Should it be expected or unexpected event

Former Member
0 Kudos
973

Hi Experts ,

We have a requirement to capture " scheduled delivery appointment " .

Considering carrier collaboration portal design in TM , I am wondering should we make it "expected event " or "unexpected event " .

Concern is about reporting of same event multiple times through carrier collaboration portal  .

If user report the same event 5 times with 5 different date , then business want to see all dates which he changed with respect to original date .

I could make unexpected event to fulfill the requirement . But the issue is if we make it unexpected event then it will not be displayed in CCP with all expected event . In this case , carrier has to select the event manually to report the event . We are worried that if this event is not displayed in the screen , there is possibility that carrier will forget to report the event so we do not want to make it unexpected event .

If we have to make it expected event and carrier report date multiple time then how we can show mutilple change date in "execution " tab in freight order .

Waiting for your valuable suggestion .

Thanks in advance .

Regards,

Rajesh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Rajesh,

I would go with unexpected event but if you have issue carriers not reporting it if they do not see expected event, then you need to find the middle ground.

Solution 1:

If you are OK with not having location based scheduled delivery appointment, then keep it as Expected Event, remove reprocess expected event flag from EE profile and make it location independent( check the "do not check" location but you can keep set location function unchecked.

This way you can have expected event in CCP and keep posting events. The first one will be posted onto expected event and subsequent events show as unexpected events in TM/EM and it helps to see all history.

Solution 2: Keep as EE and location based. Everytime you post event, copy over the previous events date onto datetime1,2,3,4,5 fields in EH_EXPEV. This will provide you history upto 5 + current event = 6 events history.

Run the first solution in your system and see if it's OK with your team.

Thanks,

Vishnu

Former Member
0 Kudos

Hi Vishnu ,

Solution 2 will not work cause business will not be able to see all reported event in execution tab of freight order .

I tried solution 1 but it is not creating unexpected event date when 2.3 rd time event is reported .

If you remove reprocessed flag , it will not create unexpected event , it will simply not consider the event which is posted 2 nd and 3 rd time .

Regards,

Rajesh

Former Member
0 Kudos

In addition you will have to define the event code as "Allowed Unexpected Event Code" in your EH Type - otherwise it will not be processed as unexpected event if the EE is reported multiple times.

Best regards, Daniel

Former Member
0 Kudos

Daniel is correct. I missed to mention that.

You have uncheck it  or add your event as unexpected as well.

Message was edited by: Vishnu Cheeti

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Rajesh,

something similar was discussed here:

Best regards,

Steffen

Former Member
0 Kudos

Hi Rajesh,

I can see think of unexpected event on this scenario. I don't have visible on CCP tool.

When I check SAP link Tracking of Freight Orders and Freight Bookings - Integration with SAP Event Management - SAP Librar..., it shows like below as you can define which events can be visible including unexpected event. Check this.

"Your carrier can also report unexpected events in the SAP TM Collaboration Portal.

In Customizing for Transportation Management under Start of the navigation path Integration Next navigation stepTracking and Tracing of Processes and Documents Next navigation stepDefine Transportation Activities for Tracking and Tracing End of the navigation path, you can define which events are visible in the SAP TM collaboration portal."

Regards


GGOPII