Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Configuration Step

Customizing transaction

Corresponding sending transaction

❗ Assign personnel areas relevant for employee transfer. Employees assigned to them can be transferred to a given FSM company (use object type ‘EMPLOYEE’)

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

Binding between an SAP user (PERSON of type ‘ERPuser’) and an HR employee (PERSON of type ‘EMPLOYEE’) is maintained via infotype 0105 Communication, subtype 0001

PA30

❗ Maintain general user settings, such as user name source or email source 

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

❗ FSM-relevant users must be entered in one of the user maintenance transactions, otherwise it won’t be possible to transfer them to SAP FSM

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

Specify how person address should be determined.

Panel
panelIconId1f4a1
panelIcon:bulb:
panelIconText💡
bgColor#FFF0B3

Learn more about Person address: Person Address

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

Permission groups (assignment to user groupsUser Policy Groups) can be managed from SAP ECC/S4, if permission group IDs are maintained in a dedicated customizing.

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

FSM user entries can be created automatically after assignment of a specified user role to an SAP user.

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

Customize how employee’s skills sent to SAP FSM should be determined.

Panel
panelIconId1f4a1
panelIcon:bulb:
panelIconText💡
bgColor#FFF0B3

See an example of skill/tag creation and transfer to SAP FSM: Configuration Steps. Learn more about prerequisites for REQUIREMENT transfer and the delivered BAdI implementation: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38175423

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

/PACG/ECM_TRIG_TAG - Tag send;

/PACG/ECM_TRIG_SKILL - Skill send

Optionally enter period work schedules which can be transferred to FSM as work time patterns. Transfer technician assignment to such a schedule.

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

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

Optionally customize what should be sent to FSM as regions (geographical regions or work centers) and how regions should be determined for technicians.

Panel
panelIconId1f4a1
panelIcon:bulb:
panelIconText💡
bgColor#FFF0B3

Learn more about Regions: Regions and planning scenarios

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136514, https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138382

/PACG/ECM_TRIG_RGPWC - Work center as Region or /PACG/ECM_TRIG_RGPAR - Address region as Region

...

Configuration Step

Customizing transaction

Corresponding sending transaction

❗ Assign sales areas relevant for customer transfer. Customers assigned to them can be transferred to a given FSM company (use object type ‘CUSTOMER’)

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

CUSTOMER MASTERDATA:

/PACG/ECM_CUSTMASTER - Customer, address, contact person

❗ Assign purchasing organizations relevant for vendor transfer. Vendors assigned to them can be transferred to a given FSM company (use object type ‘VENDOR’)

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

VENDOR MASTERDATA:

/PACG/ECM_VENDMASTER - Vendor, address, contact person

❗ Specify if SAP business partners (see transaction BP) are used on the system and should be used to determine contact persons 

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

❗ Specify which customer/vendor account groups in SAP ECC/S4 are relevant for SAP FSM and as which customer groups they should be reflected in SAP FSM (CUSTOMER/LEAD) 

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953445 ; https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137589

Specify how customer addresses should be determined.

Panel
panelIconId1f4a1
panelIcon:bulb:
panelIconText💡
bgColor#FFF0B3

Learn more about Business Partner address: Business Partner Address

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1166606379 and/or https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/2309259265

A variant of the transaction above, which uses account groups

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

❗ If Business Partners are used on a given system (see transaction BP), you must specify which BP roles are allowed for being used as an FSM customer, supplier or contact person. The customizing is prefilled by the setup program.

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

...

Scenario

Object assignment

Additional settings

Sales area-dependent

 

Sales area-dependent and exceptionally plant-dependent when a given item has no sales data but it has stock in FSM-relevant storage locations. The plant-dependent option assumes that both sales and plant-dependent materials can be sent to FSM at the same time.

One of the below conditions is met:

Plant-dependent  

 

No object-dependent

 

...