Writing a Virtual Characteristic or Key figure

Added From Arun KK Blog sapbikk

Writing a Virtual characteristic is one which i really struggled to get on - more because of lack of material than the complexity itself.
Here, i have documented my approach to write one - hope it is a good reference for some one planning to write one.
CAUTION: Virtual char and KFs seriously impact the performance of the query; therefore use them with discretion.
---------------------------------------

Need for virtual char & KFs:

To do calculation/manipulation of char or KFs at query run-time

Walk-through:

We’ll go through the virtual char & KFs using this example.

‘Calc Date’ is an IO that holds the below logic

If Current Date > Revised Promise Date Then

Calc Date = ‘PD’

Else

Calc Date = Revised Promise Date

We shall see how this is implemented using virtual characteristics.

Step 1: Creation of dummy IO

Create a ‘dummy’ info object (without any mapping) that would be the holder for Calc Date

I created IO - ZCRPDTCLC.

Step 2: Associating IO to data target

Add this info object to the data target that would be used for reporting.

I added ZCRPDTCLC under DSO ZPP_DS06 and again to ZPU_M03 MP.

The next steps would involve writing the code for calculating Calc Date.

The code is written in 3 modules.

ZXRSRTOP - Global declaration of variables is done here

ZXRSRU02 - Mode of access for each of the IOs used in the exit is defined here.

ZXRSRZZZ - Association of the global variable to the actual IO is done here.

The exit logic is also written here.

Step 3: Global declaration of variables

Go to ZXRSRTOP module in ABAP editor (tcode se38)

In the ‘Include for Virtual Char’ block (it could be in other blocks also, code written here to make it more organized), declare global variables for Calc Date and Revised Promise Date (these are the objects that will be used in the calculation)

The global variables declared should be in the format –

g_pos__

Data type should be number.

Eg:

Data:

g_pos_ZPP_DS06_ZCRPDTCLC TYPE I,

g_pos_ZPP_DS06_ZCRPDT TYPE I.

Step 4: Defining mode of access for the IO.

Go to ZXRSRU02 module in ABAP editor (tcode se38)

There will be a single CASE block for structure i_s-rkb1d

Eg:

CASE i_s_rkb1d-infocube.

…

ENDCASE

This structure ‘i_s_rkb1d’ has all details regarding the query like query tech name, data target, etc.

Thereby, i_s_rkb1d-infocube will contain the data target for each query.

CASE i_s_rkb1d-infocube.

WHEN 'ZPP_DS06'.

* Fields to read

g_t_chanm-mode = rrke_c_mode-read.

g_t_chanm = 'ZCRPDT'.

APPEND g_t_chanm to e_t_chanm.

* Fields to write

g_t_chanm-mode = rrke_c_mode-no_selection.

g_t_chanm-chanm = 'ZCRPDTCLC'.

APPEND g_t_chanm to e_t_chanm.

ENDCASE.

We check the info cube attribute for the corresponding data target related to our query.

‘rrke_c_mode’ is the structure that defines the mode of access for each IO (read mode, write mode).

‘g_t_chanm’ is the structure that will hold the name of characteristics that will be used

‘g_t_kyfnm’ is the structure that will hold the name of key figures that will be used

In our example, we use only characteristics and hence only ‘g_t_kyfnm’ structure.

The rest of the code should be self-explanatory.

For each new object, you assign its tech name to ‘g_t_chanm_chanm’ object and append it to ‘e_t_chanm’ which is the output structure.

Similarly for key figures, ‘e_t_kyfnm’ is the output structure.However for key figures, there is no structure to set the mode of access (mode of access – read/write by default).

Another example to drive the point home:

* Characteristics and Units

g_t_chanm-mode = rrke_c_mode-read.

g_t_chanm-chanm = '0MATERIAL'. append g_t_chanm to e_t_chanm.

g_t_chanm-chanm = '0PLANT'. append g_t_chanm to e_t_chanm.

g_t_chanm-mode = rrke_c_mode-no_selection.

g_t_chanm-chanm = 'PR_ID1'. append g_t_chanm to e_t_chanm.

g_t_chanm-chanm = 'PR_ID2'. append g_t_chanm to e_t_chanm.

g_t_chanm-chanm = 'PR_YEAR1'. append g_t_chanm to e_t_chanm.

g_t_chanm-chanm = 'PR_YEAR2'. append g_t_chanm to e_t_chanm.

g_t_chanm-chanm = 'PR_CURR1'. append g_t_chanm to e_t_chanm.

g_t_chanm-chanm = 'PR_CURR2'. append g_t_chanm to e_t_chanm.

* Key Figures

append '0QUANT_B' to e_t_kyfnm.

append 'AMOUNT1' to e_t_kyfnm.

append 'AMOUNT2' to e_t_kyfnm.

For ‘g_t_kyfnm’ we need not set any mode.

Step 5: Writing the logic for virtual char/KF

Go to ZXRSRZZZ module in ABAP editor (tcode se38)

Here, create a new form for the data target being used.

Form name should be begin with ‘USER_’ followed by the data target’s name.

C_S_DATE is the structure that would hold the data in the query.

To access the IOs in the code, we have to create field symbols that act as aliases.

Then the global variables created are associated to these aliases using the ASSIGN statement.

The rest of the code involves the implementation logic as in the snippet below.

FORM USER_ZPP_DS06 USING I_S_RKB1D TYPE RSR_S_RKB1D

CHANGING C_S_DATE TYPE ANY.

DATA: L_DATE TYPE SCAL-DATE.

DATA: L_WEEK TYPE SCAL-WEEK.

CONSTANTS: PAST_DUE(2) TYPE C VALUE 'PD'.

FIELD-SYMBOLS: , .

ASSIGN COMPONENT g_pos_ZPP_DS06_ZCRPDT OF STRUCTURE C_S_DATE TO .

ASSIGN COMPONENT g_pos_ZPP_DS06_ZCRPDTCLC OF STRUCTURE C_S_DATE TO .

L_DATE = SY-DATUM. "Today's Date

CALL FUNCTION 'DATE_GET_WEEK'

EXPORTING

DATE = L_DATE

IMPORTING

WEEK = L_WEEK.

IF L_WEEK GT . "If Current Week is greater than Revised Promise Date, Calc_Date holds "PD"

= PAST_DUE.

ELSE. "Calc_Date holds Revised Promise Date

= .

ENDIF.

ENDFORM.

Overall Program Flow for Calc Date

ZXRSRTOP

Data:

g_pos_ZPP_DS06_ZCRPDTCLC TYPE I,

g_pos_ZPP_DS06_ZCRPDT TYPE I.

ZXRSRU02

CASE i_s_rkb1d-infocube.

WHEN 'ZPP_DS06'.

* Fields to read

g_t_chanm-mode = rrke_c_mode-read.

g_t_chanm = 'ZCRPDT'.

APPEND g_t_chanm to e_t_chanm.

* Fields to write

g_t_chanm-mode = rrke_c_mode-no_selection.

g_t_chanm-chanm = 'ZCRPDTCLC'.

APPEND g_t_chanm to e_t_chanm.

ENDCASE.

ZXRSRZZZ

FORM USER_ZPP_DS06 USING I_S_RKB1D TYPE RSR_S_RKB1D

CHANGING C_S_DATE TYPE ANY.

DATA: L_DATE TYPE SCAL-DATE.

DATA: L_WEEK TYPE SCAL-WEEK.

CONSTANTS: PAST_DUE(2) TYPE C VALUE 'PD'.

FIELD-SYMBOLS: , .

ASSIGN COMPONENT g_pos_ZPP_DS06_ZCRPDT OF STRUCTURE C_S_DATE TO .

ASSIGN COMPONENT g_pos_ZPP_DS06_ZCRPDTCLC OF STRUCTURE C_S_DATE TO .

L_DATE = SY-DATUM. "Today's Date

CALL FUNCTION 'DATE_GET_WEEK'

EXPORTING

DATE = L_DATE

IMPORTING

WEEK = L_WEEK.

IF L_WEEK GT . "If Current Week is greater than Revised Promise Date, Calc_Date holds "PD"

= PAST_DUE.

ELSE. "Calc_Date holds Revised Promise Date

= .

ENDIF.

ENDFORM.

Constant selection in query (Apples and Oranges)

Added From Sven van Leuken’s Blog

The great thing about an infoset is that it can combine data from different sources via a "JOIN" (inner/outer) mechanism. This may come in very handy if you want to report on two different sources (apples & oranges) without having to show the annoying '#'.
But what to do if you want to show data from the Apples bucket, even though this bucket is empty for the corresponding Oranges bucket? (and vice versa)
Eg.
Apples: 10 pieces in January 2010 for customer A
Oranges: 5 pieces in January 2010 for customer B
With an infoset (JOIN) on Apples & Oranges (where Apples is 'leading') it is impossible to show the Oranges of January for customer B because Apples has no customer B entry.
To be able to show the Oranges data, you have to use a multiprovider which uses the UNION mechanism. The downside of the multiprovider is that it will show a # for January Oranges for Customer A and a # for January Apples for Customer B.
This unwanted # behaviour can be overruled by using constant selection
Step 1: Create restricted keyfigure

Step 2: Tick on constant selection

Without constant selection:
January 2010;Customer A; Apples 10; Oranges #
January 2010;Customer B; Apples #; Oranges 5
With constant selection:
January 2010;Customer A; Apples 10; Oranges 5
January 2010;Customer B; Apples 10; Oranges 5

LO COCKPIT - V3 update: Questions and answers

Added By Vinay

Question 1
Update records are written to the SM13, although you do not use the extractors from the logistics cockpit (LBWE) at all.
Active datasources have been accidentally delivered in a PI patch.For that reason, extract structures are set to active in the logistics cockpit. Select transaction LBWE and deactivate the active structures. From now on, no additional records are written into SM13.
If the system displays update records for application 05 (QM) in transaction SM13, even though the structure is not active, see note 393306 for a solution.

Question 2
How can I selectively delete update records from SM13?
Start the report RSM13005 for the respective module (z.B. MCEX_UPDATE_03).

• Status COL_RUN INIT: without Delete_Flag but with VB_Flag (records are updated).
• Status COL_RUN OK: with Delete_Flag (the records are deleted for all modules with COL_RUN -- OK)

With the IN_VB flag, data are only deleted, if there is no delta initialization. Otherwise, the records are updated. MAXFBS : The number of processed records without Commit.

ATTENTION: The delta records are deleted irrevocably after executing report RSM13005 (without flag IN_VB). You can reload the data into BW only with a new delta-initialization!
Question 3
What can I do when the V3 update loops?
Refer to Note 0352389. If you need a fast solution, simply delete all entries from SM13 (executed for V2), however, this does not solve the actual problem.
ATTENTION: THIS CAUSES DATA LOSS. See question 2 !
Question 4
Why has SM13 not been emptied even though I have started the V3 update?

• The update record in SM13 contains several modules (for example, MCEX_UPDATE_11 and MCEX_UPDATE_12). If you start the V3 update only for one module, then the other module still has INIT status in SM13 and is waiting for the corresponding collective run. In some cases, the entry might also not be deleted if the V3 update has been started for the second module.In this case, schedule the request RSM13005 with the DELETE_FLAG (see question 2).
• V3 updating no longer functions after the PI upgrade because you did not load all the delta records into the BW system prior to the upgrade.Proceed as described in note 328181.

Question 5
The entries from SM13 have not been retrieved even though I followed note 0328181!
Check whether all entries were actually deleted from SM13 for all clients. Look for records within the last 25 years with user * .
Question 6
Can I schedule V3 update in parallel?
The V3 update already uses collective processing.You cannot do this in parallel.

Question 7
The Logistics Cockpit extractors deliver incorrect numbers. The update contains errors !
Have you installed the most up-to-date PI in your OLTP system?
You should have at least PI 2000.1 patch 6 or PI 2000.2 patch 2.

Question 8
Why has no data been written into the delta queue even though the V3 update was executed successfully?
You have probably not started a delta initialization. You have to start a delta initialization for each DataSource from the BW system before you can load the delta.Check in RSA7 for an entry with a green status for the required DataSource. Refer also to Note 0380078.

Question 9
Why does the system write data into the delta queue, even though the V3 update has not been started?
You are using the automatic goods receipt posting (transaction MRRS) and start this in the background.In this case the system writes the records for DataSources of application 02 directly into the delta queue (RSA7).This does not cause double data records.This does not result in any inconsistencies.

Question 10
Why am I not able to carry out a structural change in the Logistics Cockpit although SM13 is blank?
Inconsistencies occurred in your system. There are records in update table VBMOD for which there are no entries in table VBHDR. Due to those missing records, there are no entries in SM13. To remove the inconsistencies, follow the instructions in the solution part of Note 67014. Please note that no postings must be made in the system during reorganization in any case!

Question 11
Why is it impossible to plan a V3 job from the Logistics Cockpit?
The job always abends immediately. Due to missing authorizations, the update job cannot be planned. For further information see Note 445620.
Posted by Vinay

How to Restore Query into Older Version

 

• Added by Mahesh Kumar, last edited by Arun Varadarajan

Once older verion (3.x) queries are migrated into latest version (7.0).Query can be restored to 3.x after migration. The backup for any query created in 3.x will be taken when first opened for editing in 7.0 Query Designer. The backup contains the last change done to the query using 3.x editor, any changes done in 7.0 Query Designer will be lost on restore. Also the query originally created in 7.0 can not be restored to older versions as there is no Backup in 3.x.

   Queries can be restored to 3.x version using program COMPONENT_RESTORE.

Steps followed for Restoring Query with 3.x versions:

Step 1 : Execute "COMPONENT_RESTORE" program in SE38.

Step 2 :   Next screen Select InfoProvider and component type. Different component types are available like

Step 3 : Select REP as a component type to revert back Query.  


Step 4 :  Execute (F8). In the next screen it will displays all related Queries for that particular infoprovider.

Step 5 : Search for the query which you want to revert back to older versions.

Step 6 : Then say transfer selection. below message will appears in the system.

Technorati Tags: SAP BI INTERVIEW QUESTIONS,SAP BI,BI Reporting,BI QUERIES

Step 7 : Once we select Yes, Query successfully restored into older versions.

The below 25 points are the small tips to increase your query performance. You can use them as a checklist while creating a Query. Here it goes..

1. If exclusions exist, make sure they exist in the global filter area. Try to remove exclusions by subtracting out inclusions.
2. Use Constant Selection to ignore filters in order to move more filters to the global filter area. (Use ABAPer to test and validate that this ensures better code)
3. Within structures, make sure the filter order exists with the highest level filter first.
4. Check code for all exit variables used in a report.
5. Move Time restrictions to a global filter whenever possible.
6. Within structures, use user exit variables to calculate things like QTD, YTD. This should generate better code than using overlapping restrictions to achieve the same thing. (Use ABAPer to test and validate that this ensures better code).
7. When queries are written on multiproviders, restrict to InfoProvider in global filter whenever possible. MultiProvider (MultiCube) queries require additional database table joins to read data compared to those queries against standard InfoCubes (InfoProviders), and you should therefore hardcode the infoprovider in the global filter whenever possible to eliminate this problem.
8. Move all global calculated and restricted key figures to local as to analyze any filters that can be removed and moved to the global definition in a query. Then you can change the calculated key figure and go back to utilizing the global calculated key figure if desired
9. If Alternative UOM solution is used, turn off query cache.
10. Set read mode of query based on static or dynamic. Reading data during navigation minimizes the impact on the R/3 database and application server resources because only data that the user requires will be retrieved. For queries involving large hierarchies with many nodes, it would be wise to select Read data during navigation and when expanding the hierarchy option to avoid reading data for the hierarchy nodes that are not expanded. Reserve the Read all data mode for special queries---for instance, when a majority of the users need a given query to slice and dice against all dimensions, or when the data is needed for data mining. This mode places heavy demand on database and memory resources and might impact other SAP BW processes and tasks.
11. Turn off formatting and results rows to minimize Frontend time whenever possible.
12. Check for nested hierarchies. Always a bad idea.
13. If "Display as hierarchy" is being used, look for other options to remove it to increase performance.
14. Use Constant Selection instead of SUMCT and SUMGT within formulas.
15. Do review of order of restrictions in formulas. Do as many restrictions as you can before calculations. Try to avoid calculations before restrictions.
16. Check Sequential vs Parallel read on Multiproviders.
17. Turn off warning messages on queries.
18. Check to see if performance improves by removing text display (Use ABAPer to test and validate that this ensures better code).
19. Check to see where currency conversions are happening if they are used.
20. Check aggregation and exception aggregation on calculated key figures. Before aggregation is generally slower and should not be used unless explicitly needed.
21. Avoid Cell Editor use if at all possible.
22. Make sure queries are regenerated in production using RSRT after changes to statistics, consistency changes, or aggregates.
23. Within the free characteristics, filter on the least granular objects first and make sure those come first in the order.
24. Leverage characteristics or navigational attributes rather than hierarchies. Using a hierarchy requires reading temporary hierarchy tables and creates additional overhead compared to characteristics and navigational attributes. Therefore, characteristics or navigational attributes result in significantly better query performance than hierarchies, especially as the size of the hierarchy (e.g., the number of nodes and levels) and the complexity of the selection criteria increase.
25. If hierarchies are used, minimize the number of nodes to include in the query results. Including all nodes in the query results (even the ones that are not needed or blank) slows down the query processing. The "not assigned" nodes in the hierarchy should be filtered out, and you should use a variable to reduce the number of hierarchy nodes selected.

Copying Queries between InfoCubes

By Debasish BI EXPERT

You can use this function to copy queries and their sub-objects (structures, calculated key figures and restricted key figures) between different InfoCubes.

The target InfoCube, the InfoCube for the query copies, must contain all the InfoObjects of the source InfoCube (InfoCube of the original queries).

Procedure...
1. In the SAP Easy Access Menu of the BI system, choose SAP Menu  Business Explorer  Query  Copy. Double-click on Copy Queries. The Copying Queries between InfoCubes dialog box appears.
2. Select the required source and target InfoCube.
3. Choose Continue. A selection box appears that contains all the queries of the source InfoCube.
4. Select a query from those available.

You have the following options for selecting multiple queries.
• To make several selections from the list, select the required queries with a mouse click and the Ctrl key.
• If you want to select several queries that are next to each other in the list, you can select whole blocks by holding down the Shift key.

5. Choose Transfer Selections.

Note the following if you are working with reusable sub objects such as variables, structures, calculated key figures and restricted key figures:

• Variables are not dependent on InfoCubes so they are not copied.
• If you select more than one query to be copied and these queries reference reusable sub objects that are next to each other in the list, the system only makes one copy of the sub object. The references of the copied queries are retained.
• If you copy queries again at a later time, the system creates new sub objects. The references to queries that have already been copied are lost.

6. Change the technical names of any copied query components in dialog box Rename Components.

7. Choose Continue.
Result:
The copied queries and the copied sub objects have their own names. The new names are derived from the name of the original object and the added element _.

This does not affect variables, since they are not copied.

Example:

The queries weekly report, monthly report and annual report use company code as a variable and the calculated key figure contribution margin. If you copy the queries weekly report and monthly report into another InfoCube, the queries weekly report_1 and monthly report_1 are created along with the calculated key figure contribution margin_1. The new queries refer to the new key figure contribution margin_1 and the variable company code.
If you copy queries quarterly report and annual report, a new calculated key figure, contribution margin_2, has to be created as a copy of contribution margin. Quarterly report_1 and annual report_1 then refer to contribution margin_2 and not contribution margin_1. Company code is still used as a variable.

Major benefits of SAP NetWeaver BW 7.3 are:

Major benefits of SAP NetWeaver BW 7.3 are:

Enhanced Scalability & Performance for faster decision making
􀂄 Remarkably accelerated data loads
􀂄 Next level of performance for BW Accelerator
􀂄 Teradata supported as additional database for SAP NetWeaver BW


Increased flexibility by further integration of SAP BusinessObjects BI and EIM tools
􀂄 Tighter integration with SAP BusinessObjects Data Services
􀂄 Tighter Integration with SAP BusinessObjects Metadata Management


Reduced TCO and higher development efficiency
􀂄 Automated data flow design tools
􀂄 Graphical data modeling and best practice data modeling patterns


Simplified configuration and operations
􀂄 Admin Cockpit integrated into SAP Solution Manager
􀂄 Wizard based system configuration

All SAP Standard Reports

No	Broad level Report	Options available for report execution	Tcode	Remarks	Used by	Report area
1	Purhase order analysis	By delivey schedule	ME80FN	This report can be used for displaying the information of purchase orders created and the transactions that has taken place.	Purchase	Purchase
		By purchase order details
		By purchase order hostory
2	Purchase order display	By supplier	ME2L	Facility available to restrict the viewing based on the status of PO viz. Partly received,	Purchase	Purchase
		By material	ME2M	Closed, No GR made
		By buyer		Bill passing not done , etc.
		By plant
3	Anlysis of order values	By Material	ME81N	Totals analysis	Purchase & Finance	Purchase
		By buyer		ABC analysis
		By supplier		Analysis using comparison period
				Frequency analysis
4	Goods receipt forecast	By purchase order	ME2V	Number of anticipated deliveries	Pruchase & Stores	Purchase
		By vendorwise
		By material wise
5	Stock lying with subcontractors	By Supplier	ME2O	Can be useful in deciding which component is to be given to supplier if the procurement is on subcontracting basis. It also helps in giving the visibility of stocks lying at subcontractor.	Pruchase & Stores	Purchase
		By material
6	Monitor supplier confirmation	By Supplier	ME2A	This program is useful especially for imported purchase orders or such cases where the lead time of procurement is very high.	Purchase & planning	Purchase
		By buyer
7	Purchase analysis	By buyer	MCE1	This program will give you information on purchase value, invoice value during a selected period. However for these reports it is necessary to update the relevant LIS structure.	Purchase Executives	Purchase
		By Material	MCE3
		By commodity type	MCE5
		By supplier	MCE7
			MCE8
8	Long term planning analysis	By supplier	MCEA	This report can be used for Purchase budget requirement. However for this report to work, long term planning functionality should be put in use.	Purchase Executives	Purchase
		By material	MCEB
		By commodity type	MCEC
9	Material document listing	By Material	MB51	This report provides you with a list of the material documents which  were posted for one or more materials.	Stores / Finance	Inventory
		By movement wise
		By supplier
10	Account document listing	By material	MR51	The report Accounting documents for material produces a list containing all accounting documents available for a selected material.	Finance	Inventory
		By date
11	Stock Overview	By material	MMBE	The stock overview provides you with an overview of the current stocks of a material at all places within plant	All	Inventory
		By Plant
		By batch
12	Stock requirement list	By material	MD04	This report will help you to analyse material requirement plan considering stocks and future requirements.	Planning	Inventory
		By material planner
13	Plant Stock availability	By material	MB52	This report provides an overview of the stock situation of a given  material in selected plants. If there are multiple plants where the same material exists, this report can give the information on stocks at various places	Stores / Purchase	Inventory
		By material type	MB53
		By buyer group	MCBA
			MCBE
			MCBR
14	Expiration date list	By material	MB5M	This report provides an overview of the remaining shelf life of batches. This report is generally useful in Pharma.	Stores / Planning	Inventory
		By Plant
		By batch
15	Stock on posting date	By material	MB5B	The report Stock for posting date lists a company's own stocks in a particular time period.	Stores	Inventory
		By Plant
		By batch
16	Stock in transit	By material	MB5T	This report issues a list with all stocks that are located in a plant's  stock in transit. This information is useful when interplant / intercompnay material transfer is taking place.	Stores / Finance	Inventory
		By supplying plant
		By receiving plant
17	Stock with subcontractor	By plant	MBLB	This report provides an overview of the stocks of material provided to vendor	Stores / Purchase / Accounts	Inventory
		By supplier
		By plant
18	List of GR / IR balances	By material	MB5S	The report compares the GR quantities and values relating to a purchase order with the invoice quantities and values for the same PO. The report can thus be used to check goods and invoice receipts when purchasing documents show some discrepancy.	Purchase / Accounts	Inventory
		By supplier
		By buyer
		By Purchase order
19	MRP Controller analysis	By inventory controller	MCBG	This report will help you in tracking the inventory by responsible person.	Executive	Inventory
20	Material usage based ABC Analysis	By usage	MC40	This report will help you in identifying the fast moving, slow moving / non moving items. The report can be executed at the material level / plant level	Executive	Inventory
		By requirement	MC41
21	Range of coverage	By usage	MC42	This report will help you in getting the information of coverage of the material for production purpose based on the past consumption pattern. The report can be executed material wise, commodity type wise, material planner wise etc.	Stores / Planning	Inventory
		By requirement	MC43
			MC.G
			MC.4
22	Inventory turnover	By material	MC44	This report will help you in getting the information on the inventory turn over ratio.	Executive	Inventory
		By commodity type	MC.3
		By buyer	MC.B
		By material planner	MC.7
			Mc.O
23	Slow moving items	By material	MC46	This report will help you to identify slow moving items.	Executive	Inventory
		By commodity type
		By buyer
		By material planner
24	Dead Stock items	By material	MC50	This report will help you to identify dead inventory	Executive	Inventory
		By commodity type
		By buyer
		By material planner
25	Usage value	By material	MC45	This report identifies the share of the usage value to the total usage. You can also see the report graphically for a selected material in detail screen.	Executive	Inventory
		By commodity type
		By buyer
		By material planner
26	Sales analysis	By Customer	MCTA	These reports can give you information regarding incoming sales order, credit memos, quantity, value etc.	All	Sales
		By material	MCTC
		By sales person	MCTE
		By sales office	MCTI
			MCTG
27	Report on: -	By material	MC(A	These reports can be used for seeking the information on billing	All	Sales
	Incoming orders	By Customer	MC+A
	Invoiced sales	By sales channels	MC+E
	Credit Memo		MC+I
	Sales return		MC+U
			MC+Y
28	Sale report with option like	By sales area	MC+2	The standard report MC+2 & MC+6 can meet the reporting requirement. However in case the standard report are not serving the reporting requirement user defined info structure can be created and transaction MCSI can be used for sales analysis.	All	Sales
	Area wise	By customer	MC+6
	Statewise	By material	MCSI
	Executive wise
29	Vendoe master list	By Supplier	MKVZ	This report can give you the list of suppliers	Purchase	Purchase
		By Purchase group
30	Status of indents	By indent	ME5A	This report can be used to seek the information of status of indent raised, purchase order number, goods receipt status etc.	Purchase	Purchase
		By material	ME5K		Stores
		By buyer
31	Quotations listing	By suppliers	ME4L	This report is useful to view / extract information on quotations from supplier in case  the quotations are invited for a particular indent	Purchase Executives	Purchase
		By mateial	ME4M
		By commodity group	ME4C
32	Commodity price	By material	ME1L	This report is useful to view the purchase order price change history for various pricing conditions	Purchase Manager	Purchase
		By plant	ME1M		Finance
		By Supplier	ME1W
			ME1P
33	Planned share of business	By material	MEQM	This report can be useful to know the % share of business planned with a supplier in case multiple sources exist for a commodity.	Purchase Executives	Purchase
		By supplier
34	Vendor rating	By commodity	ME64	This report is useful to extract information of supplier performance on various parameters such as delivery, quality, cost etc.	Purchase Manager	Purchase
		By commodity group	ME6D		Quality Manager
		By supplier	ME6C
			ME65
35	Commodity listing	By commodity	MM60	This report will give you the list of all materials created in the system with the parameter values	All	Logistics
		By plant
		By commodity group
36	Purchase value		MC$G	This report can be used by purchase buyer / manager to track purchase performance	Purchase Executives	Logistics
	Purchase quantity		MC$1
	Quantity reliability		MC$M
37	Availability overview		CO09	This report gives you the information of material availble for production	Stores	Inventory
38	Physical inventory listing		MI24	This report may be used in case physical inventory system is followed in an organization	Stores	Inventory
					Finance
39	Bill of Materials	Display BOM	CS03	This report can give  you information related to Bill of materials, comparison of BOM between two materials etc.	All	Production
		Display BOM allocation to Plant	CS09
		Where used list	CS15
		BOM Comparison	CS14
		BOM explode - Multi level	CS12
		Bom explode - Level by level	CS11
40	Work center information system	By machine wise	CR60	This report will give you information of the machines used for the purpose of manufacturing. The machines / work center could be labor work center also	Shop floor	Production
		By planner wise	CR05		Costing
		By plant wise
41	Work cener analysis	By lead times	MCPB	This report can be used to extract the information of operation qy, scrap qty, lead time, target lead time etc.	Shop floor Manager	Production
	Operation analysis	By date	MCPY
		By quantity	MCPK
			MCPQ
42	Material analysis	By lead times	MCPW	This report is useful for giving the information of Target vs actual lead time,	Executive	Production
		By date	MCPF	Planned order qty vs actual order qty,
		By quantity	MCPO	Planned cost vs actual cost,
		By product cost	MC89	Planned consumption vs actual consumption
		By material consumption
		By sales / production plan
43	Operation analysis	By plant	MCP1	The order information system is a tool for shop floor control with a reporting function for production orders and planned orders. These reports are useful in discreet manufacturing set up.	Shop floor	Production
	Material analysis	By material	MCP3
	Work center analysis	By order	MCP5
	Production order analysis	By machine	MCPB
			MCPU
			MCPW
44	In repetitive manufacturing set up: -	By plant	MCRP	These reports are extensively used for reporting purpose in the repetitive manufacturing environment	Shop floor	Production
	Production analysis	By material	MCRK
	Material consumption analysis	By component used	MCP6
	Product cost analysis
45	Pull list	By plant	MF60	This report can be used in repetitive manufacturing environment to know the shortage of material for production	Shop floor	Production
		By material			Stores
		By quantity
		By storage location
46	For process industry: -	By plant	MCP5	These reports are useful only when PP-PI component is installed.	Shop floor	Production
	Shop floor information system related to material analysis,	By material	MCRU
	operation analysis, process order analysis, material usage analysis, product cost analysis	By order	MCRV
		By machine	MCRW
			MCRX
			MCRY
47	Kanban analysis	By plant	MCQ.	This report will give the information of Kanban usage. Can be used only when Kanban component is used	Shop floor	Production
		By supply area
		By material
48	Kanban analysis	By demand source overview	PK13	This report can be used only when Kanban feature of SAP is used.	Shop floor	Production
		By supply source overview	PK12
		By plant overview	PK11
			PK18
49	Material usage analysis	By plant	MCRE	This report can be used for analysing the actual material usage against plan in manufacturing process.	All	Production
		By material
		By component used
		By order
50	Product cost analysis	By plant	MCRI	This report can be used for finding out planned cost vs. actual cost in the manufacturing process	All	Production
		By material
		By component used
		By order
51	Product cost analysis - Summarised	By hierarchy	KKBC_HOE	This report can give you summrised information of all the production orders related to cost & quantity	Executive	Production
		By period
52	Cost Variance Target / Actual	By plant	S_ALR_8701348	This report can give you information on the cost variance analysis	Executive	Production
	Variance analysis
53	Missing parts checklist	By plant	CO24	Missing Part list check
		By material
		By component used
		By order
54	Order progress report	By plant	CO46	This report can give you information of the order which is in process.	Shop floor	Production
		By material
		By order
55	Production order information system	By order	COOIS	This report give information on production order	Shop floor	Production
		By Material
		By plant
		By production planner
56	Production order cost analysis	By order	KKBC_Ord	This report can give you information on target cost against actual cost for production order	Executive	Production
57	Actual comparison of financial results by period with previous period	By GL Account	S_ALR_8701249 / 87012250 / 87012251 / 87012252	This report can give you financial statement for the selected period with comparison. The report can be viewed on half yearly / quarterly / periodic basis as well. For 10year comparison use transaction S_ALR_87012257	GL	Finance
		By Financial statement version
58	Balance sheet / P&L statement	By financial statement	S_ALR_870122284	This report will give you balance sheet / P&L	GL	Finance
		By company code
59	Plan /  actual comparison on periodic basis		S_ALR_87012253	This report will be useful incase you are using GL planning.	GL	Finance
60	Cash flow report		S_ALR_87012271	This report will give you cash flow.	GL	Finance
61	GL Balances		S_ALR_87012277	This report can be used to display GL balances	GL	Finance
			S_ALR_87012301
62	Document Journal at summary level		S_ALR_87012287	This report is useful to extract information of GL entries	GL	Finance
	Document Journal at line item level		S_ALR_87012291
63	Statement of customer / vendor / GL Accounts	By company	S_ALR_87012332	This report will give you statement of customer wise / Vendor wise / GL wise accounts	GL	Finance
		GL Account
		Customer account
		Supplier Account
64	Customer payment history		S_ALR_87012177	This report will help you to analyse history of customers. It contains a forecast of payment volumes and arrears.	AR	Finance
65	Due date analysis for customer open items		S_ALR_87012168		AR	Finance
66	Account receivable information system		S_ALR_87012167	The report is used for displaying the evaluations available in the customer information system.	AR	Finance
67	Customer balances		S_ALR_87012172	This report will give you balance at the period start, debit total & credit total for the reporting period and closing balance at the end of reporting period.	AR	Finance
68	Customer evaluation with open item sorted list	By Customer	S_ALR_87012176	This report can give you open AR sorted in days bucket as per your selection	AR	Finance
		By Company
69	Vendor information system	By company	S_ALR_87012077	This report is used for displaying the vendor payment information based on due date, over due, currency etc.	AP	Finance
		By supplier
70	Vendor business	By company	S_ALR_87012093	This report is to be used  when you want to see the information of purchases made from a supplier	AP	Finance
		By supplier
71	Due date analysis for supplier open items	By company	S_ALR_87012078		AP	Finance
		By supplier
72	Vendor payment history	By company	S_ALR_87012085	This report is used for determining the current payment status for vendors. The report carrry out an analysis of the vendor open items according to user defined time pattern.	AP	Finance
		By supplier
73	Check register	By bank	S_P99_41000101	This report is used to extract the information of check issued	Bank	Finance
		By amount
74	Asset History	By Asset	S_ALR_87012075	It is the most important and most coprehensive report for the year-end clsoing or for an interim financial statement	Asset	Finance
		By asset class	AR02
		By company code
75	Depreciation simulation / forecast	By Asset	S_ALR_87012936	This is a report for the simulation of future depreciation	Asset	Finance
		By asset class
		By company code
76	Posted depreciation	By Asset	S_P99_41000192	The report list the period values from posting depreciation	Asset	Finance
		By company code
77	Year end income tax depreciation report	By Asset	J1IQ		Asset	Finance
		By company code
78	Asset Inventory list		S_ALR_87011981		Asset	Finance
79	Cost center accounting - Plan / Actual comparison	By Cost Center	S_ALR_87013611	This report lists actual and plan figures for cost center .	CCA	Controlling
		By cost center group	S_ALR_87013615
		By version	S_ALR_87013620
80	Cost center accounting - Actual / Actual comparison	By Cost Center	S_ALR_87013640	This report can be used to compare the actual costs on period basis	CCA	Controlling
		By cost center group
81	Cost center plan	By cost center	KSBL	This report can be used to view cost center plan	CCA	Controlling
82	Analyse / compare product cost estmates	By plant	S_P99_41000111	This report can give you the information on standard cost of material	PC	Controlling
		By material number	S_ALR_87013047
83	Profitability report	By sales order	KE30	This report can give you profitability at the sales order level. However it is necessary to implement PA module	PA	Controlling
		By material
		By plant
84	Profit center report		S_ALR_87010777		PA	Controlling
			S_ALR_87010779
85	Display machine list	By machine number	IH08	This report will give you the list of machines installed in the plant	Shop floor	Maintenance
		By plant	IW29
		By status	IW33
			IW39
86	MTTR / MTBR for machine	By machine number	MCJB	This report can be used for extracting information on Meant time to repair.	Shop floor	Maintenance
			MCJC
87	Damage analysis	By machine	MCI5	This report can be used to extract the information on damage analysis	Shop floor	Maintenance
		By damage code
88	Breakdown analysis	By machine	MCI7	This report can be used to extract the information on breakdown such as number of break down, MTTR, MTBF	Shop floor	Maintenance
		By machine group
89	Maintenance cost analysis	By machine	MCI8	This report will be used to extract information on planned cost and actual cost for different type of breakdown	Shop floor	Maintenance
		By machine group
90	Customer notification analysis		MCIA	This report can be used for reporting customer notifications. It can be used if service management functionality is put in use.	Service	Maintenance
91	History of inspection characteristics		QGP1	You can use this report to display inspection results for a task list characteristics	Quality	Quality Magt
92	Control Chart		QGC1	You can get quality control charts are lot level / characteristics level	Quality	Quality Magt
			QGC2
			QGC3
93	Quality Notification analysis		QM11		Quality	Quality Magt
			QM15
			QM50
94	Defect analysis report		MCXX	This report can be used to view quality defects at material / vendor / customer level	Quality	Quality Magt
			MCVX
			MCOX
95	Calliberation inspection		IP24	These reports can be used for extracting information related to calliberation of equipments	Quality	Quality Magt
			IP19
			QA33
96	Project cost / revenue / expenditure		S_ALR_87013531	These reports gives you cost related information of projects. However it is necessary to implement Project systems module to extract these reports	Projects	Project System
			S_ALR_87013532
97	Batch where used list		S_ALR_87012972	For extracting the information of batch traceability	Logistics	Logistics
98	Engineering change management		S_ALR_87012975	For tracking engineering changes.	Logistics	Logistics
			S_ALR_87012976
99	All Standard SAP Reports -- Module wise	Module wise	SAP1	Displays all the Standard report available in SAP in each module	Logistics	Logistics