Set Tables Change Pointer

Hi all,
I have a requirement where i have been given a settable in GS03. I need to record every change in this on ECC side and pass it to PI and then send it to target.
I am not aware of how to do this.
Can anybody please help me either by a blog or some steps.
Thanks
-Kulwant

what do you mean by 'change pointer'? normally this idiom is used for sending ÍDOCs from one system/client/org-unit to another ...
do you generally want to record changes to a specific table? then set parameter rec/client using RZ10 for your instance profiles and restart the instances in order for the parameter to take effect.
set the table to 'record all changes' using SE11.
you might re-consider if the table has a lot of data and is accessed very often for performance-resons.
change protocols can be evaluated using tx, SCU3.

Similar Messages

How to set a change pointer for a perticular table?

Hi,
Please let me know how to set a change pointer for a perticular table.

what do you mean by 'change pointer'? normally this idiom is used for sending ÍDOCs from one system/client/org-unit to another ...
do you generally want to record changes to a specific table? then set parameter rec/client using RZ10 for your instance profiles and restart the instances in order for the parameter to take effect.
set the table to 'record all changes' using SE11.
you might re-consider if the table has a lot of data and is accessed very often for performance-resons.
change protocols can be evaluated using tx, SCU3.

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

Activate change pointer to shipment tables

Hi,
Is is possible to activate change pointers to shipment tables like VTTK or VTTP? not to message type.
regards,
sree

Hi Friend,
No it is not possible to maintain change pointer for tables except message type.
Because message type help to recognize what type fo data SAP should send or receive.
Regards
Krishnendu

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

Idoc trigerring with change pointer under conditions

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

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

Doubt on logging the table change

For the logging the table changes, we have to check log data changes in the technical setting of a table. But came to know that it is not enogh to log the table changes. There is some parameter rec/client, that we need to take into consideration for logging the table changes. Can anyone please help me where exactly can i find that parameter and what changes do i need to make there.

Hi,
The logging flag defines whether changes to the data records of a table should be logged. If logging is activated, every change (with UPDATE, DELETE) to an existing data record by a user or an application program is recorded in a log table in the database.
It has a Dependency:
Logging only takes place if parameter rec/client in the system profile is set correctly.
Now rec/client is a system parameter which i think you see in sytem profile but I am not sure how do we go about it.
Some BASIS consultant can help you on this.
Regards,
Mayank Verdia
Moderator message: copy/paste of parts of the F1 help of field "log data changes", points removed, please do not repeat this behaviour!
Edited by: Thomas Zloch on Sep 7, 2010 9:39 AM

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

Turning off Change pointer HRMD_A

We currently have the change pointer HRMD_A turned on and it's creating the IDOCs just fine.
Now, we want to turn off the change pointer, which I did in tcode BD61 and unchecked the message type HRMD_A in tcode BD50.
But, the IDOCs are still getting generated. What else has to be done to turn off the change pointer and the creation of the IDOC's ???

Hi John,
Did you save your changes into a transportable request and client-copied (SCC1) the changes back to the client where the data is i.e. the client where the IDocs are created? You can double check this by checking BD50 & BD61 in the client where the IDocs are generated. Then, as a test, go to PA30 change some employee data (keeping in mind the infotype filter if set in IMG) then cross check with table BDCP and field CRETIME.
If you have already done this and checked as per above and the system's still creates HRMD_A IDocs (which I find it unbelievable) then you should create an OSS message with a high priority and let SAP take a look at this!
Hope this helps.
Cheers,
Sougata.

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?

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

Activate change point for message type - message type FIDCC1 not in list

I want to set up idoc for sending entire FI documents.
For this I want to use the change points in the message type FIDCC1 but this message type is not in the list of transaction BD50 (neither if I go via SALE)
I'm not allowed to add it myself, I get a warning the name is not in the namespace (Zxxx or Yxxx).
Is there a way I can add this message type in this list?
-> change points are generally activated
-> ECC 600
edit: I see the message type is in WD81
Edited by: Renaat Vanhaverbeke on Apr 28, 2010 11:05 AM

I found the solution: when I tried to add the message type in BD50 I got the warning the name does not match the namespace rules. But by opening the Performance Assistant I could start the transacion RDDKOR54 to display the namespace rules.
By exiting this transaction I got the question if I want to bypass the namespace check and by answering positive on this I could save the new entry.
PS: I also found that alle message types are defined in table EDMSG

11.1.1.6 - NPE :: Failed to apply row key set attribute change in logs

Hi All ,
Using POJO Data controls and ADF Faces - Jdev 11.1.1.6.
Setup - Tab -> taskflow ->jsff -> table
Issue happens once I reload the taskflow . I get the below error's in the logs (only if data is populated in the table in jsff via search).
There is no pointer to my code , this happens immediately after the iterator is refreshed in the page definition.
Please let me know if you need any other information.
There are various unresolved threads on this like - https://forums.oracle.com/message/10747913#10747913
<RowKeySetAttributeChange$GetOldValueAndUpdate> <_updateKeySet> Failed to apply row key set attribute change. Reason : {1}
java.lang.NullPointerException
at oracle.jbo.uicli.binding.JUCtrlHierNodeBinding.<init>(JUCtrlHierNodeBinding.java:210)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlHierNodeBinding.<init>(FacesCtrlHierNodeBinding.java:66)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlHierBinding.createNodeBinding(FacesCtrlHierBinding.java:94)
at oracle.jbo.uicli.binding.JUCtrlHierBinding.createRootBinding(JUCtrlHierBinding.java:409)
at oracle.jbo.uicli.binding.JUCtrlHierBinding.getRootNodeBinding(JUCtrlHierBinding.java:105)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlHierBinding$HierCurrencyRowKeySet.getRowIterator(FacesCtrlHierBinding.java:1178)
at oracle.adfinternal.view.faces.model.binding.CurrencyRowKeySet._computeCurrentRowKey(CurrencyRowKeySet.java:125)
at oracle.adfinternal.view.faces.model.binding.CurrencyRowKeySet.iterator(CurrencyRowKeySet.java:41)
at java.util.AbstractCollection.addAll(AbstractCollection.java:303)
at org.apache.myfaces.trinidad.change.RowKeySetAttributeChange$GetOldValueAndUpdate._updateKeySet(RowKeySetAttributeChange.java:136)
at org.apache.myfaces.trinidad.change.RowKeySetAttributeChange$GetOldValueAndUpdate.invokeContextCallback(RowKeySetAttributeChange.java:117)
at org.apache.myfaces.trinidad.component.UIXCollection.invokeOnComponent(UIXCollection.java:1063)
Message was edited by: SudiptoDesmukh

Figured out that the issue is due to selectedRowKeys property and happens whenever the taskflow is refreshed and the iterator binding is executed. Again happens only when prior to region refresh few rows have been selected (other than first selected by default).
Issue is I cannot remove selectedRowKeys as I need to show the first row of the table as selected.
Will probably need to log an SR as this is happening throughout the application and looks to be a fwk issue.

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

Trigger CREMAS change pointer for vendor classification change in XK02/FK02

Hi,
I have a business case where I need to trigger a change pointer of type CREMAS whenever a client modifies vendor classification in transactions FK02/XK02. I realize classificatiion/characteristics have their own change pointer types (CLFMAS, CHRMAS, etc.), but I was wondering if there was a user exit/BADI available for this scenario where I can manually create a change pointer. I need the characteristic data to be part of a custom IDoc type (based off of CREMAS03), and it's no problem to include this data in the custom IDoc, but I need a way to trigger the change pointer if the clients changes vendor characteristic data, and nothing else.
I also went into transaction BD52 for type CREMAS to see if there's another row for classification (CLASSIFY), but couldn't figure out the right object type.
There's a BADI called CACL_VALUE_CHANGE that triggers when vendor classification is changed, where I can generate my change pointer, but it's triggered before the client saves which means I would have a useless change pointer.
Does anyone have any ideas on what my options are? I hope I've elaborated enough
Thanks,
Chris

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

Set Tables Change Pointer

Similar Messages

Maybe you are looking for