Org Structure & Module Integration Flashcards
What is the difference between company code and company ID when in the FI global settings in IMG?
The company code is the legal entity organization unit at the lowest level at which external financial statements are prepared.
The company id is a higher organization unit used for consolodation in the SAP system. A single company id can hae many company codes assigned to it so long as the fiscal year variant and chart of accounts is consistent.
What is a financial statement version?
Financial statement versions (FSV’s) are the structures forming the P/L and Balance sheet reports from the FI module.
Accounts are assigned to the end nodes in the reporting structure tree. Depending on the setup debit/credit balances can be reflected in different asset/liability columns where required
How do you define a new company code?
Using transaction code EC01, the most straightforward way of creating a new company code is to copy an existing value.
All associated data such as the fiscal year variant and assignments to controlling area and credit control are taken accross from the source value.
Transactional data is not copied.
Here, interviewers are simply looking to hear the word ‘copy’ to prove you have defined an SAP FI/CO organizational structure before.
If several chart of accounts are in use in an SAP system and there is a requirement to merge them into a single chart, how can this be achieved?
Generally, such changes cannot be done. The only options are:
- Using SAP consultants and their own ABAP tools to perform the conversion.
- Creating duplicate entities and transferring opening balances and year to data line items accross
The above applies for other such changes as modifiying the local currency of an entity or merging several controlling areas.
What is stored in table T001?
This is the main company code configuration table and includes such assignments as:
- Fiscal year variant
- Company assignment
- Local currency setting
- Credit control area
What is a company code?
Describe its relationship with a controlling area
A **company code **represents a specific legal entity for financial reporting purposes and represents the lowest level at which external financial accounts/statements can be produced.
**Company code **is the main organizaitonal object in the FI module and is assigned to a controlling area is CO.
There is a 1:many replationship between company code and controlling area.
One company code may only be assigned to a single controlling area; however one controlling area may have multiple company codes assigned to it.
Explain how the Sales and Distribution modules creates Accounts Receivable line items for invoice postings
Following the creation of a sales order, a goods issue is performed to issue the goods out of stock. This typically generates the following FI entry:
- Debit Cost of Sales, Credit Stock
Once the invoice (billing document) has been created in the SD module, the following entry is booked into the Accounts Receivable module:
- Debit customer, credit revenue
Using copy rules in SD, it is possible to pass the sales order number or billing document number onto the AR posting for tracing an anlysis purposes
Explain briefly how the Materials Management module creates Accounts Payable line items for invoice postings
Following the creation of a purchase order, a goods receipt is booked to indicated the arrival of stock from the vendor. This tpically creates the following posting:
- Debit stock, Credit GR/IR clearing
Once the invoice is received from the vendor and booked int he invoices verification module in MM, an entry is created in the AP module
- Debit GR/IR clearing, Credit Vendor
Explain what Batch Input Sessions are, some examples of where they are used in FI/CO and the terms background and foreground processing
**Batch input sessions **are batches of SAP data (either mater or transactional data) generated through an interface/report/user applicaiton.
For example when creating cost elements automatically using SAP transaction OKB2/OKB3, the system creates a batch sessions containing all the data required
Batch input sessions are used extenstively throughout the FI/CO modules, including:
- Depcreciation run
- Recurring entries
- CO reconciliation ledger
- Master data creation in FI/CO
- FX revaluation
Foreground/background refers to how the users view the data being created by SAP. In foreground, the user can step through each screen during data creation and correct any errors as they occur. In background the system tries to create the data for the entire batch and reports the errors following completion.
What are commitment line items in CO?
Commitment line items in CO are not actual cost items but rather committed expenditure items generated through purchase orders.
They are flagged with a unique value type (e.g. 21 for Purchase Requisition Commitments and type 22 for Purchase Order Commitments) in the CO tables and can be reported seperately in report painter.
It’s also possible to post manual commitment values in order to report non-PO related expenditure commitments.
When defining a new ledger in the Special Purpose ledger, how can you retrospecitvely populate FI data for a pervious fiscal year?
Using SAP transaction GCU1, FI data can be transferred for a particular company code, fiscal year, or specific document number range.
A similar transaction exists for controlling data, GCU3
What is the special purpose ledger?
What would be some reasons for using it?
The special purpose ledger (SPL) is a user defined ledger which can be built to support reporting requirements which cannot normally be met through the usual SAP modules
You can pull information from many SAP modules such as FI, CO, MM, SD and build user defined fields whose contents are based on calculations from other SAP standard information
Typical uses include:
- Reporting using an alternative fiscal year variant other than the one assigned to the entity
- Reporting in a different currency (maybe to meet a new head office reporting currency)
- Meeting US GAAP and local reporting requirements
Explain the purpose of the following SAP tables: BSEG, BKPF, GLT0
**BKPF **- this is the document header table. It stores all fields common to all of the document line items such as posting date, currency key, document number
**BSEG **- this is the document line item table (relates to BKPF). Specific line item information such as the posting key, GL account, and document amount are stored
**GLT0 **- this is the summarized account balances table showing account balances by period, by account, by fiscal year
Explain the purpose of the following SAP tables: COEP, CSKA, CE1XXXX
**COEP **- this is the CO object line item table
**CSKA **- is the cost element master table (dependant on the chart of accounts)
CE1XXXX (where XXXX is the name of your operating concern) - is the profitability analysis line item table
What is the Legacy Systems Migration Workbench (LSMW)?
When would you use it in your FI/CO rollout?
LSMW is a technical tool used for migrating master data and transaction data from your old ‘legacy’ systems to SAP
Though usually setup by your ABAP programming collegues, the LSMW projects are usually run by project team members in order to upload vendors, customers, cost centers, internal orders, etc.
Describe some of the standard credit checks avaialble within SAP.
What does most of the credit management information sit in the IMG (config)?
Credit management is one of the key integration areas between Sales and Distribution modules (SD) and Financial Accounting (FI).
Most of the configuration sits in SD IMG under Sales and Distribution => Basic Functions => Credit Management/Risk Management => Credit Management => Define Automatic Credit Control
The following are standard credit checks available:
- Static (a simple check against customers credit limits of the total AR open items, SD billing docs, etc.)
- Dynamic (as above but including open sales orders not yet delivered over a particular time period)
- Maximum sales order or delivery specified
- Critical field check (for such fields as payment terms0
- Next Review Date - checks the review date stored on the customer master
- AR open items - checks existing overdue items on the customer account
- Highest dunning level - specifies a max dunning level allowed
