Custom Objects

SL No 1 2 3 4 5 6 7

Objects List

Total without customizations

Total with required customizations 6 58 15 11 11 1 3 105 31 10 21

FI/CO 3

Reports Interfaces Conversions Enhancements Forms MSg Classes Custom transaction Grand Total Total Customisation required FICO related SD / MM

58 15

0 6 1 10

1 74

Comments as per comments in individual sheet

No customisation in FICO required as per comments in individual sheet as per comments in individual sheet

REPORTS - FINANCE Sl.No Module Development Complexity Comments At present, the bank recon is automated in Coda but in SAP the interface with banking system need to be done to automatically knock off common references. Non automation will however, increase work load. This return is submitted on a monthly basis and currently it is being done in Coda as per regulations.Non automation will however, increase work load and may get stressed as the return carries specific timelines to meet. This reporting system helps in store wise analysis of profits/losses.This is a management reporting which is done through pivot use / Cognos but inputs comes from Coda. The reporting will remain a necessity even after SAP implementation. We need to see if any other alternative is available. In Rosebys, store-wise analysis is very important.

1 FI/CO

Bank reconcilation system

High

2 FI/CO

VAT report

High

3 FI/CO 4 SD 5 SD 6 MM

Profit center - P&L Promotion change history with stock in hand at different org/merchandise heirarchy levels Sales Report Stock Movement Report

High High High High

INTERFACES - FINANCE Sl.No 1 Module FI/CO Source system Target system POS SAP Development Payment advance knocking Invoice for other expenses - Small proc/maintenance(manual EXCEL) Utility bill electronic form MANUAL SAP Property system interface SAP BACS Bank payment - EDI (BACS)(Electronic payment-Vendor-Flatfile) BACS SAP Bank statement - EDI (BACS)(Electronic statement-Flatfile) MANUAL SAP Monthly accrual entries provision HIGHJUMP SAP Highjump - Goods in HIGHJUMP SAP Highjump - PI Routines SAP HIGHJUMP Highjump - Import items(ARTICLE) (CRETE/CHANGE) SAP HIGHJUMP Highjump - Import vendors(CREATE/CHANGE) SAP HIGHJUMP Highjump - Import purchase orders(po+sto) SAP HIGHJUMP Highjump - Import order SAP HIGHJUMP Highjump - stores SAP ALLPORT Allport - Import PO information SAP EDI EDI - Order EDI SAP EDI - Invoices 3rd party full stocktake- full product list 3rd party full stocktake- Current stock for requested store 3rd party full stocktake- Counted stock from stores 3rd party Partial stocktake- Peak data reference files 3rd party Partial stocktake- Product data 3rd party Partial stocktake- Intransit SAP NUCLEUS,RGIS 3rd party Partial stocktake-Counted stock from stores 3rd party full stocktake-Counted stock from stores NUCLEUS,RGISSAP SAP DATAWAREHOUSEData warehouse - Stores SKU level inventory data SAP COGNOS COGNOS Cubes - Cubes data Product, stock, takings etc SAP DATAWAREHOUSEData warehouse - Sales data SAP E-PORTAL E-Portal - Category master SAP E-PORTAL E-Portal - Brand Master SAP E-PORTAL E-Portal - Product Master SAP E-PORTAL E-Portal - Product Category Master SAP E-PORTAL E-Portal - Top Ten Product Master SAP E-PORTAL E-Portal - Related Product Master SAP E-PORTAL E-Portal - Co-ordinate Product Master SAP E-PORTAL E-Portal - Supplier Master SAP E-PORTAL E-Portal - Store Location Master SAP E-PORTAL E-Portal - Store Opening SAP E-PORTAL E-Portal - Store by Region SAP E-PORTAL E-Portal - Customer Order header,Customer Order details,Customer Details SAP E-PORTAL E-Portal - Product Pricing Delivery E-Portal - Product Delivery Confirmation used to claim payment SAP E-PORTAL Complexity High

2 3 4 5 6 7 8 9 10 11 12 13 14 15

FI/CO FI/CO FI/CO FI/CO MM MM MM MM MM MM MM MM MM MM

High High High Medium High Medium Medium Low Medium Medium Low Medium High High

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

MM MM MM MM SD MM MM MM MM SD SD MM MM MM MM MM MM SD SD

High High High High High Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium Medium

35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58

SD SD SD SD SD SD SD SD SD FI/CO FI/CO FI/CO SD SD MM MM MM SD SD SD SD SD SD SD

POS SAP Aggergated daily sales - store wise or till wise - From POS High POS SAP Aggregated store wise or till wise Mode of Payment for Regular sales - From POS High POS SAP Gift voucher sale - From POS High POS SAP Gift voucher storewise or till wise aggregated Mode of Payment - From POS High POS SAP Curtain Express sales, Made to Measure item sales, Layaway sales - From POS High POS SAP Mode of Payment for Curtain express sales, Made to Measure item sales and High Layaway sales - From POS POS SAP Shop Credit Sales with actual customer number - From POS High E-PORTAL SAP Web order information - From Web High E-PORTAL SAP Mode of payment information for Web sales - From Web High POS SAP Bank Remmitance information - From POS High POS SAP Store Paid outs - From POS High POS SAP Store Paid ins - From POS High HIGHJUMP SAP Returns from the customer on web sales - From highjump High SAP E-PORTAL Reversing the payment transaction in case of returns to the web server - To Web High POS,HIGHJUMPSAP Store dispatches in Store to Store transfers - From POS, DC dispatches in DC High to Store transfers - From High J SAP HIGHJUMP,POS STO information in Store to Store transfers - To POS, STO information in DC to High Store transfers - To High Jum POS,HIGHJUMPSAP Store receipts in Store to Store transfers - From POS, DC receipts in Store retuns High- From High Jump SAP SAP Merchandise category - To POS High SAP POS Article Hierarchy - To POS High SAP POS,HIGHJUMP,E-PORTAL Article Master Create / Change - To POS, To High Jump, To Web High SAP POS,E-PORTAL Promotions - To POS, To Web High SAP POS,E-PORTAL Bonus Buy - To POS, To Web High SAP POS,E-PORTAL EAN Master - To POS, To Web High SAP POS,E-PORTAL Sales Sets - To POS, To Web High

CONVERSIONS - FINANCE Sl.No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Module FI/CO FI/CO FI/CO FI/CO FI/CO FI/CO FI/CO FI/CO FI/CO MM MM MM MM MM SD Development Complexity GL master Medium Cost center master Medium Profit center master Medium GL Trial balance Medium GL Balance Medium Vendor Balance Medium Customer Balance Medium Asset Balance- Prev year Medium Asset Balance- Curr year Medium Article master High Article master- extension Medium Source list Medium Initial stock Medium Purchase info record Medium Price master - Promotions High

ENHANCEMENTS - FINANCE Sl.No 1 2 3 4 5 6 7 8 9 10 11 Module MM MM MM MM MM MM MM MM MM SD SD Development Additional field requirements in article master Anticipating a major enhancements in forcasting and replenishment Purchase order enhancement for procurement block Additional field requirements Forecast execution PO block (to allow STO) Replenishment run & requirements planning Additional field in sales view Additional field in basic view To prevent article being existing in multiple promotions with validity dates Pricing routines for sales price calculations invoice Complexity Medium Medium Medium Medium High Low High Medium Medium Medium Low

FORMS - FINANCE Sl.No Module Development Complexity Comments Currently, the preprinted stationey is run off through coda for printing but if the volumes are not too high and most transactions are done through BACS, we may avoid customisation of this report. Further, if automation is required, then this activity can well be offshored too which Marie at present has retained in UK. alternatively, we may develop EFT for payments and minimal use of manual checks, this will avoid customisation of report as well. Bank remittances are not through Coda as quality is not upto standards. It is produced via program called CRYSTAL. If interfacing is possible then we may avoid customising this report. Also, cost benefit analysis to be done before deciding. Remittances are very imp. as they are tools for Vendor reconciliations and balance sign offs. This is done manually. Depending upon the volumes again it needs to be decided whether any customisation is required or not. This may not be very important report and may be handled manually too. Again, customer's perspective may be taken to close this. This is done manually. Depending upon the volumes again it needs to be decided whether any customisation is required or not. This may not be very important report and may be handled manually too. Again, customer's perspective may be taken to close this. At present, each user send this via Excel sheet so that the name of the sender can be identified easily At present, each user send this via Excel sheet so that the name of the sender can be identified easily

FI/CO

Cheque printing

High

FI/CO

Bank payment advice

Medium

FI/CO

Customer invoice-Debit Medium

4 5 6 7 8 9 10 11

FI/CO FI/CO FI/CO MM MM MM MM MM

Customer invoice-Credit Medium Vendor invoice-Debit Vendor invoice-Credit PO - Domestic PO - Import PO - Asset PO - Stock transfer Goods receipt Medium Medium Medium Medium Medium Medium Medium

MESSAGE CLASSES - FINANCE Sl.No 1 Module ALL Development Custom message class Complexity Low

CUSTOM TRANSACTIONS - FINANCE Sl.No Module Development 1 MM To mass update the forecasting and replenishment parameters 2 MM Create material inventory doc on group level Complexity High Medium

3 FI/CO

Transfer amount from individual control to bank

Medium

Comments

This is being uploaded from Merlin application through RAMS (a interfacing tool) directly in Coda. If this is to be done manually, it would be task with accuracy issues. Later, reconciliation with Cash Control A/c would become difficult. As discussed in blueprinting, various cash control a/c will be managed for each tender type. If this is done a weekly journal may be posted manually. Another suggestion is if Merlin can be interfaced with SAP and direct transfer happens.