Deleting change pointers in IDOC
Is there any other way to delete change pointers other than using transaction code BD22?
Hi,
u can activate/deactivate change pointer using Transaction code BD50. Guess this will be helpful.
Similar Messages
-
Deletion change pointers are not going to ECC after C5
Hi,
My issue is that I am running C5 after Planning run.But deletion change pointers are not going to ECC.Because of this we have duplicate of orders in ECC.We are running CCR to bring back the "Planned orders with deletion change pointers and deleting again using RRP4.Why deletion change pointers are not going along with creation change pointer?Help will be highly appreciated.
Thanks&Regards
VenkadeshHi,
Check whether you have enabled the " delete events" check box. This check box will be valid if you are publishing the planning results thru background job.
If you set this indicator, the system deletes all selected change pointers without sending them first.
Thanks,
nandha -
Hi
Does anyone know the standard application which deletes consumed/processed change pointers from the tables.
This i want since, it is having lot of entries in change pointers and i want to delete the processed change pointers to improve the performance.
shyleshHi Sailesh,
You can use standard program <b>RBDCPCLR</b> (t/code BD22) to delete change pointers.
For more information on chnage ponter, please check this link.
http://help.sap.com/saphelp_erp2005/helpdata/en/12/83e03c19758e71e10000000a114084/content.htm
Hope this will help.
Regards,
Ferry Lianto -
This is to send the data from SAP to third party system . For data mapping, we have used the exit 'EXIT_SAPLRHA0_003' in the enhancement 'RHALE001' . Iam using the message type 'HRMD_A' and the basic type 'HRMD_A07' . I have activated the change pointers. How to test this?
Hi,
Please goto we02 and check whether the idoc is generated or not , when you change master data and executed RBDMIDOC.
If yes Check the segment to which you have made changes to populate the data using EXIT.
Thanks and Regards,
P.Bharadwaj -
Change pointers and Idoc creation
Hello,
I would like to create change pointers for any changes regarding one of our customer infotypes: 9002 (hrp9002)
I was able to do that, however, I'm struggeling with the details.
The problem is that I do not want to send any data related to infotype 9002. I just need this change pointer to trigger idoc creation for the related objects.
Example: Let's assume that infotype 9002 gets created for position S 40001234. Once a night a customer report is executed via a job which reads all unprocessed change pointers (including the one mentioned above) and sends the corresponding object. In this case, an Idoc for the holder of position 40001234 should be created WITHOUT data for infotype 9002.
The message type is HRMD_A.
What do I need to do?
Thank you for your input.Hi,
For Info type 9002 we need to implement Badi HRALE00CHANGE_PTRS using below code.
LOOP AT t_changed_objects INTO wa_changed_objects .
CASE wa_changed_objects-infty.
WHEN '9002'.
wa_cp_data-tabname = 'HROBJINFTY'.
wa_changed_objects-plvar = '01' .
wa_cp_data-tabkey = wa_changed_objects .
wa_cp_data-cdchgid = 'U'.
* wa_cp_data-CDOBJCL = 'HRMD_A'.
APPEND wa_cp_data TO t_cp_data1 .
ENDCASE.
ENDLOOP.
IF t_cp_data1 IS NOT INITIAL .
CALL FUNCTION 'CHANGE_POINTERS_CREATE_DIRECT'
EXPORTING
message_type = 'HRMD_A'
TABLES
t_cp_data = t_cp_data1
EXCEPTIONS
number_range_problems = 1
OTHERS = 2.
IF sy-subrc <> 0.
* Implement suitable error handling here
ENDIF.
ENDIF.
This code will create entry in BDCP2 table.
After thsi populating segemnet you need to code for below exit as .
EXIT_SAPLRHAL_003
IF PNNNN_NAME = 'P9002' .
*FIELD-SYMBOLS: <FS_plog> TYPE ANY. "Field Symbol for dynamic filling of data based on the structure
*Clearing the SUBRC
CLEAR SUBRC.
* fill workarea for infotype with infotype-data
ASSIGN pnnnn_data TO <FS_plog> CASTING TYPE P9002.
LS_9002 = <FS_plog>.
* move fields
MOVE-CORRESPONDING LS_9002 TO LS_p9002.
* fill IDoc-data with workarea for segmenttype
ASSIGN sdata_data TO <FS_plog> CASTING TYPE Z1P9002.
<FS_plog> = LS_P9002.
CONVERTED = ZCDP_IF_CONSTANTS_DTIRIS=>GC_CROSS .
ENDIF.
It will work fine.
Thanks
Anju -
1. Does anyone know if the process of deleting a material from a BOM can be configured to create change pointers?
2. Same change pointer question for after the materials are deleted from the BOM and the BOM header is marked for deletion.
Your feedback is much appreciated.Hi nlira,
1. Does anyone know if the process of deleting a material from a BOM can be configured to create change pointers?
Your question is not clear. As i understand you know how to delete a line item in BOM and you want to know if change pointer picks it up at line level.
If you activate BOMMAT in BD50, all changes should be captured from BOM.
Before that, check TCODE- BD52 for message type BOMMAT to see you have all the fields listed which you want to capture.
Typically in your case its LKENZ for STPO which is not added by default in sap. You have to add it to capture.
2. Same change pointer question for after the materials are deleted from the BOM and the BOM header is marked for deletion.
I did not understand this question.
BOM Header Deletion indicator STKO- LOEKZ is captured for BOMMAT message Type.
Let me know if i answered your question.
Thanks,
Shekhar Ramineni -
Please conduct a simple question. T-code BD52 is Maintain change-relevant fields for message type,the first column is 'Object', the contents of this column can be maintained in where?
Thanks a lot.>
Hao Zhang wrote:
> Please conduct a simple question. T-code BD52 is Maintain change-relevant fields for message type,the first column is 'Object', the contents of this column can be maintained in where?
> Thanks a lot.
Hi,
CDHDR,CDPOS,BDCP,BDCP2 and BDCPV are the tables related to change pointers. These change Document objects are stored in CDHDR and CDPOS. CDHDR contains header level information and CDPOS contains item level information
Regrds
Vinod -
Restrict IDoc creation by using deactivate change pointers
Hi Experts,
I am trying to restrict the creation of IDOCS by deactivate the change pointers from a ztable. if the record in ztable and BDCP table match then i should deactivate the change pointer. And restrict the creation of Idocs.
pls, suggest me soon... its urgernt.......
Regards,
CHKMaybe using program RBDCPCLR to delete change pointers you don't want to use?
-
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 -
Help With IDOC Change Pointers
Hi guys,
I'm trying an IDOC to file scenario. The scenario is working fine. I have activated change pointers for my IDOC. My understanding was that if there will be any change in my master tables, then because of the activated change pointers, the IDOC will be generated automatically. But in my case, for eg if i'm inserting any new record say Vendor data, no new IDOC is generated. For sending IDOC i have to use bd14 to send my IDOC explicitly.
Is my idea of change pointers wrong???Or am i missing some setting, so that the IDOC should be generated automatically???
Please help me on this guys...
Regards
Varun<b>Automatic generation of IDOC when we change the MASTER DATA:</b>
<b>Change Pointers:</b>
Change documents are working based on change document technique which
tracks changes made to the key documents (Material Master, Customer Master,
Vendor Master.Etc) in SAP.
Changes made to the keydocuments are recorded in the change document Header
table i.e. CDHDR and Item table CDPOS, Additional change pointers are written
in the BDCP and BDCPS tables.
Change pointers technique is used to initiate the outbound process automatically
when master data is created or changed.
A standard program RBDMIDOC is sechuled to run on periodic basis to evaluate the change pointers for a message type and starts the ALE process for distributing the Masterdata to the appropriate destination.
'Object' is collection of fields of different database tables. T.code for creating an object
is SCDO.
<b><u>Configuration for Change Pointers:</u></b>
1. BD61 Active change pointers generally
- Check the checkbox "Change pointers activated -generally"
- Save it
2. BD50 Active change pointers for Message Type
Message Type Active
MATMAS Check the check box
3. SCDO Change Document Objects
- Check whether the "MATERIAL" is available in the object list.
4. BD52 Maintain Table Views
- Enter the Message type "MATMAS" and press enter.
For example
OBJECT TABLE NAME FIELD NAME
MATERIAL MARA BISMT
5. BD60 Additional data for message types:
For example:
Message Type Function Module Table
MATMAS MASTERIDOC_CREATE_SMD_MATMAS MARA
6. WE21 Port
7. WE20 Partner Profile
8. BD64 Distribution Model
as michal said we have to use RBDMIDOC program.for executing this program we need to give message type like
MATMAS or
DEBMAS or
CREMAS
depending on your requirement.
go to SE38 tcode
--- copy RBDMIDOC to zprogram(i'e., ZRBDMIDOC)
---create variant
use this zprogram(ZRBDMIDOC) in BACKGROUND SCHEDULING SM36
<u>STEPS IN BACKGROUND SCHEDULING:</u>
Use tcode SM36
Click Job wizard in the button set
Click Continue
Enter Job name and press continue
Select ABAP program and press Continue
enter Program name and press continue
and again press Continue
set Schedule type immediately and continue
Select periodic job checkbox, press continue
Select none of the above and click on other periods give one-minute and then press create
Press continue and then press complete.
recently i did this requirement
if u have any doubts plz let me know
Best Regards,
Srikanth
Reward the useful answers and you will get one point yourself -
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,
SRavanWhen we remove an Cost center it physically gets deleted from the data base.There is no delete indicator as such
-
IDoc to CRM - change pointers?
Hi,
I'm currently involved in scenarios where I need to post various CRMXIF_* IDocs to CRM.
What I'm wondering is, if I need to maintain change pointers in the IDocs - that is at header and item level maintain the fields OBJECT_TASK or TASK with proper values being either U (UPDATE), I (INSERT), C (CURRENT STATE), D (DELETE)?
Now I've never had to do this before in any other IDoc scenario I've developed, so it would surprise me a little if its necessary - but need to be sure. It's my impression that SAP handles this internally and automatically, so that there is no need to worry about it!?
Hope someone can clarify it for me:-)
Best Regards and thanks in advance,
DanielHi,
Change pointer concept is in R3 side not in Xi side.That is to be created and activsted in R3 Side and send the Idoc by triggering the change pointer.
So see the below link to ge more details.
http://help.sap.com/saphelp_nw04/helpdata/en/ab/27bde462848440ba70cf8eb348c86f/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/12/83e03c19758e71e10000000a114084/frameset.htm
Creating a change pointer and subsequently triggering an IDOC
Regards
Chilla -
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 -
Creation of Idocs from the change pointers by the program RBDMIDOC
Hello,
I'm Creating Idocs from the change pointers by the program RBDMIDOC.
The IDOCS Created using the message type HRMD_A are Correct but when i try to RUN RBDMIDOC for message type HRMD_B no Data is selected for distribution.
All the customizing are similar and i presume that all the change pointers are active (BD50 and IMG->Personnel Management -> Organizational Management -> Basic Settings -> Activate change documents).
Can anyone help me with the necessary steps to create this IDOC types.
Do anyone know if the RBDMIDOC report is the Same for messages HRMD_A and HRMD_B.
Thanks in Advance,
Pedro FerreiraIf the setting is fine, there may be some code in exit or badi for program RBMIDOC. Check the Exit and BADI.
check the exit EXIT_SAPLBD11_001 and
check the badi IDOC_CREATION_CHECK.
Probably there may be some code on these exits which are stoping your code from getting generated.These are the two trigger happen once u execute the RBMIDOC program.for HR, we use RHALEINI program to generate the idoc. but even RBDMIDOC works. These 2 triggere will come with RHALEINI also.
If there is no code here, Then there is problem in the setting only. -
IDOC trigger using Z change pointers for standard SAP table
For IDOC trigger, is using custom change pointers on standard SAP master data tables, a good idea? A seasoned abaper told me "it will mess with the standard" and further told to go with scheduled job.
So, for example, say that my data for table T001K is updated via transports in PRD and I need to transfer this updated data via IDOC to an external system. Since there is no standard message type for this data, I will create a new one. Further, I will create a new change pointer for table T001K (it already has six fields with their data elements activated for Change Documents). Then I link the message type and the new change pointer. And so on an so forth. I have followed the procedure given here:SAP Tips: A to Z of Custom Change Pointer
Now, the question is, will this be a good idea to capture data and trigger IDOC? Or a batch program with calls to standard FM to read CDHRD/CDPOS be a more suitable option.
I need to know if a near instantaneous data transfer (and an effecient one as far as the system performance and reliability is concerned) can be acheived. If there is any other way of doing this, I am not aware of it!
Any one has any input/experience on this?Hi Viktor,
I think the batch program approach would be a good solution as the by this way you are taking matter into your own hands rather giving control to the SAP framework because you may have to test out the other approach as to how the standard SAP framework is behaving for custom change pointers.
Thanks,
Ravi
Maybe you are looking for
-
Problem, trying to play many sound files
hello, I did not find a specific answer to my question in most of the archives and so I am posting here. my problem is that I have to play a sound when mouse moves over an object and another sound when the same object is clicked. there are many such
-
When you buy a new ipad air is it locked to a carrier
I have just purchased a Ipad Air Cellular in the UK , it came with a Pre Loaded EE nano sim, can you tell me if that means my Ipad is Locked to that carrier? as it also had the option to have it without the sim included?
-
Switching Sun Ray to one of two exicting servers
I have the same problem as (bugjuice )-I need to switch session on Sun Ray terminal between two servers depending wich card been insrted...I searched all sun blogs,read this posts but still can understand how to cinfigure AMGH and scritp,official man
-
Folio Producer: Scheduling can only be applied to private folios
Um, why is there this limitation? we have our work done, but now i need to get to my computer at midnight (i can't use any iOS device) and clik update. Why?
-
Viewing became black in iMovie
I was working on a project in iMovie and i saved and quit and came back later and the project was messed up. The clips showed up in the bottom timeline, but in the big viewer, it was black. The sound was playing and everything, and I could view clips