Month: July 2013

SAP-COPA: Source and Target Fields

Posted on by Jayanth Maydipalle
Use: You enter the source and target fields for derivation in a derivation step.
Source fields:
You can use the following operating concern fields as source fields:
  • All fixed characteristics
  • All user-defined characteristics
  • All characteristics copied from SAP tables or from the field catalog
  • All characteristics copied from customer hierarchies (CO-PA HIE01 to HIE10)
  • All quantity unit fields (CO-PA *_ME)
Target fields:
You can use the following fields as target fields for derivation:
  • All user-defined characteristics
  • All characteristics copied from SAP tables or from the field catalog
  • All characteristics copied from customer hierarchies (CO-PA HIE01 to HIE10)
  • Only the following fixed characteristics:
  • Customer number (CO-PA KNDNR)
  • Product number (CO-PA ARTNR)
  • Business area (CO-PA GSBER)
  • Profit center (CO-PA PRCTR)
  • Sales organization (CO-PA VKORG)
  • Distribution channel (CO-PA VTWEG)
  • Division (CO-PA SPART)
  • Plant (CO-PA WERKS)
  • All quantity unit fields (CO-PA *_ME)
  • Temporary fields (GLOBAL USERTEMP1 to GLOBAL USERTEMP8)

OKP1 – Period Lock

Posted on by Jayanth Maydipalle

Purpose

Use this procedure to open or close the month on the Controlling module/ledger. This will allow or block postings to the CO ledger, including through posting from FI module. Period locks will be managed on the Controlling Period by the Financial Reporting office, based on when the Fiscal Month has been closed for financial reporting purposes.

There are separate CO period locks & Transaction locks for “Actual postings” and “Plan postings”. 

Trigger

Perform this procedure, together with the FI module close, to indicate the end of the fiscal month, according to the Month-end Closing schedule.

Prerequisites

Before closing a period, the user should make sure that all postings to the CO ledgers (including those originating from revenue & expense accounts into FI ledger) for the current month are completed by the Financial Reporting office and the User Departments. For this purpose, it is necessary to follow the month-end closing schedule, which would outline the sequence of the steps.

Menu Path

SAP menu ⇒ Accounting ⇒ Controlling ⇒ Cost Center ⇒Accounting  Environment ⇒ Period Lock  ⇒ OKP1 – Change

T Code: OKP1

period_lock_unlock

 

Accounts Payable Transaction Codes- SAP

Posted on by Jayanth Maydipalle

Document Entry:

FB60 – Invoice
F-43 – Invoice – General
FB65 – Credit Memo
F-41 – Credit Memo – General
FB10 – Invoice/Credit Memo Fast Entry
FV60 – Park or Edit Invoice
F-63 – Invoice Parking – General
FV65 – Park/Edit Credit Memo
F-66 – Credit Memo Parking – General
F-47 – Request Down Payment
F-48 – Down Payment
F-54 – Clearing Down Payment
F-40 – Payment Bill of Exchange
FBW6 – Check/Bill of Exchange
F-52 – Incoming Payment
F-42 – Without Clearing
F-51 – With Clearing
F-55 – Statistical Posting
F-57 – Noted Items
FKMT – Account Assignment Model
FBD1 – Recurring Entry Document
F-01 – Sample Document
F-53 – Post Outgoing Payment
F-58 – Post + Print Forms for Outgoing Payment
F-59 – Payment Request for Outgoing Payment

Document

FB02 – Change
FB09 – Change Line Items
FB03 – Display
FB04 – Display Changes
FBV0 – Post/Delete Parked Document
FV60 – One-Screen Transaction for Posting/Deleting Parked Documents
FBV2 – Change Parked Documents
FV60 – One-Screen Transaction for Changes Parked Documents
FBV3 – Display Parked Documents
FBV4 – Change Header Parked Documents
FBV5 – Display Changes Parked Documents
FBV6 – Reject Parked Documents
FBD2 – Change Recurring Entry Documents
FBD3 – Display Recurring Entry Documents
FBD4 – Display Changes Recurring Entry Documents
F.56 – Delete Recurring Entry Documents
FBM2 – Change Sample Documents
FBM4 – Display Changes Sample Documents
F.57 – Delete Sample Documents
F-56 – Reverse Statistical Posting
F-46 – Reverse Check/Bill of Exchange
FBWD – Process Bill of Exchange Payable
FB08 – Individual Reversal of Document
F.80 – Mass Reversal of Documents
FBU2 – Change Cross-CC Transactions
FBU3 – Display Cross-CC Transactions
FBU8 – Reverse Cross-CC Transactions
FBZ5 – Print Payment Forms

Account

FK10N – Display Balances
FBL1N – Display/Change Line Items
F-44 – Clear
FB12 – Request Correspondence
F.64 – Maintain Correspondence

Master Records

FK01 – Create
FK02 – Change
FK03 – Display
FK05 – Block/Unblock
FK06 – Set Deletion Indicator
FK08 – Single Confirmation of Change
FK09 – List Confirmation of Change
FK04 – Display Changes
F.48 – Purchasing – Accounting
FK15 – Send Company Codes
FK16 – Receive Company Codes
XK01 – Create Centrally
XK02 – Change Centrally
XK03 – Display Centrally
XK05 – Block/Unblock Centrally
XK06 – Set Deletion Indicator Centrally
XK04 – Display Changes Centrally

Periodic Processing

SCMA – Schedule Manager
F110 – Payments Automatic
F110S – Schedule Payment Program Periodically
F.4A – Without Open Items Interest on Arrears Calculation
F.4B – With Open Items Interest on Arrrears Calculation
F.4C – Without Postings Interest on Arrears Calculation
F.47 – Free Selections Interest on Arrears Calculation
F.44 – Balance Interst Calculation Calculation
F150 – Dunning
F.13 – Automatic Clearing
F13E – With Clearing Currency Specified
F.61 – As per Requests Print Correspondence
F.63 – Delete Requests Print Correspondence
F.27 – Periodic Account Statements Print Correspondence
F.62 – Internal Documents Print Correspondence
SO10 – Enter Text Standard Letters
F.66 – Issue Letters Standard Letters
F.18 – Print Letters Balance Confirmations
F.1B – Create Index Balance Confirmations
F.1A – Group Vendors Balance Confirmations
F.14 – Execute Recurring Entries
F.15 – Lists Recurring Entries
S_ALR_87012114 – Bill of Exchange List
S_ALR_87012115 – Extended Bill of Exchange List with ABAP List Viewer
F.18 – Balance Confirmation: Print
F.1B – Balance Confirmation: Create Index
F.1A – Balance confirmation: Group vendors
FB2E – Cross-System Reconciliation of Affiliated Companies
F.05 – Valuation of Open Items in Foreign Currency
FAGL_FC_VAL – Foreign Currency Valuation of Open Items (New)
FJA4 – Inflation Adjustment of Open Items in Foreign Currencies
FJA6 – Inflation Adjustment of Open Payables in Local Currency
F101 – Reclassify Receivables/Payables
FAGLF101 – Sorting/Reclassification (New)
S_ALR_87012098 – Open Item Account Balance Audit Trail from the Document File
F.07 – Balance Carryforward

Withholding Tax

S_P00_07000134 – Generic Withholding Tax Reporting
S_PL0_09000447 – Withholding Tax Report for the Vendor

Information System

S_ALR_87012077 – Vendor Information System
S_ALR_87012082 – Vendor Balances in Local Currency
S_ALR_87012093 – Vendor Business
S_ALR_87012079 – Transaction Figures: Account Balance
S_ALR_87012080 – Transaction Figures: Special Sales
S_ALR_87012081 – Transaction Figures: Sales
S_ALR_87012078 – Due Date Analysis for Open Items
S_ALR_87012103 – List of Vendor Line Items
S_ALR_87012083 – List of Vendor Open Items for Printing
S_ALR_87012084 – Open Items – Vendor Due Date Forecast
S_ALR_87012085 – Vendor Payment History with OI Sorted List
S_ALR_87012104 – List of Cleared Vendor Items for Printing
S_ALR_87012105 – List of Down Payments Open On Key Date – Vendors
S_ALR_87012086 – Vendor List
S_ALR_87012087 – Address List
S_ALR_87012089 – Display Changes to Vendors
S_ALR_87012090 – Display/Confirm Critical Vendor Changes
S_P99_41000099 – Payment List
S_P99_41000101 – Check Register
S_ALR_87012119 – Cashed Checks
S_P99_41000102 – Number Ranges for Checks

P2P:

ME51N- Create Purchase requisition

ME21N-Creare Purchase Order

MIGO- Make Goods Reciept entry

J1IEX-Create Part 2 Excise Invoice

MIRO-Vendor Invoice

f110-Automatic Payment

SE93-Creating Z*/Y* T-Code

Posted on by Jayanth Maydipalle

se93 is a transaction where you can create your own custom transaction codes…

Custom transaction codes with start with Z* and Y*.. in real time if you have created to report and wanted the end user to use it..he cannot open se38 and enter program name ans execute it… as he does not have access to use it…

so in that scenario you create a transaction called Z_report name and give that transaction to the user to hit it and see the report output.

I would be showing you how to create a simple transaction code using SE93.

First, type in on the object navigator SE93.

215

Click on “ Create Button”

next screen as follows,

311

Select “Program and selection Screen (Report Transaction)”  check box.

Click on “Enter”

next screen,

49

Now you will need to fill in the name of your program in which you would like to assign the transaction code you are creating. Click on the SAVE button.

next screen,

510

Click on SAVE again, then the CHECK button(or you could just click on ENTER.

68

Press “Enter”

79

To change/Rename  the name of  Transaction Code Use SE80

View list of Z-Codes:

Go to T.Code SE93⇒ Enter the value as Z* then press F4, now  the system will show the list of Z- T Codes.

Assign Z code to SE16:

In Tcode SE93,  create a tcode with option

Transaction with parameter option

Then  give the following values

Transaction    :    SE16

then check skip initial screen check box.

In the down table control

field :Name of screen field ,select value

DATABROWSE-TABLENAME

and in the value field give the table name which you want to see in se16 tcode.

Report painter

Posted on by Jayanth Maydipalle
  • Report painter is the main tool for defining reports in the information system in controlling module.
  •  All of the controlling reports (Cost center accounting, internal orders and profit center accounting) are created using report painter. You can also create reports in FI.
  •  With Report Painter you can define reports quickly and easily across rows and columns.
  •  You can use standard reports delivered by SAP as a base, copy them and do minor modifications, so as to suit your requirement.
  • Very often it is felt that the stand and reports delivered by SAP do not meet the user’s requirement. Therefore you need to create new reports.

Transaction code for Report painter:

1) goto SE93 -> ENter a name for tcode

2)Define the Transaction Code as a Parameter Transaction

3)in the default values for selection-screen block enter the Transaction as ‘START_REPORT’ .

4)Check skip initial screen , inherit GUI attribute

5)In the default values ->name of screen field,   use F4 help to select D_SREPOVARI-REPORTTYPE

6) Against this field ,in the value column Enter ‘RW’ .

7) again in  next row of  name of screen field select D_SREPOVARI-REPORT

8) as in step 6 ,enter the name of your report Group to which you haev assigned your Report.

Save and test the TCode.

Report:

Create: GRR1

Change:GRR2

Display: GRR3

Delete: GR34

Report Writer Set:

Create: GS01

Change:GS02

Display: GS03

Delete: GS04

Report Writer Variable:

Create: GS11

Change:GS12

Display: GS13

Delete: GS14

Report Writer Key Figures:
Maintain:GS32
Delete:GS33
Report Writer Report:

Create: GR31

Change:GR32

Display: GR33

Delete: GR34

Report Writer Report Group:

Create: GR51

Change:GR52

Display: GR53

Delete: GR54

Execute: GR55
2013-07-12_171649

Tax Calculation in TAXINN procedure

Posted on by Jayanth Maydipalle

If you selected TAXINN procedure , you can maintained tax rate with respective condition types  in FTXP during creation of tax code.But you should maintain condition record in FV11 t.code for condition types JMX1 & JMX2  are as 100%. Also you can maintain  tax rate for condition types basic excise duty,edu cess , H. Edu cess,VAT/CST in FV11 t.code in stead of maintaining

tax rate in FTXP.

<what are the condition types need to maintained for tax coces>

You can maintain condition types  for Basic excise duty,edu cess , H. Edu cess,VAT/CST  ( both for settoff & inventoried), Service tax recoverable  etc….

<what is the difference between maintaining tax codes in TAXINJ and TAXINN>

Both procedure TAXINJ and TAXINN has thin line difference where as TAXINN procedure is condition based &  TAXINJ is fomula based.If you drag down details of  TAXINJ is fomula based,where you can find Routine( selection with logic in line of condition type)  are play vital role in tax calculation.

Difference between Indian GAAP and US GAAP

Posted on by Jayanth Maydipalle

1. Underlying assumptions: Under Indian GAAP, Financial statements are prepared in accordance with the principle of conservatism which basically means “Anticipate no profits and provide for all possible losses”. Under US GAAP conservatism is not considered, if it leads to deliberate and consistent understatements—revenue recognized when earned or when it is realized or realizable.

2. Format/ Presentation of financial statements: Under Indian GAAP, financial statements are prepared in accordance with the presentation requirements of Schedule VI to the Companies Act, 1956. On the other hand , financial statements prepared as per US GAAP are not required to be prepared under any specific format as long as they comply with the disclosure requirements of US GAAP.

3. Cash flow statement: Under Indian GAAP (AS 3) , inclusion of Cash Flow statement in financial statements is mandatory only for companies whose share are listed on recognized stock exchanges and Certain enterprises whose turnover for the accounting period exceeds Rs. 50 crore. Thus , unlisted companies escape the burden of providing cash flow statements as part of their financial statements. On the other hand, US GAAP (SFAS 95) mandates furnishing of cash flow statements for 3 years – current year and 2 immediate preceding years irrespective of whether the company is listed or not .

4. Depreciation: Under the Indian GAAP, depreciation is provided based on rates prescribed by the Companies Act, 1956. US GAAP , depreciation has to be provided over the estimated useful life of the asset,

5. Long term Debts: Under US GAAP , the current portion of long term debt is classified as current liability, whereas under the Indian GAAP, there is no such requirement and hence the interest accrued on such long term debt in not taken as current liability.

6. Consolidation of subsidiary accounts: Under the Indian GAAP, consolidation of accounts of subsidiary companies is not mandatory. Under US GAAP (SFAS 94),Consolidation of results of Subsidiary Companies is mandatory.

7. Investments: Under Indian GAAP (AS 13), Investments are classified as current and long term. Investments are required to be segregated in 3 categories i.e. held to Maturity Security ( Primarily Debt Security) , Trading Security and Available for sales Security and should be further segregated as Current or Non current on Individual basis.