Activating change pointers

Hi All!
I had activated chnage pointers on VBAK-Vbeln filed by using SAP access key. My requirement is to capture vbeln in CDHDR and CDPOS tables when ever a sales doc is created or deleted. After checking the change pointer on the data element of VBELN I still don't see any records being update to the CDHDR and CDPOD tables. Shall I have to do any further settings to activate the change pointers.
Please advise..
Regards
Praneeth

Praneeth,
I don't think you have declared a change pointer on the right field. If you see the document number will not change by itself, right.
So, you need to identify those fields that the user will change in a document and activate the change pointers on that. For example the quantity of the material, prices of the material etc.
Regards,
Ravi
Note - Please mark all the helpful answers

Similar Messages

0CML_DELTA : Change pointers are not active

Hi All,
I have successfully did the delta init without data transfer for datasource 0CML_DELTA and 0CML_DELTA_CAP. Now, While trying to load delta, I am getting an error "Change pointers are not active" for both the datasource 0CML_DELTA and 0CML_DELTA_CAP.
The position datasources are fecthing 0 records.
I have activated the change pointers in BD61, even though I am getting the same error.
Anyone faced the similar issue or have any clue about the problem.
Thanks in advance,
Pravender
Edited by: Pravender on Sep 30, 2010 11:09 AM

I resolved it. I was activating change pointers in BD61. But fot CML we need to activate in SPRO--> SAP Banking --> Loans Management --> Basic settings --> Installation parameters ---> Define general installation parameters.
Then it will work.
Pravender

Change Pointers are not getting populated in BDCPV table.

Hi All,
         I am trying to create IDOC for Activity type master - KL02 through change pointers. For that I have done following things.
Message type - COAMAS
1. Created Custom message type - WE81 - ZIN_COAMAS_TCSMOBILE
2. WE82 - Config for Mess Type and Idoc type combination
3. SCDO - Checked object type LSTAR and have required tables in that object.
4. BD61 - Activated Change pointers - Generally.
5. BD50 - Checked Active for ZIN_COAMAS_TCSMOBILE
6. BD52 - Added fields for I want to create Change pointers
7. BD60 - Message type and ref Mesage Type and function module config.
8. BD64 - Created distribution model for my Message type
After doing all this settings the change pointers are not getting created in BDCP and BDCPV tables.
Note - The entries are going in CDHDR and CDPOS table for activity which i change through KL02 for class LSTAR
Can anybody figure out what need to be done in this case?
Regards,
Gautam Joshi.

Hi All,
          Solved the problem myself.
          In BD52 I have given
          LSTAR               CSLA         KOARS
          LSTAR               CSLA         LSTAR
          LSTAR               CSLT          KTEXT
          Here the data of activity are stored in TCLA and TCLT tables. So intially while doing config in BD52 I have given TCLA and TCLT table names.
          But I debugged the KL02 and found that change pointers are not created for TCLA and TCLT table. further looking into CDHDr and CDPOS table I found that for COAMAS message type in these two tables table name was CSLAB.
CDPOS entry
LSTAR
3166442
119512890
*CSLAB*
2003166442   2400123120000101
KTEXT
U
--> BUT CSLAB is structure.
After putting these entry in BD52 the problem solved.
LSTAR     CSLAB     KOKRS
LSTAR     CSLAB     KTEXT
LSTAR     CSLAB     LSTAR
Regards,
Gautam Joshi.

How to find out what are all the change pointers assoicated for an idoc ??

Hi ,
How to find out what are all the change pointers activated for an idoc ??
Thanks,
Varma

Verma,
You can check what are the active Change Pointers for the message type in tcode BD50
Use tcode BD61 to check whether change pointers are active or not??
Hope this helps..

Change pointers problem

I have created message type ZMATMAS and I want to see an entry in BDCP2 (Change pointers table)
when ever any material is created or changed
I did following steps until now.
1. Created ZMATMAS
2. Activated change pointers - BD61
3. Activated change pointers for message type - BD50
What else I've to do?
Thanks in advance..

Hi,
Visit this link for more details on Change pointer.
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
also i will tell you in short about what next to be done...
To be able to activate the writing of change pointers via the SMD tool for your master data object, you must carry out these steps:
·        Activate change pointers for each message type
·        Maintain change-relevant fields for message type
·        Activating change pointers generally
You also have to:
·        Implement function module for evaluating change pointers
·        Defining the ALE object type MSGFN as a filter object type
NoteIf you distribute master data using a asynchronous BAPI, all the settings below apply to the generated message type of the BAPI-ALE interface.
Thanks and Regards
Anup

Change pointers

HI All,
Can you guys plz help me on change pointers.
I have activated change pointers for CREMAS and I am running program RBDMIDOC in background. But it is generating idocs properly when ever vendor is created or changed.
Change pointer is triggering for all vendors when ever vendor is created or changed.
Here my problem is that i don't want to generate all idocs i want to generate idocs for some specifi vendors only (Here we are having different types of vendors depend upon Account group.)
How can I generate specific venodr Idocs using change pointers.
Thanks & Regards
Praveen

Hi Praveen,
There are two filtering in IDoc.
Segment Filtering:
Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
Data Filtering:
Data filtering can be done in dustribution model where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
For your case, you can use segment filter to send only to specific vendor(s).
Please check this link for detail information.
http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
Hope this will help.
Regards,
Ferry Lianto

How to create change pointers for IT6 when custom table Z777A changes?

Situation: We are using custom table Z777A (copied T777A and added fields) to store building locations. Employee's IT6 subtype 92 retrieves valid work address building locations from table Z777A.
Problem: Whenever there are updates to Z777A, we need to find all IT6 subtype 92 records that use the changed building location from Z777A and create IDOC's The change pointer entry will need to be for the IT6 subtype 92 row that is affected.
Question: Can anyone give me specific details as to how this can be accomplished? Thanks.

Hi,
MASTER DATA CHANGES DISTRIBUTION BY CHANGE POINTER TECHNIQUE:
Step 1: Creating change document object in SCDO transaction.
Step 2:Assigning tables to the change document object.
Step 3:Specifying change document items in transaction BD52.
Step 4: Activating change pointers for the message type HRMD_ABA in transaction BD50.
Step 5:Activating change pointers globally.
Step 6:Executing program RBDMIDOC in SE38, Specifying message type HRMD_ABA.
with regards,
M.Sreeram.

ALE configuration - change pointers

Hello,
Iam trying to create idocs whenever there is a change in the customer master i need to trigger an idoc.Iam trying to use change pointer for that.
I checked in bd61,bd52,bd50 all the settings are ok.
but still idocs are not created when i change the customer master...
Do i need to run BD12(RBDMIDOC)...?or am i misssing any other settings...(When i tried to use bd12 to send customers iam able to generate idocs so my model is working...).
Second question I need to send DUNS number in the idoc which Iam not able to find in DEBMAS/DEBMAS04 how can i send that...?Even if i extend how can i populate it ...I dont find any user exits for MASTERIDOC_CREATE_SMD_DEBMAS which holds the control record....?
can anyone help....
Thanks
Larry

Hi Joseph,
The above process is for outbound.
the tool used behind for the process is SMD tool (Shared Master Data tool)
based on the configuraution steps as below they work
BD61 - activates the Change pointers tool (SMD)
BD50 - is for activating Change pointers specifically that message type
BD52 - is for activating Change pointers specifically for that message type and specifically to a field in belonging to that message type
and the CMD (Customer Distribution Model also need to be configured)
you can come up with furthere questions

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

About change pointers in ale

hi,
i have finished ale customization and processed idoc succesfully!
now i would like to send idoc using change pointers,
i know 3 tranasactin codes bd50,bd,......
i ahve activated change pointers ,messae tyepes,then my doubt is..
If we create a new material in outbound side will it go directly into inbound side
i mean will it need to run bd 10 or not?
i want backgorund schedulilng using change pointer...
could anybody give me some suggetions..

Hi,
After completing the configuration of ale as well as for change pointers, v have to schedule the job. For that v have to go to either SM36 to create a job or SALE --> click on shcedule job.
There is no need for going to that BD10. consider this example, u r changing the material description for a material which is alreading existing using MM02. These changes are stored in the change documents. Change pointers in turn keep track of the changes. As per ur start condition specified in the job description(Background) that job will be automatically started and the material is transferred to the other system as per ur configuration.
First of all clear with the definition of the change pointers.
change pointers techinque is based on the change document technique which keep track of the changes made in the key documents in the sap.
Regards...
Arun.
Reward points if it helps.

Do we need the change pointers to be set..

do we need the change pointers to be set/activated
if we are to send data via TRFCs

Change Pointers:
-Change documents are working based on change document technique which
tracks changes made to the key documents (Material Master, Customer
Master, Vendor Master ..etc) in SAP.
-Changes made to the keydocuments are recorded in the change document
Header table i.e. CDHDR and Item table CDPOS,   Additional change
pointers are written in the BDCP and BDCPS tables.
-Change pointers technique is used to initiate the outbound process
automatically when master data is created or changed.
-A standard program RBDMIDOC is sechuled to run on periodic basis to
evaluate the change pointers for a message type and starts the ALE
process for distributing the Masterdata to the appropriate destination.
-'Object' is collection of fields of different database tables. T.code
for creating an object is SCDO.
Configuration for Change Pointers:
1. BD61 Active change pointers generally
     - Check the checkbox "Change pointers activated -generally"
     - Save it
2. BD50 Active change pointers for Message Type
     - Message Type           Active
        MATMAS           check the check box
3. SCDO Change Document Objects
     - Check whether the "MATERIAL" is available in the object list.
4. BD52 Maintain Table Views
     - Enter the Message type "MATMAS" and press enter.
     - OBJECT      TABLE NAME     FIELD NAME
   Ex:    MATERIAL      MARA          BISMT
5. BD60 Additional data for message types
        - Message Type           Function Module          Table
   Ex:       MATMAS     MASTERIDOC_CREATE_SMD_MATMAS     MARA
6. WE20 Partner Profile
7. BD64 Distribution Model
8. Create a Material by using T.Code MM01
9. SE38 Run the program RBDMIDOC by passing Message type "MATMAS"
10. WE02 IDOC List
Regards
srikanth

Help With IDOC Change Pointers

Hi guys,
I'm trying an IDOC to file scenario. The scenario is working fine. I have activated change pointers for my IDOC. My understanding was that if there will be any change in my master tables, then because of the activated change pointers, the IDOC will be generated automatically. But in my case, for eg if i'm inserting any new record say Vendor data, no new IDOC is generated. For sending IDOC i have to use bd14 to send my IDOC explicitly.
Is my idea of change pointers wrong???Or am i missing some setting, so that the IDOC should be generated automatically???
Please help me on this guys...
Regards
Varun

Automatic generation of IDOC when we change the MASTER DATA:
Change Pointers:
Change documents are working based on change document technique which
tracks changes made to the key documents (Material Master, Customer Master,
Vendor Master.Etc) in SAP.
Changes made to the keydocuments are recorded in the change document Header
table i.e. CDHDR and Item table CDPOS, Additional change pointers are written
in the BDCP and BDCPS tables.
Change pointers technique is used to initiate the outbound process automatically
when master data is created or changed.
A standard program RBDMIDOC is sechuled to run on periodic basis to evaluate the change pointers for a message type and starts the ALE process for distributing the Masterdata to the appropriate destination.
'Object' is collection of fields of different database tables. T.code for creating an object
is SCDO.
Configuration for Change Pointers:
1. BD61 Active change pointers generally
 - Check the checkbox "Change pointers activated -generally"
 - Save it
2. BD50 Active change pointers for Message Type
Message Type Active
MATMAS Check the check box
3. SCDO Change Document Objects
 - Check whether the "MATERIAL" is available in the object list.
4. BD52 Maintain Table Views
- Enter the Message type "MATMAS" and press enter.
For example
OBJECT TABLE NAME FIELD NAME
MATERIAL MARA BISMT
5. BD60 Additional data for message types:
For example:
Message Type Function Module Table
MATMAS MASTERIDOC_CREATE_SMD_MATMAS MARA
6. WE21 Port
7. WE20 Partner Profile
8. BD64 Distribution Model
as michal said we have to use RBDMIDOC program.for executing this program we need to give message type like
MATMAS or
DEBMAS or
CREMAS
depending on your requirement.
go to SE38 tcode
--- copy RBDMIDOC to zprogram(i'e., ZRBDMIDOC)
---create variant
use this zprogram(ZRBDMIDOC) in BACKGROUND SCHEDULING SM36
STEPS IN BACKGROUND SCHEDULING:
Use tcode SM36
Click Job wizard in the button set
Click Continue
Enter Job name and press continue
Select ABAP program and press Continue
enter Program name and press continue
and again press Continue
set Schedule type immediately and continue
Select periodic job checkbox, press continue
Select none of the above and click on other periods give one-minute and then press create
Press continue and then press complete.
recently i did this requirement
if u have any doubts plz let me know
Best Regards,
Srikanth
Reward the useful answers and you will get one point yourself

Change Pointers Needed

Hi All,
Please give me a scenario to expalin about change pointers.
Regards,
Srik

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 points hope this helps u,

ALE Change Pointers in source system not active

Hi All,
I am trying to load 0COSTELMNT using deltas. The initial load is OK and then i use a delta and it fails and i get the error:
"ALE Change Pointers in source system not active"
I have carried out the following steps in an attempt to resolve the problem - but it didnt. Anyone have any advice??
(1) Checked BD61 to confirm whether the change pointers are active
(2) Checked BDCP to confirm the number range is maintained
(3) Checked SALE (Activate change pointers for message types) to confirm whether the change pointer has been activated for the type we need:
COCOKA Control segment CO object/cost element
COELEM Cost element master data
(4) In transaction snum, Selected number ranges and confirmed the intervals are setup
No. 01
FROM: 0000000001
TO: 0000009999
(5) Activate transfer structure
(6) Replicate Datasources
Thanks,

If you are transferring master data from source system, the BD61 setting on the source system should be checked.
Why it has been unchecked - not sure (likely someone did it by mistake).
It shouldn't have any effect on txnl delta. What will be effected though is that you will have lost delta of the ALE based data sources for the period this setting was unchecked.

Change Pointers activation for customer specific Infotype

dear friends,
could you please let me know how to activate the change pointers for customer specific infotypes? Currently we are using message type HRMD_ABA.
regards,
jp

Anand:
Unfurtunatly, not all the modification are registered in the log. For ei., You can track the systema status modification, the PR generation, etc. What fields change are you trying to modify?
Hope this help
Ezequiel

Activating change pointers

Similar Messages

Maybe you are looking for