Professional Documents
Culture Documents
ERP
SAP HISTORY SAP MODULE SAP SERVERS
What is ERP?
ERP stands for Enterprise Resource Planning.
Money
Machine
Labour
Ankita Limited Departments are in my Ankita Ltd company
Finance
HR
Production
Sales
Purchase
There are different types of resources used in those departments so here ERP is used which can monitor
and work on all those platforms as a one unit.
ERP Vendors
People soft- HR
Oracle finance- finance
JD Edwards- Sales
Ban- Production
Company
code AT1 AT2
Business
areas
COA is the main account group of financial accounting under which we can create
Gl .It is defined at client level and assigned to each company code
Business areas are not assigned to any organizational values. Business areas cut across
company codes. Any company code can post into any business area. However, you can
restrict it through validation. Write validation in GGB0 and assign the same in OB28 to
your company code.
Spro- sap ref img- Financial acc (new)-FA Global settings- Ledgers-fiscal year and posting period-
Maintain fiscal year variant
Spro- sap ref img- financial acc ( new)- FA Global settings- Ledgers –fiscal year and posting period-
posting periods-Define variant for open posting period
variant Name
Spro- sap ref img- financial acc ( new)- FA Global settings- Ledgers –fiscal year and posting period- posting
periods-Assign variant to company code
13. Define open and close period ( OB52)
Spro- sap ref img- financial acc ( new)- FA Global settings- Ledgers –fiscal year and
posting period- posting periods- Open and close posting period
to account
from from period From
variant A account 1 year to period 1 year period 2 year to period 2 year
Ankived + 100000 999999 1 2020 12 2020 13 2020 16 2020
Ankived A 200000 299999 1 2020 12 2020 13 2020 16 2020
Ankived D zzzzzzz 1 2020 12 2020 13 2020 16 2020
Ankived K zzzzzzz 1 2020 12 2020 13 2020 16 2020
Ankived M zzzzzzz 1 2020 12 2020 13 2020 16 2020
Ankived S zzzzzzz 1 2020 12 2020 13 2020 16 2020
Spro-sap ref img- Financial accounting New-FA Global setting-Document –Document type
After completing the configuration of FBZP run the automatic Payment Program through F110
Downpayment to Vendor (F-48)
First create GL in Fs00 Asset side : Advance to Vendor : Field status G067
Example:
After posting entry of advance to vendor then post a normal invoice through FB60
Clear Vendor downpayment (F-54)
After removing the special GL indicator we post vendor outgoing payment through F-53
The below entry is example:
What is Accounts Receivable in SAP?
First create GL in liabilities i.e advance from customer G067 and maintain recon account as customer
Spro- FA(new)- Accounts Payable-Business transaction-Downpayment received- Define reconciliation account for customer downpayments
Entries for customer down payment
After passing the downpayment entry do post a normal invoice through FB70
After passing the above entry check in customer line item by selecting special GL indicator. After this
we need to remove the special GL indicator by clearing the customer account through F-39
After this we need to receive the remaining amount from customer by posting incoming payments
Dunning
Path for SAP Dunning in IMG
Financial Accounting > Accounts Receivable and Accounts Payable > Business Transactions > Dunning .
To perform the dunning we can create dunning procedure in FBMP.
We can assign dunning procedure to customer account with transaction code XD02 in company code area. We can
also define dunning block, dunning recipient, dunning level and other data related to dunning to customer here only.
Terms of Payment (OBB8)
Path --> Financial Accounting --> Accounts Receivables and Accounts Payables --> Business Transactions -->
Maintain Terms of Payment
Terms of payment is used in SAP to determine the due date and discount calculation. Terms of payment is
maintained in vendor master and customer master to default at invoice level however this can be changed at invoice
level as well.
For FI invoices payment terms is defaulted from “Accounting View” for customer and vendor. FB60/FB70
For Purchasing invoices payment term is defaulted from “Purchasing View” in Purchase Order / MIRO Invoices
For Customer Invoices from SD side the payment is defaulted from “Sales Data” view.
Payt Terms: This field contains four characters alphanumeric identifier for payment term key.
Sales text: Maintain the short text for explanation. The explanation can be maintained up to 30 characters. This field
validates the account type “Customer”. If you maintain the text here and account type “Customer” is not “Selected”
system will give you an error as below.
Day limit: This field is used to specify the particular term of payment is valid from which particular date. Example as below –
Example 1 – Payment Term T001
Day Limit – 20
Discount – 5 %
As per above details system will consider this payment terms for the invoices posted in system ON or BEFORE 20 th date in every month
and applies 5% cash discount. The discount won’t be applicable for invoices posted after 20th in month.
Example 2 – Payment Term T001
Day Limit – 31
Discount – 2 %
As per above details system will consider the invoices for 21st to 31st and applies the 2% discount.
This perfectly suits where the requirement is – the invoices posted upto 20th should have 5% discount and invoices posted in
date range of 21st to 31st should apply discount of 2%
Own explanation: This field is used to give detail explanation of the payment term. Be careful while using this field because this
field overrides the explanation automatically generated by system based on discount percentage and days entered.
Account Type –
Customer: If payment term is intended to use for “Customer” please select this check box.
Vendor: If payment term is intended to use for “Vendor” please select this check box.
Baseline Date Calculation –
Fixed day: This field signifies the “calendar fix day” for base line date calculation.
Additional Months: Value maintained here is used to add the calendar month for base line date calculation.
Pmnt block/pmnt method default –
Block Key: The value maintained in this field signifies the block key for payment. If block key is
maintained here the system proposes the block key along with terms of payment.
Payment Method: If user wants to maintain the payment method here other than customer/vendor
master it can be maintained here as an identifier.
No Default: Selecting “No Default” here means system prompts user to enter baseline date as own.
Posting date: Selecting this means posting date mentioned will be same as “Baseline Date”.
Document date: Selecting this means document date mentioned will be same as “Baseline Date”.
Entry date: Selecting this means “Systems Date” will be same as “Baseline Date”.
Payment terms –
Installment payment: Check this field if user wants to break down the invoice line items with different
due dates.Use the installment payment term functionality to achieve this.
Rec Entries:Supplement fm Master: Selecting this indicator means, for recurring entries the payment is
term is fetched from master record if does not found in line item.
Percentage: The percentage rate which will be used to calculate the discount.
No. of days: Maintain the number of days for the discount rate is valid. Like if payment received within
10 days 3% discount will be granted. So maintain the 3% in percentage field and 10 days in “No. of days”
field.
Fixed date: This field is used to determine the fix day of the calendar month as due date.
Additional months: Enter the value here if you want to add the months to fix day.
After creation of GL assign GLs to accounting key For example below:
SAP FI Withholding Tax (TDS)
Cost center Creation ( ks01)
SAP path : – Accounting > Controlling > Cost center accounting >> Master data > Cost center > Individual
processing > Create. Step 1 : – Enter SAP Tcode “KS01” in the SAP command field and enter. Step 2 : – Now
the system asking for entering the controlling area for which you like to create cost centers in SAP.