講稿sap培訓時得到

1、Interni nalog planiranja istraivanja i razvojaSAP Best PracticesSvrha, prednosti i kljuni koraci procesaSvrha Ovaj proces koristi SAP-ovu funkcionalnost internog naloga za praenje trokova i statusa. Prednosti Mogunost usporedbe planiranih i stvarnih trokova u internim nalozima, nadzor trokova i stat

2、usa naloga.Kljuni koraci procesaInterni nalog istraivanja i razvojaPostavljanje profila planera Planiranje trokova za interni nalog istraivanja i razvojaObraun planiranih trokova za interni nalog istraivanja i razvojaPotvrivanje tonog obrauna IzvjeivanjePotrebne SAP aplikacije i uloge u poduzeuPotre

3、bno Paket proirenja 7 za SAP ERP 6.0Uloge u poduzeuEnterprise KontrolerDetaljni opis procesaInterni nalog planiranja istraivanja i razvojaRazni interni projekti troe resurse i dovode do trokova i rashoda. Ovi se projekti obino provode radi daljnjeg razvoja buduih proizvoda. Potrebno je pratiti plani

4、rane i stvarne trokove tih projekata na razini linije proizvoda u razliite svrhe kao to je kontrola trokova, izrauni povrata na ulaganje, prijava poreza itd.Za svaki se projekt kreira interni nalog pomou tipa naloga za istraivanje i razvoj (Y100). Planiranje trokova provodi se na tom nalogu. Planira

5、ni trokovi mogu se obraunati dodijeljenom mjestu troka istraivanja i razvoja ili u CO-PA (ako je CO-PA aktiviran). Dijagram toka procesaInterni nalog planiranja istraivanja i razvojaEnterprise KontrolerDogaajPod. toni?Obra. trok. int. naloga(188)AOP ope planiranje mjesta troka(175)Potvrivanje da su

6、svi nalozi tono obraunatiGodinji operativni planKred. planir. vrijed. internog nalogaAnaliza tereenja profit., npr. istra. i raz. po lin. proizNeUnos pod. plana nal. istr. i raz. po trok. elem.Planir. vrijed. internog nalogaDaAOP = godinje operativno planiranjeObra. trokova naloga istr. i raz. anali

7、zi prof.LegendSymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart continues on the next / previous pageHardcopy / Document: Identifies a printed document, report, or form Does not correspond to a task step in a document; instead, it

8、is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesFinancial Actuals: Indicates a financial posting document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not

9、have any outgoing flow linesBudget Planning: Indicates a budget planning document Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesManual Process: Covers a task that is manually done

10、Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow. Existing Version / Data: This block covers data that feeds in from an external process Does not ge

11、nerally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does not have any ing flow lines System Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task step in the

12、document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed. External to SAPBusiness Activity / EventUnit ProcessProcess ReferenceSub-Process ReferenceProcess DecisionDiagram ConnectionHardcopy / DocumentFinancial ActualsBudget PlanningManu

13、al ProcessExisting Version / DataSystem Pass/Fail DecisionSymbolDescriptionUsage CommentsBand: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role.The other process flow symbols in this

14、 table go into these rows. You have as many rows as required to cover all of the roles in the scenario.Role band contains tasks common to that role.External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.Flow line (solid): Line indicates the

15、 normal sequence of steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow.Connects two tasks in a scenario process or a non-step eventBusiness Activity

16、/ Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenarioDoes not correspond to a task step in the document Unit Process: Identifies a task that is covered in a step-by-step manner in the scenarioCorresponds to a task step in

17、the document Process Reference: If the scenario references another scenario in total, put the scenario number and name here.Corresponds to a task step in the document Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario hereCorresponds to a task step in the document Process Decision: Identi