03-16-2006 10:57 PM
Why is COSMAS message type NOT included in ALE distribution via change pointers ?
BD16 allows you to distribute cost centres for one time load. But for daily changes, I was hoping to activate mesg type COSMAS (for cost center) and distribute using
change pointers. But since it is not included, how will I distribute any changes to cost center?
Any other solutions ?
05-24-2007 5:14 PM
Bhaven,
I would like to ask you if you solved this problem? Because i'm facing the same problem... I can not find an automated distribution for creation and updates to send the CC's via ALE.
Thanks in advanced for your reply...
Jerry.
05-24-2007 6:24 PM
What version of SAP are you running?
We are on 4.7 and when we go into SALE, and activate change pointers for message types, COSMAS is available.
I then changed a cost center and it showed up in change pointer table BDCP.
Then I executed the program to generate IDOCs for Message type cosmas and the IDOC was generated.
Best Regards,
Chris H.
05-24-2007 10:24 PM
Chris,
I'm setting up the ALE's scenarios on 4.6C and 4.7, so, what you are saying is that there's in the TC SALE a place where to setup change pointers to automate trigger ALE messages while creation or updates to COSMAS...
Now i will ask you if this also applies for:
- SRVMAS (service master)
- GLMAST (GL account master)
- CREMAS (vendor master)
Thanks in advaced for your reply...
Jerry
05-25-2007 11:22 AM
Yes. Here is how you get there from SALE:
Modelling and Implementing Business Process->Master Data Distribution->Replication of Modified Data
<b>Activate Change Pointers Generally</b> -> You have to set this switch to turn the general change pointer functionality on
<b>Activate Change Pointers fro Message Types</b> ->COSMAS, SRVMAS, GLMAST, CREMAS can all be turned on here. Just put an X in the checkbox
<b>Creating IDOCs from Change Pointers</b> - under this node you can access the program that turns the change pointers into IDOCs.
Hope this information helps.
Chris H.
10-24-2008 2:46 PM
For cosmas the chaig pointer is the correct way.
You must check flag in BD50 transaction on cosmas message and check flag on bd61.
After that you must schedule a job for BD21 transaction with cosmas message type so the cosmas change or createtion are distribute.