SAP MAM 3.0 Configuration

[Former Member]

Hi All,

I have been trying to configure SAP MAM 3.0 since last week. There is lot of documentation and different SAP Notes which are making me of lots of confusion. I have downloaded all the required guides of SAP MAP Configuration guide,master guide and installation guide. Is there any other simple way to go through and config SAP MAM 3.0. Our Mobile middleware is Mobile 7.0 and SP13. I have checked all the previous forum discussions about this subject. Please share your experience who successfully implemented SAP MAM 3.0.

Thanks in advance.

Regards,

Ameer Baba.

[Former Member]

Hi Ameer,

well, getting MAM 3.0 working as such is not that difficult at all - to be honest. The problem comes later with the fine tuning. But we want to make it simple and easy - so you get the data down to the device and it gives you a starting point for all the docu.

Ok, we say you have installed properly the MI 7.0 system, you can sync a mobile client, get a Mobile ID and a device ID and all works fine that far.

Good, then lets start!

The good thing is: on the backend, all necessary items are already there! The thing we need: configure an RFC connection from the backend to the middleware and one from the middleware to the backend. Look into the doku, cause the naming of these is unfortunately not free of choice. In my version it was necessary to name it MAM_MI.

Ok, RFC established, next step is to upload the SyncBO definitions. Open the MEREP_MIG screen on the middleware and upload the SYNCBO definition from the CD that fits the backend plugin you have. This is usually either PI2004 or PI2005 in case of MAM3.0. In there you see if the naming of the RFC is correct - cause it shows you which RFC name it needs. If yours is not correct - simply create the one you need. Do not try to rename the requested RFC here in MEREP_PD - it is much easier to simply create a new RFC!

Ok, now lets hop to the backend. We need to configure the MAM in SPRO. We open SPRO, drill down to the MAM settings and setup the stuff there we need. Basically we start with just as less limitations as possible by just adding the user, init the screens for order and notification selection and so on. Straight forwasd engineering and from the screens you should easily see what informartion you need to enter. If you have problems with that, ask your PM or SD people, they can help you with that - for sure!

Compile and enable all these SyncBOs, you can even run the replicator for T01 BOs already. Check in Table MEREP207 on the middleware if all data is there. If you do that before the SPRO steps are done, you will get the message, that there is no mobile scenario for certain users - that is the reason why we do SPRO first.

Then it gets a little more problematic: we need to implement and switch on Server driven replication pon the backend. Cause this is a little bit of a hassle (implement notes, switch on several settings, bla bla .... follow this guide:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/818ac119-0b01-0010-ba8b-b6e3f349...

Voila, now even the server driven stuff runs.

Upload the XMAM30.war file to the NWA, assign it to the device and deploy it ..... After a successfull deployment you should see the request of data in MEREP_MON for all MAM syncbos. Voila - now the basic stuff works fine.

Whatever scenario you have chosen, you could get orders down if all is right. Lets say you said orders are assigned by person responsible. Assign the order to you in the backend and sync, then this order should come down to the device withj all other required thuings.

If an order is not comming down - well, then go to the backend and run MAM30_001_GETLIST for your user - see if it is listed there. If not, check SPRO again.

It is as easy as that to get a running MAM version at the first place. Takes you about 1 hour plus the server driven stuff - rest is then on top and fine tuning!

Hope this helps to walk you through. If not - on my card you see my credentials. Feel free to contact me on either Skype or MSN - then I will guide you through.

Have fun!

Oliver

[Former Member]

Hi Oliver,

Thank you very much for your detailed explanation. I will go through the steps as you mentioned. Will get back in case of any help.

I appreciate your help.

Once again my sincere thanks to you!

Regards,

Ameer.

[Former Member]

Hi Oliver,

I was following the steps that you have mentioned in earlier reply. You mentioned about the PI2004 or

PI2005 Plugin. My middleware and bakend are separate servers. My backend server version is SAP ECC 6.0. I believe for the mentioned version plugin step is not required. Am I correct? If not where can I find the PI2004 or PI2005 and in which CD you are mentioning?. Please let me know.

Regards,

Ameer Baba.

[Former Member]

Hi Ameer,

yes,you are right. Check the Master Guide of MAM for the specification. There you will find the required patch level for the Backend in your scenarion. I think it is somewhere at page 12 or 16...... not 100% sure!

Hope that helps!

Regards,

Oliver

[Former Member]

Hi Oliver,

Thanks for your quick response.

Regards,

Ameer

[Former Member]

Oliver,

I have been following the steps which you mentioned in your reply. I have done like this.

1. Uploaded SyncBo Definitions

2. Generated multiple SyncBo's

3. Enabled SyncoBo's.

Then when I am trying to run the Replicator Report I am getting the error of "SyncBo MAM30_001 does not exist". What does it mean. I have checked with all the SyncBo's and getting same error.

Please let me know where I have to look to rectify this error.

Thanks and Regards,

Ameer

[Former Member]

Hi,

well, this error message is a little bit confusing - I know

You can not run a replicator for SyncBO MAM30_001 - cause it is of typoe S01. Replicator run is only necessary for SyncBOs of type T01. Go to MEREP_PD, there you can see the type of the BO.

S01: no replicator run at all!

T01: start replicator on Middleware

T51: Go to the backend, SE38 and run "*FULL_DOWNLOAD_SD". You will find a few programms. These will run the replication for FunctLoc, Partner, Equipments and MEasp.

Well, most likely if you are novice you will face issues in these modules (T51). Here is a guide that should help you solving these:

Link: [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/818ac119-0b01-0010-ba8b-b6e3f3490a63]

Hope that helps!

Regards,

Oliver

[Former Member]

Hi Oliver,

You rocks in this forum. Now I can see the data in the middleware.Now I am deploying MAM application on NWA and to see the data on my Laptop.

Thank you verymuch.

Regards,

Ameer.

[Former Member]

Hello Oliver,

Your posting is extemely helpful! I followed your steps, and I finally got data on the middleware. Thank you.

I have question about the replication of data from backend to middleware. I have variants specified in spro in backend to only bring over equipment of a particular category, but when I replicate, and I check the merep_207 table, I am getting eqipment records of other categories. Is this normal? I don't get them when I sync my device, but it is taking over 48 hours to do the inital replication from our testing backend system to the testing middleware. I thought it was only supposed to bring over the values specified in the perform general settings area of spro in the backend?

Thanks in advance,

Jim

[Former Member]

Hi again,

I just checked and it is not the merep_207 table yet, it is on the merep_delta table, and I think it has been on that table for a long time.

Thanks,

Jim

[Former Member]

Hi,

Can you guys let me know how did you deploy XMAM30.WAR file in NWA.

Thanks in advance

[chintan_virani]

Vikram,

Check my reply [here|; on how to deploy the applciations through NWA.

Chintan