Skip to Content
0

Should table SFIOM_KMAP_OSI be updated manually with all the HRP1000 object ids

Mar 29, 2017 at 09:25 PM

585

avatar image
Former Member

Hi Experts,

We are working on Org data replication from EC to SAP and wanted to understand if table SFIOM_KMAP_OSI be loaded with all data in HRP1000.

When new positions comes in from EC , how would those get updated in SFIOM_KMAP_OSI table. I see that method GET_ERP_ID_FROM_EC_POSITION_ID class CL_SFIOM_EE_ORG_AS*_PERN_2_POS is being used to validate position id in ECC, and only if position exists in SFIOM_KMAP_OSI it will be successful else error gets generated "No key mapping exists for related Employee Central object Position 00004496"

Please help or let me know if any more information is required.

Thanks & regards,

Uttam

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Siddharth Rajora
Apr 14, 2017 at 01:34 PM
0

yes for existing Objects IDs table would be updated ie before migration from ERP to EC

the existing objects from SAP into SF EC and completed table, SFIOM_KMAP_OSI with the existing objects from SAP to match with SF EC.

Now them any new object ID which is created in EC would not be existing in below table and hence new one would be created

also are you using

RH_SFIOM_ORG_OBJ_REPL_QUERY in SAP system to Pull the object: (departments / positions / jobcodes?

With the EC Object ID of field SFIOM_RPRQ_OSI-OSI_ID, it searches in key mapping table SFIOM_KMAP_OSI the corresponding backend Object ID. In case no mapping is found, a new Object ID is always created, table SFIOM_SYNC_IDS is NOT taken into consideration here.

The new Generic object replication is initiated with report "RH_SFIOM_ORG_OBJ_REPL_QUERY". The information from EC will arrive laterto the backend and will be also stored in DB tables (staging area). The tables are SFIOM_GENRQ_HD, SFIOM_GENRQ_DP and SFIOM_GENRQ_DFLD. Transaction SFIOM_VIEW_ORG_REQS is also used here. The transaction can also read these tables and are shown in the list to replicate. When you process them, the new generic replication code runs.

The new generic replication code also searches in the key mapping table SFIOM_KMAP_OSI whether the object already exists. If no mapping in found, it checks table SFIOM_SYNC_IDS to see whether it should try to use the EC Object Id as backend Object Id.

Share
10 |10000 characters needed characters left characters exceeded