SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

What is significance of table ESERVICE?

Former Member
0 Kudos

Hi all,

In case of de-regulated market, we have a scenario of a different distributor and supplier for a particular customer. In such a case, there will be two installations and two contracts - one each for distributor and supplier on the same POD.

My queries are -

1. how this scenario is represented in SAP (in terms of entries in tables) and what is the role of table ESERVICE in this case?

2. And, when and how the entry in table ESERVICE is created?

3. In this table ESERVICE, the primary key is - VERTRAG. but this VERTRAG has no relation with the one in table EVER (correct me if I am wrong). SO what is the significance of this field and why is it called VERTRAG?

4. Can there be a scenario where there are more than one supplier active on a POD at a particular time slice? If yes, how is it represented in the table ESERVICE?

5. In such kind of scenario, if for a customer distributor and supplier is the same for the customer, how is this scenario maintained in the system? IS there any entry in table ESERVICE?

Can someone provide any material / link for more information on this table?

Thanks

Rohit

1 ACCEPTED SOLUTION

Former Member
0 Kudos

hi;

Answer of your few questions -

You can divides point of delivery services into billable and non-billable services. Billable services are modeled using contracts is IS-U; non-billable services are stored in the new table ESERVICE (point of delivery service).

The point of delivery service has two sub-objects, contract and non-billable service. This does not entail any new levels in the data model. The point of delivery service contains the service provider and the service type. This means that Communication Control can always find the service provider with whom the system has to communicate for each point of delivery.

For the rest informations please have a look

[Link|http://help.sap.com/erp2005_ehp_02/helpdata/en/14/91720b05eb45b6a37dfcc7c299bb4f/frameset.htm]

Regards

Shashi

View solution in original post

2 REPLIES 2

Former Member
0 Kudos

hi;

Answer of your few questions -

You can divides point of delivery services into billable and non-billable services. Billable services are modeled using contracts is IS-U; non-billable services are stored in the new table ESERVICE (point of delivery service).

The point of delivery service has two sub-objects, contract and non-billable service. This does not entail any new levels in the data model. The point of delivery service contains the service provider and the service type. This means that Communication Control can always find the service provider with whom the system has to communicate for each point of delivery.

For the rest informations please have a look

[Link|http://help.sap.com/erp2005_ehp_02/helpdata/en/14/91720b05eb45b6a37dfcc7c299bb4f/frameset.htm]

Regards

Shashi

Former Member
0 Kudos

Hi,

ESERVICE are nothing but non billable services which uses same number range as EVER-VERTRAG.

Please refer to this [Link|http://help.sap.com/erp2005_ehp_04/helpdata/EN/f0/88d63be785476fe10000000a11402f/frameset.htm] for the detailed description.

Regards,

Pranaya