Archive for December, 2008

F-52 Incoming payment from Vendors

December 25th, 2008

Incoming Payment from Vendors

In case of following scenario incoming payment from Vendors will be applicable

Rejection of material after payment to Vendors
Refund of advance payment due to cancellation of Purchase order
Recovery of salvages done on behalf of vendor 
Recovery of advance payment /Rent deposit from employees
Income tax/Sales tax etc refund from statutory vendor

Following SAP  T  Code to be used » Read more: F-52 Incoming payment from Vendors

Vendor Outgoing payments

December 25th, 2008

Vendor Outgoing payments

We may have to do outgoing payments in SAP for one of the following reason

Payment to a supplier / subcontractor against invoice
Payment to a supplier / subcontractor as an advance
Payment for any expenses / Deposits
Payment on behalf of other office / branches
Payments for Cash withdrawals
DIRECT DEBITS made BY BANKS through (NEFT)
DIRECT DEBITS made BY BANKS through standing instructions
Manually prepared cheque payment accounting.
Employee payments related to expenses, salaries, advances etc.

In SAP we have following two option to make outgoing payment in such cases » Read more: Vendor Outgoing payments

Procurement to Payment Document Flow

December 25th, 2008

Process logic to get PO Amount and PO Number from Payment Document 

Follow logic flow can be used to build cash flow report in SAP. In SAP we do not have any report which provide details from PO to Payment document. You may have to develop it for your client. In such cases following logic may help you to build your report.

COLLECT ALL THE PAYMENT DOCUMENTS FROM TABLE BKPF ON FOLLOWING BASIS

Look For
BKPF-BUKRS Company Code
BKPF-GJAHR Fiscal Year
BKPF-BLART Document type (KZ or other payment document type)
BKPF-CPUDT Accounting Document Entry Date
BKPF-CPUTM Time of Entry
This need to be assured that all the documents posted with doc type KZ and CP has been covered by the above parameter. » Read more: Procurement to Payment Document Flow

Important features of ECC 5.0. and ECC 6.0

December 24th, 2008

Some of the important features of ECC 5.0. and ECC 6.0

In addition you can enhance the new general ledger flexibly, that is you can enter user-defined fields  and update the corresponding totals (Profit Center / Segment / Region). Many standard reports can evaluate the information from the user-defined fields.
Due to the new document splitting function  (Online Split) you can create financial statements, if required, at the company code level as well as for entities, such as the Profit centers / Segment.
Using the “Document splitting” function (online document split), you can create balance sheets for company codes as well as for further entities such as the profit center . The balance is then set to 0 for each document for the profit center.
There are no longer any time-consuming reconciliation tasks between FI and CO  for the end of period, since in real-time in Controlling, the system transfers cross entity processes into the new general ledger.
Transactions 3KEH and 3KEI  from the classic Profit Center Accounting for maintaining proposal profit centers for balance sheet and P&L accounts are no longer used to set the profit center.
Display of receivables and payables per profit center real time ( if document splitting is active) » Read more: Important features of ECC 5.0. and ECC 6.0

Profit Center Derivation in New General ledger Accounting

December 24th, 2008

Now in mySAP ERP 2005 (ECC 5.0 / 6.0) we have following option to derive profit center,

SAP T Code 3KEH and 3KEI are not to be used.
New SAP T Code FAGL3KEH can be used for default profit center derivation
We can use BADI FAGL_3KEH_DEFPRCTR for default profit center derivation
We can use FI substitution for profit center derivation whenever required
We can use BADI AC_DOCUMENT for profit center derivation for accounting interfaces
For the derivation of partner profit center it is recommended to use new BADI FAGL_DEFPPRCTR
SAP T code 8KER and 8KES is still active in classic profit center accounting only.

If you have any comments and observation in this regard, put it  below…..

Solution Manager Important T Codes List

December 23rd, 2008

Following T Codes is being used in solman during SAP project implementation. 

Menu Path

SAP menu > Tools > SAP Solution Manager

SOLAR_PROJECT_ADMIN – Project Administration
SOLMAN_PROJECT – Project Overview
AI_SPS – Project Setup: Quick Start
RMMAIN – Roadmap
SOLAR01 – Business Blueprint
SOLAR02 – Configuration
SOLAR_LEARNING_MAP – SOLAR_LEARNING_MAP
STWB_2 – Test Plan Management
SOLAR_EVAL – Project Analysis
SOLUTION_MANAGER – Solution Operation
SMSY – System Landscape

Some Other Important T Codes

» Read more: Solution Manager Important T Codes List

Vendor Down Payment in SAP

December 16th, 2008

Down payment means advance paid to Vendor. These advances may be paid to Vendors for

Purchase of goods from Vendor
Taking services from Vendor
Advance to Employees
Payment to statutory Authorities
Payment of security Deposit

Advance payment to employees as vendor, security deposit, statutory Authorities should be routed through Vendor account » Read more: Vendor Down Payment in SAP

Bills of Exchange

December 13th, 2008

Bills of exchange

This Process is applicable for accounting of bill of exchange & releasing payment against bill of exchange on due date.  The bill of exchange is a written “Acceptence” by the drawee to pay money to the payee. » Read more: Bills of Exchange

SAP FI Vendor Invoice

December 13th, 2008

Booking of Vendor bills directly in FI without integration with material management.

Scenarios considered for   Vendor Invoice & Credit Memo (Without PO) Manual Booking

FI Invoice (Credit Memo)  to Vendor against any Expenses incurred by Vendor
FI Invoice (Credit Memo) to Vendor against Freight Paid by the Vendor
FI Invoice (Credit Memo)   to Vendor against Octroi Paid by the Vendor
Debit note Vendor against ESIC/PF & other statutory payment paid by organization on behalf of Vendor
Booking Commission invoice received from vendor
Debit note to Vendor Against Freight Paid by organization on Vendor’s behalf
Debit note to Vendor against Octroi Paid by organization on Vendor’s behalf
Debit note to Vendor against Price difference (Bill Booking)
Debit note to Vendor against any other miscellaneous Expenses payable » Read more: SAP FI Vendor Invoice

Vendor Master Data in SAP

December 13th, 2008

Vendor Master Data in SAP / Accounts Payable

Creation of vendor code in SAP

Vendor master records are divided in to the General data, company code data and Purchase organization data.
(1) General data contains Vendors Name, Address, Telephone number, language, Accounting control (if vendor is customer), vendor bank name & Account number etc
(2) Company Code data contains reconciliation account number, payment    terms, withholding tax, sales tax, service tax, excise detail etc                                   
(3) Purchasing Organization data (refer PDD of MM Department) » Read more: Vendor Master Data in SAP