2019-03-01 99999
99999 - ATP server: Installation and sizing
Version 13 Type SAP Note
Language English Master Language German
Priority Recommendations / Additional Info Category Consulting
Release Status Released for Customer Released On 24.11.2017
Component SD-BF-AC ( Availability Check )
Please find the original document at https://launchpad.support.sap.com/#/notes/ 99999
Symptom
General information
As of Release 4.0A, the availability check can be carried out for a dedicated
application server, the ATP server. The concurrent use of more than one ATP
server in a system is not possible. The following checks (basic methods) are
possible:
• Check in accordance with the ATP logic
• Check against planned independent requirements
• Check against product allocations
The ATP server has a global, cross-transaction memory (shared buffer), in which
ATP-relevant information such as the requirement date, requirement quantity, and
confirmed quantity from the database tables RESB (reservations and dependent
requirements) and VBBE (individual customer requirements) are aggregated by day.
When you check the material availability, the system reads the data of the two
tables mentioned above from the shared buffer, not from the database. This
access method improves performance considerably. A corresponding delta
processing ensures data consistency between the shared buffer and the database.
The ATP server is not a separate installation. As the application server, is
part of the respective R/3 installation.
Installation and sizing of the ATP server
The activities needed to install the ATP server correctly are listed below. If
this is not done (standard delivery), the check is performed without using the
shared buffer, which means the ATP-relevant data from the database tables RESB
and VBBE are generally read from the database.
Changes in system administration
Change the following SAP parameters (see transaction RZ10):
• RFC address of the ATP server
(parameter: rdisp/atp_server):
Here, enter the name of the application server that will serve as the ATP
server, analogous to the enqueue server (see transaction SM51: SAP servers).
This parameter must be visible for all application servers, which means it
should be entered in the DEFAULT profile (DEFAULT.PFL).
The following parameters are important only for the ATP server, which means they
© 2019 SAP SE or an SAP affiliate company. All rights reserved 1 of 7
2019-03-01 99999
must be entered in the instance profile of the ATP server.
• Size of the shared buffer
(parameter: rsdb/obj/buffersize):
In a first approximation, you can estimate the size of the shared buffer as
follows: There is an object in the shared buffer for each table (RESB and VBBE),
client, material, and plant. The size of this object is primarily dependent on
the number of organizational levels (storage locations, batches, and MRP element
indicators saved in the tables RESB and VBBE) and the number of different dates
for each organizational level. 25 bytes are required for each organizational
level and date.
Example for a VBBE object: 3 storage locations, no batches, 20 dates and 2 MRP
elements for each storage location: Sales orders and deliveries.
This results in (25 bytes x 20 x 3 x 2 ) + (25 x 3 x 2) = 3150 bytes of storage
space for this object. If you need to store10,000 material/plant combinations in
the shared buffer, 3150 x 10,000 bytes is needed. You now have to make a similar
estimation for the table RESB, if the corresponding MRP elements are to be
included in the scope of the check. You must also add the administration
overhead for the shared buffer and the object directory where the objects are
stored. This factor is highly dependent on the maximum number of objects (see
below) and is in the range of 10%-20%.
• Maximum number of stored objects
(parameter: rsdb/obj/max_objects):
Set this parameter approximately twice as large as the number of ATP-relevant
client/material/plant combinations, if you want to perform the ATP check for
both sales requirements and material reservations.
• Maximum size of a saved object
(parameter: rsdb/obj/large_object_size)
The default value is usually correct here.
In addition, some configuration parameters of the application server defined as
the ATP server may have to be adjusted, to handle the additional processing
steps and remote function calls with good performance:
• Max. number of registered users
(parameter: rdisp/tm_max_no):
Determines how many users are able to log on to an application server at the
same time. The default is 200; this value should be larger than the maximum
number of users who want to run ATP checks in parallel.
• Maximum number of RFC connections
(parameter: gw/max_conn):
The default here is 500; this is usually sufficient.
• Number of dialog work processes
(rdisp/wp_no_dia):
Increase the number of dialog work processes on the ATP server by 1-2 processes.
For more information about these parameters, see transactions RZ10, RZ11, and
ST02.
You can find further information about the gateway in transaction SMGW (Gateway
Monitor).
© 2019 SAP SE or an SAP affiliate company. All rights reserved 2 of 7
2019-03-01 99999
In particular, after you set up the ATP server, you should use transaction ST02
to check the buffer setting during regular operations.
Actions to correct errors in the dataset
Transaction ACBD provides additional monitoring and management functions for the
shared buffer of the ATP server, for example:
• Complete or partial deletion of the shared buffer (with regard to ATP data)
• Synchronization of the shared buffer with the database
This transaction allows the preloading of the data from the database to the
shared buffer. Otherwise, the data is loaded for each client, material, plant,
and table at the time of the first availability check for this combination.
Connections between ATP server and MRP jobs
Note the following: For performance reasons, MRP jobs do not update the FTP
server (default settings). Therefore, the ATP server is invalidated with regard
to the reservations when an MRP job is started (default settings).
This means the ATP server no longer has any reservation data after an MRP job
(default settings)
Nor can the ATP server update the reservations while an MRP job is running
(default settings).
Note: An MRP run that is started in dialog does not invalidate the ATP server.
Recommendation:
In this situation, there are two options:
1. Check whether you can schedule the jobs such that jobs that have to access
the ATP server are all started after the MRP jobs. If necessary, schedule an
additional job with the program ATPBD001, which performs data synchronization,
to refill the ATP server with data.
2. Check whether SAP Note 704310 might be the better solution in your case. SAP
Note 704310 is a modification note that prevents the ATP server from being
invalidated during an MRP job. It increases the runtime of the MRP job, because
the ATP server has to be updated, but reduces the total runtime of all the
required jobs.
Other Terms
ATP, performance
Reason and Prerequisites
Important prerequisites that you should take into account when installing the
ATP server:
• During the installation, all application servers must be stopped, so the
default parameters can be copied.
• The check with quantity block (see Customizing of SD availability check
[table TMVF]) must be active.
• To keep the data transfer low, the same server should be used as both ATP
server and enqueue server (this applies to the classic enqueue server). This
means: The parameters "rdisp/atp_server" and "rdisp/enqname" should refer to
the same server (this does not apply to a standalone enqueue server - the
© 2019 SAP SE or an SAP affiliate company. All rights reserved 3 of 7
2019-03-01 99999
parameter rdisp/enqname is not relevant here (use the online help for
further information)) – in other words, the same SAP instance. In the best
case, both parameters will be defined in the default profile (DEFAULT.PFL).
• Make sure that the related SAP Notes are implemented in your system.
Solution
See above.
Software Components
Software Component Release
SAP_APPL 40A - 40B
SAP_APPL 45A - 45B
SAP_APPL 46A - 46B
SAP_APPL 46C - 46C
SAP_APPL 470 - 470
SAP_APPL 500 - 500
SAP_APPL 600 - 600
SAP_APPL 602 - 602
SAP_APPL 603 - 603
SAP_APPL 604 - 604
SAP_APPL 605 - 605
SAP_APPL 606 - 606
SAP_APPL 616 - 616
SAP_APPL 617 - 617
SAP_APPL 618 - 618
PI 2001_1_31I - 2001_1_31I
Other Components
Component Description
© 2019 SAP SE or an SAP affiliate company. All rights reserved 4 of 7
2019-03-01 99999
BC-DB-DBI DB Independent Database Interface
SD-BF-AC-TS Technical Services
Support Package
Software Component Release Support Package
PI 2001_1_31I SAPKIPZDI2
This document refers to
SAP Note/KBA Title
99972 Error in availability check for CO40/CO41/MD04
863705 ATP server: Reservations are not loaded
835219 FAQ: ATP composite note
770784 Information on locking problems during availability check
704310 ATP server not populated in batch total planning run
704130 Belgium Central Bank Reporting Format changed.
668143 ATP server: Shortage after goods issue
596401 ATP server: shortage after goods issue
456060 ATP server: Buffer is loaded with irrelevant data
373986 Overflow of the export/import buffer
362769 Error handling during preload
210808 Inconsistency in ATP buffer after calling MDAC
192423 Delivery Processing Performance: Consulting
1766163 Improved selection in RESB
166749 ATP:Inconsistencies in buffer data after MRP run
163819 ATP: Transaction ACBD
145838 Error in ATP buffer after collective availab. check
144673 Inconsistnt ATP buffer aft.conversn of plannd order
© 2019 SAP SE or an SAP affiliate company. All rights reserved 5 of 7
2019-03-01 99999
143911 Update reservation confirmed quantity is incorrect
127425 No update of ATP buffer during backorder processing
125848 Internal documentation collective availability check
124458 ATP: Shared buffer not updated correctly
103725 No update ATP float during backorder processing
103714 ATP: Quantity locks are not deleted
102889 Sales reqs. incorrect in buffer of ATP server
102328 Missing initialization ATP server
101570 ATP: Update of the shared buffer
101036 ATPserver:database/shared buffer comparisn incorrct
100427 Incorrect update of data in the ATP server
This document is referenced by
SAP Note/KBA Title
704310 ATP server not populated in batch total planning run
1766163 Improved selection in RESB
101036 ATPserver:database/shared buffer comparisn incorrct
863705 ATP server: Reservations are not loaded
335965 Performance of availability check when using ATP server
835219 FAQ: ATP composite note
770784 Information on locking problems during availability check
704130 Belgium Central Bank Reporting Format changed.
668143 ATP server: Shortage after goods issue
163819 ATP: Transaction ACBD
373986 Overflow of the export/import buffer
596401 ATP server: shortage after goods issue
125848 Internal documentation collective availability check
456060 ATP server: Buffer is loaded with irrelevant data
© 2019 SAP SE or an SAP affiliate company. All rights reserved 6 of 7
2019-03-01 99999
362769 Error handling during preload
143911 Update reservation confirmed quantity is incorrect
192423 Delivery Processing Performance: Consulting
144673 Inconsistnt ATP buffer aft.conversn of plannd order
210808 Inconsistency in ATP buffer after calling MDAC
145838 Error in ATP buffer after collective availab. check
166749 ATP:Inconsistencies in buffer data after MRP run
127425 No update of ATP buffer during backorder processing
102328 Missing initialization ATP server
99972 Error in availability check for CO40/CO41/MD04
124458 ATP: Shared buffer not updated correctly
100427 Incorrect update of data in the ATP server
102889 Sales reqs. incorrect in buffer of ATP server
103714 ATP: Quantity locks are not deleted
101570 ATP: Update of the shared buffer
103725 No update ATP float during backorder processing
© 2019 SAP SE or an SAP affiliate company. All rights reserved 7 of 7
