Monday, October 01, 2012

QnA 2


Account Assignment Model?

‘Account Assignment Model’ is a ‘reference method’ used in document entry when the same distribution of amounts to several Company Codes, cost centers, accounts, etc., is frequently used. Instead of manually distributing the amount among accounts or Company Codes, you may use equivalence numbers for distributing both the credit and debit amounts. A cross-Company Code account assignment model can also be created.
The account assignment model may contain any number of GL accounts. The GL account items need not be complete. The model can be used across several Company Codes, and can even include Company Codes from non-SAP systems. You can use the account assignment model while ‘parking’ a document (but you cannot use a ‘reference document’ for ‘parking’).
    The use of account assignment models is limited to GL accounts.
Unlike a ‘Sample Document,’ an account assignment model may be incomplete and can be completed during document entry by adding or deleting or changing the data already saved in the model.

What are the Month End Closing Activities in Finance?

1. Recurring Documents.
a) Create Recurring documents
b) Create Batch Input for Posting Recurring Documents
c) Run the Batch Input Session

2. Posting Accruals or Provisions entries at month end

3. Managing the GR/IR Account-Run the GR/Ir Automatic Clearing

4. Foreign Currency Open Item Revaluation-Revalue Open Items in
    AR.AP
5. Maintain Exchange Rates

6. Run Balance Sheets –Run Financial Statement Version

7. Reclassify Payables and Receivables if necessary

8. Run the Depreciation Calculation

9. Fiscal Year Change of Asset Accounting if it is year end

10. Run the Bank Reconciliation
11. Open Next Accounting Period

Follow the steps

Step1

After posting the down payment amount you have to clear the down payment amount $25 against the Invoice .the transaction code is F-54.

Step2
Now go to transaction code f-44 and put the vendor code and go to the residual clearing tab and residually clears against $25 against $100.
what you have to do ...you select all the line items and the deselect . again you select/activate line items of $25 and $100 and in the next box (line item$100) double click ......see automatically $75 will appear.....simulate and post.

Now you go to F110 ....run the proposal......you can see the line items of $75 to be paid and it will be seen as a credit balance.


You need to use a down payment request to a vendor. This will create a noted item in the vendor, which you need to include with the APP. This will post the advance to the vendor as a special G/L transaction.
There are two steps to make an advance payment to a vendor:
1.Create a down payment request through T-code F-47.
2.in FBZP for All Company Code do not foreget to put F (down payment request) and down payment Sp. GL you want to perform payment for.
2.Post the down payment through T-code F110 (APP). The system will pay for all down payment requests by    check or bank transfer

line item display and open item management in vendor account are always preset for every vendor account

The logic behind the use of special periods is to identify and have control over transactions after the closing of normal posting periods.
   Management adjustments
   rectification entries by auditors


In transaction code OB52 click on new entries and maintain an interval or a single GL code for the account type S with the posting period variant. If the GL codes are not in sequence then you need to maintain further entries for the posting period variant and account type S

If we select the “relevant to cash flow” check box it will determain that the GL account is related to Cash receipt account / cash disbursement account and the same can use to make out going payment through either cash or bank.And it can usefull while making cash flow statements.

If you are using Cash Management and Cash Concentration functionality in Treasury module then this field has great importance.You will select this field for cash and bank accounts because all movements in these accounts have cash flow relevancey.
The following accounts are typically defined as cash flow accounts:
- bank account
- account for bank charges
- check clearing account
- Clearing account for incoming payments

If you don't select this field for the bank account which you use for making down payment, withholding tax will not be calculated.
We can post the vendor document in F-43 and it allows to make outgoing payment entry through F-53 also
But we can’t run the manual check number from the register It will through the error message "the particular document no is not a payment document


Ans)Customers with whom you transact business have to pay their  dues eventually. Generally the due date on which the customers have to settle the dues is stipulated in the  terms of payment agreed into with them.

Now one of the three logical events can happen:

1) Customers pay on the due date specified:

They pay the entire value of money for which you have  supplied materials and / rendered services. Not a bad
situation at all..... you can meet your financial commitments as planned since you have received prompt
payment ....

2) Customers pay ahead of the due date specified:

This is a better situation for you..... Your money comes ahead of your original plan and you can be safe about
meeting your financial commitments as planned ......Therefore, You waive off a small part of the dues owed by your customers since your working capital is not hampered.

3)What a mess things are in this business world !. You had promised money to your creditors assuming that your
customers would pay promptly and that is not happening.  This is a Domino effect commencing with your customers which you are forced to pass on to your vendors..... That is not one bit good !!!!. You must do something to prevent  recurrence of such an uncomfortable situation !

What are the corrective measures which you intend to take?
SAP calls it as DUNNING.

As a first step, you need to identify which of your  customers have not paid their dues promptly . You need to 
remind each one of such customers about the non-payment and insist that the dues are settled immediately. This is done through letter correspondences ( indicating break up of  dues owed by the customers). Some deaf customers who do not heed your letters need to be reminded often ( that is periodically , each time the letter sounding a little sterner than the earlier one.

The second optional step would be to levy penal charges for the defaulted payment in the following manner:

1. Levy of interest for nonpayment / belated payment

2. Levy of incidental charges incurred with regard to dunning ( the process of dunning is going to cost you by
way of follow up,dunning and printing costs, maintenance of additonal records,additional labor incurred by way of wages
to dunning clerks etc...)

Customers who are tone deaf even after repeated reminders would be handled through a legal process.

This is the process of dunning.
  
Generally, each time you dun a customer you are crossing one level of dunning. Though you can dun upto a maximum
of nine times , you would normally resort to legal help after dunning three or four times, at the most. The number of
dunning levels you need can be configured and theoretically it ranges from 0 to 9 levels ( 0 if your company is run by
an inefficient management which does not bother to collect money on time  and 9 if your management is too liberal with
your customers !).

I trust this gives you a basic understanding of what dunning is and what the dunning levels are.....


1) Check whether the document type (DR) and no. ranges have given  or not?
2) Create customer account and sales account for sales invoice posting
3) Assign the reconciliation account(sundry debtor) to sub ledger customer account.
4)Check the posting period is open or not for AR & G/L
5)check no.ranges assigned to document types RV and KA
6)tolerance group
7)check the recon a/c and sales a/c in FS00 because it might be a 

chance of blocked from posting ..

Account Currency indicates the currency in which this Account is held.
When creating a G/L account, you must define the currency in which the account is to be kept.
This defines the following:
·                     The currency used for postings made to this account
·                     The currency in which transaction figures are updated and the account balance is displayed
You specify the account currency in the company code area of the G/L account master data. This allows you to keep the G/L account in the local currency of each company code.


This is especially useful for international groups that have all subsidiaries use the same chart of accounts but with the accounts kept in the local currency.

Features
When setting the account currency, you have two options available:
·                     If we Enter the local currency of your company code.                                                                                         The system automatically uses the local currency that you defined when creating the company code as the default value. This allows posting to the G/L account in any currency. 

When you make a posting in a foreign currency, the amount is translated into the local currency. For more information, see 
 Posting a Document in a Foreign Currency.

The transaction figures are kept as follows:
·                                                                     In the local currency, that is, the total of all the amounts posted in the local currency
·                                                                     In the individual currencies, that is, the total of all the amounts posted in various currencies.
·                     If we Enter a foreign currency.                                                                          
 If the Currency is other than Company Code Currency then, User can only post items into this Account in which the Account is mentioned. The transaction figures and the account balance are kept in the foreign currency entered and in the local currency.
Scenario: If you have bank account in US wherein only USD currency is posted, so your business does not want to post any other currency so you will put USD in this field.

Balances in Local Currency’ Only
It means the balances are updated only in local currency when users posts to this Account.
even if the document posted in foreign currency. In FS10N or FAGLB03, you will not be able to display balance in foreign currency..
Example: Consider an invoice for USD 1,000, which on that day translates into an amount of INR 45,000 with an exchange rate of I USD=INR 45. Imagine that when the goods are received, the exchange rate was 1 USD=INR 44.
         If the indicator is set, the balances are updated only in local currency @ Rs.45000 the system ignores the exchange rate as if the line items have been maintained only in the local currency (INR)(Rs45000), and the items are cleared.
         If the indicator is NOT set, the system makes a posting for the ‘exchange rate difference’ (INR 1, 000) before clearing the two line items.

This Option is used both for 
·                     Cash Discount Clearing 
·                     GR/IR Clearing Account 
·                     It is also used for Balance Sheets Accounts which not managed Open Item basis Or not kept in foreign Currency.(but not used for Customer / vendor reconciliation Accounts.) 
you need to set this indicator so that the transactions are posted without posting any exchange rate difference that otherwise might arise.

QnA 1


Functional Spec is mainly prepared for the purpose of developing the new reports (this happens only when SAP standard report not achieve the client purpose) using the ABAP Program. for ABAPers you need to give the details of the Tables , Fields and the logic how to pick the value and get the report.

The information contains in the functional specs are:

a)Document segment (BSEG): which contains the company code,posting keys, vendors,etc.

b)the line items(BKPF) consists of document type, etc.

for example: from BSEG table you have to go to the field of BUKRS for company code, BSCHL for Posting Keys.
From BKPF table you have to go to the field of BELNR for document Number, etc.

Based on your functional specification the Abaper will design the report using his technical specifications.

The above are examples only to understand. There are plenty of tables & fields for FI, CO and Assets separately.

Please assign points, if the above are useful.

Functional spec are based on the business requirment and contains details of end user expectations of the product Functionality
·                     document describes requested properties of inputs and outputs
·                     the blueprint for how you want a particular application to look and work
·                     it details what the finished product will do 
·                     who a user will interact with it and
·                     what it will look like
the key benefit of writing up a funtional spec is streamlining the development process. time and productivity are saved during development stage because the programmers can program instead of also working out the logic of the user experience

S/W or program will be developed based on the functional specs
it consist of
1.                   business requirments- brief detail about the business process and the need of your cutomized program/report
2.                   security consideration- who all can have access to this program and level of security whether it is at co.code level or country level
3.                   business dependences- whether is there any other process / program should have been completed before the execution of this program
4.                   Data requirement
5.                   priority- whether the failure lead to production stoppage or any work around
6.                   error management
7.                   how the program retrive the data if it is a report program
Eg:-
The requirement was to add the vendor name to the fbl3n screen, we couldnt add this so we we went for a new report with all the fbl3n fields + vendor name. This is a spec for the program.


DEV ID Sales tax report
Functional Team Zaid Azam
(phone)
SAP Dev. Team (lead) Zaid Azam (phone #)
(member) (phone #)
Phase / Priority Phase 1
Medium

The above part is just a header, which system the report is in what report is it i.e sales report, material reprot etc, then the consultants name, lead name etc.
how important it is medium , low, high
Revisions
Rev. Id Rev. date Author Description
00 Initial release

1 Report definition
Basic Information

Report type 1                  A/P
Report type 2                  Printed
Language requirem.
Printer requirement       Local printer / system printer
Paper requirement        Landscape
Source environment:     R/3
Module:                            FI
Suggested technique   ALV / other
Triggered:                       Manually
Frequency:                      On-demand
Volume:                           Daily

Then in the report definition

you specify what module it is in i.e FI, MM etc

what subledger AP/AR etc

how often it will be printed etc etc ( nothing really usefull here, just giving a business touch)

2.Functional Requirements
Functional Requirements
Selection        Posting Date, G/l account

Narrative flow The report should list the all the transactions of the G/l account( all items i.e open and cleared) selected on the initial screen. It should list the vendor name and number when a G/l transaction is of a vendor
Assumptions / issues
Should have the capability of being exported to excel
This is the important part

here you tell what are the fields on the selection screen.
Then in the narrative flow you should tell the abapper what the report should do like it’s mentioned above, eg apart from above get the sales for customers who reside in California between the date range specified on the selection screen

3.Processing logic

Processing logic
Step 1 Enter g/l account (HKONT) on the selection screen and run with or without a date range Or run by a date range  only without specifying a G/L

Step 2 Get the G/L number from BSIS that was selected on the initial screen Or get all the G/ls that had postings in the posting date ( BUDAT) specified on the initial screen.

Step 3 Get the amount ( WRBTR) from BSIS ( Open and cleared both are in BSIS)

Step 4 Take the Document Number (BELNR) from BSIS and get the vendor number for that doc number from BSIK ( open item), from BSAK ( cleared) if item is paid.

Step 8 Should get the vendor name from LFA1 for the vendor number from BSIK or BSAK
Step 9
Step 10
 

Processing Logic tells him in detail about which fields should come and from which table( not necessary to give technical names and tables, he could find that out, depends on the abbapper)

4.Output
Output

4.1 Layout

FORMAT 

G/L             Posting date           Amount         Doc type      Text                   Doc number      Pk           Vendor #       Name
650100      12/03/2006               500                 SA          Test for report      19000042342    40            10229               GMC

In the format i put an excel view of how the final report should look like

4.2 Header elements

SAP Field Report Field Comment
BSAK _LIFNR,BSIK_LIFNR Vendor number
LFA1_NAME1 Vendor Name
BSIS_BUDAT Posting Date
BSIS_HKONT G/l account 

4.3 Line item

SAP Field Report Field Comment
BSIS_WRBTR amount
BSIS_BLART Document type
BSIS_SGTXT Item text
BSIS_BSCHL Posting Key 

Then i enter the fields that should be there in the report first the table name is liste then the technical name and then the english name. Both header and line items are sprecified.

Additional topics
Unit Test Suggestions: Same as the standard SAP report FBL3N. Only addition is the vendor name and number
Security/ Authorizations:
Error handling
Dependencies
References
Out of scope requirements NA

2.Eg 
 I need one new report like in the output i need only company code, Vendor number and recon.account assigned. like as below:
Company Code                                          Vendor Recon                                                account
1000                                                                90000001                                                     156001
1000                                                                90000002                                                     156001
2000                                                                90000001                                                     156002

for the above requirement with the input selection criteria like as below

Company Code ( ) ( )
Vendor ( ) ( )

if you give input selection as above as required you will get the output as given above

Logic should be as below:

for input selection
Company Code - BUKRS is the ABAP field for the company code
Vendor - LIFNR

for the output

Company Code - LFB1-BUKRS
Vendor - LFB1-LIFNR
Recon account - LFB1-HKONT

You will get the recon account details in the LFB1 table , if you give the logic as above , ABAPer will write the program for the same.


When you post documents in SAP, there are instances where the system also adds some more line items (such as tax, cash discount, gain/loss from foreign exchange transactions, etc.) besides the ones you have entered in the document. This helps to reduce your work as the system calculates these automatically. However, you need to define accounts you want the system to automatically post to; this will ensure that no manual posting is allowed to any of these accounts.

Post automatically check box is valid for only actual postings.
You can choose post automatically for withholding tax accounts, GR/IR clearing accounts, all sales tax accounts, discount accounts, consumption accounts. etc

for all these accounts you are only posting automatically, means you are not giving the posting key and GL account while posting any transactions.

In the GL master record a check box exists where in the automatic posting option is selected called " Post automatically only".

Stock and consumption accounts of GL accounts that should be automatically posted.
Stock and Consumption accounts (Inventary Raw Materials) you can select post automatically.
If you set this indicator this account can only be posted to by the system using account determination tables.



Sort Key: When u post the line item in GL account, the field called Assignment is populated, and when u run the report of the GL Account ( GL account line item report), the system by default sort the value specified assignment field.

   `001  Posting Date

   `012  vendor no
  
  `014  Purchase order

   `018  Asset number

   `031  Customer number

Why we are using sort keys.

Straight answer to this is sort key offers great help in Automatic Clearing.

First we understand how does it function. If you have created Bank GL and there you have used 001 (posting date)
as sort key then whenever you make entry for that bank Gl your sort key "Posting date" is automatically updated
in "Assignment" field unless you manually insert anything in assignment field.

Let's take a simple example for why sort keys are helpful.

Suppose, there is GR/IR account created with sort key 014 (Purchase Order) so at the time of

1. Goods receipt Purchase order with item no will automatically filled in assignment field.

Inventory dr. 15000

GR/IR cr 15000.

In GR/IR account item Assignment would be 150000 10.

2. Invoice through MIRO will also feed Purchase Order with item no in assignment field.

GR/IR dr . 15000
Tax dr. 5000
Vendot cr. 20000

In GR/IR account item Assignment would be 150000 10.

Now your entry is over. There are large number of such entries posted in the period for the GR/IR account.
So, manual clearing becomes very tedious for GR/IR clearing account. In order to avoid that Automatic Clearing program is configured in OB74, where you give field ZUONR i.e. assignment in first criterion. So, line items with same assignment and amount will be cleared automatically upon F.13 transaction.

QnA



A sub ledger is used for tracking individual items and transactions separate to the General Ledger (GL). Sub-
ledgers may exist for, but are not limited to Accounts Receivable (AR), Accounts Payable (AP), Inventory and Fixed
Assets etc. Without a sub-ledger individual customers or inventory items would require their own GL code making the GL unnecessarily large. Sub-ledgers also allow for more specific detail to be included in transaction details. Each sub-ledger links to the GL by way of a control account (e.g. Debtors control the AR sub-ledger etc.). The total of the sub-ledger account should equal the balance in the control account at all times. Individual transactions
should be posted via sub-ledger not directly to the control account. Reconciliations should be performed between the sub-ledger and control account on at least a monthly basis to ensure this is the case.


LSMW is a tool used to transfer data from legacy system to R/3 periodically or once.It supports conversion of data and Batch Input, BAPI, IDOC or Direct Input can be used as the method for transfer of data.Total of 26 processing steps are available in LSMW ,In case of data transfer using Batch Input only 14 steps are required.

Execute the transaction LSMW to start transfer of data,Before using the LSMW we should have good knowledge about the business object and the fields that will be transferred.
The main screen of LSMW provides wizard-like step-by-step tasks,  To complete your data conversion, you need to execute these steps in sequence. Once a step is executed, the cursor is automatically positioned to the next step.

Note that these steps may look different depending upon your Personal menu settings. You could make step numbers visible by ‘Numbers on’ icon or hidden by ‘Numbers off’ icon. You can execute a step by double-clicking on the row. Toggle icon ‘Doubleclick=Display’ or ‘Doubleclick=Edit’, makes the step in ‘display’ mode or ‘change’ mode.

There are 14 steps that are normally used and these are:
1)   Maintain Object Attributes.
2)   Maintain Source Structures.
3)   Maintain Source Fields.
4)   Maintain Structure Relations
5)   Maintain Field Mapping and conversion rules .
6)   Maintain Fixed Values,translations ,user defined routines.
7)   Specify Files .
8)   Assign Files .
9)   Read DATA.
10) Display Read Data.
11) Convert Data.
12) Display Converted Data.
13) Create Batch Input Session.
14) Run Batch Input Sesion.

1)   Maintain Object Attributes.
In this example, you will be updating the customer master records with the help of recording a transaction (XD02).
 a.Choose radio button Batch Input Recording and
 bclick on the recording overview icon to record the R/3 transaction.
 c.Enter the Recording nameasXD02_REC,the description as Customer Master Updates Recording,   and
 d.the transaction code as XD02(FS00 in case of gl accounts)
Once the transaction is completed, R/3 records the flow of screens and fields and saves the information,


2)   Maintain Source Structures.
Give a name and a description to the source structure

3)   Maintain Source Fields.
In this step, you need to list what fields are present in the source structure. The easiest way is to click on ‘Table Maintenance’ icon to enter Fieldname, Type and Length for each field
Note that your input file will have four fields as key fields and you need to update three fields in the system

4)   Maintain Structure Relations
Execute a step to ‘Maintain Structure Relations’. Since, there is only one Source and Target Structure, the relationship is defaulted automatically

5)   Maintain Field Mapping and conversion rules .
In this step, source/legacy fields in each structure are assigned to R/3 fields. It may be done individually for each R/3 field, which being time-consuming for complex structures or we can use automatic mapping utility (Extras > Auto-Field mapping).

We can specify the conversion rule to be used to convert an LS field into the corresponding R/3 field. For this, use predefined conversion rules or create your own conversion rules in the editor.

You may use the buttons ‘Initial’, ‘Constant’, ‘Move’ & ‘Fixed Value’ to assign different values. You may also assign different rules by using the button ‘Rule’. automatic mapping utility (Extras > Auto-Field mapping).

6)   Maintain Fixed Values,translations ,user defined routines.

7)   Specify Files .
In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive)
Create an Excel file with your data and save it as a Tab-delimited text file on your local drive.

8)   Assign Files .
Execute step ‘Assign Files’ and the system automatically defaults the filename to the source structure.

9)   Read DATA.
In this step, LSMW reads the data from the source file (from your PC’s local drive).

10)  Display Read Data.
This step is optional. If required, you can review the field contents for the rows of data read

11)  Convert Data.
This is the step that actually converts the source data (in source format) to a target format.Based on the conversion rules defined, source fields are mapped to target fields.

12)  Display Converted Data.
Again this is an optional step to view how the source data is converted to internal SAP format

13)  Create Batch Input Session.
Once the source data is converted in an internal format, you can create a batch session to process updates .

14)  Run Batch Input Sesion.

You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in the system. You can confirm this by viewing the customer master records (XD03).

Note! Browsing thru these 14 steps, you may get a feeling that this is a very lengthy and time-consuming activity. However, for the purposes of demonstration, I have made it detailed. Although it looks lengthy, actually it takes hardly few hours from start-to-finish! After playing around with few simple LSMW scripts, you will find it so easy to change and create more complex ones.



Depreciation keys = depreciation method + depreciation rate.

depreciation method could be slm(straight line method), wdv(written down value method)etc

depreciation rate is nothing but the percentate like 5%, 6%,etc

hence dep key = slm + 5 %

A Depreciation key can be considered as a box which houses all the depreciation methods

You are aware that every fixed asset keeps losing value as time progresses and the loss of value is called as depreciation.

Depreciation Keys are pre-defined mathematical functions which perform number crunching so as to reduce the value of
asset (usually) with the passage of time.

A Depreciation Key is a bundle of various methods of standardized depreciation.  A depreciation key contains

a.  Base method (such as straight line depreciation etc.)

b. Declining Balance Method ( more affectionately known as WDV method, Written Down Value Method) this menthod includes both the declineing balance method sum of the years digits method. the normar declining balance method of dep mutiplies the straight line % by a given factor usually the factor would be 2/2.5/3 which means that your depreciation would be 2/2.5/3 times more under this method as compared to SLM this is just to accelerate the intial depreciation so that you have earmarked a sizable portion of your intial profits.

c. Maximum Amount Method ( an arbitrary pre-defined  amount up to which depreciation of an asset can be carried out)

d. Multi-level method ( which is a mixed bag of one or more of the aforesaid methods ) . Usually it has been
mathematically proved that the Declining Balance Method cannot be effective in writing off the value of an asset in
full ( viz. reduce to zero balance) in a finite period of time. In order to avoid this complication, you can use
multi-level method which effects a change-over from declining balance method to straight line method under
certain conditions pre-defined in the depreciation methods/
keys)
each level represents a validity period for a given percentage rate.

e. Period Control Method ( this tells you the date on which capitalization / de-activation, start of depreciation could
commence with regard to asset acquisition, additions to it, retirement and transfer ).

All these depreciation methods are bundled into a depreciation key which is assigned to the asset master record.
in the class field of dep key we select the actual method

There are many depreciation keys available and you can create them too. Usually they are country-specific.

Assignment of a suitable depreciation key to the asset master helps in the fair valuation of assets and profits /
losses ( through fair estimation of depreciation of assets).

Product Costing


Product Cost = Materials Cost(ROH + HALB Materials Cost)+Activity Cost (Operation Cost)+Overhead Cost.
1.Raw materials cost are generally entered as Planned price along with the valid from date in Costing 2 view, and price control indicator is "V". Origin group has to be given to all the Raw materials in costing 1 view.
2. For HALB Materials Price control indicator will be S for Inhouse manufactured & V for externally processed materials (Sub-Contracted Items) respectively. Also assign Overhead group for all Inhouse manufactured items.
3. No need to enter any value for the materials having S as the price indicator and for Sub-contracted items that's F30 also no need to enter any cost in the material master.
4. Activity cost is the cost incurred in performing individual operation. This cost is captured via the work center which we mention in each operation in the routing of that product. A Cost centre and an appropriate activity type is assigned in the work centre.
5. Proper Cost should be assigned for the combination of Activity type and Cost centre.
6. Overhead cost is the indirect cost that we capture according to the customer's requirement.
7. If certain items for certain products alone should not be considered for costing means, then we can achieve this using costing relevancy indicator in the BOM and for the activity(operation's mentioned in routing) which should not be considered for costing also can be mapped by removing the costing relevancy indicator in routing. Overhead group is assigned in Costing1 view.
8. Creating Cost center - KS01
9. Create Activity Type - KL01.
10. Assiging Rates for a cost center/activity type combination in T code KP26.
11. Cost estimate Related T codes are CK40N,CK11N,CK24.
12. UseCK40N always, so that you can do the costing ,mark the price and release the same. Generally Cost Rollup will be taken for Finished product so that the system automatically calculates for the Semi- Finished products standard cost.
13. IF you use CK11N,then only costing will be done, but for marking and release you have to use CK24.
14. For each Production order type in T code OPL8 Order Type Dependent Parameters - Under controlling tab - Costing variant Planned and actual has to be assigned. 
15. In REM scenario - Product Cost Collector has to be created using T code KKF6N for all Inhouse Manufactured assemblies.
Check these links [What's Order settlement?|https://www.sdn.sap.com/irj/scn/thread?messageID=6237793#6237793]
*Steps For Order Settlement*
 You should follow following steps for Order Settlement after confirmation :
1. After Final Confirmation of Order ( Status : CNF) make GR for order using Tcode : MIGO / MB31 so Production Order Status will be DLV.
2. Then complete the order technically by using Tcode : CO02----> Functions ( Menu)-----> Restrict Processing -------> Technically Complete. You can carry out TECO for multiple Orders in Tcode : COHV (Mass Processing).
3. Over head calculation- KGI2 or CO43 4. WIP calculation - KKAX or KKAO 5. Variance - KKS2 or KKS1 6. Settlement - KO88 or CO88.