SAP MCF customizing is located in SPRO → SAP Customizing Implementation Guide → Public Sector Management → SAP Multichannel Foundation for Utilities and Public Sector → Maintain Settings for Business Processes.
As a prerequisite
- Use transaction SCPR20 to activate the BC set FMCA_MC_SETTING
- When the BC set has been executed, the example entries are created
In customizing:
- Rule_Iddefines which rule id are exposed to the Odataentity "FormBundleRule"; if no rule ids are defined in the MCF customizing, no BRFplus rules can be called
- Rule_Idcorresponds to the Activity field in the backend.
- Read_Data_From_Db defines whether forms data not provided by the odata interface is read from the database.
In customizing:
- Allowed_Form_Bundle_Type defines which form bundle types are exposed to the ODATA entity FormBundle
- If no form types are defined in the MCF customizing, no forms can be created or displayed
- Rule_Engine_Check
- If this parameter is set to "X", no submission can take place if the status is "Submitted" and the business rules engine call returns at least one error.
- Rule_Engine_Rule_Id defines which Rule ID is used in the backend to do the business rules engine check
- Straight_Through_Processing triggers billing and invoicing after a form is submitted. The backend Badi implementation IF_FMCA_MC_SETTING_BADI~FOLLOW_UP_PROCESS_FORM_SUBMIT must be defined to trigger a the follow-up process.
For more information on Straight-through Processing, refer to SAP notes.
- 2520932 - Straight Through Process (Backend developments)
- 2523576 - Straight Through Process (Frontend developments)
Note
FormBundleType returns metadata on the form bundle type.
This entity also evaluates the customizing setting "Allowed_Form_Bundle_Type" which is defined for the entity "FormBundle"
FormBundleAttachment upload/delete* attachments, which are linked to a form bundle.
- Make sure that you have assigned a virus profile in the customizing
- Virus scan interface can be used to restrict file types that can be uploaded to
Correspondence
- Display FICA correspondence documents, which have been stored in the SAP Document Management system
- If no CorrespondenceType entry is maintained, no correspondence type is exposed.
- If, for performance reasons, you want to restrict the correspondence that can be displayed to a maximum date range (for example, so that the user can only see correspondence from the last 12 months), you can use the optional parameter MaxDaysRange.
Co-Browsing enables a customer service agent to co-browse the self-service website with a customer should they face difficulty in navigating, or finding a page, menu, or button to carry out a task.
- The agent sees the same information on the website as the customer and is able to guide them.
- Security Notice: if a hacker gets access to the userid/pw of an agent, he can access all data of all taxpayers, which is exposed by MCF….
- Recommendation: ensure that user ids of co-browsing agents are not on the gateway server for end users.
The communication preferences function is implemented based on the SAP FI-CA Correspondence and Dispatch control function. The combinations of communication preferences are defined as "correspondence variants" and stored in the contract account.
Communication preferences are grouped by communication preferences category. Each communication preferences category could contain one or multiple correspondence types. The Correspondence role in the standard Correspondence Customizing is used as Communication Preference Category in SAP Multichannel Foundation for Utilities and Public Sector. The correspondence variants group all correspondence types in the communication preferences categories for controlling dispatch of send methods and periodic correspondence.
For more details, see.
These entities enable the possibility to display contract object information including fact attributes.
The method IF_FMCA_MC_SETTING_BADI~FILTER_CONTRACTOBJECTSFACTS of the class CL_FMCA_MC_SETTING_IMPL of the BAdI implementation FMCA_MC_SETTING_IMPL of BAdI FMCA_MC_BUSINESS_SETTINGS allows you to filter out contract object facts that should not be exposed to the OData service.
The default sample implementation only exposes fact_category_sequence 81 and 82 to the OData service.
The BusinessDirectory OData service allows you to search for all business partners in a system that are linked to a particular business partner role.
The Allowed_BusinessPartnerRole parameter can be used to configure which business partner role can be accessed by the BusinessDirectory OData service.
The AccountRelationship OData service enables you to display or create business partner relationships in a system.
The Allowed_Relationship_Types parameter determines which business partner relationship types are available to this OData service.
If no Allowed_Relationship_Types entry is maintained, no relationships are displayed, can be created or deleted.
For further details, check SAP Help Portal: Multichannel Foundation for Utilities and Public Sector (Public Sector).