Error in Closing of Production Order

Dear Gurus,
I am getting following error whil closing Production order
"Unprocessed Future change Recs for order ### prevent deletion flag /completion "
Can anybudy explain me what is this ?
Ishwar

Hi,
Please check the following
Prerequisites for Setting the Deletion Flag
The following prerequisites must be fulfilled before a deletion flag can be set:
Are there any more (manually added) purchase requisitions or purchase orders assigned to this order?
If so, these must be deleted first.
Is there a balance for this order?
The deletion flag can only be activated if the order has already been settled or if no actual costs have been accrued in the order. This means that the actual costs for the order must be equal to zero.
Are there any commitments for this order?
If so, these must be deleted first.
Are there any inspection lots in this order?
If so, each lot must have the Completion of all inspections is set and the Usage decision made status.
Are there any goods movements with errors for this order?
If so, these must be processed first.
Regards
Kannan

Similar Messages

Error while Closing the Production order.

Hi ,
We are doing operation Subcontracting Process. This process works on the basis of Production order, once the Production order generated automatically system generates a Purchase requisition which we are converting to Purchase order and doing the sub contracting process.
Now i have received all the material from the Subcontractor ( GRN and MIRO ) has been completed , for the Production order all the confimration and Delivery has also been completed , now i have done Technically completion for that order , now i am closing the Order ( Functions -Restrict processing - close ) , while closing it gives me an error saying that Purchase order still exists .
Wat is this error ?? why is it coming so ??
Regards
Rajesh

hi,
You have to ensure that the order is not having any WIP, if you have any WIP for that order you have to complete the order and then only you could abale to clsoe the order.
Check the WIP for the order thorugh KKAX.
Regards,
Rama Mohan

Error while closing a production order

Hi
I have raised a production order for 10 products.I have a confirmed yeild of 11 products.I have a overdue tolerance of 10% for that semi finished good.Even then it is not allowing to TECO the order.Why
regards,
PradeepM.

Actual problem in my case is like
1. there are 4 operations in the semi finished good that is produced
2.In first operation some products are produced in extra then actually required
3.In second operation the extra quantity produced is scrapped
4.The final quantity confirmed for the required product is same as the ordered quantiy
Even then it is showing an error message GR quantity is more than confirmed quantity when trying to TECO the order.
how to correct this error
regards,
PradeepM.

Serial number error while creating the production order

Hello frds,
I am getting the following error while creating the production order.
"Item 000000 requires exactly 100 serial numbers for the asset".
If i give 100 serial numbers in the order, the error is solved. But i do not want to assign 100 serial numbers, i want to assign only 2 numbers.
I have tried using the new serial number profile also, but it is giving same error.
Kindly guide.
Regards,
Narendra Bora

Dear Narendra
Select the serial number profile and go to serialization procedure and set the ser. usage status 02 - Optional as below.
Procd Procedure description Ser.Usage
PPRL PP order release 02
since the serail number creation is optional for order relase this will allow you to relase with out error and with serail number assigned in partial.
Regards
Soundar

Error While saving the Production Order

Dear Experts
Pls let me know why am getting the below error while saving the production order after release..
PSFC_STD_LAYOUT does not exist
Message no. SSFCOMPOSER004

Dear,
Please check have you assigned the scheduling profile in work scheduling view of materail master?
Then go to OPKP check the same scheduling profile where you have activited the On realese execute printing remove this tick mark and then try with new order.
Or you can do the configuration in Tocde :OPK8 here assign the PSFC_STD_LAYOUT in forum.
Regards,
R.Brahmankar

Allocation error when I create production order

Hi guys:
I met allocation error when I created production order with CO01.could you help me out?urgent!

hi
What is the excatly the error so that we can tell u the reason
regards
ramakant

Error during release of production order - AFS Specific

Hi SAP gurus,
Iam getting error during release of production order in AFS specific system during COHV transaction. Error is ''Error calling ATP server'' and message no is AG022. But when we read the PP master data then this error is cleared and production order is released.
Thanks & Regards,
N. Laxman

hi
1. When mass conversion of AFS planned order to production order is performed via COHV, the resulting production order does not contain the SKU details of the component.
2. When a planned order is converted to a production order & an ATP is carried out on the production order, Message no.AG022 - 'An error occurred during Remote Function call on the ATP Server' is issued by the system.
so you need to use the note 1087613.
read the note and apply with the help of technical team ABAP and BASIS
-ashok

Error -10 while closing a Production Order with DI API

Hi,
I've been trying to close some production orders using this code:
Dim oProdOrder As SAPbobsCOM.ProductionOrders
        Try
            oProdOrder = Me.Company.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oProductionOrders)
            If oProdOrder.GetByKey(intDocEntry) Then
                oProdOrder.ProductionOrderStatus = SAPbobsCOM.BoProductionOrderStatusEnum.boposClosed
                If oProdOrder.Update <> 0 Then
                    Me.Company.GetLastError(intError, sErrMsg)
                    If (0 <> intError) Then
                        sErrorMsg = sErrorMsg & "Production Order Close Error: " & CStr(intError) & "," & sErrMsg & _
                            ". DocEntry: " & oProdOrder.ProductionOrderOriginEntry & vbCrLf
                    End If
                End If
            End If
...But I keep getting the same error every time I try: -10,Date out of reference date range, '_SYS00000005340'
The error doesn't show when I close the Order with BO's Form. And I've checked the exchange rate for the posting and due date of the document (and also for my current date) and there seems to be no problem with it.
I'm currently working with SAP BO 2004A PL 45.
Anybody has a suggestion? a workaround?
I'll appreciate any help you can give me.
Thanks in advance...
Alfredo

Alfredo,
just in case,
what is the previous state of the production order (planned, released,...)?
before you try to close the order, update the status to released:
If oProdOrder.GetByKey(newID) Then
'Cambio di stato dell'ordine da 'Planned' a 'Released'
                oProdOrder.ProductionOrderStatus = boposReleased
oProdOrder.Update
I found this code in a DI API application written for 2004A. It was commented out so I suspect it didn't work.
'Chiusura dell 'ordine
        'SelProductionOrder.ProductionOrderStatus = boposClosed
        'ret = SelProductionOrder.Update
        'If ret <> 0 Then
        '    sboCompany.GetLastError nErr, errMsg
        '    MsgBox "Errore " & nErr & " - " & errMsg
        'End If
Hope this helps

How to avoid actual cost error log while confirm production order activity

Hi
I dont want to post actual activity cost via production order activity confirmation. But i want standard value keys for my production duration purpose. So,i defined activites(strd value key) in work center without assigning cost center to that work center. While i confirm in CO11N, system throws erro log as Actual cost calculation contain errors and allows me to confirm the activities. I am doing MB31 and all CO settlement activities also. But when i try to close the order it says error log exists,so closing of order is not possible. How to overcome this problem as i dont want to capture any cost of activites via production order,but i want confirmation only for production analysis.

Hi
Issue is resolved thru PP forum. Thanks for ur reply.
Solution lies in Control key of routing and BOM costing relevancy.

How to avoid Cost error log while confirming production order

Hi
I dont want to post actual activity cost via production order activity confirmation. But i want standard value keys for my production duration purpose. So,i defined activites(strd value key) in work center without assigning cost center to that work center. While i confirm system throws erro log as Actual cost calculation contain errors and allows me to confirm the activities. I am doing MB31 and all CO settlement activities also. But when i try to close the order it says error log exists,so closing of order is not possible. How to overcome this problem as i dont want to capture any cost of activites via production order,but i want confirmation only for production analysis.

Sudhar,
You can make the operation not relevant for Costing by using a Customized Control key which is not relevant for Costing or else in the operation details you need to leave the "Costing relevancy" field blank.
Regards,
Prasobh

Co- Product Error while creating a production order

Hi,
While performing the Co-Products Approtionment at the time of creation of Production order..
we are facing a problem regarding cost apportionment I have crated a Source Structure and the cost element is assigned to that Source Structure but still iam facing this issue
kindly help me out.
the error msg is
Debit with cost element 9460404 cannot be settled.
Message no. KD549
Diagnosis
Costs/revenues exist for cost/revenue element 9460404. This cost/revenue element was given source assignment 40 in the source structure (-> settlement rule for sender -> parameters). However, there is no distribution rule with settlement type FUL for this source assignment or the total of the percentages for the rules is less than 100.
Note:
Full settlement settles all the costs and revenues which have occurred up to the settlement period and have not already been settled. In the case of periodic settlement, you can configure the settlement profile so that all the costs occurring in the settlement period are settled, or if an amount less than 100% can be settled.
Procedure
Maintain the distribution rules for source assignment 40 and settlement type FUL or use periodic settlement to settle less than 100%. Change the settlement profile for the sender as necessary.
Change settlement profile
Note:
Cost and revenue elements receive source assignment " " if you have not entered a source structure in the settlement rule parameters.

Hi Krishna Murthy I went through the note but i couldnt recive a big help from that note.
I will explain the step by step process that i have done.
I am attaching the Screen shots of the issue.
1. For co-products I have created a source structure and Sec. Cost Elements were assigned in the source structure.
2. The source structure was assigned in the Material Master for co-products equally distrubuting the amount between 2 materials.
3. When we are trying to create a production order the error was displayed but the costs was getting calculated properly.
4. When I was settling the production order the same error was getting displayed.
I have tried various methods to resolve it.
1. I have created a periodic settlement rule and tried to settle but it didnt work
2. I have assigned the source structure in the settlement profile this also didnt work.

Error while creating a production order

Dear PP gurus
I am trying to create a production order of a material through CO01 , I am getting a error 05.05.2016 date comes after end of valid factory calendar. (Please correct
Although for all other material , no error is coming.
My factory calender is till 2015, but i am not able to understand why and how it is capturing the above date.
please help me how to correct it?
Thanks in advance
Regards

Dear Aadi,
When your in operations screen
Extras > Scheduling > Schedule > operation overview = operation segments > Click on Gang chat icon
it should show you the days for ur base qty
then click on scheduling results then click on update material master & save
then Go to CA96
input plant
then mark a tick for ur material & click on update material master icon
then check in material master work scheduling view
Regards
Madhu

Error message while creating production order with KMAT material strategy25

Hi PP Gurus I am running variant configuration cycle...Strategy 25, Custermer Req KEK (KMAT Matrl)
Sales order & MRP Picked the components correctly as per the dependencies
written. So Planned order generated against sale order.
When I tried to convert planned order to Production order...I am getting the
below error message..
Error Message:
You cannot make an assignment to make-to-order stock Message no. CO684
Diagnosis The component cannot be allocated to an individual stock because
make-to-order production and engineer-to-order production cannot be executed
with this order.
A possible cause is that you are trying to create an order with reference to a
sales-order/project, where an account assignment to a sales order/project is not
allowed in the settlement profile that is assigned to the chosen order type.
This is inconsistant.
System response The following responses are possible:
Order processing is cancelled.
The system resets the special stock indicator back to the original value.
Procedure Choose another order type.
I used order type with SD1 as settelement profile.
OVZG: default 046, settlement profile = SD1
OPJH: Settlement profile = SD1
Plz through some light on this if u have worked on Variant Configuration/MTO
settlements.
Question:
1) Is creation of production order with KMAT material supported by SAP?
2) If yes, why the above error occurs?
Waiting for Ur reply
With Best Regards

Dear R.Brahmankar,
I have check on the note, but it is not relevant to ecc6. The current system default setting is :
Standrad setting for reqt class 046
Special Stock E
Acct Assgt Cat. M
Valuation M
Settlmt Profile SD1
However if I change the Acct Assgt Cat. from M to E. It resolve the problem. I would like to know is this the right solution?
Config in Acct Assgt M
Consumption Posting = E
Config in Acct Assgt E
Consumption Posting = ' '
In F1 key of Consumption Posting field it shown following:
To flag the sales order item as cost- and revenue-carrying, enter an "E" (settlement via sales order).
If you do not wish to flag the sales order item as cost- and revenue-carrying, do not enter anything.
Dependencies
If you are working with nonvaluated sales order stock, always flag the sales order item as cost- and revenue-carrying.
If you are working with valuated sales order stock:
In the case of complex make-to-order production, flag the sales order item as cost- and revenue-carrying
In the case of sales-order-related mass production, do not flag the sales order item as cost- and revenue-carrying
Should we change to E?
Regards,
Ong

Run time error while closing the CRM Order using BAPI

Hi Experts,
Need your invaluable suggestions here.Apologies for the lengthy mail, intention is to give clear idea of the issue.
I am facing an issue while closing the CRM orders. According to our business process, when an issue is solved we will keep the order in resolved status only. We will not directly close the order from the CRM tool, instead we have created a custom program for the same purpose.
For the custom program we will give input as the order number and execute it, this will close the order.
Here close the order means assigning it to Close status as well assign the reason code.
We have created some reason codes for closed status.
So when the program is run the Order moves from resolved status to closed status along with reason code.
But of late we are facing some problems with this program, it is giving run time error for some CRM orders.
Run time error message : The ABAP/4 Open SQL array insert results in duplicate database records.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "CRM_SERVICE_OS_UPD_OST_DU" "(FUNCTION)", nor was it propagated by a RAISING clause.
Please find my code which have used in the custom program
Closing the resolved SOs in the system
    CALL FUNCTION 'CRM_STATUS_CHANGE_EXTERN_OW'
        EXPORTING
          objnr                     = iv_guid
          user_status          = lc_status_closed
       EXCEPTIONS
         object_not_found          = 1
         status_inconsistent       = 2
         status_not_allowed       = 3
         OTHERS                        = 4.
    IF sy-subrc <> 0.
      WRITE : 'Error at maintaining status'.
    ENDIF.
Set reason code
build lt_subject
    ls_subject-ref_guid = iv_guid.
    ls_subject-katalogart = 'A2'.
    ls_subject-codegruppe = 'ZR000003'.
    ls_subject-code       = 'ZR33'.                      " Reason code
    ls_subject-mode       = 'A'.
    APPEND ls_subject TO lt_subject.
build lt_ossset
    ls_osset-ref_guid        = iv_guid.
    ls_osset-subject_profile = 'ZREASON03'.
    ls_osset-profile_type    = 'G'.
    ls_osset-subject         = lt_subject.
    APPEND ls_osset TO lt_osset.
build lt_service_os
    ls_service_os-ref_guid = iv_guid.
    ls_service_os-ref_kind = 'A'.
    ls_service_os-osset     = lt_osset.
    APPEND ls_service_os TO lt_service_os.
build lt_input_fields
    REFRESH: lt_input_fields, lt_field_names.
    CLEAR : ls_input_fields, ls_field_names.
    ls_field_names-fieldname    = 'CODE'.
    APPEND ls_field_names TO lt_field_names.
    ls_field_names-fieldname    = 'CODEGRUPPE'.
    APPEND ls_field_names TO lt_field_names.
    ls_field_names-fieldname    = 'KATALOGART'.
    APPEND ls_field_names TO lt_field_names.
    ls_field_names-fieldname    = 'SERVICE_PROFILE'.
    APPEND ls_field_names TO lt_field_names.
    ls_input_fields-ref_guid    = iv_guid.
    ls_input_fields-ref_kind    = 'A'.
    ls_input_fields-objectname = 'SERVICE_OS'.
    ls_input_fields-field_names = lt_field_names.
    APPEND ls_input_fields TO lt_input_fields.
     CALL FUNCTION 'CRM_ORDER_MAINTAIN'
      EXPORTING
        it_service_os     = lt_service_os
      CHANGING
        ct_input_fields   = lt_input_fields
      EXCEPTIONS
        error_occurred    = 1
        document_locked   = 2
        no_change_allowed = 3
        no_authority      = 4
        OTHERS            = 5.
    IF sy-subrc <> 0.
      WRITE : 'Error at maintaining reason'.
    ENDIF.
    CALL FUNCTION 'CRM_ORDER_SAVE'
      EXPORTING
        it_objects_to_save   = lt_header_guid
        iv_update_task_local = lv_update_task_local
      IMPORTING
        et_saved_objects     = lt_saved_objects
      EXCEPTIONS
        document_not_saved   = 1
        OTHERS               = 2.
    IF sy-subrc <> 0.
      WRITE : 'Error at saving'.
    ELSE.
      WRITE : 'Successfully Closed'.
      COMMIT WORK AND WAIT.
    ENDIF.
Run time error is coming at COMMIT WORK AND WAIT statement.
Please let me know any corrections are required in the above program.
When I analyzed the run time error I have found that it trying to insert the record in CRMD_SRV_OSSET for that CRM order, but already one record is present in the table for the same CRM order number.
For most of the CRM orders there is no entry in this table so they are closing successfully but for a few orders for which there is an entry we are getting the above run time error.
There is nothing wrong with the orders which have an entry already in the table CRMD_SRV_OSSET, I need to close these kind of orders with out run time error.
Kindly provide your feedback.

Hi Dinakar,
You posted this in APO PPDS forum. This question should go to PP forum where someone could answer it.
Please close this thread and open a new thread in PP forum so that you could get help quickly from the relevant experts.
Regards - Pawan

Error while release of production order u201CNext period is not openu201D

Hi Experts,
Need your opinions on this issue where my client is facing a problem while create and release a production Order on the last day of the month (Last day of period change).
While create and release of production order for Plant xxxx, system uses to give the error; period Next (e.g. 12) is not open. Same thing if I have created the order using T. code CO01; but when I tried to release and save the order through T. code CO02 then it gave me the same error (Next period is not Open), it checks for the next period to open.
The above scenario happens only on last day of the month. Earlier this kind of error was not there so the question is why the period check is happening while saving the production order.
After speaking to the user, it is determined that they are facing this problem since upgrade (Since last 8 month). Hence need to check what additional check has been implemented with upgrade from R/3 4.7 to ECC 6.
Error Message No F5201
Appreciate your help how to dig up this issue.
With Regards
Anant

Hi Guys,
Please throw some light why on the last day of the month (Last day of period change) at the time of release the order user is getting error: Period Next (FI Next period) is not open ( message No. F5201).
My question is why system carried out period checks at the time of release of Production Order.
With Regards
Anant

Error in Closing of Production Order

Similar Messages

Maybe you are looking for