Service Order Deletion problem

We have a service order created three weeks ago and released. It is now disapeared from the system mysteriously. We are aware that we have completed the order and released. The only log that we have is on the external system that retrieve this information. We have no trace whatsoever on SAP side whether this record is created or deleted. Even if we deleted, we can only set the flag but NOT physically removed. If there is an archive job that is looking for the deletion flag to remove from the table, is there a way that we can retrieve or find out how this record is being removed? such as job name or so?
Thanks,
Tai

Thanks all. I've talked to our BASIS team and we used SM13 to look back and the transaction that was failed last month. This is the only history that we can track for the problem. Luckly we found that order sitting to be processed.
Thanks,
Tai

Similar Messages

Service order creation problem

Hi Experts, I have a requirement to create a Service order using a BAPI. I'm trying to use the BAPI BAPI_BUSPROCESSND_CREATEMULTI. I found some code related to this BAPI on this forum . THE service order is created
but ibase / component is not filled . How can i give the Ibase through the bapi and in which parameter of the bapi i have to fil this. Could anyone please help me figure out what the problem is . my code is as follows.

Please find the code current thread and below thread.
FUNCTION ZBAPI_SERVICE_SORDER2.
DATA : IS_HEADER            TYPE TABLE OF      BAPIBUS20001_HEADER_INS,
        WA_HDR               TYPE               BAPIBUS20001_HEADER_INS,
        IS_ITEM              TYPE TABLE OF     BAPIBUS20001_ITEM,
        WA_ITEM              TYPE               BAPIBUS20001_ITEM,
       IT_ACTIVITY             TYPE TABLE OF      BAPIBUS20001_ACTIVITY_INS,
       WA_ACTIVITY           TYPE               BAPIBUS20001_ACTIVITY_INS,
        IT_PARTNER             TYPE TABLE OF      BAPIBUS20001_PARTNER_INS,
        WA_PARTNER           TYPE               BAPIBUS20001_PARTNER_INS,
        IT_SALES             TYPE TABLE OF      BAPIBUS20001_SALES,
        WA_SALES             TYPE               BAPIBUS20001_SALES,
        IT_ORG             TYPE TABLE OF      BAPIBUS20001_ORGMAN_INS,
        WA_ORG               TYPE               BAPIBUS20001_ORGMAN_INS,
        IT_PRICING             TYPE TABLE OF      BAPIBUS20001_PRICING,
        WA_PRICING           TYPE               BAPIBUS20001_PRICING,
        IT_SERVICE           TYPE TABLE OF      BAPIBUS20001_SERVICE_OS_INS,
        WA_SERVICE           TYPE               BAPIBUS20001_SERVICE_OS_INS,
        IT_RETURN              TYPE TABLE OF     BAPIRET2,
        WA_RET               TYPE               BAPIRET2,
        IT_PROD             TYPE TABLE OF      BAPIBUS20001_PRODUCT,
        WA_PROD              TYPE               BAPIBUS20001_PRODUCT,"PROCESS_QTY_UNIT -EA
*        IT_SCHED             TYPE TABLE OF     BAPIBUS20001_SCHEDLIN, "QUANTITY
*        WA_SCHED             TYPE              BAPIBUS20001_SCHEDLIN,
        IT_SCHEDLINEs         TYPE TABLE OF     BAPIBUS20001_SCHEDLIN,
        WA_SCHEDLINEs         TYPE              BAPIBUS20001_SCHEDLIN,
        lv_partner_fct1      TYPE               crmt_partner_fct,
        lv_partner_fct2      TYPE               crmt_partner_fct,
        lv_partner_fct3      TYPE               crmt_partner_fct,
        lv_partner_fct4      TYPE               crmt_partner_fct,
        LV_HANDLE            TYPE               CRMT_PRP_HANDLE,
        t_object_to_save     TYPE               crmt_object_guid_tab,
        IT_OBJECT_TO_SAVE    TYPE TABLE OF      crmt_object_guid_tab,
        ts_object            type               CRMT_OBJECT_GUID,
        It1_object_to_save   TYPE TABLE OF      BAPIBUS20001_GUID_DIS,
        W_OBJECT_TO_SAVE     TYPE               BAPIBUS20001_GUID_DIS,
        LV_LOG_HANDLE        TYPE               BALLOGHNDL,
        IT_RETURN1              TYPE TABLE OF     BAPIRET2,
        it_saved_objects     type             crmt_return_objects,
        t_exceptions         type              CRMT_EXCEPTION_T,
        t_objects_not_saved type              CRMT_OBJECT_GUID_TAB,
        WA_INPUT_FIELDS      TYPE              BAPIBUS20001_INPUT_FIELDS,
        IT_INPUT_FIELDS      TYPE TABLE OF     BAPIBUS20001_INPUT_FIELDS,
        ITAB_CREATED_PROCESS TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
        WA_CREATED_PROCESS   TYPE              BAPIBUS20001_HEADER_INS,
        IT_OBJECTS           TYPE TABLE OF     BAPIBUS20001_OBJECTS,
        WA_OBJECTS           TYPE              BAPIBUS20001_OBJECTS.
DATA:   CV_LOG_HANDLE        TYPE              BALLOGHNDL,
        i_saved_objects      type table of     BAPIBUS20001_OBJECT_ID,
        IT_RET2              TYPE TABLE OF     BAPIRET2,
        WA_SAVed_objects     type BAPIBUS20001_OBJECT_ID,
        g_objnr              type CRMT_OBJECT_ID.
DATA :
        LV_GUID1   TYPE       GUID_32,
        LV_GUID2   TYPE       GUID_32,
        LV_GUID3   TYPE       GUID_32,
        V_OBJNR22 TYPE       IBIN-OBJNR,
        V_GUID16     TYPE       COMT_PRODUCT_GUID,
        V_OBJID    TYPE       COMT_PRODUCT_ID.
*************HEADER-GUID**********
CALL FUNCTION 'GUID_CREATE'
IMPORTING
    EV_GUID_32       = LV_GUID1.
***********ITEM-GUID************
CALL FUNCTION 'GUID_CREATE'
IMPORTING
   EV_GUID_32       = LV_GUID2
*********SCHEDULELINE********
CALL FUNCTION 'GUID_CREATE'
    IMPORTING
      EV_GUID_32       = LV_GUID3
************DATA IN HEADER**********
WA_HDR-GUID = LV_GUID1.
WA_HDR-PROCESS_TYPE = 'YESV'.
WA_HDR-DESCRIPTION = PROCESS_DESCRIPTION.
APPEND WA_HDR TO IS_HEADER.
*************** INPUT FIELDS HEADER**************
CLEAR WA_INPUT_FIELDS.
CLEAR IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'GUID'.
wa_input_fields-fieldname = 'MODE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'PROCESS_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_H'.
WA_INPUT_FIELDS-FIELDNAME = 'DESCRIPTION '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN ITEM**********
WA_ITEM-GUID = LV_GUID2.
WA_ITEM-HEADER = LV_GUID1.
WA_ITEM-ORDERED_PROD = PRODUCT.
WA_ITEM-DESCRIPTION = PROD_DESCRIPTION. "product name
WA_ITEM-ITM_LANGUAGE = 'EN'.
WA_ITEM-ITM_TYPE = ITEM_CAT.
WA_ITEM-NUMBER_INT = ITEM_NO.
WA_ITEM-MODE = 'A'.
INSERT WA_ITEM INTO TABLE IS_ITEM.
*******INPUT FIELDS ITEM*****************
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ORDERED_PROD'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'DESCRIPTION '.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ITM_LANGUAGE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'ITM_TYPE'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID2.
WA_INPUT_FIELDS-REF_KIND = 'B'.
WA_INPUT_FIELDS-OBJECTNAME = 'ORDERADM_I'.
WA_INPUT_FIELDS-FIELDNAME = 'NUMBER_INT'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN ACTIVITY**********
WA_ACTIVITY-REF_GUID = LV_GUID1.
WA_ACTIVITY-PRIORITY = PRIORITY.
APPEND WA_ACTIVITY TO IT_ACTIVITY.
*************INPUT FIELDS SALES*************
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'C'.
WA_INPUT_FIELDS-OBJECTNAME = 'ACTIVITY_H'.
WA_INPUT_FIELDS-FIELDNAME = ' PRIORITY'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN SALES**********
WA_SALES-REF_GUID = LV_GUID1.
WA_SALES-PO_NUMBER_SOLD = SOLD_T0_PARTY.
wa_sales-ref_kind = 'A'.
APPEND WA_SALES TO It_SALES.
*************INPUT FIELDS SALES*************
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'E'.
WA_INPUT_FIELDS-OBJECTNAME = 'SALES'.
WA_INPUT_FIELDS-FIELDNAME = 'PO_NUMBER_SOLD'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
************DATA IN PARTNER *********
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000001'.
WA_PARTNER-PARTNER_NO = SOLD_T0_PARTY .
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000014'.
WA_PARTNER-PARTNER_NO = EMPLOYEE_RESPONSIBLE .
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000056'.
WA_PARTNER-PARTNER_NO = SERVICE_EMPLOYEE_GROUP.
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
WA_PARTNER-REF_GUID    = LV_GUID1.
WA_PARTNER-REF_KIND    = 'A'.
WA_PARTNER-PARTNER_FCT = '00000003'.
WA_PARTNER-PARTNER_NO = BILL_TO_PARTY.
wa_partner-ref_partner_handle = '0001'.
wa_partner-display_type = 'BP'.    "Business Partner Number
wa_partner-no_type = 'BP'.        "Business Partner Number
wa_partner-kind_of_entry = 'C'. "entered manually
APPEND WA_PARTNER TO IT_PARTNER.
*INPUT FIELDS PARTENER
CLEAR WA_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_FCT'.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
WA_INPUT_FIELDS-REF_GUID = LV_GUID1.
WA_INPUT_FIELDS-REF_KIND = 'A'.
WA_INPUT_FIELDS-OBJECTNAME = 'PARTNER'.
WA_INPUT_FIELDS-FIELDNAME = 'PARTNER_NO '.
wa_input_fields-logical_key = '0001'.
APPEND WA_INPUT_FIELDS TO IT_INPUT_FIELDS.
wa_input_fields-ref_guid = lv_guid1.
wa_input_fields-ref_kind = 'A'.
wa_input_fields-objectname = 'PARTNER'.
wa_input_fields-fieldname = 'KIND_OF_ENTRY '.
wa_input_fields-logical_key = '0001'.
APPEND wa_input_fields TO it_input_fields.
wa_input_fields-ref_guid = lv_guid1.
wa_input_fields-ref_kind = 'A'.
wa_input_fields-objectname = 'PARTNER'.
wa_input_fields-fieldname = 'NO_TYPE '.
wa_input_fields-logical_key = '0001'.
APPEND wa_input_fields TO it_input_fields.
wa_input_fields-ref_guid = lv_guid1.
wa_input_fields-ref_kind = 'A'.
wa_input_fields-objectname = 'PARTNER'.
wa_input_fields-fieldname = 'DISPLAY_TYPE '.
wa_input_fields-logical_key = '0001'.
APPEND wa_input_fields TO it_input_fields.
as follows.
please find below thread.
Edited by: venkatrao veeramaneni on Nov 4, 2011 3:54 PM
Edited by: venkatrao veeramaneni on Nov 4, 2011 3:57 PM

Service order delete?

Hi all,
I created a Service Order and make status as release at item level so it is available in billing due list.
Now we have such a configuration that once i released the item i can not change status again.
Now i want to delete the order but system is not allowed me to change.
Pls any body tell me how to delete this order?
Regards
jayesh

Hi.
I used the function module CRM_ORDER_DELETE.
CALL FUNCTION 'CRM_ORDER_DELETE'
EXPORTING
 IT_OBJECTS_TO_DELETE = IT_OBJECTS_TO_DELETE
 IV_UPDATE_TASK_LOCAL = 'X'
IV_NO_CHECK = FALSE
IV_NO_BDOC_SEND = FALSE
IV_CHECK_ONLY = FALSE
IMPORTING
 ET_DELETED_OBJECTS = ET_DELETED_OBJECTS
 ET_EXCEPTION = ET_EXCEPTION
CHANGING
CV_LOG_HANDLE =
EXCEPTIONS
 SINGLE_DELETION_ERROR = 1
 DELETION_ERROR = 2
 NO_AUTHORITY = 3
 DOCUMENT_NOT_FOUND = 4
 OTHERS = 5.
But, I can delete the service order.
What did you do ?

Order Deletion Problem

Hello all...i've a strange situation...When a planner deletes an order in the past for a particular time bucket, the order gets deleted in this bucket but is added up to the next bucket. Does anyone know why this might happen??
Thanks!
NV

one more point...this works perfectly for the future buckets and only for the past buckets we are facing this problem...this is in SCM 4.0
Thanks!

Service Order Creation through IC Web client

Hello Experts,
I am facing some problem for service order creation in IC Web client.
Description: "ISUSRV" is the new BOL component in CRM 7.0 for service order creation in ISU System. BOL Object is given in this component is "IsuserviceOrder" for service order creation.
Through this component in BOL i am able to search service order.
Problem: When i am trying to create new Service Order it gives error Massage creation failed.
(1) How to create service order through this BOL Root Object "IsuServiceOrder" which field are required to fill the data before create order.
(2) I found ORDER_CODE field in BOL Root Object "IsuServiceOrderu201D when trying to create order what value fill in this field.
(3) I have create one view Using BOL Root Object "IsuServiceOrder" with Save button how to save the service order through this button. What code is required for Save the View data?

Hi Gagan
Could you please share with your solution, i am kind looking help in same are. We are using CRM 7.0, but i can not find BOL component which is ISUSRV.
My requirement is to create Service Order from Webclient, example meter problem reporting, etc
Please kindly reply or by email shankar no dot vangari at gmail com
regards
shankar

IMP: How to delete the service order

Hey Experts,
Can you tell me how to delete the service order which was created in IW31..? or we have any Functions Module to delete the service order?
and one more question is I have more than 100 service order in the table ,but it will display only 50 order when i execute this Functions Module BAPI_ALM_ORDERHEAD_GET_LIST
can you tell me how to solve this problem...?
Thanking you in advance,
Regards
J Sarathi

This is what the BAPI_ALM_ORDERHEAD_GET_LIST documentation says
"You can use this method to determine a list of orders according to a list of selection criteria. The number of hits that are produced for the person calling up the list, can be specifically reduced; without further parameter transfers, the first 50 hits are displayed. A complete list of the hits is stored internally. If you call up the selection again within a Logical Unit of Work (LUW) without changing the selection parameters, but with other refurbishment parameters, then you receive further partial quantities of the selection result, as specified by you."
and for deletion
check whether you can set any deletion status through the fm BAPI_ALM_ORDER_MAINTAIN
Also check the business objects BUS2007, BUS2088

IW32: Assignments deleted from service order after editing operation number

Dear SAP gurus,
I have a problem with a service order containing muiltiple operations.
When I change the order in IW32 and I edit the operation number of only one operation, the assignments of ALL the operations and suboperations are deleted.
Can anyone tell me if it's normal behaviour to delete assignments from operations when they are edited? Or is there a way to avoid this (apart from not editing the operation positions)?
Thanks in advance and kind regards,
Jermey!

The assignments are deleted whenever one of the operations is edited. This can be:
- changing the operation position to reorder the operations;
- deleting one of the operations;
- making changes in the component list of one of the operations.
The result is always the same: all the assignments of all the operations are deleted.
The problem seems to be a lot bigger than it appeared at first. We asked SAP for support and they are trying to solve the problem right now. It seemes that the MRS add-on causes the assignments to disappear.
Update:
SAP created a note to resolve this problem. It's note number 1255589.
Anyway, thanks for your responses.
Kind regards,
Jermey
Edited by: Jermey Krul on Sep 30, 2008 11:34 AM

Restrict Deletion of Components from Service Order

Hello All,
I noticed that I am able to delete the components from the Components tab of a Service Order even after I have completely issued the components.
Is there a possible way to prevent deletion of components that have already been issued..?
I think I can use the Business Transaction RMKL in the system status GMPS. But I guess this will prevent deletion of those components which have not been issued to the service order.
What would be the best way to prevent deletion of components that have already been issued...?
Thanks
Jensibo

Hello All,
I don't know if you all received the last reply I posted against this thread... coz I am not able to find it in the thread. I had asked for your comments on any repercussions that may occur because of this config.
Anyway, the thing is, I followed Narashiman's suggestion and although I did not use the exact config he pointed me to, I used the config in the following nodes:
1.) Production --> Shop Floor Control --> System Modifications --> Define System Message Attributes
2.) Production Planning & Process Industries --> Process Order --> System Modifications --> Define System Message Attributes
and added an entry: Application Area = CN, Message No. = 750-Component & item & was already withdrawn and Category = E.
Having done this, the system did display the "Component & item & was already withdrawn" message when I tried to delete a component that was issued to a service order, but it did not delete the component from the service order. I was able to save the service order with the issued component still in the components tab.
Narashiman,
to specifically respond to your latest reply, I did find the node you pointed me to. But the trouble was that it did not have an entry for CN750 in it. When I tried to add an entry, the system did not let me do so and displayed the error message "Please specify a legal value".
So I went around opening each system message control node and finally found the two that I mentioned earlier that did work for me.
Thanks
Jensi

Problem follow-up item from Service Order to Complaint in IC CRM 7

Hi gurus,
From a Z Interaction Center CRM 7 role (Front Office agent) create by ourselves, we need to create a follow-up complaint from a service order, exactly we need to create a CRMC transaction follow-up from a SRVO transaction. We have do the copying control between these two transactions.
The items categories that we use are, for SRVO transaction, the SRVS category (Product) and, for CRMC transaction, the COMP category (Complaint). We also have do the copying control between these two items categories.
In addition, we have defined the following item category determination when copying:
Source category: SRVS (Product)
Target transaction type: CRMC (Complaint)
Target item category: COMP (Complaint)
When we use a the CRM 7 role SERVICEPRO (Back Office agent), we can create a Complaint (CRMC) follow-up from a Service Order (SRVO) and immediately it appears a pop-up that allows to select the item of the Service Order to add it as a item of the Complaint. But when we use the Z Interaction Center CRM 7 role and do the same, we can't select this item, no pop-up appears.
Please, is it necessary to do some configuration for it? Our Front Office Agent has to be able to do it.
Regards,
Jesus

Hi Jesus,
I was suspecting this, we had a similar problem in CRM 6.0, i thought this is no more there in CRM 7.0. Well we had raised an OSS message for this and the reply was a development in the view or use the service pro view(sans)ICWEB apllications.
This happens with any followup you want to create in the ICWEB view since there is no pop up here.
I would suggest you to raise an OSS for this
Regards
Raj

Problem in Changing the Service Order Using BAPI_ALM_ORDER_MAINTAIN

Hi ABAPers,
I want to change the Service order(TCODE-IW32) Using BAPI_ALM_ORDER_MAINTAIN.But i don't know what are all the
Parameters needs to be passed.I want to chnage the COMPONENT of the Service Order.Please anyone tell me what all are the
mandatory parameters should be passed to change the COMPONENT of the Service Order.If anyone has the code Please send me.
It is very Urgent Kindly help me to Solve this problem.
Regards,
Ashok.

Hi Ashok,
i am sending u the sample eg thread for bapi create i thnk u can find out the mandatory fields frm tht ...
check this link though it is for create the mandatory fields and structure will be same .
Create Order BAPI
regards
Sana M.
reward for useful answers..

Problem with sales order and Service order

Dear Guru's
We have a real problem with sales orders and service orders and how we treat these. For a project that uses a WBS, it's not a problem to manipulate SAP to give us a list of shortages (orders with no or limited supply) for each order, but for some reason our after sales orders and our service orders do not work this way.
Thanks and Regards,
Deethya.

CLOSED

How can we restrict users from marking service orders as deleted

Hi,
Please guide me :
Is it possible to restrict users (who are having authorization of marking service orders as deleted) from marking some service orders as deleted, if they have not created these service orders?
In other words, requirement is : only the person creating the Service Order should be authorized to delete.
Please guide.
Thanks and Regards

There are many BADI and EXITS available, you have find the appropriate place to put your code.
USER - EXITS
CNEX0013 Order: Cust. enhancement: Default item category comp. assgmt
CNEX0026 Customer enhancement for general inspection of material
CNEX0027 Customer enhancement: Plant, storage loc. finding for comp.
IWO10004 Maintenance order: Customer check for order completion
IWO10005 Maintenance order: Cust.-specif. determination of profit ctr
IWO10006 Maint. order: Fcode exclusion through cust. enhancement
IWO10007 Maint.order: Customer enhancement - permits in the order
IWO10008 Cust. enhancement: Determination of tax jurisdiction code
IWO10009 PM Order: Customer Check for 'Save' Event
IWO10010 Maint. order: Cust. enhancement for determining WBS element
IWO10011 Maint. order: Customer enhancement for component selection
IWO10015 Maintenance order: F4 Help for user fields on operation
IWO10016 PM Order: Cust. enhancement to check operation user fields
IWO10017 Determine external order number by customer logic
IWO10018 Maintenance order: User fields on order header
IWO10020 Maintenance order: Automatically include task list
IWO10021 Automatic task list transfer when creating order from notif.
IWO10022 Determine calendar from user exit
IWO10023 Service order: Change header data for advance shipment doc.
IWO10024 Service order: Changes to items for advance shipment
IWO10025 PM/SM order: Finding responsible cost center
IWO10029 Inclusion of bill of material in PM/SM order
IWO10030 Preset Fields for Event Object
IWO10031 Hide personnel number in PM/SM order
BADI
Name of a BAdI Definition
ARC_PM_ORDER_CHECK
ARC_PM_ORDER_DELETE
ARC_PM_ORDER_PREPROCESSING
ARC_PM_ORDER_WRITE
ARC_PM_QMEL_CHECK
ARC_PM_QMEL_DELETE
ARC_PM_QMEL_PREPROCESS
ARC_PM_QMEL_WRITE
IWO1_ORDER_BADI
IWO1_PREQ_BADI
IWO1_SCREEN_MODIFY
IWO1_TL_INTEGRATION
IWO1_TL_INTEGRATION2
Edited by: Manish Bisht on Jul 11, 2009 9:27 AM
Edited by: Manish Bisht on Jul 11, 2009 9:28 AM

Delete the attachments in Service orders

Hi Guys,
I am developing a report, which it needs to be delete the attachments from the CRM service order, could you please suggest, is any FM/BAPI for the same.
Thanks,
Gourisankar.

Hi,
User below code, it will work.
REPORT zcrm_service_order_delet_attch.
TABLES
TABLES:crmd_orderadm_h.
 TYPES DECLARATION
TYPES: BEGIN OF t_crmd,
 guid TYPE crmt_object_guid,
 object_id TYPE crmt_object_id_db,
 date TYPE crmt_posting_date,
 object_type TYPE crmt_subobject_category_db,
 END OF t_crmd.
TYPES: BEGIN OF t_crmd_final,
 object_id TYPE crmt_object_id_db,
 date TYPE crmt_posting_date,
 sucess TYPE i,
 failure TYPE i,
 total TYPE i,
 END OF t_crmd_final.
 Internal Tables *
DATA: i_crmd TYPE STANDARD TABLE OF t_crmd,
 w_crmd TYPE t_crmd,
 i_object_no TYPE STANDARD TABLE OF crmt_icss_object_guid,
 w_object_no TYPE crmt_icss_object_guid,
 i_attch TYPE STANDARD TABLE OF crmt_icss_att_info,
 w_attch TYPE crmt_icss_att_info,
 i_crmd_final TYPE STANDARD TABLE OF t_crmd_final,
 w_crmd_final TYPE t_crmd_final,
 ls_crmt_object_guid TYPE crmt_object_guid_tab,
 i_return_objects TYPE crmt_return_objects.
DATA: lt_ios TYPE skwf_ios.
DATA: ls_io TYPE skwf_io.
DATA: l_docbusobj TYPE sibflporb.
DATA: l_sucess TYPE i.
DATA: l_failure TYPE i.
DATA: l_tot_final TYPE i.
DATA: l_lines TYPE i.
 CONSTANTS *
CONSTANTS:
c_typeid(10) TYPE c VALUE 'BUS2000116',
c_catid(2) TYPE c VALUE 'BO',
c_object_type(1) TYPE c VALUE 'P'.
Selection-Screen
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-s01.
SELECT-OPTIONS: so_date FOR crmd_orderadm_h-posting_date OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.
Start-of-selection
START-OF-SELECTION.
PERFORM getdata.
PERFORM delete_attach_save_order.
PERFORM display_output.
write: u_line(100)
skip.
WRITE: /05 'Total number of attachments deleted',
 75 l_tot_final.
*& Form getdata
FORM getdata .
SELECT guid
 object_id
 posting_date
 object_type INTO TABLE i_crmd
 FROM crmd_orderadm_h
 WHERE posting_date IN so_date.
ENDFORM. " getdata
*& Form delete_attach_save_order
FORM delete_attach_save_order .
*Fetching the attachments for GUID.
LOOP AT i_crmd INTO w_crmd.
 CLEAR: i_attch, i_object_no.
 MOVE: w_crmd-guid TO w_object_no-object_guid.
 APPEND w_object_no TO i_object_no.
 CALL FUNCTION 'CRM_ICSS_GET_ATTACHMENTS'
 TABLES
 it_object_guid = i_object_no
 et_attachment_list = i_attch.
*Deleting the attachment for GUID.
 DESCRIBE TABLE i_attch LINES l_lines.
 LOOP AT i_attch INTO w_attch.
 l_docbusobj-instid = w_crmd-guid.
 l_docbusobj-typeid = c_typeid. "'BUS2000116'.
 l_docbusobj-catid = c_catid. "'BO'.
 ls_io-objtype = c_object_type. "'P'.
 ls_io-class = w_attch-att_class. "'CRM_P_ORD'.
 ls_io-objid = w_attch-objkey.
 APPEND ls_io TO lt_ios.
 CALL METHOD cl_crm_documents=>delete
 EXPORTING
 business_object = l_docbusobj
 ios = lt_ios.
 IF sy-subrc = 0.
 l_sucess = l_sucess + 1.
 ENDIF.
*Saved the service order after deleting the attachment.
 APPEND w_crmd-guid TO ls_crmt_object_guid.
 CALL FUNCTION 'CRM_ORDER_SAVE'
 EXPORTING
 it_objects_to_save = ls_crmt_object_guid
 iv_update_task_local = 'X'
 IMPORTING
 et_saved_objects = i_return_objects
 EXCEPTIONS
 document_not_saved = 1
 OTHERS = 2.
 IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 ENDIF.
 ENDLOOP.
*Moving the data to inter table to display the output.
 IF l_lines EQ l_sucess.
 MOVE: w_crmd-object_id TO w_crmd_final-object_id.
 MOVE: w_crmd-date TO w_crmd_final-date.
 MOVE: l_sucess TO w_crmd_final-sucess.
 MOVE: l_failure TO w_crmd_final-failure.
 MOVE: l_sucess TO w_crmd_final-total.
 APPEND w_crmd_final TO i_crmd_final.
*Clearing the internal tables and variables.
 CLEAR: i_attch,
 w_crmd,
 l_sucess,
 l_failure,
 ls_crmt_object_guid,
 l_docbusobj,
 lt_ios,
 i_object_no,
 l_lines.
 ENDIF.
ENDLOOP.
ENDFORM. " delete_attach_save_order
*& Form Display_output
FORM display_output .
IF NOT i_crmd_final IS INITIAL.
 WRITE: /5 'Order Number',
 20 'Creation date',
 35 'success Records',
 55 'Fail Records',
 75 'Total Records'.
ENDIF.
LOOP AT i_crmd_final INTO w_crmd_final.
 WRITE: /5 w_crmd_final-object_id,
 20 w_crmd_final-date,
 35 w_crmd_final-sucess,
 55 w_crmd_final-failure,
 75 w_crmd_final-total.
 l_tot_final = l_tot_final + w_crmd_final-total.
ENDLOOP.
CLEAR : w_crmd_final.
ENDFORM. " Display_output

Set deletion flag for service orders

Hi
How do I mass update service orders and notifications to set the deletion flag.
I tried with IW72 but no luck Please help.
Thanks
Kumar

Hi,
You can use batch recording to assign DLFL status to work orders,
This is the program code
                      0000     T     IW32
SAPLCOIH              0101     X
0000           BDC_CURSOR                                                                                CAUFVD-AUFNR
                      0000           BDC_OKCODE                                                                                /00
                      0000           CAUFVD-AUFNR                                                                                4000488
SAPLCOIH              3000     X
0000           BDC_OKCODE                                                                                =LVMS
                      0000           BDC_CURSOR                                                                                CAUFVD-AUART
SAPLCOIH              3000     X
0000           BDC_OKCODE                                                                                =BU

Problem while Creating Service order through Work Order

Hi Gurus,
I have a problem While creating Service order (me21n) through - Work order it contains service requisitions.
So that means they carry information such as G/L and work order number while entering the requistion no in PO Creation Screen (me21n) which automatically should be picked from the work order refference.
But problem here is the service items and all other are assigned to PO except the Account Assingnment tab which is GL Account and Work Order No and Cost center..
Can anyone explain me this?
Is this something that one can explain?
Regards,
Murugesh R
Rewards for value replies.

Closed..

Service Order Deletion problem

Similar Messages

Maybe you are looking for