Ansicht
Dokumentation
/PRA/R_WH_ADMIN_WORKPLACE - Withholding - Admin Workplace
rdisp/max_wprun_time - Maximum work process run time RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
Purpose
One time setup to maintain payment processing's technical parameters.
Activities
Maintain Server Groups - Various payment processing steps allow for parallel processing. Standard aRFCs are used to achieve this parallelization per SAP norms. aRFCs are executed in RFC server groups. This server group defines how many dialog processes can be consumed by the parallel processing session. Standard SAP RFC server group guidelines should be followed (or per your company standards).
Maintain Parallel Processing Settings (the pencil icon in the table control) - this allows the administrator to specify the RFC server group to be used for each processing group. Moreover, the admin can specify the maximum number of parallel groups each applicable parallel steps can utilize. For example, a maximum of 10 parallel groups is setup for processing group A utilizing RFC server group X. RFC server group X has set a maximum of 5 dialog processes to use. This means that when the applicable step is executed in payment processing, it'll divide up the work into 10 parallel groups and the system will process a maximum of 5 groups at a time until all 10 are processed.
Maintain Destinations/Queues - Payment processing 2.0 utilizes a queue concept whereby other PRA subsystems can continue to work without stop even if payment processing is running. This is accomplished using the standard SAP bgRFC concept. SAP's bgRFC function requires some basic system setup. A supervisor destination will need to be created. (Please follow the documentation provide in the SAP Help Portal to perform this action: SAP NetWeaver -> Components of SAP Communication Technology - Classical SAP Technologies -> RFC -> Background Communication -> bgRFC -> Configuration -> Creating a Supervisor Destination). Once the supervisor destination has been setup, click on the Define Inbound Destination tab.
Create new destination: /PRA/PP
Logon/Server Group: Please pick a group which represents only 1 server - because the queue is meant to be processed by 1 and only 1 daemon - else, the order of postings may not be followed
Create prefix associated with this destination: /PRA/PP/
Save the setup.
The actual queue itself is the business grouping of what is running versus what is stopped (due to a payment processing run in trial mode). The recommendation is to setup a UNIQUE queue for each processing group (the easiest would be to name the queue the same as the processing group - leaving all defaults). This recommendation is based on the fact that the customer may want to have one process group in trial mode in payment processing - and any information for other process groups can continue to flow into the system. For example, the customer has 2 process groups (A & B). Customer creates a payment processing run for process group A. When the populate step of that trial run is executed - the queue to A is locked (provided 2 different queues A & B were created for processing groups A & B). Business can continue to post values into the system for B and those entries will continue to flow in. However, entries belong to process group A will NOT be updating the owner payable summary (since the queue has stopped).
Next click on the Scheduler Destination tab.
Click create button
Select Inbound
Enter /PRA/PP as destination and in order for this implementation of bgRFC to act as a queue, the value for Scheduler Count MUST be set to 1.
Save the setup.
Maintain Queue Settings (pencil icon in the table control) - this is where you assign the queue destination and the queue to the process group. Enter /PRA/PP as destination and /PRA/PP/xxxx as queue name where xxxx = process group.
Example
Addresses (Business Address Services) General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 4013 Date: 20240424 Time: 112939 sap01-206 ( 86 ms )
