Customizing Settings

You must make the following customizing settings to be able to use the accelerated move-in, moveout and move-in/out entry.

Permitted Contract Model

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 also determine for which division(s) a contract model is valid. The contract model is used to determine the master data template for creating a contract (see the section on master data templates).

Parking Variants
Maintain the viewcluster VC_TECAMIOVAR (using transaction SM34) to define parking variants. You can make the following settings: Header Data
Explanation:

You can store an explanatory text for the parking variant here.
StdTemp.BP/CA MoveIn (Master Data Template for Business Partner and Contract Account at

Move-In): Here, you enter the master data template from the BPARTNER category, which, when creating a move-in, is to be used to create or change business partners and contract accounts.
StdTemp.BP/CA Move-Out (Master Data Template for Business Partner and Contract Account

at Move-Out): Here, you enter the master data template from the BPARTNER category, which, when creating a move-out, is to be used to create or change business partners and contract accounts.
Create Sales Activity (Indicator: Create Sales Activity for Parked Document):

This indicator means that a sales activity is created for a parked document. The class and action of the contact are determined using the configuration determination for customer contacts. You can find the corresponding Customizing activities under, Financial Accounting Contract Accounts Receivable and Payable Basic Functions Customer Contacts. The program SAPLEC70, with the three sub-contexts 0001 (Parking: Move-In), 0002 (Parking: Move-Out) and 0003 (Parking: Move-In/Out for Business Partner) are relevant for parking. (Note: Two contacts are written during move-in/out for premise. The sub-contexts 0001 and 0002 are relevant here).
Save Immediately (Indicator: Save Immediately):

This indicator ensures that move-in and move-out documents are not created asynchronously, but immediately after an error-free parked document has been created. Division-Dependent Data Enter a contract model for each division. This serves as a default value for calling the accelerated entry interface. Field Visibility Here, you can define which fields are displayed at the parking interface. The visibility of the fields is dependent upon the process (move-in, move-out, move-in/out for business partner or move-in/out for premise). You can divide the fields into three categories: Field is Visible: These fields are immediately visible when you call the parking interface. Field is Hidden: These fields are visible when you select (expand all). We recommend this category for fields that the agent must only maintain occasionally for move-in, move-out or movein/out. Field Invisible

Allocating Parking Variants to User Groups Maintain the TECAMIOVARU table (transaction SM30) here.

Master Data Templates

To use the accelerated move-in, move-out and move-in/out entry, you must define at least two master data templates.

For more information, see the documentation IS-U.

Master Data Templates in SAP

Master Data Template Category CRMNEWCONTRACT To create utility contracts you require at least one master data template from the category CRMNEWCONTRACT, with the following properties:
You have entered a permitted contract model in the header data for the master data template. The master data template has the status E (Increased Efficiency Released).

SAP provides the EC70_MOVEIN master data template.

Copy this template and then adjust the copy to meet your requirements. When doing this, note the following: Activate the node from the CONTRACT category (create contract for move-in). Because a contract is created when you create a move-in document, the VERTRAG attribute of the node from the CONTRACT category must be a parameter. In the header data for the master data template, set the Ignore Device indicator if you do not want your master data template to change device-dependent data. When you enter meter reading results in the accelerated entry interface, these results are automatically included in the follow-up processing when you create the move-in document. This is independent of the master data template settings. Therefore, do not activate the node from the MOVE_IN_MR category (create move-in meter reading result)!

If you are using the IS-U/CRM integration, you can also use master data templates from the CRMNEWCONTRACT category with the status R (released). Instead of entering the contract model in the header data for the master data template, enter a product. SAP provides the EC70_MOVEIN master data template. Master Data Template Category BPARTNER To create or change business partners and contract accounts, you require at least one master data template from the category BPARTNER. SAP provides the following master data templates:
EC70_BPARTNER_MI (for creating or changing business partners and contract accounts for a

move-in)
EC70_BPARTNER_MO (for creating or changing business partners and contract accounts for a

move-out)

Copy this template and then adjust the copy to meet your requirements. When doing this, note the following:
If you want to enter changes to business partners and contract account as planned changes,

you require the VALDT (validity date) for the BPARTNER and CONTRACT_ACCOUNT categories.
During the move-in/out for a business partner, it can be the case that a different contract

account is used when creating the move-in document to when creating the move-out document.

Therefore, when you use the move-in/out for a business partner, you should duplicate the node from the CONTRACT_ACCOUNT category when defining your master data template. Recommendations for the Master Data Template for Accelerated Entry For more detailed information on master data templates and the master data generator, see the documentation Master Data Templates in SAP IS-U. The following recommendations apply specifically to master data templates that you must define for the accelerated move-in, move-out and move-in/out entry:
If you define a field in the accelerated entry interface as visible and hidden, the corresponding

attribute of the master data template must have the evaluation category Parameter. Otherwise, the user entries are saved in the parked document, but the master data generator does not include them in follow-up processing.
If you define the field as invisible, the corresponding attribute of the master data template must

have the evaluation category constant, do not change, or virtual.

Required entry fields (such as contract account fields) that are not visible on the accelerated

entry interface should have the evaluation category constant or virtual in the master data template from the BPARTNER category for the move-in. This ensures that the required entry fields are maintained when creating a contract account. Because a contract account that already exists is always used for move-in/outs, the evaluation category Do not change is often recommendable for required entry fields in the master data template from the BPARTNER category for the move-in/out.