Auto Trigger DEBMAS IDoc for a customer change

[Former Member]

Hello Experts,

I have a business case where in I need to auto trigger the DEBMAS IDoc when ever customer details are changed. What is that I need to do in SAP to trigger the IDoc automatically.

Please help

Thanks in Advance,

Suma

[former_member188685]

You need to Activate the Change Pointers , then Idoc will be sent automatically..

Check for these three...

1. Activate Change Pointers

2. Partner Profiles inplace (RFC Destination , Logical System etc)

3. Distribution model

Then only Idoc will be sent.

[Former Member]

Hello Vijay,

I have not done this before can you please give me flow in detail?

Like the T-Code and what to do exactly.

We are in a critical position please help ASAP.

Thanks in Advance,

Suma

Edited by: Suma B on Jul 8, 2008 8:52 AM

[soumya_jose3]

Hi Suma,

1) Go to BD61 and then enable the checkbox 'Change pointers activated-generally'.

2) Enable change pointers for the message type.

For that go to BD50 and enable the checkbox active for the message type DEBMAS

3) Specify the fields for which change pointers are to be written.

ie, if any of these fields change, an idoc will be sent.

For that go to BD52 give ur message type DEBMAS and there specify the fields.

4) The program RBDMIDOC should be scheduled as a background job to send the idocs automatically when any of the above fields specified is changed.

Hope it is clear.

Regards,

Soumya.

[Former Member]

Hello Sowmya,

Thanks for your very valuable inputs.

I have done the first 3 steps and getting confused with the fourth.

How can I schedule the program as back ground?

Is that in SM36 by saving variant as background job? or directly using the program in SM36?

Thanks in Advance,

Suma

Edited by: Suma B on Jul 8, 2008 10:04 AM

[soumya_jose3]

Hi Suma,

First you save a variant for the RBDMIDOC program with message type as DEBMAS. Then in SM36 schedule background job using this variant.

Regards,

Soumya.

[Former Member]

Hello Sowmya,

After I maintain variants and using the same in background processing also, IDoc is not getting triggered for change of the customer number.

What I have done:

Step 1 : Maintained ALE for outbound for DEBMAS message type and DEBMAS05 Baisc type and was able to trigger the master IDoc from BD12.

Step 2 : BD61 is already enabled with checkbox 'Change pointers activated-generally'.

Step 3 : Enable change pointers in BD50.

Step 4: In BD52, I have not entered any new change document items for message type as I am changing the name of the customer and its already in there with Object type as DEBI, Table Name KNA1 and Field Name NAME1.

Step 5 : Maintained Variants RBDMIDOC program as ZChange, with check box selected for "Only for back ground processing". Is there any thing that I need to maintain here?

Step 6 : In SM36 I have scheduled back ground job with name ZCustomerChange, job class as C and given the variant as ZChange.

Still the Idoc is not getting triggered, did I miss any configs inbetween?

Please help...

Thanks in Advance,

Suma

Edited by: Suma B on Jul 8, 2008 11:01 AM

[former_member188685]

There is another way to check

You can run the transaction BD12

Fill Outputtype and logical system

and check

[Former Member]

Hello Vijay,

When I trigger IDoc from BD12 its working and I was able to the IDoc in WE05. But when I change the customer details in XD02 the IDoc is not getting triggered. So this is my concern.

Hope you have gt it...

Thanks,

Suma

Edited by: Suma B on Jul 8, 2008 11:18 AM

[Former Member]

Hello Suma,

Please follow this.....

Automatic generation of IDOC when we change the MASTER DATA:

Change Pointers:

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.

Configuration for Change Pointers:

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

DEBMAS Check the check box

3. BD52 Maintain Table Views

Enter the Message type "DEBMAS" and press enter.

For example

OBJECT TABLE NAME FIELD NAME

DEBI KNA1 NAME1

5. WE21 Port

6. WE20 Partner Profile

7. BD64 Distribution Model

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 Maintain variants then use the same back in scheduling.

STEPS IN BACKGROUND SCHEDULING:

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.

Hope this resolves your issue....

please reward if helpful...

Thanks,

Sree

[Former Member]

Anyway to trigger outbound Idoc on customer master change/create based on certain value, such as sales organization?

[alex_cook]

Using the above change pointer method, use T-Code BD52 to maintain the list of fields that trigger the change pointer creation. If you only want Sales Organisation for example, remove all entries except DEBI KNVV VKORG

[Former Member]

Hi Alex,

Understand can use T-Code BD52 to maintain the list of fields that trigger the change pointer creation. But if I only wish to trigger outbound customer master idoc for sales organization equal AUS, how can I configure it?

Thanks in advance.

[Former Member]

Addition to what Soumya Jose has mentioned.

You can also send the Customer data from one client to another using BD12.

for receiving at the other end you can use BD13. For this you need to create a distribution model thru BD64 and generate partner profiles through that also or go to WE20 and create them.

Regards

Kannaiah

[alex_cook]

Howdy,

Slightly off-topic but you implement BADI IDOC_CREATION_CHECK to filter the IDoc creation based on your criteria, eg Sales Org.

Cheers

Alex

[Former Member]

Hi Alex,

How / Where to implement BADI IDOC_CREATION_CHECK to filter the IDoc creation based on my criteria, eg Sales Org? Mind to provide information in detail?

Thanks lot.

[alex_cook]

Howdy,

Not much to say really, the BADI only has 1 method so just go into SE18 with the BADI name and create an implementation.

Parse the IDOC_DATA table to look for the Sales Org node.

Clear the CREATE_IDOC parameter if you don't want the Idoc to be generated.

Cheers

Alex