Dear Stefan
1.) CG33 does have some difference in comparison to CG02. Using Cg33 you an import e.g. phrases and preapre value assignemtn data records for characteristic there this phrase is not part of phrase set; therefore CG33 is not so "strict" in comparison to CG02
2.) I did some short analysis. As you may be know: CDHDR, CDPOS are the tables which are used in Change document generation. I have the feeling that CG33 is "supported"
3.) regarding import process: If you analyse pachacke CBUI you will easily find the related function groups related to spec import. The spec import is "very" complex and therefore many function module and form routines are used
I agree with you, taht CG02 and CG33 should behave the same regarding RC1_CHANGE_DOCS_GET
PLease check: http://www.stechno.net/sap-notes.html?view=sapnote&id=485263
In EH&S to my understanding table EST_CHANGE_DOCS is used to store "temporarily" data which is then used by RC1_CHANGE_DOCS_GET toi generate the data in CDHDR, CDPOS
So may be analyse this table using your example.
Please prepare an inquiry in this FORUM. The topic of "Change docs" and the corresponding process / tools etc. have been discussed in some threads.
I found indication that this topic has been as well discussed in different FORUM example:
http://scn.sap.com/thread/2117788
I am not aware of any OSS related the topic. CG33 is "relative" stable. During my thumb analysis of the import process I only found indication that the process hase "updated" to consider / Take into account new SAP EH&S functionality coming with EH&S 6.0 and the different Enhancement Packages.
I believe there are further SAP reports availble like: RSSCD110 helping to you analyse "change doc" topic.
In any case. from technical perspective the change doc generation for specifications in EH&S is quite complex
C.B.