Data transfer of substances fails

[Former Member]

Hi @all,

we need to distribute substances via ALE/IDcos between two SAP systems.

Unfortunaltely the data structure is quit complex and every time we distribute data the SLG1 error log tells us that data is missing, e.g. component substances, legal entities or simple values mentioned in some of the characteristics (e.g. SAP_EHS_1023_006_REVISION --> "06 2001").

Is there any chance to get this data migrated (quick and dirty would be also fine as this is a temporary solution) and the missing data is either generated automatically or ignored during inbound processing?

Thank you in advance for your help!

Best regards,

Christoph Giehl

[former_member215519 · Accepted solution]

Hi Christoph, from my understanding, you will have to have the same EHS IMG to enable ALE transfer, also you need to have the same set of class/characteristic maintained. Some dependencies are also required, such as phrase, phrase set and component substances.

Only with this, the ALE function can work properly, because ALE itself is calling the standard EHS substance creation function module to create new substance, the error handling will be the same if you input data online.

Not sure if there are some ways to skip those errors, at least not in my knowledge.

Thanks.

[Former Member · Accepted solution]

Hi John, you are correct: IMG, classes, characteristics, phrases and phrase set assignments, everything is aligned. What we are missing is a chance to insert values as shown above in the example like the value "06 2001" for SAP_EHS_1023_006_Revision. Every specification, containing such a value, will not be inbound processed due an error message stating, that this value is not existing.

So we are searching for a way to insert these values while inbound processing - the system should simply accept the value inside the IDoc.

Best regards, Christoph

[christoph_bergemann · Accepted solution]

Dear Christoph

I am sorry to say: please check really the definition of SAP_EHS_1023_006_Revision in both systems (check any relevant EHS customizing). Make as well sure that the phrases are there (using ALE phrase tarnsfer).

It is "well" known that sometimes the "sequence" of inbounding in the traget system is not "good" enough; e.g. the systems try to to book spoecification A but cannot as component B is not there. It is quite tricky to get robust ALE set up.

C.B.

PS: Thanks to John. Very good explanation. Good job !

PPS: to prepare a stable ALE set up is not easy. The topics is not discussed often here.

May be check e.g.:

A number of exists exists in ALE: e.g.

C14A0001            EHS: ALE - Identification of substance in target system; may be by using them you get some "stabilisation"

[Former Member · Accepted solution]

Dear Christoph,

the ALE dirtsribution itself is set up fine and working properly.

The only issue we are facing is that some properties (existing in both systems) reject the distribution of single values, which are not maintained as phrases.

Bottom line - it seems that we have to distribute the respective substance headers only and maintain the data manually.

Thanks for your help!

Best regards,

Christoph

[christoph_bergemann · Accepted solution]

Dear Christoph

to do manual maintenance is no good option ! You should really check the issues ! Don't use the manual option. This is the wrong way and will get more problems as before !

I tried to identify a different thread related to your topic. But I was not able to find it once again. IN the topic a ALE issue regaridn reports have been mentioned. There was some "afterwork" to be done (using better inbound processing)

You should invest the time to go on issue by issue. Coming back to your list:

e.g. component substances, legal entities or simple values mentioned in some of the characteristics (e.g. SAP_EHS_1023_006_REVISION --> "06 2001").

a:) component substance are missing => this is a "well" known problem; but using clever inbound/outbound etc. it can be removed

b.) legal entities missing => this is a gap in customizing: BOth system must ! be the same !

c.) SAP_EHS_1023_006_REVISION --> "06 2001" => this should not happen !

Be aware of the fact that ALE  success or failure can as well be related to the "user" doing the job (user profiel is critical !!)

Don't do it manual ! You will never get rid of the problem. Invest time to solve issue step by step. Make sure that any body starting ALE is doing the same way (using the same user set up (date format etc.)

C.B.

[Former Member · Accepted solution]

Dear Christoph,

usually I would agree - but as this is a temporary solution the manual maintenance seems to be the best option. As you said yourself:

a:) component substance are missing => this is a "well" known problem; but using clever inbound/outbound etc. it can be removed --> solved

b.) legal entities missing => this is a gap in customizing: BOth system must ! be the same ! --> solved

c.) SAP_EHS_1023_006_REVISION --> "06 2001" => this should not happen !

Well, it happens, but the number of respective substances is about 20-25. So the manual maintenance is not too big.

And as time is the most critical issue here we have to do it.

Thanks again and best regards,

Christoph

[christoph_bergemann · Accepted solution]

Dear Christoph

I will not give up to help you. Can you pleaese once again check characteristic SAP_EHS_1023_006_REVISION in both systems? It should be CHar29 without any check function etc. It is (or shouuld be) a "free text" characteristic and therefore the value "06 2001" should be booked without trouble or problems. may be if needed start OSS dialog,.

Can you play around in dev or test system? E.g. change value "06 2001" to different one? This is really a standard characteristic used very often (e.g. to store content) and I am not aware of any issues in ALE here.

C.B.

PS: I forgot to mention this: sometimes even if you have a stable ALE sometimes you get trouble. In this case: there is an issue in data base. Check in source and target system the specification. There is a very important report in place which you shoud use . Tjhis report is not well known but especiall yin ALE can help you to survive.

May be take a look first here: SAP program RC1SUBREORG - EHS: Check for consistency of EH&S data

RC1SUBREORG EHS: Check for consistency of EH&S data - SAP Report - ABAP

as well as: RC1SUB_HIERARCHY_SHOW EHS: Display Hierarchy of All Relevant Objects for a Substance - SAP Report - ...

Both reports can help you top survive in daily EHS consistency analysis.