SAP for Oil, Gas, and Energy Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and navigate the evolving energy landscape. Join the conversation today!
cancel
Showing results for 
Search instead for 
Did you mean: 

interface between normal sales cycle to tas

Former Member
0 Kudos

Dear All,

can anyone process the flow to configure the TAS with normal sales cycle ?

Regards

Amit

1 ACCEPTED SOLUTION

Swetabh
Explorer
0 Kudos

TAS interface is used to send load information from SAP-ISOIL to external system (TAS). A middleware could be used for example SAP-XI could be used to communicate between SAP R3 and TAS external system. Also external TAS will send back loading information to SAP R3 after processing. So XI can be used as middleware.

Following loading ifo could be send

  1. pickups

#shipments

#goods movement

#phisical inventory count.

[SAP TAS Help|http://help.sap.com/erp2005_ehp_02/helpdata/en/8b/2d253754df2709e10000009b38f889/frameset.htm]

I can give an example in which loading information is send to XI. Whenever a shipment is created/changed (o4f1/o4f2) , an output type is triggered which sends across the outbound idoc with required data. The XI will send the information to TAS. The TAS will return back the information to XI. The XI will send the information back to R3 (may be using abap proxy) . So in this way loading details are updated automatically in R3 interface,

[PDF file in sdn|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6a7ae90-0201-0010-3a9f-fcef19c944c8]

Some basic idoc types

OILLDD01 – Send loading data from TAS to R/3

OILLID01 – LID Master data distribution

OILORD02 – Sending Contract/Order/ Quantity Schedule data to TAS

OILSHL01 - Send shipment relevant data to TAS

OILLDC01 – Send loading data to 3rd party

OILLDD01 – Forward loading data from R/3 to 3rd Party system

I am not expert in TAS, but i have worked on one such object in my project, so thought of sharing. Reward points if it is helpful.

View solution in original post

1 REPLY 1

Swetabh
Explorer
0 Kudos

TAS interface is used to send load information from SAP-ISOIL to external system (TAS). A middleware could be used for example SAP-XI could be used to communicate between SAP R3 and TAS external system. Also external TAS will send back loading information to SAP R3 after processing. So XI can be used as middleware.

Following loading ifo could be send

  1. pickups

#shipments

#goods movement

#phisical inventory count.

[SAP TAS Help|http://help.sap.com/erp2005_ehp_02/helpdata/en/8b/2d253754df2709e10000009b38f889/frameset.htm]

I can give an example in which loading information is send to XI. Whenever a shipment is created/changed (o4f1/o4f2) , an output type is triggered which sends across the outbound idoc with required data. The XI will send the information to TAS. The TAS will return back the information to XI. The XI will send the information back to R3 (may be using abap proxy) . So in this way loading details are updated automatically in R3 interface,

[PDF file in sdn|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6a7ae90-0201-0010-3a9f-fcef19c944c8]

Some basic idoc types

OILLDD01 – Send loading data from TAS to R/3

OILLID01 – LID Master data distribution

OILORD02 – Sending Contract/Order/ Quantity Schedule data to TAS

OILSHL01 - Send shipment relevant data to TAS

OILLDC01 – Send loading data to 3rd party

OILLDD01 – Forward loading data from R/3 to 3rd Party system

I am not expert in TAS, but i have worked on one such object in my project, so thought of sharing. Reward points if it is helpful.