Vous êtes sur la page 1sur 47

SAP QUIZ:

1. What are the components of Sales Area? a. Sales Organization b. Distribution Channel c. Division 2. How many Company Co es are ass!"ne to a Sales #r"an!$at!on? a. Only One company code can be assigned to a sales Organization %. How many Sales #r"an!$at!ons can &e ass!"ne to a Company Co e? a. Many sales Organizations can be assigned to a Company Code '. How many Company Co es can &e ass!"ne to a Chart of Acco(nt? a. Many Company Codes can be assigned to a Chart of Accounts ). *!st the +aster ,ata !n S,? -here are three +aster ,ata !n S, a. Customer Master Data b. Material Master Data c. Pricing Condition 6. hat is the relation bet!een sales organization and company codes" Many to One .. What !s the !fference &etween cash sales an r(sh or er? In r(sh or er !f a C(stomer places an or er el!/ery w!ll ta0e place !mme !ately &!ll!n" w!ll &e later 1. In cash sale !f a c(stomer places an or er el!/ery an 2!ll!n" w!ll &e on the same ay. 3. How system p!c0s (p pr!c!n" wh!le o!n" &!ll!n"? 4rom Sales #r er 15. What !s a 6AP? 78pla!n a 6ap !n yo(r last pro9ect?:real l!fe e8ample nee to create new ro(tes; &atch 9o&s for el!/ery create el!/ery 2loc0s< a. Difference bet!een AS #S and $O %&
11. In customer master data the client requirement needs legacy PeopleSoft customer number which can be solved with User exit. In sales order we need customer Phone number, we can use user exit If client want new field in customer master like nearest fire station. GAP analysis is done in Blue Print stage. It aims to understand what can be done with the standard SAP and how the client actually wants a particular scenario to be processed. Its an understanding of the GAP between the actual & required scenarios. he difference between agreed work and completed work is !"P "nalysis. #.g.$ o %ill his !ap, &e Use the #nhancements, These Enhancements are Divided Into Exits, Like User exits, Field Exits Screen Exits & Menu Exits. These

Enhancements are used to update the standard pro ram in its !espective "usiness Transactions, Used as a #ate$a% to Meet the &lient !e'uirements.

12. #ne or more plants can &e ass!"ne to a company co e; an one or more stora"e locat!ons can &e ass!"ne to a plant= $'(& a. A plant al!ays lin)ed to one company code and be assigned to one or more sales organization 1%. -he top le/el or h!"hest le/el of the or"an!$at!on !n sh!pp!n" !s the sh!pp!n" po!nt. -he el!/er!es are always !n!t!ate from e8actly one sh!pp!n" po!nt. $'(& 1'. A sh!pp!n" po!nt !s ass!"ne one or more plants an can &e s(&= !/! e !nto se/eral loa !n" po!nts= $'(& 1). A *oa !n" po!nt !s a s(&= !/!s!on of a sh!pp!n" po!nt an !t !s man(ally entere !nto the hea er of the el!/ery. $'(& a. >ol(ntary 7ntry 1?. What are the /!ews !n c(stomer master ata? a. General Data* Address+ Control Data ,ta- information.+ payment transaction ,ban) details.+ mar)eting ,customer. Classification+ industry.+ unloading points ,goods receiving hours.+ e-port data+ contact persons b. Company Code Data* Account management ,reconciliation account.+ Payment transactions ,$erms of payment+ payment bloc).+ Correspondence ,dunning procedure.+ #nsurance ,amount insured. c. Sales Data* orders ,sales office+ district+ group+ price group+ currency.+ shipping ,shipping condition+ delivering plant+ transportation zone.+ billing document ,terms of payment+ output ta- classification.+ partner function ,sold to party+ ship to party+ bill to party+ payer. 1.. What are the /!ews !n mater!al master ata? a. Basic data/ valid for all organizational units0 material 1+ material description+ base unit measured+ material division2 b. Sales/ Sales Org/ SD0 material pricing group+ volume rebate group+ product hierarchy c. Purchasing/ MM0 delivering plant+ material group+ ta- classification d. General/Plant Data/ SD0 Availability chec)+ transportation group+ loading group e. Other/ engineering+ accounting+ MP 11. What are the &(s!ness partners !n S,? a. Sold $o Party* Pricing+ #ncoterms+ Shipping Condition b. Ship $o Party* Ship to address+ goods receiving hours+ tac. %ill $o Party* %illing Address d. Payer* $erms of Payment+ Credit 3imit Chec) 13. *!st the !nternal or"an!$at!onal str(ct(re !n S, a. Sales Office b. Sales 4roup c. Sales Person 25. *!st the e8ternal or"an!$at!onal str(ct(res !n S,

Sales Organization Distribution Channel Division Plant* assumes the role of a delivering plant in SD. hen the delivery item is entered+ the system chec)s for the delivery plant automatically from the master data+ copies it to the document item. e. Storage (nit hat do you assign distribution channels and divisions" A Sales Organization. What are the h!"hest or"an!$at!onal (n!ts !n S,; ++.PP; 4I; C#? S, to Sales #r"an!$at!ons.++ to Plant; PP to Plant; 4I to Company Co e; Can a sales or"an!$at!on sell from a plant &elon"!n" to a !fferent company co e? @es. How many sh!pp!n" po!nts can yo( ass!"n to a plant? +any. 21. How many sh!pp!n" po!nts can yo( ass!"n to a sales or"an!$at!on? Aone. 22. What !s the str(ct(re of a sales oc(ment? a. 5eader Data* include customer related data* 6%A7 b. #tem Data* include material and 8uantity ordered data* 6%AP c. Scheduling 3ine Data* include delivery 8uantities and dates* 6%&P 2%. What !s the str(ct(re of a &!ll!n" oc(ment? a. 5eader Data* includes payer and billing date* 6%'7 b. #tem Data* material+ 8uantities+ and price* 6%'P 2'. What !s the str(ct(re of a el!/ery oc(ment? a. 5eader Data/ includes ship to party+ schedules for shipping process data* 3#7P b. #tem Data/ include material+ 8uantities+ !eights data* 3#PS 2). What are the ta&les !n SAP S,?
VBAK VBAP VBEP LIKP LIPS VBRK VBRP VBPA VBUK VBUP VBKD VBFA Order header Order item Order schedule Delivery header Delivery item Billing head. Billing item Partners Status head Status items Bus. data Doc. flow

a. b. c. d.

2?. *!st the f!el s !n SAP?


KUNNR Sold-to arty

ASAP methodology means noth!n" &(t stan ar process for !mplementat!on of SAP; It cons!sts of ) phases. 1. Pro9ect preparation = cons!sts of ! ent!fy!n" team mem&ers an as how to "o a&o(t the pro9ect. e/elop!n" strate"y

2. %usiness %lue print = cons!sts of ! ent!fy!n" the cl!ent c(rrent process; reB(!rement an how SAP pro/! es sol(t!on. Cons!sts of eta!le oc(mentat!on %. 'ealization =-he p(rpose of th!s phase !s to !mplement all the &(s!ness an process reB(!rements &ase on the 2(s!ness 2l(epr!nt. '. :inal Preparation = -he p(rpose of th!s phase !s to complete test!n"; en =(ser tra!n!n"; ). 6o *!/e an S(pport 1.
Pro!ect Pre aration "n this hase you lan your ro!ect and lay the foundations for successful im lementation. "t is at this stage that you ma#e the strategic decisions crucial to your ro!ect$ o o o o Define your ro!ect goals and o%!ectives &larify the sco e of your im lementation Define your ro!ect schedule' %udget lan' and im lementation se(uence )sta%lish the ro!ect organi*ation and relevant committees and assign resources

+. Business Blueprint "n this hase you create a %lue rint using the ,uestion - .nswer data%ase /,-.d%0' which documents your enter rise1s re(uirements and esta%lishes how your %usiness rocesses and organi*ational structure are to %e re resented in the S.P System. 2ou also refine the original ro!ect goals and o%!ectives and revise the overall ro!ect schedule in this hase. 3. Realization "n this hase' you configure the re(uirements contained in the Business Blue rint. Baseline configuration /ma!or sco e0 is followed %y final configuration /remaining sco e0' which can consist of u to four cycles. Other #ey focal areas of this hase are conducting integration tests and drawing u end user documentation. 4. Final Preparation "n this hase you com lete your re arations' including testing' end user training' system management' and cutover activities. 2ou also need to resolve all o en issues in this hase. .t this stage you need to ensure that all the rere(uisites for your system to go live have %een fulfilled. 5. Go Live & Support in this hase' you move from a re- roduction environment to the live system. 6he most im ortant elements include setting u roduction su ort' monitoring system transactions' and o timi*ing overall system erformance. +7.8B)9N Document num%er

N)6:R ;.6NR )RD.6 .U.R6

Net value ;aterial num%. Date Document ty e

What !s the p(rpose of sales oc(ment type? Sales oc(ments !s noth!n" &(t ata conta!ner; an !ts a proof of transact!ons to s!mpl!fy &(s!ness process oc(ment cate"or!$e !nto % types :sales oc(ment; el!/ery oc(ment ; &!ll!n" oc(ment sales oc(ment :sales relate ata !s "o!n" to &e capt(re here to map !fferent process transact!ons sap has cate"or!$e !nto ' types. Presales or er: !nB(!ry; B(otat!on :IA; Q-< Stan ar or er: #C; cash r(sh C(stomer o(tl!ne a"reement: Sche (l!n" a"reement=,S D contracts C(stomer compla!nts: cre !t; e&!t :62; *2< -he f(nct!ons of sales oc(ment type are: It can eterm!ne whether the sales oc of that type !s &loc0e or not; Ao. ran"es for the oc(ments; whether a reference oc !s man atory or not; whether !t sho(l rea c(stomer .mater!al !nfo recor ; whether the system sho(l r(n cre !t chec0s an how !t sho(l respon etc.. A sales oc(ment type f(lf!lls a reB(!rement of a spec!f!c &(s!ness transact!on. 4or e8ample; !n a cash sale yo( wo(l reB(!re the el!/ery to &e happen!n" !mme !ately after the or er an yo( wo(l reB(!re an !n/o!ce sl!p to &e han e o/er to the c(stomer !mme !ately after h!s p(rchase. -hese th!n"s are c(stom!$e !n yo(r Cash sales :CS< oc(ment type.. 22. *!st ) #r er -ypes !n S,? InB(!ry; B(otat!on; sales or er el!/ery; an &!ll!n". 2%.*!st Sales ,oc(ment -ypes: a. Credit; Debit 'e8uest b. Standard Order c. Contract d. Cash Sales e. 'ush Order f. :ree of Charge Delivery g. 'eturns h. Consignment :ill up <= Sales ,oc(ment 4(nct!ons the f(nct!on of a sales oc(ment !s to: i. Delivery Scheduling 9. $ransfer of re8uirements get product to customer ). Pricing l. Sales #nformation System m. Credit Chec)* Credit Management n. Output* &D#* In pract!ce; 7,I !s the act of e8chan"!n" ata thro("h comp(ters. +any &(s!nesses an other or"an!$at!ons (se 7,I e/ery ay !n the re"(lar co(rse of o!n" &(s!ness. -h!s !s &eca(se 7,I ma0es o!n" &(s!ness to"ether a more a(tomate an eff!c!ent process.

o. $e-t* $A> p. Availability Chec)* goods in !arehouse bac)!ard;for!ard scheduling+ apply to A$P+ safety Stoc)+ stoc) in 8uality 2) What are the !tems cate"or!es?
o

#tem categories are defined to provide additional control functions for the sales documents. :or e-ample+ the functions of a standard item are completely different from those of a free*of*charge item or a te-t item. $he system uses an item category to process a material differently in each sales document type. :or e-ample+ you can define a different control for a material in an in8uiry and a material in an order. $he item category in the sales document depends on the sales document type and the material. An item category group is defined in the material master record. #M4 SD Sales Sales Documents Sales Document #tem Define #tem Categories Assign #tem Categories* 6O6= control function attached to the transaction for the line item control for the delivery so you can ta)e. Delivery type could be partial+ combine+ complete consignment.

2'. Sales oc(ment -ypes controls how the sales oc(ment m(st f(nct!on; !t represent the !fferent &(s!ness transact!ons !n a company an perform certa!n controll!n" f(nct!ons. 2) what are !tem cate"or!es? Item cate"ory !s a "ro(p!n" of /ar!o(s mater!al types. Item cate"ory !s ass!"ne to the mater!al master. Item cate"ory !s a(tomat!cally eterm!ne &y SAP (r!n" the sale or er process!n" >#>' -=co e 2?. What are sche (le l!ne cate"or!es? Conta!ns !nformat!on a&o(t the B(ant!t!es of mater!al or ere &y the c(stomer an the correspon !n" el!/ery ate reB(este &y the c(stomer for el!/ery of that mater!al. $he items in a sales document are divided into one or more schedule lines. $hese schedule lines differ from each other !ith respect to date and 8uantity. Different control elements are also defined for the schedule lines. :or e-ample+ for some schedule lines+ material re8uirement planning is not carried out0 for other schedule lines+ it is carried out. Also goods receipt+ not goods issue+ is posted for a schedule line defined in a returns document. ?ame at least five features that you can control for the schedule line category"

Cele/ance for el!/ery; A/a!la&!l!ty chec0; -ransfer of CeB(!rements; 6oo s +o/ement; P(rchas!n" an Incomplet!on log. SCH7,U*7 *IA7:=It !s a&o(t el!/ery ate an el!/ery Q(ant!ty

hat is Condition type" A con !t!on type !s one wh!ch escr!&es that what !s the p(rpose of that con !t!on !.e. !t represents a real t!me pr!c!n" l!0e price+ discount+ freight or ta-es condition types are (se to ef!ne how the part!c(lar con !t!on !s "o!n" to perform. Con !t!on types are l!n0e to access seB(ence wh!ch !n t(rn !s l!n0e to con !t!on ta&les. Con !t!on types are (se where/er we (se con !t!on techn!B(e. Hence !t !s (se !n pr!c!n"; mater!al eterm!nat!on; o(tp(t control; etc. Some !mportant con !t!ons types !n pr!c!n" are pr55= pr!c!n"; 0foo=fre!"ht; 055.=c(stomer !sco(nt... hat are the fields in pricing procedure? -here are 1? col(mns !n pr!c!n" proce (re

$he follo!ing graphic provides an overvie! of some of the item categories !hich are defined in the standard system.

2. What !s A-P or a/a!la&!l!ty chec0? o Available to Promise availability chec) bac)!ard and for!ard schedule ta)es place here. #t chec)s inventory lead time for delivery. :or!ard schedule for delivery date.

Matches supply to demand 4ives customers reliable delivery commitments based on real time chec)s o Process of chec)ing the available 8uantities of a material. o A$P 8uantity@ arehouse stoc) A planned receipts ,incoming stoc). B the planned issues , outgoing stoc). ,ta)es into account all movements into and out of the !arehouse. 21 -ransact!on Co e for 2atch Process!n" !s S+%) an Eo& Sche (le !s S+%..
o o

23 What oes A2AP stan for? o Advanced %usiness Application Programming %5What oes 2API stan for? o %usiness Application Programming #nterface* is an interface providing access to processes and data of business application systems. #nterface for integrating third party applications and components in the business frame!or). %1What !s cons!"nment stoc0 n cons!"nment or ers yo( are allow!n" the stoc0 to s!t !n yo(r c(stomer locat!on. #nce he !nforms that he (se the stoc0 yo( w!ll !n/o!ce h!m. If he ret(rns the stoc0 yo( w!ll accept the stoc0 to ta0e !t &ac0. It !s ef!ne !n ' steps. %278pla!n +CP mon!tors sche (l!n" a"reements; an controls the!r stat(s o Material 'e8uirement Planning o -a0es place !n a plant %%What are a sche (le a"reement an !ts components? A sche (le a"reement conta!ns eta!ls of a el!/ery sche (le &(t a contract 9(st conta!ns B(ant!ty an pr!ce !nformat!on an no eta!ls of spec!f!c el!/ery ates hatCs the difference bet!een scheduling agreement !ith normal order" hatCs the condition for us to choose schedule line or order" 2oth of them conta!n sche (le l!ne; pr!ce; an B(ant!ty. -here are a co(ple ma9or !fferences: :1< * Schedule agreements allo! you to have < different sets of schedule lines :>27P= A2AC-<. Stan ar SAP yo( sho(l ha/e two sets of ta&s = of sche (le l!nes. #ne 4orecast D the other EI-. 4orecast forwar s the sche (le l!nes to plann!n" :seen !n +,5'< an EI- passes them to sh!pp!n" :>*15<. -hey can &e ! ent!cal or !fferent. -yp!cally these are (se for component s(ppl!er c(stomers :namely A(tomot!/e<. -he

c(stomer w!ll pro/! e yo( '=15 wee0ly &(c0ets :(s(ally a +on ay ate< of f(t(re forecast B(al!ty. Also sen yo( 1=2 wee0s of !n !/! (al 4IC+ sh!p ates = wh!ch are entere on the EI-. It comes own to the c(stomer not 0now!n" e8actly what they nee ne8t wee0; &(t they onFt want to s(rpr!se yo( w!th a lar"e or er Bty; where yo(r lea t!mes are )G ays. -he forecaste Btys they sent last wee0 sho(l acco(nt for th!s. :2< C(m(lat!/e Q(ant!t!es are trac0e an !nfl(ence how the sche (le a"reement passes reB(!rements to &oth forecast!n" an sh!pp!n". -hese Btys are somet!mes reB(este &y the c(stomer on ASAs. C(m(lat!/e Btys reset at year en (nless yo(F/e "ot a c(stomer calen ar or yo(F/e mo !f!e stan ar SAP (ser e8!ts to not reset. Sche (le a"reements are /ery n!ce when the c(stomer sen s 7,I ata :1%5s H forecast or 1?2s H EI-s<. #(ts! e of that they can really ca(se tro(&le re"ar !n" a!ly ma!ntenance; m!ss!n" reB(!rements; c(m Bty correct!ons; year en process!n"; etc. #ne alternat!/e wo(l &e to (se c(stomer !n epen ent reB(!rements = enter!n" the wee0ly; monthly forecast!n" Btys an enter!n" stan ar sales or ers :w!th or w!tho(t m(lt!ple sche (le l!nes< to represent the tr(e f!rm Btys. D= &-plain bloc)ing reasons+ bill bloc)ing and material bloc)ing? 2!ll!n" &loc0 pre/ent a &!ll!n" oc(ment from &e!n" create !t can &e one for cre !t memo or pro9ect m!lestone &!ll!n". +ater!al &loc0!n" for a material has technical defects or is to %e discontinued' you can %loc# the
material.

If yo( set a &loc0; or ers; el!/er!es an !n/o!ces conta!n!n" th!s mater!al cannot &e create at all; or only w!th a warn!n" messa"e. -he system react!ons to a &loc0e mater!al epen s on the type of %loc# set. Sh!pp!n" &loc0= most commonly (se = #>*S Shipping E delivery bloc)s can be manually entered. DF hat is ma)e to stoc)" +-S :+a0e to Stoc0< l!terally means to man(fact(re

pro (cts for stoc0 &ase on eman forecasts; wh!ch can &e re"ar e as p(sh=type pro (ct!on. +-S has &een reB(!re to pre/ent opport(n!ty loss (e to stoc0 o(t an m!n!m!$e e8cess !n/entory (s!n" acc(rate forecasts. In the !n (str!al!$e soc!ety of mass pro (ct!on an mass mar0et!n"; th!s forecast mass pro (ct!on (r"e stan ar !$at!on an eff!c!ent &(s!ness mana"ement s(ch as cost re (ct!on.
D6 hat is ma)e to order? +a0e=to=or er pro (ct!on !s a process !n wh!ch a pro (ct !s !n !/! (ally man(fact(re for a part!c(lar c(stomer. In contrast to mass pro (ct!on for an (nspec!f!e mar0et where a mater!al !s man(fact(re many t!mes; !n ma0e=to=or er

pro (ct!on a mater!al !s create only once tho("h the same or a s!m!lar pro (ct!on process m!"ht &e repeate at a later t!me. In "lo&al tra e; yo( often nee to process se/eral !fferent 0!n s of transact!ons at the same t!me. -he -ra !n" 78ec(t!on Wor0&ench :-7W< pro/! es a central coc0p!t where tra ers can process tra !n" contracts an the!r s(&components; s(ch as p(rchase or ers an sales or ers an follow=on oc(ments. In a !t!on; -7W a(tomates a lar"e part of the ata entry; ma0!n" process!n" B(!c0er; eas!er; an more error=free. FG. #n ho! many places !e can bloc) the Sales Document" Sales document can be bloc)ed at three places depending on $he customer ris) categories+ they are H. Sales order level ,high ris) customer. <. Delivery level ,medium ris) customer)
3. Goods issue level (low risk customer)

DG

hat is material determination? ;aterial determination ena%les the automatic su%stitution of materials in sales documents during sales order rocessing. <or e=am le' during the course of a sales romotion' the system can' during sales order entry' automatically su%stitute a material that has romotional ac#aging. . consumer roduct may have a s ecial wra er for' for e=am le' the &hristmas season. Using material determination' the system su%stitutes the material only during the s ecified eriod.

DI

hat is te-t determination) Text Determination: Any Texts in Material Master/Material Determination/Order/Delivery, etc is meant to convey messages to the subsequent documents for compliance e g !"ive Top #riority! message mentioned in Order is meant for #roduction Dept $b% Account Determination: is integration bet&een 'inance and (D The A/# along &ith Account )eys needs to be allocated accordingly &ith combination of Account Determination "roup for *ustomer and Material if required $c% #artner Determination: To identify &hich type of #artner it is so that if required for same *ustomer different #artner 'unctions may be required e g Only One (old To #arty per *ustomer More than One (hip to #arty/ +ill to #arty/ #ayer possible Accordingly different Masters &ill have to be created ,seful for dispatch of Material in case of (hip to #arty, sending +ill in case of +ill to #arty and payment follo& up/Dunning in case of #ayer $d% Output Determination: -hat DJ hat is output determination" o Output is the information sent to the customers via various media/ print+ email+ fa-+ &D#. o $a)es place using condition techni8ue o #n the output master data+ you define the transmission medium+ the time+ and the partner function for an output type. o $he layout of an output is defined by a form in SAP script. $he form is assigned to the output type.

=K.

hat is account determination? /.ssign what account the revenue is going to0 6o %e a%le to use revenue recognition' you should select several s ecial general ledger accounts. &hoose$ Sales and Distribution -> Basic Functions -> Account assignment/Costing -> Revenue Recognition

Automatic account determination


Configure the Automatic account determination -o allows the system to eterm!ne the correct 6I* acco(nt to post to &y cons! er!n" the type of transact!on an other factors. :%7P = Conf!"(re a(tomat!c acco(nt eterm!nat!on

Account determination: 'or transferring financial and costing information to proper financial docs

Determining t e Revenue A!!ount


Revenue recognition uses revenue account determination. 6o set u revenue account determination' use transaction 8KO..

Determining "on#Bille$ Re!eiva%les A!!ounts


6he account for non-%illed receiva%les is a s ecial general ledger account' used to determine revenue which has %een im lemented %ut not yet %illed. "f you want to set u an account' !oin an account with non-%illed receiva%les together with a customer reconciliation account which is a art of your chart of accounts. 2ou can use the transaction O8UR for this. 6he standard system has the %alance sheet account 74+7>> for non-%illed receiva%les in the US. and in &anada /.ccruals and Deferred "ncome0.

Determining t e De&erre$ Revenue A!!ount


6he deferred revenue account is a s ecial general ledger account' used to determine revenue which has %een %illed %ut not yet im lemented. 6he system determines the deferred revenue account for a document item using standard SD account determination. Use the transaction 8KO. for this.
'or controlling revenue account determination, the follo&ing criteria are important:

Account determination table .n the account determination table, you define the criteria on &hich account determination should depend

Access (equence /ere, you define in &hich sequence fields are read from the billing document $header and item% An access sequence refers to the permitted field combinations stored in the condition table

Account determination type The account determination type is a module of the conditions technique 0ou have to create at least one account determination type and allocate it to an account determination procedure

Account determination procedure The account determination procedure contains the necessary account determination types &ith &hich the (A# (ystem can automatically find the revenue accounts

Account 1ey -ith the three2digit account 1ey, you finally allocate the revenue account 0ou can set the system so that account determination is dependent upon the follo&ing master data fields:

Account group for material in the material master record Account group for customer in the customer master record

'1. What are A-P an the I+6 Path for A-P?


o o o o o

Available $o Promise Matches supply to demand 4ives customers reliable delivery commitments based on real time chec)s Process of chec)ing the available 8uantities of a material. A$P 8uantity@ arehouse stoc) A planned receipts ,incoming stoc). B the planned issues , outgoing stoc). ,ta)es into account all movements into and out of the !arehouse. #M4 SD %asic :unctions Availability Chec) E $O' Availability chec) Availability chec) !ith A$P 3ogic

'2. Wh!ch of the follow!n" apply!n" to A-P? all o Safety Stoc)/ stoc) e-amined for A$P o Stoc) in $ransfer o Stoc) in Luality

%loc) Stoc)

'%.*!st % el!/ery types: o Complete Delivery* $he system !ill only confirm a delivery date on a date !hen the entire scheduled+ ordered 8uantity for that line in the sales order is available. o Partial Delivery* one order* < deliveries o Order Combination* combined orders* H delivery o Consignment ''. What !s sh!pp!n" po!nt eterm!nat!on? o $he shipping point is the organizational unit responsible for the shipping processes. o $he shipping point is determined for each document item in the sales document item in the sales document. o $he three !ays system determines the shipping point automatically for each delivery item is through the shipping condition in the SD data for the sold to party+ the loading group in the SD data for the material+ and the delivering plant

&-plain the Steps to setup a route" A Co(te !s part of sh!pp!n" wh!ch !s eterm!ne ,epart(re ZoneG Sh!pp!n" con !t!onsG -ransportat!on 6ro(p an -ransportat!on $one '). What !s CIC74? ; Ceport; Interface; con/en!ence; enhancement; format D portal. CIC74 !s not a stan ar SAP acronymJ Is there anyone 0nows who ma e CIC74 acronym f!rstly? All r!"ht; CIC74 stan s for 'eports+ #nterfaces+ Conversions+ &nhancements+ and :orms. ' B 'eports Cefers report pro"ramm!n". #f co(rse; f!rstly class!cal report pro"ramm!n"; '#$& statementK then !t means A36 pro"ramm!n" w!th e!ther A*> f(nct!on mo (les or A2AP o&9ects. # * #nterfaces Interfaces are A3& ; #DOC e/elopments. Aot only e/elopment; A2AP pro"ramm!n" for I,#Cs; also I,#C c(stom!$at!on; mana"ement. I th!n0 !t m!"ht refer 7,I too. C * Conversion I th!n0 con/ers!ons means %DC programming; &atch !np(t f(nct!on mo (les; 2,C,A-A str(ct(re; CA** -CAASAC-I#A. +ay&e con/ers!on spec!f!cally refers con/ers!on pro"rams for stan ar &atch !np(t pro"rams. 7/en we can say !t refers *S+W.

& * &nhancements 7nhancements are user*e-its an the o&9ect or!ente mo el of (ser=e8!ts that !s %AD#s. 2(s!ness A =Ins !s a new SAP enhancement techn!B(e &ase on LLA2AP #&9ectsMM = -hey can &e !nserte !nto the SAP system &ase on spec!f!c (ser reB(!rement = 2(s!ness A =Ins sho(l &e cons! ere "eneral!$e 2(s!ness -ransact!on = 7/ents that can &e (se to &(n le pro"ram; men( an screen enhancements !nto a s!n"le a =!n. : * :orms 4orms are SAP script forms; SAP scr!pt pr!nt pro"rams; an Smart :orms. '?. What !s 3SM an what !s !t (se for? -he *S+ Wor0&ench !s an CI%=&ase tool that s(pports when transferr!n" ata from non=SAP systems to CI% once or per!o !cally. -he tool s(pports con/ers!on of ata of the le"acy system !n a con/en!ent way. -he ata can then &e !mporte !nto the CI% system /!a &atch !np(t; !rect !np(t; 2APIs or I,ocs. 4(rthermore; the *S+ Wor0&ench pro/! es a recor !n" f(nct!on that allows "enerat!n" a N ata +!"rat!on o&9ectO !n an entry or chan"e transact!on. '.. What !s el!/ery &loc0? o %loc) the transactions in shipping o Mou can customize the delivery bloc) to configure the detailed effects of bloc)ing in the shipping process. o &-ample/ bloc) create of delivery+ or allo! processing of the delivery and pic)ing but bloc) goods issue o Mou can specify a delivery bloc) for any of the follo!ing/ Sales document type/ 5eader 3evel Schedule 3ine 3evel Schedule 3ine Category Delivery $ype o Can also bloc) customer master record for a particular sales area or for all sales areas as far as deliveries are concerned. 6DKF o Delivery bloc) has to be assigned to the delivery document types '1. hat is billing bloc)" 2loc0s are somet!mes reB(!re to stop or hol a oc(ment from &e!n" &!lle to c(stomer. In the c(stomer master recor yo( can spec!fy a &!ll!n" &loc0. 2!ll!n" &loc0 can &e conf!"(r!n" !n the !tem cate"ory. . %loc# can revent the
release of %illing documents to financial accounting. Billing documents can %e %loc#ed in the following circumstances$

"f %illing ty es are used for which an automatic %loc# is set when a %illing document is created. 6he %loc# is defined in a ta%le "f errors occur during account determination "f a %illing document is incom lete %ecause' for e=am le' the customer master record of the ayer has not %een u dated for financial accounting

Bloc# %illing documents can %e released manually after they have %een chec#ed.

Can set !n the oc(ment hea er an !n the !n !/! (al !tems '3.What !s Co(te ,eterm!nat!on? o $he route is the transport channel of an outbound delivery from the delivering plant to the ship to party. o 'oute defines the actual transit time and the lead time for transportation planning. o Determining the route automatically through the departure zone for the shipping point+ shipping conditions from the sold to party data+ transportation group in the SD for the material data+ and the transportation zone in the ship to party general data )5. What are 2 types of 2!ll!n" Plans? o Milestone* in !hich the total value to be billed is distributed bet!een the individual billing plan dates o Periodic* in !hich the entire value is billed in full on each billing plan date. )1*!st 2!ll!n" -ypes? o #nvoice Split*partial o Collective Processing*complete o Order Combination*Separate billing document for each outbound delivery )2.P What act!/!t!es happen aro(n sales; &!ll!n"; an payments?

)%. What !s !nter=company &!ll!n" an !nter=company sales? o Inter=Company 2!ll!n" o #nter*Company Sales* A sales organization can sell products supplied by a plant !hich is assigned to a different company code. )'What !s yo(r (n erstan !n" of pr!c!n" an the components aro(n !t? o Con !t!ons= Pr!ces; ,!sco(ntsI S(rchar"es; fre!"ht; ta8es o 4!el Catalo"= conta!ns the l!st of 0ey f!el s o Con !t!on Cecor s= Conta!ns the /al(e for pr!ces; !scIs(rchar"e; fre!"ht; an ta8es=can &e ef!ne accor !n" to a scale to set l!m!t. Can spec!fy (pper D lower l!m!t= when pr!ces are entere man(ally !t has to &e w!th!n these l!m!ts

))What !s the I+6 Path for re&ate process!n"? *!st the ASAP +etho olo"y: o Pro9ect Preparation 4etting the pro9ect started #dentifying the team members Developing a high level plan o %usiness %lueprint (nderstand the business goal of the company Determine business re8uirements needed to support those goals o 'ealization #mplement all the business and process re8uirements based on the business blueprint o :inal Preparation Complete testing+ end user training+ system management Critical open issues are resolved o 4o 3ive and Support ).. What !s the transact!on co e for pr!c!n"? 6;K6

)1. Pr!c!n" proce (re !s allocate to the sales oc(ment or &!ll!n" oc(ment &y a eterm!nat!on r(le Because the R?3 condition techni(ue from ricing is used for calculating the shi ment costs' the most im ortant tool for controlling shi ment costing is the pri!ing pro!e$ure. 6he ricing rocedure contains all condition ty es that are to %e used for shi ment costing and it defines the se(uence in which calculation is carried out in the shi ment cost document. 2ou can s ecify re(uirements in the determination rocedure which define when individual conditions are considered. 6he ricing rocedure allows any num%er of su%totals %etween the gross value and the net value. Condition $ype A con !t!on type ser/es to !fferent!ate &etween pr!ces !n the system. @o( can ef!ne a separate con !t!on type for each type of pr!ce; s(rchar"e or !sco(nt that may ar!se !n yo(r &(s!ness transact!ons. -he con !t!on type ef!nes; for e8ample; a !sco(nt as a f!8e amo(nt or as a percenta"e. Calculation Schema

-he calc(lat!on schema escr!&es a seB(ence of con !t!on types that are (se to eterm!ne pr!ces. Access Se8uence An access seB(ence !s a search strate"y w!th wh!ch the system loo0s for /al! ata for a spec!f!c con !t!on type. @o( can ef!ne an access seB(ence for each con !t!on type. In

Enterprise Buyer the access seB(ences are pre ef!ne ; chan"es are not !nten e to &e ma e &y c(stomers. Condition $able

A con !t!on ta&le conta!ns pr!ce !nformat!on on a master ata type; for e8ample; on a pro (ct master. If yo( ef!ne a pro (ct pr!ce or a spec!al !sco(nt; for e8ample; yo( create con !t!on recor s !n the rele/ant con !t!on ta&le.

Using the Delivered Condition Types


-he el!/ere C(stom!$!n" sett!n"s han le the catalog price :con !t!on type 01CG< !n a spec!al manner s!nce !t or!"!nates from an e8ternal ata so(rce for techn!cal reasons an cannot &e represente (s!n" an access seB(ence an con !t!on ta&les. -he el!/ere "ross pr!ce con !t!on types !n the calc(lat!on schema are spl!t &ase on the!r pr!or!ty !n relat!on to a catalo" pr!ce: Con !t!on types that ha/e a h!"her pr!or!ty than the catalo" pr!ce; for e8ample; a man(al "ross pr!ce or a "ross pr!ce from a contract -he con !t!on type for the catalo" pr!ce

Con !t!on types that ha/e a lower pr!or!ty than the catalo" pr!ce; for e8ample; pr!ces !n a pro (ct l!n0a"e or !n a pro (ct.

Prerequisites
@o( ha/e set the necessary elements for Pricing !n SAP Enterprise Buyer C(stom!$!n". :4or more !nformat!on; see the Supplier Relationship Management Implementat!on 6(! e :I+6<: SRM Server Cross=Appl!cat!on 2as!c Sett!n"s Pr!c!n" 6eneral Conf!"(rat!on Parameters Process Con !t!on -ypes Process Calc(lat!on Schema Process Con !t!on 6ro(ps

4!rst a determination occ(rs that chec0s !f a /al(e e8!sts for each con !t!on type. In the secon an ma!n part of Pricing; a valuation occ(rs that eterm!nes wh!ch of the eterm!ne /al(es the system !s to (se.

-he system eterm!nes the "ross pr!ces an !sco(nts for the con !t!on types !n the calc(lat!on schema. If the con !t!on recor conta!ns a pr!ceIB(ant!ty scale; the system calc(lates the pr!ce accor !n" to the scale ef!ne !n the contract. 4or the "ross pr!ce eterm!nat!on; the system (ses the follow!n" pr!or!t!$at!on of con !t!on types :accor !n" to the el!/ere calc(lat!on schema<:

+an(al pr!ce Contract pr!ce Catalo" pr!ce Pr!ce from pro (ct l!n0a"e or from pro (ct.

Pricing ensures that a manual price has priority over a contract price; that a contract pr!ce has pr!or!ty o/er a catalo" pr!ce; an that a catalo" pr!ce; !n t(rn; has pr!or!ty o/er a pro (ct pr!ce. -he system e (cts e8!st!n" !sco(nts from the "ross pr!ce an th(s arr!/es at the net pr!ce.

Example
4or the pro (ct Qpenc!lsQ; there e8!sts a contract :/al! from 51.51.255R (nt!l 12.%1.255R< w!th a B(ant!ty scale an a percenta"e !sco(nt. -he pro (ct !s l!ste !n a catalo" w!th a pr!ce. In a !t!on; the pro (ct has a pr!ce !n pro (ct ma!ntenance :see SAP +en( +aster ,ata Pro (cts +a!nta!n Pro (cts<. #n 15.%5.255R a (ser or ere 2;555 penc!ls. -he system eterm!nes the contract to &e the so(rce an (ses the con !t!on recor from the contract to eterm!ne the pr!ce. -he system !splays the "ross pr!ce accor !n" to the store scale. -he net pr!ce !s calc(late less the percenta"e !sco(nt.

)3.-hese pr!c!n" proce (re eterm!nat!on !s &ase on the c(stomer master recor ; the sales oc(ment; an the sales area= $'(& ?5. $a- determination eterm!nes an calc(lates ta8es &ase on the or"an!$at!onal str(ct(re; co(ntry; re"!on; or c!ty of el!/er!n" plants an co(ntry or rece!/!n" c(stomer !n com&!nat!on w!th ta8 rele/ancy !n !cator on the c(stomer an mater!al mastersS recor . ?1. SAP has an !ncomplet!on str(ct(re that can &e ma!nta!ne to h!"hl!"ht m!ss!n" ata !n sales an el!/ery oc(ment as well as sales act!/!t!es an partner f(nct!on; th!s !s calle !ncomplet!on lo". In c(stom!$!n" yo( can ef!ne wh!ch

f!el s sho(l &e part of the !ncomplet!on lo". A/a!la&le !n the Sales #r er an ,el!/ery. $'(&

?2. -he concept of #(tp(t ,eterm!nat!on !s o(tp(t !n the form of me !a from a &(s!ness to one of !ts &(s!ness partnerK the poss!&le +e !as are pr!nto(ts; fa8es; tele8es; ema!ls; an 7,I. $'(& 6D. Define the concept of customer hierarchy" *ustomer hierarchy setup, firstly
decide the hierarchy type to be used The standard is type A 0ou can also assign a partner function to the customer so that the higher level customer in the hierarchy is copied into a sales order as a partner function 2 but you don3t need that right4 5ext assign your customer account group to the hierarchy type And enter the combinations that &ill be allo&ed for creating the hierarchy 0ou &ant to assign a ship2to to a payer (o enter the ship to account group and enter the payer account group as the higher level 0ou must also ma1e an entry for permitted sales area assignments (o if you &ant to a hierarchy for customers in the same sales area then enter the sales area and enter the same one as the higher level sales area All these settings can be found in the .M" ,nder (D 2 master data 2 business partners 2 customers 2 customer hierarchy you use for example customer hierarchy &hen you have a company li1e ,nilever and you agree both on a discount ,nilever does have different locations / businesses and you have to maintain the discount for all customers .f you use a customer hierarchy you can maintain the discount for the partner in the top of the hierarchy and in this &ay it &ill be valid for all customers in the hierarchy

6=.A product hierarchy li)e a customer hierarchy has an automatic Nfamily treeO lin)ing it bac) to a certain grouping of products.

65 Define the concept of credit management? What is Credit Management?


+ost enterpr!ses e8ten cre !t to the!r c(stomers. -h!s l!terally means; sell!n" the!r "oo s an collect!n" money at a later po!nt of t!me. -he amo(nt of cre !t e8ten e !s eterm!ne &y the c(stomerSs cre !t worth!ness :Also calle cre !t l!m!t < . -he n(m&er of ays for wh!ch cre !t !s e8ten e !s &ase on the payment terms assoc!ate w!th that transact!on. 4or e8.; C(stomer A co(l &e "!/en a cre !t l!m!t of T 155;555 &y the company.

Aow; let say that c(stomer or ers "oo s worth T 25;555 w!th payment terms of Aet ') 2 U : +ean!n" !f the c(stomer pays for the "oo s w!th!n ') ays of p(rchase; he w!ll &e "!/en a 2U cash !sco(nt. So !nstea of pay!n" T25;555; the c(stomer wo(l nee to pay :T25;555 V 2U of 25;555< H T 13;?55. -h!s !s to enco(ra"e t!mely payment of the!r &!lls an !mpro/e cash flow. A cre !t control area !s an or"an!$at!onal (n!t that !s compr!se of one or more company co e; also a company co e can ha/e no more than one cre !t control area? ?.. &-plain concept of bloc)ing customers? It !s poss!&le to &loc0 c(stomer master recor &eca(se of tra e ne"ot!at!ons are !n place or a c(stomer !s &lac0 l!ste . @o( ha/e the opt!on to &loc0 sales or er; el!/ery; an &!ll!n" oc(ment.

6I hat is the difference bet!een factory calendar and regular calendar" :actory calendar tell !or) days at a particular location. $hey are also use to determine !hen a delivery must ta)e placed A regular calendar is needed as !ell to tell the holidays

6J hat is the function of copy control and the different copy control scenarios !ith the transact!on co es? Copy Control !s (se for oc(ment flow for S, ,oc(ments !n SAP. @o( can spec!fy copy control !n SAP for certa!n sales oc(ment types. 4or e8ample yo( can ef!ne new sales or er type as NZ66O an yo( want to (se th!s sales or er type for new el!/ery or er wh!ch as NZ6@O. @o( can spec!fy new copy control for ata flow &etween these two sales oc(ments. @o( can also spec!fy ata wh!ch yo( want to copy from sales or er to el!/ery oc(ment. @o( can e8ec(te th!s process for hea er; !tem an sche (le l!ne for sales or er type. 2y (s!n" th!s f(nct!on; yo( can copy ata from reference oc(ment to &e ass!"ne oc(ment s(ch as mater!al n(m&er; c(stomer n(m&er; B(ant!ty; pr!ce; sales or"an!$at!on; company W -here are % le/els to e8ec(te copy control as &elow: 1. ,ata -ransfer Co(t!nes -h!s !s (se for how to copy f!el from reference oc(ment to &e ass!"ne 2. Copy!n" CeB(!rements -h!s chec0s the reB(!rement wh!ch !s met or not. %. Sw!tches -h!s !s (se for spec!f!c control. 4or e8ample yo( want to copy !tem n(m&er or not. @o( can (se copy control for &elow so(rce an tar"et oc(ment as &elow: oc(ment

X Sales oc(ment type from a sales oc(ment type X Sales oc(ment type from a &!ll!n" oc(ment type X ,el!/ery type from a sales oc(ment type X 2!ll!n" oc. type from a sales oc(ment type X 2!ll!n" oc(ment type from a el!/ery type X 2!ll!n" oc. type from a &!ll!n" oc(ment type

GK. 3ist a migration tool in SAP and the transaction code Performance -race tool !s a free &(!lt=!n SAP tool that comes w!th stan ar SAP !nstallat!ons. *S+W A2AP e/elopers can act!/ate an r(n Performance -race or w!th !ts 0nown name SQ* -race tool &y call!n" SAP -ransact!on S$KF. SAP Performance trace tool ena&les A2AP e/elopers to mon!tor ata&ase access; #pen SQ* calls an #penSQ* comman s e8ec(te on ata&ase. It ser/ers f(nct!ons to A2AP e/elopers to analy$e performance of the SAP system. Us!n" SQ* -race tool !n SAP; !t !s poss!&le to analy$e an etect loc0!n"; an trace remote calls of A2AP reports an SAP transact!ons.

GH. hat is the purpose of the Account 4roup" .2. $ransactions code SLKK is used to create A%AP Luery" GD hat is the use of 6ariant Configuration and list a $ code used for it"

>ar!ant Conf!"(rat!on !s (sef(l !f yo( ha/e a lar"e n(m&er of com&!nat!ons of parts that "o !nto a pro (ct. It means !fferent perm(tat!ons an com&!nat!ons of the parts for same mater!al. If yo( ma!nta!n a (n!B(e mater!al co e for each poss!&le com&!nat!on of parts; yo( reB(!re a lar"e n(m&er of mater!al n(m&ers. Us(ally !n/ol/es +a0e to #r er Pro (ct!on Process 78amples: A c(stomer or er!n" a comp(ter can choose !fferent com&!nat!ons of mon!tor; CPU; 0ey&oar . A c(stomer or er!n" a car can choose !fferent com&!nat!ons of accessor!es an color !n a &(s!ness !n/ol/!n" steel man(fact(r!n"; the c(stomer may or er steel !n/ol/!n" !fferent phys!cal propert!es l!0e tens!le stren"th; !ameter. >ar!ant conf!"(rat!on !s !nte"rate w!th the follow!n" appl!cat!ons: CA Class!f!cat!on *# +ater!al +aster
PP Bill of ;aterial PP Routings PP ;aterial Re(uirements Planning /;RP0 PP Production Orders

PP@P" ;aster Reci es &O &osting SD Sales SD &onditions ;; Purchasing

G=During incompletion log+ the follo!ing tables can be used/ An !ncomplet!on lo" or an !ncomplet!on proce (re ef!nes how the system sho(l respon when a sales oc(ment !s !ncomplete V mean!n" some of the necessary f!el s are not f!lle (p. -yp!cal cho!ces !ncl( e forc!n" the (ser to enter the ata an not let the (ser sa/e the or er &efore all the necessary f!el s are f!lle . -h!s !ncomplet!on proce (re can &e ass!"ne set to not 9(st the sales or er ; &(t sales or er l!ne !tem le/el; sche (le l!ne le/el; el!/ery hea er an el!/ery l!ne !tems. : Incomplet!on lo" cannot &e set for &!ll!n" oc(ments < -a&le >2AY
o

GF

hat are the vie!s in Condition Master 'ecord" Pr!ces: mater!al pr!ces :can ma!nta!n a mater!al pr!ce; c(stomer spec!f!cally<; pr!ce l!st; c(stomer spec!f!c o 4re!"hts: 4re!"hts Incoterm 1 G 2 o S(rchar"esI ,!sco(nts: for c(stomer; for mater!al; for pr!c!n" "ro(p; for c(stomerImater!al; :can ef!ne a !sco(nt to &e epen ent on the c(stomer an the mater!al pr!c!n" "ro(p<. o -a8es: /al(e a e ta8es G6Condition $ype/ Defines multiple uses of the conditions. ,epen !n" on the con !t!on type yo( can ha/e a percenta"e; a B(ant!ty epen ent; an amo(nt epen ent s(rchar"es an !sco(nts. GG. 6alidity Period/ restricts the price agreement to a certain period. GI.Condition 'ecord: +a!nta!n >al(es GJ. Automatic Pricing :unction: Allows yo( to /!ew pr!ces; s(rchar"es D !sco(nts; fre!"ht; ta8es for a &(s!ness transact!on. @o( can also chan"e these con !t!ons man(ally. IK. Pricing is performed using the Condition $echni8ue. o Pr!c!n" can &e (p ate on se/eral le/els (r!n" oc(ment process!n" o Can conf!"(re the &eha/!or of pr!c!n" f(nct!ons (r!n" (p ates !n the pr!c!n" type Con !t!on techn!B(e !s -H7 most per/as!/e an a /ery fle8!&le metho olo"y (se &y SAP to a! the cons(ltant !n conf!"(r!n" comple8 &(s!ness r(les. Some mo (les : S,; ++ < are more epen ent on !t than others. We are ta0!n" Pr!c!n" as an e8ample here; &(t w!ll not enter !nto the oma!n of Pr!c!n" :wh!ch !s pretty lar"e &y !tself<. -h!s art!cle !s also (sef(l for cons(ltants wor0!n" !n other mo (les l!0e 4IC# who m!"ht reB(!re an (n erstan !n" of Con !t!on -echn!B(e &efore they (n erstan Pr!c!n"
o

What is Condition Technique


Con !t!on -echn!B(e !s an SAP conf!"(rat!on techn!B(eImetho olo"y that !s (se to conf!"(re comple8 &(s!ness r(les. Cons! er !t as a 'ules en"!ne. 4or e8ample;

!n S, !t !s (se across m(lt!ple f(nct!onal!t!es V Pricing, Outputs, Texts etc. #n ++ the same techn!B(e !s (se to conf!"(re Schemas :Same as Pr!c!n"<.

Why is Condition Technique Used


Con !t!on techn!B(e !s (se when a comple8; e/er=chan"!n" set of &(s!ness r(les nee to &e conf!"(re as "ener!cally as poss!&le !n the system. Aoth!n" co(l capt(re the essence of th!s statement more than the comple8 r(les that &(s!nesses (se to Pr!ce the!r pro (ctsIser/!ces. 4or e8ample; !n pr!c!n"; each or"an!$at!on has the!r own set of &(s!ness r(les !ncl( !n" &ase pr!ce; mar"!ns; !sco(nts; ta8es; s(rchar"es; ealsIpromot!ons; pr!ce l!sts etc. 4or a s!n"le system to &e "ener!c eno("h to cater to all of these comple8 nee s !s a challen"e !n !tself an that !s e8actly what con !t!on techn!B(e tr!es to sol/e.

Condition Technique at a Very High Level


-here are . 0ey components of Con !t!on -echn!B(e. Aot all of the components are (se all the t!me. 2(t !t !s &enef!c!al to learn all of them 9(st !n case yo( want to sol/e comple8 pro&lems l!0e pr!c!n". . :ield Catalog 4!el Catalo" cons!sts of all the poss!&le set of f!el s that play a role !n eterm!n!n" the &(s!ness r(les Condition $able Con !t!on ta&le !s a ata&ase ta&le that !s create from a small s(&set of the f!el catalo" as part of the c(stom!$at!on. Access Se8uence Access seB(ence compr!ses of a seB(ence of con !t!on ta&les pr!or!t!$e !n a part!c(lar or er. Condition type each con !t!on type represents a lo"!cal component of the con !t!on techn!B(e. 4or e8ample; e8c!se ta8 co(l &e one of the lo"!cal components of pr!c!n" an !t co(l &e represente (s!n" one con !t!on type or a com&!nat!on of m(lt!ple con !t!on types. Procedure A proce (re !s a com&!nat!on of m(lt!ple con !t!on types. 4or e8ample; !n o(tp(t eterm!nat!on proce (re; all the seB(ence of con !t!on types m!"ht e8!st V *!0e 7,I; Pr!nt; 4a8 etc. Procedure Determination f!nally the proce (re !s ass!"ne to the f!nal oc(ment type that !s affecte &y the &(s!ness r(le.

It may not ma0e m(ch hea s or ta!ls 9(st yet. 2(t cont!n(e to rea an yo( w!ll &e s(rpr!se how s!mple an powerf(l th!s !s. Con !t!on techn!B(e co(l &e learnt e!ther &ottom (p or top= own. Howe/er; we are try!n" to e8pla!n !t here (s!n" the &ottom=(p approach. Also; !t !s m(ch eas!er to e8pla!n con !t!on techn!B(e (s!n" a stan ar SAP f(nct!onal!ty as an e8ample. We w!ll ta0e the most compl!cate e8ampleI(se :Pr!c!n" < an that way all of the aspects of the con !t!on techn!B(e w!ll &e co/ere . -he men( path to &e followe !s (n er SPC# =Z Sales D ,!str!&(t!on =Z 2as!c 4(nct!ons =Z Pr!c!n"M.
o

IHOptions for Changing Document Data: o 4ast chan"e !n oc(ment: allows yo( to chan"e se/eral or all !tems of a oc(ment at the same t!me. :Chan"!n" el!/ery plant or ate; re9ect!ons; sett!n" &loc0s<. Allows yo( to el!/ery or &!ll!n" &loc0 all at once for se/eral oc(ments o Chan"!n" se/eral oc(ments: can (se the oc(ment l!st to chan"e the plant; c(rrency; mater!al; pr!c!n" !n se/eral oc(ments at the same t!me. I<. hat is the purpose of maintaining common distribution channels and divisions" o Poss!&le for 2 areas +aster Cele/ant ,ata an Con !t!on Cele/ant ,ata o I+6=ZS,=Z+,=Z,ef!ne Common ,!str!&(t!on Channels or ,!/!s!ons o >#C1 o C(stomer or +ater!al master can &e ma!nta!ne wI respect to one !str!&(t!on channel an can &e (se as a reference !n other ,Ch. It pre/ents the m(lt!pl!cat!on of master recor s. ID. hat is bac)order processing? o Process!n" of a &ac0or er; wh!ch !n !tself !s a sales or er that has not &een conf!rme !n f(ll or not conf!rme at a certa!n el!/ery ate. I=.
o

hat is meant by rescheduling" Proposal of how conf!rme B(ant!t!es alrea y ass!"ne to sales or ers can &e reass!"ne to other or ers that ha/e a h!"her pr!or!ty; s(ch as an earl!er el!/ery ate.

1).

hat is the 'eplenishment 3ead $ime" o -!me nee e to pro (ce the reB(este stoc0 o -!me ta0en for the mater!al to &e a/a!la&le o #nly (se when o!n" an A$P chec)

I6. $ransfer Orders? o -ransfer of stoc0 from the !nter!m stora"e area: loa !n" an (nloa !n" area !nto the wareho(se o Instr(cts the wareho(se staff where to "et the stoc0 from an to el!/er !t to the !nter!m stora"e area for "oo s !ss(e

IG.

hat are the five fields to be maintained in Account Determination"

Acco(nt ass!"nment "ro(p= for c(stomer or mater!al H. Sales org <. Sales vie! D. Account )ey =. Chart of accounts F. Company code Acco(nt eterm!nat!on can &e allocate w!th c(stomer or mater!al II . 5o! can !e delete the Sales Orders" 5o! can invoices be cancelled or deleted" @o( cannot elete an In/o!ce. @o( can only cancel !t w!th ,6:HH. if the rele/ant acco(nt!n" oc(ment !s not &een "enerate . As0 yo(r 4I "(y to re/erse the acco(nt!n" oc. #nly after the acco(nt!n" oc !s re/erse an Ior elete ; yo( can cancel yo(r !n/o!ce. @o( also nee to chec0 !f any -AR oc(ments are "enerate w!th yo(r In/o!ce. @o( nee to re/erseI elete those oc(ments also. 1= create; 52= chan"e; 5%= !splay; 5?= elete; 522= ma!nta!n Ynow C#P@ C#A-C#*PPPPPPPPPPP Ynow Pr!c!n"PPPPP Ynow 2APIPPPP Iss(es= offshore cl!ents so lan"(a"e an t!me !fference P6I= Post 6oo s Iss(e Scenar!os= !ss(es an how ! yo( sol/e !t Conference callVoffshore= meets !n person to sol/e comm(n!cat!on pro&lems an opt!m!$e the t!me I onSt 0now &(t I w!ll f!n o(t *et them 0now yo(r stren"th !s functional= not techn!cal ,o yo(r homewor0 a&o(t the company *oo0!n" for more challen"esWa /ancements.. Prepare B(est!ons to as0..)=.

I,#C?= I,oc :for intermediate document< !s a stan ar ata str(ct(re for electron!c ata !nterchan"e :7,I< &etween appl!cat!on pro"rams wr!tten for the pop(lar SAP &(s!ness system or &etween an SAP appl!cat!on an an e8ternal pro"ram. I,ocs ser/e as the /eh!cle for ata transfer !n SAPFs Appl!cat!on *!n0 7na&l!n" :A*7< system. I,ocs are (se for asynchrono(s transact!ons: each I,oc "enerate e8!sts as a self=conta!ne te8t f!le that can then &e transm!tte to the reB(est!n" wor0stat!on w!tho(t connect!n" to the central ata&ase. Another SAP mechan!sm; the 2(s!ness Appl!cat!on Pro"ramm!n" Interface :2API< !s (se for synchrono(s

Learn More

SAP !nterface technolo"!es

transact!ons. A lar"e enterpr!seFs networ0e comp(t!n" en/!ronment !s l!0ely to connect many "eo"raph!cally !str!&(te comp(ters to the ma!n ata&ase. -hese comp(ters are l!0ely to (se !fferent har ware an Ior operat!n" system platforms. An I,oc encaps(lates ata so that !t can &e e8chan"e &etween !fferent systems w!tho(t con/ers!on from one format to another. I,oc types ef!ne !fferent cate"or!es of ata; s(ch as p(rchase or ers or !n/o!ces; wh!ch may then &e &ro0en own !nto more spec!f!c cate"or!es calle message types. 6reater spec!f!c!ty means that an I,oc type !s capa&le of stor!n" only the ata reB(!re for a part!c(lar transact!on; wh!ch !ncreases eff!c!ency an ecreases reso(rce eman s. An I,oc can &e "enerate at any po!nt !n a transact!on process. 4or e8ample; (r!n" a sh!pp!n" transact!on process; an I,oc may &e "enerate that !ncl( es the ata f!el s reB(!re to pr!nt a sh!pp!n" man!fest. After a (ser performs an SAP transact!on; one or more I,ocs are "enerate !n the sen !n" ata&ase an passe to the A*7 comm(n!cat!on layer. -he comm(n!cat!on layer performs a Cemote 4(nct!on Call :C4C<; (s!n" the port ef!n!t!on an C4C est!nat!on spec!f!e &y the c(stomer mo el. -he I,oc !s transm!tte to the rece!/er; wh!ch may &e an CI%; CI2; or some e8ternal system.
IDo!s' "Docs /"ntermediate Documents0 are the cru= of .9). 6hese are the documents with the hel of which $ata is e(! ange$ %et)een SAP R*+ an$ non#R*+ s,stems . .s the name suggests' these documents act as intermediate storage of information' which can %e sent %i-directionally. ;essage ty es are res onsi%le for creation of "docs. "Docs &om onents

Data on "nternet is e=changed using data formats li#e "P8A @ and S.P uses a similar a roach. "docs are a well-structured medium through which data transfer ta#es lace. <igure 3 e= lains the structure of "docs.

"mage Source$ htt $??hel .sa .com

.n "Doc is made u of the following arts$

7. -ontrol Re!or$' 6his section contains control information regarding the "doc. "ts
constituents are Sender1s name' Receiver name' ;essage ty e and "doc ty e /illustrated in figure 30. 6he format of the control record is similar for all "Doc ty es. +. Data Segment$ "t consists of a header that contains the identity of the "doc. "ts constituents include' a se(uential segment num%er' a segment ty e descri tion and field containing the actual data of the segment. 3. Status re!or$s$ 6he status record shows the information regarding the already rocessed stages and remaining rocessing stages of the "doc. "t has an identical format for each "Doc ty e. "docs Structure$ I$o!s support a ierar! i!al stru!ture. <igure 4 shows an "doc' starting with the header. 6he header has items' which in turn have su%-items. 6he lowest level in the hierarchy contains the te=t. 6he end of the "doc is re resented with the hel of .&&U; /means accumulate0 segment. Remem%er that an "Doc can only contain character fields.

Figure .' IDo! S/RU-/URE


"mage Source$ htt $??hel .sa .com

2API=2(s!ness appl!cat!on pro"ramm!n" !nterface= lan"(a"e that yo( wr!te to &e (n erstoo &y SAP Compan!es= Ynow the m"mt.; pro (cts they sell Pro9ect= PP* !n/ol/e = % or ' 9(st S,= yo(r role= Conf!"(rat!on ,(rat!on= 3 to ) years -ype= *on" term :(p"ra es<I short term:(p"ra es<I enhancementsI

Know the steps in LSMW What is SAP LSMW ?


Posted on January 7th, 2011
-he 3SM Wor0&ench !s an tool that supports the transfer of data from non*SAP systems ,N3egacy SystemsO. to SAP ';D systems. -h!s can &e a one=t!me transfer as well as a per!o !c one. *S+W also s(pports conversion of data of the le"acy system !n n(mero(s way. -he ata can then &e !mporte !nto the SAP CI% system /!a batch input+ direct input+ %AP#s or #Docs. 4(rthermore; the *S+ Wor0&ench pro/! es a recor !n" f(nct!on that allows "enerat!n" a Ndata migration ob9ectO to ena&le m!"rat!on from any reB(!re transact!on.

*S+W can &e (se for follow!n" D functions = -he ma!n f(nct!ons of the *S+ Wor0&ench are: 1. #mport data :le"acy ata !n sprea sheet ta&les an Ior seB(ent!al f!les< 2. Convert data :from so(rce format to tar"et format< %. #mport data :!nto the ata&ase of the CI% appl!cat!on< -o start the *S+W wor0&ench (se transact!on 3SM @o( m!"ht l!0e: ,!alo" Pro"ramm!n" -(tor!al What !s a >ar!ant *S+W ,ata +!"rat!on V Step &y Step All A&o(t Smart 4orms All A&o(t I,#C:,ef!n!t!on; Arch!tect(re; Implementat!on emplate to create a scr!pt

Ynow CIC74=Ceports; Interfaces; Con/ers!ons; 7nhancements an 4orms What !s the wor0 l!fe &alance?

How o yo( "(ys mot!/ate?

'#C&: Ob9ects on SAP Pro9ects


CIC74 represents the e/elopment o&9ects that nee to &e es!"ne an &(!lt on a SAP !mplementat!on to meet the &(s!ness reB(!rements. CIC74 !s an acronym for Ceports; Interfaces; Con/ers!on; 7nhancements an 4orms respect!/ely. It has also been re erre! as "RICE or RICE"# $%ith # or SAP #or& lo%'( -ra !t!onally QCeportsQ !n CIC74 (se to represent A2AP reports :A*>; 2atch; s!mple o(tp(t or !nteract!/e< &(t w!th the a !t!on of 2I an 2(s!ness #&9ects; SAP c(stomers ha/e &een !ncl( !n" these transact!onal an analyt!cal reports also as Reports. Same appl!es for QInterfacesQ !n CIC74. It (se to represent SAP !nterface technolo"!es s(ch as A*7; I,#C; etc &(t now a ays SAP systems !nte"rators !ncl( e e8ternal as well as !nternal SAP an non=SAP system !nterfaces to a/o! conf(s!on for the SAP c(stomer. -he o(tp(t of the pro9ect &l(epr!nt phase !s the SAP Solution Inventory wh!ch compr!ses of the CIC74 o&9ects to"ether w!th conf!"(rat!on !tems. It !s /ery !mportant to (n erstan each sol(t!on "ap an properly class!fy the same as e!ther a report; !nterface; con/ers!on o&9ect; enhancement; form or a wor0flow.

'eports
Ceports can !ncl( e class!c A2AP pro"rams that pro (ces s!mple o(tp(t or A2AP pro"rams w!th comple8 !nteract!/e (ser !nterface /!a A*> pro"ramm!n" or other mo ern techn!B(es. -hese reports may &e tr!""ere (s!n" a c(stom transact!on co e; A2AP 7 !tor :se%1<; A2AP Wor0&ench :transact!on se15< or /!a a &ac0"ro(n 9o&. Cons! er enhanc!n" the stan ar el!/ere SAP reports /ers(s &(!l !n" new reports from scratch. If yo( are e/elop!n" m(lt!ple reports w!th s!m!lar!t!es; then cons! er &(!l !n" one ro&(st report w!th ynam!c APIs an !fferent report /ar!ants to a/o! (pl!cat!on of es!"n an &(!l effort. We recommen that yo( 0eep the A2AP reports separate from the SAP 2I operat!onal an analyt!cal reports. SAP Project anager ! "#C$% De&elopment anager) Reports can be !esigne! an! built by ABAP !evelopers %ho are not e*perience! in speci ic SAP mo!ules client is implementing( +his may help you balance your ABAP resources %ell an! reserve the more &no%le!geable senior resources or enhancements %hich most o ten re,uires e*pertise %ith the SAP mo!ule( Assign simple reports to -unior !evelopers an! have your senior ABAP !evelopers %or& on reports that have comple* user inter ace. processing logic or heavy on !ata processing %hich may re,uire heavy ocus on architecture an! per ormance(

#nterfaces
Interface !ncl( es all the e/elopment an conf!"(rat!on o&9ects that allows !nternal as well as e8ternal SAP an non=SAP systems to comm(n!cate w!th each other. What "ets !ncl( e !n the CIC74 !n/entory has e/ol/e o/er t!me. #r!"!nally !t (se to &e !n str!ct A2AP conte8t wh!ch !ncl( e A*7; I,#C; 7,I an C4C ena&le comm(n!cat!ons. Aowa ays w!th e/ol(t!on of SAP PI o/er the years an to a/o! term!nolo"y conf(s!on for a SAP c(stomer; all the SAP systems !nte"rat!on !ncl( !n" e=S#A :Ser/!ce 7na&le Arch!tect(re< comm(n!cat!on; th!r party I e8ternal systems !nte"rat!on; we& !nterfaces; etc that are mana"e &y SAP PI are co(nte as CIC74 inter ace o&9ects. -a0e !nto cons! erat!on all e8ternal systems that (se a s!n"le &(s!ness process w!th!n 7CC system so that effort to re=en"!neer an re es!"n the &ac0en operat!on !s m!n!m!$e . ,ata /ol(me also plays a ma9or role !n ec! !n" the !nterface type an !ts es!"n for opt!mal performance. ,(r!n" the &l(epr!nt yo( sho(l meet w!th the &(s!ness S+7 an (n erstan the normal ata /ol(me as well as pea0 /ol(mes. Cemem&er that we are eploy!n" the SAP system to s(pport &(s!ness "rowth an as s(ch ata /ol(me pro9ect!on for 15=1) years !nto the f(t(re sho(l &e cons! ere . Any chan"es to an !nterface or (n erly!n" &(s!ness process sho(l &e followe &y thoro("h en =to=en test!n" of ent!re !nterface to ens(re that o(tp(t; performance an ata han l!n" st!ll a here to the es!"n. SAP Project anager ! SAP P# 'ead) /n most pro-ects no% a !ays the systems integration $PI' %or& is mostly outsource!( Ensure that you have senior SAP PI architects %or&ing onsite !irectly %ith the client SME( Blueprint re,uirements gathering %or& shoul! !e initely be !one at customer location( #e highly recommen! that these onsite PI architects an! senior consultants !esign the large an! comple* inter aces by !irectly %or&ing %ith business teams( +he buil! an! testing can be assigne! to the o shore team %ith at least 1)0 ratio bet%een senior PI architect an! consultants( +his %ill ensure that business gets a ,uality pro!uct an! you have the best resources rom SI %or&ing !irectly %ith the client %hile maintaining the cost e ectiveness using the o shore mo!el(

Conversion
Here we !ncl( e all SAP 1ata Conversion o&9ects wh!ch are reB(!re to loa the ata from cl!ent le"acy systems !nto yo(r f(t(re state SAP system. It !ncl( es A2AP e/elopment an conf!"(rat!on tas0s w!th SAP tools an technolo"!es that s(pport ata con/ers!on l!0e 2,C pro"ramm!n"; ,!rect Inp(t :,I< pro"rams; *S+W :*e"acy System +!"rat!on Wor0&ench<; Comple8 A2AP pro"ram to s(pport ata loa ; -ransfer Wor0&ench; 2API; etc. 2(!l !n" a ata con/ers!on strate"y; ata e8tract!on an cleans!n" plan are not !ncl( e !n the CIC74 !n/entory an sho(l &e a resse separately on the SAP pro9ect &y yo(r ,ata Con/ers!on *ea .

Some systems !nte"rators :an o(tso(rce /en ors< &(!l s!mple A2AP pro"rams to loa le"acy !rectly !nto SAP ata&ase ta&les w!th !rect !nserts an (p ates. DO ?O$ 3OAD DA$A D#'&C$3M #?$O SAP DA$A%AS& ,DD#C.. 2eca(se the ata from yo(r le"acy system sho(l systemat!cally enter the SAP system as !f the (ser was man(ally enter!n" !t (s!n" the stan ar SAP transact!ons. All &(s!ness an (ser !np(t /al! at!ons nee to occ(r &efore the ata !s s(ccessf(lly comm!tte to the ata&ase. We recommen that yo( ha/e a CIC74 lea represent!n" the SAP c(stomer who w!ll per!o !cally re/!ew the ata loa pro"rams an strate"!es to a/o! (nforeseen !ss(es (r!n" &(s!ness m!"rat!on. SAP Project anager ! SAP Data Con&ersion 'ead) Ma&e sure your pro-ect %or& plan inclu!es prototyping o !ata loa!s in the san!bo* to vali!ate the cleansing o !ata e*tracte! rom legacy system( Most li&ely you %ill be able to use stan!ar! APIs or ABAP classes to create or mo!i y the business ob-ects that you nee! to loa!( Some o these ob-ects may have been built as RICE" enhancements( Ma&e sure you reuse them be ore buil!ing rom scratch( 1e ine milestones an! !epen!encies bet%een legacy !ata e*traction. trans ormation. prototype. trial loa!s an! inal loa!s(

&nhancements
Enhancements !ncl( e all mo !f!cat!ons to SAP stan ar el!/ere pac0a"e components s(ch as the (ser !nterface; system processes an o(tp(t to meet &(s!ness reB(!rements of an SAP c(stomer. +o !f!cat!ons to stan ar el!/ere &(s!ness processes are most often !mplemente (s!n" (ser e8!ts or &(s!ness a =!ns :2A,I<. Somet!mes enhancements can !ncl( e c(stom e/elope stan alone transact!ons or &(s!ness processes. #n pro9ects where c(stom e/elope SAP sol(t!on scope :!ncl( es new ,,IC; appl!cat!on layer an UI< !s s!"n!f!cant; a new wor0 stream e !cate to SAP C(stom ,e/elopment may &e !ntro (ce . #therw!se c(stom e/elopment o&9ects can &e !ncl( e as enhancements. SAP Project anager ! SAP "#C$% 'ead nee! to ma&e sure that you have a %ell balance! team o ABAP !evelopers %or&ing on enhancements( Architects an! senior !evelopers must have prior e*perience %ith speci ic mo!ules implemente! on the pro-ect as it is very important that they have soun! e*pertise about all available user e*its. BA1Is. 11IC ob-ects. etc that can be enhance!( +he comple* enhancements shoul! be !esigne! an! !evelope! by senior SAP ABAP !evelopers( I using a o shore mo!el. you pro-ect shoul! have at least 1)2 ratio bet%een these senior !evelopers3architects an! other ABAP resources( At least a thir! o these architects shoul! be present onsite to e ectively communicate an! %or& %ith the business teams(

:orms
"orms refer to str(ct(re ata that nee s to &e presente as o(tp(t wh!ch are stan ar !$e &y the &(s!ness or &y e8ternal re"(latory ent!t!es. 4orms that are reB(!re for &(s!ness

operat!ons !ncl( e !n/o!ces; p(rchase or ers; pol!c!es; etc. 78ternal forms that an SAP c(stomer may nee to a opt !ncl( e compl!ance reports; ta8 f!l!n" forms; state re"(latory reports; etc. 4orms can &e &(!lt (s!n" SAPscr!pt; Smart 4orms; A o&e 4orms :also A o&e Interact!/e 4orms< or +S #ff!ce Inte"rat!on. In the recent years; A o&e forms an +S #ff!ce Inte"rat!on forms are &ecom!n" more pop(lar &eca(se &oth are (ser fr!en ly :easy to create<; easy pr!nt!n" capa&!l!t!es an &oth are !nte"rate w!th the A2AP wor0&ench. #n almost e/ery SAP pro9ect we ha/e seen set of forms wh!ch compr!se of 15U common ata w!th 25U /ar!at!on epen !n" on the rec!p!ent or &(s!ness conte8t. Systems !nte"rator often o(&le co(nt these o&9ects there &y !ncreas!n" yo(r pro9ect est!mates. I recommen that one form sho(l &e co(nte as comple8 o&9ect that w!ll !ncl( e the process!n" lo"!c an layo(t wh!ch w!ll &e (se as &as!s for other /ar!at!ons. All other forms sho(l &e co(nte as very lo%. lo% or me!ium comple8!ty epen !n" on mo !f!cat!ons to layo(t an process!n" lo"!c. SAP "#C$% 'ead shoul! be concious o the types o orms that %ill be implemente! on your pro-ect( Analy4e the types o orms that %ill be implemente! as ,uic&ly as possible !uring the blueprint as you %ill nee! to onboar! ABAP !evelopers an! technical consultants %ith e*perience in either SAPscript. Smart "orms. A!obe "orms or MS /I( Ma&e sure you have !evelopers %ho have prior e*perience %ith speci ic orms( 1)0 is a goo! ratio bet%een Architect an! !evelopers %or&ing on RICE" "orms(
-ransact!on ransact!on ransact!on ransact!on Co e Co e Co e Co e

6;KD Create Condition $able 6;K= Change Condition $able 6;KF Display Condition $able 6;K6 Create;Change E Display Condition $ype 6;KG Create;Change E Display Access Se8uence 6;KI Create;Change E Display Pricing Procedure 67HH Create Condition 'ecord 67H< Change Condition 'ecord 67HD Display Condition 'ecord O67P Define Customer Pricing Procedure O67# Define Document Pricing Procedure O67P Assign Document Pricing Procedure to Order $ype O6$P Assign Document Pricing Procedure to %illing $ype O677 Define Pricing Procedure Determination O6S# Define Price 3ist Categories :or Customer O6S3 Define Pricing 4roups for Customer O6SP Define Material 4roup O6DH Define Condition &-clusion 4roup H. hat is the purpose of te-t determination+ account determination+ partner determination+ output determination+storagelocation determination Ans!erH/ -e8t eterm!nat!on: 4or transferr!n" !nformat!on from mater!al or c(stomer to

or erI el/ery or !n/o!ce :an anyth!n" !n&etween< Acco(nt eterm!nat!on: 4or transferr!n" f!nanc!al an cost!n" !nformat!on to proper f!nanc!al ocs Partner eterm!nat!on: 4or eterm!n" who !s !s le"ally respos!&le for AIr; who the "oo s are "o!n" to an whate/er else yo( waana r!/e thro("h th!s f(nct!onal!ty. #(tp(t eterm!nat!on: What 0!n a o(tp(t oes a salesI el!/eryI&!ll!n" oc(ment create an who "ets !t; where?. 4or e8ample A partner m!"ht "et an 7,I not!f!cat!on for a sales or er 9(st conf!rme ; whereas a f!nanc!alIleas!n" company "ets the !n/o!ceJ Ans!er</ :a< -e8t ,eterm!nat!on: Any -e8ts !n +aster!al +asterI+ater!al ,eterm!nat!onI#r erI,el!/ery ; etc !s meant to con/ey messa"es to the s(&seB(ent oc(ments for compl!ance. e.". Q6!/e -op Pr!or!tyQ messa"e ment!one !n #r er !s meant for Pro (ct!on ,ept. :&< Acco(nt ,eterm!nat!on:!s !nte"rat!on &etween 4!nance an S,. -he AIP alon" w!th Acco(nt Yeys nee to &e allocate accor !n"ly w!th com&!nat!on of Acco(nt ,eterm!nat!on 6ro(p for C(stomer an +ater!al !f reB(!re . :c< Partner ,eterm!nat!on:-o ! ent!fy wh!ch type of Partner !t !s so that !f reB(!re for same C(stomer !fferent Partner 4(nct!ons may &e reB(!re e." #nly #ne Sol -o Party per C(stomer. +ore than #ne Sh!p to PartyI 2!ll to PartyI Payer poss!&le. Accor !n"ly !fferent +asters w!ll ha/e to &e create . Usef(l for espatch of +ater!al !n casae of Sh!p to Party; sen !n" 2!ll !n case of 2!ll to Party an payment follow(pI,(nn!n" !n case of Payer. : < #(tp(t ,eterm!nat!on: What type of #(tp(t :4a8I+a!l; etc< !s reB(!re ; where an !n what 4ormat:A2AP C(stom!sat!on may &e reB(!re !n some cases espec!ally In/o!ces<. :e< Stora"e *ocat!on ,eterm!nat!on: epen s on Plant; Sh!pp!n" Po!nt an Stora"e Con !t!ons <. hat are the five imp fields to be maintained in account determination Acco(nt ,eterm!nat!on: Sales >!ew; Sales #r"an!$at!on; ,!str!&(t!on Chanel; Chart of Acco(nts; Acco(nt Ass!"nment 6ro(p for C(stomer an +ater!al an Acco(nt Yeys. =. hat is meant by transfer of data from legacy code to sap 3egacy Code " Ans!erH/ It sho(l &e le"acy ata to SAP. What !t means !s yo( want to transfer all the c(stomer an mater!als an all other !nformat!on from #l er :le"acy system< to new SAP system. @o( can o !t (s!n" many tools; most not!cea&ly +,+s. Ans!er</ 2efore !nstallat!on of SAP; ,ata ma!nta!ne &y Company !s calle *e"acy ,ata. At the t!me of !nstallat!on; !t !s reB(!re to transfer ,ata from *e"acy to SAP l!0e +asters :+ater!alIC(stomer; etc<. It can &e one !n /ar!o(s ways l!0e 2,C; *S+W; etc. F. hat do you do really in pricing determination+ and !hat are the main differences bet!een pricing procedures"

Ans!erH/ Pr!c!n" !s eterm!ne &y com&!nat!on of Sales #r"an!$at!on; ,!str!&(t!on Channel; ,!/!s!on; C(stomer Pr!c!n" Proce (re an ,oc(ment Pr!c!n" Proce (re. Ans!er</ We eterm!ne how the pr!ces are calc(late ; ta0!n" !nto acco(nt sales area:sales or"; !str!&(t!on channel; !/!s!on<; oc(ment type an c(stomer:"enerally sol =to=party<. -he ma!n !fferences &etween pr!c!n" proce (res wo(l &e the !fferences as we ment!one a&o/e; from the po!nt of /!ew of f!el entr!es. Com!n" to the o(tp(t an the proce (re; s(ppose the con !t!on types (se w!ll &e !fferent an hence the follow!n" whole proce (re. #ne pr!c!n" proce (re eterm!nat!on to the others; wh!ch ata control these !fferences 6. hat type of reports generally a support consultant maintains and report epen s on C(stomer reB(!rements. G. hat are interfaces used generally an #ndian organization !hich is in retail business and !hich is in ban)ing business and oil business. I. hat is the purpose of shipping point determination not menu path So that Sh!pp!n" Po!nt !s eterm!ne a(tomat!cally once the sett!n"s for the same are one. J. hat and !here types of copy control !e change Copy Control: !s &as!cally meant so that ,ata !s cop!e from prece !n" ,oc(ment to s(&seB(ent one. What s(&seB(ent ,oc(ment !s reB(!re !s to some e8tent eterm!ne &y C(stomer CeB(!rements as well as ,oc(ment -ypes. e.". In "eneral case of Stan ar #r er; !t w!ll &e Copy Control :#r er to ,el!/ery< from #C to *4 . HK. 5o! to and !here to maintain copy controls Chec0 for yo(rself !n I+6 :Sales ,oc(ment types an ,el!/ery ,oc(ment -ypes< HH. hat is purpose of maintaining common distribution channels and common divisions Common ,!str!&(t!on Channel an Common ,!/!s!on are ma!nta!ne so that !f any master ata l!0e c(stomer or mater!al ma!nta!ne w!th respect to one !str!&(t!on channel can &e (se !n other ,Ch. It pre/ents the m(lt!pl!cat!on of master recor s. 7": A c(stomer !s create for say sales area 1555I25I55 then the same c(stomer can &e (se !n sales area 1555I%5I55 !f we ma!nta!n 25 as common !str!&(t!on channel. Hence no nee for e8ten !n" the c(stomers...the same for mater!als also. H<. hat is the difference bet!een the Availability chec) KH ,Daily re8uirement. and K< ,#ndividual 'e8uirement. in material master" 51 an 52 are the chec0!n" "ro(p. A/a!la&!l!ty chec0 !s carr!e o(t w!th the help of these chec0!n" "ro(p an chec0!n" r(le. Chec0!n" "ro(p 51 an 52 are ma!nta!ne on the

mater!al master. 51 = In !/! (al reB(!rement =4or th!s system "enerates transfers the reB(!rement for each or er to the +CP .So that ++ can e!ther pro (ce or proc(re. 52= Collect!/e reB(!rement.=In th!s all the reB(!rements !n a ay or !n a wee0 are processe at a t!me. System stores all reB(!rements an passes on to the +CP !n +CP r(n. In th!s system performance !s h!"h howe/er yo( can not o the &ac0or er process!n" whereas !n other yo( can o.

here is the QShipping ConditionQ maintained in a customer master" Sh!pp!n" con !t!on !s ma!nta!ne !n the sh!pp!n" ta& (n er sales area ata of c(stomer master. -he sh!pp!n" con !t!on !s propose from the sales oc(ment type !f a sh!pp!n" con !t!on has &een ass!"ne to !t. If not; the sh!pp!n" con !t!on !s propose from the master recor of the sol =to party. Shipping conditions are maintained for !hich partner function in customer master" Sh!pp!n" con !t!on !s ma!nta!n !n Sh!p to Party partner f(nct!on : sales area ata ta& === sh!pp!n".< Sh!pp!n" con !t!ons w!ll &e efa(lte from the C+C of SP. If a /al(e e8!sts !n the sales oc(ment type :e". #C< then !t w!ll ha/e pr!or!ty an w!ll replace the /al(e efa(lte from C+C. Does the system ta)es the shipping condition t!ice in search of the route" When the system search for the ro(te !t w!ll search thro("h ro(te eterm!nat!on l!0e th!s: Sh!pp!n" po!ntP:PSales or er<PP an ,epart(re Zone PP:4rom the or er sh!pp!n" po!ntP<PGSh!pp!n" con !t!onP:PC(stomer master wh!ch yo( enter !n the or erP< PG-ransportat!on 6ro(pP:Pfrom mater!al master wh!ch yo( entere !n the or erPP< G est!nat!on $oneP:Ptransportat!on $one of the C(stomer !n the or erPP<==ZCo(te System w!ll eterm!ne the sh!pp!n" po!nt !n the sales or er &ase on these select!on Sh!pp!n" con !t!onsG*oa !n" "ro(pGPlant==ZSh!pp!n" po!nt.

After eterm!n!n" the sh!pp!n" po!nt then only the system w!ll start to search ro(te. 2(t system w!ll not search the sh!pp!n" po!nt wh!le search!n" the ro(te. So sh!pp!n" con !t!ons w!ll not cons! er two t!mes wh!le search!n" the ro(te. hat is the significance of the shipping condition and loading group" 2oth the sh!pp!n" con !t!on an loa !n" "ro(p are (sef(l !n Stoc0 transport or er. 4or the C(stomer ass!"ne to the rece!/!n" Plant; chec0 the ,el!/er!n" Plant !n C(stomer master recor !n R,52 D chec0 the sh!pp!n" po!nt ass!"nment !n #>RC. Sh!pp!n" po!nt w!ll &e eterm!ne only !f !t !s ass!"ne to the plant from the conf!"(rat!on. Sh!pp!n" con !t!on an *oa !n" "ro(p plays a /!tal part for sh!pp!n" po!nt eterm!nat!on . -he com&!nat!on of sh!pp!n" con !t!on :+aster ata of c(stomer I>en or< G *oa !n" "ro(p :mater!al master< G Plant; eterm!nes the sh!pp!n" po!nt. *(c0!ly or (nl(c0!ly; !ncomplet!on lo" oes not !n/ol/e the con !t!on techn!B(e. So; for once; yo( ont nee to learn a&o(t the con !t!on techn!B(e.
WHAT ARE SAP SS ! TES? This is a correction to a defect issue by sap, through changes to codes tables , configuration etc, on line support system use to manage tickets and interactions with clients. SUPP RT "SP# $ac%s on the other hand are a collections or bundles of sap notes. WHAT &S A TRA!SACT& ! C 'E ( S_NOTES SE! "O#. $ transaction code is a four letter command that tells the system location of a task. SNOTE is a S$% transaction that applies $&$% code corrections attached to the OSS Notes. 't is important that SNOTE can apply only the subset of corrections.

#ntervie!ed Dec <KHH in ?e! Mor)+ ?M ,too) D !ee)s.


I "ot a phone !nter/!ew from 7rnst D @o(n" after clear!n" the res(me screen!n" at the (n!/ers!ty. -he phone !nter/!ew was &eha/!oral an most of the B(est!ons were &ase on &(s!ness an lea ersh!p s0!lls. 4ew B(est!ons were 1< tell me a&o(t yo(rself 2< -echnolo"!es ! ha/e wor0e on %< a&o(t pro9ects &as!cally more a&o(t my res(me B(al!f!cat!ons

-hen; !n the one on one !nter/!ew ! ha % ro(n s 2 &eha/!oral an 1 case !nter/!ew -he &eha/!oral B(est!ons were 1< tell me a&o(t yo(rself 2< why 7 D @ %< Some h!"hl!"hts from my res(me = they wante to hear more a&o(t !t '< ,!ff!c(lt s!t(at!on ! ha to face when ! was !n a team an how ! o/er came !t )< +y stren"ths an wea0nesses ?< When I ha to tell someth!n" &a or stern to a team mem&er w!tho(t ma0!n" them feel &a .< -o("h s!t(at!on as a team lea er an how ! o/er came !t 1< lea ersh!p scenar!os 3< As a comm(n!cator; &(s!ness analyst 15< Some ach!e/ement !n yo(r wor0 place that yo( are really pro( of == +a0e th!s answer a sell!n" po!nt. Case !nter/!ew :

What o yo( cons! er yo(r ma!n wea0ness? -h!s B(est!on may &e as0e (r!n" an !nter/!ew at 7D@ to raw o(t any flaws yo( may har&or that can affect the B(al!ty of yo(r wor0. Howe/er; say!n" yo( ha/e a r!n0!n" pro&lem or an"er mana"ement !ss(es !s a s(ref!re way to &e!n" 0!c0e as! e. A "oo way to answer th!s tr!c0y B(est!on !s to state a [wea0nessS wh!ch can &e ta0en !n a pos!t!/e way &y employers. 4or !nstance say!n" that yo( feel yo( can &e a &!t too !plomat!c at t!mes can show employers that yo( can wor0 well w!th people !n a /ar!ety of s!t(at!ons. Q: Where o yo( see yo(rself !n ) years? So(n s cl!ch\ oesnSt !t? ,onSt (n erest!mate th!s B(est!on tho("h. ItSs always as0e (r!n" !nter/!ews to 9( "e whether yo( ha/e plann!n" s0!lls or prefer to "o where the w!n ta0es yo(. @o( may &e that !n !/! (al who ta0es l!fe !n yo(r str! e; &(t yo( sho(l ne/er let yo(r f(t(re employer th!n0 yo( are. Cefra!n from reply!n" !n the ne"at!/e !f yo( onSt want to rema!n (nemploye . A "oo way to answer th!s tr!c0y B(est!on !s to !mply that yo(r lon" term plans epen on the company yo(Sre !nter/!ew!n" for. If the off!ce yo(Sre !nter/!ew!n" for has a "row!n" &ase of cl!ents !n the enterta!nment !n (stry; then yo( sho(l say yo( are !ntereste !n spec!al!$!n" !n the enterta!nment !n (stry ser/!ce l!ne. -h!s way; &oth yo( an the employer w!ll en (p smell!n" l!0e roses. @o( sho(l !ncl( e 7rnst D @o(n" !n yo(r response; as th!s !s an 7D@ !nter/!ew B(est!on (r!n" yo(r 7rnst D yo(n" !nter/!ew. Hopef(lly yo( ca("ht on &y the re (n ancy how !mportant !t !s to ha/e yo(r f!rm !n yo(r )=year f(t(re.

Q: What was the reason for lea/!n" yo(r last 9o&? 2e e8tremely caref(l &efore answer!n" th!s B(est!on. A wron" answer may "et yo( shown the oor s!nce th!s B(ery has se/eral connotat!ons &eh!n !t. If yo( say that yo( left yo(r pre/!o(s 9o& &eca(se of a ser!o(s flaw or wea0ness !n yo(r own personal!ty; !t may "!/e employers an o/erall &a !mpress!on of yo(. If; on the other han ; yo( en (p &a mo(th!n" yo(r pre/!o(s &oss; yo( may en (p loo0!n" l!0e a m(l!shly st(&&orn !n !/! (al; who may not wor0 well w!th others. -he &est way to answer th!s to("h coo0!e !s to !mply that yo(r last 9o& wasnSt challen"!n" eno("h for yo(. hat are some other 8uestions that you are nervous about going your &EM #ntervie!" *et (s 0now &y lea/!n" !t !n the comments &elow an we w!ll e!ther e8pan th!s post or ma0e a new post w!th how to &est answer the B(est!on.

,o yo( ha/e any B(est!ons yo( want to as0 me?OWOAoWO So(n fam!l!ar? -h!s B(est!on an conseB(ent answer !s one of the worst th!n"s that can happen at the en of a &!" ' !nter/!ew. -h!s !s a B(ery wh!ch w!ll &e repeate !n e/ery 9o& !nter/!ew yo( s!t for e/en !f yo( are &e!n" "r!lle &y m(lt!ple employers. A s(ccessf(l acco(nt!n" !nter/!ew w!th top employers l!0e YP+6; ,elo!tte; PWC; an 7D@ can "o so(r real B(!c0 !f the recr(!ter th!n0s that yo(Sre not conf! ent eno("h to as0 rele/ant B(est!ons. -h!s B(est!on !s a "ol en opport(n!ty offere &y employers to mostly (ns(spect!n" potent!al employees to chec0 the!r conf! ence le/el an e"o. 2efore sett!n" off for a &!" ' !nter/!ew; ma0e s(re yo( ha/e at least some of the follow!n" B(est!ons !n m!n that yo( may as0 (r!n" or after the !nter/!ew: H. hat do you thin) sets your company apart" hy you should as) this 8uestion/ -h!s B(est!on sho(l &e as0e as spec!f!cally as poss!&le an as !mpress!/ely as yo( can. 4or e8ample !f yo( are apply!n" for an a( !t!n" pos!t!on at ,elo!tte; yo( can as0 the B(est!on th!s way: NWhat separates yo(r a( !t!n" metho olo"y an techn!B(es (se from those employe at 7D@; PWC; an YP+6.O Aot only w!ll th!s show that yo( !ntereste !n the spec!f!cs of the pos!t!on; !t h!nts that yo( may &e !ntereste !n other f!rms. @o( are as0!n" them to show how they stan o(t. <. 5o! fre8uently do you hire in this position" Or/ no!" hy you should as) this 8uestion/ hy is this position available

-h!s B(est!on w!ll clar!fy what the prospect!/e company has !n m!n when loo0!n" for or f!r!n" employees. -he a/a!la&!l!ty co(l &e &eca(se yo(r pre ecessor was let "o or B(!t on h!sIher own. 2e!n" !n the 0now re"ar !n" the c!rc(mstances of the!r epart(re w!ll ens(re that yo( onSt ma0e the same m!sta0es they ! . D. hat are the different career advancement opportunities your company offers" hy you should as) this 8uestion/ As0!n" th!s B(est!on w!ll ass(re employers that yo(Sre ea ser!o(s a&o(t wor0!n" for them an yo(r career. Any of them w!ll &e more than happy to h!re someone who !s as respons!&le as th!s B(est!on presents h!mIher to &e as lon" as they ha/e the opport(n!ty to 0eep yo( w!th them wh!le yo(Sre cl!m&!n" their corporate la er. -he answer yo( rece!/e w!ll also eterm!ne whether yo( sho(l stay w!th them or 0eep loo0!n" for &etter prospects.

Other %ig = #ntervie! Luestions you may as)


S(!ta&le B(est!ons yo( may as0 (r!n" the !nter/!ew can !n/ol/e yo(r 9o& respons!&!l!t!es an also ma0e s(re to as0 them for clar!f!cat!on re"ar !n" anyth!n" yo( ! nSt (n erstan . Wor to the w!se; as0!n" !f yo( can colla&orate w!th others can show yo(r employers what a respons!&le an e !cate employee yo( can &e. -eamwor0 !s one !f not the most !mportant 9o& reB(!rement many employers loo0 for when they hol acco(nt!n" !nter/!ews or any other !nter/!ews.
(. )hich components are used in a Sales $rea? Sales 'ivision rgani)ation 'istri*ution Channel

*. )hat is the relationship between plant and Sales $rea? Many to Many +. )here might it be useful to set up loading points? 'n the Material Master ,. -ow does the account group influence the screen selection? Account +rou$ control the screen and ,ields required to -aintain data ,or each custo-er *ased on custo-er.s role/ .. )hat do you ha/e to do in order to use a customer with se/eral sales areas? Create the custo-er using 0'12 0. !iscuss a useful scenario where different company code /iews are re1uired2 3. !escribe possible differences between #O- and -$)$ materials. R H is ra3 -aterial and HAWA is trading goods 4. )hat are the main functions of Sales and !istribution? To $rovide goods and service to custo-er ((. )hich kinds of 5aster !ata e6ist in S!? Custo-er4 Material4 Condition Master4 out$ut Master.

(*. 7ist the t8codes for creating, changing and displaying in1uiry, 1uotation, sales order, deli/ery, shipment, shipping cost document and &illing document ? &nquiry VA224VA254 VA264 7uotation VA524VA554VA564Salse rder VA124 VA154 VA164 'elivery VL12!4 VL15!4 VL16!4 shi$-ent VT12!4VT15!4 VT16! 4 Shi$$ing Cost 'ocu-ent V&12!4 V&15!4 V&16! 8illing V9124 V9154 V916 (+. )hat is the basic structure of a sales document? Header4 &te- and Schedule line (,. )hat are the control functions of the sales document type? (.. Name three important sales document types2 'n1uiry, Sales Order, !eli/ery and &illing (0. )hat is the difference between cross di/ision and di/ision specific sales? )here is this !efined? 8 at item le/el or at header le/el? (3. )hat does the item category control? 'tem category control %ricing, billing Schedule line and deli/ery, 5#%
0 at $oes t e item !ategor, !ontrol1 General Data

Should pricing be carried out for the item? )hen should an item be regarded as completed? $ 1uotation item, for e6ample, can only be regarded as completed if the entire 1uantity has been copied into a sales order. 's it an item that refers to a material or is it a te6t item? $re schedule lines allowed for the item? 5ay general business data, for e6ample, the terms of payment at the item le/el, de/iate from Those at the header le/el? Should a system message appear if the item cannot be fully deli/ered? )hich fields are rele/ant for the incompletion log? )hich partner functions are allowed at the item le/el and which are mandatory? )hich output 9for e6ample, an order confirmation: is allowed for the business transaction and )hich output determination procedure is used?

!a-e at least three ite- categories( Standard 'tems; $"N, $<N, T$N. "ree of charge 'tems; $"NN, $<NN, T$NN. Non=stock 'tems; $">, $<>, T$>. Te6t 'tems; $"T>, $<T>, T$T>.
&TEM CATE+ R&ES: o o SE ? T@O!E ? AOA, 9$ssign 'tem @ategories B '5<, SC!, Sales, Sales !oc, Sales !oc 'tem, $ssign 'tem @ategories: 5% ?@onfigure; '5<, SC!, Sales, Sales !oc, Sales !oc 'tem, !efine 'tem @ategories T$NBStandard 'temD T$NN8"ree of @harge 'temD T$>8Ser/ice 'temD Stock 'tem, Non8Stock 'tem, T$T>8Te6t 'tem, !ocument 'tem, @lass 'tem, 'ntra 5aterialD !'EN8Ser/ice 'tem

-he system (ses the !tem cate"ory "ro(p f!el of the mater!al master recor as the ma!n !n !cator to eterm!ne the !tem cate"ory !n the sales or er.
(E. -ow is the item category determined? (4. )hat does an in1uiry re1uest refer to? *F. )hat does a 1uotation define? *(. $re in1uiry and 1uotation both legally bound documents? No **. @an a 1uotation be used as a reference for subse1uent documents? Ges *+. )hat documents can be used as a reference for a sales order? &nquiry4 7uotation *,. )hat are the four mandatory partner functions? Sold to4 shi$ to4 *ill to4 Payer Party *.. )hich header and item partner may not differ? )hy? *0. )hat information does the headerHitem area of the sales order transaction contain? *3. )hat organiIational unit are shipping points assigned to? Plant

*E. -ow is the shipping point determined by S$%?


2o) $oes t e s,stem $etermine t e s ipping point an$ t e route in t e sales or$er1

$ shipping point can be determined for each order item. -ow the shipping point is determined depends On three factors; The shipping conditions from the customer master record 9Shipping screen:. $ condition might be that The goods are to be deli/ered to the customer as soon as possible. The loading group from the material master record 9SalesH%lant !ata screen:.Gou could, for e6ample, specify a loading group that defines that the goods must always be loaded with a crane or a fork lift. The deli/ering plant. This plant is determined per order item either from the customer master record or from the material master record. -owe/er, you can also enter it manually for each order item. Gou will find detailed information on determining the deli/ering plant in the sales order in the #H+ S! online documentation on sales.

Which organi)ational ele-ent is central in shi$$ing( +ive a de,inition o, it/ Shipping Point' Organi6ational unit at a fixed location that carries out shipping
activities A shipping point could, for example, be a company3s mail department or a plant3s rail depot 7ach delivery is processed by only one shipping point

Can you further subdivide a plant? If yes into what? $ plant can be subdi/ided into storage locations, allowing stocks of materials to be broken down

$ccording to predefined criteria, 9e.g., location and materials planning aspects:. $ plant can be subdi/ided into locations and operational areas. Subdi/ision into locations takes geographical criteria into account, whereas subdi/ision into operational areas reflects responsibilities for production.
*4. True or false; E/ery outbound deli/ery document is assigned to one shipping point. True +F. )hich steps are parts of the shipping process? !eli/ery @reation, %icking, %acking, Shipment and <oods 'ssue +(. )hat deli/ery /ariants e6ist in S$%? +*. 's any configuration necessary to allow certain deli/ery /ariants? 'f yes, where is this to be? @onfigured? ++. E6plain manual 9single, multiple: and automatic deli/ery creation2 +,. )hat information does the headerHitem area of the deli/ery transaction contain? +.. )hat is the purpose of document copy control in S$%? -ow does it work? +0. -ow is the item category proposed for an order8independent deli/ery document? +3. )hat do the picking process H the packing process include? +E. )hat types of packing e6ist in S$%? +4. )hat is re1uired to post a goods issue? ,F. )hat effects does a goods issue ha/e? ,(. True or false; &illing documents are usually created without any reference. 9alse ,*. )hat does the term Jdeli/ery8related billingK mean? Creating a delivery docu-ent *e,ore creating a *illing docu-ent ,+. )hat are the three types of billing? rder related4 delivery related4 inter;co-$/ *illing

,,. )hat are the control functions of the billing document type? ,.. E6plain the purpose of the Jpricing updateK functionality of the in/oice creation transaction2

Pr!c!n" !s one &ase on pr!c!n" proce (re; con !t!on type; access seB(ence; an con !t!on ta&le an con !t!on recor
,0. E6plain pricing in S$% using the following terms; Se1uence, condition type, and pricing procedure. ,3. )hat are the three influencing factors to determine the pricing procedure in S$%? ,E. E6plain what a sales document is and its basic structure2

,4. !escribe the sales process2 .F. Name the standard sales document types for each phase of the sales process2 .(. !escribe the document flow within the sales process2

'%.*!st % el!/ery types:


o

Complete ,el!/ery= -he system w!ll only conf!rm a el!/ery ate on a ate when the ent!re sche (le ; or ere B(ant!ty for that l!ne !n the sales or er !s a/a!la&le. Part!al ,el!/ery= one or er= 2 el!/er!es #r er Com&!nat!on= com&!ne or ers= 1 el!/ery Cons!"nment

o o o

What are c(to/er act!/!t!es? Answer: C(to/er act!/!t!es are those act!/!t!es that nee to &e complete pr!or to "o l!/e !n or er to ha/e a s(ccessf(l "o l!/e. -hese are the none transporta&le !tems that nee s to &e ma!nta!ne !rectly !n pro (ct!on th!n"s l!0e pr!c!n" con !t!on recor ; ro(te eterm!nat!on recor ; mater!al ata loa ; sh!pp!n" po!nt eterm!nat!on loa . *S+W !s (se here
S34' 0 at is an a!!ount group1

SA3: Screen an f!el select!on !n the c(stomer master recor are controlle &y the acco(nt "ro(p.
S356' 0 at are some e(amples o& a!!ount groups1 -an ne) a!!ount groups %e !reate$1

SA15: 1.< Sol =to party; Payer; 2!ll=to party; #ne=t!me c(stomer 2.< @es.
S355' Please provi$e e(amples o& parameters !ontrolle$ %, t e a!!ount groups7

SA11: 1.< -he !nter/al for the acco(nt n(m&ers 2.< Whether the n(m&er !s ass!"ne !nternally &y the system or e8ternally &y the (ser :type of n(m&er ass!"nment<. %.< Whether !t !s a one=t!me acco(nt. '.< Wh!ch f!el s are rea y for !np(t or m(st &e f!lle when creat!n" an chan"!n" master recor s :f!el stat(s<
S38' 2o) $oes t e s,stem $etermine t e !ompan, !o$e ) en a %illing $o!ument is !reate$1

SA): 2ase on the sales or" !n the or er. A sales or" can &e l!n0e to only one company co e.
S3.' Brie&l, e(plain t e relations ip %et)een sales organizations an$ !ompan, !o$es7

SA': -he sales or"an!$at!on !s an or"an!$at!onal (n!t w!th!n lo"!st!cs that str(ct(res the company accor !n" to !ts sales reB(!rements. It represents the sell!n" (n!t as a le"al ent!ty. It !s respons!&le for pro (ct "(arantees an other r!"hts to reco(rse; for e8ample. 7ach sales or"an!$at!on !s ass!"ne e8actly one company co e for wh!ch yo( enter all acco(nt!n" eta!ls of the sales or"an!$at!on.
S359' 0 at is t e purpose o& !op, !ontrol1

SA11: Copy control !n sales or er process!n" !s (se &y the system to eterm!ne what oc(ment types; !tem cate"or!es; an sche (le l!ne cate"or!es may &e cop!e !nto each other.
S354' Please provi$e e(amples o& $i&&erent t,pes o& !op, !ontrol7

SA13: 1.< 4or Sales ,oc(ments ] contracts; B(otes; an or ers. 2.< 4or ,el!/ery ,oc(ments ] from sales or er to el!/ery %.< 4or 2!ll!n" ,oc(ments ] sales or er relate &!ll!n" or el!/ery relate &!ll!n".
S3:' 0 at is t e !ustomer material in&ormation re!or$ use$ &or1

SA?: ,ata on a part!c(lar mater!al !s ef!ne for one spec!f!c c(stomer !s store !n the c(stomer mater!al !nformat!on recor s.
S3;' Please provi$e e(amples o& &iel$s store$ on t e !ustomer material in&ormation re!or$1

SA.: C(stomer=spec!f!c: mater!al n(m&er; mater!al escr!pt!on; ata on el!/er!es an el!/ery tolerances; te8t.
S35;' 2o) is t e Item -ategor, $etermine$ on an or$er1

SA1.: -he system (ses the !tem cate"ory "ro(p f!el of the mater!al master recor as the ma!n !n !cator to eterm!ne the !tem cate"ory !n the sales or er.
S35<' Please provi$e e(amples o& t)o spe!i&i! &iel$s &rom t e material master t at are use$ on t e or$er7

SA12: +ater!al 6ro(p; Pro (ct H!erarchy; Pr!ce reference mater!al; Plant; Item cate"ory "ro(p
S35+' Please $es!ri%e o) t ese material master &iel$s are use$ on t e or$er7

SA1%: 1.< +ater!al "ro(p !s &as!cally (se !n Pr!c!n". -he +ater!al "ro(p 1; 2; %; '; ) are (se for stat!st!cal p(rposes. <.< Pro (ct h!erarchy: are also (se for stat!st!cal p(rposes or Pr!c!n". %.< -he pr!c!n" con !t!ons ma!nta!ne for the Pr!ce reference mater!al; are also /al! for the mater!al master for wh!ch th!s reference mater!al has &een entere . '.< Plant: -he el!/er!n" plant from mater!al master !s efa(lte !nto the sales or er; &(t !t can &e chan"e !n the or er; pro/! e the rele/ant com&!nat!on of sales or" G !str!&(t!on Channel !s ass!"ne to the Plant !n I+6 c(stom!$!n". ).< Item cate"ory "ro(p: +ater!al master has 2 f!el s; "eneral Item cate"ory "ro(p an Item cate"ory "ro(p. System chec0s for !tem cate"ory "ro(p; &(t !f !t !s not ma!nta!ne ; then !t chec0s for 6eneral Item cate"ory "ro(p. -he "eneral !tem cate"ory "ro(p !s ma!nta!ne !n 2as!c ata of mater!al master :common to all sales or" G !str!&(t!on channel GPlant com&!nat!ons<. -he !tem cate"ory "ro(p !s (se to eterm!ne the !tem cate"ory !n sales or er !tem. :Item cat "ro(p G or er type G h!"her le/el !tem cat G (sa"e H Item cate"ory.
S35' / e =rganization Stru!ture in SD is !omprise$ o& ) i! t ree elements1 -olle!tivel,> ) at are t ese t ree elements !alle$1

SA1: Sales #r"an!$at!on; ,!str!&(t!on Channel; ,!/!s!on. -he com&!nat!on of these three elements !s calle a Sales Area.
S3+' Please provi$e t)o e(amples o& organizational units t at !an %e assigne$ to a !ompan, !o$e7

SA%: Sales #r"an!$at!on; Plant; stora"e locat!on; !str!&(t!on channel an

!/!s!on

S35.' 0 at is t e purpose o& t e partner &un!tions1 Please provi$e e(amples7

SA1': Use partner f(nct!ons to ef!ne the r!"hts an respons!&!l!t!es of each &(s!ness partner !n a &(s!ness transact!on. @o( ass!"n partner f(nct!ons when yo( create a c(stomer master recor for 78amples: Sol =to Party; Sh!p=to Party; 2!ll=to Party; an Payer

S358' 0 at %usiness partner roles are essential &or sales transa!tions1

SA1): Sol to; sh!p to; &!ll to an Payer.


S35:' 2o) are partner &un!tions relate$ to a!!ount groups1

SA1?: Partner f(nct!ons are ass!"ne to an acco(nt "ro(p.


S3<6' Des!ri%e ) at in&ormation !an %e store$ on t e s! e$ule line7

SA25: Conf!rme B(ant!t!es an ates; mo/ement type; proc(rement ata; mater!al a/a!la&!l!ty; sta"!n"; sh!pp!n" ates.
S3<5' 0 at $oes t e s! e$ule line !ategor, !ontrol1

SA21: A/a!la&!l!ty chec0; transfer of reB(!rements; proc(rement.


S3<<' 2o) is t e s! e$ule line !ategor, $etermine$ %, t e s,stem1

SA22: !tem cate"ory G +CP type H Sche (le l!ne cate"ory.


S3<+' Please $es!ri%e ) at a sales $o!ument t,pe !ontrols an$ give several e(amples7

SA2%: Sales oc(ment typeSs control how sales oc(ments m(st f(nct!on. 4or e8ample; a ret(rns or er to rece!/e "oo s &ac0 from a c(stomer w!ll f(nct!on !fferently than a sales or er or a B(otat!on. -he sales oc(ment type controls the central hea er eta!ls of the sales or er == for e8ample; the pr!c!n" proce (re to &e ass!"ne to the sales oc(ment; or what type of oc(ment the sales oc(ment !s.
S3<.' /ell me a%out pri!ing an$ o) pri!ing is $one in SAP

SA2': Pr!c!n" !s one &ase on pr!c!n" proce (re; con !t!on type; access seB(ence; an con !t!on ta&le an con !t!on recor
S3<' Des!ri%e in $etail o) a sales area is !reate$1

SA2: 2ase on the sol to party entere ; the system prompts to select the sales areas that the sol to &e ma!nta!ne for; !f the c(stomer sales areas are allowe for the oc(ment type !n B(est!on.
S3.' Brie&l, e(plain t e relations ip %et)een sales organizations an$ !ompan, !o$es7

SA': -he sales or"an!$at!on !s an or"an!$at!onal (n!t w!th!n lo"!st!cs that str(ct(res the company accor !n" to !ts sales reB(!rements. It represents the sell!n" (n!t as a le"al ent!ty. It !s respons!&le for pro (ct "(arantees an other r!"hts to reco(rse; for e8ample. 7ach sales or"an!$at!on !s ass!"ne e8actly one company co e for wh!ch yo( enter all acco(nt!n" eta!ls of the sales or"an!$at!on.
/358' 0 i! transportation pro!esses1 /38' 2o) is t e

organizational unit is re?uire$ spe!i&i!all, &or E--

-A1): -ransportat!on Plann!n" Po!nt

Route on a Sales =r$er $etermine$1

-A): -he ro(te !s &ase on the Sh!pp!n" Con !t!ons; -ransport 6ro(p; an the 4rom=-o Zone
/3:' 0 at@s t e $i&&eren!e %et)een in%oun$ route $etermination an$ out%oun$ route $etermination1

A?: 4or o(t&o(n we o !t &y or er an !n&o(n we o !t &y el!/ery as there !s no or er on !n&o(n &(t a P#
/3+' 2o) is t e

s ipping point $etermine$ in a sales or$er1

-A%: 2y Plant; *oa !n" "ro(p an Sh!pp!n" con !t!on


/356' 0 , is a s ipping point use$1

-A15: ItSs (se to ! ent!fy the start!n" po!nt of a mo/ement


/35' 0 at is a

transportation zone an$ ) at is it use$ &or1

-A1: A "eo"raph!cal !/!s!on (se for plann!n" an !nserte whene/er we ha/e an a ress !n lo"!st!cs area s(ch as sh!pp!n" po!nt or a /en or. It !s reB(!re pr!or to ro(te eterm!nat!on conf!"(rat!on.
/3<' 0 at is a

transportation group1

-A2: It !s !n mater!al master :SalesIPlant ,ata screen< an (se to pre/ent mater!als of !fferent "ro(ps !n same el!/ery :th!s a/o! !n" sh!pp!n" to"ether< @o( can (se the transportat!on "ro(p to "ro(p to"ether "oo s w!th the same character!st!cs :for e8ample; &(l0y "oo s or "oo s that m(st &e transporte !n refr!"erate tr(c0s<.
TQ3: !at is

loa$ing group and its loa$ing group use" transportation

-A%: !t !s (se for ro(te eterm!nat!on (s!n" the com&!nat!on of #,pa!r; sh!pp!n" con !t!on an loa !n" "ro(p
3' "ame t e + &a!tors in&luen!ing s,stem %e avior o&

relevan!e1
A: Co(te; ,el!/ery !tem cate"ory m(st &e chec0e !f !tSs "o!n" to &e transportat!on rele/ant an the transportat!on rele/ance for el!/ery type !n !cator m(st &e chec0e for a el!/ery type to &e place on a sh!pment.

SC,
/355' For S ipment -ost> please e(plain o) t e s,stem $e!i$es i& rate %, eig t or %, $istan!e is %etter1

-A11: -hro("h the (se of 78cl(s!on 6ro(ps


/A5<' Do ,ou ave an, ?uestion &or us1 )'What !s yo(r (n erstan !n" of o o o

pr!c!n" an the components aro(n !t?

Con !t!ons= Pr!ces; ,!sco(ntsI S(rchar"es; fre!"ht; ta8es 4!el Catalo"= conta!ns the l!st of 0ey f!el s Con !t!on Cecor s= Conta!ns the /al(e for pr!ces; !scIs(rchar"e; fre!"ht; an ta8es=can &e ef!ne accor !n" to a scale. Can spec!fy (pper D lower l!m!t= when pr!ces are entere man(ally !t has to &e w!th!n these l!m!t so(

How o yo( create a &(s!ness &l(e pr!nt? What !s !tem proposal? -ell me t!me when yo( were a&le to !mpress yo(r &oss Item cate"ory !n ++ ,!fferent P. # type
"rame work is blanket purchase order

-ow many partner profile 'n S$% and

Vous aimerez peut-être aussi