Business Process Oriented Development of Data Warehouse Structures

I've recenltly read an interesting paper by Michael Böhnlein and Achim Ulbrich-vom Ende:
Business Process Oriented Development of Data Warehouse Structures .
It discusses the derivation of data warehouse structures from business process models, as opposed to deriving relevant datasets from the underlying operational data sources.
The Semantic Object Model (SOM) methodology is also introduced. The SOM approach can be useful for the modeling of business systems as well as analysis and design.
Cheers, Davide

Similar Messages

Oracle Development Survey: Data Warehouses Customers

At the start of most data warehouse projects, or even during a project, I am sure you as customers try to find answers to the following questions to help you plan and manage your environments:
* Where can I find trend and comparison information to help me plan for future growth of my data warehouse?
* How many cpu's do other customers use per terabyte?
* How many partitions are typically used in large tables? How many indexes?
* How much should I allocate for memory for buffer cache?
* How does my warehouse compare to others of similar and larger scale?
The data warehouse development team, here at Oracle would like to help provide answers to these questions. However, to do this we need your help. If you have an existing data warehouse environment, we would like to obtain more technical information about your environment(s) by running a simple measurement script and returning the output files to us, here at Oracle. This will allow our developers to provide comprehensive documents that explain best practices and get a better understanding of which features our customers use the most. This will also allow you as Customers, to benchmark your environments compared to other customers environments.
From a Company perspective we are also interested to get feedback on features we have added to the database, are these features used, how are they used etc. For example we are keen to understand:
* Which initialization parameters are most frequently used at what values?
* How many Oracle data warehouses run on RAC? on single nodes?
* Is there a trend one-way or the other, especially as data volumes increase?
* Does this change with newer releases of the database?
All results from these scripts will be held confidential. No customers will be mentioned by name; only summaries and trends will be reported (e.g., X percent of tables are partitioned and Y percent are indexed in data warehouses that are Z terabytes and larger in size. or X percent of Oracle9i and Y percent of Oracle10g data warehouses surveyed run RAC). Results will be written up as a summarized report. Every participating customer will receive a copy of the report.
Terabyte and larger DW are the primary interest, but information on any data warehouse environment is useful. We would like to have as many customers as possible submit results, ideally by the end of this week. However, this will be an on going process so regular feedback after this week is extremely useful.
To help our developers and product management team please download and run the DW measurement script kit from OTN which is available from the following link:
http://www.oracle.com/technology/products/bi/db/10g/dw_survey_0206.html
Please return the script outputs using the link shown on the above web page, see the FAQ section, or alternatively mail them directly to me: [email protected].
Thank you and we look forward to your responses.
Message was edited by:
klaker

At the start of most data warehouse projects, or even during a project, I am sure you as customers try to find answers to the following questions to help you plan and manage your environments:
* Where can I find trend and comparison information to help me plan for future growth of my data warehouse?
* How many cpu's do other customers use per terabyte?
* How many partitions are typically used in large tables? How many indexes?
* How much should I allocate for memory for buffer cache?
* How does my warehouse compare to others of similar and larger scale?
The data warehouse development team, here at Oracle would like to help provide answers to these questions. However, to do this we need your help. If you have an existing data warehouse environment, we would like to obtain more technical information about your environment(s) by running a simple measurement script and returning the output files to us, here at Oracle. This will allow our developers to provide comprehensive documents that explain best practices and get a better understanding of which features our customers use the most. This will also allow you as Customers, to benchmark your environments compared to other customers environments.
From a Company perspective we are also interested to get feedback on features we have added to the database, are these features used, how are they used etc. For example we are keen to understand:
* Which initialization parameters are most frequently used at what values?
* How many Oracle data warehouses run on RAC? on single nodes?
* Is there a trend one-way or the other, especially as data volumes increase?
* Does this change with newer releases of the database?
All results from these scripts will be held confidential. No customers will be mentioned by name; only summaries and trends will be reported (e.g., X percent of tables are partitioned and Y percent are indexed in data warehouses that are Z terabytes and larger in size. or X percent of Oracle9i and Y percent of Oracle10g data warehouses surveyed run RAC). Results will be written up as a summarized report. Every participating customer will receive a copy of the report.
Terabyte and larger DW are the primary interest, but information on any data warehouse environment is useful. We would like to have as many customers as possible submit results, ideally by the end of this week. However, this will be an on going process so regular feedback after this week is extremely useful.
To help our developers and product management team please download and run the DW measurement script kit from OTN which is available from the following link:
http://www.oracle.com/technology/products/bi/db/10g/dw_survey_0206.html
Please return the script outputs using the link shown on the above web page, see the FAQ section, or alternatively mail them directly to me: [email protected].
Thank you and we look forward to your responses.
Message was edited by:
klaker

Business Process Repository not displaying data for 4.7 systems

Hi All,
Having a bit of an issue finding any 4.7x200 related stuff on the Business Process Repository on solar_project_admin, I checked an this should be related to the ST-ICO patch but im in ST-ICO 150-700 patch 17...
Any ideas?
System is SolMan 7.0 EHP1
Regards
Juan

Hi
The BPR is accessed via solar01
solar_project_admin is used for project creation and logical component is added here for 4.7 or other systems as per req.If that is not appearing contact ur basis team they will create a logical comp for ur req.
OR
are you having prob in adding the buss processes than you can add as shown in this guide as follows
https://websmp210.sap-ag.de/~sapdownload/011000358700002006042008E/HowTo_Impl_Bus_Proc.pdf
Hope it solves ur prb
Regards
Prakhar

No data in Business Process Analytics after setting up BPA and BPMon

Hi,
I have followed the BPA set up guide and done all the configuration for BPA. I have set up BPMon for a solution and in the logical component node i have done configuration for many application monitors.
Also in the "Load Master Data" node the master data is loaded. But still in BPA when I am selecting the time frame and applying it I am getting a message that no data is applicable in the selected time frame.
How can i get the data in BPA.

Hi Vishal,
1435043 - E2E Workload Analysis - No applicable data found
specially section 3) EFWK Resource Manager Job, wehre you find several
hints to check this job and the EFWK Adminsitration.
Also check note: 894279 Background processing in SAP Solution Manager
Please have a look at following chapter of the the BPA Setup
guide to fully understand the data flow in this application:
2 Architecture of Business Process Analytics
> 2.1 Data Retrieval and Reporting
Please also review following chapter, in to see if there are any errors
extracting the data from the managed systems to SAP Solution Manager:
3.2.3 Checking status of Solution Manager Diagnostics Extractor
Framework (EFWK)
Also check:
1570282, 1643303 and 1602437
thanks
Regards,
Vikram

Business process-BUSES

Sirs, My project is the related to the Manufacturing, industrie BUSES , Under this one what we can say as the BUSINESS PROCESS,(how to the intial stage comes to work in, and how to the finished completed structure) please what have ur valuble suggestion..... help

Dear Ameer,
ASAP Methodology
Forward Media has adopted ASAP (Accelerated SAP) as its methodology of choice for SAP implementations, upgrades and module additions.
Our in-depth knowledge of ASAP allows us to customise and streamline ASAP to suit widely varying project requirements. For example - while ASAP was originally conceived as an implementation methodology, Forward Media has found ways to apply its strengths to the smaller tasks of SAP upgrades and new module additions. Innovations such as these have become part of standard and offically endorsed ASAP methodology.
Our involvement with the ASAP methodology began in 1996, when Forward Media Director Nadia Ward worked extensively with SAP America on the creation of the original ASAP methodology. Nadia led the technical component of the first commercial trial of ASAP in an implementation for CFS in New York - in the process contributing several operational templates to the ASAP toolkit.
ASAP Phases
The ASAP methodology structures the project lifecycle into five phases which run sequentially from project start to project completion. These standard ASAP phases are:
1. Project Preparation
2. Business Blueprint
3. Realisation
4. Final Preparation
5. Go-Live and Support
Concurrently with these ASAP phases, we also run a series of continuous processes which cover the types of activities which, by their nature, transcend individual phase boundaries (eg: Quality Assurance) or which require activity throughout the project lifecycle (eg: Knowledge Transfer).
These continuous processes identified as necessary for most SAP projects:
1. Quality Assurance
2. Data Migration
3. Basis
4. Knowledge Transfer
5. Cutover Planning
6. Project Accelerators
Together, the ASAP phases and our continuous processes define the broad outline of our approach for SAP projects.
Project Management Toolkit
Forward Media has a series of Project Management tools in addition to those sourced from ASAP that we make available to our clients. These include templates such as our:
 Project Plan Template (for SAP Implementations and Upgrades)
 Data Conversion Strategy
 Cutover Plan
 ABAP specifications
 Test Scripts
 Client Landscape
 Change Management Strategy
 Month End Schedule
 Issues Log
 Phase 1: Project Preparation
 Phase 2: Business Blueprint
 Phase 3: Realization
 Phase 4: Final Preparation
 Phase 5: Go Live & Support
Phase 1: Project Preparation
In this phase of the ASAP Roadmap, decision-makers define clear project objectives and an efficient decision-making process. Here Project Organization and roles are defined and implementation scope is finalized.
System landscape and Technical Requirement
 Infrastructure need (Hardware/interfaces): Available- QuickSizing Service: to be accessed via SAPNet
 System Landscape
 High level strategies for client
 Archiving strategy
Issues Database:
Issues must be resolved before phase completion ot before beginning of the next phase. The issues can be
 Unanticipated tasks
 Normal tasks that can not be completed
 External factors that need to be dealt with.
Issues database allows the project team to enter, track and report on project issues.
Phase 2: Business Blueprint
In this phase scope of the R/3 implementation is defined & Business Blueprint is created. Business Blueprint is a detailed documentation of companys requirements.
Various tools are used in this phase.
 AcceleratedSAP Implementation Assistant
 Question & Answer Database (Q&Adb)
 Business Process Master List (BPML)
 R/3 Structure Modeler
 Business Navigator and external modeling tools
Project Management:
Activities nagement:in this work package are:
 Conducting Status meeting for project team
 Conducting steering committee meetings
 General project management
 Addressing organizational issues relating to organizational change management.
Other activities include:
 Project Team Training
 Developing the System Environment
 Defining Organizational Structure
 Defining the Business processes
R/3 reference model can be used for
 Comparing the standard functionality with your companies own organizational requirements
 Creating documentation for the conceptual design
 Optimizing business processes
 Training the project team and users
 Writing user documentation
Question and Answer Database can be used to determine
 The Baseline Scope
 Cycle Plan
 Integration test Plan
Phase 3: Realization
The purpose of Phase 3 is to configure the R/3 system. The configuration is carries out in two steps; baseline configuration & Final configuration.
Business Process Master List (BPML) is created in phase 2 as a report from Q&A database. It is used to identify, plan, schedule and monitor the configuration and testing of all R/3 scenarios and processes within the scope of an implementation. BPML is a representation of the R/3 business and transactions that are contained within the scope of the project. BPML is feeds all business information to all subsequent worksheets.
Implementation Guide (IMG):
It is the main tool for setting the parameters to configure or Customize R/3 during the realization phase. IMG reflect the chronological order in which the customizing activities are carried out.
The following aspects of configuration are also to be considered:
 Defining authorizations in the R/3 system
 Defining workflows
 Creating user documentation
System Manager Procedures
 Developing system test plans
 Defining service level commitment
 Establishing system administration functions
 Setting up Quality Assurance environment
 Defining the design of the productive system
 Defining system management procedures for the productive system
 Setting up the productive environment
At the end of this phase, Project Manager must check the status of deliverables for completeness and accuracy. This internal quality check should be carried out in addition to an external, independent third party Quality Audit.
Preparation for end-user training needs to be gone through and approved at and of this phase.
Phase 4: Final Preparation
The purpose of this phase is to complete the final preparation of the R/3 system for going live. This includes testing, user training, system management and cutover activities, to finalize your readiness to go live.
In this phase the R/3 system is handed over to individual departments for productive operation. This includes preparation of end-user documentation and training the end-users. The technical environment is installed on production system & is tested. Project managers prepare plans for going live, transfer of legacy data and support at early stages.
End-user training is a critical activity for success of the project. InfoDB may be used to plan for the User Training activities. Computer Center Management System (CCMS) must be set at this time. Simulation of productive operation system & testing the same is of great important.
The test plan contains the following activities
 Testing conversion procedures and programs.
 Testing interface programs
 Conducting volume & stress testing
 Conducting final user acceptance testing
 Developing a final go-live strategy.
The Computer Aided Test Tool (CATT) can be used to automate test sequences for key business processes.
Phase 4 also provides for the testing of the disaster recovery plan for the productive environment. Disaster downtimes are verified and details on de-escalation.
Phase 5: Go Live & Support
This phase is concerned with supporting and optimizing the operative R/3 system.
Following activities are carried out
 Production support facilities are defined.
 Validation of business processes and their configuration.
 Follow-up training for users
 Signoffs etc.
During phase 5, the first EarlyWatch session should be held, where experts from SAP analyze the systems technical infrastructure. The aim is to ensure the system functions as smooth as possible.
Version upgrades should be planned whenever found necessary. AcceleratedSAP contains a continuous roadmap, with standard activities necessary after implementation. The tasks in that structure provide solutions for all known types of continuous change: Business changes, technology changes or changes in user community.
with regards,
B.Ravindranath

Data warehouse database


Today I came across one very interesting question


"Data Warehouse can be only deployed in relation database."


Above statement is true or false.


If we see it simply without any complication or may be go back 7-8 years it's answer may be false as I find out after doing research on it


"A data warehouse can be normalized or denormalized. It can be a relational database, multidimensional database, flat file, hierarchical database, object database, etc. Data warehouse data often gets changed. And data warehouses often focus on a specific activity or entity." Larry Greenfield


The data warehouse is normally (but does not have to be) a relational database. It must be organized to hold information in a structure that best supports not only query and reporting, but also advanced analysis techniques, like data mining. Most data warehouses hold information for at least 1 year and sometimes can reach half century, depending on the business/operations data retention requirement. As a result these databases can become very large.en.wikipedia.org


But I think when we look into the complication of designing and functionality which we are expecting from a data warehouse today and plus the concept which use when designing the data warehouse structure like star scheme, snow flake etc., I think it cannot be done in any other type of database which don't follow the relation database concept. We may call it multidimensional database or ORDBMS and we may talk about cubes, measures, dimension and so on but from the base it has to follows the relation database.


Let me know if anybody has anything to say about it.

 
Regards,
 
Raj 
www.oraclebrains.com<a>
 POWERED by the people, to the people and for the people WHERE ORACLE IS PASSION.

Thanks Justin!
 
I agree with you the concept exist before the relational database was invented. Last time I know they call it EIS then they name it MIS and now data warehouse. But what I am taking about is modern data warehouse technique, If you really think that any other type of database can support it without following relational database concept. Let me know which one?
 
I am still searching for my answers and have discuss with lot of people, but when I asked them have they seen any implementation of data warehouse without using relational database, the answer that I get is always negative. 
Raj 
www.oraclebrains.com<a>
 POWERED by the people, to the people and for the people WHERE ORACLE IS PASSION.

What Master Data to hold within a Data Warehouse

Hi,
We are developing a data warehouse which will incorporate Master Data entities. We have a pre-existing Master Data Management solution which will be the system of source for MD within the DW & associated Data Marts. We have decided to have a copy
of the MD within the DW. However we are of two schools of thought on what data should be held.
One school says that only those attributes that shapes a query result should be held in the DW-MD the second says that All MD that may be used by a reporting system should be held within the DW so that it is the single source of data for the reporting
application. let me give an example. Let’s say we have a Customer MD entity with the following attributes
Customer
ID
NAME
COUNTRY *
EMAIL ADDR
CITY *
PHONE NUM
GENDER *
LAST LOGGED IN
FAX ADDR
DATE OF JOINING *
LOGO (binary)
Now, we will never do a query based on phone number, fax or email address etc. But the attributes flagged by a
* will shape queries when coupled with our facts. Such as "find all male customers with 4 or more transactions over $1000" or "find all customers registered from 2007 based in New York who have purchased an X". However when
showing the results we will always show the full customer profile including Name, email address etc. (I realise the queries are very specific and not report queries as such but they suffice for the question at hand)
The first schools says only the query shaping MD elements should form the MD within the DW and that the reporting application should obtain the remainder directly from the group MD system as required. The second school says that the DW (or the DM) should
furnish all the MD required by the application. My question is which of the two approaches is considered best practice and as importantly, why?
Cheers,
Daryl

Do you have ODS? NDS?...? or you just have Data warehouse as the only resource for covering reports and dashboards?
if you do have only the Data Warehouse then you have to cover
all report's requirements within the data warehouse, no matter it used in the filter/slicing dicing/or as display only field. So I would add those fields such as names, email address, phone number, as attributes in the data warehouse. But I will only
consider indexing and data warehouse best practices for performance tuning for attributes that participate in slicing and dicing and filtering (such as country, year....).
on the other hand; if you use SSAS multi-dimensional cube on top of your data warehouse, then you can set some attributes to be only visible (attributes for display only), and some of them to be visible and hierarchy enabled (attributes that participate
in slicing and dicing and filtering).
Regards,
Reza
SQL Server MVP
Blog:
http://rad.pasfu.com Twitter:
LinkedIn:
SQL Server Integration Services 2012 Tutorial Videos:
http://www.radacad.com/CoursePlan.aspx?course=1

Solution Directory--Business process --Check in /Out option

Dear Friends,
I am working in Solution directory (t.code: DSWP). I have created one maintenance project. In this maintenance project i have maintained the following business process.
1. Sale Order Processing
2. Production Order Processing.
These two business processes are currently running in my R/3 production process.
In SOLAR01 , "admin" tab i have assigned project team member as "ZSRAGHU" for business process 'Sale Order Processing"
Like the same way, for business process "Production order Processing" i have assigned the project team member as "ZSRAO".
In SOLAR_PROJECT_ADMIN t.code, i have checked in the box "Restrict changes to nodes in project to assigned team members" so that only assigned team member can edit the business process.
Now i have assigned this maintenance project to my Solution. (The name of my Solution is "TEST")
As per the help.sap.com document, if the business process has been "checked Out" from Solution directory by the project lead, then only the team mmeber can edit the process in SOLR01.
Am i right?
But in my system, the team members are possible to edit the business process (In SOLAR01..."Structure" tab) before the business process are being "Checked Out" from Solution directory.
I want to restrict this option to my team members.
My requirement is:
If the Business process been "Checked out" in Solution, then only the team member can able to edit the business process in SOLAR01 otherwise i can not preserve my production business process....
Please guide me to achive this & will be very much rewarded.
Note:
In "SOLAR_PROJECT_ADMIN" under "Scope" tab, check in the box "Edit structures" will NOT help to map this requirement as all aware.
Regards
Senthil

Dear Senthil,
By Business Process 'Check Out', I hope you are talking of the 'Document' attached at Process level and not the Process itself, as in the structure.
I can understand your frustration about the indicator "Restrict changes to nodes in project to assigned team members" not working.
As mentioned in the online help, did you try to work your way through Authorisation Object "AI_SA_TAB" ?
Is it due to some other authorisation that users have, which 'supersedes' this authorisation object ? Did you check any SAP Note for this object ?
If nothing else works, can you try to introduce a 'Custom Status' and use the following IMG setting to restrict it by users:
SAP Solution Manager -> Configuration -> Scenario-Specific Settings -> Cross-scenario Settings -> Document Management -> Status for Documents -> Assign Status Values for Read Authorisation
This may be a workaround !
Regards,
Srini

Create Business Process in SOLAR01 and SOLAR02

Hi Experts,
I have a basic doubt in SOLMAN. Can I add a sub process under main buisness process in Solar01 or Solar02 transactions?
For example, I am working in business process "Administering Employee HR Data", under that I have seven sub-processes as delivered. Here is my requirement, Can I add some more sub processes in there?
Prompt response is appreciated and rewarded.
Namrata.

Hi Namrata,
Please use the following links to get more info about Solar01 or Solar02 transactions.
Solar01
http://help.sap.com/saphelp_sm40/helpdata/en/45/f6da633a292312e10000000a11466f/content.htm
Solar02
http://help.sap.com/saphelp_sm40/helpdata/en/04/9dc53ace2d6265e10000000a114084/content.htm
I hope these links are helpful
Regards,
Satish.

Blue Print Documents and Business Process

Hi,
I am looking to work in XI,
Please give me brief idea about Blue Print documents in XI, who will provide it, and who will use it.
How the business process in XI is designed, who will design it, How many Integration scenarios it will consist,
Please provide me an example for this.

Please give me brief idea about Blue Print documents in XI, who will provide it, and who will use it
there is normally a team who is assigned with the duty to perform requirement gathering......additionally there may be a team who consolidates all these reqs and builds the blueprint documents out of it....same may be the case in your project....get these details from the person handling your project.....usage of these documents is for the entire projecvt team
How the business process in XI is designed, who will design it, How many Integration scenarios it will consist,
business process is developed by the functional and techinal consultants.....
Number of integration scnarios are not fixed/ limited and nobody in SDN can predict it for your project....this Q will be best answered by your manager....

Sales Forum Mandate - Business Process Topics

Hello All,
I would like to inform you of the mandate of this forum. We are looking to build a knowledge base on business process oriented questions as they relate to sales. So the questions posed should somehow relate to a business issue and should not be a purely technical issue.
For example, please do not post threads about implementation issues, customizing, BAPIs, etc. These types of questions will be better answered in CRM General and Framework forum.
You can ask questions here about how new and old functionality in CRM supports the business processes you have at your company.
Thank-you for respecting the mandate of the forum.
Regards,
Tim
Edited by: Timothy Faught on Dec 8, 2008 10:52 PM

Hi Kimmo,
I wouldn't use process steps to refine processes. This is incompatible to SAP implementation content coming from BPR (Business Process Repository). But a good idea would be to copy the main business process e.g. "Sales order processing" into two new processes on the same level, e.g. "Sales order processing by manual input" (variation1) or "Sales order processing by incoming interface" (variation2). Then you can use the Compare Button on the variations to see if any changes have been on the main business process and copy them to the variations. This minimizes the effort to keep track of changes after creating the variations. When you run transaction SA_PROJECT_UPGRADE on that project these changes even get flagged. Mostly this function is used to upgrade against BPR or a template project but it works also for copies inside a project e.g. to model variations.
Regards
Andreas

Permanent Job Opportunity - Oracle BI Data Warehouse Developer Chicago, IL

Submit Resumes to [email protected]
The Business Intelligence Specialist will play a critical role in designing, developing, deploying, and supporting data warehouse/data mart applications. In this role, the person will be responsible for all BI aspects of a data warehouse/data mart application. Primary duties will be to create reporting standards, as well as coach and support power users with selected Oracle tool. The ideal candidate will have 3+ years demonstrated experience in data warehousing and Business Intelligence tools. Must also possess excellent communication skills and an outstanding track record with the user.
Principal Duties:
Participates with internal clients to define software requirements for development, maintenance and/or improvements
Maintains accuracy, integrity, and availability of the data warehouse
Tests, monitors, manages, and validates data warehouse activity, including data extraction, transformation, movement, loading, cleansing, and updating processes
Designs and optimizes data mart models for Oracle Business Intelligence Suite.
Translates the reporting requirements into data analysis and reporting solutions.
Reviews and sign off on project plan(s).
Reviews and sign off on technical design(s).
Defines and develops BI reports for accessing/analyzing data in warehouse.
Customizes BI tools and data sets for different types of users.
Designs and develop UAT (User Acceptance Testing).
Drives improvement of BI system architecture and development process.
Develops and maintains internal relationships. Actively champions teamwork. Uses internal resources to enhance knowledge and expertise of industry, research, products and services. Provides information and support to others in the company.
Required Skills:
Education and Experience:
BS/MS in Computer Science or equivalent.
3+ years of experience with Oracle, PL/SQL Development and Data Warehousing.
Experience Oracle Business Intelligence Suite and Crystal Reports is a plus.
2-3 years dimensional modeling experience.
Demonstrated hands on experience with Unix/Linux, SQL required.
Demonstrated hands on experience with Oracle reporting tools.
Demonstrated experience with translating business requirements into data analysis and reporting solutions.
Experience in training programs/teach users to use tools.
Expertise with software development process.
Effective mediator - able to facilitate constructive and productive discussions with internal customers, external clients, and development personnel pertaining to feature definition, project scope, and status
Problem solving*identifies and resolves problems in a timely manner, gathers and analyzes information skillfully and maintains confidentiality.
Planning/organizing*prioritizes and plans work activities and uses time efficiently. Work requires continual attention to detail in composing and proofing materials, establishing priorities and meeting deadlines. Must be able to work in a fast-paced environment with demonstrated ability to juggle multiple competing tasks and demands.
Quality control*demonstrates accuracy and thoroughness and monitors own work to ensure quality.
Adaptability*adapts to changes in the work environment, manages competing demands and is able to deal with frequent change, delays or unexpected events.
Benefits/Compensation:
Employees enjoy competitive compensation. We have a full benefits package including medical and dental insurance, long-term disability and life insurance and a 401(k) plan.
The client operates within the healthcare industry.
This is a permanent full-time position. After ensuring your availability and qualifications we will put you in direct contact with the client to move forward in the process.

FORWARD THE UPDATED RESUME AS SOON AS POSSIBLE.

Defining the Business Process Structure

Dear All,
I am defining the Business Process Structure in SOLAR01.. by default we will get the following Structure
Project
               Master Data
               Organization Structure
               Business Scenario
                               Business Process
                                           Business Process Step
My Question here is , i want to add some node on parallel to to Business Scnario and Business process. as per my knowledge it is not Possible . But you guys did something on this please let me know.
Project
               Master Data
               Organization Structure
               Business Scenario
               non-SAP business scenario
                               Business Process
                                           Business Process Step
                               non-SAP business process
                                           Business Process Step
Could some expert suggest on this ?

Dear Prakash,
In solution manager till EHP1 it is not possible to meet what is ur requirement but you can do the following as an alternative
Project
Master Data
Organization Structure
Business Scenario Std Selected from BPR e.g Service Desk
Business Process std
Business Process Step Std
Business Scenario Non Std Directly entered the name of scenario in Structure tab e.g any Zscenario
Business Process Non std ( you need to add here the process for zscenario)
Business Process Step Non Std ( you need to add here the process step for z*)
But if you very specific to go with 4 main nodes as you said then you need to modify the standard with ABAP Developement and there is no alternative.
Hope it clarifies.
Regards
Prakhar

Business Process Structure

I am trying to find out which kind of terms are being used for the different levels of the process hierarchy.
Level 0 =
Level 1 =
etc
Thanks in advance
Holger

Dear Prakash,
In solution manager till EHP1 it is not possible to meet what is ur requirement but you can do the following as an alternative
Project
Master Data
Organization Structure
Business Scenario Std Selected from BPR e.g Service Desk
Business Process std
Business Process Step Std
Business Scenario Non Std Directly entered the name of scenario in Structure tab e.g any Zscenario
Business Process Non std ( you need to add here the process for zscenario)
Business Process Step Non Std ( you need to add here the process step for z*)
But if you very specific to go with 4 main nodes as you said then you need to modify the standard with ABAP Developement and there is no alternative.
Hope it clarifies.
Regards
Prakhar

Strategy in Data Warehouse Table Structure

I'm building a relational data warehouse, and there are two approaches that seem almost interchangeable to me, despite being quite different from each other.
The first approach is rather simple. I have a "User" table with a bunch of foreign keys, and then I have a bunch of other tables containing user attributes. One table for "department," another for "payroll type,"
another for "primary location," and so on for 20 different user attributes.
The second approach, instead of using 20+ tables, combines this down into far fewer. I would have an "Attribute Type" table and "Attribute" table. These two, in conjunction with a bridge table, could accommodate as many
attributes as necessary within three tables. If the business wants to track a new "user-related" attribute, I don't need any new tables. I would simply add the new attribute into the "Attribute Type" table as, say, "attribute
21," and begin tracking it. All the work could be done without ever adding new tables or columns.
Both approaches seem to maintain (at least) 3NF. Is one approach better in certain circumstances, and the other approach more appropriate at other times? Any insight is appreciated!
BrainE

Hi Brian,
The second approach with three tables is not really good here. Query Optimizer in SQL Server has a few enhancements for Star/Snowflake schemas in DW environment and 3-table schema would not be able to benefit from them. It would be also harder to maintain,
load data and query. Finally, your attributes could have different data types, which you need to store.
I would suggest to go with first solution (multiple dimensions table) and follow a few extra rules:
Avoid nullable attributes
Choose attribute data types as narrow as possible
Avoid string attributes. If needed create separate dimension tables for them
Use columnstore indexes and
Upgrade to SQL Server 2014 if it is all possible - there are multiple enhancementsin batch-mode processing there
Thank you!
Dmitri V. Korotkevitch (MVP, MCM, MCPD)
My blog: http://aboutsqlserver.com

Business Process Oriented Development of Data Warehouse Structures

Similar Messages

Maybe you are looking for