Series not defined for journal entry

Hello Sir
I have defined two series namely "SCPL" and "New1"
                Start No    Last No
SCPL        10001       3000
New1         3001        30000
Now i have made "SCPL" series as default for A/R Invoices and "New1" series as default for rest of the documents like A/R Credit memo,Journal Entry etc...
Now when I try to add an A/R Invoice , it gives me error message "Series not defined for journal entry"..??    But i have defined New1 series as default for Journal Entry

Hi,
In the series defined for journal entry,set document series as default for which default journal entries will be posted automatically.
Ex.For delivey,return,invoice journal entry will be generated automatically,so if you a series like JESYS08 indicating system automated journal entry.This series should be set as default.
If you have further issue let me know.

Similar Messages

DTW - Series not deifned for Journal Entry

2007B
Importing AP invoices thru DTW.
using Document Series
The document series assigned for AP Invoice is "APINV" and the same document series is selected for JE also.
The code for APINV is "7"
The field in DTW to define the document series is "Series" and the series code is given (eg : "7")
DTW gives error "series not defined for Journal Entry Application defined or object defined.."
where as when tried to create an AP Invoice manually, it was successful.
what could be the issue?
vijay

I managed to find the issue.
IN the DTW template,
the field, "handwritten' was tYES, which I changed to tNO as we follow document series and numbering series.
nothing is entered in the 'docnum' field.
now I get the error " to generate this document, first define document series'
vijay

Excise modvat accounts not defined for EWPO

Dear Experts,
when I click on 'Balance Choose' tab in J1IIN, it is showing an error message "Excise modvat accounts not defined for EWPO transaction and 60 excise group.Message no. 8I402" though I have maintain 'Excise account assignment table' in "Tax on goods movement>India>account determination>specify G/L accounts per excise transaction". I searched in that forum, but I didnt get no proper solution.

Hi
Check your entries
'Excise account assignment table' in "Tax on goods movement>India>account determination>specify G/L accounts per excise transaction
EWPO          CR Credit     CLEAR CENVAT clearing account
EWPO          DR Debit     RG23AED RG 23 AED account
EWPO          DR Debit     RG23AT1 RG 23 AT1 Account
EWPO          DR Debit     RG23BED RG 23 BED account
EWPO          DR Debit     RG23ECS RG 23 ECS Account
EWPO          DR Debit     RG23SED RG 23 SED account
regards
Prashanth
Edited by: Prashanth@SD on Apr 12, 2011 2:00 PM

Excise modvat accounts not defined for DLFC transaction and excise group

Dear Experts,
Iam raising this question after checking all the contents related to Sub Transaction type in SDN.
My prob is: for raw material sales scenario i have created order delivery and invoice. For Invoice i have done account determination with a different G/L in VKOA. Now i have to create an excise invoice and the accounting entry for central ED on sales should go to different G/L account. for account determination i have done the following settings:
Maintained Sub transaction type in
IMG -> Logistics - General -> Tax on Goods movement -> India -> Basic Settings
->Maintain Sub Transaction types
IMG -> Logistics - General -> Tax on Goods movement -> India ->
Account determination -> Specify Excise Accounts per Excise Transaction.
Here against DLFC sub transaction Type is maintained..
Also
IMG -> Logistics - General -> Tax on Goods movement -> India -> Account determination -> Specify G/L Accounts per Excise Transaction
Here maintained Excise group with DLFC Company Code subtransaction type, chart of accounts and all required GL Account .
But when the iam creating Excise Invoice in J1IIN and clicking on Subtransaction type-F4, no entries are shown. No values found is the message in green. Message no. DH801
If i use subtransaction type and enter billing document and enter, the following error message comes:
"Excise modvat accounts not defined for DLFC transaction and excise group"
Iam unable to understand why the subtransaction type maintained is not showing in TCODE J1IIN?
Regards

For the error message DH801, please check note 840911
Excise modvat accounts not defined for
DLFC transaction and excise group"
Please check your G/L assignments "Specify G/L Accounts per Excise Transaction"
thanks
G. Lakshmipathi

Error - Excise modvat accounts not defined for DLFC transaction and 01 exci

Dear All,
Getting below error while doing J1IIN - Posting Excise invoice for Sale.
"Excise modvat accounts not defined for DLFC transaction and 01 excise group"
I checked with the settings GL are assigned to for DLFC and 01 excise group.
Is anywhere else I need to mantain the modvat GL
Regards,
Rakesh

Check if you are using any subtransaction type along with excise transaction type.
Excise group, ETT, company code, sub transaction type (if any), Chart of account, Modvat account (pls maintain all the entries over here) search for modavat clearing field and maintain it.
BR
Edited by: Sujoy on Jan 15, 2010 9:45 AM

VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,

i am learning SAP PP and i hv ides 4.7,
now WHEN SAVING ORDER i.e DURING COST CALCULATION I GET A MESSAGE THAT VERSION 0 IS NOT DEFINED FOR FISACL YEAR 2007,
ON ANALYSING IT LEADS TO T.CODE OKEV BUT HERE SYSTEM DOES NOT PERMIT TO CHANGE THE VERSION, BUT IN ECC 5.0 IT ALLOWS ,
WHAT IS THE PROBLEM, CAN ANY ONE PL. HELP ME,
analysis of error gives following message:
Activation of the indicator is not permitted
Message no. KT253
Diagnosis
You activated an indicator (Plan, Actual, WIP/results analysis or Variance calculation ) in the basic settings for version 1 in controlling area 1000. However, a higher order of settings (general version definition) prevents you from setting this indicator in version 1.
Note
The following should be taken into account when maintaining a version:
In general version definition you decide whether a version is allowed for
     Panning (with the Plan indicator)
     Actual data update (with the Actual indicator)
Note: In Overhead Cost Controlling, actual data is updated in operational version 0.
Actual versions different from 0 are found at present only for delta versions in Activity Based Costing (CO-ABC), and when you work with parallel assesment ( additional versions):
     A data version from results and WIP determination manages (indicator WIP)
     Another version from variance determination manages (indicator Variance)
     A version for exclusive use (field exclusive application)
You must maintain the version basic settings for each controlling area in which you want to update transaction data. General version definition restricts the settings possible for the controlling area:
     If general version definition does not allow plan and/or actual data update for version, this applies to the version in all controlling areas. If plan and/or actual data updating is allowed for a version in general definition, this can be reset for each controlling area separately (unmark the plan or actual indicator).
     Delta versions in ABC may not be used for parallel valuations in the actual; the same goes for versions with exclusive applications. In both cases, the valuation fields may not be maintained.
To set indicators WIP/Results- or Variance-determination the following conditions apply:
     Both indicators may be set only during setup for the controlling area, when they are already established in the higher level general version definition
     If either indicator is already active in the data bank, then the actual indicator may not be subsequently activated
     If the actual indicator is inactive and either of these indicators is active, then the valuations in the corresponding versions and in version "000" must agree
     If the actual indicator is active, then both indicators must be activated
Versions 0 and 1 are used regularly for various purposes by the system, which sets the following limitations/restrictions:
     Version 0 must always be available. It cannot be used exclusively. The plan and actual indicators must always be active.
     The actual indicator may not be activated in version 1.
If these conditions are violated during version maintenance, error messages are issued. There are three types of error message:
1. While maintaining the general version definition, you can only make changes if they do not violate the conditions outlined above.
2. While maintaining the basic settings in the controlling area, the entries must remain consistent with the higher level entries.
3. You want to maintain version 0 or 1. The restrictions outlined above apply.
Use the "Extras" menu option to display the structure of the entries in the complex data object version:
     Select a version and choose Extras -> Version use.
The SAP System shows which controlling areas use this version.
     Select Extras -> Versions in CO area
This displays all versions used in the current controlling area.
The subordinate entries in the hierarchy (settings for each fiscal year, strategic Activity-Based Costing: transactions for a delta versions) will also be shown for both cases.
Procedure
Do not activate the indicator, or change the higher order of settings in the general version definition.

Raj,
What are you trying to change?
To me you are not suppose to make any changes, you need to select the version "0" and then hit "Settings for each Fiscal year" subfolder.... here you copy the settings of 2006 and change the year to 2007. This should resolve the problem.
Regards,
Prasobh

While creating sales order got error version "0" is not defined for company

Hi,
i got a error while creating a sales order(va01) ,i got an error
saying that "version 0(zero) is not defined for company code
if there is any solution please provide....
Thanks&regards
kishore kumar

Go to TCODE:OKEQ
1)select version 0 here and ext select settings for each fiscal year under controlling area settings
2)give your controlling area XXXX and version 0 then enter
3)select new entries maintain data for new year 2008.
Hope this will give u
Sri

Error saying 'Posting period 000 is not defined for fiscal year variant K4'

Hi All,
   When I try to add a new entry in the transaction OB52, I get an error message saying 'Posting period 000 is not defined for fiscal year variant K4'. The entry that I add is,
Variant           : 0001
Account Type: +
From Period    : 1
Year               : 1995
To Period        : 12
Year               : 2010
From Period2 : 13
Year               : 2000
To period2      : 16
Year               : 2010
Please let me know what customising needs to be done to solve this issue.
Thanks a ton.
Best Regards,
Jeff

Hi,
Hava you checked in OB52 screen, by default 0001 posting period variant will be there for +, A, D, K, S account types.
If it is already existed in your OB52 screen, you won't create one more record with the same name. You have to edit the existing 0001 posting period with new values.
Thanks
Chandra

" Unit of measure ****** is not defined; check your entry in table T006

I´m Trying to create a material from MDM to SAP and I´m monitoring the IDOC in WE05 and i get the next message:
" Unit of measure ****** is not defined; check your entry
Message no. M3490
Diagnosis
The key for the unit of measure you entered is not defined in table T006.
Procedure
Define the unit of measure through Customizing (Materials Management). "
In MDM we are sending as remote key the SAP Code and this code exists in the table T006, but in the information of failed IDOC say:
" Messages have been issued: number 0000000000184470
Message no. MK101
Diagnosis
During inbound processing for the IDoc, messages have arisen while checking material data. "
If someone has information about it ,pls I´ll appreciate your answer.
Regards Itzell T.

I´m Trying to create a material from MDM to SAP and I´m monitoring the IDOC in WE05 and i get the next message:
" Unit of measure ****** is not defined; check your entry
Message no. M3490
Diagnosis
The key for the unit of measure you entered is not defined in table T006.
Procedure
Define the unit of measure through Customizing (Materials Management). "
In MDM we are sending as remote key the SAP Code and this code exists in the table T006, but in the information of failed IDOC say:
" Messages have been issued: number 0000000000184470
Message no. MK101
Diagnosis
During inbound processing for the IDoc, messages have arisen while checking material data. "
If someone has information about it ,pls I´ll appreciate your answer.
Regards Itzell T.
Hi Itzell T,
      While creating the material the unit of measurement which is entered is not existing in the SAP System. The unit of measurement entered during creation of material is cross checked from enteries of check table T006.
      So, functional consultant should take care of this issue just let him know the message.
   He know what problem actually is and fix the problem as Ankur had said.

Error as unit of measure PC not defined for language RO while creation ofPO

Hi GUYS,
When am trying to create a PO in ME21N transaction i got error as below,
unit of measure PC not defined for language RU
Message no. 06079
Table 006A contains no entry for this unit of measure
Please let me know what action to be taken from my side to over come this issue.
Note: If i check the related vendor i could able to view that the language maintained as RU.
Cheers,
Kumar.S

Hi Jurgen,
Thanks for your reply once again.
As mentioned by you earlier i have tried to login with languae RU in Q system but unfortunately i got an error saying taht language not installed.
Also we found for Language - EN and UOM - PC has been maintianed in T006A table.But if i check for lanugage - RU and UOM PC combinatoin has not manintaned in T006A table.
Please let me know how to maintain the values in this table T006A for combination Lang - RU and UOM - PC.
Please revert back with your soilution.
Note: I have tried in SM30 but failed due to below error
The maintenance dialog for T006A is incomplete or not defined
Cheers,
Kumar.S

Unit of measure PCS not defined for language FR

Dear Gurus,
I try to raise a PO in ME21N, when saving the order, I am being prompted by the system with the following message:
"Unit of measure PCS not defined for language FR"
I then went to MM02 to check the material master data "Sales Text" Tab.
There the only language available is English, so I clicked on the "Language Maintained" Tab and created a new language for French.
The problem is that when I want to save the changes, the system prompts me with the following message:
"Blank texts exist in the following languages: French and English, these texts will be deleted"
Then the Material Master Data closes and no changes have been made.
Can you please guide me through step by step of what I have to do to be able to populate the field "PCS" for pieces in French so that it is taken into account in the Material Master Data and by extension in a PO.
Thanks for your help.
KInd regards
Chris

Hi Chris,
Goto T code CUNI. In the first screen click on GOTO-Translation-dimension.
Enter EN in Source language and FR in Target.Maintain the entry there.

Unit of measure EA not defined for language PT

Hello,
Vendor Communication is maintained in "Portuguese language-PT", while creation of Scheduling agreement system will given the below error, bcz Scheduling agreement will taken the Langause from vendr master
"Unit of measure EA not defined for language PT"
Table 006A contains no entry for this unit of measure.
We have cross checked Material master and maintained the "langauge-PT" in material master additional data.
Checked T006A table for "EA" found for language "EN, DE, CN etc. not for "PT" how to maintain T006A table for Portuguase langauge.
Regards
Mahesh Naik

>
Mahesh Naik wrote:
> Hello,
>
> Suppose we have changed the source langauge "EN" to Target Langauge"PT" is it change all the Unit from EN to PT. after that how the system will pick english language's
No, it just gives you all the units maintained in that source language as a proposal to enter the description in target language PT, there will not be any change to the source language EN while maintaining a translation.

Account 113000 3000 not defined for tax postings

hi
while generating invoice
getting the follwing error.
"Account 113000 3000 not defined for tax postings"\
here 3000 is company code.
wats the solution for this...

Hi
OK, you need to change back your G/L account, not to be defined as a VAT account.
Then, go to Financial Accounting / Contract Accounts Receivable and Payable / Basic Functions / Postings and Documents / Document / Define Account Assignments for Automatic Postings / Automatic G/L Account Determination / Define Accounts for Sales/Purchase Tax.
Check there if any of the accounts you entered is 113000. If that is the case, correct the entry.
Bogdan

Sales document item is not defined for this transaction in Pur.Order

hi,
At the time of convertion of pr to po one error message received.
Sales document item 46 000010 is not defined for the transaction
Message no. V1198
Diagnosis
You have tried to carry out a business transaction for this sales and distribution document item which, for this item, is not allowed.
This may be due to the fact that this item is not part of a make-to-order production with cost management in the sales order.
Procedure
Please check your entries.
this is MAKE TO ORDER SCENARIO THIS ERROR IS FOR RAW MATERIAL CONVERTION AGAINST SALES ORDER.

Hi,
Check in material master MRP3 view there is field called strategy group where you have option to define the planning strategy like make to order/make to stock & like.
Regards
Ravi Shankar.

Tax category DE 2 is not defined for country 1

Hi to all,
We are in retail project while changing the article master following data is coming automatically to tax data in general data DE Germany MWST Output Tax O Unbranded Other. When I save the article master, i am getting following error.
Tax category is not defined for country DE
Message no. M3019
Diagnosis
The combination of values you have entered is not defined in the system.
Procedure
Check your entries, and choose a valid value or combination of values with F4.
If you want the value(s) to be defined in the system, contact your systems administrator.
Detail error E M3 019 : Tax category DE 2 is not defined for country 1
Regards
Govind

Hi Anil,
Allready it was maintained
Regards
Govind

Series not defined for journal entry

Similar Messages

Maybe you are looking for