2011 Jan 10 2:53 PM
Hi all,
We are in a situation where we want to change the Premise associated with an Moved-In Installation. We will not be able to reverse the move-in as we have considerable billing performed on that account. We are thinking about making table updates to EANL to link the installation to a new premise. has anyone faced this situation? Is it safe to make the table update to link the Installation to a new premise. Please advise.
Regards,
Yuvi.
2011 Jan 10 3:17 PM
Dear Yuvi.
An update on EANL is not sufficient for this issue.
There is so much more to consider like Table Analysis, Validation checks.....
- check whether installation occurs in table ECAMIOPRCI (IS-U: parked document: contracts and installations).
- Same POD services for the old and new premise?
One POD must have only one relationship to a Premise. Attention, if a POD has two installations
with one premise assinged, and one of these installation get a new premise, no POD splitting is possible. Checks should be provided.
- Check owner allocation for old and new premise (similar to LES64F01,FORM check_for_property, but call FM ISU_S_OWNER_FOR_PREMISE)
- EDM validations required It could be, that IDocs, for example supplier change, have old address
datas in there bodies. References of PREMISE in: Switch document, activities, incoming invoice,
inbound queue and outbound queue.
- Check if there are active switch documents for the POD (installation) that will be changed.Check should be provide.(Table EIDESWTDOC)
- Also service orders must be checked, because it could be that the address is not right and the Field service employee goes to the wrong address.
- Check regional structure for old and new premise (similar to LES64F01, FORM check_equal_addressdata)
Database Tables to be updated
- All entries of EEINV which belong to installation
- All entries of EAUSV which belong to installation
- EANL
- EBP_ADDR_SERVICE (if there is move-in for the installation and the business partner has adopted the address of the premise, either a new entry of EBP_ADDR_SERVICE has to be created or an existing one has to be
updated)
- EUIHEAD
Limitations
-No Replication of the POD to CRM (i.e. no CRM Scenario)
- Active workflows which contain both premise and installation (contract or contract account) in their container. Workflows with relations to the combination of premises with business partner, contract account, contract or installation are relevant.
And there may be more but I hope this give you an idea of what needs to be considered as changing EANL is not sufficient...
Regards
Olivia
2021 Sep 03 11:17 AM
Hi,
anyway, it's not safety to update table in DB since you can create some inconsistency, i'll recommend you to use the transaction ES64 in order to assign a new Premise to an installation. SAP will carry out all checks to do it, good luck