Customization for Change Pointer Mechanism in IDOC Programming?

Hi,
Can anyone suggest me that
We want to Maintain Master and Transactional Data in Different SAP Servers.I want to Send the Master Data to the other Server but before IDOC Creation i need to Display all Created or Changed Master Data then Our endusers will select Specific Master Data then only IDOC will create for that Master Data and Created IDOCs will send to the other SAP Server where Transactional Data is Maintained.
In Change Poinetr Mechanism it is not possible to see the Created or Changed Master Data before IDOC is going to be Created.But i need to Display the Master Data.
Please give me an idea to solve this or if you have any solution then send me.

Hi,
When you are change pointer the system itself will take care of sending the changed master data to your partner system and the user will not have any intervention. If you really wanted to have that then you need to use the change pointers to read the master data which is modified in a custom program and then display that on the screen. Once the user selects that master data records then trigger an IDOC for creating the idoc for that master data and also flag that master data record as processed in the SAP BDCPS standard table, so that the same record will not be picked. If you wanted to know how the change pointers piece of code is written go through the program RBDMIDOC and you can understand how the change pointers logic is written.
Thanks,
Mahesh.

Similar Messages

Reg : change pointer mechanism for triggering the IDOC for delivery note

Hi ,
I am working on a change pointer mechanism for triggering the IDOC for delivery note and will be using this message class DESADV.
So SAP has suggested for assigning the message class DESADV with the function module in MASTERIDOC_CREATE_SMD_DESADV in BD60 transaction code.
So I was looking to create this MASTERIDOC_CREATE_SMD_DESADV function module in SAP and SAP suggesting that we should create this MASTERIDOC_CREATE_SMD_DESADV function module as same as the function module MASTERIDOC_CREATE_SMD_MATMAS.
So do anyone knows that is there any tool has been provided by SAP for creating this function module MASTERIDOC_CREATE_SMD_DESADV in SAP system for triggering the change pointer mechanism for outbound Delivery.
Thanks !
Regards,
Kiran

Hi,
When you are change pointer the system itself will take care of sending the changed master data to your partner system and the user will not have any intervention. If you really wanted to have that then you need to use the change pointers to read the master data which is modified in a custom program and then display that on the screen. Once the user selects that master data records then trigger an IDOC for creating the idoc for that master data and also flag that master data record as processed in the SAP BDCPS standard table, so that the same record will not be picked. If you wanted to know how the change pointers piece of code is written go through the program RBDMIDOC and you can understand how the change pointers logic is written.
Thanks,
Mahesh.

Change pointer method in IDOC.

hi,
Plz tell me necessary steps for data transfer using change pointer method . after
Activate change pointers ,De-activate change pointers. run of program RBDMIDOC ,RBDCPCLR , what other programs we need to execute related to this change pointer method . I thin I m missing 2 more steps for this method..
Thanks.

Hello sranjna ,
These are the steps for change pointer :
1. BD61 :Activate change pointer generally .
2. BD50 :Activate change pointer for message type.
3. BD21 :Create IDOC type from change pointers.
4.Save the content : create a variant .
5.For automatically process:go to SM36 :Create a job with the program "RBDMIDOC " and the variant you created.
Also see the link if you want :
[http://help.sap.com/saphelp_nw04/helpdata/EN/12/83e03c19758e71e10000000a114084/frameset.htm]
Good Luck,
Boaz

Change Pointer to create IDoc

I wrote report program to create outbound IDoc. In the report, to capture create/ change I used table 'CDHDR'. Now I require below clarifications:
1.     Clarify the process of u2018Change pointeru2019 regarding IDoc.
2.     Is it recommended to use u2018Change pointeru2019 to create Outbound IDoc?
a.     If yes, then why do we write report or function module?
b.     Can we use custom message type in this process or only standard message types will work?

Hi
Change Pointer IDOC..??
Regards
pavan

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.

Disable Change Pointer to send Idocs to a specific destination

Hello All,
We are sending several Master data idocs to a couple of SAP systems. For one destination, we need to enable change pointers for those messages and send updates of any changes/ new data created.
However for the other destination, the ALE transfer is one time and is going to be scheduled on 'as needed' basis only. Since the change pointers are enabled, Idocs are going to be sent to both destinations and we dont want that.
Pls note that there are BADI like Idoc_Creation_check where we can disable Idoc creation based on destination, but that would mean that when the one time load is scheduled, no idocs will be sent. So we dont want to go that route. We can take off the partner profile config/ ALE model and configure it as required, but that would not be a good approach as well.
Please adivse if there is a method where we can disable Idocs (that are created due to change pointers alone !!) to a specific receiver.
Thanks for your help in advance!
Liz

Hello Liz,
... However for the other destination, the ALE transfer is one time and is going to be scheduled on 'as needed' basis only ...
I feel you can use the "Collect IDocs" output mode for this particular partner profile. (can be configured via WE20)
"As needed" you can process the collected IDocs by scheduling the program RSEOUT00.
Do you think there is a problem in this approach? If yes, please elaborate!
BR,
Suhas

Stop Change Pointer Trigger via Z Program

Hi,
I have a scenario where I need to deactivate the change pointers via Z program.
For eg. The change pointers need to be created if I triggered a deletion of records via other means. But the change pointers should not be triggered if I deletes the record via one Z program.
How can I achieve this?
Thanks & Regards,
Arun.

Have a look at BADI BDCP_BEFORE_WRITE. Essentially table BDCP is where these are written to so maybe you can stop this with this BADI i.e. before writing to the table.
This link below contains much useful advice on managing change pointers, and also the standard program for clenaing this up. Perhaps here you can find your answer: http://www.dataxstream.com/2009/07/are-you-properly-managing-your-change-pointers-part-2-a-simple-source-of-runaway-growth/

Additional flag for change pointer needed

i need to store an additional "characteristic flag" for some of the changes made to routings in TC CA02 .....
how can i get the actual CHANGENR of CDHDR/CDPOS to save it somewhere together with my flag for future reporting on routing-changes for this flag ?

Hi,
If the chnage document flag is ticked at data element lever automatically chnage pointers will be triggered and u cna seee the changes in table BDCP and status in BDCPS.
Reward ponts if useful.
Regards,
Sasi

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 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

Change pointers in ALE/IDOCs

Hi guys,
Can any let me know step by procedure to implenent change pointers using IDocs including ALE settings as i am new to this concept.
Any step by step example will be helpful. useful answers will be rewarded.
Thanks in advance.
Regards,
vinay

Change pointers is the one of the IDOC processing method in ALE.
In this once we make the config to any of messages type , if any changes are made in sending system then IDOC will be posted directly to destination with user interation.
Changes pointers are configured using BD50,BD51,BD53,BD61.
Change pointers are stored in tables BDCP and BDCPS (or BDCP2 in case of high-performance setting) - like CDHDR and CDPOS for change documents (but this is not a controlling table!).
1. 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 message type.
You can deactivate change pointers for the message type
and reactivate them again in transaction BD50.
For reduced message types, deactivate the change pointer with the
Reduction tool (transaction BD53).
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.
Most applications write change documents. These are primarily log entries in the
tables CDHDR and CDPOS.
Change documents remember the modified fields made to the database by an
application. They also remember the user name and the time when the modification
took place.
The decision whether a field modification is relevant for a change document is
triggered by a flag of the modified fields data element. You can set the flag with
SE11 by modifying the data element.
For the purpose of distributing data via ALE to other systems, you may want to
choose other fields, which shall be regarded relevant for triggering a distribution.
Therefore R/3 introduced the concept of change pointers, which are nothing else
than a second log file specially designed for writing the change pointers which are
meant to trigger IDoc distribution via ALE.
So the change pointers will remember the key of the document every time when a
relevant field has changed.
Change pointers are then evaluated by an ABAP which calls the IDoc creation, for
every modified document found in the change pointers.
The Change pointers are written from the routine CHANGEDOCUMENT_CLOSE
when saving the generated change document. So change pointers are automatically
written when a relevant document changes.
The following function is called from within CHANGEDOCUMENT_CLOSE in order to write the change pointers.
CALL FUNCTION 'CHANGE_POINTERS_CREATE'
EXPORTING
change_document_header = cdhdr
TABLES
change_document_position = ins_cdpos.
Activation of change pointer update :
Change pointers are log entries to table BDCP which are written every time a transaction modifies certain fields. The change pointers are designed for ALE distribution and written by the function CHANGE_DOCUMENT_CLOSE.
Change pointers are written for use with ALE. There are ABAPs like RBDMIDOC
which can read the change pointers and trigger an IDoc for ALE distribution.
The change pointers are mainly the same as change documents. They however can
be set up differently, so fields which trigger change documents are not necessarily
the same that cause change pointers to be written.
In order to work with change pointers there are two steps to be performed
1) Turn on change pointer update generally
2) Decide which message types shall be included for change pointer update
R3 allows to activate or deactivate the change pointer update. For this purpose it
maintains a table TBDA1. The decision whether the change pointer update is active
is done with a Function Ale_Component_Check
This check does nothing else than to check, if this table has an entry or not. If there is an entry in TBDA1, the ALE change pointers are generally active. If this table is empty, change pointers are turned off for everybody and everything, regardless of the other settings.
The two points read like you had the choice between turning it on generally or
selectively. This is not the case: you always turn them on selectively. The switch to
turn on generally is meant to activate or deactivate the whole mechanism.
The change pointers which have not been processed yet, can be read with a function
module.
Call Function 'CHANGE_POINTERS_READ'
The ABAP RBDMIDOC will process all open change pointers and distribute the
matching IDocs.
When you want to send out an IDoc unconditionally every time a transaction
updates, you better use the workflow from the change documents.
To generate the IDOCS in case of change pointers we need to use the standard report
RBDMIDOC
we need execute the follwing t.code
BD61:to activate the change pointers globally
BD50,BD52: to activate message types ,and to enable the fileds for change pointers
Hope this link will help you regarding Change Pointer...
http://help.sap.com/saphelp_erp2005vp/helpdata/en/ba/c9c1c31253ed4596e3bbb74922cd4a/frameset.htm
Change Pointer Configuration and extraction in HRPay.
Infotypes to be logged are in:
V_T585A,
V_T585B,
& V_T585C
Please view the table contents to understand the structure of these tables and how they are linked. These help you identify the cluster tables which store the data.
Payroll Cluster Table PCL4 contains the cluster table reference. (Please refer to the table structure below:
Payroll Custer Tables
http://www.planetsap.com/HR_ABAP_payroll.htm
Cluster tables combine the data from several tables with identical (or almost identical) keys into one physical record on the database.
Data is written to a database in compressed form.
Retrieval of data is very fast if the primary key is known.
Cluster tables are defined in the data dictionary as transparent tables.
External programs can NOT interpret the data in a cluster table.
Special language elements EXPORT TO DATABASE, IMPORT TO DATABASE and DELETE FROM DATABASE are used to process data in the cluster tables.
PCL1 - Database for HR work area; (long text, etc)
PCL2 - Accounting Results (time, travel expense and payroll); (payroll results)
PCL3 - Applicant tracking data;
PCL4 - Documents, Payroll year-end Tax data (change logs, etc)
Database Table PCL4
The database table PCL4 contains the following data areas:
LA change logs (long term documents)
SA Short-Term Documents for HR Master Data
SB Short-Term Documents for Applicant Master
SRTFD (PC400) = trans class always A for master data (1) pernr (8) info type (4) modified date (8) modified time (8) seqnr (4)
Please note that for the extraction of data, you have to use the date portion of the SRTFD and not the field value AEDTM(since it is not primary key).
Naming convention for INCLUDES when defining clusters. These INCLUDES will define the work area key above and the cluster data that is returned from an IMPORT:
RPCnxxy0
n = 1, 2, 3 or 4 (for PCL1, PCL2, PCL3, PCL4)
xx = cluster ID
y = country grouping (0 for international otherwise country indicator T500L)
Description of Cluster Data using Cluster RX as an Example
The data description is stored in the include RPC2RX00 in accordance with the above naming conventions.
RPC1TX00 - Long text cluster ID in table PCL1
RPC2RUU0 - Payroll results for the US cluster ID in table PCL2
RPC4LA00 - Change log cluster ID in table PCL4
Importing Data (I)
The IMPORT command causes data objects with the specified key values to be read from PCLn.
If the import is successful, SY-SUBRC is 0; if not, it is 4.
REPORT ZRPIMPORT.
TABLES: PCLn.
INCLUDE RPCnxxy0. "Cluster definition
Fill cluster Key
Import record
IMPORT TABLE1 FROM DATABASE PCLn(xx) ID xx-KEY.
IF SY-SUBRC EQ 0.
Display data object
ENDIF.
See sample program for long text.
Importing data (II)
Import data using macro RP-IMP-Cn-xy.
Check return code SY-SUBRC. If 0, it is successful. If 4, error.
Need include buffer management routines RPPPXM00
REPORT ZRPIMPORT.
*Buffer definition
INCLUDE RPPPXD00.
DATA: BEGIN OF COMMON PART 'BUFFER'.
INCLUDE RPPPXD10.
DATA: END OF COMMON PART 'BUFFER'.
*import data to buffer
RP-IMP-Cn-xy.
*Buffer management routines
INCLUDE RPPPXM00.
Cluster Authorization
Simple EXPORT/IMPORT statement does not check for cluster authorization.
Use EXPORT/IMPORT via buffer, the buffer management routines check for cluster authorization.
rpcbdt00 - include needed for importing from database PCL4(la) (Change log cluster ID)
Please note that data for change pointers is stored at two levels: 1) Header which has the key info and 2) BELEGE which has the changed info ie. Old value and new value.
Check standard program RPUAUD00
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.
Most applications write change documents. These are primarily log entries in the tables CDHDR and CDPOS.
Change documents remember the modified fields made to the database by an application. They also remember the user name and the time when the modification took place.
The decision whether a field modification is relevant for a change document is triggered by a flag of the modified fields data element. You can set the flag with SE11 by modifying the data element.
For the purpose of distributing data via ALE to other systems, you may want to choose other fields, which shall be regarded relevant for triggering a distribution.
Therefore R/3 introduced the concept of change pointers, which are nothing else than a second log file specially designed for writing the change pointers which are meant to trigger IDoc distribution via ALE.
So the change pointers will remember the key of the document every time when a relevant field has changed.
Change pointers are then evaluated by an ABAP which calls the IDoc creation, for every modified document found in the change pointers.
The Change pointers are written from the routine CHANGEDOCUMENT_CLOSE when saving the generated change document. So change pointers are automatically written when a relevant document changes.
The following function is called from within CHANGEDOCUMENT_CLOSE in order to write the change pointers.
CALL FUNCTION 'CHANGE_POINTERS_CREATE'
EXPORTING
change_document_header = cdhdr
TABLES
change_document_position = ins_cdpos.
Activation of change pointer update :
Change pointers are log entries to table BDCP which are written every time a transaction modifies certain fields. The change pointers are designed for ALE distribution and written by the function CHANGE_DOCUMENT_CLOSE.
Change pointers are written for use with ALE. There are ABAPs like RBDMIDOC which can read the change pointers and trigger an IDoc for ALE distribution.
The change pointers are mainly the same as change documents. They however can be set up differently, so fields which trigger change documents are not necessarily the same that cause change pointers to be written.
In order to work with change pointers there are two steps to be performed
1) Turn on change pointer update generally
2) Decide which message types shall be included for change pointer update
R3 allows to activate or deactivate the change pointer update. For this purpose it
maintains a table TBDA1. The decision whether the change pointer update is active
is done with a Function Ale_Component_Check
This check does nothing else than to check, if this table has an entry or not. If there is an entry in TBDA1, the ALE change pointers are generally active. If this table is empty, change pointers are turned off for everybody and everything, regardless of the other settings.
The two points read like you had the choice between turning it on generally or selectively. This is not the case: you always turn them on selectively. The switch to turn on generally is meant to activate or deactivate the whole mechanism.
The change pointers which have not been processed yet, can be read with a function module.
Call Function 'CHANGE_POINTERS_READ'
The ABAP RBDMIDOC will process all open change pointers and distribute the matching IDocs.
When you want to send out an IDoc unconditionally every time a transaction updates, you better use the workflow from the change documents.
Arunsri
Posts: 307
Registered: 12/3/07
Forum Points: 246
Re: change pointers method
Posted: Feb 27, 2008 11:08 AM in response to: satish abap E-mail this message Reply
hi,,
Activating Change Pointers
Use
You can activate change pointers in the HR system to avoid distributing the entire structure when you make changes to the HR-ORG model, and distribute instead only the changes that you have made.
Procedure
1. In the Implementation Guide (IMG, transaction SALE), choose Modeling and Implementing ® Master Data Distribution ®Replication of Modified Data ® Activate Change Pointers ‑ Generally.
2. Set the activation status Activate Change Pointers ‑ Generally, and save your entry.
3. Choose the activity Activate Change Pointers for Message Types.
4. Set the active indicator for the message type HRMD_ABA.
5. Save your entries.
also see this link,
http://help.sap.com/saphelp_47x200/helpdata/en/ba/c9c1c31253ed4596e3bbb74922cd4a/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/ba/c9c1c31253ed4596e3bbb74922cd4a/frameset.htm
Check the links below;
http://help.sap.com/saphelp_nw70/helpdata/en/f1/035c8cae3d11d3b540006094192fe3/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/12/83e03c19758e71e10000000a114084/frameset.htm
Reward if useful

Change Pointer RBDMIDOC in SRM Replication

Hi Experts ,
We have ECC 6.04 with SRM7.0. We replicated HR Org Structure from ECC to SRM.
Out of 10000 Employee , only 2000 Employee will sue SRM, So I wish to replicate only 1500 Employee as initial upload from ECC by eopy paste from EXCEL in PFAL selection screen. That is okay.
For changes & Delta , I will schedule Chnage Pointer RBDMIDOC in SRM.
1) My doubt is exatly what this Change Pointer will replicate to SRM (with matching to Filter setting ).... out of below ?
1. Changes to already replicated Employees in SRM
2. New created Employees after initial replication
3. Remainning Employees in initial replication as well ( i.e. 13000 )?
Is all these 3 cases will replicate to SRM ?
2) In case of change of one field value, will system send only that Value in IDoC or all the date of Employee again ?
Please suggest
Thanks
NAP

Hello sranjna ,
These are the steps for change pointer :
1. BD61 :Activate change pointer generally .
2. BD50 :Activate change pointer for message type.
3. BD21 :Create IDOC type from change pointers.
4.Save the content : create a variant .
5.For automatically process:go to SM36 :Create a job with the program "RBDMIDOC " and the variant you created.
Also see the link if you want :
[http://help.sap.com/saphelp_nw04/helpdata/EN/12/83e03c19758e71e10000000a114084/frameset.htm]
Good Luck,
Boaz

Change pointer method

Hi Experts,
I followed the following steps for change pointer method.
1.BD61- change pointers activated -generally
2.BD50 -Activate change pointers for message type 'OILT01'.
3.BD52 - add the triggering fields and corresponding tables and change document object.
But when I run the program RBDMIDOC and give the message type I found an error message that " Message type OILT01 cannot be sent with change pointers" .Please help.
regards,
Jeetu

hi,
I dont think we have run the program RBDMIDOC for implementing chagne pointer method
<b>Activating Change Pointers</b>
Change pointer generation has to be activated at both the
general level and message type.
1) Goto BD61, check the checkbox Change pointers activated - generally.
2) Save
3) Goto BD50, Choose the row for message type MATMAS, and check mark the corresponding field
4) Save
Converting change pointers to IDOCs
Create, change or mark for deletion materials using
transaction MM01, MM02, or MM06.
Execute transaction BD21
Enter Message type MATMAS
Execute
You can see tha changes gets reflected in 810 client that are done in 800 client.
Regards,
Sailaja.

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

Hi all ,
Can anyone suggest any link where i get step by step / complete procedure to create change documnet and change pointer to trigger IDOC for changed master data?
thanks & regards
Sheetal

Hi,
Please go through SAP Technical sites for details. You can check this [Link Also.|http://wiki.sdn.sap.com/wiki/display/ABAP/ALEChangePointers]
[Check This also|http://articles.techrepublic.com.com/5100-10878_11-1048973.html]
thanks,
Abhijit
Edited by: Abhijit Mandal on Feb 15, 2010 6:54 PM

Customization for Change Pointer Mechanism in IDOC Programming?

Similar Messages

Maybe you are looking for