Create "Followup document" in Service Ticket

Dear Experts,
I'm performing mass creation for Service Ticket by using IDOC basic type CRMXIF_ORDER_SAVE_U01.
At the same time, i need to create a "Followup document" for the service ticket as well, and hence i utilized the segment E101CRMXIF_DOC_FLOW with below field population:
APPL_SNAME = E101CRMXIF_DOC_FLOW
RELATION_TYPE = VONA
RELOBJ_TYPE = BUS2000116
RELOBJ_OBJECT_ID = 1234567
RELATION_TYPE_ATTR = A
I can not get any Followup doc created. Basically i did tried to take off the value for RELOBJ_OBJECT_ID, but it still didn't worked.
Could you please comment what went wrong? Or any steps that i have left out?
Thanks in advance.

Hello FSCHU,
Please refer notes 1036737 and see if this helps.
regards,
Muralidhar Prasad Chatna

Similar Messages

  • Unable to create followup document

    Hi All,
    I am trying to create followup document from activity,
    but unable to get successful, actually debugged standard order maintain function module also,
    I  populated & followed the same in my zprogram too,
    but for the same values from standard program i.e CRMD_ORDER tcode linked GUID got generating, but from my code it is not
    generating followup document GUID....please help me out where I am doing mistake.......
    thanking you
    by code is like below :-
    ******followup document create
    *****header
    CLEAR : wa_ct_orderadm_h, ct_orderadm_h.
    wa_ct_orderadm_h-handle = '0000000001'.
    wa_ct_orderadm_h-mode = 'A'.
    wa_ct_orderadm_h-process_type = 'Z4D2'.
    APPEND wa_ct_orderadm_h TO ct_orderadm_h.
    *****input fields
    CLEAR : wa_crmt_input_field, wa_crmt_input_field_names, wa_crmt_input_field-field_names.
    REFRESH : ct_input_fields.
    wa_crmt_input_field-ref_handle = '0000000001'.
    wa_crmt_input_field-ref_kind = 'A'.
    wa_crmt_input_field-objectname = 'ORDERADM_H'.
    wa_crmt_input_field_names-fieldname = 'MODE'.
    INSERT wa_crmt_input_field_names INTO TABLE wa_crmt_input_field-field_names.
    wa_crmt_input_field_names-fieldname = 'PROCESS_TYPE'. "MANUAL
    INSERT wa_crmt_input_field_names INTO TABLE wa_crmt_input_field-field_names.
    APPEND wa_crmt_input_field TO ct_input_fields.
       document link
    CLEAR : ct_doc_flow, wa_ct_doc_flow, wa_doc_link, it_doc_link.
    wa_ct_doc_flow-ref_handle = '0000000001'.
    wa_ct_doc_flow-ref_kind = 'A'.
    wa_doc_link-objkey_a = wa_et_doc_flow-objkey_b.
    wa_doc_link-vona_kind = 'A'.
    wa_DOC_link-handle_b = '0000000001'.
    *wa_doc_link-reltype = 'VONA'.
    wa_doc_link-brel_kind = 'A'.
    wa_doc_link-brel_mode = 'A'.
    INSERT wa_doc_link INTO TABLE wa_ct_doc_flow-doc_link.
    INSERT wa_ct_doc_flow INTO TABLE ct_doc_flow.
    CALL FUNCTION 'CRM_ORDER_MAINTAIN'
      IMPORTING
        et_exception            = it_exception
      CHANGING
        ct_orderadm_h           = ct_orderadm_h
       ct_orderadm_i           = ct_orderadm_i
        ct_input_fields         = ct_input_fields
       cv_log_handle           = cv_log_handle
       ct_partner_attributes   = ct_partner_attributes
        ct_doc_flow             = ct_doc_flow
      EXCEPTIONS
        error_occurred          = 1
        document_locked         = 2
        no_change_allowed       = 3
        no_authority            = 4
        OTHERS                  = 5.
    ******followup document end
    READ TABLE ct_doc_flow INTO wa_ct_doc_flow INDEX 1.
    IF sy-subrc EQ 0.
      READ TABLE wa_ct_doc_flow-doc_link INTO wa_doc_link INDEX 1.
      IF sy-subrc EQ 0.
        v_guid16 = wa_doc_link-objkey_b.
      ENDIF.
    ENDIF.

    CRM_ORDER_MAINTAIN to create follow up document
    To create follow up : Service Confirmation document
    Creating follow up transactions
    Create a Preceeding doucument using CRM_ORDER_MAINTAIN
    check these links, might be helpful.
    Thanks
    Raman

  • Service order as followup document for service order

    HI gurus,
    Can a service order be created as a followup for service ticket. The call agent creates a service ticket for a channel partner. The channel partner should open the service ticket and create a followup document service order for the service ticket.
    Can we create a followup document which has the leading business transaction category same as the preceeding document.
    Thanking u, Madhu.

    Madhu,
    I am sure you can create a follow-up transaction from a Service ticket to Service Order, All you have to make sure is the setting in IMG for Follow-up are active and right.
    Thanks

  • Service Order as follow up document for Service Ticket

    Hi,
    we are using CRM 2005 and the IC-Webclient for the service callcenter.
    Is it somehow possible to create a service order as follow up document out of a service ticket in IC-Webclient?
    Thanks a lot.
    Best regards
    Manfred

    Hi,
    The Service Ticket itself is Service Order. The difference between them is that the Service Ticket does not have Item Category which is present in the Service Order.
    Between your transaction code maintian the copy controls.
    Hope it helps.
    Regards,
    Rajiv

  • Problem while creating followup to a Service Request

    Hi,
    I am trying to create a followUp to a service request. The problem is, it is not displaying all the followup transactions in popup. When I checked the configuration "Copy Control for Business Transactions", I am able to see more than I see in the popup.
    Could you please let me know, why I am unable to see all the transactions in the popup.
    Thanks,
    Sandeep

    Hi Maggie,
    I checked it. CRM WEB CLIENT is assigned for all the transaction types. In my copy control I manitained around 10 transactions.
    when I cliked on create follow-up, 5 transaction types I am able to see in popup. But other 5, I am not able to. not sure why.
    Thanks,
    Sandeep

  • Once,User create Followup Document Then previous Order should be dispaly

    Hi Folks,
    I'm currently in version 5.0, and having trouble with the PCUI customization,
    I have requirement like USER- A create SERVICE ORDER send to USER-B, USER-B Receive service order in CHANGE Mode only, then he will create Follow-up document Service confirmations. And same user comes back to service order that service order should be DISPLAY mode only.
    please help as much as you can ?
    i will appresiate small help also which is so help full.
    please respond as early as possible......

    Outlook 2003
    If you are using Outlook 2003, follow these steps:
    Click My Computer, and then double-click drive C.
    On the File menu, click New, and then click
    Folder.
    Name the folder temp0.
    Click Start, click Run, type regedit, and then click
    OK.
    Locate and then click the following registry key:
    HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security\
    In the right pane, double-click OutlookSecureTempFolder.
    In Value Data field, type C:\temp0\ and then click
    OK.
    Exit Registry Editor.
    Restart the computer.
    Try this and make the comment
    I used this on Outlook 2007.  Also used the "let us fix it for you" link in the help section after backing up the registry and everything is working, at least for now.
    Hope this helps others!

  • Contract data not getting copied for service ticket follow up complaint.

    Hi Experts,
    We are creating a complaint as a follow-up document to service ticket . But the contract data is not getting copied.
    We contacted SAP and they told us that its a standard behavior .The reply is basically an SAP note
    841830 - Contract data not copied to follow-up transaction
    My question is is there a way to change this behavior using CRM_COPY_BADI ?
    I tried to look for the method which I can implement to get the contract data in items, But I was not able get it .
    Please suggest the way to get it working
    Thanks in advance .
    Naval

    Please not that the contract determination works fine when creating a new complaint ... but when the I am trying to create a complaint from service ticket the item level contract determination is not working fine ...
    We have configured that the contract should be determined at the item level only option `F`.
    I checked in one of the sap document that this cant be achieved by standard .
    http://help.sap.com/saphelp_crm70/helpdata/en/46/5cd7335bbd516fe10000000a114a6b/frameset.htmhttp://help.sap.com/saphelp_crm70/helpdata/en/46/5cd7335bbd516fe10000000a114a6b/frameset.htm
    Is there a way we can put this code in the BADI eg; CRM_SERVICE_CONTRACT ?? Please note that there is already an implementation of CRM_SERVICE_CONTRACT which is working fine for new service document creation .

  • ERMS: Creation of Interaction Record and Service Ticket

    Hi All,
    I am configuring the ERMS system (SAP CRM 2007). So far I am been able to get internal emails into the CRM system and the emails are getting routed to the respective agent's inbox based on the rule in Rule Modeler.
    I have created rule for creating Interaction Record and Service ticket. However, Interaction Record and Service ticket are not getting generated. Also, I am not able to receive external emails (yahoo, gmail etc..) into SAPconnect.
    Any input on these issues is appreciated.
    Thanks & regards.

    Hi Namita,
    Same as the other thread, please make sure that the BP is identified for the incoming email and then only the creation of the IR/SO ERMS Actions will get executed with success.
    I am not sure, whether you still face this issue ?
    Thanks & Best Regards,
    Vinod
    Edited by: Vinod C on Mar 25, 2009 3:38 PM

  • Document type service

    We are trying to create a document type service meaning we want to transmit a document
    as is. The webservices documentation states:
    "RPC-oriented WebLogic Web service operations use SOAP encoding. Document-oriented
    WebLogic Web service operations use literal encoding."
    Our service method signature is:
    public void processCreditApp(String document)
    We change our web-services.xml to include: style="document" in the web-service
    element and invocation-style="one-way" in the operation element.
    The client generated builds a SOAP message with the body content typed as a string:
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <env:Body>
    <xsd:string>HelloWorld</xsd:string>
    </env:Body>
    </env:Envelope>
    We had expected the content of the body not to be typed with <xsd:string> tags.
    Likewise
    the generated web service is expecting this typing.
    Have the corect assumptions about "literal encoding"? Have we left out any necessary
    steps or settings?
    We are using WL 7, service pack 2 with the pathch: CR102544_70sp2_v2.jar.

    I am not sure I understand. The SOAP body we receive does not have a type designation:
    <SOAP:Body>
    <diag:Diagnostic
    xmlns:diag="http://www.someName.com/namespace.messaging.diag#"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <diag:DiagnosticMessage>
         <diag:RequestMessage>HelloWorld</diag:RequestMessage>
    </diag:DiagnosticMessage>
         <diag:SourceIdentifier>MySource</diag:SourceIdentifier>
    </diag:Diagnostic>
    </SOAP:Body>
    How can we map types for this?
    Steve
    "Karthik V" <[email protected]> wrote:
    Just by changing "rpc" to "document" in web-services.xml will not help.
    You missed <types> and <type-mapping> elements.
    I guess your <operation> still has input param type as xsd:string.
    You should change this to new type that you create to represent your
    document.
    Alternatively, you could servicegen with style="document" and take a
    look
    at the generated web-services.xml.
    That will give you a better idea.
    /k
    "Steve Watson" <[email protected]> wrote in message
    news:[email protected]...
    We are trying to create a document type service meaning we want totransmit a document
    as is. The webservices documentation states:
    "RPC-oriented WebLogic Web service operations use SOAP encoding.Document-oriented
    WebLogic Web service operations use literal encoding."
    Our service method signature is:
    public void processCreditApp(String document)
    We change our web-services.xml to include: style="document" in theweb-service
    element and invocation-style="one-way" in the operation element.
    The client generated builds a SOAP message with the body content typedas
    a string:
    <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <env:Body>
    <xsd:string>HelloWorld</xsd:string>
    </env:Body>
    </env:Envelope>
    We had expected the content of the body not to be typed with <xsd:string>tags.
    Likewise
    the generated web service is expecting this typing.
    Have the corect assumptions about "literal encoding"? Have we leftout
    any necessary
    steps or settings?
    We are using WL 7, service pack 2 with the pathch: CR102544_70sp2_v2.jar.

  • Unlinking an InteractionRecord from a Service Ticket.

    Hi Gurus,
    I would like to find out if it is be possible to remove the link between an InteractionRecord and a Service Ticket? In our scenario whenever we create a service ticket an interaction record will be created automatically along with the service ticket. But it is not happening all the times. Some times Interaction record won't be created along with the service ticket. Can any one tell me why this happens like this?

    Hi ManniF,
                  Thanks for your quick response. Here we are creating the service ticket under IC_AGENT role. Actually what happens in our case is whenever we open a Service Ticket in IC, sometimes all the servicetickets comes under business context of a service ticket. Can you tell me why the service tickets comes under business context of a service ticket.Can any one tell me how to restrict the service tickets under business context when I open a service ticket?
    Edited by: MuraliKiran on Jul 2, 2010 12:18 PM
    Edited by: MuraliKiran on Jul 2, 2010 12:20 PM
    Edited by: MuraliKiran on Jul 2, 2010 12:23 PM

  • How do I create a "document-centric" Web Service?

    By document-centric I'm talking about receiving a SOAP message on the server-side, where the initial parsing and security processing (this aspect is very important) is performed but then allowing the developer to access the delivered "payload", i.e. the XML, and perform whatever mapping/processing that is required without automatically mapping to the "standard" auto-generated Java objects.
    It is important that the client receives the "full" complex WSDL and can therefore generate their proxy classes with whatever tool (or language) that is appropriate.
    On the server side we do not want to create hundreds (if not thousands) of Java Bean clases as we already have the legacy code to map XML to Java. The idea is that JAX-RPC only instantiates the SOAPElements that represent the "raw" message, or, if possible, doesn't instantiate any objects whatsoever.
    I've spent many days now trying to find a single well-worked example for this type of Web Service without success - many, many references of the style "..and you can then create a document style web service.." but without the all important "how".
    From what I've read a custom type-mapping and/or serializer/deserializer could be the answer but again no good, solid examples are forthcoming.
    Another alternative seems to be to create the server side stub-classes using a "dummy" WSDL with the elements set to "anyType" but then distribute the "genuine" WSDL to the clients - we've got a simple example of the kind working but I don't like the idea of "tricking" the system in this way.
    I'm working with WASD 5.1, which in theory conforms with JAX-RPC so any ideas offered here should also apply in that environment.
    Has ANYONE successfully created a service of this type?
    Any help with this issue would be very much appreciated and rewarded (with Duke Dollars of course).
    Chris.

    Chris,
    I too noticed that most vendors take the RPC centric approach. Its because most of the industry examples of how WSs were used were simple enough to implement using RPC and anything more (document literal) would add to the complexity of implementation. This is something that is feared by many developers, especialy the .Net crowd who seem to want everything done through a wizard menu interface and don't care about other WS implementations at all.
    This is sort of changing. J2EE 1.4 is WS-I compliant, so when you compile server side ties from WSDL you can specify a document literal option and WS-I compliance. This gives you access to the SOAPElement objects. There's still issues with going between W3C DOM and SOAP elements but that's just API inconvenience, not a show stopper. As the inudustry develops more complex WSs we will see the vendors change their tools to better support this...
    Anyway, some more help...
    I use the the following wscompile options to build from WSDL for document literal WSs.
    wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -import config.xml
    wscompile.bat -d . -nd . -s . -f:documentliteral -f:wsi -keep -model model.gz -gen:server config.xml
    My "wrapper" elements look like this...
    <xs:element name="AComplexXMLResponse">
         <xs:complexType>
              <xs:sequence>
                   <xs:element ref="myNS:MYComplexXMLType"/>
              </xs:sequence>
         </xs:complexType>
    </xs:element>
    If I do this:
    <xs:element name="ASimpleXMLResponse">
         <xs:complexType>
              <xs:sequence>
                   <xs:element name="AName" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
    </xs:element>
    I still get the JAXRPC language bindings to a string, but in my case I don't really care. This may well be different for you.
    What I do to manage these elements is to split up the WSDL, WS wrapper element definitions and actual data XML schema definitions into separate documents. This means I have a WSDL which IMPORTS my message schema (this is where I define wrappers for in and out XML) which INCLUDES the actual DATA XML schema that I have.
    The WSDL import looks like this:
    <types>
         <xs:schema>
              <xs:import namespace="http://schemaURI" schemaLocation="./relativePath/WrapperElementSchema.xsd"/>
         </xs:schema>
    </types>
    The wrapper element schema has:
    <xs:include schemaLocation="./ActualDataSchema.xsd"/>
    This way I can easily replace the wrapper documents with just anyType references if something doesn want to play nice. The data schema file and the WSDL stay the same. This minimises the impact on what you have to change in your distribution. This is important as the WSDL is often generated on the fly by your WS environment and so can not be easily changed once you build your WSs, but the schema files it references are easily changed without affecting your code.
    Another reason for the wrapper elements was a JWSDP 1.2 issue (I don't know if this has been fixed in 1.3), where if you had the same method parameter signature in a web service (the parameters it took were the same XML types, for instance if you have an add and update methods for the same document input) JWSDP would get confused at runtime. It did not take account of the SOAP action that came along with the request to determine which operation to call. It just took the incoming XML, saw that it was of a certain type and it passed it to the first operation that took this element, which is VERY wrong. By using the wrapper elements, I could give all my input and output elements for each method different names (I used a naming stragegy that appended a 'request' or 'response' string to the method name to form a method parameter element name. This is a pain in the ass, but works and does wonders for interoperability with other WS vendors. Like I said before, I've got this working with JWSDP, BEA and .Net servers and clients.
    Hope this helps,
    If you think there is a real need for a public HOWTO on this, I could write one with a full step by step guideline that shows where I broke my legs getting this stuff to work. But this would eat into my sleep time :-/ TO JUDGE INTEREST I call on all people interested in a tutorial to respond to this thread (esp people involved with the JWSDP WS tutorial documentation). If I get 5 or more different people responding I will loose some sleep for the good of this community. Otherwise, I will just try to help you when I have time to read the forums.
    Kuba

  • Error while creating service tickets

    Hi all,
    we are facing the followin error when we try to create a service ticket in WEB UI.
    Version CRM 7 with EhP1 installed.
    Please find the error details
    Context initialization failed in view ICCMP_BTPARTNER/PartnerTable of UI Component ICCMP_BTPARTNER
    An exception has occurred Exception Class  CX_CRM_IC_JEXCEPTION - Exception CX_CRM_IC_JEXCEPTION occurred (program: CL_CRM_IC_MCM_SESSION_PROXY===CP, include: CL_CRM_IC_MCM_SESSION_PROXY===CM00C, line: 28). 
    Method:  CL_CRM_IC_MCM_SESSION_PROXY=>GET_LOGON_STATUS 
    Source Text Row:  28
    Initialization of view ICCMP_BTPARTNER/PartnerTable of UI Component ICCMP_BTPARTNER failed
    An exception has occurred Exception Class  CX_CRM_IC_JEXCEPTION - Exception CX_CRM_IC_JEXCEPTION occurred (program: CL_CRM_IC_MCM_SESSION_PROXY===CP, include: CL_CRM_IC_MCM_SESSION_PROXY===CM00C, line: 28). 
    Method:  CL_CRM_IC_MCM_SESSION_PROXY=>GET_LOGON_STATUS 
    Source Text Row:  28
    Cannot display view ICCMP_BTPARTNER/PartnerView of UI Component ICCMP_BTPARTNER
    An exception has occurred Exception Class  CX_CRM_IC_JEXCEPTION - Exception CX_CRM_IC_JEXCEPTION occurred (program: CL_CRM_IC_MCM_SESSION_PROXY===CP, include: CL_CRM_IC_MCM_SESSION_PROXY===CM00C, line: 28). 
    Method:  CL_CRM_IC_MCM_SESSION_PROXY=>GET_LOGON_STATUS 
    Source Text Row:  28
    Initialization of view ICCMP_BTPARTNER/PartnerView of UI Component ICCMP_BTPARTNER failed
    An exception has occurred Exception Class  CX_BSP_WD_RUNTIME_ERROR - View ICCMP_BTPARTNER/PartnerTable in component ICCMP_BTPARTNER could not be bound 
    Method:  CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW 
    Source Text Row:  165
    Cannot display view ICCMP_BTPARTNER/PartnerViewSet of UI Component ICCMP_BTPARTNER
    An exception has occurred Exception Class  CX_BSP_WD_RUNTIME_ERROR - View ICCMP_BTPARTNER/PartnerTable in component ICCMP_BTPARTNER could not be bound 
    Method:  CL_BSP_WD_VIEW_CONTROLLER=>BIND_VIEW 
    Source Text Row:  165
    Worker session error in session initialization (SAM_QUEUE NOT SET )
    No categorization schema assigned to application
    I am using IE 7 version. The CRM application is installed in Windows SQL server 2008.
    I have checked and the acitivated all the required service in SICF. The services are running.
    Please guide me through about how to solve this issue.
    regards,
    Chandru

    Hi Chandru,
    Check if the following [thread1|No categorization schema assigned to application area (SERVICE_ORDER.....)] [thread2|No Categorization Schema assigned to application Area] helps you.
    Regards,
    Saumya

  • Error Message when we create a Service Ticket in SAP CRM 2007

    Hi All we are having a serious production issue when we create a S.Ticket in SAP CRM 2007 We get the following error message we are not trying to send any information to R/3 We have a planned go live this saturday. So any help would be greatly appreciated.
    An error occurred in system EDIES during account assignment
    Message no. CRM_ORDER_MISC 060
    Diagnosis
    Errors occurred when assigning an account assignment object to a business transaction. To view the error message, see the accompanying log file.
    Transfer Log
    No controlling type could be determined (Notification E IAOM 012)
    No controlling type could be determined (Notification E IAOM 012)
    Regards
    Sathya

    Hi,
    I have looked into your issue.
    For this service ticket, kindly check the Org Unit maintained in Transaction and table OFIC_BILLORG_SRV are same. If not same kindly make changes in the following path in SPRO.
    ==> SAP Implementation Guide
    ==> Customer Relationship Management
    ==> Organizational Management
    ==> Cross-System Assignment of Organizational Units
    ==> Assign Billing Units to Service/Sales Organizations
    If the above information is not helpful kindly take a look at note 861116.
    I hope this helps.
    Regards,
    Venkat

  • On Workflow completion in ECC create Service ticket in CRM

    Hi Experts,
    Our client requirement is to create service ticket in CRM on completion of work flow in R3 system.
    Can anyone please advice me how to achieve the above requirement.
    Thanks in advance
    Kind Regards,
    Veined.

    Hello,
    You may try to call an RFC FM in CRM from ECC as the last step in your WF.
    Regards,
    Sharif.

  • Web Service to Create a Document Info Record with attachments (e.g. PDF)

    Hello guys,
    we are looking forward to create a Web Service that should be able to create a Document Info Record on SAP ERP Application Server. As we don't have installed the SAP Standard Web Services on our SAP ERP ECC 6.0 system we will manually create a Web Service with the help of the standard BAPI_DOCUMENT_CREATE2.
    The current problem is that the Web Service based on the Standard BAPI can not upload Files (PDF or Word files) from the Users Client PC to the Application Server.
    Is there a possibility to Create a Web Service that can handle files and create DIRs on application server?
    Thanks a lot!!
    Regards,
    Christian

    Hello Natallia,
    Well, in this case you don't really need the CV01N transaction. This represents the user interface (UI), and you only need an interface (that is, an API), which in SAP is represented by a BAPI
    I'm not familiar with CRM, but I assume that at some point when saving a Service Contract, you have a BAdI, where you can check the status and insert some custom code.
    So, all you have to do is call BAPI_DOCUMENT_CREATE or BAPI_DOCUMENT_CREATE2 (if available on your installed version), with the required attributes (this can be master data, classification, custom data...). After this function is called successfully, you should receive the document key (DOKAR, DOKNR, DOKVR, and DOKTL). Which you can also save in the Attachments tab.
    Hope this helps,
    Tudor

Maybe you are looking for