Escolar Documentos
Profissional Documentos
Cultura Documentos
Purpose
Provide an overview of existing SAP functionality to gain knowledge of SAP functionality while thinking how it varies from current functionality. These sessions will occur prior to business engagement.
These sessions are not intended to design the end-state SAP solution. These sessions will not provide detailed explanation of current business processes. This will be completed during Preparation Sessions.
Intended Audience
Business representatives from all ledgers who will be engaged in Prep Sessions as part of the Working Group
Table of Contents
Document Principle Structural Elements of a Journal Entry Type of Journal Entries Standard Journal Entries Interface Journal Entries
Process Flow of Interface Journal Entries
Document principles
Definition All postings are always stored as a Document. A Document must be complete before it is posted. Each Document receives a unique Document Number by Company Code and Fiscal Year. Line items in each Document must be balanced, i.e. debits equal credits and have at least two items, prior to posting. Each Document must contain the required minimum information (e.g. Document Date, Document Type, Posting Key, Account Numbers and Amounts). Incomplete or inconsistent documents cannot be posted. A business transaction can create one or more Documents A Document remains as a complete unit in the system until it is archived. Approach Target follows these standard SAP document principles.
A Journal Entry in SAP is used for any accounting activity that does not impact a sub-ledger/sub-system. These entries are made directly to the General Ledger Module. The system checks consistency before saving the data. If errors exist, the data is not saved, and the system proposes adjustments. Typical Methods of Creating Journal Entries include:
On-Line Entry using FV50 Excel Upload using WinShuttle Interface direct postings from external applications Template Document in SAP (Account Assignment Model)
Approach
Target uses Park and Post functionality. The Park and Post functionality exists to ensure segregation of duties for entering and posting. The ability to Park or Post is maintained through appropriate security access. Once a journal entry is completed, it is in a Parked status, waiting for proper approval for posting. Parked journal entries are reviewed by the appropriate approver and changed to a Posted status, generally through the Workflow approval process. Target uses a third party tool WinShuttle that allows for Excel uploads and facilitates the creation of Journal Entries.
Parked Documents are used to enter and store complete or incomplete documents in the system with the intent that a user will approve or complete and post the document later. Parked Documents do not update any data in the system such as an account balance.
Approach
Target uses a standard parking functionality along with SAP workflow for approval and posting.
10
Approach
Standard SAP Workflow is configured. All manual journal entries require a two step approval process. Workflow approval for parked documents is only required for manually parked journal entries and manual Excel uploads in SAP-ECC. It is not required for automated journal entry interfaced from Legacy systems. Dollar thresholds are not be used.
11
12
13
14
Approach
In Release 1.0, Target is not using this functionality.
15
16
17
18
Cross-company code transactions cannot be posted with the recurring entry program
Approach
In Release 1.0, Target is not using this functionality.
19
20
21
Approach
Target uses Standard Reversals for Journal Entries initiated in SAP ***Keith to update this slide
22
23
24
12
Error Handling for interfaces from external applications (requires updates to process flow)
25
14
15 16 17 18 19 20 21
26
Appendix
TCI/ Hedberg
Summarized JE
CIF
Summarized JE
SAP
HFM
PeopleSoft
Navision
JE Extract
CIF
JE Posting
SAP
HFM
Approach
Target is not currently using this functionality for journal entry process.
29
Approach
Target has defined Trading Partners with a unique six(6) character alpha-numeric key(TPXXXX where XXXX is the company code) Target adopted one to one relationship between a Trading Partner and a Company Code to enable inter-company transactions between all company codes Every Company code has also been created as a customer and Vendor in every other Company code. Trading Partner has been assigned in the customer and vendor master record.
Values
Following document types are configured and used for inter-company transactions
- ZI - Inter-company transactions - DG Customer credit memo - DR Customer Invoice - KR Vendor Invoice - KG Vendor credit memo
30