![]() ![]() Please consider testing this very carefully during the project implementation. However, this will require maintenance in the target system. Mapping Non-OIM accounts to OIM accounts is permitted.Mapping OIM to Non-OIM accounts can lead to inconsistencies for the subsequent postings (such as clearings, reversals) when document splitting is active.when harmonizing and mapping GL accounts you need to consider mapping OIM to OIM and Non-OIM to Non-OIM GL accounts The balance of these accounts is always equal to the balance of the open items.Items posted to accounts managed on an open item basis are marked as open or cleared.In S/4Hana new account types are introduced to differentiate by primary cost/revenue and secondary cost:.Only one master record is created in FI (G/L account) Primary cost element (FI and CO is merged): only one master record is created in FI (G/L account).Secondary cost elements: Master record only created in CO.Primary cost elements: Master record created separately in FI and CO.Traditionally in ECC, Cost Elements (Management Accounting) were kept separate from G/L accounts (Financial Accounting).Subsequently, secondary cost elements are now GL Accounts (in contrast to SAP ECC source systems) In S/4 HANA cost elements become part of chart of accounts and are maintained in G/L Master data.G/L account type determines how the general ledger account can be used in financial accounting (FI) and controlling (CO).G/L account type classifies the G/L account.However, it may represent a big risk of error in cases when the field is not populated in the source. ![]() If a field is optional in source, it could technically be defined as required entry in target.If mapping is required for Field Status Groups then all the fields must be analyzed and the Central Finance systems always needs to be more permissive than the source system.If the source accounts have different field statuses comparing to the field status of the target system, one of the options is to set up the field statuses for the target account fields as optional.Harmonizing and defining the mapping for the Field Status Groups, especially when more than 1 ERP are involved in the exercise, can become cumbersome.Determines which fields are ready for input (optional), which are required entry fields (mandatory), and which are hidden during document entry (suppressed).Defined in company code specific area of each G/L account.Some of these attributes can be critical, some of them not when defining the mapping. A G/L Account can have multiple attributes.The GL accounts settings of mapped GL accounts in the Central Finance system, must be compatible with the ones in the source system. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |