Activate change pointers
Hi
all SAP Gurus
if I have a transaction to create products and skus and would like to activate the change pointers as soon a s there is any kind of change occuring , creating or , deleting the records, and there should be an IDOC created. this is my requirement , please suggest me how to.
I am activating the change pointers with the appropriate fields in the message type.
how will it happen can anyone explain me the procedure
every line of ur explination is appreciated
thanks
do the following steps for Change pointers ::
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
Raja T
Similar Messages
-
How to activate change pointers for HRMD_A message
Hi all,
I want to activate change pointers for HRMD_A message for intotypes 0001, 0002, 0006.... .
But I can't find any change object which I could use in BD52 transaction.
Is there any delivered change object by SAP for HRMD_A message?
Could you please tell me which change object should be used for example for infotype 0001?
Thanks a lot.
PetrThere seem to be a number of related questions asked and answered in the forums. Have you searched?
Rob -
Activate Change pointers for TREX classification search for Business Objects
Hey all...
Does anyone out here has any idea on how to activate the change pointers for TREX classification search for business objects: - for me I am specifically doing it for Materials and Customers.
Okay, let me explain the issue: -
For TREX search, we need to schedule a background job for Delta Indexing. But Alas! Delta indexing does not capture the changes to Classification data of the business object.
For this we activated the change documents for the particular class in the customizing. But to my surprise, change documents and change pointers for TREX are entrirely different.
How do I know:
Change ID of CDHDR does not correspond to Change pointer in table COM_SE_CPOINTER. Now by activating the change documents I am getting entry in CDHDR and CDPOS but the mentioned change pointer table still does not get the entry.
I searched for BTEs and I got the below: -
Now to me the very obvious one was 4003, but it is not called while changing the classification data for materials. Ofcourse I activated the Product and the function module.
and now I am stuck!!
Any pointers for the Change pointers would be really appreciated??
Please share your knowledge even if you don't know the exact answer . I am new to TREX so possibly vague conversations could provide me a hint .
Thanks,
Best Regards,
ShreyaHi Guys,
This issue was solved by implementing the BTE 4005 (OPEN_FI_PERFORM_00004005_E). This particular event is triggered in the update task for saving changes to business object. So In my function module (corresponding to BTE), I have explicitly called the method to write an entry in COM_SE_CPOINTER, because we just need the reference of business object for which classification data is changed.
Please refer the below code for more clarity.
BTE position: -
method called in FM to write change pointer.
Thanks anyways, for all the responses.
Cheers,
Shreya -
Activate Change Pointers for Purchase Orders
I thought that change pointers would be active by default for purchase orders, but when I change a purchase order field that should be change pointer enabled, nothing is written in table BDCP.
Here's what I have done:
1) Used transaction SCDO to look at the change Documents.
2) Identified object EINKBELEG (Purchasing Document) as the likely object.
3) Verified that table EKKO is one of the tables in the object.
4) Verified that the data element of the field that I am changing in the PO - ZBD2T - is change pointer enabled (it is).
I cannot get any entry created in BDCP with these settings; change pointers are working for other documents.
I also put a breakpoint on the sebugger for the function module EINKBELEG_WRITE_DOCUMENT in the update task, and I cannot see it being triggered, so I am wondering if I am doing the correct thing here.
Can somebody please tell me what I am doing wrong?
BR,
Tony.Hi Guys,
This issue was solved by implementing the BTE 4005 (OPEN_FI_PERFORM_00004005_E). This particular event is triggered in the update task for saving changes to business object. So In my function module (corresponding to BTE), I have explicitly called the method to write an entry in COM_SE_CPOINTER, because we just need the reference of business object for which classification data is changed.
Please refer the below code for more clarity.
BTE position: -
method called in FM to write change pointer.
Thanks anyways, for all the responses.
Cheers,
Shreya -
Activate change pointers for Z-idocs
Hi friends,
I've created a Z-idoc for some standard SAP tables (like TCJ1T, TCJ05 etc). I've written a function module which fetches all the data from the above-mentioned tables and pass it on to the idoc. So far so good.
Now the requirement is like, I need to pass only the updated records (insert/update/delete) in these tables to the idoc. I found that there are concepts like change document and change pointers assosciated with it. Again, the fields that I need to transfer in the above tables have their change document flag set. I've also created a Z-Object through SCDO to capture the changes. (I initially tried adding the tables in the standard object PROJ regenerated the programs, but the approach didn't work). The function modules generated through SCDO, i guess, have to be called somewhere, may be in an exit (I got an info in a previous question that it is never called automatically, but has to be called explicitly). The entries for most of the tables I'm working with are created via SPRO (which links to the Table Maintainence Generator for the above tables). I found that there are no user-exits for the transactions SPRO and SM30, to call these function modules in the first place.
Change pointers refer to the tables CDHDR and CDPOS, the tables which the change document updates (as found in the function module CHANGE_POINTERS_CREATE). Now, how do I track the updates on these tables, since the change pointers itself is dependent on the change documents and I couldn't find a place to incorporate the function module call that would update the change document tables?
Any help is appreciated.
Thanks & Regards
Anil MadhavanHi Anil,
In SM30 you have programmable events:
Environment -> Modification -> Events
Here's the link to documentation teaching how to create change documents:
http://help.sap.com/saphelp_47x200/helpdata/en/2a/fa015b493111d182b70000e829fbfe/frameset.htm
I'm also trying to learn how to access the needed data in these SM30 events so that I can call the function to generate the change document with the right data in SM30
Let me know if this was useful.
Bye,
Nuno -
Activate change pointer for a new screen field in MM42/41
Hi,
I created a new screen field for Article master(MM41/42/43) under basic data. If there are changes made to this new field how will the system create a corresponding IDOC? does this have something to do with the change pointer thing?
Thanks,
JeffHi Jeffrey,
first of all got transaction SALE :
ALE
-> Modeeling and Implementing
-> Master Data Distribution
-> Replication
-> Activate Change Pointer generally
Check if Changepointers are generally on.
Then goto BD50 and activate change pointers fpr message type.
Finally goto BD52 and check if your field is "watched".
After that you can generate idocs from BD21.
Hope it helps. -
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 -
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,
PabloPablo,
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 -
Change pointers for custom message type
Hi All,
Please help me with questions.
1. The requirement is to add two additional fields to CSCK table and then activate change pointers for COSMAS. My question is when I activate the change pointers for COSMAS will it send this two z fields when there is a change?
2. I dont see a message type in BD50 for a standard IDOC Internal_order? Can I add that standard message type? How can I do this? WIll this create an IDOC when ever there is a change in data?
Thanks.Hello Oscar,
1. Which changes should be relevant for creation of COSMAS-IDoc, you have to define in BD52.
2. You need to define INTERNAL_ORDER in WE20. In BD64 you add BAPI "InternalOrder.SaveReplica", filters can be added.
Best Regards, Dirk -
ALE IDOC change pointers - Msgtype CLFMAS
When making a change to a material class of a material a change pointer is created (as expected) for message class CLFMAS.
In the IDOc segment E1OCLFM of CLFMAS, OBTAB = ESTVA (instead of MARA as expected).
Where does this config take place?Hi Appana,
Thank you for your time. I did checked all these steps still no luck.
1.Go to the Data Element of the field and check whether change doucment option is checked or not .
DONE
2.change the value of the field and check the entries in CDHDR and CDPOS.here u can check the change document object and table .
DONE
3.check BDCP table also incase of ALE.The program RBDMIDOC generates IDOc when there is an entry in BDCP.
if not check the following config
1.BD61- change pointers activated -generally
DONE
2.BD50 -Activate change pointers for ur message type
DONE
3.BD52 - add the triggering fields and corresponding tables and change document object.
DONE
Please check the entries in BDCP table ,if u find the entries execute the program RBDMIDOC
DONE
Any places I missed ? Please note usual ALE config has been done like SM59,WE,20,WE21 etc. Iam basically sending this Idoc to XI and then to 3rd party system. -
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. -
Providing the message types to included for change pointers
Hi Everyone,
How can we Provide the message types to be included for change pointers.?
How can we turn-on Change pointer update generally?
Iam converting the idoc to XML format in XI , So. i need the queries to solve( understand)
Thanks
Manju
P.S. Points will be rewarededHi Manju,
How can we provide the message types to be included for change pointers?
You can use transaction BD50 to activate change pointer for a message type.
How can we turn-on change pointer update generally?
You can use transaction BD61 to activate change pointers generally.
Regards,
Ferry Lianto -
Regd. change pointers and notifications
Hi,
The question might sound a little too broad.
But bear with me...Just give me a brief overview,
of how do I go about using change pointers....
Just correct me if I am wrong.
We create a change document object in the system, or use an existing one. About pointers I am not sure.
Then, through SPRO and ALE we activate the change pointer for some message type. then....??Hi,
I haven't done this in a while, so please check my answer!
1) You activate change pointers in general in one transaction (I think it was BD61, but I'm not sure)
2) Then you activate them for certain master data (i. e. material, customer, ...) in another transaction which I don't recall atm.
3) Every time one of those master data objects is changed, the system generates a "change pointer", which you can basically just think of as an entry in a transparent table, which includes the type and key of your master data object (such as e. g. the material number).
4) You plan a background job which will go through those change pointers and which will generate a master IDoc (e. g. MATMASxx) for this data object. The change pointers are then reset (i. e. every item will only be sent once).
5) Depending on your ALE customization this master IDoc will be sent to a remote system.
You can refine this scenario using quite a bunch of different techniques. One of them is filtering (e. g. only materials with a certain material group, or based on classification etc.). Other options are reducing the Master IDoc, e. g. sending only relevant data instead of the whole master IDoc. There are even a few customer exits, if that doesn't suffice.
Hope that helps (please reward me if it does)!
Regards, Joerg -
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,
vinayChange 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 -
ALE Idoc Change Pointers Question
Though I selected Transfer Immediately on Partner Profile screen, why Idoc hasn't been generated and transmitted?. Why do I have run RBDMIDOC explicitely to pickup change pointers?. Appreciate your responses.
Hi Appana,
Thank you for your time. I did checked all these steps still no luck.
1.Go to the Data Element of the field and check whether change doucment option is checked or not .
DONE
2.change the value of the field and check the entries in CDHDR and CDPOS.here u can check the change document object and table .
DONE
3.check BDCP table also incase of ALE.The program RBDMIDOC generates IDOc when there is an entry in BDCP.
if not check the following config
1.BD61- change pointers activated -generally
DONE
2.BD50 -Activate change pointers for ur message type
DONE
3.BD52 - add the triggering fields and corresponding tables and change document object.
DONE
Please check the entries in BDCP table ,if u find the entries execute the program RBDMIDOC
DONE
Any places I missed ? Please note usual ALE config has been done like SM59,WE,20,WE21 etc. Iam basically sending this Idoc to XI and then to 3rd party system.
Maybe you are looking for
-
SAP workflow for purchase requisition and purchase order
Hello Sap Workflow, Can you please help me on building workflow for purchase requisition and purchase order with the necessary screen shots ? your quick response will be greatly appreciated. Thanks in Advance
-
Problem with Ipad3 landscape position
I have a strange problem with my Ipad. When I open a particular page (www.fotohulp.nl/portret.html), and I hold the Ipad in the portret-position, the page displays correctly. However, when I rotate the Ipad to the landscape-position, this page dropps
-
Hi, I have adf master detail data table , I put af:selectbooelancheckbox and autosubmit is true in detail data table .When I click the detail table , valuechangelistener of the af:selectbooelancheckbox is runnig I don't want this situation. Is it pos
-
Hi, I have already configured the different variance categories e.g. input price variance, input qty variance, etc.. Currently, its posting to one GL account - Production Variances. But client's reqt is to classify to material price variance, mate
-
Password issue in Transport Domain
Hi We was getting some problem while releasing the transport request in ERD (SAP Dev server). We was getting error 12. I tried different option but did not worked and then we decided to re-configure the Transport domain (deleted old trasnport route u