SERVICES in EM

[former_member193027]

Currently we are planning to implement  service called ErrorHandlingxxx  which gets triggered from EM whenever there is an event failure in EM for Inbound message from service provider.

Would like your suggestion how we can make best use of the service to analyse event/error message

[Former Member]

Hi Dipak,

The effective way to manage error handling can be done through IDOC EVMSTA02 & EHPOST01 or custom IDOC (if the message comes and convert as IDOC).  This is a well proven method and long standing one in most of the SAP systems.

If the IDOCs are failed due to incorrect data, segment missing, duplicate records etc then IDOC will automatically trigger a workflow task and assign it to responsible agent to remediate the issue on time.  The user can go to work item and IDOC can be edited and reposted or an agent send email to sender about the incorrect data.

This is not complex one and lot of documentations available in SAP to design this solution.  Moreover, you don't need to think about SAP EM way as this is more or less generic approach for IDOC error handling scenarios.

Let me know if you need anything.

Regards

GGOPII

[former_member193027]

Currently we are not using IDOC here for integrating EM with TM.

[Former Member]

Hi Dipak,

Can you let me know your system architecture and where you want to implement the Error Handling?

For example: -

1. SAP TM -> SAP EM - Queues Failure

2. Unprocessed event messages

3. Locked event handlers

4. Data quality failures

5. Processing Inactive event handlers etc

Regards

GGOPII

[former_member193027]

Basically we want to implement the error handling as an additional column in PI monitoring transactions so that in case of EM message failures via PI from external reporting via carrier, the error handling will serve more details for the event failure. So in this case I would like to understand how we can set this up since this error handling is only related to interface failures thru PI.

[Former Member]

Hi Dipak,

PI has component integration where you can monitor separately SAP EM messages. You can wait for other team members comment who have done this similar setup or you could post in PI forum to get the answer.  Because, it will be the same monitoring action as per my understanding like other SAP system messages error handling.

The PI integration has facility to integrate Alert and send an email to respective team if any failure of messages.

Check this document Central PI Monitoring and Alerting

Regards

GGOPII

[former_member193027]

Thx.

But based on your experience what are the important fields ( like location, event code etc)  we should capture via the error handling mechanism.If you have any input it will be great

[Former Member]

Hi Dipak,

Validation determines based on missing data, incorrect value, missing qualifier, invalid characters, etc

1. Shipper code validation

2. Shipper Name validation

3. Vessel Name validation (if ocean shipment covering)

4. Lloyd's code validation

5. Voyage

5. Point/Port of Acceptance Location

6. Hub or Stages validation for multi-leg

7. SCAC code validation

8. Booking reference validation

9. Container number validation on Ship on Board message

10. Seal number validation specific to customs export or import

11. Event code

12. Prov. Code ID

13. Tr. ID Prov. Name

14. City and Country (ISO formats)

15. so on...

The above validations are differ from project to project, but some of them are mandatory on shipment stages.

The incorrect data failures are inevitable with 4PL or 3PL,when they send event message.

Best approach:

1. Take data failures of last six months

2. List down all message failures and why those are failed

3. Take top 10 failures (you can solve 40 to 50% in this approach) in first stage for error handling to trigger alert if it is failed in PI itself, but it is coming and updating incorrect data then use preprocessing of event message convert to EM EVM format data.

Check and let me know.

regards

GGOPII