cancel
Showing results for 
Search instead for 
Did you mean: 

MCTG SOURCE DATA

ernash
Discoverer
0 Kudos

Hello, can someone please tell me how to reach the source data for the key figure 'Incoming Orders' in MCTG?  We use Cognos for our formal reporting software, which is fed daily from SAP, but we are finding a significant difference between SAP's figure and Cognos figure.  We know the filters applied in Cognos and can account for some of the discrepancy, but there is still close to $1 million unaccounted for.  When I run VA05/VA05N, the figures do not match, and they don't match when I take the data directly from the VBAK table either, even accounting for the returns and credit memos.

Ideally, I would like to see the actual data that is calculating 'incoming orders' and then compare this to the line item data in Cognos to weed out the discprepancies.

Any help or direction will be greatly appreciated.  I am 2 days into this now!

Thank you,

Erica Nash

Accepted Solutions (0)

Answers (2)

Answers (2)

ernash
Discoverer
0 Kudos

Thanks for your quick reply.

I cannot say if the figures in MCTG are correct in the first place.  This is what I want to proof out with determining what exactly makes up the key figure 'incoming orders'.

For the Cognos figure, we take daily extractions of VBAK and VBAP, subtract out certain order types and material groups and come to a figure that makes sense.  But with MCTG, I cannot even say what this figure starts with.  I cannot reconcile it to VBAK. 

The path IMG - Logistics - General - Logistics Information System (LIS) - Information Structures does not exist for me.  I am on ECC 6.0 .

Thanks for your help.  I really appreciate it.

jignesh_mehta3
Active Contributor
0 Kudos

Hello,

Are Figures that you are getting in MCTG correct in the first place?

I mean that the MCTG figures may be reported wrong & that is way Cognos is generating wrong figures.

The settting for MCTG are done here: IMG - Logistics - General - Logistics Information System (LIS) - Information Structures

Thanks,

Jignesh Mehta