Problem in TECOing/Closing the process order.

Hi PP Gurus,
We're facing a problem when trying to TECO the process order and system is generating the error message
Message no. BS013 (System status CRCR is active (ORD 1000xxxxxx))
We're using Browser based PI sheet here to process the order.
If anybody faced the same, please reply.
Regards,
Abu Arbab

Hi Rupesh,
Thanks for reply
Though we set 'Clear Reservation' in intial screen of COR6N/CORK/CO15/Co11N, it'll wok only for those components which are having Backflush indicator set. As in PI sheet, Goods Issues section is completely different and Ticket confirmation is different. And the components that we're using are not backflushed components, so it makes no sense though we put Clear Reservation in confirmation through PI sheet.
Now the actual issue comes into picture when in Goods Issue table we put Issue indicator= final and it is properly updated for that component in MSEG table. But when we go and check in RESB table or COR3/COR2 there is no final indicator set in Component detail. Is this standard behavior of SAP or are we missing something here?
Please help
Regards,
Abu Arbab

Similar Messages

TECO the process order

Why do we need to discard the control recipe in order to set the process order to TECO.
Is it possible to TECO the process material even the status is CRCR or control recipe created?

Hi Ellen
Yeah you need to make system status CRFI , do with follwing steps
Transaction CO57, to trigger manually a process message with message Category PI_CRST for the process order and Control reciepe combination.
Then use Transaction CO54 to send the Message to the process order.
Pls reward if it is closed
Thanks
Bala

Problem of Missing parts during the Process Order release

Hi
For a Make to Order strategy, I have run MRP for a sales order which resulted in planned order for the material. But when I try to convert the Planned Order to Process Order, I am getting error Parts are missing during the availabilty check even though the components are available in the stock.
But when I create a Process Order manually, I am not facing the problem of missing parts as stock for components are available in stock.
Please advice why I am facing the problem with Planned Orders which are created via MRP.
Regards
Brijesh

Dear all,
If we set the Individual requirement (1) in MRP4 view of the material master for the component, the system will not consider the plant stock and it will give the message like Parts are missing during the Process Order process even though the plant stock is exists for the component.
So I would like to where in customization you define this?
--> To not consider the plant stock if individual req is set (1)
--> To consider the plant stock if collective req is set (2)
Kindly advice,
Regards,
Brijesh

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

Process Order does Confirmations and GR even after the Process order is CNF

Not Sure why the Formatting is lost.
Hi Gurus,
I am a beginner in this area and request your help.
We are implementing a project where the process order Confirmation in SAP ECC 5.0 in SAP PPPI module is done using xMII which call the BAPI_PROCORD_CREATE_TT     RFC.
The customer wants to (certain times) do a final confirmation without actually completing the order e.g if the Order Qty is 100 then, they want to just manufacture 25 and then do a final confirmation, after which SAP GUI screen does not allow any Process order Confirmations against that process order.
We are using the BAPI_PROCORDCONF_CREATE_TTRFC to do multiple PO Confirmations and GR for particular Process order. Below is a scenario
Case 1:
1. Order Qty =100 ( Unlimited Delivery is not checked and tolerance is Zero).
     Which means only 100 is accepted.
2. 100 Quantities are produced and confirmed using the BAPI_PROCORDCONF_CREATE_TT (with Final confirmation value as 1 , which mean auto confirmation)
3. Next when the BAPI confirms & GR's against the same order, the Complete qty is not visible in the COR3 status. And is visible only in the COGI transaction.
That is expected behavior. and i am ok with that.
Case 2: (The one with the problem)
1. Order Qty =100 ( Unlimited Delivery is not checked and tolerance is Zero).
     Which means only the 100 is accepted.
2. 25 Quantities are produced and confirmed using BAPI_PROCORDCONF_CREATE_TT (with Final Confirmation value as X , which mean Final confirmation)
3. The Confirmation and GR go through and the status of the process order now changed is CNF and the Deliverd qty is 25.
At this point , if you logon to SAP GUI and try to make a process order confirmation you get an error messages which says the Process Order is already confirmed and no more confirmations or GR can be done against this Process order.
4. But when you Again Run the BAPI_PROCORDCONF_CREATE_TT, it goes ahead and confirms and makes the GR for that Process order.
The Expected Behavior should have been that this quantity is now in the COGI transaction.
5. The Process order allows any number of Further confirmations till the Ordered Qty and Delivered quantity are same .
so dear gurus I know i have written a very long doubt but would be very happy to get a response from you. I would ideally not like to enhance or change the BAPI and want to understand if I have missed some setting or parameter that I have to pass in the BAPI for the final confirmation so that once the Status of the Process order is CNF , no more Confirmations are allowed even from the BAPI.
Thanks in Advance.
Regards
Suraj

Hi Suraj,
I am not positive, but I suspectt the problem lies in the BAPI. It might be how you have the data set in MII, but it sounded like you are doing it correctly.
However there are a number of things you can do to troubleshoot your situation.
First create a few process orders to test with.
Record the confirmation numbers and counters for each of the following:
1) Do a final confirmation (for quantity of 25 instead of the 100) in CORK (or whichever transaction you are using).
2) Do a final confirmation (for quantitiy of 25 instead of the 100) in SE37 or BAPI in ERP using the BAPI_PROCORDCONF_CREATE_TT.
3) Do a final confirmation (for quantitiy of 25 instead of the 100) from MII using your current transaction.
Review the confirmations in ERP to see if there are any differences.
Review the confirmaitons in MII to see if there are any non visible differences (use a Tracer to retrieve the response segment from an execution of BAPI_PROCORDCONF_GETDETAIL using the recorded confirmation numbers and counters)
Case 1) If there are differences in the results, that should tell you how to modify your transaction to include or change the appropriate values in your inputs.
Case 2) If there are no differences, then it is most likely that there is something not working properly in the BAPI you are using. It may not completely replicate the functionality in CORK (or whichever transaction you are using in ERP). Then open a ticket, because the BAPI is not working as it should.
Good luck,
Mike
Edited by: Michael Appleby on Aug 17, 2009 8:20 PM

Error while releasing the Process order

while releasing the Process order i am getting the follwing error message
Message no. CO118 Release of order not possible
Cna you Please any body explain me detail of thi error ie where the error lies.
Thanks

Hi,
In Process Order Header Screen Go to ---> Log ---> On Release.Here you will find the detail error behind this problem.Go though it .Resolve it and then try to release the Process Order, and if required get back to us.
Suppose reason may be,
- Missing part
- Missing Capacity
- Batch Determination is required to perform.
- Any User Exit (Other then std. SAP)
Regards,
Dhaval

Fiscal Year Not allowed while creating the Process order (COR1)

Hi Friends,
My Indian client is following the Fiscal year of 2011 for the period of April 2010 to March 2011). We have gone live one month before. But now the problem we are facing is while creating the process order (T.Code COR1) system gives the error message "Fiscal year 2010 is not allowed".
The Diagnosis shows as below
Fiscal year 2010 is not allowed
Message no. F5568
Diagnosis
The fiscal year entered (2010) is different from the fiscal year derived from the posting date and fiscal year variant (2011).
System Response
Error.
Procedure
Correct the fiscal year entered.
I have Checked the Controlling area version. Fiscal Year 2011 starts from 01.04.2010. This issue is only at the time of Process oder creation and not in other module like FI, MM, SD, PS, QM and PM. I have checked with V3 Variant also and there is no problem with that.
Can any one help me where the setting is missing or what whould be the probable reason for this issue.
Regards,
Deva

Hi Prakash,
Thank you for your reply. I have checked the MMPV and MMRV set up and that is fine with fiscal year 2011. We are also processed lot many Material receipts for the fiscal year 2011. I have checked with OB52 for finace it is opened for the entire year of 2011 from 2009 for all periods.
We are facing only when we try to create the process order. When we enter the starte date as 24.11.2010 the derived period shows as fiscal year 2011. But entered fiscal year shows as 2010. We are not entering any other dates in the process order.
Is there any other probablity the date is picking from any Production related set ups??
The costing version fiscal year 2011 starts from 01.04.2010. So no problem with Controlling area. I have Checked the Factory calendar. The calendar starts from 01.01.2010 to 31.12.2010 for the year 2010.
Is there any other possibility of the missing settings or problem in date control???
Regards,
Deva

Reprint the processed order with BDC call transaction

Hi Mentors,
I have a problem with printing the order which is coming in a cockpit program.
for that i am using the bdc and call transaction 'ZVA31' which is exactly the standard program 'SD70AV1A'.
but after first processing i am not able to reprint the processed order.
Below is my bdc code and i am using processing mode 1 at the time of recording.
FORM ZSD70AV1A_PRINT_BA01 USING p_vbeln TYPE vbeln.
DATA: wa_ba01 TYPE nast-kschl VALUE 'BA01'.
perform bdc_dynpro      using 'SD70AV1A' '1000'.
perform bdc_field       using 'BDC_CURSOR'
'RG_KSCHL-LOW'.
perform bdc_field       using 'BDC_OKCODE'
'=ONLI'.
perform bdc_field       using 'RG_KSCHL-LOW'
wa_ba01."wa_ba01."'ba01'.
perform bdc_field       using 'PM_NSORT'
'01'.
perform bdc_field       using 'PM_VERMO'
'1'.
perform bdc_field       using 'RG_VBELN-LOW'
p_vbeln."'513785'.
perform bdc_dynpro      using 'SAPMSSY0' '0120'.
perform bdc_field       using 'BDC_CURSOR'
'04/03'.
perform bdc_field       using 'BDC_OKCODE'
'=&ALL'.
perform bdc_dynpro      using 'SAPMSSY0' '0120'.
perform bdc_field       using 'BDC_CURSOR'
'04/03'.
perform bdc_field       using 'BDC_OKCODE'
'=PROC'.
CALL TRANSACTION 'ZVA31' USING BDCDATA
MODE   'A'
MESSAGES INTO MESSTAB.
CLEAR BDCDATA[].
ENDFORM.                    " ZSD70AV1A_PRINT_BA01
Br,
Surya

Solved myself.
DATA: wa_ba00 TYPE nast-kschl VALUE 'BA00'.
DATA: p_vermo TYPE kschl.
DATA: cur_vstat TYPE nast-vstat.
SELECT SINGLE vstat INTO cur_vstat FROM nast
WHERE objky = p_vbeln
AND   kschl = 'BA00'.
IF sy-subrc = 0 AND cur_vstat = 0.
p_vermo = '1'."wa_vstat.
ELSE.
p_vermo = '2'.
ENDIF.
p_vermo is processing status.
Br,
Surya

Automated TR creation while release the Process Order

I have to split the quantity into smaller units based on the ‘LE quantity’ before TR creation. In transaction LB03, there should be additional line items after the quantity split.
I am using the EXIT ‘EXIT_SAPLLCPP_001’. It is triggering during the transaction run. But it doesn’t serve the purpose.
Can anyone help me to achieve this functionality?

Hi,
In Process Order Header Screen Go to ---> Log ---> On Release.Here you will find the detail error behind this problem.Go though it .Resolve it and then try to release the Process Order, and if required get back to us.
Suppose reason may be,
- Missing part
- Missing Capacity
- Batch Determination is required to perform.
- Any User Exit (Other then std. SAP)
Regards,
Dhaval

Close the Process Orders

Hi All,
Need to close the process orders which are in TECO ststus.
There is no batch number assigned to the process order so no consumption of materials.
The activities are in CRTD WRCE status which are not allowing the process order to close.
Regards,
Mallika

Please follow the below path,
Cor2 --> Process Orders --> Functions --> Restrict Processing --> Complete Technically.
Once the Order are in TECO you cant do the change in its activity.

Setting an job for closing settled process orders

Hi PP Gurus,
I have a requirement to set a background job to close the process orders that have been settled and have not been modified with a certain time frame.
Are there any standard programs which support this requirement of influencing the selection parameters like settled + eligibility time frame? How to identify the settled process orders in SAP?
Regards,
Ramana

Hi,
After the settlement, no particular status is updated in the process order. Hence not possible to select only those orders to close which have been settled.
Workaround I can think of is, in Tcode COHVPI, select those orders which have status TECO and VCAL, my argument would be orders which have status TECO and Variance calculated would be settled most of the time (Say 99%).
Hence set the parameters for background job as status TECO and VCAL. Then go to mass processing tab, select the function COMPLETE, select BACKGROUND in execute function option and create a variant and save.
In SM36 create job, enter the program PPIO_ENTRY, enter the variant created in the earlier step, schedule the date and time.
Regards
Vinod

Error while saving the process order

Hi All,
I changed the quantities of the components and trying to save the process order. But I'm getting a message " "PLEASE REEXPLODE BOM, SINCE THE PROCESS ORDER COMPONENTS HAVE CHANGE". What would be the reason? It is not happening to all the users. Some users can able to save after changing the qty. Some users can't?
Regards,
Sureshbabu G.

Hi,
"PLEASE REEXPLODE BOM, SINCE THE PROCESS ORDER COMPONENTS HAVE CHANGE"
I think it is your Develpment and not from SAP Standard One.So it is difficult to trace out the cause, better will be contact your devlopment team to trace out the reason.
Regards,
Dhaval

How does the GR processing time affect the scheduling of the process order & the latest start date in the operation.

Hi
Can anyone explain how does the GR processing time affect the scheduling of the process order & the latest start date in the operation overview.

Hi
GR processing time means number of workdays required after receiving the material in storage.
Check this link:GR Processing time
Regards,
Anupam Sharma

Not able to see the Cost analysis in the Process order (T-Code COR2).

Hi SAP Guru's
Csoting in the Process order Configuration.
I have done the Config setting related to the Product Costing Controlling with regard to the
Cost Sheet, Cost Componet Structure.Overheads, asssigning the Cost elements in the Costing sheet.
assigned the same in the Process order.
And also the Costing variant options seen in OPL1 t-code can not be displayed in the Process order Csoting Variant selection.
where as the in the Costing variant for the cost component structure, i can see the Xompany code with required plant details.
looking the costing alanysis data in Process order, unable to see

Hi,
If you are looking at cost analysis. You will get this only some you do confirmations to the production or process Order.
I hope you did confirmation of material and quantities to the Process Order
Best Regards
Surya

Confirmation number sequence in the process order

Hi,
When we create a process order , system assigns the confirmation no for each of the operation & these confirmation numbers are in sequence.
In our case we have activity numbers in the recipe as 0010, 0020, 0030, 0040, 0050, 0060...... Subsequently we have inserted operations..now the sequence has become 0010, 0020, 0030, 0040, 0041, 0042, 0050, 0060...... Now when we create the process order, the confirmation numbers for operations 0041, 0042 comes after 0060. We have a development which has a pre-requisite that the sequence of confirmation no's should be as per sequence of operations.
Any idea how to achieve the correct sequence of confirmation no's?
regards,
Mohit

Dear Mohit,
I have find the route cause BUT I Don't know how to fix it
Based on Operation ID, system is creating a confirmation No
Since you have created a operation 41 and 42, System gives the operation ID next to 60
Thats the reason system is giving the confirmation No after 60
I don't know how To add operation ID in routing

Problem in TECOing/Closing the process order.

Similar Messages

Maybe you are looking for