Service Order Info

• IH01- Functional Location Structure
• IW58 – Change Service Notifications
• IW72- Change Service orders
• DP90 – Billing for Service Order
• IW33- Display Service Order
• IW53 – Display Service Notifications

 

Purpose of Physical Partitioning

Here is how you can see is there any physical partition for the particular cube:

1. Double click the cube
2. Go to Extras -> DB Performance -> Partitioning
3. If you see any info object is maintained then there is using physical Partition.

The purpose for physical partitioning is for performance. I will update more info later.

 

How To Read Fact and Dimension Table via RSRV

Here is the step to check the fact table and the dimension table:

There are 2 options that you can use:

Option 1:

Run Program SAP_INFOCUBE_DESIGNS to analysis all the cube that have fact and dimension table.

Option 2:

In RSRV, run the test: All elementary > database > Database Info about Infoprovider tables. Supply the name of your cube and execute it.

Rule of thumb is the dimension table shouln’t exceeed 20% of the fact table.

1. Table /BIC/FZCO_C11 has 2549370 entries; size corresponds to 2% of the InfoCube
2. Table /BIC/EZCO_C11 has 134842199 entries; size corresponds to 98% of the InfoCube
3. Table /BI0/D0CATS_C01C has 12647541 entries; size corresponds to 31% of the InfoCube

Example you will see some information as above after you have run RSRV as mention above and here is how you read this info.

The first line /BIC/F represent the Fact Table which has 2549370 number of entries and is 2% of the fact table.

The second line /BIC/E if there is any compression to the cube this line will have info else it will be 0. After the compression, the F fact table contains no more data. Instead, the compressed data now appear in the E fact table.

The third line /BI0/D is the dimension table and 31% means that it has exceed the fact table and need to analyst and change the dimension accordingly. 

Below is a useful link for more information for how you can read  and optimize your cube.  

http://forums.sdn.sap.com/thread.jspa?forumID=131&threadID=77761&messageID=837101

 

Process Chain Monitor Tools

To monitor your daily process chain you can go to Tcode RSPCM. This tool will show you all your process chain that you added.

To send mail to your mailbox if process chain is having error Tcode ALRTCATDEF.

 

Shortdump Message type – X

If when you try to open info package it gives you a short dump message type X. Try the solution below esle go to sapnotes 852443 for more details:

Go to ECC RSA7 and delete the info source.

 

Newly Added IO not populating

If you have coding in End Routine in your transformation and when you debug everything is fined and data populated in the result package but data not displaying in the infoprovider. Here is the solution…

- Just put in a constant value in those IO although is just blank value. After that you should be able to see the value populated in the DSO. Guess it might be a bug in BI.

 

Frequently Used Tcode in BI

S.No	Tcode	Description
1	RSA1	Administrator Work Bench
2	RSA11	Calling up AWB with the IC tree
3	RSA12	Calling up AWB with the IS tree
4	RSA13	Calling up AWB with the LG tree
5	RSA14	Calling up AWB with the IO tree
6	RSA15	Calling up AWB with the ODS tree
7	RSA2	OLTP Metadata Repository
8	RSA3	Extractor Checker
9	RSA5	Install Business Content
10	RSA6	Maintain DataSources
11	RSA7	BW Delta Queue Monitor
12	RSA8	DataSource Repository
13	RSA9	Transfer Application Components
	RSBBS	Maintain Query Jumps (RRI Interface)
14	RSD1	Characteristic maintenance
15	RSD2	Maintenance of key figures
16	RSD3	Maintenance of units
17	RSD4	Maintenance of time characteristics
18	RSDBC	DB connect
19	RSDCUBE	Start: InfoCube editing
20	RSDCUBED	Start: InfoCube editing
21	RSDCUBEM	Start: InfoCube editing
22	RSDDV	Maintaining
23	RSDIOBC	Start: InfoObject catalog editing
24	RSDIOBCD	Start: InfoObject catalog editing
25	RSDIOBCM	Start: InfoObject catalog editing
26	RSDL	DB Connect – Test Program
27	RSDMD	Master Data Maintenance w.Prev. Sel.
28	RSDMD_TEST	Master Data Test
29	RSDMPRO	Initial Screen: MultiProvider Proc.
30	RSDMPROD	Initial Screen: MultiProvider Proc.
31	RSDMPROM	Initial Screen: MultiProvider Proc.
32	RSDMWB	Customer Behavior Modeling
33	RSDODS	Initial Screen: ODS Object Processng
	RSDS	Data Source Repository
34	RSIMPCUR	Load Exchange Rates from File
35	RSINPUT	Manual Data Entry
36	RSIS1	Create InfoSource
37	RSIS2	Change InfoSource
38	RSIS3	Display InfoSource
39	RSISET	Maintain InfoSets
40	RSKC	Maintaining the Permittd Extra Chars
41	RSLGMP	Maintain RSLOGSYSMAP
42	RSMO	Data Load Monitor Start
43	RSMON	BW Administrator Workbench
44	RSOR	BW Metadata Repository
45	RSORBCT	BI Business Content Transfer
46	RSORMDR	BW Metadata Repository
47	RSPC	Process Chain Maintenance
48	RSPC1	Process Chain Display
49	RSPCM	Monitor daily process chains
50	RSRCACHE	OLAP: Cache Monitor
51	RSRT	Start of the report monitor
52	RSRT1	Start of the Report Monitor
53	RSRT2	Start of the Report Monitor
54	RSRTRACE	Set trace configuration
55	RSRTRACETEST	Trace tool configuration
56	RSRV	Analysis and Repair of BW Objects
57	SE03	Transport Organizer Tools
58	SE06	Set Up Transport Organizer
59	SE07	CTS Status Display
60	SE09	Transport Organizer
61	SE10	Transport Organizer
62	SE11	ABAP Dictionary
63	SE18	Business Add-Ins: Definitions
64	SE18_OLD	Business Add-Ins: Definitions (Old)
65	SE19	Business Add-Ins: Implementations
66	SE19_OLD	Business Add-Ins: Implementations
67	SE21	Package Builder
68	SE24	Class Builder
69	SE80	Object Navigator
70	RSCUSTA	Maintain BW Settings
71	RSCUSTA2	ODS Settings
72	RSCUSTV*
73	RSSM	Authorizations for Reporting
74	SM04	User List
75	SM12	Display and Delete Locks
76	SM21	Online System Log Analysis
77	SM37	Overview of job selection
78	SM50	Work Process Overview
79	SM51	List of SAP Systems
80	SM58	Asynchronous RFC Error Log
81	SM59	RFC Destinations (Display/Maintain)
82	LISTCUBE	List viewer for InfoCubes
83	LISTSCHEMA	Show InfoCube schema
84	WE02	Display IDoc
85	WE05	IDoc Lists
86	WE06	Active IDoc monitoring
87	WE07	IDoc statistics
88	WE08	Status File Interface
89	WE09	Search for IDoc in Database
90	WE10	Search for IDoc in Archive
91	WE11	Delete IDocs
92	WE12	Test Modified Inbound File
93	WE14	Test Outbound Processing
94	WE15	Test Outbound Processing from MC
95	WE16	Test Inbound File
96	WE17	Test Status File
97	WE18	Generate Status File
98	WE19	Test tool
99	WE20	Partner Profiles
100	WE21	Port definition
101	WE23	Verification of IDoc processing
102	DB02	Tables and Indexes Monitor
103	DB14	Display DBA Operation Logs
104	DB16	Display DB Check Results
105	DB20	Update DB Statistics
106	KEB2	DISPLAY DETAILED INFO ON CO-PA DATA SOURCE R3
107	RSD5	Edit InfoObjects
108	SM66	Global work process Monitor
109	SM12	Display and delete locks
110	OS06	Local Operating System Activity

111	RSKC	Maintaining the Permittd Extra Chars
112	SMQ1	qRFC Monitor (Outbound Queue)

113 ALRTCATDEF - Tcode to set Alert for Process chain

 

How To Create IDOC in WM

For IDOC in WM it will have some different configuration as in WM no output type are required for the transaction.

If you required IDOC in WM you have to configure extra setting in OMKY.

1) In OMKY under R/3 ->Ext System choose Interface Control. Select your warehose number, source type, destination type, movement type and under Receiver fill in the partner number name.

2) The IDOC generation is based on those field that mention in step 1. Only those field that fullfill the requirement will generate IDOC.

In WM not all the message type have Inbound and Outbound functions. Please refer to the link http://help.sap.com/saphelp_nw04/helpdata/en/52/16ac57543311d1891c0000e8322f96/frameset.htm

 

How To Create IDOC – Part II

As I received some comments that requested to have a step by step how-to create IDOC, I will try to explain the step here…

In IDOC the main configuration will be in Partner Profile (WE20)

1) Create a Logical system to use in the logical system as Partner No in WE20

Tcode: SALE -> Sending and Receiving Systems -> Logical System -> Define Logical System

2) In WE20 create new partner number and put in the logical system name that you created in the 1st step and partner type = LS.

3) In Outbound/ Inbound Parameter fill in the relevant message type.

4) For Outbound you will require to fill in Receiver port. Before this you have to create a port using WE21 by filling in your RFC destination name.

Notes: If your destination are using RFC create the port under Transaction RFC. File are used if the data are send using file format and same as XML File.

5) Fill in the basic type or Extension if necessary under Outbound Options.

6) Fill in also data under message control tab for application, message type, process code and other relevant info.

7) For Inbound parameters it has less info to fill in. You need to fill in the process code. This process code will tie to the Function module. Just double click on the process code to check on the function module.

WE41 – Outbound process code

WE42 – Inbound process code

After you have completed these steps create the relevant document eg: Sales order (VA01) and make sure you put in the output type in the Sales order. Check your IDOC created under WE02. If no IDOC is created check your partner profile and make sure all the partner function, message type in your SO output type fullfill the requirement in partner profile.

These are the basic steps you are required to setup IDOC. Hope these steps are clear for you to start your own IDOC

 

Request has reporting status BUT CANNOT BE ACTIVATED and DELETE.

1. Try Goto RSA1 -> PSA, find the PSA, then delete the error request from there
2. Goto RSRV, drag in the ‘foreign key ..’ and ‘check status…’ tests to the right, then put in the ODS name, and run
3. ST22, see if there is any relevant error
4. SM37, job name you put “BI_DEL*” basically try to find the deletion job that failed see if u can find it
5. Solution: a) Goto table RSODSACTREQ

b) Put the request number in the request ID

Eg: “REQU_ALZLI4CPDLXMINAQ7397WLNWC”

c) Delete that record, check the record, then ‘table entry’ -> ‘delete’

d) Goto table RSODSACTUPDTYPE, deletes all the entries which have the same request number

e) After deleted go to SE37,

RSDRO_SETSTATUS_FOR_REQUEST_20

I_ODSOBJECT put your ODS name

I_ACTREQUEST put your ODS request name

Eg:“ODSR_0V86SZU38DNXULICERI5A6CJ7”