SAP Interview Questions and Answers

kanhaiya@consultant.com

SAP Interview Questions and Answers What is ERP? - ERP is a package with the techniques and concepts for the integrated management of business as a whole, for effective use of management resources, to improve the efficiency of an enterprise. Initially, ERP was targeted for manufacturing industry mainly for planning and managing core business like production and financial market. s the growth and merits of ERP package ERP software is designed for basic process of a company from manufacturing to small shops with a target of integrating information across the company.

Di erent ty!es o ERP? - ! P, " #, $% Edwards, &racle 'inancials, !iebel, People!oft. mong all the ERP()*+,*-)s most of the companies implemented or trying to implement ! P because of number of advantages aver other ERP packages. What is SAP? - ! P is the name of the company founded in ./01 under the 2erman name 3!ystems, pplications, and Products in %ata Processing4 is the leading ERP 3Enterprise Resource Planning4 software package. E"!lain the conce!t o #$usiness %ontent& in SAP $usiness In ormation Warehouse? - "usiness 5ontent is a pre-configured set of role and task-relevant information models based on consistent 6etadata in the ! P "usiness Information 7arehouse. "usiness 5ontent provides selected roles within a company with the information they need to carry out their tasks. 8hese information models essentially contain roles, workbooks, queries, Info!ources, Info5ubes, key figures, characteristics, update rules and e9tractors for ! P R:;, my! P.com "usiness pplications and other selected applications. Why do you usually choose to im!lement SAP? - 8here are number of technical reasons numbers of companies are planning to implement ! P. It<s highly configurable, highly secure data handling, min data redundancy, ma9 data consistency, you can capitali=e on economics of sales like purchasing, tight integration-cross function. %an $W run without a SAP R'( im!lementation? - 5ertainly. >ou can run "7 without R:; implementation. >ou can use pre-defined business content in "7 using your non-! P data. ?ere you simply need to map the transfer structures associated with "7 data sources 3Info5ubes, &%! tables4 to the inbound data files or use ;rd part tool to connect your flat files and other data sources and load data in "7. !everal third party E8@ products such as cta, Infomatica, %ata!tage and others will have been certified to load data in "7. What is IDES? - International %emonstration and Education !ystem. sample application provided for faster learning and implementation. What is W) and its im!ortance? - "usiness 7ork 'lowA 8ool for automatic control and e9ecution of crossapplication processes. 8his involves coordinating the persons involved, the work steps required, the data, which needs to be processed 3business obBects4. 8he main advantage is reduction in throughput times and the costs involved in managing business processes. 8ransparency and quality are enhanced by its use. What is SAP R'(? third generation set of highly integrated software modules that performs common business function based on multinational leading practice. 8akes care of any enterprise however diverse in operation, spread over the world. In R:; system all the three servers like presentation, application server and database server are located at different system. What are !resentation* a!!lication and data+ase servers in SAP R'(? - 8he application layer of an R:; !ystem is made up of the application servers and the message server. pplication programs in an R:; !ystem are run on application servers. 8he application servers communicate with the presentation components, the database, and also with each other, using the message server. ll the data are stored in a centrali=ed server. 8his server is called database server. What should +e the a!!roach or writin, a $D% !ro,ram? - 5onvert the legacy system data to a flat file and convert flat file into internal table. 8ransfer the flat file into sap system called Csap data transferD. 5all transaction37rite the program e9plicitly4 or create sessions 3sessions are created and processed ,if success data will transfer4. E"!lain o!en SQ- vs native SQ-? - " P #ative !E@ allows you to include database-specific !E@ statements in an " P program. 6ost " P programs containing database-specific !E@ statements do not run with different databases. If different databases are involved, use &pen !E@. 8o e9ecute " P #ative !E@ in an " P program, use the statement EFE5. &pen !E@ 3!ubset of standard !E@ statements4, allows you to access all database tables available in the R:; !ystem, regardless of the manufacturer. 8o avoid conflicts between database tables and to keep " P programs independent from the database system used, ! P has generated its own set of !E@ statements known as &pen !E@. What are datasets? - 8he sequential files 3processed on application server4 are called datasets. 8hey are used for file handling in ! P. What are internal ta+les check ta+le* value ta+le* and trans!arent ta+le? - Internal tableA It is a standard data type obBect, which e9ists only during the runtime of the program. 5heck tableA 5heck table will be at field level checking. Galue tableA Galue table will be at domain level checking e9A scarr table is check table for carrid. 8ransparent tableA - E9ists with the same structure both in dictionary as well as in database e9actly with the same data and fields. What are the ma.or +ene its o re!ortin, with $W over R'(? 7ould it be sufficient Bust to 7eb-enable R:; ReportsH - Performance I ?eavy reporting along with regular &@8P transactions can produce a lot of load both on the R:; and the database 3cpu, memory, disks, etc4. $ust take a look at the load put on your system during a month end, quarter end, or year-end I now imagine that occurring even more frequently. %ata analysis I "7 uses a %ata 7arehouse and &@ P concepts for storing and analy=ing data, where R:; was designed for transaction processing. 7ith a lot of work you can get the same analysis out of R:; but most likely would be easier from a "7.

/ow can an ERP such as SAP hel! a +usiness owner learn more a+out how +usiness o!erates? In order to use an ERP system, a business person must understand the business processes and how they work together from one functional area to the other. 8his knowledge gives the student a much deeper understanding of how a business operates. Jsing ! P as a tool to learn about ERP systems will require that the people understand the business processes and how they integrate. What is the di erence +etween 0-AP and Data 1inin,? - &@ P - &n line nalytical processing is a reporting tool configured to understand your database schema ,composition facts and dimensions . "y simple point-n-clicking, a user can run any number of canned or user-designed reports without having to know anything of !E@ or the schema. "ecause of that prior configuration, the &@ P engine CbuildsD and e9ecutes the appropriate !E@. 6ining is to build the application to specifically look at detailed analyses, often algorithmicK even more often misappropriate called Creporting. What is 234567#E"tended Star Schema234568 and how did it emer,e? - 8he !tar !chema consists of the %imension 8ables and the 'act 8able. 8he 6aster %ata related tables are kept in separate tables, which has reference to the characteristics in the dimension table3s4. 8hese separate tables for master data is termed as the E9tended !tar !chema. De ine 1eta data* 1aster data and 9ransaction data - 6eta %ataA %ata that describes the structure of data or 6eta&bBects is called 6etadata. In other words data about data is known as 6eta %ata. 6aster %ataA 6aster data is data that remains unchanged over a long period of time. It contains information that is always needed in the same way. 5haracteristics can bear master data in "7. 7ith master data you are dealing with attributes, te9ts or hierarchies. 8ransaction dataA %ata relating to the day-to-day transactions is the 8ransaction data. :ame some draw+acks o SAP - Interfaces are huge problem, %etermine where master data resides, E9pensive, very comple9, demands highly trained staff, lengthy implementation time. What is $e"? - "e9 stands for "usiness E9plorer. "e9 enables end user to locate reports, view reports, analy=e information and can e9ecute queries. 8he queries in workbook can be saved to there respective roles in the "e9 browser. "e9 has the following componentsA "e9 "rowser, "e9 analy=er, "e9 6ap, "e9 7eb. What are varia+les? - Gariables are parameters of a query that are set in the parameter query definition and are not filled with values until the queries are inserted into workbooks. 8here are different types of variables which are used in different applicationA 5haracteristics variables, ?ierarchies and hierarchy node, 8e9ts, 'ormulas, Processing types, Jser entry:%efault type, Replacment Path. What is AW$?. 7hat is its purposeH - 7" stands for dministrator 7ork"ench. 7" is a tool for controlling, monitoring and maintaining all the processes connected with data staging and processing in the business information whearhousing. What is the si,ni icance o 0DS in $IW? - n &%! &bBect serves to store consolidated and debugged transaction data on a document level 3atomic level4. It describes a consolidated dataset from one or more Info!ources. 8his dataset can be analy=ed with a "E9 Euery or Info!et Euery. 8he data of an &%! &bBect can be updated with a delta update into Info5ubes and:or other &%! &bBects in the same system or across systems. In contrast to multi-dimensional data storage with Info5ubes, the data in &%! &bBects is stored in transparent, flat database tables. What are the di erent ty!es o source system? - ! P R:; !ource !ystems, ! P "7, 'lat 'iles and E9ternal !ystems. What is E"tractor? - E9tractors is a data retrieval mechanisms in the ! P source system. 7hich can fill the e9tract structure of a data source with the data from the ! P source system datasets. 8he e9tractor may be able to supply data to more fields than e9ist in the e9tract structure. ;. What is trans er order? Here are some basic points for Transfer order1)TO is movement of goods within warehouse. It can be within storage types and storage bins. 2)TO can be created manually with reference to delivery for posting change notice and for transfer re!uirement ")The control for TO li#e whether it is confirmed automatically or not whether screen for TO should appear after material document is posted is all controlled in configuration of movement types in $% &) TO once confirmed cannot be cancelled. only if it is not confirmed can you cancel it. ')(ome Transactions are )T*1+manual) )T*"+create with ref to delivery) )T11,)t12+confirmation) )T*-+TO for material document). -) Then there is something consisdered while creating TO is !uant..uant is combination of plant material batch storage type storage bin stoc# category special stoc#. when any one of these changes new !uant is generated.while creaing TO system automatically determines the !uants. 1. What are the ields in !ricin, !rocedureH 1- fileds in pricing which is bac# bone when configuring the pricing. (tep, /ounter, condition type, description, from, to, manual, mandatory, statistical, print, subtotal, re!urirement, alternative calclutation type, alternative condition base value ,account #ey, accrual,

(. What are the Standard out!ut ty!es in SD? 1. (ales Order /onfirmation0 12** 2. Outbound 3elivery 4ote0 )3** ". 1illing 3ocument0 53** '. /ash (ales0 53*" -. In!uiry0 26** 7. .uotation0 24** 8. /ontract0 9O** :. ;ic#ing )ist0 <9** L. 7hat is 5ondition typeH M. What is di erence +etween delivery document < schedulin,H N. 7hat is E9tract used in condition tech. in pricingH =. What is the !ur!ose o sales document ty!e? 2 sales document type fullfills a re!uirement of a specific business transaction.. for e=ample in a cash sale you would re!uire the delivery to be happenign immediately after the order and you would re!uire a invoice slip to be handed over to the customer immediately after his purchase..These things are customised in your /ash sales+/() document type.. 2lso It can determine whether the sales docs of that type are bloc#ed or not 4o ranges for the documents whether a reference doc is mandatory or not whether it should read cus.material info record whether the system should run credit chec#s and how it should respond etc..

O. 7hat are 6RP typesH

/. 7hat is the difference between incomplete order and backorder processingH .P. 7hy does the customer master have different viewsH ;;.What is t>code or listin, the +locked documents? !6.1 ;?.What is Product attri+utes? Summary #ormal !ales Process involves, that 5ustomers ordering certain quantity of general 6aterial without any special requirements. &nce these 6aterials are ready it will be shipped to the customer and the Invoice document will be sent to the customer for receiving payment. 'or these 5ustomers one can sell the 'inished 2oods without any constraints. ?owever, there are few 5ustomers who will have a specific 5lause while placing the &rder. 8he 5lause could be likeK they do not want the 'inished Product made out of Raw 6aterial imported from certain countries or in case of 5hemical Products, the quantity of certain 5hemicals used during Production of the 'inished Product must not e9ceed a particular quantity. 8hese kinds of 5ustomer clauses are really difficult to check manually while selling : shipping the 'inished Products and somehow we need to have auto check before the 2oods are shipped to the 5ustomers to have repetitive business. 7e will see how this Product ttributes 'unctionality in ! P helps us in achieving this requirement. ;. 1aster Data Settin,s 8o achieve this functionality, we need to do the appropriate settings in 6aterial 6aster %ata and 5ustomer 6aster %ata. lso we have the 5ustomi=ation part, which we will be discussing below. #ow let us see the 6aster %ata setting involved enabling the complete business process flow. ?. De ine Product Attri+utes in 1aterial 1aster 'ollow the below menu path to define Product ttributes in 6aterial 6asterA -o,istics - SD > Products > 1aterial > 0ther 1aterial > %reate or %han,e@ 0r %an use the 9ransaction %ode > 11A; ' 11A?@

?ere, you can enter the 6aterial #umber for which you need to assign the Product ttribute values. 2o to !ales &rg 1 view in 6aterial 6aster Record and in that select appropriate Product ttributes as per requirement. 'or E9ample, !elect QProduct ttribute - ;Q for materials with more than or equal to .R of specific 5hemical used 3like "en=ene related content4 during its production. (. De ine Product Attri+utes in %ustomer 1aster 'ollow the below menu path for defining the Product ttributes in 5ustomer 6asterA -o,istics > SD - $usiness Partner - %ustomer - %reate or %han,e@ 0r Bse the 9ransaction %ode > CDA; ' CDA?.

?ere, you can enter the 5ustomer #umber, for which the Product ttribute value has to be assigned. 2o to !ales rea %ata in 5ustomer 6aster and in that !ales Giew, !elect the QProduct attributesQ field highlighted in the above screenshot and in that select the appropriate Product ttributes. 'or E9ample, !elect QProduct ttribute - ;Q for materials with more than or equal to .R of specific 5hemical used 3like "en=ene related content4 during that material production. D. ReEuired %ustomiFation Settin,s 'ollow the below menu path to determine how the system has to behave if the Product ttributes of the 6aterial and 5ustomer is well matchedA SPR0 > SD > Sales - Sales Documents - Sales Document /eader - De ine Sales Document 9y!es@ 0r 9ransaction %ode > G0GH@

?ere, select the appropriate !ales %ocument 8ype for which you need this Product ttribute functionality. If needed for all the !ales %ocument types, then the following 5ustomi=ation has to be done in all the !ales %ocument 8ypes. 2o to 8ransaction G&GO or to the above said 6enupathA

?ere, let us take !tandard &rder 8ype for e9ample. !elect Q&RQ and then click on the details button to do the necessary customi=ation.

?ere, select the appropriate behavior for Product ttributes 'ield as per your requirement. In the !ales &rder, for this !ales %ocument 8ype, the system will carry out a check on the compatibility of the Product ttributes selected in 5ustomer 6aster 3!hip to Party4 and in 6aterial 6aster. If the Product ttributes of the 5ustomer and 6aterial matches, then depending upon the indicator set in !ales %ocument 8ype for the Product ttribute 'ield, the system will behave. 'or e9ample, the Product ttribute field in !ales %ocument 8ype can be set with the following available optionsA :one > A > $ > :o 1essa,es will +e dis!layed Dis!lays a Warnin, messa,e. Dis!lays a Error messa,e and +locks urther !rocessin,.

I. )unctionality 9estin, 2o to 8ransaction G P. - !ales &rder 5reation and enter the &rder 8ype, for which we have maintained the Product ttribute 'ield messages.

Enter the Product ttribute enabled 5ustomer #umber in !hip to Party field and the 6aterial #umber for testing this 'unctionality. fter entering all the required data in the !ales &rder 5reation !creen, select Q&SQ button. #ow the system will check for the Product ttributes of the 5ustomer 6aster 3!hip to Party4 and the Product ttributes maintained in the 6aterial 6aster, if matches, then the !ystem will behave as per the settings in the !ales %ocument 8ype.

8he above screenshots displays the 7arning 6essage, as the Product ttribute is compatible for the 5ustomer 3!hip to Party4 - 0NPPP.1 and the 6aterial - .1LM in the !ales &rder created with !ales %ocument 8ype - &R. ?owever, this functionality will not be working if the Product ttribute for 5ustomer and the 6aterial entered in the !ales &rder is not compatible. J. Advanta,e o Product Attri+ute )unctionality over 1aterial E"clusion 8he material e9clusion functionality gives only an option to e9clude selling specific material to specific customers with condition technique, where as product attribute gives us the option of e9cluding sales of materials with !articular attri+ute to the customers who did not accept the product with same kind of attribute. Product ttribute functionality requires only minimal 5onfiguration settings when compared to that of 6aterial E9clusion.

.;.

7hat is difference between !% account key and 'I account keyH 7hat are a variant and its useH .L. ?ow is credit control determinedH ;I.What are the !arameters in )D(?? .N. 7hat is the difference between routine and requirementsH .0. 7hat is condition supplement and why is it usedH .O. 7hat is the difference between milestone and periodic billingH ;K.What is the landsca!e? )andscape is li#e a server system or li#e a layout of the servers or some may even call it the architecture of the servers vi>. (2; is divided into three different lanscape 3<? .2( and ;5O3. - 3<? would have multiple clients for e=0 1:*- (andbo= 1**- @olden 18*- Anit Test. - .2( may again have mutiple clients for e=0 "**- Integration Test 7** to 71* Training. - ;5O3 may have something li#e a 2** ;roduction. These names and numbers are the implementerBs discreet on how they want it or they have been using in their previous implementations or how is the clientBs business scenario. 4ow whatever you do in the (andbo= doesnBt affect the other servers or clients. $henever you thin# you are satisfied with your configuration and you thin# you can use it moving forward you 5<-3O it in the golden client +remember this is a very neat and clean client and you cannot use it for rough usage). 2s you re-do everything that you had thought was important and usable you get a transport re!uest pop up upon saving everytime. Cou save it under a transport re!uest and give your description to it. Thus the configuration is transported to the Anit Test client +18* in this e=ample). Cou donBt run any transaction or even use the (2; <asy 2ccess screen on the 1** +golden) client. This is a configuration only client. 4ow upon a successful tranport by the 1asis guy you have all the configuration in the Testing client Dust as it is in the @olden client. The configuration remains in sync between these two clients. 1ut in the Testing client you can not even access (;5O +3isplay I%@) screen. ItBs a transaction only client where you perform the unit test. Apon a satisfactory unit test you move the good configuration to the ne=t (<5?<5 +3<?). The incorrect or unsatisfactory configuration is corrected in @olden +may again as well be practised in the sandbo= prior to @olden) and accordingly transported bac# to 18* +Anit Test) until the unit test affected by that particular config is satisfactory. The @olden client remains the BdatabaseB +if you wanna call it that) or you may rather call it the BultimateB reference client for all the good complete and final configuration that is being used in the implementation. In summary: )andscape 0 is the arrangement for the servers I3<( 0 is purely for education purpose and is 4OT I4/)A3<3 in the landscape. 3<?<)O;%<4T ---E .A2)ITC ----E ;5O3A/TIO4 3<?<)O;%<4T 0 is where the the consultants do the customi>ation as per the companyBs re!uirement. .A2)ITC 0 is where the core team members and other members test the customi>ation. ;5O3A/TIO4 0 is where the live data of the company is recorded. 2 re!uest will flow from 3ev-E.ual-E;rod and not bac#wards. 1. (andbo= server0 In the initial stages of any implementation proDect Cou are given a sandbo= server where you do all the configuration,customi>ation as per the companies business process. 2. 3evelopment (erver0 - Once the 11; gets signed off the configuration is done is development server and saved in wor#bench re!uests to be transported to ;roduction server. ". ;roduction (erver0 This is the last, most refined client where the user will wor# after proDect @O )I?<. 2ny changes, new develpoment is done is development client and the re!uest is transported to production.

These three are landscape of any /ompany. They organised their office in these three way. 3eveloper develop their program in 3evelopment server and then transport it to test server. In testing server tester chec#,test the program and then transport it to ;roduction (erver. )ater it will deploy to client from production server. ;resentaion (erver- $here (2; @AI have. 2pplication (erver - $here (2; Installed. 3atabase (erver - $here 3atabase installed. What is the meaning of "R" in R/3 systems? 5," stands for realtime three tier architecture. This is the #ind of architrecture (2; 5," system has. 5," means three layers are installed in 3ifferent system,server and they are connected with each other. 1) ;resentation 2) 2pplication ") 3atabase Why do we call client AAA as ,olden client? 2olden client contains all the configuration data and master data so some e9tent. ll the configuration settings are done in golden clients and then moved to other clients. ?ence this client acts as a master record for all transaction settings, hence the name Q2olden 5lientQ. 1P. ?ow variant is used in reportingH 1.. 7hat is the difference between !tatic and %ynamic 5redit 5heckH 11. 7hat is difference between the item proposal and dynamic proposalH 1;. 7hat are the issues u have faced in integration testingH ?D.What is a ield catalo,? New Fields in Pricing To use a field in pricing one creates a condition table. This condition table is created using the allowed fields from the field catalog. (hould the fields one re!uires not be included in the list of allowed fields one can add the fields from the list of available fields. However one may find that a new field may not be in the list of available fields. 6or this reason one must create new fields for pricing. The document and item data in (3 is stored in data tables such as ?129 and ?12; +for the order transaction). %any of the fields from these tables are available in the field catalog. The field catalog is a structure +9O%@) that consists of two tables +9O%9 and 9O%;). These tables contain the header and item data for pricing respectively. They are called 9O% F=G because they are communications structures used to communicate the transaction data with the pricing procedure. Table 9O%@ contains the fields of tables 9O%9 and 9O%;. If you re!uire a field that is not in 9O%@ it means that it is not in 9O%9 or 9O%;. This means that the field you re!uire cannot be used in pricing because there is no communication of this field from the transaction to the pricing procedure via the communication structures. To use a field not defined in the field catalog you need to add this field to the 9O%9 or 9O%; structures and then write the 212; code to transfer the data in the field from the transaction tables to the communication structure. 6ollow these steps0 1. /reate the field in the 9O%9 +header data) and 9O%; +item data) tables using the standard includes provided for this re!uirement. 2. $rite the code in the user e=it to read the transaction data and transfer it to the 9O% F=G structures. %enu ;ath The menu path here is I%@ (ales and distribution (ystem modification /reate new fields +using the condition techni!ue) 4ew fields for pricing. Adding the Field to !" and !"P

This process re!uires some #nowledge of the 212; dictionary and how to use the 212; dictionary to create and change fields and tables. Cou may have to use an 212; s#ill to assist you. If the field is from the header table +for e=ample the order table ?129) youHll need to add it to the include table 9O%92I in table 9O%9. If the field is from the item table +for e=ample the order item table ?12;) youHll need to add it to the include table 9O%;2I in table 9O%;.

)etHs say you need to use the Fbase materialG to define a price and the base material is not in the pricing field catalog. The base material is a field on the material master basic data screen and is defined as %252-$59(T. (ince this relates to the material it is at the item level so you would add the field to the 9O%;2I include table. 4ote $hen you add a field to these tables it must start with FII.G Therefore the field you add would be II$59(T. In 212; when you add the field use the same domain as in the field in the original table %252$59(T. 2fter adding the field generate the structure 9O%;. This field is not available in the field catalog and can be used in condition tables. Writing the A#AP $ode The field in the communications structure will be blan# unless the 212; code transfers the data from the material master to the field 9O%;II$59(T. ;ricing occurs in the order and in the invoice so you need to put this code in both places. 6or the order transaction write the 212; code in user e=it A(<5<JITK;5I/I4@K;5<;25<KT9O%; in include program %?&'26II. 6or the billing transaction write the 212; code in user e=it A(<5<JITK;5I/I4@K;5<;25<KT9O%; in 5?-*26II. 4ote 0 The T9O%; is for the item level. If you are writing the code for a field at the header level you would use the user e=its that end with T9O%9. The 212; code would select the 1ase material field from the material master table using the material from table ?12;,?15;. It would then transfer this field to the structure T9O%; from %O?< %252$59(T to T9O%;-II$59(T. ?I.What is the di erence +etween condition ty!e ELA; and ELA?? These are the condition type that will display the results of the unit costing for certain type of sales document. % &' If you use this condition type the result of unit costing is issued to the first position on the conditions screen for the item. The value can be used as a basis for price determination. % &(0 If you use this condition type the result of unit costing is simply a statistical value which you can compare with the price. ;lease note the following points 0 1) The condition type must have condition category B.B +costing). 2) The condition type must agree with the condition type defined for unit costing in the pricing procedure. (I.I have a customer who is +ein, o ered two discounts ie kAA= and kAAI* now I want to e"clude kAA= or the ne"t ? orders or so? I have set the e"clusion indicator or the condition ty!e*+ut still the condition is +ein, acce!ted when I create a sales order. Am I missin, somethin,* how do I do it? I thin# u need to change the validity of the condition record for the condition type 9**7 defining it not valid for that particular 2 months. 2nd also the settings of the 5e!uirements as it is correct that it overrules the e=clusion. 1N. 7hat are the user e9itsH 10. 7hat is the 'unction of item category groupH 1O. 7hat is pricing procedureH 1/. 7hat is condition e9clusionH ;P. 7hich delivery document type for !8& 3!8&5S 8R #!'ER &R%ER4 processH I#8R ---#@ I#8ER---#@55 I:9RA J" #@ I:9ER #" #@55

Standard document ty!e Delivery ty!e 1ovement ty!e Sin,le ste! Issuin, !lant Receivin, !lant

NL0 .P.

NLM .P.

9wo ste! Issuin, !lant Receivin, !lant NL. .P. NL; .P.

;.. 7hat is difference between the header level condition ;1. 7hat is the link between credit management and subtotalsH ;;. 7hat is %elivery group and what is its purposeH (D.What is main !ur!ose o maintainin, the master data? $ommon )istri*ution $hannel and $ommon )i+ison are maintained so that if any master data li#e customer or material maintained with respect to one distribution channel can be used in other 3/h. It prevents the multiplication of master records. <g0 2 customer is created for say sales area 1***,2*,** then the same customer can be used in sales area 1***,"*,** if we maintain 2* as common distribution channel. Hence no need for e=tending the customers...the same for materials also. ;M. 7hat is line itemH ;N. 7hat is a 8ransfer orderH ;0. 7hat is value ! PH (H.What is di erence +etween listin, and e"clusion? )isting is nothing but what ever material u assigned to particular customer then he can access those materials but e=clusion is nothing but e=cluding the particular material to the customer then customer cannot access those materials ;/. 7hat happens when you overrate the customerH LP. What are the unctions !er ormed in a su!!ort client? Cou can opt for any of the following " 0 1)credit the customer for the amount of short-charged invoice by creating a /redit %emo 5e!uest with reference to the previous invoice and create a new sales order with correct rate 2)you can ma#e a /redit %emo 5e!uest for the overcharged amount and ma#e a /redit 4ote 1illing 3ocument to give credit for the difference amount ")you may ma#e an Invoice /orrection 5e!uest L.. 7hat is the access sequence for header conditionsH L1. 7hat are the highest organi=ational units in !%, 66, PP and 'I5&H L;. 7hat is the functionality of negative posting in billing documentH LL. 7hat is mean of Rebate processingH LM. ?ow is shipping point determinedH $riteria for Pro,osing a -hi,,ing Point 2 shipping point can be determined for each order item. How the shipping point is determined depends on three factors0 The shipping conditions from the customer master record +(hipping screen) 6or e=ample it might have been agreed with the customer that the goods are to be delivered as soon as possible. The loading group from the material master record +(ales,;lant 3ata screen) Cou could for e=ample specify a loading group that defines that the goods must always be loaded with a crane or a for#lift. The delivering plant This plant is determined per order item either from the customer master record or from the material master record. However you can also enter it manually for each order item. 6or more information on determining the delivering plant refer to the section The following figure shows how the shipping point is determined using the data listed above.

On the basis of shipping condition *1 the loading group /524< and the plant ***1 the system determines shipping point ***1 for the item. Instead of this shipping point you can also select shipping points ***2 and ***" if for e=ample you #now that shipping point ***1 is out of operation or does not have the capacity to deal with the item at the time when delivery is to ta#e place. $hanging a -hi,,ing Point Cou are still able to change the shipping point proposed by the system in the sales order within specified limits. If you enter a shipping point that is not valid you will receive the following error message from the system0 L(hipping point is not available for this activity.L If the shipping point cannot be determined because for e=ample the delivering plant could not be found in the sales order an entry is made in the incompletion log in the standard version of the (2; 5," (ystem. This ensures that the shipping point is entered before the sales order can be processed for delivery. Cou can obtain an overview of the shipping points for all order items by choosing Overview . (hipping in the sales order. Cou will find the shipping points in the (h;t column. If you enter a delivery for the sales order you must always specify the shipping point from which the sales order is to be delivered. The shipping point cannot be changed in the delivery. )eli+ery *y a -hi,,ing Point Cou can only carry out delivery processing for the items in a sales order for which a shipping point has been defined. If different shipping points have been assigned to the various items in a sales order the deliveries have to be processed for each shipping point. If you create a delivery for a sales order that contains several shipping points the system reacts as follows0 If you create an individual delivery you receive a note in the log that the items with different shipping points have not been included in the delivery. If you process a delivery via the delivery due list no note is entered in the log. $hen you process the delivery due list the system only informs you of errors that occur during processing. If the customer re!uests complete delivery of the sales order it does not ma#e sense to define different shipping points for the order items since this would lead to the sales order being split into several deliveries. DJ.What is di erence +etween trans!ort and task? /as01Information carrier in the Transport Organi>er for entering and managing all changes to 5epository obDects and /ustomi>ing settings performed by employees within a development proDect. 2 tas# is assigned to a change re!uest $hange Re2uest 2n information source in the Transport Organi>er that records and manages all modifications made to 5epository obDects and /ustomi>ing settings during a development proDect. Cou can not release change re!uest prior to release tas#+s). L0. 7hat is the client specific dataH LO. ?ow subtotal in pp is related to credit limitH L/. 7hat is the difference between discount and rebateH MP. 7hat are the influencing factors for account determination M.. 7hat are dependencies in variant configurationH M1. ?ow alternate condition base valueH M;. 7hat is the use of podH

ML. 7hat is difference between listing and e9clusionH MM. ?ow revenue account is determinedH IJ.When will you com+ine deliveries into one invoice? we will compile multiple deliveries into one invoice when the bill to party payment terms and billing date is same. 2nd also when billing date that means billing is done only once in a month for that particular customer then you combine all deliveris of that month create invoice M0. ?ow will be the 8icket process flow happens in a Production support proBectH '8. 7hat is transfer orderH ':. 7hat are the fields in pricing procedureH JA.What are the Standard out!ut ty!es in SD? (tandard Output Types in (3 are as under0 1. (ales Order /onfirmation0 12** 2. Outbound 3elivery 4ote0 )3** ". 1illing 3ocument0 53** &. In!uiry0 26** '. .uotation0 24** -. /ontract0 9O**

-1. -2. -". -&.

7hat is 5ondition typeH 7hy does the customer master have different viewsH 7hat is t-code for listing the blocked documentsH (%12 What is di erence +etween SD account key and )I account key? 2ccount #ey is created and provided by 6I. 2ccount #ey determines the @,) account to which the amount is to be posted.. -) defines account 0ey in ,ricing and FI uses it for ,osting ta3es4

NM. ?ow will access the data in to productionH NN. 7hat is consumption based planningH J=.What is Item %ate,ory %ontrol? 2n item category controls the overall behaviour of an item.it determines whether the item is relevant for pricing or not whether it is relevant for delivery or not whether it is relevant for billing or not.it also detrmines whether it is a free item te=t item and it also help to determine the sales document type. NO. 7hat is Returnable packaging processing meansH JK.What is I1M? The Implementation 5uide +I%@) is the tool which adDusts the 5," (ystem to the re!uirements of a company. Cou use the implementation guide to structure and organi>e the implementation of the 5," (ystem in your company. Im,lementation 5uide structure The implementation guide is a hierarchical structure of the application areas in the component hierarchy. It contains all the wor# steps re!uired for the implementation with documentation. There are three implementation guide variants0 the (2; 5eference I%@ ;roDect I%@s ;roDect view I%@s 0P. 7hat are the %ifferences between invoice and billing docH =;.What are the user e"its? 2 user e=it is a place in a software program where a customer can arrange for their own tailor-made program to be called. (2; creates user e=its for specific programs screens and menus within standard 5," applications. These e=its do not contain any functionality. Instead the customer e=its act as hoo#s. Cou can hang your own add-on functionality onto these hoo#s. 01. What is a handlin, unit? What is the access seEuence or header conditions? Handling unit is M ,ac0aging materials 6 "aterials to *e ,ac0ed 6 7ehicle

There is no access se!uence for header conditions co> we enter all the header conditions manually =(.What is -um! sum !ayment? 5ustomer is used for generating statistics and also used to give group pricing, and discounts etc...

0L.

What is the advanta,e o usin, the te"t as a re erence To reduce load on the system referencing is considered better than copying. 0M. 7hat are the !teps in consignment processingH =J.What is the di erence +etween GL;; < GL(; GS.. is to maintain a single condition record and GS ;. is to maintain a group of condition records according to the situations In vk.. u can update for particuler condition record. where as in vk;. u can do the 6ass changes /he *ottom line difference *etween 7 '' and 7 3' is that 7 3'8 7 3( !N9: wor0 for standard -AP deli+ered $ondition /y,es ;e34 PR&&<4 If you create any customer s,ecific $ondition /y,e codes ;e34 =>>><you can only create / maintain $ondition Records for them using 7 ''8 7 '(4 #!/? transactions allow mass entry and changes. 00. 7hat basic questions do they ask relating to order managementH 0O. ?ow is storage location determinedH =K.What is the di erence +etween A9P check and availa+ility check? 2T; /hec# is chec#ing of availablty !uantities i.e 2T; M Total $arehouse (toc# N ;lanned receipts+Incoming (toc#) - ;lanned Issues +Out going stoc#) 2vailbilty /hec# is an integral part of business process it determines the if the desire deliverible !uantity can be met on re!uested delivery date or not.Then it passes to %aterial 5e!uirement ;lanning.

OP. 7hat is the purpose to differentiate the sales document typeH O.. What is the im!ortance o release status and dynamic ield? The importance of release status in release procedures is to create the condition records purely for the planning purpose.for further clarification see release procedures in pricing. The 3ynamic field chec# is to determine the customer-specific fields even the te=t fields. O1. 7hat is the parent and child relationshipH Euestion from 6%6 data management . H(./ow to con i,ure !artial deliveries? Cou can configure the system for partial deliveries in two places 1. In /ustomer-material info.2. /ustomer %aster. If you allow the system for partial deliveries there. Then you can change ;artial to complete delivery in sales order. HD.What are the e ects o PMI? The following are the effects of ;@I0 1.stoc# !uantity is updated. 2.?alues are updated in inventory accounting. ".(tatus in all sales document is updated. &.cost of goods sold is updated. '.5e!uirments is updated. -.1illing inde= is updated. cost of goods gl acount increases- credited.inventory @) account decrease -debited HI.What is cut over strate,y? /utover strategy depends upon how the organi>ations design their data load strategies. 4ormally you decide the se!uence of 3ata loads for /onfiguration settings %aster data Transaction data which follows whom and then you ma#e a copy of the system as a ;roduction system a day before and after chec#ing the successful data loads you go-live 1**O or partial again depending upon organi>ational setup and policies.

/utover strategy depends upon how the organi>ations design their data load strategies. 4ormally you decide the se!uence of 3ata loads for /onfiguration settings %aster data Transaction data which follows whom and then you ma#e a copy of the system as a ;roduction system a day before and after chec#ing the successful data loads you go-live 1**O or partial again depending upon organi>ational setup and policies. /utover planning is highly site specific. ThereBs no thumb rule. The stoc# data as on the date of going live should be correctly entered. 1ut stoc# being a highly dynamic !uantity the strategy for loading should be crystal clear. Then you have to load all the bac# dated transaction on the stoc#. (ome stoc# comes into your plant,storage location as return and some stoc# is actually delivered to your customer through sales orders of various #inds. The final phase before going live with (2; is often referred to as the cutover phase which is the process of transitioning from one system to a new one. The organi>ation needs to plan prepare and e=ecute the cutover by creating a cutover plan that describes all cutover tas#s that have to be performed before the actual go-live. <=amples of cutover tas#s are0 5eview and update all systems-related operations procedures li#e bac#up policies and system monitoring 2ssign ownership of (2;Hs functional processes to individuals )et (2; 2@ do a @oing )ive chec# to get their blessing to go live with the system )oc# down the system i.e. do not ma#e any more changes to the (2; system /ut-Over 2ctivities0 /utover ;lan - The details of how to move to the production environment and go live. <nsuring that all master data to be loaded to production server is ready P in correct format. Aser training is conducted P user is in a comfort or atleast managable position to wor# on production server. ;reparation of user manual. 2ll go-live preparatory activities. Open /lient activity0 The activity or configuration to be done in production server by opening an client should be ensured that it is done before go-live. /utover 2ctivities 2t the end of ;hase & it is necessary to refine and validate the cutover plans generated in the 5eali>ation phase. 2mong other things this includes tas#s such as the reviewing of the runtime of test runs to estimate runtime for the complete data si>e. 2 conversion chec#list for transporting all changes into the productive system is provided for all the configuration settings to be imported. 2t this stage it is important to verify that re!uired tas#s have been successfully completed for e=ample that the technical environment is in place the cutover programs are ready and the application data is verified. 2pproval is now sought from proDect management and company senior management to start the cutover process. Here you can also refer to the 3ata Transfer %ade <asy @uideboo# created especially for this purpose. It is located in the 9nowledge /orner of the 2(2; /3. The help des# is particularly important in the first wee#s after going live but you will re!uire help des# support throughout the productive life of your 5," (ystem. 2n internal help des# should be staffed and supported mainly by employees of the enterprise. (etting up a help des# involves among other things installing office and technical e!uipment and defining O(( users. ;roblems which cannot be solved by this internal help des# are forwarded to (2; via the O(( system. 2s soon as you #now when you will go live with the 5," (ystem or with new 5," applications you should inform (2;. Thus you can ensure that (2; can provide optimal support throughout your goinglive phase. 6or the last wee#s before and first wee#s after the go-live date (2; offers the 5," @oing)ive /ustomer /are (ervice accessible via (2;4et and O(( HJ.What is the relation +etween PMI and 90R? ;@I is the last step we can say at the delivery It depends on the client re!uirement for the process flow ;@I is issuing the @oods after the TO creation and pic#ing TO5 is transfer of re!uirements to the production 3ept this can be Individual and collective re!uirments what ever the orders created which has no confirmed !uantity will be transferred for the re!uirements which in turn creates ;5 and ;Os and 6or this at the schedule lines should have T5,assembly activated

H=.What are the Di erences +etween invoice and +illin, doc? 1oth are same in (3 point of view. - In (3 terminology we call as 1illing 3ocument and - In 6I terminology we call as I4?OI/<. - In %% again only I4?OI/< will be there for ?endors. Invoice is document indicating to delivery goods and 1illing is a receipt of payment. If we receive the goods from vendors that is called bill if we give the goods to customer that is called invoice. 1ill means we have to pay the amount against bill 0 invoice means we have to receive the amount against invoice. Invoice is for both 0 ?endor Invoice and /ustomer Invoice. 9iterally meaning of *ill is to charge for ,roduct @ ser+ices where in+oice is itemiAed *ill4 $illin, 9codes@ - ?6*1 create billing document. The delivery order comes up auto. - ?6*2 the billing doc comes up auto . ?iew the accounting enteries In+oice /codes: - 61-* /reate invoice with respect to rawmaterial and ta=. - 617* Invoice entries with respect to sales and ta= OO. 7hat is the functionality of negative posting in billing documentH HK.What is mean o Re+ate !rocessin,? 2 rebate is a discount which is granted subse!uently to a rebate recepient on the basis of defined sales volume within certain period. there are three process on rebate.. 10- /onfiguring 5ebate 20- (etting of rebate agreements "0- managing rebate agreement P payments 1ut before the processing the rebate you need to activate the following fields 0- in ;ayer master record 0- (ales organisation 0- 1illing document type. Cou have following rebate agreement types for your customer. 10- %aterial rebate 20- customer rebate "0- customer Hierarchy rebate &0- %aterial group rebate '0- Independent of sales volume. KA./ow is shi!!in, !oint determined? shipping conditions N loading group N 3elivery plant M (hipping point /.. 7hat is the client specific dataH /1. 7hat is " P debuggingH K(./ow su+total in !! is related to credit limit? KD.What is the di erence +etween discount and re+ate? 5ebate is a partial repayment whereas a refund is a repayment of the total purchase price 3iscount is reduction in ;rice 3iscount means ...it happens on a single purchase...when comes to rebate.....it happens on only after some particular period of time. 5ebates are retrospective in nature with a specific time frame or other conditions li#e (ales ?olume (ales .uantity attached to it. 5ebate0an incentive to be given to a customer .clubbed with !ty purchased by a customer within the period specified +say one month)-conditional.

3iscount0unconditional to be given to a customer on account of heavy purchase by one single billing.-6rom the price )ist+1ase price). Or 5ebate is a partial repayment whereas a refund is a repayment of the total purchase price 3iscount is reduction in ;rice or discount means ...it happens on a single purchase...when comes to rebate .....it happens on only after some particular period of time. or 5ebates are retrospective in nature with a specific time frame or other conditions li#e (ales ?olume (ales .uantity attached to it. 5ebate0an incentive to be given to a customer .clubbed with !ty purchased by a customer within the period specified +say one month)-conditional. 3iscount0unconditional to be given to a customer on account of heavy purchase by one single billing.-6rom the price )ist+1ase price). or reabte is a discount which is settled ate the end of a perod of a contract or an agreement. discounts normally given anytime. or 5ebate is basically 3iscuont on turover means if u buy " shirts u will get discount of 2*O whereas if the no of shirts het reduced the discount will get reduced. 3iscount doesnt depends upon the turover it is fi=ed.and can only differ from customer to customer. or 5ebate is a retroactive agreement.it is given to a partial payment to perticular secheduled time. +1yr or " Cr). discount is given at a time to the customer. or 5ebate is given for the purchase of specified !uantity or on the volume of the sales over a given period of time . 3iscount is given on everyQ goods purchased by the customer KI.What are the routines? Routines Routines are short sub-programs that carry out various checks during document processing. In the !% module, you can create and process routines for copying requirements, data transfer, requirements and formulas using transaction G&'6. "esides the routines delivered to you with the system, you can create your own individual routines. 8ransaction G&'6 allows you to follow a standardi=ed procedure for creating routines. 8he name ranges are predefined for routines delivered to you with the system and for routines created by the customer. 8his name convention guarantees that your own routines are not overwritten during a Release upgrade. What are routines? are 9rans er'B!date rules and routines one and the same? 5outines are li#e conditions or business rules that could be applied to filter the data while entering the 1$ system or could be used to apply certain conditions on the info obDects itself. There are & types of routines 1. (tart routine- /ould be used at two levels +transfer rule level and the Apdate rule level) This (tart routine written at the transfer rule level helps filter the necessary data coming from the source system. 6or <=ample0 If you decide to e=tract data that contain only !uantity greater than '** then you could specify the (tart rouitne to achieve this. The (tart routine at the Apdate rule level provides similar functionality but at this point it helps direct specific data to different data targets. 6or <=ample0 If there " data targets being fed from the Infosource you may want to apply some condition to each data target li#e send year 2*** data ti 3ata target1 2**1 to data target 2 and so on. This can be achieved by using (tart routine at the Apdate rule level 2. Transfer 5outine0 This feature is available at the transfer rule levels $hile performing the transfer rules operation there are & features available to the developers to create business rules on top pf the InfoobDects. 1. Cou could do a one to one mappping of the InfoobDect 2. ;rovide a constant value ". Include a formula &. $rite an 212p routine.

These & options refers to the transfer routine ". Apdate 5outine0 The limitations of Dust having & options in the transfer routine is overcome at the update rule level. There are various other sophisticated features avaialable apart from the & options mentioned above. These business rules could be specified pertaining to each data target. &. /onversion 5outine0 It provides functionality to do /urrency and unit conversion. KJ.What are the re!orts u have ,enerated with hel! o A$AP? /0. 7hat is meant by Gariant 5onfigurationH Some li,ht on Gariant %on i,uration in Detail. 8he procedure is as followsA /reate a %aterial - 9%2T type with Item category +**2) /reate /harateristics in /T*& - Ibi#e where in values mention the /olor of the bile li#e 5ed 1lue etc /reate another characteristics in /T*& - I;rice where directly go the additional data tab and maintain the table (3/O% and field ?9O43 +212; 3ictionary it will as# for) 2ssign these two characteristics to a /lass in /)*1 - I1i#eclass + Type "**) in characteristics tab page. Then go to /A&1 /onfiguration profile select the material and enter the description clic# on the class assignment ie assign Ibi#class. 4ow go bac# to /T*& - enter Ibi#e -go to values- select 5ed- go to e=tras - Other 3ependencies (elect ;rocedure enter in front 1* write - Rself.I;riceMB5edB and save 4ow go bac# go to e=tras - Other 3ependencies - assignments and assign relationship + by default it will come Dust save) 4ow select 1lue- go to e=tras - Other 3ependencies - <ditor - (elect ;rocedure enter in front of 1* write - Rself.I;riceMB1lueB and save 4ow go bac# go to e=tras - Other 3ependencies - assignments and assign relationship + by default it will come Dust save) 4ow go to ?911 - <nter ?2** +/ondition)+6or (td 5?2**1 ;ricing ;rocedure) - enter variant 5ed and 1lue give the rates accordingly and create the sales order. 9ell me a+out variant con i,aration? What are the ty!e o Euestions we can e"!ect in that? Gariant configuration is used where you have a configurable material like computer 3made up of components like processor, monitor, keyboard, mouse etc4. 8hese components are called as characteristics in variant config. gain this will be having values like processor can be either PL or P;, monitor can be .MQ or .0Q etc. "ased on the values selected the variant pricing will happen using the condition type G PP. Possible questions you can e9pect areA 7hat is variant configurationH 7hat is characteristicH 7hat is valueH 7hat is classH 7hat is configuration profileH 7hat is dependency and what are the typesH 7hat is a variant tableH nd the transaction codes for the above.

/O.

What is the di erence o GL;; and GL(; Ncondition recordsO? 1y condition ty!e is PRAA and Access seEuence is PRA?. And in this access seEuence ta+le (AD is availa+le. :ow when I was enterin, the PRAA in GL(; it shows error 9a+le (AD is not de inin, or the condition ty!e PRA?. $ut when I was enterin, the PRAA at GL;; it is acce!tin, it. 3ifference between ?911 and ?9"1 - if you go through the menu path you will get the v# "1 as condition record from the tamplets whereas v#11 as simple condition record. In ?911 you can store condition record for more than one condition type. This means you can have same condition record for different condition types.This feature is given to enhance the systemBs performane and not to create the duplcation of the wor# for each condition type.

2gain system is not allowing to store the record in the v#"1 for the condition type pr** and access se!uence pr*2.This is because if you see this ac se! cointains two accessses 2* and "* having the same table no.1ut you see there is the difference between the technical view of it for transfering the data from document field and condition field so you can not maintain the data at ?9"1.

//.

What is the di erence +etween /eader condition and Item condition? I know item condition a!!lies to each item in a sales document. /eader condition can only +e a!!lied to an entire document. 3ifference between header and item condition - as COA /O55</T)C (2I3 H<23<5 /O43ITIO4 I( 2;;)I/21)< 6O5 TH< $HO)< 3O/A%<4T where as item is for item.<=-(ay fright is dependent on the total weight of all the items in the documents then header condition adds on weights of all items and calculates the record accordingly. Cou have two different types of the header conditions. a) In one you can duplicate the same value throughout the document for each item.(ay discount 2O at header level which is also applicable to all the items b)(econd is the accumulation of the values of all the item at the header level as earlier e=plained for the weight,fright. These differenes are controlled through the indicator of group condition in the cond.type configuration. 2nd so obviously header condition can not have the condition record and hence access se!uence.

.PP. Disallowin, %ondition 9y!es > /ow I can accom!lish the

ollowin,@ $e a+le to DISA--0W PA$P %ondition ty!e to +e ne,ative N Invoice $lockO Cou can modify condition type from customisingS (ales and 3istribution-E1asic 6unctions-E;ricingE;ricing /ontrol-E3efine /ondition Types-E%aintain /ondition Types-/hange condition type IO1;Bs plus,minus indicator to L2L which means only positive is allowed.

.P.. In !ricin, !rocedure there are column such as reEuirement* su+ total altclty* alt+v*
accurals. What are these and where we calculate all these values which we !ut. 1 Re2uirement: 3enoted by nos and maintained in ?O6% this is a condition re!uired for a particular condition type to be e=ecuted. <g. ;5**0 re! 2 ie item relevant for pricing ?;5(,<9O10 re! & ie cost 5ebate 12O1 5e! 2&,5e! 2' etc 2. -u*total: this represents where a which table a value is stored which can be processed for further calculation. <g. for ;5** if this value is to be used for credt chec# of a customer we mar# the subtotal as 2. " Alternate $alculation ty,e0 this is also denoted by numbers and maintained in ?O6%. <g. (uppose for &' units each unit is charged R1** per unit the order value comes out to be R&'** that is calculation is done as per unit price if the client wants calculation type to be based on volume or wieght alternate calculation type can be configured. &. Alternate *ase +alue0 3enoted by no. and maintained in ?O6%. <g if the pricing scale is maintained and pricing for &' units comes under the scale of R1** per unit. the base value is &' units but if the client wants a standard base value in some casesto be assumed inspite of maintaining the scale an alternate base value is confihured that is the base value based on which the order value is to be calculated changes. '. Accruals: 2ccruals are maintained for rebate agreements it constitutes the total accumulated value which customer has earned through rebate one the rebate for certain amount is settled the amount from the accruals get deducted. Ma! Analysis @ap 2nalysis0 In simple terms0 @ap means small crac#s. In (2; world or in Information Technology world gap analysis is the study of the differences between two different information systems or applications+ e=S e=isting system or legacy system with /lient and new is (2;) often for the purpose of determining how to get from one state to a new state. 2 gap is sometimes spo#en of as Lthe space between where we are and where we want to be.L @ap 2nalysis is underta#en as a means of bridging that space. 2ctual @ap 2nalysis is time consuming and it plays vital role in 1usiness 1lueprintT2( I( ;rocessU stage. 2 through @ap 2nalysis will identify the gaps between how the business operates and its needs against what the pac#age can canBt do. 6or each gap there will be one of three outcomes which must be recorded and actioned 1. @2; must be closed and customised software can be developed 2. @2; must be closed but software cannot be written therefore a wor#around is re!uired ". @2; does not need to be closed.

2 point worth mentioning here is that at time people confuse between user-e=its and @ap 2nalysis. Aser e=its are standard gate ways provided by (2; to e=it the standard code and we can write our own code with the help of 212; wor#bench its not new functionality which we are trying to build in sap but its slight enhancement within the same code. @ap analysis is start point of 5eali>ation and once business 1lueprint is finished we have to find the reali>ation of sap system for client re!uirment and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with (2; or we have to use A(<5 e=its in case of small deviations or complete enhancements with the help of 212; to fit with the (2; system. 8he 2aps can differ from company to company. 6ost commonly, however, missing functionality is industry-specific. Scra! Sales 0rder %ycle@> (tep 10 (ales 3ocument TypeI%@ E (ales and 3istribution E (ales E (ales 3ocuments E(ales 3ocument Header01. (ales 3ocument Type0The sales document types represent the different business transactions such as In!uiry .uotation (ales Order etc. To create new sales order type always copy as with reference to similar sales order. If possible use standard sales order.2. 3efine 4umber 5anges 6or (ales 3ocuments0 %aintain number range with discussion with core team.". 2ssign (ales 2rea To (ales 3ocument Types0 2. /ombine sales organi>ations , /ombine distribution channels , /ombine divisions0 <nsure to maintain these else (ales Order creation will give error.1. 2ssign sales order types permitted for sales areas0 2ssign only re!uired (ales Order Types to re!uired (ales 2rea. This will minimi>e selection of (ales Order Type as per sales area. (ales 3ocument Item01. 3efine Item /ategories0 If possible use (tandard Item /ategory. Incase if re!uired to create new copy as from standard P maintain 4ew.2. 2ssign Item /ategories0 If possible use standard. 6ormula for deriving item category0 (ales 3ocument Type N Item /ategory @roup N Asage N Higher )evel Item /ategory M Item /ategory (chedule )ine01. 3efine (chedule )ine /ategories0 If possible use (tandard (chedule )ines. Incase if re!uired to create new copy as from standard P maintain 4ew.2. 2ssign (chedule )ine /ategories0 If possible use standard. 6ormula for deriving (chedule )ine0 Item /ategory N %5; Type , 4o %5; Type. (tep 20I%@ E )ogistic <=ecution E (hipping E 3eliveries E 1. 3efine 3elivery Types0 If possible use (tandard 3elivery Type. Incase if re!uired to create new copy as from standard P maintain 4ew.2. 3efine Item /ategories for 3eliveries0 If possible use (tandard Item /ategories for 3elivery Type. Incase if re!uired to create new copy as from standard P maintain 4ew.". 3efine4umber5anges for 3eliveries0 <nsure to maintain number range. (tep "0 I%@ E (ales and 3istribution E 1illing E1. 3efine 1illing Types0 If possible use (tandard 1illing Type. Incase if re!uired to create new copy as from standard P maintain 4ew.2. 3efine 4umber 5ange 6or 1illing 3ocuments0 <nsure to maintain number range. ". %aintain /opying /ontrol 6or 1illing 3ocuments0 %aintain relevant copy controls such as (ales Order to 1illing 3eliver to 1illing etc. Stock or Scra! SaleA8here are 1 options 1. (crap material can be identified as regular material at the point of sale. If yes then we can use the same material in (ales Order. 2. (crap material cannot be identified as regular material at the point of sale. 6or <g0 2 2utomotive seat manufacturing company purchases different grades of foam but has a single scrap yard for foams. 4ow at the point of sale it may not be possible to differentiate. 1ut we re!uire a material P stoc# to sell scrap. $e can create a dummy material say BscrapfoamB P as concerned for stoc# we can generate stoc# as per re!uirement through T./ode0 %112 using movement type '*2. Note0 In Indian <nvironment ensure to add T/( +Ta= /ollected at (ource) /ondition Type in ;ricing ;rocedure. )abels parameters What is the Di erence +etween %onsultant < End users? (2; consultant role is to build the system changes P modification,updation in currently installed (2; system for the end users. (2; <nd user only use the (2; system Dust to fetch some info or to create new thing. (o a end user is Dust using the final product which it is meant for and consultnat design the product,updation and modification. The roles and responsibilities of end users is wor#ing in easy access menu they will not have authori>ations of using img settings if they get doubt they will send !uery to the implemented company and Dust entering day to day transactions. Roles and Res,onsi*ilities of %nd Bser: Asing the software at the end or after the implementation is an <nd Aser. In sap H5 we do come across entire Org %anagement creation by an end user after the ;ersonnel strucutre is created. O% obDects li#e creation of Org Anit means functional area or dpt creation Vob and

;osition and its occupancy is with in the limits of an enduser. Initiallly the O% is created by sap consultant . In course of time a new department has appeared in the company of the client .. this has to be created by the enduser rather than depending up on the implementor... similarly new Dob and position..li#e this small things are always done by the enduser. The entire wor# of O% is purely depends upon the enduser. 2fter from this running periodical payroll and <nsuring of the Time schedules + $or# (chedules) of each employee is done from sap easy access by an enduser and the show run of payroll everymonth is by the enduser only. )i#e this lot of roles are there for an end user. $hatever the problems come across during the enduser utilisation of sap ...that will reach as tic#et to the support team E"!lain what are the .o+ res!onsi+ilities o E:D user < P0WER user. One would need user id and password to access (2; be it a developer consultant administrator or end user. <nd user is the one who performs transactions in (2; after it goes live. (uch as posting an invoice goods receipt creating purchase orders sales orders etc. ;ower Asers are users with advanced #nowledge in certain applications and with special permissions or roles. They wor# in the specialist departments in the company and are available to other users as contact persons. Durin, the SAP Im!lementation Pro.ect* what is the Role o %ore 9eam 1em+ere < %onsultants? The main responsibility of the core team member will to impart #nowledge about the companies processes to the (2; /onsultants. The consultants will be providing the core team members with templets that will describe the format of the 2(-I( documentation wherein the core team members will write the different processes of the company into these documents and submit it to the (2; /onsultants. The (2; consultants will then start mapping this into the system and provide the best possible solution that can be incorporated using the TO-1< documents. The main aim is to map the companies processes into the system. The (2; consultants will then train the core team members for how to use the (2; system. What Are SAP End Bser 1anual It is the same for every other modules although here I reference it mainly for (2; H5. 1) Cou should understand which targeted group for the end-user training is for. 3o they have any computer bac#ground or not. 2) In what way they are going to ma#e use of the manuals supplied to them during the course of training. )et us focus on how to prepare manuals0 In the client side <nd Asers are not permanent. If they get any better Dob outside they will resign and go out. <ven if you train them well again the end-user team disappears after some time. That is why implementing company+ /lient ) e=pects (2; /onsultants to prepare documents which are self e=planatory +even to a layman in (2;) and study themselves and use the sap easy access very comfortably. Hence we should prepare a document which e=plains the following things comfortably0 2) 2ll the buttons and (creens we have in sap and its importance for an end-user. 1) 2ll the transaction codes used by end user. /) The (T<; by (T<; usage methodology with screen shots and e=planatory foot notes for each Transaction code. 3) ;repare a boo# a table and columns which should have the following information0 - (l.4O. - Transaction /ode - 4avigation path - Ase of the /ode - <=pected 5esult - 2chieved 5esult - 5emar#s,2ny /omment <) Highlight the common troubles during the usage of (2; by an end- user and give the solutions +ready to use) These problems you can come across while giving the in house training for the end-users. Cou Dust place them at one place and publish it for their usage in future for any of their new Doinees as an end-user. 6) <very consultant is aware that the entire Organsiational %anagement is with end user only. %eans consultant should train the end user in entire O%.

@) $e should inform the importance of info types and usage for our purposes at e=pert mode ;2"* ;2&* etc. H) <ach field in the international infotypes should be e=plained very clearly and ensure that they are comfortable with the fields of infotypes which have been configured for their company. 6or e=ample 0 info type ***1 Org 2ssignment insists about the three structures of the H5. $e should e=plain each sub field li#e <mp @roup <mp (ub @roup ;ersonnel 2rea and (ub 2rea and its importance and relevance to their company so as to understand while processing them from the end- user point of view . $hen an employee is hired into the company now the end-user in a position to understand which employee group and subgroup ;ersonnel 2rea 2nd (ub 2rea etc. should allotted.. )i#e this whatever comes across in (2; <asy 2ccess should be insisted through the training of end users. I) 3emo e=ercises and solutions should be provided in the manuals. V) @lossary of terms and e=pansion of 2cronyms 2bbreviations should be given. )i#e this each consultant should focus on end user training and prepare the documents. What are the di erent ty!es o !ickin, strate,y? ;ic#ing (trategies The $% system includes the following pic#ing strategies0 1) 6I6O - 6irst In 6irst Out0 The system proposes the oldest !uant for the stoc# pic#. 2) )I6O - )ast In 6irst Out0 The system proposes the most recent !uant for pic#ing +!uant with most recent goods receipt date). ") ;artial !uantity - 5emoval of bro#en pallets first then standard pallets. &) )arge,small - ;ic# proposal based on !uantity. ') (helf-life e=piration date +()<3) - (imilar to 6I6O the oldest !uant is proposed for pic#ing +the !uant with the oldest shelf-life e=piration date). -) 6i=ed bin - The !uant is posted to the fi=ed bin. 7) 4o pic# strategy - %anual entry of storage bin. The strategy Lstringent 6I6OL is also available as a material-dependent pic# strategy. Here the 6I6O principle is applied across all the storage types. ;. What is the role o SD %onsultant in 9estin, while im!lementin, the !ro.ect? ?. What is Bnit testin, and Inte,ration 9estin,? 8esting A the core team members along with endusers will test whether the postings done in ! P is resulting as per the requirements of the organisation. 8hey will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data. Jnit testing is refer to the module which are going to implement. !%, 66, 'I5& etc. there will be test script based on that testing will be performed. Integration testing will be cross the modules. 66-!%-'I5& for e9ample. Integration testing is also called !I8 3 !ystem integration testing4 8esting mathologies and typesA there are N types of testingsA .. Jnit 8esting 1. !ystem 8esting ;. !ystem Integration security 8esting L. Performance 8esting M. Jser cceptance testing N. Regression 8esting Jnit testing is done in bit and pieces. @ike e.g. in !% standard order cycleK we do have .-create order, then 1-delivery, then ;-transfer order, then L-P2I and then M-Invoice. !o we will be testing .,1,;,L and M seperately alone one by one using test cases and test data. 7e will not be looking and checking:testing any integration between order and deliveryK delivery and 8&K 8& and P2I and then invoice. 7hrereas !ystem testing you will be testing the full cycle with itTs integration, and you will be testing using test cases which give a full cyclic test from order to invoice. !ecurity testing you will be testing different roles and functionalities and will check and signoff. Performance testing is refered to as how much time : second will take to perform some actions, like e.g. P2I. If "PP defination says M seconds for P2I then it should be M and not N second. Jsually it is done using software. Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact e9isting functionality. 8his will be done on each phase of testing. Jser cceptance 8estingA Refers to 5ustomer testing. 8he J 8 will be performed through the e9ecution of predefined business scenarios, which combine various business processes. 8he user test model is comprised of a sub-set of system integration test cases. 7e use different software during testing. 6ost commonly use are

8est %irectorA which is used to record requirement, preparing test plan and then recording the progress. 7e will be incorporating defects that are coming during these testings using different test cases. 6ercury @oad RunnerA is used for performance testing. 8his is an automatic tool. What does the ollowin, terms means @ > 9echnical Bnit 9estin, > )unctional Bnit 9estin, > Inte,ration9estin, > Golume 9estin, > Parallel 9estin,? 8echnical Jnit 8estingU 8est of some technical development such as a user e9it, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. successful test only proves the developed code works and that it performed the process as as designed. 'unctional Jnit 8estingU 8est of configuration, system settings or a custom development 3it may follow the technical unit testing4 8hese usually use actual data or data that is masked but essentially the same as a real data set. successful test shows that the development or configuration works as designed and the data is accurate as a result. Integration8estingU 8esting a process, development or configuration within the conte9t of any other functions that the process, development or functionality will touch or integrate . 8he test should e9amine all data involved across all modules and any data indirectly affected. successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas. Golume 8estingU testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, successful test indicates that the processes will not slow or crash the system due to a full data set being utili=ed. Parallel 8estingU 8esting the new system or processes with a complete data set while running the same processes in the legacy system. successful test will show identical results when both the legacy system and new system results are compared. I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several. What kind o testin,s that are carried out in testin, server? .. Individual 8esting 3 Individually which weTve created4 1. Regressive 8esting 3 Entire Process4 ;. Integration 8esting 3 long with other integrated modules4 8he ; types of testing is as followsA.. Jnit testing 3where an individual process relevant to a !% or 66 etc is tested4 1. Integration testing 3where a process is tested that cuts across all areas of ! P4. ;. !tress testing 3where lots of transactions are run to see if the system can handle the data4 What are the di erences +etween a unctional and +usiness consultant? 8he difference between 'unctional consultant and "usiness consultant are as followsA .4 funcitonal consultant is able to configure the system unlike business consultant. 14 'unctional consultant know more about business process unlike "usiness consultant. ;4 business consultant will bring business process knowledge and provide it to functional consultant who in turn used this knowledge to configure the system. L4 'unctional consultant has more configuration knolwledge then "usiness consultant. 9he res!onsi+ilities o a su!!ort consultant are@ - Primarily responsible for ?andling tickets and application support to the endusers - 7hen an issue comes diagnose, analyse and solve the issue - Responsible for any enhancements - 7riting functional specs and interacting with bapers to develop any user e9its - 8raining the end users and preparing end user training material )or those who wished to know the role o a unctional consultant. "elow is one viewA functional consultant evaluates the demands in talking with the customerTs representatives, transforms the essence into an abstract and algorithmic business model. ?ence, he identifies the use cases and transforms them into logical and technical views. 8hen the main task startsA customi=ing the respective business area and making sure the system reacts in the manner according to the constraints of the requested use case. 8he consultant documents the settings and prepares proper guidelines that allow other consultants to do further changes or repairs with due efforts. 8he consultant takes care that proper training is given to the users and that the system is usable, performing appropriately and the business flow is complete and correct. %uring go live he assists the technical staff by testing the behaviour of the system.

fter go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enhancements. 8he main duty of a consultant is to transfer e9ternal know-how to the client. It is not manpower that counts but intelligence, understanding of processes, a feeling for defects and general a common sense. SAP 9ickets > What Is 9hat? ?andling tickets is called Issue 8racking system. 8he errors or bugs forwarded by the end user to the support team are prioriti=ed under three seviority ?igh, 6edium and @ow. Each and every seviority as got its time limits before that we have to fi9 the error. 8he main Bob of the supporting consultant is to provide assistance on line to the customer or the organisation where ! P is already implemented for which the person should be very strong in the subBect and the process which are implemented in ! P at the client side to understand,to analyse,to actuate and to give the right solution in right time.8his is the Bob of the support consultant. 8he issues or the tickets3problems4 which are arised is taken care of on priority basis by the support team consultants. 8he work process in support proBects are given below for your reference. .. 8he customer or the end user logs a call through any tool or by mail 3R %IF4. 1. Each one of the support team is a part of support group. ;. 7henever a customer logs a call he :she has to mention to which work group 3by name4. L. &nce the calls came to the work group the support consultant or the team need to send an IR 3Initial Response4 to the user depending upon the priority of the calls. 38op,?igh,6ed,@ow,#one4 M. 8hen the error is fi9ed, debugged by the support consultant or the team. 8hen after testing properly by generating 8R38ransport Request through the basis admin4 N. 8hen it is informed to the end user:customer:super user about the changes which have moved to the production server by 58! process. 8hese are the process. In summary, what I understand is that if any configuration or customi=ation is required to solve the issue, then the consultant have to work on %EG 5lient, then the end user will test it in the E client and after approval the " !I! consultant has to transport it to the PR&%J58I&# client. n e9ampleA 8ickets in !% can be considered as the problems which the end user or the employee in the company face while working on R:;. 8ickets usually occur during the implementation or after theimplementation of the proBect. 8here can be numerous problem which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline. 8o begin with , we should give Q8I5SE8Q to you for not knowing it. ?ere is an eg of a ticket raiseA End user is not able to .. 5reate !ales order for a customer from a #ew plant , since shipping point determination is not happened . 3 7ithout !hipping point the document becomes I#5&6P@E8E and he will not be able to proceed further like %E@IGER>, "I@@I#24. ?e raises a ticket and the priority is set in one of the belowA .. @ow 1. 6edium ;. ?igh. #ow you need to solve this ticket. >ou would analy=e the problem and identify that the !P configuration has to be done for the new plant. >ou would request a transport for %EG 5@IE#8 to " !I!. >ou do the change and Request one more 8ransport to " !I! for E client. 8he End user will test the same by creating a sales order for the new plant and approve it. 'inally, you request a transport to move the changes to PR&%J58I&#. &nce the change is deployed in production the 8I5SE8 is closed. 7hat I have given is a small e9ample. >ou would get some real issues with severity ?I2? in your day-day support. What is maintainin, S-A in !roduction su!!ort? !@ is an abbreviation for Q!ervice @evel greementQ. It means to have guaranteed reaction or resolving times for incidents 3U trouble tickets4. 'or instance you could have defined the following !@ levels 'or e9ampleA 2oldA Reaction time U ;P minutes, resolving time U L hours !ilverA Reaction time U L hours, resolving time U 1L hours !@ s normally are part of a contract between a customer and a service provider. V&r in details descriptionAV !@ are !ervice @evel greements to resolve the tickets by the market. !@ means !ervice @evel agreement. It is the service agreement between a 5ompany and a service provider. 'or e9ample an I8 &rgani=ation providing support of ! P : other software : hardware has a agreement. 8his can be for

e9ample categori=ed based on criticality of the incident. ?igh priority incident has to be resolved on .P hours. 6edium priority incident has a ; days time to resolve etc V-- nu radha !@ Ts are nothing but !ervice level agreements. 8hese are defined in proBect preparation phase and client would have made an agreement with the company for the level of service. 8he !@ Ts are applicable in Production as well as maintanence support proBects. 'or e9ampleA if your company follows a ticketing process3a ticket is nothing but an environment contains complete description of the problem which contains !hort description, problem, customer contact details, sreen shots of the error et9c.,4 and for each ticket there will be a severity for e9ample business critical issues or problems may be treated as high or top severitieTs. In those case your company or your team has to deliver the solution to the customer in agreed time limit or otherwise you might end up missing !@ Ts. !@ Ts has two important time specifications .. IPR8 --- initial problem response time --- this is nothing but time taken to respond to the problem. 1. PR8 --- Problem response time ----- this is nothing but time taken to solve the issue or problem. "oth IPR8 and PR8 will be different for different severitieTs. Where to ind the Bser E"its on Sales and Distri+ution alon, with unctionality? 8o see the detail go to !PR& --- !ales and %istribution ---- !ystem 6odifications --- Jser E9its 8here you will find all the details by checking I62 ctivity %ocumentation. >ou will have Jser e9it for !ales %ocument Processing. 8his I62 step describes additional installation-specific processing in sales document processing. In particular, the required I#5@J%E! and user e9its are described. Involved program components !ystem modifications for sales document processing affect different areas. %epending on the modification, you make the changes in the program components providedA - 6GLM 8WW 'or entering metadata for sales document processing. Jser-specific metadata must start with QWWQ. - 6GLM &WW 'or entering additional installation-specific modules for sales document processing which are called up by the screen and run under P"& 3Process "efore &utput4 prior to output of the screen. 8he modules must start with QWWQ. - 6GLM IWW 'or entering additional installation-specific modules for sales document processing. 8hese are called up by the screen and run under P I 3Process fter Input4 after data input 3for e9ample, data validation4. 8he modules must start with QWWQ. - 6GLM 'WW and 6GLME'W. 'or entering installation-specific '&R6 routines and for using user e9its, which may be required and can be used if necessary. 8hese program components are called up by the modules in 6GLM &WW or 6GLM IWW. >ou will find all Jser E9its on !ales and %istribution along with functionality.

SD Integration points with other modules

SD module is highly integrated with the other modules in SAP.
Sales Order Integration Points Availability Check Credit Check Costing a! "eter#ination rans$er o$ %e&uire#ents "elivery ' (oods Issue Integration Points Availability Check Credit Check %educes stock %educes Inventory ) %e&uire#ent *li#inated Module MM FI CO/ MM FI PP/ MM Module MM FI MM FI/ CO PP/ MM

+illing Integration Points "ebit A/% Credit %evenue ,-dates (/ . / a!0 discounts0 surcharges0 etc12 Milestone +illing %eturn "elivery ' Credit Me#o Integration Points Increases Inventory ,-dates (/ . Credit Me#o Ad3ust#ent to A/% %educes %evenue -

Module FI/ CO FI/ CO FI/ CO PS Module MM FI FI FI FI

D. /ow we can do invoice s!lit de!endin, on item cate,ory in which scenario we will use? Cou first need to go for copying controls either from sales to billing +invoice) or delivery to billing or billing to billing use transactions +vtaa vtaf vtla vtfa vtfl vtff) all possibilities for copy controls. this basicly is flow of doc to doc. +may it be sales to billing del to bil or bil to bil etc..) -E this is where you see the Item category and you control whether split is possible or not with the indicatorL1L. eg0 representing split in invoice based on item category. The field here Ldata ?159,?15;L +headre,item)whcih actually is used for splits or combining different deliveries. create a splitting rule using ?O6% +you need access #ey to get here). Here you define comparisions for the fields at header table and item tables and the comparision fields say (;25TLdivisionL. Lpurchase order L1(T93 Instance0 ' sales orders combined into 2 deliveries and the split at the invoice would be ' individual billing with respect to fields ;O and 3Iv. of each sales order would let you create ' billings. Cou need to define the e=act LfieldL in the comparisions both at header and item level that could lead to invoice split. the #ey here is the field that is different from header to item will cause split at the item level. What is the di erent +etween A-E* ID0% and $API? A9% 2)< is (2; proprietary technology that enables data communications between two or more (2; 5," systems and,or 5," and e=ternal systems. $hen a new enterprise resource planning +<5;) solution such as 5," is implemented companies have to interface the <5; system with legacy systems or other <5; systems. 2)< provides intelligent mechanisms where by clients can achieve integration as well as distribution of applications and data. 2)< technology facilitates rapid application prototyping and application interface development thus reducing implementation time. The 2)< components are inherently integrated with (2; applications and are robust leading to a highly reliable system. 2)< comes with application distribution,integration scenarios as well as a set of tools programs data definitions and methodologies that you can easily configure to get an interface up and running. #API 12;Is provide a stable standardi>ed method for third-party applications and components to integrate into the 1usiness 6ramewor#. These interfaces are being specified as part of (2;Bs initiative with customers partners and leading standards organi>ations. 2lso (2; has implemented the emerging ObDect 2pplication @roup +O2@) specifications with 12;Is. Pros and %ons or +oth $API and %all 9ransaction $API One of the big plusses for 12;Is is that the interface and function are not supposed to change. This is a big plus when you do upgrades or hot pac#s because the transaction can change +format re!uired inputs etc) which means you then need to update the call transaction. (ome of the 12;Is are better documented and easier to use than others. Cou usually need to perform the 12;I that actually does the /O%%IT after you call your 12;I. The ;rogram coding for calling a 12;I is usually cleaner than setting up the screen flow etc for the /all Transaction. Cou donBt need to worry about special data circumstances interrupting the normal data flow of the screens and causing errors because of that. 12;Is probably have better performance since they donBt do the screen flow processing.

In general if the 12;I e=ists for the transaction you want to perform and you can figure out how to use it the 12;I is probably the best way to go. This is Dust from my e=perience wor#ing with both 12;I and /all Transaction. I have had some very good successes with 12;Is but very occasionally found that I could not get the 12;I to perform the update I needed. A$AP 9i!s The interface concept of the classic 5," is based on two different strategies0 5emote 6unction /alls +56/) and data e=change through I3oc message documents. 56/ ma#es direct and synchronous calls of a program in the remote system. If the caller is an e=ternal program it will call an 56/-enabled function in 5," and if the calling program is the 5," system it will call an 56/-function in another 5,"-system or it will call a non-5," program through a gateway-pro=y +usually rfce=ec.e=e). 12;Is are a subset of the 56/-enabled function modules especially designed as 2pplication ;rogramming Interface +2;I) to the (2; business obDect or in other words0 are function modules officially released by (2; to be called from e=ternal programs. I3ocs are te=t encoded documents with a rigid structure that are used to e=change data between 5," and a foreign system. Instead of calling a program in the destination system directly the data is first pac#ed into an I3oc and then sent to the receiving system where it is analy>ed and properly processed. Therefore an I3oc data e=change is always an asynchronous process. The significant difference between simple 56/-calls and I3oc data e=change is the fact that every action performed on I3ocs are protocolled by 5," and I3ocs can be reprocessed if an error occurred in one of the message steps. $hile I3ocs have to be understood as a data e=change protocol <3I and 2)< are typical use cases for I3ocs. 5," uses I3ocs for both <3I and 2)< to deliver data to the receiving system. 2)< is basically the scheduling mechanism that defines when and between which partners and what #ind of data will be e=changed on a regular or event triggered basis. (uch a set-up is called an 2)<-scenario. The philosophical difference between <3I and 2)< can be pinned as follows0 If we send data to an e=ternal partner we generally spea# of <3I while 2)< is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the I3oc data. The difference is made clear when we thin# of a purchase order that is sent as an I3oc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However if we send the purchase order via 2)< to another 5," system then the receiving system will store the purchase order also as a purchase order. 1I-ES90:E $I--I:M %0:)IMBRA9I0: 6ilestone billing means distributing the total amount to be billed over multiple billing dates in the billing plan. s each milestone is successfully reached, the customer is billed either a percentage of the entire proBect cost or simply a pre-defined amount. %uring sales order processing, the system determines from the item category whether a billing plan is required and, if so, which type of plan 8he type of billing plan that is determined at this point is set up in 5ustomi=ing and cannot be changed in the sales document. "illing plans for periodic billing and milestone billing plans for proBect-related milestone billing have different overview screens so that you can enter data relevant to your processing. 'or e9ample, for milestone billing, you must be able to enter data to identify the individual milestones. I62 configuration requires A.. 1. ;. L. M. N. 0. O. 6aintain billing plan types for milestone billing in &G"&. %efine date description in !6;P - GX8G8". 6aintain %ate 5ategory for "illing Plan 8ype I# &G"$. llocate date category in !6;P - GX8'P@ X8>. 6aintain date proposal for "illing Plan 8ype in &G"6. ssign "illing Plan 8ype to !ales %ocuments 8ype in &G"P. ssign "illing Plan 8ype to Item 5ategories in &G"R. %efine rules for determining the date in &G"!.

6ilestone billing is typically used for billing proBects, such as plant engineering and construction proBects. !uch proBects often include a series of milestones that mark the completion of different stages of the work. In the ! P R:; !ystem, milestones are defined in a network along with planned and actual dates for the completion of work. 8he milestones are also assigned to the billing dates in the billing plan. Each milestone-related billing date is blocked for processing until the ProBect !ystem confirms that the milestone is completed. %elivery-relevant order items for which a milestone billing plan applies are billed on the basis of the requested delivery quantity and not on the total of the confirmed quantities. 8he

connection between the proBect and the sales document item is made in the individual schedule lines of the item. Each schedule item can be assigned to a network in a proBect. 8o display the proBect-related data for a schedule line, proceed as followsA In one of the overview screens of the sales document, select .. Item -Y !chedule lines. 1. 6ark the schedule line and select Procurement details. 8he following figure shows an e9ample of milestone billing where only the 5ontract have been billed A &rder Item 8urbine .PP,PPP "illing Plan "illing date %escription R Galue "illing "lock 6ilestone "illing !tatus P.-.P-/L 5ontract .P .P,PPP - 9 9 P.-P;-/M ssembly ;P ;P,PPP 9 9 P.-PL-/M 6aintenance ;P ;P,PPP 9 9 P.-PM-/M cceptance ;P ;P,PPP 9 9 P.-PN-/M 'inal invoice .. .. 9 #etwork: ctivities 6ilestone Estimate ctual ssembly P.-P;-/M P.-P;-/M 6aintenance P.-PL-/M cceptance P.-PM-/M 'or each billing date in a milestone billing plan, you can specify whether the billing date isA .. fi9ed 1. always updated with the actual date of the milestone ;. updated with the actual date of the milestone, if the date is earlier than the planned billing date for the date Reasons )or 1akin, Any Pricin, Procedure in SAP ;. Why we are maintainin, se!arate !ricin, !rocedure or inter com!any sales and +usiness !rocesss. ?. What is the di erent +etween standard and inter com!any !ricin, !rocedure and what ty!e condition ty!e we are usin, in this intercom!any. 8here are two simple reasons for making any Pricing Procedure in ! P !% 6odules. .4 "usiness Reason. 7hat are the pricing aspects or strategies you want to apply for the client requirement in order to sell their goods or render services, is all about the reason for various pricing procedures. EgA %omestic sales pricing procedure, - E9port Pricing Procedure, - rebate pricing procedure or - ?igh %iscount oriented pricing Procedures. - repair pricing procedures. >ou have your own conditions intended to few transactions only. Put all this conditions as a set defining your own Procedures. It may even include special requirements and formulas applied for such Pricing Procedures. 14 special pricing procedures, in order to facilitate added functionalities of ! P pricing architecture, we must define new pricing procedure. ! P !tandard programmes checks these special Indicators in-order to do some required functions. s a e9ample ., you need to have a Pricing procedure for condition supplement inorder to use the condition supplements. 8he condition supplement pricing procedure must be given in the condition type definitions 3v:PN4 of the Pricing 5ondition where you need to supplement, without which ! P !% 5ondtion !upplements functionality doesnt work. s a e9ample 1, you need to have a Pricing procedure for Inter 5ompany "illing 5onditions3IGP. Z IGP14 inorder to be active for Inter 5ompany "illing specific transactions. 8hus make sure that, the procedure wouldnot apply for non-Inter company transactions. EgA S PPPP for 5ondition !upplement for S PP - PRPPPP for 5ondition !upplement for PRPP - I5 P. for Inter-5ompany "illing ?ere I would like to remind about a important field in pricing.

In G:PO of defining a new Pricing Procedure, in main screen, you have a field called 8!PP 38ransaction !pecific Pricing Procedure4. 8his has to be ticked on for Intercompany "illings. 8he ! P help reads for this field as JnderA 8ransaction-specific pricing procedure Pricing procedure transaction-specific indicator "efore Release L.P , no special pricing procedures were used for intercompany billing and rebate credit memos, programs were Bust set accordingly to deal with these situations. s of Release L.P you are offered greater fle9ibility in the form of the option to define special pricing procedures for intercompany billing and rebate credit memos. 'or reasons of future compatability, you will still be able to use the old program specifications. 'or this reason, you must set this indicator if you want to create a special pricing procedure. 8his is to prevent the program settings being used. 8his indicator is also used as of Release L.P to redetermine the condition class and the statistical condition indicator when copying from a reference document. E9ampleA >ou copy prices from a shipment document to the billing document. 8he prices should lead to a surcharge in the billing document. 8his is guaranteed by the redetermination of the condition class in the pricing procedure. !ame case with !tandard Pricing procedure or Inter 5ompany Pricing Procedure. 8his configuration is done when user request for new pricing condition type other than the standard ones provided by the system.

Important Tables for SAP SD

Sales and Distribution: Table Customers acct) 45A6 45+6 45+7 45+9 45+4 454A 4544 45:: 45:I 45:P 45:" 45:S 4.PA :+A4,4 :+,4 :+A4 :+4" :+,P :+AP :+PA :+FA :+*P :++* Description (eneral "ata Custo#er Master Co1 Code "ata /-ay#ent #ethod0 reconciliation Custo#er Pay#ent 8istory Custo#er Master "unning in$o Custo#er Master +ank "ata Custo#er Master Credit Mg#t1 Custo#er Master Credit Control Area "ata /credit li#its2 Sales Area "ata /ter#s0 order -robability2 Custo#er Master a! Indicator Partner Function key Out-ut ty-e Custo#er Master Shi- "ata Custo#er/:endor .ink :+A4 ; :+,4 8eader Status and Ad#inistrative "ata Sales "ocu#ent - 8eader "ata Sales "ocu#ent - +usiness "ata Ite# Status Sales "ocu#ent - Ite# "ata Partners "ocu#ent Flo< Sales "ocu#ent Schedule .ine Sales %e&uire#ents= Individual %ecords "elivery "ocu#ent ite# data0 includes re$erencing PO "elivery "ocu#ent 8eader data +illing "ocu#ent 8eader +illing "ocu#ent Ite# Shi--ing ,nit Ite# /Content2 Shi--ing ,nit 8eader

Sales Documents

SD Delivery Docume.IPS .I4P Billing Document SD Shipping Unit :+%4 :+%P :*4P :*PO

Table

Description

VBAKUK VBUK VBKD VBEP VBFA VBAK VBUP VBAP VBPA VBBE K!VV K!VI K!VP K!VD K!VS KLPA K!A+ K!B+ K!B0 K!B1 K!BK K!KA K!KK K3!V LIKP LIPS VBEH

Sales Document Header and Status Data Sales Document Header Status and Administrative Data Sales Document Business Data Sales Document Schedule Line Data Sales Document Flow Sales Document Header Data Sales Document Item Status Sales Document Item Data Sales Document Partner Sales Re uirements Individual Records "ustomer #aster Sales Data "ustomer #aster $a% Indicator "ustomer #aster Partner Functions "ustomer master record sales re uest &orm "ustomer #aster Shi''in( Data "ustomer)Vendor Lin*in( ,eneral Data in "ustomer #aster "ustomer #aster -"om'an. "ode/ "ustomer Pa.ment Histor. "ustomer master -dunnin( data/ "ustomer #aster -Ban* Details/ "ustomer master credit mana(ement2 "entral data "ustomer master credit mana(ement2 "ontrol area data "onditions -$ransaction Data/ SD Document2 Deliver. Header Data SD document2 Deliver.2 Item data Schedule line histor.

VBLB VBLK VBRK VBRP VEKP VEP3 VEPV,

Sales document2 Release order data SD Document2 Deliver. !ote Header Billin(2 Header Data Billin(2 Item Data Handlin( Unit 4 Header $a5le Pac*in(2 Handlin( Unit Item -"ontents/ Deliver. Due Inde%

Fundamentals of SAP SD Pricing Concepts

Pricing is one of the core concepts in SAP SD and all SD consultants need to know pricing. Just as the name says, SAP SD Pricing is configuring the system to effectively determine the price of a product under different circumstances. The most easiest example to explore pricing is to take a simple grocery ill and expand on it.

!onsider this as an extract of a grocery ill. "ou have purchased some items from the Produce section and some from the stationery section. "our Produce su #total is $%.&& and your stationery su #total is $&.&&. "ou have een taxed $&' and your total comes to ().&& as shown in the picture a ove.

*et+s ,ust explore on how the pricing is calculated on line item -o. $& # .ilk. /owever, they might not e shown on the ill ut are internal to the company selling the product. *et+s explore how a potential ill could e created. As you can see from the picture elow, there is a 0ase Price from the price list # 1.&& . And since the ill is for a retail customer , there is a retail discount of $.&&. So the su # total for the line item $& is 2.&&.

Condition Type :
The types of calculation 3 whether its a price, discount or a tax calculation, and in price # if its a retail price or a wholesale price or a variant price etc 4 are called condition type. -ormally, condition types of a particular kind are not cumulative # .eaning if there are more than $ Pricing condition type, they don+t add up # instead the last pricing condition type is taken y the system. There are some exceptions to this however. 5or example when pricing a car, its the sum of the different pricing condition types that gives you the Price. They are called variant condition types.

Requirement
A re6uirement is a piece of code that calculates if a particular condition type should e evaluated or not. This is not necessarily the only way to check if. /owever, since this involves hard#coding the logic in the system, this functionality should e used sparingly. 5or example, the following piece of code says, 78f the item is not relevant for pricing # do not price it7. 5unctional consultants should e aware of the final result S"#S90:!. S90:! stands for S90 :outine :eturn !ode. Typically in SAP, a return code of & signifies a success. ;therwise its a failure. < Pricing is turned on in item category configuration 3T=AP4 form ko ed>&&(. sy#su rc ? 2. if komp#kposn ne &. check@ komp#prsfd ca +0A+. check@ komp#kBnep ? space. endif. sy#su rc ? &. endform. < Prestep form ko ev>&&(. sy#su rc ? &.

endform.
> Pricing is turned on in ite# category con$iguration / :AP2 $or# kobed?@@A1 sy-subrc B 71 i$ ko#--k-osn ne @1 check= ko#---rs$d ca C+DC1 check= ko#--kEne- B s-ace1 endi$1 sy-subrc B @1 end$or#1 > Preste$or# kobev?@@A1 sy-subrc B @1 end$or#1 Similarly, the following picture shows a simple re6uirement. There are ( types of discount condition types # :etail and Cholesale. 8f the customer is retail, then apply that discount. 8f the customer is wholesale, then apply the other discount. So the actual total depends on who the ;rder+s customer is. The same can e achieved using many different ways, ut this is sure one hard#coded way to do it.

Sub-Total
A su #total as the name implies holds temporary totals efore the final price is calculated. As shown in the picture elow, the Dross price is a su #total that results from the ase price. The -et Price is a su #total that is arrived at su tracting the Discount percentage off of the Dross Price. There are many additional steps that might e re6uired to arrive at the final price. 5or example, if the item is taxa le, should the tax e applied on the Dross Price or the -et Price..E That actually depends on the usiness scenario. /owever, the Su #totals allow for easily identifying and computing values for further use.

Alternative Calculation Type

The value 1.&& for the 0ase Price 3 shown in the picture a ove 4 is derived ased on condition records which we will see much further in the discussion. /owever, if the condition type should -;T e calculated ased on a condition record, ut should e calculated ased on an external or internal logic, then an alternative calculation routine should e used. Fach alternative calculation routine is a G digit num er etween $ and HHH that contains a piece of code that does some calculation either internally or externally and returns a value. That value will e used to calculate the condition type as opposed to a condition record. A simple example for the same is 9S Taxes. Taxes in the 9S and !anada are ased on Jurisdiction code. There are around 1&&&&I ,urisdiction codes in the 9S alone 3 0ased on all possi le variations of !ity, !ounty, State and District 4. And they change continuously. So it is not practical for companies to keep track of the changes in tax rates. There are external tax companies 3 !alled Tax =endors 4 that only does this. So it is wiser for companies to ,ust call an external tax vendor using a remote function call, get the tax rate as relevant for the corresponding ,urisdiction code and return that value to the pricing procedure.

Account

ey

Chen an invoice is created, the finance departments wants the corresponding Sales, expenses, tax accounts etc to e updated on the fly. The account key in the pricing procedure 3 with the help of Account Determination 4 helps in identifying which DJ* account this should the amount flow into. A simple example could e

Account Key F:* F:* F:S F:S

Description Sales Sales Discounts Discounts

!ustomer AJ! Droup Cholesale Cholesale Cholesale Cholesale

.aterial AJ! Droup !onsuma les Stationery !onsuma les Stationery

DJ* Account $&&&&2& $&&&&1& $$&&&2& $$&&&1&

Statistical
This is a flag 3 A !heck mark 4 that is used to signify if the pricing condition type is eing used in the calculation or not. 5or example, the actual cost of the material 3 not the price ut the cost price 4 is availa le in all pricing procedures, since this is used y !ontrolling 3 !; 4 to evaluate profita ility. /owever, the value should not e relevant when pricing to the customer. So, if you need informational condition types for further analysis set them up in the pricing procedure as statistical.

Print Flag
The print flag is another check mar that is used to tell SAP if the particular pricing condition type should e printed on the final ill or not. As discussed in the previous example, the cost condition type should not e printed on the invoice. Cith the advent of advanced technologies like Smart5orms, Ado e 5orms etc, this flag has almost no use 3 Since what is printed and what is not is decided mostly y these programs 4.

SAP Pricing Configuration

-ow that we have understood the asic terminology used in Pricing, let+s dig deeper into the configuration. The configuration is very similar to ! P 5ondition 8echnique. Ce will only discuss the rest of the pricing relevant stuff going forward.

!aintain Condition Records

A condition record is actually a row in a data ase ta le. The actual data ase ta le is defined in the Condition Table assigned to the Access Sequence. *et+s start y creating an condition record for a condition type P:&&. The transaction code to create the same is L=K$$M. The menu path is L *ogistics #N Sales and Distri ution #N .aster Data #N !ondition #N Select 9sing !ondition Type M. Fnter the pricing condition type, and select the right !ondition Ta le.

Fnter the values and save the record. There are some advanced concepts like re ate functionality, condition supplements, scales etc which will not e discussed here.

SAP Pricing DEMO

*et+s start y creating a new sales order for the customer and material that we have created condition records for and see the effect of the condition records on the sales order pricing. A sales order is shown elow for !ustomer $2&& and for the material .#&$ that we created the condition record for with a price value P:&& of 1&. Select the line item and click on the -ickel utton in the ottom 3 Pricing utton 4 to view the pricing details for that line item.

"ou will e taken to the *ine 8tem+s !ondition ta where the pricing details can e viewed specific to that line item. As you can see, the P:&& value is set as 1&.&& which is exactly what we have set in the pricing condition record.

*et+s say some ody else has entered the condition record for that material and you have ,ust created the sales order. -ow if you want to analyBe and acktrack why the pricing is coming up as 1&.&& click on the Analysis utton as shown elow.

A new screen opens up where if you explore the particular condition type 3 P:&& in this case 4 you will see for which com ination 3 customer material in this case 4 that pricing has een picked up.

"ou can ,ust click on the area highlighted a ove to see further details of the condition record. 5or example, if you click on P:&& a ove, you will e taken to a new screen that shows you the actual condition record, its validity 3 =alid 5rom and =alid To dates 4 along with the value for P:&&.

This concludes SAP SD Pricing 5undamentals.

$APIs realted to SD $APIQSA-ESMR0BPQME9QDE9AI!ales 2roupA %isplay #ame $APIQSA-ES0))I%EQME9QDE9AI!ales &fficeA %isplay #ame $APIQSA-ES0))I%EQMRPQECIS9 !ales &ffice : !ales 2roupA E9istence 5heck $APIQSA-ES0RMQECIS9 !ales &rgani=ationA E9istence 5heck $APIQSA-ES0RMQME9QDE9AI!ales &rgani=ationA %isplay %ata $APISD0RDERQME9DE9AI-ED-IS9 !ales &rderA @ist of ll &rder %ata $APIQ0RDERQ%/A:MEQS9A9BSQME9 5hange status for order $APIQSA-ESD0%BQ%REA9E)R01DA9A 5reating a !ales %ocument

$APIQSA-ES0RDERQ%/A:ME !ales &rderA 5hange !ales &rder $APIQSA-ES0RDERQ%REA9E)R01DA9; !ales &rderA 5reate !ales &rder $APIQSA-ES0RDERQ%REA9E)R01DA9? !ales &rderA 5reate !ales &rder $APIQSA-ES0RDERQ%REA9E)R01DA9A 5reate sales order, no more maintenance $APIQSA-ES0RDERQME9-IS9 !ales orderA @ist of all orders for customer $APIQSA-ES0RDERQME9S9A9BS !ales orderA %isplay status $APIQSA-ES0RDERQSI1B-A9E !ales &rderA !imulate !ales &rder Sales related e"its 5ustomer e9its 356&% transaction4 Enhancement code Descri!tion !% P&PP. ctivating !ourcing !ubitem Euantity Propagation !%8R6PP. Reschedule schedule lines without a new 8P check GLM PPP. %etermine alternative materials for product selection GLM PPP1 Predefine sold-to party in sales document GLM PPP; 5ollector for customer function modulpool 6GLM GLM PPPL 5opy packing proposal GLMEPPP. Jpdate the purchase order from the sales order GLMEPPP1 %ata transfer in procurement elements 3PRreq., assembly4 GLM@PPP. !% component supplier processing 3customer enhancements4 GLMPPPP. !% customer function for cross-company code sales GLM!PPP. Jpdate sales document from configuration GLM!PPP; 6RP-relevance for incomplete configuration GLM!PPPL Effectivity type in sales order GLM7PPP. !% !ervice 6anagementA 'orward 5ontract %ata to Item GLN?PPP. !% 5ustomer functions for resource-related billing GNP'PPP. !% "illing plan 3customer enhancement4 diff. to billing plan Include routines reserved for customers 3need a modification key4 Include Descri!tion 6GLM 8WW 'or entering metadata for sales document processing 6GLM &WW 'or entering additional installation-specific modules for sales document processing which are called up by the screen and run under P"& 3Process "efore &utput4 prior to output of the screen. 6GLM IWW 'or entering additional installation-specific modules for sales document processing. 8hese are called up by the screen and run under P I 3Process fter Input4 after data input 3for e9ample, data validation4. 6GLM 'WW and 6GLME'W. 'or entering installation-specific '&R6 routines and for using user e9its, which may be required and can be used if necessary. $illin, related e"its 5ustomer e9its 356&% transaction4 Enhancement code Descri!tion !%G'FPP. Jser e9it header line in delivery to accounting !%G'FPP1 Jser e9it for :R line in transfer to accounting !%G'FPP; Jser e9it cash clearing in transfer to accounting !%G'FPPL Jser e9it 2:@ line in transfer to accounting !%G'FPPM Jser e9it reserves in transfer to accounting !%G'FPPN Jser e9it ta9 line in transfer to accounting !%G'FPP0 Jser e9itA "illing plan during transfer to ccounting !%G'FPPO Jser e9itA Processing of transfer structures !%-'I !%G'FPP/ "illing doc. processing SI%&#& 3payment reference number4 !%G'FP.P Jser e9it item table for the customer lines !%G'FP.. Jsere9it for the komkcv- and kompcv-structures GPMIPPP. Jser e9its for billing inde9 GPM#PPP. Jser E9its for Printing "illing %ocs. using P&R Procedure GNP PPP. 5ustomer functions in the billing document

GNPPPPP. %ata provision for additional fields for display in lists GN. PPP. 5ustomer enhancementA Pricing Delivery related e"its 5ustomer e9its 356&% transaction4 Enhancement code Descri!tion GMPP!8 8 %eliveryA Item !tatus 5alculation GMPEPPP. %elivery 6onitorA Jser E9its for 'illing %isplay 'ields GMPRPPP. 5ollective processing for delivery creation GMPRPPP1 5ollective processing for delivery creation GMPRPPPL 5alculation of !tock for P&s for !hipping %ue %ate @ist GMP!PPP. Jser E9its for %elivery Processing GM;5PPP. Rough workload calculation in time per item GM;5PPP1 7Z!A R7E enhancement - shipping material type:time slot GM;7PPP. Jser e9its for creating picking waves G6%EPPP. !hipping InterfaceA Error ?andling - Inbound I%oc G6%EPPP1 !hipping InterfaceA 6essage PI5S!% 3Picking, &utbound4 G6%EPPP; !hipping InterfaceA 6essage !%PI5S 3Picking, Inbound4 G6%EPPPL !hipping InterfaceA 6essage !%P 5S 3Packing, Inbound4 GP1GPPP. !ales area determination for stock transport order GP1GPPP1 Jser e9it for storage location determination GP1GPPP; Jser e9it for gate [ matl staging area determination 3headr4 GP1GPPPL Jser E9it for !taging rea %etermination 3Item4 Include routines reserved for customers 3need a modification key4 Include Descri!tion 6GMP 'W. Jser E9its for %elivery Processing 6GMP 'W1 Jser E9it for "atch Euantity llocation 6GMP 'W; @IP!-S&EJI 3Picking is subBect to confirmation4 determination 6GMP 'WS 8he user e9its in this include can be used to fill the condition tables for material listing and material e9clusion 3S&6S2 and S&6P24 and product selection 3S&6S% and S&6P%4 with own data. 6GMP 'W@ In delivery creation process for sales orders there is the possibility to restrict the delivery creation to some order items. If these order items are member of a delivery group, but not all items of this delivery group are includes in the restriction range of the order item nubers, you can specify in this routine what to do. 6GMP 'WP 8his user e9it can be used to modify change mode of pricing screens in delivery processing. 6GMP 'WW Jsers E9it for "atch %eterminationK @IP!-@2&R8 determination Bser E"its or 9rans!ortation Include routines reserved for customers 3need a modification key4 Include Descri!tion 6GMN &WW >ou can include your own modules in this program, to be processed in shipment processing screens during P"&. 6GMN IWW >ou can include your own modules in this program, to be processed in shipment processing screens during P I. 6GMN 'W> >ou can include your own '&R6 routines in this program. 8hey can contain your own adBustments for shipment processsing. 6GMN 'WW 8his program contains pre-defined '&R6 routines, in which you can carry out your own adBustments for transportation processing. Bser E"its or Price Determination Routine 6odule pool or function group Include %escription J!EREFI8XPRI5I#2XPREP REX8S&6S ! P@GNP RGNP 'WW 8his user e9it allows you to copy additional fields for pricing in the 8S&6S communication structure 3header fields4, which have not been provided in the standard ! P system. 8hese fields can also be used for pricing in the billing document. 8his user e9it is described in detail in the Q#ew fields in pricingQ section. J!EREFI8XPRI5I#2XPREP REX8S&6P ! P@GNP RGNP 'WW 8his user e9it allows you to copy additional fields for pricing in the 8S&6P communication structure 3item fields4, which have not been provided in the standard ! P system. 8hese fields can also be used for pricing. 8his user e9it is described in detail in the Q#ew fields in pricingQ section. J!EREFI8X'IE@%X6&%I'I5 8I&# ! P6GN. 6GN. 'W >ou can use this user e9it to adBust the display of individual lines in the condition screen by changing the display attributes of the screen fields. 8his does not include the display of subtotals. 8his user e9it is also used in order processing. J!EREFI8X'IE@%X6&%I'I5XSW7I ! P6GN. 6GN. 'W" >ou can change the display of subtotals in the condition screen by changing the display attributes of the screen fields. 8his user e9it is also used in order processing.

J!EREFI8X'IE@%X6&%I'I5XS&P' ! P6GN. 6GN. 'W" >ou can adBust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields. 8his user e9it is also used in order processing. J!EREFI8X'IE@%X6&%I'I5X@EER ! P6GN. 6GN. 'W" >ou can adBust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields. 8his user e9it is also used in order processing. J!EREFI8XPRI5I#2X5?E5S ! P6GN. 6GN. 'W >ou can install additional checks to the standard checks of condition lines 3e.g. ma9imum:minimum value4. J!EREFI8XPRI5I#2XRJ@E ! P@GN. RGN. 'W In the standard ! P system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. >ou can change the predefined standard procedure for each pricing type. J!EREFI8X5? #2EXPRI5I#2XRJ@E ! P6GN. 6GN. 'W >ou can use this user e9it to change the pricing type that has been predefined in the copying control table in billing. J!EREFI8XFS&6GX"E7ER8E#XI#I8 ! P@GN. RGN. 'W" 8his field is used in the formulas and therefore initiali=ed before the loop for the pricing procedure starts. J!EREFI8XFS&6GX"E7ER8E#XE#% ! P@GN. RGN. 'W" 7ithin a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed. J!EREFI8XFS&6GXER2 E#WE# ! P@GN. RGN. 'W" In change mode, you can change the dynamic part of the condition record 3S&#G%4 that is always redetermined 3i.e. it is not stored in database table S&#G4. J!EREFI8XFS&6GXER2 E#WE#X6 #J ! P@GN. RGN. 'W" >ou can use this user e9it to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen. J!EREFI8XFS&6GX'JE@@E# ! P@GN. RGN. 'W" 8his user e9it is always called up during a redetermination of all or individual price components. >ou can change the work fields of the condition line. ?owever, this only applies to conditions that have been determined via a condition record. J!EREFI8XFS&6GX'JE@@E#X&XS&#P ! P@GN. RGN. 'W" 8his user e9it is always called up during a redetermination of all or individual price components. >ou can change the work fields of the condition line. ?owever, this only applies to conditions that have been determined via a condition record. 8his may include subtotals, manually entered conditions or conditions that have been calculated with a formula. J!EREFI8XPRI5I#2X5&P> ! P@GN. RGN. 'W >ou can change the S&#G fields for copied price components. :ote@ as of Release L.N , the display of the condition screen 3screen N1P.4 has been converted from a full screen to a subscreen. 8he full screen is included in the ! P6GN. module pool, the subscreen, however, in program ! P@GN/ . 8herefore, instead of 6GN. 'W and 6GN. 'W", the user e9its in @GN/ 'WW should be used. 'or reference, see &!! note ;.;MN/. Bser E"its or Partner Determination Partner determination contains the following user e9its for your useA EFI8X! P@GP/ XPP. >ou can use this user e9it to control whether an address that was entered manually and has already been used in other documents 3referenced4, should be referenced again if it changes or whether a new address shold be created 3duplicated4. EFI8X! P@GP/ XPP1 5all up this user e9it if a customer has not been maintained in the current sales area. EFI8X! P@GP/ XPP; Jse this user e9it to control the origin of partners in the partner determination procedure 3origin F, > or W4. If F, >, or W has been entered in the &rigin field, this user e9it is automatically called up during partner determination. EFI8X! P@GP/ XPPL Jse this user e9it to integrate your own check in a program, that runs before the partner is saved in the document. 'or more detailed information, see the program documentation for each ofthe user e9its. Bser E"its )or %redit %hecks If you want to carry out your own individual credit checks, that differ from those in the standard system, you must define them in the following user e9itsA @GS6P8WW @GS6P'W.A J!ERX5RE%I8X5?E5S. @GS6P'W1A J!ERX5RE%I8X5?E5S1 @GS6P'W;A J!ERX5RE%I8X5?E5S; Bser E"it or availa+ility check Jser e9it J!EREFI8X G I@X5?E5SX5RE%I8 e9ists in Include 6GLM 'W'. 8his user e9it allows you to determine whether the system should or should not carry out an availability check after a blocked document has been released or after a new credit check.

Bser E"it or Risk 1ana,ement or Receiva+les RGS6PJ!1 Jsing this user e9it, you can define new forms of payment guarantee. Bser E"its or $illin, Plan RGNP'J!. Jser E9it from ! P@GNP', "illing PlanA %istribute %ifference \"I@@I#2X!5?E%J@EX%E@8 'or milestone billing a percentage value is fully invoiced for each billing deadline. In the case of deviations between the original item value and any later changes, you can use the user e9it to determine whether the difference should be stored in the final invoice or sent to the ne9t deadline. \J!EREFI8X6&GEX'IE@%X8&X'P@8 A 8his user e9it allows you to create your own fields in table 'P@8. \J!EREFI8X6&GEX'IE@%X8&X'P@ A 8his user e9it allows you to create your own fields in table 'P@ . RGNP'J!1 Jser e9it from ! P@GNP', "illing planA Prepare pricing \J!EREFI8XPRI5I#2XPREP REX8S&6F 8his user e9it is used to copy or create an additional field in the definitive communication structure for pricing. 8he user e9it is also often used to change the duration of a billing plan deadline. >ou can do this by overwriting the following fieldsA ]tkomp-an=Xtage 3#umber of days in a deadline4 ]tkomp-an=Xmonate 3#umber of months in a deadline4 ]tkomp-an=XBahre 3#umber of years in a deadline4 ]tkomp-an=Xwochen 3#umber of weeks in a deadline4 RGNP'J!; Jser E9it 'rom ! P@GNP', "ill. PlanA %eadline Proposal 'rom !ource \J!EREFI8X% 8EXPR&P&! @ In the standard release deadlines are set according to a template in the billing plan. 8his grid entry list sets the deadlines for each day but you can adBust the template with the user e9it so that the grid entry list could, for e9ample, follow a monthly pattern instead. 6odification report for billing plan !%'P@ P1 8his report enables you to update the header data for a billing plan with the result that new billing plan deadlines are determined and set in the billing plan. In this way you can, for e9ample, set the goods issue date as the starting date for the billing plan. dditions to billing plan with transaction !6&% \Jser e9it !%G FPP. In the standard release the billing plan type is determined from the item category of the sales document and set in the billing plan. >ou can also use the user e9it to determine the billing plan type dependent on data from the order header, order item, etc. \Jser e9it GNP'PPP. 8his user e9it is for changing the deviating billing date 3'P@8- '% 84. RGNP'J!L Jser e9it from ! P@GNP', field preparation field selection for screen RGNP'J!M 8his usere9it can be used to split date lines 8S&6S for ?eader fields RGNP'J!8 Jser Part for "illing Plan - %ata %efinition

Characteristics of the Various Stock Transfer Procedures

The following ta le lists the characteristics of the individual procedures used for stock transfer. Plant to plant 1 step Order t#pe MM$P%& Mo'e(ent t#pe MM$)M Deli'er# t#pe SD *illing t#pe SD Doc. t#pe MM$)V Price Planning 'ia... Stock after +) Deli'er# costs # Transfer postg. using G&$ # # # =aluation price :eservation # # Plant to plant 2 steps # D8@ G&G D:@ G&1 # # # =aluation price # Stock in transfer # !ompany code clearing St. trnsp. ord. !o SD 90 D8@ G1$ D:@ $&$ # # # =aluation price Purchase order Stock in Transit yes !ompany code clearing St. trnsp. ord. ith SD 90 D8@ O2$ D:@ $&$ -* # # =aluation price Purchase order Stock in Transit yes !ompany code clearing St. trnsp. ord. ith "illing -0 D8@ O2G D:@ $&$ -*!! 8= :F Pricing in SD and .. Purchase order 3Stock in transit !!4 yes :evenue accountP D:J8: clearing

Cross$co(pan#$code !ompany code 'ia... clearing

MOV M !T T"#