Change Pointer Creation in Specification management not working

[stefan_reichert]

hi colleagues,

We have an issue at customerside with the change pointer creation for specifications

If a realsubstance is changed manually via CG02 and the report

RC1_CHANGE_DOCS_GET is executed.

The change points for this real substance is generated and visible.

If the change is done via external document and transaction CG33, the

change is also done but with the help of report RC1_CHANGE_DOCS_GET no

change pointer is created.

do you have any ideas why the systems works like that?

best regards

Stefan Reichert

[christoph_bergemann]

Dear Stefan

your topic is not clear enough.

Check e.g. https://scn.sap.com/thread/2117788

Check e.g. http://scn.sap.com/message/9029200

1.) RC1_CHANGE_DOCS_GET => this report takes care regarding change documents not change pointers; regarding change pointers as an example read: http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htmhttp://sapignite.com/what-is-change-pointer-in-sap/

2.) Please check:  http://help.sap.com/erp2005_ehp_06/helpdata/en/70/f96ee4217b11d393e9080009b98822/content.htm?framese...

You can use Report RSSCD110 or you can use CG02 to get a "display" of change docs per specifications; Cg02/Cg33 should be have the same if the same "logical action" is done

3.) CG02 and CG33 should "react" the same without difference regarding generation or not of change documents; I found no indication that they are different regarding change document generation

4.) may be check e.g.: http://www.stechno.net/sap-notes.html?view=sapnote&id=485263

PLease describe better your scenario.

1.) what are you trying to change using CG02?

2.) what are you trying to change using CG33?

C.B.

PS: may be check as well:

http://www.se80.co.uk/sapreports/r/rc1_/rc1_change_docs_display.htm

http://www.consolut.com/en/s/sap-ides-access/d/s/doc/YC-EHSENVP_CD_NO_CHANGE_DOCS (there should be an englisch version available as as well)

http://www.consolut.com/s/sap-ides-zugriff/d/e/doc/YC-EHSENVP_CD_PROTOCOL_SAVE_PER     (there should be an englisch version available as as well)

[stefan_reichert]

hi Christoph,

sorry for my wrong wording. I'm aware that the report generated change Documents instead of change pointers.

I will try to explain my issue with an example.

if a change in CG02 a value of a Characteristic, save the specification, run the report RC1_CHANGE_DOCS_GET and check the generated change document afterwards for example via RSSCD110. I can see a change document, where the value change is protocolled.

that is what I would expect from the system. that also shows me that the parameters for report RC1_CHANGE_DOCS_GET are set up correctly.

if I do the value change via a flatfile from CG33 and check the specification afterwards I can see that the value was changed. than I run the report RC1_CHANGE_DOCS_GET. I check via RSSCD110 if my change was recorded as expected but this is not the case.

that means a change via CG33 does not create a change document in my case.

best regards

Stefan

[christoph_bergemann]

Dear Stefan

1.) CG33 does have some difference in comparison to CG02. Using Cg33 you can import e.g. phrases and prepare value assignment data records for characteristics 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 pachage 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, that 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 to 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 FORUMs example:

http://scn.sap.com/thread/2117788

I am not aware of any OSS related to the topic. CG33 is "relative" stable. During my fast analysis of the import process I only found indication that the process has been "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 available 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.

PS: please Check

OSS note 793947 with title "Analysis tools for inconsistent administrative fields"

OSS note 485263 with title " "Extras -> Change Document Log" does not display documents"

[christoph_bergemann]

Dear Stefan

Small add on:

if you check e.g.: http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm

and make some research regarding change pointer you will find transactions like BD21/BD22

http://www.erphowtos.com/sap-bw/2-deleting-change-pointers-in-sap-from-bdcp2-bdcp-bdcps-and-bdcpv-ta...

You will in these links and others find the standard SAP tables to store change pointers. I am pretty sure that CG33 / CG02 must support the change pointer writing as EH&S is designed in such a way that ALE distribution is possible for specifications.

So may be use your test example and make first sure that change pointer are writing "similar" (I would expect that this must/will be done).

C.B.

PS: I found this nice link as well:

http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a61bd507d11d18ee90000e8366fc2/content.htm

Interesting here is: first the change document is generated, second the change pointer is generated and then using the change pointers and the corresponding "Master data" (in this case specification data) is transferred to an IDOC

That means: without a "change document" no ALE Distribution take place.

Result: if CG33 really would not create a change document, no ALE distribution would take place;

PPS: e.g. check this as well:

http://scn.sap.com/thread/1538939

and this link:

http://www.stechno.net/index.php?option=com_saptable&view=saptable&id=EST_CHANGE_DOCS&layout=graph