exam system application and production sap

7/23/2019 Exam System Application and Production SAP

http://slidepdf.com/reader/full/exam-system-application-and-production-sap 1/9

Exam System Application and Production/ SAPMaav nih blog baru :D . saya mau berbagi buat agan" yang mau est SAP !#DAME#A$ % dari &' soalsaya bisa menger(a)an *+ soal :D %%

saya mau share nih gan Soal dan ,a-aban untu) SAP !undamental Semoga berguna untu) )ebanya)anorang

,a-ab: SAP stands or01. System% Application and Program2. System% Application and Procedure3. System Application Procurement. System% Application and Product

,a-ab: 24lient that is used or user acceptance test should be created in the ollo-ing SAP system01. Development2. 5uality Assurance3. Production

,a-ab: !alse6t is recommended to have more that one client in the Production system.7rue/!alse8

,a-ab: !alse6t is possible to create sales order in Sales Area 1'''/12/1' or sold9to9party -hich is created or Sales

Area 12''/12/1'.7rue/!alse8

,a-ab: !alse6t is possible to conduct good issue or selected items in a delivery document.7rue/!alse8

,a-ab: rueood 6ssue can only be perormed ater the transer order is created.7rue/!alse8

,a-ab: !alse;hen user created 4ompany code in client 2''% the same Purchase <rder can also be ound in 4lient3''.7rue/!alse8

,a-ab: rue6t is not possible to maintain dierent material -eight and volume or dierent plants.

7rue/!alse8

,a-ab: 1 A layer that stores all transactions data is called01. Database $ayer 2. 4ommunication $ayer 3. Application $ayer . Presentation $ayer +. <utput $ayer



,a-ab: 3he ollo-ings are the development tools provided -ithin the SAP system% except01. A=AP ;or)bench2. Screen Painter 3. A=AP 6nterpreter . A=AP Dictionary

,a-ab: 2he highest organi>ational unit in SAP application is called01. =usiness Area2. 4lient3. 4ompany 4ode. Purchasing <rgani>ation+. #one o the above

,a-ab: 3 A ?/i@ entry instruct the SAP system to01. 4lose current session2. <pen ne- session3. Deletes current session

. Display overvie- sessions+. #one o the above

,a-ab: +o access the technical inormation or a ield in a transaction% user must perorm the ollo-ing01. #avigate to elp 9B Application elp2. #avigate to System 9B Status3. System 9B Status. Press ! )ey+. Press !1 )ey 9B echnical 6normation

,a-ab: !alseSeveral Databases can be used to increase the SAP system perormance.

7rue/!alse8,a-ab: 2%3%%+he ollo-ing inormation can be ound in status bar01. !ield name2. Cesponse time3. ser name. 4lient number +. Application server name7multiple ans-ers8

,a-ab: 1%2%3%<ne o the ollo-ings is considered master data01. 4ustomer Master

2. endor Master 3. Material Master . 6notypes+. Purchase order 7multiple ans-ers8

,a-ab: An organi>ation unit in Sales Distribution module that could represents a branch is called01. Sales <ice2. Sales Area



3. Division. Sales <rgani>ation+. Distribution 4hannel

,a-ab: An organi>ation unit that is responsible or negotiating prices -ith vendors is called01. 4ompany 4ode2. Purchasing Area3. Purchasing Department. Purchasing <rgani>ation+. Purchasing roup

,a-ab: 1%2%;hen multiple logon occurs% SAP system shall display the ollo-ing -arning01. erminate this logon2. 4ontinue -ith this logon -ithout ending any other logons in the system3. erminate this logon and end any other logons o this user in the system. 4ontinue -ith this logon and end any other logons o this user in the system7multiple ans-er8

,a-ab: 2he ollo-ings are principal characters o the A46D concept% except01. Atomic2. 4onstant3. 6solated. Durable+. All o the above

4hart o account that is used to capture daily transactions is called0

1. <perational chart o accounts2. $ocal chart o accounts3. roup chart o accounts. eneral chart o accounts,a-ab: 1

Sta)eholders that may be interested in loo)ing at the accounting rom an external vie- points mayinclude01. 4ustomer 2. Share holder 3. Supplier . ax agency+. All o the above

,a-ab: +

A ?/i@ entry instruct the SAP system to01. 4lose current session2. <pen ne- session3. Deletes current session. Display overvie- sessions+. #one o the above,a-ab: 3



An organi>ation unit that is responsible or negotiating prices -ith vendors is called01. 4ompany 4ode2. Purchasing Area3. Purchasing Department. Purchasing <rgani>ation+. Purchasing roup,a-ab:

6t is possible to conduct good issue or selected items in a delivery document.7CE/!A$SE8!A$SE

ood 6ssue can only be perormed ater the transer order is created.7CE/!A$SE8CE

<ne o the organi>ational ob(ects is )no-n as organi>ational unit -here the ollo-ing ob(ect is assigned:1. Position2. ,ob3. Division. ser

+. Person,a-ab: 1

;hen user created 4ompany code in client 2''% the same Purchase <rder can also be ound in 4lient3''.7CE/!A$SE8!A$SE

Sales <rder document can be created by reerencing the ollo-ing documents0 7M$6P$E A#S;EC81. 6nuiry2. 5uotation3. Sales <rder . Delivery

+. =illing,a-ab: 1% 2% 3

During good issue% the ollo-ing activities ta)e place in the bac)ground% except07M$6P$E A#S;EC81. Stoc) uantity is reduced by the uantity in delivery2. Serial number status is updates3. Material document is generated. Stoc) value in balance sheet is updated+. =illing status is updated,a-ab: 1% 2% 3% +

he Activity =ased 4osting 7A=48 allo-s costs to be analy>ed at the product level by calculating the costo each processes involved.

7CE/!A$SE8,a-ab: CE

Personnel Development module maintains the development and urther education or employees. ;hen itcompares the (ob/position reuirements and employee ualiications% it is called as:1. ,ob comparison2. Proile matchup3. Development plans. raining and Event Management+. #one o the above



,a-ab: 2

he ollo-ing transaction can generate posting to !inancial Accounting07M$6P$E A#S;EC81. Sales <rder 2. Purchase <rder 3. Delivery <rder . ood 6ssue+. 6nvoice eriication,a-ab: % +

6t is possible to maintain dierent vendor addresses or the same vendor number in dierent companycodes.7CE/!A$SE8,a-ab: !A$SE

raining and Event Management has an intuitive menu that enables user to access individual unctions othe application directly via the ob(ects in the business event catalog. hese menus are )no-n as:1. Dynamic action2. Personnel action3. Day9to9day activities. Attendance menus+. Dynamic menus,a-ab: +

,a-ab: !A$SEManagement 4ontrolling module loo)s accounting reporting rom external vie- point -hereas !inancials

Accounting module loo)s accounting reporting rom internal vie- point.CE/!A$SE

,a-ab: 3<ne o the ollo-ing ields in customer master is maintained at the sales area level01. 4ustomer name2. 4ustomer address3. Shipping 4ondition. 4ustomer phone number +. Ceconciliation Account

,a-ab: 1% 2Ms. ,ose Farmel% as an C administrator -ants to boo) Mr. ,ose ega to $eadership course. heollo-ings are the pre9reuisite processes to be able to boo) a person or a course 7M$6P$E

A#S;EC8:1. =usiness event preparation2. =usiness event catalog



3. Day9to9day activities. Cecurring activities+. ;eb9based learning methods

,a-ab: 1% 2% 3% <ne o the ollo-ings is considered master data0 7M$6P$E A#S;EC8:1. 4ustomer Master 2. endor Master 3. Material Master . 6notypes+. Purchase order

,a-ab: CE6t is not possible to maintain dierent material -eight and volume or dierent plants.CE/!A$SE

,a-ab: % +he ollo-ings are data components in SAP system% except07M$6P$E A#S;EC81. Cepository2. 4ustomi>ing3. 4lient. System 6D+. Parameter 6D

,a-ab: 1 A layer that stores all transactions data is called0

1. Database $ayer 2. 4ommunication $ayer 3. Application $ayer . Presentation $ayer +. <utput $ayer

,a-ab: An organi>ation unit in Sales Distribution module that could represents a branch is called01. Sales <ice2. Sales Area3. Division. Sales <rgani>ation+. Distribution 4hannel

,a-ab: 1% 2% % +he ollo-ings are not included as main ob(ects in <rgani>ational Plan% except:7M$6P$E A#S;EC81. Position2. ,ob3. Division. <rgani>ational nits



+. Person

,a-ab: 3he ollo-ings are the development tools provided -ithin the SAP system% except01. A=AP ;or)bench2. Screen Painter 3. A=AP 6nterpreter . A=AP Dictionary

,a-ab: 2he highest organi>ational unit in SAP application is called01. =usiness Area2. 4lient3. 4ompany 4ode. Purchasing <rgani>ation+. #one o the above

,a-ab: % +Ms. ,ose Farmel is an C administrator. She maintains personnel data through Personnel Actions. ;henexecuting a hiring action% she reuires to at least maintain the ollo-ing inotypes% except 7M$6P$E

A#S;EC8:1. <rgani>ational Assignment 76'''182. Personal Data 76'''283. Addresses 76'''*8. ravel Privilleges 76''1&8+. ime Cecording 6no 76'+'8

,a-ab: 1% 2% 3% he ollo-ing statement is true regarding the 4ommand ield0 7M$6P$E A#S;EC81. 6t is possible to hide the command ield section

2. ransaction code can be typed in the 4ommand !ield to open a transaction3. 6t is possible to delete a session using the 4ommand !ield. istory o transaction codes can be seen in the 4ommand !ield

,a-ab: 2% 3% endor master consists o the ollo-ing data07M$6P$E A#S;EC81. 4ompany Data2. eneral Data3. !inancial Accounting/4ompany 4ode Data. Purchasing Data+. 4lient Data

,a-ab: SAP stands or01. System% Application and Program2. System% Application and Procedure3. System Application Procurement. System% Application and Product

,a-ab:



he ollo-ing statements are true about Cole9based ser Menu...1. ;hen a user is assigned to a role% that particular user cannot access other transactions usingtransaction code2. ser can only access the ser role menu through customi>ing3. 6t is not possible to assign the same user more than one user menu. ser can access the transactions and report through their role9based menu

,a-ab: 3% + he ollo-ings are CE statements in regards -ith

iring action% except: 7M$6P$E A#S;EC81. <rgani>ational Assignment% Personal Data% Addresses are some o inotypes that are created in thehiring action2. ;hen hiring action is ta)en% the inormation in Applicant data in Cecruitment is transerred to CMaster Data as inotype records3. Employee data is entered on relevant inotypes and displayed in seuential order. hereore it isimpossible to restart the action at later date to enter the missing inormation.. Planned -or)ing time 7inotype '''&8 is used in the iring action as to record the -or)ing scheduleassigned to the person+. he seuence o inotypes that comprises the action is not conigurable/customi>able

,a-ab: 1% 2% 34ustomer master consists o the ollo-ing vie-s07M$6P$E A#S;EC81. !inancial Accounting data2. Sales Area data3. eneral data. 4lient data

,a-ab: !A$SE6t is possible to add and delete transaction codes in the 4ommand !ield.CE/!A$SE

,a-ab: !A$SE6t is possible to conduct good issue or selected items in a delivery document.CE/!A$SE

,a-ab: 26t is possible to classiy ixed assets by using01. Asset group2. Asset 4lass3. Asset Master Cecord. Asset Areas+. #one o the above

,a-ab: 3he layer that consist o buer is called01. Database $ayer 2. 4ommunication $ayer 3. Application $ayer . Presentation $ayer +. All o the above



,a-ab: +o allo- integration and data exchange bet-een SAP components% the ollo-ing service is needed01. A$E2. =AP63. Method. =usiness <b(ect+. #one o the above

,a-ab: 2Mr. eorge ega holds a position as !inance Manager -hereas Ms. 4atherine 4amino as an 6 Manager.=oth o them have same tas)s o eam $ead and Setting up departmental target. hese tas)s areinherited rom the ollo-ing ob(ect:1. Position2. ,ob3. Division. <rgani>ational nits+. #one o the above

,a-ab: 1 An organi>ation unit Plant in Sales Distribution module represents the ollo-ing in the actual physicallocation01. Delivery Area2. $egal Entity3. !actory. Department+. Ceceiving Area

exam system application and production sap

Documents