Load to psa is in yellow status only in quality n production system

Hi All,
We have created a generic FM which wil take date parameter as input and fetch records for that specific month. This FM works perfectly fine in dev server, but when i run the same in quality and production the load status is still in yellow status.
FYI, data records are fetched/extracted correctly and data package individually is in green status. But under extraction flow i see the following message " Missing message: Selection completed " at this stage the status is in yellow.
If i check the job in r/3 system then the last job log entry is
" Asynchronous transmission of info IDoc 3 in task 0003 (1 parallel tasks) "
Kindly suggest what can be done here to resolve this. We have stuck for quite long on this.
Thanks & Regards,
Anup

hi
debug the FM program , if you wont find any then try this.
you may missing messages in extraction process
try this
trun load to red and re-start and check the source system extraction process also check in the source system envio t Rfc-- in the source system ( to know the status)
Missing message: Selection completed
Error: 'Missing message: Selection completed' - URGENT
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=153780896
Data Loads into BI system
check this may help you.
Edited by: Srikanth.T on Dec 22, 2011 9:47 AM

Similar Messages

Write incorrect record to Unix file and not load to PSA

Hi,
Is there anyway to write an incorrect record to a file from the transfer rules, such as if the record is not found after a search through one of the master data table, it should not load to the PSA but write to a UNIX file? What would be the ABAP code?
Thanks,
Will

Hi Will,
Transfer rules are processed after data are loaded to PSA. So you can only avoid that records are updated to info providers and write them to a file on your application server.
If you really want to manipulate records in PSA you need to load required data to PSA within a process chain and to add a report that deletes the records from PSA and writes them to a file.
The steps are
1. Transfer rules
     1.create a start routine
     2.load required masterdata to an internal table
     3.loop at datapak
     4.delete records according to conditions
     5.append records to an internal table
     6.load file from internal table
2. PSA
     1..Create a report
     2. Load PSA request into an intenal table
     3.load required masterdata to an internal table
     4. loop at internal PSA
     5 .delete records according to conditions
     6.append records to an internal table
     7.load file from internal table
Hope this helps
Joe

Hierarchy loading Error in Production system

Hi All,
I am loading Hierarchy file, the file is there in application server(AL11), in external tab i gave same path. but when i try to load it is showing below Error message.
Invalid entry, hierarchy 0XMK4PVWO05BM4GP5KVEFQ9L4 does not exist.
Diagnosis
Hierarchy 0XMK4PVWO05BM4GP5KVEFQ9L4 does not exist.
Procedure
If the underlying InfoObject supports hierarchies create the hierarchy and try again.
If hierarchies are not supported, select another InfoSource or change the definition of the InfoObject.
That means Hierarchy file problem (OR) In Info package I selected Hierarchy selection problem?
Kidnly help on this issue.
Cheers,
Srikanth.
Edited by: srikanth on Apr 21, 2009 11:49 AM

Is this only happening in your production system? Have you tried loading the hierarchy file to your development or acceptance system?
I've seen this error occur when the authorizations are not set up for loading hierarchies (i.e. maybe they can only be loaded via process chains under the remote ID used for process chains, and not using your own ID). That's why I was suggesting you try to load the same file to your dev and acc systems and see if you get the same error. Sometimes this error is thrown for other reasons and does not really have to do with the file being loaded or the hierarchy missing.
Also, if you're loading from the App Server, double-check that you have the Application Server radio button selected on the tab where you select the file path.
Good luck!

Problem while loading data from quality to production

Hai,
We are using standard extractor 2LIS_11_VASCL, and in test case in QTY 300, we were able to make some changes and see the changes and see the results of the changes in T-CODE RSA3. When we try the same changes in PRD300, No Changes are triggered and T-CODE RSA3 shows no changes.
Can any one suggest me regarding this prolem...

Hi bandi,
Instead of trying for the same changes in production, why cant you do the transport the object from Quality to Production & then check for the changes in RSA3.
You are transporting the object only from Quality to production.
As no data is present in PRD, u may not be finding any changes in RSA3.
Hope it helps.

PSA load remains in yellow status.

Hi Gurus,
I have created a generic datasource based on function module.
I have replicated the datasource in SAP BI dev instance.
I have even checked the extractor checker in R/3 and it shows 381 records.
On BI side I am loading data upto PSA.When I execute the infopackage for full load in the monitor screen I could see
"381 out of 0 records".The request remains in yellow status.
The idoc status in source system side is 03 and on BI side is 53.
I dont get any error message.Even I am not seeing idocs with red status in SM58 tcode.No logs are seen in sm21.
I even asked the basis team to check for RFC connection SM59 and partner profile.Every thing looks fine .
This loading issue is only happening with this specific datasource(ie datasource created on function module).
For other datasources load are carried out fine.
Has anybody faced a similar issue?.Please help in this regard.

seems the load is hung bcoz of thehung IDOCs.
Process the idocs manually. after
check the below things
--> Check weather the source system job finished or not?
If the job is finished check the TRFCs are processed or not?
In the monitor screen - menu bar --environment -->job overview (to check the job) -->TRFcs - to check the TRFCs.
Check for short dumps using transaction ST22.
-->Check for the Idocs in BD87 and if there are any IDOCs got stuck process them manually.
To process Idocs first change the status of request to red and try to process them in the background.

ERROR in XI TO BI INTEGRATION PSA in yellow status

Hi, I have a scenario of XI 2 BI (JDBC to ABAP proxy), I have done the configuration and in SXMB_MONI it is showing processed successfuly. in BI Side message is succesful in SXMB_MONI
but PSA Data is not updating. when i go to t code RSA1 and then manage PSA , there status is yellow
"process is not yet complete" while i can see datais inserted in the table
can anybody tell me what change should we done so that we can receive green status in PSA.
regards

Hi Sandeep,
Please have a look at the following links and see if it helps
Re: data can not be loaded into PSA iva process chain
Re: Yellow flag in PSA and Cube for full load mean?
Best Regards

PSA request is in yellow status

Hi
We got the problem when loading the 2LIS_03_BF data into cube. We have around 4 cubes and 2 ods.
The data got loaded into all the cubes and ods except on Cube. There was a problem of table space and now it is solved.
Now the request is in yellow status in PSA. It cube it shows no of records added and transferred but the status is in red color.
How can i upload the delta data into the cube from PSA when PSA request is in yellow color.
I feel strange that when the request is in yellow color how come the data is loaded into all other cubes.
REgards
Annie

You should be able to load request from PSA to data target using the option available in PSA. When you manage on Datasource, you see all requests. You can select that PSA request and use Scheduler option in that screen to update that particular request. It will run infopackage as usual. It will execute all the routines if there are any in update rules.
When you say you have some programs running in process chain, they must be after this failed load right?
If that is the case, all you need to do is push process chain further. Below are steps to push process chain further if you any step is stuck in yellow or if mually carry out any red step in process chain. In you case, load that failed step manually using scheduler form PSA manage tab and then push PC further using these steps. That will continue PC further and run any programs that run after load.
Execute in SE38 -> RSPC_PROCESS_FINISH
Fill the following parameters on screen and rest all can be left blank.
1. LOGID - you will find this when you do monitor of your process chain. Every time you run process chain, unique LOGID is created.
2. TYPE - If step is ODS activation then TYPE wud be ODSACTIVAT and if it is infopak loading TYPE wud be LOADING and if it is DTP Load TYPE wud be LOAD. In your case it will be LOADING.
3. VARIANT - In the process chain monitor mode, right click on step which you executed manually -> Display Messages. Go to chain tab and there you will find VARIANT
4. INSTANCE - In the process chain monitor mode, right click on step which you executed manually -> Display Messages. Go to chain tab and there you will find INSTANCE
5. STATE - Value wud be G
After entering above parameters, click execute. It will be done in fraction of second and wont give any popup. Now when you will check process chain monitor, you will see that step 4 is green and next step has started executing.
Abhijit

Data load from R3 to BW shows yellow status

Hi Guru's,
While extracting the data from R3 to BW, BW is receiveing all the packages e.g. 10 packages. But out of 10, one of the package is showing in the yellow status and the rest in the green status.
Overall the Status is shown as yellow but the messages display in the Monitor that all the records are fowarded and received.
I have this loads in the process chains and because of this issue, my process chains are not getting executed further.
Could any one of you tell me how to resolve this issue.
Is this an issue that BW consultant should resolve or is this a BASIS issue ?
Thanks for your help !

No error messages are found in the Monitor.
I tried thrice executing the process chain and it does the same.
Any clue ?
Thanks,

DTP load in Yellow status forever

All,
The DTP load to this particular remains in Yellow status forever even though the transferred records are just 5000. After observing the dump, it shows problem where a select query to a table is done in the end routine of the transfroamtion.
The select is on a big master data table (material) but when I gave the selection by itself in SE16, there were not many records - just 3000. then why would the trace say that all the time is being spent querying this database table?
This was all working in D but not in q
Another important note is that there was no scuh change to the material table. however, there were four attributes to which we had enabled 'conversion' in the transfer structure
Would this be an issue if not the code itself?
Thanks

Any updates please?
MORE iNFORMATION:
The dtp loads from one DSO to another. I checked a similar scenario in the same system - things look fine.
I have an end routine in the transformation. when I look at the dtp monitor for the status, it says:
Extract. from DataStore xxxx: 4709 Data Records ---status GREEN
Filter Out New Records with the Same Key : 5000 -> 5000 Data Records------status GREEN
ODSO xxxxx-> ODSO yyyyy-----status YELLOW
-Transformation Start---status GREEN
-Rules---status GREEN
-End Routine---status GREEN
No Message: Transformation End
No Message: Update to DataStore Object yyyyyy
No Message: Set Technical Status to Green
No Message: Set Overall Status to Green
Thanks!

The data has been updated-loaded upto PSA only

Hi,
The data has been updated-loaded upto PSA only even though the processing type
has update into PSA and then into data targets. Please let us know what can be problem and what will be the solution for this.
Regards,
Raghav

Hi Kolli,
Do you have the further update from PSA process in your process chain? You will need this if the InfoPackage has the 3rd option on the Processing tab (PSA and then to data targets).
Hope this helps...

Data Loading is in Yellow Status

Hi All,
I have scheduled the data using info package.I have Checked in RSMO and after long time, the job is in the yellow status. I have checked the job in SM37 in R/3 side and found the status as "Released".
And data is not pulling into BW.
Can you provide how to rectify this.
Thanks,
Siva.

Hi there,
Your job is stucked on the R/3 side (probably no more process available on R/3 side).
Normally I could "force" that job, but I don't actually remember all of the steps.
Try this:
go to sm37 and for that particular job that is in the released state, select it and in the Menu choose Job->Released->Schedule
This will start your job, if not, you can still find it in sm37 with the status "Schedule". Select it again and choose Release. This will or start your job immediatly or prompt to when you want to start your job. Select immediatly and this will start your job.
Diogo.

My BDOCs in CRM are all waiting with yellow status

I don't know why my BDOCs(transaction smw01) are all waiting with yellow status. Shouldn't they be automatically transfering data to my data source. If i manually process the BDOC then data goes to the datasource which can be seen via transaction RSA3. Help?
Message was edited by: Prakash Singh

hi Prakash,
again oss note 692195-FAQ: Sales Analytics and CRM-BW data Extraction ?
bwa5 and bwa7, delta is activated ?
and initialization performed in bw ?
626214 619122
3. If there are queues in SMQ1 with erroneous status then activate
   these queues.
   In Transaction SMQ1 if there are Queues existing with
   names beginning with CRM_BWAn (n is number) then
   activate these queues in the same transaction.
4.a)If required activate the datasource
    Go to transaction BWA5   > select the required datasource and
    activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
  selecting the name of the datsource and pressing the candle icon for
  'activate delta'.
Symptom
There may be problems or issues related to data tranfer from CRM to BW.
Other terms
CRM-BW extraction,upload,initial,delta,full upload ,Sales Analytics,
Reason and Prerequisites
There could be errors in customization or program errors due to which
data may not be transferred or incorrectly transferred to BW.
Solution
Question 1 : The Extraction from CRM to BW takes a very long time. What
can be done? (Performance Issues)
Question 2 : On executing transaction RSA3 I get records but I find 0
records when I load data from BW request.(No Data Available).
How can I extract data in this case?
Question 3 : The Deltas for my data source are not extracted . What can
I do?
Question 4: How can I extract the fields, which are not provided in the
standard data source extraction ?
Question 5: I am unable to extract user status correctly.What should I
do?
Question 6 : What can I do when the activity/Opportunity/Complaint
reasons(Code,CodeGruppe,Katalogart) are not extracted?
Question 7: What can I do if the deleted opportunities
are not reflected in BW?
Question 8: How do I activate the metadata?
Question 9: I donot get any records for the delta upload of my attribute
datasource(s).What is to be done?
Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0
and various other BW status mean ?
Solutions
Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues)
Suggestion 1: Please implement notes 653645 (Collective note) and
639072(Parallel Processing).
The performance could be slow because of the wrong control parameters
used for packaging.
You can change the package size for the data extraction.
Also note that changing the package size in the transaction SBIW
would imply a change for all the extractors. Instead, you could
follow the path in the bw system.
Infopackage (scheduler)    > Menu 'Scheduler'   > 'DataS. default data
transfer'   > maintain the value as 1500 or 1000(This value is variable)
The package size depends on the Resources available at the customer side
(The no of parallel processes that could be assigned =
1.5 times the no of CPU's available approx.)
Question 2 : On executing transaction RSA3 I get records but I find 0
records when I load data from BW request.(No Data Available)
Suggestion 2: First check if there are any entries in the table
CRMD_ORDER_INDEX.Only if there are entries in this table you can
extract records.
If this is not the case then,
It is possible that the user does not have sufficient
authorities for extraction of the relevant objects.
Additionally, please review and implement the following notes
615670
161570
150315
618953
If you are in the release 4.0 then
To do BW extraction with the user please see that the following
authorization object exists(display mode is enough):
CRM_ACT, CRM_OPP, CRM_LEAD, CRM_SAO, CRM_SEO, CRM_CO_SE, CRM_CO_SC
CRM_CO_SA, CRM_CON_SE, CRM_CMP, CRM_ORD_OP, CRM_ORD_LP, CRM_ORD_PR
CRM_ORD_OE, CRM_CO_PU, CRM_CO_PD, CRM_ORD_PO
(all these objects are linked to transaction crmd_order).
Question 3 : The Deltas for my data source are not extracted . What can I do?
Suggestion 3: Please check the following.
Please Check if the services have been generated in transaction GNRWB.
If they are not active(not marked 'X' before their names) then activate
the services following the steps here.
Go to transaction GNRWB
Select BUS_TRANS_MSG
Select (on the right, the services) : BWA_DELTA3, BWA_FILL, BWA_queue
Press Generate.
Also check for the following:
1. The delta should have been initialized successfully.
2. Confirm that all Bdocs of type BUS_TRANS_MSG
   are processed with success in SMW01.
3. If there are queues in SMQ1 with erroneous status then activate
   these queues.
   In Transaction SMQ1 if there are Queues existing with
   names beginning with CRM_BWAn (n is number) then
   activate these queues in the same transaction.
4.a)If required activate the datasource
    Go to transaction BWA5   > select the required datasource and
    activate.
4 b) The Delta may not be active ,activate the delta in BWA7 by
selecting the name of the datsource and pressing the candle icon for
'activate delta'.
5. In BW system
   Go to transaction RSA1   > modeling   > infosources   > select the
   infosource   > right mouse click on the selected
   infosource   > choose option replicate datasource
    Activate the infosource.
6. Go to the scheduler for the infosource   > select delta in the
    update >choose the option PSA only (in the Processing tab)
    > start immediately
Check the entry in the RSA7 in the OLTP(CRM system)
Question 4: How can I extract the fields, which are not provided in the standard data source extraction .
Suggestion 4: Follow the steps mentioned below.
1. Enhance Extract Structure with the required fields. (Create & include
   an append structure to the extract structure via transaction RSA6).
2.a) Release the fields of the append for usage. ( To do this, double
   click on the Datasource and remove the flags in the column 'Hide
   Field' for all fields of Append. )
2.b)If the new fields cannot be seen in the extract structure of
    the transaction BWA1 then change and save the datasource, and then
    activate it in RSA6.
3. Define your mappings in BADI (CRM_BWA_MFLOW) to fill these fields.
Goto SPRO .
Follow the path ->
SAP Implementation guide ->Implementation with other mySAP components ->
Data transfer to the Business Information Warehouse->
Settings for the application specific datasources (CRM)->
Settings for BW adapter->
Badi :BW adapter :Enhancement of datasources in messaging flow.
4. Replicate the new Datasource to BW.
5. Expand the Communication Structure in BW.
6. Maintain transfer Rules for the new Datasource.
7. Activate the trasfer rules and perform the upload.
Question 5: I am unable to extract user status correctly.What should I
do?
Suggestion 5 :Check the following notes
531875
616062
713458
700714
765281
Question 6 : What can I do when the activity/Opportunity/Complaint
reasons(Code,CodeGruppe,Katalogart) are not extracted.
Suggestion 6 :Check the following notes
481686
516820
603609
617411
711146
Question 7:Deleted opportunities are not reflected in BW.
Suggestion 7: Check the note 706327.
Question 8: How do you activate the metadata?
Suggestion 8:CRM BW adapter meta data has to be activated first before
it is available in the system. You can use Transaction BWA5 to copy the
meta data for selected DataSources. You can reach the transaction via
the IMG maintenance 'SAP Reference IMG -> Settings for SAP Business
Information Warehouse -> Activate BW Adapter Meta Data'. For more
information, see the documentation on the IMG activity 'Activate BW
Adapter Meta Data'. (Note 432485)
Question 9: I donot get any records for the delta upload of my attribute
datasource(s).What is to be done?
Suggestion 9: In case of attribute datasources, it is possible that the
entry for the GUID is missing in the table SMOXAFLD.
If , for example the datasource 0CRM_OPPT_ATTR is not giving deltas
then you can follow the steps:
1)If Delta process is active for the attribute datasource e.g.
     0CRM_OPPT_ATTR, then stop the delta process in the BW
     system
2) In the CRM system, Make the entry in the table SMOXAFLD
   for the datasource with the Key
   as 0CRM_OPPT_ATTR     GUID 3) Save the entry.Activate the datasource                           4) Check that the above entry is replicated in smoxafld_s also    after this.               5) Create a transport request manually for the following    object             R3TR   SMO4   0CRM_OPPT_ATTR
Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0 and various other BW status mean ?
Suggestion 10: The BW status are used to extract system and user defined
status.
The BW status are defined in the customization settings in SPRO.
Check for-> Status Concept for BP/Product/CRM objects
Here goto-> Process user status You will find the documentation attached here for the user status. Going inside the transaction you will find the status groups USS0, ZIOP,ZMOP etc. The names of the various BW status are derived from this For ex. BW + ST+ One + USS0 gives the name of the field BWSTONEUSS0 or BWST + ONE + ZMOP = BWSTONEZMOP (Master opportunity values) (which means BWST + (status group name) + status object group name) Double clicking on any of the object groups will take you to the values that these status can have . For ex. BWSTONEUSS0 in your system can have values E001 ,E002,E003,E007 which will be shown in RSA3 as BW status values 1,2,3,7, respectively.
Similarly we have Goto -> Process system status (in SPRO). Here you can get the values for the system status in exactly the same way as BWSTONESYS0(Lifecycle status) , BWSTTECSYS2 (Error) etc. In RSA3 you get the names as BW status, To know which corresponds to which status here,Goto the record list in RSA3 . Here goto Settings - Layout -Current . Right click -> Press Show technical field names . You will be able to see the BW status names and will be able to adjust the layout accordingly.

Request status in infocube is always in yellow status..

Hi Friends,
We are loading the data from 3 ODS to one infocube but all the requests from ODS to infocube is always haivng yellow status ( even though load is completed without any errors). We are manually changing the status to Green.
Any suggestions regarding this problem...
Thanks in advance

Symptom
All requests in InfoCubes have the QM status 'yellow traffic light'.
Solution
In the InfoCube administration in the menu
'Environment -> Request handling...'
activate the flag 'Set quality automatically' on the popup 'Maintenance of the automatisms'.
This flag was of no importance before BW Release 2.0.
This flag is interpreted actively as of BW Release 2.0. For InfoCubes where this flag is deactivated, every request must be set manually to green (available for reporting) or red (incorrect) by a QM action.
As a result, the individual request can have a different status independent from its monitor load status in different InfoCubes.
After upgrading from BW1.2B to BW2.0, the flag is interpreted, but is not set for any of the old InfoCubes.
Therefore data, including old data, is not automatically visible in reporting, if it is not rolled up or compressed.
In order to accomplish this, you can either activate the flag 'Set quality automatically' or set every request manually to green (administering the InfoCube on the 'Requests' tab in column 'QM status of the request after update').
This is a button column that only affects the status of this request in this InfoCube!
By setting the QM status in the monitor for the load log of this request you can set all QM statuses of this request in all updated InfoCubes simultaneously.
If you change this flag, you choose button 'Refresh' in the tabstrip 'Requests' so that the flag will interpreted and the requests are set to 'Green' in the InfoCube and thus displayed in Reporting.

Why PSA data show red status when opened but green on PSA page?

Run RSA1 -> click PSA to open PSA page, locate one infosource and find the PSA under it, find the status column shows it's green, but when opening it, find the 1st column shows red for each row. How does the inconsitance occur?
BTW, if we open the infopackage monitor for the above one, find a weird thing is that each request get two consecutive processes running with a circle of red ball and green ball in the left frame. Double click one of them, in the right frame and click the monitor Status tab, the msg window is as following (in between two dashed lines below):
Incorrect data records - error requests (total status GREEN)
Diagnosis
Data records were recognized as incorrect.
System response
The valid records were updated in the data target and can be used in reporting.
The incorrect records were not written to the data target, but were posted retractively under a new request number in the PSA.
Procedure
Check the data in the error requests, correct the errors, and post the error requests.
Sounds like the data failed to uploaded to data target due to error in PSA, but why the status show green in somewhere? And if clicking the Details tab, all show green! Weird!
Thanks

Hi Kevin,
In your InfoPackage Update tab, click the Error Handling button. It seems that the Valid records update, request green option is chosen. This is why you see the green request and some error records.
This means that the corect reocrds were loaded and are available for reporting, but the incorrect ones were left behind. This is used to check the erro records separatelt so that they do not disrupt the entire data load.
Hope this helps...

FM to read yellow status requests from transactional InfoCube

Hi,
I am using the FM RSDRI_INFOPROV_READ to read data from the transactional InfoCube. My problem is that my code using this FM should be able to read data requests that have the yellow status for the transactional InfoCube.
My code using this FM is able to read data from the green requests only but not the yellow requests. I was told in BPS, the yellow requests should turn green automatically after 50K of records have been queue up and ready to be turned green by itself.
Has anyone come across this and help me solve this issue of reading data using FM RSDRI_INFOPROV_READ to read yellow request data. Is there another FM to read both the green and yellow requests?
Please advise. Thanks
RT

Hi Rob,
The function module mentioned by you is correct and it will read the yellow requests please try this, by default the parameter i_rollup_only is set as true set it to false (blank) while calling the function module.
Please see the attached code
CALL FUNCTION 'RSDRI_INFOPROV_READ'
   EXPORTING
     i_infoprov             = p_infocube
     i_th_sfc               = t_sfc
     i_th_sfk               = t_sfk
     i_t_range              = lt_range
     I_PACKAGESIZE          = p_pksize
     i_rollup_only          = rs_c_false
   IMPORTING
     e_t_data               = <fsl_data_read>
     e_end_of_data          = w_end_of_data
   CHANGING
     c_first_call           = l_first_call
   EXCEPTIONS
     illegal_input          = 1
     illegal_input_sfc      = 2
     illegal_input_sfk      = 3
     illegal_input_range    = 4
     illegal_input_tablesel = 5
     no_authorization       = 6
     ncum_not_supported     = 7
     illegal_download       = 8
     illegal_tablename      = 9
     trans_no_write_mode    = 10
     inherited_error        = 11
     x_message              = 12
     OTHERS                 = 13.
Hope this was helpful.
thanks

Load to psa is in yellow status only in quality n production system

Similar Messages

Maybe you are looking for