GTS Waybill API

[former_member449516]

All,

I am facing an issue with the building GTS waybill automatically from our ECC shipment. In our system we have inbound shipments which contain multiple inbound deliveries. These have container handling units which are packed with carton handling units. We have most all the necessary bill of lading information such as freight forwarder, port of origin, destination, etc.

We are using /SAPSLL/API_6800_CFB_SYNCH to try to replicate this data from our ECC system into GTS. However, every time we attempt to execute the function module we are receiving an error. Error is number 219, "There is no busines partner with identification ####" as it seems to not like the freight forwarder we are providing.

We have tried putting the internal GTS busines partner number (with and without leading zeros), the SAP vendor number, and leaving it blank, etc.

We referenced note 2553101 but this does not seem to explain the root cause very well.

Does anyone have any suggestion?

[former_member215181 · Accepted solution]

Hi Kyle,

It seems like you are not providing all of the configured partners.

In configuration, check the Partner Group assigned to your Document Type. The entries in that Partner Group (probably PGCBGN) must all be present in the API call - if not, error /SAPSLL/API_INBOUND 219 ("There is no business partner with identification number xx") is issued, as you describe. For the Forwarding Agent, you must specify Partner Function 'CUSFRW'.

Hope that helps.

Regards,
Dave

[dean_hinson2]

Hello Kyle,

Yep, we found this too. The BP allows the same SCAC code to be assigned to multiple carriers (vendors). Which it should. Since the API is not released by SAP, we took over the development into our namespace and made changes to flush these inconsistencies out of the code.

Regards, Dean.

[former_member449516]

We found the issue as it related to the SLLSCA identification code assigned to the freight forwarder partner. The system required the SLLSCA to be filled in which identifies the SCAC code. Also, it was issuing this error when more than one vendor had the same SCAC which can happen in our ECC system. In some instances, we have created multiple vendors for the same SCAC for financial reporting per region (we have many company codes in use). The GTS system would issue the error stated above when multiple vendors had the same SLLSCA assigned.

[dean_hinson2]

Hello Kyle,

We have implemented this API. Make sure the the business partner has an ID type SLLTEC and that this is passed from the ERP.

Regards, Dean.