AdobeLibrary1.jsx etc License and Distribution

[Preamble - I may be totally wrong about the following - I do hope so, please put me right if so]
It would make life a lot easier if we could include the Adobe Library scripts along with scripts we release ourselves - when they are required. At the moment the Library scripts' licenses do allow us to include them ('we may distribute them'), but then the user is not allowed to use them without written permission from Adobe. That really isn't workable. Furthermore, the only place I have found that provides the files for download is as part of the ImportCamera package. Again, that is not a particularly workable or helpful route for other scripters to direct users to. If they have to be downloaded separately, please could Adobe include them as an individual item from Studio Exchange. Is there really a strong reason for not just making these Libraries copyright Adobe but open to anyone to distribute *and use*?
My experience in releasing scripts is that if the process is not totally simple (one set of files to be put in one location) then it doesn't happen and you end up with frustrated and pissed off users. Because of that I think I am going to have to fall back on not using the libraries (and reinventing the wheel - usually not so well as a consequence) until a more workable way of getting them to the user is made possible.
While it appears the libraries come as part of the package for CS2, this does not seem to be the case with PS CS2, also I believe the Library3 was not written when the initial release of CS2 was made, so again there may be gaps.
Andrew

Bob, I appreciate that is "your" intent to let us distribute and use these library files as we wish, but for people contemplating some money making enterprises that include Bridge scripts, your posting here isn't enough for me. So, like Andrew, I've taken to NOT using them because of that legal ambiguity.
Is there some more formal way to fix this? Like re-release the files under one of the common licenses and let us redistribute files that contain a usable license. I think in this case you want a very open license since you're more interested in encouraging people to build off what you have and make useful stuff rather than trying to guarentee open-ness of derivative works. The LGPL, referenced above, would do as would several of the other "open licenses" that are less restrictive than the GPL.
I know this involves the legal dept at Adobe and is probably a pain to get done, but you're really going to limit the use of those libraries for anyone intending redistribution until it's fixed.
In case it's relevant, the Image Processor script has no licensing clause in it at all, but the stock photo scripts have the same one that AdobeLibrary*.jsx have.
--John

Similar Messages

  • I have a CC Photography License and tried loading the new Lightroom cc but it will not open (only flashes the welcome screen for a split second) then goes blank.  I tried uninstalling it, rebooting, etc. several times and it will not work on my Mac with Y

    I have a CC Photography License and tried loading the new Lightroom cc but it will not open (only flashes the welcome screen for a split second) then goes blank.  I tried uninstalling it, rebooting, etc. several times and it will not work on my Mac with Yosemite.  Please help!

    Check out this thread: Downloaded Lightroom CC but only get a quick flash of the startup screen then nothing, Lightroom 5 still working.

  • Cin in sales and distribution

    hi,
    can any one tell me the role of CIN in sales and distribution, if possible
    post some material regarding CIN configuration.
    my e-mail id: [email protected]
       thank you.

    Hello Sriram,
    CIN in other words "Country Version India" is basically used for taxation purposes. Every country has its own tax system..........so SAP has come up with its own country versions for taxation like CIN for India.
    <b>The following is the detailed notes on CIN:</b>
    Basically Cin is divided in to two types:
    1. TAXINJ - Is a Routine Based that is used in the condition types. it will work on the logic what ever is there in the Routine.
    2. TAXINN: - Is a condition Record based. Means we have to create condition records for each and every condition type that you are going to use in the Pricing Procedure.
    Since Version 4.7 this TAXINN came into picture and start using this.
    And one of the important point is since 4.6 c CIN comes a separate package. But after introduction of 4.7 Version, CIN is coming the SAP Package itself and even in the Customer Master Record also we will find the CIN Icon.
    Basically 4 types of Pricing Procedures are used in CIN and are as follows:
    1.JDEPOT - Depot Sales
    2.JEXPOR - Export Sales
    3.JFACT - Factory Sales
    4.JSTKTR - Stock Transfer
    Country Version India comes with four pricing procedures as follows:
    • JINFAC (Sales from manufacturing plants)
    • JINEXP (Export sales)
    • JINDEP (Sales from depots)
    • JINSTK (Stock transfers
    CIN:
    IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
    Maintain Excise Registrations
    Use
    In this IMG activity, you maintain the data relating to your excise registrations.
    Activities
    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.
    Activities
    For each excise registration in your business create a registration ID, and state:
    • 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.
    • The maximum number of items to be printed on each excise invoice
    • Whether you are allowed partial CENVAT credits
    Maintain Registration ID NUMBER, Excise code number, excise registration 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.
    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 leviable 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 leviable 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
    Use
    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
    Use
    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 Utilization
    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.
    Use
    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
    Use
    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.
    Activities
    For each plant:
    • Specify whether it is a manufacturing site or a depot.
    • 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.
    Dependencies
    Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    Number of goods receipt per excise invoice.
    Multiple GR for one excise invoice, Single credit
    Multiple GR for one excise invoice, multiple credits
    Maintain Excise Groups
    Use
    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.
    Activities
    1. Create one excise group for each set of registers that you need to keep.
    1. Assign the excise groups to plants.
    2. Maintain whether this Excise group is for a depot or not.
    3. 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 avail 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 creates' 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.
    Dependencies
    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.
    Dependencies
    Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    GR Per Excise Invoice
    Multiple GR for one excise invoice , Multiple credit
    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.
    Dependencies
    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:
    Blocked stock
    Stock transport order
    Consignment stock
    Maintain Series Groups
    Use
    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.
    Activities
    • Define excise series groups based on type of outgoing document
    • Assign series group to excise registration ID
    • If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    • If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
    Example
    You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    No account postings for CENVAT in sales cycle
    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
    Use
    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
    Use
    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.
    • If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
    • 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
    Use
    In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
    Activities
    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:
    • Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
    • Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
    • Specify the conditions in the sales order that are used for excise rates.
    • 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
    Use
    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.
    Activities
    Customizing
    India&#61614;Make for Logistics – General, by choosing Taxes on Goods&#61614;the settings in Customizing Basic Excise Duties Using&#61614; Condition Technique and …&#61614;Movements Account 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
    Use
    When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
    Prerequisites
    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 Maintenance screen, which you can Master&#61614;Excise Rate access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.&#61614;Data
    You maintain the following types of data:
    • 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).
    • 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 – 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.
    • 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.
    • Material master data
    each material is assigned a chapter ID.
    • 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.
    Activities
    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 indictor 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.
    Let’s 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
    Use : 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.
    Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
    Assign Tax Code to Company Codes
    Use
    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
    Use
    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.
    • For taxes on purchases, use the condition types contained in the tax procedure.
    • For taxes on sales, use the condition types contained in the pricing procedures.
    Standard settings
    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
    Use
    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.
    Activities
    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.
    • VS1 (basic excise duty)
    • VS2 (additional excise duty)
    • VS3 (special excise duty)
    • VS5 (sales tax setoff)
    • MWS (central sales tax)
    • MW3 (local sales tax)
    • ESA (service tax)
    • ESE (service tax expense)
    Specify Excise Accounts per Excise Transaction
    Use
    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 subtransaction types, enter the accounts for each subtransaction type as well.
    Activities
    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
    Excise TT DC ind Account name
    GRPO CR CENVAT clearing account
    GRPO CR RG 23 BED account
    GRPO DR CENVAT on hld account
    Specify G/L Accounts per Excise Transaction
    Use
    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:
    • Excise group
    • Company code
    • 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:
    • Defined the G/L accounts
    • Defined the excise groups
    • 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 alltransactions.
    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 config step has to be made in Screen Sequences for Material Master.
    Following document helps you to do this configuration.
    Logistics General&#61664; 1. Go to IMG Define Structure of&#61664; Data Screen&#61664;Material Master Configuring the Material master Screen Sequence.&#61664; for each
    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 “Foreign Trade: Import Data”. Select the same and click on Subscreens 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 subscreen and ensure that the subscreen is blank.
    5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 – 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 – Import, Excise related subscreen appears.
    MASTER MAINTENANACE.:
    Transaction Code : J1ID
    1. Chapter id – Description Master : - Excise chapter id and description as per law will be maintained in this master. With out maintaining the chapter id in this master we can not proceed to other masters. Maintain the chapter id in format xxxx.xx
    2. Material / Chapter id combination :- Excisable materials with chapter id details for a plant is maintained in this master. In case of Raw and Packaging materials we will be maintaining for branch plant only. But in case of FG even CPs details will be maintained. If the material is a base material used for subcontracting then give a ‘tick’ in the check box in the coloumn subcontr’s. Choose relevant material type from drop down menu. In the coloumn GR-xref, select Multiple GR for one Excise invoice-Multiple credit from the drop down menu. Enter ‘1’ in the declared coloumn. With out this value in this coloumn the material will not be subjected to excise procedures.
    3. Material assessable Value:- In this master, plant wise (including CP plants) assessable values for FG are to be maintained. MRP per CBB and per ATC will be enetred in Net dealer price coloumn. Assessable value per CBB and per ATC will be given in Assessable value coloumn with effective date in the valid from coloumn. Since it is not possible to maintain differential MRP for the same SKU in this master, the MRP and Assessable value details for despatches from branch plant will be maintained in SD module. In this case we should not maintain the details in this master for branch SKUs and details will be maintained only for CPs.
    4. CENVAT determination :- Plant wise MODVAT input materials will be listed in this master with one of the FG as the out put material. This master will be maintained for branch plants only. If the input material is not maintained in this master MODVAT credit can not be availed.
    5. Vendor Excise details: - Vendor Excise details such as ECC no, reg no, Exc.range, Exc.div, Exc.coll, CST, LST nos, PAN no will be maintained for all Excisable materials vendors. In the coloumn Exc.ind.ve enter ‘1’. With out this value in this coloumn the MODVAT procedure will not take place. We are not maintaining SSI status in this master.
    6. Customer Excise details:- For such of those customers for whom invoices are to be raised from branch plant details are to be maintained in this master. The excise details can be blank for customers bur CST and LST no are to be entered. In the coloumn Exc.Ind.Cus. Enter ‘1’. With out this value in this coloumn, Excise invoice will not be generated for the customer.
    7. SSI rate: - We will not be maintaining this master. At the time of capturing the MODVAT details we can enter actual duty details as per the Excise invoice received from the Vendor.
    8. Excise indicator for Plant:- Excise details such as ECC no, Range etc. for the branch plant will be maintained here. In the coloumn Exc.ind.co maintain a value’1’
    9. Excise indicator for plant and vendor and Excise indicator for plant and customer: - Initial Configuration masters need not be maintained by users.
    10. Excise tax rate: - Chapter id and tax rates combination is maintained in this master. In the ExcInd coloumn enter’1’.
    11. Cess rate:- Cess rate if applicable will be maintained in this master.
    12. Exceptional material excise rates:- If differential excise rates are applicable for a material falling under same chapter id , this master will be maintained.
    13. Quantity based AED & SED: - If applicable the details will be maintained here.
    Some of the check points pertaining to Masters.
    • For raw materials, the assessable value will be picked up from PO.
    • For FG, the assessable values only for CPs are to be maintained in this master.
    • Excise indicator in Vendor / Customer excise details is mandatory.
    • Chapter ID, material Chapter ID and Excise tax rates - should contain all the relevant tax details.
    • CENVAT determination correlates the raw material to finished goods. All new materials are to be added without fail.
    • Material Chapter ID - for conversion activity (only base matl.) sub-contracting indicator has to be checked.
    • Material Chapter ID- excise indicator is to be ‘ticked’.
    • For removals from branch plant (raw material/finished goods), CST/LST numbers have to be given in the customer masters, which is used in Excise invoice printing
    Path is : IMG - Logistics General - Tax on goods movement - India
    http://help.sap.com/saphelp_47x200/helpdata/en/5a/d34a9f544811d1895e0000e8323c4f/frameset.htm
    <b>Reward if helps</b>
    Regards,
    Sai

  • Between SAP Licenses and Employee Records Realtinship

    Hi Experts
    <u>The Scenario of the issue is as below.</u>
    <b>SAP Licenses held by the company is -- numbers.
    And the employee records including PD(appraisal),PA  & OM exceeds the allowed records numbers.</b>
    Qn1 Whats the realtion between SAP license and records ?
    Qn2 How to go about in this scenario?
    Qn3. Should i prioritise the existance of records in appraisals and delete the least priority after consulting the client?anyway OM & PA records should not be deleted.
    Please throw some light on the issue.

    Abhilash,
    Usually the SAP Licenses are with respect to named users and their rights to the system....
    If you have N licences of various types and M employees accessing SAp ( M > N ) then it will be an issue .. usually for services like ESS - you have a licence called employee user and for more access you have professional licenses etc...
    You could check the type of licenses that the company has and the number of licenses of each type and also the Contract signed with SAP as to the licensing policy..
    Arun
    Hope it helps...

  • User exits used in sales and distribution?

    i need  some  user exits   that we commonly  used in sd. please if  somebody has  worked on  user exits . and  how  are  they used..
    points will be awarded  to all  for replying...
    thanks in advance
    Neha.

    Hi refer below
    It is most common that one or other time we need to use this function while configuring multi tasking & complex Prcing Architecture.
    Here Iam giving a simple guide to add fields to the Pricing Field Catalogues:
    For example you want to use field PSTYV ('Sales document item category') that is included in structure KOMP ('Pricing Communication Item') as a key for a condition table.
    When you create a condition table (Transaction V/03), however, the system does not propose the field in the field catalog.
    Condition access, field catalog, allowed fields, KOMG, KOMK, KOMP, KOMPAZ, KOMKAZ, PSTYV are the other terms which we need to know about, to add Fields.
    Reason and Prerequisites
    For technical reasons, field PSTYV was included in structure KOMP, however, not in structure KOMG ('Allowed Fields for Condition Structures').
    Proceed as follows:
    1. Call up the ABAP Dictionary (Transaction SE11) and create data type ZZPSTYV. Choose PSTYV as a domain.As a short text, you can use, for example, 'ZZ - sales document item category' and as a field label, you can use the field labels of PSTYV.Save, check and activate your entries.
    2. Call up structure KOMPAZ in the ABAP Dictionary (Transaction SE11) in the change mode and make the following entry:
    Component   Component type
    ZZPSTYV     ZZPSTYV
    Save, check and activate the change you made.
    3. Note:Because of the change in structure KOMPAZ, field ZZPSTYV is now known in structures KOMG and KOMP because structure KOMPAZ is included in both structures.
    4. Call up Transaction SPRO. Navigate to 'Sales and Distribution -> Basic Functions -> Pricing -> Pricing Control' and execute 'Define Condition Tables'.
    Choose 'Conditions: Allowed fields' and include ZZPSTYV as a new entry.
    5. Note:Now you can use field ZZPSTYV as a key field when you create a condition table Axxx.
    6. Supply the new field you defined by including the following source code line in USEREXIT_PRICING_PREPARE_TKOMP:
                  MOVE xxxx-PSTYV TO TKOMP-ZZPSTYV.
    In order processing you find the user exit in Include MV45AFZZ, and in billing document processing you find it in Include RV60AFZZ.
    Consider that you can also use this note as a help if you want to use other customer-specific fields as key fields in a condition table.
    For header fields, use structure KOMKAZ instead of structure KOMPAZ and USEREXIT_PRICING_PREPARE_TKOMK instead of USEREXIT_PRICING_PREPARE_TKOMP.
    For more information, see Transaction SPRO via the path 'Sales and Distribution -> System Modifications -> Create New Fields (Using Condition Technique) -> New Fields for Pricing' and OSS Note 21040.
    USEREXIT
      Userxits allow us to add our own functionality to SAP standard program
    without  modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
        All Userexits start with the word USEREXIT_...
    FORM USEREXIT_..
    z..
    ENDFORM.
    The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary
    customer code is inserted in the customer include starting with the z..
    in the form routine.
    e.g. USEREXIT_SAVE_DOCUMENT_PREPARE
    Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions
    instead they are using EXITs which come bundeled in enhancement packages . Neverthiless existing USEREXITS will be supported by SAP an all the newer versions of SAP.
    HOW TO FIND USEREXITS
      Userexits can be found in number of ways:
    1) To find userexits in SD module , goto object navigator(SE80) and select
        development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press
    enter and you will find all the includes which contain userexits in SD for
    different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it
    and start coding .
    Some examples of userexits in SD(SALES & DISTRIBUTION ) are:
    1)ADDING OF NEW FIELDS IN PRICING  
    In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields.
       The fields which are not in either of the two tables KOMK and KOMP
    cannot be used in pricing .Sometimes a need arises when the pricing
    is to be based on some other criteria which is not present in the form of fields in either of the two tables.
      This problem can be solved by using USEREXITS which are provided for pricing in SD.
      Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is
    USEREXIT_PRICING_PREPARE_TKOMP  or
    USEREXIT_PRICING_PREPARE_TKOMK
    Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
    In the case of userexit which will be called when invoicing is done ,these
    are provided in the include RY60AFZZ which is in the standard SAP
    program SAPMV45A. The name of the userexits are same. i.e
    USEREXIT_PRICING_PREPARE_TKOMP  or
    USEREXIT_PRICING_PREPARE_TKOMK
    These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely
    created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that
    has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
    Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose
    includes are provided in each of them .
    To create the field in header data(KOMK) the include provided is KOMKAZ
    and to create the field in item data(KOMP) the include provided is KOMPAZ.
    One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
    2)The other method of finding userexit is to find the word USEREXIT in the
    associated program of the transaction for which we want to determine userexit using SE38.
    3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
    Some other examples of userexits in SD are:
    USEREXIT_NUMBER_RANGE
    This userexit is used to assign a different internal document number to the
    sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .
    USEREXIT_SAVE_DOCUMENT_PREPARE
    This userexit is used to insert the ABAP code which will be called when
    the document (sales order VA01) is just about to be saved.This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.
    Exits & Enhancements
    There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.
    These are different from USEREXIT in the way that they are implemented
    in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits .
       These start from the word EXIT_ followed by the program name and then followed by a three digit number.
    e.g.  EXIT_SAPMV45A_002
      This exit is found in SD in enhancement V45A0002.
    TYPES OF EXITS
    1)MENU EXITS
    2)FUNCTION EXITS
    3)TABLE EXITS
    4)SCREEN EXITS
    5)KEYWORD EXITS
    6)FIELD EXITS
    We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit , it is required to create the project by using CMOD
    selecting the enhancement e.g. V45A0002 and selecting the component
    (one which fulfills our need) i.e the exit which will be implemented in SMOD and after coding has been done the project has to be activated.
      An exit can be coded only once.
    FUNCTION EXITS
      These are used to add functionality through ABAP code . These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any tupe of exit including function exits.
       The function exits are called from the standard SAP program in the form
    of ABAP statement
    CALL CUSTOMER-FUNCTION 'NNN'
    This is in contrast to USEREXITs where PERFORM statement is used to call
    the required userexit.
    To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its compnents the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.
    e.g.
    ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation
        To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located
    in enhancement no V45A0002 . Before we can choose the exit we have to
    create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components . In the components you will see the
    exit EXIT_SAPMV45A_002 . This exit is used for our purpose.
      Double clicking on this exit will takes us to function builder (SE37) . This
    function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is  E_KUNNR
    of type KNA1-KUNNR i.e if we move the desired customer name to this
    structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order.
    This function also contains a customer include ZXVVA04 . This include
    will be used to write our custom code .
      Double clicking on this include and it will prompt us that this include does not exists do you want to create this object ,select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
    e.g. E_KUNNR = 301.
    Activate the include and Activate the project. Now when ever the SALES ORDER will be created , sold-to-party field will come up with a predefined
    customer .
    FIELD EXITS
      The field exits are managed,created,activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.
      The format of field exit is :
    FIELD_EXIT_dataelement_A-Z or 0-9
       If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.
       The function module associated with field exit shows two parameters
    INPUT and OUTPUT.  Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3 , We can write our own code to change the output parameter depending upon our requirements.
        Before the field exit can have any effect the system profile parameter
    ABAP/FIELDEXIT in all the application servers should be set to YES
    ABAP/FIELDEXIT = YES.

  • Database Lite License and App Tutorial

    Hello,
    I'm looking for information regarding oracle database lite licensing and if any one could provide me with demo/tutorial on an application built using oracle jdev with ADF for mobile that uses oracle lite.
    Currently I have developed a demo mobile browser application (using oracle ADF) that does not use oracle lite and works only in connected mode. Any documentation on how to go about with oracle lite and work on offline mode/ synchronization would help me.
    I have a fair idea on licenses, Please correct me if I'm wrong or require any other,
    Oracle Database Enterprise or Standard Edition,
    Oracle Mobile Server,
    Oracle Weblogic Server,
    ADF Runtime licenses
    Greatly appreciate your input.
    Thanks and Regards

    Hi,
    Related to Oracle Lite you need to license:
    - the Oracle Lite Mobile Server
    - the Oracle Lite client (for each device)
    If you want to have an aproach check any online store of Oracle, but anyway you will have to contact an Oracle Partner for licensing, discounts, etc... if your partner know about mobile ;-)
    https://shop.oracle.com/pls/ostore/f?p=ostore:product:4500444252482991::NO:RP,3:P3_LPI:4509478177681805719950
    https://shop.oracle.com/pls/ostore/f?p=ostore:product:4500444252482991::NO:RP,3:P3_LPI:4509426259321805719944
    I hope it helps you
    Regards,
    T.

  • SOA suite: configure a new oc4j container, licensing and support

    Hi
    We have a SOA suite installation (10.1.3.4).
    Default installation is containing a OC4J_SOA running the esb, bpel etc.
    Now we have a java ear (java web service), and would like to deploy this to a dedicated oc4j container.
    So we want to configure a new oc4j instance named oc4j_jws.
    Actually, we have already done this, and it is looking good.
    Now I only want to make sure the configuration of a new oc4j container is not violating any licensing and support agreements.
    We have soa suite license.
    I believe a soa suite license allows for configuration of additional oc4j containers.

    The adding of oc4j instances is at least well documented within the Oracle Application Server Administrator's Guide:
    http://download.oracle.com/docs/cd/B31017_01/core.1013/b28940/reconfig.htm

  • Total Cycle of Sell and Distribution

    HI
    Will gurus please tell me the Total Cycle of Sell and Distribution?
    thanks in advace,
    Best Regards,
    Juan.

    SD Configuration:
    Enterprise Structure:
    1. Maintaining Sales Organization
    Sales Organization is an organizational unit responsible for the sale of certain products or services.
    IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
    2. Assigning Sales Organization to Company Code
    This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
    3. Maintaining Distribution Channel
    Distribution Channel is the way, in which Products or Services reach Customers.
    IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
    4. Assigning Distribution Channel to Sales Organization
    This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
    5. Maintaining Division
    Division is a way of grouping materials, products, or services.
    IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
    6. Assigning Division to Sales Organization
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
    7. Setting up Sales Area
    All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
    IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
    8. Assigning Sales Organization- Distribution Channel- Plant
    Plant is created ny MM Consultant.
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
    9. Define Shipping Points
    Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
    IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
    10 Assigning Shipping Point to Plant
    This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
    IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
    Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
    11. Defining Common Distribution Channels for Master Data
    Use
    The purpose of this activity is to define distribution channels which have common master data..
    Procedure
    Access the activity using one of the following navigation options:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
    Transaction Code: VOR1
    12. Defining Common Divisions for Master DataUse
    The purpose of this activity is to define distribution channels which have common master data..
    Procedure
    Access the activity using one of the following navigation options:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
    Transaction Code: VOR2
    Pricing Procedure
    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure (T.Code: OVKK). Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
    5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
    Normal Sales Order Cycle:-
    Step 1: Sales Document Type
    IMG > Sales and Distribution > Sales > Sales Documents >
    Sales Document Header:
    1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
    2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
    3. Assign Sales Area To Sales Document Types:
    A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
    B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
    Sales Document Item:
    1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
    2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
    Schedule Line:
    1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
    2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
    Step 2:
    IMG > Logistic Execution > Shipping > Deliveries >
    1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
    2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
    3. Define Number Ranges for Deliveries: Ensure to maintain number range.
    Step 3:
    IMG > Sales and Distribution > Billing >
    1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
    2. Define Number Range For Billing Documents: Ensure to maintain number range.
    3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
    Note: Ensure that Copy Control settings are done
    Sales Order to Sales Order (QT --> OR): VTAA
    Sales Order to Delivery (OR --> LF): VTLA
    Sales Order to Billing (OR --> F1): VTFA
    Delivery to Billing(LF --> F2): VTFL
    Billing to Sales Order (F2 --> RE): VTAF
    The configuration differs from scenario to scenario & requirement of the client.
    Regards,
    Rajesh Banka
    Reward point if useful.

  • Buglet in AdobeLibrary1.jsx

    I thought I'd point out a technical bug in one of the functions in AdobeLibrary1.jsx. The function file.getExtension() can return wrong results when the filename has no extension because (on Windows, at least) parts of the pathname can have "." in them. This isn't real common, but is possible. So if you pass the filename "c:/bob/ted.alice/jack" to your function, it will return ".alice/jack" as the extension which is not technically correct. In reality, it should return "" since there is no extension.
    In my own code, I've used a regular expression /\.[^\/\\]*$/ which is a period, followed by some number of non-path separator characters at the end of the string and this handles both cases.
    --John

    [email protected] wrote:
    > I think you need to use brackets with the exec method of the re eg
    >
    > var re = /\.([^\.\/\\]+$)/;
    > var reResultsAr = re.exec(targetstring);
    > var firstBracket = reResultsAr[1];
    >
    > I better admit that I have not tested this, I'm just going from the Core Javascript Ref 1.5.
    >
    > Andrew
    I knew about doing this, but he wanted a one liner, i.e. one that just used
    regexp to return a result. It's not possible with JavaScripts regexp implementation.
    Also, you don't need to use RegExp.exec: String.match will give you the same
    behaviour.
    And, if you really want to get it all on one line, do it like this:
    ((RegExp.__tmp = str.match(/\.([^\.\/\\]+$)/)) ? RegExp.__tmp[1] : undefined)
    While something like this is (almost) obvious to me, I can't say that most PS
    scripters would understand it at first glance.
    ciao,
    -X

  • Server 2012 Standard license and VM license for windows instances

    Hi,
    A question about VM instances on standard server 2012 license exists here 
    I  cannot link it here as my account is not verified. The topic is titled "Windows Server 2012 Standard License and VMs"
    My question is tad different...
    If I understand this correctly, 1 windows server standard license provides support for 1 Physical Operating System Environment (The VM Host /  POSE) and permission to run 2 Virtual Operating System Environment(VOSE).
    Does this imply that I can install 2 additional instances of Windows Server 2012 Standard Edition on the permitted 2 VM instances on the server? Or... should I purchase additional licenses for each VOSE that runs windows?
    Does the standard license provide rights to run  2 Virtual instances AND offer install and activation rights for 2 MS windows (virtual) environments AND install and activation rights for the windows host?
    If license is require for each instance of server 2012 running on the VM ... can I avoid purchasing additional licenses for operating systems, say, if I run 2 Centos operating system instances in 2 VOSE?
    Please help!
    Thanks.

    Licensing questions should be asked of a trained Microsoft licensing specialist.  I haven't seen one of those lurking in this forum.  www.microsoft.com/licensing.
    That said, licenses are assigned to the physical host, not to VMs.  The License you assign to the host grants you the "right to run" addition virtual operating system environments running Windows Server.  It does not grant you additional licenses. 
    Licensing for Microsoft Windows Server operating system is controlled by Microsoft.  Licensing for any other operating system is not covered by the virtualization rights of the Windows Server operating system.  Therefore, if the CentOS virtual machines
    are properly licensed by whoever licenses them, you can run however many instances that license allows.
    A single Standard Edition license can be installed on the physical host granting you the right to run up to two virtual instances of Standard Edition.  However, if you run additional services, such as file services or Active Directory or IIS, etc.,
    on the physical instance, that means you can only run one additional virtual instance of Windows Server.
    Free advice is worth every cent.
    .:|:.:|:. tim

  • Oracle Trading Community Architecture (TCA) licensing and Marketing?

    Our organisation owns fully Oracle Finance (Receivables, payables, gl and cash management, HR and Payroll and Oracle Sales and Oracle Marketing. We rely heavily on the Trading Community Architecture (Oracle TCA) and store all customer data there (party names, phone/fax/email, addresses etc.).
    However, we do not use any Oracle Sales or Oracle Marketing functionality - we simply create 'Customer' records using the Oracle Sales and Marketing WEB JSP front ends.
    We would like to stop using Oracle Sales and Marketing an stop buying the licenses and maintencance for this and reinvest in other Oracle products.
    Can you tell us - if we 'get rid of' Oracle Sales and Marketing can we still 'write' to the Oracle TCA using the API's that Oracle provides (something we already do today) or will we lose the right to create records to be stored in the TCA (like apps_fnd.hz_parties , contact_points, hz_locations etc.).

    You would think that would be the case -- however they are quite incompetent.
    Any one else have a suggestion?

  • Identification of Core and Distribution Layer Design

    Hi 
    I am a CCNA certified and I am doing a job as an IT technician here in UAE. I'm the only IT person in my company. Having no prior experience in networking field, I find myself in a pickle. With the help of CDP, I have figured out the network diagram. I am told that there is a COLLAPSED CORE network running in my company. I cannot identify the Core switches here. My question is how to identify the the core switches? We have two internet connections in two separate buildings. Can somebody please help me out. Please..

    Generally speaking with a L2 access layer to L3 distribution switches the default gateways of the vlans are on the distribution switches.
    The core switches are used when you need to interconnect multiple distribution switches eg. a campus LAN type environment.
    In many sites if you only have one building the core and distribution switches are the same pair of switches but to be precise the default gateways are not on the core but the distribution switches.
    If you have a separate pair of core switches you usually connect your distribution switches using L3 links so again the STP root for the vlans would actually be the distribution switches for the vlans they route for and not the core switches.
    Separate core switches are basically just a high speed interconnect between your distribution pairs and should be left to do that so the routing between vlans, acls etc. are done locally on the distribution switches and only traffic for remote vlans/IP subnets ie. those on other distribution switches would go via the core switches.
    If the same pair of switches is used for both functions then all routing between vlans and routing to remote networks is done by that pair.
    Jon

  • Universal Connection Pool license and release policy

    Hi,
    the Oracle JDBC drivers are licensed by the "Oracle Technology Network Development and Distribution License Terms" which allows you to distribute the JDBC drivers with your software without the need to purchase any additional license from Oracle.
    UCP is licensed by the "Oracle Technology Network Developer License Terms". This license is the same you get for your development version of the database itself, meaning that you are not allowed to use the software for any production use or development of an already released software.
    This is irritating, since I cannot see that I can purchase a license for UCP to distribute UCP with my software. In addition, the version of UCP currently available at oracle.com is not the most current one (11.2.0.1.0; Oracle database patchset 11.2.0.2.0 contains UCP version 11.2.0.2.0).
    Another issue is that the connection pool implementation bundled with the Oracle JDBC driver is deprecated, so UCP is the only option to go with in the long run.
    Could someone help me to clarify the licence and release strategy for UCP?
    Thanks,
    Ulf

    You can either require a customer to download it themselves or perhaps even automate the download as part of your install.
    Other than that I can only mention that my expectation is that you will not get an answer from Oracle (a rep) unless you have a monetary relationship with them. If you have a good customer that has purchased an Oracle license they might be able to ask for you via their support license.

  • New .TV (pets, recipe, etc.) and Viacom channels not in zap2it or Tivo guides

    So, it's been about a month since the new .tv channels came out and two days since the Viacom HD channels were introduced.  And zap2it.com, Tivo, etc. all still don't list ANY of the new channels in their programming guides.
    I've opened cases with Tivo.  With Zap2it.  With Verizon.  Everyone points fingers saying it's the other's fault.
    In the meantime, for the .TV channels that got added a while back, if you go to zap2it, or Tivo, you get "loor633" for channel name and "to be announced" for guide info for pets.tv.  You get "loor599" for Cars.tv.  You get "loor674" for MYDestination.tv.  Etc.
    And for the Viacom channels, you also get nothing.  Just blank space with "to be announced" for programming info.
    From what I understand, Verizon needs to tell Tribune that their channel lineup has changed.  And Tribune, Zap2it and Tivo all claim that Verizon hasn't done that.  Verizon, of course, is silent on the matter and the "fiber solutions center" says there is nothing they can do right now and that channel info for the .tv and Verizon channels might get added to online guides in a few MONTHS!?!?!?!?!?!?
    Why does this seem to be a problem with Verizon's lineup and no one else's?  When I had Dish, Zap2it would have updated listings within 2 hours of new channel additions.  When I had Charter, both Zap2it and Tivo had channel guide info for new channels usually the day BEFORE the channel was added.  But Verizon doesn't seem to provide Tribune with new channel info / guide data at all.
    Having had FIOS for less than two months, I'm not happy.  I'm almost certain the goal is for Verizon to get me to dump my lifetime Tivo service and instead pay them $15.99 for their DVR.  But trust me -- I'd rather go back to Charter first.
    Message Edited by skierrob2 on 06-24-2009 10:44 AM

    I do not understand why you folks are blaming Verizon for this. Please give me a moment to explain my theory.
    First of all, I have been for a long time a very dissatisfied user of the FiOS Guide data. So dissatisfied that late last year I sent an email to Verizon's CEO expressing my dissatisfaction, and providing examples and pointers to various forum threads discussing the problem. I received maybe 4 or 5 phone calls about the issue, no resolution, but I was told the procedure for the FiOS Guide was this:
    Each channel (say ESPN, whatever) develops the data, and sends it to FYI Television of Grand Prairie, TX (in the DFW area). FYI gathers the schedule info from all of the channel providers and once a day sends that data to Verizon. Verizon then inputs the data to the Guide and bingo, we see it, good or bad (lots and lots of bad IMO). I have no way to know if this is really the process, but this is the way it was explained and it makes sense to me.
    Now, lets talk about one of the other guide providers for the Tivo or whatever. It seems to me that a very similar process would have to take place: channel to guide data collector to actual guide data provider (maybe the last two are one and the same?).
    Now, where would Verizon be in this process for the other guide data providers? Seems to me nowhere, it should be the responsibility of the channel to notify the data provider that the channel is now on FiOS, what the channel name and number is, etc.
    I am sure you will disagree with me, but where am I wrong? It seems to me you should be complaining to the channel providers, not Verizon.
    (jumping into the foxhole....)
    Justin
    Verizon FiOS TV, Internet, and phone
    IMG 1.6.2, Build 08.58
    Keller, TX 76248

  • Licensing and costs for Creative Cloud for teams on small company

    Hello,
    I have a few questions regarding the teams solution.  They  are:
    1- Is the license by user or by computer?
    2- What is the actual cost of Creative Cloud for Teams ( small companies with less than 100 employees).  In some sections it states monthly cost of 69,99€ while others state 49,99€.
    3- Assuming the monthly cost of 69,99€ does this cost covers all products listed ( ilustrator, photoshop, dreamweaver, premiere,...) for a single user or  is that the cost per user and per product?
    4- How long do I have to keep the contract? Only 1 year?  If I want to cancel when should I communicate? or I just need to set on the console 0 users?
    5 - Assuming I have only one creative user can the admin console be installed in a different machine (e.g. network admin) without the need of an extra license? 
    6 - If I acquire 1 license and decide to drop it 1 year and 1 month after will I pay 1 year plus that month or do I need to pay the 2 years?
    Thanks for your feedback,
    Regards,
    Pedro

    Hello,
    I have a few questions regarding the teams solution.  They  are:
    1- Is the license by user or by computer?
    2- What is the actual cost of Creative Cloud for Teams ( small companies with less than 100 employees).  In some sections it states monthly cost of 69,99€ while others state 49,99€.
    3- Assuming the monthly cost of 69,99€ does this cost covers all products listed ( ilustrator, photoshop, dreamweaver, premiere,...) for a single user or  is that the cost per user and per product?
    4- How long do I have to keep the contract? Only 1 year?  If I want to cancel when should I communicate? or I just need to set on the console 0 users?
    5 - Assuming I have only one creative user can the admin console be installed in a different machine (e.g. network admin) without the need of an extra license? 
    6 - If I acquire 1 license and decide to drop it 1 year and 1 month after will I pay 1 year plus that month or do I need to pay the 2 years?
    Thanks for your feedback,
    Regards,
    Pedro

Maybe you are looking for