Skip to Content

Certain field changes in a delivery shouldn´t lead to a compliance check in GTS

Hi all,

our business doesn´t want that a change in the delivery for the field "delivery prio" should start a compliance check in GTS. I learned that in general all fields in a delivery cause a new compliance check in GTS. But is it also possible to exclude certain fields from that logic? Maybe by using a certain BADI?

Kind regards,

Carsten

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Jan 31, 2017 at 03:38 AM

    Hi Carsten,

    There is indeed a Badi on the ECC side to control when a document is sent over to GTS (for a compliance check). Its not clear if you need this for Inbound or Outbound deliveries, there is a separate badi for each level (MM0B/SD0B).

    the Control Badi allows you to prevent sending the document, the trick is how to find if only that particular field (priority) changed or some other field as well - As a small proposal - I`d get a helping hand from SD functional / developer, I think there is a classic SD user exit that compares the delivery document before saving, and delivery document after saving. If the difference between the 2 version is only the delivery priority field, you can send this indicator information `downstream` during the saving event , pick this information in the GTS Badi, which then decides whether to trigger the check or not based on this indicator

    Something along those lines perhaps, hope it makes sense ?

    Regards,

    Branislav

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 01, 2017 at 09:55 AM

    Hi Branislav,

    thanks for the advice. Sounds not too easy ;-) . But I ´ll try it this way, if no other suggestion will follow.

    Kind regards,

    Carsten

    Add comment
    10|10000 characters needed characters exceeded