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.
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.
SAP Account payable: ACH, APP
Automatic Payment Program(APP) is most important in SAP Account Payable (AP).
Here are steps for APP configuration in t code FBZP.
Status:
Parameters: Vendors, Payment methods, next payment date,
Proposal:
Payment run:
Print: if check payment is configured
Electronic Bank Statement (EBS) configuration:
Here are steps for APP configuration in t code FBZP.
- Setup payment method per country
- Setup payment method per company code
- Setup all company codes
- Setup paying company codes
- Bank determination
- Assign payment methods for vendor
Status:
Parameters: Vendors, Payment methods, next payment date,
Proposal:
Payment run:
Print: if check payment is configured
Electronic Bank Statement (EBS) configuration:
- Create House bank & account ID (FI12)
- Setup EDI Partner profile for FINSTA message type (WE20)
- Configure global settings for EBS
- Account symbols
- Assign account symbol to account
- Key for posting rules
- Posting rules
- Transaction types
- Assign transaction types for posting rules
We can get Bank Reconciliation statement through t code FF67
No comments:
Post a Comment