UD - Selected set code does not exist

Dear All,
We have create material in 0001 plant. It is consumable material and QA is not required. But by mistake Inspection flag was activited in material master.
Now material received is in QA Stock. We have created inspection plan and not inspection lot is in REL status.
During UD system shows following message :
"Selected set code does not exist, or data entered is incomplete"
Is there any way to take stock in unrestricted without doing any QA activity ?
Thanks and Regards,
Nirav

Hi,
Why don't you simply complete the Stock posting using 'Inspection lot stock' tab in QA32?
If you only need to take the stock out of QI and doesn't need Usage decision then why do bother about it.
Besides, this error comes when the UD selected set defined in Configuration is not maintained for the Plant.
To check this, Follow this path,
QCC0> Quality inspection> Maintain inspection type. Select the Relative inspection type and see what is maintained.
Once you maintain this Selected set for the plant 0001 using QS51, you won't get this error. Other way, define that selected set in the configuration which is already maintained for the plant.
ntn

Similar Messages

Error during unattended install of SQL 2012 (..setting 'CLTRESULTDIR' does not exist.)

Hi ALl,
I'm trying an automated install of SQL 2012 on WIndows 2012, but I keep running into this error (using a configuration.ini file generated by running through setup and grabbing it just before I clicked 'OK')
Contents of summary log:
Overall summary:
   Final result:                  Failed: see details below
   Exit code (Decimal):           -2068578304
   Exit facility code:            1204
   Exit error code:               0
   Exit message:                  The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not
exist.
   Start time:                    2015-01-09 10:19:12
   End time:                      2015-01-09 10:20:07
   Requested action:              Install
Setup completed with required actions for features.
Troubleshooting information for those features:
   Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for AS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHP:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for RS_SHPWFE:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DQC:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SDK:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CTLR:    SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for DREPLAY_CLT:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BIDS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
   Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
Machine Properties:
   Machine name:                  IDCSQLTST11
   Machine processor count:       2
   OS version:                    Future Windows Version
   OS service pack:
   OS region:                     United States
   OS language:                   English (United States)
   OS architecture:               x64
   Process architecture:          64 Bit
   OS clustered:                  No
Product features discovered:
   Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
   Description:                   Microsoft SQL Server 2012
   ProductName:                   SQL Server 2012
   Type:                          RTM
   Version:                       11
   SPLevel:                       0
   Installation location:         E:\SQL_Server_2012_StandardEdition\x64\setup\
   Installation edition:          Standard
Product Update Status:
   None discovered.
User Input Settings:
   ACTION:                        Install
   ADDCURRENTUSERASSQLADMIN:      false
   AGTSVCACCOUNT:                 NT Service\SQLSERVERAGENT
   AGTSVCPASSWORD:                <empty>
   AGTSVCSTARTUPTYPE:             Automatic
   ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Backup
   ASCOLLATION:                   Latin1_General_CI_AS
   ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Config
   ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Data
   ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Log
   ASPROVIDERMSOLAP:              1
   ASSERVERMODE:                  MULTIDIMENSIONAL
   ASSVCACCOUNT:                  NT Service\MSSQLServerOLAPService
   ASSVCPASSWORD:                 <empty>
   ASSVCSTARTUPTYPE:              Manual
   ASSYSADMINACCOUNTS:            DOMAINAA\SQLADMINS
   ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.MSSQLSERVER\OLAP\Temp
   BROWSERSVCSTARTUPTYPE:         Disabled
   CLTCTLRNAME:
   CLTRESULTDIR:                  C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
   CLTSTARTUPTYPE:                Manual
   CLTSVCACCOUNT:                 NT Service\SQL Server Distributed Replay Client
   CLTSVCPASSWORD:                <empty>
   CLTWORKINGDIR:                 C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir
   COMMFABRICENCRYPTION:          0
   COMMFABRICNETWORKLEVEL:        0
   COMMFABRICPORT:                0
   CONFIGURATIONFILE:             E:\SQL_Server_2012_StandardEdition\ConfigurationFile.ini
   CTLRSTARTUPTYPE:               Manual
   CTLRSVCACCOUNT:                NT Service\SQL Server Distributed Replay Controller
   CTLRSVCPASSWORD:               <empty>
   CTLRUSERS:                     DOMAINAA\user12345
   ENABLERANU:                    false
   ENU:                           true
   ERRORREPORTING:                false
   FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, BIDS, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS,
DREPLAY_CTLR, DREPLAY_CLT, SNAC_SDK
   FILESTREAMLEVEL:               0
   FILESTREAMSHARENAME:           <empty>
   FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher
   FTSVCPASSWORD:                 <empty>
   HELP:                          false
   INDICATEPROGRESS:              false
   INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server
   INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server
   INSTALLSQLDATADIR:             <empty>
   INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server
   INSTANCEID:                    MSSQLSERVER
   INSTANCENAME:                  MSSQLSERVER
   ISSVCACCOUNT:                  NT Service\MsDtsServer110
   ISSVCPASSWORD:                 <empty>
   ISSVCSTARTUPTYPE:              Automatic
   MATRIXCMBRICKCOMMPORT:         0
   MATRIXCMSERVERNAME:            <empty>
   MATRIXNAME:                    <empty>
   NPENABLED:                     0
   PID:                           *****
   QUIET:                         true
   QUIETSIMPLE:                   false
   ROLE:
   RSINSTALLMODE:                 DefaultNativeMode
   RSSHPINSTALLMODE:              SharePointFilesOnlyMode
   RSSVCACCOUNT:                  NT Service\ReportServer
   RSSVCPASSWORD:                 <empty>
   RSSVCSTARTUPTYPE:              Manual
   SAPWD:                         <empty>
   SECURITYMODE:                  SQL
   SQLBACKUPDIR:                  <empty>
   SQLCOLLATION:                  Latin1_General_CI_AS
   SQLSVCACCOUNT:                 NT Service\MSSQLSERVER
   SQLSVCPASSWORD:                <empty>
   SQLSVCSTARTUPTYPE:             Automatic
   SQLSYSADMINACCOUNTS:           DOMAINAA\SQLADMINS
   SQLTEMPDBDIR:                  F:\TempDB
   SQLTEMPDBLOGDIR:               <empty>
   SQLUSERDBDIR:                  E:\SQLData
   SQLUSERDBLOGDIR:               D:\SQLLog
   SQMREPORTING:                  false
   TCPENABLED:                    1
   UIMODE:                        Normal
   UpdateEnabled:                 true
   UpdateSource:                  MU
   X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\ConfigurationFile.ini
Detailed results:
   Feature:                       Database Engine Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Replication
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Full-Text and Semantic Extractions for Search
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Analysis Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - Native
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - SharePoint
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services Add-in for SharePoint Products
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Integration Services
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Complete
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Backwards Compatibility
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Distributed Replay Controller
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Distributed Replay Client
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Data Tools
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Basic
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity SDK
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Writer
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Documentation Components
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Browser
   Status:                        Failed: see logs for details
   Reason for failure:            Setup was canceled for the feature.
   Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150109_101753\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.InputSettingValidationException
     Message:
         The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
     HResult : 0x84b40000
         FacilityCode : 1204 (4b4)
         ErrorCode : 0 (0000)
     Data:
       SQL.Setup.FailureCategory = InputSettingValidationFailure
       DisableWatson = true
     Stack:
         at Microsoft.SqlServer.Chainer.Infrastructure.InputSettingService.LogAllValidationErrorsAndThrowFirstOne(ValidationState vs)
         at Microsoft.SqlServer.Configuration.SetupExtension.ValidateFeatureSettingsAction.ExecuteAction(String actionId)
         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun, ServiceContainer context)
     Inner exception type: Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException
         Message:
                 The specified directory 'C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir' for setting 'CLTRESULTDIR' does not exist.
         HResult : 0x87d00006
                 FacilityCode : 2000 (7d0)
                 ErrorCode : 6 (0006)
         Data:
           DirectoryPath = C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir
           SettingName = CLTRESULTDIR
           WatsonData =
Microsoft.SqlServer.Configuration.DistributedReplayExtension.DirectoryNotExistException@6

Hello,
Open the configuration file with notepad, then go to the “features” variable. On the following article you will find what
means each parameter:
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.110).aspx#Feature
You will also find the list of features supported by each edition on the following article:
http://msdn.microsoft.com/en-us/library/Cc645993(v=sql.110).aspx
For example, it seems you have DQ and DQC on that configuration file, please remove them with their corresponding commas.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
Thanks Albert that worked when I just selected the main features and excluded ones like DQ and DRC. Thing is why would the standard media allow you to install enterprise features, create a configuration file with these enterprise features and then fail?? Why
would Microsoft tease you like that? Frustrating since I spent hours on this ..

Tax Code does not exist in the system (T007A)

Hi All
When we try to create a receipt for a particular expense type in ESS Travel & Expenses, we get the follwing error "Tax code Z0 does not exist in the system (T007A)". Upon creating a tax code Z0 it gives the following error "Tax code does not exist in the system (T007A)". When we change the Receipt currency to USD instead of Bristish Pound it gets accepted without the error. It works perfectly fine when expense report created using GUI. The error occurs only when we create the expense report using Portal ESS T&E. I was not able to find anything related to this in the SDN. If any of you could help me out, that would be great.
Thanks, Raj

Hello Mr. Raj!
I checked the related issues that other customers reported.
I came up with a list of things you can try that may help you solve your issue.
a) Check if the field V_706D_B-LAND1 is filled with the home country in the IMG step 'Define Global Settings'. So may I ask you to check. Moreover, if this is not the reason, may I also ask you, if you get the same error when using our backend test transaction PR_WEB_1200? Thank you,
b) Could you please check that you don't have any expense type with value " "(blank) in the tax code field in V_T706B1?
c) Apply Note 1129853 - Web: Input tax code for credit card receipts
d) Please follow in IMG:
Financial Accounting
Travel Management
Travel Expenses
   Master Data
    Control Parameters for Travel Expenses
     Define Global Settings
Input Tax
Country                                       { Your country here }
Enter an input tax code for 0% input tax [    ] <<<
If here it's blank, this must be filled with a tax code. I found this out when I set the field "Input Tax per Travel Expense" then I get a warning "Enter an input tax code for 0% input tax".
The reason for this is that in your system, you don't have a "blank" tax code and it looks for this entry. Please kindly define a tax code in this setting.
I hope I was able to help you with this information.
Wilian Segatto
SAP Support - HCM/XSS

"The selected communication device does not exist"

Whenever I log on (or come out of sleeping), I get a prompt box from Internet Connnect that says "The selected communication device does not exist. Please verify your setting and try again". I think this started to happen when I stopped using a USB modem to access the internet. Recently I was again using a (different) USB modem, and when I stopped (I now have a wireless router), I now get TWO of the above alerts!
To be clear - I have no problem accessing and using the internet with the wirelss router I am using.
Is there a way of deleting historical communication devices I no longer use from Internet Connect that might stop this from happening?
Thanks in advance.
G4 iBook Mac OS X (10.4.8)

Hello Dunstan,
I wonder if this might have something to do with Location and Network settings.
I'd go to System Preferences/Network and, choosing the location that you are using, select the "modem" tab. On the presumption that, because you are now using wireless router and that your computer is no longer using its built-in modem, I'd delete all settings under "modem".
Then I'd open Internet Connect and see what crops up when you click on the Modem tab. It should be blank. If it is not, I'd close Intertet Connect, then go to My User Folder/Library/Preferences, and there move the following file to the Desktop: com.apple.internetconnect.plist. Open Internet Connect again.
There are other things that can be done, especially in the Locations settings. However, I'd try the above first.
Best of luck,
Martin
If you found that this contribution helped to answer your question, please consider the "Helpful" and "Solved" buttons in this message. Why reward points?
Powerbook 15-inch G4 1GHz Mac OS X (10.4.8) Several veterans that go on and on. 40gig, 3rd generation iPod

Condition type & tax code & does not exist

Hi,
I have a problem to find out the reason why i can not process documents which came via IDocs from Sales SAP system. The error is "Condition type & tax code & does not exist". Following places i have already checked :
1. FTXP - tax code for which error exists the same in both systems
2. Table A053 - Condition types for specific tax codes and country are created in both systems.
The tax determination is under billing and in Sales system it is ok, document is posted and when comes to our FInance system via Idoc it is in error even we have the same entries in the table A053.
Maybe someone knows what can be also checked ?
Thanks
Tomek

Hi Tomasz,
Please go to T.code WE02 and check the reason for the error.
The failed IDocs will be in status "51" and will also give you the reason for errors.
Regards,
Shiv

The material code does not exist or is not activated

Dear All,
I am using SAP ECC6. When I go through MM03 for certain material code, it gives the error: The material code does not exist or is not activated.
But this code exists in MARA. There seems to be no problem in the fields of MARA.
Where the problem can be?
Regds
Amit

do you know when and how the material was created?
Maybe the material is stored with a key that does not anymore fit to the customizing.
In SE16 in menu Settings > user parameter check if you have a flag in field conversion exit., if yes, then remove it and display this material along with other materials that you can access with MM03 in one list.
Check if the material number is different from the others (e.g. with or without leading zeros)

IDoc error - Condition type & tax code & does not exist

Hi,
I have the problem with CANADA tax codes. I have a few documents sent from external SAP to different SAP. In the source system documents were posted. In the target system i have error "Condition type & tax code & does not exist". I have compared the tables A003 and A053 in both systems and the settings are the same for specific Condition type and tax code... So where to find the reason Idocs are in error ? The only thing which is different is validity from (in the source system is earlier than in the target but the docs are created after both validation start)...
I would appreciate advice.
Tomek

Hi Tomasz,
Please go to T.code WE02 and check the reason for the error.
The failed IDocs will be in status "51" and will also give you the reason for errors.
Regards,
Shiv

Msg FF 718 Tax code & does not exist for jurisdiction code

Hi,
I am trying post a goods issue for a Return Delivery PO.
After entry the data, I made the consistency check and then the system show me the related message: Msg FF 718 Tax code & does not exist for jurisdiction code.
I checked the configuration about Tax on Sales/Purchases, but I did not see nothing wrong.
Anybody knows how about this message?
Thanks in advance.

Hi Demetrio,
Please refer the below mentioned OSS notes:
Note 675382 - ME31K No check on tax jurisdiction code in contract
Note 765309 - Check combination MWSKZ/TXJCD incorrect
Hope this helps,
Please assign points as way to say thanks

Tax code does not exist for jurisdiction code sap

Dear All,
I have gone through all these links and many more
Tax code does not exist for jurisdiction code
Tax code not maintained for Juridiction code
Tax code O1 does not exist for jurisdiction code CNT5K2L60
Tax code EA does not exist for jurisdiction code QC000000
This has ben discussed many times. I have searched the forums as well. But still I am not able to solve this.
If i use the tax code V0 the system is accepting. But if i create any other tax code in tax jurisdiction IN00 and TAXINJ
it gives the error.I tried OBCL also as told by experts.But still I am not able to solve. Kindly help.
Requesting the moderators not to lock the thread just because it has been discussed. I will close the thread once i solve the issue. My last thread was locked even though it was not asnwered.

scm.sd wrote:
Dear All,
>
> I have gone through all these links and many more
> Tax code does not exist for jurisdiction code
> Tax code not maintained for Juridiction code
> Tax code O1 does not exist for jurisdiction code CNT5K2L60
> Tax code EA does not exist for jurisdiction code QC000000
>
> This has ben discussed many times. I have searched the forums as well. But still I am not able to solve this.
> If i use the tax code V0 the system is accepting. But if i create any other tax code in tax jurisdiction IN00 and TAXINJ
> it gives the error.I tried OBCL also as told by experts.But still I am not able to solve. Kindly help.
>
> Requesting the moderators not to lock the thread just because it has been discussed. I will close the thread once i solve the issue. My last thread was locked even though it was not asnwered.
HI,
can you tell me which tax code and condtion type you are using.
why you are using tax jurisdiction in your tax procedure
thanking you.
Edited by: R.Rasumalla on Oct 13, 2011 3:56 PM

DNS: The selected log file does not exist

Hi to all,
I am using Lion Server on a Mac Mini and everything seems to work fine. However, when I want to check my DNS log file (Server Admin > DNS > Log) I get a message that "The selected log file does not exist"! Stopping and starting the DNS service doesn't help. Anyone any idee how to view the log file within the Server Admin app?
Thanks in advance!
Ewald.

hi John!
if you have time, patience, and squared balls (just for laugh! ):
Use "strace" to trace all system calls a binary make... System calls like "open" file and "close" file =)
That's say, we are going to "trace the files opened by specific application".
"Strace" in MacOSX comes with Developer Tools, so you'll need to install these to continue.
First you have to know which are the Applications in the game, because "Server Admin" is a client-server application, there will be a client application in the client machine, and a server application running in the server.
You have to trace the server application running in the server. It will be the one which opens the log file, and sends the data to the client application.
I've made some previous investigation about the Server Admin Log parser (see https://discussions.apple.com/thread/3352647?start=0&tstart=0).
Also will be helpfull to read a little bit about strace ( http://linux.die.net/man/1/strace )
Here i do my bet, maybe that command line is what you look for:
#sudo strace launchctl load -w /System/Library/LaunchDaemons/com.apple.ServerPerfLog.plist | grep "open"
sudo: do as super user
strace: trace the binary
launchctl: system service
load -w file: load, as defined in this file
| grep open: and substract just the "open file" traces
Let me know if that gives you more clues!
regards, T

Tax code does not exists in TAXINN

While doing FB60 and FB70 message shows Tax code does not exists in TAXINN. Since Tax code A0 and V0 are already assigned to company code and also maintained condition type, tax procedure, and condition record.
Regards,

First check the tax procedure assigned to country IN using T code OY01 - most likely it is TAXINN in your case. Then make sure that you have defined those tax codes in FTXP in country IN. The assignment of A0 and V0 you have done to the company code is just for default tax code in case system doesn't find any tax code for posting.

PS Elements 11 says Redemption Code does not exist

Just bought and have activated receipt. Install says Redemption Code does not exist.

See if this FAQ helps you:
http://helpx.adobe.com/x-productkb/policy-pricing/serial-number-retrieval-process-faq.html

Just purchased adope premiere elements 11 and redemption code does not exist

just purchased premiere elements 11 and when trying to get serial number, i am told the redemption code does not exist, its brand new right out of the package. WHY.

Did you try entering the redemption code at http://www.adobe.com/go/getserial/? You can find additional details at Serial number retrieval process FAQ | Point-of-sale activation products - http://helpx.adobe.com/x-productkb/policy-pricing/serial-number-retrieval-process-faq.html.

Cross system company code does not exist.

Hello,
I am trying to upload Cost center through IDOC menthod.
Message type of IDOC is : COSMAS
Basic Type : COSMAS01
But i am getting a error as Cross system company code does not exist in ( Create IDOC Overview).
Kinly help me in resolving this issue.
Regards,
Hemanth.
Edited by: hemanth kumar on Feb 20, 2009 3:08 PM

Hi Shweta
Have you checked with the data i.e. company code .
May the company code which you are passing is not there in ur receiver system.
Just check it out.
Regards
-Mitesh

Company code does not exist error while sending idoc

Hi Expert
I am trying to send idoc from one client(800) to another client(810).I have faced error Company code does not exist, searched scn ,Got solution if company code does not exist in reciever system(810 client) ,it will show this error .Then i have tried to give specific company code which is exist in 810 client also .But same issue is coming . So what exactly the issue can any one say .
More Info:FI(Finance) header items and line items are sending .
Thanks & Regards

Hi,
Your company code not activated for material management. Few pre-requisites to create material and one is to activate company code for material management
Please activate in T.code: OMSY,
[For example: For Fiscal year variant K4]
In OMSY steps, u have to enteru2026u2026u2026..
Company Code (enter your company code name 2001)u2026u2026u2026u2026u2026.
Company Name..
Fiscal Year of Current Period 2009
Current period (posting period) 03( )
Fiscal year of previous period 2008( will come automatic)
Month of previous period 02( will come automatic)
Fiscal year of last period of previous year 2008
Last month of previous year 12
Allow Posting to Previous Period (Back posting)
Disallow back posting after a change of period
Now create material with T.code; MM01
Regards,
Biju K

UD - Selected set code does not exist

Similar Messages

Maybe you are looking for