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:

 

Reporting coordinator is Sandrine Micollet

Tool leader is François Rublon.

Usage information

3 type of population for FSCM application

History

Project done between 2013 and 2015.

Roles & Access

Roles and access

Role Code
Role Description
Explanation
ZR_RCS_CA_M42ITC - Short PaymentRole menu
ZR_RCS_CA_M39ITC - Credit ManagementRole menu
ZBI_RCS_FI_A27ITC Credit Management Analysis - End User roleEnd user role

Authorisation objects

Link to the BW Catalog of role

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

Dataflow overview

Overview

Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B_p_Afe8sjVlQXVsRmNEYzRVeVU

Functional and Technical rules on Workbench + Reporting

Rules & Explanations

Model 1 - Cash Collection Piloting Tool

Model 2 - Scenario Collection Piloting Report

Model 3 - Dunning Level Report

Model 4 - Statistics FSCM Report

Common rules for legacies


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)

Specific rules for legacies

Sales employee determination

Reminder : You can see more details in following documentation :
https://docs.google.com/a/solvay.com/spreadsheets/d/1VUYjzm6EGl6KnyJpa47MBMWs3gXk_h__3F6gZCfhr5A/edit#gid=1259214365

Dependencies with other applications

FSCM applications is dependant with

Data loadings

Info providers and objects loaded

Detail of process chain, list + link between or special event done for the loading

Loading frequency

Detail of frequency : monthly; weekly or else

Average performance

if possible, give some information on average process chain duration, amount of data loaded and total data volume example: daily process chain loaded in 30 min, weekly chain loaded in 1h15, with around 2k to 10k lines in DELTA mode for a total of 10M lines in cube. The purpose is to give a general overview of the volume of data managed y the application

 

Key FigureEstimation
~ Average Process Chain Runtime 
~ Average nb of rows loaded per load 
~ Total nb of rows loaded (if full) 
~ Average Runtime for 10k lines 

Record Keeping

Give details if any historisation is done, example: keep only data greater than beginning of Y-3

Reporting

Queries End User Documentation

Query end user documentation should be created in the public "Customer Support Wiki" space under the corresponding BW application page : BW - Application. Technical query query documentation, if necessary should be added as a sub-page of this documentation using the BW Technical Query Documentation template.

 

Main queries

List the most important and complex queries only with a link to the documentation

Main functionalities

 

Broadcast

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

Specific Broadcasts (See dataflow for more details) 

Maintenance

Known bugs

No known bugs

Recurring procedure

Bursting broadcast analysis

https://drive.google.com/open?id=1VUYjzm6EGl6KnyJpa47MBMWs3gXk_h__3F6gZCfhr5A

Bursting broadcast documentation

https://docs.google.com/a/solvay.com/document/d/15DaFZFEcYsfZc98zzlox-J3QaCYbbGsMTd7GxbSHOMM/edit# (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