Diane Kealy - Buying Channels
Ricardo Nunes - Invoicing Channels


WW Solutions:
  • Marie-Line Ardito
Regional Animator:
  • Stephane Bourgeaud-Lignot/Emma Glasson (EMEA)
  • Karina Tsuji (LATAM & NAM)
  • Lilian Cheong (APAC)



General Description - Buying Channels

Compare the performance of the Solvay Buying Channels with benchmarkable data
i.e. to understand how well the recommended buying channels by region and/or expense domain are being used
Channels Buying amount and volume details results can be analyzed by:
  • Country
  • Legal Entity
  • Plant
  • Site
  • Domain
  • Segment
  • Zone
  • GBU
  • Channel
  • Threeshold
Date Reference: PO Item Creation date
Calculation:
Based on # of PO Items
# of PO Items created in which the recommended channel was used
--------------------------------------------------------------------------------------
  Total # of PO Items created

Note: Currently, for “Energy domain” compliance level is not applicable



Buying ChannelsDefinitionCalculation
Remediation
# of PO Items created as Remediation
PO Item Requirement Urgency = “98”
Ecatalog
# of PO Items created from an eCatalog contract
  • SAP PO Type = “EC”
  • (BW PO Origin = 1)
Tail-Spend
# of PO Items created for Tail-Spend suppliers
Based on a List of suppliers
Framed Agreements
# of PO Items created for any service with agreed conditions
Includes: invoicing plans + recurring services POs (ZFO), blanket orders and Framework Orders (FO)
Transport
# of PO Items created for outbound transport
BW PO Origin = 6
Spot
# of PO Items created without any contract agreement
  • Contract number = empty
  • PIR = empty
  • PO Origin <> “12” or “13”
Stock Replenishment
# of PO Items created based on a contract and coming from MRP
  • Contract number <> empty
  • PIR <> empty
  • PO Origin = “12” or “13”


Source Information: BW (WP1 & PF1)
Core Query:
BW_QRY_MV_THRESH_0005
QV Query:
QV_BW_QRY_MV_THRESH_0005
BW Filters:
  • PO Item Deletion Flag <> X
  •  Condition: Order Value (EUR) <> 0
  •  Purchasing document type <> UB, UBNI
  • Purchasing organization <> 3100, 3010, 3102, 3103, 3300, 3303
  • Vendor Class <> G


General Description - Invoicing Channels
Compare the performance of the Solvay Invoicing Channels with benchmarkable data
i.e. to understand how does Solvay effectively positions itself through the different invoicing channels
Channels Invoicing amount and volume details results can be analyzed by:
  • Country
  • Legal Entity
  • Plant
  • Site
  • Domain
  • Segment
  • Zone
  • GBU
  • Channel
  • threshold
Date Reference: Invoice Posting date
Calculation:
Based on # of Invoices (cockpit documents)
# of Invoices created in which the recommended channel was used
--------------------------------------------------------------------------------------
Total # of Invoices createdNotes:
Currently, for “Energy domain” compliance level is not applicable
For FI Invoices (including Corporate Purchases and PCard) there are some dimensions in which normally are not be determined and therefore cannot be filtered, namely:
  • Global Business Unit
  • Plant
  • Site


Invoicing ChannelsDefinitionCalculation
PCard
# of Statement lines
Number of lines posted in G/L Accounts:
  • PF1: 2740000011
  • WP1: 40100344 + 40100346
Database here
Corporate Purchases
# of FI Invoices posted for approved vendors at corporate level
Based on a List of suppliers
Remediation
# of Remediation Invoices posted
Cockpit document type = “RG - Remediation”
2-Way-Match
# of 2-Way-Match/Value PO Invoices posted
Cockpit document type = “VP - Value PO”
FI Invoice
# of FI Invoices posted (except Corporate Purchases and PCard)
Invoice Type = “FI”
3-Way-Match
# of Invoices posted where Goods Receipt is required
Cockpit Type = “MM”, including Invoicing Plan but excluding Remediation and 2-Way-Match


Source Information: BW (WP1 & PF1)
Core Query:
BW_QRY_MV_RDSF01_0001
QV Query:
QV_BW_QRY_MV_RDSF01_0003
BW Filters:
  • Currency <> “not assigned”
  • Threshold <> “not assigned”
  • Cockpit Status <> 13 “Rejected”
  • Supplier Class <> “S, G”
  • Document Number <> “not assigned”   (i.e. document needs to be posted)
Refresh Frequency:
1st, 5th and 26th of the month


Specific Dimensions

Channels threshold
Channel
**Missing Dimensions from SBS_PtP - If you do not find the same dimensions you used to see in SBS_PtP, please refer here for details


Documents Received Overdue

KPIDefinition
Late Invoice
Invoices received after the scheduled payment date (Net due date)

Invoices with a creation date > net due date

%Documents Received Overdue

Note: # Invoices Created is based on Creation Date and it's not available in the dashboard


Source Information: BW (WP1 & PF1)
Core Query:
BW_QRY_MV_RDSF01_0001
QV Query:
QVSBS_BW_QRY_MV_RDSF01_0001B


Non Conform PReq
Numbers of PReq out of accordance to the conformity (Non conform)
Non conform refers to either one of these Purchasing Groups is equal E02, E03, FQE, N01, N02, N03, N04, N05, N06, N07, N08, N09, N10, N11, N12, N13, N14, N15 (missing of at least 1 mandatory information when creating a purchase request to create a PO). Below is the process of Non conform PREq.


Source Information: BW (WP1 & PF1)
Core Query:
BW_QRY_MV_PROVG_0004
QV Query:
QVSBS_BW_QRY_MV_PROVG_0001 (PREQ)
BW Filters
PO Transaction = ME21, ME21N, ME22, ME22N, ME23, ME23N, ME52, ME52N, ME53, ME53N, ME59, ME59N, ZBBP, #
Purchasing document type = FO, NB, ZFO
Deletion Flag = NO
PO Item Deletion Flag = NO
Exclude Condition: Order Value (EUR) <> 0
Exclude Preq Number <> #


on SBS_PtP - If you do not find the same dimensions you used to see in SBS_PtP, please refer here for details