Change Pointer Configuration

Hi Experts
Is it possible to add a Change Pointer for any Fields of any Tables.
If Yes, where do I have to configure the the missing tables and Attributes to choose them in the BD52 and activate the CP.
Cheers and Thanks
Sascha
Moved by moderator to the correct forum
Edited by: Hilit Fisch on Jun 14, 2009 8:27 AM

Yes provided you have corresponding master data object available.
Please refer [this|http://help.sap.com/saphelp_nw04/helpdata/en/78/2178da51ce11d189570000e829fbbd/content.htm] for more information.

Similar Messages

ALE/Change Pointer Configuration for ZSEGMENTS

Hello all,
I have been searching for a few days now trying to obtain my requirement with extending of an idoc. I am working with the following:
Message Type: HRMD_A
BASIC Type: HRMD_A06
Extension: ZHRMDA06
I extended the idoc because I wanted to include 2 extra infotypes which are not on that idoc. Infotypes 77 and 709.
Here is what I have completed so far.
WE30...Created ZSEGMENTS to include below.
WE31...Extended the HRMD_A idoc to include the ZSEGMENTS defined below.
WE82...Updated the output types and assignments to idoc.
BD61...Activate Change Pointers
BD50...Activated change pointer for HRMD_A.
I change the address field in infotype 0006.
Run the BD21...idoc is generated with the changes to address, everything looks good.
Do the same thing for the ethnic origin on infotype 77, no idoc is generated.
I turned on logging onto table PA0077.
I am evaluating the change logs via SCU3, and I am seeing my changes on the field.
What I have tried...
I have tried creating a object in t-code SCDO (ZTEST)
I have associated ZTEST with table/field PA0077-RACKY.
Tried running BD21...No iDoc generated.
I have been researching for a few days and it feels that this should be able to be done through configuration and not custom coding. Am I wrong to think that?
Has anyone ever did anything like this before which they can point to documentation or even the appropriate search criteria on the SCN forums.
Thanks in advance for your help!
Jason

Hi Jason,
I believe you have to enter the fields that trigger the changing pointer in tcode BD52. In my case these are the fields for BOM:
Regards,
Custodio

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

Configuring change pointer in SAP DEPOSIT MANAGEMENT system

Hi,
I am working on SAP Deposit Management system, which is very much similar to a normal R/3 system.
I need to create a change pointer everytime a business partner is created or changed. Can you please guide me through the steps especially
1. what would be the message type i need to configure and activate in BD50
2. What is the object name and Table name that i should select in BD52
And also if there is anything else I need to be doing?
Cheers,
Babs. 

Hi Babs
Here are my suggesstions.
1. There are different message types available for business partner, seems it depends on what data you want make synchronous. Try with BUS1006, search for BUPA* for message types.
2. Here you can try for the above message type with object type BUPA_BUP and table as BUT000
Cheers
Manohar

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,

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

Vendor Master IDOC (CREMAS) and change pointer activation..

Hi Guys..
I am using CREMAS idoc to transfer Vendor Master data to 3rd party system..
I configure the change pointer in SALE..
BDCP
BD61
BD50
BD52
But when I make changes in vendor master.. its not creating the idoc immediately.. I have to run RBDMIDOC manually.. to create the idoc..
How to make it create immediately.. ?
Also if I make a change in Email.. its not creating idoc at all.. !
Thanks for Ur time..

posting it in data transfer forum..

IDOC to XI (Using Change Pointer) - Error

Hi all,
I have 1 scenario to update external GL master data using XI. in this case i already configure the source system (SAP) to sending the IDOC to XI whenever got changes.
BD61 ---> Activate Change Pointer Globally,
BD50 ---> Activate Change Pointer for GLMAST Message Type.
SM59 ---> RFC destination for XI system (PX6CLNT300).
BD54 ---> Logical System source (ST6CLNT100) and target xi (PX6CLNT300)
WE20 ---> Partner Profile for XI (PX6CLNT300).
BD64 ---> Create Distribution Model View. Sender = ST6CLNT100, Receiver = PX6CLNT300 and Message Type = GLMAST
The system can generate the IDOC whenever changes happen with running program RBDMIDOC. but the got error with no sender / receiver information in WE05.
Please advise any step that i have to do ?
Best Regards
Fernand

Hi Matias,
Thank you for your answer. The problem is because i had used wrong logical system in my distribusion model. The system using not common logical system. nomarly it will use "PX6CLNT100" but in my system the basis people using different logical system that's why the GLMAST IDOC cannot pass throught to XI system.
Best Regards
Fernand

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

Change pointer for Sales Order

Hi,
Using change pointers I want to create an IDOC when ever a specific field in the sales order line item is changed. I have activated the change pointer for message type ORDRSP. Also maintained the following entries in BD52
VERKBELEG(Object) VBAP(Table) ABGRU(field).
After this when I change this field at the sales order line item, it inserts entries into change pointer table.
But my problem is creating IDOC's from those change pointer entries. I am not sure which function module (MASTERIDOC_CREATE_XXXXX) works for this.
Anyhelp on this highly appreciated.
Thanks
Ram

Hi Ram,
I don't think so you can use change pointer for sales order changes. Usually, it is done through transaction code NACE - configuring condition for output type.
You can setup requeirement in procedure control to trigger IDoc ORDRSP for any changes in item level.
Hope this will help you and give an idea.
Regards,
Ferry Lianto

What is the use of change pointer concept in ale?

what is the use of change pointer concept in ale?
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

ALE Architecture:
It consists of an Outbound process, an Inbound process, and an Exception Handling process.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocs definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
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 and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programs design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocs packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Creation of IDoc:
Basic Type:
Basic IDoc type defines the structure and format of the business document that is to be exchanged between two systems.
Segments:
Segments form the basic building blocks of an IDoc type and are used to store the actual datta. A segment type is the name of a segment and is independent of the SAP elease. A segment definition is the release-specific name of a segment.
Steps in creating Segments:
T.Code WE31
Enter the name for your segment type and click on the create icon.
Type the Short text.
Enter the variable names and data elements.
Save and Go back.
Go to Edit -> Set Release.
Repeat the steps to create more segments.
IDOC TYPE:
Business data is exchanged with an external system using the IDoc Interface.
IDoc types (Special Structures) An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). The IDoc interface can check for each IDoc whether thhe segments contained are compatible with thhe definitiion of its type. This systax check is activated or deactivated in the Partner Profiles.
Steps in creating IDoc Type:
T.Code WE30 to create IDoc Type.
Enter the Object Name, Select Basic Type and click Create Icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDoc name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press enter
The system transfers the name of the segment type to the IDoc editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation.
Save it and go back.
Go to Edit -> Set Release.
Message Type:
Steps in Creating Message Type:
T.Code WE81.
change the details from Display mode to Change mode
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
Assign Message Type to IDoc Type:
T.Code WE82
Change the details from Display mode to change mode.
After selection, the system will give this message "The table is cross client (See help for further info)". Press enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back.
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Feb 6, 2008 5:10 PM

CREMAS Change Pointer, custom fileter

Hi Experts,
I have a requirement in which Vendor master change pointer is configured and working fine. But Now they want to set a filter based on some conditions which is not possible to configure in filter.
(Ex: based on Vendor characteristic value from table AUSP, I have restrict sending IDoc).
I am looking for userexit or badi which should allow me to create or not create change pointer option,
OR allow me to restrict posting of IDoc.
I tried BADI VENDOR_ADD_DATA_BI, but looks to me not suitable.
Thanks,

this BADI will trigger always before creating idocs - here you can keep your custom filter logic to control idoc creation.
On CP - are your characteristic value changes creating change pointers?

Change pointer creation

Hi
I have Custom Message type and I linked it to the change pointer , which have basic type DEBMAS. But I just wonder about , when I create a new customer change pointer could not be created. Isnt possible to extract an Idoc for create a Customer with change pointer ..
Thanks ...

HI,
Please try like this
-     Change documents are working based on change document technique which tracks changes made to the key documents ( Material Master, Customer Master, Vendor Master u2026.etc) in SAP
-     Changes made to the key documents 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 RBDMOIND is scheduled to run on periodic basis to evaluate the change pointers for a message type and starts the ALE process for distributing the master data to the appropriate destination.
-     u2018objectu2019 is collection of fields of different database tables. T.Code for creating an object is SCDO.
Configuration ofr change pointers----
1.   BD61 Active change pointers generally
     - Check the check box u2018Change pointers activated - generallyu2019
            - Save it
2. BD50 Active change pointers for message type
     - Message type           active
               DEBMAS               check the check box
3. SCDO changed document objects
     - Check whether the u2018DBMSu2019      is available in the ogject list.
4. BD52 Maintain table views
-     Enter the message type u2018DEBMASu2019 and press enter
-     OBJECT          TABLE NAME          FIELD NAME
Ex :           DBMS      KNA1
5. BD60 Additional data for message types
     - Message type      Function Module                         Table
Ex :   DEBMAS          IDOC_INPUT_DEBMAS01        KNA1
6. WE20 Partner Profile.
7. BD64 Distribution model.
8. Create a Customer by using t-code KNA1
9. SE38 run the program RBDMIDOC by passing message type u2018MATMASu2019.
10. WE02 Idoc list
I hope this code is helping to you,
Thanks,
Murali

ALE Distribution LOIROU Change pointer

Hello
I want to know if it is possible to manage LOIROU idoc with change pointer management in SALE and how ?

Hello Jean,
I think you can manage LOIROU idoc with change pointers.
Steps are as follows:
1. Activae change pointers generally : TC : BD61.
2. Activate change pointer for message type LOIROU using TC : BD50.
3.Create an object for the Change Documents, by transaction SCDO.
4. Maintain Distribution model using BD64.
5. Maintain Partner profile & remaininf basic configuration.
6. After creating / changing document goto transaction BD21 and execute it with Message type LOIROU.
Thats all!!
Cheers,
Nilesh

Idoc without activating change pointer

what is the alternative way of without activating the change pointer in bd61,bd50 and bd52 in idoc creation??
i mean there is a way of doing code instead of that. can anybody gv me that sample code...
thanx in advance...

Hi Biswajit,
Please check this link which will show you step by step on how to configure creation of IDoc (inbound and outbound).
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
Hope this will help to start with.
Regards,
Ferry Lianto
Please reward points if helpful.

Change Pointer Configuration

Similar Messages

Maybe you are looking for