Dimension maintenance

I have a database1 having schema 1 where we have all dimensions data and also a databaase2 having schema 2 where we have stg and fct tables.In stage table data ,dimension values are populated as code.From moving to stg to fct we need to populate skey.Currently we are pulling only required dimension value from schema1 while moving to stg to fct and keep seperate dimension tables in schema2 with skey and these skeys are used in fct. Is it a right process or what would be the best approach for this?.Keeping dimenasion in both schema1 and schema2 is good and pull only required data from schema1 to schema2 is a good process?
Please suggest

Is this a question of general data warehousing design or are you using your tables to populate an OLAP cube?

Similar Messages

SQL Procedures for dimension maintenance?

I can't seem to find any stored procedures for refreshing dimensions & measures in 10.2. Looking at version 10.1 of the OLAP reference lists procedures such as:
execute dbms_awm.refresh_awdimension ('MYSCHEMA', 'MYAW', 'AW_PROD');Is there an equivalent in 10.2.0.3? The OLAP reference docs have changed quite significantly from 10.1 to 10.2, so I'd assume so too has the database and the methods it uses to refresh structure. Docs for 10.2 don't appear to mention refreshing structure anywhere.
Can anyone point me in the right direction? We're essentially looking for the same functionality as is provided in AWM's Maintain Dimension/Measure wizards, only called from our own application.
Thanks,
Aaron

Hi,
Have you tried having AWM creating a maintenance script for you?
In the end of the maintenance wizard theres an option for selecting "create to script" or something similar.
This will generate an anonymous PL/SQL block you can put into whatever procedure or application you want as long as it can run PL/SQL.
Ragnar

Resource dimension maintenance error

Hello Experts,
We have to maintain capacity of the vehicle for a variety of products. The company has a wide list with mix of goods which has different units of measure for them.
There is no one unit of measure to calculate the load of the vehicle. So we decided to maintain one unit of measure for the vehicle resource (in terms of % percentage) and maintain the conversion factor for each product in additional units of measure tab of APO. This was the idea to calculate the capacity of the vehicle for mixed loads & full loads.
So in vehicle resource master apart from MASS (kg) we maintained PROPOR ( proportion for %) the system complained that "Dimension PROPOR does not exist in dimension table for SAP liveCache".
Is there a way to maintain proportion in resource master or can you suggest another way to measure the vehicle load for the wide variety of materials.
Thanking you in anticipation.
Regards,
Vasudevan

Hello Jennsen,
There is a chance it is a data corruption issue. Have you found the root cause already?
Best regards,
Alex.

Error while populating Dimension

I am unable to populate the dimension I am getting the below error message
INI: XOQ-01711: Aggregation path for hierarchies on a dimension "ACCOUNT" is inconsistent, Generic at TxsOqStdFormCommand::execute
I am creating a Account Dim with the following hierarchy and Levels
All_Accounts
Account_Type
Account_Group
Account_no
Regards
Ishaq

Please find the details of the dimension
Environment Details :- AWM (11.1.0.7 B).
Data Base 11.1.0.7
Details Regarding the Dimension
Cost Center Dim
Levels
ALL_Cost_centers
Cost_Center_Group
Cost_Center_Sub_Group
Cost_Center
Hierarchy
Cost_Center_Hier
ALL_Cost_centers
Cost_Center_Group
Cost_Center_Sub_Group
Cost_Center
Cost center Attribute created and last level is checked (the lowest level)
Attribute Mappings
Hierarchy
Account_Hier
All_Cost_Centers
Member --> 'ALL_COST_CENTERS'
Long Desc --> 'All Cost Centers'
Short Desc --> 'All Cost Centers'
Cost_Center_Group
Member --> Cost_Center_Dim.Code_B_Group
Long Desc --> Cost_Center_Dim.Code_B_Group
Short Desc --> Cost_Center_Dim.Code_B_Group
Cost_Center_Sub_Group
Member --> Cost_Center_Dim.Code_B_Sub_Group
Long Desc --> Cost_Center_Dim.Code_B_Sub_Group
Short Desc --> Cost_Center_Dim.Code_B_Sub_Group
Cost_Center_No
Member --> Cost_Center_Dim.Cost_B_Key
Long Desc --> Cost_Center_Dim.Code_B_Descrip
Short Desc --> Cost_Center_Dim.Code_B_Descrip
Cost_Center_No --> Cost_Center_Dim.Code_B
Code_B Table Data
CODE_B_GROUP CODE_B_SUB_GROUP CODE_B_KEY CODE_B CODE_B_DESCRIP
PRODUCTION 1 C0010 PRODUCTION
PRODUCTION PRODUCTION 2 C0011 PROCESS/RECOMBINING
PRODUCTION ENGINEERING 11 C0020 ENGINEERING
PRODUCTION MATERIAL MANAGET 20 C0030 MATERIAL MANAGEMEN
SALES 27 C0050 SALES & DISTRIBUTION
SALES SALES 28 C0055 SALES
SALES SALES 29 C0056 SALES & MARKETING - GENERAL - H/O
SALES MARKETING 33 C0060 MARKETING
FINANCE 40 C0080 FINANCE & ADMINISTRATION
FINANCE ADMINISTRATION 44 C0100 ADMINISTRATION
FINANCE IT 51 C0110 INFORMATION TECHNOLOGY (IT)
I have also checked metalink it points to the below bug 7606712 - DIMENSION MAINTENANCE ERRORS OUT WITH MULTIPLE HIERARCHIES UNDER 11G

FAST refresh not working for Cube & Dimensions in AWM

Hi,
My doubt is regarding refreshing cube/dimension using FAST refresh method in AWM
1     My dimension (MVIEW refresh enabled in AWM) is refreshed without an error when I pass the refresh method parameter as *'F'* in DBMS_CUBE.BUILD() script, although there is no MVIEW log present on the dim table.
     In ALL_MVIEWS.LAST_REFRESH_TYPE, a *'COMPLETE'* refresh is logged.
2. My CUBE doesn't allow to select refresh_type=FAST when there is no MVIEW log built.
     The same CUBE (MVIEW refresh enabled, refresh_type=FAST in AWM) throws following error even when I create Mview logs for all fact and dimension tables in the DB.
java.lang.NullPointerException
at oracle.olap.awm.dataobject.DatabaseDO.commitOLAPI(Unknown Source)
at oracle.olap.awm.dataobject.aw.WorkspaceDO.commitOLAPI(Unknown Source)
at oracle.olap.awm.dataobject.olapi.UModelDO.commitOLAPI(Unknown Source)
at oracle.olap.awm.dataobject.olapi.UModelDO.update(Unknown Source)
at oracle.olap.awm.dataobject.olapi.UCubeDO.update(Unknown Source)
at oracle.olap.awm.dataobject.dialog.PropertyViewer.doApplyAction(Unknown Source)
at oracle.olap.awm.dataobject.dialog.PropertyViewer$1ApplyThread.run(Unknown Source)
If I continue with this error, CUBE mview vanishes from the DB.
Please help - How to do a FAST refresh for CUBE and Dimensions.
Edited by: 861346 on May 26, 2011 12:12 AM
Edited by: 861346 on May 26, 2011 12:13 AM
Edited by: 861346 on May 26, 2011 12:14 AM

If your object is to process the cube as quickly as possible, MV refresh of the cube is probably not required. As an alternative, you can do the following:
- Map the cube to a view and use a filter control what data is presented to the cube during a refresh.
- Avoid dimension maintenance (adding new members, dropping members, changing parent-child relationships).
Let's say you update your cube daily with sales data coming from 10,000 stores. You could add a LAST_UPDATED column to the source fact table, timestamp rows whenever the fact table is updated and then filter on that column in a view to present only the new or changed records to the cube (or whatever filtering scheme you might like).
Dimensions are always entirely processed (compiled) regardless of what data is presented to them, so there isn't any advantage to timestamping the records in the dimension table and filtering on them. What is important to understand is that any change to a hierarchy (adding members, deleting members, changing parentage) will trigger re-aggregation of the cube. If you can batch those changes periodically you can limit how much of the cube is processed during a refresh.
Continuing with the example of the daily update of the sales cube, we can examine two scenarios. In both cases, the cube is partitioned by month and a fact view filters for only the new or updated fact records (let's say there are new records every day).
Scenario 1
New records are added to the sales fact table and new stores are added to the store dimension table each day. The store dimension will be updated with new stores, new records will be loaded from the fact table and all partitions will be processed (loaded and solved/aggregated).
Scenario 2
New records are added to the fact table, but new stores loaded into the store dimension only once a week (e.g., Saturday). The fact view filters for only new or changed records and stores that currently exist in the store dimension. For Sunday through Friday, new or changed records will be loaded from the fact table and only those partitions in the cube that have new or updated data will be solved / aggregated. (If there are no changes to hierarchies and no records are loaded into a partition, that partition is not solved / aggregated). On Saturday, new stores are added to the store dimension table and the store dimension and the cube are updated. Because the store dimension has changed, all partitions of the will be processed.
With scenario 1, data for new stores are available each day but the entire cube might be solved each day (if there are new stores). In scenario two, new stores are not available until Saturday but the processing of the cube will be limited to only those partitions where there is new fact data.

ASO Dimension building slow

Hi all,
We just switched from BSO cubes to ASO cubes and found that building complete dimensions (parent child) takes much longer than building BSO dimensions.
We use the same loadrules as we used for the BSO cubes.
Is this normal?
Is there any way to speed up the dimension building?
Your help is much appreciated!
rgds,
Rudy

Thanks very much guys,
this info will definitely help us come to an optimized approach.
btw, since rebuilding all dimension in BSO wasn't any problem I'll now also spend some thoughts on rebuilding only those dimensions that have actually changed.
No reason to rebuild if nothing has changed, right...<@Cameron,
We went for this approach because we don't want the business users to manually change the outline.
So we created an dimension maintenance GUI on a sql table that can be maintained by the business users. That way we're able to load all dimension from sql.
It has its downside when it comes to e.g. member formulas, but as this more of an administrator task, it's no problem, as we're able to set which dimension should be fully rebuild/resorted.
Now we have one ODI scenario that's able to load to any essbase cube (ASO and BSO), fully parameterized. IT definitely works great!

ESSBASE Aggregation Issue.

Hi,
I am facing a serious problem with Essbase. Iam implementing Hyperion Planning 11.1.2.2 for one of our client and first time I am implementing this version.
The aggregation is not working in my setup. I have written a rule to aggregate the hierarchy. I have tried with AGG, CALC DIM, etc. But still the same issue.
I have also tried running the Calculate web form rule file, but still aggregation is not happening.
I have also noticed that in Planning Dimension maintenance, even the level 0 members showing the consolidation operation.
Any body has clue?
Please help me as I am unable to proceed further.
Thanks in Advance.
Regards,
Sunil.

It is probably worth testing your script as a calc script and then run it directly against the essbase database using EAS, then check the data with Smart View, this process should eliminate any issues in planning or calc manager.
If you are still having problems then post your script and I am sure somebody will give you some further advice.
Cheers
John
http://john-goodwin.blogspot.com/

Question in Oracle Financial Anaylzer (Please help)

Can anyone of you point to where documentation for Application Programming Interface is for Oracle . Financial Analyzer (v6).
I am having difficulty in understanding functions used for maintaining Structures like Dimension Maintenance, Dimension Value Maintenance and Financial Data Item Maintenance. Functions used are: ofa_create_dim(), ofa_del_dmv(), DIST.DFN.MEMBER().
Please assist.

Danny,
Type inheritance is a prerequisite for table inheritance. Once
you have created a type hierarchy, then you can build an
instance hierarchy (i.e., view or table) from this type
hierarchy.
What are you trying to accomplish with table inheritance in
Oracle8? Are you adding columns in subtables? Without
inheritance support in Oracle8, the workarounds documented will
let you use object views to simulate inheritance.
Regards,
Geoff
when I finally dcyphered that url itturns out to be
http://otn.oracle.com/docs/products/oracle8i/doc_library/817_doc
appdev.817/a76976/adobjdes.htm#449267
anyway ..
that stuff is on Type iheritance workaround? I need TABLE
inheritance workarounds .. or is it implied that the same type
inheritance workaround can be used for the Table inheritance
workaround?
cheers
Danny

ISO codes for Units of Measure

are the iso codes held in the uom the standard codes? are these sap standard or can these be amended to what is being output and received by the business for EDI?

Hi Smith,
Go through the below explanation, which would be helpful for you.
Check units of measurement
In applications you often have to make calculations with quantities and physical units. Units of measurement are needed for their screen display and for internal conversions (such as kilogram <-> gram, but also centimeter <-> inch). The international system of units (SI) is used for this.
The international system of units is based on seven basic units of measurement. All other units are derived from these basic units. Units of measurement that measure the same quantity (and can therefore be converted into each other) are included in a dimension.
Units of measurement are held centrally in the SAP System for all applications. The conversion factors are stored in the system with a unique internal key. The external display specifications are maintained for each unit of measurement language-dependently. A business key (3 characters) and a technical key (6 characters) should be maintained for each language.
Standard settings
In the standard delivery system, units of measurement are defined according to the international system of units (SI).
For a new installation, units of measurement are delivered in all clients. For upgrades, new units of measuremente are delivered only in Client 000. They then still have to be transported to the production clients.
Recommendation
If you intend to perform cross-company data exchange, note that units of measurement with company-specific characteristics may have an adverse effect.
Activities
Check that the dimensions delivered and the associated units of measurements are complete.
If you are using EDI, you should also check the ISO codes.
Dimensions
1. Call the maintenance transaction by double-clicking with the mouse on the Execute symbol.
2. On the initial screen of the maintenance transaction, call the function Dimensions
To get a definition of a dimension, place the cursor on the dimension and choose the function Details.
3. If required, create new dimensions with the function New entries.
Units of measurement
1. Call the maintenance transaction by double-clicking with the mouse on "Execute", or press F3 to leave dimension maintenance and return to the initial screen of the maintenance transaction.
2. Select - from F4 Help for the field next to the Units of Measurement function - the individiual dimensions, and choose the Units of Measurement function.
To get a definition of a unit of measurement, position the cursor on the unit of measurement and choose the function Details.
3. If required, define new units of measurement according to the international system of units (SI) with the menu function Unit of meaurement -> Create.
Here you have to make make specifications for:
Display (including a descriptive Units of measurement text)
Conversion (not applicable to units of measurement without dimensions)
Data exchange (EDI) (optional)
Application parameters
ISO codes
1. Call the maintenance transaction by double-clicking with the mouse on "Execute", or press F3 to leave maintenance of units of measurement or dimensions and return to the initial screen of the transaction.
2. Choose the function ISO codes.
3. If required, maintain new ISO codes with the function New entries.
Hope this helps.
Thanks,
Viswanath

Issue in loading Vendor Hierarchy in BPC 7.5 in NW version

Hi Gurus,
I am using BPC NW version 7.5.
I am automating vendor master data for loading Ids in BPC dimension.
My BI infoobject (0Vendor) has no Hierarchy.It has only Member ids.Business Requirement is to populate Hierarchy as Defaulf as ALLVENDOR.
By using the DM in BPC i loaded Member ID sucessfully in the BPC Dimension.
Please guide me with steps for populating Hierarchy as Default (ALLVENDORS) in the Parent1 column in BPC dimension.
Thanks In advance.
Mahesh

Scott,
Mapping the hierarchy in the transformation file via PARENTH1=*NEWCOL(ALLVENDORS) gives an error message 'Hierarchy is not allowed to be created by mapping PARENTH1'. So I think the only way of maintaining default PARENTH1 values - besides loading from a hierarchy - is to populate it via the Excel BPC dimension maintenance. Which can be cumbersome, specifically if a lot of new members get added frequently to a dimension and the dimension sheet each time needs to be manually updated. The only other way I can think of is to create an ENDROUTINE BADI for this which I am not sure if it allows to populate PARENTH1.
Regards,
Lars

Managing AW

HI,
We are using Oracle 10g release 2. The AW size is 50GB. On a regular basis we need to completly rebuild the AW. The comple rebuild takes around 6-7 hours. we cannot afford to bring the AW offline for so long. Is there any way in whci we can rebuild the AW parallal in othe Db or schem etc and that quickly replace the new AW with the OLD one. mind you that the existing workbooks etc of old AW should continue to work seamlessly
Thanks for the support

This is interesting. The problem here will be ensuring all the workbooks continue to function and this complicated by the way the metadata is stored - it contains the schema name so you cannot easily build the new AW in a new schema and switch the users to this new schema.
I think you have the following options:
1) Build the AW in a separate schema, isolate the changed values within the cubes, export to EIF file and import into the existing AW schema. You will have to check the import times to see if this is acceptable
2) Perform dimension maintenance on the production AW (this step should be quick and could be performed while other users are connected). In a separate AW (may be even in the same instance) update the shadow AW (dimensions and cubes). When ready to update the production AW attach both AWs together and transfer the cube data from one shadow to the production AW using OLAP DML to manage the process. The shadow AW will need to have different object names to prevent schema clashes.
3) Create the AW in separate database in the same schema as the production AW. When ready to move the AW, use transportable tablespaces to move the AW to the production instance.
4) Create the AW in separate database in the same schema as the production AW. When ready to move the AW, use data pump to move the AW to the production instance.
Trying to resolve this problem I think you are likely to run into an existing OLAP bug (with options 2 and 3) where restored AWs are not recognised in the SYS schema tables although the AW$xxx object is correctly located in the user schema. I will have to do some research to see if there is a workaround for this issue.
Obviously as you transition from the old AW to the new AW you would need to disconnect all the users.
Does that help?
Keith

X12 Transaction Sets Supported

Hi all ,
Can you tell me all the transaction ( message type ) will be for x12 ? where in EDIFACT we will have orders01, cremas etc
Thanks
Manju

Hi,
<b>Type
Description
100 Insurance Plan Description
101 Name and Address Lists
102 Associated Data
103 Abandoned Property Filings
104 Air Shipment Information
105 Business Entity Filings
106 Motor Carrier Rate Proposal
107 Request for Motor Carrier Rate Proposal
108 Response to a Motor Carrier Rate Proposal
109 Vessel Content Details
110 Air Freight Details and Invoice
111 Individual Insurance Policy and Client Information
112 Property Damage Report
113 Election Campaign and Lobbyist Reporting
120 Vehicle Shipping Order
121 Vehicle Service
124 Vehicle Damage
125 Multilevel Railcar Load Details
126 Vehicle Application Advice
127 Vehicle Baying Order
128 Dealer Information
129 Vehicle Carrier Rate Update
130 Student Educational Record (Transcript)
131 Student Educational Record (Transcript) Acknowledgment
132 Human Resource Information
133 Educational Institution Record
135 Student Aid Origination Record
138 Educational Testing and Prospect Request and Report
139 Student Loan Guarantee Result
140 Product Registration
141 Product Service Claim Response
142 Product Service Claim
143 Product Service Notification
144 Student Loan Transfer and Status Verification
146 Request for Student Educational Record (Transcript)
147 Response to Request for Student Educational Record (Transcript)
148 Report of Injury, Illness or Incident
149 Notice of Tax Adjustment or Assessment
150 Tax Rate Notification
151 Electronic Filing of Tax Return Data Acknowledgment
152 Statistical Government Information
153 Unemployment Insurance Tax Claim or Charge Information
154 Secured Interest Filing
155 Business Credit Report
157 Notice of Power of Attorney
158 Tax Jurisdiction Sourcing
159 Motion Picture Booking Confirmation
160 Transportation Automatic Equipment Identification
161 Train Sheet
163 Transportation Appointment Schedule Information
170 Revenue Receipts Statement
175 Court and Law Enforcement Notice
176 Court Submission
179 Environmental Compliance Reporting
180 Return Merchandise Authorization and Notification
185 Royalty Regulatory Report
186 Insurance Underwriting Requirements Reporting
187 Premium Audit Request and Return
188 Educational Course Inventory
189 Application for Admission to Educational Institutions
190 Student Enrollment Verification
191 Student Loan Pre-Claims and Claims
194 Grant or Assistance Application
195 Federal Communications Commission (FCC) License Application
196 Contractor Cost Data Reporting
197 Real Estate Title Evidence
198 Loan Verification Information
199 Real Estate Settlement Information
200 Mortgage Credit Report
201 Residential Loan Application
202 Secondary Mortgage Market Loan Delivery
203 Secondary Mortgage Market Investor Report
204 Motor Carrier Load Tender
205 Mortgage Note
206 Real Estate Inspection
210 Motor Carrier Freight Details and Invoice
211 Motor Carrier Bill of Lading
212 Motor Carrier Delivery Trailer Manifest
213 Motor Carrier Shipment Status Inquiry
214 Transportation Carrier Shipment Status Message
215 Motor Carrier Pickup Manifest
216 Motor Carrier Shipment Pickup Notification
217 Motor Carrier Loading and Route Guide
219 Logistics Service Request
220 Logistics Service Response
222 Cartage Work Assignment
223 Consolidators Freight Bill and Invoice
224 Motor Carrier Summary Freight Bill Manifest
225 Response to a Cartage Work Assignment
227 Trailer Usage Report
228 Equipment Inspection Report
240 Motor Carrier Package Status
242 Data Status Tracking
244 Product Source Information
245 Real Estate Tax Service Response
248 Account Assignment/Inquiry and Service/Status
249 Animal Toxicological Data
250 Purchase Order Shipment Management Document
251 Pricing Support
252 Insurance Producer Administration
255 Underwriting Information Services
256 Periodic Compensation
259 Residential Mortgage Insurance Explanation of Benefits
260 Application for Mortgage Insurance Benefits
261 Real Estate Information Request
262 Real Estate Information Report
263 Residential Mortgage Insurance Application Response
264 Mortgage Loan Default Status
265 Real Estate Title Insurance Services Order
266 Mortgage or Property Record Change Notification
267 Individual Life, Annuity and Disability Application
268 Annuity Activity
269 Health Care Benefit Coordination Verification
270 Eligibility, Coverage or Benefit Inquiry
271 Eligibility, Coverage or Benefit Information
272 Property and Casualty Loss Notification
273 Insurance/Annuity Application Status
274 Healthcare Provider Information
275 Patient Information
276 Health Care Claim Status Request
277 Health Care Information Status Notification
278 Health Care Services Review Information
280 Voter Registration Information
283 Tax or Fee Exemption Certification
284 Commercial Vehicle Safety Reports
285 Commercial Vehicle Safety and Credentials Information Exchange
286 Commercial Vehicle Credentials
288 Wage Determination
290 Cooperative Advertising Agreements
300 Reservation (Booking Request) (Ocean)
301 Confirmation (Ocean)
303 Booking Cancellation (Ocean)
304 Shipping Instructions
309 Customs Manifest
310 Freight Receipt and Invoice (Ocean)
311 Canada Customs Information
312 Arrival Notice (Ocean)
313 Shipment Status Inquiry (Ocean)
315 Status Details (Ocean)
317 Delivery/Pickup Order
319 Terminal Information
322 Terminal Operations and Intermodal Ramp Activity
323 Vessel Schedule and Itinerary (Ocean)
324 Vessel Stow Plan (Ocean)
325 Consolidation of Goods In Container
326 Consignment Summary List
350 Customs Status Information
352 U.S. Customs Carrier General Order Status
353 Customs Events Advisory Details
354 U.S. Customs Automated Manifest Archive Status
355 U.S. Customs Acceptance/Rejection
356 U.S. Customs Permit to Transfer Request
357 U.S. Customs In-Bond Information
358 Customs Consist Information
361 Carrier Interchange Agreement (Ocean)
362 Cargo Insurance Advice of Shipment
404 Rail Carrier Shipment Information
410 Rail Carrier Freight Details and Invoice
412 Trailer or Container Repair Billing
414 Rail Carhire Settlements
417 Rail Carrier Waybill Interchange
418 Rail Advance Interchange Consist
419 Advance Car Disposition
420 Car Handling Information
421 Estimated Time of Arrival and Car Scheduling
422 Equipment Order
423 Rail Industrial Switch List
424 Rail Carrier Services Settlement
425 Rail Waybill Request
426 Rail Revenue Waybill
429 Railroad Retirement Activity
431 Railroad Station Master File
432 Rail Deprescription
433 Railroad Reciprocal Switch File
434 Railroad Mark Register Update Activity
435 Standard Transportation Commodity Code Master
436 Locomotive Information
437 Railroad Junctions and Interchanges Activity
440 Shipment Weights
451 Railroad Event Report
452 Railroad Problem Log Inquiry or Advice
453 Railroad Service Commitment Advice
455 Railroad Parameter Trace Registration
456 Railroad Equipment Inquiry or Advice
460 Railroad Price Distribution Request or Response
463 Rail Rate Reply
466 Rate Request
468 Rate Docket Journal Log
470 Railroad Clearance
475 Rail Route File Maintenance
485 Ratemaking Action
486 Rate Docket Expiration
490 Rate Group Definition
492 Miscellaneous Rates
494 Rail Scale Rates
500 Medical Event Reporting
501 Vendor Performance Review
503 Pricing History
504 Clauses and Provisions
511 Requisition
517 Material Obligation Validation
521 Income or Asset Offset
527 Material Due-In and Receipt
536 Logistics Reassignment
540 Notice of Employment Status
561 Contract Abstract
567 Contract Completion Status
568 Contract Payment Management Report
601 U.S. Customs Export Shipment Information
602 Transportation Services Tender
620 Excavation Communication
625 Well Information
650 Maintenance Service Order
715 Intermodal Group Loading Plan
753 Request for Routing Instructions
754 Routing Instructions
805 Contract Pricing Proposal
806 Project Schedule Reporting
810 Invoice
811 Consolidated Service Invoice/Statement
812 Credit/Debit Adjustment
813 Electronic Filing of Tax Return Data
814 General Request, Response or Confirmation
815 Cryptographic Service Message
816 Organizational Relationships
818 Commission Sales Report
819 Joint Interest Billing and Operating Expense Statement
820 Payment Order/Remittance Advice
821 Financial Information Reporting
822 Account Analysis
823 Lockbox
824 Application Advice
826 Tax Information Exchange
827 Financial Return Notice
828 Debit Authorization
829 Payment Cancellation Request
830 Planning Schedule with Release Capability
831 Application Control Totals
832 Price/Sales Catalog
833 Mortgage Credit Report Order
834 Benefit Enrollment and Maintenance
835 Health Care Claim Payment/Advice
836 Procurement Notices
837 Health Care Claim
838 Trading Partner Profile
839 Project Cost Reporting
840 Request for Quotation
841 Specifications/Technical Information
842 Nonconformance Report
843 Response to Request for Quotation
844 Product Transfer Account Adjustment
845 Price Authorization Acknowledgment/Status
846 Inventory Inquiry/Advice
847 Material Claim
848 Material Safety Data Sheet
849 Response to Product Transfer Account Adjustment
850 Purchase Order
851 Asset Schedule
852 Product Activity Data
853 Routing and Carrier Instruction
854 Shipment Delivery Discrepancy Information
855 Purchase Order Acknowledgment
856 Ship Notice/Manifest
857 Shipment and Billing Notice
858 Shipment Information
859 Freight Invoice
860 Purchase Order Change Request - Buyer Initiated
861 Receiving Advice/Acceptance Certificate
862 Shipping Schedule
863 Report of Test Results
864 Text Message
865 Purchase Order Change Acknowledgment/Request - Seller Initiated
866 Production Sequence
867 Product Transfer and Resale Report
868 Electronic Form Structure
869 Order Status Inquiry
870 Order Status Report
872 Residential Mortgage Insurance Application
873 Commodity Movement Services
874 Commodity Movement Services Response
875 Grocery Products Purchase Order
876 Grocery Products Purchase Order Change
877 Manufacturer Coupon Family Code Structure
878 Product Authorization/De-authorization
879 Price Information
880 Grocery Products Invoice
881 Manufacturer Coupon Redemption Detail
882 Direct Store Delivery Summary Information
883 Market Development Fund Allocation
884 Market Development Fund Settlement
885 Retail Account Characteristics
886 Customer Call Reporting
887 Coupon Notification
888 Item Maintenance
889 Promotion Announcement
891 Deduction Research Report
893 Item Information Request
894 Delivery/Return Base Record
895 Delivery/Return Acknowledgment or Adjustment
896 Product Dimension Maintenance
920 Loss or Damage Claim - General Commodities
924 Loss or Damage Claim - Motor Vehicle
925 Claim Tracer
926 Claim Status Report and Tracer Reply
928 Automotive Inspection Detail
940 Warehouse Shipping Order
943 Warehouse Stock Transfer Shipment Advice
944 Warehouse Stock Transfer Receipt Advice
945 Warehouse Shipping Advice
947 Warehouse Inventory Adjustment Advice
980 Functional Group Totals
990 Response to a Load Tender
993 Secured Receipt or Acknowledgment
996 File Transfer
997 Functional Acknowledgment
998 Set Cancellation
999 Implementation Acknowledgment
</b>
Thanks
Manju

Maintenance Planning with Cycles of Different Dimensions

Hello All,
I am having trouble finding the solution for the following requirement in PLM310 "Maintenance Planning with Cycles of Different Dimensions": I am having trouble creating a maintenance strategy that can handle both time and measurement.
SImple version of the requirement: perform car maintenance every three months OR 3000 miles, whichever comes first.
I can see where SAP can handle multiple counters, but where I can mix time and performance measurements.
Thank you all for your help in advance.
Alex

Hi,
You can achive this in two ways.
1. If you have strategy only as you mentioned 3Months or 3000 miles then you can use T code IP43 Multiple counterplan.
2. Is you create cycle sets in IP11Z tcode and use them as like strategy. In this typr you can maintain different UOM.
Regards,
N.Nagaraju

Follow-up on u0093Fact Table VS. Dimension relative sizeu0094

You dont have to read the background info. below, it is only for reference. I have already gone though several links as such your touch in your own words will be much appreciated.
Can you help me understand these which came from the many links the Experts referred me .
1. For better performance: Use line item dimension where applicable, but use the "high cardinality" option with extreme care. Any clarification on high cardinality? And why with extreme care?
2. For better performance: 1. Make the Index perfect and create secondary index based on requirement.. I dont seem to follow this index issue being raised here.
Thanks.
--Background: References from these past postings ---
There is much to be said about performance in general, but I will try to answer your specific question regarding fact and dimension tables.
First of all try to compress as many requests as possible in the fact table and do that regularily.
Partition your compressed fact table physically based on for example 0CALMONTH. In the infocube maintenance, in the Extras menu, choose partitioning.
Partition your cube logically into several smaller cubes based on for example 0CALYEAR. Combine the cubes with a multiprovider.
Use constants on infocube level (Extras->Structure Specific Infoobject properties) and/or restrictions on specific cubes in your multiprovider queries if needed.
Create aggregates of subsets of your characteristics based on your query design. Use the debug option in RSRT to investigate which objects you need to include.
To investigate the size of the dimension tables, first use the test in transaction RSRV (Database Information about InfoProvider Tables). It will tell you the relative sizes of your dimensions in comparison to your fact table. Then go to transaction DB02 and conduct a detailed analysis on the large dimension tables. You can choose "table columns" in the detailed analysis screen to see the number of distinct values in each column (characteristic). You also need to understand the "business logic" behind these objects. The ones that have low cardinality, that is relate to each other shoule be located together. With this information at hand you can understand which objects contribute the most to the size of the dimension and separate the dimension.
Use line item dimension where applicable, but use the "high cardinality" option with extreme care.
Generate database statistics regularily using process chains or (if you use Oracle) schedule BRCONNECT runs using transaction DB13.
Good luck!
Kind Regards
Andreas
There are some simple things by which we can maintain the performance.
1> Make the Index perfect and create secondary index based on requirement.
2> Make statistics perfect.
3> Based on data size in dimenssion table use lineitem dimenssion.
HOpe this will help you.
Suneel

Hi Caud..
1] High Cardinality..
High Cardinality means that this dimension contains a large number of characteristic values. This information is used in accordance with the individual database platform in order to optimize performance. For example, an index type other than the standard may be used. Generally a dimension is perceived to have high cardinality when the dimension is at least 20% the size of the fact tables in terms of the number of entries each contain. Avoid marking a dimension as having high cardinality if you are in any doubt.
Cardinality creates indexes on the Dimension table entries and there by you would see an improvement in performance.
With Oracle DB, setting the Cardinality option causes a b-tree index to be built instead of a bitmap index even if it is not a line item dim.
Setting it as a Line Item dim also causes a b-tree index to be built instead of a bitmap index, but also embeds SID directly in the fact table, eliminating the dimension table.
As it changes from bit map to B-tree, u have to be careful as the SAP recommends the Bit map.
2]As indices increased the performance tremendously, u have to consider when ever the performance is main factor. it is very easy for query to access the data in the data target if it already indexed.
Refer this link..
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Hope it helps-
Regards-
MM
Assign points if it is useful, it is right way to say thanks.
Message was edited by: vishnuC

How can I manage access to dimension members in a layout?

Hello,
I have a dimension member list of materials (400) on a "material" dimension. But some people have access to one portion of the whole group and others may have access to other groups. But the materials can be shared between groups so I cannot group them in differents hierarchies.
The problem is in the layout you need to select a hierachy to show various rows (the whole group of materiales). The layout shows all the list of materials. Even if the user only have access to 10 of them. I don't know how is the best way for presenting this to the user? It should presents only the 10 rows corresponding to his materials.
One way that I found (but I don't find it acceptable because of the hard effort that represents the maintenance) is to create differents member access profiles and denied the access to each material (dimension member - 390) that the user cannot modified. Then in excel I have to run a macro that hides all the rows that have an empty description in the cell of the material name.
How can I achive this?
Is there a function in BPC to see if a user have access or not to a dimension member?
The only way to show in a layout various rows is to set in the view a hierarchy?
Thanks & Regards
SU

hi
pl. verify whether this will suit your requirements:
Material           UG1           UG2
MAT1               Y
MAT2                                 Y
MAT3               Y
MAT4                                 Y
MAT5               Y               Y
Now UG1,UG2 diff user groups and property in Material. Assignment of Y is one time job.
At the time of accessing the dimension members can restrict on the basis of UG1="Y" or UG2="Y" property
Here MAT5 is common in both UG1 and UG2
(Hardly may have 3-4 set of users: Accordingly can have UG1,UG2,UG3,UG4 etc.)
sri

Dimension maintenance

Similar Messages

Maybe you are looking for