SAP Accounts Payable Introduction
•
166 j'aime•107,405 vues
You can download this SAP Accounts Payable Training Material from http://sapdocs.info/sap/fico/sap-accounts-payable-training-pdf-tutorials-documents-for-beginners/ get more SAP FICO documents from http://sapdocs.info
![Course Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Recommandé
Contenu connexe
Plus de sapdocs. info
Plus de sapdocs. info (20)
Dernier
Dernier (20)
SAP Accounts Payable Introduction
- 1. Accounts Payable Version 1.0 Unit 1: Introduction SAP-ERP
- 5. Accounts Payable Easy Access Screen Different SAP R/3 Modules – AP module highlighted Non-purchase order invoice processing
- 10. Standard Document Types for AP AP Document Types
- 12. Financial Document Overview Line Item Data Header Data Overview Data
- 17. SAP R/3 Menu Path for Vendor Master Records Vendor Master Records Transaction for both company code and purchasing views
- 18. Initial Vendor Master Record Screen (FK03)
- 20. A/C Inquiries and Management Transactions Display Line Items and Balances
- 22. Reporting Functionality Additional Wyeth custom reports
Notes de l'éditeur
- Trademarks SAP and the SAP logo are registered trademarks of SAP AG. PowerPoint, Word, and photos are registered trademarks of Microsoft. NOTE: All screen shots in this presentation are representative examples. Screens in the actual environment may have minor differences, such as additional unused fields and colors based on system version. Copyright 2007 Wyeth. All rights reserved. Neither this training manual nor any part thereof may be passed on to others, copied or reproduced in any form or by any means, or translated into another language, for any purpose without the express prior consent in writing of Wyeth. All rights reserved.
- The Accounts Payable module within SAP R/3 records all accounting data for vendors. SAP R/3 supports this process by: Verifying goods received against vendor invoices Settling outstanding invoices through the payment program Automatically transferring postings in the AP module to the G/L Supporting reporting requirements Postings made in Accounts Payable are simultaneously recorded in the General Ledger where different G/L accounts are updated based on the transaction involved. Vendor invoices are paid using the payment program.
- Company Code: is maintained for every entity where a set of financial statements is required for external purposes. Purchasing Organization: within a company code is responsible for all the purchasing activities for that company. Plant: is the operating area or branch within a company. The plant can be used to subdivide a company into production, procurement, quality, or maintenance. Postings made in Accounts Payable are simultaneously recorded in the General Ledger where different G/L accounts are updated based on the transaction involved. Document Structure: is the format in which a transaction is recorded on SAP. Document Flow: is used to trace transactions through the system. It is possible to trace a material from the PO stage of the process right through to the payment stage of the process. SAP R/3 Modules: each business function is processed through a different module within SAP R/3, for example - Production Planning, Accounts Payable, Warehouse Management are all different modules.
- With the use of the different document types when a business transaction is executed on SAP R/3, it is easy to identify the type of transaction that has been processed.
- Each Document Type is also assigned a different number range. This also helps a user to identify the source of an entry into accounts. For example: Vendor Invoice Doc type KN = Number Range 0190000000 – 0199999999 Every time a KN document is posted, the next available number in this range will be posted as the document number. When an invoice is posted, the user will always know if the document number starts with 19 it was an invoice posted. For example: Vendor Payment Doc type KZ = Number Range 1500000000 – 1599999999 Every time a KZ document is posted, the next available number in this range will be posted as the document number. When an payment is posted, the user will always know if the document number starts with 15 then it was an payment posted. For example: Goods Receipt Doc type WE = Number Range 5000000000 – 5099999999 Every time a WE document is posted the next available number in this range will be posted as the document number. When a receipt is posted, the user will always know if the document number starts with 50, then it was a receipt was posted against a PO.
- The benefits of the 3 way match concept within SAP R/3: Less processing for the Accounts Payable clerk. Full traceability of materials through the system from the Purchase Order to the payment (through the Document Flow functionality). Elimination of some processing errors. Postings automatically flow through the effective modules (all integrated).
- The Vendor Master Record holds all relevant information relating to the vendor. For example: The Company Code - each vendor is linked to the company code, i.e. the company which purchases from the vendor. Purchasing Org - again each vendor is linked to the purchasing, i.e. the purchasing org which purchases from the vendor. Address, telephone, contact details are all maintained for each vendor. Payment Terms - details of how the vendor account will be settled each period. Currency - what currency the vendor will invoice and be paid in is maintained. Vendor A/C Creation: Both the Finance and the Purchasing views must be set up before any transaction can be processed for a vendor. It is possible to set up both views at the same time or a user from each department can be responsible for their own view, that is a user from finance will set up the finance views and a user from purchasing can set up the purchasing views.
- A Vendor Master File template is utilized to request changes / adds to the vendor master file by Authorized personnel. Wyeth management approves all changes / adds.