cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Regarding modification of child items in MAM25_001 SYNC BO

Former Member

on ‎11-18-2006 2:32 AM

0 Kudos

Hi,

I have added data (fields) to CE_ORDER_HEADER & CE_ORDER_COMPONENT tables in the order which is already downloaded from backend through updateMam001Item020 & insertMam001Item010 functions.

When I see the logs in MEREP_MON after synchronization, the log is at the end of this query

I dont see the MAM25_001_CHANGE BAPI being invoked. Only GETDETAIL BAPI is invoked.

There is a warning "TOP record read from R/3 itab; conflict detected (sync key=0000000309)".

We are not modifying the header/TOP of the sync BO.

Please let me know of any solution.

Thanks

Raj

1 3 I 17.11.2006 16:22:54 Z_MEREP_GEN_S01_____MAM25_001 has started for run number 0000015830 and runtime counter

2 4 I 17.11.2006 16:22:54 MAM25_001_GETDETAIL has started for run number 0000015830 and runtime counter 4

3 4 I 17.11.2006 16:22:54 MAM25_001_GETDETAIL has finished for run number 0000015830 and runtime counter 4

4 3 I 17.11.2006 16:22:54 Line items: R/3 key=000062006097, synchronization key=0000000309, action=M, item number

5 3 I 17.11.2006 16:22:54 Line items: add=0, changed=0, deleted=0, not changed=0

6 3 I 17.11.2006 16:22:54 Objects found in R/3=1, passed filter=0, loaded filter=1

7 3 I 17.11.2006 16:22:54 Objects: Add=0, changed=1, deleted=0, not changed=0

8 3 W 17.11.2006 16:22:54 TOP record read from R/3 itab; conflict detected (sync key=0000000309)

9 3 I 17.11.2006 16:22:54 Mobile ID=0000000171: Total records=14, total worklists=1, conflicts detected=1

10 3 I 17.11.2006 16:22:54 Mobile ID=0000000171: Added=8, changed=6, deleted=0

11 3 S 17.11.2006 16:22:54 Downloader completed successfully (mobile ID: 0000000171, SyncBO: MAM25_001)

12 3 I 17.11.2006 16:22:54 Z_MEREP_GEN_S01_____MAM25_001 has finished for run number 0000015830 and runtime counte

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
‎12-06-2006 2:09 AM
0 Kudos

Hi Kishore,

Thanks for your information. I was working on your suggestions and also was in quest of different ways to sort out the problem.

I want to debug the Z_MEREP_GEN_S01_____MAM25_001 function.

I am not able to create the input data that the function requires namely

DEVICE_CONTROL,HANDLER_CONTROL, HANDLER_WORKLIST etc.

Can I get the above parameters from any table in Mi server.

Thanks

Raj

Show replies
Show replies
Former Member
‎11-20-2006 11:42 PM
0 Kudos

Kishore,

I appreciate your reply.

Please find below the MEREP_MON log with the level at 5.

I have also attached the data displayed by the MEREP_MON transaction for that synchronization. The action as you have mentioned has 'A' or 'M'.

So I am not sure why CHANGE BAPI is not invoked.. Let me know in case you have some suggestions.

I have done a BAPI Interface check for the MAM25_001 sync BO. It displayed a message "no error". Is there a better way to test the BAPIs from BO. Can you let me know the order in which the BAPIs are invoked when an order is changed ?

Thanks

Raj

-

MEREP_MON log

071 16104

44 14 I 20.11.2006 10:54:48 MEREP_PROCESS_HANDLER_WL has started for run number 0000016104 and runtime counter 14

45 15 I 20.11.2006 10:54:48 Z_MEREP_GEN_S01_____MAM25_001 has started for run number 0000016104 and runtime counter

46 16 I 20.11.2006 10:54:48 MAM25_001_GETDETAIL has started for run number 0000016104 and runtime counter 16

47 16 I 20.11.2006 10:54:48 MAM25_001_GETDETAIL has finished for run number 0000016104 and runtime counter 16

48 15 I 20.11.2006 10:54:48 Line items: R/3 key=000062006097, synchronization key=0000000309, action=M, item number

49 15 I 20.11.2006 10:54:48 Line items: add=0, changed=0, deleted=0, not changed=0

50 15 I 20.11.2006 10:54:48 Objects found in R/3=1, passed filter=0, loaded filter=1

51 15 I 20.11.2006 10:54:48 Objects: Add=0, changed=1, deleted=0, not changed=0

52 15 W 20.11.2006 10:54:48 TOP record read from R/3 itab; conflict detected (sync key=0000000309)

53 15 I 20.11.2006 10:54:48 Mobile ID=0000000171: Total records=14, total worklists=1, conflicts detected=1

54 15 I 20.11.2006 10:54:48 Mobile ID=0000000171: Added=8, changed=6, deleted=0

55 15 S 20.11.2006 10:54:48 Downloader completed successfully (mobile ID: 0000000171, SyncBO: MAM25_001)

56 15 I 20.11.2006 10:54:48 Z_MEREP_GEN_S01_____MAM25_001 has finished for run number 0000016104 and runtime counte

57 14 I 20.11.2006 10:54:49 MEREP_PROCESS_HANDLER_WL has finished for run number 0000016104 and runtime counter 14

071 16106

3 2 I 20.11.2006 10:54:43 MEREP_ARECEIVER has started for run number 0000016106 and runtime counter 2

4 2 I 20.11.2006 10:54:43 MEREP_ARECEIVER has finished for run number 0000016106 and runtime counter 2

071 16109

1 1 I 20.11.2006 10:54:44 MEREP_PROCESS_SENDER_WL has started for run number 0000016109 and runtime counter 1

2 1 I 20.11.2006 10:54:44 Start processing conversation worklist O 0000000171

3 1 I 20.11.2006 10:54:44 2 worklists found to be processed for mobile ID 0000000171

8 1 I 20.11.2006 10:54:44 End processing conversation worklist O 0000000171

9 1 I 20.11.2006 10:54:44 MEREP_PROCESS_SENDER_WL has finished for run number 0000016109 and runtime counter 1

-

MEREP_MON DATA

I 0000000171 227 1 TOP

STRUCT_ID C 3 3 TOP

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0000000309

STR_CNTR N 10 10 0000000000

ACTION C 1 1 M

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32 45452BDDF61D021D00000000A888A7AB

POSTSTATE_ID C 32 32 4559905AB0F5069B000000EB683160F0

ID C 32 32 4559905AB0F5069B000000EB683160F0

REQUEST_ID C 32 32

ORDERID C 12 12 000062006097

ORDER_TYPE C 4 4 MNT1

PLANPLANT C 4 4 0200

BUS_AREA C 4 4

MN_WK_CTR C 8 8 T000000D

PLANT C 4 4 0200

MN_WKCTR_ID N 8 8 10003146

PMACTTYPE C 3 3 REP

PLANGROUP C 3 3 PDA

SYSTCOND C 1 1

FUNCT_LOC N 10 10 1602710

FUNCLOC_CREATE C 40 40

EQUIPMENT N 10 10 0

EQUIPMENT_CREATE C 18 18

SERIALNO C 18 18

MATERIAL C 18 18

MATL_DESC C 40 40

ASSEMBLY C 18 18

ASSEMBLY_DESC C 40 40

DEVICEDATA C 40 40

MAINTPLANT C 4 4 0200

COMP_CODE C 4 4 0001

SALESORG C 4 4

DISTR_CHAN C 2 2

DIVISION C 2 2

START_DATE D 8 8 20061116

FINISH_DATE D 8 8 20061116

BASICSTART T 6 6 000000

BASIC_FIN T 6 6 000000

PRIORITY C 1 1 1

PRODUCTION_START_DATE D 8 8 20061116

PRODUCTION_FINISH_DATE D 8 8 20061116

PRODUCTION_START_TIME T 6 6 231627

PRODUCTION_FINISH_TIME T 6 6 231627

ACTUAL_START_DATE D 8 8

ACTUAL_FINISH_DATE D 8 8

ACTUAL_START_TIME T 6 6 000000

ACTUAL_FINISH_TIME T 6 6 000000

REFDATE D 8 8 20061116

SALES_ORD C 10 10

S_ORD_ITEM N 6 6 0

CALC_MOTIVE C 2 2

INVEST_PROFILE C 6 6

SCALE C 2 2

ESTIMATED_COSTS P 12 6 2 0.00

CURRENCY C 5 5 USD

CURRENCY_ISO C 3 3 USD

SCENARIO C 4 4 O100

SYS_STATUS C 40 40

USER_ST C 1 1

USERSTATUS C 40 40

STAT_PROF C 8 8 PMORDER

OBJECT_NO C 22 22 OR000062006097

ROUTING_NO N 10 10 0

RESERV_NO N 10 10 0

SHORT_TEXT C 40 40 Repair/TN267A /PROD/41CRX /C/63125 -1

LONG_TEXT C 1 1

NOTIF_NO N 10 10 0

NOTIF_NO_2 C 12 12

NAME1 C 40 40

POST_CODE1 C 10 10

CITY1 C 40 40

STREET C 60 60

ENHANCEMENT_FLAG C 1 1

I 0000000171 227 2 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0000000375

STR_CNTR N 10 10 0000000001

ACTION C 1 1 A

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 MATNR

FIELD_TEXT C 20 20 Material

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 18

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 000000000073002178

I 0000000171 227 3 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0000000376

STR_CNTR N 10 10 0000000002

ACTION C 1 1 A

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 MAKTX

FIELD_TEXT C 20 20 Description

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 40

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 H2S probe o-ring

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 REQD_QTY

FIELD_TEXT C 20 20 Quantity

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 13

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 1.000

I 0000000171 227 6 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0000000379

STR_CNTR N 10 10 0000000005

ACTION C 1 1 A

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 AVAILABLE_QTY

FIELD_TEXT C 20 20 Quantity

DATATYPE C 4 4 CHAR DATALENGTH N 6 6 13

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 990032.000

5 I 0000000171 227 7 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0000000380

STR_CNTR N 10 10 0000000006

ACTION C 1 1 A

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 UOM

FIELD_TEXT C 20 20 Base Unit

DATATYPE C 4 4 UNIT

DATALENGTH N 6 6 3

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 EA

5 I 0000000171 227 8 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

DATALENGTH N 6 6 13

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 990032.000

5 I 0000000171 227 7 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0000000380

STR_CNTR N 10 10 0000000006

ACTION C 1 1 A

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 UOM

FIELD_TEXT C 20 20 Base Unit

DATATYPE C 4 4 UNIT

DATALENGTH N 6 6 3

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 EA

5 I 0000000171 227 8 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

DATALENGTH N 6 6 13

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 990032.000

5 I 0000000171 227 7 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0000000380

STR_CNTR N 10 10 0000000006

ACTION C 1 1 A

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 UOM

FIELD_TEXT C 20 20 Base Unit

DATATYPE C 4 4 UNIT

DATALENGTH N 6 6 3

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 EA

5 I 0000000171 227 8 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

SNDMSK C 64 64 000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0000000381

STR_CNTR N 10 10 0000000007

ACTION C 1 1 A

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 REPAIR

FIELD_TEXT C 20 20 Single-Character Fla

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 1

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255

I 0000000171 227 9 010

STRUCT_ID C 3 3 010

STRVERS N 4 4 0001

SNDMSK C 64 64 000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0000000382

STR_CNTR N 10 10 0000000008

ACTION C 1 1 A

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 RETN_CONF

FIELD_TEXT C 20 20 Single-Character Fla

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 1

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255

I 0000000171 227 10 020

STRUCT_ID C 3 3 020

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0001742031

STR_CNTR N 10 10 0000000001

ACTION C 1 1 M

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 P_TELNR

FIELD_TEXT C 20 20

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 10

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 123

I 0000000171 227 11 020

STRUCT_ID C 3 3 020

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0001742032

STR_CNTR N 10 10 0000000002

ACTION C 1 1 M

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 P_UNAME

FIELD_TEXT C 20 20

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 12

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 Rajaskekhar

I 0000000171 227 12 020

STRUCT_ID C 3 3 020

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0001742033

ACTION C 1 1 M

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 P_DELPNT

FIELD_TEXT C 20 20

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 25

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255

I 0000000171 227 13 020

STRUCT_ID C 3 3 020

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0001742034

STR_CNTR N 10 10 0000000004

ACTION C 1 1 M

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 DELIVERF

FIELD_TEXT C 20 20 Single-Character Fla

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 1

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 P

I 0000000171 227 14 020

STRUCT_ID C 3 3 020

STRVERS N 4 4 0001

SNDMSK C 64 64 0000000000000000000000000000000000000000000000000000000000000000

SYNC_KEY N 10 10 0001742035

STR_CNTR N 10 10 0000000005

ACTION C 1 1 M

TIMESTAMP N 21 21 000000000000000000000

PRESTATE_ID C 32 32

POSTSTATE_ID C 32 32

ID C 32 32

REQUEST_ID C 32 32

OBJECT_ID C 40 40 0001

KEY_LENGTH N 2 2 22

FIELD_NAME C 30 30 OPERATION

FIELD_TEXT C 20 20 Not More Closely Def

DATATYPE C 4 4 CHAR

DATALENGTH N 6 6 4

DECIMALS N 6 6 0

GENERAL_FLAG C 1 1

FIELD_VALUE C 255 255 10

-

Show replies
Show replies
kishorg
Advisor
Advisor
‎11-21-2006 9:29 AM
0 Kudos

Hi Raja,

All the delta data we created on the Mobile Client for a particular SyncBO

would come to the MI Server as one Inbound Worklist.The 'MEREP_PROCESS_HANDLER_WL'

function module present in the MI framework will read the inbox data.

This inturn trigger the generated function modules for a particular syncbo.

Framework is using these generated function modules while synchronizing.Within

these generated function modules, we can see the call to our RFCs.(GETLIST , GETDETAIL,

CREATE, MODIFY,nd DELETE).

Since the syncbo type in your case is S01, you can see these generated function modules

for your syncbo 'MAM25_001',

Z_MEREP_GEN_F01_____MAM25_001

Z_MEREP_GEN_S01_____MAM25_001

Z_MEREP_GEN_S02_____MAM25_001.

Z_MEREP_GEN_S01_____MAM25_001 - This is to find out the delta data and to find out whether

a conflict has been happened or not(for modification to the same data on the client and on the server).

Z_MEREP_GEN_S02_____MAM25_001 - We can see the call to our actual RFCs used for SyncBO creation within this function module itself.

<u><b>In the Profile Dialog ,</b></u>

<b>In the Synchronizer tab , just check,

whether you have checked the BAdi Active tag or not.

This defines whether or not the BAdIs in the synchronizer of the corresponding SyncBO are active and whether they should be used at runtime.

If you set this flag to false(if not checked), no BAdIs are executed, even if you implemented them for the SyncBO.</b>

Check these things...

Regards,

Kishor Gopinathan

kishorg
Advisor
Advisor
‎11-18-2006 6:26 AM
0 Kudos

Hi Raja,

You can see the Structure that you used as the table parameter of the GETLIST BAPI Wrapper as the Export parameter of the GETDETAIL Bapi Wrapper. Framework would use this export parameter to find

out the conflict(if you are changing the same data in the mobile client and in the MI server, then

it is marked as a conflict. Changes to the same TOP record or changes to the same ITEM record or

changes to the different ITEM records of the same TOP record are will be treated as conflict.If you

are adding one more item to the same TOP record and in the backend changes to the another ITEM record

of the same TOP record. this can also..)

This problem could be because of these reasons,

1)You might have changed the TOP record by means of - adding new ITEM or changing one of

the ITEM record or even deleting the already existing ITEM record ..like .. and the modification

to the same TOP record already happened in the backend by means of the above mentioned reasons.

or in the worst case,,

2) There is a problem in the GETDETAIL BAPI wrapper. Framework will report as a conflict,

if we are not filling the EXPORT parameter of the GETDETAIL Bapi Wrapper exactly same as that

one we selected in the TABLE parameter of the GETLIST.(based on the collected table records in

the GETLIST Wrapper, we might have one or more keys. Based on these keys, we are selecting the

GETDETAIL data.If the particular row of data we selected for the GETLIST wrapper and the data we are EXPORTING in the GETDETAIL Wrapper for the same Header (TOP ) data are different , then the framework

will treat this as a conflict since the data already present in the replica DB and that one in the

back end are different because of improper selection in the GETDETAIL wrapper)...

check these things...

Regards,

Kishor Gopinathan

Show replies
Show replies
Former Member
‎11-18-2006 4:39 PM
0 Kudos

Kishore,

Thanks for the reply.

Yes, we are adding new ITEM or changing one of the ITEM record in the application.

I would like to explain the scenario that we are trying to implement again.

We have written a BADI in the MAM25_001_CHANGE BAPI to run a custom transaction using the data in CE_ORDER_HEADER & CE_ORDER_COMPONENT tables.

In our MAM application, we are trying to modify the order as follows

Mam001 order = custom.getSelectedOrder();

BOList OrderDeliveryOptions = OrderHelper.getOrderManager().getMam001Item020s(order);

Mam001Item020 orderDelivery = (Mam001Item020)OrderDeliveryOptions.get(counter);

orderDelivery.setObjectId(objectID);

orderDelivery.setKeyLength("22");

orderDelivery.setDecimals("000000");

orderDelivery.setGeneralFlag("");

orderDelivery.setFieldName("P_TELNR");

orderDelivery.setFieldText("");

orderDelivery.setDatatype("CHAR");

orderDelivery.setDatalength("000010");

orderDelivery.setFieldValue(contactNO);

OrderHelper.getOrderManager().updateMam001Item020(order,orderDeliveryOption);

What we are expecting is to invoke the MAM25_001_CHANGE BAPI & inturn invoke the BADI to use the data in the CE_ORDER_HEADER table to run a custom transaction.

But the MAM25_001_CHANGE is not getting invoked even after updating the item records. Instead MAM25_001_GETDETAIL is invoked.

In what scenario will the CHANGE BAPI be invoked?

I am not sure as to how to invoke the CHANGE BAPI after modifying the customer enhancement tables.

Thanks

Raj

kishorg
Advisor
Advisor
‎11-20-2006 6:13 AM
0 Kudos

Hi Raja,

After changing the details, are you able to view those changes?.

(i just want to confirm, whether that code written in the persistence level is working or not.).

Could you please paste that code template in the persistence level?.

When you change one entry on the MI client, the client framework would put those entries in the Outbox of

the MI client( Every entries would have one attribute named 'action'. For those modified entries,

the action could have values like 'M' for modify, 'A' for add , 'D' for delete. These are the possible

action values applicable to MI client. But for the MI server in addition to the above mentioned values,

'R' for replace also present.) and will be sent to the MI server while synchronizing. This values fill

up the Inbox of the MI server. From here, the MI server will call the concerned BAPIs with respect to

the values for the action attribute.(if the action is 'M' , then frame work would call the CHANGE wrapper ,

when 'A' - call CREATE wrapper like...).

If the code written in the persistence level is not working, then the client framework won't

find out the delta data and those values won't be sent to the MI server.If those changed values

are persisting on the MI client, it means there is nothing wrong with those code templates.

MI framework would call the GETLIST , GETDETAIL wrappers for delta determination(depending upon the

type of syncbo, only for S01 nd download) while synchronizing.

Which log level you have set there in the Runtime Component( in profile dialog. hope 5 - information)?.

If the invocation of CHANGE wrapper is not there in the trace, then it means thats not get invoked. In the worst case check that change wrapper and confirm whether its is working or not.

Regards,

Kishor Gopinathan

Ask a Question