How to activate TM Forwarding Order for GTS Preference LTVD worklist

[former_member755706]

Hi SAP GTS Gurus

We have TM to GTS system integration. Forwarding orders are transferred to GTS via XML thru middleware. TM is embedded with S/4 HANA with all master data residing in S/4. No documents are created in S/4. TM Forwarding orders go thru GTS compliance and they are used for the creation of customs declarations as well.

We now need to activate these Forwarding Orders for Preference management in GTS. Is there a standard option to activate these for LTVD worklists in GTS. We were hoping to create a custom program in GTS to add them to the preference LTVD worklist. What will trigger the inclusion of these documents into the worklist stream? Needless to mention that "Control Settings" does not exist for these documents in S/4 from what I know.

Please advise

Thanks - Arvind

[mouaz_benredjeb · Accepted solution]

Hi Arvind,

Having a closer look at the tables you populated to call FM /SAPSLL/API6800_PREVDWLI_SYNCH, I noticed now that field RELTY in the item table is blank.

It should be set to value 1 (= Active Vendor-Material Relationship).

Please give it a try changing this value.

Hope this helps.

Mouaz

[mouaz_benredjeb]

Hi Arvind,

Let's please put aside for a a minute the technical question you asked. 🙂

May I ask you first what you are trying to achieve from a business or customs perspective by allowing the Forwarding Orders to feed the LTVD/LTCD worklist?

As I imagine you already know, the LTVD/LTCD worklist is the GTS tool to issue positive or negative LTCD statements to the customers. The LTCD is (as far as I know) legally binding and hence must accurately indicate the preferential country of origin of the goods supplied to the customer (in case it is possible to identify this country of origin).

So, this is why I am asking you my question from a business/customs perspective: How and what is the benefit of having the Forwarding Order to issue an LTCD and eventually at the end provide the customer with the preferential country of origin of the goods supplied?

Regards.

Mouaz BEN REDJEB

[former_member755706]

Hi Mouaz

Guess I would be needing some more help from you if it is ok.

For LTCD I used FM - /SAPSLL/API6800_PREVDWLO_SYNCH ( Please correct me if this is wrong and whether I shall be using /SAPSLL/VD0_WORKLIST_6800 instead)

Got the below Message when I ran a test data.:

Please advise

Thanks - Arvind

[mouaz_benredjeb]

Hi Arvind,

As this is a new question, please open a new thread.

Bu doing so, it is easier for other participants to find the right thread for the right question/topic.

As well, as each thread is marked as solved or not solved, having a separate thread allows to filter on the solved question when browsing through the forum.

Thanks.

Mouaz

[former_member755706]

Bingo!!!! It worked.

Thanks, Mouaz - Greatly appreciate your help.

We are now starting to work on the customer LTCD. Will seek your help if needed.

Thanks again

Arvind

[former_member755706]

Hi Mouaz

The issue is that even though I do not get any error when running the FM, there is no entry made in table /SAPSLL/PREVDWLI. It is totally empty. I am pretty familiar with Preference Management in GTS so I am using data that would be relevant.

In debugging we find that while filling data in /SAPSLL/PREVDWLI at one point it tries to fill /SAPSLL/PREVDWLD which has just 5 fields plus a GUID entry field for /SAPSLL/PREVDWLI. We want to know what are the parameters it is seeking under what logic. Are there other tables involved? Unfortunately, we do not have a standard setup where we can push an actual PO from S/4 and debug it

Any suggestion? All help is greatly appreciated.

Thanks - Arvind

[mouaz_benredjeb]

Hi Arvind,

There are many many reasons why the integration of the POs Material and Vendor will fail to show up in the LTVD worklist.

The most common reason is that there is already an entry in the WL for the same Material & Vendor. The system will not add a new entry in the WL in such cases as one 1 entry is sufficient for the purpose of the WL.

The other common reason is that an LTVD for the same Material & Vendor has already been issued/requested for the same period. Again, the system will not add a new entry in the WL as a previous entry (for the same period) has already been used to request an LTVD. If the system would have recorded the new entry in the WL, you could ending up issuing 2 LTVDs for the same product/vendor/period, so this is why the WL is not updated.

These are 2 examples but there are many more that could explain why the WL is not populated as expected (e.g. Specific activation of Vendors for LTVD, existence of master data, etc...)

To start, I would suggest that you:

- Check the content of table /SAPSLL/PREVDWLI in order to find out if an entry for the same product/vendor already exist (This is the most common reason)

- Have a look at OSS note "1353683 - FAQ for vendor-based long-term vendor declarations" which gives lots of hints about how the WL works

Hope this helps.

Mouaz BEN REDJEB

[former_member755706]

Hi Mouaz

We have been exploring FM - /SAPSLL/API6800_PREVDWLI_SYNCH. for a while now. However, when we run it even if we do not get any errors we do not see the PO in the PO worklist. Could you please advise what could be the reason and where should we look to resolve this? Please check the screenshots below for your reference:

Header Input

Item input page 1

Item input page 2

Result

Thanks a lot for your help

Arvind

[mouaz_benredjeb]

Thanks Arvind for the complement of information.

Based on the latest information you have provided, I would suggest to create a new interface between your legacy system, where the POs are created, and SAP GTS, in order to mimic the standard integration of POs.

In my opinion, this makes more sense rather than having to create a new interface from TM to GTS.

The development effort is I would say the same (both solutions require a new interface anyhow). And having the interface between the legacy system (POs) and GTS is closer to the standard foreseen solution by SAP, plus having the advantage of feeding GTS with PO data ( think about the case where no forwarding order is existing for instance) rather than with "transportation" data.

To do so, for the new interface Legacy system to GTS, you would need to implement an RFC call of FM /SAPSLL/API6800_PREVDWLI_SYNCH.

Additional info: This RFC FM /SAPSLL/API6800_PREVDWLI_SYNCH is the same used for both the standard interface of POs and GRs. So you may consider as well creating the interface GR in the Legacy system to GTS (in case the Legacy system has GRs or a similar object).

[former_member755706]

Hi Mouaz

There is no document created in S/4, neither PO nor SO, any related documents. These POs and SOs are created in non SAP legacy systems that create these forwarding orders via interfaces. Only documents that pass thru to GTS are from TM system and they are Forwarding Orders and related Freight Orders. The forwarding orders come into GTS as outbound or inbound customs documents.

We simply want these export and import customs documents created referencing the forwarding orders to show up on the two worklists for preference management.

We are a manufacturing company otherwise why would we calculate preference status.

Meanwhile, we already have done a lot of R&D and are now exploring some relevant tables in GTS. Should you have a technical design map, please do let me know.

Thanks - Arvind

[mouaz_benredjeb]

Hi Arvind,

As you have wrote it yourself:

(The LTVD worklist) This will give us the list of all the product and material combos which have had recent purchases

This is one point I wanted to get to when I asked you what you wanted to achieve: How is the Forwarding Orders going to help you to identify the "purchased products/materials"? It probably helps to somehow identify the "transported" goods (Disclaimer: I don't know enough TM) but how will it help you to identify the "purchased" goods?

So this is one sticky point for which I am dubious if the Forwarding Order is the perfect fit to identify the purchased goods.

OK, let's assume you can identify the "purchased" goods using the Forwarding Order, to whom will you be issuing the LTVD then? Surely, the LTVD request has to be sent to the goods supplier/vendor.

• If you are a trading or manufacturing company and if you have a Forwarding Order, this probably means you already issued a PO to the goods supplier/vendor, so why not use this PO to feed the LTVD worklist then?
• If you are a Freight Forwarding company, why would you want to request an LTVD? And to whom would you request this? To the company instructing you to transport goods? And why would know the preferential origin of the goods if you are only transporting goods?

I am really struggling to understand why the Forwarding Orders could/should be used to feed the LTVD worklist. Please understand me: It is not that I do not want to give you the technical answer you are expecting, I am trying to figure out if a technical answer would be actually solving a real business problem.

Talking of which, may be it is a good idea to provided us with a Business example where it makes sense to use the Forwarding Order to feed the LTVD WL and finally where the Forwarding Order would be used to get the legally binding LTVD from the goods supplier/vendor. I am sure such Business example will give enough hindsight to justify the use of a Forwarding Order to feed the LTVD WL.

Appreciate your help and contributions to understand better the requirement.

Regards.

Mouaz BEN REDJEB

[former_member755706]

Hi Ben

Lets for example take LTVD worklist. This will give us the list of all the product and material combos which have had recent purchases and are missing the LTVD in the system. The worklist is a standard GTS guide to facilitate LTVD solicitation from the vendors. We want to convert the inbound Forwarding orders from TM to behave like Purchase Orders from S/4 so that we can utilize full GTS functionalities related to the process. The same is applicable to LTVD for customers which we will issue based on outbound forwarding orders acting as billing documents.

Hope I am able to explain the reason we need the technical help.

Thanks - Arvind