Idoc serialization and change pointers automatic trigger

Hello Experts
How to trigger an Idoc automatically once the application has been saved ?
Scenario 1: Here serialization of message types are used, all the idocs in the serialization group must trigger & sent to the receiving system as per the sequence even if any field in the complete serialization group of message type changes (Note No Manual processing using reports Like RBDSER01, RBDSER02 etc..or Batch Jobs)
Scenario 2: Again Idoc has to trigger and sent to the receiving system as per the change pointer configuration once the application has been saved (Note: No manual processing like BD10, BD11 etc.. and no user exits has to invoke while saving the application).
Please let me know is this two cases can be implemented. Thank you in Advance.
Regards
Imran.

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

Similar Messages

Idoc Conversion rule, Change pointers and Filters

Hi Experts,
Please any one can help me out, i need material or clear picture about Idoc Conversion rule, Change pointers and Filters where we can use these concepts what is the befit for these concepts.
Thanks in advance,
Ramesh.

Hi,
Check this link. It has got some of the tutorials you are looking for.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Cheers
VJ

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 Ferreira

If 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.

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,

Creating IDoc Type from Change Pointers using RBDMIDOC

Hi All,
we are executing program RBDMIDOC(Creating IDoc Type from Change Pointers) evrey 15 minuts in background.
Issue : if some jobs are taking more than 15 minuts then next jobs are failed,
is next job will pick up any idocs that were missed?
there is no extesion's and ther is no Z-fields are used in that message type , we are used OILMAT as mesage type.
Regards,
DSK
Edited by: suresh dameruppula on Aug 5, 2008 2:04 PM

Hi,
Include a step in your job and have a program which checks if a job is already running. If yes do not start the next instance of the same job.
in the custom program just call function module
   CALL FUNCTION 'ZBC_JOB_ALREADY_RUNNING'
      EXPORTING
         JOBNAME           = p_job
      IMPORTING
         JOB_RUNNING       = w_count
      EXCEPTIONS
         JOB_NOT_SPECIFIED = 1
         OTHERS            = 2.
Code within FM ->
   select count(*)
   into   job_running
   from   tbtco
   where jobname = jobname
   and    status = 'R'.
where p_job is the job name.
w_count is current running job count. If its greater than 1, then stop the 2nd with an error message.
Rgds,
Hema

Avoid the creation of idoc Debmas with Change Pointers

Hi everybody.
Ive customized the creation of idoc debmas with change pointers.
In BD64 I´ve defined the distribution model but Id like to avoid the creation of the debmas idoc when an specific user has created/modified the custumer data.
How can I get this?
Regards

Hello,
I would suggest to handle this issue with authorization check...
check the authorization object using SU53 and add a separate role for those specific user excluding those objects...
Thanks
K.

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

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

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,
Daniel

Hi,
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

BD10 and change pointers

I'm new to using BD10 to create MATMAS Idocs.
I've set up change pointers, created a change document and then run BD10. The IDOCs I expected were created just fine.
However, the BD10 transaction continues to create new IDOCs every time I run it, even though I haven't made any new changes to the materials.
Is this behavior normal?
I'd like to have the IDOCs created only once.

Hi Ed,
BD10 is for sending material, regardless of any change.
Use BD21 to process change pointers.
Regards,
Frank Umans

Table maintenance generator and Change pointers

If a Ztable contains table maintenance generator, then the change pointers will not work?

Hi Saraoja,
If you want make active your change pointers for your Ztable, then in your Zfields, get into the Data element and click futher Characteristics tab, there you have one check box called Change document, Check that box and activate your data element again.Now your Zfield changes will reflect in CDHDR and CDPOS.
Thanks

Problem in Outbound Idoc Scenario with change pointers

Hi All,
I have a requirement where i have to create an outbound scenario, whenever i create or change in transaction PAL1 (Create Sales Representative), an idoc should be triggered.
i have created
- ZBasic idoc type
- ZSegments
And have assigned the ZBasic Idoc type to ZMessage type
Even I have maintained the fields to be triggered during change pointer in transaction BD52
Now my problem is, whenever i change a field in transaction PAL1 or create a new one, change pointer is not getting triggered via RBDMIDOC program.
Do we need to add an additional code to populate the Zsegments?
If so... can you send me the logic or Sample Code which fits my scenario?
Thanks.

Satish,
you cna check this badi HRALE00OUTBOUND_IDOC
Thanks
Bala Duvvuri

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

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

posting it in data transfer forum..

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 Madhavan

Hi 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

IDoc Configuration for Production Order Creation and Change

Hi All,
Please Help me out for IDoc Configuration for Production Order Creation and Change
I have found the IDoc for Production Order
Messgae Type : LOIPRO and IDoc type : LOIPRO01
Actually my requirment is to send the (LOIPRO01 )IDoc from SAP R/3 to XI system ,when ever the Production Order Created and Changed,
I have done following Configurations:
1. RFC Destination created for XI system
2. PORT was created for XI
3. Partner profile created WE20 and LOIPRO01 IDoc is added in OutBound Perameter.
I need to know how to do the followning.
1. How do i configure the outbound Production order idocs when Production Order is created or changed.
2. in NACE (Output control) which is the Application for Production Order.
3. How can I set IDoc as output Type for Production Order Creation.
Thanks in advance
Dhanabal T

Hi Michal,
I know that it is the old thread but still want to get clarified from you out of curiosity.
Unlike other IDOC, i actiavated change pointers for LOIPRO
1.message and idoc type is linked
2.function module , message type , idoc type is linked
function module used is CLOI_MASTERIDOC_CREATE_LOIPRO
3.BD64, distribution model is created and distributed
4. port and partner profile is in place.
5. IDOC is not getting generated after creating the process order.
do we need to activate the change documents for the message type in BD52,
if yes can you please provide the object types for the same.
or i am missing something else. please guide me in this regards.
Thanks in advance for your time.
S.Janagar

Idoc serialization and change pointers automatic trigger

Similar Messages

Maybe you are looking for