Showing posts with label Data Loading issues. Show all posts
Showing posts with label Data Loading issues. Show all posts
13 Oct 2008
Function module to make yellow request to RED
Use SE37, to execute the function module RSBM_GUI_CHANGE_USTATE.From the next screen, for I_REQUID enter that request ID and execute.From the next screen, select 'Status Erroneous' radiobutton and continue.This Function Module, change the status of request from Green / Yellow to RED.
25 Sept 2008
What will happend if a request in Green is deleted?
Deleting green request is no harm. if you are loading via psa, you can go to tab 'reconstruction' and select the request and 'insert/reconstruct' to have them back.But,
For example you will need to repeat this delta load from the source system. If you delete the green request then you will not get these delta records from the source system.
Explanation :
when the request is green, the source system gets the message that the data sent was loaded successfully, so the next time the load (delta) is triggered, new records are sent.
If for some reason you need to repeat the same delta load from the source, then making the request red sends the message that the load was not successful, so do not discard these delta records.Delta queue in r/3 will keep until the next upload successfully performed in bw. The same records are then extracted into BW in the next requested delta load.
For example you will need to repeat this delta load from the source system. If you delete the green request then you will not get these delta records from the source system.
Explanation :
when the request is green, the source system gets the message that the data sent was loaded successfully, so the next time the load (delta) is triggered, new records are sent.
If for some reason you need to repeat the same delta load from the source, then making the request red sends the message that the load was not successful, so do not discard these delta records.Delta queue in r/3 will keep until the next upload successfully performed in bw. The same records are then extracted into BW in the next requested delta load.
20 Sept 2008
PSA reverse posting
When the data is loaded to BW Infocube and then it is compresed then u can't delete the data pertaining to this request in the cube . For this what u can do is if the request is loaded via PSA then u can click on the Request Reverse Posting option on the MOnitor screen of the particular Request . This will reverse the sign of the keyfigures loaded into the InfoCube for that particular request only ,so that it will make overall keyfigyure value in the cube for this particular request to 0
Reverse posting to be done by system @ Monitoring --> Scheduler --> Reverse posting --> Immediate & Save.
This will nullify the before request values by sending reverse values.
This can be done only if the loaded data is still present in PSA.
Reverse posting to be done by system @ Monitoring --> Scheduler --> Reverse posting --> Immediate & Save.
This will nullify the before request values by sending reverse values.
This can be done only if the loaded data is still present in PSA.
19 Sept 2008
Unable to Cancel Job in SM37 (R3)
Question from sdn :
We got a situation :Unable to Kill the Background job (BI_REQ*).It shows "ACTIVE" and been running for more than 19,000 secs (2 days..) .When this job started ,the PROCESS ID was : 244277..But after a day,this PROCESS ID : 244277 has been allocated to some other R3 Program(Monitored in SM50).But the Background Job is still "ACTIVE".Tried killing the Job in SM37--->Cancel Active Job or Delete the Job) but ,when tried to "Cancel" the Job,we get a message : The job is NOT ACTIVE !!!. Then when tried to "DELETE" the job ,we get a message " Job is still ACTIVE"......!!!!
----->Since there is no Work Process in SM50,what is the alternative solution to Kill this Job..........???
(In BW ,there is no Update of data records,with the monitor showing
Answere :
Go to SM37 >> select the job >> Click on the JOB tab in the top >> Click on Check status............
Then it status will show cancel...........
Actually sometimes it happens job gets cancelled but staus shows active....then we need to do this..........actually job is already cancelled......
We got a situation :Unable to Kill the Background job (BI_REQ*).It shows "ACTIVE" and been running for more than 19,000 secs (2 days..) .When this job started ,the PROCESS ID was : 244277..But after a day,this PROCESS ID : 244277 has been allocated to some other R3 Program(Monitored in SM50).But the Background Job is still "ACTIVE".Tried killing the Job in SM37--->Cancel Active Job or Delete the Job) but ,when tried to "Cancel" the Job,we get a message : The job is NOT ACTIVE !!!. Then when tried to "DELETE" the job ,we get a message " Job is still ACTIVE"......!!!!
----->Since there is no Work Process in SM50,what is the alternative solution to Kill this Job..........???
(In BW ,there is no Update of data records,with the monitor showing
Answere :
Go to SM37 >> select the job >> Click on the JOB tab in the top >> Click on Check status............
Then it status will show cancel...........
Actually sometimes it happens job gets cancelled but staus shows active....then we need to do this..........actually job is already cancelled......
17 Sept 2008
Attribute delta loading "duplicate record found"
Master data attribute loading error: "x duplicate record found. y recordings used in table z "
Fix:
Option in InfoPackage "Ignore Double Data Records"
OR
Make "Change Run" tool run for every upload.
OR
In start routine of Transfer or Update rules make a sort of record of the package and then delete adiacent duplicates.
Fix:
Option in InfoPackage "Ignore Double Data Records"
OR
Make "Change Run" tool run for every upload.
OR
In start routine of Transfer or Update rules make a sort of record of the package and then delete adiacent duplicates.
Production Support Issues in BW
Production Support Errors :
1) Invalid characters while loading: When you are loading data then you may get some special characters like @#$%...e.t.c.then BW will throw an error like Invalid characters then you need to go through this RSKC transaction and enter all the Invalid chars and execute. It will store this data in RSALLOWEDCHAR table. Then reload the data. You won't get any error because now these are eligible chars done by RSKC
2) IDOC Or TRFC Error:
We can see the following error at “Status” Screen:
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely connected to the SAP BW. Check especially the authorizations of the background user in the source system.
Action to be taken:
If Source System connection is OK Reload the Data.
3)PROCESSING IS OVERDUE FOR PROCESSED IDOCs
Diagnosis
IDocs were found in the ALE inbox for Source System that is not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs
manually using the Wizard or by selecting the IDocs with incorrect
status and processing them manually.
Analysis:
After looking at all the above error messages we find that the IDocs are found in the ALE inbox for Source System that are not Updated.
Action to be taken:
We can process the IDocs manually via RSMO -> Header Tab -> Click on Process manually
4) LOCK NOT SET FOR LOADING MASTER DATA ( TEXT / ATTRIBUE / HIERARCHY )
Diagnosis
User ALEREMOTE is preventing you from loading texts to characteristic
0COSTCENTER . The lock was set by a master data loading process with the
request number.
System response
For reasons of consistency, the system cannot allow the update to continue, and it has terminated the process.
Procedure
Wait until the process that is causing the lock is complete. You can call transaction SM12 to display a list of the locks.
If a process terminates, the locks that have been set by this process are reset automatically.
Analysis:
After looking at all the above error messages we find that the user is “Locked”.
Action to be taken:
Wait for sometime & try reloading the Master Data manually from Info-package at RSA1.
5) Flat File Loading Error
Detail Error Message
Diagnosis
Data records were marked as incorrect in the PSA.
System response
The data package was not updated.
Procedure
Correct the incorrect data records in the data package (for example by manually editing them in PSA maintenance). You can find the error message for each record in the PSA by double-clicking on the record status.
Analysis:
After looking at all the above error messages we find that the PSA contains incorrect record.
Action to be taken:
To resolve this issue there are two methods:-
i) We can rectify the data at the source system & then load the data.
ii) We can correct the incorrect record in the PSA & then upload the data into the data target from here.
6) Object requested is currently locked by user ALEREMOTE
Detail Error Message.
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.Object requested is currently locked by user ALEREMOTE
Procedure
Look in the lock table to establish which user or transaction is using the requested lock (Tools -> Administration -> Monitor -> Lock entries).
Analysis:
After looking at all the above error messages we find that the Object is “Locked. This must have happened since there might be some other back ground process running
Action to Be taken :
Delete the error request. Wait for some time and Repeat the chain.
1) Invalid characters while loading: When you are loading data then you may get some special characters like @#$%...e.t.c.then BW will throw an error like Invalid characters then you need to go through this RSKC transaction and enter all the Invalid chars and execute. It will store this data in RSALLOWEDCHAR table. Then reload the data. You won't get any error because now these are eligible chars done by RSKC
2) IDOC Or TRFC Error:
We can see the following error at “Status” Screen:
Sending packages from OLTP to BW lead to errors
Diagnosis
No IDocs could be sent to the SAP BW using RFC.
System response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of the SAP BW.
Further analysis:
Check the TRFC log.
You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Removing errors:
If the TRFC is incorrect, check whether the source system is completely connected to the SAP BW. Check especially the authorizations of the background user in the source system.
Action to be taken:
If Source System connection is OK Reload the Data.
3)PROCESSING IS OVERDUE FOR PROCESSED IDOCs
Diagnosis
IDocs were found in the ALE inbox for Source System that is not updated.
Processing is overdue.
Error correction:
Attempt to process the IDocs manually. You can process the IDocs
manually using the Wizard or by selecting the IDocs with incorrect
status and processing them manually.
Analysis:
After looking at all the above error messages we find that the IDocs are found in the ALE inbox for Source System that are not Updated.
Action to be taken:
We can process the IDocs manually via RSMO -> Header Tab -> Click on Process manually
4) LOCK NOT SET FOR LOADING MASTER DATA ( TEXT / ATTRIBUE / HIERARCHY )
Diagnosis
User ALEREMOTE is preventing you from loading texts to characteristic
0COSTCENTER . The lock was set by a master data loading process with the
request number.
System response
For reasons of consistency, the system cannot allow the update to continue, and it has terminated the process.
Procedure
Wait until the process that is causing the lock is complete. You can call transaction SM12 to display a list of the locks.
If a process terminates, the locks that have been set by this process are reset automatically.
Analysis:
After looking at all the above error messages we find that the user is “Locked”.
Action to be taken:
Wait for sometime & try reloading the Master Data manually from Info-package at RSA1.
5) Flat File Loading Error
Detail Error Message
Diagnosis
Data records were marked as incorrect in the PSA.
System response
The data package was not updated.
Procedure
Correct the incorrect data records in the data package (for example by manually editing them in PSA maintenance). You can find the error message for each record in the PSA by double-clicking on the record status.
Analysis:
After looking at all the above error messages we find that the PSA contains incorrect record.
Action to be taken:
To resolve this issue there are two methods:-
i) We can rectify the data at the source system & then load the data.
ii) We can correct the incorrect record in the PSA & then upload the data into the data target from here.
6) Object requested is currently locked by user ALEREMOTE
Detail Error Message.
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.Object requested is currently locked by user ALEREMOTE
Procedure
Look in the lock table to establish which user or transaction is using the requested lock (Tools -> Administration -> Monitor -> Lock entries).
Analysis:
After looking at all the above error messages we find that the Object is “Locked. This must have happened since there might be some other back ground process running
Action to Be taken :
Delete the error request. Wait for some time and Repeat the chain.
3 Sept 2008
Error loading master data - Data record 1 ('AB031005823') : Version 'AB031005823' is not valid
Problem
Created a flat file datasource for uploading master data.Data loaded fine upto PSA.Once the DTP which runs the transformation is scheduled, its ends up in error as below:
Solution
After refering to many links on sdn, i found that since the data is from an external file,the data will not be matching the SAP internal format. So it shud be followed that we mark "External" format option in the datasource ( in this case for Material ) and apply the conversion routine MATN1 as shown in the picture below:
Once the above changes are done, the load was successful.
Knowledge from SDN forums
Conversion takes place when converting the contents of a screen field from display format to SAP-internal format and vice versa and when outputting with the ABAP statement WRITE, depending on the data type of the field.
Check the info here:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/e9a20d3347b340946c32331c96a64e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/07/6de91f463a9b47b1fedb5be18699e7/content.htm
This fm ( MATN1) will add leading ZEROS to the material number because when u query on MAKT with MATNR as just 123 you wll not be getting any values, so u should use this conversion exit to add leading zeros.
Created a flat file datasource for uploading master data.Data loaded fine upto PSA.Once the DTP which runs the transformation is scheduled, its ends up in error as below:
Solution
After refering to many links on sdn, i found that since the data is from an external file,the data will not be matching the SAP internal format. So it shud be followed that we mark "External" format option in the datasource ( in this case for Material ) and apply the conversion routine MATN1 as shown in the picture below:
Once the above changes are done, the load was successful.
Knowledge from SDN forums
Conversion takes place when converting the contents of a screen field from display format to SAP-internal format and vice versa and when outputting with the ABAP statement WRITE, depending on the data type of the field.
Check the info here:
http://help.sap.com/saphelp_nw04/helpdata/en/2b/e9a20d3347b340946c32331c96a64e/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/07/6de91f463a9b47b1fedb5be18699e7/content.htm
This fm ( MATN1) will add leading ZEROS to the material number because when u query on MAKT with MATNR as just 123 you wll not be getting any values, so u should use this conversion exit to add leading zeros.
Subscribe to:
Posts (Atom)
