3. Scenario
īIn settlement, load shapes or schedules are determined in the
settlement workbench using multiple settlement steps. The
settlement results are updated as result profiles. If we want to
send these profiles, we have to implement another settlement
step.
īSettlement step SENDSUPR can send to service providers that
are allocated to the settlement unit. One can use this settlement
step to control load shapes sent to the settlement coordinator or
supplier etc.
īSettlement step SENDGRIDPR can send data to all distributors in
the grid hierarchy. Generally, the supplier uses this step to send
the schedule to either all or to specific distributors in the grid
hierarchy.
īSettlement step SENDGRSUPR combines the functions of the
two previous steps to make a single step.
4. Important Points
īIn both steps, the existence of result profiles for the allocated
register (business partner of the service provider) determines, to
which service providers one should send data. Therefore, the
appropriate profile headers must already be allocated to the
relevant registers in the preliminary stages.
īOnce the system has determined which service providers to send
profiles to its will automatically trigger the data exchange when the
settlement run has been executed. Basic Data Exchange Process
EXPSETTLPA is used.
īFor details of EXPSETTLPA check this
http://help.sap.com/erp2005_ehp_05/helpdata/en/02/8f30ed3a53
11d6a82a00a0c9303371/content.htm
īMaster Data for IDE
http://help.sap.com/saphelp_erp60/helpdata/en/f5/7ce438276385
5ee10000000a114084/frameset.htm