Kontakt

Ansicht
Dokumentation

Restrictions to IDE Functions ( RELNISU_462_IDE_NEGATIVE )

Restrictions to IDE Functions ( RELNISU_462_IDE_NEGATIVE )

RFUMSV00 - Advance Return for Tax on Sales/Purchases   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Restrictions to IDE Functions

Use

The functions available in this release do not yet cover the complete scope of functions in the Intercompany Data Exchange (IDE) component. Note that restrictions also exist in the IS-U standard functions.

The data model and general design of the IDE functions were selected to meet the requirements that have so far come from the North American and European markets. However, note that in detail the functions are oriented towards the North American market. Other markets that use different functions can take the function supplied in IDE as templates and then adapt them to their requirements.

The detailed functions are still heavily oriented towards suppliers that operate as billing agents. To a great extent, these functions have been carried over from the last release. Elements necessary for the complete integration of a supplier that does not operate as a billing agent (and therefore acts as the oppposite number to the above supplier) are missing.

There follows a list of the main restrictions to the IDE component. It is based on previous market requirements and cannot be considered to be complete.

Restrictions to IS-U standard functions

  • Billing-relevant device installation not possible
Scenario:
From a supplier's point of view, the consumption of several points of delivery has to be processed in billing together. This leads tp problems as one contract has to be created for each point of delivery. The standard solution to this in IS-U is the billing-relevant installation of all the regsiters to be aggregated in a single installation.
Do not choose this option as communication takes place on the level of the individual registers. It is not clear how, for example, the omission of individual points of delivery would affect the billing-relevant construct.
Alternatives include an outline contract for larger customers. In some markets you can also combine several points of delivery and then request a single point of delivery in their place.
  • No adjustment reversal
We have not evaluated the consequences of carrying out an adjustment reversal, especially how it affects automatic data exchange. If the processing events for reversal, billing and invoicing are active then refrain from using an adjustment reversal.

Missing functions

  • We do not support the storage of electronically transmitted historical consumption data.
To use this function you must define your own solution
  • Customers in different distribution grids
If a distribution company has customers in different distribution grids then device numbers may occur twice. This scenario can only be modelled using a workaround that creates different material master records for the affected devices.
  • We do not support transaction statistics from deregulation processes such as enrollments.
  • Issuing of electronic bills
When you send electronic bills from Invoicing, the system can only take into account items from IS-U Billing. Other items, such as SD charges, budget billing plan payments, installment payments, dunning and interestcharges that were intially generated in Invoicing are not contained in the electronic bill.
  • There is no communication interface for inbound and outbound interval data.
  • The system supports a maximum of two billed point of delivery services (distributor and supplier).
  • Change in bill creation from distributor to supplier
There is currently no automatic process that supports either this or the reverse process. You must develop your own solution. As of Release 4.62, the service provider that issues the bill is to be stored in the contract. Since this information is normally historically any changes involve a contract change.
  • There is no interface or associated processes for electronic data exchange involving service requests.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information






TXBHW - Original Tax Base Amount in Local Currency   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4947 Date: 20240520 Time: 200846     sap01-206 ( 89 ms )