General presentation

Objective of the application

FSCM (Financial Supply Chain Management) application provides an unique reporting tool for the collection team, including in particular the following points:

Give a global overview of overdues (FIAR module) with a data enrichissement for disputes, promise to pay, dunning and collection data (Scenario, collection specialist ...)
Give some statistics on disputes and P2P (Nbr, average time, …)
Overdue follow up for sales team using bursting broadcast

Reporting coordinator is Sandrine Micollet

Tool leader is François Rublon.

Usage information

3 type of population for FSCM application

Collection Team
Short Payment Team (Only one query => Dispute Follow up for Short Payment)
Sales Team

History

Project done between 2013 and 2015.

Roles & Access

Roles and access

Role Code	Role Description	Explanation
ZR_RCS_CA_M42	ITC - Short Payment	Role menu
ZR_RCS_CA_M39	ITC - Credit Management	Role menu
ZBI_RCS_FI_A27	ITC Credit Management Analysis - End User role	End user role

Authorisation objects

Link to the BW Catalog of role

https://drive.google.com/open?id=10GEfKYqrT1eeTO_uHYAheL1GX7L5y_pvH0KQU64qh5I

Dataflow overview

Overview

https://drive.google.com/file/d/1EFjNonONwS-IbI8xlFPBFh2vfZIk9tRF6sjyHF9ZMCs/view

Reporting documentation drive folder:

https://drive.google.com/drive/folders/1Y5OaPXx0M99OxYCHynk9pee_AM-DdEMl

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Model 1 - Cash Collection Piloting Tool

Only open items are present in this model (delete + full loading)
Data are dispatched in tabs in the workook
By default, we display data without inter-company link (DM Flag < CLM Flag < Err Flag)
Key figures: all overdues are based on NetDueDate VS Current Date)

Model 2 - Scenario Collection Piloting Report

Data are distributed in 2 tabs
- Distribution of scenario (<=> Collection strategy => allow prioritization for coll. specialist)
- History of scenario
- WARNING : Model based on infoset with inner join => Only customer / company with a BP partner for CLM data are displayed (Same logic for Scenario)

Model 3 - Dunning Level Report

This model is used to display dunning’s information at master data level
Dunning information at transactional data (link to FI doc) is not supported
- Some technical and functional analysis must be done in order to find a way to replicate transactional dunning data (which are for certain customers, only maintained in WARP)
- Reminder : WARP is a technical company create for financial mirroring concept

Model 4 - Statistics FSCM Report

Data are distributed into 4 tabs without dimensions (nav. attr. customizing)
- Disputes Statistics (3 months displayed by default + 3 additional month)
- Promise to Pay (P2P) Statistics
- Customer TOP 10 by number of disputed
- Customer TOP 10 by disputed amount
Model contains opened and closed items (Base on business layer DSO)

Common rules for legacies

Transcodification of FI Doc. from WARP to Affiliate (For GBU determination)

This part is manage by a RFC module function in CICC and allow to find the affiliate document linked to a WARP document (Useful for data affectation of disputes and P2P which are only created into WARP for the majority of cases)
WARNING : Transcodification covers 92% of cases (Tech./Func. analysis to deepen)

Since CAMS project, WARP is not used anymore.

New transformations from factoring DSO were created, the rules are similar but the notion of "legal" and "affiliate" objects had to be added in the CICC FIAR-FSCM DSO. Please have a look at the BW ITC documentation for more information on full factoring flows.

Joining Data for FIAR, CLM, DM & WARP (Level 1 -> .. -> Level 4)
Technical Flag management (DM Flag, CLM Flag, Error Flag ...)
All doubtful accounts are filtered using subtype for identification
Use pledging factor (= FA) to identify customer managed in WARP for dunning
Customer -> BP -> Collection Specialist (1:1 Relation)
- Relation between Customer, Business Partner and Collection specialist is managed by DSO DPCLM03 & DPCLM06 and contain only CICC data (WARP + NAFTA + CICC)
- WARNING : Rule is not correct for APAC data (Tech. analysis in progress)

Specific rules for legacies

Sales employee determination

Acetow legacy: Sales Employee is linked to customer credit group associated to customer in FI document
Rhodia legacy: Sales Employee is linked to Sales Group associated to FI document
CICC legacy: Sales Employee is linked to Sales Manager of factoring document associated to FI document
Solvay legacy: Sales Employee is linked to Sales Manager of invoice associated to FI document

Reminder : You can see more details in following documentation :
https://drive.google.com/file/d/1OBV5nyjzYQnlljHxHNS5aQilmhnSu9TAAUU12DEjg70/view

Dependencies with other applications

FSCM applications is dependant with

WCAP Working Capital (FIAR flow)
ITC Invoice to Cash (FIAR data source)

Data loadings

Info providers and objects loaded

List of info providers is in the technical cockpit in Google Drive.

Loading frequency

Process chain PC_FI_FSCM_01 FSCM : GB - T - WISE 01.00 - FSCM Data (Global) - Master

During closing period (last day of the month and 4 first working days): 7 times a day: 6am, 10am, 12am, 2pm, 4pm, 6pm and 10pm (french time)

Outside closing period: 3 times a day: 6am, 12am and 6pm (french time)

Average performance

1h

Record Keeping

We keep all records. Some info providers work in delele + full loading.

Reporting

Queries End User Documentation

No documentation on queries

Main queries

Queries are available through workbooks. Workbooks have been created with Bex Analyzer 7 then migrated to SAP BO Analysis.

Main functionalities

Nothing specific

Broadcast

Bursting broadcast has been created for FSCM project (Drive by characteristic C_SALEMP - Sales Employee)

Type of broadcast which allow to send more than 700 emails with only 5 broadcast settings
- Easier maintenance / Better performance (query run only one time and then data is split using bursting logic)
Manage using control queries for selection of sales employee (+ manual flag in MD)
- WARNING : Without control query, you need to create filter in broadcast setting else for each record in master data an email will be sent (More than 60 000 sales employee)
Manage by 3 specifics process chains (One for each zone ⇔ APAC, NAM/LAM & EMEA)

Specific Broadcasts (See dataflow for more details)

Manage for DM (Director of Market) and KAM (Key Account Manager)
- These broadcasts contain specifics rules for filtering (Like list of customer, or sales employee, or account …)
- The layout is also different than for bursting broadcast
- List of email’s recipient is directly managed into the broadcast settings

Maintenance

Known bugs

No known bugs

Recurring procedure

Bursting broadcast analysis

https://drive.google.com/file/d/1DrmWtWvGgQ8HLmlXxy94HDCbz2_fCiJ63osM5hLvavQ/view

Bursting broadcast documentation

https://drive.google.com/file/d/1Z8mFBin0YRkm230dpubG3VVvjZ8LzMC2m23ifYgzLVw/view# (How to use it)
https://drive.google.com/a/solvay.com/?usp=chrome_app#folders/0B6UtwJUYvmgTYU1ndXBZczMtWTQ (How to solve issues)

Business content installation for FSCM

https://drive.google.com/open?id=1wSQPHs-4qCcIcMDpOCnJT9AcPNI_2hHXG–YBuI3Vhk

Planned Evolution

No planned evolution