MAU Rule Issue

[Former Member]

Dear Friends,

This is regarding the MAU Rule Evaluation and our observations.

Kindly correct us in case of any issues in our understanding/observations

1. SAP Transported the Customized SWCV for MAU Application on our Sandbox MI 7.1 SP08 System.

2. Customized SAP MAU SWCV behaved successfully in our sandbox system by populating the appropriate device queues.

3. We followed the same procedure on our new development system ( i.e, implementation of Mobile Specific SAP Notes in new system, transport of SWCV , initial data load for middleware driven objects, et al ) .

However, we observe that the Pending Extracts for the following Data Objects are not working :

MAM_CE__090, MAM_CE__095, MAM_CE__016, MAM_CE__017.

Does regenerating the DM for the above Data Object help us eliminate the issue? ( although the DM for the above DO is Consistent).

Thanks in Advance,

Suresh BJ

[sivasatyaprasad_yerra · Accepted solution]

Regeneration of DM doesn't resolve the problem. Are you facing the problem for all devices or set of devices?

[Former Member · Accepted solution]

Hi Siva,

Thanks for the quick reply.

I get this issue with all the Devices.

We are in immediate need of resolution. Can you help us with few pointers?

Thanks in Advance, Suresh BJ

[Former Member · Accepted solution]

What is not working with the Pending Extract?

Is it not going to the outbound queue?

or

Is the Pending Extracts for those DOs not populating like it is suppose to?

[Former Member · Accepted solution]

Hey Alan,

The Pending Extract is not populating the Outbound Queue even though the Subscriptions are successful ( AT, DRDS tables are having valid instances + status ).

these things are tried ...

a. de activate the rule + activate the rule

b. disable the device + enable the device

c. add the USER to the device in order to satisfy the subscription

Suresh~

[Former Member · Accepted solution]

Even when you click on Trigger Extract, it does not populate the Outbound queue?

Does the data objects in Pending Extract say "Running" or "Ready"?

From my experience with Pending Extract, it only populates the Outbound queue when you synchronize the device and when you configure the Refresh Queue to either Synchronously or Asynchronously.

If it is configured as Don't Refresh Queue, then you need to do the Trigger Extract manually.

[Former Member · Accepted solution]

Hi Suresh,

In the pending extracts,

-does it show the number of instances that is pending?

-does it show that the DMSWCV is operational?

Best regards,

Vinodh

[Former Member · Accepted solution]

Hi Vinod,

In the pending extracts we see the number of instances as 2 and also the DMSWCV is operational.

(All other MAU data objects are extracted succesfully to the device Q. Only 4 DOs are not getting extracted out of the 20 odd DOs)

On trigger of extract - The entries for the 4 DOs never disapear from the peding extract view and the queue status is always shown as running. Actually there are no queues that are running - we checked in the transaction SMQ1 and SMQ2

Regards

Somashekar Avadhani n Suresh BJ

[Former Member · Accepted solution]

Hi Som,

Okay, this is a known issue but was fixed with a note. But to proceed do the following,

1. goto tcode se16 and open table smmw_devmbomaper

2.Filter for all the entries with extract_status 'P'.

3. Now delete all these entries and trigger extract. It should go fine.

Also, check if you have implemented all the notes for DOE to avoid this issue in future.

Best regards,

Vinodh

Edited by: Vinodh Nagarajan on Dec 11, 2009 10:30 AM

[Former Member · Accepted solution]

Hey Vinodh,

Thank you for the quick response

We are checking with Basis for the deletion of the dev_mbomaper entries ( 12 overall) . [[ we shall update and close the thread accordingly ]]

Also, we are on SP09 with all Notes ( as indicated in the release note+documentation ) implemented successfully.

We shall try this on SP09 and update accordingly!.

Suresh BJ

[Former Member · Accepted solution]

Hi Suresh/Som,

Forgot to mention, while filtering for the extract_status, filter it along with your device id as well and delete only the entries for the affected devices only.

Best regards,

Vinodh.

[Former Member · Accepted solution]

Hi Vinodh,

We deleted the entries with Status 'P' and found the issue to be resolved.

However, last night SAPCD did a regeneration of the 90+16 DM and luckily the issue is solved for the new device too.

Since things are working fine, marking the Question as Solved.

See you until the next bug!

Suresh BJ