Number field value of SyncBO is changed in middleware

July 7, 2009 at 1:26 am

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

  1. Mobile component(s) getting deleted from Admin UISymptom Wrong mobile component(s) is getting deleted while unassigning device configuration. Context for a problem: - Device Configuration DC1 with a Mobile Component app1 - Device Configuration DC2 with a Mobile Component...
  2. Performance improvement for ‘Add’ Action in SynchronizationSymptom Middleware is taking a long time to send records for Add action during synchronization for any smartsync application. Other terms Smart Sync, Delta, Synchronization, Middleware, Application, Performance, Time, Data, Iteration, SyncBO,...
  3. Inbound Worklist stuck in Waiting statusSymptom Inbound SyncBO’s continue to get ‘hung’ in ‘W’ on the MI server in merep_mon. The only way to get them moving again is by selecting the SyncBO stuck in ‘W’ status...

Symptom

If any record is created or changed from client, number field value of that SyncBO is getting changed by middleware before calling bapi wrapper.

Other terms

Display, User, Synchronization, Records, Deletion, Incorrect, Wrong, Bapi wrapper, Values, Admin UI, Database, Table, MI 7.0.

Reason and Prerequisites

You are currently using SP22 or above for WebAS 6.40
Or
You are currently using SPS16 or above for WebAS 7.0
Or
You are currently using SPS01 or above for WebAS 7.01.
Or
You are currently using SPS01 or above for WebAS 7.02.

Solution

Kindly regenarate all the SyncBOs from Tn: MEREP_SBUILDER after implementing this note.
For WebAS 2.5:
- Apply Support Package 25
or
- Apply this note via Note Assistant(SNOTE) if you are on SPS22 to SPS24
For WebAS 7.0:
- Apply Support Package 20
or
- Apply this note via Note Assistant(SNOTE) if you are on SPS16 to SPS19
For WebAS 7.01:
- Apply Support Package 05
or
- Apply this note via Note Assistant(SNOTE) if you are on SPS01 to SPS04
For WebAS 7.02:
- Apply Support Package 02
or
- Apply this note via Note Assistant(SNOTE) if you are on SPS01

————————————————————————
|Manual Post-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_BASIS SAP Basis compo…|
| Release 700 SAPKB70016 – SAPKB70019 |
————————————————————————
Caution: You have to perform this manual post-implementation step manually and separately in each systemafteryou have imported the Note to implement.
After implementing the note, kindly regenerate all the SyncBOs so that changes may get effected in auto generated function modules.

————————————————————————
|Manual Post-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_BASIS SAP Basis compo…|
| Release 701 Until SAPKB70104 |
————————————————————————
Caution: You have to perform this manual post-implementation step manually and separately in each systemafteryou have imported the Note to implement.
After implementing the note, kindly regenerate all the SyncBOs so that changes may get effected in auto generated function modules.

————————————————————————
|Manual Post-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_BASIS SAP Basis compo…|
| Release 702 Until SAPKB70201 |
————————————————————————
Caution: You have to perform this manual post-implementation step manually and separately in each systemafteryou have imported the Note to implement.
After implementing the note, kindly regenerate all the SyncBOs so that changes may get effected in auto generated function modules.

————————————————————————
|Manual Post-Implement. |
————————————————————————
|VALID FOR |
|Software Component SAP_ABA SAP Application…|
| Release 640 SAPKA64022 – SAPKA64024 |
————————————————————————
Caution: You have to perform this manual post-implementation step manually and separately in each systemafteryou have imported the Note to implement.
After implementing the note, kindly regenerate all the SyncBOs so that changes may get effected in auto generated function modules.

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

Leave a Comment