Prerequisites for Crowd integration with purchase orders

Supported objects

Since activity dispatching, acceptance and rejection are communicated with SAP ECC/S4 using Events, make sure that transaction /PACG/ECM_TRIG_SUPO - Supported object send was executed. This serves as confirmation for SAP FSM that ActivityConfirmed, ActivityAccepted and ActivityRejected events should be transferred to SAP ECC/S4.

Draft activities

Company setting CoreSystems.FSM.SyncDraftActivity.Enabled should be set to true.

Control key determination

Control keys for internal and external technicians should be set in transaction /PACG/ECM_CKDET - Control key determination:

Based on this customizing, the operation control key will be changed after assignment of an activity to a crowd technician.

Purchase order/requisition customizing

Use the following transactions to customize purchase order/requisition-related settings, such as which agreement type should be used for finding conditions for purchase requisition creation:

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1559756804

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1559232530

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1560018945

Attachments

Printout attachments created for purchase orders after Confirmation Event can be added as GOS, BDS or DMS, depending on customizing in transaction /PACG/ECM_CUST_ATTA:

PURCHASEORDER cloud message type should use SAP object EKPO (EKKO for SAP S4) in the ‘Cloud Message to SAP object configuration’ (transaction /PACG/ECM_CUST_ATTA):

This is set by the setup program.

Additional prerequisites for BDS

Transaction OAC3, maintain an entry for BUS2012, the document type should support PDF files:

BDS configuration in transaction /PACG/ECM_CUST_ATTA, maintain an entry for BUS2012:

Additional prerequisites for DMS

Transaction DC10, for the relevant document type, create an object link for object EKPO/EKKO: