IDoc DEBMAS07 - Change Pointer

Hi.
There is already created an outbound interface for sending customers to legacy system through IDoc > PI > SQL.
As it was defined in DB52:
Object Table Field
DEBI KNA1 LOEVM
When users marks customer for deletion (t-code VD06 or XD02, don't know exactly how) the IDoc is generated, so the customer is deleted from the legacy system.
However, when the same user unmark the customer for deletion, the IDoc should be generated as well once the mark f, shouldn't it?
It's not being generated. Any suggestion of how to fix that?
Tks.

Hi veerendranath, tks for your reply!
Actually, the problem I'm facing has no relation to partners.
If you read it carefully, you will see that the IDoc is being triggered when the user marks the customer to be deleted.
So, the IDoc triggers and interface which performs the deletion in the legacy system. However, when the user access again (maybe through XD02 or VD06 or someway else) and undo tha To-be-deleted flag, the IDoc is not being generated, and it must be triggered and send all the relevant related information for the customer to be created/updated in the target system.
Can someone help on that?
I really appreciate your help!

Similar Messages

IDOC type DEBMAS06 change pointer

Hi,
I am working on idoc to file scenario.
I want to create/send idoc DEBMAS06.It is possible to send all segment of idoc using change pointer.
I am changing customer using XD02,and it send only 2 segment in idoc.There is require ment to pass all segment whenever there is any change in customer data.
Regards
Mohit

Hi Rajesh,
Thanks for your reply.
I have tested bd12 and now it shows more segments then before.
But i need to send idoc automaticaly to pi system ,Is there any way to do so.
Right now i have activated chnge pointer and schedule back ground job RBDMIDOC to send idoc type debmas06 to pi system.
regards
Mohit

ALE Distribution LOIROU Change pointer

Hello
I want to know if it is possible to manage LOIROU idoc with change pointer management in SALE and how ?

Hello Jean,
I think you can manage LOIROU idoc with change pointers.
Steps are as follows:
1. Activae change pointers generally : TC : BD61.
2. Activate change pointer for message type LOIROU using TC : BD50.
3.Create an object for the Change Documents, by transaction SCDO.
4. Maintain Distribution model using BD64.
5. Maintain Partner profile & remaininf basic configuration.
6. After creating / changing document goto transaction BD21 and execute it with Message type LOIROU.
Thats all!!
Cheers,
Nilesh

Change Pointer processing - send all data

HI,
do you know a way to fill the complete IDoc during change pointer processing ?
Example DEBMAS.
IS it possible to fill all segments/data instead of the changed data ?
The normal way is to fill only the changed segments/data.
thx,
Gordon

Hi ,
Please find the sample code to fill the Idoc data.
DATA:     C_INVREV_SEGNAME(7) TYPE C VALUE 'Z1INVRV',
          C_INVREV_MESTYPE(6) TYPE C VALUE 'ZINVRV',
          C_INVREV_IDOC_TYPE(8) TYPE C VALUE 'ZINVRV01',
          Z1INVRV LIKE Z1INVRV,
          C_INVREV_DOCTYPE LIKE BKPF-BLART VALUE 'YY',
          IDOC_CONTROL LIKE EDIDC,
          T_COMM_CONTROL LIKE EDIDC OCCURS 0 WITH HEADER LINE,
          IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE.
*--- Move the document header into a structure
LOOP AT DOC_HEAD_TAB INTO DOC_HEAD.
ENDLOOP.
*--- Move the document item data into a structure
LOOP AT DOC_ITEM_TAB INTO DOC_ITEM WHERE NOT ( LIFNR IS INITIAL ).
ENDLOOP.
*--- Populate the IDoc segments field with the required data
CLEAR Z1INVRV.
Z1INVRV-LIFNR = DOC_ITEM-LIFNR.          Store vendor number for filter
Z1INVRV-XBLNR = DOC_HEAD-XBLNR.          Billing number
IDOC_DATA-SEGNAM = C_INVREV_SEGNAME.     Segment name
IDOC_DATA-SDATA = Z1INVRV.               Segment data
APPEND IDOC_DATA.                    Populate IDoc internal table
Please let me know if u have any Queries
Rgds
Sree M

Suppress Non Changed Fields in change pointer triggered IDOC

I have a requirement to clone message type MATMAS as ZMATMAS. This ZMATMAS is the message type I used to create change pointer triggering outbound idoc for change/create of materials.
When i change a material, all fields are sent instead of the fields only changed(of course key fields should be sent as well). Is there a way via configuration that I can suppress fields which are not changed? Or do i need to clone FM MASTERIDOC_CREATE_SMD_MATMAS and suppress the fields via program
Thanks in Advance!

i'll clarify the requirement again.
Let say i changed a field BRGEW in the material master.
Currently, all the segements which contains BRGEW is sent, but these segements contains other data which are not changed in the material master.
How do i suppress it?
Thanks,

How to find - Customer Master IDoc was created Manually or by Change pointe

Hi all,
I have an IDoc(Customer master) number (which I have taken from the payload in SXMB_MONI). I would like to know whether this has been created by a user manually(BD14) or by a change pointer.
Please help.
Cheers
danus

Hi Vardharajan,
Yes I agree with you. What I mean by IDoc created by change pointer is - 'IDoc generated because a change(pointer) is tracked by the system', in other words, due to some change made to the data.
As you know, the other option of creating IDoc is by BDxx transaction. This option is usually used to push (unchanged) data.
So in essence, what I am interested to know is , has the IDoc been generated because someone made a change using say, VD02 / XD02 or pushed the data manually.
Please do ask, if anything is not clear.
cheers
danus

Idoc trigerring with change pointer under conditions

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

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

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

XI IDOC Master Data Synch with Change Pointer (GLMAST)

Hi,
I have scenario to create integration between 2 SAP system with XI 7.0 using IDOC - GLMAST. I already acitvate Change Pointer Globally (BD61) and Activate Change Pointer for GLMAST (BD50).
The problem is whenever changes have done in system 1, 2 IDOC generated, First IDOC to Logical System PRODUCTION and second IDOC to Logical System SALES.
In order to seding the IDOC i have scheduled report RBDMIDOC. My question is how i can modify the IDOC target port in stead of send to PRODUCTION and SALES to others port (XI in this case).
Thank you and Regards
Fernand

Hi Prateek
I already create partner profile and port for XI and add GLMAST. but then the IDOC generated alwasy sent to PRODUCTION and SALES partner profile.
How to disable that IDOC to send to PRODUCTION and SALES partner profile and only send to XI Profile ?
Thank you and Regards
Fernand

IDOC to XI (Using Change Pointer) - Error

Hi all,
I have 1 scenario to update external GL master data using XI. in this case i already configure the source system (SAP) to sending the IDOC to XI whenever got changes.
BD61 ---> Activate Change Pointer Globally,
BD50 ---> Activate Change Pointer for GLMAST Message Type.
SM59 ---> RFC destination for XI system (PX6CLNT300).
BD54 ---> Logical System source (ST6CLNT100) and target xi (PX6CLNT300)
WE20 ---> Partner Profile for XI (PX6CLNT300).
BD64 ---> Create Distribution Model View. Sender = ST6CLNT100, Receiver = PX6CLNT300 and Message Type = GLMAST
The system can generate the IDOC whenever changes happen with running program RBDMIDOC. but the got error with no sender / receiver information in WE05.
Please advise any step that i have to do ?
Best Regards
Fernand

Hi Matias,
Thank you for your answer. The problem is because i had used wrong logical system in my distribusion model. The system using not common logical system. nomarly it will use "PX6CLNT100" but in my system the basis people using different logical system that's why the GLMAST IDOC cannot pass throught to XI system.
Best Regards
Fernand

Change Pointer to create IDoc

I wrote report program to create outbound IDoc. In the report, to capture create/ change I used table 'CDHDR'. Now I require below clarifications:
1.     Clarify the process of u2018Change pointeru2019 regarding IDoc.
2.     Is it recommended to use u2018Change pointeru2019 to create Outbound IDoc?
a.     If yes, then why do we write report or function module?
b.     Can we use custom message type in this process or only standard message types will work?

Hi
Change Pointer IDOC..??
Regards
pavan

Reg : change pointer mechanism for triggering the IDOC for delivery note

Hi ,
I am working on a change pointer mechanism for triggering the IDOC for delivery note and will be using this message class DESADV.
So SAP has suggested for assigning the message class DESADV with the function module in MASTERIDOC_CREATE_SMD_DESADV in BD60 transaction code.
So I was looking to create this MASTERIDOC_CREATE_SMD_DESADV function module in SAP and SAP suggesting that we should create this MASTERIDOC_CREATE_SMD_DESADV function module as same as the function module MASTERIDOC_CREATE_SMD_MATMAS.
So do anyone knows that is there any tool has been provided by SAP for creating this function module MASTERIDOC_CREATE_SMD_DESADV in SAP system for triggering the change pointer mechanism for outbound Delivery.
Thanks !
Regards,
Kiran

Hi,
When you are change pointer the system itself will take care of sending the changed master data to your partner system and the user will not have any intervention. If you really wanted to have that then you need to use the change pointers to read the master data which is modified in a custom program and then display that on the screen. Once the user selects that master data records then trigger an IDOC for creating the idoc for that master data and also flag that master data record as processed in the SAP BDCPS standard table, so that the same record will not be picked. If you wanted to know how the change pointers piece of code is written go through the program RBDMIDOC and you can understand how the change pointers logic is written.
Thanks,
Mahesh.

Transaction for using change pointer technique in ALE -IDOCS

Hi,
please let me know the following points.
1: while using change pointer technique , any change in the sale order(any field ) will trigger IDOC or only specific field change. Or do we have to specify field on which we want to trigger IDOC?
2:When IDOC gets genrated from change pointer , does it contain complete sales order or only change fields?
3:Do we have Native format of IDOC in 4.6c ?? XML format??
Please reply soon.

Hi,
For the changes to be carried over by change pointers, the steps followed are,
If it's gonna be the vendor master for which change pointers needs to be activated,
- goto SALE transaction ->Modelling and Implementing business processes ->Replication of Modified data -> Activate Change pointers - generally / for message types.... or as said in the earlier post, alternatively BD61/BD50.
- Schedule a background job for program RBDMDIOC providing the message type(CREMAS) for which the change pointers needs to be processed.
- Now for any changes made to the vendor via transaction XK02, automatically CREMAS IDocs would get generated with the IDoc carrying the changed fields in it. You would also be able to find the number master and communication IDocs generated from the joblog of the scheduled RBDMIDOC background job.
~ Bineah.

Problem to create change pointer for custom message type - Idoc creation

Hi,
We want to create IDOC and send it out when the data of "planning calendar" changes. So we are trying to generate change pointers whenever entries in Table T439I (Planniing calendar) data change.
We created a message type, activated change pointers generally and maintained change relevant fields for message type (not sure if this step is done correctly). But not getting any change pointer in table BDCP2 when I create a new planning calendar in MD25.
Can anybody help / guide?

Thanks once again,
I had linked idoc type and message type in we82. Now after i activate the change pointers. I try to generate the IDOC type using BD21. It gives me the error message :<b> "Message type ZP2PPROJ_MSG cannot be sent with change pointers"</b>
whereas in my segments i am using all the master data only (i.e. PRPS, PROJ,PRHI). Please throw some light on this.
Also please clarify, do i need to make an entry of this custome message type in the partner profile ?
Rgds
kewal.

Change Pointer Program for IDOC creation..??

To All
Where does the message type is assigned, which allow that type of IDOC getting created in WPMU...??
Can COND_A be created in Change pointer Program...??
If possible ..How...??
Thanks
Sumeet

3)
RBDMOIND to confirm whether idocs have been successfully
dispatched to the receiver..and v can also use this program to change the status of idoc from 3 to 12....
RSNATED is the program used for triggering IDOC for the output type..where the output medium is 6.
And the subroutine that triggers the IDOC in the program is EDI_PROCESSING.
RSNASTED itself determines the associated IDoc outbound function module, executes it to fill the EDIDx tables and passes the prepared IDoc to the port.
You can call the standard processing routines from any ABAP, by executing the following call to the routine. You only have to make sure that the structure NAST is declared with the tables statement in the calling routine and that you fill the at least the key part and the routing information before.
TABLES NAST.
NAST-MANDT = SY-MANDT.
NAST-KSCHL = 'ZEDIK'.
NAST-KAPPL = 'V1'.
NAST-OBJKY = '0012345678'.
NAST-PARNR = 'D012345678'.
PERFORM einzelnachricht_screen(RSNAST00).
Calling einzelnachricht_screen determines how the message is processed. If you want to force the IDoc-processing you can call it directly:
TNAPR-PROGN = ''.
TNAPR-ROUTN = 'ENTRY'.
PERFORM edi_processing(RSNASTED).
~~Guduri

IDoc DEBMAS07 - Change Pointer

Similar Messages

Maybe you are looking for