Skip to Content
avatar image
Former Member

Vendors & Customers Not Transferred to GTP

Hello -

What t-code in GTP will show vendors or customers from ECC that were not successfully transferred to GTP? Currently, I am using /SAPSLL/PARTNER_APPL however this shows a log of ALL vendors & customers that were attempted for transfer. In some cases, a vendor may show up as 'red' (not transferred) one day, but then the issue was subsequently resolved and the next day transferred to GTP.

What t-code can I run to narrow the report down to only not transferred customers & vendors so that I can work on resolving any potential errors?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Sep 23, 2017 at 08:27 PM

    Hi Navneet,

    What is GTP? Is it similar to GTS?

    If so, then you can try checking the transfer log for Business Partners (in the System Monitoring area) - any failures will show up a "red lights" there.

    Regards,
    Dave

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Dave -

      Yes sorry GTP is GTS.

      I am currently reviewing the transfer log for business partners (t-code /SAPSLL/PARTNER_APPL) however this log shows all records that were sent to GTS... both successful and unsuccessful. Also, I am unable to export this data to do a review against my master data tables in ECC.

      Is there another log in GTS that only shows a listing of the business partners that were not successful?

      For example, if a business partner was sent to GTS in June of 2017 but failed due to an email format issue that was subsequently resolved, this business partner would now be in GTS. However, when I review the log I am encountering both instances where partners show as red, but are also in GTS (so I believe the error was since resolved). How do I limit the view to only see which business partners are still in a 'fail' state.

      Thank you,

  • Oct 03, 2017 at 12:16 PM

    Hi Navneet,

    In the IMG (GTS > General Settings) you can configure the log so that it is only saved if errors occur. That might help.

    But since the total log shows a "red" light if ANY error occurs in the run, that may not help too much. Technically, I don't have much more help to offer.

    But functionally - and preferably before go-live - you should analyse each error to provide an action process to clean-up your master data. For example, if some failures are due to missing postcodes, put in an urgent action to harmonise the postcode rules between the systems, and make sure that the field is part of the incompletion log in the feeder system - then no new errors of that sort should occur. And for the existing data, run queries to identify the "bad" records and start a "clean-up" activity to add or change any missing or wrong data. If your organisation is serious about data quality, you should not meet much resistance, and before long, your system will be free of the disease - and you won't have to waste time looking into transfer errors in the future.

    Hope that helps.

    Regards,
    Dave

    Add comment
    10|10000 characters needed characters exceeded