Functional Location

As Location

Functional Location creation process is unidirectional (SAP EAM to asset central foundation) while the synchronization is bi-directional. Synchronization of Functional Location header (for example, Functional Location ID, Description, Superior Functional Location and so on) characteristics values and hierarchies are currently supported.

The important configuration objects of Functional Location synchronization object are as follows:
Exchange Object SACI_FUNCTIONAL_LOCATION
Mobile Data Object ID SACI_FUNCTIONAL_LOCATION_SYNC
Data Filter for MDO
  • Synchronization Filter fields: Company Code, Controlling Area, Cost Center, Distribution Channel, Division, Functional Location Category, Functional Location, Maintenance Plant, Sales Organization, System Status and User Status.
  • Value Mapping Configuration: The EAM specific values can be mapped against the asset central foundation values for properties like:
    • ABC Indicators: Mapped against the Risk and Criticality of asset central Location.
  • Location Configuration: System administrator must configure the required Location configuration for the below properties:
    • PUBLISH: Setting the value of this property to 'X" allows you to automatically publish the location in asset central foundation. Make sure the value for this property is empty, if automatic publishing is not required.
  • Object Identification: If customers prefer to replicate functional location as Equipment in asset central foundation, they can configure the object identification filters. The filter fields are Location Category, Manufacturer Part Number, Manufacturer Serial Number, Model Number and Object Type. If any of the Location obeys this filter rule, during replication, will be represented as equipment in asset central foundation.

As Functional Location

Prerequisite

  • The Structure Indicator configuration for Functional Location need to be pushed to asset central foundation. Refer to the Structure Indicator and Planning Data.

  • A new BC set (/ACI/ASSET_CENT_INT_2111_PATCH_1) activation is required.

The Functional Location master data synchronization is bidirectional that is, from SAP EAM to asset central foundation and vice versa. Synchronization of FLOC header (for example, FLOC Number, Description, Manufacturer and so on), characteristic value, hierarchies and business partners are currently supported. FLOC replicated to asset central foundation is always created as lean FLOC (FLOC without assignment to Model). The important configuration objects of Functional Location synchronization object are as follows:
Exchange Object

  • SACI_FUNCTIONAL_LOCATION
Mobile Data Object ID

  • SACI_FUNC_LOC_SYNC
Data Filter for MDO
  • SACI_FUNC_LOC_SYNC

    • Synchronization Filter Fields: Company Code, Controlling Area, Cost Center, Distribution Channel, Division, FLOC Category, FLOC Number, Maintenance Plant, Material, Manufacturer, Planner Group, Planning Plant, Sales Organization, System Status, User Status and Work Center.

    • Field Property Mapping: Standard property mappings configurations are pre-delivered for equipment. This can be edited based on specific needs. The standard EAM BAPIs are used to read and update data and the mapping is provided against the BAPI structure fields.

      • BAPI_ITOB_PARMS, BAPI_ITOB and

        BAPI_ITOB_FL_ONLY
    • Value Mapping Configuration: The EAM specific values can be mapped against the asset central foundation values for properties like:

      • Status: Mapped against asset central FLOC Lifecycle. Possible asset central values are 1 - Planned 2 - Fully Operational 6 - Partially Operational 9 - Not Operational 10 – Disposed Of 11 - Retired

      • Functional Location Category: Mapped against Source Business Partner Role. Possible asset central values are 1 - For my operations. 2 - For Service. 3 - For Customer.

      • FLOC Configuration: System administrator must configure the required FLOC configuration for the below properties:

        • PUBLISH: Setting the value of this property to “X” allows you to automatically publish the Functional Location in asset central foundation. Make sure the value for this property is empty, if automatic publishing is not required.

        • ALLOW_SHARED_DATA: This property controls the behavior of incoming shared equipment data into the SAP ERP system. Possible values are:

          • A - Automatic

          • R - Review

          • N - Not allowed

Handling of Shared Data

Asset data and related content can be collaboratively exchanged over the SAP Asset Intelligence Network referred as “Shared data” and can also be synchronized with connected SAP ERP systems. ​

Shared data updates are pushed to the SAP ERP system when functional location is shared (or) revisions of shared functional location are published.​

Shared data handling supports the replication of Functional Location header, Characteristics value, Functional Location structure and documents based on the sharing pattern. Processing of shared data in SAP ERP can be achieved in different modes such as Automatic, Review or Not Allowed mode.​ These modes are described as below and the configuration is defined in the Functional Location Configuration settings under config panel. For more information about configuration, refer the Functional Location topic.
  • Automatic: Use this to allow automatic creation and updates to shared asset data in backend ERP​

  • Review: Use this to review incoming shared data requests using workflow before allowing changes to asset data in ERP​. Multiple shared data changes for an equipment are consolidated in a single workflow​. Approve or Reject changes to equipment data in ERP with workflow support​.

  • Not Allowed: Use this to restrict incoming shared data requests​

In case of multiple ERP setup, shared events will reach all the connected ERP systems. It is highly recommended to enable the Review option ( workflow) so that the incoming objects can be reviewed before synchronizing.
  • Caution: If the Review option is NOT enabled, shared events may get synchronized with an incorrect ERP system.

Functional Location Structure and Document Sharing

You can share Functional Location, Functional Location structure and corresponding document over the SAP Asset Intelligence Network and these shared data can also be replicated in the SAP ERP system. To replicate/share the Functional Location structure to the ERP system, user need to share the parent object along with its components. ERP user will receive a work item on the parent object for approval and on approving the parent object all the shared child objects of the parent gets replicated automatically and the hierarchy is built accordingly.

If the user also shares the document along with the parent object, document will also be replicated to the SAP ERP system and assigned to the functional location accordingly.

Workflow

Workflow support provides visibility to incoming shared data requests in SAP ERP and helps to verify data accuracy, required preparation for incoming shared data.

  • When Review mode is opted, incoming shared data requests enters a workflow process.

  • Multiple shared data requests for an equipment are consolidated into a single workflow process.​

  • Workflow template WS 35100001 and standard task TS 35100013 are used to enable workflow approvals and process state transitions in the inbound transaction queue.

  • Incoming shared data can be processed for standard business workflow Inbox or from Inbound transaction monitor.​

Workflow Activation Steps

  1. Execute transaction SM30 and enter the Table/View name SWFDVEVTY2

  2. Click New Entries and maintain the following values:

    • Object Category: ABAP Class

    • Object Type: /ACI/CL_WF_INB_QUEUE_PROCESS
    • Event: WF_TRIGGER
    • Receiver Type: WS35100001
    • Receiver Call: Function Module
    • Receiver Function Module: SWW_WI_CREATE_VIA_EVENT_IBF
    • Event Delivery: Using tRFC (Default)
    • Linkage Activated: Select this checkbox
    • Behaviour Upon Error Feedback: System defaults
    • Receiver Status: No errors
Agent Assignment Attribute for Standard Task

  1. Access transaction PFTC_CHG.

  2. On the Task: Maintain screen, make the following entries:
    Field Name User Action and Values
    Task Type Standard Task
    Task 35100013

  3. Choose Change and in the information dialog box, choose Continue.

  4. On the Standard Task: Change screen, go to the menu bar and choose Start of the navigation path Additional Data - Next navigation step Agent Assignment - Next navigation step MaintainEnd of the navigation path.

  5. On the Standard Task: Maintain Agent Assignment screen, choose Attributes.

  6. On the Task: screen, choose General Task and Continue.