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.

Comments

Post a Comment

Popular posts from this blog

Batch input session SM35

Image
Batch in put session is the same for all the modules and processes. Its independent and it can be use for all the processes. In SM35, we can select the session for recurring entry or for any other scheduled process. We can manage sessions, lock it, unlock it, see logs etc. For running batch input session it gives us 3 options. Foreground, background and errors only. Foreground means system will roll all the transaction on the screen and we can see it. Background means system will process all the transaction in background. Errors only means the system will process in background but will show errors. For ease we select extended log and expert mode while starting a batch input session. Now once we run batch input session we need to know results of it right? Here it is how we get results of batch input session in SAP FICO.  Batch job overview
Read more

Manual Clearing Vendor open line items F-44

Image
In SAP FICO, F-53 kept the line items open even if it got paid. How to clear them? Through F-44. Here give the vendor account number whom we want to clear line items. Process open items will redirect to the new screen. Select which line items to be cleared, simulate and save. It will clear the line items and gives a document number. Upon displaying document it shows a document with no line items but just header data. It is an important certification question that only clearing document display have just header data and no line items. All the financial accounting entries saved in tables BKPF and BSEG for header data and line item data respectively. So for most of the documents there is a link between these two tables, but for clearing document there is an entry in BKPF only.
Read more

iDoc types and applicable message types

Outbound processing: BENREP     BENEFIT1 CARNOT    DELVRY01 CREADV     PEXR2001, PEXR2002 DEBADV     PEXR2001, PEXR2002 DELFOR     DELFOR01 DELINS     DELFOR01 (FDS and JIT) DELJIT     DELFOR01 DESADV     DELVRY01, DELVRY02, DELVRY03 (previously: DESADV01) EXPINV     EXPINV01, EXPINV02, EXPINV03 GSVERF     GSVERF01 IFTMIN     SHPMNT03 IMPINV     IMPINV01 INVOIC     INVOIC01 ORDCHG     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 ORDERS     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 ORDRSP     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 PAYEXT     PEXR2001, PEXR2002 PRICAT     PRICAT01 PROACT     PROACT01 QUOTES     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 REMADV     PEXR2001, PEXR2002 REQOTE     ORDERS01, ORDERS02, ORDERS03, ORDERS04, ORDERS05 SHPADV     SHPMNT03 SHPMNT     SHPMNT01, SHPMNT02, SHPMNT03, SHPMNT04 SHPORD     DELVRY01 WHSORD    DELVRY01 Inbound processing: CREADV  
Read more