SAP TM 9.5 - Can we enable EDI 990 to work with RFQ instead of FO number ?

[Sunny_Chiliveru]

Hello,

We have setup the Tendering in TM in such a way that the carrier gets 90 minutes to respond to a load tender. If the carrier does not respond in that time frame, the tender will be rejected and a new tender is sent out to the next carrier.

When the Peer to peer tendering is completed and no carrier responds, a broadcast tendering kicks in and sends tender to all carriers.

Now the issue is, When a carrier receives the broadcast tendering and when he tries to respond, he has to process the earlier peer to peer tender requests sent initially, that means he sents out 3 990's. 2 for peer to peer requests (Inital tender and rejected tender which we sent out due to no response in 90 mins) and then 1 for broadcast Accepted.

Though he Accepts the load, TM is setting the tender rejected because it senses multiple responses from the carrier.

I checked the code base and figured out that 990 is looking at the Freight order number always to process. My thought is to make the 990 work with RFQ number rather than Freight Order number OR may be in conjunction so that the reponse will target the right RFQ in the Freight order and does not reject the load as part of final response from carrier.

I am not sure if there is any standard process aleady. Please let me know if you already have this setup in your system this way Or any other ideas on how not to get the tender rejected with multiple responses. Any pointers will be helpful .

Regards,
Sunny Chiliveru.

[yannicktuemmler]

Hi Sunny

you might want to check out the version_ID of the RFQ. This is updated with every RFQ & is part of the outbound message already. If the carrier sends this together with the FO all 990 based XML will fail where the version ID is not the current open RFQ for this carrier