Differential invoice creation
Hi gurus,
Need urgent help..how are differentials invoices created stepwise.?
The way I am going about it is.....Sales order-Delivery- invoice-differential invoice in ref to del doc.
just the concept ? The error I am facing is that while creating a differential invoice from LF to S1, where in no relation between creating a differential invoice and cancellation, As a cancellation should not be allowed while creating a Diff. Invoice.
regards,
Vineet
Hi John,
Support package which the client is using is 4.0B 38. Whenever I am trying to create Differential invoice in Quality environment which is copy of production, I am getting these mesgs
" Ind. for differential invoice requires final eval. of all invoice cyles"
and sometimes
"Billing type OID2 contains cycls 123456789, uninvoiced cycles: &, nothing
Differential invoice control requires at least one provisional cycle"
Somehow it is working in production. So clearly, I am not missing a point here.
Can you please help me out in this.
Thank and regards
Vikram
Edited by: Vikram Saigal on Feb 10, 2009 11:27 AM
Similar Messages
-
Hi SAP Gurus,
My client requirement is to create a Differential invoice after provisional invoice. However, we don't use MAP to set provisional and differential rules. We get the pricing from external system. So, Provisional invoice is raised with the price from Sales order where as differential invoice with the avg monthly price which is coming from external system.
As there are no provisional and differential rules set, Deliveries will not be available in Billing due list(VF04) for Differential invoice creation as they are allready billed(for provisional invoice)
Can anybody suggest/share how the deliveries will be available in Billing due list for Differential invoice?
Regards,
Praveen
Edited by: Praveen Kotha on Feb 14, 2012 8:54 AMIn the copy control for the Invoice and cancellation invoice type at item category level (VTFF) you can see there the negative entry in the field 'Pos./Neg. Qnty'.
Result is - the reverse amounts are posted to in the same GLs. In conditions tab you may see the same sign.
Thanks -
Excise invoice creation incase of price increase
Dear all,
I am facing a problem in case supplementary billing scenario at my client's place.
Some times price of the material increases and that price will be effected from past date.Then a supplementary excise is created with values consisting of
Differential value + 16% excise on differential price + 2 % Ecess + 1%Hecess + sales tax against all the effected invoices previously created.
" Differential value = (New Price - Old Price)*(total invoiced quantity of the material from effected date to till now ) "
How can i create excise invoice in sap for this case, where there would be no goods movement..
With the help of my abaper i can create debitmemo with this pricing structure with some modifications in program for VFRB - Retro-Billing by individual invoice wise.
But my client is asking for excise invoice creation for this scenario but not debit memo.
Pls guide me the way to do this scenario.
Thanks in advance
Kartheek NHi,
We also have same scenario and we done work around for this solution.
Suppose i have
Base Price 1000
ED 160
ECESS 32
SECC 16
Based on the above we made Billing document VF01 and Excise Invoice through J1IIN. After sending the material there is price change and you require to raise suplementary invoice for the same, in that wat you required to do is
1. Create Sales Order with referene to main billing document
2. Create Billing document with refernce to sales order and note that the Billing category is M becasue as per standard SAP billing category M and U are only relevent for Exicse Invoice cration.
Through the above you can rraise the invoice.
If it helps provide rewards
Rgds
Gautam -
Excise invoice creation for Debit Memo or Credit Memo
Dear All,
I have to create Excise Invoice J1IIN with reference to Debit Memo in Differential Invoice Senario.
When i goto J1IIN it shows Customization for Document is missing in table Billing Reference type.
How to create Excise invoice for Order related billing.Plz solve my problem.
Award Pts for useful answers.
Thx & Regards,
PankajCIN Configuration for Excise Invoices in case of RETURNs
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 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 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Make for Logistics General, by choosing Taxes on Goodsthe settings in Customizing Basic Excise Duties Using Condition Technique and 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Excise Rate access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.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.
Lets 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.
Logistics General 1. Go to IMG Define Structure ofData ScreenMaterial Master Configuring the Material master Screen Sequence.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.
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
rewards if it helps -
Purchase Order and Invoice creation
Hi All,
I am having some fields related to Purchase order and Invoice creation, i have to find out the tables to which tables these fields belongs to.
Below are the Header fields:
Wrbtr Tcode - MIRO,
Lfsnr Tcode - MIGO,
Evertn Tcode - Me32k,
Kbetr Tcode - Me32k,
Kschl Tcode - Mek1,
Selkz Tcode - Mek1,
Werks Tcode - Mek1,
Evart Tcode - Me31k,
Frgco Tcode - Me35k,
Sddat Tcode - Me35k,
Below are the Detail fields:
Kbetr Tcode - Mek1,
Konwa Tcode - Mek1,
Lgobe Tcode - Me21n,
Planloc Tcode - Me31k,
Datab Tcode - Mek1,
Datbi Tcode - Mek1,
Fromdate Tcode - Me31k,
Todate Tcode - Me31k,
i have to retrive all these fields from tables, so plz anybody give me exact tables to use in the select quries to retrive these fields.
Thanks in advance,
Balu.Hi,
U can get the req fields as follows:
Below are the Header fields:
1)Wrbtr Tcode - MIRO- table rseg ,field-wrbtr
give belnr (invoice no ) & BUZEI(item) if known, else, give ebeln,ebelp.
2)Lfsnr Tcode - MIGO,-table mkpf,give mblnr (mat doc no ) & ZEILE(item) field-xblnr or give ebeln,ebelp
3)Kbetr Tcode - Me32k,
table:konp or konv.
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in 1 of the tables- konp or konv,wil get kbetr.
4)Kschl Tcode - Mek1,
Pass ebeln,ebelp to table ekpo, get mwskx(taxcode), u will get condition type kschl from FM -FI_TAX_GET_CONDITION_TYPES.
or
table:konh or konp or konv.
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in 1 of the tables-konh or konp or konv, wil get kschl.
5)Werks Tcode - Mek1,-table-ekpo, field-werks(give ebeln,ebelp)
Below are the Detail fields:
1)Kbetr Tcode - Mek1,
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in 1 of the tables- konp or konv,wil get kbetr.
2)Konwa Tcode - Mek1,
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in 1 of the tables- konp or konv,wil get konwa.
3)Lgobe Tcode - Me21n,give ebeln.ebelp in table ekpo, get lgort.pass lgort to table t001l, u wil get lgobe.
4)Datab Tcode - Mek1,table-konh,field datab
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in - konh ,wil get datab.
5)Datbi Tcode - Mek1,table-konh,field databi
Pass ebeln to ekko, wil get KNUMV.Pass KNUMV as KNUMH in table- konh,wil get databi.
Hope its useful to u. -
Excise Invoice creation error -Billing document does not exists
Dear Experts,
I have created supplementary sales order, billing with refernece through sales order by VF01.
Now I want to create Excise Invoice but system gives error Billing Document does not exists
I have checked billing document in VBRK table & it is showing in table.
My item categroy is L2N -and set it to C
I have assigned Billing type under Outgoing excise invoice ->Assign billing type to delivery type still my excise invoice is not generating.
Pl. guide me.
Thanks
TruptiResolved my problem.
Actually in Billing item categroy if you put SD Doc. Catg. as M you can do excise invoice even if you have not created the
outbound delivery.
So cycle will be Supplementary Sales Order->VF01 with ref. to SO->J1IIN -Excise invoice creation.
Thanks to all.
Trupti. -
How to restrict accounting doc generation while excise invoice creation
Hi,
i have to restrict accounting document generation while excise invoice creation through J1IIN.
i can't use statistical in my pricing proceedure since this is excise group and plant specific requirement.
same priicing proceedure is being used across all other excise groups and plants.
requirement is that one plant is having excemption from duties. my client wants excise duties to be calculated but should not be posted to accounting for that excise group.
can you suggest me how to map this scenario.
Thaks in advance.
Regards
SatyaHi
If it's a Deemed Export scenario then you can map this as a standard process.
Click the utilization button in the left corner, this will give you a next screen , Now here there is a pencil button .
Now click over this - this will change the color of the description and activate it. Now here if you select Deemed and save the document - There will NOT be any accounting entries for the excise document .
Try this , hopefully this will help you.
Thanks
RB -
Accounting entries at billing and excise invoice creation in J1IIN
Hello Guruz
I need to know the accouning entries at the time of billing and the excise invoice creation in J!IIN.
Thanks in advance.
Regards.Hi
At the time of Billing Customer a/c will get debited and Sales revenues a/c will get credited.
At the time of Excise Invoice Excise paid a/c will get debited and all excise duties (Cess, Basic,S cess ) will get credited.
Hope this will helps you.. -
Automatic excise invoice creation in STO scenario
Hi All,
This is related to stock transfer from Depot to manufacturing plant.
I have done the replenishment delivery at Depot. Now my requirement is automatic excise invoice creation. For that i have done the required settings like excise and series group. I have checked the Creation EI option in exciser group also.
PO(ME21n) --> VL10B --> VL02N --> VF01 (JEX) --> Automatic excise invoice once save the billing.
Once i sqve the billing, it has to create excise invoice at Depot. It is not happining.
Please let me know if i have to do any more settings.
Regards
LakshmikanthDear Lakki,
Please check, whether for Defined Excise Group:
Path: SPRO --> IMG --> Logistics General --> Tax on Goods Movement --> India --> Basic Settings --> Maintain Excise Group
Select your Excise Group and Mark the Boxes: Create EI, and Box: Depot EIs.
Have you maintained relevant setings, like:
--> Had you checked the Box: Excise Inv during Billing, under Tab: Outgoing Excise Invoice
--> Relevant checks for Depot Settings, under Tab: Depot Settings
Best Regards,
Amit -
Internal Error -2038 Invoice Creation
¡Hi! Help!
I explain my problem
I've created a vb.net 2005 application. Through DI API (SBO 2005 SP 01, patch level 20).
This application, windows forms run, it opens an SBO conection and starts a timer. Every 5 secconds the timer ticks, it
searches for custom xml files containing info needed to create/update Invoices, or Sales Orders. Whenever I find files to
process, the timer stops, documents are processed one after another and then timer continue ticking. I use one Company and
one conection open since the moment the program starts and it remains opened the whole day.
There are two servers. SAP Server, and there's another server (in this server runs my application, here I have just my app
and DI API so it connects to SAP Server) both on same Domain.
Database size is 50 GB, and it grows about 90 - 100 MB every day
The amount of invoices created is about 500/600 daily.
Problem is many times invoices creation are unsuccesfull due to one of the following errors:
OINV.Series , 'Internal error (-2038) occurred' or just OINV.Series , 'Internal error (-2038) occurred'
this makes more difficult to figure out the reason why this happen and moreover how to solve it, because as some or many of
you may know, internal error is not much explict and the causes for this error are very different.
Now, I'm certain Invoice series are OK because the same Invoice creation that fails in one moment, simply is succesfully
created after 2, 3 or even 5 or 6 tries!.
Errors increase a lot at evening, when intensive use of SBO database is taking place. However these errors use to happen
even at morning when few Invoices are created, I mean, not necessarily happen at intensive use.
Invoices are not that large. The biggest are about 10 - 12 lines.
This situation is frustrating both for my customer and myself
Has anyone experienced something similar? is this something about sbo db performance? does anyone knows if there's some kind
of document about Internal error?Hi Marcel,
I think the first thing I'd check is for deadlocks on the database. Earlier patches of SBO 2005A SP1 are known to have issues in this area (see SAP note 1113543 for an example). It would certainly fit the symptoms you are getting (ie the same document can be created without errors at a different time).
Kind Regards,
Owen -
Hi All,
I want to create Multiple Invoice Creation through BAPI or FM. For this invoice PO is the Reference.
As per requirement i have multiple PO in container, at one shot i want to create invoice realted PO as the reference.
Thanks
Amithi,
I am trying in another way - creating one proforma invoice for multiple deliveries. and with that proforma invoice trying to create excise invoice.
But i am facing problem in creating proforma with multiple deliveries because of DIFFERENT NUMBER RANGE IN HEADER (delivery)AT FOREIGN TRADE --- UNDER ORGANIZATION --- NUMBER OF FOREIGN TRADE DATA - ( which is internally assigned by the system)
If i can get where this number is assign my problem is solved
K.S.Rao -
PO creation Date and Invoice creation Date
Hi,
Can any one help me regarding which table I can look for PO creation date and Invoice creation date. I require these fields for my reporting requirement.
Thanks in advance,
Arvind.Thanks for your response Bala.
I got the Table which I require. I have one more question on this.
Can you tell me Invoice Creation Date is RBKP-BLDAT(Document Date in Document) or RBKP-BUDAT(Posting Date in the Document) and PO creation Date is EKKO-AEDAT(Date on which the record was created) or EKKO-BEDAT(Document Date in Document).
Points already rewarded. -
How to Check product warranty in CRM based on R/3 invoice creation date
Dear all,
As per our client business process, for a sales product warranty starts once after creation of Invoice in ECC system. in that case, how to perform warranty check in CRM Complaints based on ECC Invoice creation date.
Please suggest me the standard SAP solution for this. Your help will be highly appreciated
Regards
Raghu ram
Edited by: Raghu Ram on Jan 11, 2010 7:24 AMHi Raghu,
This is pure development. But it is possible.
You need to use a function module to create warranty contract in CRM against to ECC invoice with the following prerequisites
1. Same SLA should be available in both ECC and CRM (In ECC there is no SLA concept, in that case u need to maintain SLA as text component in delivery/sales order or any Z transaction document, the same can be pulled into CRM warranty contract)
2. All the products sold in ECC should be having serial number during delivery process. Then the combination of product and serial number will be created an equipment master in ECC. This equipment master should be replicated to CRM as and when it is created in ECC.
3. The partners in equipment master should be same as in invoice or sales order document in ECC
4. Addiitionally, all the products in the ECC invoice to be replaced as service material with SCN item category (We used this logic), so you can use any other logic to get service line item. You can use any common service material also as line item.
5. Male the status profile settings to release the contract once it is created and saved in CRM
6. In the complaint or service request document, set the contract determination as Unique number (I think "D")
As standard, You can create wrranty contract and assign warranty master as and when ECC invoice is created by manual method.
Hope this development logic will be useful.
Regards,
Ram. -
User Exits for Invoice creation ,cancellation and sales return
Hi Gurus,
Pl help me it's very urgent.
I did not find any user exit invoice creation so i wrote the following code in include program
MV60AF0B_BELEG_SICHERN.
This code is to update the Z*table while saving invoice ,cancellation and sales return.
The code modification is like below
FORM BELEG_SICHERN *
Buchen Fakturabelege *
FORM BELEG_SICHERN.
READ TABLE XVBRK INDEX 1.
IF SY-SUBRC NE 0.
CALL FUNCTION 'DEQUEUE_ALL'.
MESSAGE S032.
EXIT.
ENDIF.
IF SAMH_MOD = ON.
EXPORT XKOMFK TO MEMORY ID 'SDBILLDL'.
ENDIF.
DATA: CALC_TYPE.
IF REBATE_DETERMINED = 'Y'.
CALC_TYPE = 'A'.
ELSE.
CALC_TYPE = 'I'.
ENDIF.
*{ INSERT RD1K903017 1
Work Area*********************
data : wa_xvbrk type VBRKVB.
data : wa_xvbrp type vbrpvb.
data : wa_zmigo type zmigo.
data : wa_vbrp type vbrp.
Internal table Creation*******
DATA: BEGIN OF tab_XVBRP OCCURS 100.
INCLUDE STRUCTURE VBRPVB.
DATA: END OF tab_XVBRP.
data : begin of tab_vbeln occurs 10,
vbeln type vbrk-vbeln,
knumv type vbrk-knumv,
end of tab_vbeln.
data : tab_zmigo type table of zmigo.
data : tab_vbrp type table of vbrp.
*****Data declaration*************
data : v_no_of_inv type i.
data : v_vbeln_no(10) type n.
data : v_last_inv_no(10) type n.
data : v_first_inv_no(10) type c.
data : v_tot_qty type i.
data : v_frbnr type mkpf-frbnr.
*******Ranges*********************
ranges : r_vbeln for vbrk-vbeln.
*****Populating IT****************
tab_xvbrp[] = xvbrp[].
describe table xvbrk lines v_no_of_inv.
*} INSERT
CALL FUNCTION 'RV_INVOICE_DOCUMENT_ADD'
EXPORTING
VBSK_I = VBSK
WITH_POSTING = 'A'
PREISFINDUNGSART = CALC_TYPE
IMPORTING
VBSK_E = VBSK
TABLES
XKOMFK = XKOMFK
XTHEAD = XTHEAD
XVBFS = XVBFS
XVBSS = XVBSS
XVBRK = XVBRK
XVBRP = XVBRP
XVBPA = XVBPA
XKOMV = XKOMV.
*{ INSERT RD1K903017 2
data : v_count type i,v_fkimg type i .
data : v_no_of_records(10) type n.
wa_xvbrk = xvbrk.
********Selecting the last rec no from ZMIGO
select max( sr_no ) from zmigo into v_no_of_records.
*****If Distribution channel is not ZB*********
if wa_xvbrk-vtweg ne 'ZB' and ( wa_xvbrk-fkart = 'ZRIN' or wa_xvbrk-fkart = 'ZRTE' ).
if v_no_of_inv = 1. " Process only when there is one invoice
loop at tab_xvbrp into wa_xvbrp where ( matnr ne 'CDGSTP0001' and
matnr ne 'CD-RW' and
matnr ne 'CD-RW65OHS' and
matnr ne 'CABLE' and
matnr ne 'CD-R' and
matnr ne 'CDQ80N4' and
matnr ne 'GENERAL' and
matnr ne 'NERO' and
matnr ne 'OTHERS' and
matnr ne 'SPARE PARTS' and
matnr ne 'PROMO ITEM' and
matnr ne 'PROMO-1' and
matnr ne 'PROMO-2' and
matnr ne 'PROMO-3' and
matnr ne 'PROMO-4' and
matnr ne 'PROMO-5' and
matnr ne 'PROMO-6' and
matnr ne 'PROMO-7' and
matnr ne 'PROMO-8' and
matnr ne 'PROMO-9' and
matnr ne 'PROMO-10' ).
v_fkimg = wa_xvbrp-fkimg .
v_fkimg = v_fkimg / 1000.
do v_fkimg times.
v_no_of_records = v_no_of_records + 1.
wa_zmigo-sr_no = v_no_of_records.
wa_zmigo-po_no = wa_xvbrk-vbeln.
wa_zmigo-item_no = wa_xvbrp-posnr.
wa_zmigo-mblnr = wa_xmkpf-mblnr.
wa_zmigo-doc_type = wa_xvbrk-fkart.
wa_zmigo-posting_date = wa_xvbrk-fkdat.
wa_zmigo-created_on = sy-datum.
wa_zmigo-created_time = sy-uzeit.
wa_zmigo-bill_lno = v_frbnr.
wa_zmigo-material = wa_xvbrp-matnr.
wa_zmigo-inv_no = wa_xvbrk-vbeln.
wa_zmigo-inv_item_no = wa_xvbrp-posnr.
wa_zmigo-plant = wa_xvbrp-werks.
wa_zmigo-inv_date = wa_xvbrk-fkdat.
wa_zmigo-customer = wa_xvbrk-kunag.
wa_zmigo-unit = 1.
wa_zmigo-mtype = '601'.
insert into zmigo values wa_zmigo.
enddo.
clear : wa_zmigo.
endloop.
clear : v_count,v_fkimg,wa_zmigo.
refresh tab_zmigo[].
clear v_no_of_inv.
else. "When there are Split Invoices
v_last_inv_no = wa_xvbrk-vbeln.
v_vbeln_no = v_last_inv_no - v_no_of_inv + 1.
v_first_inv_no = v_vbeln_no.
sort tab_xvbrp by vbeln.
loop at tab_xvbrp into wa_xvbrp where ( matnr ne 'CDGSTP0001' and
matnr ne 'CD-RW' and
matnr ne 'CD-RW65OHS' and
matnr ne 'CABLE' and
matnr ne 'CD-R' and
matnr ne 'CDQ80N4' and
matnr ne 'GENERAL' and
matnr ne 'NERO' and
matnr ne 'OTHERS' and
matnr ne 'SPARE PARTS' and
matnr ne 'PROMO ITEM' and
matnr ne 'PROMO-1' and
matnr ne 'PROMO-2' and
matnr ne 'PROMO-3' and
matnr ne 'PROMO-4' and
matnr ne 'PROMO-5' and
matnr ne 'PROMO-6' and
matnr ne 'PROMO-7' and
matnr ne 'PROMO-8' and
matnr ne 'PROMO-9' and
matnr ne 'PROMO-10' ).
v_fkimg = wa_xvbrp-fkimg .
v_fkimg = v_fkimg / 1000.
do v_fkimg times.
v_no_of_records = v_no_of_records + 1.
wa_zmigo-sr_no = v_no_of_records.
wa_zmigo-po_no = v_vbeln_no. "wa_vbrp-vbeln.
wa_zmigo-item_no = wa_xvbrp-posnr.
wa_zmigo-mblnr = wa_xmkpf-mblnr.
wa_zmigo-doc_type = wa_xvbrk-fkart.
wa_zmigo-posting_date = wa_xvbrk-fkdat.
wa_zmigo-created_on = sy-datum.
wa_zmigo-created_time = sy-uzeit.
wa_zmigo-bill_lno = v_frbnr.
wa_zmigo-material = wa_xvbrp-matnr.
wa_zmigo-inv_no = v_vbeln_no.
wa_zmigo-inv_item_no = wa_xvbrp-posnr.
wa_zmigo-plant = wa_xvbrp-werks.
wa_zmigo-inv_date = wa_xvbrk-fkdat.
wa_zmigo-customer = wa_xvbrk-kunag.
wa_zmigo-unit = 1.
wa_zmigo-mtype = '601'.
insert into zmigo values wa_zmigo.
enddo.
clear : wa_zmigo.
at end of vbeln.
v_vbeln_no = v_vbeln_no + 1.
endat.
clear : v_count,v_fkimg,wa_zmigo.
refresh tab_zmigo[].
endloop.
endif. "End of first 2nd IF.
clear : v_no_of_inv, v_vbeln_no.
endif.
****************Sales return************************************
if wa_xvbrk-fkart = 'ZRRE' and wa_xvbrk-vtweg ne 'ZB'.
loop at tab_xvbrp into wa_xvbrp where ( matnr ne 'CDGSTP0001' and
matnr ne 'CD-RW' and
matnr ne 'CD-RW65OHS' and
matnr ne 'CABLE' and
matnr ne 'CD-R' and
matnr ne 'CDQ80N4' and
matnr ne 'GENERAL' and
matnr ne 'NERO' and
matnr ne 'OTHERS' and
matnr ne 'SPARE PARTS' and
matnr ne 'PROMO ITEM' and
matnr ne 'PROMO-1' and
matnr ne 'PROMO-2' and
matnr ne 'PROMO-3' and
matnr ne 'PROMO-4' and
matnr ne 'PROMO-5' and
matnr ne 'PROMO-6' and
matnr ne 'PROMO-7' and
matnr ne 'PROMO-8' and
matnr ne 'PROMO-9' and
matnr ne 'PROMO-10' ).
v_fkimg = wa_xvbrp-fkimg.
v_fkimg = v_fkimg / 1000.
v_tot_qty = v_tot_qty + v_fkimg.
do v_fkimg times.
v_no_of_records = v_no_of_records + 1.
wa_zmigo-sr_no = v_no_of_records.
wa_zmigo-po_no = wa_xvbrk-vbeln.
wa_zmigo-item_no = wa_xvbrp-posnr.
wa_zmigo-doc_type = wa_xvbrk-fkart.
wa_zmigo-posting_date = wa_xvbrk-fkdat.
wa_zmigo-created_on = sy-datum.
wa_zmigo-created_time = sy-uzeit.
wa_zmigo-material = wa_xvbrp-matnr.
wa_zmigo-inv_no = wa_xvbrk-vbeln.
wa_zmigo-inv_item_no = wa_xvbrp-posnr.
wa_zmigo-plant = wa_xvbrp-werks.
wa_zmigo-inv_date = wa_xvbrk-fkdat.
wa_zmigo-customer = wa_xvbrk-kunag.
wa_zmigo-unit = 1.
wa_zmigo-mtype = '651'.
condense wa_xvbrk-xblnr.
wa_zmigo-reference = wa_xvbrk-xblnr.
********Bill of lading no**
select single bill_lno from zmigo_final into v_frbnr where inv_no = wa_xvbrk-xblnr and material = wa_xvbrp-matnr.
if sy-subrc eq 0.
wa_zmigo-bill_lno = v_frbnr.
endif.
insert into zmigo values wa_zmigo.
enddo.
clear : wa_zmigo,wa_xvbrp , v_fkimg, v_frbnr.
endloop.
endif.
*******Invoice Cancellation*****************************
if wa_xvbrk-fkart = 'ZRS1' and wa_xvbrk-vtweg ne 'ZB'.
delete tab_xvbrp[] where shkzg eq 'X'.
loop at tab_xvbrp into wa_xvbrp where ( matnr ne 'CDGSTP0001' and
matnr ne 'CD-RW' and
matnr ne 'CD-RW65OHS' and
matnr ne 'CABLE' and
matnr ne 'CD-R' and
matnr ne 'CDQ80N4' and
matnr ne 'GENERAL' and
matnr ne 'NERO' and
matnr ne 'OTHERS' and
matnr ne 'SPARE PARTS' and
matnr ne 'PROMO ITEM' and
matnr ne 'PROMO-1' and
matnr ne 'PROMO-2' and
matnr ne 'PROMO-3' and
matnr ne 'PROMO-4' and
matnr ne 'PROMO-5' and
matnr ne 'PROMO-6' and
matnr ne 'PROMO-7' and
matnr ne 'PROMO-8' and
matnr ne 'PROMO-9' and
matnr ne 'PROMO-10' ).
v_fkimg = wa_xvbrp-fkimg.
v_fkimg = v_fkimg / 1000.
v_tot_qty = v_tot_qty + v_fkimg.
do v_fkimg times.
v_no_of_records = v_no_of_records + 1.
wa_zmigo-sr_no = v_no_of_records.
wa_zmigo-po_no = wa_xvbrk-vbeln.
wa_zmigo-item_no = wa_xvbrp-posnr.
wa_zmigo-doc_type = wa_xvbrk-fkart.
wa_zmigo-posting_date = wa_xvbrk-fkdat.
wa_zmigo-created_on = sy-datum.
wa_zmigo-created_time = sy-uzeit.
wa_zmigo-material = wa_xvbrp-matnr.
wa_zmigo-inv_no = wa_xvbrk-vbeln.
wa_zmigo-inv_item_no = wa_xvbrp-posnr.
wa_zmigo-plant = wa_xvbrp-werks.
wa_zmigo-inv_date = wa_xvbrk-fkdat.
wa_zmigo-customer = wa_xvbrk-kunag.
wa_zmigo-unit = 1.
condense wa_xvbrk-zuonr.
wa_zmigo-reference = wa_xvbrk-zuonr.
wa_zmigo-mtype = '602'.
********Bill of lading no**
select single bill_lno from zmigo_final into v_frbnr where inv_no = wa_xvbrk-xblnr and material = wa_xvbrp-matnr.
if sy-subrc eq 0.
wa_zmigo-bill_lno = v_frbnr.
endif.
insert into zmigo values wa_zmigo.
enddo.
clear : wa_zmigo,wa_xvbrp , v_fkimg.
endloop.
endif.
clear : v_no_of_records.
*} INSERT
CALL FUNCTION 'STACK_RESET'.
R185D-DATALOSS = SPACE.
FOLGEAUFRUF102 = SPACE.
PERFORM SETPAR_INIT.
*{ INSERT RD1K903017 3
*} INSERT
LEAVE.
ENDFORM.
This program is working fine for single user but in production where no of people are creating the invoices from different places the data is not getting updated in table ZMIGO.
sometime populating with wrong data , partial data and sometimes no updation at all.
I have used the table locking system enqueue and dequeue FM's before n after updation but still the same
thing is happening.
What could be the reason.
Looking for help very urgent any other alternate option.Hi,
Go thru these..
Enhancement
SDVFX009 Billing doc. processing KIDONO (payment reference numbe
SDVFX010 User exit item table for the customer lines
SDVFX011 Userexit for the komkcv- and kompcv-structures
V05I0001 User exits for billing index
V05N0001 User Exits for Printing Billing Docs. using POR Procedu
V60A0001 Customer functions in the billing document
V60P0001 Data provision for additional fields for display in lis
V61A0001 Customer enhancement: Pricing
SDVFX001 User exit header line in delivery to accounting
SDVFX002 User exit for A/R line (transfer to accounting)
SDVFX003 User exit: Cash clearing (transfer to accounting)
SDVFX004 User exit: G/L line (transfer to accounting)
SDVFX008 User exit: Processing of transfer structures SD-FI
SDVFX007 User exit: Billing plan during transfer to Accounting
SDVFX006 User exit: Tax line (transfer to accounting)
SDVFX005 User exit: Reserves (transfer to accounting)
Business Add-in
SD_CIN_LV60AU02 BADI for billing
If it is helpful rewards points
Regards
Pratap.M -
SAP-MM CIN Error: JTAX Access sequence missing at the time of excise invoice creation in J1IS
Dear Sir,
During creation of excise invoice with ref to material doc system give a error massage JTAX access sequence is missing. Access sequence and tables are already exist in system.
1.PO
2. GR with excise capture& post here Part-I&II are genarated.
3.Invoice
4.Return delivery with reference to above goods receipt document.(122 m.type)
5. J1IS- Creating outgoing excise invoice w.r.to return delivery material document.
JTAX Access sequence missing at the time of excise invoice creation in J1ISThe same error coming while consignment stock issue to cost center.
1.Consignment Info record with excise tax code.
2.PO consignment purchase order.
3.GR with excise capture & post here Part-I&II documents are created.
Material document created but there is no accounting document.
4.While doing Consignment stock issue to cost center system generate an error message
Access sequence JTAX missing ( ) Message no. VE306"
Maybe you are looking for
-
I don't know how to ask this question... Can you help?
I'll state right from the get-go, this is NOT a Premiere problem. This is a Windows problem, but I don't know exactly what it is. Why I'm I posting it here? It's in Premiere that I notice it the most. I can be watching my playback in Premiere fine
-
Is it possible to prevent the OS from dropping and deleting a network share shortcut?
One thing that has always bugged me about Mac OS is that when a network share becomes unresponsive or unavailable the shortcut on the desktop disappears and you get a glaring messaging that the share has been disconnected. Is there any way to prevent
-
I Need help to remove or change link on photo gallery web site menu
Hi, I am not a flash specialist. I want to insert a photogallery in my web page. I purchased on line a photo gallery Template made on flash and I am unable to desable the menu on the gallery or change the link on gallery menu to link to my other page
-
Problem in CMC login with SAP authentication type
Hi, We have installed the SAP Integration kit successfully for BO XI R2 & when I logon to CMC i am able to enable the SAP authentication and import the roles from the SAP BW system as well. But when I try to login into CMC using the 'Authentication t
-
Accessing DataGrid currentTarget from a dataGridColumn button
I am trying to access the row item clicked from within a datagrib button. Any thoughts? It seems to only accept event or mouseevent... public function onDeleteItem(e:Event):void{ trace(e.currentTarget.parent);