Page Comparison

Send master data for all equipment/functional location related to the service order.

Customize sending rules for equipment and functional location. Possible options are: only equipment, only functional location, both.

E.g. it’s not possible to send an equipment with the sending transaction if 'Equi&telo' is set to ‘Only Functional Location’,

When sending equipment/functional location, generate outbound idocs with all the equipments/functional locations belonging to the structure of the one that was initially being sent.

Defines the source of the Equipment Text, either from the Equipment, from the Characteristics or from the internal Note

Defines the source of the Technical Location Text, either from the Technical Location or from the Characteristics or the internal Note

Send Equipment also when Sold-to is empty

Send Technical Location also when Sold-to is empty

Standard, Equipment - or Equipment ship-to

Define Notification type per Equipment (History will be written into Notification)

Define Notification Type per Technical Location (History will be written into Notification)

GOS Attachments per Equipment / Technical Location will be transmitted.

Rule for Equipment name generation

Use Planning Plant, not maintenance plant to determine sending relevance

Do not use Equipment ID as Manufacturer serial number

Equipment's Partner Source - config option which controls where the partner information is taken from.:

Following options are

available:

• Equipment ('space') -

• Read partners from equipment

• Functional location ('X') -

• Read partners from related functional location

• Functional location, Equipment

• ('A') - Read partners from the related functional location and if there is no related functional location then read partners from equipment.

• Status
  title (S4)PACG 200 SP07

  Equi or Inherit partners from parent object

In equipment 10000023 has no partners defined. When creating service call using that equipment then partners are then taken from functional location 000128-001:

Image Removed

Lack of defined partners is not taken into account in this scenario

• ('B') - Read partners from equipment and if no partner roles were defined for that equipment get partners inherited from parent object in the equipment structure. This option works in an analogical way in case of functional locations.

Partner Function

Specify which partner (based on the entered partner function) should be sent as equipment’s Business Partner. E.g. if ‘SP’ is entered, the equipment’s sold-to party Partner will be sent as Business Partner.

Partners are retrieved from table IHPA (Plant Maintenance: Partners).

Define a partner role which represents the person responsible (owner) for the tool. The owner should be sent to the cloud.

Expand
title Example
The role VU - user responsible is maintained in SAP The role User responsible is defined to tool (equipment) partner functions After saving and sending tool to FSM, the tool responsible person defined for tool is updated in FSM:

If alternative labeling is enabled for functional locations in transaction OIPU:

processing of functional locations might end up with an error ‘Functional location does not exist', due to a different object key.

Enable this field to convert functional location key during processing of various objects and avoid errors if alternative labeling is used on the system.

Send Material from iBase as equipment

Enable sending of equipment characteristics values as UDF data (dedicated segments in outbound equipment idocs).

Learn more: Equipment characteristics - transfer and update

The setting enables sending equipment serial number without leading zeros (field ‘SERIALNR’ in idoc of type /PACG/ECM_ITYPE_EQUI).

To test the functionality, transfer an equipment with transaction /PACG/ECM_EQUI. The equipment should have a serial number maintained. Find the generated idoc of type /PACG/ECM_ITYPE_EQUI and notice that there are no leading zeros in the ‘SERIALNR’ field.

The leading zeros are absent in FSM too.

If checked, documents such as protocols and certificates attached in SAP ERP should be sent to SAP FSM as attachments linked to the tool equipment object  

Expand
title Example
Following tool (equipment) has some attachments linked in SAP: After sending tool to FSM, the attachments are visible in FSM:

If checked, Equipment of type ‘Tool’ should be sent to SAP FSM Cloud without an owner. This option allows to send the object without business partner. 

In case when the equipment (tool) is not linked with any partner and the option is checked the equipment (tool) is sent to FSM.

In case when the equipment (tool) is not linked with any partner and the option is not checked, the deletion IDOCs are created and the tool is not visible in FSM  

When a new equipment is added from FSM it will be created using this category

When a new functional location is added from FSM it will be created using this category