Trigger IDOC using change pointers

Dear All,
We are using change pointers for triggering IDOC's when a cost centere is creaed/changed/deleted.
We are using message type COSMAS for the same.
I have maintained all the necessary settings including Distrubution model.
When a cost centre is created or changed the IDOC is getting triggered ( After executing prgroam RBDMIDOC ).
But when we delete an cost centre the IDOC is not getting triggered.
I am able to see the releated entries in BDCP and BDCPV tables as well as CDHDR and CDPOS tables.
Can any one say how this can be achieved? When a cost centre is deleted then also IDOC should get triggered.
Regards,
SRavan

When we remove an Cost center it physically gets deleted from the data base.There is no delete indicator as such

Similar Messages

Can anyone send me link of IDOC gentn using change pointers!

Hey guys I need to learn IDOC generation using change pointers.Please send me some help notes and link and sample program on that !

Hi,
Change pointers are the mechanism through which you can send data to another SAP system or external system if there is a change happening to specific fields of master data.
For more information, please check this link.
http://www.angeli.biz/www5/cookbooks/workflow/workflow_30/docu.htm
http://help.sap.com/saphelp_nw04/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
Regards,

Using change pointers for Process orders

Hi Experts,
We have a requirement where we need to send idocs when a process order is changed. Since process order data is a transactional data, can we still use change pointers?
We tried using the message type LOIPRO and it is giving an error saying that this message type cannot be sent with change pointers.
Can anyone guide me with the process and steps to get this done?
Thanks.

For change pointer, you would have to deligate the business object with t.code SWO1. To handle it, it would take too much time to explaint.
If you use the BAdI, and call function in this way : " CALL FUNCTION 'FUNCTION_NAME' IN BACKGROUND TASK AS SEPARATE UNIT EXPORTING ....." the function would executed only after commit (when you call the funtion, it holds in a queue for commit. In roll back, it get disapeared).
User method in_update from the BAdI.
Edited by: Lior Tabib on Oct 19, 2010 4:18 PM
Edited by: Lior Tabib on Oct 22, 2010 7:27 PM

Difficulties using change pointers

Hi all.
We are currently working on a project where we will have SAP HR as the master HR table, and distribute changes to connected systems. To to this we will use change pointers to track and collect changes to master data, and create IDoc for distribution. I have a question regarding the validity-periods for all objects in SAP.
Say I activate change pointers to track changes to master data. Is the IDoc always created when you enter the information in SAP (which not necessarily is the same date as valid-from date)? This would allow the receiving system to perform other related tasks, such as setting up email accounts for a new hire, before the actual change is implemented in the receiving system. On the other hand, the receiving system does not support the valid-from date concept, so we cannot transfer the IDoc to the receiving system until the change is actually effective. A solution here would be to create an email when the data is entered in SAP, and send the email to the receiving system instead of the Idoc, stating what action occured. This would allow the receiving system owner to perform these related tasks. Is this possible? If so, it brings me to my next question.
Is it possible to create IDoc for transfer from SAP when a valid-from date becomes effective? Since the receiving system does not support valid-from dates the IDoc can only be sent when the data is actually effective.
Any help on this issue is highly appreciated.

Hi all.
We are currently working on a project where we will have SAP HR as the master HR table, and distribute changes to connected systems. To to this we will use change pointers to track and collect changes to master data, and create IDoc for distribution. I have a question regarding the validity-periods for all objects in SAP.
Say I activate change pointers to track changes to master data. Is the IDoc always created when you enter the information in SAP (which not necessarily is the same date as valid-from date)? This would allow the receiving system to perform other related tasks, such as setting up email accounts for a new hire, before the actual change is implemented in the receiving system. On the other hand, the receiving system does not support the valid-from date concept, so we cannot transfer the IDoc to the receiving system until the change is actually effective. A solution here would be to create an email when the data is entered in SAP, and send the email to the receiving system instead of the Idoc, stating what action occured. This would allow the receiving system owner to perform these related tasks. Is this possible? If so, it brings me to my next question.
Is it possible to create IDoc for transfer from SAP when a valid-from date becomes effective? Since the receiving system does not support valid-from dates the IDoc can only be sent when the data is actually effective.
Any help on this issue is highly appreciated.

How to trigger idoc using commnad line?

Hi abap gurus,
anyone knows how we can trigger idoc using commnadline like STARTRFC.EXE.
Please let me know its very urgent.
Thanks,
Jack.
Edited by: Alvaro Tejada Galindo on Feb 15, 2008 2:34 PM

solved on my own

BATMAS IDocs not gettting generated using Change Pointers

Hi,
I have scenario where I am supposed to replicate Batch between R/3 & Ware House Systems. So, for this I am using the standard BAPI to generate IDocs correctly for the batch.
Now, when I go and change the document flow i.e. make changes to the Batch using transaction MSC2N and saving a new document is getting generated.
Change Pointers are active globally and also on the message type. Now when I use the transaction BD21 to generate IDocs, they are getting created successfully for the distribution model that is existing. Now, when I add a filter in my distribution model based on Plant IDocs are not getting generated.
Can any one let me know if I missed out any configuration step or else what needs to be done in order to solve this issue.
Raghuram.

Is this thread still valid? If not, please close the thread.
If so, as no response has been submitted, please rephrase your question and/or provide further information to describe your requirement.
Thanks
Jason
SDN SRM Moderator Team

Sending Idocs from Change pointers

Hi All,
When using RHALESMD or RBDMIDOC, is it possible to send Idocs with transfer mode Insert instead of Update?
Currently when I create new P objects and run the programs the Idocs sent is of transfer type Update. But since the object doesn't exist in receiving system there is nothing to update.
Please let me know if you have any thought what action i can take to solve this problem.
Best regards
Mikael

Dear Karyna,
The data is fetched from tables TBDME and TBDA2. Neither of the tables has partner system.
You can use below parameters by copying the program and modifying as per your requirement. See if you can link them to receiver partner system.
The data is fetched from TBDME.
You can use below parameters.
MESTYP     Message Type
REFMESTYP     Reference message type
IDOCFBNAME     ALE: IDoc editing function module
OBTAB     Name of database table for object
CREUSER     Created by
CREDATE     Created on
CHAUSER     Changed by
CHADATE     Changed On
OBJTYPE     ALE Object Type
REDUCIBLE     ID for reducible message type
BDCP2_SUP     Message Type Supports Change Pointers in Table BDCP2
Table TBDA2:
MESTYP     EDI_MESTYP
ACTIVE     ALE_ACTIVE
BDCP2_ACT     BDCP2_ACT
Regards,
Naveen.

How to trigger Material CIF change pointers when changing Source List

I need to trigger a Material Change pointer (CIFMAT) creation when the Source List is updated for that material. In BD52 (ALE configuration) table EORD is not an option for CIFMAT message type, so by standard ALE this can not be done automatically. I could not find any BAdI/Userexit which will help me to create a material master change pointer so that the Material (Product) will be sent to APO via the CIF when the Source List in R/3 is changed.

Hi , Can you please check user exit CIFMAT01 function module EXIT_SAPLCMAT_001.You can use this enhancement to influence the logic according to which material data from SAP R/3 is mapped to APO product interface data.
I suggest to put logic in user exit to check table source list table EORD changes & trigger CIF for material master.You can pull change data from table CDPOS using EORD table reference & material object value details.
Based on change record CIF user exist should trigger material CIF run and feed to APO.
Hope this solution will work in your case.thanks
Sanjay Karkun

IDOC HRMD_A + Change pointers + Infotypes change objects doesnt exist???

Hi guys,
I Have to send master data from infotypes 0002, 0006, 0032 and 0105 from HR to SAP PI. I've configured BD61, BD50 and BD53 to reduce Idoc HRMD_A. Then in BD52 I've tried to put this fields to activate change pointers when data from this infotypes is changed.
But in BD52 doesnt exist infotypes 0002, 0006, 0032 and 0105. I tried with object HR_IT1002, table HRP1002 and fields BEGDA and ENDDA, then run program RBDMIDOC and the Idoc is sent, but is possible with infotypes metioned????
Regards,
Pablo

Pablo,
are you able to see entries getting created in BDCP* tables
did you activate change pointers in BD53
Thanks
Bala Duvvuri
Edited by: Bala Duvvuri on Jul 29, 2010 10:35 AM

Idoc and change pointers question.

Hi everybody,
How can I create a change pointer automatically for a change document on table JCDS? Becuase I can create change pointers for the change documents on table CDHDR, but I need to catch a technical object status change and create an idoc for the object that changed its status.
Thanks,

Hi Fernando,
I'm trying to accomplish the same thing that you were... trying to get a change pointer to be created based off the status change of a technical object (functional location or equipment).
Can you give me any detail on what you did?
Thanks,
John

Use change pointers to send complete employee in HRMD_A

Hi
I need to distribute employee data from my SAP system. I want to send a Idoc every time a record in PA30 is changed. But know it only sends out a IDoc with the infotype that is changed, I need to distribute all infotype's.
Example: One person is changed in infotype IT0002. I need to send out not only IT0002 but also IT0006 and IT0008.
Is there a way to solve this?
Best Regards,
Morten

Hello Morten,
Yes, you can do it. I have done same thing in one of my interface. You need to write code into BADI.
BADI : BDCP_BEFORE_WRITE
Method : FILTER_BDCPV_BEFORE_WRITE
Basic idea is to populate internal table change_pointers with remaining infotype details.
Refer following code for reference....
BADI implemented in order to send customised data as
maintained in the distribution mdoel
METHOD if_ex_bdcp_before_write~filter_bdcpv_before_write.
Type Declaration
TYPES : BEGIN OF ts_range,
            sign    TYPE tvarv-sign,
            option TYPE tvarv-opti,
            low     TYPE tvarv-low,
            high    TYPE tvarv-high,
          END OF ts_range.
TYPES : BEGIN OF ts_group,
            int_grp     TYPE zthr_infty_subty-int_grp,
          END OF ts_group.
Internal table
DATA:
    lt_zthr_infty_subty TYPE TABLE OF zthr_infty_subty,
    lt_dist_infty_subty TYPE TABLE OF t788u,
    lt_groups           TYPE TABLE OF ts_group.
DATA:
    lt_changed_objects TYPE TABLE OF hrobjinfty.
DATA :
    lr_infty    TYPE RANGE OF t591s-infty, " Range for infotypes
    lr_subty    TYPE RANGE OF t591s-subty. " Range for subtypes.
Work Areas
DATA:
    lw_change_pointers   TYPE bdcpv,
    lw_change_pointers1 TYPE bdcpv,
    lw_text(254)         TYPE c,
    lw_infty             TYPE ts_range,
    lw_subty             TYPE ts_range,
    lw_groups            TYPE ts_group.
DATA:
    lw_zthr_infty_subty TYPE zthr_infty_subty,   "Infotype & Subtype
    lw_zthr_infty_subty1 TYPE zthr_infty_subty,   "Infotype & Subtype
    lw_dist_infty_subty TYPE t788u.              "Infotypes
DATA:
    lw_changed_objects   TYPE hrobjinfty,
    lw_changed_objects1 TYPE hrobjinfty,
    lw_changed_objects2 TYPE hrobjinfty.
Local Variables
DATA:
    lv_tabix      TYPE sy-tabix,      " Table index
    lv_cpident    TYPE cpident,       " Change pointer no.
    lv_pernr      TYPE pa0000-pernr, " Employee Number
    lv_tabname    TYPE dd02t-tabname, " Table Name
    lv_abkrs      TYPE pa0001-abkrs, " Payroll Area
    lv_infty(4)   TYPE n.             " Infotype Number
Local Constants
CONSTANTS:
    lc_e       TYPE t591s-sprsl   VALUE 'E',
    lc_i       TYPE tvarv-sign    VALUE 'I',
    lc_x       TYPE c             VALUE 'X',
    lc_7       TYPE c             VALUE '7',
    lc_p       TYPE otype         VALUE 'P',
    lc_zhrmd   TYPE edi_mestyp    VALUE 'ZHRMD_A',
    lc_eq      TYPE tvarv-opti    VALUE 'EQ',
    lc_pa(2)   TYPE c             VALUE 'PA',
    lc_begda   TYPE sy-datum      VALUE '19000101',
    lc_02      TYPE pa0001-abkrs VALUE '02',
    lc_1000(4) TYPE n             VALUE '1000',
    lc_2000(4) TYPE n             VALUE '2000'.
Clear all local variables / internal tables / Work Areas
REFRESH : lt_groups,
            lr_infty,
            lr_subty,
            lt_changed_objects.
CLEAR : lv_tabix,
          lv_abkrs,
          lw_change_pointers,
          lw_dist_infty_subty,
          lv_tabname,
          lw_groups.
Select only otypes and infotypes from distribution model
Read change infotype / subtype data
IF NOT change_pointers[] IS INITIAL.
    LOOP AT change_pointers INTO lw_change_pointers.
      lw_changed_objects = lw_change_pointers-tabkey.
Filter CE Employee if Pay-Area not '02'          ***
      IF flt_val EQ lc_zhrmd.    " Check for CE emploeyee
        SELECT abkrs
          INTO lv_abkrs
          FROM pa0001 UP TO 1 ROWS
        WHERE pernr EQ lw_changed_objects-objid
          AND endda GE sy-datum
          AND begda LE sy-datum
          AND abkrs EQ lc_02.
        ENDSELECT.
        IF sy-subrc EQ 0.
          APPEND lw_changed_objects TO lt_changed_objects.
        ELSE.
          DELETE change_pointers.
        ENDIF.
      ELSE.
        APPEND lw_changed_objects TO lt_changed_objects.
      ENDIF.    " IF flt_val EQ lc_zhrmd.
    ENDLOOP. " LOOP AT change_pointers INTO lw_change_pointers.
    lv_cpident = lw_change_pointers-cpident.
ENDIF. "IF NOT change_pointers[] IS INITIAL.
Select only otypes and infotypes from distribution model**
Select corresponding infotypes / subtypes from table    **
ZTHR_INFTY_SUBTY to create change pointers              **
CALL FUNCTION 'RH_DISTRIBUTED_INFOTYPES'
    EXPORTING
      message_type            = flt_val
      check_model             = lc_x
    TABLES
      distributed_infty_subty = lt_dist_infty_subty.
IF NOT lt_dist_infty_subty[] IS INITIAL.
Read table ZTHR_INFTY_SUBTY
    SELECT mandt                         " Client
           mestyp                        " Message Type
           infty                         " Infotype
           subty                         " Info Subtype
           int_grp                       " Change pointer group
      INTO TABLE lt_zthr_infty_subty
      FROM zthr_infty_subty AS a
      FOR ALL ENTRIES IN lt_dist_infty_subty
      WHERE mestyp EQ flt_val
        AND infty EQ lt_dist_infty_subty-infty.
    IF sy-subrc EQ 0.
      CLEAR : lw_changed_objects.
      LOOP AT lt_changed_objects INTO lw_changed_objects.
        MOVE : lw_changed_objects TO lw_changed_objects2.
        AT NEW objid.
Read all groups belongs to infotype.
          CLEAR : lw_groups.
          REFRESH: lt_groups.
          LOOP AT lt_zthr_infty_subty INTO lw_zthr_infty_subty
                  WHERE infty = lw_changed_objects2-infty
                    AND subty = lw_changed_objects2-subty.
            lw_groups = lw_zthr_infty_subty-int_grp.
            APPEND lw_groups TO lt_groups.
          ENDLOOP. " LOOP AT lt_zthr_infty_subty INTO ....
Do not create change pointer if infotype not maintained in
table 'ZTHR_INFTY_SUBTY'.
          IF sy-subrc NE 0.
            DELETE change_pointers WHERE
                        tabkey+12(4) = lw_changed_objects2-infty
                    AND tabkey+16(4) = lw_changed_objects2-subty.
          ENDIF. " IF sy-subrc NE 0.
Read all infotypes belongs to all above groups.
          LOOP AT lt_groups INTO lw_groups.
            LOOP AT lt_zthr_infty_subty INTO lw_zthr_infty_subty
                          WHERE int_grp EQ lw_groups-int_grp.
Check if change pointer already present
              READ TABLE lt_changed_objects INTO lw_changed_objects1
                  WITH KEY infty = lw_zthr_infty_subty-infty
                           subty = lw_zthr_infty_subty-subty.
              IF sy-subrc NE 0.
Check if data exist for infotype / subtype
                IF lw_changed_objects-otype EQ lc_p.
                  CONCATENATE : lc_pa lw_zthr_infty_subty-infty
                         INTO   lv_tabname.
                  SELECT SINGLE pernr
                    INTO lv_pernr
                    FROM (lv_tabname)
                   WHERE subty EQ lw_zthr_infty_subty-subty
                     AND pernr EQ lw_changed_objects2-objid.
                  IF sy-subrc EQ 0.    " Change pointer for employee
Create change pointer for infotype / subtype combination
                    ADD 1 TO lv_cpident.
                    lw_change_pointers-cpident      = lv_cpident.
            lw_change_pointers-tabkey+12(4) = lw_zthr_infty_subty-infty.
            lw_change_pointers-tabkey+16(4) = lw_zthr_infty_subty-subty.
                    lw_change_pointers-tabkey+20(8) = lc_begda.
                    APPEND lw_change_pointers TO change_pointers.
                  ENDIF. " IF sy-subrc EQ 0.
                ELSE.
Create change pointer for Org Data
                  ADD 1 TO lv_cpident.
                  lw_change_pointers-cpident      = lv_cpident.
            lw_change_pointers-tabkey+12(4) = lw_zthr_infty_subty-infty.
            lw_change_pointers-tabkey+16(4) = lw_zthr_infty_subty-subty.
                  lw_change_pointers-tabkey+20(8) = lc_begda.
                  APPEND lw_change_pointers TO change_pointers.
                ENDIF. " IF lw_changed_objects-objtyp EQ lc_p.
              ENDIF. " IF sy-sybrc NE 0.
            ENDLOOP. " LOOP AT lt_zthr_infty_subty INTO..
          ENDLOOP. " LOOP AT lt_groups INTO lw_groups.
        ENDAT. " AT NEW objid.
      ENDLOOP. " LOOP AT lt_changed_objects INTO lw_changed_objects.
    ENDIF. " IF sy-subrc EQ 0.
ENDIF. " IF NOT lt_dist_infty_subty[] IS INITIAL.
ENDMETHOD.
But make sure you maintained remaining infotypes in distribution model. I have created table zthr_infty_subty twhere I am keeping track of all infotype and subtype for which I have to send a data.. You can hardcode values in u r program if you want / if you know the all infotype for which you have to send data.
if you still have any doubt / issues let me know your email id will mail you badi-code.
Cheers,
Nilesh

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

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.

Change pointers to trigger the IDOC

HI
I am having a selection screen with fields to create a custom info record (transaction VD51/ VD52 )
Customer
material
salesorganisation
distribution channel
division
if we can use change pointers to determine when procedure is triggered.
Please provide the steps for that (including change document)or we need to check the CDHDR table using the following fields.
Plz suggest

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.
Reward if useful

Need to trigger change pointers for a change in std text

I need to trigger an idoc via change pointers when any change in a std text occurs. I am doing this for changes in Customer Master. For example, if the std text obtained via tcode XD02 is changed, then I need to trigger an idoc. Is this possible? What is the object class used?
Thanks,
Keerthi

Hi,
All Standard text views are stored in V_E071.
Use the View for V_E071 for checking standard text transport
Give Object Filed Name = TEXT and check
And search the standard object
Go to se09 create workbench request and
Double Click the request and go to program give R3TR and Object: TEXT and object Name: TEXT, Nike_FT_AB_4700, ZEPC, D
Object: TEXT
Where Nike_FT_AB_4700 is Customized Name of Standard Text
Text Id: ZEPC (Default: ST)
Language: D (DE)
Go to SE03 double click the Search for Objects in Requests/Tasks in the
R3TR Object ; TEXT and do search.. with respective to that you will get change request.
Do rewards points.

Trigger IDOC using change pointers

Similar Messages

Maybe you are looking for