Technical Design Review Question: Operating Concern.

I got my hands on technical design documentation for a project on COPA budget. I came up with a few questions but I will post them separately for fast closing and awards:
1. In the Data Flow Description, it was noted that
The operating concern will be 1010
Any clarification on the above 1010? Any clarification as to how the decisions on the operating concerns are made? What are the options and why is one chosen over the other.
Thanks.

Hi Caud,
http://help.sap.com/saphelp_erp2004/helpdata/en/7a/4c38b54a0111d1894c0000e829fbbd/frameset.htm
Try to take a look to this operating concern definition to better understand which char, value and account compose it to better understand how your company build this organizational unit (with a more or less uniform structure) related to its sales and the reason for what they choos this OC rather than another one !
Hope it helps!
Bye,
ROberto

Similar Messages

Technical Design Review Question: mySAP Execution Architecture.

I got my hands on technical design documentation for a project on COPA budget. I came up with a few questions but I will post them separately for fast closing and awards:
1. In the Requirements discussion, I came across something
Job naming conventions apply and completion of Autosys Job Schedule request form is required.Forward this form to the mySAP Execution Architecture team for processing
Is this a an internal team or it refers to some group at SAP company?
Is the Autosys Job Schedule request form a standard for or you think the environment had just come up a form for their internal processes? What may this include?
Thanks.

Hi,
If I understood correctly, The organization wants to maintain a document on jobs to be maintained regularly in production system. It will be used as a reference in the support of BW production activities.
I hope, the mySAP Execution Architecture team for processing is the internal team from your client.
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma

Technical Design Review Question: Key Figures

I got my hands on technical design documentation for a project on COPA budget. I came up with a few questions but I will post them separately for fast closing and awards:
In the discussions of Key Figures, a table was provided showing Name, description, source field, data type and Unit. With the exception of 5 of them, all the key figures had data type as Curr(17,2).
My confusion is why all their equivalent Units were 0Currency while the 4 exceptions which had Data Type QUAN(17,2) had Units of the form zvv90_ME, zvv094_ME, etc.
I will appreciate your thoughts on these.
Thanks

All the Key figures which are curr(17,2) are meant to be used as Amounts which can be ties to different currencies..
Like The key figure might have a number 1,000 and the corresponding entry in 0currency might be USD which means its $1000.
You can find all the valid currency keys in the TCURC table..
On similar lines For Key figures which specify quantity a few examples will be ;
100 pc
30 Hr
Where the unit is stored in 0UNIT.
Ashish

Technical Design Review Question: Requirements.

I got my hands on technical design documentation for a project on COPA budget. I came up with a few questions but I will post them separately for fast closing and awards:
1. In the Requirements, I saw a reference to some terms and I am wondering whether they are standard BW terms that I missed or, whether they are some abbreviations related to the particular project.
Product Contribution, Gross Margin, etc. reports from SAID, RAPID, and SMRS must be enabled from the BW COPA design
Any clarification on the above quote and are SAID, RAPID, and SMRS some terms in BW or some abbreviations in the project.
Thanks.

Hi Caud,
I think it's better to directly ask your client !
Probably it's something related to reportins system...
??? SMRS = (Study Management and Reporting System from PercipEnz Technologies, Inc) or (Standard Mortality Ratios)
RAPID = http://www.microwavenews.com/rapidereport.html
...but are you working on an healht and science project ?!?

Technical Design Review Question: Data target Mapping and transformation

I got my hands on technical design documentation for a project on COPA budget. I came up with a few questions but I will post them separately for fast closing and awards:
In the discussions of Data target Mapping and transformation, there was a table of characteristics, showing dimensions, BW filed, Source field, data type, etc.
1. What is the technique in deciding which characteristics get grouped together into a particular dimension?
2. Why do some dimensions only have one characteristic and what is its significance?
3. I saw one BW field, OVAL_TYPE (description= valuation type) included in three dimensions: Customer, Material and Valuation Type(only field=OVAL_TYPE). What is the significance of this repetition?
Thanks

Morning,
To define Dimension means, to group all characters together, which do have a relationship "1 to n" and not "n to m" to reduce data volume (cardinality). If you reduce cardinality (which means to define 1:m relationship whenever it is possible and group them within one common dimension) you increase performance (make performance better) because of less data volume. It is essential to understand that this can not be changed easily after definition in PROD. So data modeling is also from this point of view very important.
Example:
An accounting object has a "m:n" relation ship to the accounting partner object. that's the reason way accounting object and accounting partner object do not belong to the same dimension.
Ni hao
Eckhard Lewin

Technical Design Review Question: InfoPackage Selection

I got my hands on technical design documentation for a project on COPA budget. I came up with a few questions but I will post them separately for fast closing and awards:
1. In the discussions of InfoPackage Selection, a statement
The budgets InfoSource will have full/Replace loads, based on plan version
Can you explain what this statement may mean? I am not sure I get it right.
Thanks.

Hi Caud !
I think that thi statement refers to the possibility to delete the content of an infoprovider for the same selection criteria...so, in this case, you have to load budget data on the basis of the plan version and delete (replace) the already existing data for the same plan version loaded before !
Hope it helps!
Bye,
Roberto
http://help.sap.com/saphelp_nw04/helpdata/en/f8/e5603801be792de10000009b38f842/content.htm

Technical Design Review Question: Characteristics --UNITS

I got my hands on technical design documentation for a project on COPA budget. I came up with a few questions but I will post them separately for fast closing and awards:
1. In the discussions of characteristics I find that some were user defined i.e. begins with z and others 0.
How is the decision made to create your own Units? And in particular, what are the steps to define it in BW for the system to know it? Need to do the same on R/3 side?
Thanks.

Hi,
You do not need to create the units and currencies in BW system .Those will be populated from R/3 system .For the updation of unit and currency table(in BW) you have an option in the context menu of source sytem in the source sytem tree(RSA1).
With rgds,
Anil Kumar Sharma .P

Technical Design Review Question: Technical Build

I got my hands on technical design documentation for a project on COPA budget. I came up with a few questions but I will post them separately for fast closing and awards:
1. In the discussions of the technical build steps, the Profit Center was to be made the field for partitioning.
How is such a decision made?
And what is the implication?
Thanks.

Hi,
If the reports are profit center specific , you can built
the partitions on base of profit center. That means
reports does not take the data from multiple profit
center , then take that characterstic as base for
partition.
Here you will go for logical partitioning by
multiproviders.
http://help.sap.com/saphelp_bw32/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/frameset.htm
http://help.sap.com/bestpractices/crossindustry/businessintelligence/v131/documentation/Multi-dimensional_modeling_EN.doc
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma

BI Technical Design Review Criteria/Best Practice Assessments

Dear Experts,
I am currently involved in conducting a pre-build BITechnical Design Review i.e. Data Model structure/Extractor/Transformation Logic/Data Flow Diagrams.
Are there any tangible criteria/review template/methods out there to ensure all components are included in a BI design and that they conform to the SAP Best Practices?
Thanks,
Jony

Hi jonathan,
The BW Project guidelines can be as follows ,
Stages in BW project
1 Project Preparation / Requirement Gathering
2 Business Blueprint
3 Realization
4 Final Preparation
5 GO Live & Support
Project Preparation / Requirement Gathering
Collect requirement thru interviews with Business teams /Core users / Information Leaders .
Study & analyze KPI 's (key figures) of Business process .
Identify the measurement criteria's (Characteristics).
Understand the Drill down requirements if any.
Understand the Business process data flow if any .
Identify the needs for data staging layers in BW (i.e need for ODS if any)
Understand the system landscape .
Prepare Final Requirements Documents in the form of Functional Specifications containing :
Report Owners,
Data flow ,
KPIs ,
measurement criterias,
Report format along with drilldown requirements .
2 Business Blueprint
Check Business content against the requirements
Check for appropriate
Info Objects - Key figures & Characters
Check for Info cubes / ODS
Check for data sources & identify fields in source system
Identify Master data
document all the information in a file follow standard templates
Prepare final solution
Identify differences (Gaps) between Business Content & Functional
specification. propose new solutions/Developments & changes if required at different levels such as Info Objects ,Info cube , Data source etc . Document the gaps & respective solutions proposed follow standard templates
Design & Documentation
Design the ERD & MDM diagrams for each cube & related objects
Design the primary keys/data fields for intermediate Storage in ODS
Design the Data flow charts right from data source up to Cube .
Consider the performance parameters while designing data models
Prepare High level / Low level design documents for each data model.--- follow standard templates
Identify the Roles & Authorizations required and Document it follow standard templates
final review of design with core BW users .
Sign off the BBP documents
3 Realization
Check & Apply Latest Patches/Packages ...in BW & R/3 systems.
Activate/Build & enhance the cubes/ODS as per data model designs...maintain the version documents .
Identify & activate Info objects / Master data info sources / attributes ,prepare update rules
Assign data sources .prepare transfer rules , prepare multi providers . prepare Info packages .
perform the unit testing for data loads.both for master data & transaction data .
develop & test the end user queries .
Design the process chains ,schedule & test
create authorizations / Roles assign to users ..and test
Apply necessary patches & Notes if any .
freeze & release the final objects to quality systems
perform quality tests .
Re design if required . (document changes, maintain versions)
4 Final Preparation
Prepare the final check list of objects to be released .identify the dependencies & sequence of release
perform Go Live checks as recommended by SAP in production system
keep up to date Patch Levels in Production system
Test for production scenarios in a pre-production system which is a replica of production system .
Do not Encourage the changes at this stage .
freeze the objects .
5 GO Live & Support
keep up to date Patch Levels
Release the objects to production system
Run the set ups in R/3 source system & Initialize Loads in BW
Schedule Batch jobs in R/3 system (Delta loads)
schedule the process chains in BW .
Performance tuning on going activity
Enhancements - if any
You can get some detailed information in the following link.
http://sap.ittoolbox.com/documents/document.asp?i=3581
Try to go to ASAP implementation roadmap.
https://websmp103.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000420636&_SCENARIO=01100035870000000202
Check the links below that gives you brief overview of the above steps .
https://websmp201.sap-ag.de/asap
http://www.geocities.com/santosh_karkhanis/ASAP/
ASAP
https://websmp201.sap-ag.de/asap
http://www.geocities.com/santosh_karkhanis/ASAP/
https://service.sap.com/roadmaps
https://websmp104.sap-ag.de/bi
***Please reward if useful.**
Blue Print:
http://www.sap.com/services/servsuptech/bestpractices/index.epx --- look for blueprint
http://iris.tennessee.edu/Blueprint/BW/BW-Blue%20Print-Final.doc
http://help.sap.com/bp_biv335/BI_EN/html/Business_Blueprint.htm
You can get some detailed information in the following link.
http://sap.ittoolbox.com/documents/document.asp?i=3581
also please chck out
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
a hwo to on BI7.0 upgrade .. also as suggested check out the BW upgrade roadmap on the support portal..
Hope it helps..
CSM Reddy
Assign points if helpful
Message was edited by:
CSM REDDY

Maintain Operating Concern

We are only tracking expenses & revenue by products. My question is , while maintaining Operating Concern, do we need to choose the Characteristics. Because I do not see the Characteristic "Product" there. All we have there is "Product Hierarchy". How do we get to choose Product in "Maintain Operating Concern"?

Hi Sheena,
In KEA0 Product is a Fixed charachteristic provided by SAP. The technical field name is ARTNR and origin table is MARA. You can check the field once you click on extras - Fixed fields in data structure view of KEA0.
Hope it helps.
Regards,
Abhisek

Info about a new value field in a live operating concern

Hi Team,
I'm working on 4.7 system.
I have a live Operating Concern with 120 value fields in "Active" Status.
Some of them never have been posted until now. I need a new "Quantity type" value field, but I can't create another one because I already have 120.
In addition, the value fields that have not been used until now are "Amount type" ones.
Is it possible to delete or modify one of these value files and create another "Quantity type" one, considering that Operating Concern is productive? And how can I do it? What kind of problems could I have?
Best Regards,
Gio

Hi Gio,
Good evening and greetings,
Please go through the SAP Note No.21207 on Deleting a Characteristic / Value Field from an active Operating Concern. This should clarify your questions.
Please reward points if the note is of some use to you.
Thanking you,
With kindest regards
Ramesh Padmanabhan

Adding new value fields to an existing and productive operating concern

Hi,
I would like to have 5 new value fields active in 4 out of 6 operating concerns that I am working with.
Is it correct that I could do this one of the following ways:
1. Use a value field that exists already in an operating concern and rename it?
In this case is it necessary to regenerate the operating concern?
Do I transport the change ?
2. Create an entirely new value field, and assign it to the operating concern?
Is it necessary to regenerate the operating concerns in question?
Do I transport the change?
3. Select a value field that is currently in the system but is not assigned to any operating concern eg some kind of SAP delivered value field? How do I assign it to the op con? Do I need to re gen the op con?
Which way is the best or is there a 4th option?
Thanks for your help in adviance
Regards
Aisling

Hi,
This note is a catalogue of notes of consulting notes where SAP tell you steps, reports to use and son . If you read them (these notes and related notes) you have the steps, guides, reports that you must use. Better advice. Try a solution with all steps in mind and check it in a quality enviroment. As you know there a lot of things in CO-PA concern (you have your own tables, with your own fields, your reports as KE2Rxxxx, and so on), your secondary indexes, etc.. , the best is try the solution in your Quality Enviroment (a quasi-clone of your production enviroment) and check the results (create SO, invoices, after modifications to check possible problems,...).
Regards,
Eduardo
pd: I forgot. If the size of tables (CE4xxxx, CE1XXXX, ...check them with DB02) are so big, get the opinion of a Basis Consultant. Surely in the before note there notes about this issue.
Edited by: Eduardo Hinojosa on Apr 23, 2010 2:41 PM

Operating Concern -COPA.. urgent!!

Hello friends
I've created a couple of new value fields in an operating concern in development box. Also generated the operating concern. It didn't prompt me for any transport request though.
How do I create a trasnport request to transport the new fields to the QAS?
I've tried creating them manually in QAS, but it wouldn't let me to.
I'm sure there are some special transports need to be done in COPA to get the desired results, but don't know what they are..
Can someone help please to resolve this issue?
Thanks a lot.
Message was edited by: Fico Able

Thanks for ur answer, but I cannot retransport the operating concern. The op.concern was established 3 years back and I wouldn't risk touching it.
My question is how would I create a trasnport when i create new value fields in an operating concern, so that I can have the same new value fields in QAS as well.
Thanks very much

Definition of a new operating concern

Hi experts,
We have a question about transporting a new operating concern.
To transport customizing settings of the new operating concern we used Tcode KE3I.
We defined new characteristics and value fields for the new operating concern.
In the customizing request we can see that for the tables TKEF and TKEFD all entries (old and new) were included.
But all old fields already exists in the target system of the transport request.
Should we keep the old fields (existing characteristics and value fields) in the customizing request or should we delete them and leave only the new ones ????
Thanks.

Cincean:
By old entries you mean the SAP delivered entries/characteristics??
Or the characteristics you previously created?, if so, just keep it that way and transport
Vj
Assign points if info helps

Why is there only one Operating Concern defined in GBI?

Hi all,
I have the following question: when looking at the CO structure of the GBI case study, why is there only one, global operating concern defined? According to the definition of an OC, it is the level whereupon profitability analysis is performed. So why is in GBI that has two very distinct business areas not at least two OCs defined (one per business area), if not more (per product)?
As a follow-on, what is then the relation between OC and Controlling Area? I am looking for a plain English explanation that I can also use for teaching purposes.
Thank you in advance for reading!
Regards,
Gerhard

Hi Gerhard,
I hope my reply is not too late.
I agree with you. Profitability analysis is typically done at a detailed level - by market segments, which may be defined by geographical segments, customer groupings, product groupings, salesforce grouping, etc. CO-PA does support profitability analysis at such detailed levels.
After defining an operating concern and activating it, the system generates a series of database tables for the operating concern. I took a screenshot of the (partial) structure of the "master" table for the global GBI operating concern, GL00, from the GBI 2.2 system I am using, below:
As you can see, with such a table structure, CO-PA is capable of capturing profitability information at a very detailed level for reporting and analysis.
You may also notice that operating concern is not a field in the table. The reason is, the entire table (as well as its related tables in the same series) is used only for operating concern GL00. Its name is even hard-coded in the last 4 characters of the names of these tables. When CO-PA reports are executed in SAP ECC, they retrieve data from only one series of tables, i.e., only data of only one operating concern can be reported.
Back to your question: Why is there only one operating concern and not two? The wisdom of defining one global operating concern is that profitability data of both controlling areas (Europe and North America) will be updated into the same series of database tables and reported together. If there had been two separate operating concerns for the two controlling areas, there would have been two series of database tables, making profitability analysis across the two areas difficult, if not impossible.
Let me know if you need further clarifications.

Technical Design Review Question: Operating Concern.

Similar Messages

Maybe you are looking for