Replacing List subs within Standard Composition of Real subs with other List subs - in Mass

[Former Member]

Hi,

After data migration from 2 different clients, we noticed CAS numbers appearing more than once within CG02, but under different List_subs.

For example, CAS number 121-33-5 is assigned within List Sub A and List Sub B.

List Sub A is used within 400 Real_subs (in standard composition), while List Sub B is used within a further 300 Real_subs (std. composition).

Within CG02, I want to perform a 'find and replace' if possible. The goal would be to find where List Sub B is being used (i.e. within the standard composition of my Real_subs), and replace List Sub B with List Sub A within each of the 300 Real_subs. I would then subsequently delete List Sub B from CG02.

Is this possible? We have multiple instances of this.

We use Atrion CE Property Tree v4.1.4.

[christoph_bergemann]

Hello

you need to differentiate the "find" from the "replace" part. It is "obvious" that youi have "killed" EHS by establishing this data situation (in most cases you need very good reasons of such se tup),

Coming back to your example:

"For example, CAS number 121-33-5 is assigned within List Sub A and List Sub B."

Step one. Define if "A"  or "B"  should "represent" CAS number 121-33-5

Step two: Depending on step one: what is "A" or B" (if not 121-33-5) ? or did you simply "generated "my "mismatch" the "same" LIST_SUB twice

Step three: Check for "use" of "A" or "B" => this is now the "nightmare story".  Depening on the number of "CAS" number mismatches you should:

1.) either create an own "ABAP" Report

2.) use se16 to check

3.) But you should not use "CG02" => this wil lbe only a "disaster" => Reason is "quite" simple:

a.) runtime

b.) you have to many properties of type "composition" or "Speclisting"

For the part "B" => the exchange part so to say: it is very probable that the use of the "wrong" numbers is "quite" to high. Therefore once again: by using ABAP report you should correct

To sumup: in most cases. for the "where used" part" and for teh "Replace" part you need an own "ABAP" report. Any other topions are quite "tricky" / "expensive" and time consuming.

I keep fingers crossed for you in solving this "disaster"

C.B.

PS: Potentially you can try to generate a EHS Expert rule set: to "exchange" A by B; never tried it. YOu could then just use hitlist. for any composiiton at the same time (as long as the rule is designed as such) and then giv it a try.

Workaorund can be: if "A" or "B" is used only in "standard composition" then you can check for: which REAL_SUB contain A. You will get hit list. As you know now: only standard composition is effected and you know that "A" must get "B" then the suer can do the job. IN your case for either 200 or 300 objects. Painful work but possible and you avoid the use of ABAP etc. reports.

[Former Member]

Hi C.B.

Thanks for your response.

In terms of dividing find and replace - I am able to create a report which tells me exactly where each of my list subs are being used; in which Real_sub, the %, associated CAS number... I am using custom transaction zcedel.

So for find, we are okay. Also, we have identified the List_Subs (CAS numbers) we wish to keep, and the duplicated CAS numbers (in the form of List_Subs) we wish to replace (and delete) within the standard composition of our Real_subs.

Now that we have our report and know exactly 'what' to replace, we have now idea 'how' to replace. Manual replace is not possible (as we are talking in excess of 1000 cases).

"Potentially you can try to generate a EHS Expert rule set: to "exchange" A by B;" - This is exactly what I'm looking for, but during research on how to do this, I have been unsuccessful.
Help on how to do this would be great if a anyone has any suggestions?

[Ralph_P]

Hi Eoghan,

If you know for which specification the composition needs to be corrected you could export these compositions, replace the key of LIST_SUB 1 with that of LIST_SUB 2 and re-import the whole list. You may have to divide the export into two packages, depending on runtime, but that way would work I'm sure.

Ralph

[Former Member]

Hi Ralph,

Yes that could work. The problem is uploading data into the property tree. We can upload data using excel spreadsheets into our identifiers tab - i.e. replacing identifiers, Reference specification, material assignment... The issue is uploading data directly into our property tree.

In the past, we have used IDocs to upload our data into EH&S in order to create new specifications. But the IDoc process doesn't work if we want to update existing specifications.

Is there a standard way to re-import a whole list with the correct info, as you suggest?

[Ralph_P]

Hi Eoghan,

using Excel to adjust the data and then OCC for the import works fine, even for a few thousand records. It's not rocket science, just a bit tricky if you do it for the first time.

Ralph

[christoph_bergemann]

Dear Eoghan

". But the IDoc process doesn't work if we want to update existing specifications."

The trick here is the "right" trigger and the right ALE IDOC: Imagine this:

You have REALSUB with component A. Distrbuted to system X. Now you exchange A manully by B. On Traget side the ALE mechanism must make sure that A is replaced by B. So in my opionion ALE must work (but is not easy),

My knowlegde on OCC side in this are is to "low". but for "content" upload the "update" is possible. But not sure how this is done SAP internally (e.g. using delet/insert or just "update").

But as you can load compositions with OCC you should be able to "change" the data as well. Tricky thing but will work.

More or less you should check: is there the "chance" that something similar must happenas well in the future? If there is a chance that you need to exchange component A by B on "mass level" it is always a good idea to look for either a "rule set" or othere "user oriented" options to hand other the "real job" to enduser

OCC, IMport etc. are in most cases "consulting" activities and not done by end user.

C.B.