Here is rough overview about all application / functions used by Commission Management solution. Click on the link to get to the right item:Table of Contents
Some of the Commission Management customer functionalities can be called by using the single transactions / the VSS menu. Others happen in background, e.g. like create commission out of the invoice by message.
Here we describe the following maintenance transactions:
- Create commission based on source document invoice
- Create cancellation commission based on source document invoice
- Create manual commission
- Application “commission maintenance report” – ALV
- Application “commission maintenance report” – detail
- Report “mass redetermination”
- Report / interface “transfer to HR”
- Interface “maintenance in external frontend"
Creating commission based on source document invoice
Functional Requirements
The trigger for the creation of a commission based on source document invoice, is the standard message handling of an invoice. In order to setup this process, just create an individual SD invoice message type (application V3) with all corresponding steps (access sequence, message schema, message condition) and assign the “printing” program, which call the creation of commission.
As result, the commission is created automatically in the background, when the message is processed successful. The status of the processing and also the created commission number, you can see in the message protocol / log of the invoice.
Create commission - successful invoice message log
Relevant for a successful creation, is that all customizing settings have been done, like commission type definition and determination, number range definition, item type definition and determination, etc.
To ensure, that there is for each invoice always only one commission, a corresponding check is processed during commission creation.
Create commission - invoice message log with error
If you want to reprocess the creation and start an additional message, you first must delete the existing commission with the reference to this invoice.
During the processing all defined values of the settings, the source invoice, the VSS order the invoice is coming from and the vehicle that is assigned to the VSS order, are stored in the corresponding commission tables. Also, some admin stuff like created by, creation date, etc. are stored.
Create commission - detail view
| Info | ||
|---|---|---|
| ||
You should store (by enhancement) always all values from source documents, that you want to use in calculation. This especially (only) is relevant, when these values could change after commission creation, e.g. like some values in vehicle. Otherwise you will never get a stable calculation result. |
The commission date initially is the creation date of the commission. But this date is especially important, because it is used also for the complete calculation as basis date, e.g. for determination of price conditions, and also to check validity of relevant employee. So, in case the customer defines here different dates as relevant calculation basis, e.g. invoicing date or selling date of the car / car contract date, this date should be updated with BAdI during commission creation.
Concerning the register / table “conditions” nothing happens during the automatic creation. Register and table are initial empty.
Create commission - register "conditions"
Also during the creation, the partner verification and determination is done. Based on the determined commission type definition (main partner) there is a check that corresponding partner role is assigned within the invoice. If the partner role is not in the invoice, no commission will be created.
Is the partner role assigned, the creation checks the settings of “relevant employee”.
Is the partner number not assigned here, the commission will also be created, but with the status, that is assigned to the business operation “CRNR” (Create inactive commission) in the status schema settings, e.g. in proaxia example case this is “0008” (not relevant for HR transfer). In that case the commission result automatically is zero.
Create commission - info & register "participants" when partner is not assigned
Is the partner number assigned in the relevant employee settings, the commission will be created normally with the status that is marked as “initial”, e.g. in proaxia example case this is “0001” (new). In that case the creation checks in addition, if the main partner is part of a valid pool definition. If he is, also all additional partners from pool will be added with the defined pool partner role from commission type definition.
Create commission - info & register "participants" when partner is assigned
When all data of the commission is determined, finally the calculation in formula builder is called and the result is returned to the commission calculation table.
The main idea to show relevant values of the calculation and also the calculation result, is to display them in the HTML view of tab / register “price/commission”.
...
Creating cancellation commission based on source document invoice
Functional Requirements
The trigger for the creation of a cancellation commission based on source document cancellation invoice, is the standard message handling of an invoice – like the normal commission / invoice.
The main difference between creation of a normal commission and creation of a cancellation commission is, that cancellation commission must be connected to the original commission. So, during creation the cancellation commission determines the original commission based on information in the invoice field VBRK-SFAKN (Cancelled Bill.Doc.). When the original commission is determined, the cancellation commission is created depending on the case based on the values of the original commission and the status of the original commission maybe will be changed.
During the creation processing also here defined values are taken from the settings and the source documents (invoice, VSS order, vehicle). But especially the commission values are not calculated new by formula builder. To ensure, that commission value result is 100% like the original commission, they are transferred “1:1” from the original commission. So the following main values are taken from original commission:
- Commission date
- All entries of commission participant table
- All entries of the commission calculation table
Also, if these entries are copied from original commission most likely “1:1”, there could be small differences, because creation of cancellation commission must happen case depended, based on the actual status of the original commission.
- Case A: Original commission is up to now not transferred to HR – “is open”
- Commission date is copied 1:1; this is relevant because of “steering meaning” concerning the check of the employee’s validity
- Partner entries are copied 1:1, just the flag “calculation relevant” always will be initial and the administration data will be updated with actual values
- Calculation entries are copied 1:1, just the administration data will be updated with actual values
- Status of the cancellation commission will be directly set to the target status of business operation CRCA (or function module logic) which should be a status from type “canceled”
- Status of the original commission will be changed to the target status of business operation CANC (or function module logic) which should be a status from type “canceled”
- The objective is that cancellation commission has the same value results, both commissions are no longer changeable and both commissions are not relevant for the transferred to HR
- Case B: Original commission is already transferred to HR – “is in HR”
- Commission date is copied 1:1; this is relevant because of “steering meaning” concerning the check of the employee’s validity
- Partner entries are copied 1:1, just the administration data will be updated with actual values
- Calculation entries are copied 1:1, just the posting information will be cleared and the administration data will be updated with actual values
- Status of the cancellation commission will be directly set to the target status of business operation CRCA (or function module logic), which should be a status from type “ready to transfer to HR”
- Status of the original commission will not be changed and so still is from type “already transferred to HR”
- The objective is that cancellation commission has same value results, cancellation commission in best case should be no longer changeable, cancellation commission will be ready for transfer to HR and original commission is not changed in any way
| Info | ||
|---|---|---|
| ||
The values on data base level are also for cancellation commission stored always “positive” (okay, if there is negative value from original, this is also negative in commission). These values are also shown always “positive” at the screens. So, when implementing BAdI for the HR transfer you have to take care, that you multiply them by “-1” based on case commission / cancellation commission. |
So, the header information of a cancellation commission most likely is similar to a normal commission. There is just an additional checkbox, showing that it is a cancellation.
Create cancelation commission - detail view
Concerning the register / table “conditions” also for cancellation commission nothing happens during the automatically creation. Register and table are initial empty.
Create cancelation commission - register “conditions”
Concerning the register / table “participants”, we have case depended the situation described above.
- Case A: Original commission is up to now not transferred to HR – “is open”
Create cancelation commission - register “participants” in case original commission is still open
- Case B: Original commission is already transferred to HR – “is in HR”
Create cancelation commission - register “participants” in case original commission is already transferred
Concerning the register / table “price/commission”, we should see the same information like in the original commission (because of copy all entries of commission calculation table 1:1.
Create cancelation commission - register “price/commission”
| Info | ||
|---|---|---|
| ||
Because the design of the HTML view will be defined customer individual by using own elements with own structures and own BAdI logic, we can’t ensure that we will see here always 1:1 the same information like in original commission. So, during creation of the HTML view (elements/structures/BAdI) you should always keep in mind, that also the cancellation case should show same information. |
| Info | ||
|---|---|---|
| ||
Because in some cases the cancellation commission also has to update the original commission, the original commission must be changeable during cancellation commission creation. If this is not possible (e.g. original is locked by a user) the processing of the cancellation invoice message fails and must be reprocessed |
Create cancelation commission - log in case of error
Creating manual commission
Functional Requirements
To create a manual commission, there are two possibilities – by separate transaction “create commission” or out of the commission report ALV list (via icon ). In both cases the user gets the same screen to enter the manual commission data.
Create manual commission - creation screen
When all relevant values are entered and confirmed with ENTER, a new commission without connection to a source document is created.
Comparing to the creation out of a source document, there is no check, if such a commission already exists. So theoretically, you can create the same manual commission several times – if you like to do .
During the processing also all defined values of the settings are stored in the corresponding commission tables. Also some admin stuff like created by, creation date, etc. are stored.
Create manual commission - detail screen
The commission date here also (like in source document based commission) will be the creation date of the commission. But this date is not so relevant in a normal manual created commission, because you usually create to set it with a fix commission value (not a calculated value).
The entered values from creation screen, you will find initial in the register / table “conditions”.
Create manual commission - register “conditions”
The definition which conditions are shown at the creation screen and which price conditions are used to store them in the commission condition table is done by the customizing / settings of commission type definition.
Example 1 – one value: Example 2 – two values:
↓ ↓
↓ ↓
Create manual commission - steering of available conditions at creation screen
Also during the creation, the partner verification and determination is done. The logic here is like the source document based commission creation.
Create manual commission - register “participants”
When all data of the commission are determined, finally the calculation in formula builder is called - okay, normally not so interesting in case of manual commission with fixed value and the result is returned to the commission calculation table and shown in tab / register “price/commission”.
Create manual commission - register “price/commission”
Function “commission calculation”
Functional Requirements
The commission calculation happens mainly in the formula builder. Here we define for each calculation scheme the corresponding calculation logic, which is assigned to a commission type.
The calculation is called in the background at each time we create a commission or when we change the values of the commission.
The main result of calculation is the total commission vale, which then is always divided to the actual assigned and active participant based on their percentage / fix value. The distributed values are stored for each relevant partner in the commission calculation table.
For more information, please see corresponding description in chapter “Maintain Predefined Condition Text Entries” (linkowanie uzywajac kotwicy?)
Usage
Definition of predefined text entries for a single manual price condition within the commission.
- T-Code: /DBME/PMA_ACNDR
Maintenance screen:
Maintenance view for predefined condition text entries
- If here for a manual price condition no entry exist, the text in the condition is open for free text entry.
- If here for a manual price condition only one entry exist, this text entry automatically is set for the condition in the commission.
- If here for a manual price condition several entries exist, the user must choose one of this text entries from provided list. Only these entries are allowed.
To enter translation for the text entries, choose “Goto” → translation”.
Authority check
- No specific authority check
Maintain calculation logic (formula builder)
Application “commission maintenance report” - ALV
Functional Requirements
Entry to the main application of commission management to manage the created commissions.
At the selection screen, the user defines the criteria to reduce the shown commissions, that are relevant for the actual processing case. As result all corresponding commissions are shown with the main / defined information in a single ALV screen. To get more detailed information, a single line can be selected by single click and the commission detail screen appear. In addition, there are several functions available to handle the commissions.
In this chapter, the main selection screen and the ALV screen incl. the available functions are described.
- T-Code: /DBME/PMA_PROV
Selection screen:
To get a better usability, the standard selection screen is divided into two separate register.
In the first register, called “Main selection”, you can define the selection criteria for:
- Main commission data at header level
- Commission status data at header level
- Commission partner data at participant level
- Commission vehicle data at header level
And at the second register, called “admin. data”, you can define the selection criteria for:
- Commission creation and last change data at header level)
- Some addition commission parameters at header level)
Commission maintenance report - selection screen areas
Optional, the customer has here the possibility to enhance the selection screen / selection logic by additional fields. To get more details about this enhancement possibilities, please see chapter with BAdI enhancements.
Selection type:
In addition to the standard report variants, the customer can define own “selection types” within the DBM|E commission report solution.
Commission maintenance report - selection type
One idea behind these selection types, is partially like the report variants. In both cases, some fields of the selection screen could be “pre-filled” with default values.
But the main advantage of such a selection type is, that they can handle more complex “filling logics”. The reason is, that they are handled by corresponding BAdI coding. In addition, also some more settings, e.g. layout of result ALV list, … can be set by BAdI enhancement based on the selection type. To get more details about this enhancement possibilities, please see chapter with BAdI enhancements.
But no advantage, without any disadvantage - comparing variants, the selection types must be defined by IT department (incl. development) and not easily from user, by saving the actual settings like it is for variants.
ALV screen:
As result, the user gets a normal ALV list reporting with all corresponding commissions.
...
For each commission, the main information on header level is shown in one single line. If relevant, the customer can add own / additional fields. To get more details about this enhancement possibilities, please see chapter with BAdI enhancements (tutaj robic kotwicę?).
The title of the list, is a concatenation of report name, the chosen selection type value and the number of selected commissions.
Available functions:
Next to the SAP standard ALV functions 
, like sort, filter, sum, print, … and the general report standard functions like cancel, back, …, the DBM|E commission report provides the following additional functionalities:
Function “refresh” 
(icon in push button line / in menu “commissions”)
Refresh the shown data based on the selection criteria entered, when starting the report. So, commissions can disappear, in case, they have been changed in the meantime, but also some new commissions can be added to the list, because they now fit to the selection criteria.
Function “create manual commission”
(icon in push button line / in menu “commissions”)
Calls the screen to create a new commission manually. To get more details, please see chapter with “creating manual commission”.
Function “status mass change” (push button 
in ALV icon line)
Mark all rows in the ALV, where the status should be changed and press button “set status”.
A popup with all for the selected commission possible status values appears.
Commission maintenance report - ALV mass status change
| Info | ||
|---|---|---|
| ||
The popup shows the collection of all possible status values for the marked commissions. To get the list, for each single commission the possible status settings are determined based on the actual status and collect them into the list. So, for some commissions the combinations of actual status and in the popup provided status could be impossible. But the system cehcks this during processing and shows a corresponding message in the update protocol. |
Select a status by single click at the status line and if relevant, enter an additional comment.
| Info |
|---|
Comments are added to each single commission status change, which is successful processed. |
Commission maintenance report - ALV mass status change log
After status mass change the ALV automatically process the refresh function.
| Info | ||
|---|---|---|
| ||
The following commission flags (set by business operations) do not longer allow a status change: |
- Deleted
- Canceled
- Posted into HR
Function “change”/ ”display” (entry in menu “commissions”)
In case a single line of the ALV list is marked, these functions call the commission detail screen in change mode / in display mode. In case no line / several lines are marked, an error message appears.
Function “delete” (entry in menu “commissions”)
Mark all rows in the ALV, which should be relevant to delete and select function “delete” in the menu.
Commission maintenance report - ALV mass deletion
Now system show security message, which is to confirm.
Commission maintenance report - ALV mass deletion popup
In case security question is confirmed with “yes”, the business operation “DELE” is processed.
- Commission status is changed to the corresponding status (based on status settings for DELE)
- The flag “deleted” is set in commission header
- When flag deleted is set in commission header, corresponding icon is shown in ALV list
- Show processing protocol
Commission maintenance report - ALV mass deletion log
After mass deletion, the ALV automatically processes the refresh function.
Function “recalculate” (entry in menu “edit”)
Mark all rows in the ALV, which should be recalculated and select function “recalculate” in the menu.
In case the user has the corresponding authority the recalculation for the selected commissions will be processed.
As result the processing protocol is shown.
Commission maintenance report - ALV mass recalculation log
“Hyper Links” (direct in ALV list)
In the ALV list, some fields have a special function. …
- Commission number
- Call the commission detail screen for the corresponding commission.
- Reference document (invoice number)
- Call the corresponding invoice in display mode (T-code VF03).
- Long text icon
- Just appear, in case there is a long text created for the corresponding commission.
- Shows for the corresponding commission a popup with the actual long text in display mode. Details about how to edit a long text / the general text logic see in commission detail functions.
Application “commission maintenance report” - detail
Functional Requirements
Detail commission maintenance screen in commission management
At the selection screen of commission report, the user defines the criteria to reduce the shown commissions, that are relevant for the actual processing case. As result all corresponding commissions are shown with the main / defined information in a single ALV screen. To get more detailed information, a single line can be selected by single click and the commission detail screen appear.
Alternative, a direct access (without commission report) is possible by commission change / display transactions.
In addition, there are several functions available to handle the commissions (independent how detail screen is started).
In this chapter, the detail maintenance screen incl. the available functions will be described.
- T-Code: /DBME/PMA_PROV (by click at single commission)
/DBME/PMA_PROV02 - Change commission
/DBME/PMA_PROV03 - Display commission
Detail screen
In standard the detail screen shows general header data (org. data and status information), main vehicle and customer data and in the different tabs, the calculation result, the conditions, the participants, the status history and some administrational data.
Commission maintenance report - commission detail
| Info |
|---|
Because the customer requirements are very different (could be case depending, but also including own customer fields) and the complete screen is based on GUI Framework and the complete content in tab “price/commission” is based on HTML Framework, the final customer solution can look different. To get more details about “screen replacement” see the corresponding chapters of settings (to assign own screens) and also of BAdI enhancements (to handle data of own screens). |
If the auto. recalculation for the actual commission type is active and the status of the commission allows changes, the commission calculation will be processed in background during calling the detail screen.
- Available functions:
In addition to the here described detail functionalities, there are also some of the ALV functions (described in chapter before) are available (in case ALV list is toggled on).
Commission maintenance report - ALV function in detail view
E.g. it is also in detail screen mode possible to mark several commissions and process mass status update function.
Function “display / change” (icon 
in push button line / in menu “commissions”)
Change the processing mode of the commission detail between “change” and “display”, depending on the actual mode.
| Info |
|---|
In case you are in the change mode and select any commission in ALV list via click, it is possible, that you get an error message “operation not allowed” and commission is opened in display mode. |
Function “check object” (icon 
in push button line / in menu “commissions”)
Process a complete check of the actual commission in detail screen. It checks the data concerning completeness, but also concerning data consistence.
In each case, an information message appears in the status line, e.g. like:
Commission maintenance report - function "check object" messages
Function “other commission” (icon 
in push button line / in menu “commissions”)
Calls a popup, where user can enter the number of any existing commission. In case the activity is coming out of commission report, the entered commission must not be part of the actual selection / ALV list.
Commission maintenance report - function "other commision" popup
As result the entered commission data is shown in the detail screen.
In case the entered commission number does not exist, a corresponding message appear in the status line.
E.g. 
Function “toggle list on/off” (icon 
in push button line / in menu “extras”)
With the toggle function, the user can switch off / switch on the shown part of ALV list.
Commission maintenance report - function "toggle list on/off”
The function is only available in commission report processing.
Function “save” (icon 
in push button line / in menu “commission”)
Save actual commission data. Function is only in change mode useful.
Function “close (icon 
in push button line / in menu “goto”)
Close the commission detail screen and return to the full size ALV screen.
Function “exit” (icon 
in push button line / in menu “commission”)
Close the commission detail screen and return to the commission report selection screen.
Function “close” (icon 
in push button line / in menu “edit”)
Close the commission detail screen and return to the full size ALV screen.
Function “delete” (in menu “commission”)
Sign the current commission as deleted. This function calls the business operation “DELE”, which set the flag “delete” and also set the commission status based on the assignment from settings (business operation / status).
Function “header long text” (icon 
at screen “Header data” / in menu “edit”)
The function opens a popup, where the user can add / change additional text information (object SAP long text) for a specific commission. The function is also available in case of display mode, but then the text in the popup is not editable.
Commission maintenance report - function "header long text" popup
To ensure that text information is shown also in multi-language countries (e.g. Swiss with DE, FR and IT), the long text information for a commission is always stored in one language. As base for the language, we define the language assigned to the plant from commission.
The long text is sored with following parameters:
- Object: /DBME/P_PR
- ID: 0001 (header long text)
- Language: assigned language from plant
- Name: commission number
Function “redetermine" (in menu “edit”)
The redetermination function is a kind of “refresh commission master data”. Here the user has the possibility to update commission relevant data based on the actual settings / master data. E.g. this could be relevant, if master data during commission creation was wrong - so user can correct the master data and update commission with the corrected master data version.
The function shows a popup, where several redetermination levels are selectable:
- Commission header data→ read the main commission header information from invoice, VSS order and the vehicle, like it is done during commission creation
- Commission participant / pool data → read the actual partner and pool information for the main commission partner
→ there is additional option, to decide if manual created participants in the commission should be hold or should be deleted - Commission condition data → option, to decide if manual created conditions (normally all conditions) in the commission should be hold or should be deleted
- Additional set commission status → additional option to set status immediately during redetermination; also, here status can be set only to allowed status values
Commission maintenance report - function "redetermine" popup
This function is only for active (not deleted, not cancelled and not already transferred commission) possible.
This function is only in change mode available.
Function “change status” (icon 
at screen “Header data” / in menu “edit”)
Set the actual commission status to a new status. Here the status can be set only to values, which are allowed concerning the status settings – just this values are provided in the popup. In addition, it is possible to enter a comment / info text for the status change.
Commission maintenance report - function "status change" popup
After status change it is necessary to save the commission, before the next status change could be done. If the commission is not saved, the last status change / comment is the relevant change, which is stored in the history. All other changes between will be lost.
The history of all status changes, including their text comments, will be shown in the tab “history”.
Commission maintenance report - function "status change" in register "history"
Here also a corresponding icon shows, if for the single status change, there is a comment available or not.
The status change text is stored as long text with following parameters:
- Object: /DBME/P_PR
- ID: 0005 (status change text)
- Language: assigned language from plant
- Name: commission number + status sequence number + status number
Function “show vehicle” (icon 
at screen “Vehicle”)
Call the vehicle master application of the corresponding vehicle within the commission.
Function “change condition values” (icon & lines in tab “Conditions”)
This functionality is at the end, a set of functions to create manual conditions, change these condition entries and also delete them again from commission.
Commission maintenance report - function "change condition values" icon
By adding a new condition (icon 
above ALV), there appears a new line in the ALV and user must choose one of the available price conditions (defined by commission type settings).
Commission maintenance report - function "change condition values" popup
| Info |
|---|
Same conditions could be added several times and each of them are included in the commission value calculation. But there could be also some, where it is technical possible to add them several times, but to do, is somehow “free of space”, e.g. fix value condition. In general, this depends not from technical condition type, but from customer individual definition of condition meaning and calculation logic. |
| Info |
|---|
Depending on the maintained master data for condition text entries, the comment text for a single entry is free changeable text (no text entry for condition), automatically filled text (only one text entry for condition) or must be chosen by available list (several text entries for condition). |
The condition entry itself, is stored in the own table /DBME/PMA_APCND (not in “standard” price condition table).
As far as the commission allows changes, also the condition entries could be changed directly in the conditions ALV.
To delete an existing condition, mark the corresponding line in conditions ALV and press the icon 
.
Function “change partner values” (icon & lines in tab “Participants”)
This functionality is at the end, a set of functions to add manual additional commission partner, change these entries and also delete them again from commission.
Commission maintenance report - function "change partner values" icon
By adding a new partner (icon 
above ALV), there appear a new line in the ALV and user must enter:
→ One of the available partner roles (defined by commission type settings).
Commission maintenance report - function "change partner values" popup
| Info |
|---|
Based on the settings, some partner roles are shown in selection, but because they are defined as unique in the settings, an error message appears. For main partner role of the commission, the unique flag must be active in the settings |
| Info |
|---|
Based on the settings, some partner roles are defined as not manual changeable. So, manual adding of such partner roles makes no sense (also if they are offered in the selection), because for such an entry no values can be entered. For main partner role of the commission, the unique flag must be active in the settings. |
| Info |
|---|
Irrespective of the settings, the main partner role and pool partner role are defined in commission header and have a special logic. So, it never makes sense to add one of them manually. |
→ In addition to the partner role, also the person (HR number) must be entered.
Commission maintenance report - function "change partner values" HR number search
| Info |
|---|
Each combination of partner role and person (HR number) is allowed only once for a commission. |
| Info |
|---|
In the VSS standard, there is normal HR search help behind the partner ID field. So, each PERNR within the system can be found / added. If customer does not like this behavior and e.g. will provide here only employees, which are defined in the “commission relevant employee” table for the corresponding plant, the search help has to be extended by search help exit. The Criteria here could be e.g. the transaction code in SYST (to determine, where the request is coming from (standard or commission)) and in example above the data from commission relevant employee. In such a case, there should be in addition a BAdI implementation, checking partner ID’s during commission saving process, to avoid wrong manual entries (without search help) |
→ And finally, the corresponding value for this partner, to define which part he should get from total commission value. Here the user can enter a percentage or an absolute value and also mark the entry as commission relevant or not.
Commission maintenance report - function "change partner values" register "participants"
| Info |
|---|
In case percentage and absolute value are entered, the absolute value has priority and percentage will be cleared (= 0). |
| Info |
|---|
The total sum of all entered percentage values could not be bigger than 100%, otherwise an error message appears. |
| Info |
|---|
The total sum of all absolute values cannot not be bigger than the total commission value, otherwise an error message appears. |
| Info |
|---|
Values from manual partner entries has priority and reduce the values from automatic determined partner entries. In general, automatic determined partner entries (main partner / pool partner) are always calculated as percentage (based on master data definition) and their percentage values are always recalculated by change of manual partner entries. |
...
- Base is the total commission value calculated in formula builder and by the price conditions.
E.g. 2000 EUR - Reduce total commission value by the sum of absolute value from all manual partner entries.
E.g. 2000 EUR – 500 EUR = 1500 EUR - Recalculate percentage of the automatic determined partner roles.
- Reduce 100% by the sum of percentage value from all manual partner entries.
E.g. 100% - 20% = 80% - Split rest of percentage based on the master data definition (which commission hold always in the background, e.g. main partner =60%, pool partner = 40%)
E.g. main partner 60% of 80% = 48%; pool partner 40% of 80% = 32% - Split rest of commission value by the new determined percentage values to the single partner entries.
E.g. main partner 48% of 1500 EUR = 720 EUR, pool partner 32% of 1500 EUR = 480 EUR and manual partner 20% of 1500 EUR = 300 EUR
- Reduce 100% by the sum of percentage value from all manual partner entries.
Commission maintenance report - function "change partner values" calculation example
| Info |
|---|
Clearing the flag “calculation relevant” sets the corresponding partner entry inactive for the calculation and the values are recalculated without these entries. |
...
- "
...
→ And in addition, it is optional possible to add a comment for each changeable entry, e.g. why this person should get a part of this provision.
Commission maintenance report - function "change partner values" comment lines
As far as the partner role allows changes, also the person and the value entries could be changed directly in the partner ALV.
To delete an existing partner entry, mark the corresponding line in partner ALV and press the icon 
. Automatic determined partner entries (main partner / pool partner) cannot be deleted, here only the flag “calculation relevant” can be cleared and so commission value is set to zero.
Several Hyperlinks
In the detail screen, some fields have a special function (by double click).
- SD document (invoice number) (in “header data”)
- Call the corresponding invoice in display mode (T-code VF03).
- Sales document (invoice number) (in tab “administration”)
- Call the corresponding invoice in display mode (T-code VF03).
- Reference document (VSS order number) (in tab “administration”)
- Call the corresponding VSS order in display mode (T-code /DBE/ORDER03).
- Canceled commission number (in tab “administration” / just for cancelation com.)
- Call the corresponding commission in display mode (in actual detail screen).
Report “mass redetermination”
Functional Requirements
With the report for mass redetermination it is possible to “refresh commission master data” for a specific selection of active commissions (not deleted, not canceled and not already transferred). Here the user has the possibility to update commission relevant data based on the actual settings / master data. E.g. this could be relevant, if master data during commission creation was wrong - so that the user can correct the master data and update the commission with the corrected master data version.
- Selection screen:
The selection screen mainly contains two sections:
→ the options (what should be done)
Mass redetermination - selection screen settings
- Show list
→ shows first a list of the selected commissions and the user can mark the relevant commissions and process the redetermination for them; otherwise redetermination runs without list and all selected commissions are updated - Save protocol
→ stores the processing protocol additional in the application log with object /DBME/PMA and subobject MASS_UPDATE and so it can be called also later on; otherwise protocol is just shown at the screen during runtime - Commission header data
→ read the main commission header information from invoice, VSS order and the vehicle, like it is done during commission creation and update commission - Commission participant / pool data
→ read the actual partner and pool information for the main commission partner and update commission
→ there is the additional option, to decide if manual created participants in the commission should be hold or should be deleted - Commission condition data
→ optional, to decide if manual created conditions (normally all conditions) in the commission should be hold or should be deleted
→ the selection criteria (at which commissions it should be done)
Mass redetermination - selection screen criteria
- ALV list
Mass redetermination - ALV list result
In addition to the standard ALV functions, here we have just one additional function “start mass update”. Pressing this function, the “refreshing of master data” will be processed for all in the ALV selected commissions, based on the chosen options at selection screen.
- Processing log during runtime
Mass redetermination - processing log
After each processing, the actual log is shown to inform about successful, not allowed and not successful updates.
Authority check
- Authority object “/DBME/P_MS” for activity
Customer Enhancement
- Yes, BAdI and enhancement points are available.
- BAdI
- /DBME/PMA_IF_E_PROV_SELECTION~SELECTION_EXECUTE
- /DBME/PMA_IF_E_PROV_SELECTION~SELECTION_POSTPROCESS
- Enhancement points
- BAdI
- /DBME/PMA_MASS_UPDATE01
- /DBME/PMA_MASS_UPDATE02
- /DBME/PMA_MASS_UPDATE03
Customer example
- No, activities will be described in user manual
Proaxia example
- No specific setting
Report / interface “transfer to HR”
Functional Requirements
With the report for “HR transfer” it is possible to send the open commission values for each employee / commission combination to the target system, e.g. an HR system to process there the commission payments.
The report itself just collects all relevant commission value entries, which are relevant for transfer, fit to the selection criteria and not already transferred, and send each of them to the BAdI implementation.
Within the BAdI implementation, the customer has to develop / enhance his own transfer logic. Reason for this approach are the large variants of target solutions (SAP HR within the system, SAP HR in different system, non SAP HR, …).
Based on the return value of the BAdI, the report updates in addition the commission value entry and marks it as transferred.
Most likely this report is running frequently as batch job.
- T-Code: SA38
- Report: /DBME/PMA_MASS_POST
- Selection screen
The selection screen mainly contains two sections: - → the selection criteria (at which commissions it should be done)
Transfer to HR - selection screen criterial
...
Transfer to HR - selection screen settings
- Posting date
→ with this date the posting will be done in target system - Ignore posting calendar
→ process report without check to the settings in the posting calendar; if flag is initial, the report checks posting calendar and process the single entries only in case the posting date is marked as transfer relevant; in case report is running frequently in a batch job, flag should be marked and posting calendar should be maintained - Test mode
→ select relevant commission values, but do not call BAdI / do not update commission values - Remarks
→ possibility to add a remark to the single postings to transfer this information to the target system
- Processing log during runtime
Transfer to HR - processing log
...
Authority check
- No specific authority object.
Customer Enhancement
- Yes, BAdI and enhancement points are available.
- BAdI
- /DBME/PMA_IF_E_PROV_SELECTION~SELECTION_EXECUTE
- /DBME/PMA_IF_E_PROV_CREATE~SD_DOCUMENT_DATA_READ
- /DBME/PMA_IF_E_PROV_CREATE~DATA_PREPARE_CREATE
- /DBME/PMA_IF_E_PROV_CREATE~ITEM_CREATE
- BAdI
Customer example
- No, activities will be described in user manual
Proaxia example (internal test)
- No specific setting
Interface “maintenance in external frontend”
Functional Requirements
If the customer will not use the SAP GUI as frontend, e.g. because the salesman in general does not work in SAP and so they should handle / release their commissions via an UI5 frontend, the VSS standard does not provide a final solution, just a tool set.
The main reason for this approach is based in the large number of possible solutions concerning interface (web service, proxy, ODATA, direct, via PI, via Gateway, …) and concerning frontend (own solution, UI5, Fiori, …).
...