1 / 57

Interfaces Training

Interfaces Training. Date: 6 – 9 March 2007 Trainer: Terry Mahoney. HSSE Message. Course Guidelines. Course Rules Course will be 3 half day session with Q&A session on Friday Ask as many questions as often as possible Please be in good time for prompt 9.00am and 2.00pm start times

boris
Download Presentation

Interfaces Training

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interfaces Training Date: 6 – 9 March 2007 Trainer: Terry Mahoney

  2. HSSE Message

  3. Course Guidelines Course Rules • Course will be 3 half day session with Q&A session on Friday • Ask as many questions as often as possible • Please be in good time for prompt 9.00am and 2.00pm start times • Ask as many questions as often as possible • Important to complete ALL topics as they will link together and provide great experience. • Ask as many questions as often as possible • Important to come away with a solid grounding in this technology to take up support going forward • Mobiles off • Enjoy it! • Ask as many questions as often as possible

  4. Dobrý deň! Terry Mahoney • GSS Technical Architect • Working on GSS since 2003 • Likes to talk • Talks too fast • Contact info: • Terry.mahoney@bp.com • +1-630-836-7990

  5. BP Organization Terry Mahoney

  6. Agenda Session 1 • Introductions • Overview/ timeline • Conceptual Model • Component Architecture • General Reference Information • Interface specifics • Pricebook Session 2 • Promotions • Supply Chain • Food Services • Management Information • Finance Data • Fuel Data Session 3 • Specials • Trouble Shooting • Escalation • Release changes • Local issues

  7. Course Objectives Course objective • Understand the Architecture and flow of interfaces • Understanding timings and restrictions on Interfaces • Determine the difference between Core and Country level Interfaces • Learn problem investigation Techniques and demonstrate competence to resolve various issues and knowledge of existing PDG’s • Understand Limitations of Recovery activities • Understand the file layouts and structure of each of the interface types • Understanding role of the receiving systems and escalation in the event of problems.

  8. Session 1

  9. DART-GSS Global Template • Is a set of software components designed together • Standard solution across countries and channels of trade • Includes: • Specific version of DART (based on SAP Retail and SAP BW) • Specific versions of Retalix BOS and POS software • Interface versions (both directions) including Informatica and POSDM functionality • Specific Retalix configuration • Retalix application parameters • Key master data • Deployment may also be accompanied by changes in other site components (EPS, forecourt controller, …) • Templates are additive: each one builds on previous work. • Countries on prior templates will eventually migrate to the most current template.

  10. Programme Overview / Timeline DART-GSS Programme • The Global Site Systems (GSS) program aims to leverage BP’s scale to provide a common POS and back office solution for all of BP Retail, enabling a consistent customer experience, improved store efficiency and a dramatic reduction in total cost of ownership of site systems • Programme Timeline: • Global Template 2: Currently in pilot in ANZ • Global Template 3: • Pilot planned for UK (get dates from Kim) • ANZ sites will be retrofitted with GT3 plus ANZ localizations (GT3.2) • Global Template 4: • Pilot planned for US Franchise sites in July • First implementation outside of COCO channel

  11. Programme Activity 2006 2007 2008 Oct Nov Dec Jan Feb Mar Aprl May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Aprl May Jun Jul Aug Production GT2a Deploy Production GT 2b Deploy Retrofit Activity Production GT 2c Deploy Retrofit Activity GT 3 Retrofit Activity Development Testing Deploy GT 4 Development Development Retrofit Activity Deploy

  12. Additional head office systems SAP (DART) head office systems Retalix Host Wetstock Pricing Wetstock Inventory Supply Chain/EDI Portal eMaintenance Email Etc. Merchandising Financials MI (POS Keybd maint) Interfaces EPS DGI Interfaces Interfaces Interfaces Interface WAN infra structure Forecourt Devices Interfaces Car wash Dispensers OPPs Tank Monitor Price pole Site infra structure Other site software Retalix BOS Retalix POS Interfaces HR/Timekeeping Software distribution client Remote Support BP Global Template (config and S/W) BP Global Template (config and S/W) Other Site Devices Retalix Fuel Interfaces • QSR systems • Local cards (e.g. HTEC) • Cameras • Etc. BP Global Template (config and S/W) GSS Site Components Overview of the GSS Implementation High Level Conceptual Model Cards FEP(s) Global Template GSS Integration Work NCT/EPS Components Head office systems Existing site systems

  13. Component Architecture

  14. Interfaces and Data Flows

  15. Retail Site Secure LAN Retalix BOS POS Tran Database Retalix BOS Application Retail Site EUC LAN In scope for Global Site Systems Closely related enabling projects Out of scope Future State of BP Retail Systems - Physical layerSeparate PC and LAN for Business and EUC On-Site Systems NCT/ EPS FEP POS 1 POS n PIN pad/ Card Rdr 1 PIN pad/ Card Rdr n Tank Gauge WAN Connection (VSAT, VPN, Frame, …) Retail WAN/ Hub / Extranet Site Firewall/ Router Other Site Systems EPS Server Retail Portal Forecourt Control Application Hand Held Term. Retalix Host System BP Intranet Internet Card rdrs at pump EPS ToolKit Server Dispensers Site Manager “End User Computing” PC Trading Partners MSOffice Browser (HR, BP Portal, … ) SAP Retail Servers Data Delivery Servers (e.g. XcelleNet) Franchise Accounting Package Acrobat

  16. Key GSS Interface Reference Information

  17. Interfaces in general … General information related to all interfaces: • Majority of master data held in a common data base shared by SAP Retail and SAP BW • Files that move between SAP Retail or BW and the Retalix BOS are formatted and translated by Informatica • Head Office systems communicate with the Retalix BOS, not the POS. Downloads: • Formats specified in the Retalix Host-to-BOS document • Typical download contains multiple files; one file for each type of data • Accompanied by Diary File that the BOS uses to verify all files have arrived and contain the correct information Uploads: • Formats specified in the Retalix DailyTrans document • Typical download contains multiple files; one file for each type of data • Accompanied by Diary File that the BOS uses to verify all files have arrived and contain the correct information

  18. Price Book – Basic Elements Data origin: SAP Retail Data is maintained by country price book team • Business Purpose of Interface • List of items sold at that specific retail site along with related details. • Impact • Controls whether site can order, receive and sell those items; • Sets retail price for the items; • Key data for many site reports and uploads. • File can be sent to site ahead of time • Data lifecycle • Site system uses the price book to aggregate information for SAP IS Retail and SAP BW. • Schedule • Daily updates Transport & transformation: SAP data reformatted to Retalix H2B formats by Informatica. Transport to site handled by XcelleNet or IntraNect Destination: Retalix BOS database Items, cost prices & retail prices, additional item codes, units of measure, recipes. 10 objects in total (GT3)

  19. Pricebook: Contents • Item file • Filename is ITnnnnnn.DAT where nnnnnn is a sequential number • Item is the main file, but Items will not import if the item record refers to other pricebook items that do not exist: • Category • Main Vendor • Unit of measure • Each item linked to other entities through SAP Article Number (also called Main Item ID or Item.BarCode) • Departments, Sub-Departments, and Categories • Align with SAP Categories, Sub Categories, and BMCs • Do not change very often • Units of Measure (each, gram, case, carton, …) • Additional Item Codes (used for alternate EANs) • Item Status • Item Cost and Retail • Price List

  20. Pricebook: Item File Structure

  21. Pricebook: Linkage between download files Item File Item Cost and Retail File Vendor Table Additional Item Codes Table

  22. Contents and Record Structures Downloaded files located in C:\Office\RCV See Host to BOS interface doc version 3.5 Problem Determination and Resolution Downloaded files located in C:\xxx Current template error handling capabilities: Diary file checks Retalix import programme creates a log for each import file processed; Errors reported in BOS message window; No error correction in site system, typical resolution requires verifying data in SAP and re-downloading. Price Book continued Data origin: SAP Retail Data is maintained by country price book team Transport & transformation: SAP data reformatted to Retalix formats by Informatica Transport to site by XcelleNet or IntraNect Destination: Retalix BOS database Items, cost prices & retail prices, additional item codes, units of measure, recipes. 10 objects in total (GT3)

  23. Session 2

  24. Review of previous training Session 1 • Introductions • Overview/ timeline • Conceptual Model • Component Architecture • General Reference Information • Interface specifics • Pricebook

  25. Promotions (part of Pricebook data) • Business Purpose of Interface • Special deals for customers to increase sales • Includes identifiers so business can trace the effectiveness of the promotions • Has a start date and end date • Impact • Controls whether customer sale transactions will trigger the advertised deal • Does not change retail price for the items • Data lifecycle • Promotion codes are sent to SAP BW in the individual sales transactions. • Schedule • Typically a monthly cycle Data origin: SAP Retail Data is maintained by country price book team Transport & transformation: SAP data reformatted to Retalix formats by Informatica Transport to site by XcelleNet or IntraNect Destination: Retalix BOS database Temporary price reductions (different from normal price changes), combination groups 5 objects in total (GT3)

  26. Promotions: Contents and Record Structure • Temporary Price Reductions • Promotional prices, not new retail prices • Can override price or be a percent • Combinations • “Buy two get one free” • “Buy sandwich and drink, get crisps for free” • For both • Start dates and end dates • Can be cancelled early • Can be active on specific days of the week

  27. Contents and Record Structures Downloaded files located in C:\Office\RCV See Host to BOS interface document. Problem Determination and Resolution Downloaded files located in C:\xxx Current template error handling capabilities: Diary file checks Retalix import programme creates a log for each import file processed; Import errors reported in BOS message window; No error correction in site system, typical resolution requires verifying data in SAP and re-downloading. Promotion logic errors are hard to find in testing due to the number of possible combinations! Corrections often need to be done quickly to avoid legal penalties. Promotions continued Data origin: SAP Retail Data is maintained by country price book team Transport & transformation: SAP data reformatted to Retalix formats by Informatica Transport to site by XcelleNet or IntraNect Destination: Retalix BOS database Temporary price reductions (different from normal price changes), combination groups 5 objects in total (GT3)

  28. Pricebook - Supply Chain Information • Business Purpose of Interface • List of items vendors authorized to supply merchandise at that specific retail site. • Also specifies which items that vendor can supply • Items have to be in the pricebook first • Impact • Controls whether site can order or receive items from that vendor • If vendor not defined; items will not import!. • Data lifecycle • Included in orders and receiving documents sent from site system to SAP IS Retail. • Schedule • Not updated that frequently • Included in the daily pricebook updates Data origin: SAP Retail Data is maintained by country price book team Transport & transformation: SAP data reformatted to Retalix formats by Informatica Transport to site by XcelleNet or IntraNect Destination: Retalix BOS database Vendors and vendor items. 2 objects in total (GT3)

  29. Pricebook: Linkage between vendor files Item File Vendor Item File Vendor Table

  30. Contents and Record Structures Downloaded files located in C:\Office\RCV See Host to BOS interface document Problem Determination and Resolution Downloaded files located in C:\xxx Current template error handling capabilities: Retalix import programme creates a log for each import file processed; Errors reported in BOS message window; No error correction in site system, typical resolution requires verifying data in SAP and re-downloading. May require item updates also Supply Chain continued Data origin: SAP Retail Data is maintained by country price book team Transport & transformation: SAP data reformatted to Retalix formats by Informatica Transport to site by XcelleNet or IntraNect Destination: Retalix BOS database Vendors and vendor items. 2 objects in total (GT3)

  31. Merchandise Ordering interfaces • Merchandise pricebook has to be maintained in SAP Retail (DART) • Retalix may have to support a range of supplier order options including: • EDI. Formats that the ANZ merchandise suppliers require to be determined • Fax. Retalix BOS will print the order; site manager will fax to supplier. • Email. If suppliers need orders sent through email, Retalix will create a flat file. Either XcelleNet will generate the email, or the site manager will have to attach the Retalix flat file to an email. • Merchandise orders may be created at the Retail Site or head office • One retail site may be ordering from more than one merchandise supplier • Retail site systems use their sales history and Retalix Computer Assisted Orders to determine merchandise order quantities. • Supplier details, including how the sites can order from that supplier, will come from SAP Retail through the Pricebook download • Retail infrastructure systems (XcelleNet and IntraNect) pull order files from sites, and send invoices/ASNs back to site

  32. Retail IP WAN Data Flows – Merchandise Orders Vendor and vendor-item info in Pricebook feed BOS Retalix Pricebook Informatica / POSDM DART SAP Retail GSS Standard Export Daily export, including stock movements Retalix Computer Assisted Ordering (CAO) Module XcelleNet DART SAP BW GSS Standard Vendor Order Output Formats ANS X.12 or Retalix native flat file order format POS Vendor communications mechanism(s) BOS Printer EDI capable Vendors Vendors that can only accept paper or fax orders

  33. Food Services • Business Purpose of Interface • Links items together for recipes and production plans • Items have to be in the pricebook first • Impact • Controls whether site can accurately order and prepare made-on-site food service articles • Delivered “grab and go” articles managed like other drystock • Data lifecycle • Primary impact on uploads is accurate order quantities of ingredients. • Schedule • Not updated that frequently • Included in the daily pricebook updates Data origin: SAP Retail Data is maintained by country price book team Transport & transformation: SAP data reformatted to Retalix formats by Informatica Transport to site by XcelleNet or IntraNect Destination: Retalix BOS database Recipes, production plan templates, tree structures, …. 4 objects in total (GT3)

  34. Contents and Record Structures Downloaded files located in C:\Office\RCV See Host to BOS interface document. Problem Determination and Resolution Downloaded files located in C:\xxx Current template error handling capabilities: Retalix import programme creates a log for each import file processed; Errors reported in BOS message window; No error correction in site system, typical resolution requires verifying data in SAP and re-downloading. Food Services continued Data origin: SAP Retail Data is maintained by country price book team Transport & transformation: SAP data reformatted to Retalix formats by Informatica Transport to site by XcelleNet or IntraNect Destination: Retalix BOS database Recipes, production plan templates, tree structures, …. 4 objects in total (GT3)

  35. Management Information (MI) • Business Purpose of Interface • Details on every sale that occurred that day at that site. • Used by BW to create Management Reports for site and head office personnel • Items, tenders, etc. need to be defined in the BW data base in order for the sales data to be recognized. • Impact • Used to determine if site is operating correctly • Also used for “like-to-like” comparisons • Data lifecycle • One end of the pricebook life cycle. • Schedule • Created when POS systems change business days • Uploaded every day from every site Destination: SAP BW Transport & transformation: Retalix data transformed by IntraNect and POSDM into SAP iDocs Origin: Retalix BOS database Details on each sale (items, tenders, taxes, etc.) and Item Stock on Hand. 8 objects in total (GT3)

  36. Unreconciled file upload: Upload Records

  37. Unreconciled file upload: Upload Records

  38. Unreconciled file upload: File Structure • Record 16: Ticket Header Transaction (TILL) • Header table for every transaction on the PoS terminals. Holds sales transactions and monetary transactions. Based on Till table

  39. Contents and Record Structures Upload files located in C:\Office\XMT See DailyTrans interface document. Problem Determination and Resolution Exported files located in C:\xxx Current template error handling capabilities: Export errors not likely Problems with the data more likely to surface in the head office systems Management Information (MI) continued Destination: SAP BW Transport & transformation: Retalix data transformed by IntraNect and POSDM into SAP iDocs Origin: Retalix BOS database Details on each sale (items, tenders, taxes, etc.) and Item Stock on Hand. 8 objects in total (GT3)

  40. Finance Data • Business Purpose of Interface • Summary information on the site’s business day • Includes sales, inventories, stock movements • Includes all adjustments entered during site manager End of Day • Used by SAP Retail Financials to prepare accounting entries for that date • COCO only – franchise sites will feed a local accounting package • Impact • Used to report site financials • Also used for financial control and auditing • Schedule • Created when manager completes BOS end of day • Uploaded every day from every site Destination: SAP Retail Financials Transport & transformation: Retalix data transformed by IntraNect and POSDM into SAP iDocs Origin: Retalix BOS database Daily summary of tenders, tank readings & deliveries, Item sales, Pau ins/outs, … 15 objects in total (GT3)

  41. Reconciled file upload: Upload Records

  42. Reconciled file upload: Upload Records

  43. Reconciled file upload: Upload Records

  44. Contents and Record Structures Similar to the MI data Upload files located in C:\Office\XMT For additional detail see the Retalix DailyTrans interface document. Problem Determination and Resolution Exported files located in C:\xxx Current template error handling capabilities: Export errors not likely Most likely problem – No data because site manager has not run the BOS EoD Problems with the data more likely to surface in the head office systems Head office systems may monitor for missing data Finance Data continued Destination: SAP BW Transport & transformation: Transport & transformation: Retalix data transformed by IntraNect and POSDM into SAP iDocs Origin: Retalix BOS database Daily summary of tenders, tank readings & deliveries, Item sales, Pau ins/outs, … 15 objects in total (GT3)

  45. Session 3

  46. Review of previous Days training Session 2 • Promotions • Supply Chain • Food Services • Management Information • Finance Data • Fuel Data

  47. Fuel Data - Pricing • Business Purpose of Interface • Send fuel prices to retail sites • Only at sites where BP controls the “street price” of fuel • Looks like a message, but is really a file • Impact • Significant impact on site profitability • Manual procedures used as backup • Schedule • Typically daily - also sent as needed • Messages down • Price Change notice (may be automatic or require cashier action). Supported in most countries • Price Query (only supported in some countries) Data origin: Head Office Fuel Pricing Systems.Maintained by country fuel pricing team – different from drystock Transport & transformation: Head Office systems modified to send and receive GSS formats. Transport to and from site handled by XcelleNet or IntraNect Destination: Retalix BOS database Fuel price change notices

  48. Messages Up Confirmation of Receipt of change notice Confirmation of automatic change Price Query response Notification of manual price change by site manager Notification of price change rejection by site manager Message Upload files still located in C:\Office\XMT Problem Determination and Resolution Level 1 will hear (quickly!) Current template error handling capabilities: Reporting of arrival on site Retalix components include processing notices at the POS Fuel Data – Pricing continued Data origin: Head Office Fuel Pricing Systems.Maintained by country fuel pricing team – different from drystock Transport & transformation: Head Office systems modified to send and receive GSS formats. Transport to and from site handled by XcelleNet or IntraNect. Destination: Retalix BOS database Fuel price change notices

  49. Fuel Data – Inventory data • Business Purpose of Interface • Send fuel inventory data to the head office systems that schedule fuel deliveries • Head office systems vary, but we are using a standard interface • Similar to Reconciled file but only 1-2 records (RT13 and in some countries RT43) • Impact • Head office will not know the fuel levels at site • Manual procedures used as backup • Schedule • Daily Destination: Head office Fuel Management Systems (Orion, Aspen, …) Transport & transformation: Data reformatted to Head Office system formats by Informatica. Transport from site handled by XcelleNet or IntraNect Source: Retalix BOS database Fuel inventory snapshot. May also include fuel sales

  50. Contents and Record Structures Similar to the reconciled EOD file (RT13 and potentially others) Upload files located in C:\Office\XMT Problem Determination and Resolution Exported files located in C:\xxx Level 1 will hear (quickly!) Current template error handling capabilities: Reporting of arrival on site Retalix components include processing notices at the POS Fuel Data – Inventory Data continued Destination: Head office Fuel Management Systems (Orion, Aspen, …) Transport & transformation: Data reformatted to Head Office system formats by Informatica. Transport from site handled by XcelleNet or IntraNect Source: Retalix BOS database Fuel inventory snapshot. May also include fuel sales

More Related