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.
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.
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 |
---|---|
| Parked Document ID (no need for creation) |
| Business Partner ID |
| Complex type |
| Complex type |
The fields in the complex type MasterDataKey
are as follows:
Value | Description |
---|---|
| Contract Account ID |
| Premise ID |
| 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 |
---|---|
| Parked Document ID (no need for creation) |
| Installation ID |
| Division ID |
| SAP CRM Product ID (Template for Creating Contract) |
| Service Provider ID |
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
For more information, see the Increased Efficiency SAP IS-U/CCS - New Developments
on the SAP Service Marketplace at http://service.sap.com/utilities under .