SAP Tfin 52

Possiblities with new G/L. legal and management reporting. real-time integration CO=>FI. segment reporting. transparency & consistency. accelerated period-end closing. simple representation of parallel accounting. financial reporting using any characteristics. standard enhancement & extensibility.

in mySAP ERP customers have to install and operate many different components to meet specific requirements. true. false.

New G/L Accounting. extended data structure in standard delivery. customer fields cannot be added to G/L. real-time document splitting. real-time integration. periodic reconciliation of CO & FI. time-consuming reconciliation tasks are obsolete. management of multiple ledgers within G/L accounting.

management of multiple ledgers within G/L accounting is one of possible ways of portraying parallel accounting. true. false.

new G/L contains functions that combine classic G/L with special purpose ledger component. true. false.

due to new features data entering interfaces are essentially different in the new release. true. false.

new G/L accounting is obligatory for new as well as existing customers. true. false.

for new installations new G/L accounting is active by default in mySAP ERP. true. false.

activation of new G/L accounting. is done using a customising transaction. is performed at the start of the course and in practice. results in system wide changes to application and customising paths. makes several new nodes available.

activation indicator is set for each client. true. false.

customising paths. new G/L paths are added to existing customising paths. classic paths are replaced by new paths. running program RFAGL_SWAP_IMG_OLD hides classic paths. few classic functions can no longer be executed.

SAP provides leading ledger OL and totals table FAGLFLEXT with standard system. true. false.

leading ledger. manages only currencies assigned to company code. uses fiscal year variant assigned to company code. uses posting period variant assigned to company code. exactly one leading ledger per company code. values from leading ledger are posted to CO in standard system.

non-leading ledgers can be assigned currencies or fiscal year variants different from leading ledgers. true. false.

totals table FAGLFLEXT. makes primary standard extension of data structure visible immediately. updates same entities as GLT0. can be extended with additional fields. extending account assignment block locks out all other transactions.

to add customer fields to FAGLFLEXT they have to be added to account assignment block. true. false.

what defines which fields are updated in ledger (in G/L view) during a posting. scenario. leading ledger. non-leading ledger. account assignment block.

you can define your own scenarios. true. false.

scenario definition and assignment. scenarios are assigned to ledgers. a ledger can be assigned one or more scenarios. a ledger can be assigned even all six scenarios at once. you have to necessarily non-leading ledgers. you need a ledger for each scenario. if corresponding scenarios are not assigned no entities are inhertited to G/L accounting.

multiple/non-leading ledgers are useful for portraying accounting in accordance with different accounting principles. true. false.

when new G/L accounting is active a financial accounting document always has two views. true. false.

segment can now be derived from profit center. true. false.

CO object is used to derive profit center and functional area. true. false.

entities are inherited to G/L even if no corresponding scenarios are assigned. true. false.

deriving a segment. segment is assigned in the master data of a profit center. postings are automatically made to the segment when profit center is posted to. customers cannot develop their own derivation solutions. derivation solutions can be developed through a user exit (BAdI). segment field is a standard field in totals table for new G/L.

if scenario segmentation is not defined for the ledger the segment is only visible in the entry view. true. false.

new FI drilldown reporting functions let you create segment financial statements. true. false.

assumptions for document splitting. operative process must not be disturbed. process of document entry should be changed. user wants to enter vendor once. document splitting is only relevant for general ledger, it does not need to be visible from within subledgers.

document splitting has three steps and they are. passive split. active (rule-based) split. clearing lines/zero balance formation. all of the above.

passive split. account assignments are inherited. the step needs to be customised. ensures account itself is balanced as well as additional dimensions.

clearing lines are always formed when values have to be reposted between account assignment objects. true. false.

typical document split characteristics. business area. profit center. segment. user defined entities.

system proposes logical document splitting characteristics based on assigned scenarios. true. false.

if you elect to use additional document splitting characteristics you should use these characteristics in at least one ledger. true. false.

zero balance indicator. ensures balance of involved entities is zero for every posting. should always be set if you plan to use characteristics to create financial statements.

mandatory field in document splitting. is an extension of field status for accounts in which characteristics cannot be entered during document entry. is an extension of field status for accounts that cannot be controlled using field status. is a check as to whether a business-process equivalent business transactions variant was selected.

inheritance. is practically first step to enable documents to be posted when document splitting is active. is performed online and at line item level. if not used rules for projection of account assignments have to be defined.

to use a default account assignment you first have to define a constant. true. false.

simulating G/L view. allows simulation of entry view as well as G/L view after posting. allows simulation of entry view as well as G/L view before posting. facilitates analysis of an error early that would lead to a termination. expert mode gives a view of detailed data of document splitting.

total of all splitting rules of all business transactions is. splitting method. business transaction variant. rule-based split. passive split.

general breakdown of actual business processes and that is assigned a wide variety of item catagories is. business transaction. business transaction variant. item category. splitting rule.

specific version of predefined business transaction and (technical) modeling of a real business process for document splitting is. business transaction variant. item category. splitting rule. business transaction.

item category. is a (technical) map of posted line items. describes items that appear withina document (business transaction). are derived from, among other things account types of G/L accounts. is the semantic description for the document split.

individual splitting rule defines which item categories can/will be split and at the same time defines which base can be used. true. false.

what provides information on all essential document splitting parameters (such as splitting method or business transaction) and describes how split amounts are achieved. expert mode. choosing printer icon. simulating general ledger view.

reasons for error message. no base item category is assigned for item category. inheritance of the segment is not possible because it is not unique.

to modify a rule, create your own splitting method and copy assigned rules from standard configuration. true. false.

account assignment objects in revenue line item are inherited to customer and tax items in the invoice. you can see this in G/L view of document display. true. false.

Leading ledger gets many of its control parameters from the company codes, specifically: Leading ledger manages the (additional) local currency (currencies) that is (are) assigned to the company code. Leading ledger uses fiscal year and posting period variant that is assigned to the company code. Only the values from the leading ledger are posted to CO in the standard system. There are many leading ledger.

In addition to leading ledger, you can also define other, non-leading ledgers. The non- leading ledgers can then be assigned currencies and/or fiscal year variants that differ from the leading ledger. true. false.

The total table of New General Ledger accounting updates more entities than was possible in the classic total tables. For example Cost centers, profit centers, segments. true. false.