SAP BLOG QM Open Notice – #7 – QM Migration Objects and Function Modules

SAP Blog

Kayıtlı Üye
Katılım
22 Ara 2017
Mesajlar
1,475
Tepki puanı
7
Puanları
6

QM Open Notice​


QM Open Notice is a blog post series about topics, which can be useful when working with Quality Management.


Overview​


Current blog post is about the existing migration objects in QM area and their reference to the used function modules to migrate the data.

In detail​


For all ‘Available Migration Objects’, check SAP Help at:



Release and component information for QM objects:

Migration ObjectTechnical Migration Object NameFirst Delivered with Cloud Release…
[SAP Help link]

First Delivered with On-Premise Release…

QM – Inspection methodSIF_INSP_METHOD17021709
Material Inspection Type (QMAT)
Material inspection setup (new name in 1811)
SIF_INSP_TYPE17051709
QM – Master inspection characteristicSIF_MSTR_CHAR17021709
QM – Inspection plan (deprecated)SIF_INSP_PLAN1702 / will be removed in 20081709
QM – Inspection planSIF_INSP_PLAN_220022020
QM/PM – Catalog code group/codeSIF_QM_CATALOG1709
QM – Selected setSIF_SELECTED_SET17021709
QM – Selected set codeSIF_SELSET_CODE17021709
QM – Certificate profile incl. assignmentSIF_CERT_PROFILE1911n/a
QM – Quality info recordSIF_QM_QINF1911n/a

Relevant function modules:

Migration ObjectUsed Function Module (BAPI / API)Application Component
QM – Inspection methodBAPI_QMTB_SAVEREPLICAQM-PT-BD-ICH
Material Inspection Type (QMAT)
Material inspection setup (new name in 1811)
BAPI_MATINSPCTRL_SAVEREPLICAQM-PT
QM – Master inspection characteristicBAPI_QPMK_SAVEREPLICAQM-PT-BD-ICH
QM – Inspection plan (deprecated)BAPI_INSPECTIONPLAN_CREATEQM-PT-IP
QM – Inspection planBAPI_INSPECTIONPLAN_CREATEQM-PT-IP
QM/PM – Catalog code group/codeBAPI_QPGR_SAVEREPLICAQM-PT-BD-CAT
QM – Selected setQPAM_SELECTED_SET_CREATEQM-PT-BD-CAT
QM – Selected set codeQPAM_SELSET_CODE_CREATEQM-PT-BD-CAT
QM – Certificate profile incl. assignmentQM_CERT_PROFILE_MIGQM-CA-MD
QM – Quality info recordA_QualityInProcurement
[Behaviour Definition (RAP/BO)]
QM-PT-RP-PRC

Known problem & solution​


The SAP S/4HANA Data Migration content (migration templates and predefined mapping rules) is based on the pre-configured SAP S/4HANA Cloud business processes.

Therefore, it might comes to bottlenecks when using the transaction LTMC / LTMOM in On-Premise systems, as the Cloud product is a newly developed solution and not a copy of the On-Premise functions.

For more details read following KBAs:

  • 2515151 – SAP S/4HANA Migration Cockpit: Migration objects or fields which you want to migrate cannot be found
  • 2683477 – Why are fields on screens not available in the migration content? (SAP S/4HANA Migration Cockpit)

In specific circumstances there is the possibility to extend the pre-delivered migration templates with LTMOM, see KBA:
2576565SAP S/4HANA Data Migration – On Premise

However, the modified object falls outside of the scope of SAP Support. See also SAP Note:
2481235SAP S/4HANA Migration Cockpit (on premise) – restrictions and extensibility of pre-delivered migration objects

Last, but not least, to influence SAP Software Development, check the possibilities in SAP Note:
11 – Would you like to shape & influence future releases of SAP Products?



Feel free to share your experience/feedback in the Comment Section. Thank you.

Okumaya devam et...
 
Üst