on 11-22-2005 4:30 AM
Hi Gurus.....,
when i am trying to check the status of the datasource i got the following error in <b>BWA1</b>.
i check both tables.., i didn't get what can i do there..., please let me know if any one knows it...
***************************************************
0CRM_QUOTA_ORDER_I: Fld PATH_GUID: Dif. selection indicators in ROOSFIELD (A) and SMOXRELP ()
Message no. SMOX3106
Diagnosis
The information that that a field of the extract structure could be selected by or is hidden from BW is stored in both tables: SMOXRELP and ROOSFIELD. And this error occurs if these two tables have different informations.
This could be due to a manually change in one of the tables. (Normally the maintainance of these tables is done by the transaction BWA1 automatically.)
Procedure
To correct this problem, you can either repair it manually by changing the value in the table that is wrong.
Or you let BWA1 do it for you: Edit the DataSource, change the shown value to the wright one (if necessary) and save it.
******************************************************
in this how can we find out the wright value...,
expecting from ur help in this regards experts....,
Regards
Anil
HI,
Symptom
Inconsistency in the assignment of the info-object for the Territory extraction in One order datasources
If the one order Infosources are activated then the mapping of the Datasource fields TERR_GUID and PATH_GUID are assigned to the same infoobject 0CRM_TR. Therefore, activation of the infosource causes an error.
Other terms
Sales Analytics, Service Analytics, One order data Extraction, Territory extraction
Reason and Prerequisites
PATH_GUID field of the Datasource is not marked as field hidden in BW
Solution
Please note that this correction is available from the following CRM Releases
CRM 4.0 SP08
The correction is relevant for the following datasources
0CRM_LEAD_H
0CRM_LEAD_I
0CRM_OPPT_ATTR
0CRM_OPPT_H
0CRM_OPPT_I
0CRM_QUOTATION_I
<b>0CRM_QUOTA_ORDER_I</b>
0CRM_SALES_CONTR_I
0CRM_SALES_ORDER_I
0CRM_SRV_CONFIRM_H
0CRM_SRV_CONFIRM_I
0CRM_SRV_CONTRACT_H
0CRM_SRV_PROCESS_H
0CRM_SRV_PROCESS_I
In order to have this functionality available, please re-activate the datasource in the OLTP (CRM system) and replicate the datasource in the BW systems
The correction is the following:
The Datasource had the fields Territory Guid and Path Guid. The path guid should be marked as Field hidden in BW.
Or in other words in the datasource maintenance in the transaction BWA1, for the extract structure tab, the field PATH_GUID should have the value for Selection as 'A'.
If you still have any problems, do let me know.
regards,
ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ravi,
Thanks for your reply...,
You said:"Or in other words in the datasource maintenance in the transaction BWA1, for the extract structure tab, the field PATH_GUID should have the value for Selection as 'A'."
Yes i checked in BWA1->Extract Structure->Selection is 'A'.
"The Datasource had the fields Territory Guid and Path Guid. The path guid should be marked as Field hidden in BW."
for this one i didn't get wht it means. i checked in Extract structure, where PATH_GUID is not marked as Hidden field.., u mean that should i check it as hidden field here...,
actually i am getting the error in BWA1 when i am trying to check the datasource, even i tried in RSA3, there also i didn't get any data..., 0 records it showing...
let me know please ravi......,
Thanks for ur answer.
Regards
Anil
Hi,
Is there any custom fields?
If Yes, then You need to map the new custom fields in txn BWA1 so that the bdoc is extended properly.
If you go to the mapping tab in BWA1 and then use the 'check' icon..
the application should show you a list of your new fields with a yellow
light indicating that you need to map them. You must update table
SMOXRELP to get the new fields to show on the extract structure tab
in transaction BWA1.
regards,
ravi
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.