Kontakt

Ansicht
Dokumentation

W_RMA_0001 - Create Condition Table

W_RMA_0001 - Create Condition Table

Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Condition tables are part of the RMA condition technique and contain (movement) data.

To ensure that a table can be used in Customizing for RMA, you must first identify it as a condition table that is relevant for RMA. Only then can it be used for RMA in the following steps.

The condition tables contain (movement) data which is transferred from a non-SAP R/3 system as raw data (via SAP BI). The data is processed in the calculation and then sent back to the condition tables.

Condition tables have different condition categories. A differentiation can be made between the following different categories:

  • Raw data:
    Raw data is taken from BI and is used as initial values for the calculation. The data is period-dependent. It can be transferred to to the feeder system (R/3) but not to SAP BI.
  • Results data:
    Results data is calculated in the course of the calculation. The results data is related to a specific period and can be sent to SAP BI or a feeder system (R/3).
  • Shrinkage:
    These tables contain data with a shrinkage percentage factor that is used to calculate the actual shrinkage. The data is related to a specific time (date) but is not related to a specific period. It can be transferred to SAP BI but not back to the feeder system (R/3).

There are two possible types of condition tables:

  • DSO (BI DataStore)
  • Transparent table

Before the condition tables can be defined, you must first create them in the DDIC (transparent table) or in BI Content (DSO).

The following condition tables are shipped as standard:

  • 0RMA_DS01 (DSO for storing raw and results data)

You can change all of the above data as required using the condition technique. In doing so, only the table category should to be taken into consideration. You can add additional tables.

When creating condition tables, ensure that the tables do not become too large due to the volume of data that they contain.

Data should only be split using the access condition types and not according to valuation levels as no differentiation is made between the valuation levels in the condition technique.

It is appropriate to split the raw data by goods receipts and goods issues since, using access sequences, a selection from various tables is possible.

A different selection is, however, not possible for two sites without previously creating two different calculation schemas with different condition types and access sequences.






RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 2795 Date: 20240523 Time: 155931     sap01-206 ( 49 ms )