Default Config Register for 4507 ?

what the Defult Config Register for 4507 ? this was Question and the answer was as below
When supervisor cards are shipped out from the factory, the config-register is set to 0x2101. The value of 0x2101 means "ignore the boot variable string and boot the first valid IOS image from flash".
The correct config register value should be 0x2102 but this means you need to have the correct boot variable string or else the switch will either boot the wrong IOS file or the switch will go into ROMmon.
i want to know what is the correct variable string , and how to know it , and what is the correct value ???

Duplicate posts.
Go here: http://supportforums.cisco.com/discussion/12201406/what-defualt-conf-register-core-4507-series

Similar Messages

Creating default config file for htop

Hi there. I think the title says it all.
I've been using htop for some time now, but I hate to have to reconfigure it each time I start it. Is there a way to save the current config of htop to a file or something or create a new default one ?
Thanks in advance

Um, .htoprc?
It looks like this on my system: http://paste.pocoo.org/show/208652/
htop's configuration interface changed the file, and it was loaded on next startup.
Last edited by JohannesSM64 (2010-05-01 23:08:14)

Where can I find a default rc.lua for awesome 3.4?

I have upgraded to 3.4 but my config file ain't working .. so (like I don't have any important configs) I'd like to find a default config file for this new version.
I already downloaded awesome-3.4.tar.bz2 from awesome official site but there's no rc.lua in it.
Thanks

pox@eee> pacman -Ql awesome | grep rc.lua
awesome /etc/xdg/awesome/rc.lua
If you installed awesome from pacman, you should have the default config available in /etc/xdg.

ADF_FACES-60003:Component with ID: pt1:cil2 not registered for Active Data.

When I generate a pdf Reporte using <af:fileDownloadActionListene> and Ireport this erros fires when i click active tab.
I'm Using Studio Edition Version 11.1.2.3.0:
pt1 is a <af:pageTemplate>
cil2 us <af:commandImageLink disabled="#{!bindings.CreateInsertEnc.enabled}" id="cil2"
<af:commandImageLink id="cil11"
binding="#{backingBeanScope.BakingDocument.cil11}"
icon="/Pictures/printer.png"
shortDesc="Print">
<af:fileDownloadActionListener method="#{backingBeanScope.BakingCotizar.PrintDoc}"/>
</af:commandImageLink>
Error Log:
java.lang.IllegalStateException: ADF_FACES-60003:Component with ID: pt1:cil2 not registered for Active Data.
     at oracle.adfinternal.view.faces.activedata.PageDataUpdateManager.unregisterComponent(PageDataUpdateManager.java:600)
     at oracle.adfinternal.view.faces.context.RichPhaseListener.handleStartAndStopActiveData(RichPhaseListener.java:478)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:487)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:202)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:508)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:173)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:125)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:468)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:468)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:293)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:199)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
     at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
     at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
     at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

Don't work, all iterator have ChaangeEventPolicy: default none.
And adfc-config.xml has ChaangeEventPolicy unchequed.
Another suggestion please. I need a solution so fast.

Redis' default config and systemd

Hello,
redis' default config includes settings exclusively targeted towards logrotate:
It includes a redis.logrotate for managing logs
It explicitely defines a log file (/var/log/redis.log)
It daemonizes the server, making sure that nothing is outputted on stdout
While I have no grip with logrotate, this setting makes it incompatible with systemd's own logging, journalctl: no logs are registered by it. Plus, since it's impossible to specify a custom file as a log for a given unit, it is impossible to use journalctl with redis. Seeing as the trend goes towards using systemd more and more, I'd like to ask: is it really the best thing to have a unit's log outside systemd ?
Please note that I don't want to discuss the pluses/minuses of systemd, rather the default configuration one gets when installing redis that is inconsistent with the rest of the system.

Introduction to Redis wrote:Redis is written in ANSI C and works in most POSIX systems like Linux, *BSD, OS X without external dependencies.
Linux and OSX are the two operating systems where Redis is developed and more tested, and we recommend using Linux for deploying. Redis may work in Solaris-derived systems like SmartOS, but the support is best effort. There is no official support for Windows builds, but Microsoft develops and maintains a Win32-64 experimental version of Redis.
Is this a technical problem like Redis log doesn't hold correct info if journalctl is running ?
Or is redis loginfo accurate, but you feel those logs SHOULD be accessible through journalctl ?
Give your OP content , I'll assume it's the 2nd case.
I feel that logging mechanism is an upstream decision.
OS X and *BSD don't have systemd, and on linux there are still plenty of distros that don't use systemd (like the *buntus) .
For redis this would mean that supporting journalctl would force them to support 2 different logging systems instead of 1.
They will probably be reluctant to do that.
An alternative to Redis supporting journalctl would to be for journalctl to support Redis.
Maybe systemd journalctl could gain the option to accept a log file as input ?

CIN Config Guide for MM

Hello Gurus,
Can any one provide me the Best Practice Config guide for CIN.
Thanks N Regards,
Venu M Gannu
SAP MM Consultant

Dear Venu
You can get material from forum itself for your information
Please find some details mention below:
What is CIN?
CIN Means Country India Version
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenariou2019s. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better)
Country Version India comes with four pricing procedures as follows:
u2022 JINFAC (Sales from manufacturing plants)
u2022 JINEXP (Export sales)
u2022 JINDEP (Sales from depots)
u2022 JINSTK (Stock transfers
CIN: IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings > Maintain Excise Registrations
In this IMG activity, you maintain the data relating to your excise registrations.
u2022 Enter each of your excise registrations, specifying a four-character code for each Excise Registration Ids
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
u2022 For each excise registration in your business create a registration ID, and state:
u2022 Which taxes the registration covers (additional excise duty, special excise duty, and cess) Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
u2022 The maximum number of items to be printed on each excise invoice
u2022 Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
ECC Number: Specifies the organization's ECC number.
Excise Registration Number: A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division: Specifies the excise division in whose area the excise registration is located.
Excise Collectorate: The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming, AED usage Additional Excise duty Percentage.
These are livable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty. Example - Additional Excise duty is livable in case of textile products, tobacco and sugar.
Similarly for SED CESS Number of Items in Excise Invoice Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies - This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements. This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description: Description of the excise registers set.
Partial CENVAT Credit: Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account
Dependencies - When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings.
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings.
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator - Excise year start month. The calendar month marking the beginning of the excise year. This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure :Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received. Number of excise invoices to be selected Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection Number of days from document date for excise invoice selection.
Example - If the value of this field is 20 and today is 28-03-97. The excise invoice selection will show the related invoices only for the period 08-03-97 to 28-03-97.
Document type for TDS FI posting: Financial accounting document type for TDS posting.
Document type for FI posting on Utilisation Financial accounting document type for TDS posting.
Indicator for item level excise duty round off - This indicator is to be used for deciding whether Item level excise
duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice - You can round off the Excise amount to be paid during an outgoing
Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods - Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts. The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account - Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type - Key representing a type of exchange rate in the system.
u2022 You enter the exchange rate type to store different exchange rates. Example - You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts - When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings - In this IMG activity, you maintain excise information relating to your plants.
Plant Settings - In this activity, you maintain excise information relating to your plants.
For each plant:
u2022 Specify whether it is a manufacturing site or a depot.
u2022 Assign it an excise registration ID. - You can assign the same ID to more than one plant, if required.
Depot - Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
u2022 Number of goods receipt per excise invoice.
u2022 Multiple GR for one excise invoice, Single credit
u2022 Multiple GR for one excise invoice, multiple credit
Maintain Excise Groups - In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Excise Groups - In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation - Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
1. Create one excise group for each set of registers that you need to keep.
2. Assign the excise groups to plants.
3. Maintain whether this Excise group is for a depot or not.
If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock. Excise Group Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration. - In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to. At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
u2022 GR Per Excise Invoice
u2022 Multiple GR for one excise invoice , Multiple credit
u2022 Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically - Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background. - If you want to make use of this function, you must also define the
default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option - RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step. If this is not selected then you need to separately do RG23D selection
followed by PGI and then RG23D verification and posting. If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR - If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo Posting - If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
u2022 Blocked stock
u2022 Stock transport order
u2022 Consignment stock
Maintain Series Group - In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents. Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
u2022 Define excise series groups based on type of outgoing document
u2022 Assign series group to excise registration ID
u2022 If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
u2022 If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' Iindicator. Example - You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
u2022 No account postings for CENVAT in sales cycle
u2022 No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
If the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators - In this IMG activity, you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty > Select Tax Calculation Procedure
In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
u2022 If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
u2022 If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
Maintain Excise Defaults - In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
If you use formula-based excise determination, fill out all of the fields as follows:
u2022 Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
u2022 Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
u2022 Specify the conditions in the sales order that are used for excise rates.
u2022 Specify the countervailing duty condition type used for import purchase orders.
See also : SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features : The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Customizing : Make the settings in Customizing Basic -> India -> for Logistics u2013 General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and u2026-> Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data - Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities - When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for. On the dialog box, Control Code means "chapter ID." So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination - When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data®access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.
You maintain the following types of data:
u2022 Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone. See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
u2022 Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type u2013 for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry. For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
u2022 Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
u2022 Material master data
Each material is assigned a chapter ID.
u2022 Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant. Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indicator is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Letu2019s assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under
status 7.
Define Tax Code for Purchasing Documents - In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents. Only carry out this activity if you use condition-based excise
determination.
u2022 Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
u2022 Assign Tax Code to Company Codes
In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
Only carry out this activity if you use condition-based excise determination.
Classify Condition Types - In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method. The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a
purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here. In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
u2022 For taxes on purchases, use the condition types contained in the tax procedure.
u2022 For taxes on sales, use the condition types contained in the pricing procedures.
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
Define G/L Accounts for Taxes - In this IMG activity, you specify which G/L accounts you will use to record which taxes.
Requirements - You have set up G/L accounts for each of the processing keys listed below.
u2022 Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
u2022 VS1 (basic excise duty)
u2022 VS2 (additional excise duty)
u2022 VS3 (special excise duty)
u2022 VS5 (sales tax setoff)
u2022 MWS (central sales tax)
u2022 MW3 (local sales tax)
u2022 ESA (service tax)
u2022 ESE (service tax expense)
Specify Excise Accounts per Excise Transaction - In this IMG activity, you specify which excise accounts (for excise
duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type. If you use sub transaction types, enter the accounts for each sub transaction type as well.
Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly. The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
Example:
u2022 Excise TT DC ind Account name
u2022 GRPO CR CENVAT clearing account
u2022 GRPO CR RG 23 BED account
u2022 GRPO DR CENVAT on hld account
Specify G/L Accounts per Excise Transaction - In this IMG activity, you assign the excise and CENVAT accounts to G/L
accounts. When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
u2022 Excise group
u2022 Company code
u2022 Chart of accounts
Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
Requirements
You have already:
u2022 Defined the G/L accounts
u2022 Defined the excise groups
u2022 Maintained the transaction accounts
Activities - For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for all transactions.
Note : you need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty. Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small configuration step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
u2022 Material Master à Logistics General
1. Go to IMG Define Structure of Data Screen for each Configuring the Material master Screen Sequence.
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is u201CForeign Trade: Import Datau201D. Select the same and click on Sub screens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view sub screen and ensure that the sub screen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 u2013 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade
u2013 Import, Excise related sub screen appears.
***CIN CONFUGURATION***
1.1 Maintain Excise Registration
SPRO BasicSAP Ref. IMG Maintain Logistics general  tax on Goods MovementsIndia setting Excise Registrations
APPLICABLE
1.2 Maintain Company Code Settings
SPRO Maintain Company Code SAP Ref. IMG  Logistics general tax on Goods Movements SettingsIndia Basic setting
APPLICABLE
1.3 Maintain Plant Settings
 tax on Goods MovementsIndia  Basic setting SPRO SAP Ref. IMG Maintain Plant SettingsLogistics general
APPLICABLE
1.4 Maintain Excise Groups
 Logistics general  tax on Goods MovementsIndia SPRO Basic setting Maintain Excise GroupsSAP Ref. IMG
APPLICABLE
1.5 Maintain Series Groups
SAP Ref. Logistics general  tax on Goods MovementsIndia  Basic settingSPRO Maintain Series GroupsIMG
APPLICABLE
1.6 Maintain Excise Duty Indicators
SAP Ref. Logistics general tax on Goods MovementsIndia  Basic setting SPRO Maintain Excise DutyIMG Indicators
APPLICABLE
1.7 Maintain Sub transaction Type with Text
SPRO SAP Ref. IMG  Logistics general  tax on Goods MovementsIndia  Basic settingMaintain Sub transaction Type with Text
APPLICABLE
1.8 Determination of Excise Duty
SPRO SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Determination of Excise DutySelect Tax Calculation Procedure
APPLICABLE
1.9 Maintain Excise Defaults
SPROSAP Ref. IMG Logistics general  tax on Goods MovementsIndia Determination of Excise DutyMaintain Excise Defaults
APPLICABLE
1.10 Condition-Based Excise Determination
SPRO Define Tax SAP Ref. IMG  Logistics general tax on Goods Movements PurchasingIndia  Condition-Based Excise DeterminationCode for Documents
APPLICABLE
1.11 Condition-Based Excise Determination
tax SPRO Assign Tax Code to SAP Ref. IMG  Logistics general on Goods Movements CompanyIndia Condition-Based Excise Determination Codes
APPLICABLE
1.12 Classify Condition Types
SPROSAP Ref. IMG Logistics general  tax on Goods MovementsIndia Condition-Based Excise DeterminationClassify Condition Types
APPLICABLE
1.13 Maintain Chapter IDs
SPRO Maintain SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Master dataChapter ids
APPLICABLE
1.14 Assign Users to Material Master Screen Sequence for Excise Duty
MasterSPRO  SAP Ref. IMG Assign Logistics general  tax on Goods MovementsIndia data Users to Material Master Screen Sequence for Excise Duty
APPLICABLE
1.15 Specify Excise Accounts per Excise Transaction
SPRO Specify SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Account determinationExcise Accounts per Excise Transaction
APPLICABLE
1.16 Specify G/L Accounts per Excise Transaction
SPRO Specify G/L SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Account determinationAccounts per Excise Transaction
APPLICABLE
1.17 Incoming Excise Invoices
SPROSAP Ref. IMG Incoming Logistics general  tax on Goods MovementsIndia Business TransactionsExcise Invoices
APPLICABLE
1.18 Define Processing Modes Per Transaction
SPRO Define Processing SAP Ref. IMG  Logistics general  tax on Goods Movements PerIndia  Business TransactionsModes Transaction
APPLICABLE
1.19 Define Reference Documents Per Transaction
SPRO Define Reference SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Business TransactionsDocuments Per Transaction
APPLICABLE
1.20 Maintain Rejection Codes
SPROSAP Ref. IMG Maintain Logistics general  tax on Goods MovementsIndia Business TransactionsRejection Codes
APPLICABLE
1.21 Specify Which Movement Types Involve Excise Invoices
SPRO Specify Which SAP Ref. IMG Logistics general Movement Types tax on Goods MovementsIndia Business Transactions Involve Excise Invoices
APPLICABLE
1.22 Outgoing Excise Invoices
Outgoing ExciseSPRO Assign SAP Ref. IMG  Logistics general tax on Goods Movements Billing Types to DeliveryIndia  Business TransactionsInvoices Types
APPLICABLE
1.23 Maintain Default Excise Groups and Series Groups
 Outgoing Excise Invoices SPRO  SAP Ref. IMG  Logistics general  tax on Goods Movements Maintain Default ExciseIndia Business Transactions Groups and Series Groups
APPLICABLE
1.24 Subcontracting Attributes
SPRO Subcontracting SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Business TransactionsSubcontracting Attributes
APPLICABLE
1.25 Maintain Movement Type Groups
SPRO SAP Ref. IMG Logistics general  tax on Goods MovementsIndia Business Transactions Attributes SubcontractingSubcontracting
APPLICABLE
1.26 Utilization Determination
 tax on Goods MovementsIndia SPRO BusinessSAP Transactions UtilizationRef. IMG UtilizationLogistics general Determination
APPLICABLE
1.27 Specify SAP script Forms
tax on GoodsIndia SPRO Business ExciseSAP Ref. IMG Specify SAP script Logistics general Movements Transactions FormsRegisters
APPLICABLE
1.28 Number Ranges
SAP Logistics general tax on Goods MovementsIndia  ToolsSPRO NumberRef. IMG Ranges
APPLICABLE
1.29 Message Control
SPRO SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  ToolsMessage Control
APPLICABLE
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challan
J1IFR
List subcontracting challan
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
Regds
shailesh

I have no navigation bar and firefox will not open in safe mode to reset to default config. Reinstalling doesn't work. Any help please.

I have no navigation bar ever since I closed it to gain more space on the screen. It won't re-open. Firefox will not open in safe mode, but opens immediately in normal mode with the new improper config, so I cannot reset to default config. I erased Firefox and re-installed and it still opens with the same faulty config. Why does Firefox not give me the safe mode dialog box, why can I not re-open the nav bar, and how can I do these two things, please? Firefox is currently unusable for me without a nav bar and without access to the default settings in safe mode. I cannot research the extensions I'm running since I have no nav bar to go to Tools, Add-ons, Extensions.
== This happened ==
Every time Firefox opened
== I closed the navigation bar to gain more space on the screen and I couldn't re-open it. ==
== User Agent ==
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; GTB6.4; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0)

Hit the '''Alt''' key to show the Menu bar, then open View > Toolbars and select Menu bar and Navigation bar, so they have a check-mark.

Configuration Result: This device is currently being registered for ePrint. Please try again later.

When enabling eprinting for the HP LaserJet 500 MFP M525 it would not register with the services. It has been stuck on this status for several days under web services: This device is currently being registered for ePrint. Please try again later.
I have reset the printer factory defaults, upgraded to the latest firmware, and the status remains the same. ePrint does not show the device as registered or a way to cancel the registration. I am looking for some suggestions to remove the device fom this status in order to attempt to register the device again.

Hi,
From that help page:
For LaserJet: Print a configuration page from your printer to locate the IP address. Open a Web browser and type the product IP address into the address line. The HP-embedded Web Server will open. Click the HP Web Services tab. Select the option to remove Web Services.
This doesn't work, since the printer doesn't thinks it's connected. It still says that "HP Web Services is not enabled":
And when I click the "Enable HP Web Services" button, I'm taken to this page:
That's the issue.

How do I change the default paper size for printing?

I am running Firefox 3.6.3. Recently, the default paper size for printing unexpectedly changed to a user-defined size of 3.00" x 4.57". It used to be letter size (8.5 x 11). The default paper size is 8.5 x 11 for everything else. I have tried changing the size in the preferences dialog box and then clicking "default", but after I close Firefox or if Firefox opens a new window, the default size switches back to 3.00" x 4.57". Does anyone know how to fix this?
== This happened ==
Every time Firefox opened
== About 2 weeks ago

In "mine" dutch firefox 3.6.12 there is no option to change paper-size see
"about:config" Promise to be careful (and be!) Enter "print.postscript.paper_size" gives a empty screen
"paper_size" gives a few results
What about the numbers 4259872, 4784247 and what is the meaning of
paper_size, paper_size_type , paper_size_unit

How to set the config-register on a 2960

I have tried the config-register command and it is not available. Here is part of the show ver command. I want to change the config-reg from 0xF to 0x2102.
I have run into this before but don't remember how to correct it.....I think I have to use the boot command but not sure. Here it the output
show ver
Cisco IOS Software, C2960 Software (C2960-LANBASE-M), Version 12.2(25)FX, RELEASE SOFTWARE (fc1)
ROM: Bootstrap program is C2960 boot loader
BOOTLDR: C2960 Boot Loader (C2960-HBOOT-M) Version 12.2(25r)FX, RELEASE SOFTWARE (fc4)
System returned to ROM by power-on
System image file is "flash:c2960-lanbase-mz.122-25.FX/c2960-lanbase-mz.122-25.FX.bin"
cisco WS-C2960-24TT-L (PowerPC405) processor (revision A0) with 61440K/4088K bytes of memory.
Last reset from power-on
4 Virtual Ethernet interfaces
24 FastEthernet interfaces
2 Gigabit Ethernet interfaces
The password-recovery mechanism is enabled.
64K bytes of flash-simulated non-volatile configuration memory.
Model number : WS-C2960-24TT-L
Switch Ports Model SW Version SW Image
* 1 26 WS-C2960-24TT-L 12.2(25)FX C2960-LANBASE-M
Configuration register is 0xF
Thank you

hi
Just off your switch and press the mode button
while pressing mode button start the switch again and keep your finger pressed on mode Button ( Mode button is present in front At Left Hand )
Now release the Mode button after 15 to 30 seconds
Now follow the below lines
If the password-recovery mechanism is enabled, this message appears:
The system has been interrupted prior to initializing the flash file system. The following
commands will initialize the flash file system, and finish loading the operating system
software:
flash_init
load_helper
boot
Step 1 Initialize the flash file system:
switch: flash_init
Step 2 If you had set the console port speed to anything other than 9600, it has been reset to that particular speed. Change the emulation software line speed to match that of the switch console port.
Step 3 Load any helper files:
switch: load_helper
Step 4 Display the contents of flash memory:
switch: dir flash:
The switch file system appears:
Directory of flash:
13 drwx 192 Mar 01 1993 22:30:48 c2960-lanbase-mz.122-25.FX
11 -rwx 5825 Mar 01 1993 22:31:59 config.text
18 -rwx 720 Mar 01 1993 02:21:30 vlan.dat
16128000 bytes total (10003456 bytes free)
Step 5 Rename the configuration file to config.text.old.
This file contains the password definition.
switch: rename flash:config.text flash:config.text.old
Step 6 Boot the system:
switch: boot
You are prompted to start the setup program. Enter N at the prompt:
Continue with the configuration dialog? [yes/no]: N
Step 7 At the switch prompt, enter privileged EXEC mode:
Switch> enable
Step 8 Rename the configuration file to its original name:
Switch# rename flash:config.text.old flash:config.text
now I hope you will done with it
If my post helps you then please do rate it
For full details follow this link
http://www.cisco.com/en/US/products/ps6406/products_configuration_guide_chapter09186a0080511fe2.html#wp1021182
And for password recovery section
http://www.cisco.com/en/US/products/ps6406/products_configuration_guide_chapter09186a0080511fe2.html#wp1090048
Take Care

Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator

Hello Experts,
I am configuring the scenario ( AS2 to EDISeparator and EDISeparator to IDOC ).
Can you please help me with the error below which is from the either the EDISeparator Receiver channel or the EDISeparator Sender channle.
09.06.2014 17:52:18.709
Information
Message is encrypted with 1.3.14.3.2.7 algorithm
09.06.2014 17:52:18.778
Information
AS2 Message is signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.779
Information
AS2 Message message signature is validated, signer ID is X509CertSelector: [ Serial Number: 1624063516 Issuer: CN=Mendelson AS2 TEST,OU=Integration,O=Mendelson,L=Berlin,ST=Unknown,C=GE matchAllSubjectAltNames flag: true ]
09.06.2014 17:52:18.784
Information
AS2 document size is 350 Bytes
09.06.2014 17:52:18.784
Information
Payload charset converted from ISO-8859-15 to ISO-8859-15
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule : EDI format detected as EANCOM
09.06.2014 17:52:18.785
Information
B2B EdifactConverterModule: Message will be read as ISO-8859-1.
09.06.2014 17:52:18.785
Information
MP: processing local module localejbs/EdifactConverterModule
09.06.2014 17:52:18.785
Information
0}: The module-paramteter "eancom.subversion.prefix" is not set. Using default value "false"
09.06.2014 17:52:18.786
Information
0}: The module-paramteter "eancom..audit" is not set. Using default value "false"
09.06.2014 17:52:18.791
Information
MP: processing local module localejbs/CallSapAdapter
09.06.2014 17:52:18.791
Information
Application attempting to send an XI message asynchronously using connection AS2_http://sap.com/xi/XI/AS2
09.06.2014 17:52:18.792
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.831
Information
Message successfully put into the queue
09.06.2014 17:52:18.831
Information
The application sent the message asynchronously using connection AS2_http://sap.com/xi/XI/AS2. Returning to application
09.06.2014 17:52:18.836
Information
MIC (DeJYUIusqQj6aaYRASdHhAo+4J0=) is calculated using SHA1 algorithm.
09.06.2014 17:52:18.838
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.843
Information
Message status set to DLNG
09.06.2014 17:52:18.845
Information
MDN is succcessfully signed with SHA1 (1.3.14.3.2.26) algorithm
09.06.2014 17:52:18.859
Information
Trying to put the message into the send queue
09.06.2014 17:52:18.912
Information
Message successfully put into the queue
09.06.2014 17:52:18.913
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:18.918
Information
Message status set to DLNG
09.06.2014 17:52:18.961
Information
Trying to put the message into the send queue
09.06.2014 17:52:19.001
Information
Message successfully put into the queue
09.06.2014 17:52:19.001
Information
The message was successfully retrieved from the send queue
09.06.2014 17:52:19.006
Error
MP: exception caught with message No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.006
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
09.06.2014 17:52:19.006
Information
Message status set to DLNG
09.06.2014 17:52:19.009
Error
Exception caught by adapter framework: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.010
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.Exception: No configuration / default adapter specified for EDISeparator
09.06.2014 17:52:19.015
Information
The asynchronous message was successfully scheduled to be delivered at Mon Jun 09 17:57:19 CEST 2014
09.06.2014 17:52:19.015
Information
Message status set to WAIT

Hello Ruchir Sinha and Dimitri Sannen,
I think I have progressed a bit. Just unsure of the usage of the Module configuration .I now get a new error (see below) and the updated config details are :
Sender Interface :
Receiver Interface :
Sender AS2 config :
Receiver EDISeparator config :
Sender EDISeparator config :
Receiver IDOC config :
IDoc details configured but not added in this document
16.06.2014 11:52:35.414
Information
The message was successfully retrieved from the send queue
16.06.2014 11:52:35.420
Information
Delivering to channel: B2BSE00002_O2C_ORDERS_VANS_PO_WRITE_EDISeparator
16.06.2014 11:52:35.420
Information
MP: processing local module localejbs/ModuleProcessorExitBean
16.06.2014 11:52:35.420
Information
Message entered AF MP exit bean and will now be passed to the JCA adapter
16.06.2014 11:52:35.420
Information
Message status set to DLNG
16.06.2014 11:52:35.433
Information
UNA segment UNA found
16.06.2014 11:52:35.444
Information
Parsed UNB segment 333333333/014 to 111111111/014
16.06.2014 11:52:35.445
Information
Parsed UNH segment ORDERS D96A
16.06.2014 11:52:35.514
Information
Searching sender channel for Eancom message part message with Message type ORDERS, Message version number D, Message release number 96A, Interchange sender identification 333333333, Interchange sender identification code qualifier 014, Interchange recipient identification 111111111, Interchange recipient identification code qualifier 014, Message Subversion EAN008, Message Agency UN
16.06.2014 11:52:35.579
Information
Sender channel (Channel) keys: ObjectId=7abf551ddbb638268f91af80ec1c04c8 values: ToPartySchema= Attributes=(Attributes:Channel:EDISeparator:INBOUND) values: edisep.advanced=false snd.interchangeSenderId=.* snd.tradacommessagetype=.* snd.xpath= snd.xpath.value= snd.filterCondition=equal snd.edifactMessageReleaseNumTxt= snd.tradacomMessageTypeUsingFreeText=false snd.eancomMessageReleaseUsingFreeText=false snd.eancomMessageVersionFreeText= snd.odetteMessageType=.* snd.edifactMessageVersion=.* snd.xml.splitPath=null snd.eancomMessageVersion=.* snd.odetteMessageVersion=.* snd.edifactMessageRelNumUsingFreeText=false snd.otherVersionReleaseIndustryIdentifierCodeEnabled=false adapterStatus=active snd.vdaMessageType=.* snd.eancomCONTRLMessageRelease=3 snd.odetteMessageTypeTxt= snd.tradacommessageversion=.* snd.edifactMessageVerNumUsingFreeText=false snd.edifactMessageTypeUsingFreeText=false snd.xpathUsingFreeText=false snd.interchangeSenderIdCode=.* snd.otherVersionReleaseIndustryIdentifierCode=.* snd.odetteMessageTypeUsingFreeText=false snd.tradacomreccode=.* snd.edifactMessageVersionFreeText= snd.edifactInterchangeRecipientIdentification=.* eoio.sequenceId= snd.edifactMessageTypeTxt= snd.odetteMessageVerNumUsingFreeText=false snd.eancomMessageVerNumUsingFreeText=false snd.interchangeReceiverId=.* snd.eancomMessageRelease=.* snd.tradacomsendername=.* snd.tradacomMessageTypeTxt= snd.vdaLieferantenNummer=.* snd.interchangeReceiverIdCode=.* snd.edifactInterchangeSenderIdentificationCode=.* snd.odetteMessageVersionFreeText= snd.versionReleaseIndustryIdentifierCode=.* snd.edifactInterchangeSenderIdentification=.* snd.edifactMessageType=.* snd.eancomMessageType=.* snd.xpathTxt= snd.vdaMessageTypeTxt= deliverySemantics=eo snd.eancomMessageReleaseTxt= snd.plainmessagetype=.* snd.xml.split=false snd.edifactMessageRelease=.* snd.vdaMessageTypeUsingFreeText=false snd.tradacomrecname=.* edisep.addParameterParams=TableData: edisep.addParameterParams {} snd.encoding=iso885915 snd.vdaKundenNummer=.* snd.tradacomsendercode=.* snd.edifactCONTRLMessageRelease=3 snd.edifactInterchangeRecipientIdentificationCodeQualifier=.* snd.transactionSetIdentifierCode=.* Service=ASJAVA_DX5 Channel=B2BSE00002_O2C_ORDERS_PO_ECC_READ_EDISeparator EngineType=CA Party= TransProt=XI TransProtVers=1.0.0 FromPartySchema= FromPartyAgency= Direction=I MsgProt=EANCOM MsgProtVers=1.0.0 EngineName= AdapterType=EDISeparator AdapterSWCV=06c536e6fafe11e0bb1cea8f0a4290b1 ToPartyAgency= AdapterNamespace=http://sap.com/xi/XI/EDISeparator found. New message ID is f18894a8-f53b-11e3-a748-00001e96c7e2
16.06.2014 11:52:35.586
Error
MP: exception caught with cause javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.586
Error
Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.590
Error
Exception caught by adapter framework: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule
16.06.2014 11:52:35.591
Error
Transmitting the message to endpoint <local> using connection AS2_http://sap.com/xi/XI/AS2 failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: Error during processing local class: localejbs/GenericConverterModule

J2Se receiver File adapter-HTTP 503 no listener registered for service

Hi,
We are using J2Se file adapter for one the interfaces and the logs of the J2se adapter engine has shown the following error-
Error: com.sap.aii.messaging.net.TransportException: HTTP 503 no listener registered for service /file/example_outbound
     at com.sap.aii.messaging.net.HTTPRequest.run(ServerHttpImpl.java:416)
I checked with the J2SE File/FTP receiver adapter configuration given at help.sap and found the following the following info related to the error-
Specifications for addressing by the Integration Engine
○       XI.httpPort=<port_no>
<port_no>specifies the HTTP server port that receives the messages from the Integration Engine.
○       XI.httpService=<service>
<service> describes the service part of the address where the Integration Engine must send its messages.
These specifications are mandatory.
If, for example, you have specified XI.httpPort=1234 and XI.httpService=/file/Receiver, the end point address of the file/FTP adapter in the Integration Engine must be specified as follows:
http://<fileadapterhost>:1234/file/Receiver
The end point address must be extended as follows for the Integration Engine in Release 1.0:
http://<fileadapterhost>:1234/file/Receiver?action=execute&pipelineid=Receiver
If the Integration Engine message is sent to a non-specified adapter service, the system displays the following error message:
*No registered listener for <Service> found*
The system displays the same message if the adapter is initialized, but has not been started (status STOPPED or INITIALIZED).
Where I need to check this Integration engine address specifications. I have't found any of the above code in the adapter configuration which we are using presently.The interface is running successfully before but thrown this error now.
Please reply me if some one has faced similar issue and get it resolved.

Hi
How was this issue resolved? I have the same problem.
I only have two receivers - the deafult j2se file receiver and my newly created one which used the default as a template. The ports and service's are different.
I've even tried deleting my custom receive adapter and using only the default one but i still get that error.

Default item category for components in task list

Hii all,
I need one help. We need to maintain default item category for components in task list.
Currently it comes as "L" and the field is non editable.
Is there any way wherein i can edit the item category to "N" or any other. Also need to know why this category "L" appears?
I can brint the default item category in the service order by the standard config.(PM/CS--> Maint & serv processing --> Main & Service orders --> General data --> define default values for component item categories)
But i want it in the task list.
Please help
Regards,
Vijay

Hi Vijay,
Just go to task list and then to component. go to item category field and press F1 (help)
its mention
Item Category (Bill of Material)
Categorization of the items in a BOM according to set criteria, such as whether they refer to an object (for example, material master or document info record) or whether they are kept in stock.
To my knowledge It wont be possilbe have item category N in task list by directly adding material.
Hi Pete,
Correct me if i am wrong that configuration setting for default material type and item category works for orders only.

HT5687 Its 1 year 4 months of the purchase. How can I register for the warranty for now. Please help.

Hi,
I bought MacBook Pro in Sep/2012. I did not buy the warranty at the time of purchase. Its 1 year 4 months of the purchase now.
I lately came to know, that we cant register for apple warranty if we dont purchase it earlier.
However I want to get my Mac covered under the apple warranty. How can I do so. Please guide & help.
Thanks,
Anita

This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve your problem.
If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
Below are instructions to run a UNIX shell script, a type of program. All it does is to gather information about the state of your computer. That information goes nowhere unless you choose to share it on this page. However, you should be cautious about running a program at the instance of a stranger on a public message board. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them.
Here's a summary of what you need to do: Copy a line of text from this web page into the window of another application. Wait about a minute. Then paste some other text, which will have been copied automatically, back into a reply on this page. The sequence is: copy, paste, wait, paste again. Details follow.
You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.
The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in your browser, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
clear; shopt -s extglob; Fb='%s\n\t(%s)\n'; Fm='\n%s:\n\n%s\n'; Fs='\n%s: %s\n'; Fu='User %s%%\t\tSystem %s%%'; PB="/usr/libexec/PlistBuddy -c Print"; A () { [[ a -eq 0 ]]; }; R () { o=; [[ r -eq 0 ]]; }; Pm () { [[ "$o" ]] && o=`sed 's/^ */ /' <<< "$o"` && printf "$Fm" "$1" "$o"; }; Pc () { o=`egrep -v '^[[:blank:]]*($|#)' "$2"`; Pm "$1"; }; Pp () { o=`$PB "$2" | awk -F'= ' \/$3'/{print $2}'`; Pm "$1"; }; Ps () { o="${o##+( )}"; [[ ! "$o" =~ ^0?$ ]] && printf "$Fs" "$1" "$o"; }; id | grep -qw '80(admin)'; a=$?; A && sudo true; r=$?; t=`date +%s`; clear; { A || echo $'No admin access\n'; A && ! R && echo $'No root access\n'; system_profiler SPSoftwareDataType | sed '8!d;s/^ *//'; o=`system_profiler SPDiagnosticsDataType | sed '5,6!d'`; [[ "$o" =~ Pass ]] || Pm "POST"; o=`pmset -g therm | sed 's/^.*CP/CP/'`; egrep -q 'No th|pms' <<< "$o" && o=; Pm "Thermal conditions"; o=`pmset -g sysload | grep -v :`; grep -q '= [^GO]' <<< "$o" || o=; Pm "System load advisory"; o=`nvram boot-args | awk '{$1=""; print}'`; Ps "boot-args"; d=(/ ""); D=(System User); for i in 0 1; do o=`cd ${d[$i]}L*/L*/Dia* && ls *.{crash,hang,panic} | tail | awk -F_ '{$NF=a[split($NF,a,".")]; print}'`; Pm "${D[$i]} diagnostics"; done; o=`syslog -F bsd -k Sender kernel -k Message CReq 'GPU |hfs: Ru|I/O e|n Cause: -|NVDA\(|pagin|SATA W|ssert|timed? ?o' | tail -n25 | awk '/:/{$4=""; $5=""; print}'`; Pm "Kernel messages"; o=`df -m / | awk 'NR==2 {print $4}'`; [[ o -lt 5120 ]] && Ps "Free space (MiB)"; o=$(($(vm_stat | awk '/eo/{sub("\\.",""); print $2}')/256)); o=$((o>=1024?o:0)); Ps "Pageouts (MiB)"; s=( `sar -u 1 10 | sed '$!d'` ); [[ s[4] -lt 90 ]] && o=`printf "$Fu" ${s[1]} ${s[3]}` || o=; Pm "Total CPU usage" && { s=(`ps acrx -o comm,ruid,%cpu | sed '2!d'`); o=${s[2]}%; Ps "CPU usage by process $s of user ${s[1]}"; }; s=(`top -R -l1 -n1 -o prt -stats command,uid,prt | sed '$!d'`); s[2]=${s[2]%[+-]}; o=$((s[2]>=25000?s[2]:0)); Ps "Mach ports used by process $s of user ${s[1]}"; o=`kextstat -kl | grep -v com\\.apple | cut -c53- | cut -d\< -f1`; Pm "Loaded extrinsic kernel extensions"; R && o=`sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix\.cron)|org\.(amav|apac|calendarse|cups|dove|isc|ntp|post[fg]|x)/{print $3}'`; Pm "Extrinsic system jobs"; o=`launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)|\.[0-9]+$/{print $3}'`; Pm "Extrinsic agents"; for d in {/,}L*/{La,Priv,Sta}*; do o=`ls -A "$d" | egrep -v '^(\.DS_Store$|com\.apple\.)'`; Pm "$d"; done; o=`find -L /S*/L*/E* {/,}L*/{A*d,Compon,Ex,In,Keyb,Mail,P*P,Qu,Scripti,Servi,Spo}* -type d -name Contents -prune | while read d; do ID=$($PB\ :CFBundleIdentifier "$d/Info.plist") || ID="No bundle ID"; egrep -qv "^com\.apple\.[^x]|Accusys|ArcMSR|ATTO|HDPro|HighPoint|driver\.stex|hp-fax|\.hpio|JMicron|microsoft\.MDI|print|SoftRAID" <<< $ID && printf "$Fb" "${d%/Contents}" "$ID"; done`; Pm "Extrinsic loadable bundles"; o=`find /u*/{,*/}lib -type f -exec sh -c 'file -b "$1" | grep -qw shared && ! codesign -v "$1"' {} {} \; -print`; Pm "Unsigned shared libraries"; o=`launchctl getenv DYLD_INSERT_LIBRARIES`; Pm "Inserted libraries"; o=`find {,/u*/lo*}/e*/periodic -type f -mtime -10d`; Pm "Modified periodic scripts"; o=`scutil --proxy | grep Prox`; Pm "Proxies"; o=`scutil --dns | awk '/r\[0\] /{if ($NF !~ /^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./) print $NF; exit}'`; Ps "DNS"; R && o=`sudo profiles -P | grep :`; Pm "Profiles"; for f in fstab sysctl.conf crontab launchd.conf; do Pc $f /etc/$f; done; Pc "hosts" <(grep -v 'host *$' /etc/hosts); Pc "User launchd" ~/.launchd; R && Pc "Root crontab" <(sudo crontab -l); Pc "User crontab" <(crontab -l); R && o=`sudo defaults read com.apple.loginwindow LoginHook`; Pm "Login hook"; Pp "Global login items" /L*/P*/loginw* Path; Pp "User login items" L*/P*/*loginit* Name; Pp "Safari extensions" L*/Saf*/*/E*.plist Bundle | sed 's/\..*$//;s/-[1-9]$//'; o=`find ~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $ | wc -l`; Ps "Restricted user files"; cd; o=`system_profiler SPFontsDataType | egrep "Valid: N|Duplicate: Y" | wc -l`; Ps "Font problems"; o=`find L*/{Con,Pref}* -type f ! -size 0 -name *.plist ! -exec sh -c 'plutil -s "$1" >&-' {} {} \; -print`; Pm "Bad plists"; d=(Desktop L*/Keyc*); n=(20 7); for i in 0 1; do o=`find "${d[$i]}" -type f -maxdepth 1 | wc -l`; o=$((o<=n[$i]?0:o)); Ps "${d[$i]##*/} files"; done; o=$((`date +%s`-t)); Ps "Elapsed time (s)"; } 2>/dev/null | pbcopy; exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign ($) or a percent sign (%). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.
Click anywhere in the Terminal window and paste (command-V). The text you pasted should vanish immediately. If it doesn't, press the return key.
If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important.
If you're not logged in as an administrator, you won't be prompted for your password. The test will still run. It just won't do anything that requires administrator rights.
The test may take up to a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. There is no indication of progress until it's done. Wait for the line "[Process completed]" to appear in the Terminal window. If you don't see that line within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report your results. No harm will be done.
When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
When you post the results, you might see the message, "You have included content in your post that is not permitted." That's because the forum software falsely identifies something in the post as a violation of the terms of use. If that happens, please post the results on Pastebin, then post a link here to the page you created.
Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Terms of Use of Apple Support Communities ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

[Bug?] DSC - Registering for Server Events

[LV2009, Win 7 Pro]
Howdy (Ben S another one for you? )
I am trying to register for alarm events.
This works fine by using the Register for Shared Variable Events method.
Since I have a lot of SVs and a dedicated server, I thought listen to the server would be much easier to implement.
The LabVIEW Help implies that using the Request System Event Notifications.vi will do the trick:
However, I can't seem to Register for Server Events - it doesn't work.
The code seems quite simple (below) - I just want to listen to all SVs on the localhost (default).
All the Events are coming through to the DSC (viewed in MAX), however, using the Server method I don't get any notifications through the Event Structure.
Am I doing something wrong? - Or is this a bug?
Is there somewhere I need to configure stuff?
Or does it just not send me Alarm and Notification Events of Shared Variables?
What does it send me then?
I couldn't even get the Example in NI Example Finder to work (labview\examples\lvdsc\Event Structure Support).
It shows the SV Registered Event but not the Server/System Event.
Attached is a simple project I used to demonstrate this - a SV configured for a HiHi Alarm:
The work around is to list out all Shared Variables and just read that from disk and load it into the application etc...
However, it is much more desirable to subscribe to the server and get all SV Events - is this possible?
Cheers
-JG
Certified LabVIEW Architect * LabVIEW Champion
Attachments:
DSC Server Events [LV2009].zip ‏20 KB

Ravens Fan wrote:
I think if you put in the fully qualified name for the network path and process and library on the other machine, you should be able to get the list.
You'll have to try it and find out.
Cheers for posting
From the help - I didn't think this was possible?
I gave it a go using the following naming
But I get the following error (I tried to connect to multiple SVE across our network and got the same error).
I can use though and it returns the local SV List, so I think I have the naming correct?
<edit>
My other thought is to build a hook in to the app and invoke this across the network using VI Server, so that it can run the VI on the localhost then report back the SV List).
</edit>
Certified LabVIEW Architect * LabVIEW Champion

Default Config Register for 4507 ?

Similar Messages

Maybe you are looking for