SAP ATP Server

Overview
The SAP ATP (Available To Promise) server caches availability checks in the export/import buffer, replacing database calls to !S" and #""!$ eference% SAP &ote ''''' ( ATP server% )nstallation and si*ing (https%//service$sap$com/sap/support/notes/''''') SAP &ote +,-+-. ( Profile parameter for export/import buffer instances (https%//service$sap$com/sap/support/notes/+,-+-.) SAP &ote /+/'.0 ( 1verflo2 of the export/import buffer (https%//service$sap$com/sap/support/notes//+/'.0) 3SAP Performance 1ptimi*ation 4uide (0th !dition),5 Thomas Schneider, 4alileo Press (-,,'), section 6,$7, pp$ 77/879,$ (http%//222$sap8 press$com/products/SAP8Performance81ptimi*ation84uide8:-.0th8!dition :-'$html)

Install the ATP Server

Pick a suitable SAP )nstance to run the ATP server, sub;ect to the space constraints belo2$ The ATP server is a logical service activated by a profile parameter, and since all of the instance<s servers 2ill use this same server, the parameter should be set in the =!>A?@T profile (transaction A6,)$ The ATP server and !nBueue server should run in the same instance$ Set both% rdisp/enBname rdisp/atpCserver

estart the instances to pick up the changes

Tune the Export/Import Buffer

>igure out ho2 many ob;ects you plan to cache$ !ither follo2 the elaborate formulas in the references above, or ;ust flush the cache, run a sample test, and extrapolate$ Duick and dirty guideline% figure out ho2 many maximum ob;ects you<ll ever need (rsdb/ob;/maxCob;ects) and set it, and set the !xport/)mport "uffer (si*e in E") to t2ice that number (rsdb/ob;/buffersi*e), since each ob;ect should take a little less than half a E"$ Tune as needed$

Transactions
A6, ( Set parameters$ ST,- ( #ie2 buffer statistics$ SF9,/SF96 ( #erify ATP and !nBueue servers activated$ AG=" ( #ie2 and delete export/import buffer table entries$

Some of the 1SS notes 2hich can be of use to you for ATP server are as follo2s$ 6//76.

67,9-7 69,9+. 60/.6' 6.,/7' 60...' 60.0'/,/6.' //9'09 ATP8Server An Available8To8Promise8Server provides all the data available throughout a company$ Hhen demand is increasing the system can define supply expectations and support their fulfillment$ As of elease 7$,A, the availability check can be carried out on a dedicated application server, the ATP server$ Iou can make the follo2ing checks (basic methods)% o Gheck according to the ATP logic o Gheck for planned independent reBuirements o Gheck for allocations The ATP server has a cross8transaction, global memory (shared buffer),2here ATP8relevant information, for example, reBuirement date, reBuirement Buantity and confirmed Buantity of the database tables !S"( eservations/dependent reBuirements) and #""! (Sales eBuirements% )ndividual ecords) is aggregated according to the date for one day at a time$ Hhen you check material availability the system reads the data of the t2o mentioned tables from the shared buffer instead of from The database$ This method of access considerably improves the performance$ A corresponding delta processing ensures data consistency bet2een the shared buffer and the database$ The ATP server is not a separate installation$ As an application servers, it is part of the used // installation$ )nstallation and Si*ing of the ATP server "elo2 2e describe the necessary actions to install the ATP server correctly$ )f you do not do this (standard system) then the check is

carried out 2ithout the use of the shared buffer, that is, the system al2ays reads the ATP8relevant data of database tables !S" and #""! from the database$ Ghanges to the system administration Ghange the follo2ing SAP parameters% o >G address of the ATP server (parameter% rdisp/atpCserver)% As 2ith the !nBueue server, you must enter the name of the application server 2hich is to be used as an ATP server (see Transaction SF96% SAP server)$ This parameter must be displayed for all application servers, it should be entered in the default profile$ The follo2ing parameters are only important for the ATP server, thus, you have to enter them into the instance profile of the ATP server$ Si*e of the shared buffers (parameter% rsdb/ob;/buffersi*e)%As a first approach you can estimate the si*e of the shared buffer as follo2s% >or each table ( !S" and #""!), client, material, and plant, there is an ob;ect in the shared buffer$ The si*e of this ob;ect mainly depends on the number of the organi*ational levels(storage locations, batches and F P element indicators 2hich are stored in tables !S" and #""!) and the number of the different dates for each organi*ational level$ >or each organi*ational level and date you need -9 byte$ !xample for a #""! ob;ect% / storage locations, no batch, 6, dates >or each storage location, - F P elements% Sales orders and deliveries$ The result is (-9 byte x$ x / x - ) J (-9 x / x -) K 609, byte Storage reBuirement for this ob;ect$ )f 6,,,, combinations of material and Plant should be buffered in the shared buffer, then 609, byte x 6,,,, Are reBuired$ Iou must carry out a similar estimation for table !S" if corresponding F P items occur in the check according to scope of check$ )n addition there is the administrative overhead for the shared buffer and the ob;ect directory, 2hich contains the ob;ects$ This factor largely depends on the maximum number of stored ob;ects (see belo2) and is in the

scale of 6,:8-,:$ o Fax$ number of stored ob;ects (parameter% rsdb/ob;/maxCob;ects)%>or this parameter you should choose a value 2hich is about t2ice as large as the number of ATP8relevant client/material/plant combinations, if you 2ant to carry out the ATP check for both sales reBuirements and material reservations$ o Faximum si*e of a stored ob;ect (parameter%rsdb/ob;/largeCob;ectCsi*e) here the default value 2ill generally be correct$ )n addition you may have to ad;ust some configuration parameters of the application server 2hich is defined as an ATP server to handle the additional processing steps and the remote function calls efficiently% o Faximum number of logged on users (parameter% rdisp/tmCmaxCno)% Specify ho2 many users can log on at the same time to an application server$The default is -,,, the value should be larger than the maximum number of users 2hich 2ant to carry out ATP checks simultaneously$ o Faximum number >G connections (parameter% g2/maxCconn)%Lere, the default is 9,,, this 2ill normally be enough$ o &umber of dialog 2ork processes (rdisp/2pCnoCdia)%1n the ATP server, increase the number of dialog 2ork processes by 6 8 processes$ >or more information on these parameters see Transactions A66 and ST,-$ Fore information on the gate2ay you 2ill find in Transaction SF4H (gate2ay monitor)$ )n particular, after you setup the ATP server 2ith Transaction ST,-, you should check the buffer update settings$ Actions to correct errors in the dataset >or the shared buffer of the ATP server Transaction AG"= offers 1ther monitoring and administration functions, for example% o complete or partial deletion of the shared buffer(concerning

ATP data) o comparison of the shared buffer 2ith the database This transaction permits you to load the data from the database into the shared buffer in advance$ 1ther2ise, the data is loaded for each client, material, plant, and table at the date of the first availability check for this combination$ Additional key 2ords ATP, performance Gause and prereBuisites )mportant preconditions 2hich should be taken into account during The installation of the ATP server% o =uring the installation all application servers must be stopped so the default parameters are transferred$ o The check 2ith Buantity block (see Gustomi*ig availability check S= MTabelle TF#>N) must be active$ o To keep the data transfer lo2 the ATP server should be selected like the enBueue server$ o Fake sure you applied the related notes into your system$

SF6- 8 Faximum records in lock table and enBue/table si*e SF6- 8O !xtras 8O Statistics sho2s the @ock !ntries Table Si*e K /0,/$ 1ne of the SAP programs ( PG)P!,,) is causing a @ock table overflo2 (locking /0,- recrods)$ ) had increased the profile parameter PenBue/tableCsi*eP from the default of 7,'0 to 6,,,,$ After bouncing the system, SF6- still sho2s a @ock !ntries table Si*e of /0,/$ ) checked my production system 2hich also sho2s a table si*e of /0,/, yet the PenBue/tableCsi*eP over there is set to 7,'0,$ ) guess ) am reali*ing that this parameter has no affect on the maximum number of records that can be locked$ Hhat does affect this value in SF6-Q Ans% ) discovered my problem$ ) 2as altering the profile parameter in my =#!"F4S instance, but 2e run the enBueue server on our */1S mainframe under ?SS$ )t is that profile that the enBueue server reads to set the lock table si*e$ ) guess A6, R A66 do not look at the profiles for the enBueue server 2hen run Pelse2hereP$

ATP Server and Buffer Updation

What is ATP Server

!ompanies which are operatin" with lar"e volume of data usuall# faces lon" time to perform availa$ilit# chec%& 'ata$ases associated with availa$ilit# chec% are (ESB and )BBE The ATP server has a cross*transaction+ "lo$al memor# ,shared $uffer-+where ATP* relevant information li%e (ESB/)BBE are a""re"ated accordin" to the date for one da# time&When we chec% material availa$ilit# the s#stem reads the data of the two mentioned ta$les from the shared $uffer instead of from he data$ase& This method of access considera$l# improves the performance& Transaction AG"= and )ts ?sage% Transaction A!B' offers further monitorin" and administrative functions for t Shared Buffer of the ATP Server.

!omplete or partial deletion of the Shared Buffer !omparison of the Shared Buffer with the data$ase This transaction also allows #ou to preload the data from the data$ase into the Shared Buffer& ,This is re/uired for after ever# 0(P runIf we not loaded+ the data is loaded the first time availa$ilit# is chec%ed * which could ta%e some time& 4enerally AG"= transaction is executed at Plant level 2hich 2ill run long time depends upon the volume of the data$ He can create several selection screen variant based business criteria$ Scheduling this ATP run 2ith this selection screen variants after each F P run is tedious one$ >or this 2e can use background ;ob after event method to run periodically$

0a%e ATP 1o$ after the 0(P 1o$ Periodicall#.

Step 2. !reate event in S034