GL assignment for production variance

Hi,
Production variance GL assignment is to GL89961000 and value fields VV455.
Question: Where is the settings (automatic GL booking to GL89961000) for this production variance?
Thanks in advance.

Hi,
In OBYC you have to maintain gl account for production variance in PRD Transaction event key. If you want this field is to flow to COPA Then in PA Transfer structure you have to maintain allocation structure with this value field assignment.
Regards,
Sreekanth

Similar Messages

CO Substituion for Production order variance settlement

Hi,
In make to order production, Our client requirement was not to settle variances to sales order but directly to COPA.
We cannot use variance categories in settlement profile/PA transfer structure as we have transfer pricing setup and direct settlement of variances categories to COPA updates only legal view of COPA and not profit center view of COPA.
Therefore variance GL account was created as cost element in our case.
Now that client wants to settle variances to sales order for certain plants and directly to COPA in certain plants.
Therefore i tried with a CO substitution to clear sales order assignment for the variance GL and then in OKB9 i have set up PSG as default account assignment.
Now when i run the settlement, in debug mode i am able to see that the substitution works and clears the sales order assignment, but when i see the FI document posted, it still has SO assignment. No COPA document is triggered and a controlling document on sales order is posted.
Why does substitution not work for variance settlement in case of MTO process.
Regards
Raghu

Hi Ajay,
I used user exit OKC9 as suggested in SAP note 183250 (last paragraph) and SAP note 105024.
With the user exit, we have cleared the Sales order information and also called OKB9 as per the note 105024.
Now the settlement document is generated without Sales order assignment. A PSG is generated but no cost based COPA document. We also use account based copa. In controlling document, i can see PSG is updated as cost object against the variance GL.
Why does not Cost based COPA automatically generated.
We have FI settlement profile properly maintained. With a manual posting to this GL, i can see cost based copa document.
Accounting document before changes to user exit has following object
Dt 40600 Change in Stock, Prd Order
Ct 44760 Production Variance, Sales Order
Accounting document after changes to user exit has following objects
Dt 40600 Change in Stock, Prd Order
Ct 44760 Production Variance, Material & PSG
In the user exit, i have cleared the material from COBL, still it appears in the posting
Regards
Raghu
Edited by: Raghu Ram Thatavarthy on Nov 25, 2011 1:19 PM

Hi production variance

hi
help me on report
report for displaying actual start date,finish date,planned quantity,actual quantity and production variance.

Hi,
In OBYC you have to maintain gl account for production variance in PRD Transaction event key. If you want this field is to flow to COPA Then in PA Transfer structure you have to maintain allocation structure with this value field assignment.
Regards,
Sreekanth

Product Variance Calculation

Gurus,
How do we calculate Product variance?
What is the procedure / process?
Where can the effect be seen?
Edited by: Bhatia on Oct 15, 2008 6:44 PM

Hi,
Variance Calculation
As long the production order is not fully delivered or flagged Technical Complete the remaining order balance is treated as WIP. Otherwise the order balance shows up in variance calculation.
If a lot-based product-controlling WIP, is valuated at actual costs. The WIP is calculated as the difference between the debit and credit of an order as long as the order does not have the status DLV (delivered).
In lot-based product controlling the variances are not calculated until the order has the status DLV (finally delivered) or TECO (technically completed). This means that at the time the order has reached this status, the system no longer interprets the difference between the debit and the credit as work in process but as a variance. In lot-based product controlling orders never have work in process and variances at the same time.
Variance calculation compares the actual costs incurred for the production/process order with the target costs according to the standard cost estimate for the finished material, and assigns the individual variances to variance categories. The target costs are calculated using the quantity delivered for the order.
In this way you can find out which variances occurred between the value of the delivery and the actual costs and you can find the reason for the posting to the price difference account for materials with standard price control.
Variances from production (target version 1)
Variance calculation compares the actual costs incurred for the production order with the target costs for the production order and assigns the individual variances to variance categories. The target costs are calculated using the quantity delivered for the order.
This enables variance calculation to find out which variances occurred between the time the production order was created and the end of the production process.
Variances from planning (target version 2):
Variance calculation compares the planned costs for the production order with the target costs according to the standard cost estimate for the finished material, and assigns the individual variances to variance categories. The target costs are calculated using the quantity delivered for the order.
This enables variance calculation to find out which variance occurred between the time the standard cost estimate was created and the time the production order was created.
Variance categories:
The system assigns every variance to a variance category. The variance category indicates the cause of the variance (such as price change, lot-size variance). Variances are updated to the information system and passed on to Profitability Analysis according to variance category.
You differentiate between variance categories on the input side and on the output side:
u2022     Variances that occur because of goods issues, internal activity allocations, overhead and G/L account postings are displayed on the input side. Price variances, quantity variances, resource-usage variances and input variances are displayed on the input side.
u2022     Variances that occur because too little or too much of the planned order quantity were delivered, or because the delivered quantity was valuated differently are displayed on the output side.
Variances on the output side occur when you deliver using a price that differs from that found by dividing the target costs and the delivered quantity. If you deliver using the standard price, a variance can occur when the order lot size differs from the costing lot size. This is displayed as a lot-size variance.
For config
3.1.4.2     Variances & Settlement
Variance Calculation determines differences between the actual costs incurred on a production order and the standard costs of the material produced. Variances are calculated not at once, but for different variance categories. The variances computed are then transferred to CO-PA.
3.1.4.2.1     Define Default Variance Keys for Plants
Use
The Variance Key is part of the order header and controls variance calculation. The system selects the value set by this step as default value when a material master is created. From the material master the variance key then is transferred to the order when an order for the material is created.
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     OKVW
IMG Menu     Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period End Closing  Variance Calculation -> Define Default Variance Keys for Plants
2.     Make the following entries:
Plant     Variance Key
BP01     000001
BP02     000001
BP03     000001
BP0X     000001
3.1.4.2.2     Define Target Cost Versions
Use
The target cost version controls various parameters related to calculation of target costs in variance calculation. In variance calculation, target costs are needed as a comparison to the actual costs incurred.
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     OKV6
IMG Menu     Controlling Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period End Closing  Variance Calculation  Define Target Cost Versions
2.     Choose New entries and enter the following values or copy from default settings of CoArea 0001 to BP01:
CoArea     TgtCostVsn     Text     Variance Variant     Control Cost     Target Cost
BP01     0     Target Costs for Total Variances     001     Actual Costs     Current Std cost Est
BP01     1     Target costs for production variances     001     Actual Costs     Plan Costs / Preliminary Cost Estimate
BP01     2     Target costs for planning variances     001     Plan Costs     Current Std cost Est
3.1.4.2.3     Create Settlement Profile
Use
The settlement profile controls various parameters related to settlement.
Prerequisites
Allocation Structure
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     SPRO
IMG Menu     Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period-End Closing  Settlement  Create Settlement Profile
2.     Choose New Entries and enter header data. Then for each new entry choose Details and enter remaining data.
3.     Overview of data records:
Profile     Text
YGPI00      BP Process Order w/o CO-PA
YGPP00     BP Production Order w/o CO-PA
YGPI00     YGPP00
Actual costs/costs of sales
To be settled in full     X     X
Can be settled
Not for settlement
Default Values
Allocation Structure     A1     A1
Source Structure
PA Transfer Struct.
Default object Type
Indicators
100% Validation     X     X
%-Settlement     X     X
Equivalence Nou2019s     X     X
Amount Settlement
Var. to co. bsd. PA
Valid receivers
G/L account     N     N
Cost center     O     O
Order     O     O
WBS Element     O     O
Fixed asset     N     N
Material     O     O
Network     N     N
Profit. Segment     N     N
Sales order     O     O
Cost objects     O     O
Order item     O     O
Business proc.     N     N
Real est. object     N     N
Other parameters
Document type      SA     SA
Max.no.dist.rls     3     3
Residence time     3     3
You have to assign Variance Key in material master for semi-finished and Finished goods in costing 1 tab also.
To Execute
KKS1-Collective Variance calculation
KKS2-Individual Variance calculation
CO88-Collective settlement
KO88-Individual settlement
Thanks,
Rau

Business partner maintenance for Product catalog view - Problem

Hi All,
I am using the FM 'CRM_PRP_MAINTAIN' to create Business partner assignment for product catalog view.
Can anyone help me with this FM?
I am passing the following:
        gs_prp_bupa_i-ref_kind = 'B'.
        gs_prp_bupa_i-processing_mode = 'A'.
        gs_prp_bupa_i-bupa_ref_guid = gv_partner_guid.
        gs_prp_bupa_i-partner_id = gv_partner.
        APPEND gs_prp_bupa_i TO gt_prp_bupa_i.
        ls_input_fields-ref_kind = 'D'.
        ls_input_fields-objectname = 'PRP_BUPA_I'.
        ls_input-fieldname = 'BUPA_REF_GUID'.
        APPEND ls_input TO ls_input_fields-field_names.
        ls_input-fieldname = 'PARTNER_ID'.
        APPEND ls_input TO ls_input_fields-field_names.
        ls_input-fieldname = 'PROCESSING_MODE'.
        APPEND ls_input TO ls_input_fields-field_names.
        ls_input-fieldname = 'TYPE'.
        APPEND ls_input TO ls_input_fields-field_names.
        APPEND ls_input_fields TO lt_input_fields.
        CALL FUNCTION 'CRM_PRP_MAINTAIN'
          EXPORTING
            it_prp_bupa_i                   = gt_prp_bupa_i
          CHANGING
            ct_prpadm_h                     = lt_prpadm_h
            ct_prpadm_i                      = lt_prpadm_i
            ct_input_fields                   = lt_input_fields
            cv_log_handle                   = lv_log_handle
         EXCEPTIONS
           error_occurred                  = 1
           prp_locked                      = 2
           no_authority                    = 3
           status_change_not_allowed       = 4
           prp_id_already_exists           = 5
           invalid_prp_id                  = 6
           OTHERS                          = 7 .
But i don see the partner assignment working.
My doubt here is wat GUID shud b passed in the field gs_prp_bupa_i-GUID. As of now i m not passing any value here.
Please help me.
IF not this FM wat else can i use?

Hi Ganesh,
Thanks for your response.
i hope you understood my question.i have already performed all the steps which you have mentioned.Understand my query first.
I could solve that query myself.
Message was edited by: mdv sapcrm

Error while calculating variances for production order

Hi Gurus,
while calculating variances for production order i am getting the following error
"Cannot calculate scrap variances" ( Error message)
" no standard value estimate for material" (Warning message"
A standard cost estimate exists for the material at the date mentioned in the error in released status.
Please give solution for the error.
Thanks in advance n Regards
Arul.

Is there an itemization, generated for the cost estimate used to calculate the target costs?
Does the material components listed in the BOM of the cost estimate used to calculate the target costs, assigned to the operations in which they are used. Otherwise it is not possible to correctly report the variances and scrap when operations are confirmed.
Does the order for which the variances are calculated have a valid variance key. ?
Does the order have the status DLV (delivered) or TECO (technically completed). If the status was withdrawn, any variances and scrap variances are canceled.

Product Variances in COPA for SFG

Hi Freinds,
I am facing a issue relating to production variances arising from settlement of production order for SFG.
As SFG is not sold in my case and is being used for producing 2-3 types of Finished goods, therefore client wants that the production variance of SFG should be allocated to the FG's based on Sales Quantity.
However as all production variances are being settled to COPA, SFG production variannce are also coming to COPA, now I am not able to fine in COPA if there is anything to support this.
Thanks

Hi
The answer to your question is both YES & NO
It is possible to allocate SFG variances upon FG using top down distribution in COPA (KE28)... However, for that, you should have "Some thing in Common"
"Some thing in Common" means - Your SFG and FG should have a relation in SAP where by you can identify that they co-relate.. In one of our clients, we set up the system in such a way that the related SFG and FG shared the same material group...
So, while distributing in COPA (Top Down Dist), we specified that Variances Pertaining to Mat Type = HALB & Mat Group= XX should be allocated to Mat Type = FERT and Mat Group = XX...
Do you such a co-relation established in your system?
Regards
Ajay M

COPA Configuration for settlement of Production Variances

Hi,
Can anybody explain me detail configuration steps required to settle production variances to COPA in case of Make to Stock Scenario.
Helpful answers will be rewarded with points.
Regards
Milind Nair

Hi
These are broadly the requirements for settling production variances:
1.) The production variances first need to be calculated in CO-PC.
2. Your PA transfer structure must contain assignments of variance categories to COPA value fields.
3. In the settlement profile, you define the variances to be settled and profitability segments should be a valid receiver.
4. The settlement rule to profitability segments is created automatically based on the information available in the production order (product, product group, plant and so on).
5. You must have maintained number ranges for record type "C".
6. The desired form of Profitability Analysis (costing based) must be active in the relevant controlling area.
Hope this is useful
S Jayaram

Define G/L Account for Product Category and Account Assignment Category

Hello Experts,
I got a requirment to make a new entry in below SPRO path.
Define G/L Account for Product Category and Account Assignment Category
*Individual entries cannot be put into the change request*
*Message no. SV141*
*Diagnosis*
*For technical reasons, the entries cannot be fully specified in the change request. There are two possible reasons for this:*
*1. The key of an entry is longer than 120 characters. All entries whose keys match up to character 119, are then copied into the change request, rather than an individual entry.*
*2. The key of an entry contains fields of special data types, for example, packed numbers. The key can only be specified in the change request up to the first such field from the left.*
*all entries whose keys match up to character 26 are copied into the change request, rather than a single entry.*
*System Response*
*The selected entry is copied into the change request correctly, but other entries may be copied as well.*
My question is, If I make one entry and move to Quality and production system will it move only one entry or whole table will move?
Kindly help me.
Thanking you
Regards
Sharan

I got the same message trying to make an entry in SPRO:
Define Backend System for Product Category
I found the note 305942 describing exactly the issue for my and above mentioned entry, which offers the correction, then the note 326802 which offers the correction of the first notes. However, both notes are for Releases 4.6C and D (from 2000), and we are using EHP2 FOR SAP SRM 7.0.
I see another discussions in SCN regarding this topic, but haven't found real solution yet. Any hints? At least the answer to previous question from Sharan would be appreciated.
Best regards,
Toni

Defining G/L Account for product category and account assignment category

We are using the standard configuration to default in a G/L account for a given product category and account assignment category combination. This works well for us when it comes to the shopping transactions (i.e. BBPSC01, BBPSC02, etc.), however we have a problem with this logic in the carry out sourcing transction BBPSOCO01. Our users are creating describe requirements which are then delivered to BBPSOCO01, however the user is not assigning the correct product category, so the sourcing department updates the cart with the correct product category. Upon doing so, the G/L account gets changed to whatever the V_BBP_DET_ACCT table determines is correct for that given product category/account assignment combination. We would like to know if their is a way to not fire the "default G/L account determination" when the shopping cart is changed in transaction BBPSOCO01. I already know about the BBP_DETERMINE_ACCT BADI but thought there might be a less expensive alternative. Our business treats the G/L account provided by the configuration as a guideline, therefore when the buyer changes the product category they also want to retain the account assignment information. Any suggesstions on how this might be accomplished outside of creating my own logic in the BADI?
Best regards,
Shawn O'Connor

I got the same message trying to make an entry in SPRO:
Define Backend System for Product Category
I found the note 305942 describing exactly the issue for my and above mentioned entry, which offers the correction, then the note 326802 which offers the correction of the first notes. However, both notes are for Releases 4.6C and D (from 2000), and we are using EHP2 FOR SAP SRM 7.0.
I see another discussions in SCN regarding this topic, but haven't found real solution yet. Any hints? At least the answer to previous question from Sharan would be appreciated.
Best regards,
Toni

Input Quantity Variance and Input Price Variance for Production Order

Dear All
I am running variance program KKS2 for calculating variance of production order. for Activity variances are coming under input price variance and input quantity varinace but for material the variances is now shown separately for quantity and price rather it is shown as variances total amount. Can someone help me in know why material quanitty variance and price variance not shown separately
Regards

How does input variance and output varia.nce will be calculated on the settlement of production order after TECO.
VARIANCE CALCULATION DEPENDS ON CONFIGURATION IN THE FOLLOWING AREAS,
1) VARIANCE VARIANT - DETERMINES WHAT VAREIANCE CATEGORIES ARE CALCULATED, E.G MATERIAL PRICE , USAGE, LABOUR RATE , USAGE VARIANCE ETC..
2) TARGET COST VERSIONS
3) VALUATION VARIANT FOR WIP AND SCRAP
Can we check in KOB3 or COOIS.
KOB3 - YES
COOIS - CHECK IN COST REPORT

Print indicator assigned to the MM movement type 101 F ( GR for Production Order )

Hello!
I'd like to know how to assign a print indicator to the movement type GR for Production Order 101_F
When I use the IMG path : Material management/ Inventory Management and Physical Inventory/ Print Control/ Maintain Print Indicator for Goods Receipt Document, I can only assign the movement type 101 (Goods receipt) but not the movement 101_F.
Thank you for your help!
Charlotte

Hello Dev!
The movement 101 F is Goods Receipt for Production Order. The letter "F" corresponds to the movement indicator.
I'd like to dissociate the movements types 101 and 101_F to have only one printed label.
Regards,
Charlotte

Variance calculation for production order with settlement receiver as SDI

Hi...
I have one query reference to Variance calculation for production order with settlement receiver as SDI(Sales document item).
I am working on Varaint configuration with strategy 25(Make-to-order for configurable material) with requirement class 046.
I have created sales order ref. to configurable material,subsequently created planned order & then converted to production order.
In production order settlement receiver is SDI(Sales document item).
While doing production confirmation ,variance has been created.
Now during variance calculation KKS2, I have got error message as no suitable settlement rule found for object Order no.
Is there any way to come out of this?Or variance calculation KKS2 is not applicable with settlement receiver as SDI(Sales document item).
Pl. guide
Redards
Tushar

Hi
In case of non valuated material, concept of variance does not apply...
Variance is Actual Cost - Cost of Goods receipt posted in stock.. If the later value is zero, your entire actual cost is variance... That is one way of saying it
But, in SAP, var not calculated in case of non valuated material and that makes sense as well.. Since you are in MTO scenario, it would make sense to analyse costs vs revenues @ sale order level as each SO will be unique in itself
Regards
Ajay M

Variance calculation for production order

Hello,
I am clarifying what's the selection criteria for settled production orders so that we can carry out the following
close and deletion flag activities.
I am currently in release ECC605. Need to carify the below questions.
1. For production order without header material (dismantle production order), no need to do variance calculation before
settlement,right? Because I found system will respond green light but "no order was processed", this kind of production order
won't possess "VCAL variance calcaulted" system status.
2. For all production orders created with header material, vairance calculation is a must, even the variance is 0.
So the production orders will possess "VCAL" status after variance calculation transaction is done.
Thanks for your help in advance.
B. Regards,
Nancy

How does input variance and output varia.nce will be calculated on the settlement of production order after TECO.
VARIANCE CALCULATION DEPENDS ON CONFIGURATION IN THE FOLLOWING AREAS,
1) VARIANCE VARIANT - DETERMINES WHAT VAREIANCE CATEGORIES ARE CALCULATED, E.G MATERIAL PRICE , USAGE, LABOUR RATE , USAGE VARIANCE ETC..
2) TARGET COST VERSIONS
3) VALUATION VARIANT FOR WIP AND SCRAP
Can we check in KOB3 or COOIS.
KOB3 - YES
COOIS - CHECK IN COST REPORT

Transfering Production variances to COPA

Hi,
I have doubts about transferring Production variances to COPA.
Will this functionality work both for settlement of variances to GL Variances Account and at the same time for settlement of variances to COPA?
From my experience with cost centers and internal orders, I know that if I want to settle an Internal order both to COPA char and to GL Account, I have to make 100% overhead for the costs gathered on IO. Then I can do the settlement in both directions.
Could you please explain to me the case of Production order variances settlement? I need to have them both on GL accounts and in COPA.
Best wishes,
Karol

Hi
At the time of settlement of production orders, FI entry also passed as well as variances are also settled to COPA
In FI, variances will be debited (assuming production order debit is more than what it is settled to Inventory at Std cost) and Inventory changes account is credited.
In COPA, depending on the variance categories like Price, qty and their assignment to value fields, this amount is transferred.
For eg, if prodn order actual costs is say 12000 and is settled to Inventory is 10000 (at std cost), and the difference is 2000 and if this difference is due to Price (800) and qty (1200).
Hope this is useful
S Jayaram

GL assignment for production variance

Similar Messages

Maybe you are looking for