cancel
Showing results for 
Search instead for 
Did you mean: 

customs events

Former Member
0 Kudos

We have some expected events related to customs like filing corrected, filing submitted etc where the status will be updated at FWO/FU level and status is displayed at FU level.

In this case since EM-GTS integration is out of scope, how we can have the E-E visibility in EM from the above mentioned expected events specific to customs.

Accepted Solutions (1)

Accepted Solutions (1)

former_member186607
Active Contributor
0 Kudos

Hi Indraneel,

in this case you should define an event types in TM to send an event message to EM as soon as e.g. the status has been updated in TM for the FU. For each such a milestone that you want to track in EM, you should define an expected event in EM. The corresponding event will then be reported by TM as soon as the prerequisites are met (like certain status).

Best regards, Daniel

Former Member
0 Kudos

Can you kindly ellaborate this a little bit. Like if a certain filings has been submitted then how the EM be able to update itself.

Also is it a best practise to involve all customs related expected events in the same profile where other expected events are clubbed or do we create a separate event profile for customs only.

former_member186607
Active Contributor
0 Kudos

Hi Indraneel,

I am sorry, but I do not understand your first point. Maybe you can rephrase it? What are filings?

In the IMG activity documentation there is written the following:

"You use expected event profile groups to create sets of items within an expected event profile, so that recurring expected events can be generated multiple times in the system."

Expected events that occur always together (and maybe also multiple times) should be together in the same group. If all the customs related expected events do not have any dependencies to other expected events, it would make sense to put them in a separate group.

Best regards, Daniel

Former Member
0 Kudos

I mean we have some events like security filings corrected, security filings submitted, export custom process started etc.

Hence my question is that for customs since the above events are repeated for both export and import, hence does it make sense that we create a separate event profile for customs or is it that the above events for customs can be grouped with the standard expected events profile like loading started, loading end etc.

Also as per your previous reply, do we require any separate extractors to be built for customs or can we just create event types in TM system.

Also for custom status change, if the status change implies that export customs started, import customs started in TM object, then do we need to create event types for export/import for customs or we just create event type"Customs" which can then be used for both export and import.

former_member186607
Active Contributor
0 Kudos

Hi Indraneel,

it would make sense to have a separate expected event group (NOT a separate expected event profile) for the customs related expected events. You always have one expected event profile per event handler type - and one profile can contain multiple groups.

To generate the expected events for these custom related events you certainly need new expected event extractors in TM. For the sending of the corresponding event messages from TM to EM you then need also new event types in TM.

Typically for each event code (like departure) for which event messages shall be sent from TM to EM one event type is created.

Cheers, Daniel

Former Member
0 Kudos

One more question,

If we create different group as suggested by you, is it mandatory in that case that we have the planned date for these custom events.

Also is it right that based on the event type extractor in TM, once the status in customs changes from like export process started- export process completed, the respective events will be triggered in EM so that the user in EM can post the above custom events with actual dates?

former_member186607
Active Contributor
0 Kudos

Hi,

1) it is not mandatory to have planned dates for an expected event (although it is the mostly the case). If you do not have a planned date, then, of course, you cannot use the overdue monitor for these events.

2) I am not sure, if I understand you correctly. You can surely set-up TM that once the status is changed to a specific value an event message is extracted from TM and send to EM (e.g. with event code like "ExportProcessCompleted". I do not understand what then should be posted additionally in EM.

Cheers, Daniel

Former Member
0 Kudos

One more question- If there is any status change in custom processing, then is it that via rule sets weneed to include the function"Set status check" and then based on that event message is triggered.

How does the change in TM status triggers event message?

former_member186607
Active Contributor
0 Kudos

For each event type in TM there is the tab Event Management Relevance (in transaction /SAPTRX/ASC0AO), where you have to define when the event is relevant. The recommendation would be to create a EM Relevance function to determine if the event message should be sent or not. In this function you then can e.g. compare the old status value and the new status value and if the status has been changed to a certain value, the relevance function should return "TRUE". Only then the event message will be sent by the event extractor from TM to EM.

Cheers, Daniel

Former Member
0 Kudos

Hi,

A last question- for triggering the event message from status change, do we need to maintain anything in rule sets config also

former_member190756
Active Contributor
0 Kudos

If you mean Status Attributes and Status Profiles they are customized in transaction /SAPTRX/TSC0SP and  /SAPTRX/TSC0ST. The Profile you must then assign to your EH Type.

For the update you need the status activity in your rule set and maintain there the Status Attribute that you want to update.

Best regards,

Steffen

former_member186607
Active Contributor
0 Kudos

You always have to distinguish between customizing settings on TM and on EM side. For the triggering of the event message from TM to EM, you do not have to maintain anything in the rule set (which is on EM side). To trigger further reactions on EM side after receiving this event message in EM you surely have to maintain a rule set for this.

Best regards, Daniel

Answers (0)