Cloud message to SAP object configuration
- proaxia
- 1 Cloud Message to SAP object configuration
- 2 Attachments for Signature
- 3 Attachments for checklist instances and templates
- 4 DMS attachments for maintenance orders and maintenance order operations (S4 only)
- 5 Attachments for Skills (crowd)
- 5.1 Prerequisites
- 5.2 Example
- 6 Attachments for Person
- 6.1 Prerequisites
- 7 Attachments for notification-based service calls
- 8 Attachments for measurement readings
- 8.1 Prerequisites
Cloud Message to SAP object configuration
Mapping between cloud message types, DOKOB (Linked SAP object) types, business types and ERP objects. It is necessary for proper handling of BDS and DMS attachments.
This mapping used to be partially ‘hard-coded' and should not be modified unless with special caution and reason.
Field | Description | Example value |
|---|---|---|
CLOUD_OBJECT | Cloud message type | SERVICECALL |
BUS_TYPE | Type of Objects in Persistent Object References | BUS2088 |
OBJID | ERP Object ID | SERVICECALL |
DOKOB | Linked SAP object | AFKO |
Currently, the following values should be filled after running the setup program:
ACTIVITY | /PACG/ECMA | ACTIVITY | /PACG/ECMA |
ACTIVITY | BUS1037 | ACTIVITY | /PACG/ECMA |
BUSINESSPARTNER | KNA1 | BUSINESSPARTNER | KNA1 |
BUSINESSPARTNER | KNA1 | CUSTOMER | KNA1 |
BUSINESSPARTNER | LFA1 | BUSINESSPARTNER | LFA1 |
BUSINESSPARTNER | LFA1 | CUSTOMER | LFA1 |
CHECKLISTINSTANCE | /PACG/ECM1 | CHECKLISTINSTANCE | /PACG/ECMC |
CHECKLISTTEMPLATE | /PACG/ECM2 | CHECKLISTTEMPLATE | /PACG/ECMT |
CHECKLISTTEMPLATE | /PACG/ECM2 | CHECKLIST_T | /PACG/ECMT |
EQUIPMENT | BUS0010 | EQUIPMENT | IFLOT |
EQUIPMENT | EQUI | EQUIPMENT | EQUI |
EXPENSE | BKPF | EXPENSE |
|
EXPENSE | BUS2072 | EXPENSE |
|
ITEM | BUS1001006 | ITEM | MARA |
MEASUREMENTREADING | BUS2092 | MEASUREMENTREADING | IMRG |
PURCHASEORDER | BUS2012 | PURCHASEORDER | EKPO (EKKO for S4) |
SERVICECALL | BUS2002 | SERVICECALL | AFKO |
SERVICECALL | BUS2007 | SERVICECALL | AFKO |
SERVICECALL | BUS2054 | PROJECT | PRPS |
SERVICECALL | BUS2054 | SERVICECALL | PRPS |
SERVICECALL | BUS2088 | SERVICECALL | AFKO |
SERVICECALL | BUS2038 | SERVICECALL | PMQMEL |
SERVICENOTIFICATION | BUS2078 | SERVICENOTIFICATION | SMQMEL |
SERVICECALL | BUS2080 | SERVICECALL | SMQMEL |
SERVICENOTIFICATION | BUS2080 | SERVICECALL | SMQMEL |
SERVICENOTIFICATION | BUS7050 | SERVICENOTIFICATION | SMQMEL |
SERVICENOTIFICATION | BUS7051 | SERVICENOTIFICATION | SMQMEL |
SERVICERATING | /PACG/ECM4 | SERVICERATING | /PACG/ECMS |
SIGNATURE | /PACG/ECM3 | SERVICERATING | /PACG/ECMS |
SIGNATURE | BUS2088 | SERVICERATING | /PACG/ECMS |
SIGNATURE | /PACG/ECM4 | SERVICERATING | /PACG/ECMS |
SKILL | BUS7030 | SKILL | /PACG/ECMQ |
PERSON | BUS1065 | PERSON | PLOGI |
Attachments for Signature
(S4)PACG 200 SP04
For Signature attachments created during Checkout, a new Business Object - '/PACG/ECM4' (FSM Checkout) has been created and replaced the previously used object 'SCOK'. This object is set up automatically. The ‘Cloud Message to DMS object' mapping (transaction /PACG/ECM_CUST_ATTA) is updated after executing the setup program. The FSM checkout object can be used also for DMS storage method, due to updating the TCLO table by the FSM Cloud Connector setup program.
Additional prerequisites for BDS attachments - after running the setup program, object /PACG/ECM4 should be maintained in transaction OAC3 (at least for JPG attachments), as well as in the 'BDS configuration' node of transaction /PACG/ECM_CUST_ATTA.
Additional prerequisites for DMS attachments - after running the setup program, object /PACG/ECMS should be maintained as an object link to a relevant document type in transaction DC10.
Attachments for checklist instances and templates
(S4)PACG 200 SP04
DMS attachments for checklist instances and checklist templates are stored using the special objects delivered with FSM Cloud Connector - /PACG/ECMC and /PACG/ECMT.
Learn more: DMS attachments for checklist instances and templates
DMS attachments for maintenance orders and maintenance order operations (S4 only)
(S4)PACG 200 SP04
DMS attachments added to maintenance orders (S4 object PMAUFK) can be sent to FSM. Attachments added to a service call in FSM (created based on a maintenance order) can be stored as maintenance order attachments in SAP S4. On SAP ECC the object AFKO is used for both service and maintenance orders, on SAP S4 two separate objects exist and can now be used. DMS attachments added to maintenance order’s operations can be sent to FSM for activities. Attachments added to an activity in FSM can be stored as both activity and maintenance order operation attachments in SAP S4.
Learn more: DMS attachments added to maintenance orders
Attachments for Skills (crowd)
(S4)PACG 200 SP04
DMS attachments added to Skills in crowd will be saved in SAP ECC/S4 with link to object /PACG/ECMQ.
Prerequisites
enable ‘Short skill key’ in transaction /PACG/ECM_SKTAG -General settings Skill_Tag. PPDPIM (HRP1001) qualifications should be used.
make sure that /PACG/ECMQ can be found in field ‘SAPOBJECT’ for cloud message type ‘SKILL’ in the hereby described configuration node
Maintain /PACG/ECMQ as an object link for the relevant document types in transaction DC10:
Example
The number corresponds to the Skill ID found in table /PACG/ECM_SKILL:
Attachments for Person
(S4)PACG 200 SP07
GOS/BDS attachments added to employees (transaction PA30) will be automatically transferred to FSM and displayed in FSM master data - on Person level, under the tab ‘Attachments’:
Attachments added in FSM master data for a Person under the tab ‘Attachments’ or ‘Personal information’ can be saved as GOS/BDS attachments in SAP ECC/S4 (to be displayed via PA30 → 'Attachment List').
Attachments deleted in SAP ECC/S4 will be automatically deleted from SAP FSM and vice versa.
The solution currently does not cover DMS storage method. If ‘DMS’ is the default storage method for all attachments, it is recommended to adjust ‘Inbound configuration’ in such a way, that attachments for object PERSON will be saved as GOS or BDS.
Prerequisites
The following ‘Cloud message to SAP object configuration’ entry should exist:
PERSON | BUS1065 | PERSON | PLOGI |
It will be created automatically after executing the setup program.
Attachments for notification-based service calls
(S4)PACG 200 SP08
GOS/BDS/DMS attachments added to service and PM notifications in SAP ECC/S4 can be transferred to FSM as service call attachments, if the notifcation-based service call scenario is configured. Make sure to enable attachments for a given notification type in transaction /PACG/ECM_VSCTDQ - Service call types (SN) definition (“Send attachment”/”Transfer SAP attachments to FSM”) and adjust the mapping configuration for object types BUS2080 and BUS2038 as shown in the table at the top.
Attachments for measurement readings
(S4)PACG 200 SP10
GOS and BDS attachments added in SAP ECC/S4 to measurement readings can be transferred to FSM and be visible on the mobile app. Attachments added during measurement reading creation on the mobile app can be stored as GOS or BDS attachments in SAP ECC/S4 and be accessible in IK13 via GOS menu → Attachment list. DMS attachments are not supported for this object.
Prerequisites
The following ‘Cloud message to SAP object configuration’ entry should exist:
MEASUREMENTREADING | BUS2092 | MEASUREMENTREADING | IMRG |
If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.