Execute Consistency Checks - Sub-activity - PC001_PCL_CHECK I have error

Hello!
I use TDMS version 3.0 SP 17. Process Type - ERP Initial Package for Time based & Company Code Reduction.
In phase System Analysis - Start Programs for Generation and Receiver Settings - Execute Consistency Checks - Sub-activity - PC001_PCL_CHECK I have error:
Errors detected for conversion object TVKOV :
TVKOV: member ID_VKORG of group G_VK has no selref field!
Errors detected for conversion object TWPA :
TWPA: member ID_WERKS of group G_WE has no selref field!
Errors detected for conversion object TWRF2 :
TWRF2: member ID_BUKRS of group G_BU has no selref field!
and
Errors detected for conversion object MARV :
MARV: member ID_BUKRS of group G_BU has no selref field!
What should I do?
Thank you.
Best regards,
Denis Gaykov

Hello!!
I've implemented SAP note 1536915 but don't corrected the problem. I still have errors of type:
Errors detected for conversion object MARV :
MARV: member ID_BUKRS of group G_BU has no selref field!
Errors detected for conversion object TVKOV :
TVKOV: member ID_VKORG of group G_VK has no selref field!
Errors detected for conversion object TWPA :
TWPA: member ID_WERKS of group G_WE has no selref field!
Errors detected for conversion object TWRF2 :
TWRF2: member ID_BUKRS of group G_BU has no selref field!
Thanks.

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?

SELS error during consistency checks. Fieldname not found in sender

I'm stuck in the System Analysis section, after starting programs for Generation and Reveiver settings. The task "Execute Consistency Checks" returns an error in PC001_PCL_CHECK.
Check SELS started at 16.06.2011 14:38:31
Errors detected for conversion object A910 :
A910:Fieldname VKORG of structure S_A910 mentioned in selref not found in sender
Check SELS finished at 16.06.2011 14:39:00
The help says:
The selection field mentioned for the reduction of this conversion object does not exist in the sender system. Thus this selection field can not be used for reduction. Please remove the assignment of this conversion object from reduction. For further assistance please contact SAP support.
My question is simply HOW? Where can I remove this object? I don't even find a structure called S_A910 in any of my systems. I have table A910 but it doesn't have a field called VKORG in it at all... I'm somewhat lost here.
I've added the latest SPs (17) and also applied all the notes. At least I think I applied them all... I repeated the step several times, no luck.
Any ideas?
Thanks in advance
Stefan

Hi Sandeep,
Many thanks for your reply. The note hasn't fixed the issue so I'm still stuck with the exact same error. I did run it as described and while the report updated a few fields, it didn't help to eliminate the error. Reading the note it would appear that the error described there is different from what I'm facing.
> error message like : "TVKOV: member ID_VKORG of group G_VK has no selref field!
I am getting "Fieldname of structure S_A910 mentioned in selref not found in sender" so to me it looks like a different issue.
Oh well... Nothing like a bit of fun.

Budget Consistency Check

hi there
i would like to prevent the system reducing budget by more than what is avail eg. Orig Bdg   Exp   Avail
                                2000        500    1500
In this example you should not be able to reduce/transfer more than 1500 but system allows you to transfer 2000 yet there is already expenditure. this is for 4.7 former budgeting not BCS. the standard system when consistency check is activated seems to allow the above scenario but it should not be the case that you can reduce/transfer more than what is available.
thanks

With Former Budgeting, you will need to be very carefull with your budget structure. For example, if you have FC hierarchy and CI hierarchy as below:
FC1
CI1
I
CI11
A budget structure could be like FC1/CI11 + FC1/CI1. Say, you put budget amount $2000 at the child node FC1/CI11 and additional $1000 at the parent node FC1/CI1. When the available budget at the child node is $1500 and somebody posts $1600 commitment to that node, AVC will check and find there is $100 shortage and it will automaticlly clime up to the parent node to grab that $100. That is why you don't get the error. With BCS, I think they eliminated this behavior.
So, if you still want to sick with former budgeting, you probably want to review your budget structure.

Compliance Unknown - Client Check passed/Active

I am running SCCM 2012 R2 in a test environment. My setup is very simple in that I only have around a dozen machines in it and I only have one site server.
I have a couple of software deployments for my baseline updates and when I check these all of my machines are green and compliant. However, I have another deployment that is created via an ADR and most of my machines are green and compliant except two which
are stuck on the Unknown tab saying "client check passed/Active". I have rebooted them, kicked off every action, refreshed, run summarization, reinstalled the client - yet none of these seem to be having any effect. Keep in mind these two machines
are also in my 'baseline' deployments and they are reporting back just fine. For whatever reason, they are stuck as unknown in my ADR deployment.
I've checked on a few of the logs and haven't stumbled across anything that stuck out but if anyone could kindly point me in the direction of the logs that are relevant to this issue I would appreciate it.
EDIT 1:
I ran the 'Compliance 1 - Overall Compliance' report against the ADR deployment and my test collection and the two machines in question came back as "Non-compliant" rather than compliance state unknown... which I find interesting
EDIT 2:
In my past experiences with SCCM 2012, I had very similar issues related to checking compliance. We would have a ton of machines go into the 'unknown' state and several other weird issues. We had a complex environment at my past job so I figured this evaluation
would go much smoother since I have one site system and a dozen test machines. It makes me nervous that I am already experiencing similar issues. I am also shocked I can't find more info when searching related to machines reporting back as
Unknown Passed/Active...

One of the servers in question has not received updates since February. Here is WUAHandler.log and updatesHandler.log - I don't see anything that sticks out. Most logs appear to be acting normal and don't have any glaring errors being reported. I do not
have any updates showing up in the software center on the server in question. It is the same OS and image as other servers that are working. Please let me know if you would like to see a different log....
WUAHandler.log (timestamps removed for readability)
Its a WSUS Update Source type ({E280636E-013D-473D-96D6-E9A09826B935}), adding it.
Existing WUA Managed server was already set (**EDITED OUT**), skipping Group Policy registration.
Added Update Source ({E280636E-013D-473D-96D6-E9A09826B935}) of content type: 2
Scan results will include superseded updates only when they are superseded by service packs and definition updates.
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')
Async searching of updates using WUAgent started.
Async searching completed.
Successfully completed scan.
Scan results will include superseded updates only when they are superseded by service packs and definition updates.
Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains '0FA1201D-4330-4FA8-8AE9-B877473B6441') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains
'FDFE8200-9D98-44BA-A12A-772282BF60EF') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains '7F44C2A7-BC36-470B-BE3B-C01B6DC5DD4E') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'BA0AE9CC-5F01-40B4-AC3F-50192B5D6AAF')
OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'BFE5B177-A086-47A0-B102-097E4FA1F807') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'A105A108-7C9B-4518-BBBE-73F0FE30012B') OR (DeploymentAction=*
AND Type='Software' AND CategoryIDs contains '2EE2AD83-828C-4405-9479-544D767993FC') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'E6CF1350-C01B-414D-A61F-263D14D133B4'))
Async searching of updates using WUAgent started.
Async searching completed.
Successfully completed scan.
Scan results will include superseded updates only when they are superseded by service packs and definition updates.
Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains '7F44C2A7-BC36-470B-BE3B-C01B6DC5DD4E') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains
'DBF57A08-0D5A-46FF-B30C-7715EB9498E9'))
Async searching of updates using WUAgent started.
Async searching completed.
Successfully completed scan.
Scan results will include superseded updates only when they are superseded by service packs and definition updates.
Search Criteria is ((DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'FDFE8200-9D98-44BA-A12A-772282BF60EF') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains
'7F44C2A7-BC36-470B-BE3B-C01B6DC5DD4E') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'BFE5B177-A086-47A0-B102-097E4FA1F807') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'BA0AE9CC-5F01-40B4-AC3F-50192B5D6AAF')
OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'CB263E3F-6C5A-4B71-88FA-1706F9549F51') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains '2EE2AD83-828C-4405-9479-544D767993FC') OR (DeploymentAction=*
AND Type='Software' AND CategoryIDs contains '0FA1201D-4330-4FA8-8AE9-B877473B6441') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains '3B4B8621-726E-43A6-B43B-37D07EC7019F') OR (DeploymentAction=* AND Type='Software'
AND CategoryIDs contains 'E6CF1350-C01B-414D-A61F-263D14D133B4') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains 'A105A108-7C9B-4518-BBBE-73F0FE30012B') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains
'DBF57A08-0D5A-46FF-B30C-7715EB9498E9') OR (DeploymentAction=* AND Type='Software' AND CategoryIDs contains '9B135DD5-FC75-4609-A6AE-FB5D22333EF0'))
Async searching of updates using WUAgent started.
Async searching completed.
Successfully completed scan.
UpdatesHandler.log (timestamps removed for readability)
Initiating updates scan for checking applicability.
Successfully initiated scan.
Updates scan completion received, result = 0x0.
Initiating updates scan for checking applicability.
Successfully initiated scan.
Updates scan completion received, result = 0x0.
Initiating updates scan for checking applicability.
Successfully initiated scan.
Updates scan completion received, result = 0x0.
Method (Discover) called from SDM.
Starting job with id = {A007C151-234D-4EEF-9907-4E029C0FDBBD}
Initiating Scan. Forced = (0)
Successfully initiated scan for job ({A007C151-234D-4EEF-9907-4E029C0FDBBD}).
Scan completion received for job ({A007C151-234D-4EEF-9907-4E029C0FDBBD}).
Evaluating status of the updates for the job ({A007C151-234D-4EEF-9907-4E029C0FDBBD}).
Successfully sent job ({A007C151-234D-4EEF-9907-4E029C0FDBBD}) success completion to the SdmAgent
CompleteJob received from SDM.
Complete - Job ({A007C151-234D-4EEF-9907-4E029C0FDBBD}) Cleanup.
CompleteJob - Job ({A007C151-234D-4EEF-9907-4E029C0FDBBD}) removed from job manager list.
Initiating updates scan for checking applicability.
Successfully initiated scan.
Updates scan completion received, result = 0x0.
Method (Download) called from SDM.
Starting job with id = {FB0A56F7-0247-45C0-A4E2-D7A3CFF91BBD}
Initiating Scan. Forced = (0)
Successfully initiated scan for job ({FB0A56F7-0247-45C0-A4E2-D7A3CFF91BBD}).
Scan completion received for job ({FB0A56F7-0247-45C0-A4E2-D7A3CFF91BBD}).
Evaluating status of the updates for the job ({FB0A56F7-0247-45C0-A4E2-D7A3CFF91BBD}).
Initiating download for the job ({FB0A56F7-0247-45C0-A4E2-D7A3CFF91BBD}).
Bundle update (39d68759-cc66-4fa4-8907-096b610c9583) is requesting download from child updates for action (INSTALL)
Starting download on action (INSTALL) for Update (46201763-6bf4-47f9-8d9c-b6549bb32a3b)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Contents already available.
StateCore - bundle update (39d68759-cc66-4fa4-8907-096b610c9583) state changed from (WAIT_CONTENTS) to (EXECUTE_READY) as child update state changed
Bundle update (67c66c9f-bef4-4057-860f-0dbbd2fc25dd) is requesting download from child updates for action (INSTALL)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Starting download on action (INSTALL) for Update (8efab745-b428-4bab-9933-822857c11e03)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Contents already available.
StateCore - bundle update (67c66c9f-bef4-4057-860f-0dbbd2fc25dd) state changed from (WAIT_CONTENTS) to (EXECUTE_READY) as child update state changed
Bundle update (8263f7a7-6ed2-48a9-90bd-05a361e0a81f) is requesting download from child updates for action (INSTALL)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Starting download on action (INSTALL) for Update (ebb06d79-b446-432d-b26d-0bd168e58192)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Contents already available.
StateCore - bundle update (8263f7a7-6ed2-48a9-90bd-05a361e0a81f) state changed from (WAIT_CONTENTS) to (EXECUTE_READY) as child update state changed
Bundle update (8f7e4dbd-be3f-463b-bb5a-55b33039a023) is requesting download from child updates for action (INSTALL)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Starting download on action (INSTALL) for Update (8d7948a9-3fd9-4430-b790-0511a7cb4502)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Contents already available.
StateCore - bundle update (8f7e4dbd-be3f-463b-bb5a-55b33039a023) state changed from (WAIT_CONTENTS) to (EXECUTE_READY) as child update state changed
Bundle update (9550b374-112f-42ab-80a0-8caba8652e59) is requesting download from child updates for action (INSTALL)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Starting download on action (INSTALL) for Update (8a454fff-d319-4bb0-bb00-76a67f07c88f)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Contents already available.
StateCore - bundle update (9550b374-112f-42ab-80a0-8caba8652e59) state changed from (WAIT_CONTENTS) to (EXECUTE_READY) as child update state changed
Download completed for the job ({FB0A56F7-0247-45C0-A4E2-D7A3CFF91BBD}).
Successfully sent job ({FB0A56F7-0247-45C0-A4E2-D7A3CFF91BBD}) success completion to the SdmAgent
CompleteJob received from SDM.
Complete - Job ({FB0A56F7-0247-45C0-A4E2-D7A3CFF91BBD}) Cleanup.
CompleteJob - Job ({FB0A56F7-0247-45C0-A4E2-D7A3CFF91BBD}) removed from job manager list.
Initiating updates scan for checking applicability.
Successfully initiated scan.
Initiating updates scan for checking applicability.
Successfully initiated scan.
Initiating updates scan for checking applicability.
Successfully initiated scan.
Updates scan completion received, result = 0x0.
Updates scan completion received, result = 0x0.
Method (Discover) called from SDM.
Starting job with id = {EB8A0FE5-B84E-471A-9658-3607767C7CCE}
Initiating Scan. Forced = (0)
Successfully initiated scan for job ({EB8A0FE5-B84E-471A-9658-3607767C7CCE}).
Scan completion received for job ({EB8A0FE5-B84E-471A-9658-3607767C7CCE}).
Evaluating status of the updates for the job ({EB8A0FE5-B84E-471A-9658-3607767C7CCE}).
Successfully sent job ({EB8A0FE5-B84E-471A-9658-3607767C7CCE}) success completion to the SdmAgent
Updates scan completion received, result = 0x0.
CompleteJob received from SDM.
Complete - Job ({EB8A0FE5-B84E-471A-9658-3607767C7CCE}) Cleanup.
CompleteJob - Job ({EB8A0FE5-B84E-471A-9658-3607767C7CCE}) removed from job manager list.
Initiating updates scan for checking applicability.
Successfully initiated scan.
Updates scan completion received, result = 0x0.
Method (Download) called from SDM.
Starting job with id = {CD1BC7C4-1BFF-44D1-B206-6BC650B4D54C}
Initiating Scan. Forced = (0)
Successfully initiated scan for job ({CD1BC7C4-1BFF-44D1-B206-6BC650B4D54C}).
Scan completion received for job ({CD1BC7C4-1BFF-44D1-B206-6BC650B4D54C}).
Evaluating status of the updates for the job ({CD1BC7C4-1BFF-44D1-B206-6BC650B4D54C}).
Initiating download for the job ({CD1BC7C4-1BFF-44D1-B206-6BC650B4D54C}).
Bundle update (39d68759-cc66-4fa4-8907-096b610c9583) is requesting download from child updates for action (INSTALL)
Starting download on action (INSTALL) for Update (46201763-6bf4-47f9-8d9c-b6549bb32a3b)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Contents already available.
StateCore - bundle update (39d68759-cc66-4fa4-8907-096b610c9583) state changed from (WAIT_CONTENTS) to (EXECUTE_READY) as child update state changed
Bundle update (67c66c9f-bef4-4057-860f-0dbbd2fc25dd) is requesting download from child updates for action (INSTALL)
Starting download on action (INSTALL) for Update (8efab745-b428-4bab-9933-822857c11e03)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Contents already available.
StateCore - bundle update (67c66c9f-bef4-4057-860f-0dbbd2fc25dd) state changed from (WAIT_CONTENTS) to (EXECUTE_READY) as child update state changed
Bundle update (8263f7a7-6ed2-48a9-90bd-05a361e0a81f) is requesting download from child updates for action (INSTALL)
Starting download on action (INSTALL) for Update (ebb06d79-b446-432d-b26d-0bd168e58192)
Contents already available.
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)
Ignoring update state (DOWNLOAD_READY) change in job state (2)

Consistency Checking Perform

Hi,
what are the minimum criteria to pass consistency checking for a given repository?
Regards
sandhya

hi Sandhya,
If you go thorugh the BI Admin guide CTRL+E-->Options -->help u will find the plenty of information about the best practices we need to follow
Repository metadata must pass a consistency check before you can make the repository available for queries. The Consistency Check Manager allows you to enable and disable rules for consistency checks, navigate to and fix inconsistent objects, and limit the consistency check to specific objects.
The Consistency Check Manager does not check the validity of objects outside the metadata using the connection. It only checks the consistency of the metadata and not any mapping to the physical objects outside the metadata. If the connection is not working or objects have been deleted in the database, the Consistency Check Manager will not report these errors.
The consistency checker returns the following types of messages:
Error. These messages describe errors that need to be fixed. Use the information in the message to correct the inconsistency, and then run the consistency checker again. The following is an example of an error message:
[38082] Type of Hierarchy '"0RT_C41"..."0RT_C41/MDF_BW_Q02"."Product Hierarchy for Material MARA"' in Cube Table '"0RT_C41"..."0RT_C41/MDF_BW_Q02"' needs to be set.
NOTE: If you disable an object and it is inconsistent, you will receive a message asking if you want to make it unavailable for queries.
Warning. These messages indicate conditions that may or may not be errors, depending upon the intent of the Oracle BI Administrator. For example, a warning message about a disabled join may be the result of the Oracle BI Administrator intentionally disabling a join, such as eliminating a circular join condition. The following is an example of a warning message:
[39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.
Best practices. These messages provide information about conditions but do not indicate an inconsistency. The message appears if a condition violates a best practice recommendation. The following is an example of a best practice message:
[89001] The Physical Table '"XLS_Forecast"."Forecast".."Sheet1$"' has no keys defined.
Apart from these joins,content levels,column formulas ,syntax's ....
source Admin guide
thanks,
Saichand.v

Automating global consistency check

Hi,
Could anyone please share knowledge on how to automate rpd global consistency check and creating output file containing errors and warnings of rpd.
Regards,
Varun

Hi varun,
to automate rpd global consistency checkNo,there is no automate for consistency check.Anyways why you want to automate.Its a one step process just clicking global consistency check.
By,
Kranthi.

Windows vista system, continuously trying to download a DRM file in Adobe Digital Editions application shows "Error check activation". I have authorized the Fire Wall and still the same.

windows vista system, continuously trying to download a DRM file in Adobe Digital Editions application shows "Error check activation". I have authorized the Fire Wall and still the same.

Since Re-activation as suggested by the link above is not working for you, Can you please confirm the following:
The OperatorURL is reachable. ( you can find the operatorURL from the acsm file by opening it in notepad,etc)
And Book is still available on the book-store for purchase.
(If any of first two are not available, you might have to talk to distributor for next action item to get the book. Since you will have record of purchasing the book, (in my opinion) they should provide you the new token for downloading the book)
And please confirm this that you used the same userID for downloading that you used when you first fulfilled/downloaded the book.
(If it is the case, then you have to use the correct userID)
I hope it helps.

I bought an iphone 4s from a pawn shop,i need to check and make sure the phone is clear to be activated in my name,i was told you can check the IMEI number,i have the number,but what do i do with it?

I bought an iphone 4s from a pawn shop,i need to check and make sure the phone is clear to be activated in my name,i was told you can check the IMEI number,i have the number,but what do i do with it?

Who is the carrier the iPhone is carrier locked with?
If the carrier has a blacklist for lost/stolen cell phones, it would be the carrier you need to contact.

I have just installed Digital Editions 4.3 but am having poblems downloading digital books as I get an error message stating 'Error! Check Activation'. I have Windows 7 and didn't have any problems using the previous version of Digital Editions. Can anyon

I have just installed Digital Editions 4.3 but am having poblems downloading digital books as I get an error message stating 'Error! Check Activation'. I have Windows 7 and didn't have any problems using the previous version of Digital Editions. Can anyone advise?

Hi Siobhan ,
Please refer to the following link and see if that helps.
https://helpx.adobe.com/digital-editions/kb/error-e_act_not_ready.html
I would also like to know ,does that error message has any specific number ?
Regards
Sukrit Dhingra

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

SQL SERVER 2014 - Project consistency check failed. The following inconsistencies were detected: package.dtsx. has a different ProtectionLevel than the project.

I am getting the following error when I right click on a package in solution explorer and execute using SQL Server 2014:
Project consistency check failed. The following inconsistencies were detected: package.dtsx. has a different ProtectionLevel than the project.
Luckily my solution only has 10 packages. I have verified and re-verified that everyone is set to dontsavesensitive.
I have verified and re-verified that the solution has the protection level to dontsavesensitive.
What on earth is going on here? I am using windows authentication and have no need for the package to save any sensitive information, nor should there be any.
Can someone please help me out here?
The Degenerate Dimension

Hi MMiligan,
Just as the error message said, the exactly issue is that the package package.dtsx has a different ProtectionLevel property value than the project.
So please double check the value of project ProtectionLevel property, like DontSaveSensitive, then make sure all packages in the project use the same ProtectionLevel value.
If there is still an error message indicated that some packages use a different value, please right-click the indicated package to select View Code, then make sure there is a line like below(the DontSaveSensitive
protection level corresponds to the value of 0):
DTS:ProtectionLevel="0"
The following similar thread is for your reference:
http://stackoverflow.com/questions/18705161/protection-level-changed-mid-project-now-project-wont-build
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

Error in Multiprovider consistency check after technical upgrade

Hello,
We have upgraded our BW system from 3.5 to 7.0 now.
When I check the consistency of Multiprovider it gives me warning message that CMP Problem occurs with one of the info provider.
Because I have used 0MAT_PLANT info object into my cube.
I have a Multiprovider which is combined with 4 basic cubes. Two of the cube has 0plant and 0mat_plant info object.
In other two cubes (C and D) have only 0plant and no 0MAT_PLANT is used.
When I checked the Multiprovider for consistency, it shows me warnings that CMP Error occurred in the info provider C and D, So it requires to add the 0MAT_PLANT in the basic cubes C and D and then do the identification in Multiprovider.
But this info object does not contain any data in the basic cube.
Please help me to understand the impacts on this issue.
Thanks in Advance.
Regards
M.A

Hi,
Thanks for the resposnse.
But when i go through the OSS notes it is provided that there will be performance problem in executing the report.
How to get it solved?
Thanks,
Regards
M.A

TDMS consistency check error

We are having problem at "consistency check for the rules".The
rules have been check and all are in green.i remember that SAP has
asked us to check tables CNVMBTRULEINCL and CNVMBTRULEFIPARS right? im
able to browse table CNVMBTRULEINCL but not CNVMBTRULEFIPARS. the error
message shows this table is not active, and i cant even open the table
in SE11/SE16/sm30.
the error message is as below:
x_ekpo|the rule import paramter im_bstyp will not be available for this object.
the same set of rule was used for first client(miq400), but this time its not working for second client(miq485) ..
the source and destination are the same for the first and second client.
thanks

the issue has been fixed in 0799873 2010

Spool Consistency Check

Hello,
We are facing spool consistency error messages in SM21. Later we found that there are no spool consistency jobs running in our system. Of late, I have started running RSTS0020 three times daily with an interval of one hour between each run. Whatever object I find repeating in all the three runs, I delete only those.
I am trying to automate this process. What job do I schedule to perform the same task. One more question that haunts me is, even if I schedule a report to run at midnight every day, how can I delete the inconsistent object shown in the report, automatically. And don't I need to schedule the job three times with an interval of one hour between each job schedule? I am not sure how do I go about this. I am confused. Please help.
Thank you.

Thank you for responding. If you had read my question correctly, I am also doing the same. I am running RSTS0020 in SE38 which, is the same as SP12 consistency check because, SP12 consistency check runs RSTS0020 in the background. But, my question was different. Here is my question again.
As per note 48400, you have to run RSTS0020 three times with an interval of one hour each. So, currently I am running this manually and at the end of every run, you get the output of inconsistent objects. What I do is, I take a screenshot of all the three runs then compare them. I select the check boxes and delete only those objects that has been repeated in all the three runs.
I know we can run RSTS0020 in the background but, I don't know how can I perform the later part of the above task. I mean when I execute RSTS0020 in the background, how can I delete the inconsistent objects? Any help is highly appreciated.
Thank you.

Execute Consistency Checks - Sub-activity - PC001_PCL_CHECK I have error

Similar Messages

Maybe you are looking for