Termination error while confirming the transfer order

Hi Csaba/Frenchy,
I am getting termination error while confirming or deleting the TO (TO is created out of a posting change notice). Upon confirmation, the system is giving a message that the TO is confirmed but when I try to go out of the TO confirmation screen (LT12), I get the update termination error resulting in TO not getting confirmed.
Could you pls advise how to go about resolving this issue. Matter urgent please.
regards,

One more idea: recreate the PCN (same number, ect) and set the fields via SE16N + &sap_edit as they are in the archived PCN. Else contact SAP AG how to solve.
(I do not know what is the standard solution for this - maybe before archiving belonging data such as open TOs should have been checked...)
Maybe other solution might be if you debug transaction LT12 and when it wants to refresh the PCN you eliminate this with the help of your ABAPer.
Edited by: Csaba Szommer on Jul 29, 2008 7:43 PM

Similar Messages

Error in confirmation of Transfer orders at Header level (TC LRF2)

Hello All,
A transfer order has single item. It has got confirmed at the item level for the full quantity. The confirmation switchbox at item level is checked in by the system automatically. But in header level the switch box is not checked in.
While trying to confirm the Transfer order at header level, the error message shows that the Transfer order is already confirmed. But the Transfer order still exists in LRF2.
Thanks in Advance.
Regards,
Sasi.

Hi Marcos
Note 566995 is an old correction note, which is probably already implemented on your system but it describes the standard system design regarding confirmations posted in mass processing transactions:
When you enter an operation confirmation via the order info system or the mass processing the system now sets the confirmation type to 'Automatic final confirmation' as well as the indicator 'Post open reservations'. Thus the system automatically generates a final confirmation when you confirm the whole planned quantity and the operation receives status CNF (finally confirmed) instead of PCNF (partially confirmed).
System is designed that way because a mass processing transaction will be generally executed in background mode and a huge number of confirmations can be posted at the same time. Therefore, user will not be able to enter any value to the confirmation.
If you don't want this behaviour you could use the BAPI
BAPI_PRODORDCONF_CREATE_HDR to develop your own mass processing transaction to post confirmations.
BR
Caetano

While creating the Transfer Order system is not picking Sale order stock?

Hi All,
In the B2B process the system is not picking the stock from from sale order stock while creating the transfer order? Please suggest.
Summary : Here we are creating the PR in the sale order and STO is created using the same PR to procure the materials from the WM plant to sale order plant. Since here intialy we are moving the stock to our sale order in WM plant and then picking the same. But while creating the Transfer order system is not picking the sale order stock in WM plant.
Regards.

C S Javali
Check in schedule line in transaction flow whether Transfer Req /assembly is checked or not
Regards
Pradeep

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 creating the sales order with billing reference

hi alll
i am getting error while creating the sales order with billing reference.The line items are coming in grey.I am not able to change the items as well as the quantity field.Can u guide me
cheers
shalsa007........

Dear SAP SD 007
I can confidently tell that an enhancement or an user exit has been applied in your scenario
You have to check that
Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
Your people has solved the standard problem by enhancement
Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
To solve this only your people have used userexit
Line items and qty greyed out means definately there is some enhancement or user exit applied
You have to check that
Regards
Raja

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

Error while saving the Sales Order

Hi experts,
i am getting a runtime error while saving a sales order stating: SAPSQL_EMPTY_TABNAME. It says the field T681-KOTAB could be empty. I would give in more inputs. Someone plz help.
Thanks.

I would expect that KOTN521 would be a Database table defined in the ABAP Dictionary that relates to the condition implemented in 521 for the usage specified in that record.
You should be able to go into the info system, SE84, and search under ABAP Dictionary / Database Tables to see what KOTN521 is.
Also, since the only Keys to T681 are KVEWE and KOTABNR, and there are two KOTABNR entries with a value of 521, then there must be two different usages (KVEWE) associated with that table.
If you see what they are, you can check to see what the usages represent. Based on a lookup, it appears that a usage of N is for Free Goods, A is for Pricing etc. In our system, we only have A entries.
What are the usages for the 521 entries? Do they relate to Free Goods/Pricing???
Does the table KOTN521 exist in the ABAP Dictionary?
Answering these questions may get you closer to the answer.
Can you compare the values in these entries to what you have in different SIDs?
Is this problem happening in Production, or is it still in a development or Quality Assurance client?
If it is still in development or Q, then it may be that a recent customization change was made.
Compare the entries across your systems, if possible.
Good luck
Brian

Material Listing Error while creating the sales order

Hi Guru's
I have mantained a material in the lisitng for A002 combiantion for SO/DC/Pric. ref. material
While creating the sales order is throwing an error as material is not listed so the transaction is not possible.
I have done the basic invetingation on the folowing aspects
1)checking the material in the listing
2)Validity periods
3)Material not blcoked
4)Mateial is extened for the respective sales org
Kindly help ASAP.
Thanks & Regards
Tarakaram

Dear SAP SD 007
I can confidently tell that an enhancement or an user exit has been applied in your scenario
You have to check that
Normally when creating a sales order with respect or referring billing documents the qty will be in editable mode and it is standard problem
Your people has solved the standard problem by enhancement
Usually OR--LF-PGI----F2 (SAY THE QTY IS 25 UNITS)
Now you are creating returns order with reference to F2 in the return order type Re there is a standard issue that user can edit the qty to 30 from the original 25
To solve this only your people have used userexit
Line items and qty greyed out means definately there is some enhancement or user exit applied
You have to check that
Regards
Raja

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 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

ERROR WHILE CREATING THE SALES ORDER

Hi,
When creating the sales order i am entering "mode of transport"in TSW details and while trying to save it im getting a message saying "Express document "update was terminated"" recieved from the author "Rahul". If i dont enter the TSW detail while creating i am able to save the order and later in change mode i can enter the mode of transport.
When i check the inbox, it says "definately cannot transfer message to node SMTP due to connection error".
This is hapenning for only one user.
What could be the problem?
Regards,
Rahul.

Hi Rahul,
I think you need to enter the mode of transport in external details where it will take for further processing. TSW is different process.
Thanks
Pravin

Run time error while saving the production order in CO02

HI Experts,
While i am releasing and saving the production order the system is giving the runtime error. Please help.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_SLD_API_EXCEPTION
Error analysis is
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SLD_API_EXCEPTION', was not
caught in
procedure "GET_ACCESS_DATA" "(METHOD)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Internal error in method
A Quick response is required.
Regards
Dinakar Sarma

Hi,
Please check below link for your issue , it may useful
http://forums.sdn.sap.com/thread.jspa?messageID=10815298#10815298
Regards,
Ram

Error while creating a transfer order for delivery note.

Hi Gurus,
I have already created an outbound delivery. I am creating a transfer request as a basis for goods movement in the warehouse and to print the picking list. so i use the path:
Logistics -> Sales and Distribution -> Shipping and Transportation -> Picking -> Create Transfer Order -> Single Document.
Now here i enter the warehouse number, plant, delivery. when i press enter i get error "No items that are to be picked were found".
I went to the following IMG path -- Enterprise Structure --> Assignment --> Logistics-Execution --> Assign Warehouse number to plant/storage location.
Assign the warehouse to the plan and storage location.
Still i get the same error. Could some one help me out here?
Thanks in advance
Amit

Hi,
can you check whether Warehouse number exists and transfer order creation is required or not at Delivery document under Picking tab

Error while creating TO(transfer order) w.r.t delivery note.

I am usiing HU mgmt(Handling Unit Mgmt) with standard WH mgmt.
I hae taken recipt of process order in MB31 transsanction which at the end give Inbound delivry no.
now when i am going to create TO(Transfer Order) w.r.t that delivery no is gives error given below:
" No items or handling units to be placed in storage could be determined"
details:
The inbound delivery does not have any items or handling units for putaway.
i have tried by creating HU(Handling Unit) w.r.t t delivery & then try to create TO the same error was came at that time.

Hi,
can you check whether Warehouse number exists and transfer order creation is required or not at Delivery document under Picking tab

Error while updating the sales order through Process Order API

Hi,
Please any one will help plz.
I am updating the promise_date through oe_order_pub.process_order(Process Order API) i am getting the following error.
FND_AS_UNEXPECTED_ERROR N PKG_NAME OE_Order_Cache N PROCEDURE_NAME get_tax_calculation_flag N ERROR_TEXT ORA-01403:no data found
Please any one will help plz
Below is my code.
Declare
l_archive_file_name VARCHAR2(1000);
l_shipment_exists NUMBER:=0;
l_header_id NUMBER;
l_line_id NUMBER;
p_header_rec Oe_Order_Pub.Header_Rec_Type;
l_line_tbl oe_order_pub.line_tbl_type := oe_order_pub.g_miss_line_tbl;
l_header_rec OE_ORDER_PUB.Header_Rec_Type;
l_header_val_out_rec OE_ORDER_PUB.Header_Val_Rec_Type;
l_header_adj_out_tbl OE_Order_PUB.Header_Adj_Tbl_Type;
l_header_adj_val_out_tbl OE_Order_PUB.Header_Adj_Val_Tbl_Type;
l_header_price_att_out_tbl OE_ORDER_PUB.Header_Price_Att_Tbl_Type;
l_header_adj_att_out_tbl OE_ORDER_PUB.Header_Adj_Att_Tbl_Type;
l_header_adj_assoc_out_tbl OE_ORDER_PUB.Header_Adj_Assoc_Tbl_Type;
l_header_scredit_out_tbl OE_Order_PUB.Header_Scredit_Tbl_Type;
l_header_scredit_val_out_tbl OE_Order_PUB.Header_Scredit_Val_Tbl_Type;
l_line_rec OE_ORDER_PUB.line_rec_type;
l_line_out_tbl OE_ORDER_PUB.Line_Tbl_Type;
l_line_val_out_tbl OE_ORDER_PUB.Line_Val_Tbl_Type;
l_line_adj_out_tbl OE_ORDER_PUB.Line_Adj_Tbl_Type;
l_line_adj_val_out_tbl OE_ORDER_PUB.Line_Adj_Val_Tbl_Type;
l_line_price_att_out_tbl OE_ORDER_PUB.Line_Price_Att_Tbl_Type;
l_line_adj_att_out_tbl OE_ORDER_PUB.Line_Adj_Att_Tbl_Type;
l_line_adj_assoc_out_tbl OE_ORDER_PUB.Line_Adj_Assoc_Tbl_Type;
l_line_scredit_out_tbl OE_Order_PUB.Line_Scredit_Tbl_Type;
l_line_scredit_val_out_tbl OE_Order_PUB.Line_Scredit_Val_Tbl_Type;
l_lot_serial_out_tbl OE_Order_PUB.Lot_Serial_Tbl_Type;
l_lot_serial_val_out_tbl OE_Order_PUB.Lot_Serial_Val_Tbl_Type;
l_action_request_out_tbl OE_Order_PUB.Request_Tbl_Type;
l_msg_count NUMBER;
l_msg_data VARCHAR2(2000);
l_return_status VARCHAR2(1);
l_index NUMBER;
l_rows_processed NUMBER:=0;
l_line_mawb VARCHAR2(240);
l_line_hawb VARCHAR2(240);
l_line_flight_num VARCHAR2(240);
l_org_id NUMBER :=143;--FND_GLOBAL.ORG_ID;
l_resp_id NUMBER:=FND_GLOBAL.RESP_ID;
l_resp_appl_id NUMBER:=FND_GLOBAL.RESP_APPL_ID;
l_user_id number := FND_GLOBAL.USER_ID;
l_promise_date date;
BEGIN
SELECT ol.org_id, oh.header_id, ol.line_id,ol.promise_date
INTO l_org_id, l_header_id, l_line_id,l_promise_date
FROM apps.oe_order_headers_all oh, apps.oe_order_lines_all ol
WHERE ol.header_id=oh.header_id
AND ol.line_id =1319526; --&line_id
-- apps.fnd_global.apps_initialize(&l_USER_ID,&l_resp_id,&l_resp_appl_id);
apps.fnd_global.apps_initialize(67778,51017,660);
p_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
p_header_rec.header_id :=835035;-- l_header_id;
p_header_rec.operation := OE_GLOBALS.G_OPR_UPDATE;
l_line_tbl := oe_order_pub.g_miss_line_tbl;
-------------------------Line Record -------------------------------
l_line_tbl(1) := oe_order_pub.g_miss_line_rec;
l_line_tbl(1).header_id := 835035;
l_line_tbl(1).line_id := 1319526;
l_line_tbl(1).promise_date := sysdate;
l_line_tbl(1).operation := oe_globals.g_opr_update;
BEGIN
apps.oe_order_pub.process_order
(p_api_version_number => 1.0
,p_init_msg_list => fnd_api.g_true
,p_return_values => fnd_api.g_true
,x_return_status => l_return_status
,x_msg_count => l_msg_count
,x_msg_data => l_msg_data
,p_header_rec => p_header_rec
,p_line_tbl => l_line_tbl
-- out variables
,x_header_rec => l_header_rec
,x_header_val_rec => l_header_val_out_rec
,x_header_adj_tbl => l_header_adj_out_tbl
,x_header_adj_val_tbl => l_header_adj_val_out_tbl
,x_header_price_att_tbl => l_header_price_att_out_tbl
,x_header_adj_att_tbl => l_header_adj_att_out_tbl
,x_header_adj_assoc_tbl => l_header_adj_assoc_out_tbl
,x_header_scredit_tbl => l_header_scredit_out_tbl
,x_header_scredit_val_tbl => l_header_scredit_val_out_tbl
,x_line_tbl => l_line_out_tbl
,x_line_val_tbl => l_line_val_out_tbl
,x_line_adj_tbl => l_line_adj_out_tbl
,x_line_adj_val_tbl => l_line_adj_val_out_tbl
,x_line_price_att_tbl => l_line_price_att_out_tbl
,x_line_adj_att_tbl => l_line_adj_att_out_tbl
,x_line_adj_assoc_tbl => l_line_adj_assoc_out_tbl
,x_line_scredit_tbl => l_line_scredit_out_tbl
,x_line_scredit_val_tbl => l_line_scredit_val_out_tbl
,x_lot_serial_tbl => l_lot_serial_out_tbl
,x_lot_serial_val_tbl => l_lot_serial_val_out_tbl
,x_action_request_tbl => l_action_request_out_tbl
--dbms_output.put_line('l_msg_data-->' ||l_msg_data ||' l_return_status --> ' ||l_return_status);
END;
commit;
END;
Regards,
Sangu

Hi Sangu,
See if the following notes help you:
Error when calling API from SQL*Developer, eg. ORA-01403 in API OE_ORDER_PUB.PROCESS_ORDER (Doc ID 1054295.1)
Cancellation Of Transfer Orders Is Not Possible - ORA-01403: no data found in Package OE_Order_PVT Procedure Process_Order (Doc ID 391307.1)
Thanks &
Best Regards,

Termination error while confirming the transfer order

Similar Messages

Maybe you are looking for