Showing results for 
Search instead for 
Did you mean: 

Specification Load using CG33

Former Member
0 Kudos

Using CG33 to load the specification charecteristics in EHS. First the spec header & identifier are created sucessfully with change number. During additive loading of the characteristics with the same change # CG33 treats this as a new spec and error out that spec already exists.

However, the spec was loaded without a change # the subsequent additive load of charecteristics is treated correctly.

How can CG33 be able to do additive load of charecteristic with the change #  already assigned to spec?

Accepted Solutions (0)

Answers (2)

Answers (2)

Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Rao,

you cannot do an additive load with a change number. This only works with deletion type 4 which in turn means that you overwrite all currently existing data.

Best regards,


Active Contributor
0 Kudos

Dear Rao

I have never used CG33 together with change numbers. I believe the "trick" is the "right" use of a combination of the field "Spec. deletion type" and the field "Change Number" in the screen you have prepared here. If you refer to:

there is an option of: "The specification data is deleted using change numbers"

It depends really on the business need if or if not you need to use a change number. Normally during the first set up of a specification you have no need to use a change number. The same is true regarding the first initial upload/preparation of data. The use of the change number makes sense if you have prepared a specification with data in the system and you would like to add data which is "valid" in the future but you would like to make sure that other data is not selected/used any more. Here the system is performing a so called "split" of data records. Now you can use the so called "key date" in CG02 as a seleciton criteria to check what happens in cg02 if you use change numbers. If you have used a change number e.g. 01.01.2013 (that means data record is valid starting 01.01.2013) you can prepare the system in such a way that e.g.:

Color green is valid until 31.12.2012 and color blue is starting 01.01.2013. If you use a key date of "31.12.2012" in CG02 you would get as a result "green" as the color and of you use 01.01.2013 you would get blue.

The use of change numbers in EH&S is quite tricky. They should be used only if you have a clear understanding about the "process" behind it. You need to pay attention that you can use change numbers at many places in EH&S; during maintenance of phrases, specification, generation of reports etc. etc. Therefore in reality in most cases change numbers are only used in the context of "Dangrous goods management" because the effect of the change numbers on data selection etc. is not easy to understand and the user might get in "trouble".


PS: you can use "many" change numbers with the same spec. It depends on how you prepare the change number. Normally you generate per "date" one change number.

E.G. you have prepare today a specification in the system (e.g. REAL_SUB); you can maintain this spec using change number 1 which is valid starting 01.01.2013; at the same day (e.g. today) you can go on with maintenance using the changer number 2 which is valid starting 01.01.2014.