Many times we face failure of transactional data load due to No SID found to load transactional data.
For fixing Such type of failure I have explained the workaround with the help of an example.
Let’s take an example of 0Employee, here we have a failure of transactional data load due to no SID found for value 10883250 of Characteristics 0EMPLOYEE. You can find this error in erroneous record of the PSA as shown in the below screen.
You can cross check the existence of employee 10883250 by doing Maintain Master data on 0EMPLOYEE in RSA1 you will not get the corresponding record.
Now we need to check the Master Data for the employee 10883250 in the source system.
1) Login to ECC & go to RSA3 (Extractor Checker), Put 0EMPLOYEE_ATTR as the candidate data source. Run the extractor for Personal Number = 10883250.
2) If you will be able to find the record for Personal Number = 10883250 then proceed with the next step else reach out to the responsible team who will maintain the master data for this employee in the source system.
3) If records found after executing the extractor checker from RSA3.
4) Then we will manually load that employee from ECC to BW for this follow the below steps.
a) Create infopackage (if not existing) for loading Employee Attribute in our case you can use 0EMPLOYEE_ATTR: Employee-17.07.2013
b) In the data selection tab of the infopackage enter the Personal Number = 10883250, 0EMPLOYEE_ATTR: Employee-17.07.2013
c) Save the infopackage click on schedule tab click on Start button to start the load from source system. 0EMPLOYEE_TEXT: Employee texts 17.07.2013.
d) Once started click the monitor button to monitor the extraction.
Here you can see below 1 records extracted.
e) You can check the PSA data, 1 record updated for the employee 10883250.
f) Once Employee attribute data has been loaded we have to load Employee Text data.
The steps for loading text data is same as loading Employee Attribute.
g) Execute Attribute Change run for 0Employee if its pending. Follow the below steps
Go to RSA1 -> Click on Tools -> Execute Hierarchy/Attribute Change for Reporting -> Click on InfoObject List -> if you find 0EMPLOYEE in the pending object list then save it & click on execute button at the bottom of the screen, monitor the process from SM37 once completed proceed with the next step.
5) Load 0Person Master data.
a) Create infopackage (if not existing) for loading 0Person Attribute in our case you can use 0PERSON_ATTR: Person Attributes - July MM FY13
b) In the data selection tab of the infopackage enter the Personal Number = 10883250
c) Save the infopackage click on schedule tab click on Start button to start the load from source system.
d) Once started click the monitor button to monitor the extraction.
Here you can see below 1 records extracted.
e) You can check the PSA data, 1 record updated for the employee 10883250.
f) Once Employee attribute data has been loaded we have to load Employee Text data.
The steps for loading text data are same as loading Employee Attribute.
g) Execute Attribute Change run for 0Person if its pending. Follow the below steps,
Go to RSA1 -> Click on Tools -> Execute Hierarchy/Attribute Change for Reporting -> Click on InfoObject List -> if you find 0Person in the pending object list then save it & click on execute button at the bottom of the screen, monitor the process from SM37 once completed proceed with the next step.
6) You can cross check the data which we have loaded by maintain the master data for 0EMPLOYEE & 0Person in RSA1 by the employee number in RSA1.
7) Once attribute change run completed for 0Person delete the red request from the target cube.
😎 Then go to the process chain network display, right click on the failed step of the process chain & then click on Repeat as shown below.
9) Monitor the Process chain from Se38 -> /SSA/BWT(Program) -> Process chain -> select the date.
The failed step will get completed now.
- SAP Managed Tags:
2 Comments
