Ansicht
Dokumentation

New functionality: Exchanging conditions between different systems. ( RELN31H_COND_INTERCHANGE )

New functionality: Exchanging conditions between different systems. ( RELN31H_COND_INTERCHANGE )

CL_GUI_FRONTEND_SERVICES - Frontend Services   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

New functionality: Exchanging conditions between different systems.

Description

Conditions exchange allows prices and conditions to be copied from or transferred to non-SAP systems or other R/3 systems.
This enhances existing functionality, such as the copying of material data and contract stipulations.

The new functionality supports the transfer of prices (use = A) and arrangements in Purchasing (use = E).

The actual transfer of the data is carried out via intermediate documents (IDoc) and Application Link Enabling (ALE).

On the inbound side:

Since condition types and condition tables are not always the same in the source and target system, you can convert this data in a user exit. You can do this, for example, to

  • Convert condition types in the source system to those in the target system.
  • Convert condition tables in the source system to those in the target system.

You can change the inbound IDoc manually via ALE.
A condition containing errors after transfer to the target system can be re-transferred manually from the source system to the target system at any point.
A detailed log allows you to manually edit conditions in the target system.

On the outbound side:

The change documents created in conditions and price maintenance together with the settings made in the ALE layer determine which recipient system automatically receives which information at what time.
You can also manually select conditions and transfer them to selected target systems.

Since all the information that the target system requires may not always be contained in the conditions, you can modify the functionality in a user exit.

Only conditions that are consistent in form can be transferred.
When errors occur as a result of the system creating intermediate documents, you can repeat transfer of the data.
Transport information can be called up using the standard ALE functions.

Condition relating to arrangements in purchasing can only be transferred manually. Change documents for these conditions are not taken into account by the system.
You can only transfer the condition records and not the header data of the arrangement.
Condition records are automatically assigned to arrangements after transfer. Before you can transfer arrangement-related data, the Customizing settings must be identical in both the source and target systems.
The arrangement must also have the same number in the target system as in the source system before data can be transferred. You can use external number assignment for this.

Software/hardware requirements

Installation information

Effects on System Administration

Effects on Customizing

Effect on batch input

Changes to the Interface

Changes in procedure

Procedure for removing dataset errors

Dependent functions

Planning

Further notes

You make the Customizing settings in the step Cross-Application

components -> Distribution (ALE) for the logical message category
COND_A.






BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3632 Date: 20240426 Time: 205128     sap01-206 ( 50 ms )