4-d) tables I used .

(INTRVW) Mara material master Marc plant material for data MAKT material descriptions Mard material storage location Mbew material accounting VBAK sales order eader VBA! sales order item VB"K Billing document eader data VB"! Billing document item data #KK$ purc ase document eader #K!$ purc ase document item #K!A -- partner roles in purc asing % ebeln &purc . 'oc number) ( e)org &purc . $rgn*) + 4-d) If ,ou a-e MM transaction file data t en( w at tables are in-ol-ed for e.traction/ e)po 0imilarl, w at tables are in-ol-ed for MM master data e.traction/ I can sa, mara ( e))o 4-e) If ,ou a-e 0' transaction file data t en( w at tables are in-ol-ed for e.traction/ If transaction file is related to sales order t e tables in-ol-ed -bap etc. Vbap1 - sales item data Vbrp 1-- billing item 2i)p 1--deli-er, item

0imilarl, w at tables are in-ol-ed for 0' master data e.traction/ If it is sales order master data file t en master table is VBAK. VBAK 1 sales document eader VB"K 1 sales billing eader 0imilar, if its Billing t en master data table is VB"K. If its Billing item t en transaction data table is VB"!.

asap methodologies
3) 4 at are t e fi-e A0A! Met odologies/ (INTRVW)

A: Project plan. Business Blue print. Reali ation. !inal preparation. "o#$i%e &upport.
'. Project Preparation: In t is p ase( decision ma)ers define clear pro5ect ob5ecti-es and an efficient decision ma)ing process &i.e. 'iscussions wit t e client( li)e w at are is needs and re6uirements etc.). !ro5ect managers will be in-ol-ed in t is p ase (. Business Blueprint: It is a detailed documentation of ,our compan,7s re6uirements. &i.e. w at are t e ob5ects we need to de-elop are modified depending on t e client7s re6uirements). ). Reali ation: In t is onl,( t e implementation of t e pro5ect ta)es place &de-elopment of ob5ects etc) and we are in-ol-ed in t e pro5ect from ere onl,. *. !inal Preparation: 8inal preparation before going li-e i.e. testing( conducting pre-go-li-e( end user training etc. +. "o#$i%e , support1 T e pro5ect as gone li-e and it is into production. T e !ro5ect team will be supporting t e end users.

4-9)

-uties .or implementation project

:: a) "e6uirement gat ering from scratc . b) !reparing t e business blueprint. &basicall, done b, 8unctional consultant in B4) c) !reparing pro5ect plan and specs. &done b, tec nical B4 consultants) d) data flows e) de-elopment from scratc . f) de-eloped be. reports from scratc . f) Transport.

4-;)

Responsi/ilities in implementation project.

a) In-ol-ed in preparing pro5ect plan<specs b) In-ol-ed in performance tuning of t e pro5ect&maintain aggregates ( 2I' ( compression ( partition t e I= c) Monitoring tuning of data loads and 6ueries. d) =reated process c ains ( I= ( M! ( '0! ( Infosets as per business re6uirement e) Acti-ated 2$ coc)pit e.tract structures for sales&0'). f) >sed generic e.tractor for tables. g) 'e-eloped ob5ect le-el routines( start routines and end routines. ) =reated transformation between t e source and target. i) =reated and =ustomi*ed be. 6ueries against I= ( dso ( multipro-ider etc. 5) Integrating be. reports to enterprise portal. ?-9) &upport project (INTRVW) a) 02A 1 ser-ice le-el agreement &agreement between client and compan,). b) 0$! 1 statement of procedure c) 0$4 1 statement of wor) d) "A" 1 resource allocation reports e) Tic)eting tools or incident trac)ing tools. ?-;) Responsi/ilities in &upport project. (INTRVW) 0R Pro%iding -ail1 Production &upport .rom 0..shore.(as mentioned in 2V) a) In-ol-ed in resol-ing medium and ig priorit, tic)ets. 8or e.ample additional I$@s to be added ( data load failures etc. I used remed1 tool .or tic3eting. b) "ectification of load failures li)e master data loads and transaction data loads. c) Aenerating and maintaining of aggregates on I=. d) Bob monitoring and sc eduling process c ains ( fi.ing process c ain failures.

Based on re6uirement created process c ain. 0c eduling t em for periodic loads. = anging date and time of process c ains i.e we can c ange t is in rspc. e) 4or)ed on 2$ e.traction and generic datasource. f) =reation of 6ueries and c anging t e 6ueries based on business re6uirement. g) Broadcasting of reports to portal. ) 0tatus update &of t e wor) u a-e done) i) Transported ob5ects if re6uired. &$A4s in support project:(Resol%ing tic3eting issues in production support) (INTRVW) T is means agreement between ser-ice pro-ider&compan,) and client. If an, escalation occurs client doesn@t pa, mone,. T e s,stem guarantees t at all people will be informed if escalation occurs. a) $o5 priorit1 creating report < I= Also we a-e Ac)nowledge time C "esponse time C resolution time Dou can resol-e wit in ; wor)ing da,s. b) 6edium priorit1 report broadcasting ( mismatc in data Also we a-e Ac)nowledge time C "esponse time C resolution time Dou a-e to resol-e wit in E ours. c) 7igh priorit1 'ata loads failures. !roduction support errors. 'ata inconsistenc, in reports Also we a-e Ac)nowledge time C "esponse time C resolution time. Dou a-e to resol-e wit in ; ours. F$T1 TG# AB$V# "#0!$F0# TIM# VA"I#0 8"$M =$M!AFD T$ =$M!AFD. &0P: (statement o. procedure) !reparation of agreed documents i.e responsibilities as B4 de-eloper 0$! is of ; t,pes. A) standard sop &preconfigured wit t e s,stem) H b) 8le.ible sop can -ar, depending on re6uirement. &0W:& it is 5ob of basis consultant) "esponsibilities of abap gu, ( B4 gu,

RAR: &resource allocation report) 'etails of resource t at are wor)ing H t ose w o a-e alread, wor)ed earlier in t e pro5ect. ?) w at tas)s do we perform 'ail, Basis ( wee)l, basis ( Mont l, basis etc.

(IB6)
Tas3s per.ormed on dail1 /asis: &Gig !riorit, Tic)et) a) Monitoring dataload failures. b) Monitoring process c ain failures. c) Monitoring production support failures. Tas3s per.ormed on 5ee3l1 /asis: a) creating reports. b) fi.ing issues in reports c) sc eduling reports. &Medium !riorit, Tic)et)

Tas3s per.ormed on 6onthl1 /asis: a) !ulling data from #== BI s,stem&"<3 e.traction). b) report broadcasting. c) =reating new I$@s to infopro-ider. d) Transport. e) 4riting new routines. f) Maintaining aggregates&done -er, once in 3 mont s)

I) Transport errors. (INTRVW) a) 8rror: Not correct usage "eason1 T e structure of cube could a-e been c anged. 2i)e a e.tra na-igational attribute could a-e been added. 8i.1 'elete inde.es ( and retransport H t en rebuild inde.es.

b) 8rror: The %ie5 containing trans.er structure .ields could not /e imported into target s1stem. "eason1 2ac) of table space.

8i.1 use 8M "0'AJ=>B#JA=TIVAT# to increase t e table space.

c) 8rror: In.oo/ject not a%aila/le in acti%e %ersion "eason 1 we get t is error w en we tr, to transport I$= wit out transporting t e infoob5ects. 8i. 1 Transport t e re6uired infoob5ects.

d) 8rror : 8lement is missing is %ersion 6 "eason 1 T is error occurs if all ob5ects in 6uer, are not captured. 8i. 1 =apture all related ob5ects and transport again. e) 8rror : &1nta9 error in routine. "eason1 T e routine < transformation as s,nta. errors. 8i. 1 'ebug and 8i. t e errors and retransport.