Node Level filter rule does not filter child node instances

June 30, 2009 at 10:30 am

[] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] []

  1. Replication and realignment queue runs indefinitelySymptom 1. Replication and Realignment queues in DOE runs indefinitely.2. Backend load or backend push takes more time to complete.3. Device profile when assigned to multiple devices at once, takes a long...
  2. Attachment upload issue for upload only data objectsSymptom 1. For upload only data object, attachment data sent from device is not uploaded to backend.2. Short dump occurs while pushing keys to DOE from backend.Other terms SAP NetWeaver Mobile 7.10,...
  3. Exception condition “RECORD_POS_NOTFOUND” raised.Symptom 1. Inbound queue process fails with the error : Exception condition “RECORD_POS_NOTFOUND” raised.2. Dump on restarting of failed messages.3. Message restart takes longer time than usual and sometimes ends with the...
  4. API for Gross update MessageSymptom Only updated fields information is distributed to the device in case of update message from middleware. Other terms SAP NetWeaver Mobile 7.10, Data Orchestration Engine (DOE), Gross message, DOE Connector, Mobile...
  5. NLF rules not applied during confirmation flowSymptom Deletes for non-existing instances are being sent to the device during the confirmation flow of the message. Other terms SAP NetWeaver Mobile 7.10, Data Orchestration Engine, DOE, SPS04, SPS05,SPS06, SPS07, SP08,...
  6. Missing backend updates when backend conflict is enabledSymptom Missing backend updates in client incase when backend conflict enabled Other terms SAP NetWeaver Mobile 7.11, Data Orchestration Engine (DOE), conflict for backend, rejection service, SPS02. Reason and Prerequisites Reasons: Bug...
  7. Custom group values were not considered during registrationSymptom 1. Custom group attribute values are not considered at the time of device registration.2. Assigning / Unassigning of the device users does not distribute USERDETAILS or USER_AUTHORIZATION data objects3. Devices are...
  8. Lock issues during initial load and PSPSymptom 1.Process state propagation is causing a deadlock scenario for backend load for multiple data objects. 2.If a lot of keys are pushed from the backend to the middleware, the processing of...

Symptom
1. In case of Node level filter rules, child records are not filtered based on the device subscriptions.2. Duplicate messages are sent to the device in case of custom channel assigned to the device.3. Rejection message is not distributed to the device, if device updates the instance which does not exist in Middleware (CDS).4. Backend Read operation of DOE Connector does not return backend errors to the device.Other terms

SAP NetWeaver Mobile 7.10, Data Orchestration Engine (DOE), SPS04, SPS05, SPS06, SPS07, SPS08, Custom channel, DOE Connector, Duplicate messages, Rejection Message, Backend read.
Reason and Prerequisites

Reason:
1. Devices are not considered at the time of extracting message.2. Outbound service of the custom channel is invoked twice if the data object is marked for Reassignment enabled.3. Missing validation in key map before validation service.4. Error messages are cleared before sending to device.

Prerequisites:
- The system is currently on SPS04 to SPS08 for WebAS 7.10.
Solution

For WebAS 7.10:
- Apply Support Package 09
OR
- Apply this note via Note Assistant(SNOTE) if you are on SPS04 to
SPS08.
Perform automatic delta generation (for procedure, refer to SAP NOTE
1127899).

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment