Support Issues

S.NO-21

ERROR AT SYSTEM DOWN TIME

PROBLEM: Load Failed in Process Chain - Controlling Weekly Load.

ERROR:

SOLUTION: Failed due to System Downtime. And called Basis to raise P1 (Be aware of System Down
Time).

1|Page
 Support Issues

S.NO-22

Kill the Job in SM50 as shown below

2|Page
 Support Issues

Kill the job in SM37 as shown below

S.NO-23

CONTROLLING TRANSACTION CHAIN

PROBLEM: tRFC piled up - Controlling transaction Data due to huge data by full update
(ZPAK_4EMJQLEUPMZKV2X2AU3IV4N82).

SOLUTION: To avoid the tRFC pile up, the Infopackage (ZPAK_4EMJQLEUPMZKV2X2AU3IV4N82) has
been changed from full load to delta load through routine as shown below.

OLD:

No Routine.

NEW:

data: l_idx like sy-tabix.

Data: t_start_date like sy-datum.

t_start_date = sy-datum - 10.

read table l_t_range with key

fieldname = 'AEDAT'.
l_idx = sy-tabix.
*....

3|Page
 Support Issues

l_t_range-low = t_start_date.
l_t_range-high = '99991231'.
l_t_range-sign = 'I'.
l_t_range-option = 'BT'.

modify l_t_range index l_idx.

p_subrc = 0.

S.NO-24

PROBLEM: Master Data chain running long time in the level of -

Supply Chain Master Data – Attribute  Process Monitor Attribute Chang Run

4|Page
 Support Issues

Status show there is 4 objects completed out of 10 objects. And stuck up in 4 th object and running
more than 2 hrs.

And running long time as checked in SM50 as shown below,

Due to that – Delete Indexes got fail for the following process chains:

1. APO Process Chain

2. Controlling
3. SD Analytics

5|Page
 Support Issues

Delete Indexes failed in SD Analytics Transaction Data:

Delete Indexes failed in APO Daily Process Chain:

Delete Indexes failed in Controlling Transactional Data Process Chain:

6|Page
 Support Issues

SOLUTION:

GENERAL NOTE 1:

Generally attribute change run is used when there is any change in the master data. it is used
for realignment of the master data.

Attribute change run is nothing but adjusting the master data after its been loaded from time
to time so that it can change or generate or adjust the SID's so that u may not have any
problem when loading the transaction data in to data targets.

The detail explanation about Attribute change run. The hierarchy/attribute change run which
activates hierarchy and attribute changes and adjusts the corresponding aggregates is divided,
Into 4 phases:

1. Finding all affected aggregates

2. Set up all affected aggregates again and write the result in the new aggregate table.

3. Activating attributes and hierarchies

4. Rename the new aggregate table. When renaming, it is not possible to execute queries.

In some databases, which cannot rename the indexes, the indexes are also created in this
phase

GENERAL NOTE 2:

1. When a master data is changed/updated it gets loaded into the master data table as version
"M"(modified). It is only after a attribute change run that the master data becomes activated i.e.
version "A".
2. Master data attributes and hierarchies are used in cube aggregates also. So to do update the
latest master data attributes values in the aggregates attribute change run need to be performed.

ANKIT’S NOTE:

We shall be killing the existing run and then deactivate the DP aggregate which is taking a long
time. After which we should restart the change run, which should help in allowing the COPA
reports for reporting.

7|Page
 Support Issues

Cancel Job in SM37: According to the above notes, the Attribute Change Run Job in Master
Data PC has been killed in SM37 as shown in the screen shot below. And first kill which is
started late (in this case Duration 14,529).

Cancel Job in SM50: Still if the job is running in SM50, kill as shown in the screen shot below.

Deactivate the Aggregate:

Deactivate the Aggregation for ZAPODP001 (process locked and was running long time).

8|Page
 Support Issues

REPEAT: And Repeated the Job Again

Once this Attribute Change Run job has been completed, the failed Delete Indexes Job has been
repeated as shown in the screen shot below:

Controlling PC: Once Master Data PC-Attribute Change Run job has been completed, REPEAT -
Delete Indexes

APO PC: Once Master Data PC-Attribute Change Run job has been completed, REPEAT - Delete
Indexes

9|Page
 Support Issues

SD Analytics Transaction Data PC: Once Master Data PC-Attribute Change Run job has been
completed, REPEAT - Delete Indexes

Once the Request in Infocube (Delete overlapping load request) is over, activate the Aggregate
manually.

Activate the Aggregate: Activate the Aggregate again for ZAPODP001 one by one as shown below

NOTE:

10 | P a g e
 Support Issues

- Once the DTP-APO DP Two Future Years Future Load completed, we can start activating the
Aggregate for ZAPODP001 (No need to wait for completing whole process chain).
- First activate Product Level and then Product & Org Level.

11 | P a g e
 Support Issues

ADDITIONAL NOTE:

While Master Data PC-Attribute Change Run job in the process you will not be able to delete
Indexes Manually.

12 | P a g e
 Support Issues

13 | P a g e
 Support Issues

S.NO-25

APO PROCESS CHAIN

PROBLEM: Infopackage: 9ADS_Z_DP_PA_001 - Rolling Two Future Years

(ZPAK_48NWOMQIH7Q8JM3EPO3VUSTLL) failed due to the Routine written for week 053 which is
not available for year 2010 & 2011 (Only week 052).

Note: This Infopackage is same for WSR and APO Process Chain.

ERROR: The following Error occurred in the Process Monitor.

14 | P a g e
 Support Issues

PROBLEM: Failed due to the routine in the following Process Chain.

15 | P a g e
 Support Issues

NOTE:

Tep_WSR_053 (ZPAK_4GAO8B6XII8D3883CW22M12Z1)

16 | P a g e
 Support Issues

17 | P a g e
 Support Issues

18 | P a g e
 Support Issues

S.NO – 26

Step 1 – Creation of New Process Chain

Step 2 – Creation of Start function

19 | P a g e
 Support Issues

Step 3

20 | P a g e
 Support Issues

Step 4

21 | P a g e
 Support Issues

Step 5 – Creation of DTP

22 | P a g e
 Support Issues

Creation of Delete Indexes

23 | P a g e
 Support Issues

S.NO-27

Transport Request for New Infopackage Creation

Creating New Infopackage, need to create Transport Request and forward to Basis Team to get
load/impact from D system to U system.

24 | P a g e
 Support Issues

Give the Description and Save as shown below,

Verify the Package and Save

Create the new Request as shown below screenshot.

25 | P a g e
 Support Issues

The new Infopackage has been created and verify the required selection in Each Tab.

26 | P a g e
 Support Issues

Then go toSE09 and check the Job with below selection.

Find the request below, which has been created for Infopackage creation.

27 | P a g e
 Support Issues

First you release the Sub Job.

Then you Release the Main Job.

Finally send mail to Basis mentioning the Main Job to update to the U System.

28 | P a g e
 Support Issues

S.NO-28

Delete the setup table in LBWG as shown below.

To confirm the deletion of set up table, check in RSA3 as explained below.

The above RSA3 confirm the data deleted in the Setup table.

Fill the Setup table T-code OLI (A) BW or

T-code: SBIW->Business Information Warehouse->Settings for Application-Specific DataSources(PI)

->Logistics->Managing Extract Structures->Initialization->Filling in the Setup Table->Application-
Specific Setup of Statistical Data->

Select the required the Application (E.g.-

below is SD-Sales Orders-Perform Setup)

NOTE: Do you have experience in

enhancing datasource for Glbal client ? If
you have done enhancing the datasource
for a global client ( who runs business all
24/7 around the clock, in many
countries) how will go about for outage
(to fill the setup table) ?

29 | P a g e
 Support Issues

->You need to take down time and load the data to setup tables. No other option. On holiday lock
the ECC server for 6 to 12 hours and do it.

After filling Setup table check the number of record in RSA3 (Extractor Checker) as shown in the
following screen.

Aggregate Fill up as shown below.

30 | P a g e
 Support Issues

31 | P a g e
 Support Issues

LO Data Extraction – T-code LBWE ->Select (Double Click) the name of the Datasource as shown
below.

32 | P a g e
 Support Issues

SM37 – Job View

33 | P a g e
 Support Issues

T-Code LBWQ for Monitor

Reference Site - http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0709b9f-

acbc-2c10-7a95-ab0ee18b921c?QuickLink=index&overridelayout=true

Test - Compression

34 | P a g e
 Support Issues

S.NO-29

35 | P a g e
 Support Issues

SD Analytics Transaction Data

Check List: Check the PSA table for how many records it is giving invalid records.

Solution: Delete the requests from both the targets and then go to PSA edit the erroneous records,
Save them. Then go to Data source in RSA1 and go to manage tab for that particular infopackage and
there will be error requests for today then select the Update with scheduler at the bottom then
activate the targets all the updated records will move from PSA to targets.

Note: If we forget to activate targets then it shows DSO activation got failed find the below screen.

36 | P a g e
 Support Issues

37 | P a g e