Service order creation condition

Hi,
Could anyone please tell me how can we insert a condition so that one type of service order can not be created after creation of service order of another type.
Suppose if A and B type of service orders(sub-order of C) are to created sequentially...first A then B.
Then in this case after techo of B, A must not be created....so please guide is there any option to insert this condition while we configure sub orders(Service order).
Thanks and Regards

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

Similar Messages

Credit block should not prevent service order creation

An upgrade from 4.7 to ECC6, without any changes made to the configuration or program change, has lead to the following issue. ECC6 is not creating a service order connected to a sales order, when the customer has exceeded the credit limit. The sales order of custom order type is getting saved with a warning message that credit limit has exceeded. However, earlier in 4.7, the message would not stop creating subsequent service order. What could be different, that prevent ECC6 environment to hold on to service order creation? A subsequent release of the credit block through VKM1 however triggers the service order being created.

Are you using credit card processing in SAP to get the authorization?
If you are then the authorization should not block the order.
Or are you using credit card as a form of payment (without authorization) in which case this needs to be put on the customers account as a payment and then the order entered.
Where are you holding the credit card details?

Automatic creation InternalOrder inECC after Service Order creation in CRM

Hi,
After Service Order creation in CRM, the automatic creation of Internal Order in ECC not happening, needs to be do the related settings. Can anybody share the stepts for the same to do the settings.
rgds,
balu

Hello balu,
Have you released all items?
Also,please make sure that against the item category "Assign BW/CO" is set to Service.
Hope this helps!
Thanks and Best Regards,
Shanthala Kudva.

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

BAPI for Service order creation

Hi ,
Please tell me if any Bapi for service order creation , T-code : IW31
regards,
Prakash

Hi Prakash,
Have a look on the following BAPIs:
BAPI_ISUSMORDER_CREATEMULTIPLE - Create Service Orders
BAPI_ALM_CONF_CREATE - Create confirmation for maintenance/service order
WTY04_CREATE_SERVICE_ORDER - Create Service order via function module.
Hope this will help.
Regards,
Nitin.

Service order creation using bapi with repair order number

Hi experts,
Pls suggest me a BAPI to create a service order for those repair orders where a PGR has been done(for return delivery type : LR).
The plant should be 0260 with storage location wh01 and item category ZRRE
Creation of a service order with repair order type SM03 is not allowed in iw31.
thanks and regards,
Vijayb.

Hi prakash,
Thank u for the BAPI
But an error is being displayed saying that the REFURBISHMENT ORDERS CANNOT BE PROCESSED USING BAPI.
ERROR DURING PROCESSING OF BAPI METHODS.
This is while u pass the order type as either ZM03 or SM01or SM02 or SM03.
pls help me on that.
thanks and regards,
Vijayb.

Automatic Service Order creation and OBD line item creation - Repair Order

Hi ALL,
I tried to run the Repair process based on the help document of SAP:
Configs Followed:
1) In Material master MRP3 view, strategy group is assigned as 84 (service orders). By default this str.grp is linked with Requirement type SERA and Requirement class 203.
2 ) Requirement class is assigned with appropriate Service order type.
SPRO>Sales and Distribution>Basic Functions>Availability Check and Transfer of Requirements>Transfer of Requirements-->Define Requirements Classes (OVZG)
Actual Assignment:
Reqt. Class Service Order Type
039 SM01
203 SM01
3) Task list is assigned to your Service material - Service product - OISD
Actual Assignment:
Service Pdt Work Centre Plant B Area Gen TL Group Counter Task List Type
R-1001 PC-SERV 1200 8000 62 1 A
4) Check the Requirement class setting indicator for configuration (cnfg)
Actual Assignment:
= mandatory
5) SPRO>Sales and Distribution>Basic Functions>Availability Check and Transfer of Requirements>Transfer of Requirements-->Define Requirements Classes --> Determination Of Requirement Types Using Transaction
Actual Assignment:
Item Category Reqt class Reqt. Type
IRRS 039 SE
IRRE 203 SERP
IRRP 203 SERP
IRAL 040 KE
6) Sales and Distribution>Sales>Sales Document Item-->Assign Item Categories for determining the item category based on usage
Actual Assignment:
Sal. Doc. Type Item Cat. Group Item Usage H. L . Item Cat Item Category
RAS NORM IRRS
RAS NORM R101 IRRS IRRE
RAS NORM R102 IRRS IRRP
RAS NORM R103 IRRS IRAL
Errors Faced:
1. Service Order is not getting created automatically.
Error in SAP - IDES :"A service order has not been found for action 'Repairs'"
2. Also im not getting the automatic creation of the 4th line item(Item Category - IRAL) in the repair order, which in turn stops me from creating the Outbound delivery.
Please HELP !
Regards

Hi PeteA,
Sorry, here it is...
Let me explain the process that has been followed:
1) Initially to start with Service Notification was created with IW51 T-code.
    In that, Sold to party and material # were entered. Then from there directly i go for Create Repair Order from the Action Box.
    Order type for repair order - RAS, and when i save both Service Notification and the Repair gets saved.
    Now, in the repair order, two line items were getting created automatically and the requirement Types for those line items are:
    Line Item I : SE
    Line Item II: SERP
2) After that i take the material in with the help of t-code VRRE.
3) Then, i do the acceptance of the stock ( Technical Check) with t-code QA11.
    Once i do that, i get the Third line item in the Repair Order and the requirement Type for that line item is:
    Line Item III: SERP
Now my query is, Once i do the QA11 transaction i need to get a Service Order automatically but thats not happening.
Also if i create a Service Order manually, and do the repair and do the technically completion of the service order, then i need to get a third line item (IRAL) in the repair order automatically and thats also not happening.
Regards

Service order creation from sale order

Hi Friends,
   Could you please tell me where is the setting for the automatic creation of service order from sale order.
    Iam using LEIS , TAD and CD as the sales documents and SM01 as service order document.
    Am I missing something?
    Please let me know.
    Regards,
    satish

Hi Satish,
The setting for creation of a service order from sales order can be found in the Requirement class configuration.
To know how to link, check the procurement tab in the sales order, note down the requirement type associated to the line item. Requirement type is linked to requirement class. In requirement class you find the configuration.
Standard SAP creates SM03 (refurbishment) type of service order from sales order.
Reward points if useful.
Regards
Ananth

Service order creation based on counter reading assigned to the Ibase.

Hi All,
I've created a service contract (ZXXX) with the item category (ZIT1) of service plan.
In the item category (ZIT1) definition i've copied the standard item cat. of service plan (SPLA) and assigned the standard date profile SERVPLAN to the item category.
Requirement - Service order has to be created automatically if the counter reading assigned to the Ibase is greater than counter reading that is maintained in the service plan template that is assigned to the service plan product(Item) in the service contract transaction.
Master Data -
Service Interval Template - Created service plan template for counter based interval and maintained the interval as 100HR.
Assigned the template to service plan product(item) which is assigned in the service contract.
Created a counter ID and assigned the counter to the Ibase.
In the item date profile SERVPLAN , I've assigned the date rule (Planned time based on the counter reading) to 'Release date' date type.
In the item action profile ., Action is defined as it should create a service order (ZSER) with the template defined in the item if the (Release date =< today's date) as start condition.
I've maintained the complete master data.
Now Release date should be picked based on the counter reading of the Ibase assigned to the service plan item in the service contract.
If Ibase counter reading > counter reading maintained in the interval the release date = todays date.
If Ibase counter reading < counter reading maintained in the interval the release date = future date.
which is not happening now in my case. service order is getting created even the counter reading of Ibase is less than the interval.
Please let me know if further more changes to be done to map the scenario.
Thanks
Syam

Hello,
I found the following:
If you fill someting in the fields REFOBJ_IBASE, this value is being converted into a GUID internally
This happens in function CRM_BSP_OIC_1O_SEARCH_FROM_RF
So you have to make sure that the search field REFOBJ_IBASE points towards the field CRMD_SRV_REFOBJ~GUID_OBJECT ( via table CRMC_REPDY )
And even then I have the impression it only works when you only fill the Ibase in the order. When you fill the component there is a different GUID.
In my case I found out it is even more complex, so I will need to create my own search field (extend search structure )
Regards,
Erwin

Help with validation of service order creation

Dear All,
I am working with creation of service order under service professional and got a requirement where
1) I need to validate the quantity from BOM table comm_il_momitm. and
2) Same product (product id) should not be called more than once, that is if the user selects same product once again it must throw an error.
Please find the screenshot below
Regards,
Naveenn

Hi Benoit,
I give you my exact requirement,
i need to validate quantity field entry (in above table) based on compon_qty field in comm_il_bomitm table.
I tried to implement it using eh_onsave method in component BT116H_SRVO but it is displaying error message even the quantity is equal the compon_qty whereas it should display error only when it exceeds compon_qty.
Please help by providing sample code.
Regards,
Naveenn

Service Order Creation from a Repair Order - Reg

Hi,
I have a situation where a batch of 100 Pieces of a serialized Serviceable Material has been delivered by a Customer. I have to carry out repair and treat each piece as unique. i.e., a Job Order for each Piece of the Material.
I created a Repair Order, Delivery and perform PGR to inward the incoming Serviceable Material. Now each Serial Number is in stock.
Now, is it possible to automatically create 100 different Service Orders (based on Repair procedure) for each Piece and assign Serial Number to each of these Service Orders ? Or should I have to enter 100 line items one after another manually ?
Thanks.
Raj

Raj,
No, if you want to stay within standard, then you need to create 100 items on the repair order each for one unit, then do 100 seperate goods recipts which will then create 100 seperate orders..
PeteA

Service Order Creation through Sales Order...

Hello,
I got one requirement it is , we need to copy the account assignment (WBS element ) from sales order line item to service order line item . Morever same wbs element should be used to create automatic settlement rule in service order.
This should also work even if user changes the WBS element later. i.e, updated WBS element should again update service order and settlement rule automatically.
I tried to use Exit MV45AFZB and routine USEREXIT_MOVE_FIELD_TO_COBL, but still i am not able to see the data in service order Location tab, Object tab.
I checked the table ILOA, its not getting updated when creating Service order via sales order.
I am not able to see any fields value coming on Service order screen when creating through sales order.
Regards,
Sujeet Mishra

Hi ARC,
Here the issue is that, Sales Order is getting created but while sending the Order num. to Webpage through web service then rasing below Exception.
Runtime Error UNCAUGHT_EXCEPTION
Except. CX_SOAP_CORE
Date and Time 07.05.2008 20:13:24
ShrtText
An exception that could not be caught occurred.
What happened?
The exception 'CX_SOAP_CORE' was raised but was not caught at any stage in the
call hierarchy.
Since exceptions represent error situations, and since the system could
not react adequately to this error, the current program,
'CL_SOAP_TRANSPORT_EXTENSN_ROOTCP', had to
be terminated

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 creation in the backgroung in VA01

Hi,
I want to create every time service order for my sales order in the background. is there any standard functinallity to fulfill my requirement?

This is standard functionality
The transfer of requirements settings for the sales order item can be configured to automatically create a service order.
PeteA

Service Order creation from a Repair Order

Hi,
This is about a case of performing Repair services for customers. Customers send their defective product along with replaceable parts for performing the repair. After completing the repair, the repaired Product has to be sent back to the Customer. Then, we claim service charges from the customer for the labor involved.
I created a Problem Notification and from there, a repair order (RAS). However, after taking the defective product into stock, system is not generating a Service Order. It is automatically picking up SM03 and displays "Order Type SM02 is not suitable for repair processing".
Can anyone guide me through the steps required till Billing !!
Thanks.
Raj

It is not picking up SM03. It is picking up SM02. And SM02 is not a refurbishment type maintenance order. That is why it is giving this message. Trace back to the requirements class/ requirements type to see which service order type is being determined for the item category.

Service order creation condition

Similar Messages

Maybe you are looking for