Ansicht
Dokumentation

ISM_KOND_EOB_1 - Set Up Condition Technique for Revenue and Partner Object Determination

ISM_KOND_EOB_1 - Set Up Condition Technique for Revenue and Partner Object Determination

CPI1466 during Backup   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Revenue objects are usualy derived from data that is produced from basic booking units in the schedule lines for a billing dataset. Every organization wants to be able to group their schedule line data in a flexible manner that meets their requirements.

One example of this would be grouping ad insert schedule lines by publication and edition where each group is to represent one revenue object.
Another example would be grouping basic booking units within a combined booking unit as "own" and "external" booking units, since distribution records are only to be created at this level and information about statistics and controlling is also only required at this level.

You can also determine a partner object at a level that is appropriate for your organization (such as for each sales organization and booking unit) if a partner settlement is required.

The condition technique gives you flexible control. It gives you two options that are crucial in defining revenue objects:

  • You can define the level of detail for revenue objects using key fields in those condition tables that are used for condition accesses during revenue object determination.
  • The new general data determination functionality allows the condition technique to display attributes from condition tables and key fields in a flexible way. This means that any data that you require can be displayed in addition to prices and accounts. The primary use of this functionality is to determine partner objects.

Revenue and partner object determination is performed for each schedule line. Data that is usually transferred from the schedule lines to pricing is recorded in the data dictionary structure JHFE_EVOBJ_SEARCH_STR (entries made according to the item type and data involved).
A revenue object corresponds to the condition record found and corresponds therefore to the specific features of the key fields. If the same condition record is determined for two schedule lines, the system regards both of these schedule lines as a unit.

Please note that this type of combining means that subsequent functions (revenue object valuation, partner settlement object determination, statistics, ...) can only use data that is found in the condition record for the revenue object. Data that was available during revenue object determination can no longer be identified uniquely.
CO account assignment (internal order,...) that was determined for the master data objects may also no longer be unique. In this case, the system still combines here and only transfers the first CO account assignment.

You can reuse your current condition tables for revenue object determination. Assign an additional access sequence that you want to use for the revenue object determination condition type if this is necessary (see also Pricing procedure for determination of revenue/partner object under the Settlement node). If you specify the condition type thnat has already been maintained as a reference condition type in the condition type, you can use the data that you have already maintained here.

Define a condition table with the publication and edition key attributes. Assign this to a suitable access sequence and the respective condition type. Maintain the relevant combinations of publications and edition. The publication and edition referenced here are used to access revenue object determination for each schedule line. The same condition record, i.e revenue object is found for schedule lines that have the same publication and edition. The system combines these schedule lines from a revenue object perspective. The system can only use the publication and edition information for subsequent revenue object valuation. This means that you should only record distribution percentage rates at this level. The basic booking unit from which the schedule line was derived is for example no longer available for subsequent partner settlement object determination.

  • Define a condiiton table with the sales organization (VKORGAU), booking unit (BEINH) and partner object (ISM_PFOBJ01) fields.
  • Switch to the technical view.
  • Deselect the checkbox field for the "Partner object" key field. In doing so you copy this field into the variable data part of the condition table.
  • Activate the table.
  • Assign document structure KOMPAZD and document field ISM_PFOBJ to table field ISM_PFOBJ01 in an access sequence.
  • When you enter condition records in this table, you can now also record a partner object.
  • When this condition record is accessed successfully in the order, the system copies the partner object recorded here into the revenue object document.
  • Check whether the account asssignment field exists in KOMP and KOMG. Include it as required and add it to the list of admissible fields.
  • Define a condition table with the booking unit and account assignment as key fields and the partner object as a variable field.
  • Maintain the condition table in the access sequence and condition types for revenue object determination and revenue object valuation.
  • Record the condition records. You can record a percentage rate and the partner object here.
  • Use EXIT_SAPLJHEF_001 to select the account group from the basic booking unit and copy the value to KOMP and therefore to revenue object determination.
  • During revenue object valuation, the system automatically makes all revenue object fields in the KOMG structure available. If the same fields have different names in the KOMG structure than in the pricing communication structures KOMP or KOMK, you should use EXIT_SAPLJHEF_003 as required to transfer fields with different names from KOMG to KOMK or KOMP during revenue object valuation.






rdisp/max_wprun_time - Maximum work process run time   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 6502 Date: 20240329 Time: 022333     sap01-206 ( 165 ms )