Post implementation COPA Issue - Variances not setteled for process orders

Hi Experts,
The client implemented COPA in the FY 2011. There were many process orders existing in the system prior to implementation of COPA. Now the client trying to archive the old process order and trying to set deletion flag and system throwing error message u2018variances were not calculated fullyu2019.
But client saying orders were settled and no variances existing prior to COPA implementation.
My queries are:
1. The orders are created prior to COPA Implementation and they were settled as well long back. After COPA implementation why system calculating variances once again.
2. How can I check whether the variances got settled for the process order? Please give me the report or transaction code?
3. Can I settle the variances to COPA Transfer structure now for the orders which were created before COPA Implementation and what will be the impact?
Regards
Sri laxmi

Hi Sri,
It should be settle the process orders before COPA implementations and find below my answers point by point.
1.System will not calculate again variance, once you settle the process orders, you can close the orders, so it will improve the system efficiency and system will those orders in future to calculate the variances.
2.are u try to close the order, if it is settle the order, system will allow to close the order or vice-versa.(T.code-ask PP consultants).
3.i have mentioned clearly, previous reply,it should not be open orders.
please let me know any further information is required.
thanks and regards
nagaraju sami

Similar Messages

WIP status (RESA) not updated for process order with co-product

Hi,
We are facing the scenario below, please confirm whether item 2 behaviour is standard SAP.
1. Process order with settlement rule MAT - after WIP calculated, status RESA is updated & FI document it posted.
2. Process order with settlement rule OIT (co-product) - after WIP calculated, status RESA not updated & FI document posted.
Thank you.

Self found answer

GR Cost not updating as Target Cost for process orders

Dear SAPians,
We are facing an issue in Target Vs Actual cost reporting for process orders. We are creating a process order after cost estimate of that material and doing the confirmations for activity cost. After that, GR has been done for the finished goods of that process order. That GR entry is updating the Actuals values but not updating the Target cost. When I am checking the standard report KKBC_ORD, I am getting the following figures.
Cost Elemnt Text     |     Target Cost     |     Actual Cost     |     Target Vs Act
Inventory Chnge FG     |     0     |     1,472,205.60-     |     1,472,205.60-
Packing Matrl Cons.     |     1,148,142.37     |     1,252,752.68     |     104,610.31
Raw Material Cons.     |     60,463.91     |     50,688.29     |     224.38
Semi-Fin Matrl Cns.     |     181,934.68     |     367,959.56     |     186,024.88
Labour Cost Activity     |     39,735.36     |     39,862.80     |     127.44
Machine Cst Activty     |     41,611.75     |     43,153.01     |     1,541.26
That 'Inventory Change FG' entry is showing the GR posting updating actuals and not target cost. This is causing huge difference in target vs actual cost that will affect the profit and loss figures ultimately.
What am I missing here? What should I do to update the GR amount in Target cost as well.
Shirazi

Dear,
Target Cost on Production Order or Process Order is shown only when Variance is Calculated.
So please calculate the Variance, system will show the Total Target Cost.
Br,Vivek

Archieve does not exist for purchase order

Hello Gururs,
When i tried to change the delivery date for the PO and when i trying to save the PO
then it throws the error messages-'Archieve does not exist for purchase order'.
PO was created in feb.
Please help me how can i solve this issue.
BR
Ashish

Can you give a more detailed information.
What transaction you actually use, what you enter step by step until you get to the error: 'Archieve does not exist for purchase order'
This message sounds like you want change a PO which is already archived.
A change to an archived PO is not really logical, as you can only archive closed business cases. and if the business case is closed, then why would you change the delivery date.
A PO from February should not really be archived already in June. I never saw it in practice, as you could not do any anual reporting
I would assume further that SAP found the entered PO number in the archive index but did not find the way to the archive itself. This can happen if the archive file was deleted or moved manually.
I am not sure if the next messae has really anything to do with your purchase order, thats why I ask you to post the exact steps until the messages come up:
Le fichier archieve 000524-002SD_COND n'existe pas is the message discription
But even this message explains more or less the same, that the physical archive is no longer in the same place where it is expected to be found according to the info in records of table ADMI_FILES.

Slipknots All Hope Is Gone album not avaliable for pre order in Australia

I have recently gone onto the iTunes store to pre order the new Slipknot album All Hope Is Gone. I was dissapointed to find that it was not avaliable for pre order in the Australian iTunes store. Does anyone know if it will become avaliable for pre order before its release or can i pre order it from the American store?

Does anyone know if it will become avaliable for pre order before its release or can i pre order it from the American store?
I doubt anyone here will know before such time as Apple posts it on the iTunes Store, should that occur. Apple is often unable to negotiate rights to pre-release content on all countries, so it may well not be avaiable for pre-purchase.
As to ordering from the US iTunes Store, no, you can't, not unless you have a US credit card (issued in the US and with a billing address there).

Issues during Component Batch Determination for Process Orders

Hi,
I am encountering a strange issue during component batch determination of process order.
1. During creation of process order, when I execute batch determination, systems does determination based on strategies we have set and when I click on Copy it gives an error
"Log cannot be saved: Object/subobject not specified"
Message no. BL201
*Diagnosis
Log save cancelled because at least one log contains no object or subobject.
Object and subobject are needed to classify application logs because there are several log types. Only a few logs are managed in main memory at runtime, so this classification is not needed.
If the logs are to be saved in the database, object/subobject must be specified for later retrieval.
Procedure for System Administration
Object/sub object can be passed when a log is created (function module BAL_LOG_CREATE) and changed with BAL_LOG_CHANGE.
The possible values for object and sub object must be configured in transaction SLG0.*
If I save the order with CRTD status and come back again in change mode and do determination, It works fine.
Again when the order is in REL status and do the determination, It gives the same error.
This happens only for a specific plant, In other plants batch determination works in all scenarios.
I checked for all plant related Config for batch determination and coudn't find any discrepancies.
Please advise how to resolve this issue. Thanks in advance for your help
Regards,
Aheesh

There Is no direct solution for your requirement just try this work around.
While defining the batch determination search strategy for process order in COB1, there is one column Quantity proposal where you can attach the Routines (This is written in ABAB code ) make use of this, define New Routines with ABAB help to fulfill your requirement. Try this if found useful award full points.
Regards,
Ajay Nikte

There's an error while delivery note creation for STO order

There's an error while delivery note creation for STO order even stock available in unrestricted stock
Edited by: sharma aman on Nov 8, 2011 9:00 AM

Dear Sharma Aman,
Check whether the following link helps you.
Mesaage : while creation of delivery : An item with no delivery quantity .)
Please search in google with the error message and definitely you will get some older posts in SDN which is solved.
In that case , you need not wait for the solution as it is already available.
If the solution provided do not suit you, then post it in SDN so that it will be a learning for others.
Try to search in the forum or in google before posting further queries
Thanks & Regards,
Hegal K Charles

Issue during CO43 for Process Orders

Dear SAP Experts,
I have a scenario where in Process Order is created in COR1, after that in COR2 i entered the qty then i did the confirmation for process order, now MIGO is done till now everything look fine with no errors.
But now when i do CO43 for this Order in the result screen no data is displayed.
Kindly advice.

Hi All
Try to check if the confirmation was really posted (KOB1 check production and consumption).
Sometimes the production/consumption posting is waiting for correction in transaction COFC/COGI.
If it´s OK, try to review your costing sheet for overhead.
In CO43, go to Extras - Settings and review the rules. Maybe this order doesnot fits the rule to calculate overhead.
Be sure you are not running again by mistake.
Regards.

Defaulting Rules Not Working for Repair Orders in OM?

Hi,
Defaulting Rules have been setup for return line & standard line based on few conditions and it is working fine if we create a sales order directly from OM (Manual SO)?
But in our project we are using Depot Repair(Repair Orders), we tried to create a service request and then converted to a sales order here defaulting rules not working for repair orders?
Please help me to solve this issue ASAP.
Thanks,
Kishor

Hi,
You have like this:
1. Price list
2.OE_DEFAULT_PVT.Get_SOB_Currency_Code
You have to make
1. XXOE_DEFAULT_PVT.custom_code
2. Price list
3.OE_DEFAULT_PVT.Get_SOB_Currency_Code
Did you made own custom code to pick currency?
Regards,
Luko

MIGO is not possible for refurbishment order

I have generated a Purchase requisition for a non stock material through refurbishment order(PM04) Plant Maintenance. Later PR is converted into PO further we are unable to do MIGO as it is giving a error "MIGO is not possible for refurbishment order". Plz help me in solving this issue.
Guruprasad.KS

Dear Guru
U can do the goods receipt against the Refurbish order like others. What ever u are created the PR thro PM it is Non stock as a standard.
After goods receipt this will go to order thro 101 movement (with out enetring into inventory at stores) . It means that directly consumed at order level.
There is no possible at facing the error at migo level. check your movement types 101 only
Thenna

BAPI_NETWORK_COMP_ADD     Component assignment not intended for sales order

Dear,
I have problem when I use the function:
CALL FUNCTION 'BAPI_NETWORK_COMP_ADD'
    EXPORTING
      number           = number
    IMPORTING
      return           = return
    TABLES
      i_components_add = i_components_add
      e_message_table = e_message_table.
I have inserted only these values in the structure i_components_add:
ACTIVITY_TYPE_PUR_RESV__ITEM_NR____MATERIAL_________PLANT___ENTRY_QTY___ITEM_CAT
108--8101TAH052000110025.460--
L
108--8204RAVBLA098SL0111002.000--
L
108--83034R000000011004.160--
L
but the result is wrong
e_message_table:
METHOD--C--
32
OBJECT_TYPE--C--
32
INTERNAL_OBJECT_ID---C--
90
EXTERNAL_OBJECT_ID--C90-----0108 0010 1TAH052000 1100
MESSAGE_ID--C20-----CNIF_MAT
MESSAGE_NUMBER--C3--
1
MESSAGE_TYPE--C1--
E
MESSAGE_TEXT--C72--
Component assignment not intended for sales order or project stock
Very kind for one answer of yours to this problem...
Thanks & Regards,
Marco Echino.
Edited by: Marco Echino on Sep 8, 2011 12:16 PM

Hi Marco,
I believe this is a Functional Issue rather than a Technical one. If you could speak to the Functional Concultant or pass this data via manual transaction, you will get the error details.
It's just that the data passed to the BAPI is either incorrect or incomplete. You can also refer the Function Module Documentation for tips.
Regards,
Pranav.

Scheduling parameters are not defined for production orders

Hi All,
when i convert the planned order to production order i got this massage popup coming Scheduling parameters are not defined for production orders . please let me know this .

Hi,
One of major customization steps for the order type is missing. Run OPU3 and maintain settings for the order type you are using. You may copy settings from an older type.
Regards.

Scheduled finish date for process orders not updating in BW

We are having problems with the scheduled finish date (GLTRS) for process orders. When the process order is already released, changes done in R/3 on the scheduled finish date will not result to a delta hence data in BW is not updated. Table AFKO, where data is coming from, is always updated with the changes though. 2LIS_04_P_MATNR is used in extracting the data.
Has anyone experienced the same problem? We are looking for possible ways on how to have a delta whenever there are changes on the process order even after it is already released.
Any help would be greatly appreciated...

Hi Donna,
If I've understood your problem correctly, you can increase the load frequency as Sriee has pointed out.
If you want latest data frequently and if you are on BI 7.0 then you can look at Real Time Data Acquisition(RDA)
Regards,
Tom.

Idoc not defined for processing

i am using we19 the idoc try to create an idoc ekseks01 to be send to port internal which points to application server d:\idocs
i get the following
pattern idoc written to database
not defined for processing
what does this mean

Hi,
This error occurs when an idoc is created and is written to the database, but there are errors which prevents from further processing.
Check your partner profile, process code and atlast go to we02 and watch your last status record.
Regards

User Status Profile for Process Order Operations

Hello Experts.
I have a need to set up a User Status at the Process Order Operation level that will prevent operation confirmation when the status is Active .
I have been successful at the following:
   --- Created a new Status Profile (transaction BS02),
   --- Creating a u201CHoldu201D status,
   --- Defined the Influence on Business Transactions,
   --- Set the allowed Object Types for the profile.
   --- In an individual Process Order operation, I can now select the Status Profile, and set the Hold status, and it functions correctly.
My problem is that I canu2019t figure out how to set my new profile as a default for Process Order Operations. For Production Orders, this is done in the IMG definition for the Order Type (transaction OPJH), updating field T003O-VRG_STSMA. However the Order Type definition for Process orders (transaction CORN) only has a field for a status profile at the header level. Iu2019ve searched through Configuration and the Recipe, and the Production Version, and the Control Key, but can find no where to set the default status profile for a Process Order Operation..
As a final desperate act, I manually edited a T003O record for a Process Order Type in our test system, but even this failed to set a default Operation Status Profile for subsequently created Process Orders.
If you have any knowledge about this, then please help.

As of this date, we have still not implemented a fix, but I did get some information from someone else who has.
I'll post his information here for all to see. Hope you find it helpful.
From: Joe
Yes we managed to do it.
After several false starts and CMOD/projects which suffered because only the default keys (for order number, aufpl etc) were in place and not the actual, we coded up the IN_UPDATE method in the WORKORDER_UPDATE badi. This gives us the final format after the DB save (but before the commit). The update of the STATUS using the SAP std function module was actioned successfully but the status profile was not actually passed through. We assumed that this was because of the update task - so we introduced an INSERT into JSTO instead (a bit naughty I know, but desperate needs etc). If you require anything more let me know.
Best Regards
Joe

Post implementation COPA Issue - Variances not setteled for process orders

Similar Messages

Maybe you are looking for