SAP Knowledge Base Article - Preview

3669897 - MOSB Contract Not Created Automatically During “DE_B_WIM_REGMOS_MOSN” New Installation When Supplier Is Not Assigned

Symptom

  • In the scenario of process DE_B_WIM_REGMOS_MOSN, the supplier is usually not known when the IFTSTA 21010 and 21012 messages are exchanged between MOS and DSO.
  • As a result, in step 0310-0020, the system check (CHK_MOSB_INTG_REL) returns "not relevant", so the required MOSB integration process is not triggered and no MOSB contract is created.
  • This also prevents sending required MDC (UTILMD 55640 and UTILMD 55643) messages to the DSO.


Read more...

Environment

SAP S/4HANA Utilities Master Data Updates Option for Germany

Keywords

missing MOSB contract, DE_B_WIM_REGMOS_MOSN, CHK_MOSB_INTG_REL, MOSB integration process, IFTSTA 21010, IFTSTA 21012, UTILMD 55640, UTILMD 55643, SAP S/4HANA Utilities, supplier not known, MOS billing contract creation, BAdI /US4G/BADI_WIM_PROCESS, step 0310-0020 , KBA , IS-U-LIB-DE-MDU , SAP S/4HANA Utilities Master Data Updates Option for Germany , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.