Professional Documents
Culture Documents
Support Processes
- Complementary Application
• Application Scope
• Technical Architecture
• Support
• Incidents Priorities and Categorization
• Users Management
OCM (Overheads Costing Module) is an application used to allocate white-collar costs as per the Activity
Base Costing (ABC) method. Data are received from source applications (GT/SAP, NEfamily, etc.), and
completed by a data capture by the OCM users. The application will then allocate costs as per the ABC
methodology. After that, data are sent back to the source application, (COPA for SAP). Reporting
functions are also available.
Application description should cover the following :
Critical aspects of the application
Allocation of White-Collar costs as per the ABC methodology
Interface from and to GT/SAP via MW
Interface from other accounting applications using an in-built Import functionality
Interface to other accounting applications using flat files exported from OCM by the user
Impact on Business
Costs allocated more precisely than with other methods. ABC with OCM is part of the monthly bookclosing process.
Interaction with other applications
GT/SAP data received from, then sent back to after ABC allocation
Same with non Globe accounting applications (NEfamily, etc.)
OROS is a package, with several in-house built applications used to allocate distribution costs as
per the Activity Base Costing (ABC) method. Data are received from source applications
(GT/SAP, NEfamily, etc.), and completed by a data capture by the OROS users. The application
will then allocate costs as per the ABC methodology. After that, data are sent back to the
source application, (COPA for SAP). Reporting functions are also available.
Application description should cover the following :
Critical aspects of the application
Allocation of Distribution costs as per the ABC methodology
Interface to source accounting applications using flat files exported from OCM by the user
Impact on Business
Costs allocated more precisely than with other methods. ABC with OROS is part of the monthly
bookclosing process.
Interaction with other applications
GT/SAP data received from through flat files, then sent back to after ABC allocation
Same with non Globe accounting applications (NEfamily, etc.)
MS Application Blocs
CRY
Application Library
ASP Crystal Reports
ASP Web
applications
SRS
SQL Business SQL Server
Reporting Services
Microsoft SQL Components
Server
OLAP
ORA Decision Support
Oracle
DB2
IBM DB2
RDBMS Data Layer
XMDR Data Access
SQL Server
Component BAT
Batch Server
SHSR
Shared
File Server
CAE
Complementary All All All All All All All
Applications
Endpoint
SRCH WF DMS IM EM MON SCH
Document
Search Workflow Incident Corporate Monitoring Scheduling
Management
Services Services Management Electronic Mail Services Services
Services
Business Layer
Citrix
Business
MS Application Blocs
CRY
Application Library
Crystal Reports
Workstation
SRS
SQL Business SQL Server
Reporting Services
Microsoft SQL Components
Server
OLAP
ORA Decision Support
Oracle
DB2
IBM DB2
RDBMS Data Layer
XMDR Data Access
SQL Server
Component BAT
(Proprietary) Batch Server
SHSR
Shared
File Server
CAE
Complementary All All All All All All All
Applications
Endpoint
SRCH WF DMS IM EM MON SCH
Document
Search Workflow Incident Corporate Monitoring Scheduling
Management
Services Services Management Electronic Mail Services Services
Services
Globe Users
LGO LGO
Tech Func
LGO IT team
ITSM_NETWORK_SERVICES Group
GC_COMP-APPS_ABC
SD
Middleware RG
RG
GC_COMP-APPS_ABC
ITSM_WAN Group
SD GCC_COMP-APPS_ABC
ITSM_DBA
Network Issues:
Network connection or LGO network team
Webserver identification
Create,
1ST Call Assign or
SNOW2 Issues (settings IE,
LGO desktop team
Acrobat, Excel Web Reporting)
Escalate
Non-Globe Markets
• OCM receives 2 files from legacy accounting application, and send back 1
with the result of the ABC allocation
• OROS received about 30 files from legacy accounting application, and send
back one with the result of the ABC allocation
Question to ask
- Is the issue an OROS (distribution) or OCM (white-collar) one?
- What is the issue?
- Is it an application or SAP issue?
- What dataset (OCM) or Model (OROS) are you working on when the issue arises?
Which Time Period?
- What are you doing precisely when the issue is happening (Steps, Print screen)
- What is the error message (print screen)
- If you have an issue Importing or Exporting data, attach the file(s)
Frequent Incidents
OROS Troubleshooting (Vers. 1.0) - http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3806e237b
OCM Troubleshooting (Vers. 1.0) - http://ecm.ctr.nestle.com/globelib/drl/objectId/0900f3d3806e239c
Incidents
Type of Incident and lines of SCIM to be used
OCM OROS
Requests
Users managed by key users
Citrix server access requirement in the usual way