Error in data interface SD - EHS: extract to Excel?

[former_member1073904]

Dear all,

I've been handling with errors that come to an Outlook mailbox concerning the "Error in data interface SD - EHS" for SDSs, i.e. mails showing:

Reason for distribution:

Distribution reason category (REASONTYP) = SD_CALL

Distribution reason type(REASONCAT) = DELIVERY

Business transaction triggering distrib. (REASONBPR) MSDS_DIST

-Document data:

Document type xxx (...)

However, it is quite tedious if I have to extract the data manually and one-by-one, from Outlook error mail, concerning the material number and other parameters.

One user has said that it is possible to see these error messages using TR DGSD (or run report RC1SDAPL) directly in SAP. Is there any way of extracting these reports as EXCEL spreadsheet?

I would need to find an easier and less time-consuming way of extracting the data I need other than going through the large amount of these type of mails that I find every day.

Thank you very much!

[christoph_bergemann]

Hello

normally the number of errors in SAP SD/EHS interface should be on "zero" level. So it is very surprising that you get many mails describing issues.

But let us discuss the procss (and then may be you understand the process issue better):

Depending on your set up the MSDS might be triggered via "delivery". Now in a delivery we can have many materials. Now based on SD/EHS set up: only the "relevant" deliveries are processed. But this process is an "online" process. Per delivery EHS is generating a "log".

I am sorry: for detail work on issues: RC1SDAPL is the only solution and sorry: there is no "EXCEL" interface which i am aware of

(e.g. https://archive.sap.com/discussions/thread/3389423

https://archive.sap.com/discussions/thread/3366429

https://archive.sap.com/discussions/message/14205228?tstart=0#14205228

http://www.tcodesearch.com/sap-abap-reports/detail?id=RC1SDAPL

and similar threads).

In theory: you can analyse the process used via RC1SDAPL and try to get somethiing different (using Z report) but this is waste of time as here SAP is using normal "log" and this log is not a haviong a strcuture whcih is "EXCEL" like useful; you just waste time to invest

You should generally start an analysis of the log e.g. by month i try to figure out: do we have a "general" issue in the process? or is only master data missing (e.g. released reports etc.)

PLease cehck the coresponding OSS note (there is one very good OSS note available discussing the details stapes of SDS/MSDS dispatchment).

C.B.