Consistency checks in APO

Can anybody please explain the reasons for doing the
1.Model consistency check
2. Re-org Consistency check(/SAPAPO/TS_LCM_REORG)
What would be the frequency for these consistency checks?

Okay I'll try and keep the answer simple:
1) The model consistency check results in an overview of the (in) completeness of the master data
objects within the model concerned. Missing data (for example, coordinates of a location are
initialised) will be displayed by error, warning or information messages. It can be checked and if
necessary be corrected from the log. Should be done when maintaining master data or after
activating the integration models (master data transfer).
2) For Time Series the memory consumption in the liveCache increases because of superfluous time series if the master data containing the time series information is deleted or removed from the planning version model. This report removes these superfluous data and tidies up livecache. Should be run daily.
For more info on consistency checks (mostly SNP and related) see the following document:
[Internal and External Consistency Checks|https://websmp203.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000330202007E]
Regards
Ian

Similar Messages

Error BM311 during Model Consistency Check in APO

Hi APO Experts
I find error BM311 - Units of different dimensions cannot be converted during Model Consistency Check in APO.
How can I get to know the code or Unit of Measure, where the inconsistency is there to rectify?
Please suggest.
Thank you.
Pradipta Sahoo

Hi Pradipta,
Can you check below notes:
943543
928502
837310
Regards,
Mukesh Pandey

APO DP Forecast profile consistency check

I am using APO DP V5.
Has anyone any experience of using the 'forecast profile consistency check' pgm /sapapo/rmdp_fcst_prpfl_consis?
What exactly does it do?
Thanks,
Bob Austin, Atos Origin

Hello,
This report /SAPAPO/RMDP_FCST_PRPFL_CONSIS is consistency for forecast profiles
While there is no need to schedule the report automatically at regular intervals, there are some special situations in which it can be very useful.
When must this report be run?
1. When you transport forecast profiles from a system A to a system B. In this case, you must convert the internal version indicator (Id).
2. If you are having problems with the date display or if the system changes from the relative date specification to the absolute specification for no obvious reason.
When should you run this report?
1. If you are working with generated forecast profiles (user parameter /SAPAPO/FCST_GUIDS).
2. If you are using a manual forecast.
What exactly does this report do?
1. The internal version ID is checked.
2. Date fields are checked. Fields filled with 00000000 are initialized.
3. Overall profiles without any single profiles are deleted.
4. Generated forecast profiles that are no longer assigned to a selection are deleted.
5. The assignment of forecast profiles to a selection is deleted if the forecast profile no longer exists.
6. Parameters for the manual forecast are deleted for any forecast profiles that no longer exist.
Source of above details : Note 558995 - Advice on consistency report for forecast profiles

Issues with Analysis Authorization checks in APO

Hi Friends,
I am facing an issue with Analysis authorization checks in APO.
We have setup user access based on Management Entity (Analysis authorization - AGMMGTENT and 0TCAACTVT) and core APO authorizations (based on the work profile - e.g: Demand Planner).
Scenario: Consider User A has access to India and Australia Management Entities with 0TCAACTVT - *
This user also has display access to all management Entities (AGMMGTENT - * and 0TCAACTVT - 03). This scenario works very well in Quality where the RSECADMIN trace shows check on both Characteristics. However in Production the RSECADMIN trace shows up only against AGMMGTENT (*) and by default takes 0TCAACTVT as (*).
In Quality the Characteristics that get checked are as below : and it works as expected. Display access for Management Entities that are supposed to be displayed only and change access to only the Management Entities that it should.
However the Trace for Production shows the following : As a result it is allowing the user to change access to all management Entities. Which is not desirable..
Resultant trace results are as below: This should not happen..
I have compared all Analysis Authorizations and it is same across both Instances. The Demand planner access is consistent too..
Will it be possible for you to advise on what could I be missing.

Hi All,
If it helps, in Quality: the Authorization checks are listed as: Subselection (Technical SUBNR) 1
while in Production it checks Subselection (Technical SUBNR) 1 in one place, however where it fails - the check happens as Subselection (Technical SUBNR) 0.
Is there a way we can change this to SUBNR 1. Is there any table entry that I can look at to check if the Authorization check is functioning incorrectly..
Please advise.. Thanks..
Regards,
Prakash

Consictency Check liveCache - APO DB

Hello,
I have a question and hopefully one of you knows the answer or has an idea, where I can find the answer.
In SAP APO we have the transaction /N/SAPAPO/OM17 to do a livecache consistency check. If there are inconsistencies, we will have the possibility to click the button "Correct All Inconsistencies" to correct them.
In my situation we are running the consistency check as a background job every night. The program name is /SAPAPO/OM_SYNC_LC_DB. Do we have the possibility to customize, that the job also correct inconsistencies as far as there are some.
Thanks in advance for help.
Greetings, Chris

Hi Chris,
I dont think there is any option of auto correction.
But you can run the job in background and than go to transaction and load the result by "button evaluate last background job "and correct inconsistecy.
Manish

LiveCache Consistency Check question, OM17

I have a general question about a LiveCache Consistency Check (transaction OM17). I know that it is a data inconsistency b/w the SAP APO database and SAP APO LiveCache. But what does that mean to a functional user? Can someone explain this in layman's terms?

In Layman terms, you can say that this checks the INCONSISTENCY between LiveCache and Database.
Here is a detailed documentation on each of the Object Types
Consistency Check for Setup Matrices
The consistency check for setup matrices contains:
· A check whether the setup matrices exist in liveCache
· A check whether the setup transitions exist in liveCache
· A field comparison between the setup transitions in the database and those in liveCache
When the setup matrices are corrected, the setup matrices in liveCache are completely generated from those in the database. Previously nonexistent setup matrices and setup transitions are newly created in liveCache. Superfluous setup transitions are deleted from liveCache. Setup transitions that differ at the field level are adjusted to match the database status.
Consistency Comparison for Block Basis Definitions
Use
When you set this indicator, checks are performed in liveCache and in the database on characteristic values for block basis definitions:
· The existence of block basis definitions is checked.
· The consistency of the characteristic values is checked.
After the checks you can call a correction function in the check results display. When correcting the error, the system deletes obsolete block basis definitions in liveCache. The system completes or corrects missing or inconsistent block basis definitions in liveCache.
Note
The check is performed independently of the planning version.
Consistency Check for Resources
The consistency check for resources contains:
· A check that the resource and corresponding time stream exist in liveCache
· An check that a resource's characteristic blocks exist in liveCache
· A field comparison between the database resource and the liveCache resource
When correcting the resources, the resources in liveCache are completely generated from the database resources. Previously nonexistent resources are created in liveCache.
Consistency check for downtimes caused by maintenance order
The consistency check for maintenance downtimes contains:
A check that the maintenance downtime has a reference to an existing maintenance order.
A check that the dates of maintenance downtime correspond to the exisiting maintenance order.
When correcting the maintenance downtime errors, downtimes without maintenance order are deleted and wrong dates of downtimes are corrected in relation to the maintenance order.
Consistency Check for Product Location Combinations
Use
If you set this indicator the system executes a consistency check for product location combinations. The consistency check for product location combinations includes:
· A check for the existence of a product location combination in the database and in liveCache
· A field comparison between product location combinations in the database and in liveCache
· The determination of obsolete entries for product location combinations in the database
· A check for the existence of characteristic value assignments for product location combinations in the database and in liveCache
· A field comparison of characteristic value assignments for product location combinations in the database and in liveCache
After the check you can call a correction function from the display of check results. For the correction, the system deletes obsolete product location combinations from the database and in liveCache. The system corrects inconsistent product location combinations and characteristic value assignments for product location combinations in liveCache.
Consistency Check for Stocks
Use
If you set this indicator the system executes a consistency check for stocks. The consistency check for stocks includes:
· A check for the existence of a stock in the database and in liveCache
· A field comparison between stocks in the database and in liveCache
· The determination of obsolete entries for stocks in the database
· A check for the existence of characteristic value assignments in the database and in liveCache
· A field comparison between characteristic value assignments for batch stocks in the database and in liveCache
After the check, you can call a correction function from the display of check results. For the correction, the system attempts to correct inconsistent stocks in the database and in liveCache. If a correction is not possible, the stocks are deleted in the database and in liveCache. The system corrects characteristic value assignments for batch stocks in liveCache.
After inconsistent stocks have been corrected, it may be necessary to start the delta report in order to reconcile SAP APO and SAP R/3.
Consistency Comparison of Configuration/CDP for Orders
Use
When you set this indicator, the system performs a consistency check with regard to configuration or CDP (characteristic value assignments/ requirements) for receipts/requirements belonging to orders:
· In the case of products with variant configuration and product variants, the system checks whether there is a referenced configuration in the database.
· In the case of products with CDP, the system checks whether CDP characteristics exist.
Note
In the area Restrictions, you can use the indicator CDP: Detailed Check to define a detailed check for CDP characteristics. If you set this indicator, the CDP data used for the orders is also compared with the product master.
· For products without configuration/CDP, the system checks whether invalid references to variant configuration or invalid CDP characteristics data exist.
After the check, you can call a correction function in the check results display. When executing the correction, the system tries to adjust inconsistent orders in liveCache.
After inconsistent orders have been corrected, you may need to start the delta report to compare the SAP R/3 system and SAP APO again.
Dependencies
The consistency check for configuration or CDP data is very time-consuming. You should therefore limit the comparison as far as possible to certain products or locations.
Consistency Check for Production Campaigns
If orders are assigned to production campaigns that do not exist in the database, this leads to inconsistent campaigns.
You can correct inconsistent production campaigns by removing all orders from them. That means that the campaign assignments are removed from the orders in liveCache.
Consistency Check for Operations
In the database table of /SAPAPO/OPR operations, there may exist operations that have no orders in liveCache, no orders for a simulation version, orders for deleted simulation versions, or no external operation number. These operations place an unnecessary load on the database table and can hinder system performance.
Consistency Check for Planning Matrices
As planning matrices are not master data, they are only located in liveCache. For each production version, there is a record in the database with information about matrices that must exist for this production version and whether the last matrix explosion was successful.
The consistency check for planning matrices checks:
· Whether the matrices associated with each record on the database exist in liveCache
· Whether the records associated with all the matrices in liveCache exist on the database
· Whether the last matrix explosion was successful.
If inconsistencies are discovered, they can be corrected. As corrections are made by recalculating the inconsistent matrices, the process can take a while and should only be done for large matrices (with many orders or many item variants) at times when it can be guaranteed not to hinder any other system processes.
Consistency Check for Simulation Versions
This is a check for whether simulation versions exist in liveCache.
Correction does not take place automatically. Simulation versions that still exist in the database but no longer exist in liveCache do not influence the running of the system. If necessary, they can be deleted using transaction /SAPAPO/CDPSS0.
Consistency Check for Product Allocations
The consistency check for product allocations checks the data for product allocation assignment from the database and compares this with the incoming orders quantity in Demand Planning. Surpluses or shortages are displayed and can be corrected.
The reconcile is only executed for product allocation groups with a direct connection to the product allocation group in the planning area if the connection is also fully defined.
There may be long runtimes during the consistency check due to the data structure. The following factors can hinder performance:
· Number of characteristics combinations
· Number of periods in a time series
· Number of sales orders that take product allocations from a time stream
Error in the reconcile
If it is not possible to reconcile the incoming orders quantity, the data records are issued again with a relevant error message. Check the following causes and attempt again.
Check:
· If the planning area to be checked is locked
· If the time streams are initialized (after liveCache has been initialized)
· If all characteristics combinations area available in the planning area
· The wildcard indicator for collective product allocation
· The settings for your planning area
Due Delivery Schedules/Confirmations Consistency Check
When a scheduling agreement release is received from a customer for sales and distribution scheduling agreement items, a due delivery schedule is created and stored in liveCache. As soon as a confirmation for a due delivery schedule containing at least one schedule line with a quantity larger than zero is generated, an object is also created for it in liveCache. The transaction data for sales and distribution scheduling agreement items contains, amongst other things, an entry with the key of the due delivery schedule object currently located in liveCache and an entry with the key of the confirmation that is currently valid in the database. During the check, the system checks whether liveCache objects exist for sales and distribution scheduling agreement items and whether the transaction data entries are correct.
The following individual checks are made for active sales and distribution scheduling agreement items:
· Is there an operative scheduling agreement release and/or forecast/planning delivery schedule in the database, but no associated liveCache object?
· Is there a confirmation in the database, but no associated liveCache object?
· Is there a due delivery schedule in liveCache, without at least one existing operative scheduling agreement release and/or forecast/planning delivery schedule?
· Is there a confirmation in liveCache, without an existing confirmation in the database?
· Is the key in the transaction data in the database that shows the current due delivery schedule in liveCache, also that of the actual liveCache object?
· Is there actually a confirmation in the database for the key in the transaction data that shows the currently valid confirmation in the database?
If a sales and distribution scheduling agreement item is inactive, there are not allowed to be any due delivery schedules or confirmations in liveCache. In this case, the following checks are made:
· Is there a due delivery schedule in liveCache for an inactive sales and distribution scheduling agreement item?
· Is there a confirmation in liveCache for an inactive sales and distribution scheduling agreement item?
Consistency Check for Production Backflushes
Partially confirmed orders cannot be deleted from liveCache. For each partially confirmed order of the database table, there must be a corresponding order in liveCache. If no order exists, there is a data inconsistency that can only be rectified by deleting the order from the database tables of the confirmation.
Entries for orders that have already been confirmed exist in the status matrix. The entry in an order's status matrix is deleted when the confirmed order is deleted by the /SAPAPO/PPC_ORD archiving report. Each status matrix entry for which database tables of the confirmation do not exist, present an inconsistency that can only be removed by deleting the status matrix entry.
Consistency Check for iPPE Objects
The iPPE object is not an iPPE master data structure. It is a data extract that is generated for each iPPE access object.
The consistency check for the object checks that it exists in liveCache and also determines its identity using the backup copy in the database. When correcting the object, the copy from the database is written to liveCache.
It is necessary to check the object if the following error message occurs: 'Error while calling COM routines via application program' (/sapapo/om 102) with return code 1601, 1602, or 1603. This does not apply to liveCache initialization.
Consistency Check for Procurement Scheduling Agreement Items
The following three objects represent procurement scheduling agreement items (scheduling agreement in short):
1. Scheduling agreement schedule lines
2. Release schedule lines
3. Confirmations
All these objects are located in liveCache. Release schedule lines and confirmations are also located in the database with a historical record. Depending on the process that was set up for the scheduling agreement, not all objects exist in liveCache or have historical records.
If goods movements exist for an object, there must always be at least one entry in liveCache. If all schedule lines are covered by goods receipts, at least one schedule line will exist in liveCache with the number '0000000000' and an open quantity of 0.
A liveCache crash, operator errors, and program errors can all cause inconsistencies. Below is a list of all the inconsistent statuses that have been identified and that can be removed:
1. The object is not in liveCache but goods receipts exist.
2. The number of input nodes and output nodes is different.
3. There are no input nodes at the order, but the material exists in the source location for the order.
4. The original quantity at the source of an order is different from that at the destination.
5. The accumulated quantities in liveCache are different from those in the database (the cumulative received quantity, for example).
6. The set process is compared with the status in liveCache.
7. A check is made to see whether the scheduling agreement is being planned in APO or in R/3 and whether the schedule lines have the appropriate specification.
If a schedule line inconsistency is identified, no more checks for inconsistencies are made, instead it moves on to the next schedule line.
Consistency Check for MSP Orders
Provides a list of maintenance and slot orders that
·     Exist in the database but have no corresponding orders in the liveCache
·     Exist in the liveCache, but have no corresponding orders in the database
Procedure
From within the list, you can either
·     Correct the inconsistencies
If you choose to do this, the system deletes the selected orders from the database and/or liveCache.
You receive a message that the selected order(s) have been deleted.
·     Leave the inconsistencies in the database and/or liveCache
Such inconsistencies place an unnecessary load on the database and/or liveCache. Moreover, those orders that exist in the liveCache, but have no corresponding orders in the database, influence the scheduling results of subsequent orders in the liveCache
Hope this helps
Regards
Kumar Ayyagari

The time characteristic consistency check has produced an error DBMAN 62

Hi
We are getting an error while updating to one target as The time characteristic consistency check has produced an error""
* Checked the respective PSA data field which is fine. Dates are in correct format.
* RSRV ran for the particular target. It had error but the jobs were successful till yesterday.
* Data from 01.05.2014 is having the problem ( Which I got from the record number in PSA )
NB: We are running on HANA database but the respective target is not yet HANA Optimised
Details Figures Attached
Any Idea.. What could have gone wrong
Regards
Reshoi R

Hi
Record Number 2995 is shown in the figures attached.
I have already carried out the deletion and automatic repair mentioned in RSCV061 even before posting this question but of no use ( I have shown that also in the figures attached at the posting time.
Reporting is fine. The problem is while loading the data to the cube. The loading is fine till date 30.04.2014 but from the date 01.05.2014. The record is error while updating.
The cube is partitioned from month 01.2008 to 12.2015.
Regards
Reshoi R

Error during currency conversion and consistency check in a sales order

Hi Experts,
I am facing the below error in the sales order. The sales order is having so many items. The below error is coming for few items only. I have checked the currency exchange rates also. All are maintained properly.
Please advice me how to fix this error or which class,methods are responsible for checking the above details while saving the order.
Thanks,
Sri

Hi Christophe,
FYI
Error during currency conversion frm &1 to &2 (date &3, ref. curr. &4)
Message Class - CRM_CUMULATED_I
Message No     - 013
Error during currency conversion for &1 and &2
Message Class - CRM_CUMULATED_I
Message No     - 008
Consistency check: Logical key does not match
Message Class - CRM_CUMULATED_I
Message No     - 011
Thanks,
Sri

Windows Server 2012 - Backup failing with Exchange - The application will not be available for recovery from this backup. the consistency check failed

Hi
We have a Windows 2012 server with Exchange 2013, all is working fine except now i am getting issues with the backup.
'Exchange - The application will not be available for recovery from this backup. the consistency check failed for the component Microsoft Exchange Server'
I have checked the database all is fine, i have created a new db and move all mailbox;s over and then removed the old db, i have enabled circular logging and then disabled it, it seems no matter what i do i cannot get a full backup!
i did have to restore the server once and the backups still worked for about 4 days after that and then stopped, i have also tried to remove and re add the backup role!
i am stumped, any advice would be great!

Hi
Ok, i created a test db and tried to back it up right away, it failed, i did not add any mailbox's to it either. i got quite a few events in the windows logs, as well as the same event above i got the following:
Log Name: Application
Source: MSExchangeRepl
Date: 21/01/2013 10:16:30
Event ID: 2038
Task Category: Exchange VSS Writer
Level: Warning
Keywords: Classic
User: N/A
Computer: NERDS-DC01.nerds.local
Description:
Microsoft Exchange VSS Writer backup failed. No log files were truncated. Instance 75754d0d-8dfe-4909-8beb-5a4f824254a9. Database 4843b37c-7b3c-42b2-8b57-1393615c2c15.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeRepl" />
<EventID Qualifiers="32772">2038</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-21T10:16:30.000000000Z" />
<EventRecordID>261645</EventRecordID>
<Channel>Application</Channel>
<Computer>NERDS-DC01.nerds.local</Computer>
<Security />
</System>
<EventData>
<Data>75754d0d-8dfe-4909-8beb-5a4f824254a9</Data>
<Data>4843b37c-7b3c-42b2-8b57-1393615c2c15</Data>
</EventData>
</Event>
AND
Log Name: Application
Source: MSExchangeRepl
Date: 21/01/2013 10:16:30
Event ID: 2038
Task Category: Exchange VSS Writer
Level: Warning
Keywords: Classic
User: N/A
Computer: NERDS-DC01.nerds.local
Description:
Microsoft Exchange VSS Writer backup failed. No log files were truncated. Instance 75754d0d-8dfe-4909-8beb-5a4f824254a9. Database db5826f3-1029-4219-ad80-441a0e94537a.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeRepl" />
<EventID Qualifiers="32772">2038</EventID>
<Level>3</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-21T10:16:30.000000000Z" />
<EventRecordID>261646</EventRecordID>
<Channel>Application</Channel>
<Computer>NERDS-DC01.nerds.local</Computer>
<Security />
</System>
<EventData>
<Data>75754d0d-8dfe-4909-8beb-5a4f824254a9</Data>
<Data>db5826f3-1029-4219-ad80-441a0e94537a</Data>
</EventData>
</Event>
and
Log Name: Application
Source: MSExchangeRepl
Date: 21/01/2013 10:16:30
Event ID: 2034
Task Category: Exchange VSS Writer
Level: Error
Keywords: Classic
User: N/A
Computer: NERDS-DC01.nerds.local
Description:
The Microsoft Exchange Replication service VSS Writer (Instance 75754d0d-8dfe-4909-8beb-5a4f824254a9) failed with error FFFFFFFC when processing the backup completion event.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeRepl" />
<EventID Qualifiers="49156">2034</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-21T10:16:30.000000000Z" />
<EventRecordID>261649</EventRecordID>
<Channel>Application</Channel>
<Computer>NERDS-DC01.nerds.local</Computer>
<Security />
</System>
<EventData>
<Data>75754d0d-8dfe-4909-8beb-5a4f824254a9</Data>
<Data>FFFFFFFC</Data>
</EventData>
</Event>
and
Log Name: Application
Source: SPP
Date: 21/01/2013 10:16:30
Event ID: 16389
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NERDS-DC01.nerds.local
Description:
Writer Microsoft Exchange Writer experienced retryable error during shadow copy creation. Retrying... More info: .
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="SPP" />
<EventID Qualifiers="0">16389</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-21T10:16:30.000000000Z" />
<EventRecordID>261650</EventRecordID>
<Channel>Application</Channel>
<Computer>NERDS-DC01.nerds.local</Computer>
<Security />
</System>
<EventData>
<Data>Microsoft Exchange Writer</Data>
<Data>
</Data>
<Data>The writer experienced a transient error. If the backup process is retried, the error may not reoccur. (0x800423F3)</Data>
<Data>
</Data>
<Binary>00000000A5120000981200000000000042BEB7C511CAC619E59C92030000000000000000</Binary>
</EventData>
</Event>

Consistency check error in sender file content conversion

Dear Experts,
I am trying one simple File to File scenario in which i have only fields 1>salesorder_number 2>Description
I created a txt file with line items "100,crudeoil" with file name as salesorder.txt
In the sender file adapter i have configured the file convertion paramenters as follows:
Document name : mt_salesorder_sender
Document namespace : http://se.com.sa/sec-sa-qax "Namespace of message type
Recordset Structure : document,*
document.endSeparator : 'nl'
document.fieldSeparator: ,
document.fieldNames : salesorder_number,Description
So after this if i run the scenario In file adapter i am getting the error like "Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'document.fieldFixedLengths' or 'document.fieldSeparator' is missing Consistency check: no. of arguments in 'document.fieldFixedLength' does not match 'document.fieldNames' (0 <> 2) "
Please let me know where i am going wrong.
Regards,
Santhosh

Hi,
please maintain the order as
Recordset Structure : document,*
document.fieldNames : salesorder_number,Description
document.fieldSeparator: ,
document.endSeparator : 'nl'
Rgds
joel

Getting error in DB02 after checking Consistency check Unknown objects in A

Dear All,
I have getting error in DB02 after checking Consistency check.
Please find the details.
I have queries.
How to correct the Unknown objects in ABAP Dictionary and Optional index is also we have to create please suggest step by step process.
Missing in R/3 DDIC      1              11
Consistency check of 07.04.2009 10:14:24
-- Objects missing in the database
Primary indexes                  0
Secondary indexes                0
Tables                           0
Views                            0
-- Unknown objects in ABAP Dictionary
|   |-- DB tables                        1
      |-- DB indexes                      11
     |-- DB views                        12
-- DB tables without unique index   1
-- Optional indexes
Too many indexes created         0
-- Indexes not created            145
Regards,

Hi
Check this may help you
http://help.sap.com/saphelp_nwmobile71/helpdata/en/45/e4ff3e65b66976e10000000a1553f6/content.htm
Regards
Uday

Consistency check error in OBIEE 10g

Hi
I have the below error while doing consistency check.
I was trying to join two fact tables by complex join, but getting below error
NQSError:15009 Could not load navigate space for subject area
NQSError: 15009 Multiple paths exist to table Plans.Circular joins schemas not supported
Please suggest

If you have to join fact tables in physical, make sure your logical layer remains a star.
Either add both fact tables to one logical fact table source , or create two logical stars, where both facts are joined to all conformed dimensions.
Note: if both facts are not at exactly same granularity, your reports will show incorrect results most definitely. So avoid fact to fact joins.

Reg: consistency check in recordset structure validation

Hi all,
I am doing FCC to FCC scenario, i am getting this error. Help me out, it is very urgent for me.
Sender Adapter v2723 for Party '', Service 'bs_text2text':
Configured at 2007-08-21 08:00:49 UTC
History:
- 2007-08-21 09:29:06 UTC: Retry interval started. Length: 2.000 s
- 2007-08-21 09:29:06 UTC: Error: Conversion of complete file content to XML format failed around position 0: Exception: ERROR consistency check in recordset structure validation (line no. 87: missing structure(s) in last recordset
- 2007-08-21 09:29:06 UTC: Processing started
- 2007-08-21 09:29:04 UTC: Error: Conversion of complete file content to XML format failed around position 0: Exception: ERROR consistency check in recordset structure validation (line no. 87: missing structure(s) in last recordset
- 2007-08-21 09:29:04 UTC: Processing started
Regards,
Ajay.

Hi Ajay,
Problem with the file content conversion parameters you specified in the sender file adapter.
Do let us know your DT structure and FCC parameters specified in adapter.
Regards,
Sumit

ERROR consistency check in recordset structure validation

Hi,
I have a file that has the format below. The file is managed with the below content conversion parameters. However, it's not working and the error message that i get is "Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 7: missing structure(s) in last recordset". Any idea, what when wrong? Thanks.
Message Type defined:
FileHeader            (occurrence = 1)
ARPostingRecord    (occurrence = 1 to unbounded)
    RecordHeader       (occurrence = 1 to unbounded)
    RecordDetail          (occurrence = 1 to unbounded)
Source file looks like this:
01 Field1 Field2...Field-n
H Field1 Field2...Field-n
L Field1 Field2...Field-n
L Field1 Field2...Field-n
H Field1 Field2...Field-n
L Field1 Field2...Field-n
L Field1 Field2...Field-n
where:
01 is the keyfieldvalue for FileHeader
H is the keyfieldvalue for RecordHeader
L is the keyfieldvalue for RecordDetail
Specified parameters:
FileHeader.fieldSeparator
FileHeader.endSeparator
FileHeader.fieldNames
FileHeader.keyFieldValue
RecordHeader.fieldSeparator
RecordHeader.endSeparator
RecordHeader.fieldNames
RecordHeader.keyFieldValue
RecordHeader.missingLastFields
RecordHeader.keepIncompleteFields
RecordDetail.fieldSeparator
RecordDetail.endSeparator
RecordDetail.fieldNames
RecordDetail.keyFieldValue
RecordDetail.missingLastFields
RecordDetail.keepIncompleteFields
ignoreRecordsetName
Recordset Name:
ARPostingRecord
Recordset Structure:
FileHeader,1,RecordHeader,1000000,RecordDetail,1000000

>ERROR consistency check in recordset structure validation (line no. 7: missing structure(s) in last recordset". Any idea, what when wrong?
When you are not sure about number of records for RecordHeader and RecordDetail, Please specify wildchar character. Dont give max numbers. The errors says expecting the specified number for recordset and since it is missing gives errror.

ERROR consistency check in recordset structure

Hello All,
Below is my input file format looks like:
HEADER
REC_1
REC_1
REC_1
REC_2
FOOTER
And I have defined the Recordset structure as HEADER,1,REC_1,*,REC_2,*,FOOTER,1.But the occurence of REC_2 is optional (0 to Unbounded).
Conversion of file content to XML failed at
position 0: java.lang.Exception: ERROR consistency check in recordset structure
validation (line no. 4: missing structure(s) before type 'HEADER'
It looks like the error is due to missing REC_2 segment in the input file.
Can you please tell me how to handle this in FCC
Thanks,

Hi Naresh
IMHO, I don't think that the error is due to missing REC_2 in the input file.
From SAP library, * includes also 0 occurence.
Converting Text Format in the Sender File/FTP Adapter to XML - Configuring the File/FTP Adapter in Integration Directory…
Under Recordset Structure, enter the sequence and the number of substructures as follows:<NameA,nA,NameB,nB,...>, where nA=1,2,3,... or * (for a variable, unlimited number, including 0).
Please provide screenshot of your FCC configuration and also sample input file that is causing the error so that it can be analysed further.
Rgds
Eng Swee

Consistency checks in APO

Similar Messages

Maybe you are looking for