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

Similar Messages

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

Reg; change pointer

hi gurus,
i am facing one issue for outbound. when i am replicating the master data zdebmas. Using zca1o002, idocs are succefuly genarated no issues.
but whan i do changes in master data.,those changes are rplicationg RBDMIDOC, idocs are genarated and changes are stored in BDCP2 . And my probelumm is some segmets are missing when i am replicating the changes.
is there any config issue or anything kinldy help me for to resolve this issue.

Hi Raghav,
I have a few suggestions to make with regard to this isssue:
- Firsly please review note 328355.
- Some general information on txn BD22 which you may find useful:
<< Moderator message - Cut and paste response from http://www.se80.co.uk/sapreports/r/rbdc/rbdcpclr.htm removed. Plagiarism is not allowed in SCN >>
Consider executing BD22 each night to alleviate this problem as a fix should the above notes not resolve this issue.
In relation to the size of the BDCP tables and the amount of change pointers generated please review the following information:
It is recommended that these tables be kept as small as is possible by scheduling report RBDCPCLR to run at regular intervals. Please schedule this report to run regularly and you should not encounter this problem again.
Please gothrough the below notes on this topic:
513454 REP: High-performance operation with change pointer
420562 REP: Reducing the scope of data for change pointers
As you will see these notes deal both with how best to handle obsolete change pointers in these tables but also how to ensure that your system is configured so that un-necessary change pointers are not generated in the first place. This latter point is of course of great releavance also.
Review these notes carefully together with your online help files. Please ensure that you implement the above notes and recommendations and see then if this problem persists.
Thanks & Best Regards,
Mohammed Hussain.
Edited by: Rob Burbank on Oct 19, 2011 10:43 AM

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

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

Need help in Change pointer creation

Hi Guys ,
I have one issue ..Change pointer getting created for Vendor if i create it from the Custom Program But it has some problem while Using LSMW ..
I just want to Know whether is there any Config issue with LSMW,,
Please advice me how to slove this issue ..
Thanks in advance.
Prabhu.

hi
good
go through this link ,hope this ll help you to solve your problem
http://sap.niraj.tripod.com/id51.html
reward point if helpful.
thanks
mrutyun^

What is change pointer in ALE ?

Dear Guru,
1. What is change pointer in ALE and how to configure it ?
The process of configure please guide me !
Tanks and Regards,
Subash.

Hi,
Change pointers are R/3 objects that mark changes to SAP master data. Change pointers are managed by mechanisms in a Shared Master Data (SMD) tool and are based on Change Document (CD) objects. CD objects record the changes occurring to master data at a field level. These changes are stored in tables CDHDR (header table) and CDPOS (detail table). ALE configuration provides a link between CD objects and change pointers. Internal mechanisms update tables BDCP and BDCPS, which host the change pointers. While CD objects are application-data-specific, the processing status of change pointers is message-type-specific. Also, the ALE change pointers are activated first at a general level and then at the message-type level.
ALE provides powerful capabilities to capture changes occurring to master data and to distribute them via the IDOC interface. This feature can be used to keep two or more systems synchronized with respect to master data.
Steps to configure change Pointers:
1.Activate the change pointers globally(BD61)
2.Activate the change pointers for individual message types(BD50)
3.Schedule the program RBDMIDOC to run periodically on the sending system.
To Delete Change pointers use transaction BD22 and the standard program is RBDCPCLR
Remember You can see a check box in Further characteristics tab of the data element ( se11>enter data element>Further characteristics tab) for change document.
This check box is to bo checked to trigger change pointers.
please check out the following link for more information it might help you
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
http://help.sap.com/saphelp_470/helpdata/en/dc/eb683c00e8a646e10000000a11402f/frameset.htm
Regards,
Satish

[svn:fx-trunk] 8020: Fallout from PARB changes - addressing 3 issues:

Revision: 8020
Author:   [email protected]
Date:     2009-06-19 16:02:54 -0700 (Fri, 19 Jun 2009)
Log Message:
Fallout from PARB changes - addressing 3 issues:
1.) http://bugs.adobe.com/jira/browse/SDK-21873 - Fixed
2.) missed PARB requested change, adjustSelectedIndex()/adjustSelectedIndices() are collapsed into a single method, adjustSelection()
3.) Excellent catch from Evtim - selectedIndices is now a Vector of ints instead of a Vector of Numbers (the PARB rename list had the right change!). Selection indices are always non-fractional, so we can get a slight savings by making this a Vector of ints.
QA: Yes - you'll need to update tests for point #3, and if you worked off the PARB rename list, then you shouldn't have to update for #2, otherwise you do.
Doc: Yes
Checkintests: Pass, as well as List/DDL mustella tests (except for 11 List tests that need selectedIndices to be changed from Vector.)
Reviewer: Evtim
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21873
Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/components/List.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/components/supportClasses/ListBase.as

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

Trigger Extra Change Pointer Update

We have Price and Quantity fields configured on PO for creating change pointer records.
When both of the values (NETPR & MENGE) are changed at the same time then everything works out great in BW but if let say only Price is changed then there are issues.
What I need is if only the Price is changed then during the update of the PO the record for Qty should also be created in change pointer tables (CDHDR & CDPOS). If you can briefly describe how to do it that will be great help and I will highly appreciate it.

I figured out a way to do this which was to implement the BDCP_BEFORE_WRITE BADI which allows you to interrogate a change pointer based on an IDoc message type before it's saved to the database. For starters, change pointers for message type CLFMAS must be activated in order for this to work, even though I'm not interested in those eventual IDocs.
In the IF_EX_BDCP_BEFORE_WRITE~FILTER_BDCPV_BEFORE_WRITE method of the BADI implementation, I was able to loop through all of the change pointers about to be created and this is where I was able to obtain the vendor number the classification is being applied to. I actually added another line to the internal table that's changeable in the method for CREMAS and it worked out well.
The only thing that was difficult was to debug this baby. No matter how you set the breakpoint, it just never hits it until I discovered it's called using an UPDATE TASK. I found an unorthodox method to debug this situation on the web which is to force an endless loop before your custom code such as.........
while sy-subrc <> 98.
endwhile.
<custom code here>
Once your process runs, it will be sitting in an endless loop in an update task which you can view in transaction SM50. From here, you can highlight this line then you can click on "Program Session > Program > Debugging" to debug your code. It's not something I was used to, but it allowed me to debug in the end. I would hope there's better ways, but this worked for now.
I hope this helps someone else!
Cheers,
Chris

Perfomance issue after update to 10.7.3

Hello everyone,
I have recently experienced major perfomance issues when it comes to graphical applications. I can't recall if it happened when 10.7.2 or 10.7.3 was released, but somewhere around then. And I can't determine if it was happening directly afterwards when the upgrade was done.
Watching a flash movie takes a lot of system resources and scrolling within the window the flash movie is barely possible. Before this hasn't been a problem at all. Playing a game, i.e Team Fortress 2, has gone from wonderful to non-playable. From having 60-80 fps to around 25-45 fps.
I am having a MBP 15.4 early 2011/8GB/2.0GHz. Running latest version of Lion 10.7.3
Anyone else that had the same problem? Anyone having a suggestion of what the problem might be?

Maybe it's Chrome. Maybe your update to 10.7.2 or 10.7.3 needs help. You could consider reinstalling Lion:
Reinstalling Lion Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion: Select Reinstall Lion and click on the Continue button.
Note: You can also re-download the Lion installer by opening the App Store application. Hold down the OPTION key and click on the Purchases icon in the toolbar. You should now see an active Install button to the right of your Lion purchase entry. There are situations in which this will not work. For example, if you are already booted into the Lion you originally purchased with your Apple ID or if an instance of the Lion installer is located anywhere on your computer.

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

Error when changing unit of Issue in material master

Hi,
When i am trying to change Unit of issue in Qualitymanagement view of a material using MM02 transaction, we got error message - "The unit of issue cannot be changed because the material is used in a BOM-------Mesage no. M3214"
Can anyone suggest what is the reason behind this. ?. how to avoid this error.
Thanks in advance.

HI Aditya,
"The unit of issue cannot be changed because the material is used in a BOM-------Mesage no. M3214"
The reason is that material is used as a component in BOMs with the present unit of issue as a unit in the bom line item.Unless you change that bom line item unit to its base unit ,system will not allow you to change the unit of issue in QM.
First check in which BOMs the material you were changing is used as a component.this you can do in transaction CS15.
then change the unit of measure used for the material in bom line item to base unit of measure.if one only one BOM is there change in CS02.if more BOMS are there do mass change in CS20.
Then try to change the unit o fissue.now system will allow you to do the changes.

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,

Change pointer perfomance issue(bd22)

Similar Messages

Maybe you are looking for