Show TOC

Function documentationMove-In, Move-Out and Move-In/Out in Standalone ERP Scenario

 

The API method CREATE_PARKEDDOCUMENT within the class CL_ISU_UMC_API_PARKEDDOCUMENT has been used to create a new parked document provided by the feature Accelerated Move-In, Move-Out and Move-In/Out Entry (transaction EC70 in SAP ERP).

The current implementation is particularly intended for the standard Move-In, Move-Out and Move-In/Out processes for the same business partner. Very little information is required to be entered by the user. After the parked document is created, the follow-up process begins, such as the creation of specific Move-In or Move-Out or Move-In/Out processes in the SAP ERP system.

Prerequisites

The parked document data must be free of errors. If the parked document contains errors, the user has to contact the customer service department of the utility company to resolve the errors in the parked document, and then complete the Move-In, Move-Out or Move-In/Out process.

Features

Based on the API CREATE_PARKEDDOCUMENT, the SAP Multichannel Foundation for Utilities OData Service entity ParkedDocument in SAP ERP requires the following fields to create a parked document:

Value

Description

ParkedDocumentID

Parked Document ID (no need for creation)

AccountID

Business Partner ID

MoveIn

Complex type MasterDataKey for Move-In

MoveOut

Complex type MasterDataKey for Move-Out

The fields in the complex type MasterDataKey are as follows:

Value

Description

ContractAccountID

Contract Account ID

PremiseID

Premise ID

Date

The date for Move-In, Move-Out or Move-In/Out

Additionally, a table for the ParkedDocumentInstallation OData Service entity in SAP ERP is also required with the following fields to create a parked document:

Value

Description

ParkedDocumentID

Parked Document ID (no need for creation)

InstallationID

Installation ID

DivisionID

Division ID

ProductID

SAP CRM Product ID (Template for Creating Contract)

ServiceProviderID

Service Provider ID

Activities

You must maintain the following configuration settings:

  • IS-U: Permitted Contract Model for Parking Customizing activity

    In the TECAMIOVARAS table (transaction SM30), enter the contract models that are relevant for the accelerated move-in, move-out and move-in/out entry. Here, you must also determine for which divisions a contract model is valid. The contract model is used to determine the master data template for creating a contract.

  • Parking Variants Customizing activity

    Maintain the view cluster VC_TECAMIOVAR (transaction SM34) to define parking variants. After creating the variants, allocate parking variants to the user groups by maintaining the TECAMIOVARU table (transaction M30).

  • Master Data Templates

    To use the accelerated move-in, move-out and move-in/out entry, at least two master data templates must be defined under the following categories:

    • Master data template category CRMNEWCONTRACT

    • Master data template category BPARTNER

More Information

For more information, see the Increased Efficiency SAP IS-U/CCS - New Developments on the SAP Service Marketplace at http://service.sap.com/utilitiesInformation published on SAP site under Start of the navigation path SAP for Utilities - Product Information Next navigation step SAP ERP for Utilities (IS-U) Next navigation step General Next navigation step Cookbooks & Guidelines End of the navigation path.