Skip to main content

~ Tolerance Groups

In SAP S/4HANA FI, tolerance groups (transaction OBA4) are used to set posting limits for different types of transactions. Let's understand using two amounts:

1. "$1000 for Amount per document":

- This refers to G/L (General Ledger) postings

- It means users can post G/L account transactions up to $1000 without requiring additional approval

- These are direct postings to G/L accounts (like expense accounts, revenue accounts, etc.)

2. "$2000 for Amount per open item account item":

- This refers to postings to open item managed accounts, which includes both A/P (Accounts Payable) and A/R (Accounts Receivable)

- This $2000 limit would actually apply to both A/P and A/R accounts since both are open item managed accounts

- G/L postings are direct transactions that need to be controlled separately from subledger postings

The difference between G/L (direct) postings and subledger postings:

G/L Direct Postings:

- These are transactions posted directly to G/L accounts without involving a subledger

- Examples:

  * Recording office supplies expense directly to an expense account

  * Recording bank charges directly to a bank charges account

  * Recording a manual journal entry between two G/L accounts

- These are typically more "sensitive" because:

  1. They bypass the additional controls that come with subledger processing

  2. There's no supporting subledger detail to validate against

  3. They're often manual entries rather than system-generated

Subledger Postings (like A/P and A/R):

- These transactions first go through a subledger (like Vendor or Customer master records)

- They have additional built-in controls:

  1. They require valid master data (vendor/customer numbers)

  2. They create audit trails in both the subledger and G/L

  3. They often follow predefined business processes (like purchase-to-pay cycle)

- Examples:

  * Recording a vendor invoice (A/P)

  * Recording a customer payment (A/R)

This is why in OBA4:

- The $1000 limit for direct G/L postings is lower than the $2000 limit for subledger postings

- It's a common control practice to set stricter limits on direct G/L postings because they have fewer inherent controls

- The higher limit ($2000) for subledger transactions reflects the additional control layers already present in subledger processing


Would you like me to explain more about how these tolerance groups work in practice?

Comments

Post a Comment

Popular posts from this blog

Primary & Secondary

A key aspect of how CO and FI are integrated within the SAP S/4HANA system: 1. Primary Cost Elements: • Example:  ○ FI: Salaries expense in the P&L statement. ○ CO: Salaries expense used in cost center accounting to track labor costs. 2. Secondary Cost Elements: • Example:  ○ Depreciation: While depreciation is tracked in FI, a secondary cost element might be created to allocate depreciation costs to specific cost centers or internal orders based on factors like asset usage.   In SAP S/4HANA, the distinction between cost elements and costs, whether primary or secondary, is fundamental to how Financial Accounting (FI) and Controlling (CO) interact and provide granular insights into an organization's financial performance. Here's a breakdown of the differences: 1. Primary Cost Elements What they are: Primary cost elements are essentially General Ledger (G/L) accounts from Financial Accounting (FI) that are relevant for cost accounting in Controlling (CO) ....
Post a Comment
Read more

~ Currency Types in ECC vs. S/4

Currency Types in ECC and S/4HANA FI: ECC: There are indeed only 3 Currency Types in ECC: Company Code Currency: The primary currency used for financial transactions in the company code. Group Currency: The currency used for consolidation purposes at the group level. Hard Currency (or Additional Currency) S/4HANA FI: There are 10 Currency fields available in the ACDOCA: Company Code Currency Group Currency Document Currency Global Currency Free-Defined Currency 1 .  .  . Free-Defined Currency 6 Differences Between OB22 and FINSC_LEDGER: OB22: Primarily used for setting currencies at the company code level. Allows you to define and manage local currencies for a specific company code. The screen for "Change view additional local currencies for a company code: details" is specifically for ECC, as it only lists three local currencies. FINSC_LEDGER: A more comprehensive transaction for managing currencies and other financial ledger settings. Offers a wider range of options and f...
Post a Comment
Read more

~ CO Area Assignment and Currency Type Settings

~  The choice between "Controlling Area Same as Company Code" and "Cross-Company-Code Cost Accounting" in transaction OKKP does indeed affect the currency type options available. Here's a breakdown of the currency type options for each scenario: Controlling Area Same as Company Code: Only one option is available: Company Code Currency . This means that the controlling area will always use the same currency as the company code it is assigned to. Cross-Company-Code Cost Accounting: Six currency type options are available: Company Code Currency: The default currency of the company code. Controlling Area Currency: A currency defined at the controlling area level, allowing for different currencies within a single controlling area. Group Currency: A currency defined at a higher organizational level (e.g., a corporate group). Hard Currency: A currency typically considered stable and less prone to fluctuations (e.g., USD, EUR). Index-Based Currency: ...
Post a Comment
Read more