S4PACG 300 SP 1
- proaxia
- proaxia
The FSM Cloud Connector component was released on 02.09.2024.
Download here (package can be directly downloaded from SAP Software Centre however it is recommended to use Maintenance Planner for the installation)
FSM Cloud Connector release S4PACG 300 SP01 aligns with SAP FSM release 2408
Important info
Post-installation steps
1. Notes' installation
Check notes and install relevant ones
2. Run /PACG/ECM_SETUP
3. Adjust selection and IDOC classes for the /PACG/ECM_SERVICECALL_STATUS object in /PACG/ECM_CLSASSIG - FSM Connector's Outgoing Messages Configuration
Idoc class /PACG/ECM_CL_S_IDOC_O_SCALLSTA2
Selection class /PACG/ECM_CL_S_SEL_SCALLSTATUS2
Change Log (SAP NOTE 3511468)
Category | Feature description |
|---|---|
Business partners | Multiple addresses for business partner This feature is fully supported in the systems using central business partners management (BP). From now on, Connector can correctly handle any number of address added in FSM to a single business partner. Learn more: /PACG/ECM_BP_ADDR - Address Determination for Business Partners Deactivate expired contact persons Expired contact persons can now be synced with FSM. Such contacts after validating their relevancy are sent as inactive. This helps keep customers' information in both systems consistent. |
Equipment | Relocation of the ‘MAX EQUI’ parameter Due to introduction of a new param controlling number of equipment sent with service call, the param controlling number of equipment sent with subhierarchy was moved to /PACG/ECM_EQ1 configuration transaction |
Service orders | Redesign of the service call status customizing The latest Connector release delivers new version of /PACG/ECM_SCSTD transaction. Although its layout has not change its functionality was reimplemented in such a way that it’s easier to use and less error prone. Learn more: /PACG/ECM_SCSTD - Status of Service Call Control the number of equipment sent with service call In addition to the existing parameter which can limit the number of equipment sent with subhierarchies this SP brings another one - a parameter that can limit the number of equipment sent with a service call Learn more: /PACG/ECM_SCG - Service call general settings | Max.No.Equi/FL |
SAP S/4HANA Service | New Connector’s SP provides further integration of SAP S/4HANA Service. In this release added features covers:
Learn more: Lean Order Reserved materials
Learn more: Lean Order Checklist prefilling |
Administration & Monitoring | Change layout of /PACG/ECM_CPROP To improve usability and intelligibility of the basic settings of FSM Connector we have entirely redesigned the /PACG/CPROP transaction Learn more: /PACG/ECM_CPROP - General Properties of FSM Cloud Connector Enhancements in /PACG/ECM_ALV_USERS Transaction /PACG/ECM_ALV_USERS is now capable to show the personal area to which FSM users are assigned to. More over, it is also possible to search users based on their assignment to personal area. Learn more: /PACG/ECM_ALV_USERS - Mass User Maintenance New feature of FSM Cockpit The FSM Cockpit can now show information about the actual size of Connector related data tables. This information is update by dedicated report which can be executed on demand or scheduled as a background job Learn more: /PACG/ECM_COCKPIT2 - FSM Connector Cockpit | (S4)PACG 200 Sp14 PACG tabs statistics |
FSM Activities | Optional sending of activities with service order In SP09 we disabled unconditional sending of all activities triggered from the selection class of service call. It turned out however that on rare occasions such a process is required by therefore from now on it can be enabled by a dedicated option Learn more: /PACG/ECM_CPROP - General Properties of FSM Cloud Connector | Send activities with Service Order Suboperations reflected as hierarchy in FSM By default, for each pair operation and suboperation Connector creates independent activity. In this release we have implemented a feature which can modify Connector’s behaviour and when enabled, for a pair operation and suboperation it creates activity and a follow-up activity (former suboperation) Learn more: /PACG/ECM_ACTIVE – General Properties of E4C Activity | Suboperation activities as follow up act Region update on technician’s reassignment From now on, when an activity is reassigned to a technician belonging to a different work centre than the initial one, and the region determination is based on the operation’s work centre, the Connector will update the activity’s region assignment accordingly. Learn more: /PACG/ECM_SC_GR – Group/region for service calls/activities Work centre update in network orders For updated activities created in reference to network orders, like in case of CS order, Connector is capable of the redetermination of valid work centre (for instance in case of technicians reassignment) |
UDF | Enhancements for the UDF building program The report /PACG/ECM_UDFG_UDF gained two additional features and lost one functionality. The report can now create and send UDF definitions to multiple companies at once. Then, it can now also display the list of generated UDFs. And the thing it cannot do anymore is sending of deletion requests - for this there are dedicated tools in the Connector Learn more: /PACG/ECM_UDFG_UDF - Build UDF and UDFG out of Class. |
Performance | Save Purchase Order The even triggered on the save of the purchase orders is no longer mainteined in the SWEC transaction and instead is called by ABAP method. This way number of triggered events can be limited to those which are FSM relevant Enhancement of IDoc generator for Equipment In the IDoc generator class for equipment (and functional locations) the superfluous updates of DB tables was suppressed - this should improve overall processing. Processing if incoming activities For incoming activities the process of (re)determination valid work centres was reimplemented and simplified in a way that information can be used by related objects limiting the number of DB queries |
Authorization Objects |
|
New transactions |
|
Obsolete transactions |
|
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.