cancel
Showing results for 
Search instead for 
Did you mean: 

SyncBo definitions

Former Member
0 Kudos

Hi,

I was wondering what is the process to create the SyncBo_def.txt files. Also what is the format that they follow.

Thanks,

Miguel

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

I tried to load the exported file but the system does not recognize any of the Syncbo.

Thanks for you input,

Miguel

former_member304703
Contributor
0 Kudos

Hi Miguel,

I think that you used "Simulate" instead of "Execute" button because what you copied as result from your system looks like "simulated" screen.

Cheers

Former Member
0 Kudos

Yes that solved the problem. By any change do you know what format it follows?

Thanks,

Miguel

former_member304703
Contributor
0 Kudos

Hi Miguel,

what format... Never though about it. I believe it is something SAP internal and MI specific. They generate a file that merep_mig will parse when you upload SyncBos.

I don't think you can use it ainywhere outside Netwever (Mobile Infrastructure).

Cheers,

Larissa

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

I tried the steps but the result is a file that is very different than the original file that is included in the mobile applications. For example the general layout of the downloaded file is:

14.06.2007 Dynamic List Display 1

-


Downloading Objects Overview (Test Run)

Number of SyncBO: 14

Import Option Client independent objects:Overwrite

Client dependent objects:Overwrite

Language Option All languages

-


SyncBO name

Client Dependent Objects

Table Name

Description

Record count

-


MAM25_001

MEREP_401

SyncBO ID

1

MAM25_001

MEREP_401T

SyncBO ID Short Description

1

MAM25_001

MEREP_405

Mapping Result for Synchronization (BAPI)

1665

MAM25_001

MEREP_410

Function Modules to be Called by SyncBO

4

MAM25_001

MEREP_411

Generated Function Modules

3

MAM25_001

MEREP_409

Synchronizer Control Record

1

MAM25_001

MEREP_414

Related SyncBO Control

2

MAM25_001

MEREP_406

Default Value: Value ID

1

MAM25_001

MEREP_406T

Default Value: Value ID Short Description

1

On the other hand the older text file is:

GDT_TABLE MEREP_401 SyncBO ID MAM25_001 00001

GDT_TABLE MEREP_401T SyncBO ID Short Description MAM25_001 00001

GDT_TABLE MEREP_405 Mapping Result for Synchronization (BAPI) MAM25_001 01665

GDT_TABLE MEREP_410 Function Modules to be Called by SyncBO MAM25_001 00004

GDT_TABLE MEREP_411 Generated Function Modules MAM25_001 00003

GDT_TABLE MEREP_408 Exit Source Codes MAM25_001 00000

GDT_TABLE MEREP_409 Synchronizer Control Record MAM25_001 00001

GDT_TABLE MEREP_414 Related SyncBO Control MAM25_001 00002

GDT_TABLE MEREP_406 Default Value: Value ID MAM25_001 00001

GDT_TABLE MEREP_406T Default Value: Value ID Short Description MAM25_001 00001

GDT_TABLE MEREP_407 Default Value: SyncBO X MAM25_001 00001

GDT_TABLE MEREP_104 Selection Criteria(Download): Mobile ID X MAM25_001 00000

GDT_TABLE MEREP_203 Selection Criteria(Download): SyncBO X MAM25_001 00000

.....

GDT_STOCK_MBL414 MAM25_041 MAM25_031 090MEASUREMENT_POINT XSAP 20041101211044 SAP 20041115093512

GDT_STOCK_MBL414 MAM25_041 MAM25_090 050MEASUREMENT_POINT XSAP 20041101210952 SAP 20041115093512

GDT_STOCK_MBL414 MAM25_050 MAM25_001 100PARTNER_KEY XSAP 20041101213647 SAP 20041115093512

GDT_STOCK_MBL414 MAM25_050 MAM25_010 100PARTNER_KEY XSAP 20041101213720 SAP 20041115093512

GDT_STOCK_MBL414 MAM25_050 MAM25_030 120PARTNER_KEY XSAP 20041101213528 SAP 20041115093512

GDT_STOCK_MBL414 MAM25_050 MAM25_031 120PARTNER_KEY XSAP 20041101213438 SAP 20041115093512

GDT_STOCK_MBL414 MAM25_050 MAM25_090 060PARTNER_KEY XSAP 20041101213745 SAP 20041115093512

GDT_STOCK_MBL414 MAM25_095 MAM25_090 TOPMYALM_SCENARIO XSAP 20041101204946 SAP 20041115093512

GDT_STOCK_MBL401T MAM25_001 EOrder / operation for MAM

GDT_STOCK_MBL401T MAM25_005 ETime confirmation for MAM

GDT_STOCK_MBL401T MAM25_006 EMaterial confirmation for MAM

GDT_STOCK_MBL401T MAM25_010 ENotification for MAM

GDT_STOCK_MBL401T MAM25_016 ECatalog Profiles

GDT_STOCK_MBL401T MAM25_017 ECatalog Code Groups

GDT_STOCK_MBL401T MAM25_030 EFunctional location for MAM

GDT_STOCK_MBL401T MAM25_031 EEquipment for MAM

GDT_STOCK_MBL401T MAM25_040 EMeasurement document for MAM

GDT_STOCK_MBL401T MAM25_041 EMeasurement point / history for MAM

GDT_STOCK_MBL401T MAM25_050 EPartner for MAM

GDT_STOCK_MBL401T MAM25_070 EMaterial / equipment inventory for MAM

GDT_STOCK_MBL401T MAM25_090 EUser specific customizing for MAM

GDT_STOCK_MBL401T MAM25_095 EScenario specific customizing for MAM

GDT_STOCK_MBL405 MAM25_001 A01IORDER_HEADER ORDERID TOPORDERID 0001 X ORDERID 1 AUFNR C000012000012000000 000000 Order Number MAM_25_ORDER_HEADER

GDT_STOCK_MBL405 MAM25_001 A01IORDER_HEADER ORDER_TYPE TOPORDER_TYPE 0002 X ORDER_TYPE 1 AUFART C000004000004000000 000012 Order Type MAM_25_ORDER_HEADER

GDT_STOCK_MBL405 MAM25_001 A01IORDER_HEADER PLANPLANT TOPPLANPLANT 0003 X PLANPLANT 1 IWERK C000004000004000000 000016 Maintenance Planning Plant MAM_25_ORDER_HEADER

GDT_STOCK_MBL405 MAM25_001 A01IORDER_HEADER BUS_AREA TOPBUS_AREA 0004 X BUS_AREA 1 GSBER C000004000004000000 000020 Business Area MAM_25_ORDER_HEADER

GDT_STOCK_MBL405 MAM25_001 A01IORDER_HEADER MN_WK_CTR TOPMN_WK_CTR 0005 X MN_WK_CTR 1 GEWRK C000008000008000000 000024 Main work center for maintenance tasks MAM_25_ORDER_HEADER

GDT_STOCK_MBL405 MAM25_001 A01IORDER_HEADER PLANT TOPPLANT 0006 X PLANT 1 WERGW C000004000004000000 000032 Plant associated with main work center MAM_25_ORDER_HEADER

GDT_STOCK_MBL405 MAM25_001 A01IORDER_HEADER MN_WKCTR_ID TOPMN_WKCTR_ID 0007 X MN_WKCTR_ID 1 LGWID N000008000008000000 000036 Object ID of the Work Center MAM_25_ORDER_HEADER

GDT_STOCK_MBL405 MAM25_001 A01IORDER_HEADER PMACTTYPE TOPPMACTTYPE 0008 X PMACTTYPE 1 ILA C000003000003000000 000044 Maintenance activity type MAM_25_ORDER_HEADER

GDT_STOCK_MBL405 MAM25_001 A01IORDER_HEADER PLANGROUP TOPPLANGROUP 0009 X PLANGROUP 1 INGRP C000003000003000000 000047 Planner Group for Customer Service and Plant Maintenance MAM_25_ORDER_HEADER

Thanks again,

Miguel

Former Member
0 Kudos

Hi Miguel,

Interesting!!!

Can you try to use the new file to import the syncBOs in another system or delete the syncBOs from the current system and import them using the new file? I feel the result won't be different.

Regards,

Rahul

Former Member
0 Kudos

Hi Miguel,

For creating a syncBO_def.txt file,

1. Go to transaction MEREP_MIG

2. Select the option 'Download to File'

3. Select the required syncBos (ideally beloging to an application)

4. Execute

5. The RFC destination field can be kept empty and Enter. Done

The format is SAP format.

Regards,

Rahul