Skip to Content

C4C How is the external pricing tickets proces executed if there is no SAP ECC Service Document type


I am setting up a service process with work ticket integration to SAP ECC.

In the ticket (which is not related to a service contract), we want to execute external pricing so the ticket type has been made relevant for external pricing.

Price conditions (prices for spare parts, rates for service products etc.) have been maintained in SAP ECC. The conditions have been configured in C4C. I have activated the communication arrangement for service tickets with Pricing in Service Ticket Follow Up Scenario in SAP Business Suite with web service Request Service Ticket Data from SAP Business Suite

According to the error messages I get when executing [external pricing] in the ticket, I have to make a code list mapping for the data type BusinessTransactionDocumentProcessingType and link my ticket type to a SAP ECC document type. For the (bidirectional) quote, contract, order etc. process this makes sense. But for tickets I do not have a SAP ECC document type equivalent.

The documentation on this topic is quite high level / a bit limited:

When you create a new ticket, based on the selected ticket type, you can request for pricing in the Items tab. In the Items tab, fill in data for Planned Total and Actual Total and select Actions Request External Pricing. The Net Price field gets populated. …. You can maintain pricing data in the Tickets Pricing tab. … You can Request External Pricing only if pricing relevant parameters are set.

More detailed information on the relevant parameters with regards to tickets and external pricing is missing. Do I need a ‘dummy’ service transaction with pricing determination in SAP ECC in order to simulate the external pricing in tickets? Or can I directly point to a pricing procedure? Any tips and tricks are welcome.



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    Jul 27, 2018 at 09:06 AM

    Hi Jameel,

    Thank you for your feedback. In the meantime I came to the same conclusion.

    Based on the customer's process I will map the service ticket type to an SAP ECC debit memo request document type, as this is a document that needs to be created and also refers to the pricing procedure that needs to be checked for external pricing.

    When writing this down i wonder if the price simulation is independent of the document type(s) that need to be created in the next step after the release to ECC? Or can I do the simulation on one document type and create other document types later on?

    And what is the role of the action codes (COD_SERV_PROC_TYPE) in this? I did find the data type ServiceTransactionProcessingTypeCode in the code list mapping, containing the standard action codes mentioned in all documentation, quick guides etc. But how is the service ticket item processing code e.g. SRV1 translated in action code 0001 Service so that among other activities the billing request items will be created?



    Add comment
    10|10000 characters needed characters exceeded

  • Jul 26, 2018 at 10:27 AM

    Hi MJ,

    When an external price is requested from ECC, you are in effect doing a Sales Order Simulation in ECC.

    So the missing code list mapping that you are referring to is to map your Ticket Type to the corresponding Sales Order Document Type in ECC. Your ECC colleagues should provide you the document type that should be used for a sales order simulation.

    Don't forget to also maintain a code list mapping in case the pricing procedure you maintained in C4C is different from the pricing procedure in ECC (very rare to happen).



    Add comment
    10|10000 characters needed characters exceeded