...
Functional details
...
Customer details screen has been introduced to present and maintain more than one customer specific partner function in one screen. Using customer details screen multiple partner functions relevant for customer.
Functional details
Customer details screen has been designed to accommodate multiple partner functions.
For the screen to be used, CUSTDT screen type must be customized as part of visit scenarios and parameter CUST_DTL_SCREEN_FLOW must be set to “True”. When the above is fulfilled, customer and contact information are hidden from overview screen and are maintainable only via customer details screen.
Customer details screen
Customer details screen is divided into 2 main areas:
- Customer specific information listing relevant customer partner roles
- Details / maintenance area – content role-specific
Ship-To / Payer selection example
Screenshot above presents partner selection option for Payer. Similarly Ship-To can be selected and changed for the service order
Sold to party change
Customer details screen contains also Sold-To-Party change function. Button triggers search engine and followed by sold-to-party change for existing Service Order.
When change sold-to-party button is triggered, search pop-over is shown for customer search and selection.
Sold to party change - search
Once selection is confirmed, MSA will attempt to do the following:
...
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