Quantcast
Channel: SCN : All Content - All Communities
Viewing all articles
Browse latest Browse all 8608

Question on Extractor: 0CO_OM_CCA_9

$
0
0

Hello Experts,

 

I am having a BEX query built on  the dataflow of datasource 0CO_OM_CCA_9 and is giving Budget and actual values for cost center and cost element.

 

Two columns of the query are defined as :

 

Budget1 Column: Restricted Key figure:

 

Key figure: Amount

Value type: 20- plan

Version:0

Currency type: As entered by the user in the initial selection screen.

 

Actuals Column:

 

Key figure: Amount

Value type:10- Actuals

Version:0

Currency type: As entered by the user in the initial selection screen.

 

 

      


 

BUDGET 1


 

 

BUDGET 2


 

 

ACTUALS


 

 

 

Now the requirement is :

 

User wants to maintain a new set of values with version1 in KP06 transaction for a cost center and cost element combination

 

Cost center:XXXXXX

Cost Element:XXXXXX

Fiscal Year:2014

Version:1

Period:1(Example)

 

So, if he maintains this in KP06 he wants a new column Budget2 based on this new version 1 - as a column in BW query.

 

That means:

User want to compare the actuals with a new set of Planned values and a column is to be defined exactly as Budget1 except it should use version1 instead of 0 version.

 

My question is:

 

FICO team  maintained values in KP06 for some test records. But this records are not being captured in the extractor RSA3

 

If FICO maintains the values in KP06 transaction will it reflect in our datasource : 0CO_OM_CCA_9.

 

Does this planning activity will bring records to the extractor - If not How come the budget1 value with 0 version is coming into the extractor.

 

Also if we see 0CO_OM_CCA_9 is pulling only Actuals ( Valuetype-10).... Is it true that it pulls only value type 10??

 

Can you please throw some light on this as I am in very urgent need of a solution and explanation.

 

Where from the version information coming for the extractor........ Now I am able to see only 0 version records and not the new version records maintained by the FICO team in KP06 transaction.... What is the logic behind this.

 

 

Regards


Viewing all articles
Browse latest Browse all 8608

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>