MSA- Sublet processing

Functional details

The goal of sublet process is to sell externally performed services with procurement integration, for example painting, towing services or engine overhaul.

Sublet item is part of the SAP DBM Service order and is usually invoiced to the customer. As a result of sublet item processing, MM purchase requisition is created which is a trigger for procurement process.

Process is available in MSA when parameter ENABLE_SUBLET_JOB is set to True. As a prerequisite, bot DBM and MSA specific configuration must be in place (details described in BFSG document).

Sublet Job Button - Navigation Sidebar

Once a button is pressed, depending on the customizing following information needs to be provided

Sublet data input

Sublet job creation in MSA requires online connection / integration with SAP DBM system. Once Save button is pressed, MSA triggers /DBME/MI0_S_WS01_PURCH_CREA webservice.

Only after successful processing of purchase document creation, a job is created in MSA overview screen.

Once a sublet job is created and visible on MSA overview screen, this means that corresponding job with purchasing document is already created in SAP backend system. Such job cannot be deleted nor rejected from MSA anymore.

By pressing details button on the sublet job line, user can get corresponding purchasing document number as presented on the figure below.

Sublet job created / PR Number

Technical information

Process requires online connection with the backend system. Following webservices are used:

/DBME/MI0_S_WS01_VENDOR_GET – online vendor search

/DBME/MI0_S_WS01_PURCH_CREA – purchasing document creation