Advertisement

Advertisement
EDIGenie - All things Electronic Data Interchange

Monday, December 18, 2017

SAP EM : Things to look out for when implementing SAP EM

I recently came across a SAP EM Implementation with one of my clients, where they had SAP EM implemented by one of the best consulting companies but turned out to be a complete disaster.

They have N number of issues as listed below:

  1. One EH having Multiple Values for the same TRACKING ID CODE SET - which is causing incorrect events being posted on EH's
  2. Tracking ID's without Start Date & End Date - due to which Events posted in the past get re-triggered for EH's created in Future with same Tracking ID, causing data inconsistencies
  3. All Task Logging switched on, causing billion+ entries in EH_TASK, forcing the client to do Partitioning in the database to handle the table size.
  4. BAPI COMMIT being used inside the RULE SET causing data inconsistencies and short dumps
  5. Event Generation within the Rule Sets causing short dumps
  6. No Queuing process followed and hence same the EH is called multiple times at the same moment causing data inconsistencies

Please feel free to comment on other issues that you have seen in your implementations.

No comments:

Post a Comment