Ansicht
Dokumentation

J_3G_PLFIND - Price List Determination

ABAP Short Reference   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Definition

You can define ETM price dependencies here.

Recommendation

You should not make any changes to SAP standard condition tables. Copy the tables and then make your changes.

Activities

In display mode, check to what extent you can use the SAP standard condition tables. If you want to create a new condition table, copy a similar condition table from the standard. To do this, proceed as follows:

• Enter a name for the table that you want to create.

• Define whether you want to create the table with or without a validity period.

• Enter a table type for the condition table (for example, pool table).

• Enter a description for the condition table. Choose the fields that you want to have in your condition table from the list of allowed fields in the field catalog. The fields can be enhanced in the field catalog.

• Generate the new condition table.

Notes

Prices, surcharges and discounts can be made dependent on several fields in the sales document.

Before you create a new condition table, you should check whether the fields in the field catalog are sufficient for your requirements. If you want to use a field in pricing that is not supported with this usage in the standard system, you must enter this in the field catalog.

You can only include fields that are contained in table J_3GPRLKOP.

Dependencies

Condition tables. You define the combination of fields that you want to be able to create Condition records for in a condition table.

Create new condition tables. To do this, copy a similar condition table and proceed as follows:
Enter the name of the table that you want to create.
Please note that you can only use names between 501 and 999.
If you do not make an entry, the system automatically assigns a
sequential number.
Define whether you want to create the table with or without a validity
period.
Enter the table type for the condition table (for example, pool table).
Enter a description for the condition table.
Choose the fields that you want to have in your condition table from
the list of allowed fields in the field catalog. The fields can be
enhanced in the field catalog.
Generate the new condition table.
Note:
If you want to make pricing dependent on the sold-to party, you can
only choose the customer field in the condition table.
You cannot specify the sold-to party in the condition tables since
there are only customer master records.
Only the order document recognises the special function of sold-to party and therefore you can assign the source field "sold-to party"
to the field "customer" when you define the access.
Enter the condition tables in the access sequences (see:
"Define condition types").
By doing this, you set up the connection between condition type, access
sequence and condition record. You can find an explanation of fields in table J_3gprlkop under "System Modification". Proceed in the same way, even if copying new fields to other structures is described here.

BAL_S_LOG - Application Log: Log header data   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 3639 Date: 20240523 Time: 193145     sap01-206 ( 46 ms )