sap培训时得到的

1、Accounts PayableSAP Best PracticesPurpose, Benefits, and Key Process StepsPurpose This scenario deals with posting accounting data for vendors in Accounts Payable. Benefits The Accounts Payable are also an integral part of the purchasing system. All postings in Accounts Payable are also recorded dir

2、ectly in the General Ledger. The payment program can automatically carry out bank transfers and down payments. Key Process StepsVendor master record maintainingDown payment request Post down payments using the payment program Creating new contract in main contract storagePost vendor invoice Down pay

3、ment clearing Enter vendor credit memo with reference to invoice Review and release blocked invoices Select invoices to be paid Review and block invoices for payment as needed Post payment using the payment program Post Manual outgoing payment Manual bank statement processing Accruals/deferrals docu

4、ments postingRequired SAP Applications and Company RolesRequired SAP ApplicationsEnhancement package 7 for SAP ERP 6.0Company RolesAccounts Payable AccountantDetailed Process DescriptionAccounts PayableWhen you post data in Accounts Payable, the system creates a document and passes the data entered

5、to the general ledger. General ledger accounts and vendor accounts are then updated according to the transaction concerned (payable, down payment, credit memo and so on) vendor payment activities. All business transactions are posted to and managed by means of accounts and for this a vendor master r

6、ecords are created. One time vendors are used to avoid building up of huge master data volume. Process Flow DiagramAccounts PayableYesEventAccounts Payable Accountant Down Payments Exist?Creating a Vendor Master RecordMaster RecordsYesNoClearingDocument EntryDown PaymentDown Payment ClearingPost Ven

7、dor InvoicesPosting Down PaymentPosting Down Payment RequestReview and Block Invoices for Payment as neededSelect Invoices to be PaidReview and Release Blocked InvoicesVendor Credit Memos Exist?Enter Vendor Credit Memo with Reference to InvoiceChoose Payment MethodPosting Payments using the Payment

8、ProgramManual Bank Statement ProcessingPost Manual Outgoing PaymentContract handlingCreating new contract in main contracts storagePost accraul documentsPost deferral documentsLegendSymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart

9、 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 is used to reflect a document generated by a task step; this shape does not have any outgoing flow linesFinancial Actuals: Indicates

10、 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 have any outgoing flow linesBudget Planning: Indicates a budget planning document Does not correspond to a task step in a document;

11、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 Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such a

12、s 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 generally correspond to a task step in a document; instead, this shape reflects data coming from an external source; this step does no

13、t 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 document; instead it is used to reflect an automatic decision by the system that is made after a step has been executed. External to

14、 SAPBusiness Activity / EventUnit ProcessProcess ReferenceSub-Process ReferenceProcess DecisionDiagram ConnectionHardcopy / DocumentFinancial ActualsBudget PlanningManual ProcessExisting Version / DataSystem Pass/Fail DecisionSymbolDescriptionUsage CommentsBand: Identifies a user role, such as Accou

15、nts 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 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 comm

16、on 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 normal sequence of steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or cond

17、itional 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 / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenarioD

18、oes 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 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