SAP FI CO
  • SAP FICO
  • SAP HR
  • Netezza
  • Pega
  • Python
  • Big Data
  • Teradata
  • iExpertify
Customer
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