PRODUCT COST ACCOUNTING ENTRIES FLOW (FI-PP)

Many People are searching for accounting entry flow for PRODUCT COSTING, which are below:

1) MATERIAL RECEIVE AGAINST PURCHASE ORDER (RM)

 

GL A/c	GL Description	DR/CR
2301101	RM STOCK	DR.
1991001	GR/IR A/C	CR.

2) MATERIAL ISSUE, (CONSUMPTION) RM

GL A/c

GL Description

DR/CR

4001101	STOCK CONS	DR
2301101	RM STOCK	CR

3) ACTIVITY

MACH HR ALLO ACTIVIT          1125     DR.

LAB HR ALLO ACTIVITY           967.50  DR.

OTHR OH ALLO ACT TYP          1260.00 DR.

DIESEL                                           364.50   DR.

                COST CENTRE                 3717.00 CR

4) GOODS RECEIPT FOR PRODUCTION (WE)

GL A/c

GL Description

DR/CR

2302002     F.G. MATERIAL                      DR.

4111000     CHG IN INV.PROC.ORD.      CR.

4031000     PRICE DIFFERENCE            DR/CR.

5) GOODS ISSUE FOR PRODUCTION OREDRE (WA)

GL A/c

GL Description

DR/CR

4002002      CON F.G. MATERI          DR

2302002       F.G. MATERIAL              CR

6) DURING DISPATCH OR DELIVERY

     COGS A/C                                       DR

     INVENTORY                                   CR

7) DURING SALE

    CUSTOMER                                    DR

     SALES                                             CR

Create Own Screen Varient for ANY TrasactionTcode

Transaction variants used for the below purpose:

1. Changing fields to read only(Display)
2. Making master data / transaction fields to required/Invisible
3. Inserting default values for the fields etc..

Here we will discuss with 2 simple examples:

1. Making Cost centre responsible user required while creating/changing master data
2. Making FV60/FBV2 (parked invoice) payment method field display only

Configuration:

1. Making Cost centre responsible user required: There will be always requirement for the Master data field control. In this example in order to make cost centre user responsible required we are using the transaction variant.

Transaction:

SHD0

Create Own Screen Varient for ANY TrasactionTcode

Transaction variants used for the below purpose:

1. Changing fields to read only(Display)
2. Making master data / transaction fields to required/Invisible
3. Inserting default values for the fields etc..

Here we will discuss with 2 simple examples:

1. Making Cost centre responsible user required while creating/changing master data
2. Making FV60/FBV2 (parked invoice) payment method field display only

Configuration:

1. Making Cost centre responsible user required: There will be always requirement for the Master data field control. In this example in order to make cost centre user responsible required we are using the transaction variant.

Transaction:

SHD0

Currency in INR format

There is 2 way to use currency in INR format 

1. Use T.code - SU3

2. Use T.code - SU01

HOW TO CHANGE DATE FORMAT

Q. - HOW TO CHANGE DATE FORMAT
ANS - GO TO OY01 > CHANGE HERE DATE FORMAT

HOW TO DISPLAY VALUES IN INR RUPEES FORMAT

Q. -- HOW TO DISPLAY VALUES IN INR / RUPEES FORMAT
ANSWER : -- GO TO OY04 >  ASSIGN 3 DECIMAL WITH INR > SAVE

TREE TURN OFF IN FB60, FB50, FB70

1. Manual Tree Turn Off
2. Edit > Screen Variant > Reset Screen Variant.

Thanks