Content Comparison

...

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)

Image Added

Transfer to HR - selection screen criterial

→ the posting options    (what should be done)

Image Added

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

Image Added

Transfer to HR - processing log

After each processing, the actual log is shown to inform about successful, not allowed and not successful updates. Application log object /DBME/PMA and subobject MASS_POST.

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

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, …). 

But to support such a case, we provide several classesthe customer can use to read relevant commission data (outbound processing) and to handle the different commission parts (inbound processing).