MSA- Customer details screen
- proaxia
Analytics
Customer details screen
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:
- Trigger /DBME/MI0_S_WS01_ORD_SP_UPD web service
- Transfer current state of the order (all information collected so far will be saved in the backend system)
- Change sold to party using an event defined in parameter ORD_SP_CHANGE_EVT
- Reload updated order back into application
- Refresh pricing information
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