Executing Move-In

Objective

After completing this lesson, you will be able to carry out a move-in and create corresponding business data objects.

Move-In

Flowchart illustrating the process of integrating regional, business, and technical data for a seamless Move-In scenario, emphasizing connections and structured steps.

  • Once the technical master data (connection object, premise, installation and usually the device location and device) has been created and some of the business master data (contract partner, contract account) for the new customer, it is time to proceed to move-in processing. This function links technical master data to business master data.

  • The device location and device are not required for move-in processing.

Hint

A move-in creates the contract as of the move-in date. Using the move-out process in SAP S/4HANA Utilities, a move-out will end the contract on the move-out date.
Illustrates a sequential process for setting up services, managing data, installing devices, and handling relocations, emphasizing operational efficiency, and logistics.
Illustration of a complex data flow model highlighting relationships between customer interactions, service processes, technical setups, and business structures in utility management.
  • During a move-in, you can create the business partner, contract account and contract business master data. You can also use business partners and contract accounts that already exist in the system. This data can also be changed during the move-in.
  • The initial data creation process creates the most important technical data objects.
  • The service connection is mainly modeled using Work Management.
Illustration explaining how the move-in process connects a business partner, contract account, and installation through a contract, detailing related steps and prerequisites.
  • From a business management standpoint, a move-in is when a customer moves into an existing installation. The move-in links technical master data to business master data by allocating a contract to an installation.
  • During move-in, one or more contracts are created.
  • If the business partner and contract account already exist in the system, these master data objects can re-used during the move-in.
Graphic outlining the customer move-in process, highlighting steps like agreements, validation, payments, and setup, culminating in a successful transition to a new residence.
  • The customer reports the move-in (by telephone, for example).
  • In addition to creating the master data objects for a move-in, you can also enter meter readings, create a budget billing plan, and draw up a welcome letter within the business process.
  • During move-in processing, the system automatically generates a data record (the customer contact) that describes in detail the type of contact with the customer (phone call or letter, for example) and the reason for the contact (customer moving into premises, for example). You can supplement the information contained in the customer contact with additional data, if necessary.
  • The move-in could also be the result of deregulated market communications, executed in the background.
  • Move-in can be processed in CX Interaction Center; it can also be processed via the native screen in S/4HANA via SAP Fiori apps: Create Move-In Document and Initial Processing: Move/In/Out.
  • BAPI_ISUMOVEIN_CREATEFROMDATA enables you to create move-in documents in mass via custom program.
Timeline diagram showing the transfer of installation ownership from one customer contract to another, visualizing a seamless transition on August 1, 2014.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn