2012-07-26 - 4614.100 - Spec - Allocation Optimization #ARUN

4614.100 - Allocation Optimization - Performance Time

Summary Description

Analyse the reasons for long performance time of ARUN jobs and recommend solution to cut down the performance time.

Admin Info


Purpose
 Analyse ARUN jobs and recommend solution to improve performance.
Requested by
 Thi Tran
Issue Date
 07/26/2012
Resolved by
 Surya Basa
Resolved Date
 03/28/2013
Document Status
 Complete

Detailed Description

(Include Screen Shots if required)
The NA ARun job has been running longer than the Delivery job so some deliveries are not being created and require an extra day before they are created. The ARun variant settings need to be reviewed and optimize run time and also review the batch jobs to see if the Deliveries job could be pushed out a couple of hours.


Analysis and Recommendations

(Include Screen Shots if required)
The following are the list of suggestions to improve the ARUN performance in priority sequence.

1. OSS NOTE: Implement the OSS correction note – 1440877 to improve performance. (ReCap No. 1221).
Comments: This note is implemented in DEV and Q but not in P

2. DELETE LOGS: The system updates statistical tables (ARun messages & results) after every ARUN. The contents of these tables may increase with each ARun and the same have to be deleted from time to time to ensure faster processing.
Comments: SAP has provided a note – 180155 to clean up the contents and has provided a report J_3AAREO for reorganisation.

3. PARALLEL RUN: It is recommended to have a parallel run for QS as the unique selection parameters (e.g. Seasons) are not a part of the other variants. Hence, it wouldn’t have any negative impact when run parallel along with the others.
Comments: The option of having parallel ARUN for each variant too could be considered as the system would allocate the available resources at the given point of time and the data load will be equally distributed.

4. OPTIMIZE PARAMETERS: Reconsider the longer date range for the delivery dates (360 to -360) in the Future Receipts segment of the QS ARun selection parameters.
Comments: The system looks up 360 days into the future and then 360 days backward for the existing PO’s delivery date. Hence, consumes more time in the processing. The QS ARun processes on average about 400-450 orders in a day and the duration of the run is about 1.3 – 2 hrs. This is a long time considering the number of orders being processed.

4.1 The SAP help note recommends maintaining the selection parameters as per the hierarchy in the VAPMA (sales order index) table, which has the sales area, document type at the higher hierarchy level. This could make [[#|the jobs]] run faster. Currently only the sales orgs are included and order types are excluded rather than being included.
4.2 There’s a delivery status indicator (C) maintained to be in excluded in the selection parameters for the delivered items. We have run a few tests to check if the presence or absence of the indicator has anything to do with the performance and it appeared that it didn’t make any difference whether the indicator is there or not. And we could do away with this because anyways once the item/s is/are delivered the ARun won’t pick those and it doesn’t make sense to particularly select the option to exclude those items.

5. CONFIG CHANGES: At the config level and as per the best practices, the preferred sort rule is HeaderàItemàSchedule line but currently the system follows a different sort rule (Schedule lineàHeaderàItem).
Comments: This could be reworked and the change in performance could be monitored over few days.

5.1 The KVGR1 (customer group1) field in the customer master is used as one of the sort fields for PRG ARun. This too probably could be slowing down the process.

6. VARIANT PARALLEL RUN: Run variants in parallel for e.g. The PRG ARun and QS ARun variants could be run parallel as they have unique selection parameters (seasons). These two variants consume approx 3.5 hrs between them. The processing times could be reduced with the parallel set up.

Action Items per the above recommendations:
Item 1: Note implemented but no change in performance (08/27/2012).
Item 2: Statistical tables deleted but no change in performance (09/10/2012).
Item 3: Tests are under progress, reported issues to SAP

Results: Parallel ARUN route has been dropped from the options as no resolution was provided by SAP to the issues.

Resolution


Created new selection sets with Access Rule S003 using the existing ARUN Types; created variants using the program /AFS/ARUN_BATCH and set up the jobs. SO range was included in the selection set criteria.

Results: Significant performance improvement was observed with the new selection set-variant combination using the conventional ARUN method using the program /AFS/ARUN_BATCH.
The following are the details comparing the previous NEP data-

Job
(NEW)
 Variant
(With NEW selection sets)
 Sel Set
(NEW)
 ARUN Num
 Allocated
Lines
 Allocated
SO
 Duration
(in Sec)
 Date
 Perf
Change
 Date
 Duration
(in Sec)
 Allocated SO
 Allocated Lines
 ARUN Num
 Sel Set
(OLD)
 Variant
(With OLD selection sets)
 Job
(OLD)
AU_SD_ARUN




622
 03/26/2013
 4.68
 03/25/2013
 2910






AU STK ARUN
 100000080
 1385104
 35
 3
 111
8.01
889
 3
 46
 1384061
 100000070
 AU STK ARUN
 AU_SD_ARUN

AU PRG ARUN
 100000083
 1385105
 119
 5
 135
6.22
840
 5
 158
 1384062
 100000071
 AU PRG ARUN

AU QS ARUN
 100000082
 NA
 NA
 NA
 100
8.31
831
 NA
 NA
 NA
 100000072
 AU QS ARUN

AU FUT RECPTS
 NA
 NA
 NA
 NA
 138
0.87
120
 NA
 NA
 NA
 NA
 AU FUT RECPTS

AU STK BALANCE
 NA
 NA
 NA
 NA
 138
1.67
230
 NA
 NA
 NA
 NA
 AU STK BALANCE

















EMEA_SD_ARUN




2457
 03/27/2013
 2.33
 03/26/2013
 5731




EMEA_SD_ARUN

EMEA CON ARUN
 100000084
 1387125
 1224
 33
 1456
1.86
2701
 41
 1437
 1385571
 100000000
 EMEA CON ARUN

EMEA QS ARUN
 100000085
 1387127
 NA
 NA
 816
3.53
2883
 1
 1
 1385573
 100000061
 EMEA QS ARUN

UK FUT RECPTS
 NA
 NA
 NA
 NA
 185
0.79
147
 NA
 NA
 NA
 NA
 UK FUT RECPTS

















NA_SD_ARUN




14613
 03/27/2013
 2.89
 03/26/2013
 42260




NA_SD_ARUN

NA STK ARUN
 100000086
 1387124
 6873
 731
 2740
2.84
7783
 55
 1138
 1385572
 100000010
 NA STK ARUN

NA PRG ARUN
 100000087
 1387126
 166
 2519
 2883
3.20
9240
 2107
 19015
 1385574
 100000011
 NA PRG ARUN

NA MTO ONLY S5
 100000088
 NA
 NA
 NA
 980
1.60
1568
 NA
 NA
 NA
 100000040
 NA MTO ONLY S5

NA MTO ONLY S8
 100000089
 1387129
 0
 0
 351
2.40
843
 0
 0
 1385576
 100000043
 NA MTO ONLY S8

NA MTO ONLY S9
 100000090
 1387130
 10
 30
 1253
1.31
1647
 1
 2
 1385577
 100000044
 NA MTO ONLY S9

NA MTO ONLYS12
 100000091
 1387141
 1
 7
 720
2.38
1711
 18
 125
 1385578
 100000047
 NA MTO ONLYS12

NA MTO ONLYS13
 100000092
 1387142
 0
 0
 1300
4.22
5481
 0
 0
 1385591
 100000048
 NA MTO ONLYS13

NA STK ARUN515
 100000093
 1387143
 0
 0
 310
3.19
988
 0
 0
 1385592
 100000057
 NA STK ARUN515

NA PRG ARUN515
 100000094
 1387144
 1
 1
 96
10.11
971
 0
 0
 1385593
 100000058
 NA PRG ARUN515

NA QS ARUN
 100000095
 1387150
 7
 78
 1920
5.58
10708
 30
 384
 1385598
 100000060
 NA QS ARUN

FUTURE RECPTS
 NA
 NA
 NA
 NA
 660
0.80
530
 NA
 NA
 NA
 NA
 FUTURE RECPTS

NA STK BALANCE
 NA
 NA
 NA
 NA
 1400
0.56
790
 NA
 NA
 NA
 NA
 NA STK BALANCE

arun.jpg

Documents


The following are the documents containing the notes on Parallel ARUN and the documents with the details of the Parallel ARUN issues forwarded to SAP.

Parallel ARUN_Notes.docx PARUN_J4AE.docxParallel ARUN_Direct Access Rule_NEQ100.docxParallel ARUN_Dir Access Rule.docxParallel ARUN_Statistics Group.docxExamples_SO_Allocation.xlsParallel ARUN_Issues.docx

Parallel ARUN_Issues_Examples.docxParallel ARUN_Sel Set 102_121.docx


Release Information

Provide link here to Release Notes
The following release notes were sent and the transports are not imported to NEP as the config changes are no longer required
2013-01-11 - 4614 - Rel Notes - Allocation Optimization
2013-02-01 - 4614 - Rel Notes - Allocation Optimization - Statistics Group