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

Similar Messages

Errors occur during executing consistency checks

Hi all,
During my phase"executing consistency checks", errors occur :
X_STXH| Sender structure S_STXB is not assigned to the receiver structure R_STXB.
It happened in PC001_PCL_CHECK sub-activity.
The details as follows:
ubactivity PC001_PCL_CHECK was started on 08.03.2009 at 22:10:02 by user LEEE03 | |
Check COBJ started at 08.03.2009 22:10:30 by LEEE03
Check COBJ finished at 08.03.2009 22:11:04 by LEEE03
Check HIER started at 08.03.2009 22:11:04 by LEEE03
Check HIER finished at 08.03.2009 22:11:04 by LEEE03
Check RELS started at 08.03.2009 22:11:04 by LEEE03
X_STXH
Sender structure S_STXB is not assigned to the receiver structure R_STXB
X_STXH
Sender structure S_STXB is not assigned to the receiver structure R_STXB
X_STXH
Sender structure S_STXB is not assigned to the receiver structure R_STXB
X_STXH
Sender structure S_STXL is not assigned to the receiver structure R_STXL
X_STXH
Sender structure S_STXL is not assigned to the receiver structure R_STXL
X_STXH
Sender structure S_STXL is not assigned to the receiver structure R_STXL
Check RELS finished at 08.03.2009 22:11:20 by LEEE03
Check RULE started at 08.03.2009 22:11:20 by LEEE03
Check RULE finished at 08.03.2009 22:11:29 by LEEE03
Check DICT started at 08.03.2009 22:11:29 by LEEE03
X_STXH
Field TDNAME does not exist in the sender structure on sender system
X_STXH
Field TDOBJECT does not exist in the sender structure on sender system
X_STXH
Field TDID does not exist in the sender structure on sender system
X_STXH
Field TDNAME does not exist in the sender structure on sender system
X_STXH
Field TDOBJECT does not exist in the sender structure on sender system
X_STXH
Field TDID does not exist in the sender structure on sender system
Check DICT finished at 08.03.2009 22:11:29 by LEEE03
Check FIMA started at 08.03.2009 22:11:29 by LEEE03
Check FIMA finished at 08.03.2009 22:11:31 by LEEE03
Check RUMA started at 08.03.2009 22:11:31 by LEEE03
Check RUMA finished at 08.03.2009 22:11:31 by LEEE03
Check SELS started at 08.03.2009 22:11:31 by LEEE03
Check SELS finished at 08.03.2009 22:11:33 by LEEE03
Subactivity PC001_PCL_CHECK was completed on 08.03.2009 at 23:11:40 with status ERR
I have searched in sap marketplace and also google, no results come out.
Could anybody help me out?
Thanks.
Best Regards,
Eric Lee

I've implemented the note 1101544 in the central system
executed the report Z_CNVTDMS_08_FIELD_SET with P_PHASE to 'S'.
and after this, I re-executed the activity "Execute Consistency Checks" from the extended mode of the process tree several times.
But it remains the same issue.
Did I miss anything?

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

Frequency of Model Consistency Check

Whats should be the ideal frequency of taking a model consistency check considering the fact that the check taken a long tim for execution.

Hi there.
You should run the cons_check after every major change in master data and prior to your SNP planning run. So the answer really depends on whether or not:
a) Your data model remains consistent (in which case you will only need to check after each update)
b) You do Monthly or Weekly SNP planning runs. (in which case you will need to do it weekly or monthly)
Regards
Ian

An internal error occurred during the authorization check.

Hi,
Need help,
While deleting chain in order to create Meta chain.I am getting this Error message.
Thanks

Hi,
I am creating a meta chain.When i am trying to add local chain in it.Through general services tab >> start process.A dialog box appears asking me to delete one of the chain and the other one will act as both.When i am clicking yes then i am getting this msg.
An internal error occurred during the authorization check.
Edited by: Niraj Sharma on Aug 12, 2009 11:19 AM

Model Consistency Check

We have run the model consistency check (SCM 4.1), but experienced the following problem:
If the products are flagged for deletion at client level (the highest level) the system pops-up a warning: <i>"Product X flagged for deletion, but not in location Y".</i>
As far as I know, if we flag products for deletion at client level the lower levels will be flagged automatically. Right?
Regards

That was a bug. We installed OSS note 1039639 and the problem was solved.

BI 7.0 Installed but errored out during DDIC password check !!!!!!!

Guyz,
i installed nw04s system with AS ABAPBI JAVAEP+EPC on MS SQL server ....its IDES software btw...
everything went fine till 'Import ABAP' and even 'Running ABAP Reports' proces.... but while running the process 'Check DDIC Password', it popped a window with OK and Cancel saying that
test logon to SAP system SID failed .Make sure that the system is started that the user DDIC exists and the password of user DDCI is correct
I dont udnerstand why it would fail to logon to DDIC on client 000.... becoz i set the master password and SAPInst should remember the password in some encrypted form and use the same for logging .!!!!
anyways after this error, i started SAPMMC and logged into the system and tried DDIC in 000, 001 with master password and default password (19920706) as well with no luck...but worked fine in client 800 with my master password....
What should i do now ? any suggestions would be highly appreciated....
Thanks

Actually SAPInst is trying to connect to client 001 with DDIC...so I deleted SAP* from 001 client in sqlplus and restarted the server and tried logging with ddic in 001 with my master password, PASS, pass, and even with 06071992 with no luck...
any other suggestions ?
Edited by: Kasu on Mar 27, 2008 5:18 PM

Network error (-1001) during Mac OS check update

When I try to check new update for my MAC OS 10.5.6 an network error -1001 appear. I run the network dignostic utility and the network works properly.
Concurrently if try to use SAFARI, it hang too.
thnks in advance
bgiulio66

Hey there,
Try this:
Quit Software Update,
Then trash or move the com.apple.SoftwareUpdate.plist preference file located in HD->Library->Preferences(Folder) to your Desktop, and then re-launch the Software update.
Hope it helps.
B-rock

Network error (-3001) during Mac OS check update

When I try to download new update for my MAC OS 10.5.8 an network error -3001 appear:
"A networking error has occurred: Cannot open file (-3001). Make sure you can connect to the Internet, then try again."
My internet it is up and running
what can i do?

I'd been getting the - 3001 error for an idvd upate for a few months. I finally went out to the apple website and searched for the version update manually in the downloads section. Once I downloaded and installed it went through and everything is working now.

PPM generation during consistency check

Hi,
I am getting an error during PPM consistency check. Error message says that "Phase has no activities (message no U9 111)" and "PPM has no activities (mesage no U9 116).
Please note that my resource and recipe are having the activities and scheduling formula. And I already activated the resources in another integration model without any message. In this case why system is giving message saying that no activities existed.
Please help me...
Regards,

There was a problem in the scheduling formula. After correcting that ... problem was got resolved.

Consistency check error 38011: Logical tables from multiple subject areas..

I received multiple 38011 errors when performing a consistency check after merging repositories:
For example:
Logical tables from multiple subject areas associated, OHRP and Enterprise Warehouse
(OHRP and Enterprise Warehouse refer to different business models)
I'm really not sure what this means, and Metalink and Google aren't turning up anything.
Thoughts?
-John

John,
Does it say anything about Assertion Failure? Also, this is straight up from help regarding import (through file menu) "Use this option when the objects you import are unrelated to objects already in the repository such as when the business model and physical layer objects do not exist. If an object of the same name and type exists, the import process overwrites the existing object with the new object. When you import objects from one repository into another, the repository from which you are importing must be consistent."
Sometimes Merge does bring unexpected (and unwanted results) - especially if there're presentation aliases, duplicate business models, or naming conflicts. If it's not too late, I suggest you use Import,rather than Merge, also, preferably starting with a new RPD file. This would enable you to bring items piece-by-piece and hopefully would allow you to isolate the problem.
Also, depending on the size - it's sometimes preferable to just reproduce missing part(s). I hope this is helpful.
Also, I forgot to say - the Import is deprecated and not supported. They suggest you use Project Extract and Merge. If Merge isn't working out for you and Import isn't an option - maybe you could try Project.
Edited by: wildmight on Mar 9, 2009 7:58 AM

Error occurred during budget check

Good Morning PS Gurus<
We are unable to increase the quantity of the matearil
in project & save. It’s throwing error
Error occurred during budget check, see cost protocal
Message Number :IW172
Diagnosis:
An error occurred during budget availabilty check
Procudure:
Display the cost determination log for the order or network plan for more detailed information.
We do’t have budget in our project. I checked budget TL ( it said warning message:1)
Please throw light on this issue.
Thanks
PY

Hello Team,
When i select the network-activityà extrasà logsà cost calculation.
It said WBS <<PRO1234> do't exist CJ021
Please help.
Thanks
PY

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

MAIL: The upgrade failed - error occurred during upgrade. launching Mail Import assistant to repair damaged index did not work

After installing Yosemite, the Mail required an upgrade. the upgrade was completed but resulted in a message: The upgrade failed. error occurred during the upgrade, check continue to launch Mail Import Assistant.
This resulted in an instruction: Your mail index has been damaged. To repair it quit mail. Mail will repair index next time you open mail.
Following this instruction resulted in the same failure message being repeated continuously.
How do I proceed to upgrade the Mail app.?

If doing as the alert directs (relaunching Mail) has no effect, see below.
The new version of Mail stores its database in a different format than the old one, so the database has to be converted before Mail can use it. Sometimes the conversion fails because the old database is corrupt. The easy way to recover is to discard the old database and start afresh. You can do that without losing any messages, provided that:
☞ All your incoming mail accounts are on an IMAP or Exchange server
☞ You store sent messages on the server
☞ You don't have any "On My Mac" mailboxes
Most well-known independent mail services such as iCloud and Gmail are based on IMAP. On the other hand, ISP-hosted mail services almost always use POP. If your ISP is one of your mail service providers (or the only one), you probably can't use this procedure. Ask for further instructions in that case.
If you know that the conditions above are satisfied, continue as follows.
Quit Mail if it's running. Back up all data.
Open the Library folder in your home folder by holding down the option key and selecting
Go ▹ Library
from the Finder menu bar. Inside it is a subfolder named "Mail." Move that folder to the Desktop. You're not moving the Mail application; you're moving a folder named "Mail."
Open the Internet Accounts pane in System Preferences and recreate your mail accounts other than iCloud with the same settings as before. To recreate an iCloud mail account, all you have to do is open the iCloud preference pane and check the box marked Mail.
Launch Mail. If all goes well, your mailboxes should be restored automatically. The messages will be downloaded from the servers, so it may take a long time if you have very large mailboxes. Some people have mailboxes in the gigabyte range, and that may be a problem if your bandwidth usage is metered.
If the mailboxes are created successfully, you can delete the folder you moved to the Desktop. You may have to recreate your Mail rules, signatures, and custom stationery. If it's very important to you not to have to do all that, ask for instructions before deleting the folder.

LMS3.1 psu problem - Consistency check failed for base package

Hi all,
I tried to install the following packges for CiscoView 6.1.9:
Rtr2900.cv50.v2-0.zip
Rtr3900.cv50.v2-0.zip
but it gives me the following error:
Consistency check failed for base package NGMARShare
There are no Packages to be installed.
I uninstalled all packages and installed them again after I copied these two packages in the packages sources folder but it failed again.
Any one can help?
Thanks

the new package you try to install depends on a package that you don't have
DEPENDENT PACKAGE
=================
DtShare V1.5 (DtShare.cv50.v1-5.zip)
this can be seen from the error message you got
"Consistency check failed for base package DtShare"
my advice is to read the "Release Information" for the packages you try to install
you can find the Release Information in the same page of the download.
hope this helps,
also it's better to update all the device packages if your server have internet connectivity from CS > Software Center > device update.

Error BM311 during Model Consistency Check in APO

Similar Messages

Maybe you are looking for