Change documents and Pointers

Hi Gurus,
Would anyone explain briefly about the Change documents and Change Pointers..as I am new to this concept if anyone can explain in more detail or send me documents that would be great and also I will def. reward points..please send me the docs to [email protected]
I gurantee that I will reward points...
Regards
Baba.

Hi Baba,
A Change Document is an object that contains a log of all the changes that were made on a specific business object (like a product or a business partner), so you will always be able to identify what was changed, when it was changed and who changed it.
Change pointers instead are used in a different context that is the distribution of master data changes to different system. When in the source system an object (material) is changed (e.g. change of the description) if change pointers are activated, the material is flagged as "changed" and using change pointers the material update will be sent to all the system that are configured to my sinchronized with master data. This is not for tracing like change document but for master data distribution
You can find more details on help.sap.com:
- <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/2a/fa015b493111d182b70000e829fbfe/frameset.htm">Change Documents</a>
- <a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/12/83e03c19758e71e10000000a114084/frameset.htm">Change Pointers</a>
Hope it helps,
Kind Regards,
Sergio

Similar Messages

History Documents, Change Documents and Potential documents in PGS

What are History Documents, Cleared documents, Change Documents and Potential documents in PGS.
I need to retrieve history documents from tables BSIK, VBKPF and RBKP. Which fields are considered as History documents from these tables?
How to retrieve Cleared documents from Table BSAK? Which fields from this table can be considered as cleared documents.
How to retrieve Change documents from Table CDPOS? Which fields from this table can be considered as change documents.
How to retrieve Potential duplicate documents from tables BSIK, VBKPF, RBKP? Which fields from this table can be considered as potential duplicate documents.

In order to include audio and video, you need to export it into a format that supports this, and you need to have a program to open it that supports audio and video in exactly the way it was included (not all flavors of format have the same features).
PDF does not do this. I'm not sure about .doc (but I doubt it).
EPUB does support audio and video, but I have no idea how easy it is to use (nor how reliable).

No change document and no user exit is found   for CK11N tcode

Dear All,
    After execution of the transaction CK11N in CDHDR table i dint find any entry for change document.
But there is a business object for this transaction :BUS2044 which has no event .
As there is no event in the business object and there is no change document also so how i will trigger this business object for CK11 transaction.
I serached for user exits also but i dint find any.
So can any body pls tell me how to trigger the business object for the transaction CK11.
Thanks
sharmistha
Message was edited by:
        sarmistha das

If there is no event it is difficult to trigger an event. So in any case you have to create your own subtype of BUS2044 and define the event you want to create.
If there are no user exits (I assume you have also looked for user-exits of type BTE and BAdI, even substitutions) you are perhaps out of luck? Being out of luck in this context means you will have to resort to a modification.

Change document and triggering workflow

Hi,
There's a z-table in ERP. The requirement is to send a notification to the Java server whenever there is a change in the data content of this table.
Can anyone describe the steps to be followed.
Thank you.

Hi Pavan, Sharath,
Now that I understand the concept of change documents, I have doubts about it's utility. I mean I did not find it to be a very good feature. The reason I say that is that one has to code for everything. It becomes the developer's responsibility to get the old record and the new record and pass these to the WRITE_CHANGE_DOCUMENT function. In addition, the developer also has to pass an indicator representing what kind of change is it - insert, update, delete.
The only utility I see is when you have maintain an archive of the changes that happened in a table's content over a long period. In that case, you could refer to the CDHDR and CDPOS tables and find out what change occurred on which date.
Your comments would reinforce my understanding of the concept.
Thank you.

Guidelines on Change documents and Status Management

Hi Friends,
 I am not sure whether this is the right question or not but I am in desprate need of it.
 The thing I find my self no where sometimes when I think of working on Chagne documents and Status management. I have been into WF for about 2 years. but never got a BEST chance to work on complicate workflows.
 Can anyone give me some ways or links where I can find clear difference between change docs and status mngt and how to work on those ?
 I did search in blogs but didnt find much. so posting a new thread. sorry for the inconvenience.
Thanks
Reddy

Hi Reddy ,
Go through these links.
the Tcode for Change document is swec,
http://help.sap.com/saphelp_47x200/helpdata/en/c5/e4aee2453d11d189430000e829fbbd/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/8c/1923d1932b11d2a5ea0060087a79ea/frameset.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/db/7a2a40ce93185de10000000a1550b0/content.htm
Thanks & Regards
Hari Sankar M

ABAP OO Class and Change Documents

I have created a class based on the IF_WORKFLOW interface. I created a couple of events. I created a workflow task assigned to a custom method of the class. I setup the Material Change Document to trigger the class event when there is a change. The workflow task does trigger when I change a material, but I don't know how to pass the key of the Change Document (matnr) to the workflow task/method using the ABAP OO Class interface. Any help?
Thanks,
Kenneth

Thanks for the reply Florin. Yes, I have seen Joclyn Dart's Whitepaper and blogs. They are very helpful, but I haven't seen much information within them about Change Documents. I tried your suggestions, but the material key is still not being filled when I trigger the change document and workflow task using tcode MM02.
Here is what I have done:
Created an Attribute 'Material' type mara-matnr and checked 'Key Attribute'.
Created an Attribute M_POR type SIBFLPOR.
Here are the methods:
Constructor with parameter 'Material' *
METHOD constructor.
me->m_por-catid = 'CL'.
me->m_por-typeid = 'ZMM_WF_MATTEC'.
me->m_por-instid = me->material.
ENDMETHOD.
Find_by_lpor with parameters LPOR and RESULT (default params) *
METHOD bi_persistent~find_by_lpor.
DATA: p_material TYPE matnr.
MOVE lpor-instid TO p_material.
TRY.
      CREATE OBJECT result
        TYPE
          zmm_wf_mattec
        EXPORTING
          material      = p_material.
    CATCH cx_bo_error .
      EXIT.
ENDTRY.
LPOR with parameter RESULT (default param) *
method BI_PERSISTENT~LPOR.
result = me->m_por.
endmethod.
ENDMETHOD.
Custom method MAT_CHANGED with parameter 'Material' * (not coded yet)
This is the task being triggered by the Change Documents *
METHOD mat_changed.
ENDMETHOD.
Edited by: Kenneth Moore on Nov 4, 2008 11:00 AM

Change documents optimization Business Partners and Products

Hello guru's
Does anyone know if it is possible for the objects Business Partner and Products to make settings on which changes are recorded in the change documents and which are not?
e.g. I want a change in the field "Last Name" to be recorded in a change document but if a change is made in the field "House number" I don't want it to be recorded in a change document.
Anyone know if this is possible in standard SAP? We are now on 5.2, but will be on 7.0 in a short time.
Thnx for the help!
Joost

Hi, Joost
I think it's possible.
First, Check this program changedocu_read and these tables: CDHDR, CDPOS, DBTABLOG.
Denis.

JEST table and status change document OPL8

Hi Experts,
1. I created a prod order and released it and saved. went to AUFK and got the object number to pass in JEST table. System shows no values found.I was expecting a record for the same. do I need to do something to populate JEST table?
2. In OPL8 under implementation tab, there is something called status change documents. do I need to configure OCM to use these change documents? if the answer is no, then what is the difference between these change documents and OCM change documents?
thx in advance

swathi.rege wrote:
2. In OPL8 under implementation tab, there is something called status change documents. do I need to configure OCM to use these change documents? if the answer is no, then what is the difference between these change documents and OCM change
The settings in OPL8 will just determine if system should write the change logs of status to table tables CDHDR and CDPOS (for audit trail). Entries will appear here CO03 >> Header >> Status changes
I think you opened up different windows of different boxes (DEV, QAS etc) and probably created in production order in DEV and checking status in QAS.
Edited by: Jeevan Sagar on Feb 12, 2012 10:09 PM

Change Document - Insert new value / Delete

Hi,
Jus need a quick clarification on change documents -
1. insert opertaion. I have created change documents and able to record the changes in CDPOS when changing or updating the existing values in table. But when i try to insert into the table the CDPOS is updated only with key entries and how can i track the values tht are inserted for non key fields in table? is there anything to be inlcuded in the pgrm for insert operation so tht CDPOS relflects all the values inserted?
2. delete operation - CDPOS not recording the deletion of the record!!!
any pointers for troubleshooting this issue?

The insert operation only records the key, the actual values of the non-key fields can be found in the application table itself.
The delete operation should be recorded as well. Is it your custom transaction? The application logic is responsible for making the correct calls to the functions modules that write CDHDR/CDPOS entries. Maybe you have a bug there somewhere.
Thomas

What is meant by change pointer and change request

hi,
what is meant by change pointer and change request in sap r3
plz can u any one notes or link on this , or if possible briefly tell about this..
i am looking for clear idea on this..
thanks
Ruban

With respect to Dictionary Change pointers means all the changes done to dictionary objects.
All the change logs with respect to tables are stored in CDHDR and CDPOS table
Change Pointers in broad sense are used with respect to IDOC
Change Pointers & Reduction of IDOCs.
Applications, which write change documents, will also try to write change
pointers for ALE operations. These are log entries to remember all modified
data records relevant for ALE.
Following Steps must be followed in case of Change Pointer.
1) Goto Transaction BD60.
Note down the Details of the Message Type for which change pointer has to activate. Details like Function Module, Classification Object, ALE object Type etc.
E.g. ZDEBP3
2) Next step is goto transaction BD53
Click on change button.
First select the segment for which the fields has to modified (either remove or
add ).
It will show the fields in a pop-up window where the user can select, deselect the respective fields.
Save the settings for the Message type. Dont forget to activate the change pointers by clicking Activate Change pointers button on the main screen.
3) Once the activation is done system will reset the settings for the Message type in Change pointers (BD60). Maintained the old settings for the Message type.
Check this FAQ
. Do you really need change pointers?
You need change pointers to distribute changes with the ALE SMD tool. If you do not use this tool, you do not need to write change pointers.
You can deactivate change pointers and activate them again with the transaction BD61.
2. Do you really need to activate change pointers for this messages type?
If some messages types are no longer to be distributed by change pointers, you can deactivate change pointers for this messages type.
You can deactivate change pointers for the message type
and reactivate them again.
For reduced message types, deactivate the change pointer with the
Reduction tool (transaction BD53).
3. Are there still too many change pointers to be processed?
The change pointers are analyzed with the transaction BD21 or the report RBDMIDOC in ALE and flagged as processed. If the change pointers are created periodically, this report should also run periodically.
4. Are no longer required change pointers reorganized in time?
The report RBDCPCLR (transaction BD22) to reorganize the change pointer should run periodically. Depending on how many change pointers are created or processed, you can schedule the background job hourly, daily or weekly. You should delete all obsolete and processed change pointers. You can also use this report for specified message types.
We come across change pointer technique while dealing with master data distribution thru ALE/IDOCs
When we want to reflect changes made to master data(i.e customer master, vendor master, material master ...) visible to other clients listed in customer distribution model, we follow change pointer technique.
What is customer distribution model?
A customer model depicts various messages (master data, transactional data) exchanged between the systems and establishes a sender and receiver of data
A customer model is always maintained on any system for the entire distributed network of SAP systems, so it must be distributed to various systems in the distributed network.
These r some details regarding change pointer technique which u may find it usefull.............
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master, vendor master & sales orders. changes made to a document are recorded in the change document header table CHDHR, and additional change pointers are written in the BDCP table for changes relevant to ALE. BDCPS table stores the status of changed documents processed or not.
The process for distributing master data using change pointers involves the following steps.
The application writes change documents. SAP maintains change documents for
several objects in the system, such as materials, customers, invoices, and bank data, to provide an audit trail for changes made to an object. A change document object represents a set of tables for which changes are recorded. For example, the change document for the material master is named MATERIAL and it contains the various tables of the material master object, such as MARA and MARC.
When an application transaction makes changes to an object, the application writes change documents, which are stored in the CDHDR and CDPOS tables for each change made to an object.
Tip
Execute transaction SCDO to see a list of change document objects and
their tables.
The SMD (Shared Master Data) tool writes change pointers. When changes are made to an object, the SMD tool checks the ALE settings and consults the ALE distribution model to determine whether a receiver is interested in the object that was changed. If the system finds an appropriate receiver, the system creates change pointers in the BDCP table that point to change documents in the CDHDR table.
The ALE programs analyze change pointers and generate IDocs. SAP provides
standard function modules that read the change pointer table and generate IDocs for the objects that were changed. These programs are designed to ignore multiple changes and create only one IDoc. For example, if a material is changed four times before the function module is invoked, only one IDoc with the latest data from the material master data is created. The function modules are invoked by a standard report, RBDMIDOC. The selection parameters of this report allow you to specify the message type for which change pointers are to be analyzed. Configuration
you must carry out the following configuration steps to enable master data
distribution based on changes to the object.
Step 1: Enable Change Pointers Globally
Transaction: BD61
This option enables the change pointer process globally. Make sure that the flag is checked.
Step 2 :Enable Change Pointers for a Message Type
Transaction: BD50
This setting is required for activating change pointers for a specific message type.
make sure that the Active flag is checked for your message type.
Step 3 :Specify the Fields for Which Change Pointers Are to Be Written
Transaction: BD52
For standard master data objects such as the material, customer, and vendor objects, SAP already provides a list of fields for which change pointers are written. If you are satisfied with the standard set of fields, you can skip this step. If you want to add new fields, you must add entries for the required fields. If you are not interested in IDocs being generated for changes to a particular field, you can remove it from the list. For example, if you do not want to distribute the
material master for changes made to the Catalog Profile (RBNRM) field, you can delete this entry from the table.
Step 4: Changing a Field in the Master Data
Change a field in the master data object for which the change pointer is enabled. For example, if you change the net weight of a material in the material master data, a change pointer is written.
Tip : You can verify a change document and change pointer by viewing entries in
tables CDHDR and BDCP, respectively.
Step 5 :Executing Program RBDMIDOC to Process Change Pointers
Execute program RBDMIDOC to initiate the process of generating an IDoc. On the selection screen, specify the message type. For example, you can specify MATMAS. After you execute the process, it displays the number of entries processed.
Note :
Normally, you schedule this program to run frequently and start IDoc
generation for different message types.
Step 6 : View the idocs in WE02/05

Error while approving change document(TR lost project code)

Hi All,
I am having issue in change document approval, when we are approving change document for unit testing or if release management approving change for pre-production or production approval, we are getting error, I started coming from last two days only,\
when I did detail analysis, in all transports project code related to change document, disappear
although if I create new change document, project code appear,
Do we have way to solve this issue?, I even not able to decouple the transport from change document, it giving error, do we have way where we can resync change document and transport?
Dinesh

Hi All,
Do anyone have some solution for this issue?, it is bigger than I thought, I can check it impacted all systems, and all transports, all transports seems to issue they lost project code in it we rollover maintenance cycle last week and this problem started from their, we put charm master note and few other charm fixes(notes) last week,
this problem not coming any new change document, but all change document created before rollover impacted
Dinesh

Change documents for customer Z table - serious help wanted

Hi all,
I am no beginner and I don't expect any comments from beginners.
Situation: My customer wants to replace the material valuation transactions MRN1 MRN2 MRN3 due to bad performance and locking problems with own developed programs.
The valuation results will be stored in a customer Z-Table on a monthly base. For auditing and transparency purposes, this Z-table has to get a change object and the update routines will have to write change documents.
Due to the expected size of the new Z-table, it is not advisable to simply switsch on table logging.
In this huge project (and in none I participated!) nobody ever implemented the change document process for a Z-table. BUT EVERYBODY CAN TELL YOU THI IS NO PROBLEM AT ALL.
I read some documentation at SAP and serached for threads or blogs here. I could not find anything desribing that in depth.
So before I start, I'd be happy to get some hints from people who created own change documents and implemented the process. Links to documentation and other helpful pages are also welcome.
If I can keep the process simple, I'd like to create a BLOG on this - because I think, in the future it will get more and more difficult to pass the auditing process with undocumented features and uncontrolled table changes.
TIA.
Regards,
Clemens

Hi,
Please check this thread.
http://www.sapdevelopment.co.uk/tips/changedoc/cd_createch.htm
Once you create your change document object using generate update pgm option then please check the WRITE document fm.
I have done this long back i am updating CDHDR and CDPOS for 2 table YATT and YATTPLANTS. Here YATT have single record (header table) and YATTPLANTS have multiple records (item table)
function yatt_write_document .
call function 'CHANGEDOCUMENT_OPEN'
 exporting
 objectclass = 'YATT '
 objectid = objectid
 planned_change_number = planned_change_number
 planned_or_real_changes = planned_or_real_changes
 exceptions
 sequence_invalid = 1
 others = 2.
case sy-subrc.
 when 0. "ok.
 when 1. message a600 with 'SEQUENCE INVALID'.
 when 2. message a600 with 'OPEN ERROR'.
endcase.
if upd_yctc ne space.
 call function 'CHANGEDOCUMENT_SINGLE_CASE'
 exporting
 tablename = 'YATT '
 workarea_old = o_yatt
 workarea_new = n_yatt
 change_indicator = upd_yattc
 docu_delete = 'X'
 exceptions
 nametab_error = 1
 open_missing = 2
 position_insert_failed = 3
 others = 4.
 case sy-subrc.
 when 0. "ok.
 when 1. message a600 with 'NAMETAB-ERROR'.
 when 2. message a600 with 'OPEN MISSING'.
 when 3. message a600 with 'INSERT ERROR'.
 when 4. message a600 with 'SINGLE ERROR'.
 endcase.
endif.
if upd_yctcauthplnts ne space.
 call function 'CHANGEDOCUMENT_MULTIPLE_CASE'
 exporting
 tablename = 'YATTPLANTS '
 change_indicator = upd_yattplants
 docu_delete = 'X'
 tables
 table_old = yyattplants
 table_new = xyattplants
 exceptions
 nametab_error = 1
 open_missing = 2
 position_insert_failed = 3
 others = 4.
 case sy-subrc.
 when 0. "ok.
 when 1. message a600 with 'NAMETAB-ERROR'.
 when 2. message a600 with 'OPEN MISSING'.
 when 3. message a600 with 'INSERT ERROR'.
 when 4. message a600 with 'MULTIPLE ERROR'.
 endcase.
endif.
call function 'CHANGEDOCUMENT_CLOSE'
 exporting
 objectclass = 'YATT '
 objectid = objectid
 date_of_change = udate
 time_of_change = utime
 tcode = tcode
 username = username
 object_change_indicator = object_change_indicator
 no_change_pointers = no_change_pointers
 exceptions
 header_insert_failed = 1
 object_invalid = 2
 open_missing = 3
 no_position_inserted = 4
 others = 5.
case sy-subrc.
 when 0. "ok.
 when 1. message a600 with 'INSERT HEADER FAILED'.
 when 2. message a600 with 'OBJECT INVALID'.
 when 3. message a600 with 'OPEN MISSING'.
* WHEN 4. MESSAGE A600 WITH 'NO_POSITION_INSERTED'.
* do not abort, if positions are not inserted!!!
 when 5. message a600 with 'CLOSE ERROR'.
endcase.
endfunction.
a®

How to get terminal address along with Change document header

Dear All
My client want a report of the frequencies of a sales document changes along with terminal address. In table CDHDR i can get user name, date, t-code but not the terminal address. So requesting to guide me of how to get the terminal address from which terminal the document has been updated.
Appropriate answer will be rewarded.
Regards
Kingshuk
Edited by: Kings_Roy on May 31, 2010 11:02 AM

I don't think this information is kept in change documents. So for the change documents that are already created, you cannot get this information.
For future however you can do some code changes to get this information.
Function module TH_USER_INFO can return terminal name as well as IP address for a given client and user.
All you have to do is either store this additional information along with change documents. For this i think you can check the FMs that are writing SD change documents.
OR
You can use user exit exit SUSR0001 (User exit after logon to SAP System) to call this Function (TH_USER_INFO) at user logon and store this info in a Z table. Later when you are reading change documents, you can get user name, date time from change document and search this Z table for respective user Terminal name and IP Address.
This is not a complete solution but i hope it will direct you to a solution.
cheers.

Material bapi custom field change to be logged in change document

Hello all,
I have just added a custom field to MARA table (materials), and updated it successfully via BAPI_MATERIAL_SAVEDATA.
I would like now to log changes via change documents but problem : after having changed value from "A" to "B" for example, I don't see the changes (to do this, I call function CHANGEDOCUMENT_READ with parameter OBJECTCLASS = "MATERIAL" and get results from returned EDITPOS parameter).
What is surprising me is that I can see changes of other standard and custom fields (this was done by other people in my company 2 years before but I don't have any trace what they did).
Do you have any idea what customizing need to be changed or what else need to be done, to log changes of new custom fields into change documents?
Thanks a lot.
sandra

In this transaction, there is nothing related to fields; there are only objects (like MATERIAL) and tables (like MARA).
I can't see anything which makes the difference between our 2 custom fields MARA-ZZCOLLANA (which is logged in change documents) and MARA-ZZSSCOLL (which is not logged in change documents).
For info, my SAP version is R/3 46C.

Change Pointers - adding a new field to existing Change Document

Hi,
We have a requirement to capture the changes made to the Material object through the transaction C223. The changes to field MKAL-PRFG_F have to be captured.
There is an exisitng Change Document Object - MATERIAL. This is included in Message Type MATMAS. These are the steps we have done:
1. In SCDO - added the Z structure to the Change Document Object - Material. [Z structure contains the field MKAL-PRFG_F. Change pointer option is checked for this Data element.
2. Created a Z Message Type with reference as MATMAS.
3. In BD52 - we have listed the fields for the new Z Message Type created.
4. The Change Pointers - reactivated after the steps are done.
The changes to the field MKAL-PRFG_F through C223 Tcode are not recorded in BDCPV table.
Have we missed any steps here?
Thanks,
Pallavi

HI,
I don't think a new zmessage type is required in this case.. is the structure added to MARA table??The change document programs are there which triggers the iodcs... In SCDO transaction code , click on generation info for MATERIAL.. You will find the includes. The FM MATERIAL_WRITE_DOCUMENT creates entries in CDHDR and CDPOS, if we maintain entries in BD52 , the entries wil be written in BDCP and BDCPS tables.
Try to add your structure in MARA table as append strucre and then you can debug the IDOC from WE19 and use the FM "MASTERIDOC_CREATE_SMD_MATMAS" and then you also need to switch on Update Debugging on, to debug the changes in update FM MATERIAL_WRITE_DOCUMENT.
Please see if the change is reflected or not....
ELSE.
may be you need to create a new entry in SCDO and do all the ALE configurations for change pointers.
Please find the link for change pointers and also you can get lot of information on change pointers in SCN.
http://help.sap.com/saphelp_nw70/helpdata/EN/12/83e03c19758e71e10000000a114084/content.htm
Regards,
Nagaraj

Change documents and Pointers

Similar Messages

Maybe you are looking for