SAP FI CO
  • SAP FICO
  • SAP HR
  • Netezza
  • Pega
  • Python
  • Big Data
  • Teradata
  • iExpertify
Account Number
December 15, 2010

Difference between FS10N and FBL3N

FBL3N – Display Change Line Items (gives the open item list)
FS10N – Display Acct Balances (gives the balance of transaction figure)

To say it very plain – Transaction FS10N displays balances, this balance could include many different asset numbers, drill down required for individual asset numbers. FBL3N displays detail, drill down not required.

In case you find that balances in the 2 transactions dont match:
1. Line item display was switched on after there had already been postings to the account (Check your master record for changes in FSS4 and see if the line item display was changed at any point. )
2. Archiving has been done (archiving line items but obviously keeping the account balance correct). It can be very time consuming, but you can always use SE16 on table BSEG (with your company code and account number as selection fields) to check the actual line items. Line item display uses one of the index tables (BSIS) and there can be differences between that and the actual document database, which SE16 will show you.
3. Check search criteria of FBL3N
4. Check the G/L account whether it is enabled to Line Item Display
5. Run the programm SAPF190 to check the gap
6. Check for your user role, if you have the complete authorization objects for T Codes FS10N and FBL3N. Please take the help of your Basis Consultant for that.
7. Execute the report TFC_COMPARE_V2 from SE38 and also see the program documentation (blue information button) on the selection screen of the report.
8. Run transaction SE38 and execute program RFSEPA01

December 15, 2010

GL Account Balance Display – FS10N

FS10N – is the the transaction code used for GL Account Balance Display.
Difference in Last year Closing balance and Current year Opening Balance

  • This will be corrected after running carry forward programme FAGLGVTR (for ECC 6.0)
  • Rerun the f.16 in test mode, this might generate the posting which would fix the disbalance

Note 402917 – If the opening balance does not correspond to the closing balance of the previous year on an account even after a repeated balance carryforward, you must always check whether you are dealing with a retained earnings account. If so, then you should check for inconsistencies in your system. And then you can activate the parameter for individualbalances retained earnings account during the start process of the balance carryforward program SAPFGVTR. You then receive a list of all P+L accounts with single values, which are balanced for the value of the retained earnings account. This means that you can reproduce and check the balance on the retained earnings account.

Asset number not displaying in report
SE16 for table BSEG will display asset number with the account balance.

Special fields on FS10N:
FS10N > Settings>Special Fields
This would promt a warning message stating that this would change a cross client table.

For example, if you make a change at client 800, it will change the setting on other table ( client 000 up to client 999). So, always discuss with ABAP folks before these configurations are changed.

January 26, 2009

Customer/Vendor Account Number

01) Customer/Vendor account masters have three segments.

i) General Data at the client level. (Address/Payment/transactions)

ii) Company Code Segment. (A/c Management/Payment Transaction/ Correspondence/ Insurance or withholding Tax)

iii) Sales (for Customer) /Purchase (Vendor) area segment.

02) The Customer/Vendor account number is assigned at Client level.

03) Customer/Vendor Account group Controls:

i) The Number Range of the accounts.

ii) Whether the account is a one-time customer/vendor.

The status of fields in the master records.

04) Line item Display and open line item management are configured as standard for every customer/vendor account.

05) Customer/Vendor accounts can have either internal or external number assignment.

06) There are separate number ranges for customer and vendor accounts. Number ranges must not over lap for customer/vendor.

07) Each number range can be assigned to one or more account groups.

08) In customer/vendor account groups – account number ranges are assigned by a variant, however in GL account group number ranges are entered for each a/c group.

09) The lay out of Customer/Vendor master data screens can be affected by :

i) Account group specific Field status group.

ii) Transaction-specific field status group.

Company code specific field status group.

10) Field status of a FI transaction in a Customer/Vendor Sub ledger a/c is also controlled by field status variant assigned to reconciliation account master of Customers/Vendors, while creating.

11) Customer/vendor specific data for one-time customers/vendors is entered in the document during posting.

12) Dual Control Principle: If you define a field in the customer/vendor master record as, ‘sensitive’ the corresponding customer/vendor is blocked for payment if the entry is changed.

13) If a customer is also a vendor, or vice versa, the payment and dunning program can clear open items against each other.

14) At the client and company code level, you can enter an alternative payer/payee. The entry in the company code segment has higher priority than the entry at client level.

Recent Posts

  • Business processes to be covered in SAP FICO implementation
  • Sections in a SAP FICO Business Blueprint
  • Product Cost Controlling
  • Overhead Cost Controlling
  • Purpose of Controlling Components

Recent Comments

  • Sally McClure on Business processes to be covered in SAP FICO implementation
  • Sally McClure on Product Cost Controlling
  • Reena on Company Code Configuration – OX02
  • udaya vineetha on Company Code Configuration – OX02
  • sabrina on Company Code Configuration – OX02

Archives

  • September 2014
  • May 2014
  • October 2011
  • September 2011
  • July 2011
  • December 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • March 2010
  • October 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009

Categories

  • Account number
  • account recievables
  • Assets and Liabilities
  • bank
  • basics
  • books
  • certification
  • Chart of Acount
  • Company Code
  • Configuration
  • Controlling
  • Cost Accounting
  • Currencies
  • Customer
  • Dcoument types
  • Document
  • Enterprise structure
  • FI
  • FI CO Configuration Series
  • Financial Labels
  • fiscal year
  • GL
  • Integration
  • Internal Order
  • interview
  • invoices
  • ledger
  • Master records
  • payment
  • posting
  • Profit and Loss
  • Q and A
  • Reports
  • sales
  • SAP MM
  • Screenshots
  • tables
  • Transaction codes
  • troubleshoot
  • Uncategorized
  • user
  • vendor
© Copyright 2022 - SAP FI CO
Future Theme ⋅ Powered by WordPress