Skip to Content
avatar image
Former Member

Service Level is not valid


Hi,

I am getting a message during DTR creation in TM system as "Service Level XX is not valid".

XML failed because of the above error. Service level code which is present in the XML message from ECC system is maintained in the SPRO configuration in the path SAP TM-> SCMbasis->Master Data ->Business Partner->Define Transportation Service Level codes and the corresponding mapping also done.

But still coudnt know what I am missing here. Need help on this.

Thanks in advance.

Regards,

Premalatha. S

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Jun 03, 2015 at 07:26 AM

    Hi Premlatha,

    Have you also maintained Service Level Codes in BP master data (Carrier Role) > Vendor data Tab.

    Please maintain it if not and resend the message.

    BR

    narender

    Add comment
    10|10000 characters needed characters exceeded

    • This is NOT true, I also stumbled upon this in configuration.

      The customizing in SCM Basis is used for CIFing business partners. You know that you can assign shipping conditions to business partner master records in SAP ERP. These are transferred when CIFing the record and mapped into transportation service level codes. For this, you can define a mapping of shipping conditions to service level codes.

      The customizing in FWO management is used when documents (SO, Deliveries) are transferred. The difference here is that there is NO mapping of ERP shipping condition to service level codes. This means that you have to define all the shipping conditions as service level codes with the same ID.

      Not a very straightforward design here, in my opinion: When you connect multiple ERP systems using different shipping conditions (or worse, same IDs but with different meaning!), you can't do a system-specific mapping via customizing, only via BAdI...

  • avatar image
    Former Member
    Jun 10, 2015 at 12:59 PM

    Issue is solved after maintaining the entries correctly in the SPRO config.

    Thanks for all.

    Regards,

    Premalatha. S

    Add comment
    10|10000 characters needed characters exceeded