...
No address - no address will be sent with service call to FSM Cloud.
Equipment address has piority - address for service will be not sent from ERP, FSM will add service call address based on assigned to service call equipment address.
Service Call address has piority - address for service call will be taken from service call header tab “order address”
SwO Ship-To, EQ addr., EQ Ship-To, EQ Sold- To - As address for service call Connector will look for Service Order Ship-To partner data. If there will be no address there then next program will search for Equipment Address in Equipment header. If its will be not possible to find both of addresses then program will search for Equipment Ship To Partner (assigned to EQ in IE02). In the end when previous addresses were not available then program will look for Equipment Sold To Party Partner (assigned to EQ in IE02)
Ship-To order , Sold- To order - Source of service call address will be partner Ship-To assigned to service call, if this address from partner will be not available then connector will search for assigned to service call Sold-To partner
Funct. Loc. addr., EQ addr., SwO Ship-To - service call address source should be functional location address and if it is not available then equipment address. In case when both of address are not knowable then address of service call will be taken from Service Order Ship to Party partner role.
EQ addr., Funct. Loc. addr., SwO Ship To - same like above but in different order first equipment address then functional location and in the end Ship to partner role assigned for service order
Service Order Address Determination - in that case program will check settings from transaction /PACG/ECM_SOAD and will take address based on customizing from there.
...