1 / 33

Collaborative SIG Sessions Go with the Flow Introduction – P2P

Collaborative SIG Sessions Go with the Flow Introduction – P2P. Hans Kolbe Celantra Systems hanskolbe@celantrasystems (415) 730-1131. Agenda. About the Presenter Why are we doing this Overview and Schedule of Webinars Sample Session Content

dacey
Download Presentation

Collaborative SIG Sessions Go with the Flow Introduction – P2P

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. Collaborative SIG Sessions Go with the FlowIntroduction – P2P Hans Kolbe Celantra Systems hanskolbe@celantrasystems (415) 730-1131

  2. Agenda • About the Presenter • Why are we doing this • Overview and Schedule of Webinars • Sample Session Content • Master Data – Perspectives (Multi-Org, Global) • Master Data Analysis – Sample • Vendor Master Decision (header / site) Discussion • P2P Master Data Elements

  3. About the Presenter • Celantra Systems provides international program management services with a strong focus on multi-org, inter-company, global compliance and implementation issues. The key element in our approach is the alignment of operational efficiency, legal/tax compliance and management reporting. Our goals are: • - Single global structure across country, currency, language, accounting and tax regime- Variations are transparent to operator and business user community- Flexibility for business growth, acquisitions, or other changes in business or legal model- Ease of support and upgrade • Celantra Systems clients include State Street Bank, Xilinx, Cree Inc., Terex, UPS, Xerox, Tektronix, British Telecom, Assa Abloy, Yahoo, Texas Instruments, PPG Industries, Dionex, Trident Microsystems and others. • Hans Kolbe has managed and advised software implementation projects for over 17, global projects for over 13 years. His extensive knowledge on Oracle applications is combined with a formal background as a German attorney, trained in international and comparative law. • E-mail: Hanskolbe@celantrasystems.com • Ph: + 1 (415) 730 - 1131

  4. Objectives of these sessions • Most educational presentation focus on a single module or single aspect of business processes. We want to provide an integrated view. • Provide in-depth understanding of integration and dependencies between the Oracle EBS modules, data elements, and functions • Organize detail review of functionality and data structure while maintaining the focus on integration.

  5. Objectives of these sessions • Each of us has specialties – Purchasing, Payables, finance, etc. – the sessions allow us to gain a good understanding of “other” modules that we may depend on (upstream) or we may impact (downstream). • Unique look across modules and related business processes for key users, trainers, implementers and application support managers

  6. Why these sessions • Implementation results and user experience showed as a broad lack of understanding of integration points and dependency. • This undermines the value of the E-Business Suite • Expansion of Oracle’s footprint and parallel versions (R11, R12, Fusion Apps, Peoplesoft, JD Edwards) and other acquisitions has diluted the original focus of OAUG sessions on the core EBS

  7. Why these sessions • Need for more integrated sessions discussed between SIG leaders for many years • To facilitate this process we coordinated with various SIG groups and presented a set of 14 sessions at Collaborate 2011 hosted in Florida • We have joined forces with the Multi-National SIG, Procurement SIG, Payables SIG, Assets SIG and the GL SIG to bring to you these webinar sessions.

  8. Focus on R12 • These webinars will walk the attendees through the transactional flow, including Master Data essentials, and take the attendees through to how data elements and actions/tasks will drive and flow through Agreements, Purchasing, Payables and Assets, with accounting impact reaching the GL to complete the process flow for a set of transactions.

  9. Focus on R12 • We hope that these sessions will better help a user understand the integration points, dependencies and cause-effect relation • The webinars will focus on functionality in R12, but may have references to earlier releases if they are deemed relevant. • Your opinion and feedback will help drive this as a significant presence at future OAUG conferences

  10. Procure to Pay - Overview A Start Supplier Return to Replacement Material Passes Inspection Y Analyze to Agreement # 2 Supplier Invoice to Payment # 4 N Requisition to Receipt Supplier will provide replacement? # 3 Y Receipt to Asset # 5 A Inspection to Disposition Subledger to Post Supplier Return to Debit # 6 End

  11. Schedule

  12. Master Data - Terminology • Refers to data elements used as parameters in transactional data repetitively • These are relatively constant and are applied across the enterprise • Chart of Accounts structure • Chart of Accounts values • Items • Vendors • These require controls and techniques to maintain for consistency

  13. Transactional Data - Terminology • Refers to a specific business event • They are controlled and reconciled through business process rules • These are unique for each transaction • Sales Order Booking • Purchase Order Receipt • Vendor Payment • Journal Entry

  14. Perspective on Master Data • It is critical to understand how each master data element is used. • Unique to an organization or global • Here are some considerations • Single Module or Across Modules - Global • Operating Unit • Inventory Org • Ledger • Security requirements

  15. Multi-Organization Structure

  16. Master Data Analysis

  17. P2P Master Data Elements • Ledger and Related Setups • Organizations • Supplier & Supplier Site • Banks & Bank Accounts • Employees • Locations – Ship-To, Bill-To, Sub-Inventory • Items • Projects, Types • Assets, Categories, Depreciation Schedules

  18. Critical Master Data Elements - 1 • Items • Separated by Inventory Organizations • Oracle Inventory provides special functionality to create the Items in a “master” organization • Each Item is assigned multiple attributes that drive the transactional and usage functionality for the item • Copy all pertinent information to other inventory transactional inventory organizations. • Some attributes are available for changes in the transactional inventory orgs • This process can be user defined with regards to the data elements copied or controlled separately

  19. Critical Master Data Elements - 2 • Vendors • The vendor table structure has been converted to TCA architecture, with additional functionality • Parties • Party Relationships • For our session we will stay with the most common differentiator Vendor Header and Vendor Site • Vendor Header : Global • Vendor Site Operating Unit Specific • Identical vendor sites must be assigned times for each operating unit. • For multi-org and multi-national implementations it is critical to manage the global vendor header correctly.

  20. Critical Master Data Elements - 3 • Banks • This has now been moved to Cash Management • Banks and Bank Addresses are shared (Global) • Bank Accounts are Legal Entity controlled and have access specific to Operating Units • For Bank Account access EBusiness Suite now uses Role Based Security(UMX) • Specific steps must be taken to grant this to avoid issues

  21. Critical Master Data Elements - 4 • Employees • Owned by Human Resources • The Employee is a resource that is governed by the Setup Business Group • Employees can cross Ledgers, Operating Units for transaction approval purposes, but MUST belong to one Ledger • Employee defaults ease transaction processing

  22. Critical Master Data Elements - 5 • Locations are linked to addresses • “Owned” by HR and used by many modules • Used for multiple purposes • Ship-to • Inventory organizations • Purchasing and receiving • HR and employees • For legal or business locations • Location records can contain important tax and legal information. (FA Locations are different records, but should be functionally related).

  23. Considerations for Supplier Header / Site • Option A: Should the vendor header be created as each legal company of the supplier (i.e. Dell Inc. (US), Dell Inc. (SG), Dell GmbH (DE), Dell S.A. (IT) • Option B: should the vendor header represent the global vendor (DELL) and each site to be a specific Dell subsidiary Dell Inc. (US), Dell Inc. (SG), Dell GmbH (DE), Dell S.A. (IT).

  24. Considerations for Supplier Header / Site • The decision will impact setups • Option A Tax controls at header and site level • Option B tax controls only at site level • Purchasing and Management reporting are impacted for setup controls, printing documents

  25. Considerations for Location Setup The same location record can be accessed and changed from multiple functional areas and responsibilities. A global “location” record policy is important to manage the impact across modules and organizations and to avoid duplications. Tools are: Naming conventions, access rights, and duplications detection

  26. Naming Convention for “Location” Setup • Locations and Addresses used for organizations (LE, OpUnit, Inv.Org, Bus Group) • Each location is used for a single org only • Name identical to the org name with added suffix _LOC; example UK_1820_OU and UK_1820_OU_LOC; • The same method can be used for all organizations.

  27. Naming Convention for “Location” Setup • All Locations are assigned to an Operating Unit or Legal Entity • Character 1+2 = Country Code, 3-6=Comp Code • Central Agreement on Region, City etc. identifier • Followed by purpose identifier

  28. Other Notes and Gotcha’s • The term “Address” has been replaced by the term “Location” in many cases with R12. • “Addresses” can be connected to Legal Entities in R12 in a direct manner. • Locations and addresses on Customer Records (Address) and Vendor Records (Sites) are in a different table structure • However, similar issues with naming convention exist. • Fixed Asset locations are in a location_flexfield, stored in a completely different table. • More at the end of this presentation

  29. Questions

  30. Thank you … for attending this session! Hans Kolbe and all the SIGs that helped created these sessions. PS. A more complete list of data elements is available upon request. hanskolbe@celantrasystems.com

  31. R12 Gotcha Locations – AddressesTopic 1 – visibility from both angles Java and Web-FormWe entered 12 locations into R12; From the Java form we can see all 12, from Web-Form we can see only 4 Big problem and confusion Java Form = 12 Locations Java Form = 12 Locations

  32. Web Form = 4 Locations Java Form = 12 Locations

  33. Other Observations on Locations and Addresses No easy way to see table used in Web-Form- No easy way to see total number of records in Web-Form - Locations are not consistently visible across Java and Web Forms. We are not sure what it depends on. Possibly I can see in Web form only those that have been entered in Web-Form. In Java I can see all. Possible strategy is to enter what you can in Web-Form, especially locations, organizations. - Locations in Java and 11I are called Addresses in Web-Form of 12 Java Form = 12 Locations

More Related