Deactivate Change Pointer

Dear All,
I am facing a problem. The problem says:
When we are changing any business partner related information/s(or some other informations), the change pointer is autometically getting fired. For eg., if I change the contact partnet value in transaction FPP2, autometically the change values are getting stored in table CDHDR, CDPOS. That is drastically dropping the performance. I tried to deactivate the change pointers through BD50, but those message types available in BD81 are not available in BD50. This is standard SAP and no ALE/IDoc process. Is it getting fired through any FM "CHANGEDOCUMENT_CREATE".
Expecting your valuable suggestions.....
Best wishes,
Atanu

Hi Atanu!
Change pointers are stored in BDCP / BDCPS (or BDCP2), change documents are stored in CDHDR / CDPOS.
Change pointers can be deactivated by customizing - because they should be trigger for a process.
Change documents can be deactivated by changing attribute of data elements in SE11. Sometimes (really seldom) BAPI or IDOC have a flag 'no change documents' for migration purpose. If you don't have such a flag, but you are doing a (hugh) migration, think about a modification: if user NE 'MIGRATION'.
CALL changedocument_create...
endif.
In case of normal business - maybe you have to live with it, or the modification of the data elements will help.
Regards,
Christian

Similar Messages

Deactivate change pointer in particular article type

Dear all expert
We are using IDOC type Wp_plu02 for outbound article processing we also activate change pointer setting on IDOC type wp_plu02 but now we want to do deactivate change pointer in particular article type (project articles) how we can do it
Thanks
Amit Shivhare

Dear Vinodh Balakrishnan
thanks For quick reply
but we dont want to deleate change pointer
i want to do my projects type articles not flow in outbound
so i want restruction on prticulay article type
Thanks
Amit Shivhare

What is the use of change pointer technique in IDOC

hi
could anybody suggest me
what is the use of change pointer technique and how to use it
thank you
kalyan.

Change pointers are used for changes to the master data objects are flagged for distribution by SMD Tool.i.e.shared Master Data.
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
The SMD tool is connected to the change document interface. If the master data changes are to be distributed, the application writes a change document. The contents of this are passed to the SMD tool. The tool writes change pointers, reads the application data and creates the master IDoc.
The master IDoc is then passed to the ALE layer, which sends it to all interested systems.
The change pointer tables (BDCP und BDCPS) should be as small as possible. Use as few change pointers as possible and delete change pointers which you no longer need.
You can increase the rate of processing by using the Analyze Change Pointer and Reorganize Change Pointer functions.

Restrict IDoc creation by using deactivate change pointers

Hi Experts,
I am trying to restrict the creation of IDOCS by deactivate the change pointers from a ztable. if the record in ztable and BDCP table match then i should deactivate the change pointer. And restrict the creation of Idocs.
pls, suggest me soon... its urgernt.......
Regards,
CHK

Maybe using program RBDCPCLR to delete change pointers you don't want to use?

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

Change pointer for HR master data is not getting generated in table BDCP

Hi,
I have done all the required configuration for change pointer for HR master Distribution and it was working fine few days back. Now suddnly it has stopped working.
Can anyone assist me on how should i debug it.
Thanks
Sunil Singh

Hi Shital,
Thanks for your Reply.
I am not able to find that path in SPRO
Basic Functions-> application Area
And Also My change pointer configuration was working properly and it suddenly stopped working.
I mean to say all the required settings was done previously.
Anyways kindly let me know how should i proceed.
Thanks
Sunil Singh

After successful install, all my adobe cc docs, when open, change pointer arrow, i-beam and window to oversize. When doc closes all return to normal size. I'm on a PC. Screen res set to medium 1920x1200. Any ideas how to fix?

After successful install, all my adobe cc docs, when open, change pointer arrow, i-beam and window elements to oversize. When doc closes all return to normal size. I'm on a PC. Screen res set to medium 1920x1200. Any ideas how to fix?

Ok thanks Linxup I would recommend posting in the respective forums for each of those software titles as opposed to the Creative Cloud Download & Install forum. The relevant forums are as follows:
InDesign - InDesign
Illustrator - Illustrator

Suppress Non Changed Fields in change pointer triggered IDOC

I have a requirement to clone message type MATMAS as ZMATMAS. This ZMATMAS is the message type I used to create change pointer triggering outbound idoc for change/create of materials.
When i change a material, all fields are sent instead of the fields only changed(of course key fields should be sent as well). Is there a way via configuration that I can suppress fields which are not changed? Or do i need to clone FM MASTERIDOC_CREATE_SMD_MATMAS and suppress the fields via program
Thanks in Advance!

i'll clarify the requirement again.
Let say i changed a field BRGEW in the material master.
Currently, all the segements which contains BRGEW is sent, but these segements contains other data which are not changed in the material master.
How do i suppress it?
Thanks,

EXCHANGE_RATE with change pointer

Hello Experts,
I saw that there is no option to define the message type EXCHANGE_RATE for change pointer
My question is: how can I get a partial idoc when there is a change in the exchange rate?
Is it possible?
Thank you,
Boaz

Hi Jignesh,
"It is ideal that we dont change the Exchange Rate at the time of POsting Invoice to accounts."
How you have addressed the issue. could you explain.
Thanks & Regards
Sri

Issue with the change pointer for the reduced message type ZMATMAS

Hi All,
I have created reduced message type ZMATMAS for the MATMAS to create a Idoc when change or insert material master data fields( MARA-LAENG, MARA-BREIT, MARA-HOEHE) . My Problem is that the Idoc is generated with the status (03) but the fields(LAENG, BREIT,HOEHE) are not getting fill with the values. They are always filling with the values '/'). I have done the following steps to create idoc for the change pointer. Please check whether i have missed some steps.
1.     Create reduction maintenance ZMATMAS (Tcode BD53)
keep the default selected segments E1MARAM, E1MAKTM
2.     Add following data to maintain table view for the message type ZMATMAS (Tcode BD52)
Object      Table Name     Field Name
MATERIAL       MARA      KEY
MATERIAL     MARA     LAENG
MATERIAL     MARA     BREIT
MATERIAL     MARA     HOEHE
3.     Activate particular change pointer in BD50
Message Type       Active
ZMATMAS         yes
4.     Activate change pointers u2013 Generally (Tcode BD61).
5.     Assign Segment fields to change document fields (Tcode BD66 )
Segment Type     Field Name     Object     Table Name     Field Name
E1MARAM     BREIT     MATERIAL     MARA     BREIT
E1MARAM     HOEHE     MATERIAL     MARA     HOEHE
E1MARAM     LAENG     MATERIAL     MARA     LAENG
6. I have done the distribution model settings (BD64) and the idoc configurations
1.     Logical System
2.     RFC destination
3.     Create port
4.     Create partner profile
7. I changed the fields in material master data(Tcode MM02) and I executed the Tcode BD21.
Idoc is generated but the fields are not getting fill with the values
(Note: some fields are filled with values e. g material number, material description)
I checked the Idoc data segment E1MARAM (WE02)
Fld name   Fld cont.
LAENG       /
BREIT       /
HOEHE      /
Can you please let me know the issue
Prad

Issue is solved when I select the segments and the fields in the segments (Tcode :BD53)
Prad

ALE change pointer error - master data

Hi friends,
While loading master data (customer,material and order number) all delta,we faced the error "ALE change pointers are not set correctly".
In the discussions posted earlier,it was said that the change pointer in BD61 activation would solve the issue.
If i do that now,whether my other delta loads will be affected or it doesnt have any relation to my other transactional deltas.Pls clarify me.
Also explain me the reason fot this error.
Thanks & Regards
Ragu

thanks ajay for your input
regards
ragu

How to find - Customer Master IDoc was created Manually or by Change pointe

Hi all,
I have an IDoc(Customer master) number (which I have taken from the payload in SXMB_MONI). I would like to know whether this has been created by a user manually(BD14) or by a change pointer.
Please help.
Cheers
danus

Hi Vardharajan,
Yes I agree with you. What I mean by IDoc created by change pointer is - 'IDoc generated because a change(pointer) is tracked by the system', in other words, due to some change made to the data.
As you know, the other option of creating IDoc is by BDxx transaction. This option is usually used to push (unchanged) data.
So in essence, what I am interested to know is , has the IDoc been generated because someone made a change using say, VD02 / XD02 or pushed the data manually.
Please do ask, if anything is not clear.
cheers
danus

Change pointer perfomance issue(bd22)

Hi,
we are using message type HRMD_A to transfer the employee change data using the program RBDMIDOC. we are checking two table BDCP n BDCPS, but because of large number of data we r facing a perfomance issue here. I read in one forum about transaction BD22 which deletes the change pointer from these tables, but is it safe to use? and also what is the obsolete change pointer?
Thanks in advance for ur inputs.

Hey,
It is advisable to reorganize change pointer tables at regular intervals for better performance of programs accessing the BDCP* tables.
BD22 is a standard report delivered by SAP and it is absolutely safe to run this report. It also has o test run option. You could always run the report in test mode to analyze the data the report had selected for deletion.
Obsolete change pointers are those which have been created up to the specified date and time. In BD22, if this checkbox is marked, obsolete change pointers will be reorganized regardless of whether they have yet been processed.
Processed change pointers are those which have been processed in the specified period (date and time). If this checkbox is marked, the processed change pointers are reorganized.
-Kiran
*Please mark useful answers

Idoc trigerring with change pointer under conditions

Hello dear experts
Could you please tell me how can i trigger an outbound idoc using the change pointer ( RBDMIDOC program)?
I have to generate the ARTMAS outbound idoc ONLY when the material status which is the table MARA is set to a certain value.
I can manage to trigger the outbound idoc but i did not manage to restrict this triggering according to the value of the material status fields.
Thanks for all your answers.
Best Regards.
Yannick

I tested using filter on Dist Wh and change pointers - for us, Dist Wh filter for material set on plant. When we made change to matierial, only if change to plant was made, so plant was included in idoc segment, did the filter work. If change material description, plant not on idoc segment so was sent . Looking for alternative...

Activate change pointer for a new screen field in MM42/41

Hi,
I created a new screen field for Article master(MM41/42/43) under basic data. If there are changes made to this new field how will the system create a corresponding IDOC? does this have something to do with the change pointer thing?
Thanks,
Jeff

Hi Jeffrey,
first of all got transaction SALE :
ALE
-> Modeeling and Implementing
-> Master Data Distribution
-> Replication
-> Activate Change Pointer generally
Check if Changepointers are generally on.
Then goto BD50 and activate change pointers fpr message type.
Finally goto BD52 and check if your field is "watched".
After that you can generate idocs from BD21.
Hope it helps.

Deactivate Change Pointer

Similar Messages

Maybe you are looking for