Ansicht
Dokumentation

COA Determination ( RELNISM_402_HT_COA_PART )

PERFORM Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Short text

COA Determination

Description

COA determination has been changed as follows in Release 4.02:

1. Partner access sequence
   

Prior to Release 4.02, a COA was only assigned to an order in the following cases:

• If the advertiser or their group parent is the COA holder.

• If the advertiser is a beneficiary of the COA.

As of Release 4.02, you can define the partner access sequence yourself.

1. Conflict control
   

Prior to Release 4.02, an assignment that qualifies for discount was selected from several potential COA assignments using fixed rules that were programmed in the system.

As of Release 4.02, you can define conflict control yourself.

1. Partner access sequence and conflict control in COA determination
   

Temporary assignments are initially created for all potential COAs for an order. A "potential" COA is a COA where a business partner who is assigned (in a particular function) is also assigned to an order at the same time (in an additional specified function). The functions used to select COAs are determined in a partner access sequence. You can check additional functions in the customer exit SAPLJHAC 009.

The system only creates a temporary assignment if the order fulfills particular requirements that are assigned to the COA.

The system divides these temporary assignments into up to three groups and selects an assignment for each group that qualifies for discount or bonus. (Therefore, there may be up to three discounts). The remaining temporary assignments are deleted or created as parallel assignments that only count towards COA fulfillment, depending on the settings you have made. Rules for selecting assignments that qualify for discount or bonus are summarized in a conflict control.

Assignments created contain the COA conditions (discount, bonus, fixed quantity price) that are defined during COA discount determination and transfer these to order pricing.

Following pricing, the system enters the assessment basis for these discounts from the order pricing procedure in the assignments and totals these in the COA standing. The same applies to the number (e.g. 1 placement) and the quantity in the order (e.g. 0.5 pages), that can however also be influenced by positioning factors.

Dependent functions

The interfaces for the function exits EXIT_SAPMJHW1_001, EXIT_SAPMJHW1_002 and EXIT_SAPMJHW1_003 only contain an additional business partner table with functions and not the tables for agencies, agents and beneficiaries.

The example reports RJHABN02, RJHABN03 and RJHABN05 for printing output have been adjusted to the new data structure.

Installation information

All business partners for the COA are found in the new database table JHTVGPZ that is filled for COAs that already exist by the conversion program RJHXPRAO with the COA holder, agencies, beneficiaries and agents from the previous tables.

Effect on batch input

If you import COAs from an external system (using Report RJHADU02), it is still possible to transfer data records for agencies, beneficiaries and agent assignments that are then copied into table JHTVGPZ.

The system creates batch input sessions for errored COAs that are used to fill the new business partner screen. Old batch input sessions that were created during COA transfer prior to Release 4.02, are no longer run in Release 4.02.

Effects on Customizing

Check the Customizing settings you have made under COA Determination and Update and assign the partner access sequences and conflict controls to your sales areas that guarantee previous system response.

The partner access sequence settings that can be made (such as exclusivity), mean that the Use of group COAs indicator that existed prior to Release 4.02 (in Customizing in the sales area-specific settings for COAs) has become superfluous. The partner access sequences V000, V001 and V002 supplied, simulate previous system response for values 0, 1 and 2 in this field.

The conflict control settings that can be made, mean that the Conflict control for COA determination and the Parallel COA indicators that existed prior to 4.02 (in Customizing in the sales vearea-specific settings for COAs) have become superfluous. The conflict controls K000, K001, K002 and K003 supplied, simulate previous system response for values 0, 1, 2 and 3 in the Conflict control for COA determination indicator.

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

Length: 6007 Date: 20240602 Time: 041528     sap01-206 ( 105 ms )