Order capture settings in SAP

Customer is having serious issues with legacy order capture - orders come in via EDI, PC Apps, Mobile Devices.  The existing system that handles the process today has been heavily modified and is not operating efficiently.
Suppose the requirement gathering is completed and they wanna replace the legacy system by SAP.
So my question here is that, when they gonna implement the SAP, what would be the settings/ configuration needs to be done to capture the Order via EDI, PC Apps and mobile devices in the system from SD point of view?
Thank you.
Juhi Singhania

Hi Mukund,
Thanks for the reply. Do you have any document related to the step by step configuration/customization for EDI in the above discussed scenerio? i would like to request you to please fwd it to me.
and in the other scenerio of PC apps and mobile devices, what do we need  to do as frm the functional side?
My email id is:
[email protected]
Thanks much
juhi

Similar Messages

  • Cin settings relates sap sd

    hello sap guru's
    Can any one please help me?
    Related CIN settings in SAP SD.
    In my business process have factory and export under bond pricing procedure.

    Hi,
    CIN determines taxes based on the chapter-id of the material. There are 2 levels for rate determination. First the system will check if there is an exceptional rate available. If this is available then that rate is picked up. This rate could be for a material or material and customer combination. If there are no exceptions then the system looks for chapter-id of that material. The customer will have an excise tax status which along with the plant status will give a final excise status. Based on the excise status and the chapter-id the rates are maintained.
    Can I change the tax rates retrospectively?
    You can change the excise rates with any given validity period. After making the changes you will have to update the sales orders if the new tax rates have to be considered for future deliveries.
    Can I have a different rate for incoming and outgoing transactions for the same material?
    You can maintain exceptional rates for either incoming or outgoing based on the volume of exceptions data.
    What do I do if I have one chapter-id for incoming and another for outgoing and material code is the same?
    Along with exceptional rate maintenance you can maintain the chapter-id which should be used for the outgoing transactions. This chapter-id will be used only for copying on to the document and will not be used for rate determination.
    Can I have some more additional rates?You can maintain multiple excise indicators and based on that you can have additional
    rates.
    What will happen if I have multiple rates with overlapping validity periods for the same chapter-id and tax indicator?
    While picking up the rate for a given transaction system will check for that validity period where the valid from is the maximum but with in the pricing date and based on that pick up the rate applicable.
    How does CIN do the pricing?
    CIN uses R3 condition technique for pricing along with the pricing formulae. Details are available in the CIN knowledge bank. Template pricing procedures are provided for various sales scenarios.
    How many tax codes do I need?
    The number of tax codes will directly depend on how you want to account the sales tax. You can have CST and LST being determined by the same tax code if both can be accrued into the same account. Instead if you need separate account determination then you need separate tax codes. Also based on the tax concessions available you need to decide the various tax rates which need to be mapped.
    How do I open up more than one tax classification?
    CIN comes with default customization to open up the tax classificvation fields. The procedure is as follows. You need to define as many condition types as the number of tax classification fields. Tbe following procedure could be used.
    • SPRO - Sales and distribution -Basic functions-Taxes - Tax
    determination rules For Country 'IN' make entries as follows (This
    is precustomized in client 000 )
    - Seq 1 - UTXJ
    - Seq 2 - JTX1
    - Seq 3 - JTX2
    - Seq 4 - JTX3
    In SPRO - Sales and Distribution - Basic functions - Taxes
    Determine tax relevancy of master records
    How do I handle concessional excise?
    This is explained in SAP note 335577. Having opened up the new tax classification
    fields you might have to do the following
    --> Customer taxes maintain the possible values for JTX3 . Each unique value should denote one concession rate. For eg 1 - normal excise duty
    --> Maintain the JTX3 value against the form code in J1IT -Define Form types
    Maintain the customer tax classification in customer master if the customer has got
    excise exemption
    --> Maintain the excise indicator in J1ID for the customer and form code and this indicator gives the final indicator
    --> Forms database is used for determination of whether the form has arrived or not at the time of billing.
    --> The tax classification value gets defaulted from the customer master in the sales order. This can be changed in the header
    billing data if required
    How do I handle sales tax concessions?
    SPRO - Sales and distribution -Basic functions-Taxes - Tax determination rules For Country 'IN' make entries as follows (This is precustomized in client 000 )
    - Seq 1 - UTXJ
    - Seq 2 - JTX1
    - Seq 3 - JTX2
    - Seq 4 - JTX3
    -> Taxes - Determine tax relevancy of master records - Customer taxes maintain the possible values for JTX1 and JTX2. Each unique value should denote one concession rate. For eg 1 - 4% . Multiple forms could correspond to a single rate. JTX1 could be used for CST and JTX2 for LST. (UTXJ could be freely used by the customers as earlier )
    -> Maintain the tax classification in customer master as well as
    material master ( Sales org data 2)
    Build access sequences based on these new fields to point to the correct sales tax code You might have to have a new access based on region of delivering plant and region of ship to party
    Basically Cin is divided in to two types: Difference between TAXINJ and TAXINN
    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 points 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 (TAXINJ) 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 (TAXINN) as follows:
    • JINFAC (Sales from manufacturing plants)
    • JINEXP (Export sales)
    • JINDEP (Sales from depots)
    • JINSTK (Stock transfers)
    TAXINJ & TAXINN are Tax Procedures in India. TAXINJ is old version & TAX INN is new version. Both has its own advantage & disadvantage.
    Upto 4.6C & partially 4.7 version of SAP, TAXINJ was used. TAXINJ is formula based calculation, in which we maintain the tax rate in Tax Code itself. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST & permutation & combination of these, we require that many Tax Codes. For example:
    Tax Code: A1
    Taxes: 16% Excise Duty + 2% Education Cess + 12% VAT
    Tax Code: A2
    Taxes: 16% Excise Duty + 2% Education Cess + 8% VAT
    Tax Code: A3
    Taxes: 12% Excise Duty + 2% Education Cess + 12% VAT
    Tax Code: A3
    Taxes: 12% Excise Duty + 2% Education Cess + 8% VAT
    From 4.7 version onwards of SAP, TAXINN is being recommended & used. TAXINN is more user friendly & condition record based. In TAXINN, Tax Codes are statistical & of not much relevance, but are required to be maintained in condition record for taxes condition type. This makes Tax Codes simpler. The implication is that if say we are having product range such that say Excise rate differes for separate chapter ID, VAT, CST, we need not have the tax codes to that combination. For example:
    Tax Code: A1
    Can be used for any rate of excise duty, as tax code is only required to be maintained statistically in condition record.
    Tax Code: A2
    Can be used for any rate of VAT, as tax code is only required to be maintained statistically in condition record
    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 depot
    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
    Make for Logistics – General, by India the settings in Customizing Basic  Excise Duties Usingchoosing Taxes on Goods Movements Account Settings Determination.Condition Technique and …
    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 Excise Rate access from the SAP EasyMaintenance screen, which you can Master Data Access screen by choosing Indirect Taxes Excise Rate Maintenance.
    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 sub transaction types, enter the accounts for each sub transaction 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 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 config step has to be made in Screen Sequences for Material Master.
    Following document helps you to do this configuration.
     1. Go to IMG Define Structure of Logistics General Material Master Configuring the Material master Screen Sequence.Data Screen 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.
    CIN - INDIAN TRANSACTION CODES
    Transaction Codes for India
    Transaction
    Action
    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 challans
    J1IFR
    List subcontracting challans
    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
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Migrate all Open Sales Orders From Legacy System (SAP) To SAP System using

    Hi Experts,
                 I've to Migrate all Open Sales Orders From Legacy System (SAP) To SAP System using Business Objects with a new SALES ORDER DOCUMENT NUMBER referencing the older one.
               I'll get all the required data with field in an excel file.
                 Does any standard transaction exist for it ? Or how to go ahead with it ?
    Thanks and regards,
    Jyoti Shankar

    Hi
    If you are checking for CREATE option then Sales Doc Type
    For more Info goto SWO1 transaction -> BUS2032 --> DIsplay --> Execute --> There SELECT the method which you want to perform... There you can fine the MANDATORY parameters also....
    Or in DISPLAY mode PLACE Cursor on the Required Method and CLick the PARAMETERS button on toolbar...
    That will show the MANDATORY parameters...
    Reward if helpful....
    Message was edited by:
            Enter the Dragon

  • Sony Z1U HDV Capture Settings for FCP 6.0

    Hi, I am shooting a project on Sony's HVR-Z1U HDV camcorder at HDV 60i NTSC. Does anyone have suggestions for settings to capture the material into FCP. I have FCP Version 6, part of the FC Studio 2 upgrade.
    Appreciate any feedback!

    There are definiitely some advantages to editing in DV rather than HDV for easy workflow and faster renders, etc.
    To capture, you'll have to get the settingns on the deck and in FCP to match. If you have the deck/camera set to HDV then choose the appropriate easy setup in FCP such as HDV 1080i60. If you want to capture as DV, then set the deck to downconvert to DV, and choose the DV NTSC easy setup. You'll want to check the anamorphic box for you capture settings and sequences, but keep in mind if your are working with DV or any SD format, that the anamorphic setting can be esaily applied to clips and sequences after creation or capture.
    When you export your web clips with compressor, figure out a square-pixel frame size that is some multiple of 16:9.

  • Capture Settings for uncompressed Video Vs DV Video

    Im capturing footage from Digibeta masters via a J30 deck using a single SDI cable connected to my black magic extreme, (captured using the Blackmagic uncompressed 10 bit setting) editing in FCP and exporting to SD dvd via compressor using "dvd best quality 90 mins anamorphic".
    Up untill today i had been using the same workflow EXCEPT i had been capturing over firewire using DV PAL anamorphic to work in the DV PAL format.
    Comparing the final result of both workflows im not seeing a huge difference (the original footage is the same in both cases).
    Are there any capture settings i can play with that will improve the quality of the final product or should i be looking at the bitrates in compressor instead?
    I just want to make sure im not arsing up the capture and that i am capturing as much info as i can from the digibeta masters. The files created from he digi's are a lot larger then the files from the Dv stuff but i just dont feel im seeing that on screen - any advice?
    thanks,
    S

    All the original footage was shot on 35mm by a pro cinematographer - me:) Each project was mastered to Digibeta. What i want to do is show that footage in its best "light" so to speak, but i am limited to presenting it on SD DVD until Blu-ray takes off.
    Up untill recently i had been using the Digi to DV to DVD workflow i had described above. With a recent desktop upgrade i am now recapturing all the same material from the same Digimasters using the uncompressed 10bit to dvd workflow descibed above so that i can avoid the afrementioned dv compression in the middle.
    Obviously i can see a difference between uncompressed and Dv footage natively but when i view them both on DVD on a PAL monitor i cant see as big a difference as i had hoped i would see.
    can i improve this difference with my capture settings or do i need to work on my dvd bitrate settings or a combination of both?
    S

  • Batch capture settings do not match project settings

    Batch capture audio settings do not conform to project settings-
    PROJECT SETTINGS ON CREATION OF NEW PROJECT:
    For editing with IEEE1394 (FireWire/i.LINK) DV equipment.
    Standard NTSC video (4:3 interlaced).
    48kHz (16 bit) audio.
    Drop-Frame Timecode numbering.
    General
    Editing mode: DV NTSC
    Timebase: 29.97fps
    Video Settings
    Frame size: 720h 480v (0.9091)
    Frame rate: 29.97 frames/second
    Pixel Aspect Ratio: D1/DV NTSC (0.9091)
    Fields: Lower Field First
    Audio Settings
    Sample rate: 48000 samples/second
    Default Sequence
    Total video tracks: 3
    Master track type: Stereo
    Mono tracks: 0
    Please note audio setting for project 48kHz (16 bit) audio.
    When I set for batch capture by creating off-line clips using the "Log Clip" option the off-line clip shows audio as
    32KHZ 16-bit  everyting else is correct as project settings.
    Just prior to creating the off-line batch capture clip I had sucessfully captured from the same device using the same tape shot with the above settings including 48khz 16-bit audio by using standard " Capture" by setting in & out then clicking Capture>In/Out.
    I've looked at capture settings etc...unable to determine to change audio settings etc or why the audio settings under batch capture do not conform to project settings...
    Any ideas?
    Tnx,
    mick

    Thanks for your reply, Harm....
    Well now...having negated all the possibilities you listed, I decided to do a an actual batch capture with clips which I previously logged which reported audio at 32kHz instead of the project setting of 48kHz:
    1. two clips  were selected from the same device/tape ( both selected from the logging util which erroneously reported audio at 32kHz) for the batch
    2. both clips captured "flawlessly"
    3. both clips after the batch capture then reported audio as being 48kHz
    Btw, I also did a batch capture from the same device/tape in Pr 6.x...and it reported and captured at 48khz...I must say, I must prefer the legacy version of Pr 6 for batch capture which creates a log .pbl file which can then be easily exported as a csv to and .xls etc..IMO, much more useful...and useable..
    Mi dos pesos(.002US)
    So it would appear there is some kind of bug in the Pr cs4 batch capture util that is erroneously reporting audio settings?
    Should this go to the devel as a possible bug?
    Tnx,
    mick

  • TV@ Plus, what video capture settings to use?

     I have a TV@ Plus and am unsure what video capture settings to use. I've had it for several months and solved my audio problems and need to know what Video Input Format, Capture Format (Profile), Capture - Size, Quality, Bit Rate and Audio Format settings to use. Should I use the same settings for all input sources or do I use different settings for CATV and S-video inputs? It seems to be OK with my current settings as far as capture and playback goes, I'm OK on the hardware part but with tech detatails I'm a bit  .
     I will be using it to capture from CATV, DVD and VCR input sources for later recording to DVD's. I use a GoDVD! CT-2 connected to the S-video input for recording Macrovision protected media to the HDD.
     My computer sound is monitor mounted stereo speakers.
     Thanks in advance for any helpful replies.

    Quote from: HenryW on 12-September-06, 04:25:48
    I have a TV@ Plus and am unsure what video capture settings to use. I've had it for several months and solved my audio problems and need to know what Video Input Format, Capture Format (Profile), Capture - Size, Quality, Bit Rate and Audio Format settings to use.
    I already had transferred and converted some of my old VHS and VCD movie collections into DVDs (using Composite Input).
    The higher the bit rate the better quality video output you will have - but bigger file size.
    To give you an example:
    A 2 hour video captured on MPEG set at 4000/bps will be translated it to 3.58GB. More than enough to be written on a 4.7 DVD.
    For audio bit rates, you can choose from 128/bps to 224/bps. As for me I set it to 224/bps. Again the bigger bit rates the better audio output. And don't forget to slide up the audio record level to 100%. That will give you a better and clearer recorded audio output.

  • Calling DOO standard web service in ADF custom order Capture form

    Hi
    I am trying to call the standard DOO web service in my ADF form and I am using web service data control to call that service. But when I am dragging and drooping the method in my page with the parameters needed for that particular method and try to run the page. Its giving a null pointer exception. The main parameter for that method is _payload which wants an EBM to be passed to it.
    DOO is a distributed Order Orchestration which is part of SCM fusion module. In fusion we can capture the order from different places from a legacy system from an EBS or any other application and then that captured order is passed to
    DOO of fusion by calling a standard web service. But we don't have a order capture form built in ADF from where we can enter order and then pass this info to the DOO web service.
    EBM is Enterprise business message,it is an xml format file which is passed to the DOO of fusion.It accept only EBM format xml in which capture order data is dere with EBM header and the data area which contains the order information.
    The name of the method in web service which is called in j developer is SalesOrderOrchestrationService_pt_SubmitTransformAssignLaunch(__payload). payload is the parameter which accepts the EBM file.
    The sample of an EBM or the xml which is passed to this method of web service as a payload is below.
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
    <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <wsse:UsernameToken>
    <wsse:Username>ALALL</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">ssiER3#1</wsse:Password>
    </wsse:UsernameToken>
    </wsse:Security>
    </soap:Header>
    <soap:Body xmlns:ns1="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/SalesOrder/V2">
    <ProcessSalesOrderFulfillmentEBM xmlns="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/SalesOrder/V2" xmlns:coresalesorder="http://xmlns.oracle.com/EnterpriseObjects/Core/EBO/SalesOrder/V2">
    <corecom:EBMHeader xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:Sender>
    <corecom:ID>LEG1</corecom:ID>
    <corecom:Application>
    <corecom:ID>CRM</corecom:ID>
    <corecom:Version>8.0</corecom:Version>
    </corecom:Application>
    <corecom:ContactName>Siebel contact</corecom:ContactName>
    <corecom:ContactEmail>[email protected]</corecom:ContactEmail>
    <corecom:ContactPhoneNumber>1234567891</corecom:ContactPhoneNumber>
    </corecom:Sender>
    </corecom:EBMHeader>
    <coresalesorder:DataArea>
    <corecom:Process responseCode="OBJECT" xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2"/>
    <coresalesorder:ProcessSalesOrderFulfillment>
    <corecom:Identification xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:BusinessComponentID schemeAgencyID="AIA_01" schemeID="SALESORDER_ID_GUID">31343933343333353331383237343632</corecom:BusinessComponentID>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="OrderNumber">TEST-ALALL-2</corecom:ID>
    <corecom:ApplicationObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="OrderId">TEST-ALALL-2</corecom:ID>
    </corecom:ApplicationObjectKey>
    </corecom:Identification>
    <coresalesorder:CurrencyCode>USD</coresalesorder:CurrencyCode>
    <coresalesorder:OrderDateTime>2013-02-04T10:58:32Z</coresalesorder:OrderDateTime>
    <coresalesorder:PartialShipmentAllowedIndicator/>
    <coresalesorder:PricingDateTime>2013-02-04T10:58:32Z</coresalesorder:PricingDateTime>
    <coresalesorder:RequestedShipDateTime/>
    <coresalesorder:FulfillmentModeCode/>
    <coresalesorder:ShipmentPriorityCode>NEXTDAY</coresalesorder:ShipmentPriorityCode>
    <coresalesorder:TypeCode>ORDER</coresalesorder:TypeCode>
    <corecom:Status xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:Code>BOOKED</corecom:Code>
    <corecom:EffectiveDateTime>2013-02-04T23:40:42</corecom:EffectiveDateTime>
    </corecom:Status>
    <corecom:CurrencyExchange xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:ConversionTypeCode/>
    <corecom:ConversionRate/>
    <corecom:ConversionRateDateTime/>
    </corecom:CurrencyExchange>
    <corecom:BusinessUnitReference xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:BusinessUnitIdentification>
    <corecom:BusinessComponentID schemeAgencyID="AIA_01" schemeID="ORGANIZATION_ID">A40A64204F0811DDBFBB6925DE4959D4</corecom:BusinessComponentID>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="InventoryOrganizationId">300000001130177</corecom:ID>
    <corecom:ApplicationObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="OrganizationId">300000001130053</corecom:ID>
    </corecom:ApplicationObjectKey>
    <corecom:AlternateObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="OrganizationId">300000001130053</corecom:ID>
    </corecom:AlternateObjectKey>
    </corecom:BusinessUnitIdentification>
    </corecom:BusinessUnitReference>
    <corecom:CustomerPartyReference xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:PartyIdentification>
    <corecom:BusinessComponentID schemeAgencyID="AIA_01" schemeID="CUSTOMERPARTY_PARTYID_GUID">2d383037373236333033353335383233</corecom:BusinessComponentID>
    <corecom:ApplicationObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="AccountId">300000002605080</corecom:ID>
    </corecom:ApplicationObjectKey>
    </corecom:PartyIdentification>
    <corecom:OrganizationName/>
    <corecom:CustomerPartyAccountIdentification>
    <corecom:BusinessComponentID schemeAgencyID="AIA_01" schemeID="CUSTOMERPARTY_ACCOUNTID_GUID">2d363038363737353331313735393632</corecom:BusinessComponentID>
    <corecom:ApplicationObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="AccountId">300000002605080</corecom:ID>
    </corecom:ApplicationObjectKey>
    </corecom:CustomerPartyAccountIdentification>
    </corecom:CustomerPartyReference>
    <coresalesorder:SalesOrderLine>
    <corecom:Identification xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:BusinessComponentID schemeAgencyID="AIA_01" schemeID="SALESORDER_LINEID_GUID">31373632363632373039363139343635</corecom:BusinessComponentID>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="LineNumber">1</corecom:ID>
    <corecom:ApplicationObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="LineId">101</corecom:ID>
    </corecom:ApplicationObjectKey>
    <corecom:AlternateObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="IntegrationId">88290</corecom:ID>
    </corecom:AlternateObjectKey>
    </corecom:Identification>
    <corecom:ParentSalesOrderLineIdentification xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:BusinessComponentID schemeAgencyID="AIA_01" schemeID="SALESORDER_LINEID_GUID">31373632363632373039363139343635</corecom:BusinessComponentID>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="LineNumber">1</corecom:ID>
    <corecom:ApplicationObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="ParentLineId"/>
    </corecom:ApplicationObjectKey>
    <corecom:AlternateObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="IntegrationId">88290</corecom:ID>
    </corecom:AlternateObjectKey>
    </corecom:ParentSalesOrderLineIdentification>
    <corecom:RootParentSalesOrderLineIdentification xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:BusinessComponentID schemeAgencyID="AIA_01" schemeID="SALESORDER_LINEID_GUID">31373632363632373039363139343635</corecom:BusinessComponentID>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="LineNumber">1</corecom:ID>
    <corecom:ApplicationObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="RootParentLineId"/>
    </corecom:ApplicationObjectKey>
    <corecom:AlternateObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="IntegrationId">90</corecom:ID>
    </corecom:AlternateObjectKey>
    </corecom:RootParentSalesOrderLineIdentification>
    <coresalesorder:SubstitutionAllowedIndicator/>
    <coresalesorder:SourceTypeCode/>
    <coresalesorder:PreferredGradeCode/>
    <coresalesorder:CatchWeightMeasure/>
    <corecom:EffectiveTimePeriod xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:StartDateTime/>
    <corecom:EndDateTime/>
    </corecom:EffectiveTimePeriod>
    <coresalesorder:GrossWeightMeasure>0</coresalesorder:GrossWeightMeasure>
    <coresalesorder:TypeCode>ORDER</coresalesorder:TypeCode>
    <coresalesorder:Description>Servers</coresalesorder:Description>
    <coresalesorder:OrderQuantity unitCode="EA">1</coresalesorder:OrderQuantity>
    <corecom:Status xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:Code>PENDING</corecom:Code>
    </corecom:Status>
    <corecom:ItemReference xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:ItemIdentification>
    <corecom:BusinessComponentID schemeAgencyID="AIA_01" schemeID="ITEM_ID_GUID">61</corecom:BusinessComponentID>
    <corecom:ContextID/>
    <corecom:AlternateObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="ProductId">AS85008</corecom:ID>
    <corecom:ContextID>300000001130177</corecom:ContextID>
    </corecom:AlternateObjectKey>
    <corecom:ApplicationObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="ProductId">AS85008</corecom:ID>
    <corecom:ContextID>300000001130177</corecom:ContextID>
    </corecom:ApplicationObjectKey>
    <corecom:CustomerItemID schemeAgencyID="SEBL_01" schemeID="ProductId"/>
    </corecom:ItemIdentification>
    <corecom:Name/>
    <corecom:TypeCode/>
    <corecom:Description>Computer</corecom:Description>
    </corecom:ItemReference>
    <coresalesorder:FulfillmentModeCode/>
    <coresalesorder:SalesOrderSchedule>
    <corecom:Identification xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:BusinessComponentID schemeAgencyID="AIA_01" schemeID="SALESORDER_SCHEDULE_GUID">31373632363632373039363139343635</corecom:BusinessComponentID>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="SalesOrderScheduleNumber">1</corecom:ID>
    <corecom:ApplicationObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="SalesOrderScheduleId">101</corecom:ID>
    </corecom:ApplicationObjectKey>
    <corecom:AlternateObjectKey>
    <corecom:ID schemeAgencyID="SEBL_01" schemeID="IntegrationId">201</corecom:ID>
    </corecom:AlternateObjectKey>
    </corecom:Identification>
    <corecom:ShipmentSet xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:Name/>
    </corecom:ShipmentSet>
    <coresalesorder:ExtendedAmount currencyCode="USD">18762.00</coresalesorder:ExtendedAmount>
    <coresalesorder:GrossWeightMeasure>0</coresalesorder:GrossWeightMeasure>
    <coresalesorder:Description>Servers</coresalesorder:Description>
    <coresalesorder:OrderQuantity unitCode="Ea">1</coresalesorder:OrderQuantity>
    <coresalesorder:RequestedShipDateTime>2013-06-25T10:58:32Z</coresalesorder:RequestedShipDateTime>
    <coresalesorder:ScheduledShipDateTime/>
    <coresalesorder:ScheduledArrivalDateTime/>
    <coresalesorder:RequestedDeliveryDateTime/>
    <coresalesorder:LatestRequestedDeliveryDateTime/>
    <coresalesorder:LatestRequestedShipDateTime/>
    <coresalesorder:LatestRequestedShipDateTime/>
    <coresalesorder:EarliestShipDateTime/>
    <coresalesorder:ShipmentPriorityCode/>
    <coresalesorder:FulfillmentModeCode/>
    <coresalesorder:FOBPointCode/>
    <coresalesorder:ModeOfTransportCode>Air</coresalesorder:ModeOfTransportCode>
    <coresalesorder:ReasonCode/>
    <coresalesorder:ServiceLevelCode>Next day air</coresalesorder:ServiceLevelCode>
    <corecom:CarrierPartyReference xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:PartyIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>10010</corecom:ID>
    <corecom:ContextID>100010023895555</corecom:ContextID>
    </corecom:ApplicationObjectKey>
    </corecom:PartyIdentification>
    </corecom:CarrierPartyReference>
    <corecom:Status xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:Code>PENDING</corecom:Code>
    </corecom:Status>
    <corecom:PaymentTerm xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:Code>4</corecom:Code>
    </corecom:PaymentTerm>
    <corecom:CustomerPurchaseOrderShipmentReference xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:PurchaseOrderLineIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>Line # 1</corecom:ID>
    </corecom:ApplicationObjectKey>
    </corecom:PurchaseOrderLineIdentification>
    <corecom:PurchaseOrderIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>PO#A1</corecom:ID>
    </corecom:ApplicationObjectKey>
    </corecom:PurchaseOrderIdentification>
    </corecom:CustomerPurchaseOrderShipmentReference>
    <corecom:UnitListPrice xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:Amount currencyCode="USD">18762.00</corecom:Amount>
    </corecom:UnitListPrice>
    <corecom:UnitSalePrice xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:Amount currencyCode="USD">18762.00</corecom:Amount>
    </corecom:UnitSalePrice>
    <corecom:ShipFromPartyReference xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:LocationReference>
    <corecom:LocationIdentification>
    <corecom:ID>100010023895555</corecom:ID>
    <corecom:ApplicationObjectKey>
    <corecom:ID>300000001130184</corecom:ID>
    <corecom:ContextID/>
    </corecom:ApplicationObjectKey>
    <corecom:AlternateObjectKey>
    <corecom:ID schemeAgencyID="AIA_01" schemeID="CUSTOMERPARTY_PARTYCONTACTID_GUID">300000001201066</corecom:ID>
    </corecom:AlternateObjectKey>
    </corecom:LocationIdentification>
    </corecom:LocationReference>
    </corecom:ShipFromPartyReference>
    <coresalesorder:SalesOrderShipToParty xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:CustomerPartyAccountContactIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>300000003212320</corecom:ID>
    <corecom:ContextID/>
    </corecom:ApplicationObjectKey>
    </corecom:CustomerPartyAccountContactIdentification>
    <corecom:CustomerPartyAccountSiteUsageIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>300000003679213</corecom:ID>
    <corecom:ContextID/>
    </corecom:ApplicationObjectKey>
    </corecom:CustomerPartyAccountSiteUsageIdentification>
    <corecom:ShipToPartyReference>
    <corecom:CustomerPartyAccountIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>300000002605080</corecom:ID>
    <corecom:ContextID/>
    </corecom:ApplicationObjectKey>
    </corecom:CustomerPartyAccountIdentification>
    </corecom:ShipToPartyReference>
    </coresalesorder:SalesOrderShipToParty>
    <coresalesorder:SalesOrderBillToParty xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:CustomerPartyAccountContactIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>300000003212320</corecom:ID>
    <corecom:ContextID/>
    </corecom:ApplicationObjectKey>
    </corecom:CustomerPartyAccountContactIdentification>
    <corecom:CustomerPartyAccountSiteUsageIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>300000003679211</corecom:ID>
    <corecom:ContextID/>
    </corecom:ApplicationObjectKey>
    </corecom:CustomerPartyAccountSiteUsageIdentification>
    <corecom:BillToPartyReference>
    <corecom:CustomerPartyAccountIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>300000002605080</corecom:ID>
    <corecom:ContextID/>
    </corecom:ApplicationObjectKey>
    </corecom:CustomerPartyAccountIdentification>
    </corecom:BillToPartyReference>
    </coresalesorder:SalesOrderBillToParty>
    <coresalesorder:ShipmentInstruction/>
    <coresalesorder:PackingInstruction/>
    <coresalesorder:TotalAmount/>
    <coresalesorder:PricingDateTime/>
    <coresalesorder:PurchaseDate/>
    </coresalesorder:SalesOrderSchedule>
    </coresalesorder:SalesOrderLine>
    <coresalesorder:SalesOrderCustomerParty xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:CustomerPartyAccountContactIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID/>
    <corecom:ContextID/>
    </corecom:ApplicationObjectKey>
    </corecom:CustomerPartyAccountContactIdentification>
    <corecom:CustomerPartyReference>
    <corecom:CustomerPartyAccountIdentification>
    <corecom:ApplicationObjectKey>
    <corecom:ID>300000002605080</corecom:ID>
    <corecom:ContextID/>
    </corecom:ApplicationObjectKey>
    </corecom:CustomerPartyAccountIdentification>
    </corecom:CustomerPartyReference>
    </coresalesorder:SalesOrderCustomerParty>
    <coresalesorder:ModeOfTransportCode/>
    <coresalesorder:ServiceLevelCode/>
    <coresalesorder:TotalAmount currencyCode="USD">70.94</coresalesorder:TotalAmount>
    <coresalesorder:EarliestShipDateTime/>
    <coresalesorder:PricingDateTime/>
    <corecom:SourceDocumentReference xmlns:corecom="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2">
    <corecom:DocumentIdentification>
    <corecom:ID>ShipOrderGenericProcess</corecom:ID>
    </corecom:DocumentIdentification>
    </corecom:SourceDocumentReference>
    </coresalesorder:ProcessSalesOrderFulfillment>
    </coresalesorder:DataArea>
    </ProcessSalesOrderFulfillmentEBM>
    </soap:Body>
    </soap:Envelope>
    Can I get a help on this and my question is in j developer when I make a web service data control and drag and drop that method in to my pages submit button with text box taking this EBM or xml as entry and when I submit this its giving a null pointer exception. How can I overcome this.
    Regards
    Satbir Singh

    Hi,
    for complex services like this the recommendation is to use a JAX-WS proxy client, put a POJO in front (wrapper) to access information and methods to expose in the application and create a POJO DC from the wrapper. This not only is more powerful and allows you to intercept data calls, it also gives you a netter option for debugging and error handling in case something fails.
    Frank

  • Migrating Open Sales Order From Legacy System (SAP) To SAP System

    Hi Experts,
                 I've to Migrate all Open Sales Orders From Legacy System (SAP) To SAP System using Business Objects with a new SALES ORDER DOCUMENT NUMBER referencing the older one.
               I'll get all the required data with field in an excel file.
                 Does any standard transaction exist for it ? Or how to go ahead with it ?
    Thanks and regards,
    Jyoti Shankar

    hi jyothi ,
       there are lot of ways of doing it depending on data upload volume it will be decided .
    1) thru abap bdc program which directly uses XL sheet data and creates SO using bapi/FMs.
    2) using scat.functional consultant should be good enough to use this.
    3)lsmw-laborious procedure but achievable.
      reward if helps !!!!!

  • Capture settings for Canon XL2 shot in: 16:9 24p 2:3:3:2

    I just boght the XL2 and FCP, and need to capture a four hour interview I shot today in 16:9 24p 2:3:3:2. I just don't know how to set up the capture settings correctly.
    Thanks guys,
    Wes
    iMac G5   Mac OS X (10.4.7)   2.0 GHz, 400Gb Hard Drive, 2Gb Ram, 250Gb External

    Well, 2:3:#:2 pulldown refers to the way your camera flags the frames while they're recorded, in other words there's not real 24P recording while using tape, because video runs @ 29.97fps ,(what the camera does is to tell to your editing machine that it has to spread the 1st frame over the two first fields the second frame over the next three fields the third frame again over three fields and so on, from there it why it's call 2:3:3:2 pulldown) so in fact to capture true 24P for editing you have to remove the pulldown and remember,if you later are going to edit to tape you'll have to re-apply the pulldown so it prints well to a 29.97 device.
    Hope I was clear enough

  • DVCPRO 50 capture settings from SDX900

    I captured some DVCPRO50 footage that I had shot on an SDX900 set at 24pa progressive. I captured it using the anamorphic DVCPRO50 preset. Looking at the footage, some clips have an interlaced frame every 3 progressive frames, while other clips have 2 interlaced and 2 progressive. These were all shot and captured with the same settings, so I'm assuming one of the capture settings are wrong.

    OK I finally went back and figured it out. I had originally used the DVCPRO50 24p capture setting, but footage was recorded at 30 with a pulldown, whichever the SDX uses for its 24p interlaced setting. I used the generic DVCPRO50 anamorphic capture setting and then the Reverse Telecine in Cinema Tools did the trick like you said. Thanks for the help

  • FCP7 Capture Settings - HDV Audio

    I am capturing just fine with FCP 7 and a Canon HV30 camcorder. However, I would like to be able to turn off the audio monitoring while the capturing is in progress.
    Previous versions of FCP did not have audio monitoring with HDV cameras, and wasn't a problem. Now, I can't get it to be quiet without muting my system audio.
    The HDV capture settings are not editable, nor can I duplicate the preset.
    The capture window clip settings does not include a preview toggle.
    Any ideas?

    bump... HDV audio monitoring during capture, I have been unable to figure out how to shut it off.

  • Issue with Service Contracts Order Capture Integration (OKSOCINT) program

    Hi,
    Could anyone tell me how to turn off trace for Service Contracts Order Capture Integration (OKSOCINT) program? Trace is not enabled at conc. program level or user level, but the program still generates large trace files. It is scheduled to run every hour. I could not find anything on metalink regarding this. We're on 11.5.9 version of Apps. Any help is appreciated.
    TIA,
    Alka

    Sorry Nagamohan, I got sidetracked by other issues and could not reply. Here's the beginning part of the trace file that shows the concurrent program name (see the name in bold):
    Dump file /PRD1/code/oracle/11.5.9/prd1db/10.2.0/admin/PRD1_oprddb/udump/prd1_ora_29363.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    ORACLE_HOME = /PRD1/code/oracle/11.5.9/prd1db/10.2.0
    System name: HP-UX
    Node name: oprddb1
    Release: B.11.11
    Version: U
    Machine: 9000/800
    Instance name: PRD1
    Redo thread mounted by this instance: 1
    Oracle process number: 120
    Unix process pid: 29363, image: oracle@oprddb1
    *** 2009-04-09 10:01:03.120
    *** ACTION NAME:(Concurrent Request) 2009-04-09 10:01:03.119
    *** MODULE NAME:(OKSOCINT) 2009-04-09 10:01:03.119
    *** SERVICE NAME:(PRD1) 2009-04-09 10:01:03.119
    *** SESSION ID:(1077.23949) 2009-04-09 10:01:03.119
    =====================
    Regards,
    Alka

  • Capture Screen in SAP

    Hi,
    can you ppl help in this thing.How to capture screen from SAP and store it in the presentation server(any given path).Is it possible to do that.
    Kind Regards.

    Hi,
    I think there is no any such FM or functionality you can done with ABAP, but i hope you can try using some external screen capture application and call that from ABAP to capture screen.
    See EXECUTE Method of  class CL_GUI_FRONTEND_SERVICES which may help you.
    Regards
    Karthik D

  • Function module converts sy-datum to date according to user settings in SAP

    Hi experts,
    I need such a function module which converts sy-datum to a date format
    according to user settings in SAP.
    Thanks,
    Yogesh

    Use these function modules.
    CONVERSION_EXIT_PDATE_OUTPUT
    CONVERT_DATE_TO_EXTERNAL
    Please mark points if the solution was useful.
    Regards,
    Manoj

Maybe you are looking for

  • XML Publisher in Oracle Applications - Merge PDFs in Templates

    Requirement, I have PDF files stored in Huge Blob columns in a oracle apps tables. I would like to make a single PDF using the XML publisher template to merge all these PDFs into a single PDF file and show the merged PDF file, when user clicks on vie

  • Copying Files To/From External Drive: Error -36

    I recently purchased a WD 700 GB drive that I'm using as a network drive using AirportExtreme. Today, while trying to copy files from either of my internal drives to the WD drive, I get error -36 messages. If I'm copying a folder of files and click o

  • Linked charts: Error bars are not updated

    Linked charts work well: Changed values for bar graph and line graph y values in Numbers are reflected in Keynote and Numbers after "updating". However, I cannot get error bars to be updated as well. They just keep the values they had when I first pa

  • Keep getting error not vaild pdf how can i open the file

    Error msg says not a valid PDFhow can iI open

  • Deleteing report jobs from the queue

    OAS 9.0.2.0.0 on Win2K-sp4, Client Win2K-sp4. Many's the time a report job will hang up in the queue preventing other jobs from printing. Using the OEM, I can usually delete all the jobs, except the one that is "active, the one that is hanging up the